So instead of accepting that the driver should be GPL and part of the kernel, you turn things around and pretend the development of the kernel is the way that it is because of a conspiracy against Nvidia?

The bit regarding Wayland doesn’t make sense, no idea what you’re getting at. Though maybe you don’t follow Linux developments?

You’re putting words into their mouth. Plus making crazy comparisons.

I highly recommend list-inhibitors. Not sure if this is the one I mean, the command line seems to match to the one I use: https://pypi.org/project/list-session-inhibitors/

This command gives a way nicer output.

For me Firefox often prevents the system from going to idle. If some page has a video it often seems to inhibit going to idle. Firefox strangely does that even if the video is paused.

For me and Firefox I’m often intend to do something about it. And then I don’t for various reasons 😂

The EU could do that, if it wasn’t for Poland assisting Hungary. I’m guessing that Slovakia nowadays also helps Hungary by preventing the EU from stopping this nonsense.

Toss em out.

Not possible.

I don’t really know how to do that

• Install rust
• Create a directory somewhere
• Change to that directory
• Run: cargo init
• Open a text editor and do stuff in there
• Save the file(s)
• Run cargo build
• Run the executable

Hope it helps!

Everything just feels slow, clunky and some basic things are quite complecated to archive

It’s been that way for much longer than a few years unfortunately. I don’t understand how people can tolerate it. Some projects switched to it because it seemed more beginner friendly than IRC, but to me it’s not focussed on making things easy.

I haven’t tested dnf5 yet though so can’t comment on it.

It is significantly faster than dnf. I’m looking forward to it becoming the default.

I wonder if this is related to https://www.sovereigntechfund.de/. This as it shouldn’t be about saving cost. It should be about being sovereign.

Sometimes the different USB ports are backed by different manufacturers. Pretty much all of my USB outputs are a bit unreliable. Apparently a hardware issue. There are two that use a different chipset. Those are the only reliable ones.

So maybe check the various USB ports to see if there’s a difference.

In this case the upstream maintainer heavily obfuscated the code to be able to compromise ssh. Package maintainers aren’t responsible for vetting for that.

A certain Dutch political party repeated Russian talking points for various years. The party leader recently threatened another politician when they were asked if they received Russian money. Instead of going to war it’s way cheaper to just buy a few politicians.

Powertop does way more for power usage than just the CPU.

Not relying on the network during a build is pretty common while making an rpm package. It’s a pretty reasonable requirement to have. I’d suggest looking into what e.g. the equivalent Fedora package does.

There’s a huge difference in something used by 100s or 1000s of people. Once something is used significantly more it’ll result in bugs that nobody ever noticed before.

Further, the best way to keep things stable is regular timed releases. You seem to be advocating for releasing irregularly. Projects used to do that in the past. Regular releases result in way more stable software.

Maybe check journalctl for warning and/or error messages? Might be a bug that needs reporting/fixing.

That’s specific to X11. It also wasn’t always enabled for security reasons (breaking out of a locked screen). Now with Wayland there’s no standard.

Swiping to upvote/downvote comments uses the wrong/old colours. Edit: was already mentioned

Flatpaks aren’t meant for command line utilities.

With weed, what the Dutch model tries to achieve is to not punish people for smoking weed, but also not turn it into a for-profit industry that would create an incentive to get more people addicted.

It’s more that there’s a lot of conservative parties that do not agree on the drug policy. E.g. enough Christian parties who would rather be more restrictive.

The clock likely is off by an hour because of local time vs UTC difference. Where the BIOS is set to UTC.