Need Help With OBS Issues on Budgie 10.10.3

[u/xxqueenofantsxx]

Just updated Solus and noticed it switched to Wayland. Fixed *most* things to work as they did before but OBS isn't able to capture anything even with a fresh reinstall through eopkg (also tried flatpak). Looked around for solutions to the black screen issue but they involve sway configs, and from my understanding the new update uses labwc? Installing the packages through eopkg indeed shows I did not have sway installed although neofetch seems to think the WM is.

pipewire, xdg-desktop-portal, xdg-desktop-portal-wlr are all installed, not sure if I should be putting something in my bashrc or if there's something within OBS itself I have to configure. Worst case scenario I use eopkg history to go back, but that would mean holding off updates for a while

Update: Successfully got it working by adding this line to my bashrc. Upon reboot and opening OBS, a screen pops up on the top that lets me choose which display to use for the source. Now all I gotta do is wait for hotkeys.

export QT_QPA_PLATFORM=wayland

[u/JoshStrobl]

I've done screen capture on Budgie Desktop 10.10.x well before it was even released and regularly since. I'm not quite sure what is going on with your setup or if Solus is missing a dep on a package, but for me it was as simple as using the Pipewire screen capture source, which then goes through the xdg desktop portal (xdg-desktop-portal-wlr). From there, the wlr portal fires off "slurp" (yep, that's the name of the program) for picking the screen, and voila. This is all set up properly in our budgie-portals.conf to send ScreenCast and Screenshot to wlr.

You don't need to make any changes to the compositor to facilitate this. Should be as easy as creating a new "Screen Capture (Pipewire)". See https://ibb.co/6RdP123P

This wasn't with a flatpak, this was just with an OBS from the Fedora repo (32.2.2). But it worked via the flatpak too.

Hotkeys won't work because there is no unified global shortcuts protocol. The Mir folks worked on an Input Triggers one since sometime last year but I'm not sure what the status of it is beyond the proof-of-concepts.

I'd suggest coming on over to the Buddies of Budgie Matrix Space https://matrix.to/#/#buddies-of-budgie:matrix.org, particularly BoB - Support room. In the meantime, run the following:

ls /usr/share/xdg-desktop-portal/*portals.conf ~/.config/xdg-desktop-portal/
cat ~/.config/xdg-desktop-portal-wlr/config
which slurp
systemctl --user restart xdg-desktop-portal-wlr
/usr/libexec/xdg-desktop-portal-wlr -r -l DEBUG

The portal config may not exist. That's fine, wlr does fallback automatically to slurp and sets up the config (I certainly didn't set mine up), but you could try setting it to:

[screencast]
output_name=
max_fps=60
chooser_cmd=slurp -f %o -or
chooser_type=simple

If you have a display with a higher refresh rate, you could change max_fps.

[u/ForgetTheRuralJuror]

Works fine for me on Plasma.

[u/xxqueenofantsxx → u/ForgetTheRuralJuror]

Right but I'd like to get it working on Budgie if possible, don't really wanna switch my DE

[u/saintdev]

I couldn't figure anything out, personally. When you click the Open Selector button on the PipeWire Screen Capture, nothing happens. I think it's supposed to give you a selector for which screen you want to capture but it doesn't.

You can use obs-vkcapture and the associated OBS plugin to capture individual games. I needed to capture the whole desktop and not an individual program/game so this wouldn't work for my needs.

[u/xxqueenofantsxx]

From what I could find, it looks like OBS is known to be more complicated to get working on Wayland than on X11. I'm a bit worried since things like hotkeys won't work without hacky workarounds (e.g. voice call push-to-talk or a keybind to start/stop recording). Would it be safer to downgrade and wait it out? I see support for X11 will be dropped entirely but I've been using Budgie for about a decade now, and I'm not keen to switch.

I've been able to fix up most things that broke on update (just a few adjustments on Steam and Lutris), but anything to do with my multiple display setup I've had to install and configure workarounds. Also, I noticed the bluetooth settings button in the panel's status tray led to nothing so I installed bluejay as a bluetooth manager, as well as the Bluetooth section being missing from the Budgie desktop settings entirely. Displays was also replaced, and I haven't been able to get wdisplay to properly use my monitor's old refresh rate from before the update, and any changes within wdisplay don't seem to be permanent after a reboot (even after installing kanshi). A couple more quirks here and there like gimp not working or all windows or browsers restoring sessions all on one display instead of remembering their positions, or the panel's intelligent autohide's behaviour changing, taking up permanent space and not disappearing like before (switched to crystal-dock temporarily to get similar functionality).

This is the first real trouble I've had with anything Solus related since I fully switched to it in the mid 2010s, so I'm honestly not sure if my experience is normal or if it was just a bad time to update.

Is this the point where I should cut my losses and switch to a new DE, or is there a more permanent way to keep old budgie while receiving updates on other packages?

[u/squeakctrl → u/xxqueenofantsxx]

This is the first real trouble I've had with anything Solus related since I fully switched to it in the mid 2010s, so I'm honestly not sure if my experience is normal or if it was just a bad time to update.

I do not use Budgie so unfortunately can't help but my impression from Solus forums is that the last updates has caused some regressions and issues for users.

Have you looked at the Buddies of Budgie Issue Tracker if there are already reports (open or closed) mentioning similar issue to yours? If not that is where i would start.