Bug 361931

Summary: KTorrent immediately segfaults when starting download from .torrent file
Product: [Applications] ktorrent Reporter: Argy M <argymeg>
Component: generalAssignee: Joris Guisson <joris.guisson>
Status: RESOLVED WORKSFORME    
Severity: crash CC: andrius, justin.zobel, pejakm
Priority: NOR    
Version: 5.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Argy M 2016-04-18 13:33:51 UTC 
After upgrading to 5.0.1, opening a .torrent file results in a segfault moments after downloading starts. Every time KTorrent is restarted, whatever little data has been downloaded is normally checked then it crashes again. Downloading the very same torrents via magnet links works fine. Confirmed to also happen in 5.0 and with a clean configuration.

Reproducible: Always

Steps to Reproduce:
Open any .torrent file with KTorrent

Actual Results:  
Connections to trackers are established, disk space is allocated, then the moment downloading starts KTorrent crashes

Expected Results:  
Download should proceed normally.

Although I have recompiled both ktorrent and libktorrent with debug symbols and can get a backtrace for e.g. #361863, the backtrace for this crash simply reads:
Application: KTorrent (ktorrent), signal: Segmentation fault
Comment 1 Daimonion 2017-02-10 22:23:59 UTC 
I can confirm this.
Comment 2 Andrius Štikonas 2017-07-03 21:16:58 UTC 
Do you have libbotan compiled with GMP support?
Comment 3 Justin Zobel 2020-12-02 05:32:59 UTC 
Thank you for the report, Argyris.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thank you.
Comment 4 Bug Janitor Service 2020-12-17 04:34:05 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2021-01-01 04:39:26 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!