Same issue, also game doesn't properly close when you exit. Need to click stop on steam.

Same issue, also game doesn't properly close when you exit. Need to click stop on steam.

tbf the exit issue happens in windows as well, doesn't mean much to us linux users but it's nice to know we're not alone with this issue 👍

Game does not launch any more since yesterday

The game does not launch.
Full system information gist.
Game log steam-1062090.log.

I can launch the game, but it throws an error after displaying the menu. It works perfectly on proton 5.13-6, breaks on 6.3-8. Let me know if I can help with any troubleshooting.
steam-1062090.log
system info

Edit: this may be related to futex2, as the issue started roughly at the time futex2 was released, but WINEFSYNC_FUTEX2=0 doesn't solve the issue.

@fusate I couldn't reproduce this. Based on this line: "21292.877:013c:0140:fixme:rawinput:rawinput_from_hardware_message Unhandled rawinput type 0x8." I'm wondering if you have some unusual peripheral attached (or a non-standard mouse)? Could you try unplugging any extra controllers, other input devices, etc and seeing if you still get the crash?

If that doesn't work, could you also try deleting the prefix? (by default located in ~/.steam/steam/steamapps/compatdata/1062090)

@alasky17 Thanks for the reply;
I just tried both those suggestions, the only peripherals I had plugged in while testing 6.3-8 were my monitor, keyboard, mouse and ethernet. I noticed this time the game only crashes when moving my mouse; I can press enter to get past the welcome dialog, but as soon as I touch the mouse it shows the unity crash reporter, sends the report and exits. My mouse is from the cooler master lite L combo. I tried to use a different mouse, the tiny generic one included in a raspberry pi bundle. This time, my PC stopped accepting mouse input once I launched timberborn, and I found these errors.

Jan 24 19:40:49 alex-desktop kernel: usb usb1-port10: couldn't allocate usb_device
Jan 24 19:40:49 alex-desktop kernel: xhci_hcd 0000:02:00.0: Max number of devices this xHCI host supports is 127.
Jan 24 19:40:49 alex-desktop kernel: xhci_hcd 0000:02:00.0: Error while assigning device slot ID
Jan 24 19:40:49 alex-desktop kernel: xhci_hcd 0000:02:00.0: HC died; cleaning up
Jan 24 19:40:49 alex-desktop kernel: xhci_hcd 0000:02:00.0: xHCI host controller not responding, assume dead
Jan 24 19:40:40 alex-desktop kernel: usb usb1-port1: couldn't allocate usb_device
Jan 24 19:40:40 alex-desktop kernel: xhci_hcd 0000:02:00.0: Max number of devices this xHCI host supports is 127.
Jan 24 19:40:40 alex-desktop kernel: xhci_hcd 0000:02:00.0: Error while assigning device slot ID
Jan 24 19:40:15 alex-desktop kernel: usb 1-1: device not accepting address 10, error -62
Jan 24 19:39:55 alex-desktop kernel: usb 1-1: device descriptor read/64, error -110
Jan 24 19:39:39 alex-desktop kernel: usb 1-1: device descriptor read/64, error -110
Jan 24 19:39:23 alex-desktop kernel: usb 1-1: device descriptor read/all, error -110

This is starting to look like it might be a hardware issue, but timberborn on proton 6.3-8 is the only piece of software which has these issues. I tried to reproduce the mouse issue that that resulted in the kernel errors but was unable to cause it again.
Thanks for the help so far, I'll see if i can reproduce the kernel issues in software other than timberborn and send a message here if I can.

My issue seems to be resolved with proton 7, I was unable to recreate the USB error. Thank you Valve for the hard work you've put into Linux!

Timberborn has been working flawlessly recently. I think this can be closed.

It appears that even a minimal Unity 6000.2.6 project has the same problem when run on Proton (including Linux and Steam Deck):

• onPressed/isHeld/onRelease work OK when the cursor stays in one place for the duration of the click.
• But as soon as the cursor moves, for some reason it sends an onRelease event, even if the button is still held.

The same game build works fine on Windows.

So this likely affects all games that upgraded to the latest Unity version.

@bartlomiej-dawidow Thank you for reporting this - we are looking into it now :)

@bartlomiej-dawidow click and drag should be working again with proton bleeding edge https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge

@simifor We tested it on our end too and are happy to confirm that bleeding edge seems to fix the problem.

Would you be able to share how and when these changes will be rolled out to players?

If we roll back Timberborn main branch to Unity 6000.1.13 (from before the click and drag problems) but Timberborn experimental will be built using the newer Unity versions, how will this be handled by Proton / the Steam client?

@simifor

Update after testing with Proton Bleeding Edge (Oct 15, 2025):

🟢 Dragging is fixed – this is great!

🔴 BUT: Mouse wheel input no longer works in any context, including:

Camera zoom (normal mouse wheel)

Vertical layer switching (Alt + mouse wheel)

Scrolling through the bottom UI/building bar (Ctrl/Shift + mouse wheel)

Even menu scrolling (e.g. game settings)

All of these were working fine in the previous Proton versions (where dragging was broken).

This looks like a regression introduced by the recent fix for Unity's onRelease input behavior.

Let me know if I can provide a new log or help test anything further. Thanks again for the quick turnaround on the dragging issue!

Thanks! Yes, there was a bug in those changes unfortunately, it should be fixed in the just updated Proton Bleeding Edge (255711+).

Those changes are supposed to get to Proton Experimental proper after a bit of testing, releases of that happen once per 1-2 weeks usually. It may take time until these changes get to stable Proton version but the game may be pinned to Proton Experimental until then.

✅ Confirmed – everything works perfectly now!

I've just tested the Timberborn main branch from October 13, 2025 using Proton Bleeding Edge build 255711+, and I can confirm:

✔️ Click and drag is working properly again

✔️ Mouse wheel input (zooming, vertical layers, scrolling UI/building bar, in-game menus) is fully functional

🎉 This completely resolves the issue from the Linux player's perspective!

A huge thank you to the Proton team, especially @gofman, @simifor and everyone involved, for the fast diagnosis, the quick patch cycle, and the clear communication throughout.

It's not every day that a complex cross-platform bug gets addressed this quickly and transparently. You folks rock. 💪🐧

There a lot of players reporting problems but it appears that the experimental fixes work. Is there a chance the fixes could be published to all players on the main branch?