Installed from 5RC gnome livecd first round OK in live mode. After finish-install it drops to the "Oops something has gone wrong" fail whale. No mouse cursor and pressign enter drops to a blank screen. ctrl-alt-backspace to restart X doesn't help and neither does restarting prefdm service. Reproducible: Steps to Reproduce:
Created attachment 6032 [details] journal.txt
Lots of errors in the journal. eg. gnome-session ** Message: Execution of main.js threw exception JS_EvaluateScript() failed Unrecoverable failure in required component gnome-shell.desktop
Priority: Normal => release_blocker
Blocks: (none) => 14069
LiveDVD 32 fails in the same way. Testing LiveDVD 64 next.
LiveDVD 64 is the same.
CC: (none) => olav, thierry.vignaudSummary: 5RC: Gnome Live install "Oops something has gone wrong" => 5RC: Gnome Live install "Oops something has gone wrong" ("Gjs-WARNING **: JS ERROR: Error: Argument 'string' (type utf8) may not be null")Source RPM: (none) => gnome-shell?
Hardware: i586 => All
Valid for 2nd build also (DATE: Mon Mar 16 00:30:00 CET 2015)
Confirm same here in Vbox: Mageia-5-RC-LiveCD-GNOME-en-i586-CD.iso Mon Mar 16 00:30:00 CET 2015 md5sum: b4499ef32717b45d7f1a8ffba3157ded
CC: (none) => wilcal.int
From the log: Mar 10 16:31:29 localhost gnome-session[3079]: gnome-session[3079]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login. Mar 10 16:31:29 localhost gnome-session[3079]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login. Could someone from QA please check what the following environment variable shows: XDG_SESSION_ID I'm guessing it is either not set or empty, as the crash occurs near the following from misc/loginManager.js: > GLib.getenv('XDG_SESSION_ID') if that's empty, it probably turns to null, leading to the eventual crash and error message. Colin: Any idea how this could be empty? No recent GDM changes AFAIK.
CC: (none) => mageiaSource RPM: gnome-shell? => systemd
Not sure how to do that for the active session after it crashes Olav. I suspect a tty might not give relevant information?
Oh right, I forgot the session is gone! It's still possible, but bit difficult. Please follow below steps: - Make it crash - Leave the crash dialog!! (IIRC this ensures gnome-shell is still running) - Get the PID numbers for gnome-session, gnome-settings-daemon, gnome-shell (see #1) - Determine per PID number what XDG_SESSION_ID is set to (see #2) - Write down per process what XDG_SESSION_ID is set to (also in case you get nothing) All the processes should have XDG_SESSION_ID set. 1. Getting the PID numbers Please run: ps x | grep gnome-shell and use this to determine the PIDs for gnome-session, gnome-settings-daemon, gnome-shell. The PID is the first number on that line. Ignore any line with grep it in. 2. Determining the environment of those PIDs Now for each of the PIDs (numbers) found above, run: tr '\0' '\n' < /proc/2104/environ | grep ^XDG_SESSION_ID replace 2104 with the numbers in step #1
PS: With "leave the crash dialog" I mean leave it visible. Do not click ok or anything. Just go to a tty.
Thanks Olav, that's a useful tip. gnome-shell is not running, having already crashed I guess. gnome-session and gnome-settings-daemon do not have that env set. Using grep ^XDG instead gets.. gnome-session: XDG_CONFIG_DIRS=/etc/xdg:/etc/xdg/gnome XDG_SEAT=seat0 XDG_SESSION_DESKTOP=02GNOME gnome-settings-daemon and gnome-session-failed both: XDG_MENU_PREFIX=gnome- XDG_CONFIG_DIRS=/etc/xdg:/etc/xdg/gnome XDG_SEAT=seat0 XDGSESSION_DESKTOP=02GNOME XDG_CURRENT_DESKTOP=GNOME
Oops typo there, it should say XDG_SESSION_DESKTOP=02GNOME
After rebooting again Gnome starts OK, so this is probably a duplicate.
Other bug is 13687, I'll let others decide whether/which to close.
Please see bug 13687 comment 30 and later for additional information about this issue.
CC: (none) => remi
Valid round 4 live isos ISO: Mageia-5-RC-LiveCD-GNOME-en-i586-CD.iso DATE: Thu Mar 26 09:30:00 CET 2015 MD5: OK SHA1: OK I'll attach an up to date journal taken from the installed system.
Created attachment 6160 [details] journal-gnome-install.txt Could this issue be related to the previous l10n fix. One thing I noticed in the journal when logging out using the button on the "Oops" screen and switching TTY's to grab a log.. [gdm-autologin][2096]: pam_systemd(gdm-autologin:session): Failed to create session: VT number out of range There is also an X failure message displayed briefly when shutting down. Not sure if it help diagnose but thought it worth mentioning.
Should be fixed in last set of isos. Can you please confirm and close this bug?
CC: (none) => ennael1
tmb "big hammer" fix has done it
Status: NEW => RESOLVEDResolution: (none) => FIXED
Yes confirmed fixed with the nuclear option in reply to tmb on qa-d.