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 485177 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 484773
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-09 20:36 UTC by Sascha.Zorn
Modified: 2007-10-13 22:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Sascha.Zorn 2007-10-09 20:36:34 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: 571125760 vsize: 571125760 resident: 51548160 share: 20750336 rss: 51548160 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191962128 rtime: 458 utime: 349 stime: 109 cutime:0 cstime: 0 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 46912496393264 (LWP 16132)]
[New Thread 1105209680 (LWP 16168)]
[New Thread 1084229968 (LWP 16158)]
(no debugging symbols found)
0x0000003b78ac82e6 in poll () from /lib64/libc.so.6

+ Trace 169104

Thread 2 (Thread 1105209680 (LWP 16168))

  • #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 ---------------------
warning: .dynamic section for "/usr/lib64/libstartup-notification-1.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib64/libgnome-window-settings.so.1" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib64/libpanel-applet-2.so.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib64/libmetacity-private.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
(nautilus:16132): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
Xlib: unexpected async reply (sequence 0x41d9)!
--------------------------------------------------
Comment 1 Christian Kirbach 2007-10-13 22:35:32 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 484773 ***