Hello all,

I am running Slackware 12.2 (which runs kde3), I upgraded it to kde4 using the slackware-current packages (which are still compatible w/ Slackware12.2). I did this to allow me to run ktorrent 3.2.0 which was required by one of the trackers I use.

Anyway on to my question. I have gotten accustomed to using ktshell when I ran ktorrent 2.2.x and I know that it depended on DCOP which is no longer present in kde4. I am far from being a computer programer, but I would like to try and take a stab at fixing ktshell to work w/ d-bus and therefore ktorrent 3.2.x.

I set about trying to find ktorrent on the d-bus last night, but could not find it. In my setup, ktorrent runs on a headless server, and I tried connecting to it with ssh -Y xx.xx.xx.xx to allow me to execute X programs. From there I ran qdbusviewer to attempt to find ktorrent. From what I read on the forum here, it appears that ktorrent registers itself to the bus as org.ktorrent.ktorrent. However, with the viewer I was unable to find ktorrent under the Session Bus (didnt expect to as my ssh session is different than the session running on the server, correct?) nor the System Bus tab(does ktorrent register itself on the system bus?). Perhaps I am doing it wrong, perhaps the Slackware packages are not yet built right.

Anyway, if someone could point me in the right direction I would like to take a stab at fixing ktshell.

Thank you

Why not use the web interface? Or VNC? Or X forwarding?

Why not use the web interface?

Cause I don't like leaving any more ports open to the outside world than I have to.

Or VNC?

I would have to install it on every computer that I wanted to check the status from, some of which run windows. It is easier to just use putty and ssh.

Or X forwarding?

I believe that this would require killing ktorrent locally and then forwarding it to my connected computer? Plus the windows thing above, plus the connecting from the outside from above that. lol

And after all those answers, when I am logged in remotely, I prefer to do everything from the terminal as it is faster over a slow internet link. Heck I usually prefer the terminal for most simple things over a gui.