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

Black screen on xwayland #238

Closed
alvarlagerlof opened this issue Nov 15, 2021 · 16 comments
Closed

Black screen on xwayland #238

alvarlagerlof opened this issue Nov 15, 2021 · 16 comments

Comments

@alvarlagerlof
Copy link

image

@untitled9074
Copy link

untitled9074 commented Nov 30, 2021

See is this helps.

TLDR: flatpak run org.signal.Signal --enable-features=UseOzonePlatform --ozone-platform=wayland [+ socket access override if needed].

@vchernin
Copy link

Nvidia?

@alvarlagerlof
Copy link
Author

Shouldn't I work by default? Setting env vars is not nice. Yes, Nvidia.

@vchernin
Copy link

What distro? Make sure xwayland is up to date (21.1.3 or later iirc). It needed Nvidia-specific fixes for some xwayland apps to work.

@alvarlagerlof
Copy link
Author

I don't think I have completely the latest, it's fedora 35. Will get GBM in a couple of days but this app was broken while other election apps worked, so I figured it was more likely incorrect options.

@vchernin
Copy link

You could try different options, but with GBM imminent it might be best just to wait.

@alvarlagerlof
Copy link
Author

Yeah that might just fix it anyways. Will come back and report on it when it works/doesn't in a few days.

bermeitinger-b added a commit that referenced this issue Jan 10, 2022
Enable access to wayland for #188 (and maybe #238)
@alvarlagerlof
Copy link
Author

The issue does not seem to be in the not in the drivers. I am now on 510 and the issue persists. GBM is supposed to have been working for a while. Using --disable-gpu-sandbox makes the app work.

@alvarlagerlof
Copy link
Author

alvarlagerlof commented Feb 21, 2022

razzeee/im.riot.Riot@2b9214a this might fix it

@abique
Copy link

abique commented Feb 24, 2022

Maybe it did not make it yet to flathub?
Also I saw in flatseal that signal does not have dri access by default?

@vchernin
Copy link

vchernin commented Feb 24, 2022

By default Signal has --device=all which includes --device=dri

@abique
Copy link

abique commented Feb 24, 2022

So it is a display thing in flatseal then.

bermeitinger-b added a commit that referenced this issue Feb 25, 2022
Maybe fixes #238 by introducing `--disable-gpu-sandbox` (inspired from [riot](razzeee/im.riot.Riot@2b9214a))
@bermeitinger-b
Copy link
Collaborator

Can you test #277 ?

flatpak install --user https://dl.flathub.org/build-repo/77479/org.signal.Signal.flatpakref

@alvarlagerlof
Copy link
Author

Can you test #277 ?

flatpak install --user https://dl.flathub.org/build-repo/77479/org.signal.Signal.flatpakref

That just 404s, but --disable-gpu-sandbox did not work for me manually.

@abique
Copy link

abique commented Mar 8, 2022

I'm using the latest signal from flatpak and for me the bug is now fixed.

@alvarlagerlof
Copy link
Author

I'm using the latest signal from flatpak and for me the bug is now fixed.

It is indeed for me too.

image

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

Successfully merging a pull request may close this issue.

5 participants