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 516326 - crash in System Monitor: double clicked on gnome-...
crash in System Monitor: double clicked on gnome-...
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-02-14 01:00 UTC by admin
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description admin 2008-02-14 01:00:45 UTC
Version: 2.20.2

What were you doing when the application crashed?
double clicked on gnome-system-monitor panel


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

System: Linux 2.6.24-gentoo #2 SMP Tue Feb 5 18:51:40 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: 24104960 vsize: 24104960 resident: 9805824 share: 8290304 rss: 9805824 rss_rlim: 4294967295
CPU usage: start_time: 1202950778 rtime: 2 utime: 2 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 0xb6ba18e0 (LWP 13602)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6ba18e0 (LWP 13602))

  • #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 (11149 sec old) ---------------------
(23:51:11) jabber: Sending (ssl): <message type='chat' id='purple59e2dc32' to='heidizeyer@jabber.org/Home'><active xmlns='http://jabber.org/protocol/chatstates'/><body>ok ich werde da mal nachfragen</
(23:51:11) jabber: Sending (ssl): <message type='chat' id='purple59e2dc33' to='heidizeyer@jabber.org/Home'><active xmlns='http://jabber.org/protocol/chatstates'/></message>
(23:51:28) jabber: Recv (ssl)(176): <message from='heidizeyer@jabber.org/Home' to='albertzeyer@jabber.org/Gaim' type='chat' id='purpleaed570ec'><composing xmlns='http://jabber.org/protocol/chatstates'
(23:51:57) jabber: Recv (ssl)(173): <message from='heidizeyer@jabber.org/Home' to='albertzeyer@jabber.org/Gaim' type='chat' id='purpleaed570ed'><paused xmlns='http://jabber.org/protocol/chatstates'/><
(23:51:59) jabber: Recv (ssl)(176): <message from='heidizeyer@jabber.org/Home' to='albertzeyer@jabber.org/Gaim' type='chat' id='purpleaed570ee'><composing xmlns='http://jabber.org/protocol/chatstates'
(23:52:22) jabber: Recv (ssl)(449): <message from='heidizeyer@jabber.org/Home' to='albertzeyer@jabber.org/Gaim' type='chat' id='purpleaed570ef'><active xmlns='http://jabber.org/protocol/chatstates'/><
(23:52:22) jabber: Recv (ssl)(173): <message from='heidizeyer@jabber.org/Home' to='albertzeyer@jabber.org/Gaim' type='chat' id='purpleaed570f0'><active xmlns='http://jabber.org/protocol/chatstates'/><
(23:53:52) jabber: Sending (ssl): <message type='chat' id='purple59e2dc34' to='heidizeyer@jabber.org/Home'><composing xmlns='http://jabber.org/protocol/chatstates'/></message>
(23:53:55) jabber: Sending (ssl): <message type='chat' id='purple59e2dc35' to='heidizeyer@jabber.org/Home'><active xmlns='http://jabber.org/protocol/chatstates'/><body>hm</body><html xmlns='http://jab
(23:53:55) jabber: Sending (ssl): <message type='chat' id='purple59e2dc36' to='heidizeyer@jabber.org/Home'><active xmlns='http://jabber.org/protocol/chatstates'/></message>
(23:54:00) oscar: unknown short capability: {134c}
(23:54:00) oscar: unknown capability: {563fc809-0b6f-41bd-9f79-422609dfa2f3}
(23:54:00) oscar: unknown capability: {1a093c6c-d7fd-4ec5-9d51-a6474e34f5a0}
(23:54:00) oscar: unknown capability: {4d697261-6e6
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Benoît Dejean 2008-02-14 10:13:36 UTC

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