Closed Bug 51330 Opened 25 years ago Closed 25 years ago

can't reply or compose new mail

Categories

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

Product:
SeaMonkey
Component:
MailNews: Message Display
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED INVALID

People

(Reporter: spam, Assigned: rhp)

Details

(Keywords: smoketest, Whiteboard: [dogfood-])

2000090421 linux hitting "new msg" or "reply to" only spawns this error in console: ComposeMessage from XUL: [nsIMsgIdentity: id2] i = 0 JavaScript error: line 0: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgComposeService.OpenComposeWindow]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://messenger/content/mailCommands.js :: ComposeMessage :: line 262" data: no] (using newmod theme)
two pop accounts are set up - error occurs on both.
smoketest keyword, severity blocker. Personally, I crash trying to start mail. Filing a bug on that now.
Keywords: smoketest
Yep, seeing this reply problem as well.
this is just like that insane "won't start" bug: The first time i start mailnews with a NEW build (nightly) a window opens when i hit reply or new msg. When i then close mailnews, quit mozilla - and start again: the JS error appears and goes on forever after.
Putting on [dogfood+] radar.
Whiteboard: [dogfood+]
Assignee: putterman → ducarroz
reassigning to ducarroz.
QA: are you able to reproduce this problem?
Status: NEW → ASSIGNED
Target Milestone: --- → M18
I'll try to look at this one. - rhp
Assignee: ducarroz → rhp
Status: ASSIGNED → NEW
Esther and Ninoschka will try this.
I didn't run into crashes using Reply To: or New Msg. I used build linux build 2000-05-06 m18 ...installer.tar.gz. I tried this with a POP account, an IMAP account plain text compose and html compose. FYI.. also didn't have any problems with the mac or win98 09-05 builds. Any more information to help us reproduce this in QA?
I saw this crash on yesterday's Linux 09-05-08-M18 commercial build, but couldn't reproduce this on today's Linux 09-06-08-M18 commercial build.....
To be a good citizen, I will try this as well on my build when it is done and if it works, I'll mark WORKSFORME :-) - rhp
Status: NEW → ASSIGNED
Linux build just finished and this works fine. - rhp
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
well it still doesn't work for me linux 2000-080621
umm..missed a month in build ID: 2000090621 is still "no go" here.
when i simply hit "new msg" this error appears: ComposeMessage from XUL: [nsIMsgIdentity: id1] JavaScript error: line 0: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgComposeService.OpenComposeWindow]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://messenger/content/mailCommands.js :: ComposeMessage :: line 234" data: no] -- when i have selected a message and hit reply-button: ComposeMessage from XUL: [nsIMsgIdentity: id2] i = 0 JavaScript error: line 0: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgComposeService.OpenComposeWindow]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://messenger/content/mailCommands.js :: ComposeMessage :: line 262" data: no]
also see bug 51701
Let's try to isolate to see if it's system specific or profile specific. Kristen - does this happen when you create a new profile (not a new account)?
Clean profile - always. (It's "Kristin" btw)
Different behaviour for me on two different Linux boxes (both RedHat 6.2, both 2000090708 build). One (a Pentium II-300) works no problem, the other (Pentium III-450) gets Kristin's errors. The one with the errors also has problems starting, generally dying with no obvious errors after: "CSSLoaderImpl::LoadAgentSheet: Load of URL 'file:///home/peterj/.mozilla/default/ChromeuserChrome.css' failed. Error code: 16389 CSSLoaderImpl::LoadAgentSheet: Load of URL 'file:///home/peterj/.mozilla/default/ChromeuserContent.css' failed. Error code: 16389" but once with a third error: "CSSLoaderImpl::DidLoadStyle: Load of URL 'chrome://communicator/skin/menubutton.css' failed. Error code: 16389"
I think we need to investigate this further. Reopening. Kristin and peterj - how are you guys installing the product? Do you install as root or as user? Just trying to find some common items here to go with.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Whiteboard: [dogfood+] → [dogfood+][need info]
i don't install, i simply tar -zxvf mozilla nightly binaries in the /tmp directory - using my regular login. That makes me owner of the dir and files. To start moz i "cd package", and do ./mozilla & from there. Above approach has worked nicely since sometime last year and up till now, i've tested more or less every nightly since then. The last week moz has been extremely horked here - can barely start it. A couple of interesting bugs i suspect MAY have a connection to various headaches i've had with moz this last week: 51267 "Intermittent failure loading CSS from JARs" 51778 "regchrome doesn't actually register chrome" RH6.2+erratas on a P3/500, 256MB RAM. No "odd" problems with other programs running here.
Clicking a mailto link doesn't spawn anything either. Perhaps related: When trying to make attachment in bugzilla, filepicker doesn't open. (filed 51822 on that)
I'm also simply untarring the .tar.gz. I've tried extracting into an existing (working) package dir and going into a clean dir, with no difference in behaviour. Even tried copying the (working) package dir from the P2 to the P3 with no luck.
Please note: The very first time mailnews is started after a fresh install/unzip, the mailcompose window WILL appear. For the first and last time. Next time mailnews is started, error appears instead.
I'm having real problems recreating this. Any help would be appreciated from the Netscape side. - rhp
Status: REOPENED → ASSIGNED
We test with the Installer so we'll give this a try (not using installer).
lchiang and rhp: I just verified that using the installer to install 2000090808 makes it work. Extracting 2000090808 from a .tar.gz doesn't.
Well, I'm marking this invalid since the proper install seems to work. - rhp
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → INVALID
May I ask why mozilla.org at all distribute nightly builds packed as tar.gz files if they aren't even supposed to work?
oh... never mind replying. Verifying invalid instead :) I'm turning off mail from bugzilla now. Good luck.
Status: RESOLVED → VERIFIED
I will cc: asa to answer the part for Mozilla. Something may have changed which requires the installer now. Kristin - I hope you will continue to help us test.
I hope we don't require the installer to have mail functionality. If we do then it is a bug. I will look into this further.
I don't think that this bug is Invalid. I'm not convinced that ther is only one "proper install" and that that is using the Netscape or even Mozilla Installer. I think it's a bug if we need the installer to make mail work. Reopening for now.
Status: VERIFIED → REOPENED
Resolution: INVALID → ---
If mail doesn't work due to not using the installer, it would really be an installer bug. I think rhp marked this invalid because there are so many ways to test and we need to prioritize (unfortunately) which bugs to look into (there are so many!) i'll clear dogfood+ for PDT re-evaluation of this for the Netscape side.
Keywords: dogfood
Whiteboard: [dogfood+][need info]
This is based on Peter J's comments/findings (which is great). We should have a second person to verify this just to be safe :-)
With the "work around" of running the installer, this doesn't seem to be blocking use as dogfood. It would be nice to understand what magic needs to be done for those that use "tar xf", but it should not block usage. Marking dogfood-minus
Whiteboard: [dogfood-]
I strongly disagree with rhp that using the installer is the 'proper' way to install. Most people prefer to install via rpm, debs or good ol' tar.gz files. While netscape and mozilla.org don't release in those formats, others (like redhat) do repackage our builds and if our tar.gz packages don't work then they are doomed. Also, the installers are only stubs, right? A lot of people will want to install mozilla along with the rest of their linux installation from CD. Running an installer and downloading from the net will be impractical. I tried reproducing the bug with today's build and with the 90508 build with no luck. i'm using rh 6.2 with some of the early security updates, but not the recent glibc. I have glibc-2.1.3-15. I installed from a tar.gz Since the problem only shows up until the second running of mozilla, it seems like closing mozilla writes out something that breaks things later. What kind of things get written out? Prefs? registry? cache? address book? mail folders? Anything to do with chrome? I wonder if this is related to migrating prefs? If it is, that might explain why it fails for kristin and one of peter's accounts but not for the rest of us. Maybe comparing the prefs file from a working account and a broken one will help. Kristin, could you try creating a new account for yourself on your machine and see if you have the same problem there?
What happens, if run my own build (compiled by myself)? I don't "install" it... Please note that the installer doesn't support proxies either. I just *cannot* use the Linux installer. This is a blocker - if not for me, then for somebody else. A lot of people use the tarballs. (*I* didn't update yet, luckily.) mailCommands hasn't been changed between aug 31 and sept 8.
Downloaded a two week old moz to check: the error suddenly occured there too. I wrote mails just fine with that build 2 weeks ago. In between I upgraded to RH's glibc errata. Turns out RH released a NEW errata of glibc on the 7th. For RH6.2 the previous errata rpm was 2.1.3-19 The new is 2.1.3-21 In the new errata startup problems with mozilla is specifically mentioned. Let's see if that just happens to fix this weirdness..
Upgrading glibc fixed everything. This bug was ...a bug - but not a mozilla bug. Setting invalid.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → INVALID
verifying too. Been testing 2000090906 4 times now, exiting, starting, starting mailcompose - it now works each time - no errors display. O' joy.
Status: RESOLVED → VERIFIED
Thanks for following up on this! - rhp
Yup, invalid sounds right. Turns out one box was at 2.1.3-17 and one at 2.1.3-19; both at 2.1.3-21 is peachy.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.