https://bugzilla.novell.com/show_bug.cgi?id=222523 amantia@kde.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|amantia@kde.org | ------- Comment #7 from amantia@kde.org 2006-11-20 08:07 MST ------- Ok, finally it happened again. It was not easy to reproduce, I tried several times yesterday, no luck. Today morning it resumed normally. Today I left my wife here, and asked her to suspend when she is not working anymore. When I came back the problems appeared. She told me that she logged in (in a different X server) as her user, worked there, logged out from there and suspended the computer from my users using the Leave-Suspend to Disk from the kickoff menu. On resume I also got a "suspend failed" message box. Now: lshal Could not initialise connection to hald. Normally this means the HAL daemon (hald) is not running or not ready. k3b and amarok works ok now, so the device permission problem was not strictly related to this issue. kpowersave is grayed out, and in this case - even after rchal start - using the kicker logout applet or right click-logout from the KDE desktop is a "suicide" as it instantly kills your session. -- 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, or are watching someone who is.