Hide Forgot
abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 12446 bytes cmdline: /usr/bin/lilyterm comment: Replication seems simple and straightforward (see above). component: lilyterm Attached file: coredump, 11821056 bytes crash_function: read_socket executable: /usr/bin/lilyterm kernel: 2.6.35.11-83.fc14.x86_64 package: lilyterm-0.9.8-1.fc13 rating: 4 reason: Process /usr/bin/lilyterm was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1302312540 uid: 500 How to reproduce ----- 1. Launch a new instance of LilyTerm when one is already running. 2. Every time attempted so far, has crashed both instances.
Created attachment 490904 [details] File: backtrace
Works fine here in Xfce, LXDE and GNOME. From the backtrace it looks like you are running KDE. Is this correct? Are you working on a local machine or via SSH?
Package: lilyterm-0.9.8-1.fc13 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Run LilyTerm. 2. Start a second instance of LilyTerm. 3. Watch them both crash. Comment ----- Perviously encountered in KDE, now in GNOME.
(In reply to comment #2) > Works fine here in Xfce, LXDE and GNOME. From the backtrace it looks like you > are running KDE. Is this correct? Are you working on a local machine or via > SSH? (In reply to comment #2) > Works fine here in Xfce, LXDE and GNOME. From the backtrace it looks like you > are running KDE. Is this correct? Are you working on a local machine or via > SSH? Indeed, running it in KDE @localhost. However, just tried it in GNOME, and that also results in a crash. Just added new backtrace.
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