1234087 - On the Mac, Cmd+Q or File→Quit do nothing, even in Safe Mode, if all windows have been closed (but the menubar is still there).

Status: RESOLVED WORKSFORME

(SeaMonkey :: OS Integration, defect)

Description

[long]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39
Build ID: 20151103192036

Steps to reproduce:

Go to Help menu and choose to restart with add-ons disabled.  Close all open seamonkey windows.  Doe Command-Q to attempt quit.


Actual results:

Nothing.



Expected results:

Seamonkey should quit

Comment 1

[Tony Mechelynck [:tonymec]]

Do you mean closing all tabs while the "Restart with Add-ons Disabled" dialog is up? Or after reaching Safe Mode? (IIRC it means two or three clicks later)

IIRC, on the Mac the menubar is distinct from all windows. Are you sure the SeaMonkey menubar was active when you hit Cmd+Q? If some other window or widget was active, then that part of the screen would be where the keystroke "fell".

On Linux, when I close the last window (e.g. by Ctrl+Shift+W), that is itself the trigger which makes SeaMonkey start its closedown operation (though with the options I chose, I get an are-you-sure dialog for attempting to close a window with more than one tab); but here it may take several minutes (even after the last window closes) for the closedown to be complete and the seamonkey process to disappear from the system. Maybe you just didn't wait long enough?

Developers: Not sure I chose the right Component.

Comment 2

[long]

Hi, I meant closing all tabs after reaching Safe Mode.  

I am sure the Seamonkey menubar was active when I attempted the Cmd + Q because choosing Quit from the File menu also does the same thing (nothing) at that point.  

I've waited hours and nothing ever happens.  

I'm 97% sure this is is a fairly new SM behavior and that it used to quit just fine in this situation.  Perhaps this started in the last 2 or 3 versions if I had to guess?

Comment 3

[Tony Mechelynck [:tonymec]]

If you get it every time it is a serious problem.

Can you reproduce it also in "normal" (i.e. "unsafe") mode? And do you have an idea about which version of SeaMonkey was the last (highest) one where you did not have the bug?

Karsten, you're on a Mac I think? And if you aren't, do you know someone who is? Can you (or can that "someone") try to reproduce the problem on SeaMonkey 2.43a1?

Comment 4

[long]

Yes, it happens in unsafe mode, that's how I first noticed it.  When I get a block of time I'll see if I can figure out what version it stopped working in.  But it may be a bit before that happens.

Comment 5

[Tony Mechelynck [:tonymec]]

(In reply to long from comment #4)
> Yes, it happens in unsafe mode, that's how I first noticed it.  When I get a
> block of time I'll see if I can figure out what version it stopped working
> in.  But it may be a bit before that happens.

OK, thanks.

Comment 6

[Tony Mechelynck [:tonymec]]

I suppose that a workaround would be opening a window ("File → New → Browser Window" or even "File → Open Web Location… → about:blank") and _then_ closing SeaMonkey. Not very elegant of course.

Comment 7

[Philip Chee]

CC Stefan who is our Mac expert.

Comment 8

[Rainer Bielefeld]

@reporter:
Still a problem for you?

Comment 9

[long]

I am not able to reproduce it currently running 2.40

Comment 10

[Rainer Bielefeld]

I close this one due to reporter's Comment 9.

@Reporter: Please feel free to reopen this Bug if if the problem reappears with a current SeaMonkey version and a current OS.