GNOME Bugzilla – Bug 424117
crash in Gimmie: Clicking RMB over Gimmie
Last modified: 2007-03-29 22:30:49 UTC
What were you doing when the application crashed? Clicking RMB over Gimmie Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled 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 (12789 sec old) --------------------- LAVF_header: av_find_stream_info() failed AAC file format detected. ========================================================================== Forced audio codec: mad Opening audio decoder: [faad] AAC (MPEG2/4 Advanced Audio Coding) FAAD: compressed input bitrate missing, assuming 128kbit/s! AUDIO: 44100 Hz, 2 ch, s16le, 128.0 kbit/9.07% (ratio: 16000->176400) Selected audio codec: [faad] afm: faad (FAAD AAC (MPEG-2/MPEG-4 Audio) decoder) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Video: no video Starting playback... A: 1.3 (01.3) of 1732.2 (28:52.2) ??,?% A: 1.4 (01.3) of 1732.2 (28:52.2) ??,?% A: 1.4 (01.4) of 1732.2 (28:52.2) ?? A: 18.3 (18.2) of 1732.2 (28:52.2) 7.5% A: 18.3 (18.2) of 1732.2 (28:52.2) 7.5% A: 18.3 (18.3) of 1732.2 (28:52.2) 7 ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 123210
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 ***