When I try to suspend from the KLaptop system tray icon, it goes to the "Desktop Session Locked" dialog box, and sits there forever without suspending. But KPowersave will suspend just fine. This started when I ran updates yesterday morning; worked fine before that. Tried an older kernel, no difference. Any ideas? I can switch to KPowersave if there's no solution, but I prefer KLaptop.
This is on Ubuntu 10.10 and Trinity 3.5.12.
When I try to suspend from the KLaptop system tray icon, it goes to the "Desktop Session Locked" dialog box, and sits there forever without suspending. But KPowersave will suspend just fine. This started when I ran updates yesterday morning; worked fine before that. Tried an older kernel, no difference. Any ideas? I can switch to KPowersave if there's no solution, but I prefer KLaptop.
This is on Ubuntu 10.10 and Trinity 3.5.12.
Is there any way that you can find out what packages were upgraded just before the problem started?
Tim
On 09/15/2012 01:13 PM, Timothy Pearson wrote:
Is there any way that you can find out what packages were upgraded just before the problem started?
Fortunately, apt-get keeps a log at /var/log/dpkg.log. Here's everything that got upgraded at the time it started:
tzdata 2012e-0ubuntu0.11.10 man-db 2.6.0.2-2 python-support 1.0.13ubuntu1 ureadahead 0.100.0-11 linux-image-3.0.0-26-generic 3.0.0-26.42 tzdata-java 2012e-0ubuntu0.11.10 libisc62 1:9.7.3.dfsg-1ubuntu4.4 libdns69 1:9.7.3.dfsg-1ubuntu4.4 libisccc60 1:9.7.3.dfsg-1ubuntu4.4 libisccfg62 1:9.7.3.dfsg-1ubuntu4.4 libbind9-60 1:9.7.3.dfsg-1ubuntu4.4 liblwres60 1:9.7.3.dfsg-1ubuntu4.4 bind9-host 1:9.7.3.dfsg-1ubuntu4.4 dnsutils 1:9.7.3.dfsg-1ubuntu4.4 amarok-common-trinity 4:3.5.13-1ubuntu0+ax1~oneiric amarok-engine-xine-trinity 4:3.5.13-1ubuntu0+ax1~oneiric amarok-trinity 4:3.5.13-1ubuntu0+ax1~oneiric bibletime-trinity 4:3.5.13-1ubuntu0+ax1~oneiric desktop-effects-kde-trinity 4:3.5.13-1ubuntu0+ax0~oneiric digikam-trinity 4:3.5.13-1ubuntu0+ax3~oneiric gtk-qt-engine-trinity 4:3.5.13-1ubuntu0+ax2~oneiric guidance-backends-trinity 4:3.5.13-1ubuntu0+ax0~oneiric gwenview-trinity 4:3.5.13-1ubuntu0+ax2~oneiric libk3b3-trinity 4:3.5.13-1ubuntu0+ax2~oneiric k3b-data-trinity 4:3.5.13-1ubuntu0+ax2~oneiric k3b-trinity 4:3.5.13-1ubuntu0+ax2~oneiric kaffeine-trinity 4:3.5.13-1ubuntu0+ax2~oneiric katapult-trinity 4:3.5.13-1ubuntu0+ax1~oneiric kdbusnotification-trinity 4:3.5.13-1ubuntu0+ax2~oneiric kde-guidance-trinity 4:3.5.13-1ubuntu0+ax0~oneiric kde-guidance-powermanager-trinity 4:3.5.13-1ubuntu0+ax0~oneiric kde-style-qtcurve-trinity 4:3.5.13-1ubuntu0+ax1~oneiric kde-systemsettings-trinity 4:3.5.13-1ubuntu0+ax1~oneiric kdesudo-trinity 4:3.5.13-1ubuntu0+ax1~oneiric kdmtheme-trinity 4:3.5.13-1ubuntu0+ax1~oneiric keep-trinity 4:3.5.13-1ubuntu0+ax1~oneiric kgtk-qt3-trinity 4:3.5.13-1ubuntu0+ax0~oneiric kima-trinity 4:3.5.13-1ubuntu0+ax1~oneiric kio-apt-trinity 4:3.5.13-1ubuntu0+ax1~oneiric kio-locate-trinity 4:3.5.13-1ubuntu0+ax1~oneiric kio-umountwrapper-trinity 4:3.5.13-1ubuntu0+ax0~oneiric kmplayer-base-trinity 4:3.5.13-1ubuntu0+ax2~oneiric kmplayer-konq-plugins-trinity 4:3.5.13-1ubuntu0+ax2~oneiric libevemu1 1.0.5.1-0ubuntu1 libframe1 1.1.4.1-0ubuntu1 libgrail1 2.0.1.1-0ubuntu1 libgeis1 2.1.2.1-0ubuntu1 libgrip0 0.3.2.1-0ubuntu1 libk3b3-extracodecs-trinity 4:3.5.13-1ubuntu0+ax2~oneiric linux-image-generic 3.0.0.26.30 linux-generic 3.0.0.26.30 linux-headers-3.0.0-26 3.0.0-26.42 linux-headers-3.0.0-26-generic 3.0.0-26.42 linux-headers-generic 3.0.0.26.30 linux-libc-dev 3.0.0-26.42 xserver-xorg-input-evdev 1:2.6.0-1ubuntu13.1 xserver-xorg-input-synaptics 1.4.1-1ubuntu2.1 libc-bin 2.13-20ubuntu5.1 desktop-effects-kde-trinity 4:3.5.13-1ubuntu0+ax0~oneiric python-central 0.6.17 python-support 1.0.13ubuntu1
On 09/15/2012 01:13 PM, Timothy Pearson wrote:
Is there any way that you can find out what packages were upgraded just before the problem started?
Fortunately, apt-get keeps a log at /var/log/dpkg.log. Here's everything that got upgraded at the time it started:
<snip>
It looks like a number of Slavek's SRU updates were installed, so this is the likely culprit. I am forwarding this message to the trinity-devel list so that he can be made aware of the problem.
Tim
-
Dan Youngquist -
Timothy Pearson