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

            Bug ID: 520620
           Summary: Unable to initiate any screenshares
    Classification: Plasma
           Product: kwin
      Version First unspecified
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: screencasting
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

Created attachment 192588
  --> https://bugs.kde.org/attachment.cgi?id=192588&action=edit
KDE error popup

DESCRIPTION
I'm not entirely sure what caused this to start happening, and I can't find
many reports of the same issue online. I recall OBS Studio beginning to have
issues like this months ago, but I believe screensharing had worked for a while
after then, but I may be misremembering as I rarely screenshare. I'm on Arch
Linux with a Ryzen 5 7500F CPU, Intel Arc B580 GPU, and 32GB DDR5 RAM. I'm
using the linux-cachyos package, but this has also happened when I built my own
kernel. Whenever I attempt to start a screenshare in Discord (installed with
Flatpak), add a screen capture in OBS Studio (installed with the obs-studio-git
package), etc., I will get errors such as the following:

OBS:
```
May 24 21:28:40 pc obs[61334]: info: User added source 'Screen Capture
(PipeWire)' (pipewire-screen-capture-source) to scene 'Scene'
May 24 21:28:40 pc kded6[3126]: Registering ":1.308/StatusNotifierItem" to
system tray
May 24 21:28:40 pc obs[61334]: info: [pipewire] Screencast session created
May 24 21:28:40 pc obs[61334]: info: [pipewire] Asking for monitor and window
May 24 21:28:41 pc obs[61334]: info: [pipewire] source selected, setting up
screencast
May 24 21:28:41 pc obs[61334]: error: [pipewire] Error retrieving pipewire fd:
GDBus.Error:org.freedesktop.DBus.Error.Failed: Couldn't create PipeWire context
May 24 21:28:45 pc obs[61334]: info: PipeWire initialized
May 24 21:28:45 pc kded6[3126]: Registering ":1.309/StatusNotifierItem" to
system tray
May 24 21:28:45 pc obs[61334]: info: [pipewire] Screencast session created
May 24 21:28:45 pc kded6[3126]: Service  ":1.308" unregistered
May 24 21:28:45 pc obs[61334]: info: [pipewire] Asking for monitor and window
May 24 21:28:46 pc obs[61334]: info: [pipewire] source selected, setting up
screencast
May 24 21:28:46 pc obs[61334]: error: [pipewire] Error retrieving pipewire fd:
GDBus.Error:org.freedesktop.DBus.Error.Failed: Couldn't create PipeWire context
```

I have no issues with PipeWire in general - the audio playback and similar
features work fine. The only unique changes I can think of regarding PipeWire
are that I set some PipeWire settings in ~/.config/pipewire per the Arch Wiki
instructions (`default.clock.allowed-rates = [ 32000 44100 48000 88200 96000
192000 ]`, `resample.quality = 10`, etc.) and I use JamesDSP application, but I
believe this has occurred before I began using JamesDSP, and it wouldn't make
sense why JamesDSP would cause this anyway, especially as it seems to not have
been reported for anyone else.

As for Discord, sometimes it produces an error in journalctl and then does
nothing, while other times it just does nothing and doesn't produce any
relevant journalctl content. Currently, attempting to start a screenshare will
display the popup to start a screenshare, but then nothing happens after
selecting one. This is what the journalctl log looks like during this; I don't
know if the KSplash error is relevant, but the logs from Discord are very
common and happen no matter what I do in the app:
```
May 24 21:31:43 pc flatpak[37907]: 21:31:43.662 › Uncaught (in promise)
AbortError: The play() request was interrupted by a call to pause().
https://goo.gl/LdLk22
May 24 21:31:44 pc flatpak[37907]: 21:31:44.191 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:44 pc kded6[3126]: Service  ":1.323" unregistered
May 24 21:31:45 pc flatpak[37907]: 21:31:45.191 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:46 pc flatpak[37907]: 21:31:46.191 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:46 pc flatpak[37907]: 21:31:46.665 › Uncaught (in promise)
AbortError: The play() request was interrupted by a call to pause().
https://goo.gl/LdLk22
May 24 21:31:47 pc flatpak[37907]: 21:31:47.192 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:48 pc flatpak[37907]: 21:31:48.191 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:49 pc flatpak[37907]: 21:31:49.352 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:49 pc flatpak[37907]: 21:31:49.479 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:51 pc flatpak[37907]: 21:31:51.050 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:51 pc flatpak[37907]: 21:31:51.054 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:51 pc flatpak[37907]: 21:31:51.057 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:51 pc flatpak[37907]: 21:31:51.059 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:51 pc flatpak[37907]: 21:31:51.098 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:51 pc flatpak[37907]: 21:31:51.373 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:52 pc flatpak[37907]: 21:31:52.060 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:52 pc flatpak[37907]: 21:31:52.234 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:53 pc flatpak[37907]: 21:31:53.064 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:53 pc flatpak[37907]: 21:31:53.075 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:54 pc flatpak[37907]: 21:31:54.088 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:55 pc flatpak[37907]: 21:31:55.077 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:56 pc flatpak[37907]: 21:31:56.077 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:56 pc flatpak[37907]: 21:31:56.349 › [RTCControlSocket(default)]
Sending heartbeat with last received sequence number: 1
May 24 21:31:56 pc flatpak[37907]: 21:31:56.445 › [RTCControlSocket(default)]
Heartbeat ACK received
May 24 21:31:57 pc flatpak[37907]: 21:31:57.078 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:57 pc flatpak[37907]: 21:31:57.436 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:58 pc flatpak[37907]: 21:31:58.078 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:31:59 pc flatpak[37907]: 21:31:59.078 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:32:00 pc flatpak[37907]: 21:32:00.078 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:32:01 pc flatpak[37907]: 21:32:01.079 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:32:02 pc plasma_waitforname[61751]: WaitForName: Service was not
registered within timeout
May 24 21:32:02 pc systemd[2794]: dbus-:[email protected]: Main
process exited, code=exited, status=1/FAILURE
May 24 21:32:02 pc systemd[2794]: dbus-:[email protected]: Failed
with result 'exit-code'.
May 24 21:32:02 pc flatpak[37907]: 21:32:02.085 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:32:02 pc flatpak[37907]: 21:32:02.210 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:32:02 pc kded6[3126]: Registering ":1.325/StatusNotifierItem" to
system tray
May 24 21:32:03 pc flatpak[37907]: 21:32:03.277 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:32:03 pc flatpak[37907]: 21:32:03.277 › Uncaught (in promise)
AbortError: The play() request was interrupted by a call to pause().
https://goo.gl/LdLk22
May 24 21:32:04 pc flatpak[37907]: 21:32:04.266 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:32:04 pc kded6[3126]: Service  ":1.325" unregistered
May 24 21:32:05 pc flatpak[37907]: 21:32:05.266 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:32:05 pc flatpak[37907]: 21:32:05.691 › Uncaught (in promise)
AbortError: The play() request was interrupted by a call to pause().
https://goo.gl/LdLk22
May 24 21:32:06 pc flatpak[37907]: 21:32:06.267 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:32:07 pc flatpak[37907]: 21:32:07.267 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:32:08 pc flatpak[37907]: 21:32:08.267 ›
AnalyticsTrackImpressionContext function unimplemented
May 24 21:32:09 pc flatpak[37907]: 21:32:09.267 ›
AnalyticsTrackImpressionContext function unimplemented
```

In some cases in Discord, an error dialogue or journalctl entry such as what is
shown in this screenshot would be created: https://ibb.co/TDxqP3bH (I don't
have the log from May 15th because my journalctl entries auto-deleted, I just
took the screenshot at the time to show someone else, but I still have recent
entries and the problem is happening the same way.) I don't know what causes it
to log an error rather than doing nothing. I've kept a copy of my entire
current journalctl and dmesg and could provide them if it'd be useful, but I
wouldn't upload them on the public issue tracker for privacy reasons.

Taking screenshots and screen recordings with the Spectacle application doesn't
encounter any issues at all.

STEPS TO REPRODUCE
1. ??? (Unknown what makes this start happening)
2. Open any app that lets you screenshare
3. Try to screenshare

OBSERVED RESULT

Nothing happens and an error may or may not be logged.

EXPECTED RESULT

A screenshare would start.

SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window): Arch Linux
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1

ADDITIONAL INFORMATION

Operating System: Arch Linux 
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1
Kernel Version: 7.0.9-1-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7500F 6-Core Processor
Memory: 32 GiB of RAM (31.0 GiB usable)
Graphics Processor: Intel® Arc

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

Reply via email to