Hello! When running any video game in Lutris (LMDE 7) it crashes. It doesn’t matter if they’re Windows (run via Wine) or ProtonDB based. It worked almost flawlessly some days before it suddenly stopped working. Maybe I did some configuration that broke it all. When using Steam, it runs flawlessly. It’s only Lutris and even Heroic.

The log when opening Metro 2033 Redux as reference:

Started initial process 19668 from gamescope -w 2560 -h 1440 -W 2560 -H 1440 -f – gamemoderun (…)/lutris/runners/wine/lutris-7.2-2-x86_64/bin/wine (…)/drive_c/GOG Games/Metro 2033 Redux/metro.exe Start monitoring process. No CAP_SYS_NICE, falling back to regular-priority compute and threads. Performance will be affected. wlserver: [backend/headless/backend.c:82] Creating headless backend vulkan: selecting physical device ‘NVIDIA GeForce RTX 3070 Ti’: queue family 2 vulkan: physical device supports DRM format modifiers vulkan: vkCreateDevice failed (VkResult: -7) Failed to initialize Vulkan Monitored process exited. Initial process has exited (return code: 256) All processes have quit Exit with return code 256

I have had no clue of how to solve this for at least one week.

For context: I’m a total beginner in Linux. Came from windows 10 just like 2 months ago. No background in programing or anything related.

If I’m missing any info of value let me know. Thanks!

  • muhyb@programming.devEnglish
    6·
    14 hours ago

    This usually happens when you update your system but not flatpak. Update flatpak and it should be fine.

  • andrewta@lemmy.worldEnglish
    9·
    19 hours ago

    I’m just jumping in here to say welcome to Linux mint and I hope these people get things sorted for you.

    • Well1@lemmy.worldOPEnglish
      7·
      19 hours ago

      Thanks mate! Very glad I finally did the jump into the Linux world 🫡

  • dgdft@lemmy.worldEnglish
    10·
    20 hours ago

    Good job putting this together! Lots of useful info in your post.

    My eye is locking onto this bit in the logs: vkCreateDevice failed (VkResult: -7). Vulkan is failing to initialize, seemingly because of some missing extension.

    Try these for us and share your output, if you’d be so kind. Feel free to scrub any parts you don’t wanna share with a [REDACTED]. I’m mostly going off memory so some of them may fail and that’s okay:

    sudo dmesg | grep -i err | tail -10
nvidia-smi
inxi -Gxx
which vulkaninfo
which amdvlk
which vulkan-intel
vulkaninfo --summary
gamescope -- vkcube
vkcube
cat /sys/module/nvidia_drm/parameters/modeset
    • Well1@lemmy.worldOPEnglish
      6·
      20 hours ago

      Thanks for your kind reply! Here’s what it returns:

      [ 0.461210] ACPI: PCI: Interrupt link LNKC configured for IRQ 0 [ 0.461258] ACPI: PCI: Interrupt link LNKD configured for IRQ 0 [ 0.461302] ACPI: PCI: Interrupt link LNKE configured for IRQ 0 [ 0.461339] ACPI: PCI: Interrupt link LNKF configured for IRQ 0 [ 0.461376] ACPI: PCI: Interrupt link LNKG configured for IRQ 0 [ 0.461412] ACPI: PCI: Interrupt link LNKH configured for IRQ 0 [ 0.488486] AMD-Vi: Interrupt remapping enabled [ 1.401453] RAS: Correctable Errors collector initialized. [ 4.003006] sd 4:0:0:0: [sda] Preferred minimum I/O size 4096 bytes [ 7058.871691] xhci_hcd 0000:02:00.0: xHC error in resume, USBSTS 0x401, Reinit Mon Oct 26 21:13:20 2026
      ±----------------------------------------------------------------------------------------+ | NVIDIA-SMI 550.163.01 Driver Version: 550.163.01 CUDA Version: 12.4 | |-----------------------------------------±-----------------------±---------------------+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=========================================+========================+======================| | 0 NVIDIA GeForce RTX 3070 Ti Off | 00000000:07:00.0 On | N/A | | 0% 41C P5 41W / 310W | 4195MiB / 8192MiB | 20% Default | | | | N/A | ±----------------------------------------±-----------------------±---------------------+

      ±----------------------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=========================================================================================| | 0 N/A N/A 2706 G /usr/lib/xorg/Xorg 2830MiB | | 0 N/A N/A 3028 G cinnamon 112MiB | | 0 N/A N/A 3118 G /usr/bin/python3 15MiB | | 0 N/A N/A 6714 G …bian-installation/ubuntu12_32/steam 122MiB | | 0 N/A N/A 7040 G ./steamwebhelper 175MiB | | 0 N/A N/A 17635 G …cess-track-uuid=3190708988185955192 590MiB | | 0 N/A N/A 18392 G …allation/ubuntu12_64/steamwebhelper 21MiB | | 0 N/A N/A 18612 G …cess-track-uuid=3190708988185955192 303MiB | ±----------------------------------------------------------------------------------------+ Graphics: Device-1: Blackmagic Design [REDACTED] driver: blackmagic-io v: 16.4a1 pcie: speed: 5 GT/s lanes: 4 bus-ID: 04:00.0 chip-ID: [REDACTED] Device-2: NVIDIA GA104 [GeForce RTX 3070 Ti] vendor: ZOTAC driver: nvidia v: 550.163.01 arch: Ampere pcie: speed: 5 GT/s lanes: 16 bus-ID: 07:00.0 chip-ID: [REDACTED] Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6 driver: X: loaded: nvidia gpu: blackmagic-io,nvidia display-ID: :1 screens: 1 Screen-1: 0 s-res: 10240x2880 s-dpi: 120 Monitor-1: DP-0 pos: primary,right res: 2560x1440 hz: 60 dpi: 109 diag: 685mm (26.97") Monitor-2: HDMI-0 pos: left res: 3840x2160 hz: 60 dpi: 163 diag: 685mm (26.97") API: EGL v: 1.5 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: 550.163.01 glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 API: Vulkan v: 1.4.309 surfaces: xcb,xlib device: 0 type: discrete-gpu driver: nvidia device-ID: 10de:2482 device: 1 type: cpu driver: mesa llvmpipe device-ID: 10005:0000 Info: Tools: api: eglinfo, glxinfo, vulkaninfo gpu: nvidia-settings,nvidia-smi x11: xdriinfo, xdpyinfo, xprop, xrandr /usr/bin/vulkaninfo WARNING: [Loader Message] Code 0 : Layer VK_LAYER_NV_optimus uses API version 1.3 which is older than the application specified API version of 1.4. May cause issues.

      VULKANINFO

      Vulkan Instance Version: 1.4.309

      Instance Extensions: count = 24

      VK_EXT_acquire_drm_display : extension revision 1 VK_EXT_acquire_xlib_display : extension revision 1 VK_EXT_debug_report : extension revision 10 VK_EXT_debug_utils : extension revision 2 VK_EXT_direct_mode_display : extension revision 1 VK_EXT_display_surface_counter : extension revision 1 VK_EXT_headless_surface : extension revision 1 VK_EXT_surface_maintenance1 : extension revision 1 VK_EXT_swapchain_colorspace : extension revision 4 VK_KHR_device_group_creation : extension revision 1 VK_KHR_display : extension revision 23 VK_KHR_external_fence_capabilities : extension revision 1 VK_KHR_external_memory_capabilities : extension revision 1 VK_KHR_external_semaphore_capabilities : extension revision 1 VK_KHR_get_display_properties2 : extension revision 1 VK_KHR_get_physical_device_properties2 : extension revision 2 VK_KHR_get_surface_capabilities2 : extension revision 1 VK_KHR_portability_enumeration : extension revision 1 VK_KHR_surface : extension revision 25 VK_KHR_surface_protected_capabilities : extension revision 1 VK_KHR_wayland_surface : extension revision 6 VK_KHR_xcb_surface : extension revision 6 VK_KHR_xlib_surface : extension revision 6 VK_LUNARG_direct_driver_loading : extension revision 1

      Instance Layers: count = 8

      VK_LAYER_INTEL_nullhw INTEL NULL HW 1.1.73 version 1 VK_LAYER_MESA_device_select Linux device selection layer 1.4.303 version 1 VK_LAYER_MESA_overlay Mesa Overlay layer 1.4.303 version 1 VK_LAYER_NV_optimus NVIDIA Optimus layer 1.3.277 version 1 VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.3.207 version 1 VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.3.207 version 1 VK_LAYER_VALVE_steam_overlay_32 Steam Overlay Layer 1.3.207 version 1 VK_LAYER_VALVE_steam_overlay_64 Steam Overlay Layer 1.3.207 version 1

      Devices:

      GPU0: apiVersion = 1.3.277 driverVersion = 550.163.1.0 vendorID = 0x10de deviceID = 0x2482 deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU deviceName = NVIDIA GeForce RTX 3070 Ti driverID = DRIVER_ID_NVIDIA_PROPRIETARY driverName = NVIDIA driverInfo = 550.163.01 conformanceVersion = 1.3.7.2 deviceUUID = [REDACTED] driverUUID = [REDACTED] GPU1: apiVersion = 1.4.305 driverVersion = 0.0.1 vendorID = 0x10005 deviceID = 0x0000 deviceType = PHYSICAL_DEVICE_TYPE_CPU deviceName = llvmpipe (LLVM 19.1.7, 256 bits) driverID = DRIVER_ID_MESA_LLVMPIPE driverName = llvmpipe driverInfo = Mesa 25.0.7-2+deb13u1 (LLVM 19.1.7) conformanceVersion = 1.3.1.1 deviceUUID = [REDACTED] driverUUID = [REDACTED] No CAP_SYS_NICE, falling back to regular-priority compute and threads. Performance will be affected. wlserver: [backend/headless/backend.c:82] Creating headless backend vulkan: selecting physical device ‘NVIDIA GeForce RTX 3070 Ti’: queue family 2 vulkan: physical device supports DRM format modifiers vulkan: vkCreateDevice failed (VkResult: -7) Failed to initialize Vulkan Selected WSI platform: xcb Selected GPU 0: NVIDIA GeForce RTX 3070 Ti, type: DiscreteGpu cat: /sys/module/nvidia_drm/parameters/modeset: Permission denied.

      • dgdft@lemmy.worldEnglish
        8·
        18 hours ago

        Based on that output, I agree with the other comment that gamescope is your culprit. Try running this:

        sudo cat /sys/module/nvidia_drm/parameters/modeset

        It was in the last set, but I left off the sudo prefix on accident. If it outputs “N” or “0”, we’ve got an answer: gamescope needs KMS to run, but you’ve got an older GPU driver version (v550) and DRM (which KMS depends on) isn’t turned on by default until v560 per https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_setting.

        So if that is the issue, this should sort you out as a fix and get gamescope running again. Be aware that it’ll reboot your PC in the process:

        echo 'options nvidia-drm modeset=1' | sudo tee /etc/modprobe.d/nvidia-drm-modeset.conf
sudo update-initramfs -u
sudo reboot
    • Well1@lemmy.worldOPEnglish
      5·
      20 hours ago

      I was about to send a reply saying I already tried that and didn’t work. Guess what: it kinda worked haha. I tried opening Metro 2033 and worked (weird thing: My GPU and fans or whatever started go berserk. Didn’t stop until I activated VSync, smh). Now what I would need to solve would be being able to run locally preinstalled games (the one I have was installed via Bottles) and fix gamescope so I can use it without crashing. Thank you very much!

      • Leigh Weigh@lemmy.worldEnglish
        3·
        14 hours ago

        Most things can be installed via steam now as well. I stopped using lutris completely. You can go to install non steam game, find your game in your files and add it. Then go into the settings before you run it and force it to run with proton. Proton experimental seems to have covered most of my games but you can go a search and see what other people have had luck with.

  • yaroto98@lemmy.worldEnglish
    3·
    20 hours ago

    I recently switched from proton-ge to proton-cachyos. When I did that it broke the configs, and had a similar issue. I wonder if an update is having the same symotoms of nullifying your wine-cfg.

    Go into heroic edit a game’s configs and see if there’s an empty wine-cfg. Try pointing it to proton-experimental or whatever you were using before. It’s just a dropdown selector.

  • femtek@lemmy.blahaj.zoneEnglish
    3·
    21 hours ago

    What Linux OS? I saw there was an update to cachy that broke some GPU support but they fixed it later.

  • Not a newt@piefed.caEnglish
    2·
    19 hours ago

    Just to rule out the simple stuff - have you restarted your computer? Some drivers get kernel-specific versions, and if you ran updates recently then you may have the version built for the newer kernel but might still be running the old one. A restart would address this.

    • Well1@lemmy.worldOPEnglish
      2·
      19 hours ago

      Yeah, I turned on and off several times the system since it started at least one week ago

  • AcornTickler@sh.itjust.worksEnglish
    1·
    19 hours ago

    Do you know if you have installed those through flatpak or not? You can verify this by running flatpak list in a terminal. It would be helpful if you shared the entire output of that command, particularly relevant parts would be about Nvidia drivers.

    • Well1@lemmy.worldOPEnglish
      1·
      19 hours ago

      I’m totally sure I didn’t. Installed metro via Lutris GOG installer and Dysco Elysium via Bottles and then “Add locally installed game” pointing to a .bat that runs the game.