After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 505567 - crash in System Monitor: clicked on the systemmon...
crash in System Monitor: clicked on the systemmon...
Status: RESOLVED DUPLICATE of bug 516325
Product: system-monitor
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
: 490252 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-12-25 13:52 UTC by admin
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description admin 2007-12-25 13:52:03 UTC 
Version: 2.20.1

What were you doing when the application crashed?
clicked on the systemmonitor-panel twice


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.20.1 2007-11-22 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.23-gentoo-r3-mactel #16 SMP Mon Dec 24 12:37:05 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: OSX

Memory status: size: 24616960 vsize: 24616960 resident: 9973760 share: 8396800 rss: 9973760 rss_rlim: 4294967295
CPU usage: start_time: 1198590651 rtime: 2 utime: 0 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-system-monitor'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6be86d0 (LWP 28239)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 182998

Thread 1 (Thread 0xb6be86d0 (LWP 28239))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 369
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 677
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
  • #8 <signal handler called>
  • #9 __kernel_vsyscall
  • #10 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #11 *__GI_abort
    at abort.c line 88
  • #12 IA__g_logv
    at gmessages.c line 497
  • #13 IA__g_log
    at gmessages.c line 517
  • #14 main
    at procman.cpp line 689
  • #15 __libc_start_main
    at libc-start.c line 229
  • #16 _start
  • #0 __kernel_vsyscall 


----------- .xsession-errors (6956 sec old) ---------------------
(12:55:12) oscar: unknown capability: {b99708b5-3a92-4202-b069-f1e757bb2e17}
(12:55:12) oscar: unknown capability: {1a093c6c-d7fd-4ec5-9d51-a6474e34f5a0}
(12:55:12) blist: Updating buddy status for 302312484 (ICQ)
(12:55:12) oscar: unknown capability: {563fc809-0b6f-41bd-9f79-422609dfa2f3}
(12:55:12) blist: Updating buddy status for 176223620 (ICQ)
(12:55:12) blist: Updating buddy status for 72747079 (ICQ)
(12:55:12) blist: Updating buddy status for 344434657 (ICQ)
(12:55:12) oscar: unknown capability: {1a093c6c-d7fd-4ec5-9d51-a6474e34f5a0}
(12:55:12) oscar: unknown capability: {563fc809-0b6f-41bd-9f79-422609dfa2f3}
(12:55:12) oscar: unknown capability: {53494d20-636c-6965-6e74-202000090403}
(12:55:12) blist: Updating buddy status for 240522408 (ICQ)
(12:55:12) oscar: unknown capability: {1a093c6c-d7fd-4ec5-9d51-a6474e34f5a0}
(12:55:12) oscar: unknown capability: {563fc809-0b6f-41bd-9f79-422609dfa2f3}
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Benoît Dejean 2008-01-11 11:10:28 UTC 
That's a libbacon bug.
Comment 2 Benoît Dejean 2008-01-11 11:11:06 UTC 
*** Bug 490252 has been marked as a duplicate of this bug. ***
Comment 3 Akhil Laddha 2010-06-22 06:51:25 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 516325 ***