Bug 362513

Summary:	ktorrent4 config settings are not migrated to ktorrent5. New configuration settings are ignored as well.
Product:	[Applications] ktorrent	Reporter:	Vadym Krevs <vkrevs>
Component:	general	Assignee:	Joris Guisson <joris.guisson>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	5.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Vadym Krevs 2016-04-30 19:37:56 UTC

Just upgraded to ktorrent 5.0 from OBS on openSUSE 42.1 Leap. 

Started ktorrent. It lost all the configuration settings from ktorrent4. Never mind. Opened Settings->Configure Ktorrent->Application. Changed "Default save location" and "Copy saved torrent files"  to what I need it to be. Attempted to open an existing torrent file.  The open torrent dialog offers to save the file to $HOME ignoring the path in "Default save location".  Nevermind that, manually navigated to the right folder, and clicked ok. Got an error message "Could not write to file:///<path from Copy saved torrent files>/name of torrent file", even though the "Copy saved torrent files" location already exists and is writable. 

Restarted ktorrent. Same behaviour. 




Reproducible: Always

Steps to Reproduce:
1. See details section
2.
3.

Actual Results:  
See details section

Expected Results:  
old configuration settings are automatically migrated to the new ktorrent version. Any changes to the configfuration settings in Settings->Configure Ktorrent like default save location are not ignored.

Comment 1 Justin Zobel 2022-10-20 23:54:39 UTC

Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!

Comment 2 Bug Janitor Service 2022-11-04 05:07:37 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 3 Bug Janitor Service 2022-11-19 05:15:02 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!