GNOME Bugzilla – Bug 412884
crash in Text Editor: I tried to open a text f...
Last modified: 2007-02-28 23:38:53 UTC
Version: 2.15.9 What were you doing when the application crashed? I tried to open a text file from a CDROM Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.19-1.2911.fc6 #1 SMP Sat Feb 10 15:03:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 86265856 vsize: 0 resident: 86265856 share: 0 rss: 19476480 rss_rlim: 0 CPU usage: start_time: 1172626299 rtime: 0 utime: 65 stime: 0 cutime:49 cstime: 0 timeout: 16 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 -1208206784 (LWP 9561)] (no debugging symbols found) 0x00320402 in __kernel_vsyscall ()
+ Trace 114503
Thread 1 (Thread -1208206784 (LWP 9561))
----------- .xsession-errors --------------------- ** Message: No device! ** Message: Exiting connect thread /usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2) /usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2) kdeinit: Got EXT_EXEC 'kbuildsycoca' from launcher. Could not load library! Trying exec.... DCOP: register 'kbuildsycoca' -> number of clients is now 2 kbuildsycoca running... DCOP: register 'anonymous-9564' -> number of clients is now 3 Reusing existing ksycoca DCOP: unregister 'anonymous-9564' DCOP: unregister 'kbuildsycoca' kdeinit: PID 9564 terminated. ** (bug-buddy:9566): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
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 354046 ***