GNOME Bugzilla – Bug 516775
crash in Open Folder: I was searching for "avi...
Last modified: 2008-02-16 10:21:45 UTC
Version: 2.18.3 What were you doing when the application crashed? I was searching for "avidemux" in my home folder, parallel a dvd conversion process (mencoder initiated by devede) was running 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.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 108265472 vsize: 108265472 resident: 36995072 share: 23060480 rss: 36995072 rss_rlim: 4294967295 CPU usage: start_time: 1203121440 rtime: 548 utime: 495 stime: 53 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209035040 (LWP 19628)] [New Thread -1307726960 (LWP 19665)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189362
Thread 2 (Thread -1307726960 (LWP 19665))
----------- .xsession-errors --------------------- MEncoder SVN-r23545 (C) 2000-2007 MPlayer Team Launch: spumux "/home/peter/Desktop/brokebackmountain_menu.xml" Launching shell program: spumux "/home/peter/Desktop/brokebackmountain_menu.xml" Launching program: program: ['mencoder', '-oac', 'lavc', '-ovc', 'lavc', '-of', 'mpeg', '-mpegopts', 'format=dvd: --- Hash table keys for warning below: --> file:///home/peter (nautilus:19526): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:4087): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x2d4d8)! (nautilus:19628): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed --------------------------------------------------
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 ***