indicator-cpufreq crashed with dbus.exceptions.DBusException in call_blocking(): com.hostname.DeviceDriver.PermissionDeniedByPolicy: com.hostname.indicatorcpufreqselector.setfrequencyscaling

Bug #1122239 reported by Daniel Winzen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-cpufreq (Ubuntu)
New
Undecided
Unassigned

Bug Description

This happened after creating an account with standard rights and clicking on the cpufreq-indicator in unity and trying to set another frequency. I didn't enter my password, so cpufreq couldn't change the frequency and crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: indicator-cpufreq 0.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6
Uname: Linux 3.8.0-5-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Mon Feb 11 18:22:14 2013
ExecutablePath: /usr/bin/indicator-cpufreq
InstallationDate: Installed on 2012-04-03 (313 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120403)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/indicator-cpufreq
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/indicator-cpufreq']
SourcePackage: indicator-cpufreq
Title: indicator-cpufreq crashed with dbus.exceptions.DBusException in call_blocking(): com.hostname.DeviceDriver.PermissionDeniedByPolicy: com.hostname.indicatorcpufreqselector.setfrequencyscaling
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: nopasswdlogin

Revision history for this message
Daniel Winzen (q-d-deactivatedaccount) wrote :
information type: Private → Public
Revision history for this message
Robert Roth (evfool) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #957430, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.