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 449794 - crash in Home Folder: yumex
crash in Home Folder: yumex
Status: RESOLVED DUPLICATE of bug 444717
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-21 14:18 UTC by kenviliang
Modified: 2007-06-23 11:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description kenviliang 2007-06-21 14:18:23 UTC
What were you doing when the application crashed?
yumex


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 256516096 vsize: 256516096 resident: 76427264 share: 52314112 rss: 76427264 rss_rlim: 4294967295
CPU usage: start_time: 1182426644 rtime: 3908 utime: 3220 stime: 688 cutime:196 cstime: 196 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208387872 (LWP 3584)]
[New Thread -1257088112 (LWP 10599)]
(no debugging symbols found)
0x00d8c402 in __kernel_vsyscall ()

Thread 1 (Thread -1208387872 (LWP 3584))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/nosegneg/libc.so.6
  • #6 abort
    from /lib/i686/nosegneg/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 ??
  • #11 gtk_tree_model_unref_node
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_tree_model_unref_node
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #21 g_cclosure_marshal_VOID__ENUM
    from /lib/libgobject-2.0.so.0
  • #22 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #23 g_cclosure_marshal_VOID__ENUM
    from /lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #26 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #29 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 ??
  • #36 ??
  • #37 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libgdk_pixbuf-2.0.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so" is not at the expected address (wrong library or version mismatch?)
warning: /etc/named.caching-nameserver.conf saved as /etc/named.caching-nameserver.conf.rpmsave
warning: /etc/named.rfc1912.zones saved as /etc/named.rfc1912.zones.rpmsave
warning: /var/named/localdomain.zone saved as /var/named/localdomain.zone.rpmsave
warning: /var/named/localhost.zone saved as /var/named/localhost.zone.rpmsave
warning: /var/named/named.broadcast saved as /var/named/named.broadcast.rpmsave
warning: /var/named/named.ca saved as /var/named/named.ca.rpmsave
warning: /var/named/named.ip6.local saved as /var/named/named.ip6.local.rpmsave
warning: /var/named/named.local saved as /var/named/named.local.rpmsave
warning: /var/named/named.zero saved as /var/named/named.zero.rpmsave
--------------------------------------------------
Comment 1 André Klapper 2007-06-22 22:47:20 UTC
Thanks for taking the time to report this bug.
Unfortunately, the 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.

Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] Please install the following debug packages provided by Fedora: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo.

More details can be found here: http://live.gnome.org/GettingTraces
Comment 2 André Klapper 2007-06-23 11:09:00 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 444717 ***