Bug 600833 - [abrt] crash in qbittorrent-2.2.8-1.fc13: Process /usr/bin/qbittorrent was killed by signal 11 (SIGSEGV)
[abrt] crash in qbittorrent-2.2.8-1.fc13: Process /usr/bin/qbittorrent was ki...
Status: CLOSED DUPLICATE of bug 581760
Product: Fedora
Classification: Fedora
Component: qbittorrent (Show other bugs)
13
i686 Linux
low Severity medium
: ---
: ---
Assigned To: leigh scott
Fedora Extras Quality Assurance
abrt_hash:e72245dba1150e9f37f8357dc74...
:
: 600836 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-06 05:16 EDT by Martin Weiss
Modified: 2010-07-20 09:34 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-06 07:15:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
File: backtrace (14.78 KB, text/plain)
2010-06-06 05:16 EDT, Martin Weiss
no flags Details

  None (edit)
Description Martin Weiss 2010-06-06 05:16:53 EDT
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: qbittorrent /tmp/ipsc2010.pdf.torrent
comment: just pressed the cross in the upper right corner to turn it off .. two downloads pending at the moment of the crash
component: qbittorrent
executable: /usr/bin/qbittorrent
global_uuid: e72245dba1150e9f37f8357dc741913d648119f5
kernel: 2.6.33.5-112.fc13.i686.PAE
package: qbittorrent-2.2.8-1.fc13
rating: 3
reason: Process /usr/bin/qbittorrent was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Martin Weiss 2010-06-06 05:16:55 EDT
Created attachment 421563 [details]
File: backtrace
Comment 2 leigh scott 2010-06-06 05:31:33 EDT
Reassigned to qt
Comment 3 leigh scott 2010-06-06 07:06:24 EDT
*** Bug 600836 has been marked as a duplicate of this bug. ***
Comment 4 Kevin Kofler 2010-06-06 07:15:56 EDT

*** This bug has been marked as a duplicate of bug 581760 ***

Note You need to log in before you can comment on or make changes to this bug.