KDE 4.4.3 Cannot go to sleep [Solved]

[vnandak]

Hi,
I have a unique issue. In KDE I cannot go to sleep/hibernate. It only invokes the screensaver and locks up the screen. Even if I disable the screensaver the same screensaver appears again during sleep. When in gnome, I can go to sleep without any problem. I tried all settings in the KDE System settings panel, but to no avail. I can go to sleep using console command of pm-suspend at root/sudo. This I observed only recently.

The systems details are as follows:
Linux DellXPS 2.6.33-sabayon #1 SMP x86_64 Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz Gen GNU/Linux

KDE 4.4.3, gnome 2.28.2, the system is update as of 29/5/2010.

[Fitzcarraldo]

Google tells me that it's a bug in PowerDevil. See KDE Bug Report No. 205453, in particular Comment #8 for KDE 4.4.3.

[vnandak]

Thanks for the information.Hope KDE will come up with the patch soon!
Till then gnome is the best....

[joost]

Lxnay fixed it in portage.

http://gentoo-portage.com/kde-base/powe ... eLog#ptabs

Updated version is in Entropy.

[lxnay]

Yeah but doesn't solve the issue for me. I cannot suspend too. I have to use "echo mem > /sys/power/state"

[vnandak]

I updated today with equo- still the issue persists..

what would be the issue that does not allow KDE to sleep but allows gnome to sleep peacefully

[vnandak]

Finally it got rectified after I updated the kernel to 2.6.34, and updated the nvidia driver to 195.* series. It also rectified one earlier problem of appearing monitor bands while resuming from sleep.

Thanks once again!

[mktyap]

Hi,
I have a unique issue. In KDE I cannot go to sleep/hibernate. It only invokes the screensaver and locks up the screen. Even if I disable the screensaver the same screensaver appears again during sleep. When in gnome, I can go to sleep without any problem. I tried all settings in the KDE System settings panel, but to no avail. I can go to sleep using console command of pm-suspend at root/sudo. This I observed only recently.

The systems details are as follows:
Linux DellXPS 2.6.33-sabayon #1 SMP x86_64 Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz Gen GNU/Linux

KDE 4.4.3, gnome 2.28.2, the system is update as of 29/5/2010.

Since the last 2 updates my system cannot hibernate again, locking up on screensaver when resumed. There were several fixes such as:
viewtopic.php?f=5&t=19424&p=117645&hilit=hibernate#p117645 and
http://gentoo-portage.com/kde-base/powe ... eLog#ptabs
but the problem seem to be recurring at updates. I have the LMZ module kernel of 2.6.34-sabayon.
Are updates consistent in this? Does the Error 2 message on boot up:" Failed to launch user program /usr/local/sbin/tuxonice_fbsplash" something to do with this?
EDIT: A really long wait (up to 5 minutes!) is needed and the have to wiggle the mouse to bring up the screen (solved?)

[mktyap]

Recent updates on media-plugins seem to have quickened hibernated resuming:
gst-plugins-dvb, bad, faac, faad, musepack, neon, and resindvd. Wonder which solved the problem?

[Fitzcarraldo]

I have the LMZ module kernel of 2.6.34-sabayon.

I also have the LMZA-compressed kernel, but that does not affect hibernation.

Does the Error 2 message on boot up:" Failed to launch user program /usr/local/sbin/tuxonice_fbsplash" something to do with this?

I don't think so, as the program is just a user interface for TuxOnIce, and is not essential for hibernation or waking. If you look for the /usr/local/sbin/tuxonice_fbsplash file you'll find it isn't there. This is because the Entropy package sys-apps/tuxonice-userui was built with the fbsplash USE flag switched off:

Code: Select all

# eix tuxonice-userui
[I] sys-apps/tuxonice-userui
     Available versions:  1.0 {fbsplash}
     Installed versions:  1.0(20:08:56 30/03/10)(-fbsplash)
     Homepage:            http://www.tuxonice.net
     Description:         User Interface for TuxOnIce

Looking at the kernel config for the Sabayon 2.6.36 kernel, I see that it has been configured to look for /usr/local/sbin/tuxonice_fbsplash, which is why you see that error message. But you can change the kernel config to look for /sbin/tuxoniceui_text instead, which does exist if tuxonice-userui was built with the fbsplash USE flag switched off, and then rebuild the kernel.

Hibernation did not work for me with the stock 2.6.36-sabayon kernel, as TuxOnIce was not compressing the RAM image, and my swap partition -- which is slightly bigger than my RAM -- was not big enough to hold the uncompressed RAM image. The stock 2.6.36-sabayon kernel config w.r.t. LZO compression is as follows:

Code: Select all

$ cat /usr/src/linux/.config | grep LZO
CONFIG_HAVE_KERNEL_LZO=y
# CONFIG_KERNEL_LZO is not set <----- Kernel Compression Mode was selected to be LZMA rather than LZO
CONFIG_RD_LZO=y
CONFIG_JFFS2_LZO=y
# CONFIG_JFFS2_CMODE_FAVOURLZO is not set
CONFIG_UBIFS_FS_LZO=y
CONFIG_SQUASHFS_LZO=y
CONFIG_CRYPTO_LZO=m
CONFIG_LZO_COMPRESS=m
CONFIG_LZO_DECOMPRESS=y
CONFIG_DECOMPRESS_LZO=y

I had a look at the Gentoo Wiki article on TuxOnIce and rebuilt the kernel to have the following:

Code: Select all

$ cat /usr/src/linux/.config | grep LZO
CONFIG_HAVE_KERNEL_LZO=y
# CONFIG_KERNEL_LZO is not set  <---- I left Kernel Compression Mode as LZMA rather than LZO
CONFIG_RD_LZO=y
CONFIG_JFFS2_LZO=y
# CONFIG_JFFS2_CMODE_FAVOURLZO is not set
CONFIG_UBIFS_FS_LZO=y
CONFIG_SQUASHFS_LZO=y
CONFIG_CRYPTO_LZO=y
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_DECOMPRESS_LZO=y

I also changed the default resume partition to point explicitly to my swap partition:

Code: Select all

[*] Hibernation (aka 'suspend to disk')
  (/dev/sda5) Default resume partition

and I changed the default userui program location from /usr/local/sbin/tuxonice_fbsplash to /sbin/tuxoniceui_text:

Code: Select all

<*>   Userspace User Interface support
    (/sbin/tuxoniceui_text) Default userui program location

As shown in the above excerpt from /usr/src/linux/.config, I also changed cryptographic option LZO compression algorithm from a module to in-kernel:

Code: Select all

Cryptographic API  --->
  <*>   LZO compression algorithm

Now hibernation works (although I get an error message that TuxOnIce cannot find /sbin/tuxoniceui_text, which is definitely there). Also, the LZO-compressed RAM image is significantly smaller than my swap partition (see my Gentoo Forums post Size of swap required for hibernation for details). This shows that recommendations to make the swap size larger than the RAM size are unnecessary.

EDIT (Wed Dec 29 18:47:39 GMT 2010): Just found Gentoo Bugzilla Bug Report No. 291925 which seems to be the reason why tuxoniceui_text or tuxonice_fbsplash are not detected even if present. I've modified the Bash script in that bug report for Sabayon x86_64, and it works on my laptop:

Code: Select all

#!/bin/bash
#
# Quick shell script to automatically patch the genkernel-produced initramfs
# file in order to hibernate/resume using /sbin/tuxoniceui_text (or
# /sbin/tuxoniceui_fbsplash) in this initrd image
#
if [ $# -ne 1 ]; then
  echo "Usage: $0 initramfs-genkernel-x86_64-2.x.xx-sabayon[-rx]"
  exit 1
fi
echo "\"${1}\""
if [[ "${1}" =~ initramfs-genkernel-x86_64-2\.[0-9]+\.[0-9]+-sabayon.* ]]; then
  echo -n
else
  echo "Usage: $0 initramfs-genkernel-x86_64-2.x.xx-sabayon[-rx]"
  exit 2
fi
#
cd ~
if [ ! -d ./tmp ]; then
  echo "${0}: Directory ~/tmp does not exist -- exiting..."
  exit -1
fi
#
cd ./tmp
if [ -d ./tmp ]; then
  echo "${0}: Directory ~/tmp/tmp exists -- exiting..."
  exit -2
fi
#
gzip -dc /boot/$1 > ./${1}.cpio
#
mkdir ./tmp
cd ./tmp
cpio -idm --quiet -H newc < ../${1}.cpio
#
cp -ip /sbin/tuxoniceui_* ./sbin/
ln -s default ./etc/splash/sabayon
#
find . | cpio --quiet --dereference -o -H newc > ../${1}.cpio.new
cd ..
gzip -9 ./${1}.cpio.new
#
mv -i /boot/${1} /boot/${1}.orig
mv -i ./${1}.cpio.new.gz /boot/${1}
rm -i ./${1}.cpio
rm -fr ./tmp
#
exit 0

To run it, you need to:

Code: Select all

# cd /boot
# mv /home/fitzcarraldo/tuxoniceui_initramfs_modify.sh /boot/tuxoniceui_initramfs_modify.sh
# chmod +x tuxoniceui_initramfs_modify.sh
# mkdir /root/tmp/
# ./tuxoniceui_initramfs_modify.sh initramfs-genkernel-x86_64-2.6.36-sabayon

The original /boot/initramfs-genkernel-x86_64-2.6.36-sabayon will be renamed as /boot/initramfs-genkernel-x86_64-2.6.36-sabayon.orig so you can revert to it if you want.

The only downside is that you'll lose the Sabayon bootsplash background for part of the boot, but it doesn't make much difference. Actually, /sbin/tuxoniceui_text just puts up a text progress bar and is nothing special. I assume tuxonice_fbsplash is a bit more attractive but essentially the same thing. So it's hardly worth bothering with this, really.