Historically speaking, IME has been a low hanging fruit of attack vectors and intel has arguably speaking had worse problems with security vulnerabilities on hardware and firmware levels than say AMD or ARM. A bit anecdotal, but there you are.
To be fair, if you’re referring to the “alleged” backdoors in Intel processes, there’s pretty similar stuff going on in the AMD side too. That said, I still totally get not wanting to support Intel since they’re definitely the shadiest of the two, and they’ve been awful value these days.
The Framework 13 AMD is pretty great though, can confirm. It’s all I’ve ever wanted in a decent, repairable laptop.
There is a package called android-transfer-file or something like that in the void repos but I’m not sure if its also in the mint repos, might be worth checking, its a gui app that makes it very straightforward to transfer files. Or in last resort you can always git clone the project and use ‘make’ to build manually the app
It seems as if the uBlue images ship the required OpenRazer kmod by default. Therefore, I would suggest you to take a look at those. You still need to follow some additional steps though 😅. Which might not be very intuitive… Thus, I propose the following: if you’ll rebase to uBlue, you might as well rebase to Bazzite. After the rebase has been completed, the (post-)installation software should already give you the option (it’s just a simple toggle) to install OpenRazer. The toggle is clearly visible in this frame.
If you perceive Bazzite as too opinionated for your taste, then perhaps you might opt to the following instead:
I wanted to make the same suggestion with uBlue. There’s also the silverblue-main image, which is very vanilla and the one I use. The kmod is already pre-installed there.
Bazzite can also be great, but it’s too opinionated for my taste. I like Silverblue also more like the devs intended.
Idk what exactly you’re asking for, but this is already an option for me on teams in chrome running under Wayland??? Like when I choose start presenting it pops up a dialog with window options including the whole desktop.
The difference is that the popup is optional on X. They can also just access the window data directly. On Wayland they have no way to access other windows without asking for permission via the “Portal” popup.
I’m Arch and so is my wife (actually) and it doesn’t have a version. We just roll … and today my dongled, wireless mouse has stopped moving. The buttons still work and my laptop touchpad works fine.
Oh wow! This is excellent news! I hope they’ll also provide other privacy/security related features like Heads, the removal of the camera and/or microphone modules, pre-installed privacy screen, tamper-evident screws and packaging.
Honestly, I don’t know if that’s the case; I always got scared whenever I saw the prerequisites for Heads in combination with the strict list of supported hardware. FWIW, the NV41 that’s used for enabling Heads on NovaCustom’s device is included in the short list of supported hardware for Heads, while -unfortunately- the same doesn’t apply to the StarBook. I would love to be proven wrong though!
I almost never share an entire screen, but rather single application windows; when I absolutely must share visual information from multiple applications simultaneously, I create a separate virtual desktop for presenting. Is this not possible?
I know this is possible, but it makes switching different windows a chore. Since I have GUI programs running under different users, I would want the screensharing program to not even be aware that other user’s GUI programs are in the screen
We are making dbus-broker our default implementation of D-Bus, for improved performance, reliability and integration with systemd.
For the foreseeable future we will still support the use of dbus-daemon, the previous implementation. Pacman will ask you whether to install dbus-broker-units or dbus-daemon-units. We recommend picking the default.
For a more detailed rationale, please see our RFC 25.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.