Frequently Asked Questions (FAQ)
Fedora Sericea comes from Terminalia Sericea and has been chosen due to the many connections with this project:
Sericea starts with “S”, like Sway.
Terminalia Sericea is a tree. So is ostree.
Terminalia Sericea is also known as Silverleaf. Silverleaf was one of the top contenders for the project name of what later became Fedora Silverblue.
If you stare at a Terminalia Sericea for a while, you’ll eventually start noticing similarities with the Sway logo.
What is Fedora Sericea’s relationship with Fedora Silverblue, Fedora Kinoite, Fedora IoT and Fedora CoreOS?
Fedora Sericea uses the same core technology as Fedora Silverblue, Kinoite, Fedora IoT and Fedora CoreOS. However, Fedora Sericea is specifically focused on workstation/desktop use cases with the Sway compositor.
The proprietary Nvidia driver is not officially supported. It may work, but we are unable to provide any help with the configuration or resolve any issues. Check the Nvidia section of the troubleshooting guide if you absolutely have to use it.
The open-source driver (Nouveau) should work fine in general, but currently lacks support for the most recent generations of the Nvidia hardware.
The initial support for Ampere (30xx) GPU series is expected to appear in kernel 6.2/mesa 23.0 and hopefully will be ready by Fedora 38 release. There are no estimations for Ada Lovelace (40xx) GPU series support.
|Lack of support in Nouveau also means that laptops with discrete Ampere (or later) GPUs may fail to use external monitors, as the corresponding ports are routed through the Nvidia GPU.|
Firefox is included in the OS image for now (see issue#288 for progress on moving to Flatpak by default).
Until that changes, getting it to play videos works the same way as it does for the regular Fedora Sway Spin: find a package with the needed codecs, and install it.
The one difference is that you use
rpm-ostree install instead of
An alternative solution is to install Firefox from Flathub.
/etc is not part of the immutable OS image, so you can just copy files into
/etc/NetworkManager/system-connections (or let NetworkManager store them there when you recreate your connections).
/etc/pki need to be handled similarly.
You can install most IDE directly in a toolbox where you can also install all the developments tools from the Fedora repositories.
To be able to launch them directly from menus, you can copy the
.desktop file for the IDE from the toolbox to your home directory in
You should then update the
Exec line in the
.desktop file to prepend
toolbox run to start it from the toolbox.
You can also use the IDEs packaged as Flatpaks from Flathub.
If you want to compare the booted deployment with the pending deployment (or rollback deployment), simply issue:
$ rpm-ostree db diff
You can also see the RPM changelog by adding the
-coption like so:
rpm-ostree db diff -c
If you want to see which packages were updated between two specific commits:
find out which two commits you want to compare by issuing:
$ ostree log <ref>
you can now compare the two commits by issuing:
$ rpm-ostree db diff <commit x> <commit y>
At this point in time, there is no
rpm package search function built into
However, you can use
toolbox with the following command:
$ toolbox run dnf search <package>
|The assumption is that you have already created a toolbox matching the version of your Fedora Sericea installation.|
If, for whatever reason, you need to downgrade the kernel, you can do so by following these steps:
For the version you need to downgrade, download
Install the packages downloaded on the previous step by issuing:
$ rpm-ostree override replace <kernel> <kernel-core> <kernel-modules> <kernel-modules-extra>
Reboot the system to apply the changes.
How can I upgrade my system to the next major version (for instance: rawhide or an upcoming Fedora release branch), while keeping my current deployment?
OSTree allows you to pin deployments (pinning ensures that your deployment of choice is kept and not discarded).
Assuming that you want to keep your default deployment, issue the following command:
$ sudo ostree admin pin 0
0here refers to the first deployment listed by
Verify that you have pinned your deployment of choice by issuing:
$ rpm-ostree status
After the deployment is pinned, you can upgrade your system by using the instructions found here.
When you have completed rebasing, reboot the system. The GRUB menu will now present you with both: the previous deployment major version entry (e.g.: "Fedora 37.YYYYMMDD.n") and the new deployment major version entry (e.g.: "Fedora 38.YYYYMMDD.n").
At the moment it is not possible to name (pinned) deployments and their associated GRUB menu entries.
Want to help? Learn how to contribute to Fedora Docs ›