The Linux Thread - The Autist's OS of Choice

[DavidS877]

"We love $THING, here's why it isn't there."

I really fucking hate this Soft-Marxist pattern of dialog. Just be honest and say you think half-assed sand boxing is better than package management out the gate.

I suspect it's also a side of "And we don't want to bother with making packages, so just go find it somewhere else"

 

[Max Weber]

I suspect it's also a side of "And we don't want to bother with making packages, so just go find it somewhere else"

Which of course begs the question of why do you think it's necessary to have a distribution.

 

[jeff7989]

More control over users and data from telemetry?

 

[Ahriman]

Now this is a comfy distro, LMDE.

If I were to move out of Fedora, this is what I'd choose.

 

[DavidS877]

More control over users and data from telemetry?

I expect that "Supporting users on different distributions is too hard. If you want to report a bug you have to report it using KDE Linux." is also coming soon.

 

[Angie Wormwood]

What is it with Bri*ish and being control freaks. No Nigel, I will not use your immutable slop distro. If I wanted iOS experience then I'd but an Apple device.

There is so much retardation in his bulletpoints.

Conflicts and incompatibilities with add-on repos

This is easily fixed by two different sides:

1. Only installing repos that you need and not enabling every slop repo out there.
2. Have third party repo maintainers only package the things they *need*. Don't include every dependency if the OS provider has it. Or even if it's in a popular third-party repo like EPEL.

Heisenbugs from orphaned packages still present on the system

This has been a non-issue for a while now. Dandified and Aptitude both track unused packages and ones that are no longer needed as dependencies and lets you remove them with the `autoremove` option. ezpz.

The ability to uninstall important functionality without realizing it, breaking the system

A package manager doesn't prevent this, either. You can still go into /boot and whack vmlinuz/initramfs and render your system unbootable. You can modify files outside of a package manager. And really, if you do a `dnf erase <package>` and dnf resolves 300 subsequent depencies to be erased, that should give you pause to evaluate. Don't run everything with -y and you won't keep stepping on landmines, you fucknugget.

Updates that break bootability due to some untested condition present only on your system

In almost two decades of doing this, and across tens of thousands of systems, you know how many times I've seen this?

Once.

And I wasn't even there for it, so no telling if that was actually the problem or not. The cow-orker reporting this was a fuckwit, so he could've done something wrong and conflated patching with something else or ignoring some other warning.

 

[prollyanotherlurker]

Personally, I hate AppImages, but what do I know, I'm a Gentoo user who builds everything from scratch anyhow. What I hate about AppImages is that some retards think it's now acceptable to just release an AppImage instead of giving an overview of a build process. No, you retarded Windowsfag, building things from scratch is why I run Linux. Having to reverse-engineer the AppImage build to get a proper AM2R build pissed me right the hell off.

I wish they would at least go back to making portable archives at least. I feel like that's what appimages have turned into anyway.

Just a portable archive that mounts on the runtime directory as a fuse filesystem. You still need dependencies with appimages anyway. I feel like archives mesh better with the system than flatpaks. And snaps are just a whole different thing.

 

[Miller]

Does anybody know why Gwenview does this when I want to see a picture? The content appears dark for a few seconds and then I get the actual picture.
(I'm on Arch with KDE of course)

At first I thought it was related to HDR but I don't have it enabled.

 

[James Deans Ghost]

Does anybody know why Gwenview does this when I want to see a picture? The content appears dark for a few seconds and then I get the actual picture.
(I'm on Arch with KDE of course)

F10 > Configure > Configure gwenview > Image View > Animations > None

 

[Miller]

F10 > Configure > Configure gwenview > Image View > Animations > None

Thanks. It's better now.
Is that a new thing? I don't remember enabling this.

 

[Day of the Cope]

I swear to god, I don't know what Wayland's fucking problem that I update my system and suddenly everything that uses Xwayland crashes when I unlock my screens.

 

[One Angry Computer]

I swear to god, I don't know what Wayland's fucking problem that I update my system and suddenly everything that uses Xwayland crashes when I unlock my screens.

Sounds like Wayland is resetting config files that Xwayland uses with every new update, which is so moronically diabolical that I bet Wayland has former M$ employees as devs.

 

[Slav Power]

I don't know what Wayland's fucking problem

Wayland is being developed by the same people that develop GNOME. You're welcome.

 

[One Angry Computer]

Wayland is being developed by the same people that develop GNOME. You're welcome.

I bet Wayland has former M$ employees as devs.

I don't know if this validates my theory, or if the solution is worse.

 

[Day of the Cope]

Sounds like Wayland is resetting config files that Xwayland uses with every new update, which is so moronically diabolical that I bet Wayland has former M$ employees as devs.

Well, currently moving over to XLibre at this very moment. Not the first time I've had this shit of "updating and now everything that (seems) to use XWayland crashes when my monitors come out of power saving".

Of course the AUR picks today to start shidding and farding itself.

Okay, turns out that I'm not the only person having issues with KDE Plasma terminating programs! I'm not alone in my suffering!

 

[prollyanotherlurker]

Sounds like Wayland is resetting config files that Xwayland uses with every new update, which is so moronically diabolical that I bet Wayland has former M$ employees as devs.

That would probably be a package manager problem.

 

[Day of the Cope]

Gonna run a second DE until KDE pushes out 6.5.1 since I never seem to get lucky with minor version updates.

 

[Betonhaus]

Gonna run a second DE until KDE pushes out 6.5.1 since I never seem to get lucky with minor version updates.

Cinnamon?

Though you probably want one that uses qt, so there's LXQt or TDE. Not sure how many others there are, KDE didn't spawn as many forks as gnome did.

 

[Day of the Cope]

Cinnamon?

Yeah, ended up landing on that as my backup DE. Don't see myself using it once KDE pushes out a patch because some of the choices are beyond fucking baffling.

 

[Ruined by the Rain]

I just moved to Linux and it's insane how many programs support it now. Back then I remember it being a pain to install shit lol