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 360913 - crash in System Monitor: Scrolling through the li...
crash in System Monitor: Scrolling through the li...
Status: RESOLVED DUPLICATE of bug 354559
Product: system-monitor
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
: 391591 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-09 14:32 UTC by graphic23
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description graphic23 2006-10-09 14:32:25 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Scrolling through the list. 


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 36802560 vsize: 0 resident: 36802560 share: 0 rss: 13385728 rss_rlim: 0
CPU usage: start_time: 1160404232 rtime: 0 utime: 1221 stime: 0 cutime:1047 cstime: 0 timeout: 174 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225926992 (LWP 18803)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 75434

Thread 1 (Thread -1225926992 (LWP 18803))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_tree_model_get_valist
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_tree_model_get
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 sexy_tree_view_new
    from /usr/lib/libsexy.so.2
  • #7 g_source_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
  • #13 ??
  • #14 _IO_stdin_used
  • #15 ??
  • #16 ??
  • #17 ??
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2006-10-09 14:37:51 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug: 
Unfortunately, the stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols and post the output at bug 354559? Please see  
            http://live.gnome.org/GettingTraces/DistroSpecificInstructions
for more information on how to do so.

Could you also please start gnome-system-monitor in a terminal like this and post the output at bug 354559?:
            $ GNOME_SYSTEM_MONITOR_DEBUG= gnome-system-monitor

Thanks in advance for helping to fix this.

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






Comment 2


Damien Durand





          2007-01-01 18:57:15 UTC
        



*** Bug 391591 has been marked as a duplicate of this bug. ***