You are not logged in.
Hello,
i've just upgraded to KDEmod 4.2.3-1 and the battery manager of KDE stopped working. It shows the battery percentage and the remaining time. But I can't control the Screen Brightness or set the Power Profile anymore. Furthermore the Sleep and Hibernate buttons lost their function. Similar in the KDE Launcher: Suspend to RAM and Suspend to Disk doesn't work anymore (manual pm-hibernate and pm-suspend works).
Last edited by oneway (2009-05-12 12:41:17)
Offline
That looks more like an hal / policykit error....
Maybe you take a look at the "hal"wiki
Offline
I also have this problem...
Bug report:
http://kdemod.ath.cx/bugs/showreport.php?bugid=280
Last edited by muczyjoe (2009-05-08 13:39:17)
Offline
I have the exact same problem since 4.2.3. I checked my policies and acpi-event handling but did not notice anything unusual or settings referring to kde that could have changed with the update.
Offline
Same problem here. All profiles have no name, though the names appear [*] when exported to a file.
Pax Christi
+ Pax Domini +
Offline
Has anyone already a solution?
Last edited by oneway (2009-05-09 06:20:08)
Offline
After wasting one morning try to understand the deep insanity of dbus/HAL's policy framework I switched back to my ubuntu partition (after adding something hopefully useful to the bug report). Power management works in ubuntu and as a laptop user that matters a lot to me.
I notice that the /media/disk/etc/dbus-1/system.d/hal.conf I have differs from the one described at http://wiki.archlinux.org/index.php/HAL so I am thinking this is a work in progress. Hope someone is watching.
Offline
Same problem here. But only when I logged out and in again. First login seems to work, but after that powerdevil is messed up. I can't select any profile, nur sleep or hibernate.
It is working though when I log into a real console and restart KDM. Then I can use powerdevil until the next logout / login.
digiKam developer - www.digikam.org
Offline
hmmm... what's a "real" console? and do you start KDM or KDE (say with 'startkde') ?
All info for bug triage.
Offline
A "real" console for me is a login shell, not started from within X :-)
I normally login via KDM, and it always works the first time. But when I logout (to the KDM screen) and login again (the user account doesn't matter), powerdevil is not working anymore, it looks like something is kept in memory and blocks pwerdevil from working. When I restart KDM from a "real" :-) console, it works.
Maybe some HAL stuff gets reinitialized then?
digiKam developer - www.digikam.org
Offline
i just tryed a fresh archlinux i686 and x86_64 installation...kdemod powerdevil is broken only with the i686 version...
Offline
Ok I figured out when it is working for me exactly:
I copied the new kdmrc.pacnew file from last update over my kdmrc file. I had turned on auto-login before, but now it was disabled again.
So I had to login manually again... and boom: powerdevil is not working.
I logged out, restarted kdm, loged in again: powerdevil is broken.
I activated automatic login for my user account again: powerdevil is working.
When I logout, login again (now I need to provide my password): powerdevil is broken.
Logout, kdm restart, automatic login is active again: powerdevil is happy and running.
So to make it short :-)
When autologin is turned on, powedevil works, but as long as I need to login with my password, it is broken.
I don't understand this.
digiKam developer - www.digikam.org
Offline
I can confirm the behaviour TheGrudge described.
I've enabled autologin and now it works...
Offline
Yes, this is weird... I thought it might by HAL, but restarting HAL still doesn't work. So it is really the autologin that is somehow solving this issue.
digiKam developer - www.digikam.org
Offline
..i confirm aswell the autologin workaround...lol
Offline
i will... also... confirm autologin workaround :-)
for newb wonding how to enable autologin... it's in kde system settings/advanced :-/
Offline
There is always kde in [extra] to fall back to.
I need real, proper pen and paper for this.
Offline
The last dbus update seems to have fixed this, but what this has to do with the autologin... hmm I don't understand...
digiKam developer - www.digikam.org
Offline
Did you guys see the resolution on the kdemod forums
The workings of console kit are still a bit mysterious to me, but the console kit session that was causing problems was getting started by kdm, but with autologin it wasn't getting started.
Offline
Does anyone running kde from extra have the connector module there in pam?
I need real, proper pen and paper for this.
Offline
The problem should be fixed with today's kdemod update.
Last edited by ChemBro (2009-05-11 20:05:04)
Offline
Does anyone running kde from extra have the connector module there in pam?
Don't see it there...
[val@tux ~]$ cat /etc/pam.d/kde
#%PAM-1.0
auth required pam_unix.so
auth required pam_nologin.so
account required pam_unix.so
password required pam_unix.so
session required pam_unix.so
session required pam_limits.so
Offline
Ahh yes, confirmed in the bug report - it's not supposed to be there.
Glad the solution came fast.
I need real, proper pen and paper for this.
Offline
Ahh yes, confirmed in the bug report - it's not supposed to be there.
Glad the solution came fast.
I actually had kdemod installed before and followed your advice to change to KDE from extra, if I only had waited a little more... :D
Offline