Bug 20564

Summary:	Firefox reports unable to load profile (when it does indeed not yet exist) after clicking on a Mageia Welcome link
Product:	Mageia	Reporter:	Ben McMonagle <westel>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	firefox-45.8.0-3.mga6.x86_64	CVE:
Status comment:
Attachments:	report.bug.xz journal of session,

Description Ben McMonagle 2017-03-25 02:44:21 CET

Description of problem: The first run of Firefox after install and reboot into system  has a popup "Profile Missing: Your Firefox profile cannot be loaded. It may be missing or inaccessible."

closing the popup allows Firefox to run normally

this is Mate DE single install from x86-64 .iso dated : Thurs Mar 23 22:42:39 CET 2017


Version-Release number of selected component (if applicable):
firefox-45.8.0-3.mga6.x86_64

How reproducible:first run only


Steps to Reproduce:
1.install Mate only DE from above .iso and reboot
2.invoke a weblink from Mageia Welcome i.e. "release notes" 
3.above popup will occur

Comment 1 Ben McMonagle 2017-03-25 02:45:46 CET

Created attachment 9151 [details]
report.bug.xz

Comment 2 Ben McMonagle 2017-03-25 02:50:23 CET

Created attachment 9152 [details]
journal of session,

I started firefox at about 14:10

Comment 3 Ben McMonagle 2017-03-26 05:49:27 CEST

also valid for UEFI Xfce install, same date build

Comment 4 Marja Van Waes 2017-03-26 09:23:46 CEST

Funny user name, "home" :-)

I see your home partition was formatted during install, so there was no pre-existing /home/home/.mozilla

So the message is true :-)

What's weird, is that I cannot reproduce it with XFCE, a new user "home" and the same FF version but:
 not using autologin
 with a different set of FF language packs
 not using a 6sta2 cauldron, but an old, but up-to-date, cauldron
 clicking from a "Dutch" MageiaWelcome link
 
I just don't get such a message.

Tbh, I think, when ~/.mozilla doesn't yet exist, neither getting the "Profile Missing: Your Firefox profile cannot be loaded. It may be missing or inaccessible." message, nor not getting it, is a bug. It's just different behaviour.

Closing as invalid.

However, feel free to reopen it if you think this can really confuse users.

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => INVALID
Summary: Firefox reports unable to load profile => Firefox reports unable to load profile (when it does indeed not yet exist) after clicking on a Mageia Welcome link