alufers

I want to add to this: In my country (Poland, but probably many others) you are sometimes almost forced to be tracked by FAANG companies. For example our mObywatel app, which can be uses as driver’s license replacement requires you to download it via Google Play and have Google Services installed. Of course it uses firebase to send notifications.

You can still use XWayland though, it’s not going anywhere. They are only removing the ability to run a X11-only session.

I am one of those people. I have a Macbook Air laptop, which I mainly use to remote into my Linux desktop while on the go (mainly with vscode by the way). I found this to be sweet spot of usability, while at home the laptop is in a bag, charging and waiting for the next outing. This way I can enjoy the niceties of having a big desktop PC (performance, a LOT of USB ports, a huge monitor).

The reason I have the Apple laptop is mainly because of the lightness and battery life. No other machine comes close to it. For now I sort of treat it as a dumb terminal, so MacOS is not a big hassle for me (except for the insanely dumb window management). I will try to ditch MacOS as soon as Asahi Linux releases webcam and microphone support, because it is the only thing that is stopping me from using it.

And yeah, the ugly truth is that once I damage the screen or the SSD fails, the whole thing becomes e-waste (and money-waste).

I don’t know what were your particular issues, but I used to have problems with it not being able to home it’s motors and even failing to unload and load a cleanly cut filament. All it said is “MMU REQUIRES USER ATTENTION”. It was very frustrating for me, prints not being able to start etc. And of course the idiotic error message.

But about three weeks ago they released a new firmware version for both the MK3S and the MMU2. And I was surprised to see that the printer started displaying normal error messages and even a short link to the exact documentation page which explains the error condition. And basically mine was this: http://prusa.io/04306, which basically boils down to “Power issue detected”. I took a look into the mainboard box and indeed it was a loose connection on the positive terminal. I’m glad the thing didn’t melt or catch fire (the printer was a kit, which I bought second-hand, assembled by some random guy).

Anyway, you might want to put back your MMU, update it, maybe some of the issues will be better explained to you.