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 372787 - crash in System Monitor: Scrolling up
crash in System Monitor: Scrolling up
Status: RESOLVED DUPLICATE of bug 370735
Product: system-monitor
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-09 03:07 UTC by felijohn
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description felijohn 2006-11-09 03:07:00 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Scrolling up


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

Memory status: size: 141078528 vsize: 141078528 resident: 18112512 share: 11841536 rss: 18112512 rss_rlim: -1
CPU usage: start_time: 1163041552 rtime: 169 utime: 120 stime: 49 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".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47774263741248 (LWP 21815)]
(no debugging symbols found)
0x00002b734dcf9eb5 in waitpid () from /lib/libpthread.so.0

+ Trace 84608

Thread 1 (Thread 47774263741248 (LWP 21815))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_tree_model_get_valist
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #4 gtk_tree_model_get
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #5 sexy_tree_view_new
    from /usr/lib64/libsexy.so.2
  • #6 ??
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


André Klapper





          2006-11-09 19:39:12 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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