https://bugs.kde.org/show_bug.cgi?id=520620
--- Comment #9 from [email protected] --- (In reply to Harald Sitter from comment #8) > Can you try without that pipewire folder. I did that, and yes - removing that config folder and running `systemctl --user restart pipewire` and `systemctl --user restart pipewire-pulse` fixes this issue. Adding the folder back and running the same commands causes the issue to occur again. I'm not sure what it is in my configuration that causes this. The only things that I believed I changed are the following: default.clock.rate = 48000 default.clock.allowed-rates = [ 32000 44100 48000 88200 96000 192000 ] default.clock.quantum = 512 default.clock.min-quantum = 144 default.clock.max-quantum = 2048 And: stream.properties = { resample.quality = 10 } The other portions of the config were already there by default. I made my changes based on https://wiki.archlinux.org/title/PipeWire#Changing_the_allowed_sample_rate(s), https://wiki.archlinux.org/title/PipeWire#Lossless, and https://wiki.archlinux.org/title/PipeWire#Resampling. As stated on the Arch wiki: > Consult your hardware manual for supported values of your DAC. Supported > rates by the kernel driver codec are listed with the following command. > $ grep -E 'Codec|Audio Output|rates' /proc/asound/card*/codec#* I got the following output from the command and used it to set the sample rates: https://pastebin.com/H3MLqx6Y. (My audio is coming from the Realtek card, not Intel.) To see if the sampling rate settings were the issue, I tried removing the settings regarding the audio sample rate from the config without removing the whole folder and then restarting it. This time, attempting to start a screencast didn't show any preview of the windows, and created an error dialog again (previously, the error dialogs would appear when this issue started then stopped appearing on their own without the issue changing, and earlier I had never made any changes to the config when this issue started or when they stopped appearing): https://ibb.co/dw2QjQMj https://ibb.co/tp5bhW5h Again, these settings only concern the audio sampling rate, and audio playback is still entirely functional. I don't quite understand why these settings regarding audio fidelity are seemingly causing no issues with audio at all but have broken screencasting, especially when Spectacle still works fine for both screenshots and screen recording. I don't know if the issue is with the KDE portal, Pipewire, or something else, but it's been very difficult to identify and so I've reported it here to hopefully find the cause of the bug so that it can be fixed in case anyone else would experience it. This is everything that has been logged in journalctl recently (some of these are probably irrelevant, but still posting the larger snippet just in case; I redacted some unrelated file names and similar details): https://pastebin.com/QcN5Hhsc. I believe that the time I opened Konsole and Spectacle was when I first tested removing the `pipewire` folder; `/home/user/Downloads/a/pipewire` is where I temporarily copied the folder to while testing. Some of the logs are obviously just from restarting Spectacle, but some of the others might be useful. The pacman command is from running `sudo pacman -S xdg-desktop-portal-kde` to double check that the package is actually installed correctly, which it was; I didn't continue to reinstall it. The `systemctl status` logs for pipewire, pipewire-pulse, and wireplumber also do not appear to be anything very useful: https://pastebin.com/8n7w278V. Here's the logs for the xdg-desktop-portal services: https://pastebin.com/q3Tm7btq I don't remember exactly when this issue first occurred, but I believe that my issues with OBS either predate when I changed the configuration or occurred a while after. I don't remember exactly how long it was since I first encountered this issue, when I successfully screencasted, or when I changed these settings. I did notice that, according to the file metadata, `~/.config/pipewire/client.conf.d/resample.conf` was created Thursday, January 15, 2026 4:17:35 PM and modified Friday, April 17, 2026 5:23:20 PM. It seems that the last OBS screen recording with any useful content that I saved was captured on March 2nd 2026, but I also apparently have an OBS recording on April 2nd saved that only contains a still frame and speaking into the microphone to test if it is working (I don't remember why I recorded or saved this). My initial issues with OBS were that the option to record the screen had entirely disappeared from the OBS app, and I believe that later the option was visible again but nothing would actually record (same as with attempting to screencast, etc.) The earliest troubleshooting searches I have in my browsing history for the OBS issue were in April: https://ibb.co/5X8LL6zY -- You are receiving this mail because: You are watching all bug changes.
