"Shutdown" and "Restart" buttons disabled in XFCE shutdown dialog

Bug #190312 reported by Remove Me
6
Affects Status Importance Assigned to Milestone
xfce4-session (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: xfce4-session

XUbuntu, xfce as window manager, with xfce panel and compiz running (started out of a terminal and sent in bg with everything redirected into /dev/null). GDM.

After some heavy OpenGL usage (ioquake and compiz abuse) the buttons
in logout/shutdown dialog were shown grayed out and disabled.
"Logout" and "Switch user" worked.
Trying to logout and select Shutdown causes a restart of GDM.

.xsession-errors has these:
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.AccessDenied) A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.NetworkManager" member "state" error name "(unset)" destination "org.freedesktop.NetworkManager")
Terminated

** (xfce4-session:2979): WARNING **: xfsm-shutdown-helper.c:151: Failed to contact HAL: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.Hal.Device.SystemPowerManagement" member "ThisMethodMustNotExistInHal" error name "(unset)" destination "org.freedesktop.Hal")
** Message: xfsm-shutdown-helper.c:235: HAL not available or does not permit to shutdown/reboot the computer, trying sudo fallback instead.

(xfce4-session:2979): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed

(xfce4-session:2979): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed

** (xfce4-session:2979): CRITICAL **: xfsm_shutdown_helper_destroy: assertion `helper != NULL' failed

and an attempt to strace the xfce4-session process shows:

$ strace -ff -e execve -v -s 1024 -p 2979
Process 2979 attached - interrupt to quit
Process 30804 attached (waiting for parent)
Process 30804 resumed (parent 2979 ready)
[pid 30804] execve("/usr/bin/sudo", ["sudo", "-H", "-S", "-p", "XFSM_SUDO_PASS ", "--", "/usr/lib/xfce4-session/xfsm-shutdown-helper"], ["GNOME_KEYRING_PID=2849", "USER=raa", "GNOME_KEYRING_SOCKET=/tmp/keyring-F9DoJ6/socket", "SSH_AGENT_PID=2968", "HOME=/home/raa", "DESKTOP_SESSION=xfce4", "LC_CTYPE=", "GDM_XSERVER_LOCATION=local", "DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-nhLYr6IaAT,guid=d8cb5f1dde9ec5612ec3580047ac9b61", "LOGNAME=raa", "USERNAME=raa", "WINDOWPATH=7", "PATH=/home/raa/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games", "DISPLAY=:0.0", "LANG=C", "XAUTHORITY=/home/raa/.Xauthority", "SSH_AUTH_SOCK=/tmp/ssh-TTajah2853/agent.2853", "SHELL=/bin/bash", "GDMSESSION=xfce4", "PWD=/home/raa", "XDG_DATA_DIRS=etc/xdg/xubuntu:/usr/local/share/:/usr/share/:/usr/share/gdm/:/usr/share", "MANPATH=:/home/raa/share/man", "SESSION_MANAGER=local/steel:/tmp/.ICE-unix/2979", "LC_ALL=C", "LANGUAGE=C"]) = 0
Process 30804 detached
--- SIGCHLD (Child exited) @ 0 (0) ---
Process 2979 detached

and some more

writev(16, [{"l\1\0\1\0\0\0\0\22\0\0\0\264\0\0\0\1\1o\0%\0\0\0/org/freedesktop/Hal/devices/computer\0\0\0\6\1s\0\23\0\0\0org.freedesktop.Hal\0\0\0\0\0\2\1s\0000\0\0\0org.freedesktop.Hal.Device.SystemPowerManagement\0\0\0\0\0\0\0\0\3\1s\0\33\0\0\0ThisMethodMustNotExistInHal\0\0\0\0\0", 200}, {"", 0}], 2) = 200
gettimeofday({1202510043, 226718}, NULL) = 0
poll([{fd=16, events=POLLIN, revents=POLLIN}], 1, 2000) = 1
read(16, "l\3\1\0014\1\0\0\23\0\0\0m\0\0\0\6\1s\0\5\0\0\0:1.17\0\0\0\4\1s\0\'\0\0\0org.freedesktop.DBus.Error.AccessDenied\0\5\1u\0\22\0\0\0\10\1g\0\1s\0\0\7\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0/\1\0\0A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface \"org.freedesktop.Hal.Device.SystemPowerManagement\" member \"ThisMethodMustNotExistInHal\" error name \"(unset)\" destination \"org.freedesktop.Hal\")\0", 2048) = 436
read(16, 0x8405138, 2048) = -1 EAGAIN (Resource temporarily unavailable)
write(2, "\n** (xfce4-session:2979): WARNING **: xfsm-shutdown-helper.c:151: Failed to contact HAL: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface \"org.freedesktop.Hal.Device.SystemPowerManagement\" member \"ThisMethodMustNotExistInHal\" error name \"(unset)\" destination \"org.freedesktop.Hal\")\n", 393) = 393
write(2, "** Message: xfsm-shutdown-helper.c:235: HAL not available or does not permit to shutdown/reboot the computer, trying sudo fallback instead.\n", 140) = 140

I don't have /usr/lib/xfce4-session/xfsm-shutdown-helper and was not able to find it.

Revision history for this message
Gauvain Pocentek (gpocentek) wrote :

If the "Terminated" message means that dbus ended then it's more an nm bug, not an xfce4-session one. Can you try to reproduce the bug and see if the dbus session (the user session) is still running?
Thanks.

Changed in xfce4-session:
status: New → Incomplete
Revision history for this message
Remove Me (remove-me) wrote : Re: [Bug 190312] Re: "Shutdown" and "Restart" buttons disabled in XFCE shutdown dialog

Gauvain Pocentek, Sat, Feb 09, 2008 06:07:07 +0100:
> If the "Terminated" message means that dbus ended then it's more an
> nm bug, not an xfce4-session one. Can you try to reproduce the bug
> and see if the dbus session (the user session) is still running?

How do I do this? Precisely, how do I find if the user dbus session is
still running?

Revision history for this message
Gauvain Pocentek (gpocentek) wrote :

run 'ps aux | grep dbus' in a terminal and see if the dbus process are listed for your user.

Revision history for this message
Remove Me (remove-me) wrote :

Gauvain Pocentek, Sat, Feb 09, 2008 12:14:43 +0100:
> run 'ps aux | grep dbus' in a terminal and see if the dbus process are
> listed for your user.

Ok, will do next time it happens

Revision history for this message
Joel Oliver (joelol75) wrote :

Also make sure that if you installed xserver-xgl at one time, an update to Gutsy will cause this problem until it is removed.

Revision history for this message
Remove Me (remove-me) wrote :

JoelOl75, Sat, Feb 09, 2008 20:25:52 +0100:
> Also make sure that if you installed xserver-xgl at one time, an update
> to Gutsy will cause this problem until it is removed.

xserver-xgl is not installed.

Checking for Xgl: not present.
Detected PCI ID for VGA: 01:00.0 0300: 1002:5961 (rev 01) (prog-if 00 [VGA])
Checking for texture_from_pixmap: not present.
Trying again with indirect rendering:
Checking for texture_from_pixmap: present.
Checking for non power of two support: present.
Checking for Composite extension: present.
Comparing resolution (1680x1050) to maximum 3D texture size (2048): Passed.
Checking for nVidia: not present.
Checking for FBConfig: present.
Checking for Xgl: not present.
Starting emerald

Revision history for this message
Remove Me (remove-me) wrote :

It just happened again:

$ ps -ef |grep dbus
103 2063 1 0 Feb13 ? 00:00:00 /usr/bin/dbus-daemon --system
root 2109 2107 0 Feb13 ? 00:00:00 dbus-daemon --session --print-address --nofork
user 2855 2751 0 Feb13 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session startxfce4
user 2858 1 0 Feb13 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session startxfce4
user 2859 1 0 Feb13 ? 00:00:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 8 --session
user 18603 18499 0 00:03 pts/1 00:00:00 grep dbus

There is no dbus-session listed for the user. Any idea how to restart it, by the way?

There is not a lot from network manager. This is the last (from /var/log/daemon.log):

Feb 13 08:26:25 steel NetworkManager: <WARN> nm_signal_handler(): Caught signal 15, shutting down normally.
Feb 13 08:26:25 steel NetworkManager: <info> Caught terminiation signal
Feb 13 08:26:25 steel NetworkManager: <debug> [1202887585.069387] nm_print_open_socks(): Open Sockets List:
Feb 13 08:26:25 steel NetworkManager: <debug> [1202887585.069447] nm_print_open_socks(): Open Sockets List Done.
Feb 13 08:26:25 steel NetworkManager: <info> Deactivating device wlan0.
Feb 13 08:26:25 steel rpc.statd[1595]: Caught signal 15, un-registering and exiting.
Feb 13 08:26:27 steel mountd[2330]: Caught signal 15, un-registering and exiting.
Feb 13 18:33:16 steel NetworkManager: <info> starting...
Feb 13 18:33:17 steel NetworkManager: <info> wlan0: Device is fully-supported using driver 'rt2500pci'.
Feb 13 18:33:17 steel NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
Feb 13 18:33:17 steel NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
Feb 13 18:33:17 steel NetworkManager: <info> Now managing wireless (802.11) device 'wlan0'.
Feb 13 18:33:17 steel NetworkManager: <info> Deactivating device wlan0.
Feb 13 18:33:17 steel NetworkManager: <debug> [1202923997.763417] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/storage_model_DVD_A__DH20A1S').

Revision history for this message
Daniele Dellafiore (ildella) wrote :

I have this problem: ubuntu hardy up to date, nvidia driver, NO compiz.
btw, i am using gnome.
dell xps 1530, core 2 duo, nvidia 8600m gt.

Tell me what I can provide for additional info.

Revision history for this message
Remove Me (remove-me) wrote :

All requested info provided

Changed in xfce4-session:
status: Incomplete → New
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Note to Della: Could you try to get an strace and backtrace also? Please include whether or not the dbus is still running per Gauvain Pocentek's note above. Thanks for confirming this.

Changed in xfce4-session:
assignee: nobody → charlie-tca
status: New → Incomplete
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release, Hardy 8.04?

Thanks in advance.

Revision history for this message
Remove Me (remove-me) wrote :

I don't know. Haven't used Compiz nor played Quake for a long while.
Have there been any activity in XFCE recently?

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in xfce4-session:
assignee: charlie-tca → nobody
status: Incomplete → Invalid
Revision history for this message
Remove Me (remove-me) wrote :

It looks like you closed the report because no one cares, and _not_ because it lacks any information.
No one ever tried to fix the bug.

Just be frank about it.

Revision history for this message
Vincent (vinnl) wrote :

The missing information is whether it is still an issue in Ubuntu 8.04. I suppose it has to be marked as "incomplete" instead of "invalid" though.

Changed in xfce4-session:
status: Invalid → Incomplete
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

@Vincent: The requested was not supplied and by Alex comments, https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/190312/comments/12, probably won´t be. After 4 weeks, by bug-squad policy, the report is closed for lack of information. Why would it then be incomplete?

Revision history for this message
Vincent (vinnl) wrote :

@Charlie - sorry, I thought that was the thing to do when information was needed. Closing it again ;)

Changed in xfce4-session:
status: Incomplete → Invalid
Revision history for this message
apport hater (g112) wrote :

If anyone stumbles on this bug and is fed up with logind/policykit/etc. complexity,
feel free to apply the attached patch "xfce-4.12_2_force-SUDO-fallback-shutdown.patch"
and grant yourself nice&simple privilege in sudoers. See the patch header for instructions.

@ubuntu team - I apologize for non-applicable patch. I hope you can keep it here.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.