[SOLVED] Can not shut down or reboot in GNOME 3.8.4/Jessie

goumba · 05-28-2014, 12:07 PM

Hey guys,

This started a few weeks back with an update but I'm just getting to posting now, so unfortunately I don't remember exactly what was updated.

I'm running GNOME 3.8.4 with Jessie. A few things broke (like not being able to run Terminal because of a non-UTF8 locale issue not being handled graciously by the terminal devs and GNOME 3 not honoring system wide locales), but I can't fix this one.

If I select Power Off from the user menu, the hard drive will flash for a second or two, then do nothing. I can still run programs normally, except on some applications (mostly GTK+ 2, and some GTK+ 3 programs), themes are broken.

If I select Power Off from the user menu, or run the following in a terminal:

Code:

$ gnome-session-quit  --power-off

Any applications besides that terminal (if I use the terminal) will quit. The hard drive will run a second, and I can't do anything in that terminal window. Shortly after, I regain control, and can use the shell as normal.

Now, I'll try again (or if I selected Power Off the first time, I now open a terminal),

Code:

$ gnome-session-quit  --power-off

** (gnome-session-quit:5784): WARNING **: Failed to call Shutdown: Shutdown interface is only available during the Running phase

Of course,

Code:

$ sudo halt

will always work, but it's annoying to do it every time.

Any ideas?

jdkaye · 05-28-2014, 12:27 PM

The current version for gnome in Jessie is 3.8+6 and not 3.8+4. You might try updating gnome to the current version and see if that sorts out your problem. Be sure you run apt-get or aptitude update before installing the package to make sure you have the most recent version. Watch carefully for any error messages or any news of broken pages.
jdk

goumba · 05-28-2014, 02:46 PM

Thank you for your response jdkaye,

I did, last night, and no GNOME packages were updated, and nothing in GNOME being held back. Tried again now, as well.

I guess I'll have to start there as to why I'm not getting the latest packages. All I'e got in sources.list are the US debian repos for jessie/testing, with no third party repos to cause conflicts. Hmmm...

Code:

deb ftp://ftp.us.debian.org/debian/ testing main contrib non-free
deb-src ftp://ftp.us.debian.org/debian/ testing main contrib non-free

Edit:

Well, silly me, I got my version information from the GNOME Settings tools under "details" as it was the laziest way to do it. Using apt-cache and checking version numbers shows the package gnome and gnome-core are 3.8+6. gnome-desktop3-data is 3.8.4-2, and apt-cache policy indicates that is the newest candidate available. gnome-shell is 3.8.4-8+b1 (newest candidate).

jdkaye · 05-28-2014, 03:03 PM

Can you post the output of this command:

Code:

aptitude show gnome

jdk

goumba · 05-28-2014, 03:24 PM

Sure.

Code:

$ aptitude show gnome
Package: gnome                           
State: installed
Automatically installed: yes
Version: 1:3.8+6
Priority: optional
Section: metapackages
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Architecture: amd64
Uncompressed Size: 54.3 k
Depends: gnome-core (= 1:3.8+6), desktop-base, network-manager-gnome (>= 0.9.4),
         aisleriot (>= 1:3.4), cheese (>= 3.4), evolution (>= 3.8),
         evolution-plugins (>= 3.8), file-roller (>= 3.4), gedit (>= 3.4),
         gnome-color-manager (>= 3.4), gnome-documents (>= 0.4), gnome-games (>=
         1:3.4), gnome-nettool (>= 3.2), nautilus-sendto (>= 3.0), gnome-orca
         (>= 3.4), rygel-preferences (>= 0.14), seahorse (>= 3.4), totem (>=
         3.0), vinagre (>= 3.4), alacarte (>= 0.13.4), avahi-daemon, gimp (>=
         2.8), gnome-media (>= 3.4), gnome-tweak-tool (>= 3.4), hamster-applet
         (>= 2.91.3), inkscape (>= 0.48), libreoffice-gnome, libreoffice-writer
         | abiword (>= 2.8), libreoffice-calc | gnumeric (>= 1.10),
         libreoffice-impress, rhythmbox (>= 2.96), shotwell, simple-scan,
         sound-juicer (>= 3.4), tomboy (>= 1.10) | gnote, tracker-gui,
         transmission-gtk, xdg-user-dirs-gtk, cups-pk-helper (>= 0.2),
         gedit-plugins (>= 3.4), gnome-shell-extensions (>= 3.4),
         gstreamer1.0-libav (>= 0.10.13), gstreamer1.0-plugins-ugly (>=
         0.10.19), rhythmbox-plugins, rhythmbox-plugin-cdrecorder,
         rygel-playbin, rygel-tracker | rygel, telepathy-gabble,
         telepathy-rakia, telepathy-salut, totem-plugins, libgtk2-perl (>=
         1:1.130)
Recommends: browser-plugin-gnash, gdebi, telepathy-idle
Suggests: dia-gnome, gnome-boxes, gnucash, libreoffice-evolution, planner,
          iceweasel-l10n-all, xul-ext-adblock-plus, xul-ext-gnome-keyring
Conflicts: gnome
Description: Full GNOME Desktop Environment, with extra components
 This is the GNOME Desktop environment, an intuitive and attractive desktop,
 with extra components. 
 
 This meta-package depends on the standard distribution of the GNOME desktop
 environment, plus a complete range of plugins and other applications
 integrating with GNOME and Debian, providing the best possible environment to
 date.

jdkaye · 05-28-2014, 11:51 PM

Quote:

$ aptitude show gnome
Package: gnome
State: installed
Automatically installed: yes
Version: 1:3.8+6

I don't know if this is of any use but you have version 3.8+6 (same as mine) installed and not 3.8.4. You could try reinstalling gnome using the command

Code:

sudo aptitude reinstall gnome

That could either (a) fix the problem or (b) at least throw up some useful error messages so that you know what the problem is (e.g. missing dependencies, broken packages).
jdk

EDDY1 · 05-29-2014, 12:48 AM

I have 2 system Jessie & Sid neither of them shutdown without running command from terminal. Also I've been complaining about GTK bug, which affects changes to main menu, for a while.
I ran across 1 supposed solution that told me to delete the /home/user/.config/menus file, which I did & it hasn't changed anything.

goumba · 05-29-2014, 06:31 AM

Quote:

Originally Posted by jdkaye

I don't know if this is of any use but you have version 3.8+6 (same as mine) installed and not 3.8.4. You could try reinstalling gnome using the command

Code:

sudo aptitude reinstall gnome

That could either (a) fix the problem or (b) at least throw up some useful error messages so that you know what the problem is (e.g. missing dependencies, broken packages).
jdk

Thank you jdk,

I stated in my previous post, the package itself is in fact 3.8+6, but something else is amiss here as GNOME itself (System Settings -> Details) shows 3.8.4.

I tried your suggestion, the only package reinstalled was gnome, with version 3.8+6 and no errors.

Code:

$ sudo aptitude reinstall gnome
The following packages will be REINSTALLED:
  gnome 
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 54 not upgraded.
Need to get 0 B/22.0 kB of archives. After unpacking 0 B will be used.
(Reading database ... 351858 files and directories currently installed.)
Preparing to unpack .../gnome_1%3a3.8+6_amd64.deb ...
Unpacking gnome (1:3.8+6) over (1:3.8+6) ...
Setting up gnome (1:3.8+6) ...
$

I see EDDY1 has the same issue, so I'm not alone. If I can't rectify this in the next day, I'll submit a report, as I can find none on this issue in the bug tracker.

cynwulf · 05-29-2014, 07:27 AM

Post output

Code:

$ ps aux|grep systemd

goumba · 05-29-2014, 09:13 AM

Before clicking Power Off from the user menu:

Code:

$ ps aux | grep systemd
root      3847  0.0  0.0  37148  1772 ?        S    07:37   0:00 /lib/systemd/systemd-logind
anthony   7331  0.0  0.0  10468   880 pts/0    S+   10:10   0:00 grep systemd

After clicking Power Off from the user menu, and waiting a little:

Code:

~ $ ps aux | grep systemd
root      3847  0.0  0.0  37148  1772 ?        S    07:37   0:00 /lib/systemd/systemd-logind
anthony   7350  0.0  0.0  10468   876 pts/0    S+   10:11   0:00 grep systemd

Code:

$ aptitude show systemd
Package: systemd                         
State: installed
Automatically installed: yes
Version: 204-8
Priority: optional
Section: admin
Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>
Architecture: amd64
Uncompressed Size: 5,054 k
Depends: libacl1 (>= 2.2.51-8), libaudit1 (>= 1:2.2.1), libc6 (>= 2.17), libcap2
         (>= 2.10), libcryptsetup4 (>= 2:1.4.3), libdbus-1-3 (>= 1.1.1),
         libgcrypt11 (>= 1.5.1), libkmod2 (>= 5~), liblzma5 (>=
         5.1.1alpha+20120614), libpam0g (>= 0.99.7.1), libselinux1 (>= 2.1.9),
         libsystemd-daemon0 (= 204-8), libsystemd-journal0 (= 204-8), libudev1
         (>= 189), libwrap0 (>= 7.6-4~), libsystemd-login0 (= 204-8), util-linux
         (>= 2.19.1-2), initscripts (>= 2.88dsf-17), sysv-rc, udev, acl,
         adduser, libcap2-bin
Recommends: libpam-systemd
Suggests: systemd-ui
Conflicts: klogd, klogd, systemd
Breaks: lsb-base (< 4.1+Debian4), lsb-base (< 4.1+Debian4), lvm2 (< 2.02.84-1),
        lvm2 (< 2.02.84-1)
Description: system and service manager
 systemd is a replacement for sysvinit.  It is dependency-based and able to read
 the LSB init script headers in addition to parsing rcN.d links as hints. 
 
 It also provides process supervision using cgroups and the ability to not only
 depend on other init script being started, but also availability of a given
 mount point or dbus service.
Homepage: http://www.freedesktop.org/wiki/Software/systemd

cynwulf · 05-29-2014, 10:59 AM

Well systemd is installed and enabled on your system so one would think that gnome should be shutting down and rebooting normally. Ensure your system is completely up to date and consider reporting a bug.

assasukasse · 06-01-2014, 03:40 AM

Hello
exactly the same problem over here.
No way to reboot unless a reboot command from a root terminal, no way to shutdown or logout either.
It is a new install done with netinst cd jessie.
Another laptop installed a few weeks ago is performing fine so I have no idea what happened this time.
XFCE was installed by default but I completely removed it (and lightdm)
I put on a bug for gnome-shell (750058) as I was unsure which package was affected...

Seemoi · 06-05-2014, 07:49 AM

Don't you enjoy spending hours/days trying to fix yet another
non-backwardly-compatible forced change that interrupts your work ?

I believe your troubles are related to Debian Testing not completely
switching to systemd yet.

https://wiki.debian.org/systemd

From the Wiki;

Code:

To install systemd run:

# apt-get update
# apt-get install systemd

This will install the systemd packages but will not configure systemd as your init system.

Configuring for testing

To test systemd before switching to it by default, you can add the following boot parameter to the kernel:

init=/bin/systemd

I've tried the init=/bin/systemd trick. It solves the logout/reboot/poweroff problem.
But...... all kinds of other system irregularities spring up. Your mileage may vary.

If you're lucky and you like what you see, you can switch over to systemd full on.

If you would like an icon available to use that will shutdown with the 'halt' command,
1. Create a file as root, e.g. nano halt.desktop. Point to whichever icon you want.

Code:

[Desktop Entry]
Name=Halt
Comment=Power Down
Exec=gksu halt
Icon=/usr/share/icons/stop-hand.svg
Terminal=false
Type=Application
StartupNotify=true
Categories=GNOME;GTK;Utility;
Keywords=shutdown;halt;power down;

2. Move halt.desktop to /usr/share/applications/
$ mv halt.deskop /usr/share/applications
3. Logout, Login
4. Use your new halt by adding it to the favorites gnome-shell dock. Poweroff garaunteed.

Good Luck.

Regards.

jens · 06-08-2014, 08:11 AM

Quote:

Originally Posted by Seemoi

I believe your troubles are related to Debian Testing not completely
switching to systemd yet.

Installing systemd-sysv will remove everything sysv (conflicts with its core package) and add all needed links for /sbin/init (it also includes the needed docs to convert ancient init scripts).

EDDY1 · 06-08-2014, 10:42 AM

Quote:

Originally Posted by jens

Installing systemd-sysv will remove everything sysv (conflicts with its core package) and add all needed links for /sbin/init (it also includes the needed docs to convert ancient init scripts).

Will this also fix the GTK-accel bug?