-
Notifications
You must be signed in to change notification settings - Fork 569
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: black screen during screen capture and desktop portal error (pipewire) #6130
Comments
What happens if you add the following to ~/.config/firejail/obs.local?
|
I created the obs.local file with the inclue statement and it looks like I am getting the same error:
|
|
Note that firejail now keeps the pipewire group (see #5992) if that's the Does it work with firejail-git? Was this setup working in a previous version of the program/environment? If so, which versions were used?
What is the output of the following? firejail --noprofile /usr/bin/obs firejail --profile=noprofile /usr/bin/obs |
Some plugins may require it[1]: error: os_dlopen([...]): libluajit-5.1.so.2: [...]: Permission denied warning: Module '/usr//lib/obs-plugins/frontend-tools.so' not loaded [1] netblue30#6130 (comment)
Hi Rusty Snake I changed my obs.local file to as follows. I noticed that obs can see obs.local:
Output from terminal:
|
Good Morning Kelvin, Thank you for your feedback. I will answer your questions below:
Note:
(a) firejail --noprofile /usr/bin/obs
(b) firejail --profile=noprofile /usr/bin/obs
|
Some plugins may require it[1]: error: os_dlopen([...]): libluajit-5.1.so.2: [...]: Permission denied warning: Module '/usr//lib/obs-plugins/frontend-tools.so' not loaded [1] #6130 (comment)
Greetings. I see, thanks for the details.
If you could test it later it would be helpful to know whether the profile You could install firejail-git from the AUR, test and then reinstall firejail. Also, what is the output of
From #6065, it looks like it will be in January. |
Since firejail is aiming for January 2024, can we hold this bug open and I will re-test then? Just I use firejail system wide and I'd like to do a more comprehensive test. |
I appear to have a similar problem |
Hi Kelvin, I wanted to provide you with an update after a firejail update came down via Arch Repositories (stable):
Looks like I still have to use the obs.local file with the line "ignore noroot" in it to allow obs to see my screen for capture. I still see this error when obs starts:
|
Hello, this is still the same version; there hasn't been a release yet. |
Description
When Firejail is enabled (sudo firecfg) and Wayland session is used in either Gnome 45 or KDE 5.27.10 we get:
When Pipewire Screen capture is turned on we get a blank screen.
The following error shows in the terminal:
Steps to Reproduce
Steps to reproduce the behavior
Log into Gnome or KDE with a Wayland Session.
Firejail is Enabled.
Open Terminal and launch OBS with "obs' command.
The Pipewire Screen capture option will be enabled. The following will show in the terminal:
Expected behavior
OBS should start and show you a preview of the screen you wish to record.
Actual behavior
OBS starts but there is a blank black screen with the reported GDBUS.Error.
Behavior without a profile
In terminal I tried launching OBS with "obs --noprofile" and still I was getting a black screen for screen recorder preview.
Additional context
n\a
Environment
OBS 30.0.0-1
System:
Arch Linux
Kernel: 6.1.67-1-lts arch: x86_64 bits: 64
Desktop: KDE Plasma: 5.27.10
Distro: EndeavourOS
Graphics:
Device-1: Intel HD Graphics 5500 driver: i915 v: kernel
firejail --version
Checklist
/usr/bin/vlc
) "fixes" it).https://github.com/netblue30/firejail/issues/1139
)browser-allow-drm yes
/browser-disable-u2f no
infirejail.config
to allow DRM/U2F in browsers.--profile=PROFILENAME
to set the right profile. (Only relevant for AppImages)Log
Included in description.
The text was updated successfully, but these errors were encountered: