I’m not aware of another one. Some other distros like Ubuntu and OpenSUSE ship AppArmor instead, which does similar things but isn’t considered quite as secure.

I know plenty of other popular distros don’t ship any Mandatory Access Control system at all which seems like a very bad security practice to me. Same thing with Firewalls.

I use fish which is quite nice OOTB, although if you want a posix compliant shell, zsh with some plugins is also great.

I don’t think that would work since both GPUs are AMD and use the same driver

Use a shell with decent auto-completion. I have not been irritated by this in years.

One thing you could do is plugging your monitor straight into the iGPU outputs and using DRI_PRIME only for applications that need the powerful dGPU.

Unless you want to run either everything or nothing on a specific GPU, I don’t think there’s a more convenient way than setting DRI_PRIME per application.

You listed AMDGPU-Pro as a kernel driver. Correct me if I’m wrong but I’m quite sure it is a proprietary userspace OpenGL/Vulkan driver that uses the open source AMDGPU kernel driver.

Try using XWayland video bridge. It should allow any XWayland apps to use screen sharing. Unfortunately most distros either don’t ship it yet or ship broken versions but you can download nightly Flatpaks from Gitlab CI

That was my experience a month or two ago but last week I had no problem installing Neon unstable on a test system and it was amazingly stable though far from perfect.

That said, the developers using Plasma 6 obviously compile it themselves, yes.

In addition this feature makes debugging and developing KWin much easier because you can just restart the compositor without interrupting your workflow.

Pretty cool in principle, although the default word list on my system is awful for wordle.

I’m surprised he was able to watch Paramount Plus. I would assume that site requires Widevine DRM, and would not assume that it’s available on RISC-V.

As for Blender and Kdenlive not working I’m assuming it’s not because of the ISA like Christopher said, but rather because the board likely ships with crappy GPU driver blobs that only support OpenGL ES and no desktop OpenGL. Which is an important detail that this guy always misses in SBC reviews.

Can we stop shaming people who buy NVIDIA?

For one, people want to keep using what they have and not buy something new just because it may work better on Linux, abd they may not even be able to afford an upgrade. They probably didn’t even know about Linux compatibility when they got it.

And additionally, some people have to use NVIDIA because e. g. they rely on CUDA or something (which is unfortunate but not their fault).

And honestly, NVIDIA is fine on Linux nowadays. It sucks that support for older cards will likely stay crappy forever but hopefully with the open kernel drivers and NVK newer cards won’t have to suffer that fate.

Basically none of your current software works out of the box (you’ll need a special Xorg implementation that works with your Wayland implementation in order to run non-Wayland applications).

I’ve never seen any distro with Wayland that didn’t have XWayland set up and working out of the box, so that’s not something the end user needs to worry about. And “Basically None” is also not true anymore. Practically anything made with GTK3/4, Qt5/6, SDL2, recent Electron versions etc. natively runs on Wayland. It’s mostly games, Wine and a lot of proprietary software that doesn’t.

Most applications are specific to your Wayland implementation instead of a general application that runs in all environments.

Wdym by that exactly? I mean, a KDE application will run just fine on GNOME or Wlroots compositors.

There are several remarks in that article that bothered me. I agree with their message overall and am a strong proponent of Wayland but…

Unless your workflow (and hardware) comes from 20+ years ago, you have almost no reason to stick with Xorg

There definitely are valid use cases that aren’t 20 years old that will keep you on X11 for a little while longer. And hardware too: NVIDIA dropped driver support for Kepler GPUs and older before they added GBM support which is effectively a requirement for Wayland, so you can’t use these older cards on Wayland with the proprietary drivers

Of course, NVIDIA likes to do their own thing, as always. Just use Nouveau if you want to do anything with Xwayland, and you don’t have several GPUs.

Uh, no. Nouveau is not a serious option for anyone who likes using their GPU for useful things. And on those older cards it will likely never work well.

The author of that article seems extremely ignorant of other people’s needs.

I have a laptop with hybrid Intel+NVIDIA graphics, and I can say that offloading games and such to the dGPU while letting the iGPU handle everything else works with zero issues for me on Wayland.

On desktops where the NVIDIA GPU handles everything I don’t have that much experience on Wayland although when I did try it earlier this year it was surprisingly good, but with occasional dumb bugs like Plasma panels freezing or XWayland apps breaking in funny ways. Although honestly just a few years back running Plasma X11 on NVIDIA wasn’t much better than Wayland now.

I don’t think Discord screen sharing has sound on X11 either, does it?

I switched to Wayland over two years ago and these days I don’t look back at all. I don’t care if Wayland has full feature parity with X11 as long the features I actually use are supported which they are.

Clipboard sharing in VirtualBox doesn’t work right now (though I’m relatively sure it could be implemented by VirtualBox right now with Wayland as it is) and neither does AutoTyping in KeePassXC (not sure if there’s a mechanism for that on Wayland), though Autofill in the Browser works so it’s no big deal to me.

In return I get 1:1 touch gestures, better multi monitor support and an overall smoother desktop on Plasma Wayland so I’ll take it.

People often still make complaints about Wayland that have been fixed months or years ago and it’s a bit tiring.

s2idle is unfortunately the only supported state on my system apparently, no deep sleep :(