Registered Member
|
The digital plasma clock seems to take ages to update after resuming from suspend. By "ages" I mean something like roughly 20 seconds. That's a long time, though, in the computer world to resume and stare at your clock (displaying the time it had just before the suspend) waiting for it to tell you the correct time. Is it supposed to do this? Are there better clock alternatives?
|
Registered Member
|
The problem is that there was no notification from the system that the computer had resumed. All plasma clocks through 4.5 have this problem, since they all use the same source to get their information. I think this has been fixed for 4.6, though.
Man is the lowest-cost, 150-pound, nonlinear, all-purpose computer system which can be mass-produced by unskilled labor.
-NASA in 1965 |
Registered Member
|
Thanks for the explanation. I hope it's fixed in 4.6.
|
Administrator
|
This notification will only work if the newer UPower backend is active to handle power management. If your distro uses HAL, you will not get that kind of notification (and as such the clock will not update).
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
I notice that Ubuntu 10.10 is using Upower. Anyone know why Kubuntu isn't?
|
Administrator
|
KDE 4.5 does not have upower support at this time. The current aim of Solid in KDE 4.6 is to have support for UPower, UDisks and UDev in place so a HAL-less system can be used, however it is not sure if this will be reached.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I'm now running KDE 4.6 beta 1 and I have upower and udisks installed but the solid configuration GUI won't let me change the backend to upower. All I see if HAL. Is there any way of manually adjusting it?
|
Administrator
|
Note that multiple Solid backends can run simultaneously. Check the output of "solid-hardware list" to see if they are enabled.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
It looks like both are enabled. I set the InitialPreference in powerdevilhalbackend.desktop higher than in powerdevilupowerbackend.desktop, so upower should be preferred. But it's still odd that the Information Sources GUI doesn't show both of them.
|
Administrator
|
In this case, the clock should update if UPower is functioning, however PowerDevil may be responsible for the signal, and it may not be able to run multiple backends at once (as it has it's own).
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Administrator
|
With regards to upower, bear in mind that there's a bug (fixed post-beta 2, unfortunately) that may prevent powerdevil from picking up the upower backend at startup.
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
Thanks for the info. I'm dropping back to HAL until all issues are resolved.
|
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]