Closed Bug 4650 Opened 26 years ago Closed 26 years ago

Mail app DOA on Windows and Linux

Categories

(SeaMonkey :: MailNews: Message Display, defect, P1)

All
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: mscott, Assigned: scottputterman)

Details

With the current M4 builds, starting up the mail news application fails. In particular, you see the following text printed to the screen: nsMsgAppCore::SetWindow(): Failed to find webshell browser.webwindow. Scott P. thinks he might have a lead on the bug as it may be related to use initializing the app core (which attempts to set the window) before messagePane.xul has been loaded. messagePane.xul is the file which defines the browser.webwindow. (It is the browser.webwindow). This is an M4 stopper for mailnews because we can't bring up the application.
Severity: normal → critical
Priority: P3 → P1
Target Milestone: M4
Changing priority to P1 and severity to critical. Setting target milestone to M4.
Severity: critical → normal
Priority: P1 → P3
Target Milestone: M4
RE: seamonkey win32 build (apr 07 00:10:00) on win_nt 4.0 FYI. I am able to launch the application. Here is what happens: a. Select Tools and bring up message center, no crash b. Click on Inbox, thread panes displays message threads c. I can click on New Msg to open a Compose window. It allows me to type in the address field. But disallows me to enter text in the text content area. d. When I click on the Send button, it sends, no crash e. When I click on New Msg, the message thread is displayed in the thread pane. f. But when I click on the message thread to open the message, applciation crashes.
Severity: normal → critical
Priority: P3 → P1
Target Milestone: M4
Fenella overwrote my changes.
RE: april 7 Linux's build, I was able to launch the application. But when I click on Tools/Messenger to open the message center, it indeed crashes, same message as described by Scott M.
Assignee: mscott → putterman
When I get approval I'm going to back out some changes I made yesterday. This is being caused by a bug that Chris Waterson is going to fix eventually (I don't have a bug number yet). The fix won't happen today so backing out my changes is the best way to do it for the moment. This shouldn't affect any of the other code that I checked in.
Chris Waterson's bug is 4668.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
I checked in the fix for this bug. This does not fix the problem with messages not loading which I think is a duplicate bug whose number I don't know.
The part about messages not loading is covered in Bug 4585 and as you said isn't related to this problem at all....Thanks for checking this in Scott.
QA Contact: 4080 → 4114
Marking verified. The builds on Win32 and Linux from the release team today (4/8) are fine - mail has not problems starting.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.