GNOME Bugzilla – Bug 493287
crash in Image Viewer:
Last modified: 2007-12-23 11:04:15 UTC
Version: 2.18.2 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2936.fc7xen #1 SMP Fri Sep 21 11:56:20 EDT 2007 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: 445292544 vsize: 445292544 resident: 95965184 share: 17469440 rss: 95965184 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194162858 rtime: 2160 utime: 2004 stime: 156 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/eog' (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 46912496358608 (LWP 20020)] [New Thread 1094719824 (LWP 20023)] [New Thread 1084229968 (LWP 20021)] (no debugging symbols found) 0x0000003e0e4c82e6 in poll () from /lib64/libc.so.6
+ Trace 175036
Thread 2 (Thread 1094719824 (LWP 20023))
----------- .xsession-errors (13 sec old) --------------------- gstfilesrc.c(976): gst_file_src_start (): /play/source: No such file "/home/adde/Photos/2007-11-04--15.37.29/mov00831.mpg" totem-video-thumbnailer couln't open file 'file:///home/adde/Photos/2007-11-04--15.37.29/mov00831.mpg' Reason: Location not found.. ** Message: Error: Resource not found. gstfilesrc.c(976): gst_file_src_start (): /play/source: No such file "/home/adde/Photos/2007-11-04--15.37.29/mov00832.mpg" ** Message: Error: Resource not found. gstfilesrc.c(976): gst_file_src_start (): /play/source: No such file "/home/adde/Photos/2007-11-04--15.37.29/mov00832.mpg" totem-video-thumbnailer couln't open file 'file:///home/adde/Photos/2007-11-04--15.37.29/mov00832.mpg' Reason: Location not found.. --------------------------------------------------
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 as of version 2.20. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 357405 ***