GNOME Bugzilla – Bug 484632
crash in Text Editor: editing
Last modified: 2007-10-16 12:38:55 UTC
Version: 2.18.2 What were you doing when the application crashed? editing Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 67678208 vsize: 67678208 resident: 20582400 share: 12910592 rss: 20582400 rss_rlim: 4294967295 CPU usage: start_time: 1191821418 rtime: 3861 utime: 3712 stime: 149 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227536720 (LWP 2780)] (no debugging symbols found) 0xb7ef57f2 in ?? () from /lib/ld-linux.so.2
+ Trace 168704
Thread 1 (Thread -1227536720 (LWP 2780))
No plugin installed in $HOME. Module versions: pkg-config unavailable Python module versions: - python 2.4.4 - pygtk 2.10.6 (GTK+ 2.10.13) - gnome-python 2.18.2 ----------- .xsession-errors --------------------- closing closing closing closing closing closing ** (gedit:2780): WARNING **: file_system_gnome_vfs=0x82335e0 still has handle=0x86f1020 at finalization which is NOT CANCELLED! (gedit:2780): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GtkFileSystemGnomeVFS' (gedit:2780): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed ** ERROR **: file gtkfilesystemgnomevfs.c: line 3575 (gtk_file_system_handle_gnome_vfs_finalize): assertion failed: (g_hash_table_lookup (system_vfs->handles, handle) != NULL) aborting... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 373226 ***