suspend fails in KDE, but it works in GNOME

[Christian Leber]

Hardware: Laptop Dell Latitude D830 (intel chipset, intel gfx)

With gutsy i386 (updated 20070811) suspend to ram works in GNOME without any problem
and reliable (i tried it 15 times).

When I use KDE there are multiple issues:
-after suspending, the first resume directly leads back to the suspend state
-when the resume works the KDE background is only garbage
-after 1 to 3 working resumes the screen just stays off (not black, off)
 but the system works, i can login with ssh to it

The next point that makes me thinking that it is a KDE problem is that i can
open a root shell in KDE and run /etc/acpi/sleep.sh and it works realiable too. (tried it 12 times)

I have no idea where the problem exactly is and how it can be solved.

[Christian Leber (christian-leber)]

Linux ijuz-laptop 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux

[Christian Leber (christian-leber)]

i retried the suspend button in kde and now the pattern was:
-suspend
-resume -> goes back to suspend directly
-resume -> everything seems fine
-suspend
-resume -> goes back to suspend directly
-resume -> everything seems fine
-suspend
-resume -> goes back to suspend directly
-resume -> screen is black (not off) i can switch to a console and to X and X is there, but the KDE background is garbage

attached the kern.0.log from this

[CMGeorge (cmgeorge)]

I can confirm this mail too.
Is happened on my laptop.
I will test today to see if is happened in Gnome too.

-----Original Message-----
From: "Christian Leber" <email address hidden>
To: <email address hidden>
Sent: 11-08-07 22:08
Subject: [Bug 131855] Re: suspend fails in KDE, but it works in GNOME

i retried the suspend button in kde and now the pattern was:
-suspend
-resume -> goes back to suspend directly
-resume -> everything seems fine
-suspend
-resume -> goes back to suspend directly
-resume -> everything seems fine
-suspend
-resume -> goes back to suspend directly
-resume -> screen is black (not off) i can switch to a console and to X and X is there, but the KDE background is garbage

attached the kern.0.log from this

** Attachment added: "kern.log.0.bz2"
   http://launchpadlibrarian.net/8783360/kern.log.0.bz2

--
suspend fails in KDE, but it works in GNOME
https://bugs.launchpad.net/bugs/131855
You received this bug notification because you are a member of Kubuntu
Testers, which is a bug contact for kubuntu-meta in ubuntu.

[Christian Leber (christian-leber)]

I had suspend problems with my old laptop (Dell Latitude D810/feisty) too, I "fixed" it by using
a 2.6.19.7 kernel because suspend failed often with >=2.6.20.

As stated here: http://lkml.org/lkml/2007/6/16/163

I thought it's a kernel problem, but today i tried running a 2.6.20 and used /etc/acpi/sleep.sh and it works flawless for at least 13 times in a row.
When i use the button, so somehow KDE does something and it fails. (first 2 resumes work, the 3rd brigns some garbage in some windows and
the 4th time it failed)

I don't know what it is, but I'm very sure it is something in KDE.

[Gabriel Ambuehl (gabriel-ambuehl)]

Mine (D830, Intel GMA) does something different: rarely, it will wake up in KDE just fine, if not, it will be there with a blank screen and can only more be power cycled. The same happens if I do
sudo pmi action suspend
in text mode. I'm still trying to get it to display some usable debug information. Did any of you change any configuration files?

[Gabriel Ambuehl (gabriel-ambuehl)]

I just tried
sudo /etc/acpi/sleep.sh
from within konsole on
Linux host 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 GNU/Linux
and I get the black screen as well, consistently even.

[Christian Leber (christian-leber)]

I'm not 100% sure what sudo does, please retry from a real root (su) console.
(perhaps dcop still works with sudo, i have no idea)

Does it work with gnome?

[Christian Leber (christian-leber)]

In the meantime i got a report from someone with the same problem:
*IBM Thinkpad T23 (PIIIm)
*gutsy (2.6.23-rc3ish kernel)

s2r with the button when KDE is running -> brick, doesn't resume at all

/etc/acpi/sleep.sh as root -> works

[Gabriel Ambuehl (gabriel-ambuehl)]

My D830 goes to suspend using pmi action suspend as well as /etc/acpi/sleep.sh, but upon wake up, I get a blank screen with the caps and numlock LEDs blinking, neither of which are active before suspend, and the HD spins up.

I updated it to BIOS A04 which didn't change anything.

[Gabriel Ambuehl (gabriel-ambuehl)]

As of Thursday, I can suspend from KDE (using guidance-power-manager) as well as from the console.

[Christian Leber (christian-leber)]

I have to disagree, the problem isn't solved.
When using the suspend button, the laptop still goes directly back to suspend after resuming and often the screen is full of garbage, a console double switch sometimes helps, but not always.

garbage as in blinking colourfull ascii signs

when calling /etc/acpi/sleep.sh directly the problem does not exist

[Gabriel Ambuehl (gabriel-ambuehl)]

What alsa driver are you using? Are you using a docking station (that together
with alsa seems to be the main culprit for me)?

[Richard Guo (rfguo)]

I have the same problem on Kubuntu Gutsy, all latest updates installed. My machine is a Dell Latitude D620 with Intel GMA 950.

After the machine goes on standby, either from command line, guidance power manager, fn+escape, kde shutdown->suspend, upon resuming, I get a black screen with no response from keyboard or mouse. Ctrl-Alt-Backspace fails to kill X. Haven't tried ssh-ing. Only a hard power reset can reboot the machine.

The same thing happens when the screen goes into DPMS power down without suspending the whole machine (the "blank screen" option from guidance). When I try to wake up the screen, I don't see the password prompt from KDE but get a black screen.