SUMMARY Plasma session doesn't open anymore when adding this environment variable: QSG_RHI_BACKEND=vulkan. And there's also no error output. STEPS TO REPRODUCE 1. Create this environment variable: QSG_RHI_BACKEND=vulkan 2. Reboot the computer OBSERVED RESULT With the automatic login that I have, after systemd's output finishes, the Plasma session looks like it's loading normally... But it gets stuck with a black background and no text output whatsoever. The mouse is still visible and movable. The keyboard is also working as I can press CTRL+ALT+F3, login, edit the environment variables file to comment out this variable and then do a systemctl reboot. Which will succeed, as Plasma opens normally after reboot. EXPECTED RESULT 1. The Plasma session opens normally, like before setting this environment variable. 2. When Plasma session cannot open, for whatever reason, some text output with the error should be shown, no matter how technical. 3. Maybe also add a recommendation to comment out some environment variables. SOFTWARE/OS VERSIONS Linux (Debian 13 - unstable repository)/KDE Plasma: KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.12.17-amd64 (64-bit) Mesa Version: 25.0.1-2 Graphics Platform: Wayland HARDWARE SPECIFICATIONS Hardware: Laptop Dell Inspiron 5770 (17" 1080p@60Hz screen) CPU: Intel® Core™ i5-8250U CPU @ 1.60GHz (4 cores, 8 threads) GPU 1: Intel® UHD Graphics 620 (main, Vulkan capable) GPU 2: AMD Radeon R5 M465 Series RAM: 8 GiB (7.7 GiB usable) ADDITIONAL INFORMATION Here is the documentation for this environment variable: https://doc.qt.io/qt-6/qtquick-visualcanvas-scenegraph-renderer.html It's for 6.8 and I'm using Qt 6.8.2 so it should work, considering that I'm using an Intel iGPU and Mesa is also up to date. And it worked the first time I tried it, which was Plasma 6.3.0. It was broken in Plasma 6.3.1 or 6.3.2, I don't remember which one of them. I know for sure it worked because MangoHUD, I have also installed for games passing through DXVK to Vulkan, started appearing after reboot for Plasma itself too. It was not working correcly (like continuously updating), but anyway. VKcube and games going through DXVK work ok, so don't think the Vulkan drivers are the problem here. The first time I could not enter the Plasma session, I had to reinstall the whole OS as I could not link the existence of this environment variable with the fact that I could not login, especially since it previously worked. But after setting my environment variables again on the clean system and seeing that boot is affected again I got the idea that it might be one of the environment variables. So, I had to comment out all environment variables one by one and reboot until I found which was triggering this.
Please let me know if you can't reproduce it and need more! I never managed to get logs, stack traces or core dumps for any KDE software no matter how much I tried following that tutorial. Only thing that I succeed every time is to look at systemd's journal for the previous boot and from all that long output, looking for yellow and red colors, I saw these lines: Mar 14 11:50:03 JL systemd-coredump[1602]: [🡕] Process 1508 (ksplashqml) of user 1000 dumped core. Stack trace of thread 1598: #0 0x00007fd38a1acee4 n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64 Mar 14 11:50:03 JL dbus-daemon[1371]: [session uid=1000 pid=1371 pidfd=5] Successfully activated service 'ca.desrt.dconf' Mar 14 11:50:03 JL systemd[1336]: Started dconf.service - User preferences database. Mar 14 11:50:03 JL systemd[1]: systemd-coredump@0-1601-0.service: Deactivated successfully. Mar 14 11:50:03 JL systemd[1]: systemd-coredump@0-1601-0.service: Consumed 382ms CPU time, 114.8M memory peak. Mar 14 11:50:03 JL systemd[1336]: plasma-ksplash.service: Main process exited, code=dumped, status=11/SEGV Mar 14 11:50:03 JL systemd[1336]: plasma-ksplash.service: Failed with result 'core-dump'. Mar 14 11:50:03 JL systemd[1336]: Failed to start plasma-ksplash.service - Splash screen shown during boot. Mar 14 11:50:03 JL systemd[1336]: plasma-ksplash.service: Consumed 408ms CPU time, 64.6M memory peak. Mar 14 11:50:03 JL dbus-daemon[1371]: [session uid=1000 pid=1371 pidfd=5] Activating service name='org.kde.KSplash' requested by ':1.26' (uid=1000 pid=1630 com> Mar 14 11:50:03 JL systemd[1336]: Started plasma-ksmserver.service - KDE Session Management Server. Mar 14 11:50:03 JL systemd[1336]: Starting plasma-plasmashell.service - KDE Plasma Workspace... Mar 14 11:50:03 JL at-spi-bus-launcher[1626]: dbus-daemon[1626]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=1630 comm=> Mar 14 11:50:03 JL NetworkManager[1009]: <info> [1741953003.6920] agent-manager: agent[904dfab29cfb153f,:1.50/org.kde.plasma.networkmanagement/1000]: agent re> Mar 14 11:50:03 JL at-spi-bus-launcher[1626]: dbus-daemon[1626]: Successfully activated service 'org.a11y.atspi.Registry' Mar 14 11:50:03 JL at-spi-bus-launcher[1688]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Mar 14 11:50:03 JL kded6[1632]: org.kde.libkbolt: Failed to connect to Bolt manager DBus interface: Mar 14 11:50:03 JL kded6[1632]: org.kde.bolt.kded: Couldn't connect to Bolt DBus daemon Mar 14 11:50:03 JL dbus-daemon[1371]: [session uid=1000 pid=1371 pidfd=5] Activating via systemd: service name='org.kde.ActivityManager' unit='plasma-kactivity> Mar 14 11:50:03 JL kded6[1632]: QDBusObjectPath: invalid path "/modules/kded_plasma-welcome" Mar 14 11:50:03 JL kded6[1632]: kf.dbusaddons: The kded module name "kded_plasma-welcome" is invalid! Mar 14 11:50:03 JL systemd[1336]: Starting plasma-kactivitymanagerd.service - KActivityManager Activity manager Service... Mar 14 11:50:03 JL kded6[1632]: colord: X11 not detect disabling Mar 14 11:50:03 JL kded6[1632]: org.kde.colorcorrectlocationupdater: Geolocator stopped Mar 14 11:50:03 JL kactivitymanagerd[1694]: kf.windowsystem: virtual void KX11Extras::connectNotify(const QMetaMethod&) may only be used on X11 Mar 14 11:50:03 JL kactivitymanagerd[1694]: kf.windowsystem: virtual void KX11Extras::connectNotify(const QMetaMethod&) may only be used on X11 Mar 14 11:50:03 JL kded6[1632]: QDBusObjectPath: invalid path "/modules/oom-notifier" Mar 14 11:50:03 JL kded6[1632]: kf.dbusaddons: The kded module name "oom-notifier" is invalid! Mar 14 11:50:03 JL dbus-daemon[1371]: [session uid=1000 pid=1371 pidfd=5] Successfully activated service 'org.kde.ActivityManager' Mar 14 11:50:03 JL systemd[1336]: Started plasma-kactivitymanagerd.service - KActivityManager Activity manager Service. Mar 14 11:50:03 JL kded6[1632]: QDBusObjectPath: invalid path "/modules/plasma-session-shortcuts" Mar 14 11:50:03 JL kded6[1632]: kf.dbusaddons: The kded module name "plasma-session-shortcuts" is invalid!
I've also tried setting the splash screen to 'None', which also doesn't work, the boot still gets stuck. I see this in the journal in yellow if it's any help: Mar 14 12:57:04 JL sddm-helper[1319]: Failed to write utmpx: No such file or directory OK, I think I found in the journal the main problem, starting with the second line of this output: Mar 14 12:57:09 JL systemd[1334]: Reached target xdg-desktop-autostart.target - Startup of XDG autostart applications. Mar 14 12:57:09 JL plasmashell[1647]: Failed to load vulkan: Cannot load library vulkan: vulkan: cannot open shared object file: No such file or directory Mar 14 12:57:09 JL plasmashell[1647]: initInstance: No Vulkan library available Mar 14 12:57:09 JL plasmashell[1647]: Failed to create platform Vulkan instance Mar 14 12:57:09 JL plasmashell[1647]: QVulkanDefaultInstance: Failed to create Vulkan instance Mar 14 12:57:09 JL plasmashell[1647]: No QVulkanInstance set for QQuickWindow, this is wrong. Mar 14 12:57:09 JL plasmashell[1647]: KCrash: Application 'plasmashell' crashing... crashRecursionCounter = 2 Mar 14 12:57:09 JL systemd-coredump[1889]: Process 1647 (plasmashell) of user 1000 terminated abnormally with signal 11/SEGV, processing... Mar 14 12:57:09 JL systemd[1]: Created slice system-drkonqi\x2dcoredump\x2dprocessor.slice - Slice /system/drkonqi-coredump-processor. Mar 14 12:57:09 JL systemd[1]: Created slice system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump. Mar 14 12:57:09 JL systemd[1]: Started systemd-coredump@0-1889-0.service - Process Core Dump (PID 1889/UID 0). Mar 14 12:57:09 JL systemd[1]: Started drkonqi-coredump-processor@0-1889-0.service - Pass systemd-coredump journal entries to relevant user for potential DrKon> Mar 14 12:57:09 JL dbus-daemon[1375]: [session uid=1000 pid=1375 pidfd=5] Successfully activated service 'org.freedesktop.impl.portal.desktop.gtk' Mar 14 12:57:09 JL systemd[1334]: Started xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation). Mar 14 12:57:09 JL rtkit-daemon[1387]: Supervising 6 threads of 3 processes of 1 users. Mar 14 12:57:09 JL rtkit-daemon[1387]: Supervising 6 threads of 3 processes of 1 users. Mar 14 12:57:09 JL rtkit-daemon[1387]: Supervising 6 threads of 3 processes of 1 users. Mar 14 12:57:09 JL dbus-daemon[1375]: [session uid=1000 pid=1375 pidfd=5] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.kde' unit='> Mar 14 12:57:09 JL systemd[1334]: Starting plasma-xdg-desktop-portal-kde.service - Xdg Desktop Portal For KDE... Mar 14 12:57:10 JL dbus-daemon[858]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.75' > Mar 14 12:57:10 JL systemd[1]: Starting packagekit.service - PackageKit Daemon... Mar 14 12:57:10 JL kup-daemon[1868]: kup.daemon: "Kup is not enabled, enable it from the system settings module. You can do that by running kcmshell5 kup" Mar 14 12:57:10 JL kwin_wayland_wrapper[1503]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Mar 14 12:57:10 JL PackageKit[1935]: daemon start Mar 14 12:57:10 JL kded6[1606]: Registering ":1.54/StatusNotifierItem" to system tray Mar 14 12:57:10 JL dbus-daemon[858]: [system] Successfully activated service 'org.freedesktop.PackageKit' Mar 14 12:57:10 JL systemd[1]: Started packagekit.service - PackageKit Daemon. Mar 14 12:57:10 JL kernel: warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211 Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Permission denied Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: DRM_IOCTL_VIRTGPU_CONTEXT_INIT failed with Permission denied, continuing without context... Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: Failed to create virtgpu AddressSpaceStream Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: vulkan: Failed to get host connection Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: Failed to create virtgpu AddressSpaceStream Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: vulkan: Failed to get host connection Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: Failed to create virtgpu AddressSpaceStream Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: vulkan: Failed to get host connection Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: Failed to create virtgpu AddressSpaceStream Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: vulkan: Failed to get host connection Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: Failed to create virtgpu AddressSpaceStream Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: vulkan: Failed to get host connection Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: Failed to create virtgpu AddressSpaceStream Mar 14 12:57:10 JL xwaylandvideobridge[1834]: MESA: error: vulkan: Failed to get host connection Mar 14 12:57:10 JL kdeconnectd[1831]: 2025-03-14T12:57:10 qt.bluetooth.bluez: Bluetooth device is powered off Mar 14 12:57:10 JL dbus-daemon[1375]: [session uid=1000 pid=1375 pidfd=5] Activating service name='org.freedesktop.Notifications' requested by ':1.46' (uid=100> Mar 14 12:57:10 JL dbus-daemon[1375]: [session uid=1000 pid=1375 pidfd=5] Successfully activated service 'org.freedesktop.impl.portal.desktop.kde' Mar 14 12:57:10 JL systemd[1334]: Started plasma-xdg-desktop-portal-kde.service - Xdg Desktop Portal For KDE. Mar 14 12:57:10 JL rtkit-daemon[1387]: Supervising 6 threads of 3 processes of 1 users. Mar 14 12:57:10 JL rtkit-daemon[1387]: Supervising 6 threads of 3 processes of 1 users. Mar 14 12:57:10 JL rtkit-daemon[1387]: Supervising 6 threads of 3 processes of 1 users. Mar 14 12:57:10 JL dbus-daemon[1375]: [session uid=1000 pid=1375 pidfd=5] Successfully activated service 'org.freedesktop.portal.Desktop' Mar 14 12:57:10 JL systemd[1334]: Started xdg-desktop-portal.service - Portal service. Mar 14 12:57:10 JL kalendarac[1998]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Mar 14 12:57:10 JL kalendarac[2018]: org.kde.pim.akonadiserver: Starting up the Akonadi Server... Mar 14 12:57:10 JL kalendarac[2018]: org.kde.pim.akonadiserver: Running DB initializer Mar 14 12:57:10 JL kalendarac[2018]: org.kde.pim.akonadiserver: DB initializer done Mar 14 12:57:10 JL kalendarac[2018]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Mar 14 12:57:11 JL kalendarac[1998]: org.kde.pim.akonadicontrol: Akonadi server is now operational. Mar 14 12:57:11 JL systemd-coredump[1891]: [🡕] Process 1647 (plasmashell) of user 1000 dumped core. Stack trace of thread 1888: #0 0x00007f84e949e8ac n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64 Mar 14 12:57:11 JL drkonqi-coredump-processor[1893]: "/usr/bin/plasmashell" 1647 "/var/lib/systemd/coredump/core.plasmashell.1000.cd165bb2411241fa8025d2a881fe7> Mar 14 12:57:11 JL systemd[1334]: Started drkonqi-coredump-launcher@0-1893-0.service - Launch DrKonqi for a systemd-coredump crash (PID 1893/UID 0). Mar 14 12:57:11 JL systemd[1]: drkonqi-coredump-processor@0-1889-0.service: Deactivated successfully. Mar 14 12:57:11 JL systemd[1]: drkonqi-coredump-processor@0-1889-0.service: Consumed 236ms CPU time, 169.4M memory peak. Mar 14 12:57:11 JL systemd[1]: systemd-coredump@0-1889-0.service: Deactivated successfully. Mar 14 12:57:11 JL systemd[1]: systemd-coredump@0-1889-0.service: Consumed 1.401s CPU time, 338.5M memory peak. --------------------------------------- END ----------------------------------------------------------------- Could it be the same problem as I had in this bug, with the my distro Vulkan stack not being good or Plasma not looking for the right files?: https://bugs.kde.org/show_bug.cgi?id=500403
Upstream issue. Might be better in Qt 6.9. See the linked bug report and its many duplicates. *** This bug has been marked as a duplicate of bug 482754 ***
(In reply to cwo from comment #3) > Upstream issue. Might be better in Qt 6.9. See the linked bug report and its > many duplicates. > > *** This bug has been marked as a duplicate of bug 482754 *** Are you sure this is an upstream issue only? Because the fact I could login the first time I added this environment variable made me think a bit more about it. Why I could then and I couldn't later? Seeing that I reinstalled the OS wiping completely the / (root) partition, then having the system fully up to date with the unstable repository of Debian and the Info Center is not showing again the pills for the GPU, I remembered that Plasma has a problem finding the right Vulkan libraries and maybe that was the case for this too... So I decided to fix again the Info Center with the command that I discovered trying to fix it the first time, which is this: sudo ln -s /usr/lib/x86_64-linux-gnu/libvulkan.so.1 /usr/lib/x86_64-linux-gnu/libvulkan.so Then I un-commented the environment variable that gives the stuck boot problem: QSG_RHI_BACKEND=vulkan And rebooted! And guess what? Making this symlink, it fixes the login problem too, that I reported here! I guess when I first added this environment variable, I still had the symlink because I did it to fix the Info center's GPU pills and because of that it worked. Probably the updates deleted / overwritten / renamed the symlink and made my system not log in anymore. So now, with this symlink, both the Info Center's pills and the login problem are fixed! The only problem that remains is that stuff keep crashing like crazy immediately after login. And I don't even know which of them crash as that crash handler doesn't say for which component / process has been triggered and it's triggered multiple times. But it looks to me that the panel is the first one to crash, because it's the first one gone and not coming back. It looks to me that the linked bug report plus its many duplicates are for these kind of crashes, not exactly for what I opened this report. Since a simple command like this: sudo ln -s /usr/lib/x86_64-linux-gnu/libvulkan.so.1 /usr/lib/x86_64-linux-gnu/libvulkan.so Is enough to fix the problem in the previous bug report and the login problem here, can you please check which Vulkan file is Plasma trying to find? As in folder '/usr/lib/x86_64-linux-gnu/' I have: 0777 lrwxrwxrwx - root root 18 Mar 14:31 libvulkan.so -> /usr/lib/x86_64-linux-gnu/libvulkan.so.1 0777 lrwxrwxrwx - root root 16 Jan 14:38 libvulkan.so.1 -> libvulkan.so.1.4.304 0644 .rw-r--r-- 535k root root 16 Jan 14:38 libvulkan.so.1.4.304 0644 .rw-r--r-- 2.0M root root 7 Mar 06:52 libvulkan_gfxstream.so 0644 .rw-r--r-- 21M root root 7 Mar 06:52 libvulkan_intel.so 0644 .rw-r--r-- 17M root root 7 Mar 06:52 libvulkan_intel_hasvk.so 0644 .rw-r--r-- 11M root root 7 Mar 06:52 libvulkan_lvp.so 0644 .rw-r--r-- 16M root root 7 Mar 06:52 libvulkan_nouveau.so 0644 .rw-r--r-- 14M root root 7 Mar 06:52 libvulkan_radeon.so 0644 .rw-r--r-- 1.3M root root 7 Mar 06:52 libvulkan_virtio.so The first one is the one created by me with that symlink command. Is Plasma looking just for the 'libvulkan.so' file? And not also for the 'libvulkan.so.1' file?, because to me that seems to me what it's doing and that's why the symlink fixed both problems. If this is what it's doing and you consider it's normal, please let me know so I will try to find a way to contact Debian developers to fix the missing file / symlink! Since after the other bug report and my solution that I found, I don't think anyone contacted them and this is the second case where it matters and it's works than just not showing the pills in the info center. For the other problem with everything crashing after login, Qt 6.9 will not help me at all as I plan to use Debian stable when it's released this summer and most likely it will use just Qt 6.8.2 for years to come. Please at least let me know if I should contact Debian developers / maintainers for that libvulkan file! If you know also where I can find the contact details, that could be great also. Thank you and please change the status of the report again to what you think it should be!
Created attachment 179543 [details] Crash log BTW, this is some crash log that I could save after doing that symlink command and was able to login successfuly while that environement variable was set. I don't know if it's for the panel crash of for something else that crashed. And I'm not sure if it's complete or not as pressing that button to install debug symbols was not clear if it worked or not. There was some output, but it was unclear if it downloaded and installed anything or there were some errors. I even disable the OpenSnitch application firewall that I normally use.
As a rule, don't set random environment variables. :) Vulkan isn't officially supported right now. The backtrace is incomplete, but it's enough to see that the crash is caused by 3rd-party code: #8 0x00007fc80ed37ba1 in ?? () from /usr/lib/x86_64-linux-gnu/mangohud/libMangoHud.so #9 0x00007fc80ec5b893 in ?? () from /usr/lib/x86_64-linux-gnu/mangohud/libMangoHud.so #10 0x00007fc80ec5bb39 in ?? () from /usr/lib/x86_64-linux-gnu/mangohud/libMangoHud.so #11 0x00007fc80ec4c71c in ?? () from /usr/lib/x86_64-linux-gnu/mangohud/libMangoHud.so #12 0x00007fc80ec5cfed in ?? () from /usr/lib/x86_64-linux-gnu/mangohud/libMangoHud.so #13 0x00007fc80ec3dd5b in ?? () from /usr/lib/x86_64-linux-gnu/mangohud/libMangoHud.so So if this isn't Bug 482754, then it's a bug in MangoHud. In general I would recommend discontinuing your experiments with Vulkan. This isn't something we formally support, and lots of things are known to be horribly broken.