Bug 581129 - [abrt] crash in qbittorrent-2.2.2-2.fc12: Process /usr/bin/qbittorrent was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in qbittorrent-2.2.2-2.fc12: Process /usr/bin/qbittorrent was ki...
Keywords:
Status: CLOSED DUPLICATE of bug 566387
Alias: None
Product: Fedora
Classification: Fedora
Component: rb_libtorrent
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Peter Gordon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:588684152c7bcec88988d6e54cd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-10 12:05 UTC by ylmzlist
Modified: 2010-04-10 13:40 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-04-10 13:39:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (33.55 KB, text/plain)
2010-04-10 12:05 UTC, ylmzlist
no flags Details

Description ylmzlist 2010-04-10 12:05:17 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: qbittorrent
comment: I haven't done anything indeed. I have a few files which I download currently. Whenever I open qbittorrent, it crashes in a minute.
component: qbittorrent
executable: /usr/bin/qbittorrent
kernel: 2.6.32.10-90.fc12.x86_64
package: qbittorrent-2.2.2-2.fc12
rating: 4
reason: Process /usr/bin/qbittorrent was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 ylmzlist 2010-04-10 12:05:19 UTC
Created attachment 405708 [details]
File: backtrace

Comment 2 leigh scott 2010-04-10 13:05:59 UTC
Try updating to the latest version, it should be in the stable repo now.

https://admin.fedoraproject.org/updates/qbittorrent-2.2.5-1.fc12

Comment 3 leigh scott 2010-04-10 13:10:12 UTC
If that doesn't work try updating rb_libtorrent , it's in updates-testing at the moment.

https://admin.fedoraproject.org/updates/rb_libtorrent-0.14.10-1.fc12

Comment 4 leigh scott 2010-04-10 13:39:37 UTC

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


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