Red Hat Bugzilla – Bug 592493
[abrt] crash in qbittorrent-2.2.6-1.fc12: message: Process /usr/bin/qbittorrent was killed by signal 11 (SIGSEGV)
Last modified: 2010-11-04 08:30:11 EDT
abrt 1.0.9 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: qbittorrent component: qbittorrent crash_function: message executable: /usr/bin/qbittorrent global_uuid: 6036ec4d69410c5341bb37e204052d1fb25fc76a kernel: 2.6.32.11-99.fc12.x86_64 package: qbittorrent-2.2.6-1.fc12 rating: 4 reason: Process /usr/bin/qbittorrent was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) How to reproduce ----- 1.qbittorrent worked OK 2. Internet connection was broken 3. qbittorrent crash
Created attachment 414189 [details] File: backtrace
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Hello, The bug can be closed. The problem was fixed and I can not reproduce it on the latest version (2.4.4) also.