Bug 231251

Summary:	suspend2ram + un/docking issue with KDE4 session and kernel 2.6.32.x
Product:	[Unmaintained] ksmserver	Reporter:	Toralf Förster <toralf.foerster>
Component:	general	Assignee:	Lubos Lunak <l.lunak>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	drf
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	screen shot of the KDE4 screen after wakeup

Description Toralf Förster 2010-03-18 21:32:06 UTC

Version:           unknown (using 4.3.5 (KDE 4.3.5), Gentoo)
Compiler:          i686-pc-linux-gnu-gcc
OS:                Linux (i686) release 2.6.32.10

If I have my notebook in the docking station, suspend2ram it, pull it out of the docking station and wake it up (or doing the similar in the opposite direction) - the screen is either black or nearly all of the screen is black except the mouse courser and sometimes a previously opened Konsole is now with a minimal geometry seen.
This issue happens only within a KDE4 session with kernel 2.6.32.x but not with 21.6.31.x. If I use a "startx" session or if I log into a straight Xsession with kdm then there's no (big) problem so far.

Here's the bisected kernel commit :
http://bugzilla.kernel.org/show_bug.cgi?id=15100#c10

and I feel this is not the usual "kernel should not break user space" issue.

Comment 1 Oswald Buddenhagen 2010-03-18 21:47:40 UTC

this makes positively no sense to me. what makes you think that kde is in any way to blame or could at least work around the issue?

if it has anything to do with kde at all, then it is most likely either powerdevil changing policies or kwin doing some effects which confuse the driver.

Comment 2 Toralf Förster 2010-03-18 21:54:15 UTC

(In reply to comment #1)
> me. what makes you think that kde is in any way to blame

Because it is only within the KDE4 session that I cannot continue the work. If I start X11 from a console with xinit or startx, then there's no issue. If I use kdm only to login into a xinit session - there's no problem too. However startung a regular KDE4 session and the issue exists.

Comment 3 Oswald Buddenhagen 2010-03-18 22:14:04 UTC

well, as far as i'm concerned, this is a typical case of "yeah, kde triggers *yet another* kernel/driver bug. so what?". you may be able to work around it by tweaking some kde settings, but it is most unlikely that we would add any such workaround to kde itself. please come back if you have something convincing ...

Comment 4 Toralf Förster 2010-03-20 10:22:32 UTC

Created attachment 41775 [details]
screen shot of the KDE4 screen after wakeup

A straight X11 sessions (startx) doesn't have a problem to handle suspend/wakeup + change the docking station. I can use kdm to login into a straight X11 session and all is fine.

The screen shot shows the result after wakeup with kernel 2.6.34-rc2, xorg-1.7.6 and intel driver 2.10.0 under KDE4.

Therefore IMO this report should be at least handled as an enhancement request, isn't it ?