This is very informative…I’ve been using Arch as a “user” for a long time and always get in over my head when it comes to the innards of the Arch ecosystem at the center.
I noticed that the crash report suggests that the problem lies with GTK, so I suppose I should open that as another topic.
Thank you very much!
I think it is the issue. Changes like switching to new ABI need to be coordinated across all packages because in linux pretty much everything is inter linked through glibc or other low level libs.
Gentoo is a rolling release as well.
Where Arch lands into these types of problems and also has problems resolving it is it is primarily a binary distribution that updates fast but then complimented by AUR
Sure, they are all part of the issue, and they all needed to be updated at the same time. However, wxgtk3 and wxgtk-common are the specific packages that are out-of-date and need to be rebuilt.
I’m just a user and observer, but from what I’ve seen Arch does typically do rebuilds in situations like this. For example, kicad was rebuilt when python 3.9 was rolled out a few weeks ago, and presumably lots of other packages with a python dependency were also rebuilt.
I’m not sure if there is a reason for not rebuilding wxgtk3 besides “it’s an oversight” but hopefully it will be resolved when I get around to reporting it.
Turns out this was already reported, see https://bugs.archlinux.org/task/68421?project=5&string=kicad
Doesn’t seem to be any progress, probably because a) it’s a problem with another package and b) there are some seemingly unrelated issues posted in the comments which may be confusing the issue.
It’s not the same issue. One you linked is about kicad itself built with newer ABI, nothing about wxpython.
OK, so yes, one error is referring to “your program” being at a newer ABI than wxgtk3, and one error is referring to wxpython being at a newer ABI than wxgtk3. They have the same root cause: wxgtk3 needs to be rebuilt.
Reported a bug against the wxgtk3 package here: https://bugs.archlinux.org/task/68988
Of course I’m an idiot and forgot to put a title on it, and I guess I can’t edit it.
I did verify that both warnings are fixed by rebuilding wxgtk3 and wxgtk-common from the arch PKGBUILD. @MC-GDB you can do that as a temporary solution.
Bug was immediately closed: “The warnings are harmless and have nothing to do with the crashes”
They may be mostly harmless, but the popup on opening pcbnew is annoying.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.