suse 11.1 32 bit with KDE 4.2.3 running on an old toshiba laptop.
for a couple of months now i haven’t been able to use the “suspend to disk” function. when i click on it the system does the “saving system information” or whatever and shuts down fine, but when i try to restart it later i get a black screen in the middle of the booting process and the system freezes. i got to the console by doing the ctrl+alt+F1 and it asked me to log in. i logged in and it seemed fine, but i tried to get into the GUI by typing “startx” and it told me x was already running. so, what do i do next? it’s annoying to have to do a complete shut-down / startup every time i want to use the laptop for 2 minutes.
note, the problems started long before i upgraded KDE to 4.2.3.
Duplicate post merged and edited
swefal wrote:
> suse 11.1 32 bit with KDE 4.2.3 running on an old toshiba laptop.
> for a couple of months now i haven’t been able to use the “suspend to
> disk” function. when i click on it the system does the “saving system
> information” or whatever and shuts down fine, but when i try to restart
> it later i get a black screen in the middle of the booting process and
> the system freezes. i got to the console by doing the ctrl+alt+F1 and it
> asked me to log in. i logged in and it seemed fine, but i tried to get
> into the GUI by typing “startx” and it told me x was already running.
Review the tips provided by the wiki page:
Pm-utils
http://en.opensuse.org/Pm-utils
Your first steep should be checking-out the log file to find the culprit
when restoring. It is located in “/var/log/pm-suspend.log”
> so, what do i do next? it’s annoying to have to do a complete shut-down
> / startup every time i want to use the laptop for 2 minutes.
> note, the problems started long before i upgraded KDE to 4.2.3.
Well, you do not have to hibernate your computer if you are going to use it
shortly!! Just leave the computer up and running 
Greetings,
–
Camaleón
thanks for the reply. sorry if my writing seems like a mess, it’s due to lack of sleep.
anyway, thanks for the link but in my current state it might as well be in chinese. i did check the log file and there was an error message there:
utils/sleep.d/10NetworkManager =====
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
should i try to reinstall the network manager?
If you have the PolicyKit module at KDE’s systemsettings then You could edit the file that is responsible for that error You encounter.
swefal wrote:
> thanks for the reply. sorry if my writing seems like a mess, it’s due to
> lack of sleep.
> anyway, thanks for the link but in my current state it might as well be
> in chinese. i did check the log file and there was an error message
> there:
>
> utils/sleep.d/10NetworkManager =====
> Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
> Possible causes include: the remote application did not send a reply,
> the message bus security policy blocked the reply, the reply timeout
> expired, or the network connection was broken.
>
> should i try to reinstall the network manager?
Is that the only error you are seeing in the log? :-?
You can try to disable the “offending” hook (in your case that
is “10NetworkManager”) as stated here:
http://en.opensuse.org/Pm-utils#Disabling_a_hook
And see what happens…
Another thing you can try is to directly trigger the hibernation by
running “pm-hibernate” as root, and check for the output messages (in any).
Greetings,
–
Camaleón
“pm-hibernate” gave the exact same result. updating the network manager had no effect.
i tried reading about replacing the file with an empty file but i got kinda stuck with the “calling”, “touch” and the comment at the bottom “Do not set the executable bit on that dummy-hook”. i have no idea what it means and i don’t want to do something to crap up the system. again.
in any case, thanks for the fast replies. i hope this problem will be solved, unlike the graphic card driver which i gave up on for now (openGL, 3D graphics, games made after 1994…)
okay, looks like this is yet another problem with my suse that no one can solve.