Hi,

I recently noticed that when I go to the Leave... menu (e.g. right click on desktop > Leave...), the Suspend to RAM option doesn't work. However the Shut Down and Reboot work fine. When I select Suspend to RAM, nothing happens at all. I don't even get anything appearing in /var/log/messages.

However, when I enter "sudo pm-suspend" in the terminal, the computer suspends almost immediately and wakes up fine when I tap the power button on my computer. I guess the Suspend to RAM button may be calling a different command to this, but I dont know what...

Does anyone know what may be the problem, please? This used to work, but now it has suddenly stopped working and I can't figure out why

I don't know if it's related, but I've also noticed that around the same time, all of my custom keyboard shortcuts seemed to stop working as well.

I'm running Fedora 16 and have applied all available updates and rebooted, but no luck.

Thanks in advance for any help anyone can give me!
Dave

Do you have any applications running which could be suppressing suspend?

Thanks for your reply. I have tried this from a fresh boot and I don't think I have any applications auto-running that would prevent suspend.

If I had an application that prevents me suspending, would 'sudo pm-suspend' also be prevented from suspending, or does it work differently?

It operates differently.

Can you please try running:

Code: Select all

qdbus org.freedesktop.PowerManagement /org/kde/Solid/PowerManagement suspendToRam

$ qdbus org.freedesktop.PowerManagement /org/kde/Solid/PowerManagement
Service 'org.freedesktop.PowerManagement' does not exist.

I think it's clear something has really messed up. But I've no idea how. I haven't removed packages or services or anything.

Going into settings > power management yields a big red cross and: Power Management configuration module could not be loaded. The Power Management Service appears not to be running. This can be solved by starting or scheduling it inside "Startup and Shutdown"

Going into Startup and Shutdown > Service Manager yields an error pop-up: "Unable to contact KDED"

I remember setting these things up a couple of months ago just fine. I wonder what's happened since then..?

More weirdness:

It seems that if I log out, and then log in again, all of the above work perfectly; including Suspend to RAM from the Leave... menu. Also, the command-line you gave me suspends the computer as it should.

But when I restart the computer, all is back to not working again (unless I log out and log in again). Something I've noticed since these troubles as well is different icons in the system tray. There always used to be monochrome icons in the system tray for sound mixer, bluetooth, etc. I remember though, that after an update & reboot a couple of months ago, the icons suddenly became different and coloured; the bluetooth icon was now a blue oval, the sound mixer was grey with green sound indicators, etc. I didn't think too much of this at the time, just assuming it was a new redesign. But when I log out and log in again, I get the monochrome icons back.

Going into system tray settings, I can see that the names for the system tray items are different depending on whether they are monochrome or coloured:

monochrome:
Bluetooth
Desktop Search File Indexing
Printer Applet
Volume Control

coloured:
bluedevil-monolithic
kmix
nepomukcontroller
printer-applet

The rest of the items, e.g. network management and device notifier do not ever change from being monochrome and do not change name along with the other items

Any ideas what could be causing this? I think the update might have been the one that gave me KDE 4.8, but I'm not sure...

Okay, that definitely explains it. "kded4" or "KDE Daemon" is a core process responsible for a large number of functions in a KDE session. One of these is running the Power Manager. In order to Suspend to RAM or Disk, Plasma must be able to contact the Power Manager to request this. If it is not available, then it cannot Suspend to RAM or Disk.

KDE Daemon also hosts a service known as the StatusNotifierWatcher, which is responsible for connecting applications using the Status Notifier Specification with the application(s) that display the system tray icons provided through this specification. Under KDE this is the Plasma Workspace. This is why you see Coloured and Monochrome icons. The Coloured icons are provided using the legacy system tray specification, while the Monochrome icons are provided via the new Status Notifier Specification (which also allows applications to provide a nice name for themselves).

Please ensure all system updates are installed properly.
After that, please check your ~/.xsession-errors file for crash reports from "kded4".

Did your distribution originally intend to ship with KDE 4.8, or was this installed from an alternative repository.

bcooksley wrote:Okay, that definitely explains it. "kded4" or "KDE Daemon" is a core process responsible for a large number of functions in a KDE session. One of these is running the Power Manager. In order to Suspend to RAM or Disk, Plasma must be able to contact the Power Manager to request this. If it is not available, then it cannot Suspend to RAM or Disk.

KDE Daemon also hosts a service known as the StatusNotifierWatcher, which is responsible for connecting applications using the Status Notifier Specification with the application(s) that display the system tray icons provided through this specification. Under KDE this is the Plasma Workspace. This is why you see Coloured and Monochrome icons. The Coloured icons are provided using the legacy system tray specification, while the Monochrome icons are provided via the new Status Notifier Specification (which also allows applications to provide a nice name for themselves).

Please ensure all system updates are installed properly.
After that, please check your ~/.xsession-errors file for crash reports from "kded4".

Did your distribution originally intend to ship with KDE 4.8, or was this installed from an alternative repository.

I cleared .xsession-errors and restarted, but "grep kded4 .xsession-errors" returned nothing. However, this time the computer started up with monochrome icons.

I realised now though, that actually the computer only starts up with coloured icons when I restart after an update. Next time an update is available, I'll try again.

The 4.8 update came from a standard Fedora 16 update

Thanks for the information, this is very unusual behaviour which should not occur at all. (As a fresh login should have the update fully applied at that point, especially as the cache rebuild must have been completed).

I've since been unable to reproduce this problem so I assume the problem no longer exists Thanks very much for your help