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 429759 - crash in System Monitor:
crash in System Monitor:
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
Depends on:
Blocks:
 
 
Reported: 2007-04-14 18:27 UTC by yves.reecht
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description yves.reecht 2007-04-14 18:27:33 UTC 
Version: 2.16.1

What were you doing when the application crashed?



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

Memory status: size: 133603328 vsize: 133603328 resident: 17981440 share: 11833344 rss: 17981440 rss_rlim: -1
CPU usage: start_time: 1176575382 rtime: 629 utime: 347 stime: 282 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 47539208784720 (LWP 15667)]
(no debugging symbols found)
0x00002b3c93719eb5 in waitpid () from /lib/libpthread.so.0

+ Trace 127785

Thread 1 (Thread 47539208784720 (LWP 15667))

  • #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


Pedro Villavicencio





          2007-04-15 03:30:54 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 354559 ***