GNOME Bugzilla – Bug 477754
crash in Text Editor: Cerrando el programa.
Last modified: 2007-10-28 23:37:39 UTC
Version: 2.18.2 What were you doing when the application crashed? Cerrando el programa. 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: 78499840 vsize: 78499840 resident: 31354880 share: 15949824 rss: 31354880 rss_rlim: 4294967295 CPU usage: start_time: 1158498468 rtime: 658 utime: 625 stime: 33 cutime:0 cstime: 0 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 -1227184464 (LWP 9115)] (no debugging symbols found) 0xb7f527f2 in ?? () from /lib/ld-linux.so.2
+ Trace 163533
Thread 1 (Thread -1227184464 (LWP 9115))
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 --------------------- (gedit:9115): GnomePrint-WARNING **: Could not create filter from description 'frgba': filter 'frgba' is unknown ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 (evince:9609): Gtk-WARNING **: Unsupported unit (evince:9609): Gtk-WARNING **: Unsupported unit (gedit:9115): GnomePrint-CRITICAL **: gnome_print_config_unref: assertion `GNOME_IS_PRINT_CONFIG (config)' failed --------------------------------------------------
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 443083 ***