Steam crashes when using ACES ocio for Blender
Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/12193.
@Toquita3D posted on 2025-07-11T21:47:24:
Steam client version: 1751405894
Distribution: Linux Mint 22.1
Opted into Steam client beta?: No.
Have you checked for system updates?: Yes
Steam Logs:
logs.zip
GPU: NVIDIA RTX 4070 Ti SUPER / Driver version 570.133.07
Steam crashes when using ACES instead of Filmic/AgX in Blender.
With Blender becoming more popular by the day, it's normal that many artists/studios will continue their pipeline as much as possible in the new software, and that includes using well established LUTS/OCIO configuration files such as ACES so that the look between e.g. Maya and Blender are the same and that no textures need to be changed for the new LUT/OCIO.
However, Steam crashes when using Blender with ACES during certain simple operations. The operation described below is only one instance of Steam crashing, it will crash many times per day but unfortunately I can never catch when/why.
Here's the crash message from the terminal (last line): https://pastebin.com/raw/xPU1qARZ
I also recorded a quick video showing the problem: https://www.youtube.com/watch?v=fRm2McrsjSM
@kisak-valve My bad for not using the search function.
Interesting that this happens with AgX as well.
If there's anything else I can provide to help fix this bug, let me know.
Happened to me with Blender v4.5. Simply ctrl + c a piece of Python code in scripting will also SEGFAULT steam (every time).
There seems to be a double conflict with Blender and Steam. I'm using Blender 4.5.2 and 4.5.3 (non-Steam versions).
Oddly enough, copying objects in Blender doesn't cause Steam to crash. Copying values does.
I can resize Blender's window, but the app doesn't redraw. Can't close the app normally either. I have to kill the process. Running a fresh instance of Blender with no copied values, and then Steam after doesn't cause Blender to lock up.
CPU: Ryzen 7 5700x3D
GPU: Radeon RX 6800
RAM: 32GB DDR4-3200
Mobo: MSI B550M PRO-VDH WIFI (BIOS 7C95v2M)
OS: Linux Mint 22.2
Kernel: 6.14.0-33-generic
DE: Cinnamon 6.4.8 (xorg)
GPU Driver: AMDGPU w/ Mesa 25.2.4 kisak-mesa PPA
crash_20251016142450_32.dmp[24146]: Finished uploading minidump (out-of-process): success = yes
crash_20251016142450_32.dmp[24146]: response: CrashID=bp-19021084-338b-41ef-a545-72b412251016
crash_20251016142450_32.dmp[24146]: file ''/tmp/dumps/crash_20251016142450_32.dmp'', upload yes: ''CrashID=bp-19021084-338b-41ef-a545-72b412251016''
/home/thebluewii/.steam/debian-installation/steam.sh: line 928: 22189 Segmentation fault (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@"
coredumpctl gdb steam
PID: 22189 (steam)
UID: 1000 (thebluewii)
GID: 1000 (thebluewii)
Signal: 11 (SEGV)
Timestamp: Thu 2025-10-16 14:24:50 EDT (48min ago)
Command Line: /home/thebluewii/.steam/debian-installation/ubuntu12_32/steam -srt-logger-opened
Executable: /home/thebluewii/.steam/debian-installation/ubuntu12_32/steam
Control Group: /user.slice/user-1000.slice/[email protected]/app.slice/app-org.gnome.Terminal.slice/vte-spawn-81e30c21-f19f-49dc-9e12-7a7744aeaf6b.scope
Unit: [email protected]
User Unit: vte-spawn-81e30c21-f19f-49dc-9e12-7a7744aeaf6b.scope
Slice: user-1000.slice
Owner UID: 1000 (thebluewii)
Boot ID: d008117340a74bd795cc1d588d56bdd7
Machine ID: 2f5d8a1906b6430393a5d665291a4f89
Hostname: LinuxBox-Max-2025
Storage: /var/lib/systemd/coredump/core.steam.1000.d008117340a74bd795cc1d588d56bdd7.22189.1760639090000000.zst (present)
Size on Disk: 34.6M
Message: Process 22189 (steam) of user 1000 dumped core.
Module libatomic.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.i386
Module libstdc++.so.6 from deb gcc-14-14.2.0-4ubuntu2~24.04.i386
Module libudev.so.1 from deb systemd-255.4-1ubuntu8.11.i386
Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2build1.1.i386
Module libsystemd.so.0 from deb systemd-255.4-1ubuntu8.11.i386
Module libgcc_s.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.i386
Stack trace of thread 22189:
#0 0x00000000f62fe7b6 n/a (libc.so.6 + 0xa97b6)
#1 0x00000000f1ef2798 n/a (/home/thebluewii/.steam/debian-installation/ubuntu12_32/libSDL3.so.0 + 0x25e798)
ELF object binary architecture: Intel 80386
Rumor has it, VALVe decided to fix this in about 6 years, the same time it will take them to fix TF2 crashing when running in Vulkan.
Finally got around to bisecting this. The Blender commit that introduced the behaviour that crashes Steam is https://projects.blender.org/blender/blender/commit/720fc44ca38330bbc1b8cfec5f37b56a2d6b46c3. @kisak-valve hopefully this finds its way to the appropriate developers and this can be fixed. It would seem like a fairly simple issue with how the Steam client handles the clipboard in X11.
Finally got around to bisecting this. The Blender commit that introduced the behaviour that crashes Steam is https://projects.blender.org/blender/blender/commit/720fc44ca38330bbc1b8cfec5f37b56a2d6b46c3. @kisak-valve hopefully this finds its way to the appropriate developers and this can be fixed. It would seem like a fairly simple issue with how the Steam client handles the clipboard in X11.
I noticed the problem doesn't happen when using Wayland (Fedora 43 KDE, Steam with Flatpak), was about to report this here. Thank you so much for your work!
I'm back on Mint so the problem still happens. Eager to get this resolved as it's really hard to work in 3D without copying text sometimes.
I noticed the problem doesn't happen when using Wayland (Fedora 43 KDE, Steam with Flatpak), was about to report this here. Thank you so much for your work!
I'm back on Mint so the problem still happens. Eager to get this resolved as it's really hard to work in 3D without copying text sometimes.
Can confirm! Tried Blender on Bazzite (KDE, Wayland) and couldn't get it to crash Steam there.
The crashes happen both on my Linux Mint system, and on SteamOS desktop mode on my Steam Deck, since they both use X11.
Finally got around to bisecting this. The Blender commit that introduced the behaviour that crashes Steam is https://projects.blender.org/blender/blender/commit/720fc44ca38330bbc1b8cfec5f37b56a2d6b46c3. @kisak-valve hopefully this finds its way to the appropriate developers and this can be fixed. It would seem like a fairly simple issue with how the Steam client handles the clipboard in X11.
Good bisecting!
I tried raising the issue to Blender here: https://projects.blender.org/blender/blender/issues/148794
Dev on Blender suggests it's a SDL3 issue, since that's what my Steam crash log links to.
What's interesting is before they updated the clipboard code, older Blender versions had it's own odd behaviours.
Example: If you close Steam and reopen it while running Blender 4.3 or older, it causes Blender to crash when you have a clipboard of something in Blender.
Hi, Blender developer here, this issue was fixed in commit 31f8f82. The fix will be present in the next 5.0.1 corrective release, and will be backported to 4.5 LTS. Thanks for bringing the issue to our attention :)
Blender 5.0.1 is out.
Issue is fixed! Steam no longer crashes when I copy a value.
Can confirm that it's fixed. Many thanks, and Happy Holidays to everyone!
Closing per the last handful of comments.
Your system information
Steam client version: 1747701111
Distribution: Void Linux + X11 + Cinnamon
Opted into Steam client beta?: Yes
Have you checked for system updates?: Yes
Steam Logs: steam-logs.tar.gz
GPU: Nvidia
Please describe your issue in as much detail as possible:
I am not sure if this is an issue on Blender's side of things or Steam's. My expectations are that Steam does not segfault. I am able to segfault Steam 100% of the time if it is open, including in the background, and I use Ctrl + C to copy a hex colour value from a colour picker in Blender. Using Blender 4.3.2 does not cause this problem, but 4.4.3 does. Copying the hex value, pasting it somewhere else, opening Steam, and copying it again from the other program does not cause the crash. Using or not using the Steam version of Blender does not make any difference.
Steps for reproducing this issue: