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 532112 - crash in System Monitor: do nothing
crash in System Monitor: do nothing
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-05-08 06:50 UTC by andy_lau
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description andy_lau 2008-05-08 06:50:54 UTC 
Version: 2.20.1

What were you doing when the application crashed?
do nothing


Distribution: Unknown
Gnome Release: 2.20.3 2008-03-21 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.23.9 #7 SMP PREEMPT Wed Apr 16 22:40:30 CST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Linpus

Memory status: size: 29753344 vsize: 29753344 resident: 7057408 share: 5906432 rss: 7057408 rss_rlim: 4294967295
CPU usage: start_time: 1210229282 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'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208727776 (LWP 23447)]
0x453ea09e in __waitpid_nocancel () from /lib/libpthread.so.0
Current language:  auto; currently asm

+ Trace 197201

Thread 1 (Thread -1208727776 (LWP 23447))

  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #3 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #4 check_if_gdb
    at gnome-breakpad.cc line 283
  • #5 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
  • #6 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
  • #7 <signal handler called>
  • #8 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #9 *__GI_abort
    at abort.c line 88
  • #10 g_logv
    from /lib/libglib-2.0.so.0
  • #11 g_log
    from /lib/libglib-2.0.so.0
  • #12 main
  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0 


----------- .xsession-errors (313 sec old) ---------------------
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
converting comment system...done.Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
warning: could not initiate dbus
could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.PowerManager was not provided by any .service files
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
--------------------------------------------------
Comment 1 Gianluca Borello 2008-05-08 10:42:56 UTC 
can you reproduce this bug? The stacktrace seems useless...
Comment 2 Akhil Laddha 2010-06-22 06:51:59 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 ***