Page 1 of 1

Exit and next start bug

Posted: 2017-11-18, 03:56
by ron_1
Basilisk on Linux has this same bug that Firefox on Linux has. Steps to reproduce:

1) Open Basilisk and maximize, then exit by going to File >> Quit.
2) Then start Basilisk again. It should open maximized (as it was when exited) but doesn't.

However, if you exit by clicking on the "X" in the upper right-hand corner, then start Basilisk again, it will open maximized.

Basilisk 2017.11.13 (64 bit)
Linux Mint 18.2 | 64 bit | Mate

Re: Exit and next start bug

Posted: 2017-11-18, 04:37
by adesh
This has been an issue for me earlier with Firefox, and now with Pale Moon too. I never reported it as it didn't seem that important to me. I workaround the issue by stretching the unmaximized window to fill the entire screen.

Re: Exit and next start bug

Posted: 2017-11-18, 04:57
by ron_1
adesh wrote:
This has been an issue for me earlier with Firefox, and now with Pale Moon too.
I've never had this problem with Pale Moon. Only with Firefox, and now Basilisk.

Re: Exit and next start bug

Posted: 2017-12-02, 18:17
by ron_1
Bug still exists in latest version. Is this bug considered high priority, low priority, or no priority?

Re: Exit and next start bug

Posted: 2017-12-03, 02:43
by gracious1
I cannot reproduce this
Basilisk 2017.11.30 x64
Ubuntu 14.04

Re: Exit and next start bug

Posted: 2017-12-03, 04:15
by ron_1
gracious1 wrote:
I cannot reproduce this
Basilisk 2017.11.30 x64
Ubuntu 14.04
I wonder if it's a "Mint only" problem. But it's weird I don't have the same problem with Pale Moon.

Re: Exit and next start bug

Posted: 2018-03-21, 13:19
by Moonraker
Are you sure the operating system does not control this behaviour.?.Also did you make basillisk the default browser.

Re: Exit and next start bug

Posted: 2018-03-31, 04:04
by ron_1
Moonraker wrote:
Are you sure the operating system does not control this behaviour.?.Also did you make basillisk the default browser.
I don't think so. Wouldn't Pale Moon have the same issue if it did? And no, Basilisk is not my default, Pale Moon is, but I don't see what difference that could make.

Re: Exit and next start bug

Posted: 2018-03-31, 11:38
by distantpluto
It works consistently for me - close maximised and it reopens maximised. Arch with Compiz (0.8), no DE. I would suspect your Window Manager.

Re: Exit and next start bug

Posted: 2018-03-31, 13:59
by ron_1
distantpluto wrote:
It works consistently for me - close maximised and it reopens maximised. Arch with Compiz (0.8), no DE. I would suspect your Window Manager.
I don't think so as this problem started specifically with Firefox 48. Anyway, I found a work-around, but I'm not sure if it's a good idea (will probably start a new thread for it as I think it merits its own).
Off-topic:
That's the first time I heard of running no DE; how does that work?

Re: Exit and next start bug

Posted: 2018-03-31, 14:23
by Moonraker
To be honest i do not see this as a big major issue.It only takes a split second click on the maximise button and there you go,And as you pointed out by pressing on the x mark to exit seems to attain the desired result so in my mind this is not really a high priority bug.

Re: Exit and next start bug

Posted: 2018-03-31, 23:11
by Moonchild
Maybe your launcher shortcut explicitly includes the window state. In that case it will override the previous state on shutdown.

Re: Exit and next start bug

Posted: 2018-04-01, 00:18
by ron_1
Moonchild wrote:
Maybe your launcher shortcut explicitly includes the window state. In that case it will override the previous state on shutdown.
How would I check this?

Re: Exit and next start bug

Posted: 2018-04-01, 15:23
by distantpluto
Off-topic:
helloimustbegoing wrote:That's the first time I heard of running no DE; how does that work?
It's quite common actually, especially with distros like Arch. I roll my own with only what I want so it's more streamlined and efficient. I like to know exactly what's installed on my system. It's quite easy really.