GNOME Bugzilla – Bug 426271
crash in Gimmie: changing the range of ti...
Last modified: 2007-05-26 01:51:46 UTC
What were you doing when the application crashed? changing the range of time (from 1 week) clicking in the time bar Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-13-386 #2 Sun Mar 25 00:18:53 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaGilouche Icon Theme: Gion 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 (169 sec old) --------------------- warnings.warn("apt API not stable yet", FutureWarning) /home/polky/.gnome2/Gossip/contacts.xml:0: error : unterminated entity reference valeriana ** (gossip:4443): CRITICAL **: gossip_image_chooser_set_requirements: assertion `max_width >= min_width' failed ** (gossip:4443): CRITICAL **: gossip_telepathy_contacts_set_avatar: assertion `avatar != NULL' failed ** (gossip:4443): CRITICAL **: gossip_image_chooser_set_requirements: assertion `max_width >= min_width' failed warnings.warn("apt API not stable yet", FutureWarning) ** (epiphany:5061): CRITICAL **: ephy_spinner_tool_item_set_spinning: assertion `spinner' failed ** (epiphany:5061): CRITICAL **: ephy_spinner_tool_item_set_spinning: assertion `spinner' failed /usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) -------------------------------------------------- Traceback (most recent call last):
+ Trace 124967
self.spark.connect("zoom-changed", lambda w, num_days: self.set_zoom_level(num_days))
self.label.set_text(label)
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 416920 ***