GNOME Bugzilla – Bug 515443
crash in Gimmie: nix, hab versucht gimmie...
Last modified: 2008-03-10 11:45:52 UTC
What were you doing when the application crashed? nix, hab versucht gimmie zu starten!!!!! Was soll ich auch getan haben??? 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 Fri Feb 1 04:59:50 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: LiNsta2 Icon Theme: black-white_2-Vista_big 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 (7 sec old) --------------------- self.window_main.set_sensitive(False) FG: canHandleContent application/x-tar) FG: _shouldIntercept(application/x-tar) ERROR: execution of prepared query UpdateFileMove failed due to constraint failed with return code 19 ERROR: execution of prepared query GetMetadata failed due to disk I/O error with return code 10 (file-roller:9356): Gtk-WARNING **: Theme directory scalable/places/22 of theme black-white_2-Vista_big has no size field ERROR: excessive busy count in query DeleteService1 and thread (null) sh: jackd: not found Fenstermanager-Warnung: Ungültiges WM_TRANSIENT_FOR-Fenster 0x75 festgelegt für 0x1403e79 (). sh: disown: not found (gnome-terminal:10024): Gtk-WARNING **: Theme directory scalable/places/22 of theme black-white_2-Vista_big has no size field -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 188670
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 self.item.get_icon(icon_size)
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 ***