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 508983 - crash in Open Folder: It happened while search...
crash in Open Folder: It happened while search...
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: 2008-01-12 17:14 UTC by jia
Modified: 2008-01-13 12:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jia 2008-01-12 17:14:48 UTC
Version: 2.18.3

What were you doing when the application crashed?
It happened while searching for a file in the file system


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

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 20:27:10 EST 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: 545050624 vsize: 545050624 resident: 42323968 share: 21098496 rss: 42323968 rss_rlim: 18446744073709551615
CPU usage: start_time: 1200155189 rtime: 1873 utime: 1430 stime: 443 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 46912496447008 (LWP 4594)]
[New Thread 1105209680 (LWP 4858)]
(no debugging symbols found)
0x00000033638c82e6 in poll () from /lib64/libc.so.6

Thread 2 (Thread 1105209680 (LWP 4858))

  • #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 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #10 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #11 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #12 gnome_vfs_directory_visit_uri
    from /usr/lib64/libgnomevfs-2.so.0
  • #13 ??
  • #14 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #15 start_thread
    from /lib64/libpthread.so.0
  • #16 clone
    from /lib64/libc.so.6


----------- .xsession-errors ---------------------
localuser:root being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/4468
/usr/lib/python2.5/site-packages/pirut/GroupSelector.py:247: GtkWarning: Failed to set text from markup due to error parsing markup: Error on line 1: Character ' ' is not valid at the start of an enti
  self.window.show_all()
/usr/lib/python2.5/site-packages/pirut/GroupSelector.py:248: GtkWarning: Failed to set text from markup due to error parsing markup: Error on line 1: Character ' ' is not valid at the start of an enti
  return self.window.run()
(nautilus:4594): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
Xlib: unexpected async reply (sequence 0x13db5)!
Xlib: sequence lost (0x200ed > 0x14133) in reply type 0xe3!
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffa87fd000
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-13 12:00:17 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 ***