| Summary: | after default install the user cannot start firefox | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | AL13N <alien> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | eeeemail, mageia, mageia |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | firefox | CVE: | |
| Status comment: | |||
|
AL13N
2012-04-07 13:15:49 CEST
Priority:
Normal =>
High Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja Keywords:
(none) =>
NEEDINFO resolving old... after i'll reinstall my server, i can reinstall my PXE+NFS network install and then i can see if it's still there, if it is, i'll reopen. Status:
NEW =>
RESOLVED confirmed on Mga3 RC LiveCD Keywords:
NEEDINFO =>
(none) which one ? strange nobody noticed it.. x86_64 (the tmb one from 2013-05-04) it gives a mention about "session not accessible" or similar
claire robinson
2013-05-05 20:49:36 CEST
CC:
(none) =>
eeeemail you only see this on live ? CC:
(none) =>
nicolas.lecureuil i have not tested otherwise on mga3, besides using live (not installing) Can someone else confirm that bug? I have tested multiple live isos and I haven't noticed such problem :/ CC:
(none) =>
sander.lepik i must admit i seen this only once, but when i live tested, i didn't use FF except that one time. the only thing i can think of is that i booted fast, and immediately clicked on FF. perhaps too fast? used the KDE 64bit one for this, btw Tested with LiveDVD x86_64 KDE version and with LiveCD x86_64 KDE version from wl-test folder. I can't reproduce this. There are no .mozilla folder before firefox is started and when it's started those folders are created as live user. So I'm decreasing priority. You can set it back to release critical if you figure out how to reproduce it and what is the exact error. Priority:
release_blocker =>
Normal couldn't reproduce either Status:
REOPENED =>
RESOLVED |
it appears the ~/.mozilla/{extensions|firefox} directory is owned by root. this happened after a default network installation from the boot.iso media in x86_64 3 days ago. it seems that they even already contained a session for it to start. i suppose during installation, they are being created, and since it's normally the current user, but during install it's run as root, they are created as root? after chowning them, all works well...