Closed
Bug 428583
Opened 17 years ago
Closed 17 years ago
profilemanager doesn't start [x64]
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: wolfiR, Unassigned)
References
Details
This is a follow up bug from bug 426141 and bug 391311.
Firefox used to crash at startup before the patches went in for the above bugs.
Now the crashes are gone but it just doesn't happen anything if I try to start Firefox with option -p or -profilemanager.
Also trying to start another instance of Firefox (on the same profile) doesn't result in an error popup about a locked profile but silently does nothing.
| Reporter | ||
Comment 1•17 years ago
|
||
Actually I found that I only can reproduce with an x86-64 build.
Component: XRE Startup → Startup and Profile System
QA Contact: xre.startup → startup
Comment 3•17 years ago
|
||
OS?
(In reply to comment #0)
> Also trying to start another instance of Firefox (on the same profile) doesn't
> result in an error popup about a locked profile but silently does nothing.
isn't the design to not start even profile manager when the same program is running, unless you have -no-remote specified?
Summary: profilemanager doesn't start → profilemanager doesn't start [x64]
| Reporter | ||
Comment 4•17 years ago
|
||
(In reply to comment #3)
> OS?
openSUSE 10.3 or 11.0 (not sure anymore)
> (In reply to comment #0)
> > Also trying to start another instance of Firefox (on the same profile) doesn't
> > result in an error popup about a locked profile but silently does nothing.
>
> isn't the design to not start even profile manager when the same program is
> running, unless you have -no-remote specified?
Yes, but -no-remote was used IIRC and still there was no profile manager.
I've now tried to reproduce on openSUSE 11.0 with Firefox 3.0.4 and I couldn't.
So this has been fixed somehow.
If others still having issues please let us know.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•