indicator-cupufreq crashes with null pointer access error

Bug #797996 reported by eugenio
102
This bug affects 22 people
Affects Status Importance Assigned to Milestone
indicator-cpufreq
Triaged
Undecided
Unassigned

Bug Description

eugenio@eugenio-desktop:~$ indicator-cpufreq
Traceback (most recent call last):
  File "/usr/bin/indicator-cpufreq", line 81, in <module>
    ind = MyIndicator()
  File "/usr/lib/pymodules/python2.7/indicator_cpufreq/indicator.py", line 99, in __init__
    self.update_ui()
  File "/usr/lib/pymodules/python2.7/indicator_cpufreq/indicator.py", line 110, in update_ui
    fmin, fmax, governor = cpufreq.get_policy(FIXME_CPU)
  File "/usr/lib/pymodules/python2.7/indicator_cpufreq/cpufreq.py", line 143, in get_policy
    policy = (p.contents.min, p.contents.max, p.contents.governor)
ValueError: NULL pointer access

Changed in indicator-cpufreq:
status: New → Confirmed
Revision history for this message
Dennis Baudys (thecondordb) wrote :

I can confirm the bug reported by eugenio. Same or very similar symptom here, running Ubuntu 11.10 64-bit with Unity on Samsung R710 notebook (only runs Oneiric with acpi=off boot option btw.) - The indicator just doesn't start but reports an error. Please see below.

condor@ganymed:~$ uname -a
Linux ganymed 3.0.0-13-generic #23~ppa1~loms~oneiric-Ubuntu SMP Mon Nov 21 20:33:55 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

condor@ganymed:~$ sudo apt-cache policy indicator-cpufreq
indicator-cpufreq:
  Installiert: 0.1.4-0ubuntu1~oneiric1
  Kandidat: 0.1.4-0ubuntu1~oneiric1
  Versionstabelle:
 *** 0.1.4-0ubuntu1~oneiric1 0
        500 http://ppa.launchpad.net/artfwo/ppa/ubuntu/ oneiric/main amd64 Packages
        100 /var/lib/dpkg/status

condor@ganymed:~$ indicator-cpufreq

(indicator-cpufreq:3179): Gtk-WARNING **: Im Modulpfad »pixmap« konnte keine Themen-Engine gefunden werden,

(indicator-cpufreq:3179): Gtk-WARNING **: Im Modulpfad »pixmap« konnte keine Themen-Engine gefunden werden,

(indicator-cpufreq:3179): Gtk-WARNING **: Im Modulpfad »pixmap« konnte keine Themen-Engine gefunden werden,

(indicator-cpufreq:3179): Gtk-WARNING **: Im Modulpfad »pixmap« konnte keine Themen-Engine gefunden werden,
Traceback (most recent call last):
  File "/usr/bin/indicator-cpufreq", line 81, in <module>
    ind = MyIndicator()
  File "/usr/lib/python2.7/dist-packages/indicator_cpufreq/indicator.py", line 95, in __init__
    self.update_ui()
  File "/usr/lib/python2.7/dist-packages/indicator_cpufreq/indicator.py", line 106, in update_ui
    fmin, fmax, governor = cpufreq.get_policy(self.cpus[0])
  File "/usr/lib/python2.7/dist-packages/indicator_cpufreq/cpufreq.py", line 143, in get_policy
    policy = (p.contents.min, p.contents.max, p.contents.governor)
ValueError: NULL pointer access

Thanks in advance for looking into this.

Dennis

Revision history for this message
jose (o1485726) wrote :

So, I had this bug too. This happens when you disable "Cool n Quiet" from the BIOS in AMD systems (or if you enable HW thermal control, I'm not sure. I just have one AMD system, so I can't say much about other people...). When you do that, the file /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor will disappear, and the program will (obviously) not be able to find it, so it crashes...
I hope it helps.

Revision history for this message
Artem Popov (artfwo) wrote :

Thanks for the info, Jose!

Changed in indicator-cpufreq:
status: Confirmed → Triaged
Revision history for this message
Dax Solomon Umaming (knightlust) wrote :

The Cool & Quiet setting on my BIOS is set to Auto, but it still crashes.

no longer affects: ubuntu
Revision history for this message
Daniel Kessel (dkessel) wrote :

I have this on a non-AMD system (Intel Atom 330)

Revision history for this message
Carl (n6rl) wrote :

Affects me as well on an Intel Haswell running on Ubuntu 13.10.

Details:

$ ls /sys/devices/system/cpu/cpu0/
cache crash_notes_size microcode subsystem uevent
cpuidle driver node0 thermal_throttle
crash_notes firmware_node power topology

$ uname -a
Linux lapt 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

$ sudo lshw|grep "\-cpu" -A2
     *-cpu
          description: CPU
          product: Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz

Revision history for this message
Taqi Raza (mmtrt) wrote :

same thing here on ubuntu 13.10 x64

mmtrt@xxlolxxRPGxx:~$ indicator-cpufreq

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

mmtrt@xxlolxxRPGxx:~$ ls /sys/devices/system/cpu/cpu0/

cache crash_notes_size microcode subsystem uevent
cpuidle driver node0 thermal_throttle
crash_notes firmware_node power topology

mmtrt@xxlolxxRPGxx:~$ uname -a

Linux xxlolxxRPGxx 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
mmtrt@xxlolxxRPGxx:~$ sudo lshw|grep "\-cpu" -A2
PCI (sysfs)
     *-cpu
          description: CPU
          product: Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz

Revision history for this message
dougtwyman (dltwyman) wrote :

also experiencing this on 13.10 x64
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

uname -a
Linux doug-MS-7821 3.11.0-15-generic #25-Ubuntu SMP Thu Jan 30 17:22:01 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

sudo lshw|grep "\-cpu" -A2

    *-cpu
          description: CPU
          product: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz

Revision history for this message
GregL (greg-lumpkin) wrote :

Getting the following on Dell Dimension 4700 running Ubuntu 13.10:

greg@steelhead:~$ indicator-cpufreq
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
greg@steelhead:~$

Revision history for this message
fdl3 (fdl3) wrote :

Getting the following on Toshiba Satellite L305-S5919 running Ubuntu 14.04 Beta 2:

rcoc@D1B5:~$ indicator-cpufreq
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

rcoc@D1B5:~$ ls /sys/devices/system/cpu/cpu0/
cache crash_notes_size microcode thermal_throttle
cpuidle driver power topology
crash_notes firmware_node subsystem uevent

rcoc@D1B5:~$ uname -a
Linux D1B5 3.13.0-22-generic #44-Ubuntu SMP Wed Apr 2 20:04:41 UTC 2014 i686 i686 i686 GNU/Linux

rcoc@D1B5:~$ sudo lshw|grep "\-cpu" -A2
     *-cpu
          description: CPU
          product: Genuine Intel(R) CPU 585 @ 2.16GHz

System Details
Memory: 1.8 GiB
Processor: Genuine Intel® CPU 585 @ 2.16GHz
Graphics: Mobile Intel® GM45 Express Chipset x86/MMX/SSE2
OS Type: 32-bit
Disk: 147.4 GB

Revision history for this message
vak (khamenya) wrote :

i am experiencinig the same bug in Ubuntu 14.04 (64bit)
CPU: Intel(R) Pentium(R) CPU 2127U @ 1.90GHz

Revision history for this message
Hendrik De Vloed (hendrik-de-vloed) wrote :

Same here,
AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
Ubuntu 14.04.1 LTS 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64

Revision history for this message
Valentin Gilch (outeh) wrote :

I think i've got the same problem :

outeh@outeh-desktop:~$ 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

on this config :

OS: Ubuntu 16.04.3 LTS x86_64
Kernel: 4.13.0-32-generic
Memory: 7977MiB
CPU: AMD Phenom II X6 1045T (6) @ 3ghz (oc)
 WM: Compiz
 DE: Unity

Revision history for this message
AM (pinecone7) wrote :

I have run into the same problem on Bionic once more.

pixie@naked:~$ sudo 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

(indicator-cpufreq:10898): Gtk-WARNING **: 13:27:06.784: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory
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
pixie@naked:~$

Same crash as the above, pretty much.

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.