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 146033 - system monitor crashed while matlab 13 was running
system monitor crashed while matlab 13 was running
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-05-24 15:23 UTC by gerlach
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description gerlach 2004-07-08 22:41:02 UTC
Distribution: Fedora Core release 1 (Yarrow)
Package: gnome-system-tools
Severity: normal
Version: GNOME2.4.0 unspecified
Gnome-Distributor: GNOME.Org
Synopsis: system monitor crashed while matlab 13 was running
Bugzilla-Product: gnome-system-tools
Bugzilla-Component: boot-admin
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:

system monitor crashed while matlab 13 was running
Steps to reproduce the crash:
1. launch matlab 13	
2. launch system monitor
3. 

Expected Results:
no crash

How often does this happen?
1st time

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 -1084587360 (LWP 13723)]
(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)...(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)...
0x00650c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #5 raise
    from /lib/tls/libc.so.6
  • #6 abort
    from /lib/tls/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 gtk_tree_store_set_column_types
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 gtk_tree_model_get_path
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 insert_info_to_tree
  • #12 remove_info_from_tree
  • #13 proctable_find_process
  • #14 proctable_update_list
  • #15 proctable_update_all
  • #16 cb_timeout
  • #17 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #18 unblock_source
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #22 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 ??
  • #24 ??
  • #25 gtk_widget_show
    from /usr/lib/libgtk-x11-2.0.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-08 18:41 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-system-tools".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was gerlach@math.ohiostate.edu.
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 Carlos Garnacho 2004-07-08 23:50:23 UTC
gnome-system-bzzzzzz, Moving to system-monitor :)
Comment 2 Olav Vitters 2004-07-09 20:47:20 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 ***