GNOME Bugzilla – Bug 515338
crash in Gimmie: Starting it up. :)
Last modified: 2008-03-10 12:00:47 UTC
What were you doing when the application crashed? Starting it up. :) 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-rt #1 SMP PREEMPT RT Fri Feb 1 00:55:45 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Enabled GTK+ Theme: Aurora-Midnight Icon Theme: gperfection2 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 (162996 sec old) --------------------- kio_http_debug: WARNING: (14586)createCacheEntry: opening /var/tmp/kdecache-paul/http/p/prguitarman.livejournal.com_data_rss_4e504c69.new failed. QFile::open: No file name specified kio_http_debug: WARNING: (14587)createCacheEntry: opening /var/tmp/kdecache-paul/http/t/technocollie.livejournal.com_data_rss_20087f9f.new failed. ** (claws-mail:8394): WARNING **: [21:39:47] IMAP error: stream error ** (claws-mail:8394): WARNING **: [21:39:47] Can't connect to IMAP4 server: localhost:8143 (claws-mail:8394): Claws-Mail-CRITICAL **: imap_scan_required: assertion `session != NULL' failed (claws-mail:8394): Claws-Mail-CRITICAL **: imap_scan_required: assertion `session != NULL' failed ...Too much output, ignoring rest... -------------------------------------------------- Gimmie Version: 0.3.0 Traceback (most recent call last):
+ Trace 188607
self.add_item(i, target_height)
running = RunningItemTile(i, target_height, self.gravity)
self._reload(item)
self.icons = self._load_icons(item, self.target_height)
icon = item.get_icon(target_height)
return icon_factory.load_icon(found, icon_size)
assert icon_value, "No icon to load!"
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 495707 ***