a little sad they switched to chromium for default browser, but their reason makes sense.
also didn't even realize Minecraft was running in XWayland, but it's cool that it can run natively in Wayland now
this post was submitted on 26 Dec 2023
63 points (97.0% liked)
Linux Gaming
15300 readers
12 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 1 year ago
MODERATORS
uh nice. now perhaps i'll switch to nobara coming from stock fedora kde
there always was a fully functional kde spin...
Nobara really needs to make in place upgrading easier, holy crap. Literally the only criticism I've had in all my time using Nobara.
I'm not running all those console commands and risk shit fucking up, I'll just do a wipe and install after holiday madness passes.
also wtf why chromium?
Why chromium is explained in the article (better support for many apps) but you can always change it to firefox, also detailed in the upgrade article.
I upgraded from 38 to 39 with no issues. It's honestly not hard or dangerous, just copy paste a few lines then paste the last ones to prompt the upgrade. The only catch is that if you had KDE already you won't need to remove some of the packages it tells you about. Don't overthink it imo.
I already fail at the first one:
sudo dnf remove -y blender discord telegram-desktop oneapi-level-zero librist libndi-sdk firefox onlyoffice-desktopeditors
Which errors out:
Error:
Problem: The operation would result in removing the following protected packages: plasma-desktop
(try to add '--skip-broken' to skip uninstallable packages)
Try removing all of them one-by-one and ignore the ones that are trying to remove plasma.
Seems to be librist that's the issue here. The nobara-amdgpu-config package issue also errors out on the first command though, skipping a package.
Problem: cannot install the best update candidate for package pipewire-codec-aptx-0.3.69-1.fc38.x86_64
- nothing provides pipewire >= 1.0.1 needed by pipewire-codec-aptx-1.0.1-1.fc38.x86_64 from rpmfusion-free-updates
This also happened on the following nobara-sync command. And the second command gives:
error: package nobara-amdgpu-config is not installed
Went through with it anyway but I feel that's potentially one of those things that eventually causes issues further down the line until the system doesn't boot anymore...
If I have 38 Gnome, do I have to completely re-install the os or is there a "upgrade" option or something?
You can upgrade, but it's not automatic: https://nobaraproject.org/docs/upgrade-troubleshooting/how-do-i-upgrade-to-a-new-nobara-version/
Scroll down for 38 to 39.
I really hope they work on that upgrade processes so you can just do it with a simple yes click from the updater by the time 40 comes out.