Bug 17446

Summary: ktorrent hangs on recent kernels
Product: Mageia Reporter: Alexander Krylov <kafra2005>
Component: RPM PackagesAssignee: Nicolas Lécureuil <mageia>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: tmb
Version: 5   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
URL: https://bugzilla.redhat.com/show_bug.cgi?id=1232347
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: KCrash Handler log
gdb.log
KCrash Handler log

Description Alexander Krylov 2016-01-05 08:04:01 CET
Description of problem:
I updated from kernel-desktop-3.19.8-3.mga5 to kernel-desktop-4.1.13-2.mga5 and ktorrent has started hanging while seeding. Its window stops responding and it does nothing; it must be killed with eg 'kill -9'. The hang is long term (it
can last hours).

Version-Release number of selected component (if applicable):
kernel-desktop-4.1.13-2.mga5
ktorrent-4.3.1-6.mga5

How reproducible:
Basically, ktorrent is unusable now and this is the same bug as described at redhat bugzilla, however still valid for Mageia 5 even with kernel 4.1.13.

Reproducible: 

Steps to Reproduce:
Comment 1 Alexander Krylov 2016-01-05 21:00:16 CET
Created attachment 7322 [details]
KCrash Handler log
Comment 2 Alexander Krylov 2016-01-05 21:47:40 CET
Created attachment 7323 [details]
gdb.log
Comment 3 Alexander Krylov 2016-01-05 21:53:10 CET
Created attachment 7324 [details]
KCrash Handler log

Attachment 7322 is obsolete: 0 => 1

Comment 4 David Walser 2016-01-07 00:48:34 CET
Thomas: from the RedHat bug it sounds like a change in the kernel (maybe Fedora's kernel configuration) was what fixed this on their side.

CC: (none) => tmb
Assignee: bugsquad => mageia

Comment 5 Alexander Krylov 2016-01-13 11:54:15 CET
After kernel-desktop-4.1.15-1.mga5 update, ktorrent works without hangs for 1 day and 20 hours in a row, so it's safe to assume that the problem indeed was with kernel-desktop-4.1.13-2.mga5
This bug can be closed for now.
Comment 6 Thomas Backlund 2016-01-13 14:30:19 CET
Closing as fixed then

Status: NEW => RESOLVED
Resolution: (none) => FIXED