GNOME Bugzilla – Bug 427654
crash in Text Editor: opneing a dos formatted ...
Last modified: 2007-04-08 19:48:26 UTC
Version: 2.15.9 What were you doing when the application crashed? opneing a dos formatted textfile 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.18-1.2798.fc6 #1 SMP Mon Oct 16 14:54:20 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 87457792 vsize: 0 resident: 87457792 share: 0 rss: 19181568 rss_rlim: 0 CPU usage: start_time: 1176057465 rtime: 0 utime: 39 stime: 0 cutime:35 cstime: 0 timeout: 4 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 -1208265008 (LWP 3937)] (no debugging symbols found) 0x003af402 in __kernel_vsyscall ()
+ Trace 126099
Thread 1 (Thread -1208265008 (LWP 3937))
----------- .xsession-errors --------------------- libGL warning: 3D driver claims to not support visual 0x4b libGL warning: 3D driver claims to not support visual 0x4b ALSA lib conf.c:3939:(snd_config_expand) Unknown parameters 0 ALSA lib control.c:910:(snd_ctl_open_noupdate) Invalid CTL default:0 ALSA lib conf.c:3939:(snd_config_expand) Unknown parameters 0 ALSA lib control.c:910:(snd_ctl_open_noupdate) Invalid CTL default:0 err:winecfg:on_remove_click unixpath: /media/disk libGL warning: 3D driver claims to not support visual 0x4b libGL warning: 3D driver claims to not support visual 0x4b libGL warning: 3D driver claims to not support visual 0x4b Could not load 'NDCORE.DLL' required by 'WHELP', error=2 libGL warning: 3D driver claims to not support visual 0x4b libGL warning: 3D driver claims to not support visual 0x4b ** (bug-buddy:3939): 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 ***