GNOME Bugzilla – Bug 485214
crash in Gimmie:
Last modified: 2007-10-10 14:14:15 UTC
What were you doing when the application crashed? 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-386 #1 Tue Oct 9 09:23:32 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: UbuntuStudio Icon Theme: UbuntuStudio 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 (134 sec old) --------------------- ** (evolution:7374): DEBUG: mailto URL command: evolution %s ** (evolution:7374): DEBUG: mailto URL program: evolution loaded md5.js (evolution:7374): e-data-server-DEBUG: Loading categories from "/home/arsenij/.evolution/categories.xml" (evolution:7374): e-data-server-DEBUG: Loaded 29 categories checking for valid crashreport now Loading Spamassasin as the default junk plugin (pidgin:8462): Bonobo-WARNING **: Leaked a total of 1 refs to 1 bonobo object(s) ** Message: Failed to close thumbnail pixbuf loader for /home/arsenij/Energy Bliss.jpg: Формат файла изображения не распознан ** Message: Failed to close thumbnail pixbuf loader for /home/arsenij/Energy Bliss.jpg: Формат файла изображения не распознан ** Message: Failed to close thumbnail pixbuf loader for /home/arsenij/Energy Bliss.jpg: Формат файла изображения не распознан ** Message: Failed to close thumbnail pixbuf loader for /home/arsenij/Energy Bliss.jpg: Формат файла изображения не распознан (gnome-panel:6034): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -12 and height 27 -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 169136
printer.connect("attributes_changed", lambda p: self.emit("reload"))
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 475020 ***