Closed
Bug 24396
Opened 25 years ago
Closed 25 years ago
Crash trying to launch new profile created via -mail .
Categories
(SeaMonkey :: MailNews: Message Display, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M15
People
(Reporter: laurel, Assigned: sspitzer)
Details
(Keywords: crash)
Using 2000-01-19-08 commercial build on linux 6.0
I'm getting a crash after creating a new profile when using the Manage Profiles
button from within the Select User Profile dialog (launching ./mozilla -mail)
then trying to launch that new profile.
I am able to create and launch a new profile without crashing if I use the
direct method of initially going through the Manage User Profiles (launching
./mozilla -installer).
1. Launch 5.0 by command line ./mozilla -mail, where there are already a couple
profiles in existence. The Select User Profile dialog will appear.
2. From the Select User Profile dialog, click the Manage Profiles button. The
Manage User Profiles dialog will appear.
3. From the Manage User Profiles dialog, click New Profile button. A Create New
Profile dialog/wizard will appear. Click Next, give profile a name, then click
Finish. Your are taken back to select user profiles dialog.
4. Select the profile you just created and click Start Mozilla.
Result: a crash occurs.
Actual result: Crash occurs trying to launch freshly created profile when
launching via ./mozilla -mail. Crash does not occur if you launch a newly
created profile when doing so via ./mozilla -installer.
Expected result: Either method should yield the same result -- no crash.
Summary: Crash creating → Crash trying to launch new profile created via -mail .
Talkback incidents #4142424 & #4142007. Can't get to the report details at
present time to get stack info.
Updated•25 years ago
|
Severity: normal → critical
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M13
Comment 2•25 years ago
|
||
Can't dup on WinNT using 2000-01-19-13.
Updated•25 years ago
|
Component: Profile Manager → Front End
Product: Browser → MailNews
Comment 3•25 years ago
|
||
This is not a profile manager bug (although I do see the crash on RH 6.0 using
2000-01-19-16.) The mail window was trying to initialize itself as evidenced by
the messages in the console:
> ./mozilla -mail
.//run-mozilla.sh ./mozilla-bin -mail
MOZILLA_FIVE_HOME=/root/package
LD_LIBRARY_PATH=/root/package:/root/package/Cool
XPCS_HOME=/root/package/Cool
MOZ_PROGRAM=./mozilla-bin
MOZ_TOOLKIT=
moz_debug=0
moz_debugger=
nNCL: registering deferred (0)
WEBSHELL+ = 1
I am inside the initialize
Hey : You are in QFA Startup
(QFA)Talkback loaded Ok.
WEBSHELL+ = 2
nsXULKeyListenerImpl::Init()
nsCollationUnix::Initialize mLocale = C
nsCollationUnix::Initialize mCharset = ISO-8859-1
/root/package/Cool/Xpcs Registry.dat: invalid ELF headerWEBSHELL+ = 3
WEBSHELL+ = 4
title string = [Mail - Mozilla]
title string = [Mozilla]
attempt to UpgradePrefs. If that fails, open the account wizard.
start message pane with:
http://messenger.netscape.com/bookmark/4_7/messengerstart.html
In sortColumn
in showthreads
In onLoadfolderPane
In sortColumn
SetupCommandUpdateHandlers
JavaScript Error: uncaught exception: [Exception... "Component returned failure
code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgAccountManager.defaultAccount]"
nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame ::
chrome://messenger/content/msgMail3PaneWindow.js :: loadStartFolder :: line
272" data: no]
WEBSHELL+ = 5
got a request
Updated•25 years ago
|
QA Contact: gbush → lchiang
Comment 4•25 years ago
|
||
changing QA contact
I'm assuming, Grace, that you meant to change QA assignee to you? Changing it
from lisa to you.
Updated•25 years ago
|
Assignee: selmer → phil
Status: ASSIGNED → NEW
QA Contact: laurel → lchiang
Comment 7•25 years ago
|
||
Bug didn't automatically reassign to component owner when product changed...
Comment 8•25 years ago
|
||
Reassign to sspitzer for M14
Assignee: phil → sspitzer
Target Milestone: M13 → M14
Assignee | ||
Comment 12•25 years ago
|
||
crashers, keeping m15.
Assignee | ||
Comment 13•25 years ago
|
||
don't know when, but this seems to be fixed.
it no longer happens to me.
marking fixed.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 14•25 years ago
|
||
OK for me using 2000-04-07-09m15 commercial build on linux rh6.0
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•