GNOME Bugzilla – Bug 377889
crash in Text Editor: Datei-Browser - nach obe...
Last modified: 2006-11-22 00:21:41 UTC
Version: 2.15.9 What were you doing when the application crashed? Datei-Browser - nach oben mehrmals ausgewählt Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:36:14 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- mcstransd (PID 1972) wird ausgeführt... mcstrans mcstransd (PID 1972) wird ausgeführt... (gnome-panel:2895): GLib-CRITICAL **: g_string_append: assertion `val != NULL' failed (gnome-panel:2895): GLib-CRITICAL **: g_string_append: assertion `val != NULL' failed ** (nautilus:2897): WARNING **: Keine Beschreibung für MIME-Type »x-special/socket« gefunden (Datei ist »gedit.notebook.2852135516«), teilen Sie dies der gnome-vfs-Mailingliste mit. (gnome-panel:2895): GLib-CRITICAL **: g_string_append: assertion `val != NULL' failed (gnome-panel:2895): GLib-CRITICAL **: g_string_append: assertion `val != NULL' failed ** (bug-buddy:4234): WARNING **: Symbol für Ordner öffnen konnte nicht geladen werden -------------------------------------------------- Memory status: size: 103387136 vsize: 0 resident: 103387136 share: 0 rss: 31432704 rss_rlim: 0 CPU usage: start_time: 1164129566 rtime: 0 utime: 3825 stime: 0 cutime:3711 cstime: 0 timeout: 114 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208886528 (LWP 3327)] (no debugging symbols found) 0x005cb402 in __kernel_vsyscall ()
+ Trace 88330
Thread 1 (Thread -1208886528 (LWP 3327))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 354397 ***