[KScreen] [Bug 365040] kscreen KCM cannot be used if KSCREEN_BACKEND is not set

https://bugs.kde.org/show_bug.cgi?id=365040 --- Comment #5 from Allan Sandfeld --- carewolf@twilight% systemsettings5 org.kde.kactivities.lib.core: Killing the consumer kscreen: Failed to request

[KScreen] [Bug 365040] kscreen KCM cannot be used if KSCREEN_BACKEND is not set

https://bugs.kde.org/show_bug.cgi?id=365040 Allan Sandfeld changed: What|Removed |Added CC||k...@carewolf.com ---

[KScreen] [Bug 365040] kscreen KCM cannot be used if KSCREEN_BACKEND is not set

https://bugs.kde.org/show_bug.cgi?id=365040 Andreas Cord-Landwehr changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[KScreen] [Bug 365040] kscreen KCM cannot be used if KSCREEN_BACKEND is not set

https://bugs.kde.org/show_bug.cgi?id=365040 --- Comment #2 from Andreas Cord-Landwehr --- You are right; I looked at the wrong code location. Here is a probably more verbose output. I now generated a backtrace for getting the debug message: kcmshell5(30793)/(kscreen)

[KScreen] [Bug 365040] kscreen KCM cannot be used if KSCREEN_BACKEND is not set

https://bugs.kde.org/show_bug.cgi?id=365040 --- Comment #1 from Sebastian Kügler --- 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