xfce4-sensors crashed with SIGSEGV in *__GI___libc_free()

Bug #345678 reported by João Rocha on 2009-03-19
This bug affects 10 people
Affects Status Importance Assigned to Milestone
xfce4-sensors-plugin (Ubuntu)

Bug Description

Binary package hint: xfce4-sensors-plugin

I'm using (with all updates installed):
Description: Ubuntu jaunty (development branch)
Release: 9.04

The version is:
  Version table:
 *** 0
        500 http://archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status

There is a crash when I try to start Sensor Viewer in: System -> Sensor Viewer.
When executing xfce4-sensors in terminal I get segmentation fault

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/xfce4-sensors
Package: xfce4-sensors-plugin
ProcCmdline: xfce4-sensors
Signal: 11
SourcePackage: xfce4-sensors-plugin
 *__GI___libc_free (mem=0xb7fc4268) at malloc.c:3623
 g_free () from /usr/lib/libglib-2.0.so.0
 get_hddtemp_value ()
 remove_unmonitored_drives ()
 initialize_hddtemp ()
Title: xfce4-sensors crashed with SIGSEGV in *__GI___libc_free()
Uname: Linux 2.6.28-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

João Rocha (joaoesperanco) wrote :

StacktraceTop:*__GI___libc_free (mem=0xb7fc4268) at malloc.c:3623
IA__g_free (mem=0xb7fc4268)
get_hddtemp_value (disk=0x86aaaa8 "/dev/sda",
remove_unmonitored_drives (chip=0x86aaa50,
initialize_hddtemp (chips=0x86a6a20,

Changed in xfce4-sensors-plugin:
importance: Undecided → Medium
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xfce4-sensors-plugin -

xfce4-sensors-plugin ( jaunty; urgency=low

  * debian/patches/01_fix_segfault_at_startup.patch: correctly init *checktext
    to NULL, fixes a crash in free() with invalid pointer [upstream svn r6985]
    (LP: #257656, #344015, #345678).

 -- Lionel Le Folgoc <email address hidden> Thu, 26 Mar 2009 21:03:50 +0100

Changed in xfce4-sensors-plugin:
status: New → Fix Released
João Rocha (joaoesperanco) wrote :

After install the indicated bug fix, I can confirm that now everythin is ok!

Thank you!

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

Duplicates of this bug

Other bug subscribers