KDE does not wake properly after suspend

Bug #1245522 reported by Vlad Alexandru Ionescu
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-lts-saucy (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Whenever I suspend while in KDE (either via sudo pm-suspend in Konsole or via KDE's interface), upon waking up, I get to what looks like the logging output that was printed when the computer started up (rather than back to KDE's graphical interface).

At this point, the computer /seems/ frozen.

Sometimes, pressing ctrl+alt+f1, ctrl+alt+f7 gets me back to KDE after a 15-30 seconds wait. But I don't understand exactly when/how/why. But when I do get back into KDE, I get a notification saying something like graphical subsystem had to restart (not completely sure of exact wording) and also the text all over the KDE interface (all programs, including non-KDE specific ones like - eg in Chrome's address bar) is garbled (although most of it readable).

But most of the time it just remains frozen. The only way I found to make it respond again in this situation is to ssh into it and do sudo stop lightdm, sudo start lightdm (but that kills my KDE session, which defeats the purpose of suspending).

What is also interesting, is that if I run sudo pm-suspend from non-graphical tty (tty1), while KDE is running in tty7, resuming back works flawlessly (KDE works as expected when returning to tty7).

I am running Ubuntu Server 13.10, with KDE 4.11.2 (installed via sudo apt-get install kubuntu-desktop). My graphics card is NVidia NVS 300, with latest proprietary driver available in Ubuntu Repos (319-updates).

The exact same hardware was working well with Kubuntu 13.04 (suspend/wake worked as it should).

Dmesg does not show any errors.

Things that I have tried and did not work (no effect noticed):
a. The solution to this question: http://askubuntu.com/a/361706/81173
b. Different --quirks-... flags with the pm-suspend command.
c. Different versions of the NVidia proprietary graphics driver.
d. The Nouveau driver - gets back to KDE on wake, but screen frozen. After ctrl+alt+f1, ctrl+alt+f7, I get to KDE login screen (KDE crashed) and screen is garbled and unresponsive.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1245522/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Vlad Alexandru Ionescu (vlad-alexandru-ionescu) wrote :

Thanks for the (automated) reply. But I don't know how to pinpoint the exact package. For all I know, it can be anywhere: kernel, pm-utils, graphics drivers, some KDE component?

In the wiki for FindRightPackage I see "If you are unsure which package is causing the problem, a safe bet is the kernel [...]." so I'll set this to kernel.

affects: ubuntu → linux-lts-saucy (Ubuntu)
Revision history for this message
Vlad Alexandru Ionescu (vlad-alexandru-ionescu) wrote :

Some more digging: The exact message KDE displays when I can recover is "Desktop effects were restarted due to a graphics reset". Googling around, I found that "A graphics reset occurs when the kernel resets the GPU after a hang has been detected."

On another note, I've tried the 3.11.6 kernel as well (was previously on 3.11.0) and I get similar behaviour (still reproduces).

Attaching kern.log after a suspend/wake cycle, in case it's useful for anything.

Revision history for this message
penalvch (penalvch) wrote :

Vlad Alexandru lonescu, could you please execute the following in a terminal:
apport-collect 1245522

Changed in linux-lts-saucy (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux-lts-saucy (Ubuntu) because there has been no activity for 60 days.]

Changed in linux-lts-saucy (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.