Ktorrent does not work for my user but it does using sudo

[Ponder Stibbons]

Hi!

Until last Saturday ktorrent worked more or less like a charm, but something happened that changed this.
I cannot process any torrents if I don't start the application using sudo.
I've looked at the log file - for both cases, working and not working - and did not see any relevant differences, but I have to admit I did no in-depth analysis, only what I could spot with my "naked eye".
However, I've changed some of the settings with out much success, only thing that works so far, independent of any settings is running the application using sudo.

In my opinion it has to be something network related, because anything else doesn't make much sense. Without sudo no seeders/leechers are found, tracker information (on the Trackers pane) shows not really much ...

So I wondered if anyone here knows what's different running ktorrent with or without using sudo?
Is there a way to get something like debug info, something like changing the logging level in jog4j (I know ktorrent isn't Java, and therefore not log4j)?

[vinnywright]

did your problem start after using sudo to run Ktorrent ,,,,?

because thats what comes to mind first ,,,,,,,,,,run this

vinny@vinny-Bonobo-Extreme:~$ find ~/ -user root

and see what you get .

and/or a

sudo apt-get install --reinstall ktorrent

their is also "qbittorrent" that works nicely on a Qt system .

VINNY

[Rod J]

Yeah, running gui apps like Ktorrent via sudo is a quick way to upset your system ... don't do it!

+1 qBittorrent.

qBittorrent is an excellent torrent app with some really cool features. I gave up on Ktorrent some time ago as it's questionable if it's still being supported/developed.

[Ponder Stibbons]

Thanks for your reply, but that's certainly not the reason.
The problems started before I run ktorrent using sudo. Whyever would I ever do that?
I only did it because I thought I would get more information starting it on the console than what's in the log, and since doing that without sudo didn't output anything in the terminal, I tried sudo. Still the output is exactly the same as in the log.

However I thought that running it as sudo could have changed some file ownerships, but my initial examination showed only stuff not related to ktorrent or not relevant - the zipped logfile parts from the roll over from the sessions I used sudo.

I don't think reinstalling the application will do any good either. ktorrentrc is owned by my user, and all the files in ~/.local/share/ktorrent are owned by my user too, except for the said logfile GZs.
I have even dropped the complete folder (~/.local/share/ktorrent) but it didn't change anything.

Since it shows exactly the same settings running with sudo, I don't think that is the reason either.

[Ponder Stibbons]

Additional info: I tried it again today, and it works without sudo ... somewhat.
It took half an hour to download 5% respectively 35MB, and the application is very unresponsive to commands or actions (e.g. changing what information is displayed in the lower pane.
So I stopped all torrents, which took some time, because of the unresponsiveness of the application. Quit ktorrent and started it again as sudo. After I kicked of the torrents, it only took about 3 minutes to finish all torrents respecitvely the remaining 865MB.

If it wouldn't work using sudo, or show absolutely no progress, or even crash without using sudo, I would already have given up, but so I'm only really annoyed that it performs as it did in the past using sudo, but not without.

Anyway, I will give qBittorrent a try. I'm pessimistic it will show a similar behavior.

[vinnywright]

you should at least try the reinstall I posted and give the find command I posted a run and post it .

VINNY

[Ponder Stibbons]

Vinny, you could trust me, that I'm able to decide what files owned by root are relevant or not, at least I think so.
So here, against my better judgment the output of your command.

chris@odyssey:~$ find ~/ -user root
/home/chris/.kde/share/config/kopeterc
/home/chris/.cache/kio_http/8a88678b7e6cedf7f754a2802a6fffa4a5d5ea7f
/home/chris/.cache/kio_http/e403e8bb01f2e2bd28ab88924b450a493c7ccc18
/home/chris/.cache/kio_http/fe4a12ad54e837198896b7e7a93e9d55840ae9e8
/home/chris/.cache/kio_http/6839cd0d124439a8ea43bf3e8f7b45a3465f1105
/home/chris/.cache/kio_http/5c6cb812b69cfd3fb54aaca9b3d9e91e4b97c27a
/home/chris/.cache/kio_http/3c75c1b796044da2f2278a61744040edac4816e7
/home/chris/.cache/kio_http/a87f032d8329bc95a503f9e3bca8c59166360bda
/home/chris/.cache/kio_http/ee129875deb134cc698d6fee16a5ba672383c62e
/home/chris/.cache/kio_http/71d0eda09933e042ad4410f0189cc5a1c1c21802
/home/chris/.config/QtProject.conf
/home/chris/.local/share/ktorrent/log-4.gz
/home/chris/.local/share/ktorrent/log-6.gz
/home/chris/.local/share/ktorrent/log-2.gz

Do you see anything really relevant, that explains my situation?
BTW I told you, the problem started BEFORE I ever used sudo for ktorrent.
So, how could the behavior not change in any way either to the worse or the better if running it using sudo was the cause for my problems or even worsened them?

[vinnywright]

Vinny, you could trust me, that I'm able to decide what files owned by root are relevant or not, at least I think so.
So here, against my better judgment the output of your command.

chris@odyssey:~$ find ~/ -user root
/home/chris/.kde/share/config/kopeterc
/home/chris/.cache/kio_http/8a88678b7e6cedf7f754a2802a6fffa4a5d5ea7f
/home/chris/.cache/kio_http/e403e8bb01f2e2bd28ab88924b450a493c7ccc18
/home/chris/.cache/kio_http/fe4a12ad54e837198896b7e7a93e9d55840ae9e8
/home/chris/.cache/kio_http/6839cd0d124439a8ea43bf3e8f7b45a3465f1105
/home/chris/.cache/kio_http/5c6cb812b69cfd3fb54aaca9b3d9e91e4b97c27a
/home/chris/.cache/kio_http/3c75c1b796044da2f2278a61744040edac4816e7
/home/chris/.cache/kio_http/a87f032d8329bc95a503f9e3bca8c59166360bda
/home/chris/.cache/kio_http/ee129875deb134cc698d6fee16a5ba672383c62e
/home/chris/.cache/kio_http/71d0eda09933e042ad4410f0189cc5a1c1c21802
/home/chris/.config/QtProject.conf
/home/chris/.local/share/ktorrent/log-4.gz
/home/chris/.local/share/ktorrent/log-6.gz
/home/chris/.local/share/ktorrent/log-2.gz

Do you see anything really relevant, that explains my situation?
BTW I told you, the problem started BEFORE I ever used sudo for ktorrent.
So, how could the behavior not change in any way either to the worse or the better if running it using sudo was the cause for my problems or even worsened them?

well I do not know exactly,,,,,,,but I do know that if root takes ownership of the wrong files in your home it can reek havoc on you ,,,,,,,+ all those files you posted should be owned by you .

did you at least try the reinstall ?

qbittorrent is really nice ,,,,I switched to it as well

VINNY

[vinnywright]

O and as to

"Vinny, you could trust me, that I'm able to decide what files owned by root are relevant or not"

,,,I have no way of knowing your skill level from 1-2 posts.

sorry if I offended you

VINNY

[Ponder Stibbons]

Vinny, I did the reinstall, right after I finished seeding the active torrents.
In my opinion it is impolite not to give back a little, so I did let run its course until the configuration kicked in and terminated seeding.

So, I reinstalled and guess what? No change.
Don't be offended, but in my experience, if software is working with one user, but not another, at least not as expected, a reinstall almost never ever changes anything, because the problem lies somewhere in the difference between the users.
But, and not to be blunt and not to offend, the reinstall seems like a reflex when giving advice, so I almost never give it, and almost never try it myself.

About the files: even if you are theoretically right, I don't bother who owns ...
... cached files, especially if the name gives them away as KDE Input/Output for HTTPS (which shouldn't be related to this issue)
... config files for software I don't really use (QtProject) or haven't used in a long time (Kopete)
... or old logfile chunks
But I did change ownership back to my user (and group) anyway ... without any effect on my problem

BTW, I'm not offended, I'm glad at least someone tries to help.
But, given a little bit of deductive reasoning, even without a broad track record of postings in this forum, being registered on this forum for about 10 years, and having had only two questions, should have given away, that I may not be a god or guru, but not a complete newbie either.

I hope you are not offended now, but that's simply the way I am ... maybe a little bit overconfident of my intelligence, a little bit to pessimistic, and of course last but not least a little bit to sarcastic ... oh, and don't forget, most of the time tired from lack of sleep

So, going to try qBittorent tomorrow ... make that today, it is already way to much after midnight.
Hitting the sack now.

[wonder]

I have a "similar" problem.
With Ktorrent, not connect, not download any (with or with not sudo), but the same file, with bittorrent / transmission, perfect.