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

Gray screen when launching app, AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer #2419

Open
3 tasks done
DUDEbehindDUDE opened this issue Sep 18, 2024 · 1 comment
Labels
app bug Something isn't working

Comments

@DUDEbehindDUDE
Copy link

Please confirm the following.

  • I checked the existing issues for duplicate problems
  • I have tried resolving the issue using the support portal
  • I have ensured my Modrinth App installation is up to date

What version of the Modrinth App are you using?

0.8.7

What operating systems are you seeing the problem on?

Linux

Describe the bug

For the past few versions (at least since 0.8.5, maybe earlier), I have been unable to use the .deb package for modrinth. When I open the app, it just displays a gray screen, however the buttons are all there, as I can click where buttons should be and it does the expected actions (the screen is just completely gray). Opening the app from the console by running modrinth-app results in the app spamming this every frame:
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer

This is not a problem when running the .Appimage, only when installing the .deb package.

Steps to reproduce

  1. Download the deb package
  2. Open the app
  3. Gray screen

Expected behavior

I should be able to see the UI elements

Additional context

System:
Kernel: 6.8.0-41-generic arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 clocksource: tsc
Desktop: Cinnamon v: 6.2.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.2.0 vt: 7 dm: LightDM v: 1.30.0
Distro: Linux Mint 22 Wilma base: Ubuntu 24.04 noble
CPU:
Info: 6-core model: AMD Ryzen 5 2600 bits: 64 type: MT MCP smt: enabled arch: Zen+ rev: 2 cache:
L1: 576 KiB L2: 3 MiB L3: 16 MiB
Speed (MHz): avg: 2200 high: 3893 min/max: 1550/3400 boost: enabled cores: 1: 1547 2: 1547
3: 1547 4: 2595 5: 2598 6: 3892 7: 1550 8: 1547 9: 1547 10: 1557 11: 2589 12: 3893
bogomips: 81444
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2060 Rev. A] vendor: Gigabyte driver: nvidia v: 535.183.01
arch: Turing pcie: speed: 5 GT/s lanes: 16 ports: active: none off: DP-3,HDMI-A-1
empty: DP-1,DP-2 bus-ID: 0a:00.0 chip-ID: 10de:1f08 class-ID: 0300
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
loaded: modesetting,nouveau,nvidia unloaded: fbdev,vesa gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2 drv: swrast gbm:
drv: kms_swrast surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 535.183.01 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2

@DUDEbehindDUDE DUDEbehindDUDE added app bug Something isn't working labels Sep 18, 2024
@DUDEbehindDUDE
Copy link
Author

image
(Gray window is modrinth)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app bug Something isn't working
Development

No branches or pull requests

1 participant