abrt 1.0.8 detected a crash. architecture: i686 Attached file: backtrace cmdline: qbittorrent /tmp/[NNM-Club.ru]_ZverDVD_v2010.3.ISO.torrent component: qbittorrent executable: /usr/bin/qbittorrent kernel: 2.6.32.9-70.fc12.i686.PAE package: qbittorrent-2.2.2-1.fc12 rating: 4 reason: Process /usr/bin/qbittorrent was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) How to reproduce ----- 1. At page http://www.nnm-club.ru/forum/viewtopic.php?p=1608823 i choosed open torrent file with qbittorrent. 2. When app started, in list for download was task which i deleted 3 day ago. Programm start to check both download but i delete again old task. Maybe it happen conflict cause there was nothing to check and i remove torrent file with files on hard disk. 3.
Created attachment 403163 [details] File: backtrace
Created attachment 403258 [details] Patch proposal Here is a patch that should fix the issue. (Disabling peer host name resolution will also work in the meantime, as a workaround).
(In reply to comment #2) > Created an attachment (id=403258) [details] > Patch proposal > > Here is a patch that should fix the issue. (Disabling peer host name resolution > will also work in the meantime, as a workaround). Thanks Chris, I have applied the patch and pushed the package to updates-testing.
qbittorrent-2.2.2-2.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/qbittorrent-2.2.2-2.fc12
qbittorrent-2.2.2-2.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update qbittorrent'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/qbittorrent-2.2.2-2.fc12
qbittorrent-2.2.2-2.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/qbittorrent-2.2.2-2.fc13
qbittorrent-2.2.2-2.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.