Bug 258216 - KGet Bittorrent does not follow user-specified settings
Summary: KGet Bittorrent does not follow user-specified settings
Status: RESOLVED WORKSFORME
Alias: None
Product: kget
Classification: Applications
Component: torrent (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-11-28 20:31 UTC by lazx888
Modified: 2018-10-27 03:29 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lazx888 2010-11-28 20:31:32 UTC
Version:           unspecified
OS:                Linux

KGet downloads torrents using default settings (port 6881, unlimited upload/download speeds, default directory) - even if settings have been configured differently.

- KGet 2.5.3 (KDE 4.6 beta1)
- Bittorrent (Version 1.0)

Reproducible: Always

Steps to Reproduce:
1) Configure KGet's Bittorrent settings
2) Download torrent
3) Observe KGet does not follow specified Bittorrent settings.

Actual Results:  
Settings not followed.

Expected Results:  
Specified settings should have been used.
Comment 1 Lukas Appelhans 2011-02-06 12:21:07 UTC
Hey!

KGet actually passes the configured port to libktorrent for me... does it show you the correct port in the settings dialog even if you reopen it?

If yes, then this seems to be the fault of libktorrent...

Lukas
Comment 2 Andrew Crouthamel 2018-09-22 01:51:40 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 set the bug status 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 3 Andrew Crouthamel 2018-10-27 03:29:15 UTC
Dear Bug Submitter,

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!