By popular demand, I took a look at #Nobara, the gaming focused derivative of #Fedora.
I compared the default experience, various ease of use tweaks, controller support, gaming performance, and highlighted the major differences, after installing both distros on the same device.
So, is Nobara truly better than Fedora for gaming? Let’s see!
I'm continually amazed by the #Fedora community, but admittedly having trouble processing a certain mistrust for #RedHat right now in light of recent layoffs and comments from #IBM's CEO about replacing people with AI. I'm legit angry about the harm done to Fedora and the #opensource world by some clearly out of touch suits and grieved by the human cost of those decisions on people who most certainly did not deserve it.
I'm confident that #Fedora will continue to thrive in spite of the damage done by upper management at #RedHat and #IBM because it's the community that drives Fedora's innovation. Unfortunately, Red Hat doesn't seem to see that "value" as much as the rest of the Fedora community, based on their recent lay offs of key Fedora and open source community members.
Been using #Fedora Silverblue on my Surface Pro 4 now for about a week so. Really enjoy it. A bit of a learning curve but overall a nice experience. My only complaint is that using rpm-ostree for packages does require a reboot. Which I understand why, but it does take some extra time. However, that is very minor and once you're set up with all the packages you need that doesn't become an issue. It's a good way to force you to stop and think "do I really need to install this package?"
For context; I've been around since 2.6.x, which was a kernel released/maintained for about 11 years before 3.0.x came to existence. Every major new kernel version still feels unfathomable (☉｡☉)!
Ich konsterniere immer mehr bei der Frage von Linux-Distros für Nicht-Geeks. Der Text erklärt das gut: Distros, die vorgeben, einsteigerfreundlich zu sein, und dann bricht doch etwas zu stark, sind konzeptionell ein Irrweg. Das hilft am Ende niemandem.
#Ubuntu und seine Ableger (ja, auch Mint und mittelbar Pop!_OS) spielen sich mit dem #Snap-Desaster, bizarren Sonderwegen und Werbung im System an den Rand. #Fedora und #openSUSE richtige sich mMn schon an Geeks, man muss auch Repos für Video-Hardwarebeschleunigung und Mainstream-Codecs aktivieren und solche Späße. Distro-Upgrades (oder Tumbleweed) sind bei Fedora und openSUSE auch nicht unproblematisch. Dann bleibt nicht mehr viel übrig. Arch, #EndeavourOS und Co. sind für Nerds.
Does anyone know how to fix this screen coming up with Fedora 38? I saw someone have a similar issue but I can't find their post on here. Trying to avoid having to nuke and pave my system. #Fedora
My TB data spans decades, for emails, tasks & events [oh, & also contacts]. I've lost count of however many TB iterations / versions it's lived thru. It began life yonks ago in Win7, & lives now, for many years, in Linux.
For at least a couple of years, my Calendar has had this damn annoying problem. For many Events, but not all, it is just impossible to directly duplicate them. Both Ctrl-C Ctrl-V, & RMB-Copy RMB-Paste, simply do NOTHING [for it seems like the majority (but not entirety) of my Events].
Research lead me to https://bugzilla.redhat.com/show_bug.cgi?id=2015334 my distro is [#Arch not #Fedora, but IMO that's irrelevant]. I was galled to see that bug report was closed without action or solution; also that it was raised only with Redhat not actually Thunderbird.
In exasperation, recently i conceived this inefficient albeit effective workaround: for the target Event, RMB-ConvertTo-Task, then edit said new task to desired date for the intended duplicate, then convert said task to a new Event... then correct all the text formatting that was buggered by this silly indirect process.
I've wondered if possibly the database has become corrupted somehow due to surviving all the historical TB version changes, to cause this duplication problem. So last night i thought i'd Export the Tasks & Events ICS file, then Import it into a clean TB profile elsewhere [in some vague hope that this process might magically "fix" any putative data corruption; hahahaha yeah right]. The Export nominally succeeded, being an 81 MB file. The Import failed every time, with the error msg per pic.
What is a frustrated user now supposed to do? 🤷♀️
Learn how hardware security tokens, featuring the standard #FIDO2 and FIDO U2F, can be used manufacturer independent with standard tools in #Fedora#Linux. The article shows how to register keys, activate them as factor to login on terminal and #GNOME and authenticate when using #sudo.
Following articles in this series will handle #OpenSSH 8.2+ usage for ssh key management and how to use the key as factor to decrypt #LUKS partitions. Stay tuned!
Why do we still live in a world where I can't independently configure my laptop display and external monitor's scaling (100% and 150% respectively) in #Linux? Or is this just an Ubuntu/Kubuntu problem?
Under X11 both displays sync their scaling settings (awful experience when you have a 4K panel). And with Wayland both displays end up blurry, even after a reboot.
I'm using the HP Dev One.
Are there easy workarounds or should I finally make the permanent switch to #fedora?
I'm trying to install #Proton Bridge on a fresh #Kubuntu install, and keep running into this problem. Any hints out there?
EDIT 1: my package manager can't find 'libsecret' or 'secret-service'. Installing 'pass' does nothing. And kwallet isn't supported, which is ridiculous.
EDIT 2: Apparently installing gnome-keyring solves this. @protonmail: Bridge still needs serious work on #Linux...)
I wonder if there's a way to get the #aur working on #fedora. It's possible to install #pacman & #paru using #dnf and #cargo respectively, and after doing
pacman-key --init
pacman-key --populate archlinux
it's possible to get it to start installing.
The problem you run into is dependencies. Pacman can't use dnf pkgs as deps & tries to doubly install things, conflicting with the files of dnf pkgs.
I wonder if there's a way around that. Would be cool to play around with.
If you've enjoyed our new website, why not take a look behind the scenes at the team that came together to make it happen? The redesign was two years in the making - lots to cover in this blog post series! #Fedora