that_leaflet

joined 1 year ago
[–] that_leaflet@lemmy.world 9 points 1 day ago* (last edited 1 day ago)

Hoping that the preliminary Wayland support makes it in.

https://wiki.xfce.org/releng/wayland_roadmap

[–] that_leaflet@lemmy.world 1 points 2 days ago

If you continue without adding the keys, you may have issues if you rely on out of tree drivers like Nvidia. Personally, I would hit continue then leave secure boot off.

[–] that_leaflet@lemmy.world 2 points 2 days ago (2 children)

You can still do MOK management when Secure Boot is off.

[–] that_leaflet@lemmy.world 9 points 2 days ago (4 children)

For Secure Boot, the kernel is "signed" with a key. During boot up, Secure Boot checks to make sure that key is valid. Most kernels are signed with Microsoft's key that is preloaded on basically every system. However, not all kernels can be signed with Microsoft's key; if you install a proprietary driver (which you likely selected to during the setup), to continue using secure boot you need to sign the kernel using your own key.

That's what MOK management is for. You are adding your own key to your system to use for Secure Boot.

Personally, I just disable Secure Boot. While it does have some security benefits, it's not worth the headache IMO.

[–] that_leaflet@lemmy.world 2 points 2 days ago

It says that in the 9to5Linux article, not the original source. The blog post simply says "becomes ready for inclusion in the next version of Cinnamon."

Not to say that the 9to5Linux article is wrong since Linux Mint very well could ship the new theme as an option, but not the default theme.

[–] that_leaflet@lemmy.world 5 points 3 days ago (2 children)

I don’t think this new design will be used in Linux Mint by default. I believe this is just for distros that use Cinnamon’s default theme, which is different from Linux Mint’s default theme.

But who knows, maybe it could also become default in Linux Mint.

39
submitted 3 days ago* (last edited 3 days ago) by that_leaflet@lemmy.world to c/linux@lemmy.ml
[–] that_leaflet@lemmy.world 3 points 5 days ago

I haven’t been able to try it yet. I only use Proton, but Valve compiles it without winewayland.

[–] that_leaflet@lemmy.world 19 points 6 days ago (1 children)

Not directly helping with SteamOS 3. But this financial support is helping Arch improve.

 

Interestingly, the developer is already bringing up the possibility of using Wayland by default.

Btw, after this I feel like the driver is much more usable, would it be acceptable to enable it by default? Is there any other major feature missing (given that virtual display settings is being worked on)?

[–] that_leaflet@lemmy.world 1 points 6 days ago (1 children)

I’ll change it whenever I post these.

[–] that_leaflet@lemmy.world 9 points 1 week ago

It's kinda ironic that theming GTK is easier when it doesn't officially support theming. Especially when it comes to Qt flatpak apps.

[–] that_leaflet@lemmy.world 18 points 1 week ago

Linux support is definitely moving slower than the Rust team wants, but the team and Linus are still optimistic.

[–] that_leaflet@lemmy.world 22 points 1 week ago* (last edited 1 week ago) (2 children)

Android uses a forked versions of the Linux kernel, based on Linux LTS versions. They added in Rust support in 2019 and most new code since then has been written in Rust in order to avoid memory safety vulnerabilities. And memory safety vulnerabilities have been significantly down since 2019.

Now that upstream Linux is adopting Rust, we should hopefully see a similar results. Though likely slower than Google (they went all-in on Rust) while upstream Linux new code will seemingly be mainly C for the foreseeable future.

view more: next ›