https://bugs.kde.org/show_bug.cgi?id=365040
--- Comment #1 from Sebastian Kügler <se...@kde.org> --- I'm a bit puzzled. kscreen-doctor and the kscreen KCM use the same method to load the backend (GetConfigOperation). GetConfigOperation internally asks the backendmanager for the preferred backend, if that's xrandr, it loads the plugin out of process, any other backend loads in process. On X11, it should never actually hit configoperation.cpp:137 since that's the in-process codepath, are you sure it goes through that function? backendmanager.cpp decides in its ctor which method (InProcess / OutOfProcess it uses), after choosing the backend plugin. Moreover, it works on my system as expected, no KSCREEN_BACKEND env var is set. -- You are receiving this mail because: You are watching all bug changes.
