Well, I guess it is a little more complicated than that, but I was helping troubleshoot KMS dpms hangs from intel bug reports with some people on IRC and felt it should probably be brought up here because removing it did in fact fix their problem. I noticed debian carries a patch in acpi-support that would probably be much more correct than completely removing the dcop screen locking from it entirely. I'm surprised this script gets used though, perhaps its related them being on jaunty.
http://git.debian.org/?p=pkg-acpi/acpi-support.git;a=blob;f=debian/patches/screenblank.diff;h=883efd569f5d56a32c1b5bfd45fd051635c892c2;hb=HEAD 6 elif [ `pidof dcopserver` ]; then 7 - dcop kdesktop KScreensaverIface lock 8 + if [ x$LOCK_SCREEN = xtrue ]; then 9 + avail_sessions=`dcop --all-users --list-sessions | grep '.DCOP.*__0'` 10 + # send the lock command to all sessions 11 + for session in $avail_sessions; do 12 + # /dev/null because dcop warns if it can't connect to X (this is normal!) 13 + dcop --session "$session" --all-users kdesktop KScreensaverIface lock > /dev/null 2>&1 14 + done 15 + fi 16 fi 17 18 xset dpms force off -- screenblank script unconditionally forces screen lock in KDE which causes crashing upon lid close under KMS. https://bugs.launchpad.net/bugs/390917 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
