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

Blank render area without GPU acceleration #378

Open
okennedy opened this issue Mar 30, 2022 · 1 comment
Open

Blank render area without GPU acceleration #378

okennedy opened this issue Mar 30, 2022 · 1 comment

Comments

@okennedy
Copy link

okennedy commented Mar 30, 2022

After recently installing Marker on a new computer (via flatpak), the render area did not display properly (PopOS 21.10, with onboard Intel graphics). The entire area where the markdown render was supposed to be displayed was just blank grey. The same occurred in multi-window mode. Running marker on the command line produced the following output:

okennedy@athena:~$ flatpak run com.github.fabiocolacio.marker
Gtk-Message: 15:16:15.178: Failed to load module "appmenu-gtk-module"
Gtk-Message: 15:16:15.214: Failed to load module "canberra-gtk-module"
Gtk-Message: 15:16:15.215: Failed to load module "canberra-gtk-module"
Gtk-Message: 15:16:15.453: Failed to load module "appmenu-gtk-module"
Gtk-Message: 15:16:15.511: Failed to load module "canberra-gtk-module"
Gtk-Message: 15:16:15.516: Failed to load module "canberra-gtk-module"
scroll 2.0 extension initialized
libGL error: MESA-LOADER: failed to retrieve device information
intel_do_flush_locked failed: Input/output error
intel_do_flush_locked failed: Input/output error

Based on the libGL error, I tried enabling GPU permissions (device=dri) in flatseal. This appeared to resolve the problem. The same issue does not arise on computers with an identical OS, but discrete graphics.

@violetmage
Copy link

violetmage commented Apr 15, 2022

greetings

this appears to be an issue with the flatpak package, and not marker itself, therefore @fabiocolacio requesting this issue be moved or closed

however, the people maintaining the flatpak package have taken note, and already fixed this issue:
flathub/com.github.fabiocolacio.marker@edc8de4

nonetheless, thank you for your well written post

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

2 participants