Bug 12093

Summary:	Firefox does not start due to loading profile
Product:	Mageia	Reporter:	Tadej Panjtar <tadej.panjtar>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	cmrisolde, marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	firefox	CVE:
Status comment:

Description Tadej Panjtar 2013-12-23 15:26:08 CET

Description of problem:
In live DVD, firefox icon runs firefox with no problems.
After installing live version on hard disk

Version-Release number of selected component (if applicable):
firefox-24.1.1-1.mga4

How reproducible:
Install Mageia-4-beta2-LiveDVD-KDE4-x86_64-DVD.iso 
Install live CD on hard disk.

Steps to Reproduce:
1. click firefox icon
2. firefox does not start, popup appears Profile Missing: Your Firefox profile cannon be loaded. It may be missing or inaccessible.



Reproducible: 

Steps to Reproduce:

Comment 1 Carolyn Rowse 2013-12-23 21:12:42 CET

I had that problem and it turned out to be due to something on the Errata page:

"Bug 11983 - After install from the live iso ~/.cache is left owned by root. Workaround is to run (as root) "chown $USER:$USER /home/$USER/.cache", replacing $USER with the user id. The affect of this bug, is that it will stop programs that try to create files in ~/.cache (like firefox) from working."

Try that workaround.

CC: (none) => isolde

Comment 2 Marja Van Waes 2013-12-25 19:48:39 CET

(In reply to Carolyn Rowse from comment #1)
> I had that problem and it turned out to be due to something on the Errata
> page:
> 
> "Bug 11983 - After install from the live iso ~/.cache is left owned by root.
> Workaround is to run (as root) "chown $USER:$USER /home/$USER/.cache",
> replacing $USER with the user id. The affect of this bug, is that it will
> stop programs that try to create files in ~/.cache (like firefox) from
> working."
> 
> Try that workaround.

So closing as duplicate

@ Tadej

Feel free to reopen this report if changing the owner of ~/.cache to the owner of your /home doesn't solve this problem

*** This bug has been marked as a duplicate of bug 11983 ***

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => DUPLICATE