On Debian (wheezy) I installed KDE 4.8.4 and Plasma.
Everything works as expected.

I created a live DVD where I notice something peculiar: the Kickoff launcher missed the system section in the Leave menu. When I add the Lock/Logout widget there is no shut down button either.

So, in the live environment I'm unable to shut down, restart, hibernate or sleep the system through the usual graphical means and I have to shut down by typing "sudo shutdown -h -P now" in the terminal.

After installation, the icons are there and I can shut down normally.

This only seems to affect the 32-bit live version, 64-bit has the restart and shut down icons while running live.

This is what I've tried/checked:
- Delete all folders in the live user directory.
- Check Session Management: all looks well.
- I have tried adding the user to the same groups as the user from a working system (not live).
- Installing in VirtualBox, verifying that everything is working and create a live DVD from that.
- Running Live in VirtualBox does show below picture, running live from USB however, does show an extra Sleep button (!)
- I have compared (64 vs 32-bits) the config files in the following directories, without finding differences:

• /home/<user>
• /usr/lib/kde4
• /usr/share/kde4
• /usr/share/applications/kde4
• /etc/kde4
• /etc/skel

- I have compared running processes and found these not running in live 32-bit, but were running on the others:

• khugepaged
• kio_desktop
• kio_file
• kio_trash

Could these missing processes have to do with this issue (or a symptom of something entirely else)?

To see what I'm talking about:

Is KDM used on both the x86 and x86-64 images?

KDM is used in both systems and are identical: there is no difference in installed packages.
This only happens when running the live DVD of the 32-bit version.
After installation the buttons are available in both Kickoff launcher and the Lock/Logout widget.

If you are interested, you can download the iso here:
http://www.schoelje.nl/lmdekde/lmdekde3 ... 201208.iso

As a workaround, I've added a shut down button in the Favorites section but I'm still searching for a better solution.

I suspect this is because KSMServer believes it is not possible - which means it cannot contact KDM. Unfortunately a little hard to test, and it only occurring under 32-bit is very odd....

Can you check the output of this?

Code: Select all

 qdbus org.kde.ksmserver /KSMServer canShutdown

qdbus org.kde.ksmserver /KSMServer canShutdown
false

Okay, this confirms that KSMServer definitely believes shutdown is not possible.
Is UPower running on this 32-bit image?

ps aux | grep UPower
mint 4388 0.0 0.0 3524 804 pts/2 S+ 15:53 0:00 grep --color=auto UPower

Oops. Please check for "upowerd" instead.

ps aux | grep upowerd
root 3908 0.0 0.3 26308 3712 ? Sl 07:50 0:00 /usr/lib/upower/upowerd
mint 4394 0.0 0.0 3528 812 pts/2 S+ 07:54 0:00 grep --color=auto upowerd

Is the variable $DM_CONTROL set on your system?
If so, can you check the directories underneath it and confirm your user has permissions to write to both?

On both systems (32 and 64-bits) I get the same values:

# echo $DM_CONTROL
/var/run/xdmctl

# ls -ARl
.:
total 0
drwxr-xr-x 2 root root 60 Aug 10 22:46 dmctl
drwxr-xr-x 2 root root 60 Aug 10 22:46 dmctl-:0

./dmctl:
total 0
srw-rw---- 1 root root 0 Aug 10 22:46 socket

./dmctl-:0:
total 0
srw-rw---- 1 mint root 0 Aug 10 22:46 socket

Is KDM configured appropriately to allow it to shutdown the system in the 32-bit images?
ie. if you logout, can you shutdown properly from there?

Shut down from KDM: no problem.

One last thing: can you check the KDM configuration to make sure it permits all users (or even just the named user) to initiate a shutdown?

It took some time because live-config runs some bash files to change some values in /etc/kde4/kdm/kdmrc wich prevents you to get into the login screen.
After some changes and a new live DVD I changed kdmrc so that the login screen would show and that everybody could shut down.
After startup there were no shut down or restart buttons in Kickoff.
I verified that kdmrc was unchanged and that everybody could shut down.

I'm afraid we hit on a very odd bug...