Soundux opens with blank screen
Ombrezz opened this issue · comments
✍️ Bug Description
Soundux used to work perfectly fine on my PC (I haven't used it for a month or two) but launching it recently it just shows a blank screen (Flatpak is white and RPM is grey). Launching either version from the terminal spams the error AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer. I saw some of the other issues in the repo about this and that it is an NVIDIA issue. I tried the WEBKIT_DISABLE_DMABUF_RENDERER=1, WEBKIT_DISABLE_COMPOSITING_MODE=1, and update-mime-database ~/.local/share/mime fixes but none of them worked. My GPU is a GTX 970 and I'm using the proprietary NVIDIA drivers (version 550.67).
🔁 Steps to reproduce
Just launch Soundux, this probably isn't easily reproducible due to the nature of the problem but the other issues should have hopefully documented it enough.
🖥️ Console Output
RPM:
[02:05:16] [success] Config read
[02:05:16] [success] LibWnck found - Icon support is enabled
[02:05:16] [failure] Failed to create AudioBackend instance
[02:05:17] [message] Using DISPLAY :0
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
[02:05:20] [message] UI exited
[02:05:20] [success] Config written
Flatpak:
[00:43:04] [success] Config read
[00:43:04] [success] LibWnck found - Icon support is enabled
[00:43:04] [message] Connected to PipeWire ("pipewire-0") on version "1.0.3"
[00:43:04] [warning] Your PipeWire version is below the minimum required (0.3.26), you may experience bugs or crashes
[00:43:05] [message] Using DISPLAY :0
Gtk-Message: 20:43:05.212: Failed to load module "canberra-gtk-module"
Gtk-Message: 20:43:05.212: Failed to load module "pk-gtk-module"
Gtk-Message: 20:43:05.454: Failed to load module "canberra-gtk-module"
Gtk-Message: 20:43:05.455: Failed to load module "pk-gtk-module"
Gtk-Message: 20:43:05.473: Failed to load module "canberra-gtk-module"
Gtk-Message: 20:43:05.473: Failed to load module "pk-gtk-module"
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
[00:43:06] [warning] Failed to find ppid of 91642, process does not exist
[00:43:06] [warning] Could not find proccess with id 91642
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
^C
❔ Expected behaviour
Soundux boots like normal and gives me a menu to play sounds.
👀 Screenshots
🖥️ Operating System
Linux
🖥️ Distribution
Fedora 38
✅ I confirm that...
- I have collected all the required information and read all the comments in this document
- I searched for an existing bug report for this issue
- the problem does occur with the reproduction steps I provided
- what I described is indeed a problem
I'm having the same issue, with the same output from flatpak
How are you applying the WEBKIT_DISABLE_DMABUF_RENDERER=1 workaround? This has worked for other users with NVIDIA hardware.
You can add it to Flatseal as an environment variable, which should solve the issue.
You can also try to delete your config: ~/.var/app/io.github.Soundux/config/Soundux/config.json, and then relaunch soundux with that workaround in place.
That solved it, thanks!