Closed
Bug 281711
Opened 20 years ago
Closed 19 years ago
Mozilla doesn't launch properly with single-profile and / or disable-profilesharing
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: thesuckiestemail, Unassigned)
Details
User-Agent: Mozilla/5.0 (BeOS; U; BeOS BePC; en-US; rv:1.8b) Gecko/20050209 Build Identifier: Mozilla/5.0 (BeOS; U; BeOS BePC; en-US; rv:1.8b) Gecko/20050209 Did a build of Mozilla, but it would fail to launch. It would just show the splashscreen then quit. After tracking the problem to nsAppStartup::DoProfileStartup I saw that it failed on nsCOMPtr profileMgr (do_GetService(NS_PROFILE_CONTRACTID, &rv)); I had no Mozilla profile and I had the build flags for ac_add_options --enable-single-profile and ac_add_options --disable-profilesharing Rebuilding with these flags removed made the browser launch as expected. I'd say this is a problem on all platforms, but it was detected on BeOS. Reproducible: Always Steps to Reproduce:
Comment 1•20 years ago
|
||
I'm not sure that the suite supports or should support --enable-single-profile or --disable-profilesharing... those flags were meant for embedders, and are also used by the new toolkit. Not all of our build flags are meant for general-purpose use.
Comment 2•19 years ago
|
||
I read on other tech support sites that when the default profile failed to launch from the start or launch execute file, to recreate a new profile. It does launch after that, but the user will lose their bookmarks, and the lanch is still slow.
Closing according to comment 1.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•