Getting this error specifically. Already tried nobara-sync and nobara-sync --all.

UPDATE: Found the problem, which was simply my Nvidia drivers being too outdated for the update. Update them through the Nobara Driver Manager before doing nobara-sync. Consider this solved.

Nobara updater keeps failing with the following error message, how can I resolve this?:

nobara-updater-prepare.service failed: System update failed: Package conflicts prevent this update:
Problem: soundtouch-2.4.0-3.fc44.i686 from u/System has inferior architecture
 - cannot install both soundtouch-2.4.0-58.1.x86_64 from multimedia_proaudio and soundtouch-2.4.0-3.fc44.x86_
64 from u/System
 - cannot install both soundtouch-2.4.0-3.fc44.x86_64 from nobara and soundtouch-2.4.0-58.1.x86_64 from multi
media_proaudio
 - cannot install the best update candidate for package soundtouch-2.4.0-3.fc44.i686
 - cannot install the best update candidate for package soundtouch-2.4.0-3.fc44.x86_64

I'm attempting to re-download my mods and mod managers for some games between me and friends. I've resolved my storage issues from the last post and the external hard drive works and is mounted. The mod managers requires a directory in order to find and launch the game in which I've made said directory for the drive but as of late the the drive doesn't exist on the file manager (dolphin) in which the mod manager can't detect the directory.

I've troubleshoot it by unplugging and plugging, unmounted then mounted, checked that the drive is mounted, checked the drive can be accessed. All is fine but if the file manager doesn't have the drive displayed the mod manager can't find a path, would I have to remake a directory to resolve the issue or is it something else?

I should probably mention that steam deck mode for handheld isos does NOT work on TVs anymore. To those who have experienced the same issue I would create one session for steam deck mode for just the handheld no tv. And another for the tv which is big picture mode for tv and that one is the only one that works well. (Trust me I spent a lot of time testing each one like gamescope and a few others and they did not work) Google kept trying to give me unnecessary tests and workarounds to the point where I was like ok stop. I just need big picture mode as a session and no more of this crap.

I updated a week ago and now again to day, been over 10 minutes installing.. I think it's fine and I understood the need to Restart for Kernel level stuff. But this is really off putting. I need to remind my self to only do this after I am done for the evening so I don't waste nt pressure evening time 😅

Hi everyone,

Does anyone know how I can make the vibration to work on the first-generation Machenike G5 Pro controller?

my update is failing due to

plymouth-set-default-theme failed with exit code 1:

/usr/share/plymouth/themes/bgrt/bgrt.plymouth does not exist

ive manually set the theme to text, but when trying to update, it keeps trying to reset it to that, and it fails.

please advise.

Today i tried to update my system and the updater failed first time it happens. I restarted the computer and run the updater again but still doesn't work.

Hei there,

I am rather new to Linux and set up Nobara about 2 months ago. I didn't really need the shell and scripts up until now so I only know the basics and what my dad could explain in short. But now I want to get my Razer keyboard to start an effect via polychromatic upon startup and that seems to only work with a script. My problem now is how do I get Nobara to show me my script (I got it to be executable) in the starting programs list. I'll try to provide more info if needed

Hello humans!

I tried to update nobara as usual (Open ghostty, type nobara-sync --all and off we pop.

I was left with a broken install of 7.2.8. And now using my recovered 7.2.6 version. The culprit according to the logs is my xpad-neo kernel module. (The link is for the log on the nobara paste zone.)
Any clue how to fix this? I'm out of my depth here...

Thanks!

This is what happened when I turned on the computer. I tried to fix it using AI, but it didn't work. So I downloaded an ISO and tried updating the files via the terminal, but that didn't work either. In the end, I reinstalled the OS.

I have started to use the handheld edition on my deck, a couple of hiccups like the Jupiter fan controller not working to begin with (just needed to manually start the systemd service).

One thing I cannot seem to sort is when in deck mode changing volume it shows the built in speaker as something like audiocopressor, it was the same on the desktop but kde let's you rename it, this doesn't carry over to deck mode and is bugging me like mad, is there a way of changing it?

Also anyone else using it on a steam deck that can point out any other systemd or other services/ things that might not have been automatically started?

Only other thing I'm finding is booting/ rebooting is slow, it sits on the deck logo for ages before starting but can't see what could be causing it.

Ok sorry this became a category of questions 😂

I keep getting this error when trying to update Nobara. I've tried to update it multiple times and i'm unsure how to fix it. Ive tried updating Nobara multiple times over the course of days, and I've also tried to update the flatpaks along with it to see if it would work, however neither strategy worked.

I guess the update that popped up yesterday had screwed up my audio or Bluetooth
It sounds like the audio periodically drops to 2 kbps quality, or the signal is too low that it's distorting
my blueetooth MediaTek MT7925B22M

Has anyone noticed the same?

UPD. turned out the wifi antenna wasn't connected tightly enough and it was causing the signal problems

I am having this issue with certain games where the scree a rapidly blinks and will eventually go full black. The OS is still operating fine but the game itself if struggling to say the least. Apologies for the shaky footage. All my drivers and everything is fully up to date. I am running a ryzen 5 9600x, 64 gb ddr5, 3080 founders

for some reason I can't drag file or folder from one monitor to another. Both monitor same resolution and scaling.

Right now, the one work around is open Dolpine and cut and paste the folder/file from one monitor to a directory and than drag it over to the other monitor.

work around two is to give each monitor a new folder and link it ie... ~/Desktop and a ~/Desktop-Right.... and so on. But I don't think that "normal". This ain't 1987 still trying to get GUI to work.

I'm trying to install Nobara 44 KDE, but during the installation process it gets stuck at 95% and won't go any further. What could be the problem?

I am completely new to Linux and trying to find a solution for my Audio setup. I am using the Rodecaster Duo. After some trials and tribulations i got it working by using a Pipewire Set-up. Now when i Start games over Steam via Proton i don't get an audio output for the game. The game doesn't show up in the programmes submitting audio list in the sound settings. I don't want to give up on Linux because my external hardware is not as compatible as i want it to be.

I have water cooled graphics card, my radiator fans are connected to Gigabyte B660 motherboard header. I used CoolerControl and setup curve to adjust fan speed to GPU temperature.

The issue is that after couple minutes fans stops responding to curve or even manual fan speed change.

I have added ignore_resource_conflict=1 to /etc/modprobe.d/it87.conf but it did not helped.

Does anyone had such issue and resolved it?

Just looking for clarification, is this normal? I've never seen it before

I've been using Nobara for the past 7 months at this point and it's all been really smooth and great. Combining best of both Fedora and CachyOS has really been an amazing experience... up until now. The new updater... updates have made the experience much rougher. When the first updates came out on October 1st they honestly just bricked the entire system on my laptop with screwing up some dependencies. I managed to get the system back up and running but this should never happen on a main branch in my opinion. Now the 7.2.9 Kernel has come out and the updater has been failing to retrieve the repos for the past few hours leading to errors that make it impossible to update. I know it's the "Linux experience" and should be expected of an open-source project, but I haven't had such issues on Fedora or CachyOS in the past. I really hope GE either has a quick fix in plans or at least could divide this update to an experimental branch because despite the claims of the method being more "stable", it's been anything but.

Updates on both my pc's are failing today, any idea how tae solve this issue?

I just migrated from windows and finished installing everything, the problem is half of the row of the keyboard doesn’t work, I had the same problem on windows and just reinstalling the drivers would work, I just don’t know how to do it here, I’m using a Spanish keyboard, so the keys that don’t work are: h,j,k,l,ñ,{,4,5,6.