** Description changed:

  While updating to Intrepid beta 6, Policykit decided to disregard my
  GNOME default to always use the powersave CPU governor and went
  Performance instead. It took me a decent numbers of step to get near to
  solving this, but as I had foreseen my laptop overheated and died in the
  middle of the update.
  
  While I raced against the overheating CPU, error messages were mainly
  unhelpful in troubleshooting the issue.
  
  My first attempt was to use the cpu frequency selector panel tool. It
  simply failed silently. Then I tried again, and again, and then some
  more. Then I whipped up the console.
  
  "apropos cpu" showed up the commandline cpufreq-selector, which I tried.
  
  > badp:~$ cpufreq-selector -g powersave
  > Error calling SetGovernor: Failed to execute program 
/usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
  
  This error message would made a worthy entry to TheDailyWTF.com's
  Error'ed series, but nevermind that.
  
  I tried to manually set the frequency using the other option:
  
- badp:~$ cpufreq-selector 798
- Failed to acquire org.gnome.CPUFreqSelector: Connection ":1.1673" is not 
allowed to own the service "org.gnome.CPUFreqSelector" due to security policies 
in the configuration file
+ > badp:~$ cpufreq-selector 798
+ > Failed to acquire org.gnome.CPUFreqSelector: Connection ":1.1673" is not 
allowed to own the service "org.gnome.CPUFreqSelector" due to security policies 
in the configuration file
  
  I rush to the PolicyKit graphical interface, reach
  org.gnome.CPUFreqSelector and try to allow any user to change it.
  Clicking on the "Modify..." button, though, is a no-op. Nothing happens.
  Not an error message, nothing. Again, I get back to my shell, and after
  some apropos'ing I try:
  
- badp:~$ polkit-action --set-defaults-any org.gnome.cpufreqselector yes
- polkit-set-default-helper: needs to be setuid polkituser
- Error: code=8: NotAuthorizedToModifyDefaults: uid 1000 is not authorized to 
modify defaults for implicit authorization for action org.gnome.cpufreqselector 
(requires org.freedesktop.policykit.modify-defaults)
+ > badp:~$ polkit-action --set-defaults-any org.gnome.cpufreqselector yes
+ > polkit-set-default-helper: needs to be setuid polkituser
+ > Error: code=8: NotAuthorizedToModifyDefaults: uid 1000 is not authorized to 
modify defaults for implicit authorization for action org.gnome.cpufreqselector 
(requires org.freedesktop.policykit.modify-defaults)
  
- badp:~$ sudo polkit-action --set-defaults-any 
org.freedesktop.policykit.modify-defaults auth_self
- polkit-set-default-helper: needs to be setuid polkituser
- Error: code=8: NotAuthorizedToModifyDefaults: uid 0 is not authorized to 
modify defaults for implicit authorization for action 
org.freedesktop.policykit.modify-defaults (requires 
org.freedesktop.policykit.modify-defaults)
+ > badp:~$ sudo polkit-action --set-defaults-any 
org.freedesktop.policykit.modify-defaults auth_self
+ > polkit-set-default-helper: needs to be setuid polkituser
+ > Error: code=8: NotAuthorizedToModifyDefaults: uid 0 is not authorized to 
modify defaults for implicit authorization for action 
org.freedesktop.policykit.modify-defaults (requires 
org.freedesktop.policykit.modify-defaults)
  
  While I try to decode the "needs to be setuid polkituser" line, the
  computer dies for overheat. Right in the middle of a distro update.
  
  I can now choose between the 2.7 kernel with the blinking caps lock led
  of death, the old 2.5 kernels which shows helpful information about the
  mount command syntax but fails to boot, and Windows XP which I'm using
  to file this bug. I guess the only solution now is a full reinstall.
+ 
+ EDIT: I would like to add that "powersave" was set as the default cpu
+ governor by using the GNOME Configuration Editor tool. Why did PolicyKit
+ decide all of a sudden that all of a member of the admin group, root AND
+ the default settings were wrong?

-- 
[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