GNOME Bugzilla – Bug 456256
crash in Deskbar: Per Short-Cut die Anwend...
Last modified: 2007-07-13 19:29:40 UTC
What were you doing when the application crashed? Per Short-Cut die Anwendung geöffnet und einen Suchbegriff eingegeben. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.5 2007-07-11 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-7-generic #1 SMP Mon Jun 25 17:07:55 GMT 2007 x86_64 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 (26 sec old) --------------------- ***MEMORY-WARNING***: gnome-terminal[26016]: 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 ** (nautilus:5816): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »public«), teilen Sie dies der gnome-vfs-Mailingliste mit. ***MEMORY-WARNING***: gnome-terminal[26098]: 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***: gnome-terminal[26146]: 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 --- Hash table keys for warning below: --> file:///home/navi (nautilus:26160): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) ***MEMORY-WARNING***: gnome-terminal[26234]: 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 -------------------------------------------------- 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 ***