Registered Member
|
I have a few questions about how KDE4 Window Decorations are handled.
1. How do I uninstall a theme once it is installed? Can I uninstall a default theme? 2. When compiling a theme (from kde-look.org), the theme compiles and says it installs, but then it is not available from the Window Decoration section of System Settings. Is there anyway I can debug the reason why? 3. When I look at a theme's source (different from the theme mentioned in question #2), I notice there are multiple versions of the theme. Looking through the directory structure, I see different images for the same button under different directories. This is what leads me to believe that there are multiple version of the same theme. How can I select these different versions of the same theme? I've looked through the forum and kde-look.org and have googled and searched the source of the themes I'm wanting to use and am just coming up emtpy-handed. Any help or nudge in the right direction is certainly appreciated. Thanks! mw |
Administrator
|
Moved to KWin forum.
1) Uninstalling a default theme is not possible apart from through your distributions package manager. Uninstalling third party themes you have installed should be possible by running "make uninstall" in the source compilation directory. 2) Try running "kbuildsycoca4 --noincremental" after (un)installing a theme. 3) These will likely be for different resolution screens / decoration sizes, or customisation options available through the "Configure" button beside the theme drop down.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Running kbuildsycoca4 --noincremental is what I needed.
I had to uninstall a theme, then install the "mod" version of that same theme. Also, the different directories I referred to in my previous post were the different configurations under the "Button" tab in the Window Decoration section of kconfig. Thanks, bcooksley! |
Registered Member
|
I'd highly recommend that you use Portage for installing themes and other KDE packages. The reasons include that it makes uninstalling it easier, prevents file collisions, and ensures that it is in a workable state.
If there is no ebuild available in the official tree or the overlays, writing your own ebuild is extremely easy for a KDE-based application. This is pretty much all you need if it uses standard "cmake - make - make install" procedure:
Just change the download URL and you're pretty much all set.
Get problems solved faster - get reply notifications through Jabber!
|
Registered Member
|
Thanks Alec!
I would always like to use and ebuild, when available. Is this something that I could submit to the KDE team and have them put this into the official portage tree? |
Registered Member
|
I'm not sure... The best thing to do would probably be to ask at #gentoo-kde.
Get problems solved faster - get reply notifications through Jabber!
|
Registered users: bancha, Bing [Bot], Google [Bot], Sogou [Bot]