gnome-system-monitor crashed with SIGABRT in __libc_message()

Bug #919014 reported by Karl Mardoff Kittilsen
186
This bug affects 29 people
Affects Status Importance Assigned to Milestone
Gnome System Monitor
Fix Released
Critical
gnome-system-monitor (Ubuntu)
High
Robert Roth

Bug Description

When starting the system monitor for the first time after installing precise, it produced this crash. Subsequent attempts at starting it wails with no warning.

Trying to run it from the command line produces a crash. Attatching that crash.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-system-monitor 3.3.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
Uname: Linux 3.2.0-9-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Jan 20 02:54:58 2012
ExecutablePath: /usr/bin/gnome-system-monitor
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120119)
ProcCmdline: gnome-system-monitor
ProcEnviron:
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 PATH=(custom, no user)
 LANG=nb_NO.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-system-monitor
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 free () from /lib/x86_64-linux-gnu/libc.so.6
Title: gnome-system-monitor crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Karl Mardoff Kittilsen (nightdog) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7faa39370158 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=3, str=0x7faa39370290 "double free or corruption (fasttop)", ptr=<optimized out>) at malloc.c:6283
 __GI___libc_free (mem=<optimized out>) at malloc.c:3738
 apply_cpu_color_settings (settings=<optimized out>, procdata=0x644a80) at procman.cpp:192
 procman_data_new (settings=0x112a990) at procman.cpp:304

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-system-monitor (Ubuntu):
importance: Undecided → Medium
summary: - gnome-system-monitor crashed with SIGABRT in raise()
+ gnome-system-monitor crashed with SIGABRT in __libc_message()
tags: removed: need-amd64-retrace
Robert Roth (evfool)
Changed in gnome-system-monitor (Ubuntu):
importance: Medium → High
status: New → Triaged
Changed in gnome-system-monitor:
importance: Unknown → Critical
status: Unknown → New
Revision history for this message
Robert Roth (evfool) wrote :

This is caused by something introduced in the last cycle, and affects only PCs with more than 4 cores. As a workaround until this gets fixed (I'm working on it, but it could take a while until it gets fixed, commited to GNOME, released in GNOME and in Ubuntu) you can install dconf-tools with the 'sudo apt-get install dconf-tools' command, start dconf-editor, navigate to org->gnome->gnome-system-monitor, and add to the cpu-colors key's value two more tuples in form of (core_number, '#FFFFFF') if you have six cores (the default only has 4 cores, that's why it crashes with six cores). After this you should be able to start system monitor and change the colors of the CPUs from the interface.

Revision history for this message
Robert Roth (evfool) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

visibility: private → public
Changed in gnome-system-monitor (Ubuntu):
assignee: nobody → Robert Roth (evfool)
Changed in gnome-system-monitor:
status: New → In Progress
Revision history for this message
nicholas (npezolano) wrote :

thanks rober roth your fix worked on my 8 core =)

Robert Roth (evfool)
Changed in gnome-system-monitor (Ubuntu):
status: Triaged → In Progress
Changed in gnome-system-monitor:
status: In Progress → Fix Released
Revision history for this message
Bruno Munoz (bruno-bmunoz) wrote :

manual solution with dconf have done it
manually add all (core_number,'#FFFFFF') fix also this crash on my side... but have to do it for all 12 cores (intel i7 3930)

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

This bug was fixed in the package gnome-system-monitor - 3.3.90-0ubuntu1

---------------
gnome-system-monitor (3.3.90-0ubuntu1) precise; urgency=low

  * New upstream release.
    - Hide kthreadd by default (LP: #406825)
    - Fix crash if default colors list is shorter than the number of CPUs.
      (LP: #919014)
  * Rebuild against current pkgbinarymangler to fix md5sums. (LP: #936368)
  * 02_lpi.patch: Unfuzz.
 -- Martin Pitt <email address hidden> Wed, 22 Feb 2012 08:09:45 +0100

Changed in gnome-system-monitor (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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