GNOME Bugzilla – Bug 455451
crash in Deskbar: Typed the letters "ha"
Last modified: 2007-07-11 12:31:29 UTC
What were you doing when the application crashed? Typed the letters "ha" 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: Glossy Icon Theme: gnome 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 (82 sec old) --------------------- alarm-queue.c:542 (load_alarms_for_today) - From Tue Jul 10 10:45:47 2007 to Tue Jul 10 10:45:47 2007 alarm-queue.c:479 (load_alarms) alarm-queue.c:508 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80e4d18: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2008 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80e2788: Received ***MEMORY-WARNING***: update-manager[6358]: 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[6374]: 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 current dist not found in meta-release file 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 -------------------------------------------------- TypeError: function takes exactly 0 arguments (1 given)
*** Bug 455450 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 ***