GNOME Bugzilla – Bug 523342
crash in Gimmie: clicked Devices in the L...
Last modified: 2008-03-22 11:07:47 UTC
What were you doing when the application crashed? clicked Devices in the Linux panel Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-386 #1 Tue Feb 12 07:12:19 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 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 (464 sec old) --------------------- Serial number of failed request: 49 Current serial number in output stream: 50 Window manager warning: last_focus_time (3332791769) is greater than comparison timestamp (3332791689). This most likely represents a buggy client sending inaccurate timestamps in messages such as _N (rhythmbox:17722): RhythmDB-WARNING **: trying to sync properties of non-editable file (rhythmbox:17722): RhythmDB-WARNING **: trying to sync properties of non-editable file (rhythmbox-metadata:17753): GStreamer-CRITICAL **: gst_pad_set_caps: assertion `caps == NULL || gst_caps_is_fixed (caps)' failed (rhythmbox-metadata:17753): GStreamer-CRITICAL **: gst_pad_set_caps: assertion `caps == NULL || gst_caps_is_fixed (caps)' failed (rhythmbox-metadata:17753): GStreamer-CRITICAL **: gst_pad_set_caps: assertion `caps == NULL || gst_caps_is_fixed (caps)' failed (rhythmbox-metadata:17753): GStreamer-CRITICAL **: gst_pad_set_caps: assertion `caps == NULL || gst_caps_is_fixed (caps)' failed -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 192843
printer.connect("attributes_changed", lambda p: self.emit("reload"))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 475020 ***