GNOME Bugzilla – Bug 512386
crash in Home Folder: Ich habe lediglich mit d...
Last modified: 2008-01-28 15:23:56 UTC
What were you doing when the application crashed? Ich habe lediglich mit dem Dateibrowser nach einer Datei suchen lassen 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 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 84967424 vsize: 84967424 resident: 23281664 share: 15777792 rss: 23281664 rss_rlim: 4294967295 CPU usage: start_time: 1201437618 rtime: 1756 utime: 1548 stime: 208 cutime:0 cstime: 3 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208826144 (LWP 2682)] [New Thread -1242907760 (LWP 6769)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 186962
Thread 2 (Thread -1242907760 (LWP 6769))
----------- .xsession-errors (28 sec old) --------------------- invalid new backstep 591 mdb:47, lastbuf:0 skipping granule 0 mdb:47, lastbuf:0 skipping granule 0 mdb:137, lastbuf:0 skipping granule 0 mdb:137, lastbuf:0 skipping granule 0 mdb:137, lastbuf:0 skipping granule 0 mdb:137, lastbuf:0 skipping granule 0 --- Hash table keys for warning below: --> file:///home/marc (nautilus:6761): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2682): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x1077b)! --------------------------------------------------
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 ***