GNOME Bugzilla – Bug 507806
crash in Gimmie: ending its process from ...
Last modified: 2008-01-09 20:50:55 UTC
What were you doing when the application crashed? ending its process from system monitor...not responding to 'end process' 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: aero-clone Icon Theme: Aero 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 (3009 sec old) --------------------- 10047] 10:10:44: DEBUG: Trouble: can't seek any further.. 10047] 10:10:44: ERROR: Could not seek to end position 10047] 10:10:44: ERROR: *** no tag loader for type 730 (movie) 10047] 10:10:44: DEBUG: Trouble: can't seek any further.. 10047] 10:10:44: ERROR: Could not seek to end position 10047] 10:10:44: ERROR: *** no tag loader for type 730 (movie) 10047] 10:10:44: DEBUG: Trouble: can't seek any further.. 10047] 10:10:44: ERROR: Could not seek to end position 10047] 10:10:44: ERROR: *** no tag loader for type 730 (movie) 10047] 10:10:44: DEBUG: Trouble: can't seek any further.. 10047] 10:10:44: ERROR: Could not seek to end position 10047] 10:10:44: ERROR: *** no tag loader for type 730 (movie) 10047] 10:10:44: DEBUG: Trouble: can't seek any further.. ...Too much output, ignoring rest... -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 184369
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_factory.transparentize(scaled, 40))
pix[3] = min(int(pix[3]), 255 - (percent * 0.01 * 255))
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 417988 ***