For now they didn’t share nothing about it!

Tho in the roadmap for plasma 6.5 (https://community.kde.org/Plasma/Plasma_6) you can find:

• Union theming system tech preview
• plasma-login SDDM replacement
• Wayland picture-in-picture protocol support
• Rounded bottom window corners
• Location services KCM
• Global shortcuts found by KRunner
• Automatic brightness adjustment on devices with light sensors

No GPU acceleration still?

In my opinion, this is a good approach. While the vast majority of PC users aren’t used to these settings, it’s great that those who prefer them still have the option to change them. This is especially positive because features like single-click to open or drag-and-drop by default aren’t used outside of KDE — in fact, the standard behavior across macOS, Windows, and most other desktop environments is different.

This is the same kind of thing that annoys me about macOS: they change things that worked fine for years and replace them with features no one asked for. For example, why is the scroll wheel inverted by default? And if you change it, the touchpad scrolling becomes inverted instead. Why do I need to hold Control and click just to perform a right-click? It’s a change that complicates things instead of improving them.

There is kmail tho it’s not the best, far better to use something like thunderbird!

I’m not placing blame on the Linux Foundation, Linus, or anyone else for that matter. However, I believe that if Linus has publicly endorsed the use of Rust in the kernel, that decision is already largely set in motion. On the other hand, if the community collectively opposes the integration of Rust with C and no action is taken to address these problems, and everyone say no, then there is little to no reason to make the initial statement.

Much of the work being produced by Rust developers seems to struggle, often because it’s not made in C and because of maintainers saying “No I don’t want any rust code near my C code”.

I recognize that there are various technical factors influencing this decision, but ultimately it was the creator’s choice to support it.

Italy

That’s what I tought

Mhhh, your profile picture remind me of something

Lol

Dude Tc helicon dropped software support for the GoXLR 1 year ago, indeed the community continuing the support for this device was at first a GoXLR control software for Linux that, after some time, became a windows app too. https://github.com/GoXLR-on-Linux/GoXLR-Utility

I don’t know what the hell are you talking about

No better default gui?

The actual account name

I have a Elite controller v2 and I wasn’t able to pair it on my laptop with arch, indeed I had to follow this instruction on their wiki https://atar-axis.github.io/xpadneo/#troubleshooting

Use a Windows 10 computer on the same Bluetooth adapter to pair with the controller. It must absolutly be on the same Bluetooth adapter, i.e. the same computer (can be inside a virtual machine with Bluetooth passthrough) if it’s an internal Bluetooth adapter, or the same Bluetooth dongle. Then, you can get the pairing keys and install them within your Linux Bluetooth system.

Tho if you watch carefully on the xpadneo wiki, if you want to pair a xbox elite v2 controller with bluetooth you first need to pair it on windows with the same bluetooth card to be able to use it!

Ah ok thanks!

I’ve heard of it before, but the one thing preventing me from using it is my uncertainty about whether the mapping is done through software. Do I need Rewasd to always run in the background, or with the Elite V2 can I remap the key bindings directly on the controller without needing the software to be active?