Yes. If I remember correctly, it was the Proton VPN installation guide for Ubuntu (https://protonvpn.com/support/official-linux-vpn-ubuntu) telling people to install gnome-shell-extension-appindicator. That package in turn pulls in the entire Gnome shell…

It’s a thing where the Gnome desktop is installed as a dependency and shows up on the next boot: https://www.reddit.com/r/gotgnomed

Debian strongly recommends against adding repos from other distributions or other versions of Debian: https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian Doing that can easily break your system. They also recommend against adding repos for specific software packages (e.g. for LibreWolf), but this is generally less problematic.

Personally, on Debian, I try to get packages in this order:

1. From the official Debian packages
2. From Flatpak
3. Pre-built binaries (I put them in my home, not in /usr/bin)
4. Build from source (I also put those in my home)

Personally, I’m quite happy with Plasma Wayland on multiple machines and distros. However, Plasma has already been forked to create Sonic DE: https://github.com/Sonic-DE/sonic-win No idea if this will gain any traction once Plasma drops X11. For now, the activity seems to focus on the readme file…

Spreading false information about Gnome claiming it is insecure sounds like a valid concern for the Gnome team.

Could you point me to that, I couldn’t find anything related to Gnome security in the linked article.

A bit unfair IMO by the downvoters to not explain their downvotes?

There were disagreements between Gnome and System76 and they decided to go separate ways. The whole “contributing to upstream” situation is also kind-of muddy at best. Maybe that’s grounds to write a disappointed blog post 4 years ago, but saying that they are “not to be trusted” today goes too far IMHO.

Also, looking at how Gnome and System76 behave upstream (e.g. in Wayland) today, it seems to me that Gnome is the bigger problem…

I don’t know if there are any differences between the two packages. But, the CachyOS version is part of their official repositories and doesn’t depend on the AUR. I don’t know if that would have any implications regarding how often you need to rebuild the module.

Sure, I’d consider that the main option (and it had already been proposed by multiple people here). But, it also seems like that would come with quite a bit of additional hassle, as discussed below. I’ve personally had some quite annoying issues with incompatible DKMS modules… So, instead of using the unsupported AUR option, it might also be worth considering switching to a very similar distro that actually still supports this hardware configuration.

One option that you could also consider is switching to CachyOS. It seems that they’re handling support for these legacy GPUs in a much nicer way: https://discuss.cachyos.org/t/announcement-maintenance-notice-nvidia-driver-restructuring-580xx-590xx/20010

I have 3080 and I’ve seen significant performance issues too (e.g. in Cyberpunk 2077, KCD2). I think it depends a lot on the games you play. Apparently DX12 (via vkd3d) doesn’t perform well on Nvidia cards.

My next GPU will probably not be an Nvidia card.

Barrier - Keyboard and mouse sharing via network - I use this extensively and the break in compatibility is destructive for me.

Barrier has been unmaintained for a while now. The two active forks are deskflow (upstream) and input-leap. Deskflow has limited supported for Wayland. It seems that they’re working on resolving the remaining issues: https://github.com/deskflow/deskflow/discussions/7499

Upstream, the Fedora KDE Plasma edition is also doing well. Nice to see that within the first release after promotion to a full edition.

It’s either +44% (from $70) or -31% (from $101). Percentages are weird…

Yes, and it should probably be cheaper in Poland. But it’s really 17% more expensive in this case, not 44% (or 30% as the article calculates).

The Polish price includes 23% VAT, no?

15 years is too long, it doesn’t match the state of the industry or technological progress.

How is this too long? I would consider it a reasonable amount of time to receive security updates on a computer.

I have a notebook that I bought in 2012. It can run Ubuntu LTS 24.04, which is supported until 2034, without issue. There is no indication that the next release will stop supporting this hardware. I don’t see why Microsoft couldn’t provide this.

Interesting, I didn’t know that but it seems like Wayland is indeed CSD by default. However, all relevant compositors except for Mutter support xdg-decoration (https://wayland.app/protocols/xdg-decoration-unstable-v1). So in practice it’s still only a Gnome issue.

No, that’s Gnome, not Wayland. KDE still prefers SSD on Wayland.

I feel it has gotten much better in recent years. The first time I tried KDE 5 it looked weird to me. But now I acutally quite like KDE 6. Or maybe I’ve just learned to tolerate it…

What kind of issues did/do you encounter?

The VS Code/Codium essentially provide a separate development environment within the flatpak container. All the tools there, and the shell are separate from your actual system. There are some ways to work around this (https://github.com/flathub/com.vscodium.codium/blob/master/README.md). I gave up on the Flatpak and installed a native package. Containers are nice, but they have their limitations.

Sure, Bazzite has some nice features. But, I would argue that apart from the Nvidia images (there is no AMD image) those are all minor things. And for Nvidia cards, the Mint Driver Manager is pretty good. I don’t think any of those differences play a role here.

In general, I think it’s really unhelpful to present “switch to my favorite distro” as the first step in troubleshooting an issue.