xfce4-cpufreq-plugin crashed with SIGSEGV in free()

Bug #477201 reported by Petr Hejl
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xfce4-cpufreq-plugin (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: xfce4-cpufreq-plugin

Just after start the crash report was detected.

ProblemType: Crash
Architecture: amd64
Date: Sat Nov 7 00:02:16 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/xfce4/panel-plugins/xfce4-cpufreq-plugin
NonfreeKernelModules: fglrx
Package: xfce4-cpufreq-plugin 0.2-2
ProcCmdline: /usr/lib/xfce4/panel-plugins/xfce4-cpufreq-plugin socket_id 31457335 name cpufreq id 12261805293 display_name CPUFreq size 30 screen_position 1
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7f7b4fc476b9 <free+25>: mov -0x8(%rdi),%rax
 PC (0x7f7b4fc476b9) ok
 source "-0x8(%rdi)" (0x0001fff8) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xfce4-cpufreq-plugin
StacktraceTop:
 free () from /lib/libc.so.6
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
Title: xfce4-cpufreq-plugin crashed with SIGSEGV in free()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers video
XsessionErrors:
 (xfce4-xkb-plugin:2412): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table != NULL' failed
 (xfce4-xkb-plugin:2412): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table != NULL' failed
 (xfce4-xkb-plugin:2412): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table != NULL' failed
 (polkit-gnome-authentication-agent-1:2469): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Petr Hejl (hejlp) wrote :
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.