don’t do what I did: sudo pacman -Rdd dbus (because dbus-broker doesn’t have package conflicts set) sudo pacman -S dbus-broker dbus-broker-units
This will not work (even less so if you don’t bother to boot from a recovery drive). dbus broker seems very much beta and some packages with compiled-in library dependencies might completely fail altogether. I’m not sure how they’re gonna make this new dbus daemon work at all considering that this will most likely break a lot of unmaintained packages and requires new releases of active packages, but we’ll see…
I ended up having to restore a snapshot because I could no longer log in, and snapper snapshots were no longer taken (which is a plus I guess)
Edit: garuda-update installs this properly. I’m a total buffoon
The vendor strongly recommends updating as soon as possible all vulnerable versions of the DevSecOps platform (manual update required for self-hosted installations) and warns that if there is "no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, this means all types are affected.”
…causing his Linux kernel builds to be as twice as long as with previous kernels. An AMD Linux engineer was able to reproduce the regression and with upstream developers there is now a believed fix for this issue in the latest scheduler code.
GitLab admins should apply the latest batch of security patches pronto given the new critical account-bypass vulnerability just disclosed.
Linus Torvalds has indefinitely postponed the merge window for version 6.8 of the Linux kernel after a winter storm knocked out power and internet near his work-from-home location in Oregon.
“India, for instance, accounts for 30 to 40 per cent of chip design activities globally, with a higher percentage in physical design.”
The Indian tech site Analytics India Magazine just published a nice article by Pritam Bordoloi that equates what’s currently happening in India with RISC-V with what happened in the US when Linux came on the scene in the 1990s.
You would think his wife would have noticed there was something deeply wrong with him from the beginning. I mean, just look at those eyes, they’re screaming red flags!
I used to run in ReiserFS. In many ways it was ahead of its time. When Hans was arrested/convicted, it was the first time I realized how “hardcore” some developers could be.
In place of workstation, Fuchsia is gaining the much more minimal “workbench” designed almost exclusively for developer testing purposes. Google even goes so far as to say that workbench should not serve as a foundation for a Fuchsia-based product (like the Nest Hub software).
At first, the shift from workstation to workbench seems like a simple name change, but the subsequent discontinuation of Chrome for Fuchsia all but confirms that Google does not intend to release a desktop/mobile device directly powered by Fuchsia in the foreseeable future.
Hangover is a project based on Wine initially focused on running x86 32-bit Windows apps on AArch64 Linux. Hangover works by running Wine atop various emulators such as QEMU, FEX, or Box64 to handle the processor/ISA translation.
Hangover is now aiming for x86_64 emulation support on RISC-V this year.
This could bring Proton support for Asahi Linux & M-series Apple devices.
