Post Syndicated from jzb original https://lwn.net/Articles/1026848/

Security updates have been issued by Debian (commons-beanutils, dcmtk, nginx, trafficserver, and xorg-server), Fedora (atuin, awatcher, dotnet8.0, firefox, glibc, gotify-desktop, keylime-agent-rust, libtpms, mirrorlist-server, qt6-qtbase, qt6-qtimageformats, udisks2, xorg-x11-server, and xorg-x11-server-Xwayland), Mageia (apache-mod_security, clamav, docker, python-django, tomcat, udisks2, and yarnpkg), Oracle (firefox, libblockdev, mod_auth_openidc, perl-FCGI, perl-YAML-LibYAML, tigervnc, and xorg-x11-server and xorg-x11-server-Xwayland), Slackware (libssh and mozilla), SUSE (gimp, gstreamer-plugins-good, icu, ignition, kernel, pam-config, perl-File-Find-Rule, python311, and webkit2gtk3), and Ubuntu (linux, linux-aws, linux-aws-6.8, linux-gke, linux-gkeop, linux-ibm,
linux-lowlatency, linux-lowlatency-hwe-6.8, linux-nvidia,
linux-nvidia-6.8, linux-nvidia-lowlatency, linux-oem-6.8, linux, linux-gcp, linux-raspi, linux-realtime, linux-aws, linux-azure, linux-azure, linux-azure-6.8, linux-azure-5.15, linux-azure-fips, and linux-realtime).

Post Syndicated from jzb original https://lwn.net/Articles/1026552/

KDE contributor Nate Graham recently wrote
about the KDE Project’s plans for Plasma’s X11 session. He notes that
the project will continue to ensure that Plasma “continues to
compile and deploy on X11” and isn’t horribly broken. Major
regressions will probably be fixed, eventually, but the writing is on
the wall:

X11’s upstream development has dropped off significantly in recent
years, and X11 isn’t able to perform up to the standards of what
people expect today with respect to HDR, 10 bits-per-color monitors,
other fancy monitor features, multi-monitor setups (especially with
mixed DPIs or refresh rates), multi-GPU setups, screen tearing,
security, crash robustness, input handling, and more.

As for when Plasma will drop support for X11? There’s currently no
firm timeline for this, and I certainly don’t expect it to happen in
the next year, or even the next two years. But that’s just a guess; it
depends on how quickly we implement everything on
https://community.kde.org/Plasma/Wayland_Known_Significant_Issues. Our
plan is to handle everything on that page such that even the most
hardcore X11 user doesn’t notice anything missing when they move to
Wayland.

Post Syndicated from jzb original https://lwn.net/Articles/1026531/

The postmarketOS project,
which creates a Linux distribution for mobile devices, announced
it was working on adding a version with systemd last March. That day
has arrived with the announcement
of version 25.06:

We considered supporting an upgrade from OpenRC to systemd in our
upgrade script, but then decided against it as such an upgrade path
might introduce its own bugs and we would rather spend the time
improving other parts of postmarketOS. So for this one-time scenario
we ask you to please reinstall postmarketOS to get from OpenRC to
systemd. Thank you for your understanding!

Post Syndicated from jzb original https://lwn.net/Articles/1025560/

Adrian Vovk, a GNOME contributor and member of its release
team, recently announced
in a blog post that GNOME would be adding new dependencies on systemd, and soon. The idea is to shed
GNOME’s homegrown service manager in favor of using systemd, and to
improve GNOME’s ability to run concurrent user sessions. However, the
move is also going to throw a spanner in the works for the BSDs and
Linux distributions without systemd when the changes take effect in
the GNOME 49 release that is set for September.

Post Syndicated from jzb original https://lwn.net/Articles/1025863/

The KDE Project has announced the
Plasma 6.4 release. New features include more flexible tiling
features, improvements to the Spectacle screen capture utility, a
number of accessibility enhancements, and much more. See the changelog
for a complete list of new features, enhancements, and bug fixes.

Post Syndicated from jzb original https://lwn.net/Articles/1025862/

Security updates have been issued by Debian (gst-plugins-bad1.0, konsole, and libblockdev), Oracle (buildah, containernetworking-plugins, gimp, git-lfs, gvisor-tap-vsock, kernel, libvpx, podman, and skopeo), Red Hat (apache-commons-beanutils and thunderbird), Slackware (xorg), SUSE (gdm, golang-github-prometheus-alertmanager, golang-github-prometheus-node_exporter, golang-github-prometheus-prometheus, govulncheck-vulndb, grafana, kernel, Multi-Linux Manager, Multi-Linux Manager Client Tools, openssl-3, pam, python-cryptography, python-requests, python-setuptools, python3-requests, SUSE Manager Server, systemd, ucode-intel, xorg-x11-server, and xwayland), and Ubuntu (dwarfutils, mujs, node-katex, xorg-server, xorg-server-hwe-16.04, xorg-server-hwe-18.04, and xorg-server, xwayland).

Post Syndicated from jzb original https://lwn.net/Articles/1025127/

Accessibility features and the work that goes into developing those features
often tend to be overlooked and are poorly understood by all but the people who actually
depend on such features. At Fedora’s annual developer conference, Flock, Lukáš Tyrychtr sought to
improve understanding and raise awareness about accessibility with his session on accessibility
barriers and screen-reader functionality in GNOME. His talk provided rare insight
into the world of using and developing open-source software for visually-impaired
users—including landing important accessibility improvements in
the latest GNOME release.

Post Syndicated from jzb original https://lwn.net/Articles/1025634/

The Kubernetes project has announced
that it will be losing its “special status” with the Slack communication platform and will be
downgraded to the free tier in a matter of days:

On Friday, June 20, we will be subject to the feature
limitations of free Slack. The primary ones which will affect us
will be only retaining 90 days of history, and having to disable
several apps and workflows which we are currently using. The Slack
Admin team will do their best to manage these limitations.

The project has a FAQ
covering the change, its impacts, and more. The CNCF projects staff
has proposed
a move to the Discord service as
the best option to handle the more than 200,000 users and thousands of
posts per day from the Kubernetes community. The Kubernetes Steering
Committee will be making its decision “in the next few weeks“.

Post Syndicated from jzb original https://lwn.net/Articles/1025628/

Version
2.50.0 of the Git source-code management system has been released
with a long list of new user features, performance improvements, and
bug fixes. See the announcement and this
GitHub blog post for details.

Post Syndicated from jzb original https://lwn.net/Articles/1025405/

The Radicle peer-to-peer code
collaboration project has released Radicle
Desktop: a graphical interface designed to simplify more complex
parts of using Radicle such as issue management and patch reviews.

Radicle Desktop is not trying to replace your terminal, IDE, or code
editor – you already have your preferred tools for code browsing. It
won’t replace our existing app.radicle.xyz and search.radicle.xyz for
finding and exploring projects. It also doesn’t run a node for
you. Instead, it communicates with your existing Radicle node,
supporting your current workflow and encourages gradual adoption.

LWN covered Radicle
in March, 2024.

Post Syndicated from jzb original https://lwn.net/Articles/1024486/

The last year has been a rocky one for the WordPress community. Matt
Mullenweg—WordPress co-founder and
CEO of WordPress hosting company Automattic—started a messy public spat with
WP Engine in September and
has proceeded to use his control of the project’s WordPress.org
infrastructure as weapons against the company, with the community
caught in the crossfire. It is not surprising, then, that on
June 6 a group of WordPress community participants announced the
Federated
and Independent Repositories Package Manager (FAIR.pm) project. It
is designed to be a decentralized alternative to WordPress.org with a
goal of building “public digital infrastructure that is both
resilient and fair“.

Post Syndicated from jzb original https://lwn.net/Articles/1025224/

Version
10.0 of the Rocky Linux distribution has been released. As with
the AlmaLinux 10.0
release, Rocky Linux 10.0 is based on Red Hat Enterprise Linux (RHEL)
10. See the
release notes for details.

Post Syndicated from jzb original https://lwn.net/Articles/1024939/

Security updates have been issued by AlmaLinux (glibc, grafana, kernel-rt, libjpeg-turbo, libxslt, and thunderbird), Debian (curl), Fedora (dtk6core, dtk6gui, dtk6log, dtk6widget, fcitx5-qt, gammaray, kddockwidgets, kwin, LabPlot, libqtxdg, nheko, plasma-integration, python-pyqt6, python-pyside6, qt-creator, roundcubemail, zeal, and a large number of qt6 packages), Oracle (firefox, glibc, grafana, kernel, libxslt, perl-FCGI, python3.12-cryptography, thunderbird, and zlib), SUSE (glib2, libjxl, libsoup2, nbdkit, nodejs22, perl-Crypt-OpenSSL-RSA, perl-YAML-LibYAML, python3, tomcat, and transfig), and Ubuntu (dotnet8, dotnet9 and samba).

Post Syndicated from jzb original https://lwn.net/Articles/1024758/

Jean Baptiste Lallement, a member of Canonical’s desktop team, has
announced
that Ubuntu will drop support for GNOME on X11 in the 25.10
(“Questing Quokka”) release set for October. GNOME plans to remove
X11 support in GNOME 49, which is scheduled for September, so
Ubuntu is looking to be proactive:

Ubuntu 25.10 is the last interim release before our next LTS (Ubuntu
26.04). By moving now, we give developers and users a full cycle to
adapt before the next LTS, align with GNOME 49 and reduce
fragmentation while simplifying our support matrix heading into the
LTS.

Fedora decided in
early May to drop X11 support for GNOME in Fedora 43, which
is also due in October.

Post Syndicated from jzb original https://lwn.net/Articles/1024259/

At Flock,
Fedora’s annual developer conference, held in Prague from June 5
to June 8, two members of the Fedora
documentation team, Petr Bokoč and Peter Boy, led a
session on the state of Fedora documentation. The pair covered a
brief history of the project’s documentation since the days of Fedora Core 1,
challenges the documentation team faces, as well as plans to improve Fedora’s
documentation by enticing more people to contribute.

Post Syndicated from jzb original https://lwn.net/Articles/1024633/

The FreeBSD Foundation
has announced
a report
for work completed in April to improve FreeBSD support for
laptops. This includes installer updates, improved suspend/resume
behavior, as well as progress on a
port of Linux 6.7 and 6.8 graphics drivers to drm-kmod. A
roadmap
for the FreeBSD laptop work is also available.

Post Syndicated from jzb original https://lwn.net/Articles/1001773/

Nyxt is an unusual web
browser that tries to answer the question, “what if Emacs was a
good web browser?”. Nyxt is not an Emacs package, but a full
web browser written in Common Lisp and available under the BSD
three-clause license. Its target audience is developers who want a
browser that is keyboard-driven and extensible; Nyxt is also developed
for Linux first, rather than Linux being an afterthought or just a
sliver of its audience. The philosophy (as described in its FAQ)
behind the project is that users should be able to customize all of
the browser’s functionality.

Post Syndicated from jzb original https://lwn.net/Articles/1024345/

The Netdev
0x19 conference was held in Zagreb, Croatia from March 10
through March 13. The organizers announced
today that the videos and slides for all sessions are now
online. Topics from the conference include IRQ suspension, the future
of SO_TIMESTAMPING, remote TCP connection offloading, and
more.

Post Syndicated from jzb original https://lwn.net/Articles/1024190/

Version
3.0 of the privacy-centric, open-source mobile operating system
has been released. Notable changes in this release include improved
privacy tools, a “find my device” feature, and more. LWN looked at /e/OS in
March.

Post Syndicated from jzb original https://lwn.net/Articles/1023837/

Outgoing Fedora Project Leader Matthew Miller has posted an update
on Fedora’s high-level plan through 2028:

[Fedora] Council members identified potential Initiatives that we
believe are important to work on next. We came up with a list of
thirteen — which is way more than we can handle at once. We previously
set a limit of four Initiatives at a time. We decided to keep to that
rule, and are planning to launch four initiatives in the next months

The initiatives are: making Fedora releases block on accessibility
issues, experimenting with a “GitOps” workflow for packaging,
migrating from Pagure to Forgejo, and “making sure Fedora
Linux is ready for people who want to work on machine learning and AI
development“.