Gshutdown does not work properly

Bug #228815 reported by gerard
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gshutdown (Ubuntu)
New
Undecided
Unassigned

Bug Description

I've installed (no upgrade) Hardy. I found out that Gshutdown is in the same situation as previously Gutsy (I already mentioned it at that time!!) i.e.

When I program a session closing at a predetermined time: fine
BUT when I want to shutdown at a given time, Gshutdown actually closes the session but does not shutdown

Revision history for this message
JohnSchoffstall (js-immerbox) wrote :

I get the same behavior. New 8.04 install. When Gshutdown is run from a desktop launcher, and is set to shutdown the PC, it merely logs off the user and brings up the GDM screen. Version is 0.2. Preferences are set to 'autodetect'.

When it is run from the command line, however, it correctly shuts down the PC.

Incidentally, I get this on the terminal when I run it from the command line:

(gshutdown:24585): Gtk-CRITICAL **: gtk_tree_row_reference_new: assertion `GTK_IS_TREE_MODEL (model)' failed

(gshutdown:24585): Gtk-CRITICAL **: gtk_cell_view_set_displayed_row: assertion `GTK_IS_TREE_MODEL (cell_view->priv->model)' failed

(gshutdown:24585): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

** (gshutdown:24585): WARNING **: Failed to establish a connection with GDM: No such file or directory

I ran 0.2 in Gutsy, and it worked correctly from a launcher.

Revision history for this message
Danijel Šnajder (phantomlord-deactivatedaccount) wrote :

I confirm this, gshutdown "log out" my computer instead of turning it off, the program is only working when I'm real lucky. Can't figure out why it does work one time, and does not the other.

Revision history for this message
gerard (zzking) wrote :

On my part, I've never been lucky!!

Revision history for this message
Youri (i-bis) wrote :

I'm using Ubuntu Hardy Heron on Acer 9303 wlmi and I've got the same problem... GShutdown work properly sometimes but usualy not. It close the session instead of shuting-down...

Revision history for this message
heethen (heethen) wrote :

Got the same problem, gonna give it more testing, but it seems that gshutdown does not properly shutdown computer (just session) only when Im running a video player (Kaffeine). As I said, Im going to test some more and let you know, maybe it will be helpful. (And just to let you know, Im getting same error messages when runnning GShutdown from terminal as JohnSchoffstall)

Running:
Ubuntu Hardy
GShutdown 0.2 (After a delay, auto detect method)

Revision history for this message
Maxime Chéramy (maxime81) wrote :

The problem will be solved with the next release. Don't ask me when, I don't know. We're late.

If you know what you're doing, you can safely take the sources from our svn : svn co svn://svn.tuxfamily.org/svnroot/gshutdown/gshutdown
And compile it (./autogen.sh maybe twice and make && sudo make install)
We've add a new mechanism using dbus to shutdown the computer. It should work (at least it works on my computer running ubuntu 8.04).

Else you have 2 options :
- Configure your sudo to allow shutdown to be run as root without typing a password. And then configure gshutdown to use this custom command : sudo shutdown -h now

- Run gshutdown as root (gksu gshutdown) and configure gshutdown to use the custom command : shutdown -h now

This should work with any window and desktop manager.

Obviously, if you use the development version, please report any bugs.

Revision history for this message
rocknrollme (rocknrollme) wrote :

I can confirm this behavior on my laptop running Hardy.

Revision history for this message
Stefan (comesayhi) wrote :

I'm having the same problem

Revision history for this message
Stefan (comesayhi) wrote :

Just uninstall and reinstall
Then it works

Revision history for this message
gerard (zzking) wrote :

seems OK now with the latest updates

Revision history for this message
gerard (zzking) wrote :

problems getting even worse on Karmic:

because if I want to shut down after a timer, I don't shutdown, I only close the session

Revision history for this message
gada3one (yousef-shihadeh) wrote :

problem persists on Karmic...

Revision history for this message
LCC (lcc1211) wrote :

I tried running gksu shutdown but it can't determine my settings. I supplied GNOME & GDM & then used custom command sudo shutdown -h, but instead of shutting down, I got a reboot. Before this it was just closing the current session.

Using a Dell Inspiron 1525 with Karmic 64.

Revision history for this message
Jon Arnold (jonarnoldsemail) wrote :

This is still an issue on Lucid. When trying to shutdown, gshutdown logs out instead.

Revision history for this message
Stefan (comesayhi) wrote : Re: [Bug 228815] Re: Gshutdown does not work properly

just use

sudo shutdown

in the terminal

Revision history for this message
loeppel (loeppel) wrote :

The logout behaviour is not only a problem of gshutdown.

Try this:
1. Open a terminal (e.g. gnome-terminal)
2. Enter: sudo shutdown -h +10 (means: Shutdown in 10 minutes)
3. Now use the indicator-applet (usename in the upper right of the screen) to reboot or shutdown
4. You'll see the login (gdmv2) screen

So i think there is something wrong with the whole shutdown thing in GDMv2 ?! Verified with 9.10 (karmic) and 10.04 LTS Beta 2 (with fresh updates [as of 12. Apr 2010])!

Anyone ideas how to debug this situation? Don't know how the Display-Manager shutdown actions work.

Telling the people they should use "sudo shutdown" isn't very helpful!

Revision history for this message
The_Great_Bunghole (the-great-bunghole) wrote :

G-Shutdown used to work perfectly for me on 9.04, but on 9.10 it stopped working correctly. It just ends the session, and stays on and idle at GDM login screen. I am pretty sure this has something to do with the new way of logging in. I just used "loeppel" 's instructions.... and hopefully it will work, and if it does, I will use this from now on.

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.