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 146593 - Open Gnome-System-Monitor from system Monitor applet
Open Gnome-System-Monitor from system Monitor applet
Status: RESOLVED DUPLICATE of bug 98295
Product: system-monitor
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2004-06-14 14:59 UTC by Thomas M. Hinkle
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Thomas M. Hinkle 2004-07-09 07:27:43 UTC
Distribution: Debian testing/unstable
Package: system-monitor
Severity: normal
Version: GNOME2.6.1 2.6.0
Gnome-Distributor: Debian
Synopsis: Open Gnome-System-Monitor from system Monitor applet
Bugzilla-Product: system-monitor
Bugzilla-Component: general
Bugzilla-Version: 2.6.0
BugBuddy-GnomeVersion: 2.0 (2.6.1.1)
Description:
Description of the crash:
while in the background, system monitor crashes.

Steps to reproduce the crash:
1. Open system monitor
2. leave open
3. open firefox, browse for a while.

Expected Results:
Monitor keeps monitoring.

How often does this happen?
Just once so far.

Additional Information:



Debugging Information:

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

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...[Thread debugging using
libthread_db enabled]
[New Thread 1087694464 (LWP 18476)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...0x4025e40e in __waitpid_nocancel
() from /lib/tls/libpthread.so.0

Thread 1 (Thread 1087694464 (LWP 18476))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/tls/libc.so.6
  • #4 ??
    from /lib/tls/libc.so.6
  • #5 ??
  • #6 abort
    from /lib/tls/libc.so.6
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??
  • #38 ??
  • #39 ??
  • #40 ??
  • #41 ??
  • #42 g_free
    from /usr/lib/libglib-2.0.so.0
  • #43 g_log
    from /usr/lib/libglib-2.0.so.0
  • #44 gtk_tree_store_set_column_types
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 gtk_tree_model_get_path
    from /usr/lib/libgtk-x11-2.0.so.0
  • #46 insert_info_to_tree
  • #47 remove_info_from_tree
  • #48 proctable_find_process
  • #49 proctable_update_list
  • #50 proctable_update_all
  • #51 cb_timeout
  • #52 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #53 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #54 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #55 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #56 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #57 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #58 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 03:27 -------


Unknown version 2.6.0 in product system-monitor. Setting version to "0.4".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "system-monitor".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Olav Vitters 2004-07-09 20:47:18 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 98295 ***