Bug 693086

Summary: KDE reacts delayed to power button press
Product: [openSUSE] openSUSE 11.4 Reporter: Forgotten User 7bFuVpfALd <forgotten_7bFuVpfALd>
Component: KDE4 WorkspaceAssignee: E-mail List <kde-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: ctrippe, forgotten_7bFuVpfALd
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: hwinfo output

Description Forgotten User 7bFuVpfALd 2011-05-11 11:58:11 UTC
Created attachment 429074 [details]
hwinfo output

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0.0) Gecko/20100101 Firefox/4.0

Opensuse 11.4 x84-64, latest updates applied (KDE 4.6.0)

It takes KDE ca 20sec to react to a acpi power button press with the configured action (e.g. shutdown, requester). During this time KDE components lock up.

This renders the power button useless in KDE!

Reproducible: Always

Steps to Reproduce:
1. Log into kde
2. Press the acpi power button
3. wait....
4. and wait....




On the same machine acpi power button works correctly i.e. no delay if

* done in xfce desktop 

* done a second time in the same KDE session: Cancel the logout-prompt the first time, than press power button again.

Must be a kDE thing (*sigh*)
Comment 1 Christian Trippe 2011-05-13 18:39:39 UTC
Sounds like a duplicate of bug 693419. I guess you also see "Cannot execute 'grub-set-default': not in $PATH." in /var/log/messages?
Comment 2 Forgotten User 7bFuVpfALd 2011-05-16 09:18:04 UTC
(In reply to comment #1)
> Sounds like a duplicate of bug 693419. I guess you also see "Cannot execute
> 'grub-set-default': not in $PATH." in /var/log/messages?

I don't think so. I do not have the problem with kdm described #693419 and I do not see that error message in /var/log/messages.
Comment 3 Christian Trippe 2011-11-12 14:45:17 UTC
Closing as a duplicate of a newer report as this one has more information.

*** This bug has been marked as a duplicate of bug 729823 ***