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 396168 - crash in System Monitor: Trying to load swiftfox,...
crash in System Monitor: Trying to load swiftfox,...
Status: RESOLVED DUPLICATE of bug 354559
Product: gtk+
Classification: Platform
Component: .General
2.10.x
Other All
: High critical
: ---
Assigned To: gtk-bugs
gtk-bugs
: 397402 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-01-13 17:08 UTC by fjr122
Modified: 2007-01-23 00:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description fjr122 2007-01-13 17:08:52 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Trying to load swiftfox, I have both firefox and swiftfox installed and have ahd problems ever since I installed both.


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

Memory status: size: 54939648 vsize: 0 resident: 54939648 share: 0 rss: 11747328 rss_rlim: 0
CPU usage: start_time: 1168495301 rtime: 0 utime: 1835635 stime: 0 cutime:1288523 cstime: 0 timeout: 547112 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 -1225189712 (LWP 7346)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 101830

Thread 1 (Thread -1225189712 (LWP 7346))

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


Christian Kirbach





          2007-01-16 21:18:53 UTC
        



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






Comment 2


Christian Kirbach





          2007-01-16 21:19:59 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

please isntall the gtk+ and libsexy debug packages






Comment 3


palfrey





          2007-01-23 00:18:57 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 354559 ***