I have a feeling my pluggins got buggered when I upgraded. I used the Breezy version on Dapper and forced it, which may or may not have contributed to my problem. Anyway, I can't find the scheduler or the directory scanner, which are the reasons I upgraded. Are these plugins? Thanks!

Maybe it's forced Breezy version on Dapper causing troubles.
Have you tried compiling from source?

I've never actually been able to compile and install anything from source. I've only been using Linux for a couple months.

pkulak wrote:I've never actually been able to compile and install anything from source. I've only been using Linux for a couple months.

You and thousand others, so you're not alone.

Compiling is not that a big deal, it lacks the easy package management of debian, but other than that it should be allright.

First you have to make sure you have the proper packages installed so that configure and make wil be able to run smoothly: (ubuntu naming)
- build essentials
- autoconf/ automake
- xlibs-dev
- kdelibs
- kdelibs4-dev (not sure about this one)
- libqt3-headers
- libqt3-mt-dev

After that you extract the tar package somewhere you like:
tar -zxvf package-nr.tar.gz

And start compiling the program:
cd "directory just extracted"
./configure (let it run till you're back at user@box:~$)
make (could take a while)

Then install it with:
sudo make install
And you should be just fine.

I uninstalled ktorrent, tried to build from source, and I managed to get the configure script to go smoothly, but it blew up during make (as is always the case ). Then I reinstalled the Breezy .deb just for kicks, and now there are no pluggins. I think it's just pointing at the wrong place.

Believe it or not, restarting KDE is what works! (At least for me.) I installed (from source) and didn't get any of the new plugins. Then I logged out of KDE and logged back in, and now I have all of the plugins.

lengau wrote:Believe it or not, restarting KDE is what works! (At least for me.) I installed (from source) and didn't get any of the new plugins. Then I logged out of KDE and logged back in, and now I have all of the plugins.

haha, that worked! Thank you.

You're welcome. That's weird, though. Does anyone know why that happens?

I think you needed to run 'kbuildsycoca' for KDE to find your plugins, so that's why restarting KDE did the trick.

Okay, thanks. Now I see why that would work.