|
Bugzilla – Full Text Bug Listing |
| Summary: | Powersave applet needs some time to display the current state | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Michael Stather <kontakt> |
| Component: | Mobile Devices | Assignee: | Holger Macht <hmacht> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | behlert |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Michael Stather
2005-09-25 19:42:13 UTC
First possibility: hal-addon-acpi is not running or another process is accessing /proc/aci/event So please post the two outputs of: ps aux | grep hal lsof | grep "\proc\/acpi\/event" Second possibility: As you already mentioned it could be the time for fetching acpi information. Then you can try to boot with ec_burst=0 and check if the problem remains. I tried what you suggested: hal-addon-acpu is running the lsof grep doesn´t return anything (file isn´t in use) and if I boot with the force parameter there´s no change. I can live with this, if it takes so long to fetch the state from acpi. I just thought that perhaps the applet (which seems to be maintaines by SuSE) doesn´t fetch the data immediataly when it starts. Forgot to mention: You tried the lsof command as root? No unfortunately not *g Now the result is: acpid 5133 root 3r REG 0,3 0 4026532095 /proc/acpi/event This looks ok. Can you please do the following: rcpowersaved stop rchal stop rchal start rcpowersaved start If you start kpowersave now, does the icon have the correct state immediately? If so should be fixed in the final product. Yes now it displays the state immediately Ok, thanks. This will be fixed in final product. We changed the boot order to let hal start after acpid. |