Graphics problems in Signal Flatpak on Librem5

I just upgraded my signal flatpak on my Librem 5 from 7.71.0 to 7.72.1 and the graphics look horrible. The icon images on the left panel are corrupted, and all the text is blurry.

I tried manually downgrading to 7.71.0 by downloading the signal_arm64.flatpak file from Releases · signalflatpak/signal · GitHub, but when I tried running it I got an error message saying my database is incompatible with the older signal version.

Any suggestions on how to resolve the graphics problems?

3 Likes

I saw in your other post about the Pure Maps that Signal reverted back to being an X11 application. You can try this trick to enable it to use Wayland: What happened with flare - #9 by mel

2 Likes

Yes, I added the Exec=flatpak run org.signal.Signal --use-gl=egl --enable-features=UseOzonePlatform --ozone-platform=wayland line to my .desktop file a while ago, and it worked fine until the latest 7.72.1 signal update. After the last update, signal seems to have reverted to X11, despite the arguments in the Exec line.

However, I just tried running the following command from the terminal, and that seems to make signal work with wayland:

flatpak run org.signal.Signal --use-gl=egl --enable-features=UseOzonePlatform --ozone-platform=wayland

The command is the same as that in the Exec line in the .desktop file, yet for some reason, it works from terminal but not from the .desktop launcher. Any idea why?

1 Like

I get the following output from the terminal command. There seems to be some error regarding the –use-gl=egl argument, but signal still starts and runs using wayland when launched from the terminal.

1 Like

That’s weird. I do not get the same blurriness or corrupted images on the same version. I do get the same error running in the terminal, but like you said it still loads into wayland. Maybe something went wrong during the upgrade? Have you tried flatpak repair org.signal.Signal

I saw this discussed on mastodon the last few days, maybe it’s the same problem you are seeing?

From later posts in that mastodon thread it looks like there is some kind of workaround that helps. Does that help for you?

1 Like