GloriousEggroll (@gloriouseggroll.fosstodon.org.ap.brid.gy)

January 01, 2025 Happy New Year! Along with the new year comes a new version of Nobara! We’re happy to announce that Nobara 41 has officially been released. We have yet another fun list of changes that hopefully benefit everyone: Base: <ul class="wp-block-list"> <li>Nobara base updated to Fedora 41</li> </ul> Calamares installer: <ul class="wp-block-list"> <li>Rebased on top of KaOS linux fork for more feature options as well as on-screen keyboard functionality.</li> <li>Toggle added for on-screen keyboard</li> <li>On-screen keyboard now comes up within the installer instead of taking up half the screen</li> </ul> Mesa: <ul class="wp-block-list"> <li>We have noticed with a few benchmark videos throughout the past year that sometimes games may not run with Vulkan at all (very rare). This can happen as a regression because we shipped Vulkan built from git. Moving forward we have changed that. Nobara will now ship with the latest stable vulkan drivers that come with the latest mesa release, HOWEVER, we’ve added mesa-vulkan-drivers-git to the driver manager so users can easily swap back and forth between the two whenever they please. This should allow benchmarkers on a fresh install to have more stable results while still allowing users the choice of using drivers regularly built from git.</li> <li>We’ve separated libgallium into it’s own package which ships as two versions — mesa-libgallium and mesa-libgallium-freeworld. The reason for this is to fix a bug where if mesa is compiled without x264/x265 codecs and then you add the mesa-va/vdpau-freeworld packages that provide them, there would be tearing in the recording. With mesa-libgallium-freeworld compiled with the codecs and provided alongside the other freeworld packages the bug is fixed.</li> </ul> Nvidia: <ul class="wp-block-list"> <li>We now ship the open nvidia driver by default. If your GPU is older than turing but still supported by the closed driver you will need to make manual changes: <a href="https://wiki.nobaraproject.org/en/graphics/nvidia/supported-gpus">https://wiki.nobaraproject.org/en/graphics/nvidia/supported-gpus</a></li> </ul> Nobara-Updater: <ul class="wp-block-list"> <li>Detects if htpc packages are installed and disables grub boot timeout to provide smoother console-like htpc/handheld experience</li> <li>Corrects AMD ROCm packages to Fedora’s versions if installed. We now use upstream Fedora’s ROCm packages as they now work with Blender and Davinci Resolve</li> <li>We have changed the update checker systemtray icon from the ugly yellow to a simple black or white icon that users can change light/dark via its right-click options menu.</li> <li>We have implemented click-to-install on RPMs. If you download an RPM that is compatible with Fedora, double clicking it will now prompt the user with a very simple GUI for installing or updating the package. </li> </ul> Nobara-tweak-tool: <figure class="wp-block-image size-large"><img alt="" class="wp-image-2410" decoding="async" fetchpriority="high" height="576" sizes="(max-width: 1024px) 100vw, 1024px" src="https://nobaraproject.org/wp-content/uploads/2024/12/nobara-tweak-tool-1024x576.png" srcset="https://nobaraproject.org/wp-content/uploads/2024/12/nobara-tweak-tool-1024x576.png 1024w, https://nobaraproject.org/wp-content/uploads/2024/12/nobara-tweak-tool-300x169.png 300w, https://nobaraproject.org/wp-content/uploads/2024/12/nobara-tweak-tool-768x432.png 768w, https://nobaraproject.org/wp-content/uploads/2024/12/nobara-tweak-tool-1536x864.png 1536w, https://nobaraproject.org/wp-content/uploads/2024/12/nobara-tweak-tool.png 1920w" width="1024"/></figure> <ul class="wp-block-list"> <li>This is a new tool that has been introduced which controls a few things:</li> </ul> <ol class="wp-block-list"> <li>It is able to control auto-mounting of partitions with a simple click of a check box. By default Nobara will attempt to auto-mount any partition for common partition types (ext2/3/4, btrfs, xfs, ntfs). We originally introduced the automounting in N40 without a tool to control it, only a config file. Several months later we held an ongoing poll to see whether it was useful or detremental to users, at first most power users disliked it, so we disabled it for mounting by default, however as time went on more and more users voted for it on the pole. Ultimately after discussion with the community it was decided that it’s good to have the automount, but to have an easier way to manage it, so we introduced the tweak tool a a way to handle it via simple check box. Not only that but over the months of use the automount script went through several renditions thanks to great community members providing helpful bug reports and submitting fixes as well. <a href="https://wiki.nobaraproject.org/general-usage/troubleshooting/mounting-automounting-disk-drives">https://wiki.nobaraproject.org/general-usage/troubleshooting/mounting-automounting-disk-drives</a> </li> <li>It is able to control auto-updating on htpc/handheld systems. In late F40 we introduced an auto-update screen that runs auto-updating in the background. This is again for a more seamless console-like experience on the htpc/handheld editions. If you run one of those editions you can enable or disable auto-updates using the nobara tweak tool via check box.</li> <li>It is able to control input controller packages on htpc/handheld systems. By default Nobara ships with InputPlumber enabled and used by default. This is the standard tool we use for handling handheld controls, but we enable it by default for normal systems as well because it has the capability to allow the users to fake a controller as a different type, which is very useful when you need to remap certain things or have offbrand 3rd party controllers. In the event that you decide you’d rather use something like HHD, nobara tweak tool has a box you can uncheck that will disable auto-reinstallation of inputplumber.</li> <li>It is able to control auto-updating of DeckyLoader. In the htpc/handheld editions of Nobara we have installed DeckyLoader by default as well as several useful plugins. DeckyLoader is able to update itself internally, but in the case that you do not want DeckyLoader installed, you can use the nobara tweak tool to stop it from being reinstalled. We plan to continue to expand the tweak tool as needed for user purposes and hope it will make things easier for new users moving forward.</li> </ol> Nobara-driver-manager: <figure class="wp-block-image size-large"><img alt="" class="wp-image-2408" decoding="async" height="576" sizes="(max-width: 1024px) 100vw, 1024px" src="https://nobaraproject.org/wp-content/uploads/2024/12/nobara-driver-manager-1024x576.png" srcset="https://nobaraproject.org/wp-content/uploads/2024/12/nobara-driver-manager-1024x576.png 1024w, https://nobaraproject.org/wp-content/uploads/2024/12/nobara-driver-manager-300x169.png 300w, https://nobaraproject.org/wp-content/uploads/2024/12/nobara-driver-manager-768x432.png 768w, https://nobaraproject.org/wp-content/uploads/2024/12/nobara-driver-manager-1536x864.png 1536w, https://nobaraproject.org/wp-content/uploads/2024/12/nobara-driver-manager.png 1920w" width="1024"/></figure> <ul class="wp-block-list"> <li>As mentioned, AMD ROCm packages (rocm-meta) have been changed from upstream official AMD to Fedora-shipped versions.</li> <li>mesa-vulkan-drivers-git option now available as a choice instead of force-installed.</li> <li>Nvidia users will now have a ‘cuda-devel’ option for additional CUDA package support. This will install all the additional CUDA support packages.</li> <li>asusctl now provided to ASUS users</li> <li>xone driver is currently limited only to the xbox one wireless dongle as it currently has a bug upstream with the gip module that causes a system freeze: https://github.com/dlundqvist/xone/issues/14</li> <li>xpadneo driver has now been integrated as a kernel patch and is limited to xbox elite and xbox elite v2 over bluetooth. All other xbox controllers go through the standard xpad driver.</li> <li>broadcom wireless driver option added to driver manager</li> </ul> Nobara-welcome: <ul class="wp-block-list"> <li>Now offers discord-canary from the flatpak beta channel as the default offered discord option. This is because the canary version from the beta supports screen sharing under wayland.</li> <li>Now offers blender from fedora repository because it now allows recording h264 via ffmpeg.</li> <li>The Davinci Resolve wizard has been completely reworked and should make it much easier for users to both install and/or update Davinci Resolve while automatically performing the required changes to run it.</li> </ul> Nobara-package-manager (yumex-ng): <figure class="wp-block-image size-large"><img alt="" class="wp-image-2409" decoding="async" height="518" sizes="(max-width: 1024px) 100vw, 1024px" src="https://nobaraproject.org/wp-content/uploads/2024/12/DR-1024x518.png" srcset="https://nobaraproject.org/wp-content/uploads/2024/12/DR-1024x518.png 1024w, https://nobaraproject.org/wp-content/uploads/2024/12/DR-300x152.png 300w, https://nobaraproject.org/wp-content/uploads/2024/12/DR-768x389.png 768w, https://nobaraproject.org/wp-content/uploads/2024/12/DR-1536x777.png 1536w, https://nobaraproject.org/wp-content/uploads/2024/12/DR.png 1759w" width="1024"/></figure> <ul class="wp-block-list"> <li>Nobara package manager is now able to easily search/install/remove/manage flatpaks without issue and has been able to do so since N40. This is meant as a desktop-agnostic replacement instead of relying on gnome-software or kde’s plasma-discover</li> </ul> Flatpak: <ul class="wp-block-list"> <li>Flatpak-beta channel now added to the list of default installed and enabled flatpak repositories</li> <li>On the very first user login a simple flatpak search will run in the background, this is done to populate metadata for Nobara package manager.</li> </ul> HTPC/Handheld: <ul class="wp-block-list"> <li>Now installs with auto-updating enabled and provides a simple loading bar screen when auto-updating is being performed</li> <li>Now installs with no boot grub menu timeout, you won’t see grub. Again this is done for a smoother console-like experience</li> <li>Now ships with InputPlumber installed and enabled by default. The default settings should be fine for most users however if you prefer to have more control we recommend installing opengamepadui and using the controller configuration frontend within it for use with InputPlumber.</li> <li>Now ships with DeckyLoader installed by default along with the following plugins: Web Browser, Decky Terminal, Wine Cellar, MangoPeel, ProtonDB Badges, QuickLaunch, SimpleDeckyTDP</li> </ul> Theming: <ul class="wp-block-list"> <li>In the KDE-Nobara theme we’ve retired the win7showdesktop plasmoid and returned to the KDE shipped version, however we’ve swapped the icon with a simple white outlined circle or white filled in circle depending on which mode is toggled. It of course also uses black for light modes. Part of the reason we did this is because with the update to KDE6 the win7showdesktop bar just looks awful due to changes in default bar margins and the floating mode. There’s no need for it anymore.</li> </ul> <figure class="wp-block-image size-full"><img alt="" class="wp-image-2405" decoding="async" height="145" loading="lazy" src="https://nobaraproject.org/wp-content/uploads/2024/12/nobara-desktop-peak2.png" width="124"/></figure> Kernel: <ul class="wp-block-list"> <li>As noted we’ve added the xpadneo bluetooth driver as a kernel patch, however it is restricted only to xbox elite and xbox elite v2 devices because those devices do not work with the standard xpad driver. All other xbox controllers still use the standard xpad driver when connected via bluetooth.</li> <li>The lenovo legion patches have been temporarily disabled as we’ve found they caused ASUS laptops to lose fan curve controls. If needed it is available via DKMS module: <a href="https://copr.fedorainfracloud.org/coprs/mrduarte/LenovoLegionLinux">https://copr.fedorainfracloud.org/coprs/mrduarte/LenovoLegionLinux</a>. We may add it to the driver manager for easier use in the future.</li> </ul> Wiki: We’ve dumped our old wiki and troubleshooting feed in favor of a new wiki which is hopefully easier to navigate, search, and use overall: <a href="https://wiki.nobaraproject.org">https://wiki.nobaraproject.org</a>. All information from the previous sources has been migrated over to the new wiki and updated to reflect the current release information. https://nobaraproject.org/2025/01/01/january-01-2025/