Version: (using KDE 4.3.0) OS: Linux Installed from: Ubuntu Packages https://bugs.launchpad.net/ubuntu/+bug/410466 I am unable to logout/reboot/shutdown my machine from KDE. I get the logout options, and I can confirm the action and then nothing happens. I stay logged in until I reboot/shutdown or restart kdm via the terminal. Linux eniac 2.6.31-5-generic #24-Ubuntu SMP Sat Aug 1 12:48:18 UTC 2009 i686 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu karmic (development branch) Release: 9.10 Codename: karmic kubuntu-desktop: Installed: 1.137 Candidate: 1.137 Version table: *** 1.137 0 500 http://archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status kwin: Installed: 4:4.3.0-0ubuntu3 Candidate: 4:4.3.0-0ubuntu3 Version table: *** 4:4.3.0-0ubuntu3 0 500 http://archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status kdm: Installed: 4:4.3.0-0ubuntu3 Candidate: 4:4.3.0-0ubuntu3 Version table: *** 4:4.3.0-0ubuntu3 0 500 http://archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status
Confirming this on Kubuntu Jaunty with KDE 4.3 installed from PPA. The first attempt to logout gets the confirm dialog; subsequent attempts do not get the confirm dialog. There appears to be no way to troubleshoot this bug. Shutting down from the command line works normally. Attempting a shutdown with OpenOffice open with an unsaved file prompted me to save the file, whereupon it saved the file and closed OpenOffice, but the machine did not shutdown, nor did Firefox (which was also open) close.
I can confirm that bug, too. I have installed KDE 4.3 from PPA parallel to Gnome at my ubuntu system. At the login screen I set KDE to be the default session to be started. Neither logout nor shutdown/reboot works for me as described by Wesley and Greg. A first attempt brings up the confirm dialog, further tries don't. I manually do shutdown for now by 'sudo shutdown -h now' from the command line. Kernel: 2.6.28-14-generic If further information about my system are required, i would like to provide them, but how? By filling in a new bug report?
*** This bug has been marked as a duplicate of bug 201569 ***