Why do they recommend vanilla discord, dropbox, teamviewer and many more… There are way better alternatives available to replace this closed source tracking, and insecure software.
The Spectre vulnerability that has haunted hardware and software makers since 2018 continues to defy efforts to bury it.
On Thursday, Eduardo (sirdarckcat) Vela Nava, from Google's product security response team, disclosed a Spectre-related flaw in version 6.2 of the Linux kernel.
The bug, designated medium severity, was initially reported to cloud service providers – those most likely to be affected – on December 31, 2022, and was patched in Linux on February 27, 2023.
For low core count systems or systems with not enough large/performance cores, OpenGL threading ends up hurting performance more than it helps. The new logic in Mesa is disabling OpenGL threading by default if there are fewer than four big CPU cores.
An update on Maui, a new DE in development, better known as KNOME....
Lastly, I stumbled across a new-ish (2019) open source image format, AVIF, suppose to be far superior than JPEG. How did I stumble across it, you ask? I found a wallpaper using this format. Unfortunately on Garuda KDE, it would not show in Gwenview despite having 'libavif' installed. The only plugin I found that worked was in AUR, 'qt5-avif-image-plugin-git' . This might be something Garuda devs might want to include as it is popularity grows along with WEBP format.
If you want to test it for yourselves, here is the prize in your cereal box, a new wallpaper that should fit nicely with the Garuda Dragonized color theme and style. Download the wallpaper which is in the .avif format, and see if you can view it in Gwenview (KDE users.)
Yes I can see it in gwenview. I don’t have qt5-avif-image-plugin-git installed.
Strange, must be pulling it from some other plugin I don't have installed.
I’m not a fan of AVIF because it is really slow.
AVIF has some drawbacks compared to JPEG XL, like a reputation for being slower to create. That could slow down photo slideshows on the web and hamper burst mode photography on your phone.
Test result:
<Decode> [PNG]: Time: 1.43 ms
<Decode> [JPEG]: Time: 0.39 ms
<Decode> [HEIC]: Time: 1.47 ms
<Decode> [HEIF]: Time: 102.06 ms
<Decode> [WebP]: Time: 24.00 ms
<Decode> [BPG]: Time: 39.60 ms
<Decode> [FLIF]: Time: 364.84 ms
<Decode> [AVIF]: Time: 154.54 ms
<Encode> [PNG]: Time: 39.63 ms
<Encode> [JPEG]: Time: 2.46 ms
<Encode> [HEIC]: Time: 65.51 ms
<Encode> [HEIF]: Time: 1799.63 ms
<Encode> [WebP]: Time: 168.42 ms
<Encode> [BPG]: Time: 2761.79 ms
<Encode> [FLIF]: Time: 6160.68 ms
<Encode> [AVIF]: Time: 346592.24 ms
| Codec | Encoding Speed (MP/s) | Decoding Speed (MP/s) |
|---|---|---|
| JPEG (libjpeg-turbo) | 49 | 108 |
| HEVC (HM) | 0.014 | 5.3 |
| HEVC (x265) | 3.7 | 14 |
| JPEG XL | 50 | 132 |
If giant corporations were concerned about “climate change” then JXL would be the preferred codec.
Good info! Yeah, I don't see this image format used very often, unlike Webp. Maybe that is the reason. 
And more....
/me faints
Well, the GitHub issue was opened in 2019. Since 2020, AVIF has been developed by the 'Alliance for Open Media'.
Is this issue still there in 2023?
Speed
AVIF had problems with its decoding and encoding speed. Recent releases of decoders achieved various performance improvements. Encoding is however still a problem and slow. It doesn't support progressive rendering - a process of decoding where portions of an image are incrementally decoded from an incomplete image file. This can dramatically increase the viewing speed by allowing for a lower-quality preview image to be displayed while the rest of the image is decoded. Unlike some legacy formats like PNG, AVIF is parallelizable, allowing the encoder to take advantage of multi-threaded processors instead of leaving all the encoding and decoding to a single core. JPEG XL is faster across the board with single-core encode and decode speeds and is more parallelizable than AVIF. Suppose you want a speedy codec, with fast decode times being crucial for web delivery. In that case, JPEG XL is a compelling option. Although, the lower file sizes achieved by AVIF for low-fidelity photos could give a speed advantage in download times, especially on slow broadband.
This past week the Free Software Foundation finally commented on Google’s decision to deprecate JPEG-XL and the FSF says it emphasizes the need for browser choice and free media formats.
Maybe the FSF was reading this thread 
The vulnerability, tracked as CVE-2023-2033, can be exploited by a malicious webpage to run arbitrary code in the browser. Thus, surfing to a bad website with a vulnerable browser could lead to your device being hijacked. Exploit code for this hole is said to be circulating, and may well be in use already by miscreants.
This high-severity type-confusion bug is present in at least Chrome for desktop versions prior to 112.0.5615.121. Google released that version on April 14 for Windows, Mac, and Linux to close the security hole, which lies in the V8 JavaScript engine.
That new version should be installed as soon as possible, either automatically or manually.
Manjaro 22 Review on Distrowatch
Calamares crapped out.
Is that down to incompetence, bad management or just straight up bad luck with an updated package?
I had never faced such issues back when I ran manjaro, and I did my fair share of reinstalls.
Yes. With Calamares, anyway. It harkens back to days of yore, when Manjaro was still sub-1.xx release. Except back then the Cinnarch installer worked.
Broken basic functionality. I would like to see the author ask for help in Manjaro forums to see what happens next.