GNOME Bugzilla – Bug 455475
crash in Deskbar: trying to use the Deskba...
Last modified: 2007-07-11 12:31:35 UTC
What were you doing when the application crashed? trying to use the Deskbar to search a program 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: Tangerine 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 (12 sec old) --------------------- Nautilus-Share-Message: spawn arg "usershare" Nautilus-Share-Message: spawn arg "info" Nautilus-Share-Message: end of spawn args; SPAWNING Nautilus-Share-Message: returned from spawn: SUCCESS: Nautilus-Share-Message: exit code 255 Nautilus-Share-Message: ------------------------------------------ Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: usershares are currently disabled ***MEMORY-WARNING***: gksu[5704]: 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 ***MEMORY-WARNING***: gnome-terminal[5751]: 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 ***MEMORY-WARNING***: swiftfox-bin[5794]: 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 -------------------------------------------------- TypeError: function takes exactly 0 arguments (1 given)
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 ***