Open
Bug 1246999
Opened 8 years ago
Updated 8 years ago
closing the browser window opened at startup disables the SeaMonkey menu items such as Quit and Preferences. Mac OS X
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: eric, Unassigned)
Details
Attachments
(1 file)
18.38 KB,
text/html
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 Build ID: 20151103192036 Steps to reproduce: In Preferences --> Appearance, check the checkbox for "When SeaMonkey starts up, open Browser". Alternatively I found that by unchecking all options, Browser, Mail & Newsgroups, Composer, Address Book, then SeaMonkey will automatically open a browser window anyway. Quit SeaMonkey and restart it. In order to produce this bug on my computer, I must wait at least 10 seconds here. Close the browser window that was automatically opened. In the "SeaMonkey" menu, choose Preferences or Quit. Actual results: Closing the browser window that was automatically opened at startup disables most of the menu selections in the "SeaMonkey" menu. Only Services-->Services Preferences still works. Quit and Preferences are the most useful two things that stop working. The drop down menu still drops down normally and I can click on the selections like Quit SeaMonkey, but they don't do anything. Nothing hangs. The equivalent keyboard Command+Q doesn't work either. The rest of SeaMonkey keeps working normally. OS X Force Quit does not say SeaMonkey is not responding. Force Quit SeaMonkey works. Right clicking on the SeaMonkey icon in the dock and choosing Quit works. Closing a browser window that I manually opened from Window-->Browser or Command+N does not disable the SeaMonkey menu. If in Preferences --> Appearance--> "When SeaMonkey starts up, open", I uncheck all options, Browser, Mail & Newsgroups, Composer, Address Book, then SeaMonkey will automatically open a browser window anyway. When I close that browser window the SeaMonkey menu gets disabled. If I check the box "When SeaMonkey starts up, open Mail & Newsgroups" then no browser window will automatically be opened. Then I can manually open and close browser windows, avoiding the problem of a disabled SeaMonkey menu. Not the same bug as Bug 1239620 - Firefox cannot quit on OS X. Not the same bug as Bug 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). Not the same bug as Bug 1230607 - Problem Quitting Firefox Profile (MacBook Pro El Capitan 10.11.1
Updated•8 years ago
|
OS: Unspecified → Mac OS X
Comment 1•8 years ago
|
||
I can't reproduce the problem (10.11.3) with SeaMonkey 2.39. This is with a late 2011 Macbook pro. I had my preference set to open a browser window at startup, started SeaMonkey, then waited a bit, then closed the browser window. I can open preferences from the menu and I can quit SeaMonkey. Anything special/trivial that you do might be of interest here. Do you btw see any errors in the error console (Tools --> Web Developer: Error Console)? Please list them here.
Reporter | ||
Comment 2•8 years ago
|
||
There are many warnings, but here are the errors. Timestamp: 2/10/16, 10:24:56 AM Error: TypeError: browsers[i] is undefined Source File: chrome://navigator/content/tabbrowser.xml Line: 331 Timestamp: 2/10/16, 10:25:08 AM Error: TypeError: browsers[i] is undefined Source File: chrome://navigator/content/tabbrowser.xml Line: 331
Reporter | ||
Comment 3•8 years ago
|
||
The errors in Comment 2 above were for when SeaMonkey was started while the Preferences were set to open only a browser window. When I changed Preferences to only open a Mail & Newsgroups window and restarted, the error changed to Timestamp: 2/10/16, 10:39:34 AM Error: uncaught exception: 2147942487 Source File: resource://gre/components/nsMailNewsCommandLineHandler.js Line: 41
Comment 4•8 years ago
|
||
None of those errors looks related, unfortunately. Warnings might be interesting too. This is of course when you've encountered the problem.
Comment 5•8 years ago
|
||
Btw, you're on 10.11.3? If not, does the problem persists if you upgrade?
Reporter | ||
Comment 6•8 years ago
|
||
Upon first reading that you were on 10.11.3, I updated my 10.11.2 to 10.11.3. But that didn't affect the bug. The errors and warnings are not consistent. I went back to the Preference of only opening a browser window. The problem persists, but now there are no longer any errors or warnings. When I looked the first time, there were maybe 40 or 50 warnings.
Comment 7•8 years ago
|
||
OK. I'm a bit lost here since I can't reproduce it :(
Reporter | ||
Comment 8•8 years ago
|
||
But wait. Now there's about 105 warnings. I'll copy the first 5 and maybe you can tell me there's an easy way to copy them all instead of one at a time. I deleted the "source code" part of the warnings. Timestamp: 2/10/16, 1:05:58 PM Warning: Expected declaration but found '*'. Skipped to next declaration. Source File: https://bugzilla.mozilla.org/data/assets/15939e64c7a8e5ef4f308e6c8fa65252.css?1455029430 Line: 2, Column: 1157 Timestamp: 2/10/16, 1:05:58 PM Warning: Expected declaration but found '*'. Skipped to next declaration. Source File: https://bugzilla.mozilla.org/data/assets/15939e64c7a8e5ef4f308e6c8fa65252.css?1455029430 Line: 2, Column: 1179 Timestamp: 2/10/16, 1:05:58 PM Warning: Unknown property 'zoom'. Declaration dropped. Source File: https://bugzilla.mozilla.org/data/assets/15939e64c7a8e5ef4f308e6c8fa65252.css?1455029430 Line: 2, Column: 4989 Timestamp: 2/10/16, 1:05:58 PM Warning: Expected 'none', URL, or filter function but found 'alpha('. Error in parsing value for 'filter'. Declaration dropped. Source File: https://bugzilla.mozilla.org/data/assets/15939e64c7a8e5ef4f308e6c8fa65252.css?1455029430 Line: 2, Column: 5232 Timestamp: 2/10/16, 1:05:58 PM Warning: Expected declaration but found '*'. Skipped to next declaration. Source File: https://bugzilla.mozilla.org/data/assets/15939e64c7a8e5ef4f308e6c8fa65252.css?1455029430 Line: 2, Column: 6607
Comment 9•8 years ago
|
||
These are all warnings from the website you visited, so they're unfortunately not related at all :(. A more interesting warning/error would be from a source file in SeaMonkey itself. You could also check the OS X error console and see if any warning/error pops out when trying to quit. Also, information from about:support (I think it's in the Help menu - I'm not in front of my own computer atm or you can type about:support in the address bar and hit enter (there should be a way getting all info to the clipboard) is interesting.
Reporter | ||
Comment 10•8 years ago
|
||
I need more guidance on how to provide a source file in SeaMonkey itself. I attached a file containing information from about:support. Below are the warning/errors from the OS X error console. (SeaMonkey is configured to only open a browser window at start up.) Clicking on SeaMonkey icon to start program: 2/11/16 8:53:50.000 AM kernel[0]: seamonkey[3548] triggered unnest of range 0x7fff97000000->0x7fff97200000 of DYLD shared region in VM map 0xad1c608449070261. While not abnormal for debuggers, this increases system memory footprint until the target exits. 2/11/16 8:53:50.216 AM launchservicesd[78]: SecTaskLoadEntitlements failed error=22 2/11/16 8:53:50.221 AM launchservicesd[78]: SecTaskLoadEntitlements failed error=22 2/11/16 8:53:50.243 AM WindowServer[194]: Untrusted client (pid=3548) attempted to set debug options. 2/11/16 8:53:50.453 AM seamonkey[3548]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.3 instead of 10.11.3. This is not a bug in Gestalt -- it is a documented limitation. Use NSProcessInfo's operatingSystemVersion property to get correct system version number. Call location: 2/11/16 8:53:50.454 AM seamonkey[3548]: 0 CarbonCore 0x00007fff9de5ec9b ___Gestalt_SystemVersion_block_invoke + 113 2/11/16 8:53:50.454 AM seamonkey[3548]: 1 libdispatch.dylib 0x00007fff9732433f _dispatch_client_callout + 8 2/11/16 8:53:50.454 AM seamonkey[3548]: 2 libdispatch.dylib 0x00007fff97324237 dispatch_once_f + 67 2/11/16 8:53:50.454 AM seamonkey[3548]: 3 CarbonCore 0x00007fff9ddeab47 _Gestalt_SystemVersion + 987 2/11/16 8:53:50.454 AM seamonkey[3548]: 4 CarbonCore 0x00007fff9dde9ddb Gestalt + 139 2/11/16 8:53:50.454 AM seamonkey[3548]: 5 XUL 0x00000001039734a1 vpx_reset_mmx_state + 528636 2/11/16 8:53:50.493 AM appleeventsd[54]: SecTaskLoadEntitlements failed error=22 2/11/16 8:53:55.419 AM launchservicesd[78]: SecTaskLoadEntitlements failed error=22 2/11/16 8:53:55.420 AM launchservicesd[78]: SecTaskLoadEntitlements failed error=22 After entering password for the Software Security Device: 2/11/16 8:56:08.534 AM seamonkey[3548]: GetDYLDEntryPointWithImage(/System/Library/Frameworks/AppKit.framework/Versions/Current/AppKit,_NSCreateAppKitServicesMenu) failed. 2/11/16 8:56:14.769 AM sharedfilelistd[324]: SecTaskLoadEntitlements failed error=22 When closing that browser window that was automatically opened: 2/11/16 8:57:23.766 AM launchservicesd[78]: SecTaskLoadEntitlements failed error=22 2/11/16 8:57:28.255 AM launchservicesd[78]: SecTaskLoadEntitlements failed error=22 When quitting SeaMonkey using Command+Q (but SeaMonkey doesn't quit) No errors When quitting SeaMonky successfully by right clicking on the SeaMonkey icon in the dock: 2/11/16 8:59:03.570 AM launchservicesd[78]: SecTaskLoadEntitlements failed error=22
Comment 11•8 years ago
|
||
(In reply to Eric Houg from comment #10) > I need more guidance on how to provide a source file in SeaMonkey itself. Sorry, I only ment the "source file" references in the warning messages in comment #9. Those warnings refer to a web page, so they're not relevant here (compare them to the source file reference in comment #3).
You need to log in
before you can comment on or make changes to this bug.
Description
•