You skipped the "Steam Logs" step so it does make it a bit difficult. Can you run Steam in the terminal after fully exiting, and provide the version number shown in there. Also, while running Steam in the terminal, reproduce the issue and watch the terminal for output.

You skipped the "Steam Logs" step so it does make it a bit difficult. Can you run Steam in the terminal after fully exiting, and provide the version number shown in there. Also, while running Steam in the terminal, reproduce the issue and watch the terminal for output.

sorry, haven't really done this before, I usually don't have any issues with steam.
also, when it comes to the reproducing the issue part, how exactly do i put that? Am I supposed to say what I do to recreate it, or paste the terminal output?

• just looked over other posts, think i get it now

sorry, haven't really done this before

No worries. We just need to make it easier for people to help.

Am I supposed to say what I do to recreate it, or paste the terminal output?

Yeah, so when you want to explain how an issue is reproduced you can just give a step-by-step of how you encountered it.

For most issues with Steam it can be a lot easier to get concrete error messages if you run it in your terminal, try to recreate the issue, and paste any error messages you come across

post should be fixed now.
thanks

1: terminal says something about radv not conformant?WARNING: radv is not a conformant Vulkan implementation, testing use only. so I'd assume its something Radeon Vulkan related.

That's not an issue here. It's just a regulatory warning which you can ignore.

2: try and load a game 3: weep as it fails Removing process 56979 for gameID 2212330

Maybe provide some follow up lines too in the future

post should be fixed now. thanks

Awesome. If it's fixed for you, you can create a comment which shows how you resolved it, and then click "Close with comment" so this thread doesn't pollute the issue feed.

i meant like, the post should make more sense lol. unfortunately i still have an issue

Yep sorry, just realised, deleted the comment. Can you provide the full terminal output from when you click "play" to when it fails? Also remove ALL launch arguments

Can you provide the full terminal output from when you click "play" to when it fails? Also remove ALL launch arguments

could you specify what Launch arguments are? just to be uh... sure

could you specify what Launch arguments are? just to be uh... sure

When you open the gear icon for a game in the right -> properties -> launch options. Check its empty.

ah, yeah, its empty.

Can you provide the full terminal output from when you click "play" to when it fails?

Please provide this.

wineserver: NTSync up and running!
wineserver: NTSync up and running!
WARNING: radv is not a conformant Vulkan implementation, testing use only.
WARNING: radv is not a conformant Vulkan implementation, testing use only.
WARNING: radv is not a conformant Vulkan implementation, testing use only.
WARNING: radv is not a conformant Vulkan implementation, testing use only.
WARNING: radv is not a conformant Vulkan implementation, testing use only.
WARNING: radv is not a conformant Vulkan implementation, testing use only.
Fossilize INFO: Overriding serialization path: "/home/sleepi/.local/share/Steam/shader_cache_temp_dir_d3d12_64/fozpipelinesv6/steamapprun_pipeline_cache".
WARNING: radv is not a conformant Vulkan implementation, testing use only.
WARNING: radv is not a conformant Vulkan implementation, testing use only.
WARNING: radv is not a conformant Vulkan implementation, testing use only.
chdir "/home/sleepi/.local/share/Steam/steamapps/common/YourOnlyMoveIsHUSTLE"
Game Recording - would start recording game 2212330, but recording for this game is disabled
Adding process 63329 for gameID 2212330
ERROR: ld.so: object '/home/sleepi/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/sleepi/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/sleepi/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/sleepi/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/sleepi/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
WARNING: discarding _NET_WM_PID 5 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
Adding process 63330 for gameID 2212330
Game Recording - game stopped [gameid=2212330]
Removing process 63330 for gameID 2212330
Removing process 63329 for gameID 2212330

So the game you are attempting to play is "Your Only Move Is HUSTLE" and it provides a native Linux client. Please try this first by turning of "Force compatibility" in the gear icon settings.

So the game you are attempting to play is "Your Only Move Is HUSTLE" and it provides a native Linux client. Please try this first by turning of "Force compatibility" in the gear icon settings.

still having the issue. also, just to clarify, it also happens for other games, not just Your Only Move Is HUSTLE, its just the example i chose.

still having the issue. also, just to clarify, it also happens for other games, not just Your Only Move Is HUSTLE, its just the example i chose.

So the output is the same whether it's a Linux native game or through Proton? I would consider this to not be a Proton issue then.

Just ruling out some common things until someone else has any ideas:

• Your drive is NOT formatted in NTFS?
• What Mesa drivers is your 9060xt on?
• Your system has a iGPU correct? Ensure your drivers aren't failing on your 9060xt

• Your drive is NOT formatted in NTFS?

is there a way to easily check that? i use two ssd's; one with windows installed, the other with Nobara, installed Nobara a while ago now, cant quite remember how i formatted it...

• What Mesa drivers is your 9060xt on?

once again, is there a way to check that?

• Your system has a iGPU correct? Ensure your drivers aren't failing on your 9060xt

man, this fell on deaf ears, once again, a way to check? pretty sure i have an iGPU just not sure how to ensure that...

is there a way to easily check that? i use two ssd's; one with windows installed, the other with Nobara, installed Nobara a while ago now, cant quite remember how i formatted it...

I'm not too familiar with Nobara, but I'm assuming you have a disk partitioning tool? Find what partition you have installed your games on. Each partition will have a filesystem type, and you just need to check that your games aren't installed on a NTFS partition, as it isn't supported well in Linux and is a reverse engineered solution. EXT4 or BTRFS are recommended.

If you don't have a partition app, you can always use lsblk for disk listing, as well as sudo blkid for filesystem types.

• What Mesa drivers is your 9060xt on?
  once again, is there a way to check that?

I have just checked your Steam logs, looks like 26.03 so I think you're all good there. In future, go to your package manager (I believe Nobara uses some form of DNF or RPM) and search for Mesa. So maybe dnf --search mesa.

• Your system has a iGPU correct? Ensure your drivers aren't failing on your 9060xt
  man, this fell on deaf ears, once again, a way to check? pretty sure i have an iGPU just not sure how to ensure that...

Well it looks like from your logs Steam defaults to your 9060xt so you should be all good there.

Just have to work through some common issues. I don't know if you've stated this yet, but have your games ever worked for you before?

I'm not too familiar with Nobara, but I'm assuming you have a disk partitioning tool? Find what partition you have installed your games on. Each partition will have a filesystem type, and you just need to check that your games aren't installed on a NTFS partition, as it isn't supported well in Linux and is a reverse engineered solution. EXT4 or BTRFS are recommended.

news: checked my partition manager, not sure why that wasn't a thought i had sooner, anyway, checked it and my partitions are ext4. (except for the bootloader, of course)

I have just checked your Steam logs, looks like 26.03 so I think you're all good there. In future, go to your package manager (I believe Nobara uses some form of DNF or RPM) and search for Mesa. So maybe dnf --search mesa.

ill try and remember that. thanks.

Well it looks like from your logs Steam defaults to your 9060xt so you should be all good there.

Just have to work through some common issues. I don't know if you've stated this yet, but have your games ever worked for you before?

yeah, my games worked for me at some point. it might have been before i updated to Nobara 43? Im thinking that could possibly have something to do with it.

news: checked my partition manager, not sure why that wasn't a thought i had sooner, anyway, checked it and my partitions are ext4. (except for the bootloader, of course)

You say "all" your partitions are ext4, but you have a second drive with Windows, correct? You're certain you don't have your games installed on the Windows drive?

Also, can you confirm the terminal output is exactly the same for both Proton games and native Linux?

Because it worked before the update, this is probably something to do with Steam runtime or system drivers, so I don't know too much onwards.

Does Nobara have a full system sync/update? Give that a shot. Also maybe toggle Steam beta in the Steam settings -> interface -> beta.

You say "all" your partitions are ext4, but you have a second drive with Windows, correct? You're certain you don't have your games installed on the Windows drive?

i have games installed on the windows drive, but my games on this drive arent situated there, im fairly certain.

Also, can you confirm the terminal output is exactly the same for both Proton games and native Linux?

some lines happen in different orders, but otherwise they are basically identical.

Because it worked before the update, this is probably something to do with Steam runtime or system drivers, so I don't know too much onwards.

Does Nobara have a full system sync/update? Give that a shot. Also maybe toggle Steam beta in the Steam settings ->
interface -> beta.

will do. ill get back with the results.

steam beta on made no difference to off.
I also dont have any updates as far as im told.

steam beta on made no difference to off. I also dont have any updates as far as im told.

Might not be a steam issue. I'm leaning towards graphics drivers/desktop environment. Get the output of vulkaninfo --summary.

Might not be a steam issue. I'm leaning towards graphics drivers/desktop environment. Get the output of vulkaninfo --summary.

Vulkan Instance Version: 1.4.341

Instance Extensions: count = 26

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_layer_settings : extension revision 2
VK_EXT_surface_maintenance1 : extension revision 1
VK_EXT_swapchain_colorspace : extension revision 5
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_maintenance1 : extension revision 1
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 = 13

VK_LAYER_FROG_gamescope_wsi_x86 Gamescope WSI (XWayland Bypass) Layer (x86) 1.3.221 version 1
VK_LAYER_FROG_gamescope_wsi_x86_64 Gamescope WSI (XWayland Bypass) Layer (x86_64) 1.3.221 version 1
VK_LAYER_MANGOHUD_overlay_x86 Vulkan Hud Overlay 1.3.0 version 1
VK_LAYER_MANGOHUD_overlay_x86_64 Vulkan Hud Overlay 1.3.0 version 1
VK_LAYER_MESA_anti_lag Open-source implementation of the VK_AMD_anti_lag extension. 1.4.303 version 1
VK_LAYER_MESA_device_select Linux device selection layer 1.4.303 version 1
VK_LAYER_OBS_vkcapture_32 OBS Linux game capture 1.4.321 version 1
VK_LAYER_OBS_vkcapture_64 OBS Linux game capture 1.4.321 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
VK_LAYER_VKBASALT_post_processing a post processing layer 1.3.223 version 1

Devices:

GPU0:
apiVersion = 1.4.335
driverVersion = 26.0.3
vendorID = 0x1002
deviceID = 0x7590
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = AMD Radeon RX 9060 XT (RADV GFX1200)
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 26.0.3
conformanceVersion = 1.4.0.0
deviceUUID = 00000000-0300-0000-0000-000000000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000
GPU1:
apiVersion = 1.4.335
driverVersion = 26.0.3
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 21.1.8, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 26.0.3 (LLVM 21.1.8)
conformanceVersion = 1.3.1.1
deviceUUID = 6d657361-3236-2e30-2e33-000000000000
driverUUID = 6c6c766d-7069-7065-5555-494400000000

I'm running low on troubleshooting ideas here. Maybe someone a bit more knowledgeable would be able to help out in the future.

For now, update your post to show the information you've gathered, including, your GPUs, vulkaninfo, drive layout (filesystem types), when it failed, if your games were working before, both beta/stable Steam clients, Proton or Native, etc.

I'm running low on troubleshooting ideas here. Maybe someone a bit more knowledgeable would be able to help out in the future.

For now, update your post to show the information you've gathered, including, your GPUs, vulkaninfo, drive layout (filesystem types), when it failed, if your games were working before, both beta/stable Steam clients, Proton or Native, etc.

yeah, ill do that now. thanks for all the help otherwise, at least im learning something from this, lol.

My friend had a similar problem, don't know if it is related but the issue he had was the sniper 3.0 runtime was corrupted somehow and removing it from its location then verifying fixed the problem and was able to launch his games again

11/6/26 9:34 pm steam pressure-vessel-wrap[4184840]: E: Unable to open "./manifest.dpkg.built-using" in "/home/username/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-F4OSQ3/usr": openat(manifest.dpkg.built-using): Too many levels of symbolic links