Description of problem: Gnome 3 is broken after update the system Version-Release number of selected component (if applicable): mageia 2 beta How reproducible: Install since dvd mageia 2 beta, setup the repos with core, nonfree, tainted, each one with release and update. Restart your system and appear a message "the system can't be recover", and don't start gnome Steps to Reproduce: 1. 2. 3.
In /var/log/gdm/\:0-greeter.log Avertissement du gestionnaire de fenêtres : Log level 16: Could not load applications usage data: Erreur à l'ouverture du fichier : Permission non accordée JS ERROR: !!! Exception was: Error: Error invoking Gio.init: Erreur lors de l'appel de StartServiceByName pour org.freedesktop.login1 : GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1 JS ERROR: !!! lineNumber = '0' JS ERROR: !!! fileName = '"gjs_throw"' JS ERROR: !!! stack = '"("Error invoking Gio.init: Erreur lors de l'appel de StartServiceByName pour org.freedesktop.login1\xA0: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1")@gjs_throw:0 (null)@/usr/share/gjs-1.0/overrides/Gio.js:242 ([object _private_Gio_DBusConnection],"org.freedesktop.login1","/org/freedesktop/login1")@/usr/share/gjs-1.0/overrides/Gio.js:201 SystemdLoginManager()@/usr/share/gnome-shell/js/gdm/systemd.js:26 ()@/usr/share/gnome-shell/js/gdm/powerMenu.js:37 wrapper()@/usr/share/gjs-1.0/lang.js:167 ()@/usr/share/gjs-1.0/lang.js:194 ()@/usr/share/gnome-shell/js/ui/panel.js:1070 wrapper()@/usr/share/gjs-1.0/lang.js:167 start()@/usr/share/gnome-shell/js/ui/main.js:216 @<main>:1 By installing the old gnome-shell (3.3.5), I can use GNOME3 without any issue.
Priority: Normal => release_blockerStatus: NEW => ASSIGNEDCC: (none) => mageiaAssignee: bugsquad => olavSummary: crash gnome after update system (mageia 2 beta) => Can't start GNOME3 after updating gnome-shell to 3.3.90Source RPM: gnome 3 => gnome-shell-3.3.90-1.mga2.x86_64.src.rpmSeverity: normal => critical
That means nothing to me. Could you provide a translation? Do you have the systemd package?
Ok, I had a bug on my computer, so: not running systemd... I will try on next boot. If it's working, I will update bug report. The french part of the message means: Avertissement du gestionnaire de fenêtres : Log level 16: Could not load applications usage data: Erreur à l'ouverture du fichier : Permission non accordée Warning from the windows manager : Log level 16: Could not load applications usage data: Error while opening file: permission denied
Ok, so booting sysvinit. Do you have the systemd package still installed? GNOME-shell wants some daemons in this package. I've requested those daemons to be split out, but that hasn't happened yet. Maybe meanwhile I should make gnome-shell require systemd (this won't change what init system is used during boot).
When using systemd, gnome-shell is working as expected. Sorry for the noise... :-/ jherson cohecha: try to apply update again as it seems your mirror was not up to date and you have the gnome-settings-daemon bug fixed this morning.
Priority: release_blocker => High
I have installed the beta from the DVD, choosing Gnome as environment. I haven't ask for update. I have the same error. Yves
CC: (none) => yves.brungard_mageia
Papoteur, could you copy/paste your /var/log/gdm/\:0-greeter.log ?
i update again and all ok
(In reply to comment #7) > Papoteur, could you copy/paste your /var/log/gdm/\:0-greeter.log ? No I can't. I haven't keept the installation. Sorry. Do you think it is important to try again? Yves
I had something similar and it was solved when I removed the manually installed gnome shell extensions in ~/.local/share/gnome-shell/extensions . Does that help?
CC: (none) => reinout
Bug still valid ?
Keywords: (none) => NEEDINFO
wait after the rc do that not happen the same i have a desktop with intel core i3 generation second, all ok, but one laptop with nvidia 6100 and several times break down system
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
Assume this was a one-off. I'd expect at least a duplicate or something.
Status: ASSIGNED => RESOLVEDResolution: (none) => OLD