Bug 362607

Summary:	KTorrent default folder locations are changed to an incorrect path therefore ignored when opening .torrent files or magnet links
Product:	[Applications] ktorrent	Reporter:	Unknown <null>
Component:	general	Assignee:	Joris Guisson <joris.guisson>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	cygnix
Priority:	NOR
Version First Reported In:	5.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	attachment-28302-0.html

Description Unknown 2016-05-03 05:01:28 UTC

KTorrent changes the default folder locations seen in the configuration to an incorrect path, e. g. /home/rodrigo/ to file:/home/rodrigo and therefore are ignored when I open .torrent files or magnet links.

If I enter a new location, KTorrent changes it to an incorrect path adding the file: to the new one.

Changing the values of completeDir=, saveDir=, tempDir= and torrentCopyDir= in ~/.config/ktorrentrc solves this, but if you apply any changes in "Configure KTorrent", the paths are gonna be broken again.

Reproducible: Always

Comment 1 Cygni X 2016-06-03 17:37:52 UTC

It seems like this is the same bug as https://bugs.kde.org/show_bug.cgi?id=362490

Comment 2 Justin Zobel 2022-10-21 00:17:41 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 3 Unknown 2022-10-28 02:55:01 UTC

Created attachment 153248 [details]
attachment-28302-0.html

Hello, I cannot provide further information since I no longer use KDE.
Thank you for your time.

On Thu, 20 Oct 2022 at 21:17, Justin Zobel <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=362607
>
> Justin Zobel <justin.zobel@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |WAITINGFORINFO
>              Status|REPORTED                    |NEEDSINFO
>
> --- Comment #2 from Justin Zobel <justin.zobel@gmail.com> ---
> 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!
>
> --
> You are receiving this mail because:
> You reported the bug.

Comment 4 Bug Janitor Service 2022-11-12 05:14:45 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 2022-11-27 05:12:44 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!