Thank you, I’ll try. Tho I’d still be interested to by the answer to my original question, since I might want to change other keybinds later…

Did you think they were called that because they were hedging the hog? No, they’re hogging the hedge.

And they would’ve gotten away with it if it wasn’t for you meddling kid!

Saving this post in case I ever get a date.

I’ve had this problem too but the latest upgrade just fixed it. And yeah, I think it was Google’s doing and it’s not the first time, it’s a constant arm’s race between them and Newpipe programmers. And Ublock programmers. And Invidious and Piped programmers etc…

Can I go an hour without eating pickles? If I fail, I’m deleting my comment. [EDIT: It was a close one, but I made it ! This comment is here to stay ! Celebratory pickle time.]

How about systemd-windows?

I would not recommend Arch for beginners. I like it, but it’s best for someone a bit familiar with Linux already. Yeah, the install is pretty simple now that Archinstall is a thing, but it’s not the method recommended in the Arch Wiki and if there’s something wrong with your install and you complain on the Arch Forum they might not be super helpful.

More generally, the mood on the Arch forum and Arch communities at large isn’t super beginner friendly, and thay’s understandable: In a distro meant to be user friendly and aimed at general user, if the user does what seems natural to them and the system break, the community will feel a responsibility towards them, because the system wasn’t stable and user-friendly enough. In a distro primarily aimed at power users and devs, if the user does what seems natural to them and the system breaks, then the user is a fool and should’ve read the wiki.

Because it is a very fast rolling release, some updates can break stuff. It doesn’t happen often, but it can happen at a bad time and be a big problem for someone who doesn’t know how to deal with it.

Debian is more stable, and easier if you go with a D.E, but you still have to make several choices during the install, which might be a bit complicated for a beginner who doesn’t know what any of these options mean… Tho of course, it’s possible to go with all the defaults and it’ll be alright.

But my prime recommendation would be Linux Mint.

I’d switched from i3 to sway, but the click offset in Krita made me switch back.

So there’s the time I converted my partition table from MBR to GPT and it corrupted everything on it so I had to reinstall. Took this opportunity to switch from Mint to Arch, something I’d been thinking of doing for a while.

Once on Arch, I had much more opportunities to make epic mistakes: For example not putting enough room on my root partition (home was on a separate one), so after a while I had to reinstall.

I still haven’t found the solution, have you had any luck with yours?

I tried switching every UEFI setting that seemed to have something to do with booting or gpus, reinstalled gpu bios, upgrading mobo bios, getting a monitor I could plug without a switch… All to no avail.

Well, I think before upgrading the BIOS, one thing had a slightly different result: Setting the boot mode to UEFI and disabling CSM made it display “no gop (graphic output protocol)” after a few minutes, and it offered to either take me to the uefi settings or loading defaults (which implied going back to CSM), after which it boot this time go back to doing the same thing.

I don’t think I’ve had this error since the mobo bios upgrade, but still no display unless I reboot, unless the computer had been turned in until recently. I’m kinda out of ideas…

Thank you ! It didn’t seem to work on it’s own, but I also noticed I wasn’t booting in EFI mode, so maybe if I just change my booting partition and combine it with your advice it’ll work…

Using amd GX 6600… Mostly going fine, tho I haven’t tried any big heavy games. One thing tho… Everytime I turn on my computer, no display. I reboot it and then ot works fine, but ot never does the first time. One path I’ll investigate is the monitor: my monitors are both older and use DVI or VGA ports, so I have to use converters. I might try and get my hand on a more recent monitor to see if I still get the same problem. But if I do, I’m not even sure where to ask. I don’t even think it’s a linux problem, because I tried removing my drive with linux living one with windows and the problem remains. I also was using mint when the problem started and switched to Arch (btw) since and it doesn’t change a thing.

Soon we’ll be debating whether we call it systemd/linux or gnu/systemd.