I turned on my computer today, and the only widget styles (apearance & themes --> style) available are cde, ms windows 9x, motif, motif plus, platnium, and sgi. what happened to plastik and the other ones?

well, re-install KDE............and see if they show up...........

I'm no expert, but as I understand it, this a problem that happens after you upgrade to Qt 3.2.3. The KDE styles are compiled against an earlier version of Qt, and the new version no longer recognizes them. I don't know how to fix this: I tried compiling some styles from kde-look.org myself, but configure failed with a message about kdelibs -- which I think means that kdelibs has to be recompiled against the new Qt as well. At least, that's what my googling around on the subject has led me to believe.

So, the fix may to wait until kdeartwork-styles (which is where the KDE styles are) and perhaps other kde components are upgraded. I'm just speculating -- I don't really know enough about all this to be sure.

I had this problem a month or two ago but it's since been fixed in Debian Sid. Here's the bug report:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=254021

yay! thanks!

for all you debian users this fixed it for me and it will for you two if you have unstable and testing in your sources.list):

#apt-get -t unstable install kdeartwork
#/etc/init.d/kdm restart

If you are running the Debian testing distribution, and you have recently upgraded to the new Qt 3.2.3 (by way of dist-upgrade, for example), the only way to get the kde styles to work again is to upgrade to Sid (unstable). You cannot upgrade only the kdeartwork-styles package, because the required version depends on other KDE components that are only available in Sid/unstable.

I'm no expert, but I think that if you have this "disappearing styles" problem in Testing/Sarge, you have three choices:

1. Wait until the Testing (Sarge) distribution is updated with KDE that is compiled using Qt 3.2.3. I have no idea when that will happen (though probably soon).

2. Dist-upgrade to Sid.

3. Compile your own KDE using Konstruct. That's what I'm doing, and though I'm completely inexperienced with compiling, it seems to be going without a hitch. I'm just following the instructions in the readme file.

In order for a package to move from unstable to testing it must:
It must have been in unstable for 10, 5 or 2 days, depending on the urgency of the upload;
It must be compiled and up to date on all architectures it has previously been compiled for in unstable;
It must have fewer release-critical bugs than, or the same number as, the version currently in "testing" (see below for more information);
All of its dependencies must either be satisfiable by packages already in "testing", or be satisfiable by the group of packages which are going to be installed at the same time;
The operation of installing the package into "testing" must not break any packages currently in "testing". (See below for more information.)

see this page for information on using one debian version as your main system, and packages from another verision. http://www.debian.org/doc/manuals/ap...efault-version
if you set your default to testing, and apt-get install -t unstable kdeartwork, it will install all the new deps for you .

Thanks for the extra info.

I have tried "apt-get install -t unstable kdeartwork" and my system tells me that "kdeartwork is already the newest version."

Update:

After a bit more config tweaking, I get this far:

kdeartwork: Depends: kdeartwork-style (>= 4:3.2.3-2) but it is not going to be installed
Depends: kdeartwork-theme-window (>= 4:3.2.3-2) but it is not going to be installed
Depends: kscreensaver (>= 4:3.2.3-2) but it is not going to be installed
E: Broken packages

kscreensaver: Depends: kdelibs4 (>= 4:3.2.3) but 4:3.2.2-2 is to be installed
E: Broken packages