I am running Fedora 39 right now and the last time I did a distro upgrade my graphics drivers were a huge PITA. Did your upgrade to 40 went smooth?
Absolutely. It broke any leftover intention of ever trying Ubuntu again.
I cant update because of sunshine
No f40 version? Is there a spec file? Should be possible on COPR
I got it from github https://github.com/LizardByte/Sunshine/releases. I just updated it
You can install sunshine on Fedora 40 with their COPR repo. Their GitHub releases lag behind on OS releases, but the COPR is automatically configured for new versions of Fedora since it doesn’t rely on compiling in a Docker container. Haven’t tried it myself, but it was recommended on their issues page.
I updated and now kde connect wont run without kde. Any alternative to open urls from android
There’s a GNOME extension GSConnect that uses the KDE Connect backend if you’re on GNOME. I haven’t used it in awhile since switching to KDE, but it worked well when I used it.
As far as KDE’s documentation says though, you should be able to use it on any DE. What exactly is the problem you’re experiencing? Will it not start, will it not connect (if so try re-pairing), or is there functionality that is missing?
It says it requires kde desktop but the cli works so i set it to autostart on hyprland. One thing tho is i cant type from the app but i got sunshine for that
The remote input issue is related to Wayland, and currently all wlroots based compositors (including Hyperland) have issues with this. KDE Plasma has merged support for remote input to work with KDE Connect, however many other DEs do not have the support merged, and will have to rely on xdg-desktop-portal-wlr to implement it. Here are the related bug reports and issues:
https://bugs.kde.org/show_bug.cgi?id=448604
https://github.com/emersion/xdg-desktop-portal-wlr/issues/2
https://github.com/hyprwm/Hyprland/issues/1775
Also, it seems the other issue is unrelated, are you seeing an error on the command line, or is there a dialog popup, and can you quote what is said? I’m having trouble finding any related issues anywhere on GitHub, even the Hyperland issues around remote desktop did not seem to have this particular error (or didn’t mention it at least).
I have had a LOT of issues, but they’re mostly of the papercut variety - and most of them have to do with Plasma 6 rather than Fedora 40 itself (at least I think so).
I think my CPU is running hotter on 40 than it was on 39, though.
Running Silverblue here and only one minor issue due to the wifi mac address changes and locking myself out of my network.
I also realised, that the upgrade didn’t like it when Ihade packages removed from the base which resulted in broken dependencies.
After resetting it upgrading went without any glitch.
Freecad appimage stopoed working
Luckily the FLATPAK version still runs fine
Edit: I wrote snap but I intended FLATPAK Edit 2: weekly builds of freecad from GitHub are working fine
There is an officially supported Flatpak
I would 100% use that. Snap on Fedora is likely not sandboxed at all, as it relies on Apparmor, and also not really that well maintained as nobody cares.
Yes, thanks. I wrote snap but I actually intended flatpak, D’OH!
Appimage it flawed to begin
Appreciate the call out for this one, I’ll take a look on my side later.
I decided to upgrade, and so far everything is working fine. I had some hiccups after the installation, but a reboot fixed all of them. Thanks for your input :)
Nope, not at all. Silverblue here (GNOME), and the upgrade went smooth, nvidia drivers and all.
I upgraded from 39 to 40 and I think the only issues I had were:
- Background I was using got removed, got a better one anyway
- A few gnome extensions stopped working and I had to update them or find an alternative
- Had to re-create virtual disk mapped to real disk for booting windows installation in virtual box (there is a sonicwall VPN I have to use for work which only works on Windows)
I think that was it!
I have had some strange behaviour from Firefox saying it’s become unresponsive a few times and at the same time Thunderbird but that seems to have fixed itself now