GNOME Bugzilla – Bug 491231
crash in Deskbar: i did a search for WMA, ...
Last modified: 2007-10-29 01:20:09 UTC
What were you doing when the application crashed? i did a search for WMA, pressed enter and this pop up came up.... odd thing is the search worked, firefox loaded and yahoo did the search... which was what i wanted, :) 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 (551 sec old) --------------------- Can't open joystick device /dev/input/js0: No such file or directory Can't init input joystick mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Could not open/initialize audio device -> no sound. LAME: Can't get "TERM" environment string. LAME 3.97 32bits (http://www.mp3dev.org/) CPU features: MMX (ASM used), SSE, SSE2 Using polyphase lowpass filter, transition band: 16538 Hz - 17071 Hz Encoding audiodump.wav to 02_how_does_it_make_you_feel-.wma Encoding as 44.1 kHz 128 kbps stereo MPEG-1 Layer III (11x) qval=3 Frame | CPU time/estim | REAL time/estim | play/CPU | ETA 0/ ( 0%)| 0:00/ : | 0:00/ : | x| : 0/12986 ( 0%)| 0:00/ 0:00| 0:00/ 0:00| 0.0000x| 0:00 50/12986 ( 0%)| 0:00/ 0:15| 0:00 ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 173553
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
if text.startswith(query):
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 475351 ***