What is the problem?
KDE does not respect other window manager/DE settings.
Is there a way to safely run KDE alongside other window managers without having to reconfigure them every time after finishing my testing with KDE?
Background
My user's main desktops are primarily xfce (4.6, 4.8, 4.10) and Unity.
- I frequently test multiple Window Managers(fluxbox, enlightenment, unity, gnome, etc). Only KDE causes me problems when returning to another WM once I am done testing some KDE functionality.
What I have done to fix this?
When returning to a WM other than KDE, I find that I have to delete config(specifically *gtk files) files in order to return my other WM's to their default settings.
What answer am I looking for?
- Are there any file permissions that I can set to prevent KDE from breaking my other WM settings?
- Is there a way to determine what files in my home directory that KDE touches and modifies? That might help my narrow down my issue.
- I am amenable to building a login script to correct anything that KDE has broken. For three users, this would be acceptable. This doesn't scale to 50 users.
What can I do to safely test KDE and return to my default window manager without having to continually restore my configuration?
Why is this important?
Here is a use-case that is causing me problems:
I have a user(think C-level exec) that likes to change back and forth between KDE and xfce(among other WMs). How can I configure their profile so they do not get KDE window decorations when they decide to move back to xfce?
As it stands, I have been unable to prevent an xfce session from being totally mangled after a user logged into a KDE session.
.kde
and logs? If so, consider filing a bug against KDE