Ubuntu
kde-workspace package

KDE Screenlock renders machine unusable since software-upgrade of Nov. 4th, 2011

Bug #886496 reported by udippel
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
kde-workspace (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Since my daily software update && upgrade of yesterday, every time the screen lock sets in, in does not get out of it again, except at a hard reboot.
The machine underneath is running happily, but neither keyboard nor mouse re-activate the screen. The Monitor LED indicates 'no signal', likewise to the state when the screen saver has been active for some time.

Reproducible: Always

Here is the tail end of 'ps ax' obtained through ssh when the system is 'stuck' with a blank, deactivated screen:
[...]
3223 ? Sl 0:05 /usr/lib/chromium-browser/chromium-browser --type=renderer --lang=en-US --force-fieldtest=ConnCountImpact/conn_count_6/ConnnectBackupJobs/ConnectBackupJobsEnabled/DnsImpact/default_enabled_prefetch/DnsParallelism/parallel_default/GlobalSdch/global_enable_sdch/IdleSktToImpact/idle_timeout_10/Prefetch/ContentPrefetchPrerender1/ProxyConnectionImpact/proxy_connections_32/SpdyImpact/npn_with_spdy/SuggestHostPrefix/Www_Prefix/WarmSocketImpact/warm_socket/ --disable-client-side-phishing-detection --channel=2281.0x7fdee7c69700.374597154
 3974 ? Sl 0:00 /usr/lib/kde4/libexec/kscreenlocker
 3979 ? TN 0:00 kblankscrn.kss -root
 6538 ? S< 0:00 [iprt]
 6539 ? S 0:00 udevd --daemon
 6541 ? S 0:00 udevd --daemon
 6682 ? S 0:00 [kworker/1:0]
 6699 ? S 0:05 [kworker/1:2]
 7042 ? S 0:00 [kworker/0:1]
 7046 ? S 0:00 [kworker/2:0]
 7055 ? S 0:00 [kworker/u:0]
 7057 ? S 0:00 [kworker/2:2]
 7058 ? S 0:00 [kworker/u:2]
 7059 ? S 0:00 [kworker/0:0]
 7061 ? S 0:00 [kworker/2:1]
 7062 ? S 0:00 [kworker/u:1]
 7063 ? S 0:00 [kworker/0:2]
 7066 ? Ss 0:00 sshd: udippel [priv]
 7277 ? S 0:00 sshd: udippel@pts/2
 7278 pts/2 Ss 0:00 -bash
 7333 pts/2 R+ 0:00 ps ax
$

It is not possible to kill the kscreenlocker, only the kblankscrn.kss -root can go. Then it looks like this:

3223 ? Sl 0:06 /usr/lib/chromium-browser/chromium-browser --type=renderer --lang=en-US --force-fieldtest=ConnCountImpact/conn_count_6/ConnnectBackupJobs/ConnectBackupJobsEnabled/DnsImpact/default_enabled_prefetch/DnsParallelism/parallel_default/GlobalSdch/global_enable_sdch/IdleSktToImpact/idle_timeout_10/Prefetch/ContentPrefetchPrerender1/ProxyConnectionImpact/proxy_connections_32/SpdyImpact/npn_with_spdy/SuggestHostPrefix/Www_Prefix/WarmSocketImpact/warm_socket/ --disable-client-side-phishing-detection --channel=2281.0x7fdee7c69700.374597154
 3974 ? Z 0:00 [kscreenlocker] <defunct>
 6538 ? S< 0:00 [iprt]
 6539 ? S 0:00 udevd --daemon
 6541 ? S 0:00 udevd --daemon
 6682 ? S 0:00 [kworker/1:0]
 6699 ? S 0:05 [kworker/1:2]
 7042 ? S 0:00 [kworker/0:1]
 7057 ? S 0:00 [kworker/2:2]
 7062 ? S 0:00 [kworker/u:1]
 7066 ? Ss 0:00 sshd: udippel [priv]
 7277 ? S 0:00 sshd: udippel@pts/2
 7278 pts/2 Ss 0:00 -bash
 7339 ? S 0:00 [kworker/2:0]
 7340 ? S 0:00 [kworker/u:0]
 7343 ? S 0:00 [kworker/0:0]
 7353 ? S 0:00 [kworker/2:1]
 7374 ? S 0:00 [kworker/u:2]
 7442 ? S 0:00 [kworker/0:2]
 7444 pts/2 R+ 0:00 ps ax

I cannot make out which update did this; in the last 24-48 hours? The only major item that I remember was the fglrx update of the ATI-driver.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: kde-workspace-bin 4:4.7.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sat Nov 5 18:39:57 2011
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: kde-workspace
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (22 days ago)

Revision history for this message
udippel (udippel) wrote :
Revision history for this message
udippel (udippel) wrote :

Maybe the package indicated is wrong?
After I set the screen saver to never chip in, I still get the same dead machine. I found that System Settings -> Power Management -> Power Profiles still had a 60 min of 'Screen Energy Saving' setting.
Sorry, I don't know which package is responsible for this setting? And even less could I state that the missing wakeup has to make with the *setting*. It could as well have to make with another application that doesn't wake up from sleep.

I can confirm, though, that didn't experience this bug for a looong time, until yesterday.

Revision history for this message
udippel (udippel) wrote :

I can confirm by now, that when the Power Profile does not set the Screen to 'Energy Saving', the machine works like it has always worked for me.

Revision history for this message
udippel (udippel) wrote :

And here is the list of packages upgraded in the last two days:

-rw-r--r-- 1 root root 2462 2011-11-05 09:36 upstart.list
-rw-r--r-- 1 root root 42992 2011-11-05 09:36 virtualbox-4.1.list
-rw-r--r-- 1 root root 58367 2011-11-04 22:24 virtualbox-4.1.md5sums
-rw-r--r-- 1 root root 84 2011-11-04 22:24 virtualbox-4.1.conffiles
-rwxr-xr-x 1 root root 15183 2011-11-04 22:24 virtualbox-4.1.postinst
-rwxr-xr-x 1 root root 1936 2011-11-04 22:24 virtualbox-4.1.postrm
-rwxr-xr-x 1 root root 3594 2011-11-04 22:24 virtualbox-4.1.preinst
-rwxr-xr-x 1 root root 4055 2011-11-04 22:24 virtualbox-4.1.prerm
-rw-r--r-- 1 root root 13217 2011-11-04 09:31 gnome-shell.list
-rw-r--r-- 1 root root 395 2011-11-04 09:31 libedataserverui-3.0-1.list
-rw-r--r-- 1 root root 3332 2011-11-04 09:30 gedit.list
-rw-r--r-- 1 root root 74934 2011-11-04 09:29 gedit-common.list
-rw-r--r-- 1 root root 1767 2011-11-04 09:29 fglrx-amdcccle.list
-rw-r--r-- 1 root root 7812 2011-11-04 09:29 fglrx.list
-rw-r--r-- 1 root root 2028 2011-11-04 09:28 evolution-data-server-common.list
-rw-r--r-- 1 root root 371 2011-11-04 09:28 libedata-cal-1.2-13.list
-rw-r--r-- 1 root root 379 2011-11-04 09:28 libedata-book-1.2-11.list
-rw-r--r-- 1 root root 416 2011-11-04 09:28 libecal1.2-10.list
-rw-r--r-- 1 root root 425 2011-11-04 09:28 libebook1.2-12.list
-rw-r--r-- 1 root root 355 2011-11-04 09:28 libebackend-1.2-1.list
-rw-r--r-- 1 root root 417 2011-11-04 09:27 libcamel-1.2-29.list
-rw-r--r-- 1 root root 2573 2011-11-04 09:27 evolution-data-server.list
-rw-r--r-- 1 root root 479 2011-11-04 09:27 libedataserver1.2-15.list
-rw-r--r-- 1 root root 4266 2011-11-04 09:27 binutils.list

I'd be very happy to hear which one needs downgrading to make the energy efficient monitor work again.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

I'd be most suspicious of the fglrx packages. The rest don't have much of anything to do with the screen/power saving at all.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in kde-workspace (Ubuntu):
status: New → Confirmed
Revision history for this message
Harald Sitter (apachelogger) wrote :

Still a problem with more recent versions?

Changed in kde-workspace (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for kde-workspace (Ubuntu) because there has been no activity for 60 days.]

Changed in kde-workspace (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Sergei Datsenko (dosyas) wrote :

I have this bug after upgrade to kubuntu 13.04.
After unlock both notebook's and attached monitor screens remain black (with some artifacts) and X-server eats CPU. After a minute or two it may eventually unlock the screen. On "ps" via ssh it looks like this:

dosya 2578 0.0 0.1 515792 21600 ? Sl 15:34 0:01 \_ kdeinit4: ksmserver [kdeinit]
dosya 2585 3.2 0.7 943424 94536 ? Sl 15:34 11:35 | \_ kwin -session 10d4.....
dosya 20107 0.4 0.0 0 0 ? Z 21:22 0:01 | \_ [kscreenlocker_g] <defunct>

It is not 100% reproducible, though I noticed some correlation between running chromium and this bug. I suppose kscreenlocker hangs when some OpenGL-enabled application is running.

 I tried different fglrx versions but it didn't help.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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