In the taskbar, by the clock, click on a WiFi of your choice and enter you password.
For example, mine was called 01_localhost and the password was Hi_0007
Go to System Settings
Go to Wi-Fi & Networking
Select (highlight) you listed Wi-Fi
On the General Information tab, check All user may connect to this network. Changed Metered to NO. On the Wi-Fi tab, change MTU to 1408. On Wi-Fi Security tab, change to WPA3 Personal. On the IPv6 tab, disable. Now click, Apply.
1st, notice you can NOT click on the export selected connection.
2nd, if you reboot, you will NOT be connected. Notice in System Settings (KDE) to connect.
3rd, if you click the + and manually add the Wi-Fi, still no option to connect.
4th, if you connect using the icon in your taskbar, by the clock (again), you will connect and a new copy of your Wi-Fi will be listed in System Setting each time you do this (after reboot). - You never reboot with a working connection and need to enter your password each time.
I have repeated this bug on both an upgrade from v39 to v40 and later on a fresh installation of v40 Fedora KDE Spin and Ultramarine Linux (both distros).
It also decided to try, Universal Blue, Aurora, an immutable distro, also Fedora KDE Spin based, with the same results (bug). I configured the network during setup (during the installation processes).
Trying to figure out the difference between these two in the Universal Blue ecosystem. I do like the description of both. Although I will note that the name, Aurora, is easier to recall (someone thought about marketing -- Good. Good).
I'm looking to make rusticl the default for AMD and Intel users; it works well on my own system with an RX 6600XT, but I need more testing than just my own results to make this the default. We also need to check whether this breaks anything for Nvidia users.
The fact that #UniversalBlue exists and provides a valuable service just proves that #Fedora Atomic makes it too hard for sysadmins to customize their installs. Because what they are doing is mostly just changing which packages get installed in the base image.
The UniversalBlue project is out of beta as of today, after 2 years. Since they are closing in on 14 million image pulls I think they've shown how solid it is. BlueBuild enables you to brew your own, and for the last 3 weeks I was running Fedora 40 Kinoite, enhanced by Ublue and optimized by yours truly 😎 Rock solid.
Congratulations to all contributors, who made this possible. On we go! #UniversalBlue#Fedora#bluebuild
this is nowhere near a stable release and most people should look into Sodalite if they want a good Pantheon-on-Fedora-Atomic experience, but
Zeliblue Pantheon is coming together decently, though it's jank af right now because I had to build it off of silverblue-main instead of base-main for reasons, but it...mostly works
one big exception is AppCenter because of PackageKit i think, but Flatpak-only AppCenter is coming in elementary OS 8, so that'll be nice
brew has been re-promoted to the default CLI experience in Zeliblue (I am still gonna keep the zeliblue-cli image available and maintained as an alternative, though)
fish is now configured to check for the presence of several of the packages included in brew-utilities and init atuin, starship, and/or zoxide, or set up aliases for e.g. eza and bat to take place of ls and cat
just ported Zeliblue from the old ublue-os/startingpoint stuff (AKA legacy-template now) over to the new BlueBuild stuff (https://blue-build.org)
from initial testing in a VM, it looks like a totally seamless transition on the client side, so that's great
on the dev side, each PR gets its own tag for builds that get pushed to ghcr, so I don't have to do local builds to test changes now. so that's nice too
I opened the default just configuration on Universal Blue yesterday, and saw it provided the option of installing Fleek and DevBox. I guess I'm trying them out now…
Not sure how I missed this article @jorge, but it prompted me to check out Podman Desktop, which is exactly what I have been looking for (an easier entrée into making and using containers).
So resuming my OS research, I’ve realised that getting AMD ROCm to work is a “big deal” for me. And this has failed catastrophically on Debian mostly because AMD’s software is horrendous.
Google suggests that this “just works” on Fedora, which means I might go back to my teen years of being a RedHat boy.[1]
When the package manager was rpm and you got your bits stuck to a disk on the back of computer magazine.
@passthejoe nope it provides rpm Firefox with all the codecs already, I'm using the native Firefox myself. It has all the hardware acceleration goodies 😊
Are there any other #Linux users here with #Nvidia hardware? I've been using the #KDE spin of Fedora 38 for over a year now, and while I adore KDE and have for years, I'm having some issues lately and I can't help but wonder if Nvidia's crappy #Linux drivers are not a great fit for KDE. 😔
Have any of you lovely #DistroHoppers tried both #Gnome and KDE on Nvidia? Is there any noticeable difference in performance/compatibility/bugginess? Would switching to Gnome be a better fit for my system, or would I likely see all the same issues?
In that same vein, has anyone had any luck getting Wayland to work well on Nvidia hardware? IIRC, #Fedora 39 or 40 is going to cut X11 altogether, which is tough for me cause Fedora is my favorite #distro, but Wayland is a terrible experience for me, at least with Fedora KDE and my RTX 2070 Super.
I'm so tempted just to ditch Nvidia altogether, but I would miss DLSS and good performance with raytracing, so it's a really hard choice. 😥
It always defaults to OS Tree 0 upon reboot. That means all the updates likely on OS Tree 1 are not used, because you would need to manually select it on Grub
This is a problem if you are using a wireless Bluetooth keyboard. Why?
Because until your OS loads, your keyboard does not work. You would need a 2nd keyboard, either physically wired or an older USB wireless, to select OS Tree 1