We will switch authentication from OpenID to OIDC (OpenID Connect). There will be a short outage to do this.
admin )
on 2024-11-13 08:00:00 UTC
We will switch authentication from OpenID to OIDC (OpenID Connect). There will be a short outage to do this.
admin )
on 2024-11-06 08:00:00 UTC
It’s almost time for the Linux Distributions DevRoom at FOSDEM again! Let’s dive into what we’d like to see and how you can get involved! Submit your talk to FOSDEM, when you’re ready! Read on for further information.
From the FOSDEM website:
Developer rooms are assigned to self-organising groups to work together on open source projects, to discuss topics relevant to a broader subset of the community, etc.
The general idea is that a group of people get together to organize a mini-event inside the FOSDEM umbrella. The groups of folks submit a proposal to the FOSDEM organizers, and then recruit content and build a schedule for the room. Everyone involved is likely to be a volunteer, but the content is always extremely beneficial, and presented by leaders and experts on their topics.
The Distributions DevRoom provides a unique home for the convergence of several different Linux distribution communities to share ideas and start conversations that matter to all of us. Although there are several different distributions that have different approaches to software packaging, choice of desktop environments, and various use cases, this Distributions DevRoom is a historic open forum. It is unique to FOSDEM in making a space for all of our communities to share and learn from each other.
The Fedora Project is co-organizing the Distributions Devroom at FOSDEM to foster collaboration and innovation among the diverse Linux distribution communities. By facilitating this Devroom, Fedora seeks to provide a space for open-source contributors and maintainers to exchange ideas, address shared challenges, and work on cross-distro interoperability. This event supports Fedora’s commitment to community-driven development, reflecting its values of openness and inclusivity. Join us to connect with fellow distribution developers, learn about pioneering projects, and contribute to shaping the future of Linux distributions.
We are looking for your most incredible talk for the Distributions DevRoom! No matter where your focus in Linux is (development, community, distribution, testing, documentation, etc.), we want to hear from you. The full CFP details can be found on the CFP email archive. For inspiration, you can even look at the schedule that we had last year!
Important Dates
Will you be at FOSDEM in 2025? The Distributions DevRoom welcomes volunteers to help with various day-of logistics for running the dev room. The list isn’t yet defined specifically, but generally we need people to do these things:
If you are interested in helping out with the Distributions DevRoom, send an introduction email to the FOSDEM distributions-devroom mailing list.
FOSDEM is a free conference that requires no registration of any kind. You just show up on the days of the event, and then attend the talks that you want to attend. It is an extremely popular event, so the talks are also recorded and posted later on the FOSDEM website.
When the Distributions DevRoom schedule is live, you’ll be able to find it on the FOSDEM website, so keep an eye out for updates!
Don’t miss the chance to connect with the Linux distribution community! Whether you’re passionate about the future of operating systems or just curious about the latest developments, the Distributions Devroom at FOSDEM is your opportunity to engage with like-minded enthusiasts and developers. Join us for in-depth discussions, technical insights, and collaborative sessions. Be part of shaping the next wave of innovation in Linux distributions! Mark your calendar, and come ready to contribute, learn, and be inspired.
admin )
on 2024-11-05 21:45:42 UTC
Fedora 41 has been released! 
So let’s see what arrives with the new releases for the Fedora Atomic Desktops variants (Silverblue, Kinoite, Sway Atomic and Budgie Atomic).
After a long wait and a lot of work and testing, bootloader updates are finally enabled by default for Atomic Desktops.
For now, only UEFI systems will see their bootloader automatically updated on boot as it is the safest option. Automatic updates for classic BIOS systems will be enabled in the upcoming weeks.
If you encounter issues when updating old systems, take a look at the Manual action needed to resolve boot failure for Fedora Atomic Desktops and Fedora IoT Fedora Magazine article which includes instructions to manually update UEFI systems.
Once you are on Fedora 41, there is nothing more to do.
See the Enable bootupd for Fedora Atomic Desktops and Fedora IoT change request and the tracking issue atomic-desktops-sig#1.
The next major evolution for the Atomic Desktops will be to transition to Bootable Containers.
We have established a roadmap (atomic-desktops-sig#26) and for Fedora 41, we added dnf5 and bootc to the Bootable Container images of Atomic Desktops.
Those images are currently built in the Fedora infrastructure (example) but not pushed to the container registry.
The images currently available on quay.io/fedora (Silverblue, Kinoite, etc.) are mirrored from the ostree repository and thus do not yet include dnf5 and bootc.
Once releng#12142 has been completed, they will be replaced by the Bootable Container images.
In the mean time, you can take a look at the unofficial images (see the Changes in unofficial images section below).
See the DNF and bootc in Image Mode Fedora variants change request and the tracking issue atomic-desktops-sig#48.
Fedora Silverblue comes with the latest GNOME 47 release.
For more details about the changes that alongside GNOME 47, see What’s new in Fedora Workstation 41 on the Fedora Magazine and Fedora Workstation development update – Artificial Intelligence edition from Christian F.K. Schaller.
Ptyxis is a terminal for GNOME with first-class support for containers, and thus works really well with Toolbx (and Distrobox). This is now the default terminal app and it brings features such as native support for light/dark mode and user-customizable keyboard shortcuts.
See Ptyxis’ website.
Fedora Silverblue is now Wayland only by default. The packages needed for the X11 session will remain available in the repositories maintained by the GNOME SIG and may be overlayed on Silverblue systems that require them.
See the Wayland-only GNOME Workstation Media change request and the tracking issue: atomic-desktops-sig#41.
Fedora Kinoite ships with Plasma 6.2, Frameworks 6.7 and Gear 24.08.
See also What’s New in Fedora KDE 41? on the Fedora Magazine.
Kinoite Mobile is currently only provided as unofficial container images. See the Changes in unofficial images section below.
See the KDE Plasma Mobile Spin and Fedora Kinoite Mobile change request.
Fedora Sway Atomic comes with the latest 1.10 Sway release.
Nothing specific this release. The team is working on Wayland support.
Until we complete the work needed in the Fedora infrastructure to build and push official container images for the Atomic Desktops (see releng#12142), I am providing unofficial builds of those. They are built on GitLab.com CI runners, use the official Fedora packages and the same sources as the official images.
You can find the configuration and list on gitlab.com/fedora/ostree/ci-test and the container images at quay.io/organization/fedora-ostree-desktops.
With Fedora 41, we are now building two new unofficial images: Kinoite Mobile and COSMIC Atomic. They join our other unofficial images: XFCE Atomic and LXQt Atomic.
See How to make a new rpm-ostree desktop variant in Fedora? if you are interested in making those images official Fedora ones.
See the KDE Plasma Mobile Spin and Fedora Kinoite Mobile change request and the Fedora COSMIC Desktop Environment Special Interest Group (SIG) page.
If you are using the Sericea or Onyx container images, please migrate to the new Atomic names for Sericea & Onyx (sway-atomic and budgie-atomic) as we will remove the images published under the old name soon, likely before Fedora 42.
We will likely rename the official container images as well.
The polkit policy controlling access to the rpm-ostree daemon has been updated to:
See the Unprivileged updates for Fedora Atomic Desktops change request and the tracking issue atomic-desktops-sig#7.
The alternatives command (alternatives(8)) is now working on Atomic Desktops.
See the tracking issue atomic-desktops-sig#51 for more details and documentation.
Support for unlokcing a LUKS partition with the TPM is now included in the initramfs.
See the tracking issue atomic-desktops-sig#33 and the in progress documentation silverblue-docs#176.
Our friends in the Universal Blue project have prepared the update to Fedora 41 already. For Bazzite, you can find all the details in Bazzite F41 Update: New Kernel, MSI Claw Improvements, VRR Fixes, Better Changelogs, GNOME 47 & More.
For Bluefin (and similarly for Aurora), see Bluefin GTS is now based on Fedora 40.
I heavily recommend checking them out, especially if you feel like some things are missing from the Fedora Atomic Desktops and you depend on them (NVIDIA proprietary drivers, extra media codec, etc.).
We have made lot of progress since the last time, thus this section is going to be more exciting!
As I mentionned in First step towards Bootable Containers: dnf5 and bootc, the next major evolution for the Atomic Desktops will be to transition to Bootable Containers. See also the Fedora bootc documentation.
We have established a roadmap (atomic-desktops-sig#26) and we need your help to make this a smooth transition for all of our existing users.
Moving to composefs is one of the items on the roadmap to Bootable Containers. composefs is the next step for ostree based systems and will enable us to provide better integrity and security in the future.
For Fedora 41, we moved Fedora CoreOS and Fedora IoT to composefs.
For the Atomic Desktops, this is planned for Fedora 42 as we still have a few issues to resolve. See the Enabling composefs by default for Atomic Desktops change request and the tracking issue atomic-desktops-sig#35.
This fix is important for setups where the root disk is encryptd with LUKS and the user is asked a passphrase on boot. Right now, the keyboard layout is not remembered and defaults to the US QWERTY layout. Unfortunately this fix did not land in time for Fedora 41 but this will be part of the Fedora 42 installations ISOs. Help us test this by installing systems from a Rawhide ISO to confirm that this issue is fixed.
If you are impacted by this issue, see the tracking issue atomic-desktops-sig#6 for the manual workarounds.
We would like to unify the documentation for the Fedora Atomic Desktops into a single one instead of having per desktop environments docs which are mostly duplicate of one another and need to be constantly synced.
See the tracking issue atomic-desktops-sig#10.
We are looking for contributors to help us make the Fedora Atomic Desktops the best experience for Fedora users.
admin )
on 2024-11-04 08:00:00 UTC
This article introduces projects available in Flathub with installation instructions.
Flathub is the place to get and distribute apps for all of Linux. It is powered by Flatpak, allowing Flathub apps to run on almost any Linux distribution.
Please read “Getting started with Flatpak“. In order to enable flathub as your flatpak provider, use the instructions on the flatpak site.
These apps are classified into four categories:
In the Productivity section we have AppFlowy. This is a privacy-first open source workspace for your notes, tasks, databases, and more. I use this application offline, and I know a lot of people may complain about the need to create an account and cloud sync, but it works very smoothly. Their features are:
It offers a lot of AI features and synchronization with the mobile app, that requires an account on the website. The free tier is up to 2 users. You can check it out on their website.
You can install “AppFlowy” by clicking the install button on the web site or manually using this command:
flatpak install flathub io.appflowy.AppFlowy
In the Games section we have Flood It. This is a game with the simple premise of flooding the entire board with one color in the least amount of moves possible. Challenge yourself with this simple, yet addictive strategy game, where you need to flood-it as efficiently as you can! It’s a puzzle to pass time. Personally I’ve spent a lot of hours solving Flood It puzzles.
You can install “Flood It” by clicking the install button on the web site or manually using this command:
flatpak install flathub io.github.tfuxu.floodit
In the Miscellaneous section we have Dosage. Easily manage track medicinal treatments with Dosage: notifications, history, multiple doses, flexible frequency, customization, stock monitoring, and duration control.
Features:
You can install “Dosage” by clicking the install button on the web site or manually using this command:
flatpak install flathub io.github.diegopvlk.Dosage
In the Creativity section we have Bambu Studio. Bambu Studio is a cutting-edge, feature-rich slicing software for creating cross section slices for 3D printing. It contains project-based workflows, systematically optimized slicing algorithms, and an easy-to-use graphical interface, bringing users an incredibly smooth 3D printing experience.
You can install “Bambo Studio” by clicking the install button on the web site or manually using this command:
flatpak install flathub com.bambulab.BambuStudio
admin )
on 2024-11-01 10:00:00 UTC
This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.
Week: 28th October – 1st November 2024
The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issues
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
The post Infra and RelEng Update – Week 44 appeared first on Fedora Community Blog.
We will be adding disk space to pagure.io. There will be a short outage to do this.
admin )
on 2024-10-31 08:00:00 UTC
Fedora Silverblue is an operating system for your desktop built on Fedora Linux. It’s excellent for daily use, development, and container-based workflows. It offers numerous advantages such as being able to roll back in case of any problems. If you want to update or rebase to Fedora Linux 41 on your Fedora Silverblue system, this article tells you how. It not only shows you what to do, but also how to revert things if something unforeseen happens.
Prior to actually doing the rebase to Fedora Linux 41, you should apply any pending updates. Enter the following in the terminal:
$ rpm-ostree update
or install updates through GNOME Software and reboot.
rpm-ostree is the underlying atomic technology that all the Fedora Atomic Desktops use. The techniques described here for Silverblue will apply to all of them with proper modifications for the appropriate desktop.
GNOME Software shows you that there is new version of Fedora Linux available on the Updates screen.
First thing to do is download the new image, so select the Download button. This will take some time. When it is done you will see that the update is ready to install.
Select the Restart & Upgrade button. This step will take only a few moments and the computer will restart when the update is completed. After the restart you will end up in a new and shiny release of Fedora Linux 41. Easy, isn’t it?
If you prefer to do everything in a terminal, then this part of the guide is for you.
Rebasing to Fedora Linux 41 using the terminal is easy. First, check if the 41 branch is available:
$ ostree remote refs fedora
You should see the following in the output:
fedora:fedora/41/x86_64/silverblue
If you want to pin the current deployment (meaning that this deployment will stay as an option in GRUB until you remove it), you can do this by running this command:
# 0 is entry position in rpm-ostree status $ sudo ostree admin pin 0
To remove the pinned deployment use the following command:
# 2 is entry position in rpm-ostree status $ sudo ostree admin pin --unpin 2
Next, rebase your system to the Fedora Linux 41 branch.
$ rpm-ostree rebase fedora:fedora/41/x86_64/silverblue
Finally, the last thing to do is restart your computer and boot to Fedora Linux 41.
If anything bad happens (for instance, if you can’t boot to Fedora Linux 41 at all) it’s easy to go back. At boot time, pick the entry in the GRUB menu for the version prior to Fedora Linux 41 and your system will start in that previous version rather than Fedora Linux 41. If you don’t see the GRUB menu, try to press ESC during boot. To make the change to the previous version permanent, use the following command:
$ rpm-ostree rollback
That’s it. Now you know how to rebase Fedora Silverblue to Fedora Linux 41 and roll back. So why not do it today?
Because there are similar questions in comments for each blog about rebasing to newer version of Silverblue I will try to answer them in this section.
Question: Can I skip versions during rebase of Fedora? For example from Fedora 38 Silverblue to Fedora 41 Silverblue?
Answer: Although it could be sometimes possible to skip versions during rebase, it is not recommended. You should always update to one version above (38->39->40 for example) to avoid unnecessary errors.
Question: I have rpm-fusion layered and I get errors during rebase. How should I do the rebase?
Answer: If you have rpm-fusion layered on your Silverblue installation, you should do the following before rebase:
$ rpm-ostree update --uninstall rpmfusion-free-release --uninstall rpmfusion-nonfree-release --install rpmfusion-free-release --install rpmfusion-nonfree-release
After doing this you can follow the guide in this blog post.
Question: Could this guide be used for other ostree editions (Fedora Atomic Desktops) as well like Kinoite, Sericea (Sway Atomic), Onyx (Budgie Atomic),…?
Yes, you can follow the Rebasing using the terminal part of this guide for every Fedora Atomic Desktop. Just use the corresponding branch. For example, for Kinoite use fedora:fedora/41/x86_64/kinoite
fale )
on 2024-10-31 00:00:00 UTC
czanik )
on 2024-10-30 11:38:47 UTC
Recently, someone suggested I should check out Alpine Linux and prepare a syslog-ng container image based on it. While not supported by the syslog-ng project, an Alpine-based syslog-ng container image already exist as part of the Linuxserver project.
Read more at https://www.syslog-ng.com/community/b/blog/posts/a-syslog-ng-container-image-based-on-alpine-linux
admin )
on 2024-10-30 08:00:00 UTC
Fedora test days are events where anyone can help make certain that changes in Fedora work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed to Fedora before, this is a perfect way to get started.
During these test days, from Friday 01 November through Friday 08 November, the focus will be on testing the changes that will be coming in Fedora 41 as we move ahead with Podman 5.3. This is an opportunity for anyone to learn and interact with the Podman Community and container tools in general.
Podman is a daemon-less, open source, Linux native tool designed to make it easy to find, run, build, share and deploy applications using Open Containers Initiative (OCI) Containers and Container Images. It provides a command line interface (CLI) familiar to anyone who has used the Docker Container Engine. As part of a recent discussion, the Rawhide Test Day efforts, and Podman Container Engine Team’s collaborative efforts, we will hold test days for this minor Podman Release.
The wiki page helps the testers know and understand the scope of the test days. The Test day app helps the testers submit the results once they have tried the test cases.
A test day/week is an event where anyone can help make sure changes in Fedora Linux work well in an upcoming release of specific software. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed before, this is a perfect way to get started.
To contribute, you only need to be able to download test materials (which include some large files) and then read and follow directions step by step.
Detailed information about all the test days is available on the wiki page mentioned above. If you’re available on or around the days of the events, please do some testing and report your results. All the test day pages receive some final touches which complete about 24 hrs before the test day begins. We urge you to be patient about resources that are, in most cases, uploaded hours before the test day starts.
Come and test with us to make Fedora Linux even better!
Recently I posted about two of my Power t-shirts. Many people responded. Some wanted to get one of the t-shirts from me, others asked me what else do I have. I cannot give you the t-shirts, but I can show you a few more :-) I must admit that only one of them has Power printed on it, but the other two are also Power-related.
The oldest t-shirt is from Genesi. They had various Power machines, and I worked on Linux support of these systems. The first one was the Pegasos, which was a quite capable workstation. It was faster with a lot lower power consumption than x86 systems of the time. The other one was more embedded category, the EFIKA. I used it for measurement automation.
The next t-shirt only mentions nVidia. However, for a couple of years Summit was the fastest supercomputer on Earth, utilizing 9216 POWER9 22-core CPUs and 27648 nVidia GPUs. Even six years later it is the 9th fastest supercomputer.
Finally a “real” Power t-shirt by the OpenPOWER Foundation: “OpenPOWER ready”. It is a program by the foundation, collecting both hardware and software ready to be used with OpenPOWER systems: OpenPOWER Ready Mark.
I proudly wear any of these t-shirts as they remind me about important events in POWER history. However, recently I try to wear them less, as I do not know how many more washes they can survive.
PS: no, I do not want to sell them either. Oh, well, probably for a price no sane person wants to pay ;-) Or, if you do not mind something recent, Power 10 t-shirts are available at https://logostore-globalid.us/product/428389
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:
Plasma 6.2 features numerous bug fixes and additional features to continue building on the modern foundation of Plasma 6:
The Fedora Project and KDE have both worked to support ARM-based devices like Raspberry Pi and Apple Silicon with high-quality experiences. Beginning with Fedora Linux 41, the KDE Spin for AArch64 will now be “release-blocking”. This means that showstopper bugs impacting the KDE experience on these devices can now qualify as blockers for the overall release, helping ensure that projects such as Fedora Asahi Remix (for Apple Silicon) get the best possible support.
Please note that live ISOs for KDE on AArch64 are not yet release-blocking, and will be coming in a future release
Built on the foundations of the Plasma Desktop, KDE Plasma Mobile brings its flexibility to devices with a mobile form factor. Although it was originally geared towards phones, the touch-friendly interface works very well on tablets and 2-in-1 laptops, and enables users with an even broader range of devices to join the Fedora community!
This experience will be available in both the traditional distribution format, as the Fedora KDE Plasma Mobile Spin, and in an Atomic Desktop bootable container image, as Kinoite Mobile.
Please note that installation ISOs have not yet been published for Kinoite Mobile on this cycle, but are coming soon!
Some of the key updates occurring in the core components of Fedora 41, which specifically impact the KDE Spin, include:
The Fedora Project and the KDE Community hope that you’ll find Fedora KDE 41 to be an easy-to-use, reliable and powerful desktop operating system. When you’re ready to check it out, click here for download links and verification instructions.
If you use and enjoy Fedora KDE, consider getting involved in the Fedora Project, the KDE Community, the Fedora KDE Special Interest Group, or all of the above!
I’m happy to once again announce an early release of Fedora Linux 41. Every cycle, our Quality team carefully validates candidate builds against our release criteria, and this time around, we felt confident that we were ready at our early target date. Thank you and congratulations to everyone in Fedora who worked so hard to make this possible, and to all of our upstream projects — and to everyone who helps build a better world by engaging with community-built free and open source software.
What do we have in store for you this time around? A ton of updates to thousands of packages, ranging from tiny patches to big new features. Read the highlights below to find out more. Or, just jump right in!
If you have an existing system, Upgrading Fedora to a New Release is easy, and in most cases not much more of a process than rebooting for regular updates (except you’ll have more time to go get some coffee).
If you’re new to Fedora Linux (welcome!) or just want to start fresh, download the install media for our flagship Editions (Workstation, Cloud, Server, CoreOS, IoT), for one of our Atomic Desktops (including Silverblue and Kinoite), or for alternate desktop options (like KDE Plasma, Xfce, or the new “Miracle” spin).
Fedora Linux 41 defaults to a new major release of the command-line package management tool DNF. This version is faster, smaller and requires fewer supporting packages. This eliminates the need for “microdnf” for containers and memory-constrained systems — now, the same DNF can be used across containers, servers, desktops and devices.
Fedora Workstation 41 is based on GNOME 47. Read What’s New in Fedora Workstation 41? for details. Notably for command-line users, we’ve changed the default terminal to Ptyxis. It’s more lightweight, but has some nice new features as well. (GNOME Terminal is still there if you need some of the flexibility it offers.)
Fedora KDE Plasma Desktop ships with the latest KDE 6.2 release. See What’s New in Fedora KDE 41? for more. We also have a new Spin featuring KDE Plasma Mobile.
If you’re interested in trying something new, take a look at Fedora Miracle! Miracle is a new desktop environment built on Mir and Wayland. It features tiling window management and flashy graphics and smooth window animations.
We’re shipping image-based Fedora variants (such as Atomic Desktops, CoreOS and Fedora IoT) with a new tool called “bootc”. This is the successor to rpm-ostree, building on those ideas in a more flexible way — and letting you use container patterns to define your personal flavor of Fedora. (Shout out to our friends over at Universal Blue, a Fedora downstream project which pioneered this approach!)
If you’re eager to try this, it’s easy to switch from rpm-ostree to bootc. For example, for Fedora IoT, run the following command:
sudo bootc switch quay.io/fedora/fedora-iot
Soon, you’ll be able to use DNF 5 to seamlessly manage locally-installed packages, instead of needing to call rpm-ostree or bootc directly. (This is work in progress!)
Image-mode systems also now benefit from bootupd, which allows users to apply bootloader updates more easily — for example, if there is an update to the Secure Boot database.
Although we don’t ship proprietary software, we want people to actually be able to use the hardware they have, so we worked to make it easy to install the proprietary drivers from third-party repositories. However, as more and more systems are shipping with Secure Boot enabled, we temporarily removed that option. Now it’s back. When you install the driver, GNOME Software will create a Machine Owner Key which you can manually enable.
This is exciting! The cameras shipping in new laptops use an interface called “MIPI”, which expects a lot more from the operating system. Previously, these were a pain to get working. Now we have integrated support for Intel IPU6 attached MIPI cameras. We’re also shipping Firefox with PipeWire for video enabled by default. The new cameras need this — and as an added bonus, you get a nice clear indicator in the GNOME top bar when your camera is on.
There are several important release-day bugfix and security updates available today as well. If you upgrade from an earlier Fedora Linux release, you’ll get them as part of that. For new installations, please make sure to check for and apply updates as soon as possible.
If you run into a problem, visit our Ask Fedora user support forum. This includes a category where we collect common issues and solutions or work-arounds.
Drop by our “virtual watercooler” on Fedora Discussion and join a conversation, share something interesting, and introduce yourself. We’re always glad to see new people!
Fedora Workstation 41 is the latest release of one of the leading providers of free, open source software, The Fedora Project. This article describes some of the user-facing changes in the newest version of Fedora Workstation. Upgrade today from the official website, or upgrade your existing install using GNOME Software or through the terminal with dnf system-upgrade.
In Fedora 41 workstation, you can enjoy the latest features the GNOME software release has to offer, plus benefit from an array of system enhancements! Check out the GNOME 47 release notes for more details.
One of the biggest features to land in GNOME 47, and Fedora Workstation 41, is the option to customize the standard blue accent color of GNOME interfaces. You can now choose from an array of vibrant colors, and customizing couldn’t be simpler – just select a color from the Appearance setting, and enjoy a uniquely-your desktop!
This added support means user who have lower resolution screens will have a better experience as icons will be optimized and scaled for easier interaction and better visibility on smaller screens.
In GNOME 47, the dialogue windows have a new style. This is intended to enhance usability across many screen sizes. This benefits everyone, but especially users who work on compact laptops and mobiles, and this upgrade means the dialogues work more effectively and they can adapt seamlessly to different environments. For added fun, try it out with custom accent colors!
In Fedora Workstation 41, we have added integrated support into Fedora Linux for Intel IPU6 attached MIPI cameras using the IPU6 CSI-receiver together with libcamwera’s 0.3 software ISP support in Firefox through PipeWire. This means a much better experience for users with newer camera models, and users will be able to see the camera icon in the top bar in GNOME if and when your camera is on.
The default input method for Traditional Chinese has changed to ibus-chewing in Fedora Workstation 41. This change makes Fedora Linux more friendly to users as ibus-chewing is maintained by native speakers and the upstream is active. Much less reliance on Google Translate when reporting issues! It even has multi dictionary so users can load domain specific dictionaries.
Returning to Fedora Workstation in Fedora Linux 41 is support for installing Nvidia drivers with secureboot. By using mokutil, users can install the drivers, create a key with mokutil to self-sign the drivers, and provide a password for the key. On the next reboot the user is presented with the mokutil interface to enroll the key. For a how-to on using mokutil, please refer to the docs page. With this support now added, installation of Nvidia drivers on Fedora Linux 41 is now more accessible than ever!
Ptyxis is a terminal for GNOME with first-class support for containers, and works really well for Flatpaks as this is the intended distribution mechanism. This is now the default terminal app in GNOME 47 and Fedora Workstation 41 and brings features such as terminal inspector to help you debug issues when writing applications for the terminal, native support for light/dark mode and user-customizable keyboard shortcuts.
admin )
on 2024-10-28 08:00:00 UTC
Flock to Fedora 2024, held in Rochester, New York from August 7th to 10th, soared to new heights, bringing together Fedora contributors and enthusiasts for four days of immersive learning, dynamic collaboration, and vibrant community building. The event seamlessly blended in-person interactions with live stream and recorded sessions via YouTube for the first two days, ensuring accessibility for a wider audience. Using Matrix Chat for seamless communication and a well-structured online schedule, Flock 2024 successfully fulfilled its mission of uniting the Fedora community, fostering connections, and sparking a wave of innovation.
The primary target audience was Fedora contributors, encompassing developers, packagers, designers, documentation writers, and anyone actively involved in the Fedora Project. The event also welcomed newcomers and those curious about Fedora and open source.
Rochester welcomed a diverse and passionate group of attendees, including, but not limited to:
Flock to Fedora 2024 was a success, showcasing the strength and vibrancy of the Fedora community. We are already looking forward to Flock to Fedora 2025! To stay informed about future events and opportunities to get involved, visit the Fedora Project website, join the Fedora Matrix room, and follow us on social media!
We extend our deepest gratitude to all our sponsors, whose generous support made Flock to Fedora 2024 possible. Your commitment to open source and the Fedora community is invaluable.
Edited by Adrian Edwards and Justin W. Flory
The post Looking back at Flock to Fedora 2024 appeared first on Fedora Community Blog.
admin )
on 2024-10-25 10:00:00 UTC
This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.
Week: 21st October – 25th October 2024
The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issues
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
The post Infra and RelEng Update – Week 43 appeared first on Fedora Community Blog.
This post is a brief summary of the team’s highlights over the course of the second quarter of 2024 (April to June). These highlights include:
These highlights will be summarised below.
https://gitlab.com/fedora/dei/home/-/issues/19 & https://gitlab.com/fedora/dei/week-of-diversity
Fedora Week of Diversity took place June 17-22, 2024. This week is the successor to Fedora Women’s Day, originally started in 2016 as a celebration of the diverse people who make up our Fedora community.
From inspiring interviews to engaging virtual sessions hosted on Matrix, this year’s Fedora Week of Diversity showcased the strength and spirit of the community. Attendees registered for the event through Pretix, and session recordings were made available on YouTube for wider access.
You can find out more on the 2024 recap blog post of the event by Oluwatosin Olatunji.
https://gitlab.com/fedora/dei/home/-/issues/44
For this year’s Flock, the team planned a half-day hackfest. This session was designed to welcome newcomers, provide insight into the DEI team’s ongoing efforts, and outline our plans for the future.
The agenda for the session included:
Goals of the hackfest were:
Flock was held from Wednesday, August 7th to Saturday, August 10th at the Hyatt Regency Rochester in Rochester, New York, USA. You will have to wait for our Q3 report to see how it went!
https://gitlab.com/fedora/dei/home/-/issues/25
Planning took place for the half-day event focused on mentoring best practices. This year’s Mentor Summit aimed to focus on workshops and sessions to promote mentorship best practices and to connect mentors and mentees across the Fedora community.
FMS was held together with Flock and took place on Saturday, August 10th. You will have to wait for our Q3 report to see how it went!
https://gitlab.com/fedora/dei/home/-/issues/2
Given the influx of new team members the last few months, the team decided it would be good to standardize how we onboard new members. Two changes were made:
If you would like to get involved, you can check out our updated process here.
https://gitlab.com/fedora/dei/home/-/issues/30
A repository was created for the team to store pictures, videos and slides from DEI events. This was created to help us with future content creation for the team.
As mentioned above, you can look forward to summaries of how the DEI Hackfest and the Fedora Mentor Summit went.
Want to get involved? Join the DEI Team Matrix chat room (#dei:fedoraproject.org) and follow the Fedora Discussion tag. We meet twice monthly. Our next meeting can be found on the Fedora Calendar.
The post Fedora DEI Team 2024 Q2 Report appeared first on Fedora Community Blog.
Release Candidate versions are available in the testing repository for Fedora and Enterprise Linux (RHEL / CentOS / Alma / Rocky and other clones) to allow more people to test them. They are available as Software Collections, for a parallel installation, the perfect solution for such tests, and also as base packages.
RPMs of PHP version 8.3.13RC1 are available
RPMs of PHP version 8.2.25RC1 are available
The packages are available for x86_64 and aarch64.
PHP version 8.1 is now in security mode only, so no more RC will be released.
Installation: follow the wizard instructions.
Announcements:
Parallel installation of version 8.3 as Software Collection:
yum --enablerepo=remi-test install php83
Parallel installation of version 8.2 as Software Collection:
yum --enablerepo=remi-test install php82
Update of system version 8.3:
dnf module switch-to php:remi-8.3 dnf --enablerepo=remi-modular-test update php\*
Update of system version 8.2:
dnf module switch-to php:remi-8.2 dnf --enablerepo=remi-modular-test update php\*
Notice:
Software Collections (php82, php83)
Base packages (php)
RPMs of PHP version 8.3.13 are available in the remi-modular repository for Fedora ≥ 39 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).
RPMs of PHP version 8.2.25 are available in the remi-modular repository for Fedora ≥ 39 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).
The packages are available for x86_64 and aarch64.
There is no security fix this month, so no update for version 8.1.30.
PHP version 8.0 has reached its end of life and is no longer maintained by the PHP project.
These versions are also available as Software Collections in the remi-safe repository.
Version announcements:
Installation: use the Configuration Wizard and choose your version and installation mode.
Replacement of default PHP by version 8.3 installation (simplest):
dnf module switch-to php:remi-8.3/common
Parallel installation of version 8.3 as Software Collection
yum install php83
Replacement of default PHP by version 8.2 installation (simplest):
dnf module switch-to php:remi-8.2/common
Parallel installation of version 8.2 as Software Collection
yum install php82
And soon in the official updates:
To be noticed :
Information:
Base packages (php)
Software Collections (php81 / php82 / php83)
czanik )
on 2024-10-24 09:06:01 UTC
Recently I was asked the same question both at my workplace and at EuroBSDCon, the conference where I was presenting: where do you talk next? I had no definite answer. Of course, I am looking forward to the FOSDEM CfP, but I am also looking for new conferences to present syslog-ng and sudo. Do you have any recommendations?
You can read the rest of my blog at https://www.syslog-ng.com/community/b/blog/posts/where-should-i-present-syslog-ng-and-sudo
syslog-ng logo
Sudo logo
admin )
on 2024-10-24 08:00:00 UTC
The Fedora Council is considering a change to our policy for promotion of a Fedora deliverable to “Edition” status. Please read that entire document for context before commenting.
This change is being made to reflect actual practice. For example, there is clear overlap between the use-cases and potential user-bases for the current Server, Cloud, and CoreOS Editions, but each takes a different approach. We are currently considering adding an exception for a KDE Desktop Edition, which would overlap with Fedora Workstation.
Currently part of the policy currently reads in a way that prevents this exception from being possible:
A Fedora Edition:
- addresses a distinct, relevant, and broad use-case or user-base that a Fedora Edition is not currently serving;
- is a long term investment for the Fedora Project; and
- is consistent with all of Fedora’s Four Foundations.
We propose an additional line:
The Council may make exceptions to the “distinct” rule when we determine that doing so best fits the Project’s Mission and Vision.
This topic is open for community discussion, following our Policy Change Policy. After two weeks, the Council will vote in a new ticket, and if approved, the policy will be updated.
Approval of this change would not automatically mean the approval of a KDE Desktop Edition, but would allow that possibility.
The post Proposed change to the Fedora Council policy for Edition promotion appeared first on Fedora Community Blog.
Our team has put a lot of effort into the possibility of building modules in Copr. This feature went through many iterations and rewrites from scratch as the concepts, requirements, and goals of Fedora Modularity kept changing. This will be my last article about this topic because we are planning to drop Modularity and all of its functionality from Copr. The only exceptions are Module hotfixes and module dependencies, which are staying for good (until they are supported by Mock and DNF).
The Fedora Modularity project never really took off, and building modules in Copr even less so. We’ve had only 14 builds in the last two years. It’s not feasible to maintain the code for so few users. Modularity has also been retired since Fedora 39 and will die with RHEL 9.
Additionally, one of our larger goals for the upcoming years is to start using Pulp as a storage for all Copr build results. This requires rewriting several parts of the backend code. Factoring in reimplementation for module builds would result in many development hours wasted for very little benefit. All projects with modules will remain in the current storage until the Modularity is finally dropped.
In the ideal world, we would keep the feature available as long as RHEL 9 is supported, but we cannot wait until 2032.
It was me who introduced all the Modularity code into Copr, so it should also be me who decommissions it. Feel free to ping me directly if you have any questions or concerns, but you are also welcome to reach out on the Copr Matrix channel, mailing list, or in the form of GitHub issues. In the meantime, I will contact everybody who submitted a module build in Copr in the past two years and make sure they don’t rely on this feature.
admin )
on 2024-10-22 08:00:00 UTC
With the transition of the applications from Fedmsg to Fedora Messaging inching towards completion, today we want to introduce a new service, Webhook To Fedora Messaging. Webhook To Fedora Messaging has been researched and developed by the Fedora Infrastructure team members with the company of an Outreachy mentee over the last quarter to communicate with services using webhooks.
Webhook To Fedora Messaging takes webhook events from services and translates them into semantic messages to be sent over on the Fedora Messaging bus, to which every Fedora Project application can listen and act for automation. Currently, the project supports services like GitHub but going forward we plan on implementing support for services like Discourse, GitLab, Forgejo etc.
As this service was designed to be the successor to the existing Github2Fedmsg service, we are also announcing that the service is now deprecated and users are encouraged to migrate to the newer service. If you are an existing user of the Github2Fedmsg service, please open a private ticket in the fedora-infra/w2fm-registration repository using the template named “Github2Fedmsg Migration Request”.
Additionally, as GitHub allows for managing webhooks at an organizational level, users migrating from the GitHub2Fedmsg service can explore the functionality by visiting the page https://github.com/organizations//settings/hooks. Once the changes have been made by the owner of the GitHub organization, the activities from all repositories can be conveniently relayed on the Fedora Messaging bus.
The post Announcing Webhook To Fedora Messaging appeared first on Fedora Community Blog.
admin )
on 2024-10-21 17:07:06 UTC
Copr is a build-system for anyone in the Fedora community. It hosts thousands of projects for various purposes and audiences. Some of them should never be installed by anyone, some are already being transitioned to the official Fedora Linux repositories, and the rest are somewhere in between. Copr gives you the opportunity to install 3rd party software that is not available in Fedora Linux repositories, try nightly versions of your dependencies, use patched builds of your favourite tools to support some non-standard use-cases, and just experiment freely.
This article takes a closer look at interesting projects that recently landed in Copr.
If you don’t know how to enable a repository or if you are concerned about whether is it safe to use Copr, please consult the project documentation.
Hyprland is a beautiful Wayland compositor for Linux, offering advanced window management, eye-candy animations, and high customizability. It gives users fine control over their desktop environment, making it perfect for those who value both aesthetics and functionality.
The repo currently provides Hyprland and many more packages needed for your setup like ags or swww for Fedora 39, 40, 41, and Fedora Rawhide. To install it, use these commands:
sudo dnf copr enable solopasha/hyprland
sudo dnf install hyprland
Improve your security and privacy by blocking ads, tracking, and malware domains with hBlock. This POSIX-compliant shell script compiles lists of such domains from multiple sources and creates a hosts file to block connections to them. You just need to use the following command:
hblock
This will generate an /etc/hosts file with the blocked domains. Keep in mind that hBlock replaces your system’s existing hosts file by default, so it’s a good idea to back it up before running the script.
The repo currently provides hblock for Fedora 39, 40, 41, and Fedora Rawhide. To install it, use these commands:
sudo dnf copr enable pesader/hblock
sudo dnf install hblock
Ungoogled Chromium is a privacy-enhanced version of the Chromium browser, designed to remove all Google services dependencies and tracking. It offers the same speed and functionality as regular Chromium but without the built-in connections to Google. This makes it ideal for users who want more control over their data and a more private browsing experience, while still enjoying the benefits of an open-source, lightweight browser.
The repo currently provides ungoogled-chromium for Fedora 39, 40, 41, and Fedora Rawhide. To install it, use these commands:
sudo dnf copr enable wojnilowicz/ungoogled-chromium
sudo dnf install ungoogled-chromium
Floorp is a privacy-focused web browser based on Firefox, designed to enhance user security and reduce tracking. It removes telemetry and includes built-in tools for blocking ads and trackers, providing a cleaner browsing experience. With its user-friendly interface, Floorp is an excellent choice for those looking to protect their online privacy.
The repo currently provides floorp for Fedora 39, 40, 41, and Fedora Rawhide. To install it, use these commands:
sudo dnf copr enable sneexy/floorp
sudo dnf install floorp