GNOME Bugzilla – Bug 504800
crash in Open Folder: I typed in "network://" ...
Last modified: 2007-12-23 19:24:17 UTC
Version: 2.18.3 What were you doing when the application crashed? I typed in "network://" at the search bar and it crashed. 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.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 87154688 vsize: 87154688 resident: 28921856 share: 22102016 rss: 28921856 rss_rlim: 4294967295 CPU usage: start_time: 1198209280 rtime: 847 utime: 740 stime: 107 cutime:12 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 -1209162016 (LWP 9801)] [New Thread -1232241776 (LWP 9881)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182506
Thread 2 (Thread -1232241776 (LWP 9881))
----------- .xsession-errors (19 sec old) --------------------- ** Message: Error: You do not have a decoder installed to handle this file. You might need to install the necessary plugins. gstplaybasebin.c(2203): prepare_output (): /play totem-video-thumbnailer couln't open file 'file:///home/gszumo/gpodder-downloads/bd76c2bcecfdd499baa7912dead9c404/2f32613f7a6bed088a3630f4e666e062.mov' Reason: The playback of this movie requires the following decoders which are not installed: MPEG-4 Video decoder MPEG-4 AAC decoder. apps file failure apps file failure apps file failure apps file failure (nautilus:9801): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x12584)! --------------------------------------------------
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 ***