Screensharing broken on KDE Plasma 6 update

[z411]

Is this a new report?

Yes

System Info

Void 6.6.30_1 x86_64 AuthenticAMD uptodate rrrmmnFFFFFFF

Package(s) Affected

plasma-desktop-6.0.4_1 and related

Does a report exist for this bug with the project's home (upstream) and/or another distro?

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

Expected behaviour

Screensharing under KDE Wayland with PipeWire was working.

Actual behaviour

When attempting to screenshare, the portal window selection dialog appears with no images in it, and when choosing one I get "Failed to connect PipeWire context".

Steps to reproduce

1. Try to screenshare from any application, example: obs
2. Select window or screen to share
3. Get "Failed to connect PipeWire context" error. obs output shows "warning: [pipewire] Failed to start screencast, denied or cancelled by user"

[Luciogi]

start pipewire, wireplumber using runit user service

[SpidFightFR]

start pipewire, wireplumber using runit user service

Hey.. I don't find these as services... I personally run them manually at the start of my plasma session. I have the same problem.

[classabbyamp]

start pipewire, wireplumber using runit user service

the fact that people in the upstream bug report are using systemd and seeing this issue would suggest that it's probably not solved by doing that

[SpidFightFR]

start pipewire, wireplumber using runit user service

the fact that people in the upstream bug report are using systemd and seeing this issue would suggest that it's probably not solved by doing that

so it's an upstream pipewire issue ?

[classabbyamp]

look at the original post in this thread...

[Luciogi]

start pipewire, wireplumber using runit user service

the fact that people in the upstream bug report are using systemd and seeing this issue would suggest that it's probably not solved by doing that

it is workaround, i am using runit user service pipewire, it is working

[SpidFightFR]

start pipewire, wireplumber using runit user service

the fact that people in the upstream bug report are using systemd and seeing this issue would suggest that it's probably not solved by doing that

it is workaround, i am using runit user service pipewire, it is working

How did you get these services? Am i missing something?

[Luciogi]

@SpidFightFR
I took services from https://github.com/Johnnynator/dotfiles/tree/master/.sv

/etc/sv/runsvdir-oggy/run contains following
you just change USER and HOME

#!/bin/sh
export XDG_RUNTIME_DIR="/run/user/1000"
export USER="oggy"
export HOME="/home/oggy"

groups="$(id -Gn "$USER" | tr ' ' ':')"
svdir="$HOME/.sv/service"

exec chpst -u "$USER:$groups" runsvdir "$svdir"

then you can interact with user services

sv start|stop|restart ~/.sv/services/pipewire

Note: git repo does not have service for wireplumber, you have to add it too

[Luciogi]

upstream bug seems to be fixed in this commit
bug: https://bugs.kde.org/show_bug.cgi?id=483137
commit: https://invent.kde.org/plasma/kwin/-/commit/013e69988ffdbed1d3c684a536c0d4b79c7de680

[z411]

Thanks for the quick reply and patch.

So it seems Plasma 6 can't handle having a PipeWire connection start after the session is started. Makes sense as I was also starting PipeWire through session autostart, which is the recommended way to do it in the Void wiki. Maybe we could include runit a user service for PipeWire and edit the wiki to redirect people to use it instead? Seems like a cleaner way to me, and it's probably what most desktop environments expect.

[z411]

@SpidFightFR I took services from https://github.com/Johnnynator/dotfiles/tree/master/.sv

/etc/sv/runsvdir-oggy/run contains following you just change USER and HOME

#!/bin/sh
export XDG_RUNTIME_DIR="/run/user/1000"
export USER="oggy"
export HOME="/home/oggy"

groups="$(id -Gn "$USER" | tr ' ' ':')"
svdir="$HOME/.sv/service"

exec chpst -u "$USER:$groups" runsvdir "$svdir"

then you can interact with user services

sv start|stop|restart ~/.sv/services/pipewire

Note: git repo does not have service for wireplumber, you have to add it too

You can set PipeWire to start WirePlumber and pipewire-pulse as child processes, so I think this service alone should be enough. Thanks a lot.

[classabbyamp]

if you do that you need to kill those processes when stopped:

cat .config/service/pipewire/control/t 
#!/bin/sh
[ -r supervise/pid ] && kill -TERM -$(cat supervise/pid)

[Luciogi]

issue should be closed