Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OBS Freezes on Wayland with Pipewire (xdg-desktop-portal-hyprland) #239

Closed
different-name opened this issue Jul 20, 2024 · 12 comments
Closed

Comments

@different-name
Copy link

OS

Arch
NixOS

Behaviour

OBS Screen Capture (pipewire) freezes as soon as the input is selected

Frozen.OBS.xQUKy5_UHr0.mp4

See original OBS issue where this was marked as a xdg-desktop-portal-hyprland issue:
obsproject/obs-studio#10959

@dec05eba
Copy link
Contributor

dec05eba commented Jul 21, 2024

I cant reproduce this. Are you using latest hyprland desktop portal and hyprland installed from master branch?

@different-name
Copy link
Author

They've just merged the swap to aquamarine into master I believe so likely a lot of big changes, will try reproduce tomorrow and update

@different-name
Copy link
Author

I cant reproduce this. Are you using latest hyprland desktop portal and hyprland installed from master branch?

I am using the latest commit on the master branch of xdg-desktop-portal hyprland, and this commit from 7 hours ago on hyprland hyprwm/Hyprland@cbaac6d

Able to reproduce reliably, might be noteworthy that I am on an Nvidia card, and I've looked through the logs attached in the original issue, they are also using an Nvidia card

First launch can be okay, with the source not freezing, seems to reliably break on subsequent launches and after clicking the Select Monitor button in the source properties

@dec05eba
Copy link
Contributor

Oh ok that might explain it then, I tested it on amd

@SSS-Says-Snek
Copy link

I can reproduce the issue (I also have an Nvidia card)

@c4em
Copy link

c4em commented Aug 2, 2024

I'm also able to reproduce this on Nvidia, both on the latest master commit and latest stable version of Tag: v0.41.2, commits: 918d8340afd652b011b937d29d5eea0be08467f5. For me the first launch behavior is different though, it first segfaults when adding the new source:

info: PipeWire initialized
info: User added source 'Screen Capture (PipeWire)' (pipewire-screen-capture-source) to scene 'Scene'
info: [pipewire] Screencast session created
info: PipeWire initialized
info: [pipewire] Asking for monitor and window

(process:9791): GLib-CRITICAL **: 15:39:53.592: g_variant_is_object_path: assertion 'string != NULL' failed

(process:9791): GLib-CRITICAL **: 15:39:53.592: g_variant_new_object_path: assertion 'g_variant_is_object_path (object_path)' failed
zsh: segmentation fault (core dumped)  nix run nixpkgs#obs-studio

and on consecutive launches it freezes like shown in the video.

@Oery
Copy link

Oery commented Aug 11, 2024

I can reproduce it and I'm on Nvidia and latest commit. The stream freeezes instantly when created on OBS first, but if a stream is created on Discord, then the OBS streams works fine. There are no errors nor warnings in my logs.

@mufaroxyz
Copy link

Any updates on this? I'm still having issues on Nvidia

@sfjuocekr
Copy link

I have the same-ish issue, the funny thing is when I have OBS active it captures fine but when I switch back to the game my game output freezes!

When I tab back to OBS the game seems to continue fine in the background.

@LeonLeeLi
Copy link

I have the same-ish issue, the funny thing is when I have OBS active it captures fine but when I switch back to the game my game output freezes!我遇到了同样的问题,有趣的是,当我激活 OBS 时,它可以正常捕获,但是当我切换回游戏时,我的游戏输出冻结了!

When I tab back to OBS the game seems to continue fine in the background.当我返回 OBS 时,游戏似乎在后台继续正常进行。

The same issue

@mufaroxyz
Copy link

mufaroxyz commented Oct 4, 2024

So far the only workaround I found that worked for me is:
#220 (comment)

Though, the issue still occurs randomly, I was able to at least get the screen capture to work at the bare minimum

@different-name
Copy link
Author

I'm going to close this issue since I can no longer reproduce, perhaps it was fixed accidentally 🥳
If anyone else is still experiencing this I'm happy to reopen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants