GNOME Bugzilla – Bug 516068
crash in Open Folder: I was closing the progra...
Last modified: 2008-02-13 00:28:36 UTC
Version: 2.18.3 What were you doing when the application crashed? I was closing the program by the x-button in the upper right corner. 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.15-80.fc7 #1 SMP Sun Feb 10 16:52:18 EST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 508674048 vsize: 508674048 resident: 30519296 share: 12603392 rss: 30519296 rss_rlim: 18446744073709551615 CPU usage: start_time: 1202841024 rtime: 3143 utime: 1448 stime: 1695 cutime:6 cstime: 5 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 46912604525296 (LWP 3825)] [New Thread 1178638672 (LWP 4295)] (no debugging symbols found) 0x00002aaaae6ab2e6 in poll () from /lib64/libc.so.6
+ Trace 188983
Thread 2 (Thread 1178638672 (LWP 4295))
----------- .xsession-errors --------------------- Design & Programming: Guillaume Cottenceau Level Editor: Kim and David Joham Originally sponsored by Mandriva <http://www.mandriva.com/> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License version 2, as published by the Free Software Foundation. [SDL Init] [Graphics............] [Sound Init] [Levels] Ready. (nautilus:3825): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x12d1a)! warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffc0171000 --------------------------------------------------
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 ***