Hello KDE developers,
First of all, thank you for your work on KDE Plasma and Krfb.
I am encountering a problem with Krfb on a Wayland session and would appreciate any guidance or suggestions on whether this is expected behavior, a configuration issue, or possibly a regression.
System Information
- Fedora 44
- Plasma 6.7.4
- Qt 6.11.2
- Krfb 26.08.0
- Wayland session
Problem Description
Krfb starts successfully and remains running, but it never opens a VNC listening socket.
The expected behavior is that enabling unattended access should cause Krfb to listen on TCP port 5900 (or another VNC port).
Instead:
ss -ltnp | grep 590
returns nothing.
Checking all sockets associated with the Krfb process also shows no TCP listener:
lsof -p <krfb_pid> -i
Krfb owns only Wayland, PipeWire, and D-Bus related descriptors, but no listening TCP socket.
Configuration
My ~/.config/krfbrc contains:
\[FrameBuffer\]
preferredFrameBufferPlugin=pw
\[Security\]
allowUnattendedAccess=true
I have also:
- Disabled unattended access
- Applied settings
- Re-enabled unattended access
- Set a fresh password
- Restarted Krfb
The behavior remains unchanged.
What Appears to Work
Krfb appears to initialize correctly:
- GUI starts
- Process remains running
- PipeWire integration appears active
- Framebuffer plugin loads
- VNC library loads
Relevant observations from lsof:
/usr/lib64/qt6/plugins/krfb/framebuffer/pw.so
/usr/lib64/libvncserver.so.0.9.15
Both are loaded in the running process.
The process also has active PipeWire shared-memory objects and DRM render node access:
/dev/dri/renderD128
memfd:pipewire-
Startup Messages
Every launch produces:
Initializing D-Bus connectivity with XDG Desktop Portal
DBus session created: "/org/freedesktop/portal/desktop/request/..."
Failed to register with host portal QDBusError(
"org.freedesktop.portal.Error.Failed",
"Could not register app ID: Connection already associated with an application ID"
)
eglChooseConfig returned this many configs: 1
No further errors are shown.
Plugin Availability
The expected plugins are installed:
/usr/lib64/qt6/plugins/krfb/events/x11.so
/usr/lib64/qt6/plugins/krfb/events/xdp.so
/usr/lib64/qt6/plugins/krfb/framebuffer/pw.so
/usr/lib64/qt6/
Additional Notes
Earlier, the VNC server appeared to accept connections, but the remote image became frozen and input events no longer worked. After restarting Krfb while troubleshooting, the application continued running but stopped exposing any VNC listening port at all.
Other remote-desktop software on the same machine works correctly, including software using Wayland and PipeWire screen capture, which suggests the desktop capture stack itself is functioning.
Question
Is there any known issue in Krfb 26.08.0 on Wayland that could cause:
- Krfb to run successfully,
- the PipeWire framebuffer backend to initialize,
libvncserverto load,
but prevent the application from creating a VNC listening socket?
If there are additional debug options, logging categories, or commands that would help diagnose why the VNC server component is not being instantiated, I would be happy to provide more information.
Thank you for your time and assistance.