abrt version: 1.1.5 architecture: x86_64 Attached file: backtrace cmdline: gedit libdrm-poulsbo.spec comment: This should open somefile.txt in a tab of the already-open gedit, but instead it just produces 'Segmentation fault (core dumped)' at the console. The running gedit process is not affected. component: gedit executable: /usr/bin/gedit global_uuid: 852c1290c8c9ddd701a2a78be7acc5e40bc7e815 kernel: 2.6.35-0.36.rc4.git5.fc14.x86_64 package: gedit-1:2.31.3-1.fc14 rating: 3 reason: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Rawhide) time: 1279224822 uid: 501 How to reproduce ----- 1. Run gedit somefile.txt from a console while gedit is already open 2. 3.
Created attachment 432212 [details] File: backtrace
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping