GNOME Bugzilla – Bug 485613
crash in Deskbar: it's the first time i en...
Last modified: 2007-10-12 10:22:04 UTC
What were you doing when the application crashed? it's the first time i enter a search! Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Tue Oct 9 09:51:52 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human 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 (186 sec old) --------------------- alarm-queue.c:518 (load_alarms) alarm-queue.c:537 (load_alarms) - Disconnecting old queries alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-queue.c:238 (midnight_refresh_async) - Reschedule the midnight update alarm-queue.c:200 (queue_midnight_refresh) - Refreshevolution-alarm-notify-Message: Setting timeout for 86400 1192161600 1192075200 evolution-alarm-notify-Message: Fri Oct 12 00:00:00 2007 evolution-alarm-notify-Message: Thu Oct 11 00:00:00 2007 ERROR: execution of prepared query UpdateFileMove failed due to constraint failed with return code 19 ** Message: Error: Could not determine type of stream. gsttypefindelement.c(735): gst_type_find_element_activate (): /play/decodebin0/typefind totem-video-thumbnailer couln't open file 'file:///home/mazen/Desktop/1214122148_1225980053_b8f08fbf84c3516145d845ee5d0f382eb4035c0f.flv' Reason: Could not determine type of stream.. -------------------------------------------------- Traceback (most recent call last):
+ Trace 169410
reply_handler(*message.get_args_list(**get_args_opts))
reply_handler = lambda hits: self.recieve_hits(qstring, hits, max),
matches.append(TrackerLiveSearchMatch (output))
self.add_all_actions (get_actions_for_uri(result['uri']))
mime = gnomevfs.get_mime_type(uri)
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 474131 ***