GNOME Bugzilla – Bug 433353
crash in Gimmie: I have started gimmie fr...
Last modified: 2007-08-29 22:38:11 UTC
What were you doing when the application crashed? I have started gimmie from a terminal window Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 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 (526030 sec old) --------------------- (totem:22177): GStreamer-CRITICAL **: gst_segment_clip: assertion `segment->format == format' failed (totem:22177): GStreamer-CRITICAL **: gst_segment_to_stream_time: assertion `segment->format == format' failed (totem:22177): GStreamer-CRITICAL **: gst_segment_clip: assertion `segment->format == format' failed (totem:22177): GStreamer-CRITICAL **: gst_segment_to_stream_time: assertion `segment->format == format' failed (totem:22177): GStreamer-CRITICAL **: gst_segment_clip: assertion `segment->format == format' failed (totem:22177): GStreamer-CRITICAL **: gst_segment_to_stream_time: assertion `segment->format == format' failed (totem:22177): GStreamer-CRITICAL **: gst_segment_clip: assertion `segment->format == format' failed ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 130525
trashdir = TrashDirectory(trash_uri)
self._trash_dir_changed()
for file in gnomevfs.open_directory(self.trash_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 413872 ***