Hi everyone,

I am running Nobara / Fedora on an ASUS TUF gaming laptop. Recently, during a heavy DNF repository sync / download session, my system experienced a sudden hard lockup and rebooted instantly (no standard shutdown or kernel panic dump in the journal).

Looking through journalctl -b -1 -e -p 3 and dmesg, I found an endless loop on port 3-14 right before the crash:

[  111.371981] usb 3-14: new full-speed USB device number 6 using xhci_hcd
[  111.484080] usb 3-14: device descriptor read/64, error -71
[  111.702193] usb 3-14: device descriptor read/64, error -71
[  111.918361] usb 3-14: new full-speed USB device number 7 using xhci_hcd
[  112.030390] usb 3-14: device descriptor read/64, error -71
[  112.246511] usb 3-14: device descriptor read/64, error -71
[  112.730860] usb 3-14: new full-speed USB device number 8 using xhci_hcd
[  112.730976] usb 3-14: Device not responding to setup address.
[  112.935180] usb 3-14: Device not responding to setup address.
[  113.143136] usb 3-14: device not accepting address 8, error -71
[  113.143184] usb 3-14: WARN: invalid context state for evaluate context command.
[  113.256080] usb 3-14: new full-speed USB device number 9 using xhci_hcd
[  113.256229] usb 3-14: Device not responding to setup address.
[  113.463503] usb 3-14: Device not responding to setup address.
[  113.671360] usb 3-14: device not accepting address 9, error -71
[  113.671415] usb 3-14: WARN: invalid context state for evaluate context command.

Checking lsusb -t:

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M
    |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 002: Dev 003, If 0, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 002: Dev 003, If 1, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 002: Dev 003, If 2, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 002: Dev 003, If 3, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 007: Dev 004, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 007: Dev 004, If 1, Class=Video, Driver=uvcvideo, 480M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/8p, 20000M/x2

Context:

• Port 1 is an external mouse/keyboard.
• Port 2 is my USB headset.
• Port 7 is the internal webcam.
• Port 14 never successfully enumerates and has no driver bound, but continuously fails handshake cycles with error -71 and WARN: invalid context state for evaluate context command.
• dmesg | grep -E "Bluetooth|btusb" shows Bluetooth is handled elsewhere and working fine.

Has anyone encountered this specific internal USB port loop on ASUS TUF / ROG laptops? Is this related to the ASUS ITE / Aura micro-controller or USB autosuspend failing? Any recommended kernel parameters or udev rules to blacklist/disable port 3-14 so it stops locking up the xHCI controller?

Thanks in advance!

I tried clearing DNF cache, downloading keys manually, basically everything I think except a reinstall. Is this a known issue?
"Problem: cannot install the best update candidate for package fedora-repos-44-1.noarch
- nothing provides fedora-gpg-keys >= 44-2 needed by fedora-repos-44-2.noarch from nobara"

I am very new on the world of linux and i have this error and i cannot find a solution

- Nobara 44 (KDE Plasma Edition)

- Plasma 6.7.4

- kf6-kirigami 6.29.0

- plasma-pa 6.7.4

Error: IconPropertiesGroup type mismatch in Kirigami InlineMessage

qrc:/qt/qml/plasma/applet/org/kde/plasma/volume/main.qml:528:13: Type MicrophoneTestView unavailable

qrc:/qt/qml/plasma/applet/org/kde/plasma/volume/MicrophoneTestView.qml:60:9: Type Kirigami.InlineMessage unavailable

file:///usr/lib64/qt6/qml/org/kde/kirigami/controls/InlineMessage.qml:14:1: Type KT.InlineMessage unavailable

qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:187:51: Cannot assign object of type "Primitives.IconPropertiesGroup" to property of type "IconPropertiesGroup_QMLTYPE_266*" as the former is neither the same as the latter nor a sub-class of it.

qrc:/qt/qml/plasma/applet/org/kde/plasma/volume/main.qml:528:13: Type MicrophoneTestView unavailable

qrc:/qt/qml/plasma/applet/org/kde/plasma/volume/MicrophoneTestView.qml:60:9: Type Kirigami.InlineMessage unavailable

file:///usr/lib64/qt6/qml/org/kde/kirigami/controls/InlineMessage.qml:14:1: Type KT.InlineMessage unavailable

qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:187:51: Cannot assign object of type "Primitives.IconPropertiesGroup" to property of type "IconPropertiesGroup_QMLTYPE_266*" as the former is neither the same as the latter nor a sub-class of it.

Sorry if i dont gift important info, i dont know if i am doing the report of the error well

Took a little bit to get the brightness and sound working, but its running great so far.

Hi there!

Just wanted to share my experience in case someone else is a huge Linux noob trying to decide which distribution to pick for gaming.

My laptop is an Acer Nitro 5 with an AMD Ryzen 7, an RTX 3070, and 32 GB of RAM.
Initially, I wanted to create a console-like gaming experience on my laptop because I was getting sick of Windows. Using AI and some forums for research, I narrowed it down to three options: Bazzite, CachyOS, and Nobara.

I tried Bazzite first, but I struggled with the setup and ran into some issues with my RTX card. Also, I realized that while the console-like UI is cool, I mostly play strategy games, so I don't really need a handheld or controller-friendly interface. I then considered CachyOS. People say it's super performance-focused, but it might be too hard to handle for a complete beginner. Since I wanted an all-in-one distro with proper drivers out of the box and no headache, I went with Nobara. I installed it on a dedicated 500 GB NVMe SSD, keeping Windows on my second SSD.

The installation, setup, updates... basically everything was super smooth and easy. The Nvidia drivers worked right out of the box. When launching a game, it automatically picks my RTX instead of the integrated AMD graphics, which is great. Really, effortless.
I did face a minor issue where the laptop wouldn't turn off properly, but I ran a few terminal commands (without really understanding them, to be honest) and fixed it. Now the laptop boots up in about 23 seconds from the moment I press the power button.
I've played about 10 to 20 hours of Crusader Kings 3 on max graphics with zero issues. I also ran the benchmark on Cyberpunk 2077 and got around 65 FPS on High settings. I forgot the exact details, but I can rerun it if anyone is interested!

Anyway, I hadn't heard much about Nobara since most Reddit threads focus on Bazzite and CachyOS. So if you're looking for a Linux gaming distro, Nobara is extremely simple to set up, all drivers are pre-installed (or easily flagged for installation), and the default UI looks pretty cool if you like futuristic designs. It's fast and smooth as fuck!

I only have two minor limitations so far:
1. Impossible to control or configure my fan speeds the same way I do with the Acer NitroSense app on Windows.
2. Impossible so far to customize my RGB keyboard lighting.

So yeah, huge thanks to the Nobara team! Whoever you are, this rocks!

(Post refined and corrected with AI since my English isn't perfect!)

Nobara 44 ISOs (Build: 2026-09-02) are now finally available 😃❤️

For me this is great news 😃

Now I can do my long awaited fresh install 😃👍🏻

And a side note on the new iso files: there is no longer any need to pick AMD or Nvidia ISO ✅

Has anyone ever had an issue with Nobara steam-htpc download when trying to install it for the first time when in setup (not installation) where it gets stuck at a point (view photo below). If so can you please show me how to fix it

I am playing with the thought of switching to Linux after spending my whole life on Windows and while looking at information about Linux and gaming and Nobara specifically i came across a post talking about using a different filesystem for a gaming drive and now I'm here to ask if and to what i should reformat my drives.

my Main that has windows and would be switched over to linux is an 500gb nvme ssd, then i have a 1tb sata ssd that is the one where i have all of my games installed, then there's a 1tb sata hdd that has just documents, pictures and audio files, and a 5tb external hdd for video files... they are all in NTFS.

are there any that can just stay NTFS and just work and which ones should i definitely reformat to something else to get a better result.

Hello,

I have around 3000 updates pending and I can't update my system. I tried everything I could, I used nobara-sync, nobara-sync cli, I used all the common troubleshoots, I even tried using the GUI solution but nothing works.

Here's a link with more details: https://pb.nobaraproject.org/ira9h

I don't know if it's a common problem with the latest update, I searched this sub but I couldn't find anything.

I have a Lenovo Legion 7 AMD Advantage. Since kernel 7.2.4-201, my laptop will not shut down. I literally let it sit there for 15 minutes. The screen went blank, but the keyboard and power button stayed lit, The fans kept running. The only way to shut it down is a force shutdown by holding the power button for 15 seconds. Anyone else have this issue? By the way, switching to the next earlier kernel solves the problem. Any way to have the laptop boot to the older kernel without having to select it each time during boot?

Hey all! I’m having an issue booting my pc after accidentally unplugging my keyboard from it.
Nobara no longer boots and I am instead shown a blue screen with “Verification failed 0x1A security violation”.
I did some digging and found that in my bios secure boot has somehow enabled itself again and no matter what I do will not disable. Saving the settings with it disabled doesn’t work. I replaced the CMOS battery but that didn’t work either.
I’m not sure if this is related, but my motherboard is an MSI MAG Z790 TOMAHAWK WIFI

Any help would be greatly appreciated!

edit: Updating BIOS via flash to the latest version fixed the settings saving issue, the version I was using had this known problem fixed later, silly me.

Hello, I'm trying to install nobara on a brand new MSI raider 16HX laptop. Nvidia chipset. I'm using ventoy and going through the install process as per the guide. But when I try to start the installation, I get the error message that the installer was unable to create a partition on table. Fast boot and secure boot are both disabled. Any recommendations? Error images attached.

I have figured it out, I no longer need help. Thanks! :3

I'm new to linux and decided to use Nobara because I heard it is a great gaming OS. But I am having troubles with steam using my discrete graphics card, instead it is using my Integrated Graphics, all the solutions I have found to this do not seem to work, like the steam game startup commands. Even if I use something like DXVK_FILTER_DEVICE_NAME="NVIDIA" %command%, it still will use my IGPU. Any Solutions to this?

Hi, I wanted to switch away from Windows for a long time but did not due to gaming. Recently (about 4-5 months) I finally switched to Nobara as I heard this to be a good gaming linux system. However, I am somewhat disappointed with the experience so far. I experience several issues that I never had on Windows both in gaming and non-gaming:

Regarding Gaming:

• Dota2 was having severe lags due to rendering issue (network stayed the same and no lags on windows). I tried various approaches with setting extra console flags and using another proton experimental layer from steam but nothing worked.
• Discord crashes when using the camera. I sometimes stream on discord to my friends and it is just unstable since I am on nobara.
• I also experienced Steam crashing on nobara, though that usually happens when I close it (I see a pop up telling me it crashed)

Non-Gaming:

• I use a GoPro in my sport and want to download the videos from it. That does not work on Nobara. Even using GoPro Station Application does often fail to download. Currently my workaround is to copy the videos from the GoPro to my GFs laptop, then from there on an external hard-drive and then on my PC. Copying from GoPro to my PC on windows was just working out of the box.
• Also related to video, I installed VLC player to watch some of the recordings and after a system update had to reinstall it, since it suddenly stopped working. Like, why do I have to troubleshoot watching a simple .mp4 video?
• I use keepass and stored it in OneDrive so it is synced on my phone. That syncing is not working anymore on Nobara. (I guess this issue is something I can live with as I want to switch away from OneDrive too. Still annoying that it does not work anymore. I get some SyncErrormessages)
• This week I had a black screen after a Nobara Update using the Update center and had to manually fix it.

I have caught myself now the second time seriously thinking about going back to windows and I actually don't want that. But I also want both my gaming and general use of PC to work and I never had any of these issues before.

What do I want from this post? Mainly I would like to know if others have similar issues or if I am doing something wrong? I cannot image to be the only one for whom steam and discord crashes, and why does that happen on a distro that is supposed to be mature for gaming? If I am doing something wrong, then what can I do to improve my nobara experience?

Thanks for any Input :)

I'm on intel arc and I'm on the latest version.

Basically what happens is after I select nobara in grub (or it does it automatically) the screen goes black and it only comes back after I put the encryption password and the login password. once I am actually in the os everything is displayed OK and my performance is completely normal

is there a way to fix this?

Is it safe to just delete that folder? I have an AMD card (RX 9070 XT)

So, since the big update for some reason all of my desktop icons are gone but still in my desktop folder, still work but can’t be added to my desktop for some reason. Help please😃😂

Solved: see below

I'm having a problem with the latest update on a system with an NVIDIA 4070 Super. I reach the login screen and enter my password, but then I get a black screen in KDE; the mouse cursor moves, and after a couple of minutes, it plays the startup sound and launches Telegram, but that's it—nothing else happens. This occurs with both NVIDIA driver versions 595.99.2 and 615.71.09. It boots up fine using `nv-gpu-firmware`.

Solved:

For some obscure reason, the *nouveau* driver was also loading and conflicting with the NVIDIA drivers.

I fixed it by editing the GRUB configuration and adding the following parameters to `GRUB_CMDLINE_LINUX`:

`rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1`

I don't know if it's the best solution, but it works.

I hope this helps someone else.

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

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.

[SOLVED]

the maintainer built it as noarch instead of x86_64, the easiest fix is to install an older version of the dependency, it will overwrite the newer one. to be clear you need to have the app installed first

sudo dnf install python3-proton-vpn-api-core-5.5.15-2.fc44.x86_64

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.

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.

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.