

Can’t really test that.
I may need to try ratbagd then :3


Can’t really test that.
I may need to try ratbagd then :3


It does have generic tools (eg. xdotool -> ydotool), but the most powerful way is to configure it in the DE/WM itself (eg. KDE’s shortcuts or sway’s bind command). To know if what you are doing is possible with ydotool or on sway, I’d need more specific info.
But my point was rather that it’s cool to have such functionality in the kernel, independent of desktop stack and DE/WM.


I’ve never been able to actually program my G502X Lightspeeds buttons


Sucks for wayland users tho
The only component actually fucking up boot has been the NVidia driver. Otherwise, Arch with testing repos has never failed me for years on many devices.
If you want to have at least some thrill, use testing repos. I had to fix GitLab two (2) times due to the main package not being linked against testing libraries (it took 10 seconds to ln -s the new to the old version), and had one breakage due to dovecot revamping their whole config system, but publishing no example/useful docs.


Updated the comment. (The ICD is explicitly installed by vulkan-radeon, vulkan-intel or nvidia-utils/vulkan-nouveau. Just as with all linux-firmware categories/companies being their own package now, this is probably done to minize unused space/bloat.)
Vanilla Arch Linux, testing repos, with an RX 7800XT.


I’ve just always followed the Arch wiki, and never tried using Vulkan without vulkan-radeon on my one PC with an AMD card. The wiki states: “Install the mesa package, which provides both the DRI driver for 3D acceleration and VA-API/VDPAU drivers for accelerated video decoding.” and “For Vulkan support install vulkan-radeon (lib32-vulkan-radeon for 32-bit applications).”.The vulkan page itself says:
To run a Vulkan application, you will need to install the vulkan-icd-loader package (and lib32-vulkan-icd-loader from the multilib repository if you also want to run 32-bit applications), as well as Vulkan drivers for your graphics card(s). There are several packages providing a vulkan-driver and lib32-vulkan-driver:
AMD: vulkan-radeon (or lib32-vulkan-radeon)
Intel: vulkan-intel (or lib32-vulkan-intel)
NVIDIA: there are two implementations:
nvidia-utils (or lib32-nvidia-utils) - NVIDIA proprietary
vulkan-nouveau (or lib32-vulkan-nouveau) - NVK (part of Mesa project)
The vulkan-radeon package provides the ICD (
# pacman -Qlq vulkan-radeon | grep -v '/$'
/usr/lib/libvulkan_radeon.so
/usr/share/drirc.d/00-radv-defaults.conf
/usr/share/licenses/vulkan-radeon/license.rst
/usr/share/vulkan/icd.d/radeon_icd.json
); so does nvidia-utils (
# pacman -Qlq nvidia-utils | grep -i icd | grep -v '/$'
/usr/share/vulkan/icd.d/nvidia_icd.json
/usr/share/vulkansc/icd.d/nvidia_icd_vksc.json
)
, but mesa does not.


mesa only coveres, OpenGL, according to the arch wiki.
also, the former, I couldn’t remember the correct word


It basically allows vulkan, the graphics engine, to work with AMD driver (which resides in the kernel). For OpenGL to work with it, you need the mesa package, but that’s usually installed anyway.
Edit: graphics API, not engine


Actually, there is one more package you might need: vulkan-radeon. The nvidia package, which you can remove then, provided that implementation itself.


Searching these devices produced no evidence relevant to the case. Nothing linked Klayme to the girl. No intimate images were found. Klayme did have a Kik account, but cops couldn’t even show that he had accessed the service during the period in question.
And then they want us to follow the law. Fucking fascists.
Fave: vim
First: notepad.exe
Future: vim
Honorable mention: vi
Loathed: Everything but (neo)?vim?
Current: vim
Longest: vim
Most likely not, just as pretty much all of those kind of forks.
Unless it’s actually breaking something, too few people actually care enough. And in this case, those that know enough to maintain it, know enough to not care.
I hate it. I just want vanilla sway; and i want everything else to look like it too.


openssh
and on the opposite side, nvidia drivers


Build time doubles again


How is that gatekeeping?


I think we should be proud. Linux is finally large enough to at least sort of get “hit” by a malware campaign, and it demonstrates the ease with which thousands of infected packages can be cleaned, because they are centralized to a few repositories. M$‘s only bet would be to update Defenders’ index and cross fingers that the signature doesn’t change.
Windows malware is always way out of control of M$, while that’s also the norm of uninfected programs.
Almost all Linux programs are by design installed from a central repo.
Well, I tried piper before, and some other tool. Both did not work. iirc, piper did not even detect the device