can't shutdown / reboot

[chris_c]

first off - great desktop enviroment, gets out of the way lets me use it how I want too, thanks! <rant>all I want is a file manager and app launcher, not some self involved user interface experiments that are either unconfigerable or need hacking</rant> ... and breath...

I'm running Debian testing using openbox and lightdm, and for the life of me can't see what I'm doing wrong!


I'd prefer some kind of policykit trickery if shutdown / reset can't be done without root... after all I can cleanly shutdown with the power button without need for a password !

Code: Select all

chris@debian:~$ lxde-logout 

(lxsession-logout:4666): GLib-GIO-CRITICAL **: g_dbus_proxy_call_sync_internal: assertion `error == NULL || *error == NULL' failed

(lxsession-logout:4666): GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed
chris@debian:~$

Code: Select all

chris@debian:~$ lxsession-logout 

(lxsession-logout:4676): GLib-GIO-CRITICAL **: g_dbus_proxy_call_sync_internal: assertion `error == NULL || *error == NULL' failed

(lxsession-logout:4676): GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed
chris@debian:~$

these errors above occur after pressing the shutdown button - the dialog does display

TIA

[rokytnji]

What happens with

Code: Select all

sudo shutdown -r now

or

Code: Select all

sudo shutdown -h now

Back a long time ago when I built up my LXDE core install I needed hal installed to get shutdown to work properly in AntiX/Debian.

Code: Select all

apt-cache policy hal

should tell you if you have hal installed or not. If your computer is real old. The acpi=force might apply to you.

1. sudo gedit /etc/default/grub
2. Find the line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
3. Change this to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"
4. Save the file and close the file. 5. Finally, in terminal: sudo update-grub

[chris_c]

shutdown works as expected as does dbus / console kit user shutdown/reboot/suspend see the three dbus-send commands on https://wiki.debian.org/UserShutdown

glib dbus libs are installed but I don't know what is causing glib to get null from dbus...

[rokytnji]

glib dbus libs are installed but I don't know what is causing glib to get null from dbus...

Might apply to your problem

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730123

Solved.
lxsession-logout detected systemd-logind and tried sending
shutdown/reboot command to dbus through logind.
systemd has been unintentionally installed days ago by dist-upgrading,
as gnome-settings-daemon runtime dependency.
Uninstalling systemd, lxsession-logout switched back to consolekit.