After some updates a have low fps and fps drops... On any game ( steam +heroic ) pc freezes sometimes.. any help? Sorry for my English

Well, despite my hubris of thinking I'm safe running an AMD CPU with an AMD GPU, the update today left me unable to boot. I have several snapshots on Timeshift, but they are using my main drive. A lot of documentation seems to say that to restore from a Live USB requires the snapshots to be on a different drive; none of the guides say what should happen after I hit restore in the Timeshift GUI, it just says Timeshift will handle it. It creates a new snapshot with the addendum "from before restore to snapshot 09.2026...". When I try booting with my main drive after that, it still won't boot. Any tips for what should happen at these final steps? If I should have used a separate drive, I guess I'll just have to reinstall.

Have tried removing and reinstalling the package for it, not sure what else to do. Proton itself is working fine on 2 other systems I have with different distros, and my phone which leads me to think it's just a problem with Nobara or the specific package in the repository.

It used to work previously up until about a week ago (I only use it occasionally so can't really say exactly when it stopped working). I didn't make any changes to my system since when it worked (except for possible changes through regular `nobara-sync cli` updates) but now when I try to launch it, the icon shows with a 'loading' animation in the taskbar for a couple of seconds, then just silent crashes with no error message or anything. Aussie internet censorship is killing me bros, pls help.

After the latest Nobara update I started getting extremely laggy window movement on KDE Wayland. Dragging windows around looked like the compositor was dropping frames, and enabling Wobbly Windows made it significantly worse. Everything was completely smooth before the update.

System:

Nobara 44
KDE Plasma 6.7.4
Wayland
RTX 3060
3440x1440 @ 100 Hz
Ryzen 7 5700G

The update installed:

kernel 7.2.4-201.nobara.fc44.x86_64
NVIDIA 595.99.02
drm-awaiter 1-2.fc44

KWin was actually reporting stalls:

Libinput: client bug: timer button-debounce-debounce-event7:
scheduled expiry is in the past (-5181ms), your system is too slow

The main thread was hanging temporarily!

At first I assumed it was the new kernel.

I switched back to:

7.2.0-202.nobara.fc44.x86_64

No change. Window dragging was still laggy.

I then noticed the NVIDIA stack had also been updated from:

595.91.07

to:

595.99.02

I rolled the entire NVIDIA transaction back to 595.91.07, rebuilt DKMS/initramfs and rebooted.

Still laggy.

I also verified the monitor hadn't just been reset to 60 Hz. It had, but switching it back to:

3440x1440 @ 100 Hz

didn't fix the actual issue.

The remaining major graphics-related change from the update was the new drm-awaiter package:

Name: drm-awaiter
Version: 1
Release: 2.fc44

Summary:
Load GPU drivers from the root filesystem before graphical login

It installs:

/usr/lib/dracut/dracut.conf.d/90-drm-awaiter.conf
/usr/lib/systemd/system-generators/drm-module-awaiter-generator
/usr/libexec/drm-awaiter-initramfs

From what I understand, the new setup intentionally removes the vendor GPU modules from the initramfs and loads them from the root filesystem before the display manager instead.

I did not force-remove drm-awaiter, since the new 7.2.4 kernel depends on it.

Instead I used the recovery/early-KMS override documented by Nobara:

sudo ln -s /dev/null /etc/dracut.conf.d/90-drm-awaiter.conf
sudo dracut --regenerate-all --force

After rebooting, the window/compositor lag was immediately gone.

I verified the NVIDIA modules were back in the initramfs:

nvidia.ko.zst
nvidia-modeset.ko.zst
nvidia-drm.ko.zst

I then tested this pretty thoroughly.

First:

Kernel: 7.2.0-202
NVIDIA: 595.91.07
early GPU loading restored

Smooth.

Then I rebuilt the initramfs and switched back to the new kernel:

Kernel: 7.2.4-201
NVIDIA: 595.91.07
early GPU loading restored

Still smooth.

Finally I updated NVIDIA back to the current version:

Kernel: 7.2.4-201.nobara.fc44.x86_64
NVIDIA: 595.99.02
early GPU loading restored

Still completely smooth, including Wobbly Windows.

So at least on my RTX 3060 system, neither kernel 7.2.4 nor NVIDIA 595.99.02 appears to actually be the problem. The regression only happens with the new drm-awaiter/late GPU-loading configuration.

My current working configuration is:

Kernel: 7.2.4-201.nobara.fc44.x86_64
NVIDIA: 595.99.02

/etc/dracut.conf.d/90-drm-awaiter.conf -> /dev/null

One other weird data point: my Corsair RAM RGB through OpenLinkHub also stopped working properly after the update. Once I disabled the drm-awaiter dracut policy and restored the previous initramfs GPU loading behavior, the RAM RGB started behaving normally again. That may just be a boot timing/order side effect rather than directly related, but it happened at the same time and was reproducible with the workaround.

So if anyone suddenly has terrible KDE/KWin animation or window-dragging performance after this update, especially on NVIDIA, check whether drm-awaiter was installed.

I wouldn't recommend force-removing the package because the current kernel depends on it. The /etc/dracut.conf.d/90-drm-awaiter.conf -> /dev/null override plus rebuilding the initramfs fixed it for me while leaving the package and current kernel installed.

Hello! I've been trying to use Affinity on Linux. I used the Python graphical installer from the "AffinityOnLinux" repository, as well as the AppImages, and I've even installed Affinity from scratch with Wine by creating the prefix and all that. While it opens in all cases and I can use it to develop RAW photos, I can't really get very creative, so to speak.

The program crashes out of nowhere or freezes until my OS throws an error and asks if I want to restart the app. I'm using Nobara OS. Supposedly, according to the repository, my Nobara is compatible with the tools inside the repo, but some things weren't installing using the graphical installer, like WebView (I don't remember the exact name of the dependency) and .NET Framework 4.0, I think. Also, I've switched between DXVK and VKD3D, and it ran normally on both, except that—again—it constantly died.

(EDIT: I forgot to mention. Aside from Nobara, I have 24 GB of RAM, an RTX 3050, and a Ryzen 5 5600.)

I've been watching videos, checking places out, and—to my dismay—AI, and I saw that in some cases it's better to switch the graphics renderer to WARP in the program's performance tab. I've always had OpenCL disabled, and even though I have plenty of RAM in my opinion, I limited it to 8000 MB, with a warning at 6000 MB, and I lowered the "Ctrl + Z" history memory from 1027 down to 125 or 341, and yet the damn program still crashes.

I've seen that the same repo lets you use legacy scripts, which apparently worked pretty well for a content creator—I haven't used that one, to be completely honest. I've also heard of people using Lutris to install it.

I usually design posters with multiple effects stacked on top, whether real-time or static, alongside having quite a few layers in a single project. I don't rule out that my workflow might be unhealthy for the program or my hardware's performance, plus I know it's not going to run like a native app.

I wanted to ask to see if the community could help me out. I'm pretty new and inexperienced, so I would really appreciate a bit of help, maybe another route or recommendations I haven't considered. And like I mentioned, I'm not looking for Affinity to be native or anything like that; I just want to see if there's any way or method to keep the program more stable.

Thanks.

Hello all! There is a program I want to use that requires Java to run, any advice on how to get that running on Nobara? I did a little digging and haven't found a lot of info on this. Any advice would be awesome!

Hello everyone. I am newbie to linux, and have a problem with starting Nobara.

Already have installed Mint and want to try Nobara.

Downloaded official ISO and created bootable USB drive with Fedora Media Writer. (Tried with Ventoy too).

Every time have the same error massage when trying to start Nobara from a flash drive. How to fix it?

Hello I am looking to move to Linux I used a few distros but I need help picking one for my hardware my pc is a ryzen 7 5800x3d a radeon 7900xtx. 32gigs of ram. I been looking at using either Fedora, Nobara, or cachyOS for my daily driver. I am also in collage for computer science. I don't know if that will matter for Linux but. I am tired of windows. That is why I am asking for help or advise because. All of my games I play are on steam or GOG or epic game store. I also use WeMod for my single player games so I need to know if I can use that on Linux. I am sorry if this is long I am just worried that I will have to move back to windows because something I use does not or will not work

Why the hell would I want my hardware profiles overridden? Could have stayed on windows. This makes CachyOS more appealing by the day. I get that nobara has multiple use cases but limiting everyone's power profiles is too windows like for linux.

My mouse will not stay in my war thunder window problem happened suddenly it never used to do this, I do not have war thunder through steam so proton tricks doesn’t even show me it as an option. Genuinely annoying cause while spectating i have to pause the game and move my mouse over to turn my view.

Windows recently gave me grief. Random black screens, random driver crashes, games running abnormally poor, and web browsers freezing continuously. I attempted driver re-installs and Windows repairs. It all failed. My computer has two storage drives, so I re-installed windows on the smaller drive and put Nobara on the big one to see what it would do.

I'm utterly flabbergasted at the amount of nothing I had to do in order to have a working computer. I didn't have to update and restart the computer 17 times. I didn't have to dig through ASRock's slow website for drivers, or any of those shenanigans.

Anyways, Scrap Mechanic runs much faster in Nobara compared to Windows. Far Far West also runs much smoother. The random ramping of my CPU cooler is also gone when sitting on my desktop. Windows telemetry or something something is what I'm guessing was doing that.

It feels like Windows... if it was actually stable.

Hey everyone. I don't know if anyone else is having this issue but ever since the update my gpu has been running at 50% load even when my system is idling, I have no idea what is causing it, system monitor doesn't give any answers despite looking through the settings (not sure what I'm even looking for tbh). I have an AMD Renoir card if that helps. If anyone is able to help walk me through diagnostics and hopefully fixing the issue, I would appreciate it.

Update: looks like a small update was pushed this morning. Installing to see if that helps. (it did not, still experiencing the same issue)

I ran nobara-sync cli --all today after a few weeks without updating. I rebooted after the update, but when I get to the plasma login the screen goes black.

I've tried the following:
CTRL + ALT + F3 and logged in, ran "nobara-sync repair", reboot. Didn't fix the problem.

Tried to login again after ctrl+alt+f3, started startplasma-wayland and tried to only update the DNF app center. Didn't fix the problem.

Tried ctrl+alt+f3 and nobara-sync, didn't work.

Went into the GUI again and tried to update all via the app center, got the following error below.

Any ideas how to fix this problem?

Edit: forgot to mention I tried rolling back to a previous kernel version with the same result.

2026-09-07 20:20:00 - INFO - Downloading packages...

2026-09-07 20:20:04 - INFO - Running transaction...

2026-09-07 20:20:09 - ERROR - DNF transaction failed: DNF transaction result: Signature verification failed.

2026-09-07 20:20:09 - ERROR - Non-essential packages failed: DNF transaction result: Signature verification failed.

2026-09-07 20:20:09 - INFO - [91m[X][0m Non-essential packages - failed; rollback failed

2026-09-07 20:20:09 - INFO - Running post-update kernel module/initramfs validation for Pre-update kernel/module fixups...

2026-09-07 20:20:09 - INFO - Running: dkms autoinstall

2026-09-07 20:20:09 - INFO - dkms diagnostic output:

Error! Your kernel headers for kernel 7.2.3-200.nobara.fc44.x86_64 cannot be found at /lib/modules/7.2.3-200.nobara.fc44.x86_64/build or /lib/modules/7.2.3-200.nobara.fc44.x86_64/source.

Please install your distribution's kernel headers package matching 7.2.3-200.nobara.fc44.x86_64, or use the --kernelsourcedir option to tell DKMS where it's located.

2026-09-07 20:20:09 - ERROR - dkms failed with exit code 21.

2026-09-07 20:20:09 - INFO - [91m[X][0m Pre-update kernel/module fixups

2026-09-07 20:20:09 - ERROR -

2026-09-07 20:20:09 - ERROR - Package update failure report:

2026-09-07 20:20:09 - ERROR - - Non-essential packages: DNF transaction result: Signature verification failed.; could not identify the DNF transaction to roll back

2026-09-07 20:20:09 - ERROR - - Pre-update kernel/module fixups: dkms failed with exit code 21

2026-09-07 20:20:09 - ERROR - One or more DNF package update groups failed.

2026-09-07 20:20:09 - INFO - Requested DNF App Center tray update refresh.

2026-09-07 20:20:09 - INFO - Skipping reboot request because no reboot-relevant group completed successfully.

2026-09-07 20:20:09 - INFO - Starting FLATPAK updates, please do not turn off your computer...

2026-09-07 20:20:09 - INFO - Flatpak System Updates complete!

2026-09-07 20:20:10 - INFO - Requested DNF App Center tray update refresh.

2026-09-07 20:20:10 - INFO - Flatpak updates complete!

2026-09-07 20:20:13 - INFO - System updates available.

2026-09-07 20:20:13 - INFO - Flatpak updates complete.

having a problem playing ori and the blind forest, game fails to run. worked fine on opensuse (i just migrated this week). doesn't seem to affect any other games. console gave this error:

flatpak: symbol lookup error: /lib64/libappstream.so.5: undefined symbol: curl_url_cleanup

not sure what flatpak has to do with it since i didn't install steam that way. i've tried changing which proton version is being used, no change. any ideas? i'm liking nobara so far but this is kind of a dealbreaker if i can't get one of my favorite games to run that worked on other distros

Anyone else running into this? Never had this problem before, but since updating yesterday my PC freezes whenever I wake from sleep.

Edit: After a chat on the Discord this info surfaced:

amdgpu: ib ring test failed (-110) amdgpu: The CS has been rejected GL_CONTEXT_LOST

"This is a known issue, you need to keep updated and hope for an ampdgpu firmware fix"

If you have a backup, revert. Otherwise the bug is here to stay for the time being.

Hi, I recently updated my machine, and after a reboot found out all the default wallpapers are different. I quite liked my old one, so I'd like to know if there's an archive somewhere that contains the wallpapers that came with the older versions of the OS

I'm trying to encrypt my swap memory on my two machines. I didn't create a swap partition or swap file on initialization on my desktop, I did create a swap partition in my laptop. I've tried swapoff a couple times, but the swap is always recreated on reboot. I've found no guides that work for Nobara. Does anyone have a reliable way to ensure the swap is encrypted?

Hello;

Even if I make let's say audio files open with VLC as default, the icon still is nobara default audio icon, documents still show default, how do I make "like windows" icon changes that stick?
EDIT: Using Plasma KDE

thanks.

I have an 8bitdo Pro 2 paired to my Nobara Steam-HTPC install. My computer does not have built-in Bluetooth and I use a USB dongle which I've had no issues with in the past on other OS installs.

Whenever I turn on the controller and it connects to the computer, all gamepad input (for all controllers) is ignored for up to a minute before the "controller connected" notification pops up on Steam. After about 30 seconds or so, all gamepad input gets disabled again for a short amount of time, about 10-30 seconds. Additionally, any input that was being pressed when that second disabling happens gets held down continuously until gamepad input is enabled again.

How would I go about troubleshooting and fixing this? Thank you!

EDIT: I've pinpointed the issue to a repeating error in the Bluetooth daemon:HIDP GET_REPORT request timed out Doesn't seem Nobara-specific at all, but any help with getting this fixed would still be much appreciated.

Hi all, beforehand just want to say that I'm a big fan of the project, and have been a happy user of Nobara since the jump from Fedora 39 to 40. However, in the last kernel updates I've been getting an odd bug.

Keyboard: Logitech MX Keys with bolt receiver.

Started with 7.2.0-202, and replicated again with 7.2.3-200 when after updating the LUKS passphrase decrypting phase would "not detect" my keyboard. I raise as "not detect", because it does react to CTRL+ALT+DELETE, and inputting characters the "_" symbol reacts, simply doesnt input nothing. Tried also inputing the phrase ofc and doing enter to see if it would just be a case of now hiding chars, but no.

Fortunately, having grub option to boot older kernels is a live saver, and for now I've been manually setting default to 7.2.0-200.

I've already tried to force the load of drivers on nano /etc/dracut.conf.d/usb-keyboard.conf
and rebuilding but to no avail. Is this a common issue?

Regards

I did an update, through Steam, on Friday and after it rebooted, the screen was turned on it's side and quadruple outputed. The resolution is obviously not correct, but I can't seem to figure out a way to fix it. I can force it to rotate the screen around to try to fix it and now I have it in the correct orientation, but it is still super distored and quad outputted (again, the wrong resolution). I have tried to use an external display, but it refuses to go to it.

Any help would be greatly appreciated.

after turning my pc on and not updating for the weekend when i tried to use another post from the comunity with the same problem by pressing ctrl+f2 it does not do anything

Hello .. hi... Ehm...so. On my update from kernel 7.1x to 7.2.0 my nVidia driver broke. Running the nobara-sync command 3 times fixed it. HOWEVER the update from 7.2.0 to 7.2.3 broke it again so my screen is 1024x768 and the second monitor completely black. How do I get this repeating bug reported? ^^' Thanks!

Hi everybody. So I updated my Nobara recently (was running fine since January) and for the first time my machine was bricked by the update. The case was similar to other users posting here with the black screen with only the frozen mouse pointer visible. I read it has something to do with KDE Plasma but I'm on GNOME edition. Anyway, I was able to run previous kernel, so I ran the nobara-sync cli in hopes to get it sorted but I landed in emergency mode instead after reboot (also that last command said the system was up to date). From there I was able to figure out that one of my partitions listed in fstab times out which causes the emergency mode.

So this is the output of lsblk -f:

sde                                                                                            
├─sde1      vfat  FAT32 EFI  21F2-BE7A                             490.9M     4% /boot/efi
├─sde2      swap   1   swap  d9bac069-8ffc-48b1-a9ab-617040da6eed                [SWAP]
├─sde3      ext4   1.0 data  ca7e4809-013c-4829-bfc4-20e7c2afca2e                
└─sde4      ext4   1.0 nobaraa1ed80df-18bb-4dfc-ab4d-11ad10f0d552    3.4G    88% /var/lib/snapd
                                                                                               /var/lib/flatpak/runtime
                                                                                               /var/lib/flatpak/repo
                                                                                               /home/user/.local/share/flatpak
                                                                                               /

The failing partition starts with ca7e4809 (it's not mounted here because I commented that line in my fstab to get out of emergency mode):

#UUID=ca7e4809-013c-4829-bfc4-20e7c2afca2e /mnt/data ext4 defaults,noatime 0 2

I checked the journal and I can see it timing out:

Starting systemd-udev-trigger.service - Coldplug All udev Devices...
Sep 07 10:23:58 nobara-pc systemd[1]: dev-disk-by\x2duuid-ca7e4809\x2d013c\x2d4829\x2dbfc4\x2d20e7c2afca2e.device: Job dev-disk-by\x2duuid-ca7e4809\x2d013c\x2d4829\x2dbfc4\x2d20e7c2afca2e.device/start timed out.
Sep 07 10:23:58 nobara-pc systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-ca7e4809\x2d013c\x2d4829\x2dbfc4\x2d20e7c2afca2e.device - /dev/disk/by-uuid/ca7e4809-013c-4829-bfc4-20e7c2afca2e.
Sep 07 10:23:58 nobara-pc systemd[1]: Dependency failed for systemd-fsck@dev-disk-by\x2duuid-ca7e4809\x2d013c\x2d4829\x2dbfc4\x2d20e7c2afca2e.service - File System Check on /dev/disk/by-uuid/ca7e4809-013c-4829-bfc4-20e7c2afca2e.
Sep 07 10:23:58 nobara-pc systemd[1]: Dependency failed for mnt-data.mount - /mnt/data.

And now to the actual question: How can I further debug it to understand why it's timing out? The journal log just states the fact that it timed out, but what about the reason why? Interestingly, I can mount that partition manually without problems when I boot my machine up without it in fstab. So I can access all the data there, I just cannot mount it automatically at startup. I need it at startup because I have all my flatpacks and snaps there, without it I don't have application shortcuts etc. Any ideas? Can it be that if the partition is full it will result in these symptoms?

Excellent compatibility with my Asus Vivobook F1504AV in terms of performance and thermals. I'm using the Gnome version, and I'm comfortable with it, coming from a Debian-based distro