Missing KDE styles after updating to QT on apt repository
I just tried updating to the latest QT on the apt repository (it's a prereq for a lot of the new KDE3.5 stuff and the latest Amarok on apt). When I install the RPM (using apt) I loose all my 5 of the available styles for KDE. It defaults down to CDE styles. So far the only way I've found to fix it is to roll back to the older version of QT... which means I can't install the latest KDE and other QT based apps from the apt repository. Is this happening to anyone else? Is there something I need to do/run/configure after installing the latest QT to be able to keep all my nice KDE styles? C.
Clayton wrote:
I just tried updating to the latest QT on the apt repository (it's a prereq for a lot of the new KDE3.5 stuff and the latest Amarok on apt). When I install the RPM (using apt) I loose all my 5 of the available styles for KDE. It defaults down to CDE styles. So far the only way I've found to fix it is to roll back to the older version of QT... which means I can't install the latest KDE and other QT based apps from the apt repository.
Is this happening to anyone else? Is there something I need to do/run/configure after installing the latest QT to be able to keep all my nice KDE styles?
I take it that no one else is having this problem with the new QT on the apt repositories? I tried installing the new QT on 2 other machines and am getting the exact same results... I loose all KDE styles with the exception of 5 basic ones... CDE, SGI, Platinum, MS Windows 9x, and Motif. The only way I've found to fix this is to remove the new QT and use the original off the DVD... but that means I can't update anything else that's new and dependant on the new QT... yah I know I could compile my own from source, but I don't want to... don't have the patience/time to do it. No one else getting this? Any workaround? C.
On Thursday 27 October 2005 04:03 am, Clayton wrote:
Clayton wrote:
I just tried updating to the latest QT on the apt repository (it's a prereq for a lot of the new KDE3.5 stuff and the latest Amarok on apt). When I install the RPM (using apt) I loose all my 5 of the available styles for KDE. It defaults down to CDE styles. So far the only way I've found to fix it is to roll back to the older version of QT... which means I can't install the latest KDE and other QT based apps from the apt repository.
Is this happening to anyone else? Is there something I need to do/run/configure after installing the latest QT to be able to keep all my nice KDE styles?
I take it that no one else is having this problem with the new QT on the apt repositories? I tried installing the new QT on 2 other machines and am getting the exact same results... I loose all KDE styles with the exception of 5 basic ones... CDE, SGI, Platinum, MS Windows 9x, and Motif. The only way I've found to fix this is to remove the new QT and use the original off the DVD... but that means I can't update anything else that's new and dependant on the new QT... yah I know I could compile my own from source, but I don't want to... don't have the patience/time to do it.
No one else getting this? Any workaround?
C.
Clayton, You are quite likely missing several of the SuSE supplied styles when you updated to 3.5 and many of the SuSE supplied KDE files were removed. Things like kdebase3-SuSE and others which contained many backgrounds, etc. You might still be able to install those along with the 3.5, but I'm guessing there were conflicts that were removed with your apt update. Either live with it until SuSE provides the 3.5 stuff to us or do a bit of compiling to get them back. regards, Lee
You are quite likely missing several of the SuSE supplied styles when you updated to 3.5 and many of the SuSE supplied KDE files were removed. Things like kdebase3-SuSE and others which contained many backgrounds, etc. You might still be able to install those along with the 3.5, but I'm guessing there were conflicts that were removed with your apt update. Either live with it until SuSE provides the 3.5 stuff to us or do a bit of compiling to get them back.
Interesting... I have KDE and QT as found on the 10.0 DVD. If I go to the APT repository and pull in the new QT3 and keep the existing KDE3.4.3 build from the DVD, I loose the styles. If I add in all the KDE3.5 RPMs from the APT repository, I still am missing all the styles. It seems (on my system) to be tied to the new QT3 and regardless of which kde3base-SUSE I have... when I'm using the new QT I loose the styles. What gets me is that no one else seems to have this problem when they update... yet I have it on all my installs of SUSE10.0 (when I update QT and KDE). C.
On Friday 28 October 2005 03:36 am, Clayton wrote:
You are quite likely missing several of the SuSE supplied styles when you updated to 3.5 and many of the SuSE supplied KDE files were removed. Things like kdebase3-SuSE and others which contained many backgrounds, etc. You might still be able to install those along with the 3.5, but I'm guessing there were conflicts that were removed with your apt update. Either live with it until SuSE provides the 3.5 stuff to us or do a bit of compiling to get them back.
Interesting... I have KDE and QT as found on the 10.0 DVD. If I go to the APT repository and pull in the new QT3 and keep the existing KDE3.4.3 build from the DVD, I loose the styles. If I add in all the KDE3.5 RPMs from the APT repository, I still am missing all the styles.
It seems (on my system) to be tied to the new QT3 and regardless of which kde3base-SUSE I have... when I'm using the new QT I loose the styles.
What gets me is that no one else seems to have this problem when they update... yet I have it on all my installs of SUSE10.0 (when I update QT and KDE).
C.
--------------------------------------------------------------------- And how have you gone about determining that the same thing hasn't happened to others? You have also answered your own question. After updating to the new QT, you lose your styles. I only mentioned kdebase3-SuSE as an example, not to say it contained all the styles. As you have found, there are other files which have those things as well. That would tend to say that SuSE's builds include those, wouldn't it? As I mentioned, live with it for the moment or build your own "official" SuSE rpms or wait for SuSE to release them on their mirrors.
Lee
And how have you gone about determining that the same thing hasn't happened to others?
Just the fact that no one else is posting about it. There are enough amature users here and on the [SLE] list - where I've also posted about this problem, and no one has replied - not even with a "me too". That leads me to assume that the problem seems limited - either to a few pro users who know their way around the problem and how to correct it, or just to my particular install.
wouldn't it? As I mentioned, live with it for the moment or build your own "official" SuSE rpms or wait for SuSE to release them on their mirrors.
The live with it is fine... I'm just not updating on my work computer. But... it's still annoying that it's happening,a nd that I don't know why... take for example the problem with the fontconfig build that became available. I worked my way around it after tinkering, and then in a discussion here someone explained the problem... and how to fix it. I learned something from it. I was hoping for the same with the QT thing - I know I could recompile everything, but... Anyway, whatever... if there's no fix... there's no fix. C.
On Friday 28 October 2005 19:08, Clayton wrote:
The live with it is fine... I'm just not updating on my work computer. But... it's still annoying that it's happening,a nd that I don't know why... take for example the problem with the fontconfig build that became available. I worked my way around it after tinkering, and then in a discussion here someone explained the problem... and how to fix it. I learned something from it. I was hoping for the same with the QT thing - I know I could recompile everything, but...
Anyway, whatever... if there's no fix... there's no fix.
Sorry, I didn't really followed the thread, but anyway I will try to give a few suggestions. As far as I understood you have trouble after upgrading to the kde-unstable repository, as there seems to be no such problem with the kde component. Somehow I find it hard to believe that if you do a consistent upgrade there should be such problems (if you want I could try it on mine system, to check if it's really a trouble in your specific installation or a trouble with the repository). Additionally I would recommend to check a few things: -- do you have kdeartwork package installed and if it is of a correct version? -- try to enforce an complete upgrade to the kde-unstable repository. You can achieve it by putting something like this into /etc/apt/preferences ==== cut ==== Package: * Pin: release c=kde-unstable Pin-Priority: 1100 Package: * Pin: release * Pin-Priority: -10 ==== cut ==== and doing "apt-get upgrade" -- you could also try to check that there are no damaged files (rpm -V) or, even better, do a complete reinstall with "apt-get install --reinstall *" -- Best regards, Alexander.
Op vrijdag 28 oktober 2005 21:16, schreef Alexander S. Usov:
-- try to enforce an complete upgrade to the kde-unstable repository. You can achieve it by putting something like this into /etc/apt/preferences ==== cut ==== Package: * Pin: release c=kde-unstable Pin-Priority: 1100
Package: * Pin: release * Pin-Priority: -10 ==== cut ==== and doing "apt-get upgrade"
To the smartpm masters on this list: is this (pinning) possible with smartpm, yum etc? It's a not so known and not so often used apt feature, but sometimes it comes in very handy. -- Richard Bos Without a home the journey is endless
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Richard Bos wrote:
Op vrijdag 28 oktober 2005 21:16, schreef Alexander S. Usov:
-- try to enforce an complete upgrade to the kde-unstable repository. You can achieve it by putting something like this into /etc/apt/preferences ==== cut ==== Package: * Pin: release c=kde-unstable Pin-Priority: 1100
Package: * Pin: release * Pin-Priority: -10 ==== cut ==== and doing "apt-get upgrade"
To the smartpm masters on this list: is this (pinning) possible with smartpm, yum etc? It's a not so known and not so often used apt feature, but sometimes it comes in very handy.
You mean giving priorities to repositories ?
If that's what you mean, then yes, smart can do that very nicely.
smart channel <alias> --set priority=1100
It also works per package. Have a look at the README & FAQ
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
On Friday 28 October 2005 23:11, Richard Bos wrote:
Op vrijdag 28 oktober 2005 21:16, schreef Alexander S. Usov:
-- try to enforce an complete upgrade to the kde-unstable repository. You can achieve it by putting something like this into /etc/apt/preferences ==== cut ==== Package: * Pin: release c=kde-unstable Pin-Priority: 1100
Package: * Pin: release * Pin-Priority: -10 ==== cut ==== and doing "apt-get upgrade"
To the smartpm masters on this list: is this (pinning) possible with smartpm, yum etc? It's a not so known and not so often used apt feature, but sometimes it comes in very handy.
In fact I use it quite often. As for the smart, I believe it knows about priorities. -- Best regards, Alexander.
Am Freitag 28 Oktober 2005 09:36 schrieb Clayton
You are quite likely missing several of the SuSE supplied styles when you updated to 3.5 and many of the SuSE supplied KDE files were removed. Things like kdebase3-SuSE and others which contained many backgrounds, etc. You might still be able to install those along with the 3.5, but I'm guessing there were conflicts that were removed with your apt update. Either live with it until SuSE provides the 3.5 stuff to us or do a bit of compiling to get them back.
Hi Clayton,
Interesting... I have KDE and QT as found on the 10.0 DVD. If I go to the APT repository and pull in the new QT3 and keep the existing KDE3.4.3 build from the DVD, I loose the styles. If I add in all the KDE3.5 RPMs from the APT repository, I still am missing all the styles.
AFAIK the opensource version of the QT-libs only contains the basic styles. Only the commercial version include all styles. So if the packages you installed were linked against the opensource version of QT you only get the basic styles. -- mdc
participants (6)
-
Alexander S. Usov -
BandiPat -
Clayton -
meister＠netz00.com -
Pascal Bleser -
Richard Bos