People have been reporting multiple related issues regarding Firefox preferences being randomly reset, possibly caused by multiple root cause bugs. Copying from the bug:

• Loss of homepage setting (revert to Fedora Start)
• Loss of bookmarks
• Loss of language or other settings
• Sync of these issues to other devices via Firefox Sync (including lost bookmarks)
• The problem may occur after (some or all) Firefox package updates

WHAT WE KNOW

• This behavior is NOT INTENTIONAL. There is no conspiracy to reset people's settings, nor is Fedora's configuration an intentional attempt to exploit a bug or behavior.
• This behavior is NOT UNIVERSAL. It happens to some people and not others. No maintainer has been able to reproduce it so far, which is why it has not been fixed.
• This behavior affects a MINORITY of users. While it has been reported repeatedly over the years, indicating that the issue is widespread, if it were happening to a significant fraction of Fedora users, the outcry would be orders of magnitude larger and a developer would have been able to reproduce it and fix it by now.
• This behavior is NOT EXPECTED. There is no logical explanation for why it happens or why it could happen. There is no "obvious" solution. It is not even clear that the problem has anything to do with Fedora's default setting overrides, as vanilla Firefox users have reported similar issues over the years. It seems that when it happens to Fedora users, users have a tendency to blame Fedora's preference overrides and complain loudly, but so far there is a lack of solid evidence that all of this behavior is tied to Fedora's preference overrides (other than one very specific issue described below).

WHAT WE NEED FROM YOU

If you are seeing any behavior similar to the above, PLEASE comment with as much detail as possible. Do not assume that anything about your setup will be the same for others. We need details such as:

• Your Fedora version (including spin/edition, etc.) and architecture
• Any important system customizations or changes such as file system or kernel
• Your desktop environment
• Information on all other systems synced with Firefox Sync to the same account, if you use it
• How you update your system (graphical tool, dnf upgrade, dnf upgrade --offline, etc.)
• A detailed walkthrough of what happened exactly when the issue occurred (when you (re)booted your machine(s), when you started or closed the browser(s), whether you clicked through any errors or messages, etc.)
• If it happened after an upgrade, whether your browser was running during the upgrade (and whether it complained or crashed).
• What exactly was lost/reset, and what the intended setting/value was previously.

If the issue happens OFTEN on every browser update, then please back up your browser configuration before each update using this command (you might need to dnf install rsync):

rsync -av --mkpath --exclude=storage ~/.mozilla ~/.config/mozilla ~/firefox-backups/$(date +%Y%m%d%-%H%M%S)

If you experience the issue after the update, run the command again to take another snapshot and comment here. The pre-upgrade and post-upgrade snapshots could be crucial in figuring out what went wrong.

I am personally volunteering to help gather debugging information for this issue. If you are comfortable, I would greatly appreciate it if we could have a real-time chat (over Matrix, Discord, or others) to try various things in order to track down the root cause of the problem.

IT IS IMPORTANT TO CATCH THE ISSUE IN THE ACT. "This used to happen to me but it no longer does / I no longer use Fedora / etc." is sadly a common response from users. Unfortunately, there is nothing developers can do to track down this issue if the person is not actively experiencing it.

IF YOU CAN REPRODUCE THE ISSUE AT WILL (for example, with dnf downgrade firefox and dnf upgrade firefox), then you hold the key to solving this once and for all. Please, please help.

IF YOU LOSE IMPORTANT DATA

If you lose your bookmarks, do not panic. Firefox automatically keeps backups of your bookmarks. Follow these instructions to restore them from an automatic backup:

https://support.mozilla.org/en-US/kb/recover-lost-or-missing-bookmarks

Once you get back your precious bookmarks, please come back and comment on exactly what happened. The more detailed feedback we get on what might cause this issue, the better.

KNOWN BUGS

So far there is ONE identified bug that is connected with system default overrides, but it only explains a very specific subset of the reports:

• When Firefox Sync is used, and
• The user syncs Fedora and non-Fedora systems, and
• The user sets their home page to Firefox Home -or- Fedora Start, then
• The browsers will "fight" over the home page setting, as they disagree on what the "default" is, and Firefox Sync handles this case poorly.

This bug is tracked as Fedora bug 2020436, and also upstream. The solution for this specific case, going forward, is for upstream to toggle a setting (that must be changed on all Firefox builds, not just Fedora's) to make the home page setting "sticky" and not consider the "browser default" value in a special way.

(All reports of this issue have been from users setting the home page to Firefox Home, but it is important to point out that the converse would also be a problem as far as the issue is understood: they would be unable to set Fedora Start as their home page consistently either. The underlying bug is symmetric, it does not "favor" Fedora.)

For those affected, there is a simple workaround: Set your home page to the URL about:home#, with a trailing #. This will avoid the "fighting over defaults" behavior.

This issue does NOT apply to people who:

• Do not use Firefox Sync, or
• Set their home page to anything else, or
• Experience reset of non-pref data like bookmarks

---

After reading the previous thread, I'm honestly really upset at how this has gone on for so long without any ability for maintainers to actually resolve the issue. Us developers NEED your help tracking this down. So far everyone experiencing it has just assumed that it happens all the time to everyone, because it happens to THEM all the time... and nothing has ever been fixed, because nobody with the ability to diagnose and debug it could ever reproduce the problem.

System Specifications:

• Model: Lenovo Legion 5 15IPH11 (Product 83RW)
• CPU: Intel Core Ultra 9 385V / 386H (Panther Lake)
• Panel: EDO OLED (EF25QBA63.E), 2560x1600, 165Hz (Peak 1100 nits)
• Firmware: BIOS T4CN38WW (01/05/2026)
• OS: Fedora 43 / Kernel 6.19.10-200.fc43.x86_64
• Driver: xe (Intel Graphics)

The Issue: Backlight control is non-functional. The panel is locked at 100% duty cycle (maximum luminance). Standard ACPI kernel parameters (acpi_backlight=vendor/native) and i915/xe module parameters fail to trigger any hardware response.

Root Cause (Confirmed via VBT/EDID Analysis): The BIOS Video BIOS Table (VBT) provided by Lenovo is misconfigured for this SKU:

1. Identity Mismatch: VBT reports a legacy panel (ID: 2002) instead of the actual 2025 EDO OLED.
2. Pathing Error: VBT instructs the xe driver to use PCH PWM (analog) controllers.
3. Hardware Requirement: The EDO panel requires DPCD/AUX (digital) pathways via eDP for brightness modulation.

Technical Impact: The kernel correctly updates sysfs values in /sys/class/backlight/intel_backlight/, but since the routing is hardcoded to the wrong controller by the firmware, the physical backlight remains unresponsive.

• GitLab (drm/xe/kernel):https://gitlab.freedesktop.org/drm/xe/kernel/-/work_items/7681
• Bugzilla (Kernel.org):https://bugzilla.kernel.org/show_bug.cgi?id=221301
• Lenovo Forums:https://forums.lenovo.com/t5/Fedora/Technical-Support-Request-Display-Backlight-Control-Issue-on-Linux-Fedora-43/m-p/10026442

Verdict: Avoid Lenovo 83RW models for Linux until a BIOS update fixes the VBT mapping or a kernel-level override is merged.

I would like to announce that Im new to Fedora community.

Started to think about moving to linux as I dont want to upgrade to Win11. Damn the amount of distros and the trouble of choosing, finally decided I have to slap extra SSD to my system and try the distros before deciding which I wanna use or if I just suck it in and stay with Windows.

After testing 4 other distros, a week each, I installed Fedora KDE and been fiddling with it for a week and enjoyed it. Everything just works or is easy to get going, googling helps a lot.

Now the last hiccup for me is file sharing with local network through samba, my gf has windows laptop, LG oled tv and android phones, and ffs I just cannot get everything to work at once. I have followed official fedora guide for it, then troubleshooted it couple times.

So now I decided that I'll ask here if someone could do a small guide for dummies that makes it work.

If I get a good guide and manage to make it work properly I will install fedora 44 to my main drive and remove win10pro completely.

Why oh why the fileshare setup must be so effing hard in linux and possible only through console. All guides have so many commands you must know before you even can share anything. Create new folders and create new users and passwords and this and that and then give 15 other commands to even activate the sharing.

Atleast this was done better in winblows, setting up a home network and file sharing.

I picked up a cheap MacBook Air A1466 recently and wanted to see how far I could push the new bootc workflow on this hardware. While immutable Fedora isn't a new concept, using a container-native image to solve the “MacBook driver hell” definitely feels like the way forward.

Instead of manually layering kmods on every install, I’ve baked the Broadcom Wi-Fi, FaceTimeHD webcam, and thermal fixes directly into the image during the container build.

The whole project is just a Containerfile, so even though it has my personal preferences, it’s trivial to fork and customize the package list or scripts to fit your own needs.

If you're rocking an A1466 and want to try a bootc rebase that “just works” on this hardware, feel free to check out the repo.

Repo: https://github.com/CleoMenezesJr/bootc-fedora-gnome-macbookair

https://preview.redd.it/xvc6356ti1tg1.png?width=1090&format=png&auto=webp&s=c7fd9529bed606d2a136819bef8fd4b10b068d44

I wanted to share the CI/CD pipeline I created in my homelab for building my own personal derivative of Fedora Kinoite with Nvidia drivers and a few package swaps. While I do this on my homelab, it can be done entirely on a single system.

The reason for making this was in part because I simply thought it was cool, but also in part because I did not and do not like the ways the Universal Blue project(s) deviate from upstream Fedora. As an example, while I understand why things like Bazaar exist and are used, I don't like that it's implemented *in lieu of* Discover, regardless of how much better than Discover it may be.

As I have no intentions of uploading anything to Github and operate out of my own private Forgejo server in my homelab, I'll be using Pastebin to share things with you today. If there's a better alternative, I'm all for hearing about them.

The Pipeline

On my homelab I have my desktop and a server running Forgejo. Using a Forgejo Runner, my server automatically runs build jobs nightly to produce new containers provided the following is true:

1. Upstream updated their image since the last build.

2. No errors occurred at build-time.

To make sure the runner can push the resultant OCI image to Forgejo itself you have to create an auth token for the runner to use to push the OCI image.

sudo mkdir -p /root/.config/containers/
sudo podman login --authfile /root/.config/containers/auth.json your.forgejo.local

With that set up, Podman can push to your container registry without you having to authenticate every time. Here's what my build.yml ends up looking like.

The Containerfile

My objective when I started this project for myself was to remove the need to layer packages to get what I wanted out of my atomic installation. More specifically, I wanted to:

1. Add the Nvidia drivers and support services to the image.

2. Swap out toolbox for distrobox which I find to be a better and more flexible utility for the kinds of work I do.

3. Swap out firefox entirely for zen, necessitating a one-shot systemd unit (which we'll get to)

4. Add a bunch of other utilities Fedora doesn't ship by default, such as utilities for my Yubikey, Nextcloud, fonts and codecs, gaming stuff, and the like.

To achieve this I had to break the whole build down into three distinct steps:

- Extract the kernel version of the latest upstream image to build the Nvidia drivers against

- Build the Nvidia drivers against the above kernel version specifically, pulling from Koji directly in case the latest kernel version packages weren't available on Fusion yet

- Assemble the entire thingJohoBlue

The Containerfile could stand to be a lot more optimized than it is, but for the sake of simplicity I separated out steps logically so I could follow along myself during development. In short, the first stage is designed to gather kernel version information which we'll need to properly and reliably build modules against. To make sure we have access to the latest kernel packages at all times, we pull directly from Koji instead of Fusion repos which can sometimes lag behind a little bit (relative to Koji, obviously). We then build the kernel modules against the specific kernel version being shipped in the latest upstream image, and inject them in the third stage, adding in any other software we want at that point.

With this staged approach we can catch any mismatches between what kernel version the Nvidia drivers need to build against, which will simply cause the build to fail and no updated image to be pushed to our registry until the needed package versions align again.

Building Against Fedora Atomic Beta

Taking this a step further, I branched my private repo to add support for Fedora Kinoite 44. I had to add a stage to the build process to support this - I was running into weird TLS errors while trying to build the kernel modules for the Nvidia drivers that does not occur with Fedora 43 images, so I had to work around that in it's own stage. Again, this could be much better optimized, but for the sake of being able to logically read through it easily I separated out several RUN commands for myself.

To make sure both the latest and beta containers built nightly, I modified the build.yml file in the main branch to pull both branches and build against them individually.

The systemd Flatpak One-Shot Service

To support the installation of Flatpaks on an initial installation I added a one-shot systemd unit to automate the installation and then create a stub file to detect if the unit had ever run at any point on the system (which should be false on a new installation).

---

If you're dabbling in Fedora Atomic and want to try building your own images, it's a pretty fun experience seeing it all come together. My laptop and desktop both are always in identical system states and I don't have to worry about updates breaking anything as breakage is mitigated against during build-time. I have my own variants of Fedora IoT as well incorporating and enabling Cockpit without layering and adding FIDO2 support for Yubikey LUKS unlocks. The sky is the limit.

My next project will be learning to assemble the base images completely locally from scratch. To do this I'll need to mirror the upstream packages called for in the build recipies. Once I've successfully done that, my plan is to build those RPMs from source with compiler optimizations, adding a little Gentoo to my Fedora blood, all in the name of some fun and exploration.

Hi all, I booted into my system just to find out that I was not getting any audio. I've had issues similarly to this in the past, but in those cases it was simply my audio devices not being detected, but it was not so now. I can see output being displayed, as shown below. I noticed that ALSA was uninstalled, but installing it did nothing. Pipewire, Pipewire-pulse, and wireplumber are all installed and running, I basically have gone through this entire process and nothing fixed my issue: https://docs.fedoraproject.org/en-US/quick-docs/how-to-troubleshoot-sound-problems/

I have tried searching online but I haven't found anything helpful, so any help would be appreciated

(this is hyprland but I also tried switching back to plasma which didn't help)

Hi! I appreciate any wisdom you kind folk can share that might lead me out of this box of quicksand... I installed KDE Plasma as an experienced techie said it was one of the best for Discord use. However, when I tried to use Brave Browser (Chromium based) to view Amazon Prime, it rather rudely informed me that it only honors Apple or Windows OS for viewing!

So I started trying to create one of these "sandboxes" for Brave to operate it in Windows anonymously. Yikes! I'm so over my head - every set of commands I try to enter in the Konsole gives me yet another error message.

I would be SO relieved if someone posted the full script I have to enter to get firejail installed. This is supposed to be the easiest route (this is "easy"?) to build a sandbox in Fedora KDE Plasma. I went to github and... well, I don't even know how to install something like this. Not the first clue.

Someone throw me a rope, please!

Long time Arch user here, got tired of fiddling with config files every time I wanted to get something working so I decided to move to Fedora, from my point of view they feel like the poster child of wayland/systemd implementation so I bet on that to get a stable working system. I know I might have shot myself in the foot by going 44 since its "beta" but since we aren't that far off from release I figured it was going to be good.

Unfortunately, I have been plagued with issues, notably around stuttering/freezing. If I hover the mouse on top of certain UI elements like buttons and sliders, it will freeze and become unresponsive or if it moves it feels like I am dropping frames, its the worst when I go over elements but it can happen regularly too. Then I have certain flatpaks, telegram just recently, that have insane lag, im talking 15-20fps and I am dropping a lot of frames, this goes away if i force it to go through xwayland. This surprises me because I have used the same flatpaks on this very hardware in a lot of arch flavoured distros, including vanilla without issues under wayland sessions. I was wondering if any of you recognise these issues because I have come up empty handed in my search, most of what I get is from the early transitional era of wayland, feel's like I have gone back to pre-explicit sync days at this point lol.

So, I know the 595 series have been problematic, but if its to that point why does it ship with 44 with no possibility to downgrade to 590? Either way, I will try the KDE flavour on 43, I hope I won't have these issues.

Hello friends.

I am using Fedora 43 KDE Plasma.

Is there a way one can get the latest version for certain software?

For example the kitty terminal is currently at version 0.46.1, but on my system via dnf only the version 0.43.1is available.

Thanks in advance.

Hello, I hope this is okay to post here considering that other posts appear to be praise of Fedora rather than a question about an RPM package or repository as mine is.

Anyways, I was wondering if anyone knows of an accessible and earlier Mono build from before version 4, as I somewhat “need” the framework of those builds in order to accomplish what I want to accomplish in JetBrains Rider. To be clear and in case that someone knows of some alternative, I am trying to mod The Sims 3, and as I have the latest version of Mono installed, JetBrains Rider naturally calls the mscorlib DLL which is not relevant to the framework of The Sims 3.

So, in other words, I need an earlier Mono build for JetBrains Rider to call as I have no way of disabling the mscorlib DLL which is, notably, implicit and which also appears to be unremovable from the code. Interestingly, I have the right mscorlib DLL in my folder, but there doesn’t seem to be a way to force JetBrains Rider to use that DLL instead of the one supplied by Mono.

Any assistance would be very much appreciated!

As per title. I installed Nvidia drivers ver. 560.xx from the RPM fusion guide a month ago.

Cut back to today when I checked Nvidia linux drivers on Nvidia's own website out of curiosity and found that the latest version is 590.xx. I tried modifying the rpm fusion command to update the drivers ("sudo update akmods" something something) but it has shown that the drivers are still at their latest version (560). Am I fine with this? Or should I update the drivers as per Nvidia's website?

Edit: Grammar

Just installed beta Silverblue in Boxes and Firefox (from fedora repo) that comes with it has many expired (about:certificate) certificates like:

Servers:

DigiNotar Root CA expired 2025

Authorities:

Juur-SK expired 2016

ACNLB expired 2023

Actalis Authentication CA G1 expired 2022

TUBITAK UEKAK kok.. expired 2017

LuxTrust Global root expired 2021

And so on (didn't check them all).

Is this normal?

Flatpak version doesn't have those certificates..

I'm currently on Fedora 43 Workstation. I installed Discord flatpak version, I enabled Discord to run on startup but it crashes on system boot.

\"Open Discord on Startup\" is turned ON.

Discord quit unexpectedly

Problem details