GNOME Bugzilla – Bug 455809
crash in Deskbar: I typed "firefox"
Last modified: 2007-07-11 12:31:43 UTC
What were you doing when the application crashed? I typed "firefox" 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: 70000000 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 --------------------- (gnome-panel:22167): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 ***MEMORY-WARNING***: gnome-terminal[23204]: 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***: update-manager[7775]: 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***: gksu[7794]: 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 could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/gnome-power-manager exited with status 0 current dist not found in meta-release file ***MEMORY-WARNING***: gnome-terminal[10376]: 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 checking for valid crashreport now checking for valid crashreport now checking for valid crashreport now -------------------------------------------------- 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 ***