GNOME Bugzilla – Bug 436276
crash in Gimmie:
Last modified: 2007-05-26 00:58:12 UTC
What were you doing when the application crashed? 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: Milk 2.0 Icon Theme: Tango 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 (81408 sec old) --------------------- ** Message: mAutostart: 1, mRepeat: 0 ** Message: Launching: /usr/lib/totem/totem-plugin-viewer --plugin-type gmp --user-agent Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty) --mimetype v ** Message: Viewer spawned, PID 6678 ** Message: GetValue variable 14 (e) ** Message: Initial window set, XID 3271200 size 1020x579 ** Message: No viewer proxy yet, deferring SetWindow ** Message: NewStream mimetype 'video/x-ms-wmv' URL 'http://f1.grp.yahoofs.com/v1/gDk8RnyB4MmASgyXz45P9bWDX2bCaL3VlDK1HMSctvHaB6Qp6pJUoopXOiQn8LT5DyiRkePPW8ayaZ4ddSIt5FW-HFTnDfHS/cathydaytv.wmv' ** Message: Not expecting a new stream; aborting stream ** Message: Viewer DBus interface name is 'org.gnome.totem.PluginViewer_6678' ** Message: NameOwnerChanged old-owner '' new-owner ':1.29' ** Message: Viewer now connected to the bus ** Message: ViewerSetup ** Message: Calling SetWindow ** Message: NameOwne ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 132656
self.sidebar.connect("set-source", lambda sb, source: self._set_source(source))
filtered = self._filter_items_num_days_ago(source.get_items(),
for item in source.get_items():
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 ***