Red Hat Bugzilla – Bug 475444
Can't shutdown or restart any more; only "logout" is available
Last modified: 2015-01-14 18:22:14 EST
Description of problem:
If I try any of the various ways to "leave" KDE, the only option that comes up on the "are you sure" box is "Leave" -- there's no "Shutdown" or "Restart" any more. Those choices are also gone from the kickstart menu too.
I'm filing this against kdebase-workspace because that's where the problem exhibits itself. This is almost certainly the wrong component, though, as the version I'm listing below was actually installed a while ago and I only started noticing this yesterday. I did a *lot* of updates yesterday and I'm not sure which one to suspect, though.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to shut down
No option available
Are you using kdm or gdm DESKTOPMANAGER?
I'm using GDM.
(Note that, in the meantime, I've upgraded to the KDE 4.2 Beta packages from kde-redhat ... I saw this before the upgrade and I continue to see it after, though. I can downgrade if necessary.)
Also, according to my yum.log, I installed the newest GDM (gdm-2.24.1-2.fc10.i386) yesterday, right before I started noticing this; prior to that, I was using gdm-2.24.0-12.fc10.i386 and shutdown worked fine from KDE. So I'd be suspicious of something that changed in GDM between those versions.
Afaik, shutdown/restart only works when using kdm.
Sry, missed comment #3.
This may be a dbus issue,
rpm -q dbus
Let's see what the gdm folks have to say.
% rpm -q dbus
Also, according to my yum.log, this new version of dbus was also installed yesterday; before that, I was running dbus-1.2.4-1.fc10.i386. Sorry I didn't check this before posting the previous comment.
Support for shutdown/restart when using GDM is added by this patch:
It is actually ConsoleKit handling the shutdown/restart, not GDM itself. Apparently the dbus update is blocking the communication between KDE and ConsoleKit.
(Grrr, yet another issue with that broken update, IMHO the policy change should be reverted.)
The sender of the messages is ksmserver, it implements the org.kde.ksmserver and org.kde.ksmserver-PID (where PID is the actual numeric PID, e.g. 12345) interfaces. (You may need this to define the permissions.)
Uh, actually, I mean it registers the org.kde.ksmserver and org.kde.ksmserver-PID names. (Sorry for not using the correct D-Bus terminology.)
Ping? Any insight from the ConsoleKit side?
*** Bug 476065 has been marked as a duplicate of this bug. ***
CCing Colin Walters - any chance you can look at what's happening there? This looks like fallout in ConsoleKit caused by the D-Bus security update.
Same problem here too. After updates a couple of days back. Had the well known, but unfixed dependency issue with gnome-packagekit. So I had updated that package alone from updates-testing. Apart from that, a usual update.
Same problem here also. I am up to date on all released patches, but problem still exists.
(In reply to comment #15)
> Same problem here also. I am up to date on all released patches, but problem
> still exists.
I am using kdebase-workspace-4.1.3-7.fc10.i386, still have problem.
As far as I know, this problem (and many others :) ) will be fixed in an upcoming dbus update that hasn't made it out yet -- the version of kdebase-workspace is irrelevant.
You can download the pending dbus update from the places mentioned in this mailing-list message:
I guess the only workaround we can suggest for now, is to switch to using kdm, easiest way,
yum install system-switch-displaymanager
and use that tool to do the swtich to your displaymanager of choice.
Confirmed (comment #17), upgrading (reverting) to
makes it work for me.
(In reply to comment #18)
> I guess the only workaround we can suggest for now, is to switch to using kdm,
> easiest way,
> yum install system-switch-displaymanager
> and use that tool to do the swtich to your displaymanager of choice.
this work-around works well for me. Thanks rdieter.
If I run this twice as ordinary user that is logged in via gdm in kde with dbus-1.2.8-1.fc10, then my system shuts down.
/bin/dbus-send --type=method_call --system --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop
Therefore imho it should be probably also possible to do this from kde. Btw. it also works if I remove the --type argument, but then I have to run it twice, too.
It's not normal that you have to run this twice, once should be enough!
I have no idea why D-Bus blocks the first attempt and not the second.
The only machine, that does NOT have this behaviour here, is the one with KDM instead of GDM (the only one where I have chosen only KDE first). The rest (D-Bus-versions etc.) is the same.
I am using KDM and have downgraded dbus to 1.2.4 and I see a similar problem. Instead of logout, I only see Shutdown. I am using the 4.1.85 packages from kde-redhat.
> Instead of logout, I only see Shutdown.
That's a completely different issue.
> I am using the 4.1.85 packages from kde-redhat.
In KDE 4.2, you only get the option you selected in Kickoff. Make sure you select Logout right away if you want Logout. If you're using the classic menu and only get offered one option, then that's a bug in the classic menu.
(In reply to comment #25)
> > I am using the 4.1.85 packages from kde-redhat.
> In KDE 4.2, you only get the option you selected in Kickoff. Make sure you
> select Logout right away if you want Logout. If you're using the classic menu
> and only get offered one option, then that's a bug in the classic menu.
I'm using ctrl+alt+del to get the window. I don't use menus, so I don't know how they work.
still an issue?
I'm not the original poster, but I cc'ed myself some time ago because I had the same issue with Fedora 10.
One of the updates that have been released afterwards solved the issue for me. Since it's been a while, I'm not sure which update did it.
It's no longer an issue for me.
The D-Bus revert fixed it.
Someone will need to report the warnings from dbus-22.214.171.124permissive in Rawhide so we can try to fix this for good.
(In reply to comment #29)
> The D-Bus revert fixed it.
It's more a workaround, because afaik it keeps a security hole open.
> Someone will need to report the warnings from dbus-126.96.36.199permissive in Rawhide
> so we can try to fix this for good.
What needs to be done for this and where does it need to be reported? Where are there warnings to be found?
I confirm firstname.lastname@example.org's comment.
I also updated dbus and now the logout works as expected.
Closing this as WORKSFORME as it is no longer an issue, and hopefully DBUS will get its act together.