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 413900 - crash in System Monitor: unter prozesse den proze...
crash in System Monitor: unter prozesse den proze...
Status: RESOLVED DUPLICATE of bug 400162
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-03-02 15:47 UTC by juergen
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description juergen 2007-03-02 15:47:41 UTC 
Version: 2.16.1

What were you doing when the application crashed?
unter prozesse den prozessnamen amarokapp angeklickt


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

Memory status: size: 56471552 vsize: 0 resident: 56471552 share: 0 rss: 16863232 rss_rlim: 0
CPU usage: start_time: 1172850334 rtime: 0 utime: 218 stime: 0 cutime:186 cstime: 0 timeout: 32 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 -1225668944 (LWP 5330)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 115231

Thread 1 (Thread -1225668944 (LWP 5330))

  • #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 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/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 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_tree_store_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 gtk_tree_store_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_tree_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 __kernel_vsyscall 






Comment 1


Pedro Villavicencio





          2007-03-03 00:49:48 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 400162 ***