[Bug 333926] New: Powersave not working in 10.3
https://bugzilla.novell.com/show_bug.cgi?id=333926 Summary: Powersave not working in 10.3 Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: andrew@acooke.org QAContact: qa@suse.de Found By: Customer kpowersave appears as an icon in the panel, but has no options on left click and only help/quit/title on right-click. If I restart powersaved I see the following in the logs: Oct 15 11:05:04 quiet powersaved[6229]: WARNING (readConfigFile:173) Found actions variable for non existing event: 'global.suspend2disk' Oct 15 11:05:04 quiet powersaved[6229]: WARNING (readConfigFile:173) Found actions variable for non existing event: 'global.suspend2ram' Oct 15 11:05:04 quiet powersaved[6229]: WARNING (readConfigFile:173) Found actions variable for non existing event: 'global.standby' Oct 15 11:05:04 quiet powersaved[6229]: WARNING (readConfigFile:173) Found actions variable for non existing event: 'global.resume.suspend2disk' Oct 15 11:05:04 quiet powersaved[6229]: WARNING (readConfigFile:173) Found actions variable for non existing event: 'global.resume.suspend2ram' Oct 15 11:05:04 quiet powersaved[6229]: WARNING (readConfigFile:173) Found actions variable for non existing event: 'global.resume.standby' Oct 15 11:05:04 quiet powersaved[6229]: WARNING (readConfigFile:173) Found actions variable for non existing event: 'global.suspend2disk.other' -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333926#c1
Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=333926#c2
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=333926#c3
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=333926#c4
--- Comment #4 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c5
--- Comment #5 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c6
--- Comment #6 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c7
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=333926#c8
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=333926#c9
andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c10
--- Comment #10 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c11
--- Comment #11 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c12
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=333926#c13
--- Comment #13 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c14
--- Comment #14 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c15
andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c16
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=333926#c17
--- Comment #17 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c18
andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c19
--- Comment #19 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c20
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=333926#c21
andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c22
--- Comment #22 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c23
--- Comment #23 from Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=333926#c24
--- Comment #24 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c25
--- Comment #25 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c26
--- Comment #26 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c27
--- Comment #27 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c28
--- Comment #28 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c29
--- Comment #29 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c30
Danny Kukawka
Created an attachment (id=178616) --> (https://bugzilla.novell.com/attachment.cgi?id=178616) [details] /var/log/messages after starting with "su -"
What did you to get this log? rchal restart? Looks as if hal was ready. Could you run lshal in this case or not? Was hald, hald_runner running (check: ps aux) (In reply to comment #24 from andrew cooke)
Created an attachment (id=178614) --> (https://bugzilla.novell.com/attachment.cgi?id=178614) [details] strace for hal
How did you create this strace? As root (logged in to a console) or via 'su' ? This all looks somehow strange. Could you may backup your root home clean it up and try it again? I assume this is a problem caused by the update. I don't have any machine here with such problems. Do you have a chance to get a clean 10.3 install on this machine for testing? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333926#c31
--- Comment #31 from andrew cooke
What did you to get this log?
I changed the init.d script as you requested earlier and ran /etc/init.d/haldaemon restart, in a shell started via "su -". Using "su -" makes sure that the su account has the correct path defined. In my earlier reports, when hald-runner was not found, I was using a shell started with "su", which preserved the path from my user account ("andrew"). That was the source of the problem with hald being unable to find hald-runner.
Looks as if hal was ready.
Indeed, hald appears to start. However, as I posted above (2007-10-15 12:37:27 MST) both lshal and rchal indicate that hal is not starting.
Could you run lshal in this case or not?
It gave "Could not initialise connection to hald", as I psoted above.
Was hald, hald_runner running (check: ps aux)
quiet:/etc/init.d # ps aux | grep hal root 2644 0.0 0.0 25980 1336 ? S 14:30 0:00 hald-addon-input: Listening on /dev/input/event0 /dev/input/event3 /dev/input/event4 101 2664 0.0 0.0 24892 1104 ? S 14:30 0:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket root 7916 0.0 0.0 25976 1328 ? S 15:32 0:00 hald-addon-input: Listening on /dev/input/event0 /dev/input/event3 /dev/input/event4 101 7920 0.0 0.0 16912 920 ? S 15:32 0:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket root 8001 0.0 0.0 25976 1328 ? S 15:33 0:00 hald-addon-input: Listening on /dev/input/event0 /dev/input/event3 /dev/input/event4 101 8006 0.0 0.0 16912 920 ? S 15:33 0:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket root 8047 0.0 0.0 25976 1232 ? S 15:33 0:00 hald-addon-storage: no polling because /dev/sr0 is locked via HAL root 8191 0.0 0.0 25976 1332 ? S 15:35 0:00 hald-addon-input: Listening on /dev/input/event4 /dev/input/event3 /dev/input/event0 101 8195 0.0 0.0 16908 920 ? S 15:35 0:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket root 8237 0.0 0.0 25976 1232 ? S 15:35 0:00 hald-addon-storage: no polling because /dev/sr0 is locked via HAL root 8303 0.0 0.0 25976 1332 ? S 15:36 0:00 hald-addon-input: Listening on /dev/input/event0 /dev/input/event3 /dev/input/event4 101 8307 0.0 0.0 16912 924 ? S 15:36 0:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket root 8349 0.0 0.0 25980 1228 ? S 15:36 0:00 hald-addon-storage: no polling because /dev/sr0 is locked via HAL root 8464 0.0 0.0 25976 1332 ? S 15:39 0:00 hald-addon-input: Listening on /dev/input/event0 /dev/input/event3 /dev/input/event4 101 8469 0.0 0.0 16912 924 ? S 15:39 0:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket root 9007 0.0 0.0 25980 1344 ? S 15:50 0:00 hald-addon-input: Listening on /dev/input/event4 /dev/input/event3 /dev/input/event0 101 9012 0.0 0.0 16912 920 ? S 15:50 0:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket root 9114 0.0 0.0 25980 1340 ? S 15:51 0:00 hald-addon-input: Listening on /dev/input/event0 /dev/input/event3 /dev/input/event4 101 9118 0.0 0.0 16908 920 ? S 15:51 0:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket root 11132 0.0 0.0 4188 748 pts/1 S+ 16:53 0:00 grep hal
How did you create this strace?
That strace was created following the instructions you gave, but with a shell started by "su". It was seeing the paths in the second trace which made me realise that the PATH variable was from my user account. That is when I started a new account with "su -".
As root (logged in to a console) or via 'su' ?
All posts up to and including the strace were generated by typing in an xterm console where I had previously typed "su". After the strace I used an xterm where I had typed "su -".
This all looks somehow strange.
Do you understand the difference between "su" and "su -"? What is strange? To me, the "hald-runner problem" is explained by the PATH being incorrect. However, it is still strange that "lshal" cannot connect to hald when "ps aux" shows so many hal related processes.
Could you may backup your root home clean it up and try it again? I assume this is a problem caused by the update.
I am not sure what you are referring to. The problem with hald-runner was due to the incorrect PATH being used, I believe.
Do you have a chance to get a clean 10.3 install on this machine for testing?
If I could do a clean install I would not be bothering with all this! Please, can you read what I have posted carefully. I don't think you have followed what I have done. If so, please can you explain/repeat what you would like me to do? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333926#c32
andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c33
--- Comment #33 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c34
--- Comment #34 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=333926#c35
--- Comment #35 from Danny Kukawka
This all looks somehow strange.
Do you understand the difference between "su" and "su -"? What is strange?
I'm not stupid! What strange is?: 1) the log shows that hald was comming up, but you say it doesn't work with lshal 2) on a fresh 10.3 64bit install it make no difference if you start hal from a user acount via 'su -' or plain 'su' both work fine and hal get ready!
To me, the "hald-runner problem" is explained by the PATH being incorrect. However, it is still strange that "lshal" cannot connect to hald when "ps aux" shows so many hal related processes.
Because there is no hald process. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333926#c36
--- Comment #36 from andrew cooke
Because there is no hald process.
Right, and I believe the reason for that is probably best explore in the new issue, which includes an strace and console log, and which seems to show an error unrelated to all the confusion above. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333926#c37
Danny Kukawka
Because there is no hald process.
Right, and I believe the reason for that is probably best explore in the new issue, which includes an strace and console log, and which seems to show an error unrelated to all the confusion above.
But you needn't to open a new bug for this. *** This bug has been marked as a duplicate of bug 334106 *** https://bugzilla.novell.com/show_bug.cgi?id=334106 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333926#c38
--- Comment #38 from andrew cooke
participants (1)
-
bugzilla_noreply@novell.com