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 488616 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 454799
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-20 13:58 UTC by Sascha.Zorn
Modified: 2007-10-22 18:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Sascha.Zorn 2007-10-20 13:58:53 UTC
Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 513286144 vsize: 513286144 resident: 74985472 share: 22110208 rss: 74985472 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192883311 rtime: 725 utime: 619 stime: 106 cutime:195 cstime: 33 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912509026784 (LWP 3385)]
[New Thread 1178638672 (LWP 5227)]
(no debugging symbols found)
0x0000003b78ac82e6 in poll () from /lib64/libc.so.6

Thread 2 (Thread 1178638672 (LWP 5227))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strstr
    from /lib64/libc.so.6
  • #4 ??
  • #5 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #6 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #7 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #8 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #9 gnome_vfs_directory_visit_uri
    from /usr/lib64/libgnomevfs-2.so.0
  • #10 ??
  • #11 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #12 start_thread
    from /lib64/libpthread.so.0
  • #13 clone
    from /lib64/libc.so.6


----------- .xsession-errors ---------------------
 CConn:       Throughput 20158 kbit/s - changing to hextile encoding
 CConn:       Throughput 20158 kbit/s - changing to full colour
 CConn:       Using pixel format depth 24 (32bpp) little-endian rgb888
 CConn:       Using hextile encoding
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Max failures exceeded, exiting now
(nautilus:3385): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
warning: the debug information found in "/usr/lib/debug//usr/bin/nautilus.debug" does not match "/usr/bin/nautilus" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib64/libnautilus-extension.so.1.1.0.debug" does not match "/usr/lib64/libnautilus-extension.so.1" (CRC mismatch).
--------------------------------------------------
Comment 1 Sascha.Zorn 2007-10-20 15:55:21 UTC
Hi!

My Nautilus 2.18.3 crashes every time I try to "Search" for documents. But I'm not able to get the debug symbols installed. Do you know which debuginfo packet I need to install?
Comment 2 André Klapper 2007-10-22 11:35:16 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, eel2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo.

More details can be found here: http://live.gnome.org/GettingTraces
Comment 3 Sascha.Zorn 2007-10-22 16:36:12 UTC
I'm just copying Thread2, beacause the others don't look very interesting:

Thread 2 (Thread 1168148816 (LWP 4386))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #2 <signal handler called>
  • #3 strstr
    from /lib64/libc.so.6
  • #4 ??
  • #5 directory_visit_internal
    at gnome-vfs-directory.c line 401
  • #6 directory_visit_internal
    at gnome-vfs-directory.c line 426
  • #7 directory_visit_internal
    at gnome-vfs-directory.c line 426
  • #8 directory_visit_internal
    at gnome-vfs-directory.c line 426
  • #9 directory_visit_internal
    at gnome-vfs-directory.c line 426
  • #10 directory_visit_internal
    at gnome-vfs-directory.c line 426
  • #11 directory_visit_internal
    at gnome-vfs-directory.c line 426
  • #12 directory_visit_internal
    at gnome-vfs-directory.c line 426
  • #13 gnome_vfs_directory_visit_uri
    at gnome-vfs-directory.c line 495
  • #14 ??
  • #15 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #16 start_thread
    from /lib64/libpthread.so.0
  • #17 clone
    from /lib64/libc.so.6

Comment 4 André Klapper 2007-10-22 18:05:23 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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