GNOME Bugzilla – Bug 466805
crash in Gimmie: right clicking on title ...
Last modified: 2007-09-02 22:11:23 UTC
What were you doing when the application crashed? right clicking on title and flipping screens in beryl Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: nuoveXT.2.2 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 (720 sec old) --------------------- ========================================================================== ========================================================================== Forced audio codec: mad Opening audio decoder: [faad] AAC (MPEG2/4 Advanced Audio Coding) AUDIO: 44100 Hz, 2 ch, s16le, 96.0 kbit/6.80% (ratio: 12000->176400) Selected audio codec: [faad] afm: faad (FAAD AAC (MPEG-2/MPEG-4 Audio) decoder) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 672 x 416 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is undefined - no prescaling applied. VO: [xv] 672x416 => 672x416 Planar YV12 A: 0.2 V: 0.0 A-V: 0.234 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 0.3 V: 0.0 A-V: 0.213 ct: 0.002 2/ 2 ??% ??% ??,?% 1 0 A: 0.3 V: 0.1 A-V: 0.172 ct: 0.0 ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 155272
for mi in self.topic.get_context_menu_items():
self._add_templates(menu)
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 413620 ***