It's not launching, and can't change CPU frequency on the terminal

Bug #1959136 reported by Jonas Gamao
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cpufreqd (Ubuntu)
Confirmed
Undecided
Unassigned
cpufrequtils (Ubuntu)
Confirmed
Undecided
Unassigned
indicator-cpufreq (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

 indicator-cpufreq
/usr/lib/python3/dist-packages/indicator_cpufreq/indicator.py:20: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk
/usr/lib/python3/dist-packages/indicator_cpufreq/indicator.py:21: PyGIWarning: AppIndicator3 was imported without specifying a version first. Use gi.require_version('AppIndicator3', '0.1') before import to ensure that the right version gets loaded.
  from gi.repository import AppIndicator3 as appindicator
Traceback (most recent call last):
  File "/usr/bin/indicator-cpufreq", line 79, in <module>
    ind = MyIndicator(options.show_frequency)
  File "/usr/lib/python3/dist-packages/indicator_cpufreq/indicator.py", line 99, in __init__
    self.update_ui()
  File "/usr/lib/python3/dist-packages/indicator_cpufreq/indicator.py", line 110, in update_ui
    fmin, fmax, governor = cpufreq.get_policy(self.cpus[0])
  File "/usr/lib/python3/dist-packages/indicator_cpufreq/cpufreq.py", line 143, in get_policy
    policy = (p.contents.min, p.contents.max, p.contents.governor.decode())
ValueError: NULL pointer access

$ sudo cpufreq-set -g ondemand
[sudo] password for yamiyuki:
Error setting new values. Common errors:
- Do you have proper administration rights? (super-user?)
- Is the governor you requested available and modprobed?
- Trying to set an invalid policy?
- Trying to set a specific frequency, but userspace governor is not available,
   for example because of hardware which cannot be set to a specific frequency
   or because the userspace governor isn't loaded?

$ sudo cpufreq-set -g performance
Error setting new values. Common errors:
- Do you have proper administration rights? (super-user?)
- Is the governor you requested available and modprobed?
- Trying to set an invalid policy?
- Trying to set a specific frequency, but userspace governor is not available,
   for example because of hardware which cannot be set to a specific frequency
   or because the userspace governor isn't loaded?

$ sudo cpufreqd-get
No cpufreqd socket found

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: indicator-cpufreq 0.2.2-0ubuntu3
Uname: Linux 5.15.11-76051511-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Jan 26 14:58:20 2022
InstallationDate: Installed on 2022-01-14 (12 days ago)
InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
SourcePackage: indicator-cpufreq
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jonas Gamao (yamiyukisenpai) wrote :
Revision history for this message
Jonas Gamao (yamiyukisenpai) wrote :

$ systemctl status cpufreqd
× cpufreqd.service - LSB: start and stop cpufreqd
     Loaded: loaded (/etc/init.d/cpufreqd; generated)
     Active: failed (Result: exit-code) since Wed 2022-01-26 16:02:47 EST; 4min 1s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 1401 ExecStart=/etc/init.d/cpufreqd start (code=exited, status=1/FAILURE)
        CPU: 7ms

Jan 26 16:02:47 Y4M1-II systemd[1]: Starting LSB: start and stop cpufreqd...
Jan 26 16:02:47 Y4M1-II cpufreqd[1401]: * Starting CPU Frequency daemon cpufreqd
Jan 26 16:02:47 Y4M1-II cpufreqd[1401]: ...fail!
Jan 26 16:02:47 Y4M1-II systemd[1]: cpufreqd.service: Control process exited, code=exited, status=1/FAILURE
Jan 26 16:02:47 Y4M1-II systemd[1]: cpufreqd.service: Failed with result 'exit-code'.
Jan 26 16:02:47 Y4M1-II systemd[1]: Failed to start LSB: start and stop cpufreqd.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cpufreqd (Ubuntu):
status: New → Confirmed
Changed in cpufrequtils (Ubuntu):
status: New → Confirmed
Changed in indicator-cpufreq (Ubuntu):
status: New → Confirmed
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.