JRepin

The LXQt team announces the release of LXQt 2.1.0, the Lightweight Qt Desktop Environment.

Through its new component lxqt-wayland-session, LXQt 2.1.0 supports 7 Wayland sessions (with Labwc, KWin, Wayfire, Hyprland, Sway, River and Niri), has two Wayland back-ends in lxqt-panel (one for kwin_wayland and the other general), and will add more later. All LXQt components that are not limited to X11 — i.e., most components — work fine on Wayland. The sessions are available in the new section Wayland Settings inside LXQt Session Settings. At least one supported Wayland compositor should be installed in addition to lxqt-wayland-session for it to be used.

There is still hard work to do, but all of the current LXQt Wayland sessions are quite usable; their differences are about what the supported Wayland compositors provide:

• Labwc provides the most stable session, is very lightweight, neat and configurable, and has an extremely helpful and responsive team.
• Perhaps the most complete Wayland session is provided by KWin when extra KDE packages are installed. For now, it is the only Wayland compositor that supports LXQt Panel’s desktop switcher and LXQt Power Manager’s settings for turning off the monitor (see the Wayland Wiki for the latter).
• In additon to Kwin, fancy effects are also provided by Wayfire and Hyprland, the latter being one of the 4 tiling WMs to choose from.

Anyway, the best result is achieved by installing the latest stable version of the chosen Wayland compositor. Wayland users need to get familiar with Wayland counterparts of some X11 tools and the configuration of the compositor. They may use X11 apps through XWayland, but using apps that work directly on Wayland is the best choice. Also, see the Wayland Wiki.

"I'm not on Bluesky and I don't have any plans to join it anytime soon. I wrote about this in 2023: I will never again devote my energies to building up an audience on a platform whose management can sever my relationship to that audience at will

When a platform can hold the people you care about or rely upon hostage – when it can credibly threaten you with disconnection and exile – that platform can abuse you in lots of ways without losing your business. In other words, they can enshittify their service."

Welcome to the new home of "This Week in Plasma"! No longer is it a private personal thing on my (Nate Graham's) blog, but now it's a weekly series hosted here on KDE's infrastructure, open to anyone's participation and contribution! I'll remain the editor-in-chief for now, and welcome contributions via direct push to the relevant merge request on invent.kde.org. And after a post is published, if you find a typo or broken link, feel free to just fix it.

Anyway, this week we added a useful service to detect out-of-memory (OOM) conditions, did some UI polishing, and also a lot of bug-fixing! Check it out.

cross-posted from: https://lemmy.ml/post/21972449

Over the last few years, there has been a surge in interest and adoption of generative artificial intelligence systems, and a corresponding interest in clarifying and delineating what open source should mean for AI and how to ensure AI serves the public interest. The DPGA Secretariat has been an active part of these conversations. Recognizing the transformative potential of AI, we have explored ways to democratise its benefits, advocating for public spending on AI that prioritises public interest and equitable access. Additionally, we have been examining how the DPG Standard may need to adapt in order to better determine what constitutes AI systems as a type of digital public good, via a community of practice (CoP), co-hosted by UNICEF.

This work has been unfolding against a backdrop of other initiatives and organisations similarly addressing complex questions surrounding the future development and use of artificial intelligence in the public interest domain. One such particularly important initiative has been the work to define open source AI stewarded by the Open Source Initiative (OSI) with the involvement of a large number of stakeholders and experts. After a two year long process the Open Source AI Definition (OSAID) Version 1.0 was released on October 28.

This week, the Open Source Initiative (OSI) made their new Open Source Artificial Intelligence Definition (OSAID) official with its 1.0 release. With this announcement, we have reached the moment that software freedom advocates have feared for decades: the definition of “open source” — with which OSI was entrusted — now differs in significant ways from the views of most software freedom advocates.

cross-posted from: https://lemmy.ml/post/21991814

Thanks to Valve's Linux graphics team, VK_EXT_device_generated_commands is now supported by the Radeon "RADV" Vulkan driver with the upcoming Mesa 24.3 release.

Prominent RADV developer Samuel Pitoiset at Valve has landed support for VK_EXT_device_generated_commands, the multi-vendor device generated commands "DGC" implementation. Last month with Vulkan 1.3.296 the VK_EXT_device_generated_commands extension was introduced to succeed NVIDIA's vendor-prefixed DGC extension. The device generated commands extension allows for the GPU device to generate a number of commands for command buffers. VK_EXT_device_generated_commands is a very big and important addition to the Vulkan API: Valve's Mike Blumenkrantz has argued that DGC is the biggest addition to Vulkan since ray-tracing.

Thanks to Valve's Linux graphics team, VK_EXT_device_generated_commands is now supported by the Radeon "RADV" Vulkan driver with the upcoming Mesa 24.3 release.

Prominent RADV developer Samuel Pitoiset at Valve has landed support for VK_EXT_device_generated_commands, the multi-vendor device generated commands "DGC" implementation. Last month with Vulkan 1.3.296 the VK_EXT_device_generated_commands extension was introduced to succeed NVIDIA's vendor-prefixed DGC extension. The device generated commands extension allows for the GPU device to generate a number of commands for command buffers. VK_EXT_device_generated_commands is a very big and important addition to the Vulkan API: Valve's Mike Blumenkrantz has argued that DGC is the biggest addition to Vulkan since ray-tracing.

cross-posted from: https://lemmy.ml/post/21991387

AMD has been teasing the Ryzen 9000X3D Zen 5 CPUs with 3D V-Cache and today they formally announced the specs of the Ryzen 7 9800X3D processor that will begin shipping 7 November.

The AMD Ryzen 7 9800X3D is AMD's 8-core / 16-thread processor with 64MB of 3D V-Cache. This uses 2nd Gen AMD 3D V-Cache where the 64MB of cache is now underneath the processor cores so that the CCD is positioned closer to the heatsink/cooler. The intent is that the new 3D V-Cache processors will run cooler than prior generation 3D V-Cache processors.

The AMD Ryzen 7 9800X3D will boost up to 5.2GHz and feature a 4.7GHz while total it provides 104MB of cache. This 120 Watt processor will have a suggested retail price of $479 USD. Again, expect retail availability on 7 November.

AMD has been teasing the Ryzen 9000X3D Zen 5 CPUs with 3D V-Cache and today they formally announced the specs of the Ryzen 7 9800X3D processor that will begin shipping 7 November.

The AMD Ryzen 7 9800X3D is AMD's 8-core / 16-thread processor with 64MB of 3D V-Cache. This uses 2nd Gen AMD 3D V-Cache where the 64MB of cache is now underneath the processor cores so that the CCD is positioned closer to the heatsink/cooler. The intent is that the new 3D V-Cache processors will run cooler than prior generation 3D V-Cache processors.

The AMD Ryzen 7 9800X3D will boost up to 5.2GHz and feature a 4.7GHz while total it provides 104MB of cache. This 120 Watt processor will have a suggested retail price of $479 USD. Again, expect retail availability on 7 November.

CXX-Qt is a set of Rust crates for creating bidirectional Rust ⇄ C++ bindings with Qt. It supports integrating Rust into C++ applications using CMake or building Rust applications with Cargo. CXX-Qt provides tools for implementing QObject subclasses in Rust that can be used from C++, QML, and JavaScript.

For 0.7, we have stabilized the cxx-qt bridge macro API and there have been many internal refactors to ensure that we have a consistent baseline to support going forward. We encourage developers to reach out if they find any unclear areas or missing features, to help us ensure a roadmap for them, as this may be the final time we can adapt the API. In the next releases, we’re looking towards stabilizing the cxx-qt-build and getting the cxx-qt-lib APIs ready for 1.0.

Over the last few years, there has been a surge in interest and adoption of generative artificial intelligence systems, and a corresponding interest in clarifying and delineating what open source should mean for AI and how to ensure AI serves the public interest. The DPGA Secretariat has been an active part of these conversations. Recognizing the transformative potential of AI, we have explored ways to democratise its benefits, advocating for public spending on AI that prioritises public interest and equitable access. Additionally, we have been examining how the DPG Standard may need to adapt in order to better determine what constitutes AI systems as a type of digital public good, via a community of practice (CoP), co-hosted by UNICEF.

This work has been unfolding against a backdrop of other initiatives and organisations similarly addressing complex questions surrounding the future development and use of artificial intelligence in the public interest domain. One such particularly important initiative has been the work to define open source AI stewarded by the Open Source Initiative (OSI) with the involvement of a large number of stakeholders and experts. After a two year long process the Open Source AI Definition (OSAID) Version 1.0 was released on October 28.

cross-posted from: https://lemmy.ml/post/21951809

Fedora Linux provides a wide variety of users with leading edge open source technology in a community developed and maintained operating system. The Fedora KDE Spin combines the reliable and trusted Fedora Linux base with the KDE Plasma desktop environment and a selection of KDE applications – simple by default, yet powerful when needed.

Back in April 2024, Fedora Linux 40 included the KDE “MegaRelease 6” – the Plasma desktop environment, Frameworks application libraries (with the underlying Qt platform), and Gear application suite were all upgraded to new versions in one fell swoop to deliver improved performance and reliability. Since then, continuous upstream updates by the KDE teams to fix bugs and deploy new features were quickly deployed to Fedora 40 users, including breakthroughs such as Explicit Sync in Wayland (which addressed the most prevalent graphical glitches on Nvidia devices)!

Now, as part of the Fedora Linux 41 release, the KDE Spin again includes the very latest with the recently released KDE Plasma 6.2, up-to-date KDE applications and core system packages, and new ways of using Plasma on different devices.