“Is this ‘Critical Error’ the reason for the crash, or just another ill-labeled exception?”
I love WINE and it’s forks, but man, how can any program produce so many errors during optimal operation? (A rhetorical question, as I believe we all know the tragicomedic reason being Microsoft)
The Deck is a pretty nefty device. I used it for half a year as a daily driver, which included everything from gaming to light embedded development. I’ve also used it as a ground control station when flying my legacy drones, or as a relay for my main rig when tinkering on unhandy equipment (such as accessing my cars OBDII from the warm living room).
I’ve also tinkered with secured storage on the Deck, but found that LUKS needs the Deck to be unlocked (note: All of the above can be done without disabling the read-only system). I found a somewhat functional workaround using rwfus, which makes an overlay on top of the read-only system, on which I then can install packages such as veracrypt. I also tried NIX to this end, but found it to be way too much work to learn to use proper for my usecase.
And while not really anything mind-bending: I’ll be spending the next few days in our summerhouse with my sister to celebrate ‘Fastelavn’, where I expect to bring my Deck and a Steam Controller for some evening Kingdom 80’s co-op.