Bug#731686: gdm3: poweroff/reboot seems to be a noop
Hello Andreas, On Sun, 2013-12-08 at 20:30 +0100, Andreas Cadhalpun wrote: Hi Steven, On 08.12.2013 13:08, Steven Post wrote: When trying to reboot from inside the gdm3 login screen, nothing appears to happen. After several tries I can still login to Gnome and poweroff/reboot from there. This is another version of Bug #726763, this time with poweroff/reboot instead of suspend/hibernate, but still the same cause: Gnome 3.8 needs systemd as PID 1 for this to work. So you either have to use the 'init=/bin/systemd' boot parameter or install systemd-sysv. I just installed systemd-sysv on my laptop now (from which I'm typing this message). The good news: - the poweroff/reboot works again in the gdm login screen (although as of 3.8 seems to require the root password?) - this machine now boots up in mere seconds, instead of tens of seconds - The blurry text in Gnome is now more readable again (no idea how that could be related), this last issue popped up after upgrading this machine (it has been a few days, runs Jessie), rebooting didn't help until using systemd. This is using the NVidia proprietary driver. I'll try to look into this a bit more. Still not how it should be, but better. The bad news: I try to stay a bit neutral in the whole systemd vs sysvinit vs upstart debate, but so far here are my experiences. I don't know... it seems very invasive to require a change in init system to make your desktop work (more of an issue with Gnome, than systemd itself). I'm all for a modern init system, as long as the advantages outweigh the disadvantages. In my limited experience with systemd it looked terrible (or its integration with Gnome to be more precise), but do note that while it was installed, it was never pid 1. Now that it is pid 1, all issues I saw with it don't occur anymore (or have not yet manifested again). It doesn't feel right to me to remove an 'essential' package, but I guess we need to wait for the result of the TC. Best regards, Steven signature.asc Description: This is a digitally signed message part
Bug#731686: gdm3: poweroff/reboot seems to be a noop
Package: gdm3 Version: 3.8.4-6 Severity: normal Dear Maintainer, When trying to reboot from inside the gdm3 login screen, nothing appears to happen. After several tries I can still login to Gnome and poweroff/reboot from there. Switching to a tty and rebooting from there also works. This problem appeared after the upgrade to 3.8, no reboot ever worked from the 3.8 screen, but it worked in 3.4. Best regards, Steven -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdm3 depends on: ii accountsservice 0.6.34-2 ii adduser 3.113+nmu3 ii dconf-cli0.18.0-1 ii dconf-gsettings-backend 0.18.0-1 ii debconf [debconf-2.0]1.5.52 ii gir1.2-gdm3 3.8.4-6 ii gnome-session [x-session-manager]3.8.4-3 ii gnome-session-bin3.8.4-3 ii gnome-session-flashback [x-session-manager] 3.8.0-1 ii gnome-settings-daemon3.8.5-2 ii gnome-shell 3.8.4-5 ii gnome-terminal [x-terminal-emulator] 3.10.1-1 ii gsettings-desktop-schemas3.8.2-2 ii guake [x-terminal-emulator] 0.4.4-1 ii libaccountsservice0 0.6.34-2 ii libatk1.0-0 2.10.0-2 ii libaudit11:2.3.2-2 ii libc62.17-97 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libgdm1 3.8.4-6 ii libglib2.0-0 2.36.4-1 ii libglib2.0-bin 2.36.4-1 ii libgtk-3-0 3.8.4-1 ii libpam-modules 1.1.3-9 ii libpam-runtime 1.1.3-9 ii libpam-systemd 204-5 ii libpam0g 1.1.3-9 ii libpango-1.0-0 1.36.0-1 ii libpangocairo-1.0-0 1.36.0-1 ii librsvg2-common 2.40.0-1 ii libselinux1 2.2.1-1 ii libwrap0 7.6.q-24 ii libx11-6 2:1.6.2-1 ii libxau6 1:1.0.8-1 ii libxdmcp61:1.1.1-1 ii libxrandr2 2:1.4.1-1 ii lsb-base 4.1+Debian12 ii metacity [x-window-manager] 1:2.34.13-1 ii upower 0.9.23-2+b1 ii x11-common 1:7.7+4 ii x11-xserver-utils7.7+1 ii xterm [x-terminal-emulator] 297-1 Versions of packages gdm3 recommends: ii at-spi2-core 2.10.1-1 ii desktop-base 7.0.3 ii gnome-icon-theme 3.10.0-1 ii gnome-icon-theme-symbolic 3.10.1-1 ii x11-xkb-utils 7.7~1 ii xserver-xephyr 2:1.14.3-5 ii xserver-xorg 1:7.7+4 ii zenity 3.8.0-1 Versions of packages gdm3 suggests: ii gnome-orca3.4.2-2 ii libpam-gnome-keyring 3.8.2-2 -- debconf information: gdm3/daemon_name: /usr/sbin/gdm3 * shared/default-x-display-manager: gdm3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731686: gdm3: poweroff/reboot seems to be a noop
Hi Steven, On 08.12.2013 13:08, Steven Post wrote: When trying to reboot from inside the gdm3 login screen, nothing appears to happen. After several tries I can still login to Gnome and poweroff/reboot from there. This is another version of Bug #726763, this time with poweroff/reboot instead of suspend/hibernate, but still the same cause: Gnome 3.8 needs systemd as PID 1 for this to work. So you either have to use the 'init=/bin/systemd' boot parameter or install systemd-sysv. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
