GNOME Bugzilla – Bug 531747
crash in Gimmie: launching stand alone ve...
Last modified: 2008-05-13 08:06:30 UTC
What were you doing when the application crashed? launching stand alone version of gimmie while desperately looking for some kind of configuration menu^^ this error occurs ALL the time, i cannot laun standalone. Screenlet, Gnome Panel, and AWN Applet are working Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.1 2008-04-30 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-17-generic #1 SMP Thu May 1 14:31:33 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Enabled GTK+ Theme: SlicknesS Icon Theme: Crashbit 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 --------------------- ** (GimmieScreenlet.py:7677): WARNING **: IPP request failed with status 1280 ** (GimmieScreenlet.py:7677): WARNING **: IPP request failed with status 1280 ** (gimmie_computer.py:7833): WARNING **: IPP request failed with status 1280 ** (gimmie_computer.py:7833): WARNING **: IPP request failed with status 1280 ** (GimmieScreenlet.py:7677): WARNING **: IPP request failed with status 1280 ** (GimmieScreenlet.py:7677): WARNING **: IPP request failed with status 1280 ** (gimmie_computer.py:7833): WARNING **: IPP request failed with status 1280 ** (gimmie_computer.py:7833): WARNING **: IPP request failed with status 1280 -------------------------------------------------- Gimmie Version: 0.3.0 Traceback (most recent call last):
+ Trace 197034
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 taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 422739 ***