https://bugs.kde.org/show_bug.cgi?id=413476

            Bug ID: 413476
           Summary: Wayland/Pipewire segfault on connection
           Product: krfb
           Version: 19.08.1
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: grundleb...@googlemail.com
          Reporter: t...@r.je
  Target Milestone: ---

SUMMARY

When a connection is received, Krfb crashes when using wayland/pw plugin.

STEPS TO REPRODUCE
1. Run Krfb on Wayland
2. Try to connect with KRDC

OBSERVED RESULT

Krfb accepts the login, asks for authorisation and once authorisation is
granted, Krfb crashes. Log as follows:

$ krfb
found plugin at  "/usr/lib/qt/plugins/krfb/krfb_framebuffer_xcb.so"
Loaded plugin with name  "xcb"
found plugin at  "/usr/lib/qt/plugins/krfb/krfb_framebuffer_pw.so"
Loaded plugin with name  "pw"
found plugin at  "/usr/lib/qt/plugins/krfb/krfb_framebuffer_qt.so"
Loaded plugin with name  "qt"
Using FrameBuffer: "pw"
Initializing D-Bus connectivity with XDG Desktop Portal
DBus session created: 
"/org/freedesktop/portal/desktop/request/1_49/krfb2951929398"
Starting server. Listen port: 5900 Listen Address: "0.0.0.0" Password enabled:
true
Couldn't select sources for the screen-casting session
about to start authentication
found plugin at  "/usr/lib/qt/plugins/krfb/krfb_events_x11.so"
Loaded plugin with name  "x11"
found plugin at  "/usr/lib/qt/plugins/krfb/krfb_events_xdp.so"
Loaded plugin with name  "xdp"
Segmentation fault (core dumped)


EXPECTED RESULT

Linux/KDE Plasma: Arch / 5.17.1
(available in About System)
KDE Plasma Version: 5.17.1
KDE Frameworks Version: 5.63.0
Qt Version: Qt5 5.13.1
Krfb version: 19.8.2 (not in the list above)

ADDITIONAL INFORMATION

It is very difficult to find documentation on what is required to get this
working on wayland so I may be missing something.

On the host, I have installed pipewire and started the service. The log says
says "Couldn't select sources for the screen-casting session" which suggests I
might be missing something.

I am also running 2x 4k displays with a desktop resolution of 7680x2160 which
may be a higher resolution that something in the stack supports.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to