Power management works fine when an user is logged in. I can set the desired power profile characteristics with "Power Management" in "System Settings".

The problem is when no user is logged in, i.e. in the KDE login screen (KDM). I cannot find how to set power characteristics for that screen. Especially, I'm interested in suspending to RAM the laptop when closing the lid.

I've tried to set this feature as root (kdesudo systemsettings), but it seems that the login screen doesn't obbey the root settings.

Does anybody know if this can be done and how?

I would be interested in that as well, or perhaps pre-start the network using the system settings (NetworkManager backend).

Afaik this is not yet possible as KDM is just a greeter and does not load the rest of KDE until the login is complete...

cyberwizzard is correct here, KDE cannot do anything as it runs as a user, and no users are logged in so it cannot apply any settings. KDM could perhaps integrate some PowerDevil options though.

So it is not possible... Ummm I think it shouldn't be very difficult to use the root power settings for KDM, after all KDM is running as root.

I think this could be an interesting feature to be added, because I use to logout of my account before closing the laptop lid and I realized (the hard way) that then the laptop didn't suspend to RAM.

About the cyberwizzard question on pre-starting the network, I solved that by inserting the following in /etc/network/interfaces:

Code: Select all

auto lo wlan0
iface lo inet loopback

iface wlan0 inet manual
        wpa-driver wext
        wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf

iface default inet dhcp

iface my_wifi inet dhcp


and the following in /etc/wpa_supplicant/wpa_supplicant.conf:

Code: Select all

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev

network={
        ssid="Put your AP name here"
        psk="Put your AP passphrase here"
        key_mgmt=WPA-PSK
        pairwise=CCMP
        group=CCMP
        proto=WPA2
        id_str="my_wifi"
}

network={
        key_mgmt=NONE
}


You'll have to tweak the setting in the network definition above, as they are for my WPA2 AP with PSK.

Also, I had to remove NetworkManager at all, because it has a bug in old versions (I don't know if it is already solved). NetworkManager shouldn't manage the interfaces marked as auto in /etc/network/interfaces (lo and wlan0 in my case), but it does, and it starts a second wpa_supplicant process for the wlan0 interface. Of couse, two wpa_supplicant processes interfere between them and cannot connect to the AP.