GNOME Bugzilla – Bug 449223
crash in Text Editor: closing it. (alt+f4)
Last modified: 2007-06-21 21:43:57 UTC
Version: 2.18.0 What were you doing when the application crashed? closing it. (alt+f4) Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 79192064 vsize: 79192064 resident: 27512832 share: 19914752 rss: 27512832 rss_rlim: 4294967295 CPU usage: start_time: 1182277153 rtime: 567 utime: 543 stime: 24 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208170784 (LWP 13581)] (no debugging symbols found) 0x00604402 in __kernel_vsyscall ()
+ Trace 142221
Thread 1 (Thread -1208170784 (LWP 13581))
No plugin installed in $HOME. ----------- .xsession-errors (54 sec old) --------------------- localuser:dspadaro being added to access control list SESSION_MANAGER=local/hendrix.occamnetworks.com:/tmp/.ICE-unix/2634 (gnome-terminal:3097): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (gnome-terminal:3097): Vte-WARNING **: No handler for control sequence `device-control-string' defined. libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files ** (gedit:13581): WARNING **: IPP request failed with status 1030 Model not found, discarding config ** (gedit:13581): WARNING **: could not set the value of Settings.Document.Filter, node not found --------------------------------------------------
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 ***