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 521070 - crash in System Monitor: clicked twice on system ...
crash in System Monitor: clicked twice on system ...
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
Depends on:
Blocks:
 
 
Reported: 2008-03-07 19:44 UTC by admin
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description admin 2008-03-07 19:44:57 UTC 
Version: 2.20.2

What were you doing when the application crashed?
clicked twice on system monitor panel


Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.20.3 2008-02-02 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-gentoo #6 SMP Fri Feb 29 16:59:23 EET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: OSX

Memory status: size: 24121344 vsize: 24121344 resident: 9805824 share: 8290304 rss: 9805824 rss_rlim: 4294967295
CPU usage: start_time: 1204918951 rtime: 3 utime: 3 stime: 0 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 0xb6c7c8e0 (LWP 20311)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 191672

Thread 1 (Thread 0xb6c7c8e0 (LWP 20311))

  • #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 (516537 sec old) ---------------------
(22:13:49) oscar: unknown capability: {67361515-612d-4c07-8f3d-bde6408ea041}
(22:13:49) oscar: unknown capability: {1a093c6c-d7fd-4ec5-9d51-a6474e34f5a0}
(22:13:49) oscar: unknown capability: {563fc809-0b6f-41bd-9f79-422609dfa2f3}
(22:13:49) oscar: unknown capability: {b2ec8f16-7c6f-451b-bd79-dc58497888b9}
(22:13:49) oscar: unknown capability: {178c2d9b-daa5-45bb-8ddb-f3bdbd53a10a}
(22:13:49) blist: Updating buddy status for 178416883 (ICQ)
(22:13:49) blist: Updating buddy status for 178416883 (ICQ)
(22:13:49) oscar: unknown capability: {0138ca7b-769a-4915-88f2-13fc00979ea8}
(22:13:49) oscar: unknown capability: {67361515-612d-4c07-8f3d-bde6408ea041}
(22:13:49) oscar: unknown capability: {1a093c6c-d7fd-4ec5-9d51-a6474e34f5a0}
(22:13:49) oscar: unknown capability: {563fc809-0b6f-41bd-9f79-422609dfa2f3}
(22:13:49) oscar: unknown capability: {b2ec8f16-7c6f-451b-bd79-dc58497888b9}
(22:13:49) oscar: unknown capability: {178c2d9b-daa5-45bb-8ddb-f3bdbd53a10a}
(22:13:49) blist: Updating buddy status for 178416
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Gianluca Borello 2008-03-08 09:01:16 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 516325 ***