GNOME Bugzilla – Bug 422339
crash in Gimmie: Clicked on "Linux" butto...
Last modified: 2007-05-12 16:10:56 UTC
What were you doing when the application crashed? Clicked on "Linux" button on the "Gimmie" bar. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human 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 (68840 sec old) --------------------- ========================================================================== ========================================================================== Forced audio codec: mad Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 48000 Hz, 2 ch, s16le, 48.0 kbit/3.12% (ratio: 6000->192000) Selected audio codec: [ffqdm2] afm: ffmpeg (FFmpeg QDM2 audio decoder) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 720 x 480 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is undefined - no prescaling applied. VO: [xv] 720x480 => 720x480 Planar YV12 A: 0.3 V: 0.0 A-V: 0.275 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 0.2 V: 0.0 A-V: 0.161 ct: -0.003 2/ 2 ??% ??% ??,?% 1 0 A: 0.2 V: 0.1 A-V: 0.128 ct: -0.0 ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 121810
icon_size = self._set_item(item, iter, store)
icon = item.get_icon(icon_size)
found = gnomedesktop.find_icon(icon_theme, self.icon_name, icon_size, 0)
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 415965 ***