They also fuck over their own OS. I don’t think they deliberately broke dual boot installs, they simply don’t put enough effort in QA. (See their recent problems with BitLocker after an update. Or that one update that fails because some internal partition is too small. And so on.)

I ran Arch on a convertible laptop around 2006-2010. Most notes I did using OpenOffice Writer, with hotkeys to quickly add formulas. Drawings were done with the pen. Homework (where speed didn’t matter as much but where I wanted high quality) were done in ConTeXt.

Programming was done in FreePascal using Lazarus IDE or Java using Netbeans IDE, depending on the course and my personal preference.

I think I had no complaints from anyone. Quite the contrary, one professor even gifted me a book as a thanks for the high quality typesetting in my homeworks, since most students didn’t give a shit and had no fucking clue how to really use their beloved MS Word.

There is no “maybe” here. With systemctl suspend you tell systemd to suspend the whole machine. Most of the hardware will be powered down.

Maybe you should generally separate those concerns? Depends entirely on your usecase, but maybe you want your screenlock to do only that… lock the screen. Then you do not want suspend/sleep in there at all.

Offlive account during install works only when you are not connected to the internet from that PC. Maybe also only with Win Pro, not Home.

The crap you have to disable are all dark patterns and I hope the EU rips them a few more holes.

“Just update”… I think I went into enough details about what pissed me off in my initial comment.

Almost every Linux distro would have been: boot the installer, select disk, select meta packages, username, password, done. 10 mins later you have an up to date system with no shady online crap.

Just this weekend I had the pleasure of installing Win 10 on a blank disk. The install went ok, but then it bothered me logging into the MS Account. After cursing for a while and since it wasn’t my PC, I gave in. I know I can fight it, but it’s not worth it here. Then it continued trying to get me to consent to all kinds of shit. NO, I DON’T WANT FUCKING OFFICE AND I DON’T WANT MY FILES IN ONEDRIVE you assholes!

Then it forces me to choose a PIN for “secure login”. DUDE! That motherfucking PC is used for a bit of office work and gaming. Just let these poor people boot up the machine and use it! 0000? Too simple. 1234 too. Fuck you, MS. Ok, random PIN and a sticky note it is, asshats.

Anyway, after getting it to fuck off, I continue to the desktop. Oh wow, 10 updates and a ton of missing drivers? It’s a fresh install! What the fuck did it install?! Of course the installation of all these updates takes an hour and countless restarts… AFTER A FRESH INSTALL! Not even my overblown super slow Ubuntu server takes that long for updates; and that runs on a HDD not a SSD like that PC I set up.

But wait. One update failed. Why? Ah, the rescue partition is too small… THE ONE THAT DUMB SON-OF-BITCH CREATED ON ITS OWN AS PART OF THE INSTALL! How to fix? Ah, execute a bunch of commandline foo with diskpart and other tools. Wait, isn’t that exactly the kind of shit that Windows fans laugh about when looking down on us Linux nerds?!

So … ugh … just one simple anecdote of why Windows can fuck off.

I still rank OSX higher, simply because it’s at least consistent. Windows is a fucking mess.

If you are so keen on correctness, please don’t say “LLMs are lying”. Lying is a conscious action of deceiving. LLMs are not capable of that. That’s exactly the problem: they don’t think, they just assemble with probability. If they could lie, they could also produce real answers.

Buy CrossOver for Linux. Positive side effect: you support Wine development.

Do you think being maintainer makes you some kind of all knowing being? That’s not how that works. You write code and review code of others.

If there are multiple maintainers, you may obviously not even notice what another maintainer is doing; then you wouldn’t need multiple maintainers with write access if you could handle it all by yourself.

… in which case you would have seen that they delete a path referenced by an env var being set earlier.

How likely do you think it would have been to notice, that this env var will turn up empty in your specific case?

Of course. Great, another D in programming.

Thanks for saying that. I have no idea why that gets overlooked so often.

As much as I like to shit on Windows, WSL is ingenious and many dev tools integrate it nicely.

I really don’t get why Apple doesn’t offer anything in that direction, where devs are a big target audience for them and they already ride the POSIX train.

If you got sick of Windows, what do you expect from running it in a VM? A slow and bloated OS in a VM is still slow and bloated. Probably even slower, because it now runs with more constraints.

There is a commercial phone linux: SailfishOS. IMO also the most polished one.

If those fuckers at Microsoft hadn’t intervened with Nokia, we might have these things on much more devices. Meego was so promising 😔

It can’t hurt. I’ll grab another display and another cable and try a few combinations. Thanks!

Thanks for the idea!

dmesg shows the same errors as in the referenced bug ticket. So I don’t think missing firmware is the issue. I would not be surprised however, if the problem in general is a combination of amdgpu and firmware behavior. (IMO the hardware should not crash as hard as it does, so the firmware seems to be a bit wonky too)

Thanks for the suggestion!

While it’s a possibility, I think it’s unlikely, since the machine works fine with Windows. I also compiled the tkg 6.7.2 kernel which includes the revert-patch for the offending change and so far the machine booted three times without issues, so it seems to fit.

At least with my 1060 compositing wasn’t an issue. But true, I rarely used Wayland. Do you have specific issues when compositing is enabled or do you just prefer the simpler rendering?

Arch. On all my machines.

I did live like this with all my intel/nvidia systems just fine, though. If AMD tends to have bugs like this, they still seem to suffer from the same shitty software development attitude as they did back in the fglrx days… with the added advantage that people from the community can now firefight some of the problems. For a product I paid a few hundred euros for I expect some quality assurance for its driver development - that seems to work with nvidia.