Didn't reproduce here but see also bug 15016

Ben are you en_NZ locale?

CC: (none) => eeeemail
Summary: m5b2 forefox will not launch when in live system => m5b2 firefox will not launch when in live system

claire, 

yes. en_nz locale.

when attempting to start  Firefox a popup:  " your firefox profile cannot be loaded. it may be missing or inaccessible" 

was late when I entered the bug and meant to add this.
thanks for the reminder.

Sorry, tried several times but I cannot reproduce :/

Firefox works fine in a live session, even on subsequent starts.

@Ben: Did you check the permissions/ownership on ~/.mozilla and maybe also ~/.cache folders? In the past there were some issues that in some rare cases ~/.cache was owned by root and this caused quite some issues.

This is the output i get for locale settings and on first start of firefox (the addons warnings are cosmetics and unrelated)


[live@localhost ~]$ locale
LANG=en_NZ.UTF-8
LC_CTYPE=en_NZ.UTF-8
LC_NUMERIC=en_NZ.UTF-8
LC_TIME=en_NZ.UTF-8
LC_COLLATE=en_NZ.UTF-8
LC_MONETARY=en_NZ.UTF-8
LC_MESSAGES=en_NZ.UTF-8
LC_PAPER=en_NZ.UTF-8
LC_NAME=en_NZ.UTF-8
LC_ADDRESS=en_NZ.UTF-8
LC_TELEPHONE=en_NZ.UTF-8
LC_MEASUREMENT=en_NZ.UTF-8
LC_IDENTIFICATION=en_NZ.UTF-8
LC_ALL=

[live@localhost ~]$ firefox

(process:2828): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
1421342314901   addons.xpi      WARN    Add-on is invalid: Error: No ID in install manifest (resource://gre/modules/addons/XPIProvider.jsm:809:6) JS Stack trace: loadManifestFromRDF@XPIProvider.jsm:809:7 < loadManifestFromZipReader@XPIProvider.jsm:1028:9 < loadManifestFromZipFile@XPIProvider.jsm:1069:5 < loadManifestFromFile@XPIProvider.jsm:1078:5 < addMetadata@XPIProvider.jsm:2981:11 < XPI_processFileChanges@XPIProvider.jsm:3255:1 < XPI_checkForChanges@XPIProvider.jsm:3428:1 < XPI_startup@XPIProvider.jsm:1884:1 < AMI_callProviders@AddonManager.jsm:869:11 < AMI_startup@AddonManager.jsm:745:1 < AMP_startup@AddonManager.jsm:2318:5 < AMC_observe@addonManager.js:55:7
1421342314902   addons.xpi      WARN    Could not uninstall invalid item from locked install location



You may need to dig why firefox doesnt start in your live session, e.g. remove existing .mozilla folder, or try with safe mode - see maybe https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems or http://kb.mozillazine.org/Profile_cannot_be_loaded or http://kb.mozillazine.org/Firefox_:_Issues:_Firefox_Won%27t_Startup

Maybe firefox is even already runnign in the background but not responding ...

I opened Firefox with success on Mageia-5-beta3-KDE4-LiveDVD-x86_64.

Maybe it is specific to i586 iso ?

CC: (none) => stephane_oss

I've specifically tested the image Mageia-5-beta2-LiveDVD-KDE4-i586-DVD several times also for other bugreports, and firefox always started fine. Now tested again with Mageia-5-beta3-LiveDVD-KDE4-i586-DVD and Mageia-5-beta3-LiveCD-KDE4-i586-CD and it works just fine.

@benmc: Was this test in a VM or on real hardware? And can you still reproduce? Because neither me nor claire can ...

Ever confirmed: 1 => 0
Status: NEW => UNCONFIRMED

> 
> @benmc: Was this test in a VM or on real hardware? And can you still
> reproduce? Because neither me nor claire can ...

Real hardware, live system running from install media, not yet installed.
during set up selected :
Language: English- New Zealand,
Keyboard: US International,
Time zone set to advanced, ntp server: Oceania, New Zealand

no other additions to live system, no updates applied, no other software added.

then:
after installation from live and reboot, a popup to load a profile is displayed when attempting to launch Firefox.
no profiles offered so a new one must be created - default.
afterwards Firefox launches without issue.

reproducible from both USB or DVD install media.

will check both other KDE lives - cd + x86-64 and advise.

I have finished retesting the three kde lives.

cd-en was able to load but had a popup advising there is a missing profile.

586 worked perfectly.

x86-64 worked perfectly.

maybe it is my hardware?

(In reply to ben mcmonagle from comment #6)
> Real hardware, live system running from install media, not yet installed.

[...]

> then:
> after installation from live and reboot, a popup to load a profile is
> displayed when attempting to launch Firefox.

So this is only _after_ installation from live media when booting the installed system, and _not_ within live mode? Or does it occur both in live mode and installed system? As the initial description only talks about live system. Please be more precise, as far as I see it, all 3 testers so far only checked firefox in live mode.

when the problem occurs it is in live [ uninstalled ] mode.

When in live mode:
Clicking the Firefox icon gives feedback [ bouncing icon ], the popup -" your Firefox profile cannot be loaded. it may be missing or inaccessible" appears after a few seconds.
Then, after about 30 seconds, bouncing icon disappears and no Firefox browser.
the process is repeatable.

THEN: 
IF the system is then installed, via the install icon on the desktop, and then rebooted,
when launching Firefox, a popup requesting a profile for Firefox to be created also launches.
create a " default " profile and Firefox operates as expected.

Created attachment 5904 [details]
firefox attempt to start  from console and fail

sorry for long delay- does not misbehave every attempt.

today, Mageia-5-beta3-LiveCD-KDE4-en-i586-CD - latest .iso from CD
firefox would not start, even with multiple attempts.

if you require more inf, please advise.

today, Mageia-5-rc-LiveCD-KDE4-en-i586-CD - 2nd round .iso from CD
firefox would not start, even with multiple attempts.

started from konsole as root

[live@localhost ~]$ firefox

(process:5093): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
[live@localhost ~]$ su
[root@localhost live]# firefox

(process:5165): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
kmozillahelper(5178)/kdeui (kdelibs): Session bus not found 
To circumvent this problem try the following command (with Linux and bash) 
export $(dbus-launch) 
KCrash: Application 'kmozillahelper' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
KCrash: Connect sock_file=/root/.kde4/socket-localhost/kdeinit4__0
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly
drkonqi(5181)/kdeui (kdelibs): Session bus not found 
To circumvent this problem try the following command (with Linux and bash) 
export $(dbus-launch).

not an ideal option but it does start

(In reply to ben mcmonagle from comment #10)
> if you require more inf, please advise.

See the previous reply:


(In reply to Florian Hubold from comment #3)
> @Ben: Did you check the permissions/ownership on ~/.mozilla and maybe also
> ~/.cache folders? In the past there were some issues that in some rare cases
> ~/.cache was owned by root and this caused quite some issues.

 
> You may need to dig why firefox doesnt start in your live session, e.g.
> remove existing .mozilla folder, or try with safe mode - see maybe
> https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-
> problems or http://kb.mozillazine.org/Profile_cannot_be_loaded or
> http://kb.mozillazine.org/Firefox_:_Issues:_Firefox_Won%27t_Startup
> 
> Maybe firefox is even already runnign in the background but not responding


As there's not even an error message when you launched it as user in comment 11, and I don't know if another firefox process was maybe already running at that time and as I cannot reproduce this, I can't help much ...

ownership of the folders requested is user= live / group = live

and live / live

re: Ben's email to qa-d

This is still valid

and still valid 15th april isos (from pad)

Either add a word to Errata and replace FOR_ERRATA with IN_ERRATA in whiteboard (if we think other people can encounter this bug) or remove FOR_ERRATA from whiteboard

Whiteboard: (none) => FOR_ERRATA

So far nobody reproduced the issue apart from ben. Also not sure what to use as workaround ... killall firefox ?

So far nobody reproduced the issue apart from ben. Also not sure what to use as workaround ... killall firefox ?

Closing as nobody was able to reproduce.

Status: UNCONFIRMED => RESOLVED
Resolution: (none) => WORKSFORME