Bug 581780 - shutdown does not work - no action
Summary: shutdown does not work - no action
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-workspace
Version: 12
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-13 08:23 UTC by Richard Z.
Modified: 2010-09-14 23:49 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-14 23:49:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Richard Z. 2010-04-13 08:23:32 UTC
After hitting the "poweroff" button or choosing shutdown from some menu the message "shutting down in 30s" appears. However absolutely nothing ever happens, regardless whether I wait the 30s or hit shutdown immediately.

Everything continues to work as if I did not ever hit shutdown. Shutting down via "telinit 0" works immediately.

Sorry had no idea which component exactly this belongs to. No suspicious dmesg or other messages as far as I can tell.

Might be related to the pulseaudio comments here: https://bugzilla.redhat.com/show_bug.cgi?id=571065

Can't recall hearing the login sound in KDE either.

Comment 1 Richard Z. 2010-04-24 17:47:17 UTC
"logout" does not work either. "loging out in 30s" apepars and nothing happens.

Only way to logout is to kill X server which is ridiculous.

Comment 2 Richard Z. 2010-04-28 20:20:28 UTC
I can no longer reproduce it approximately since Monday. It is possible that it was the updates installed on Sunday or it was possibly one of the many tweaks in the systemsettings which I have done at the same time.

Also wrote related comments to https://bugzilla.redhat.com/show_bug.cgi?id=571065

In case I can reproduce it again - what is the procedure to debug it? Can I set some enviroment variable to get verbose output to systemlog? Which process would I strace?

Comment 3 Rex Dieter 2010-09-14 23:49:06 UTC
Sorry for chiming in so late, but if this is no longer reproducible, let's stick a fork in it and close this out.

Feel free to reopen and/or add any new information, if you have it.

(As far as debugging, my first suspect would be dbus not delivering the messages properly).


Note You need to log in before you can comment on or make changes to this bug.