Bug 433264
Summary: | KDE3's widget styles are not applying | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Sebastian Vahl <fedora> | ||||||||
Component: | kdelibs3 | Assignee: | Than Ngo <than> | ||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | low | Docs Contact: | |||||||||
Priority: | low | ||||||||||
Version: | rawhide | CC: | kevin, ltinkl, rdieter | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | All | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2008-02-18 11:35:54 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Bug Depends On: | |||||||||||
Bug Blocks: | 421891 | ||||||||||
Attachments: |
|
Description
Sebastian Vahl
2008-02-18 08:30:12 UTC
Normally, the logic is supposed to be: * if widgetStyle4 is set in kdeglobals (something I added to allow different themes in KDE 3 and 4, but systemsettings doesn't use it at the moment), KDE 3 uses widgetStyle, KDE 4 uses widgetStyle4 * if widgetStyle4 is not set, KDE 4 also uses widgetStyle, like KDE 3 So setting the style to Polyester is supposed to set it for both KDE 3 and 4. (In reply to comment #1) > So setting the style to Polyester is supposed to set it for both KDE 3 and 4. This was working before (eg. on Fedora-9-Alpha). But now it seems to not work anymore. I attach some screenshots so that you could have a look at yourself. 1. using a clean $HOME/.kde (should be KDE4: oxygen, KDE3: plastik) 2. using polyester (in KDE4 and KDE3) 3. using a modified $HOME/.kde/share/config/kdeglobals with polester I've done a re-login after applying the changed style to get sure that the KDE3 apps are catching this up. Created attachment 295144 [details]
using default widget style with a clean $HOME/.kde
Created attachment 295145 [details]
using polyester
Created attachment 295146 [details]
using polyester with a modified $HOME/.kde/share/config/kdeglobals
I've manually insterted this into $HOME/.kde/share/config/kdeglobals:
widgetStyle=polyester
widgetStyle3=polyester
widgetStyle4=polyester
Hmmm, could this be caused by this change to kdelibs3? * Mon Feb 11 2008 Than Ngo <than redhat com> 3.5.8-24 - make kresources hidden on f9+ Looking at it, I doubt that's it though. But I don't know what's the source of breakage there. (By the way, widgetStyle3 is not used anywhere.) Hmmm, if you remove the KDE 4 Polyester, does KDE 3 then load the KDE 3 one? I suspect KDE 3 may be trying to load the KDE 4 style, which obviously fails. (In reply to comment #8) > Hmmm, if you remove the KDE 4 Polyester, does KDE 3 then load the KDE 3 one? I > suspect KDE 3 may be trying to load the KDE 4 style, which obviously fails. No. It's still not working. I've also downgraded to kdelibs3-3.5.8-22.fc9.i386.rpm (the version used on Fedora-9-Alpha) and removed $HOME/.kde. It's still using the (look as) B2-Theme. Hmm, I think I know what's wrong. Are you using qt-3.3.8b-4.fc9? If so, please downgrade to qt-3.3.8b-3.fc9 until Than commits my fix for bug 433235, that should fix it. (If you're indeed using that broken qt, we can mark this as a duplicate of bug 433235.) Actually, Than just gave me commit access to qt, so I can commit it myself. :-) (In reply to comment #10) > Hmm, I think I know what's wrong. Are you using qt-3.3.8b-4.fc9? If so, please > downgrade to qt-3.3.8b-3.fc9 until Than commits my fix for bug 433235, that > should fix it. That was the problem. After downgrading to qt-3.3.8b-3.fc9 the default widget style is Plastik again and also the switch to polester/polyester3 is working again. (In reply to comment #10) > (If you're indeed using that broken qt, we can mark this as a > duplicate of bug 433235.) Done *** This bug has been marked as a duplicate of 433235 *** |