GNOME Bugzilla – Bug 520696
crash in Deskbar: just opened quodlibet wi...
Last modified: 2008-03-06 22:35:26 UTC
What were you doing when the application crashed? just opened quodlibet with deskbar <Ctrl-Space> quod <RETURN> Firefox, gnome-term, synaptic, a handful of xterms open. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 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 (11258 sec old) --------------------- (totem-plugin-viewer:20235): GStreamer-CRITICAL **: gst_value_set_fraction: assertion `denominator != 0' failed ** (totem-plugin-viewer:20235): CRITICAL **: gst_video_calculate_display_ratio: assertion `num > 0' failed ** Message: StreamAsFile filename '/home/hakim/.mozilla/firefox/x5fnj1mx.default/Cache/C0D05A7Cd01' ** Message: mBytesStreamed 6127427 ** Message: DestroyStream reason 0 ** Message: URLNotify URL 'http://diveintomark.org/public/2006/07/20060704.mp4' reason 0 ** Message: Viewer state: STOPPED ** Message: totem_embedded_open_internal 'file:///home/hakim/.mozilla/firefox/x5fnj1mx.default/Cache/C0D05A7Cd01' is-browser-stream 0 start-play 0 ** Message: BEFORE _open ** Message: AFTER _open (ret: 1) JACK tmpdir identified as [/dev/shm] ** Message: emitting signal ** Message: ButtonPress signal received ** Message: ButtonPress -------------------------------------------------- Traceback (most recent call last):
+ Trace 191482
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 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 475351 ***