It is of course fair to say that my overheating system isn't a software
bug.

However:

1. During the setup, the CPU governor was changed for whatever reason.
It was not changed to my Powersafe default, nor to Ubuntu's OnDemand
default, but to Performance. I concede I don't really know what did this
or why, nor it really is a big problem in itself. I could've changed it
back -- wasn't it for PolicyKit.

2. Attempts to fix this situtation were met with no or meaningless error
messages, some coming for Policykit itself. I hope you will concede that
"uid 0 is not authorized to modify defaults for implicit authorization
for action org.freedesktop.policykit.modify-defaults (requires
org.freedesktop.policykit.modify-defaults)" is a bit... strange error
message.

3. PolicyKit denied Root to edit settings. In
https://launchpad.net/ubuntu/+source/policykit/0.7-2ubuntu4 it is noted
that Root /is/ supposed to have full access to Policykit since Hardy.
Change logs for following versions do not highlight changes in this
behavior.

I do believe PolicyKit did not behave as designed in this situation. I
also believe that many applications need to be changed to recognise
failures coming from PolicyKit policies. Feel free to extend this bug to
the other involved packages, I could not find any.

-- 
[Intrepid] Policykit denies changes to cpu frequency and ultimately leads to 
distro update failure
https://bugs.launchpad.net/bugs/271837
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to