Closed
Bug 93621
Opened 23 years ago
Closed 23 years ago
View Menu Does Not Drop Down.
Categories
(SeaMonkey :: Installer, defect)
Tracking
(Not tracked)
People
(Reporter: bugzilla.t.jvance, Assigned: ssu0262)
References
Details
View menu item does not work, period. Switching skins changes nothing. Clicking on "home" changes nothing. Bug appears in empty, full, new, and original windows. When moused over, view item appears depressed, and nothing happens when I click on it. This bug did not appear in version 0.9.2 on my machine. Perhaps related to 81096, except changing skins or window content has no effect.
Reporter | ||
Comment 1•23 years ago
|
||
Cannot reproduce bug on same machine booted with Windows 2000.
Comment 2•23 years ago
|
||
I experienced the same problem after upgrading from 0.9.2 to 0.9.3 under Windows 2000. The View menu simply wouldn't drop down. Then I backed up the broken installation and reinstalled from scratch, and View worked fine. Comparing the broken and fresh trees, there seem to be files left around from a previous version in the components folder of the broken installation: 06/28/2001 11:22p 86,668 mail.xpt 06/28/2001 11:22p 6,541 psm.xpt 06/28/2001 04:50p 5,680 smime.dll xpti.dat is about 450 bytes larger in the fresh install than in the broken one. Replacing this file in my broken installation with a copy from the fresh installation seems to fix the View menu problem on my system.
I'm seeing this also on WinME with 0.9.3. Problem does not happen with 0.9.2 or 2001072703 so this is a fairly recent problem.
Reporter | ||
Comment 5•23 years ago
|
||
Uninstalling and reinstalling fixed the problem per Alex Halderman's comments. I suggest either changing this bug to wontfix, or (if anyone is up to it, it isn't too much work, and it doesn't break other stuff) change the install procedure to detect a previous version and prompt to uninstall it first
Can anyone verify that <cntrl +> and <cntrl -> not working happens when the view menu also isn't working? I just tried a 0.9.3 under linux that was installed in a fresh directory and <cntrl +> and <cntrl -> *are* working there, so maybe these bugs are related.
Comment 9•23 years ago
|
||
This may be related to bug 81096 or bug 87045 Can someone check to see if they are getting the following javascript error after clicking the view menu(look in the javascript console): Error: [Exception... "Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsISupports.QueryInterface]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: chrome://global/content/bindings/browser.xml#browser.markupDocumentViewer (getter) :: onget :: line 0" data: no] Source File: chrome://global/content/bindings/browser.xml#browser.markupDocumentViewer (getter) Line: 0 If you see something like that, then this is pretty much just like bug 87045. Any other javascript errors? Jake
Comment 10•23 years ago
|
||
I see a similar error in the JavaScript console : Error: [Exception... "Component does not have requested interface arg 0 [nsIDocShell.contentViewer]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: chrome://global/content/bindings/browser.xml#browser.markupDocumentViewer (getter) :: onget :: line 0" data: no] Source File: chrome://global/content/bindings/browser.xml#browser.markupDocumentViewer (getter) Line: 0 Will try to remove/reinstall the xpti.dat file.
Comment 11•23 years ago
|
||
Removing the xpti.dat file and reinstalling did not help. Removing mail.xpt, psm.xpt, smime.dll and reinstalling did not help. I was only able to fix it by uninstalling 0.9.3 and installing it back.
Comment 12•23 years ago
|
||
If a fresh install rectifies the problem, then this isn't really a bug; just an annoyance. Mozilla changes too much to just install over an old copy. I always use the nightly zip builds on Win32 and delete the entire bin directory before applying any new build. Doesn't really matter anyway, since the profile info is stored elsewhere. I'd recommend marking this invalid since there isn't really a but to fix when re-installing fixes it. Jake
Comment 13•23 years ago
|
||
I have verified that the <cntrl +> and <cntrl -> not working is the same bug. I uninstalled and reinstalled and they work now. I remember old mozilla installs specifically uninstalled the old version before installing the new one. Why don't they do that any more?
Comment 14•23 years ago
|
||
If the installer should be taking care of this, then the component should be Installer instead of browser-general. I could buy that argument. I'll leave that up to someone else here, though, since I have zero experience using the installer. I always use the nightly zip bulds. Jake
Comment 15•23 years ago
|
||
*** Bug 95283 has been marked as a duplicate of this bug. ***
Comment 16•23 years ago
|
||
*** Bug 95842 has been marked as a duplicate of this bug. ***
Comment 17•23 years ago
|
||
*** Bug 96426 has been marked as a duplicate of this bug. ***
Comment 18•23 years ago
|
||
*** Bug 97133 has been marked as a duplicate of this bug. ***
Comment 19•23 years ago
|
||
*** Bug 97458 has been marked as a duplicate of this bug. ***
Comment 20•23 years ago
|
||
Gadzooks, an unconfirmed bug with seven duplicates. -> Installer
Assignee: asa → ssu
Status: UNCONFIRMED → NEW
Component: Browser-General → Installer
Ever confirmed: true
QA Contact: doronr → gemal
Comment 21•23 years ago
|
||
This is not installer... But I dont know what component it is...
QA Contact: gemal → ktrina
Assignee | ||
Comment 22•23 years ago
|
||
Actually, it looks like it happens to be an installer problem because it can be fixed by tweaking the installer. I'm guessing that 0.9.3's installer does not detect if 0.9.2 browser is running, so that after installation is completed, not all the files have been updated because they were in use by the running 0.9.2 browser. This means that when the user quits the browser or reboots the system, the files that were not replaced are still around and picked up by the browser. At this point the browser files are not all from the same installation, which then makes the browser behave in an unpredictable manner. The latest build of Mozilla's installer has this fix to detect 0.9.2 running and will prevent the user from continuing until it is exited. If this is truly the problem, then it's a dupe of bug 96801.
Comment 23•23 years ago
|
||
*** Bug 97715 has been marked as a duplicate of this bug. ***
Comment 24•23 years ago
|
||
*** Bug 98190 has been marked as a duplicate of this bug. ***
Comment 25•23 years ago
|
||
marking duplicate of 96801 *** This bug has been marked as a duplicate of 96801 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•