Closed
Bug 1100407
Opened 11 years ago
Closed 10 years ago
Firefox will not start on Mac with multiple users
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: yury, Unassigned)
Details
On multi-user machine, after Firefox updates, one of the users cannot start Firefox. Both users are admins. I noticed that after 33.1.1 update, but that happen couple of months ago for me too, now Mac OSX is at 10.10 Yosemite, but the same (?) happened on Mavericks.
After the application icon is clicked, it "jumps" for few seconds and process stops without any message or crash report. We had to re-download Firefox (to take care of other user's frustration) using other browser to restore functionality. After that I could not reproduce the issue. Is it anything we shall worry about?
| Reporter | ||
Updated•11 years ago
|
OS: All → Mac OS X
Hardware: All → x86_64
Comment 1•11 years ago
|
||
Maybe rstrong knows? Alternatively, maybe some of our fine mac folks like Markus Stange or Steven Michaud can comment...
Flags: needinfo?(robert.strong.bugs)
Comment 2•11 years ago
|
||
Yury, please try to figure out how to reproduce this.
Do you still have any of the "broken" copies of Firefox? If so, could you arrange to upload them somewhere (like your people.mozilla.com account) so we could have a look?
Could this be bug 394984, or some variant?
Comment 3•11 years ago
|
||
> Do you still have any of the "broken" copies of Firefox?
Before uploading them you'd need to zip or tar them, to preserve file ownership and permissions.
Comment 4•11 years ago
|
||
No idea at the moment but smichaud's approach to figuring it out is the right way to go about it.
Flags: needinfo?(robert.strong.bugs)
| Reporter | ||
Comment 5•11 years ago
|
||
Update to 34.0.5 has no this issue however, not sure it is connected, on my profile I could not update automatically: the download dialog was running, but stopped at "connecting to the server" message. Another user could update the FF for me.
Comment 6•11 years ago
|
||
The fact that you were unable to update automatically is probably related to bug 394984.
Comment 7•10 years ago
|
||
Hi Yury,
Your issue is still reproducing? If yes, this is regarded to bug 394984 that Stephen mentioned?
Thank you.
Flags: needinfo?(ydelendik)
| Reporter | ||
Comment 8•10 years ago
|
||
I was not able to reproduce the issue anymore. Closing as WFM.
I agree, it's probably tracked by bug 394984.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(ydelendik)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•