GNOME Bugzilla – Bug 451795
crash in Text Editor: Trying to install adobe ...
Last modified: 2007-06-28 01:43:27 UTC
Version: 2.15.9 What were you doing when the application crashed? Trying to install adobe reader version 7 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.20-1.2962.fc6 #1 SMP Tue Jun 19 18:24:12 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 132104192 vsize: 0 resident: 132104192 share: 0 rss: 38879232 rss_rlim: 0 CPU usage: start_time: 1182991664 rtime: 0 utime: 42 stime: 0 cutime:34 cstime: 0 timeout: 8 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 -1208625456 (LWP 3785)] (no debugging symbols found) 0x002e8402 in __kernel_vsyscall ()
+ Trace 144255
Thread 1 (Thread -1208625456 (LWP 3785))
----------- .xsession-errors --------------------- rel=nevra_dict['release']) /usr/lib/python2.4/site-packages/yumgui/__init__.py:100: DeprecationWarning: returnHeaderByTuple() will go away in a future version of Yum. hdr = self.rpmdb.returnHeaderByTuple(tup)[0] GUI Setup Completted Mirrordetection : default Yum Version : 3.0.6 (/usr/share/yum-cli) [Yum] Loading "installonlyn" plugin Repository initialization completed in 22.80 seconds added install of mplayerplug-in - 3.40-1.lvn6.i386 to Queue added remove of docbook-style-dsssl - 1.79-4.1.noarch to Queue added remove of docbook-style-xsl - 1.72.0-1.fc6.noarch to Queue added remove of docbook-utils - 0.6.14-8.fc6.noarch to Queue ** (bug-buddy:3788): 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 ***