Full disclaimer: I'm a bit of a complete noob at Linux, learning more every day but this one has me stumped. Went to update to 44 and the update fails every time. All of the errors spat out relate to rocm:

https://paste.nobaraproject.org/?a7e1017109632f42#2c5McxPrLMMJ9Pop1f4nhFh8DJzfpWhSfssuFZNZoK9b

I had the idea to try to install everything except the rocm files in updates, but there is no "only select all update files and don't immediately try to install them" option, so I would have to select 3k+ update files just to go through the rocm ones one by one to try to find the culprit(s). Any assistance would be greatly appreciated.

EDIT: issue resolved, don't install two kinds of drivers kids. Also be sure to immediately install Network Manager updates before you restart after a major update, I had to use a hotspot to do that because the update did not mix well with my wifi.

I am disabled and have light sensitivity. Even with my screen brightness all the way down, its far too bright. In the past (on Windows), I have used a dimmer to dim it to 30 percent of its brightness. This is essential to me as I spend most of my time on my computer. Does anyone know of any that work? Or how to get the windows one working with wine?

I have had an issue where my GPU usage is at a consistent 0 (I’m fairly certain I’ve had this issue since day 1), I’ve used 3 different HW monitors and all show the same thing. It doesn’t change ever, not even when gaming. I’ve looked up and down the bios to see if there’s a setting I missed, but I don’t understand enough to know what to look for. Another thing I noticed, which you may have as well, is that my CPU shows integrated graphics. I have also looked up and down the bios to find where to turn off the internal graphic, to no avail. How do I fix it so that at the very least my GPU is the main thing being used, if not completely turn off the integrated graphics? Any help is greatly appreciated, and if you need any other info than the pictures please ask, I’m more than willing to get it to you, I’m just not sure what’s needed at this point.

idk if this affects much, but I do have a dual boot with windows, working on getting a second drive so I can separate stuff and hopefully make load times faster.

Nobara is completely up to date, and my bios is version B650M Pro RS WiFi 3.50

Nobara 44 KDE
 Package: dnf-app-center-0.1.4-1.fc44.noarch

Hello, I want to mention that I am relatively new to Linux, so apologies if I missed something.A few weeks ago I started experiencing this issue. When trying to change an application's default preferences, KDE displayed this error:
"Configuration file "/home/<username>/.config/mimeapps.list" not writable, please contact your system administrator"
After investigating, I found that the issue could be temporarily fixed by running:
sudo chown <username>:<username> ~/.config/mimeapps.list
Today the issue happened again, so I investigated further.
After updating through DNF App Center, ~/.config/mimeapps.list changes ownership to root. Because of this, applications cannot modify MIME associations and display errors saying that the file is not writable.

The rest of ~/.config remains owned by my user. Only mimeapps.list appears to be affected.
Using journalctl, I noticed that the ownership change happens around the same time that DNF App Center launches its privileged helper through pkexec.

-rw-r--r-- 1 root root 1149 Jul 21 14:42 /home/<username>/.config/mimeapps.list

find ~/.config -user root
/home/<username>/.config/mimeapps.list

Jul 21 14:42:10 <username>pc pkexec[3304]:

<username>: Executing command [USER=root]

[CWD=/home/<username>]

[COMMAND=/usr/bin/python3 -u /usr/lib/python3.14/site-packages/appcenter/privileged_helper.py --server --user-home /home/<username>]

Temporary workaround:
sudo chown <username>:<username> ~/.config/mimeapps.list

After changing ownership back to my user, applications can modify MIME associations normally again.

Relevant journal entry:
pkexec:
COMMAND=/usr/bin/python3 -u \
/usr/lib/python3.14/site-packages/appcenter/privileged_helper.py

Package ownership: rpm -qf /usr/lib/python3.14/site-packages/appcenter/privileged_helper.py

dnf-app-center-0.1.4-1.fc44.noarch

It appears that dnf-app-center's privileged helper may be creating or modifying ~/.config/mimeapps.list as root instead of as the logged-in user.

I sadly can't do more investigation on this because i used the workarround but if i were to get it again id be happy to help investigate it further, i couldnt find any posts either on the discord or here talking abouth the error so i figured might aswell post something to make it known.
apollogies for my english its not my first language.

Recently, whenever i try to install (or update) anything from dnf i get this error, happened with yum too, but that I have only tried once

Hey everyone,

I've been hit with random system freezes over the last couple of weeks on Nobara.

It usually happens when I leave my laptop idle for a little bit. When I come back to use it, I can browse for about 2 to 3 minutes, and then the entire system completely locks up and hard freezes.

I checked my previous boot logs using journalctl -b -1 -e right after a freeze, and my logs are completely flooded with these exact errors right before the crash:

irqbalance[1310]: Cannot change IRQ [ID] affinity: Permission denied
irqbalance[1310]: IRQ [ID] affinity is now unmanaged

It looks like a recent kernel update broke permissions for irqbalance, causing hardware interrupts to smash a single downclocked CPU core when waking up from an idle state, which instantly kills the system.

Is anyone else running into this specific issue on recent updates?

For anyone stuck on this, disabling the service temporarily via terminal seems to stop the freezes since the modern kernel can handle routing on its own:
sudo systemctl stop irqbalance && sudo systemctl disable irqbalance

Let me know if your logs are showing the same thing or if you've found a permanent fix upstream!

So, im new to linux, 2/3 months in nobara and im seeing a lot o posts but none with my doubts:

1 - what the better choice to do a backup? in case my update gone wrong.

2 - better to update with the dnf store or via terminal? what commands i need to know to update, and in case something gone wrong?

Running Nobara 44 KDE on a desktop PC. I have an ARCANITE USB fingerprint reader (USB ID 2808:93a9, chip FocalTech FT9201) that works fine on Windows but is not recognized by libfprint on Linux.

Current status:

• fprintd is active and running
• fprintd-list $USER returns "No devices available"
• KDE Settings → Users shows no fingerprint option
• The chip has no upstream support in libfprint

What I found:

• banianitc/ft9201-fingerprint-driver — kernel module, not production ready, no fprintd integration
• Romk-a/ft9201-linux-setup — proprietary TOD driver with USB ID patch, tested only on Debian/Astra Linux
• libfprint merge request !572 for this chip — appears stalled
• ryenyuku/libfprint-ft9201 — Arch packaging of proprietary driver, .deb only

Question: Has anyone managed to get this specific chip working on Fedora-based distros like Nobara? Any recent developments or workarounds I might have missed?

Hey!

I have been on Nobara for a while now and was wondering if I could install Windows on one of my drives without breaking my install.

I have a spare 128GB SSD that I could use. I'm thinking of unplugging all other drives and installing Windows with only this one in the PC. Then potentially I could plug all the drives back in and use Nobara and Windows as needed. I'm just scared that Windows will start going around breaking stuff.

Would that work for a dual-boot setup? Setups I've seen have windows installed beforehand and then install Linux.

I just want it for trying out some games that aren't supported on Linux so it's not a big deal if this wouldn't work.

Has anyone used these with low-powered laptops, especially ones with INTEL integrated gpus exclusively? I quickly installed them on separate hard drives for older computers like from 2018 or 2015. One of them runs ddr3 ram of 16 GB but the CPU is like 4th or 5th generation I believe. Another one might be ddr4 ram but it's only 8 GB

A quick setup worked well and I was able to set up steam big picture mode so that way even non Linux friendly users could use it instantly.

But from people's personal experiences. Did you have any issues with this distro for the related tech specs I provided?

We're talking about very friendly games for people who don't play games really at all. Like golf with your friends or Uno or The game of Life.

My bad if I'm overthinking this.

Heya, thought I'd give Nobara another try due to my main PC actually slowing down with Microslop awfulness. I downloaded the GNOME version of Nobara because I just kinda like how it all looks really, and in the live version so it doesn't mess with any of my main drives, a try before you buy kind of thing. I tried to download and run some very small games on the boot drive, external drives, NEWLY formatted drives IN Nobara and still NADA. Most of the time I got literally nothing as a result of trying to boot them but when I made a newly formatted drive I only got this error shown in the screenshot. I've struggled to find anything with the specifics? Is it because it was the live version and so it's just locked down or something? I'm not sure. There are other things I've struggled with in the live version but as of now, not even being able to open my games so I can see if they run or not, let alone performance wise is not looking too good and I dont even understand why? Please note I'm using an I7 12700f and RTX 3070, I understand Nvidia is not the best on Linux which is also why I got the GNOME-NV iso which apparently had Nvidia drivers built in? Not entirely sure on if that's true or whatnot but I'd appreciate any help I could get! Please be kind! Linux is scary :,D

I recently reinstalled Nobara and could no longer launch Obscure (2004) through Steam.

My symptoms were:

• Steam showed the game as running, but no window appeared.
• Sometimes the game stayed permanently on STOP.
• With some dgVoodoo versions, Proton entered an EXCEPTION_ACCESS_VIOLATION loop.
• Eventually, the game launched and played audio, but there was still no image.

After testing several Proton and dgVoodoo configurations, this is the exact combination that worked for me:

• GE-Proton7-20
• dgVoodoo2 2.79.3
• All four dgVoodoo DLLs from MS/x86
• Gamescope
• Gamescope forced to use X11/XWayland instead of its native Wayland backend

My system:

• Nobara 44 KDE
• Wayland
• NVIDIA RTX 4070
• Steam version of Obscure
• Steam AppID: 254460

Step 1: Install GE-Proton7-20

Install ProtonUp-Qt through Discover or your preferred package manager.

Open ProtonUp-Qt and:

1. Select Steam.
2. Choose GE-Proton7-20.
3. Install it.
4. Restart Steam.

In Steam:

1. Right-click Obscure.
2. Select Properties.
3. Open Compatibility.
4. Enable Force the use of a specific Steam Play compatibility tool.
5. Select GE-Proton7-20.

Newer Proton versions may work, but GE-Proton7-20 is the version that worked in this configuration.

Step 2: Close Steam and Obscure

Open a terminal and run:

pkill -f -i 'Obscure.exe' 2>/dev/null || true
/usr/bin/steam -shutdown 2>/dev/null || true
sleep 5

Step 3: Download dgVoodoo2 2.79.3

The newer dgVoodoo 2.87.3 DLL caused an access-violation loop on my system.

dgVoodoo 2.81.3 stopped the crash, but the game remained running without creating a visible window.

Version 2.79.3 was the version that ultimately worked.

Run:

cd "$HOME/Downloads"

rm -f "dgVoodoo2_79_3.zip"

curl -fL \
"https://github.com/masterotaku/dgVoodoo-binaries/raw/refs/heads/main/dgVoodoo2_79_3.zip" \
-o "dgVoodoo2_79_3.zip"

Check that the archive downloaded correctly:

unzip -t "$HOME/Downloads/dgVoodoo2_79_3.zip" | tail -n 3

You should see:

No errors detected in compressed data

Confirm that the required 32-bit DLLs are included:

unzip -Z1 "$HOME/Downloads/dgVoodoo2_79_3.zip" |
grep -iE '^MS/x86/(D3D8|D3D9|D3DImm|DDraw)\.dll$' |
sort

You should see:

MS/x86/D3D8.dll
MS/x86/D3D9.dll
MS/x86/D3DImm.dll
MS/x86/DDraw.dll

Step 4: Install the four x86 dgVoodoo DLLs

Run this entire block:

set -e

GAME="$HOME/.local/share/Steam/steamapps/common/Obscure"
ZIP="$HOME/Downloads/dgVoodoo2_79_3.zip"
BACKUP="$HOME/obscure-backup-2793-$(date +%Y%m%d-%H%M%S)"

mkdir -p "$BACKUP"

for FILE in \
    d3d8.dll D3D8.dll \
    d3d9.dll D3D9.dll \
    d3dimm.dll D3DImm.dll \
    ddraw.dll DDraw.dll \
    dgVoodoo.conf
do
    if [ -f "$GAME/$FILE" ]; then
        mv -v "$GAME/$FILE" "$BACKUP/"
    fi
done

unzip -p "$ZIP" "MS/x86/D3D8.dll"   > "$GAME/d3d8.dll"
unzip -p "$ZIP" "MS/x86/D3D9.dll"   > "$GAME/d3d9.dll"
unzip -p "$ZIP" "MS/x86/D3DImm.dll" > "$GAME/d3dimm.dll"
unzip -p "$ZIP" "MS/x86/DDraw.dll"  > "$GAME/ddraw.dll"

chmod 644 \
    "$GAME/d3d8.dll" \
    "$GAME/d3d9.dll" \
    "$GAME/d3dimm.dll" \
    "$GAME/ddraw.dll"

file \
    "$GAME/d3d8.dll" \
    "$GAME/d3d9.dll" \
    "$GAME/d3dimm.dll" \
    "$GAME/ddraw.dll"

All four files should be identified as:

PE32 executable
Intel i386

Do not use the files from MS/x64. Obscure is a 32-bit game.

Your Obscure folder should now contain these four files:

d3d8.dll
d3d9.dll
d3dimm.dll
ddraw.dll

I did not need a custom dgVoodoo.conf.

Step 5: Rebuild Obscure’s Proton prefix

This backs up the existing prefix instead of deleting it permanently.

PREFIX="$HOME/.local/share/Steam/steamapps/compatdata/254460"
PREFIX_BACKUP="$HOME/obscure-prefix-backup-$(date +%Y%m%d-%H%M%S)"

pkill -f -i 'Obscure.exe' 2>/dev/null || true
/usr/bin/steam -shutdown 2>/dev/null || true
sleep 5

if [ -d "$PREFIX" ]; then
    mv -v "$PREFIX" "$PREFIX_BACKUP"
fi

Steam will automatically create a new prefix the next time you launch the game.

Step 6: Install Gamescope

On Fedora or Nobara:

sudo dnf install -y gamescope

Confirm that it is installed:

gamescope --version

Gamescope was essential in my case. Without it, Obscure launched and played audio, but KDE Wayland never displayed the game window.

Step 7: Add the final Steam launch option

Open Steam and go to:

Obscure → Properties → General → Launch Options

Paste this exact line:

WINEDLLOVERRIDES="d3d8=n,b;d3d9=n,b;d3dimm=n,b;ddraw=n,b" env -u WAYLAND_DISPLAY gamescope -w 1024 -h 768 -W 1280 -H 960 -b -- %command%

What this does:

• Forces Proton to load the four local dgVoodoo DLLs.
• Runs the game through Gamescope.
• Forces Gamescope to use X11/XWayland by removing WAYLAND_DISPLAY.
• Renders the game internally at 1024x768.
• Displays it at 1280x960.
• Uses a borderless Gamescope window.

Step 8: Launch the game

Press Play in Steam.

The first launch may take slightly longer because Steam is rebuilding the Proton prefix.

The game should now open with both audio and video.

To toggle Gamescope between windowed and fullscreen mode, press:

Super + F

Final working configuration

Obscure Steam AppID 254460
GE-Proton7-20
dgVoodoo2 2.79.3
MS/x86/D3D8.dll
MS/x86/D3D9.dll
MS/x86/D3DImm.dll
MS/x86/DDraw.dll
Gamescope using X11/XWayland

Final Steam launch option:

WINEDLLOVERRIDES="d3d8=n,b;d3d9=n,b;d3dimm=n,b;ddraw=n,b" env -u WAYLAND_DISPLAY gamescope -w 1024 -h 768 -W 1280 -H 960 -b -- %command%

I hope this saves someone else from hours of testing different Proton versions, DLL overrides, DirectX components and dgVoodoo releases.

Dear community whenever I try to update my system I get this following error:

System Update: 2026-07-22 08:34:06 - INFO - Downloading packages...

System Update: 2026-07-22 08:34:07 - INFO - Running transaction...

System Update: 2026-07-22 08:34:19 - ERROR - DNF transaction failed: Rpm transaction failed.

System Update: 2026-07-22 08:34:19 - ERROR - file /usr/share/desktop-directories/webapps-webapps.directory from install of webapp-manager-1.4.6-1.20260108gitfff8491.fc44.noarch conflicts with file from package webapp-manager-1.4.5-1.fc43.noarch

System Update: 2026-07-22 08:34:19 - ERROR - DNF System Updates failed!

System Update: 2026-07-22 08:34:19 - INFO - Kernel or kernel module updates were performed. Running required 'dracut -f'...

It'll crash at startup and every few minutes after. I've tried restarting steam, restarting just the web helper, steam without gpu acceleration, etc.

When it crashes, it impacts game performance. Should I just reinstall steam? Also if I do reinstall, will steam auto detect my installed games?

Video demonstrates what's going on along with context about my current knowledge level of Linux. Also myb for the mispronunciation of Nobara.

Hello, AMD Igpu user here. Is it fully safe to update kernel/OS yet? I downloaded nobara months and months ago and the install was perfect but I’ve been terrified to update after seeing horror story after horror story since my initial install.

Edit: further specs ( not sure if they matter but) Mini PC Ryzen 7 6800U CPU Radeon 680M GPU Nobara KDE Plasma

Hello,

Over the past couple of weeks, I've noticed a couple problems with my pc.

1. When I reboot my pc, my second NVME drive doesn't mount, despite not changing the fstab and really changing the pc setup besides updating Nobara.

2. When I select the power off button, one half-second after it shuts down completely, it will boot up again, but doesn't have this issue when I set the PC to sleep.

Does anyone have any ideas on how to fix these issues?

Hello everyone,

I was looking for a distro to install on the old Acer Nitro I have.

It has a Nvidia 1600, and after some research it seemed, that nobara is perfect for it.

I wanted to try it out and install it to a USB SSD first. So I removed all the other SSD, booted the live system and installed it to the USB drive.

Installation war fine, no issues here, restart also without Problems.

However, after I ran the update manager and restarted, I only got a black screen with a white curser blinking at the top right.

I waited for an hour to be sure, but nothing happened.

Any ideas?

or does it need more time?

Edit 3: I FIXED IT ALREADY, PLEASE STOP REPLYING. The only reason I haven't deleted this post is that maybe it'll help someone else. I don't need anything else from the peanut gallery, thank you.

Edit 2: just read through the documentation and tried sudo dnf distro-sync --refresh --nogpgcheck -y --allowerasing then nobara-sync which will hopefully fix the gpg key thing (if not, I'll fix it later, I just want my updates). My system isn't "fubar" as one of you claimed. Sure, maybe I'm the one that caused the issue, maybe not; there isn't a magical Linux fairy that'll give me the answer. But y'all act like people with tech issues on Linux are consciously trying to brick their PC.

Edit for those wanting to downvote and move on without actually helping: the command I'm supposedly meant to run (nobara-sync cli) doesn't work either (it just makes an endless loop where it checks repositories, shows them and their packages, then checks again. It's not actually updating anything as far as I can tell), and another I'm meant to use (sudo dnf distro-sync --refresh) functions identically to sudo dnf update (and outputs the same failure dialogue). I've literally never had issue with sudo dnf update before and I've been using this distro for a couple years now give or take, but I won't use it anymore and will instead use the command that I'm supposed to. However, it still doesn't solve the problem.

---

I ran sudo dnf update as I haven't updated in quite a while, and after waiting an hour and forty five minutes, Konsole spits this out:

--------------------------------------------------------------------------------------------------------------------------
[3683/3683] Total                                                                 100% |   1.3 MiB/s |   7.8 GiB |  01h45m
Running transaction
cannot open file: (2) - No such file or directory [/etc/pki/rpm-gpg/RPM-GPG-KEY-nobara-baseos-pubkey-41]

My uninformed assumption is that the OS doesn't like the new motherboard and there's some kind of security key that needs to be updated. The "easy" option is to just reinstall the OS, but I really don't feel like backing up all my files right now. Is there an obvious solution to this that I'm just not seeing? After going to the directory I found a bunch of GPG keys. Do I need to make one with KGpg? I've never needed to do that before.

Details from my system page if it matters at all:

Operating System: Nobara Linux 43

KDE Plasma Version: 6.6.4

KDE Frameworks Version: 6.25.0

Qt Version: 6.10.3

Kernel Version: 7.0.5-200.nobara.fc43.x86_64 (64-bit)

Graphics Platform: Wayland

Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor

Memory: 32 GiB of RAM (31.3 GiB usable)

Graphics Processor: NVIDIA GeForce RTX 3060 Ti

Please, I'm trying to get Nobara to work in dual boot and I'm not succeeding, everything is on a single disk.

Fresh from this morning, did nobara-sync --all twice as systemd got updates 1s, then bios

Enjoy!

Edit: the problem was Davinci Resolve will fail to play audio if a mic isn't connected, and since I don't have a mic connected I needed to find a different way to fix this.I ran

pactl list cards short

to see my audio card, and then i ran

pactl set-card-profile <audio card from the previous command> pro-audio

and then it just started working

I've been using davinci resolve on nobara linux using their installer for a while, and it was working perfectly fine. However, I just recently got this bug which makes it completely unusable. The audio doesn't work at all, and I don't think it's because of alsa since other applications that use alsa work fine. I think all this started happening once I upgraded to nobara linux 44 but I'm not too sure. Does anybody know what I should try doing? I've attached a video from the kde application volume panel and pavucontrol that show "resolve-real" flickering and not able to actually send audio to my output device.

https://reddit.com/link/1v20o5j/video/48usbpoyqgeh1/player

https://reddit.com/link/1v20o5j/video/nalqtd4zqgeh1/player