GNOME Bugzilla – Bug 470392
crash in Gimmie: Running Gnomad, Gimmie w...
Last modified: 2007-08-27 11:15:50 UTC
What were you doing when the application crashed? Running Gnomad, Gimmie was just sitting in the bar. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-386 #2 Thu Jun 7 20:16:13 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Resilience Icon Theme: Tangerine Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (124 sec old) --------------------- totem-video-thumbnailer couln't open file 'file:///media/My%20Book_/videos/greys.anatomy.s03e01.hdtv-lol.avi' Reason: Could not determine type of stream.. ** Message: Error: Could not determine type of stream. gsttypefindelement.c(737): gst_type_find_element_activate (): /play/decodebin0/typefind totem-video-thumbnailer couln't open file 'file:///media/My%20Book_/videos/greys.anatomy.s03e01.hdtv-lol.avi' Reason: Could not determine type of stream.. ** Message: Error: Could not determine type of stream. gsttypefindelement.c(737): gst_type_find_element_activate (): /play/decodebin0/typefind totem-video-thumbnailer couln't open file 'file:///media/My%20Book_/videos/Greys.Anatomy.s03e06.HDTV.XviD-LOL.avi' Reason: Could not determine type of stream.. totem-video-thumbnailer couln't thumbnail file: 'file:///media/My%20Book_/videos/Greys.Anatomy.s03e05.HDTV.XviD-XOR.avi' Reason: Took too much time to thumbnail. -------------------------------------------------- Traceback (most recent call last):
+ Trace 157973
acct_doc = parse(self.accounts_path)
from xml.dom import expatbuilder
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 417988 ***