#[SPZ2-6003] [0.1.1] Linux - Game crash on FN key presses and alt-tabbing

195 messages · Page 1 of 1 (latest)

hexed warren
#

I haven't gotten to play yet but figured I'd report this bug first seeing as it happened a total of 5 times and I can consistently recreate it.

Specifically the press of the F3 key on my laptop, which in my case is for increasing the volume on the pc, makes the game crash. The game also crashed if I were to alt tab out of the game.

I have 5 files, all with similar names, latest one named mono_crash.mem.13943.1.blob. All 5 of these files contains around ~625.000 lines of plain 0's.

There's no information given on the crashes; the game simply closes.

I saw this line in another bug report, but that folder does not exist on my system sadly, so wont be able to find any logs there;
"Need the playr.log file for the crash, should be on: ~/.config/unity3d/tobspr Games/shapez 2/"

Files were all verified with no errors found.

OS: Ubuntu Desktop 25.04 (64-bit)
CPU: Intel® Core™ i5-1035G1
Memory: 8GB
Kernel: 6.14.0-32-generic
Graphic API: Vulkan
Game Build: 18963735

#

[0.1.1] Linux - Game crash on FN key presses and alt-tabbing

timber stream
#

Im not a mod or anything, but i also play on linux and managed to solve this by using gamescope

#

Had the same thing

#

SDL_VIDEODRIVER=wayland gamescope -f -- %command%

#

I added that to steam launch command thingy

hexed warren
#

Thanks, I do want a permanent fix tho. Can't get to 1.0 with bugs literallythis

waxen spear
waxen spear
#

@hexed warren Could you try the following for me?:

  1. Start Shapez2
  2. Go to settings
  3. Go to Graphics
  4. Change from Full Screen to Borderless
  5. Press Apply

Then see if the problem is still happening?

hexed warren
#

I will follow up on this. I just had a wisdom tooth removed the other day, so do be patient 🙏

hexed warren
#

I noticed just now that the problem also only happens when the FN buttons are activated, so just pressing F3 by itself does not make the game crash but when I activate FN and then press F3 (Volume Up), the game then crashses

waxen spear
#

Oh. Also which version of Linux?

#

Ubuntu Desktop 25.04 (64-bit)

hexed warren
#

I don't really know what Proton is tbh

waxen spear
#

Where can I download that? I am reinstalling everything on my computer this week. I might as well install your exact OS.

waxen spear
hexed warren
waxen spear
hexed warren
waxen spear
#

Cool. Good to know 🙂

#

gnome should be interesting to try out.

hexed warren
#

Been doing good for me. It's an old laptop and it was really struggling and moving to Ubuntu Desktop from Windows made a huge difference, and it's now a usuable laptop again 😄

waxen spear
#

Nice. Main reason I installed Linux was because I got employed at tobspr and knew that Shapez2 was supported on linux.

hexed warren
#

Linux is super fun and super frustrating!

waxen spear
#

I would prefer it over windows if it wasn't for the fact that it doesn't has as much stuff as windows does for applications etc

#

Yeah, linux likes to have interesting issues doesn't it...

hexed warren
#

Yup, I agree. I would've completely switched already if it wasn't for the lack of support for programs like Photoshop and general game support

hexed warren
waxen spear
#

I broke my first install of linux because I didn't realise that I could use the OS itself to install stuff.

#

Bluetooth wasn't working so I was sudoing this and sudoing that in the terminal until the OS no longer worked correctly.

hexed warren
#

As you should honestly. I've learned soo much more from my mistakes than the things that has worked out of the box

waxen spear
#

But the most recent problem is that linux couldn't see the windows 11 created D drive so steam could run. I was able to fix it by fixing something to do with the drive, but eventually it wouldn't work.

#

I started screwing up from the first time I installed windows 95

hexed warren
waxen spear
#

I screwed up so many times that I got to the point I had no fear of windows issues, because I knew what I was doing to dodge them.

waxen spear
hexed warren
#

Recently set up raid for 2 drives on my server, and had so many problems with it

waxen spear
#

Ouch. Its been a while since I used raid, like so long ago that the HDD were still chunky 😉

hexed warren
#

These are also chunky. Server-grade HDDs, as they need to withstand the vibrations and needs reliability as they will be running non-stop 😄

waxen spear
#

So, maybe still chunky ones then 😛

hexed warren
#

Yup, but only for the server 😁

waxen spear
#

makes sense

hexed warren
#

Let me know if there's anything else you want me to test, or if there's any news on the issue

waxen spear
#

I had no issues myself using the latest version

#

Previous to that I had Kubuntu, that didn't have any issues either.

hexed warren
#

I am not able to upgrade yet, without having to reinstall my system

waxen spear
hexed warren
#

Yeah, just waiting for Ubuntu to release the upgrade

hexed warren
#

I can finally confirm that the error is still present on the newest version of Ubuntu (25.10)

waxen spear
hexed warren
#

This should hopefully help 🙏

waxen spear
# hexed warren

Awesome 🙂
I apologise. Not sure if the player.log file actually had the game crash with the steps I gave.
Can you do the above steps, then cause the game to crash (with F3/alt-tabbing), then after fully crashing can you give me the log file again?

Also we didn't try proton did we?
If you want to try that do the following as per the screenshot:

  1. Right click on shapez2 in the main steam library
  2. Then click properties
  3. Then click Compatibility on the left menu
  4. Then choose to force the use of a specific Steam Play compatibility tool and choose Proton 9.0-4
image.png
hexed warren
waxen spear
hexed warren
waxen spear
waxen spear
#

Asking people who might know.

hexed warren
#

Sounds good. I'll test with Proton as soon as I get home

hexed warren
waxen spear
hexed warren
#

My laptop is too old and weak so I'll have to wait till 1.0 sadly, but good to know that the problem is already known

waxen spear
hexed warren
#

All graphics on lowest is still less than 30fps. Maybe around 20-24fps

#

Cant get myself to buy a new laptop as long as this one still works haha

waxen spear
#

30fps is playable. Not sure about 20-24

#

Sorry you have to wait for your current computer to die. I try to buy a new computer that will last for years, and then replace it when it gets too slow for games to be fun.

#

Or...if the computer gets too old where I fear it will stop working. Then I will want to get another one.

hexed warren
#

I do have a beefy desktop which is why it feels silly to upgrade my laptop when it still works so no worries. I'm surprised my laptop can even run the game so I don't mind waiting for 1.0

waxen spear
sick storm
#

Having this same issue with i3 4.24 and Fedora 42. As soon as I switch away to a different window, the game crashes, I don't even need to load a save.

I tried changing between "Windowed", "Borderless", "and "Fullscreen" and they all have the same issue

📎 shapez2.log
oak basin
waxen spear
fossil wolf
#

on 1.0.2-rc and I can confirm that the bug still occurs. I'm guessing it's more of a problem with unity than you guys, but still it's a big shame

#

like you have a linux version but it's unusable if you don't have gamescope installed

#

would be happy to provide logs, or something to help fix the bug

rigid gale
#

same here, SDL_VIDEODRIVER=wayland no longer instantly crashes but the game still crashes when alt tabbing or making any UI element draw over the window. Fresh install of CachyOS, Ryzen 5 5600X, Radeon RX 6650XT, KDE plasma Wayland session.

cedar mesa
#

Can confirm with 1.0.2-rc1, default Steam Linux runtime (scout / no compatibility tool used) on Arch Linux, AMD Ryzen 5 5600, AMD Radeon RX 6600, sway. Crashes on launch likely due to how focusing works :(

rigid gale
#

gamescope seems fine as a workaround, not a super huge fan of the input delay but maybe it won't be noticeable for a game like this

#

SDL_VIDEODRIVER=wayland gamescope -f -w 1920 -h 1080 -r 60 -- %command% my launch flags, had to specify monitor width and height because it wasn't properly detecting my screen resolution without

cedar mesa
#

Oh, interesting. gamescope has never worked for me but your command does work. Stuck to the default resolution, unfortunately... I don't use fullscreen all the time, so it's kinda annoying, but from what I know that's one of the areas that are buggy for shapez 2

rigid gale
#

from the game's perspective it will still be a fullscreen window at whatever resolution you set it as but you can freely stretch and resize the window containing it as you see fit

cedar mesa
#

As far as I can understand it's letterboxed only, which is what I meant

image.png
rigid gale
#

ah yeah i can see how that'd be a problem

hasty niche
#

I don't have any of those issue running the game on Linux/Hyprland. I can drag stuff over it etc etc and the game just runs fine.

cedar mesa
hasty niche
#

For me it just doesn't allow my resolution unless I switch to window mode, but I think that's a unity issue

cedar mesa
#

Actually I have rechecked the Linux issue threads and the reporter just switched to Proton, no follow-up on any kind of fix. If your shapes are rendering correctly (not missing entirely or displaying with glitches) then you are lucky to have an unaffected setup

cedar mesa
hasty niche
#

Well, I'm on a tiling window manager, so stuff works a little different. But I'm having no issues moving from this to another, or pushing it to another workspace etc

#

Performance is better than with proton as well

rigid gale
hasty niche
#

I have to run it exclusively in windowed mode (but I then force Hyrpland to make it fullscreen) because otherwise Unity likes to pretend my 5120x1440 resolution doesn't exist and maxes out at 3440x1440

rigid gale
#

if you set the game to use full screen and alt tab or open a dialog like a volume slider does it crash?

hasty niche
#

Like if I force to the window mode to be fullscreen and then do those things, or you mean the fullscreen in-game setting?

rigid gale
#

the ingame setting

cedar mesa
#

Oh, right. I think my issues were related to the fullscreen setting, but it also crashes when I use WM fullscreen actions

thin dew
#

This is where the game just disappears (stops running) when focusing on another window/monitor?

hasty niche
thin dew
#

Ubuntu?

timber onyx
#

hai, arch user here

#

what distro?

rigid gale
# hasty niche

might just be something to do with hyprland then, kwin doesn't draw windows over fullscreen applications, it gets minimized when focused on something else

hasty niche
rigid gale
# timber onyx what distro?

cachyOS but it was also happening to me on endeavour too which too my knowledge is pretty close to pure arch

#

not sure it's distro specific though, i think i saw reports of this bug on fedora too?

timber onyx
#

can u send you hardware?

timber onyx
#

whatever, we need you specs

#

or you can just name the brand

rigid gale
#

one sec i remember there was a command for dumping all the hardware details but i don't remember what it was

timber onyx
#

use fetch

#

we don't need 100% accurate result

rigid gale
timber onyx
#

plasma 💀

#

da basics:
update system and reboot

#

you did it, yeah?

rigid gale
#

will do, has been like a week since i last updated

timber onyx
#

bro

#

this is a small problem

neat harborBOT
#

[SPZ2-6003] [0.1.1] Linux - Game crash on FN key presses and alt-tabbing

#

🔗 This bug has been linked to our internal ticket SPZ2-6003. Our development team will now have a look. Feel free to comment with further information if you believe it might be useful!

thin dew
#

When it was happening to me I found that it could be countered by being in windowed windowed mode, but borderless it still crashed.

rigid gale
#

borderless and fullscreen do the same thing on linux iirc

timber onyx
#

lemme check

#

borderless works fine to me

#

arch+hyprland on intel+nvidia

#

i mean i can do this

image.png
#

it's your issue, the main point

#

DAYM BRO 3 DAYS OF UPTIME

rigid gale
#

packages up to date and rebooted, still crashing on fullscreen without the gamescope workaround

hasty niche
rigid gale
#

also my computer is asleep most of the time, it hasn't been running for 3 days straight

timber onyx
#

hell nah

timber onyx
#

or native build

rigid gale
#

native

timber onyx
#

u sure?

rigid gale
#

i have used proton in the past and it works but i get better performance with the native build

rigid gale
timber onyx
#

hmh

rigid gale
timber onyx
#

have you tried looking trough logs?

-# it's a nightmare, when i was fixing forza horizon 5 it created file with 1.6GB and 30million lines

#

steam logs*

rigid gale
#

like, run steam in the terminal and view the output or do you mean the unity generated player.log?

timber onyx
#

i guess seeing both is good

#

and i think unity's is better

rigid gale
#

i remember not seeing much in either but i'll look again

timber onyx
#

alr

#

i'm gonna sleep

#

see you tomorrow, if it will not fix

rigid gale
neat harborBOT
# rigid gale
📋 Log File Analysis

Log Analysis (Player.log):

  1. Fatal Runtime Error: A fatal error occurred in the Mono runtime or one of the native libraries, with native fault reporting also failing, leaving some diagnostic information unavailable.
cedar mesa
#

I launched a terminal emulator in and outside of gamescope to test what environment variables are different, with the intent of suggesting inclusion of additional Linux-specific logging in the next game builds for better analysis. Just to see what happens, I have applied most of the changes to my launch command instead. Sadly, the following did not work:

SDL_VIDEODRIVER=wayland DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0 vk_khr_present_wait=true vk_xwayland_wait_ready=false XDG_SESSION_TYPE=x11 XWAYLAND_FORCE_ENABLE_EXTRA_MODES=1 %command%
```Setting SDL_VIDEODRIVER is probably a placebo when running outside of gamescope by the way, here I tried both with and without SDL_VIDEODRIVER. It's not like that should work since I'm setting XDG_SESSION_TYPE=x11 anyway
cedar mesa
#

The information I got from another report (#1498068026057035927) is interesting. Has anyone else tested Proton + Vulkan + no gamescope? On my system (RX 6600, Arch Linux, sway) it doesn't crash, although there are some artifacts. Windowed mode seems to work (also with artifacts), the game is very slow overall. Steam Overlay displays but is pretty much unusable. To ensure this wasn't something that affected Linux too, I disabled Steam Overlay and Game Recording, then switched back to no compatibility tool. The game doesn't seem to crash when using 800x600 fullscreen resolution (I can even get a letterboxed window if I force switch to windowed using WM actions), but as soon as I set the resolution to 1920x1080 the game becomes unstable. I can't enter or exit fullscreen mode without a crash and the game will crash on startup (NOTE: the latter only applies to sway, I could launch the game without issues on KDE Plasma, however it does crash on unfocus).

I remembered Vulkan validation layers were a thing and tried applying them with VK_LOADER_LAYERS_ENABLE="*validation" %command% --no-dynamic-content (the last flag is a personal preference and should not affect rendering). It looks like the game is definitely doing something wrong, but only developers can figure out the root cause. I am completely okay with sharing any rendering traces, memory dumps, trying out debug builds, giving more details about my hardware etc. if instructed to do so by a team member. The only thing I cannot do is shipping my entire setup to Germany, even though that would probably be the most helpful thing for debugging.

📎 Player.log
neat harborBOT
# cedar mesa The information I got from another report (<#1498068026057035927>) is interestin...
📋 Log File Analysis

Log Analysis (Player.log):

Error Analysis: Player.log

  1. Curl SSL Error: A TLS certificate verification failure occurred during a network request (Curl error 35), with UnityTls error code 7 indicating the certificate was omitted or unsupported. This error occurred twice.

  2. Vulkan Validation Error: vkAcquireNextImageKHR violated validation rule VUID-vkAcquireNextImageKHR-surface-07783 (MessageID 0xad0e15f6).

  3. Vulkan Validation Error: vkCmdEndRenderPass violated validation rule VUID-vkCmdEndRenderPass-renderpass (MessageID 0x46db6f2f).

  4. Mono Runtime Fatal Error: A fatal error occurred in the Mono runtime or a native library, with the native fault reporter also failing, leaving some diagnostic information unavailable.

cedar mesa
#

-# The bot is horrible. WE ALL KNOW IT'S 6003 💀
Well, some of the other bugs it lists are probably also the same bug

rustic cloak
cedar mesa
#

I don't think this can be solved by using some magic envvars or using Proton (the latter cannot be a proper permanent solution), but the more testing is done on different hardware+software setup the easier it should be to understand the root cause. I'm not a game developer so I have no idea how helpful the Vulkan validation errors are. Debugging is probably best done by tobspr Games in collaboration with Mesa developers, but it's very likely neither of them can spend time on that 😬

rustic cloak
#

It seems to work great with DW proton Latest, i'll use that for now.

cedar mesa
#

What rendering API did you choose?

#

I assume DX11 through DXVK works the best as it's the option Valve puts most money into and has the most control over. DX12 is unstable even for some people on Windows and Vulkan seems to run with varying success.

rustic cloak
#

Nope, pure experimental vulkan.

cedar mesa
#

Alright, what's your hardware+software stack then? Is Steam Overlay or Game Recording enabled?

rustic cloak
#

No (Steam overlay seems to be enabled), i am using dawn winery proton, # System Details Report

Report details

  • Date generated: 2026-04-26 18:06:05

Hardware Information:

  • Hardware Model: HP Victus by HP 15L Gaming Desktop TG02-0xxx
  • Memory: 32.0 GiB
  • Processor: AMD Ryzen™ 7 5700G with Radeon™ Graphics × 16
  • Graphics: AMD Radeon™ RX 6600 XT
  • Graphics 1: AMD Radeon™ Graphics
  • Disk Capacity: 2.0 TB

Software Information:

  • Firmware Version: F.25
  • OS Name: Fedora Linux 40 (Workstation Edition)
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 46
  • Windowing System: Wayland
  • Kernel Version: Linux 6.14.5-100.fc40.x86_64
    .
cedar mesa
#

Thanks. Vulkan performance depends heavily on the desktop environment, I completely forgot about that - it might be GNOME that's making the difference here. Vulkan is generally more finicky on my PC with sway 😅

rustic cloak
#

Oh, yeah, i haven't used sway yet, i probabluy should try it out.

cedar mesa
#

You don't need to test all environments, as that's a huge time sink

#

I'm just trying to find potential variables that are at play. If I can allocate enough effort, I'll make a website where you can report your experience and collect the results to get the big picture (pun not intended)

#

I've been looking through player logs and so far I've only seen AMD GPUs (both dedicated and integrated) but funnily enough also one Intel iGPU. Might be a coincidence, or it's just that not many people play on integrated graphics 😄

rustic cloak
#

I used to before i got a dgpu, mostly a UHD 630, frankly, i kinda wanna pull out my intel N97 and see if it can run shapez 2.

cedar mesa
#

Okay, I re-tested with same hardware as I did on sway (RX 6600) on Hyprland instead (default config). The game launched on second attempt and seems to run fine as long as you don't try to make it floating. I can switch workspaces without the game crashing.

#

Logfile shows similar validation errors right before the crash:

GameSessionOrchestrator:TrySaveCurrent took 0.002s.
Validation Error: [ VUID-vkAcquireNextImageKHR-surface-07783 ] | MessageID = 0xad0e15f6
vkAcquireNextImageKHR(): Application has already previously acquired 1 image from swapchain. Only 1 is available to be acquired using a timeout of UINT64_MAX (given the swapchain has 3, and VkSurfaceCapabilitiesKHR::minImageCount is 3).
The Vulkan spec states: If forward progress cannot be guaranteed for the surface used to create the swapchain member of pAcquireInfo, timeout must not be UINT64_MAX (https://docs.vulkan.org/spec/latest/chapters/VK_KHR_surface/wsi.html#VUID-vkAcquireNextImageKHR-surface-07783)
Objects: 1
    [0] VkSwapchainKHR 0x5050000000505

Validation Error: [ VUID-vkCmdEndRenderPass-renderpass ] | MessageID = 0x46db6f2f
vkCmdEndRenderPass(): This call must be issued inside an active render pass.
The Vulkan spec states: This command must only be called inside of a render pass instance (https://docs.vulkan.org/spec/latest/chapters/renderpass.html#VUID-vkCmdEndRenderPass-renderpass)
Objects: 1
    [0] VkCommandBuffer 0x7efb70358c30
timber onyx
#

guys, i have arch on intel+nvidia, if you need help with testing i can help

cedar mesa
#

As far as I know there are no issues with NVIDIA GPUs. Although you may still try to run the game with Vulkan validation layers:

VK_LOADER_LAYERS_ENABLE="*validation" %command%
```in fullscreen mode, then switch to floating window mode (or change it in settings, I guess that works too) and quit the game (since it shouldn't crash). Then check if you see similar validation errors in `Player.log`. Steam Runtime ships the validation layers I believe; if not, get them from the repositories (`vulkan-validation-layers` on Arch).
#

Meanwhile I have installed gdb, then ran the game outside of Steam with the following command:

VK_LOADER_LAYERS_ENABLE="*validation" ./shapez\ 2.x86_64 --disable-store-sdk --ignore-mods --no-dynamic-content
```and collected a logfile. What I did: executed the command, pressed Escape to skip intro, waited for main menu to load, used the "Continue" button, waited for the game to autosave, entered the pause menu, navigated to Settings -> Audio and pressed the "View" button on shapez 1 OST entry. That opened the web browser and automatically switched Shapez 2 window into floating mode (at least that's what happened for me on Hyprland). Then it crashed :(
📎 Player.log
neat harborBOT
# cedar mesa Meanwhile I have installed gdb, then ran the game outside of Steam with the foll...
📋 Log File Analysis

Log Analysis (Player.log):

Errors Found in Player.log

  1. Curl Error 35: TLS certificate verification failed repeatedly; UnityTls error code 7 indicates the certificate could not be verified (omitted or unsupported).

  2. Validation Error (VUID-vkCmdDrawIndexed-None-06479): Vulkan draw call validation error on vkCmdDrawIndexed, MessageID 0x534c50ad, occurring multiple times.

  3. Validation Error (VUID-vkAcquireNextImageKHR-surface-07783): Vulkan swapchain image acquisition validation error on vkAcquireNextImageKHR, MessageID 0xad0e15f6.

  4. Validation Error (VUID-vkCmdEndRenderPass-renderpass): Vulkan render pass ending validation error on vkCmdEndRenderPass, MessageID 0x46db6f2f.

  5. Fatal Mono Runtime Error: A fatal error occurred in the Mono runtime or a native library, with native fault reporting also failing — some diagnostic information is unavailable.

  6. OID Decode Error: net/cert/ev_root_ca_metadata.cc at line 161 failed to decode an OID value of 0.

#
1. [SPZ2-6003] — 🔥 92% similar

Linux: Crash when losing focus if in full screen or borderless mode
To Do • Priority: Highest • Fix: Probably Never • Game: 6.5.5

On Linux (KDE Plasma and Ubuntu), shapez 2 crashes instantly when the game loses focus while in fullscreen or borderless screen mode. This is triggered by Alt-Tab, the Windows key, or clicking outside the game window. The crash occurs immediately upon focus change, stopping the game entirely. The expected behavior is that shapez 2 should continue running regardless of screen mode when focus is lost. The issue was previously observed on Bazzite but has since resolved there for unknown reasons.
💬 Threads: [0.1.1] Linux - Game crash on FN key pre

#
2. [SPZ2-3456] — ✨ 88% similar

Linux Game crashes when adjusting volume
Done • Priority: High • Fix: Future • Game: 0.0.8 • Resolution: Won't Fix

On Linux, shapez 2 crashes when the player adjusts system volume using volume keybindings. The crash occurs immediately after pressing volume up or down keys. On the first launch after updating, the game crashed immediately, but subsequent launches work until volume adjustment is attempted. The issue prevents normal gameplay when any volume control input is made while the game is running.

#
3. [SPZ2-6232] — 👀 55% similar

Shapez 2 can crash when switching graphics settings while using Linux.
To Do • Priority: Critical • Fix: None • Game: 0.1.1

shapez 2 can crash or become unstable on Linux when changing and applying graphics settings such as resolution and window mode. This occurs when users navigate to Settings > Graphics and apply changes. Additionally, some users experience crashes at startup, potentially due to the application attempting to apply outdated graphics settings from a previous version before the settings refactor in rc1. The expected behavior is that the game remains functional and stable after applying graphics cha...
💬 Threads: [1.0.2-rc1] Crash when hitting apply in

#
4. [SPZ2-3849] — 👀 45% similar

Minimize Game with Vulkan Crashes game
Done • Priority: High • Fix: None • Resolution: Won't Fix

When playing shapez 2 in windowed mode at 1680x1050 resolution using the Vulkan graphics backend, minimizing the game window causes an immediate crash. The player normally uses borderless mode but was testing the minimize functionality in windowed mode. The crash does not occur when using DirectX. This appears to be an engine-level issue with Vulkan's handling of window minimization in windowed display mode.
💬 Threads: [0.0.9-xmas] Minimize Game with Vulkan C

#
5. [SPZ2-3663] — 👀 35% similar

Crash on startup
Done • Priority: Medium • Fix: Version 0.0.9 • Game: 24.2.2 • Resolution: Won't Fix

shapez 2 crashes on startup with a SIGSEGV error when running natively on Linux, likely triggered by recent OS package updates (such as mesa, mutter, vulkan-loader, or xwayland). The game was previously working but newer package versions broke compatibility. Running under Proton appears to work as a workaround, though sound issues were also reported. The crash occurs in native code before the menu is displayed. This is not something the development team can fix on their end, so using Proton i...
💬 Threads: [1.0.3-rc3 Linux] Game launches for a fe

#
6. [SPZ2-4453] — 👀 28% similar

One time crash when pausing with 'P' and minimizing game
Done • Priority: Medium • Fix: None • Resolution: Cannot Reproduce

A player experienced a one-time crash to desktop when pausing shapez 2 using the keybinding 'P' and then minimizing the game window to search the Wiki in their browser. The crash occurred without warning and the player could not reproduce it afterward. Log analysis revealed a fatal Mono runtime error and a native fault reporting error, but insufficient data was available for full diagnosis. The development team attempted multiple reproduction attempts across different builds but could not rec...
💬 Threads: [0.0.9-RC7] Crash (SIGSEGV?)

Found 6 similar reports • Searched 3,520 reports • Use /check-duplicates to recheck
timber onyx
#

We need assassinate this bot

rustic cloak
#

No, just have it play a game of chess, Dr Faulken?

hushed charm
#

Since my issue was marked duplicate, might as well forward my workaround here.