GNOME Bugzilla – Bug 504925
crash in Gimmie: Starting from a term.
Last modified: 2008-03-10 13:07:11 UTC
What were you doing when the application crashed? Starting from a term. 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-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome 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 (1926 sec old) --------------------- (rhythmbox:25708): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed (rhythmbox:25708): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed (rhythmbox:25708): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed (rhythmbox:25708): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed (rhythmbox:25708): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed (rhythmbox:25708): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed (rhythmbox:25708): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed ...Too much output, ignoring rest... -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 182565
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 ***