Arch Linux

sayskar500

Member

Registered: 2024-02-18

Posts: 4

No KScreen backend found. Please check your KScreen installation.

I got a new external monitor that I connected via HDMI to my laptop which obv. has Arch Linux in it. I tried a few methods while searching for a solution to this problem but none of them have helped out. Also just FYI it has Wayland in it.

Under "Display and Monitor" >> "Display Configuration":

just a message pops up on the top stating : "No KScreen backend found. Please check your KScreen installation"

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,477

Re: No KScreen backend found. Please check your KScreen installation.

Have you tried installing the mentioned kscreen package?

sayskar500

Member

Registered: 2024-02-18

Posts: 4

Re: No KScreen backend found. Please check your KScreen installation.

There is no mention of any particular package mentioned there (which is also another point of confusion for me). Also installed KScreen already once earlier.

Running kscreen-console on the terminal shows:

START: Requesting Config
kscreen.kwayland: Connection to Wayland server timed out.
Received config. Took 3163 milliseconds
Config is invalid, probably backend couldn't load
QObject::connect(QObject, ConfigMonitor::Private): invalid nullptr parameter

Last edited by sayskar500 (2024-02-18 16:35:10)

sayskar500

Member

Registered: 2024-02-18

Posts: 4

Re: No KScreen backend found. Please check your KScreen installation.

upon running kscreen-doctor --info on the terminal I get :

Environment:
  * KSCREEN_BACKEND           : [not set]
  * KSCREEN_BACKEND_INPROCESS : [not set]
  * KSCREEN_LOGGING           : [not set]
Logging to                : [logging disabled]
Preferred KScreen backend : KSC_KWayland.so
Available KScreen backends:
  * KSC_Fake.so: /usr/lib/qt/plugins/kf5/kscreen/KSC_Fake.so
  * KSC_KWayland.so: /usr/lib/qt/plugins/kf5/kscreen/KSC_KWayland.so
  * KSC_QScreen.so: /usr/lib/qt/plugins/kf5/kscreen/KSC_QScreen.so
  * KSC_XRandR.so: /usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR.so
  * KSC_XRandR11.so: /usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR11.so

sayskar500

Member

Registered: 2024-02-18

Posts: 4

Re: No KScreen backend found. Please check your KScreen installation.

[Update]: It seems the bug is happening only for HyperLand and not Plasma (Wayland). Should have investigated it a bit more. Thanks for all the support.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,477

Re: No KScreen backend found. Please check your KScreen installation.

Yes this makes sense, kscreen Wayland only works with KWin as all DE/compositor specific integrations

piotr_dobrogost

Member

Registered: 2025-04-06

Posts: 2

Re: No KScreen backend found. Please check your KScreen installation.

I started getting this error on Plasma 6.3.5 in wayland session after connecting nvidia discrete card (earlier I was using integrated graphics).
Clicking any other section in System Settings and then going back to Display & Monitor "fixes" the problem.

$ kinfo
Operating System: Fedora Linux 42
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.1
Kernel Version: 6.14.9-300.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-8100 CPU @ 3.60GHz
Memory: 3.8 GiB of RAM
Graphics Processor 1: NVIDIA GeForce GTX 1070
Graphics Processor 2: NVIDIA GeForce GTX 1070
Graphics Processor 3: NVIDIA GeForce GTX 1070
Graphics Processor 4: NVIDIA GeForce GTX 1070
Graphics Processor 5: llvmpipe

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,777

Re: No KScreen backend found. Please check your KScreen installation.

Which has nothing to do with the OP's problem. It's also been well over a year.

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,798

Re: No KScreen backend found. Please check your KScreen installation.

piotr_dobrogost, please review the rules on Necro-bumping .

Closing this thread.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky