GNOME Bugzilla – Bug 456080
crash in Deskbar: Searching for something ...
Last modified: 2007-07-13 19:30:20 UTC
What were you doing when the application crashed? Searching for something with the deskbar (the string was "sk" before it crashed). Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.4 2007-06-29 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 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 (1451 sec old) --------------------- Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. [00000281] main playlist: nothing to play [00000281] main playlist: stopping playback Starting firefox... ***MEMORY-WARNING***: firefox-bin[19736]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this pr VLC media player 0.8.6c Janus ***MEMORY-WARNING***: [21461]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is li Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x32000e0 (VLC media ) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. [00000281] main playlist: nothing to play RUNNING FPXSOUNDDETECT test1 /usr/lib/libpulse-simple.so.0 -------------------------------------------------- TypeError: function takes exactly 0 arguments (1 given)
*** Bug 456082 has been marked as a duplicate of this bug. ***
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 455468 ***