This fix was released in Feisty
** Changed in: kde-guidance (Ubuntu)
Status: Fix Committed => Fix Released
--
guidance-power-manager.py crashes on Transmeta Crusoe
https://launchpad.net/bugs/70677
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
This patch
** Attachment added: "fix crash when cur_freq is not there"
http://librarian.launchpad.net/4976206/powermanage-fix-cpufreq-crash.diff
--
guidance-power-manager.py crashes on Transmeta Crusoe
https://launchpad.net/bugs/70677
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.c
Attached patch makes powermanager not crash.
--
guidance-power-manager.py crashes on Transmeta Crusoe
https://launchpad.net/bugs/70677
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
> -r 1 root root 4096 2006-11-06 19:09 cpuinfo_cur_freq
This one is I think equivalent, but we cannot read it as normal user. I'm
afraid
that means that we cannot display the current CPU frequency.
I've added a check now, so it doesn't crash. As soon as it's fixed upstream
(i.e. the ne
** Attachment added: "Traceback from guidance-power-manager.py"
http://librarian.launchpad.net/4974679/guidance-power-manager-traceback.log
--
guidance-power-manager.py crashes on Transmeta Crusoe
https://launchpad.net/bugs/70677
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
ht
