I seem to be having a lot of problems with 9.0.2 and Fedora 42.
I’m trying to back up to 8.0.9 to see if I see the same thing, but I can’t seem to find any way to do so. I can’t find a Flatpak for 8.0.9 nor can I seem to find any RPMs.
The copr build system seems to indicate that these were built at some point:
https://copr.fedorainfracloud.org/coprs/g/kicad/kicad-stable/build/8669343/
What am I missing?
Thanks.
One way is to use the Appimage package. Search for CyberCircuits KiCad Appimage.
Flathub is annoying in deprecating older versions though they can be found with some effort.
As @retiredfeline suggested you may have to switch to the appimage. Fedora can only afford so much disk space, and we moved to the 9.0 series for Fedora 42 around the end of January 2025. The 8.0 builds have been deleted from the Fedora servers, which is why you cannot find those builds.
I’d be curious as to what problems you are having with 9.0. I’m the KiCad maintainer for Fedora, and I’m happy to work with the upstream developers to resolve bugs, so please let me know if we can help.
@SteveFalco Thanks. I’m getting strange problems with the cursor hanging when it moves into the active schematic area.
I filed a bug about this: Cursor events getting stuck inside active schematic area (#21044) · Issues · KiCad / KiCad Source Code / kicad · GitLab
I did try the AppImage and it also exhibited the same problem.
At least maintain something historical linked from the primary KiCad pages–especially across a major version bump with such a massive set of changes. An AppImage or FlatPak or container … something.
It’s not like it will be something that very many people would download. But it would be extremely helpful for someone who hits a showstopper bug.
It looks like one of the upstream developers has already commented on your bug. This appears to be an issue with “mutter”. Another user had a similar problem and downgrading mutter solved it for them.
I tried the search that @retiredfeline mentioned, and CyberCircuits does have an appimage for 8.0.9, but I can’t say if it would solve your problem if the root problem is with “mutter”.
I feel your pain - I personally switched to the XFCE desktop so I could stay with X11. KiCad works extremely well in that environment. Wayland, on the other hand, is known to cause problems, so for KiCad work it is best avoided.
Any advice or pointers on how to do that switch on Fedora Silverblue (Fedora 42)?
The whole “Wayland or Bust” leaves enough of a sour taste behind that I’m happy to dump Gnome in the trash.
I don’t know the answer to that but there is a contact that I can ask. I’ll post back with what he says.
I did some experiments with Silverblue in a VM. I used rpm-ostree to install both kwin-x11 and plasma-workspace-x11. When I clicked on my user name to log in, there was a “gear” icon in the lower right of the login screen. I selected kde-x11, entered my password, and sure enough I had an x11 session.
By the way, you can tell the type of session by:
echo $XDG_SESSION_TYPE
I don’t know how long Silverblue will keep kde-x11 available. I am using the standard Fedora (non-silverblue) OS. It provides an XFCE spin, but I haven’t found XFCE for Silverblue.
My frield suggested trying some of the other desktops to see if they have x11, He specifically suggested Fedora Kinoite (Atomic + KDE) to see if it allows x11. But I’d bet that you still need to install the packages I mentioned above.
My friend also indicated that the mutter bug has been fixed, so if you want to stay with gnome you can update to mutter-48.3-2.fc42 to see if it fixes your problem.
I hope the above info helps.
Thanks for the advice. I’ll try some of it.
In the meantime, I rolled back the problematic update (atomic distribution, FTW) and will let some other people have the joy of beta testing XWayland.