For out-of-process backends, only the KSCREEN_BACKEND environment
variable is considered while loading. If none is set, fall-back
to the preferred backend.
BUG: 365040
For out-of-process backends, only the KSCREEN_BACKEND environment
variable is considered while loading. If none is set, fall-back
to the preferred backend.
BUG: 365040
Manual testing. Adding this fallback makes
"kcmshell5 kscreen" show again with working KCM instead of a
"No kscreen backend found..." message.
No Linters Available |
No Unit Test Coverage |
I figured out that this "fix" is wrong, since there is already code handling an empty backend name string by falling back to the preferred backend.
Will investigate why that code is not triggered for me.