Closed
Bug 24393
Opened 26 years ago
Closed 26 years ago
[dogfood] Crash following profile migration
Categories
(Core Graveyard :: Profile: Migration, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: chriss, Assigned: sspitzer)
Details
(Whiteboard: [PDT+])
Using today's commercial build 1/19, I crash immediately following profile
migraion. This may not be related, but the last console message is that the
drag and drop pref can not be found.
Steps to reproduce:
1) Do a "clean" install of seamonkey:
- delete seamonkey folder and files
- delete psm folder and files
- delete mozregistry.dat file in windows folder
- delete users50 folder and files
2) Install seamonkey
3) Select primary 4.7 profile for migration
4) Following migration I get an immediate crash
It appears that my prefs.js file wasn't properly migrated. Here is all that's in
the file:
----
# Mozilla User Preferences
----
Here is a talkback ID number and information: 4141330
Trigger Reason: Not Available
Thread ID:
Registers: Not Available
Command Line: "C:\Program Files\Netscape\Seamonkey\mozilla.exe" -installer
Comment 1•26 years ago
|
||
I see this message- but I don't crash- I just hang- whether with a migrated
profile or new created profile. Profile Manager is long gone when the console
hangs. It is in initialize:
Error message: failed to get xpfe.dragdrop.enable pref, assuming it is off
nsXULKeyListenerImpl::Init()
| Assignee | ||
Comment 2•26 years ago
|
||
it sounds like this may be the crash on startup that matt fisher fixed, when he
fixed the packaging problem.
I'm betting this is fixed now.
Comment 3•26 years ago
|
||
using the build
ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/2000-01-19-13-M13/sea
monkey32e.exe
I am launching successfully
| Assignee | ||
Comment 4•26 years ago
|
||
chriss, can you get the new build, and try again?
| Assignee | ||
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
| Assignee | ||
Comment 7•26 years ago
|
||
marking worksforme.
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Comment 8•26 years ago
|
||
build 2000011913
Updated•10 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•