Also hate “natural” scroll on PC.

Oh I went 11 > 12 > 13. But haven’t really checked all the configs from 12 to 13, there are many new ones too.

Oh, partial upgrade is the worst. Technically it’s still supported until next year as oldoldstable so it should be fine to directly upgrade if you ask me but I understand the changes affect many things and upgrade process actually check things from the previous version, so if one upgrade directly it might go bad. That’s probably why Arch Linux can get borked if you haven’t updated for a long time.

I agree. It’s mostly fine but these upgrade processes could be much better.

I heard some people use openSUSE MicroOS as their servers but my servers were always Debian and I’m quite happy about it. Though immutable server sounds nice. But I wouldn’t consider anything until my server is completely broken, so there is that. :)

I feel like 13 introduced more changes than 12. By the way, I finally took the leap and upgraded to 13. Kinda YOLO’d though and it needs some fixing in configs but currently everything I expect works, so this will be a very slow fixing process I reckon. :)

Good luck with the upgrade!

Wow, these are some huge changes. Looking forward to try them.

I mean, give the shutdown command like this, not after already choosing it via menu. This way you may catch what’s wrong. Also, you can check the logs when you boot next time via journalctl -b -1 but to make it easier maybe this one should be more helpful journalctl -b -1 | grep -i shutdown

It’s a headless server, so I’m thinking “how bad could it be” but I would be more cautious.

Well, if there are issues like even in normal upgrade, it’s better not to jump on a thing like this.

Still, it’s good to know that this is technically possible, though it’s not for a lazy person who just wants to update his server. Gotta check Debian changelog.

Switch to a TTY and do “sudo poweroff”. See what happens. I feel like this is more likely a systemd issue.

I know what I’m doing but looking at every comment here, it’s not a wise thing to do it seems. So casual or not 11 > 12 > 13 is the proper and most likely still the easiest way. It’s a good thing that I asked before doing some potentially mad thing.

Well, certainly not gonna be a tester. If it isn’t tested, there is no need to take things further. Thanks for the guides by the way.

Yeah, that makes sense. Major changes in software are no joke. If it wasn’t my actual server I could’ve tried it though, could be a fun thing to pass time.

Thanks for the suggestion, seems actually nice with all the ability to install a custom ROM. Sadly, it’s not practical for me to get it from abroad because of our government’s horrendous regulations about buying anything from outside of the country unless you are a trader. Even if I manage to buy it without any problems, there is also IMEI unlock fee which is almost the same price with this phone. My best bet would be, get this phone via a friend who comes from abroad and change the IMEI to my old phone. So, not soon but maybe some day.

How is this related to Gnome though? Adwaita for Steam is a third-party Steam client theme that only modifies CSS. This might be a coincidence but I don’t know at this point.

Maybe not a dumb phone but I would love to use a phone with an e-ink screen. I know there are some projects about this or some Chinese phones but I haven’t met an e-ink phone that I can install a custom ROM yet.

It’s possible that Adwaita for Steam causing VAC issues now. I suddenly started getting VAC warnings on CS2 and it didn’t go until disabling Adwaita for Steam.

Edit: False alarm! I tried again by using the theme and it was fine this time. Apparently it was a weird coincidence.

Hahaha, at this point they can coin the term.

We’ll see Shenmue 9 before Star Citizen’s release.