Bug 680741 - Power button respons slow on HP 6730b upgraded to 11.4 KDE
Summary: Power button respons slow on HP 6730b upgraded to 11.4 KDE
Status: RESOLVED DUPLICATE of bug 729823
Alias: None
Product: openSUSE 11.4
Classification: openSUSE
Component: KDE4 Workspace (show other bugs)
Version: Final
Hardware: x86-64 SUSE Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-18 05:55 UTC by Joost van Rooij
Modified: 2011-11-12 14:43 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joost van Rooij 2011-03-18 05:55:23 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12) Gecko/20110222 Firefox/4.0b12

Using the power button on my HP 5730b notebook to have it showing the logoff/reboot/shutdown dialog still works in 11.4 but it responds quite slow.

Once I press the power button, the KDE panels become unresponsive for about 20 seconds or so, until the logoff/reboot/shutdown dialog is shown. After that the system behaves as usual. I do not have this problem when I perform the same function from the openSUSE KDE menu.

With acpi_listen running I see the button pressing event appear immediately, but the system waits a while to process is, problably some kind of time out somewhere.

It does work when I press perform the same action after switching to the console using ctrl-alt-F1 (still in runlevel 5 though)


Reproducible: Always

Steps to Reproduce:
1. press power button
Actual Results:  
The KDE panel freezes for about 20 seconds or so before displaying the log off/shutdown/reboot dialog.

Expected Results:  
To show the log off/shutdown/reboot dialog immediately
Comment 1 Christian Trippe 2011-11-12 14:43:20 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 ***