Closed
Bug 7478
Opened 25 years ago
Closed 25 years ago
Blocker: Lost menus, compose window, ability to display messages on a previously working build
Categories
(MailNews Core :: Backend, defect, P1)
Tracking
(Not tracked)
People
(Reporter: scurtis, Assigned: saari)
Details
Attachments
(1 file)
6.03 KB,
text/plain
|
Details |
This bug is just a thought-placeholder for now, because I don't have many facts to include yet. This has happened to me twice now with different builds, so I think it may be an objective problem, and not just my brain blowing up. Using the Linux 6_1 respin build and the 6_2 build, I started out having no problems with seamonkey mail. I ran through the short list of mail smoketests and everything worked. I had normal menus and messages for POP and IMAP, and was able to send and receive messages. Somewhere along the way of using the build, I lost my menus and I lost the ability to display messages. Today I was doing few different things when this happened, and I'm going to have to investigate a bit more to try to get a reproducible case. I had been playing around with bug 7470, a compose window oddity, and had been opening and closing the mail compose window a bunch of times, sometimes actually sending the message, sometimes just closing the compose window with the window manager "x." Then I decided I wanted to test it with plain text compose, so I closed apprunner (I'm fairly sure I did a standard "File | Exit" menu selection. I added user_pref("mail.identity.id1.send_html", false); to my prefs.js. I restarted apprunner ("apprunner -mail &"). I perhaps didn't wait for the full 3-pane window to draw before I clicked on "New Msg." The compose window drew without any widgets or chrome. I closed it with the window manager "x." I noticed there were no menus. I restarted. Same thing. Now I can't get this build to work, so something got corrupted or broke. I've tried setting that pref back to true, but that seems to have no effect. I'm going to try to narrow down what might need to be cleaned out in order to get a working build again, and then will try to recreate the problem. I'm going to attach a file of the console window output for apprunner for the relevant time frame...it has some wierd-looking stuff in it, but I have no clue what it means. The wierd-looking stuff also looks like it occurred in the instance of the app that ran before the plain-text-compose instance, so either of those things might be totally unrelated.
The only "no menu on Linux" bug I recall is http://bugzilla.mozilla.org/show_bug.cgi?id=7412, but that was a build problem. Could running that build have some ramifications on your setup? Since you ran the 6/1 am build where menus had a problem and no one else in our group did, perhaps that's why you're the only person seeing this problem? Perhaps check with leaf to see if he knows anything about this?
Comment 3•25 years ago
|
||
cc alecf and sspitzer for ideas
RE: Linux 6/2 build (1999-06-02-08 m7) I do not know if this is the same problem. Here is what I have seen in today's build. 1. Run appruner, I do not see any menu item at the top. Click on mail icon, it brings up a blank window (bug 7435) 2. So I exit apprunner. 3. Run apprunner -mail to bring up messenger. I was able to see the multiple accounts in the folder pane, display messages in the thread pane and message pane, compose message and send, and I was able to receive mail. 4. Then I exit apprunner and run ./apprunner -mail again with a single pop account. 5. Click on the mail server in the folder pane, this time, all I see is: the thread pane is divided into two frames, the left frame shows the same information like the folder pane. And the right frame of the message pane is blank. I cannot go further. 6. So, I remove the registry, re-install today's build and repeat step 4 and 5, the result is like step 5 above. I cannot do any further testing. I think this should be a P1 stopper
Severity: normal → blocker
Priority: P3 → P1
Summary: Lost menus, compose window, ability to display messages on a previously working build → Blocker: Lost menus, compose window, ability to display messages on a previously working build
Raising to blocker. Fenella, Stacey, Esther, Laurel all have this problem now. After exiting the first session of using Linux Messenger, they cannot use Linux Messenger anymore (strange things happen such as the thread pane being "split up". Even after removing registry and reinstalling the build. Not sure if this is a browser bug or mail specific. I'll check with allclientqa to see if browser QA has this bug reported.
Comment 6•25 years ago
|
||
cc'ing mcafee
Comment 7•25 years ago
|
||
sounds like a dup of 7417.
Comment 8•25 years ago
|
||
wow, what a horrible bug! So it's the whole browser not just a mail thing. *To Repro: With Linux 1999060208: 1. Launch apprunner. Notice the pretty menus (File, Edit, etc.). 2. Quit. Launch again. * you will now notice you have no top level menu. I've tried deleting everything in .mozilla and reinstalling to no avail. Moreover, deleting and running an old build doesn't even work. This is the definition of a 'blocker'. This has (unfortunately) been reproduced on a number of Linux boxes in BrowserQA land
Comment 9•25 years ago
|
||
cc'ing mcafee again b/c bugzilla say i clobbered Paulmac's changes
Comment 10•25 years ago
|
||
cc'ing mcafee again b/c bugzilla say i clobbered Paulmac's changes
Updated•25 years ago
|
Assignee: phil → saari
Comment 11•25 years ago
|
||
Since menus appear to be broken on Linux, reassigning to saari, cc'ing trudelle
Comment 12•25 years ago
|
||
All of apprunner is broken for Linux. CC'ing slamm so that he can mark this a dupe of a bug he's already working on.
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Comment 13•25 years ago
|
||
*** This bug has been marked as a duplicate of 7417 ***
Reporter | ||
Comment 14•25 years ago
|
||
Whew. That's yucky. Marking as verified dupe.
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•