Upgraded ktorrent to 21.04.1 from current and now I see all my torrents have disappeared (not the first time such thing happened, btw).
"Folder to store torrent information" was ~/.kde/share/apps/ktorrent, and nothing has disappeared from there.
OK, then I restored defaults, folder was set to subfolder in ~/.local, I changed it back to ~/.kde/share/apps/ktorrent, now on restart it pours errors like "Unable to create /home/user1/.kde/share/apps/ktorrent/tor1/torrent: Permission denied"
No idea why permission denied and why try to create an already created directory in first place.
-----
forum search isn't working for me, sorry if the subject was discussed before

Backups are backups; although you don't need so many for torrent.files as they're still* out there, like libraries...

did you try searching: Unable to create /home/?/.kde/share/apps/ktorrent/?: Permission denied

...or, variations?

Edit\add: on the web that is?

Have you verified the owner:group and permissions of that folder? Maybe it's possible that they somehow got changed during your upgrade or move...

1 members found this post helpful.

This sentence makes me to raise an eyebrow.

Seriously? Did you upgraded ONLY the KTorrent from the entire KDE Applications suite?

What happened with the other Applications? What happened with the Frameworks? What happened with Plasma? What happened with Qt5 and its dependencies?

And on what you did that? On Slackware 14.2 ?

I suggest to OP to upgrade entirely to the latest slackware-current, installing every little package (even the casual Apache) OR to explain first on no less than 100000 words what he did and when he did this partial install or programs mix.

Oh, and BTW, if someone migrates even on a full install, from the latest KDE4 to latest Plasma5 the torrents will not be preserved on KTorrent. Tested myself many times.

Yes, torrent files like ~/.kde/share/apps/ktorrent/tor1/torrent are read only. I don't know why ktorrent wants to recreate them though. They were read only before, yet ktorrent was running ok.
Changed permissions to 644 for a couple of torrent files and ktorrent sees lists them now, yet to figure out how to automatically change permissions for a hundred of other files though. Like change perms 644 to all the files in subdirectories, but not to directories.
...
I've done slackpkg install-new and upgrades several kde related packages, not done upgrade-all yet.

there is a "tor" in the torrents dir path. Are those torrents opened by ktorrent called by tor browser?
ktorrent, kget, dolphin, etc, when called by tor browser have their own configuration inside tor browser directory.
Maybe if you run ktorrent "inside" tor browser, it will recognize the torrents files again.

I think tor is short for torrent.
What's interesting, looking at torrent files inside these torXX directories I can see they all have been touched on last ktorrent startup. I compared torrent file with one backed up and diff tells they are identical. I have no idea why this version of ktorrent touches them and why the version of ktorrent that I used before created them read-only.
Anyway it's developers' fault, they should expect such trouble.

Generally things work better for me with the full upgrade-all of -current. I use some Alien packages like ffmpeg that I don't want overwritten so I blacklist Alien for slackpkg. I have had a torrent going in ktorrent for about two years and never had any trouble with it disappearing.

1 members found this post helpful.