GNOME Bugzilla – Bug 488031
crash in Deskbar: I typed amarok and press...
Last modified: 2007-10-18 21:11:24 UTC
What were you doing when the application crashed? I typed amarok and pressed down arrow immediately Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 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 (20088 sec old) --------------------- ========================================================================== ========================================================================== Forced audio codec: mad Opening audio decoder: [libmad] libmad mpeg audio decoder AUDIO: 48000 Hz, 2 ch, s16le, 112.0 kbit/7.29% (ratio: 14000->192000) Selected audio codec: [mad] afm: libmad (libMAD MPEG layer 1-2-3) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 664 x 274 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is 2.42:1 - prescaling to correct movie aspect. VO: [xv] 664x274 => 664x274 Planar YV12 A: 2.6 V: 0.0 A-V: 2.602 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 2.6 V: 0.0 A-V: 2.571 ct: 0.004 2/ 2 ??% ??% ??,?% 0 0 A: 2.6 V: 0.1 A-V: 2.535 ct: 0.0 ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 171232
reply_handler(*message.get_args_list(**get_args_opts))
reply_handler = lambda hits: self.recieve_hits(qstring, hits, max),
matches.append(TrackerLiveSearchMatch (output))
self.add_all_actions (get_actions_for_uri(result['uri']))
mime = gnomevfs.get_mime_type(uri)
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 474131 ***