[SOLVED] Can't start freecad, probably due to python 3.8 ->3.9 upgrade

Markus.N2 · 2020-12-23 02:29:48

I haven't used freecad for a long time, and today it did not start. When I tried to start it, I got this error message:

/usr/bin/freecad: error while loading shared libraries: libpython3.8.so.1.0: cannot open shared object file: No such file or directory

I remember that python was updated from 3.8 to 3.9 recently, so libpython3.8.so* just can not exist anymore. In fact, I found /usr/lib/libpython3.9.so.1.0. Since freecad is provided as built package in community, I'm not sure if I can do anything about it at all. Or can I ? Does this package need to be rebuilt ? Where can I request that ?

Thanx

Last edited by Markus.N2 (2020-12-23 10:20:37)

Trilby · 2020-12-23 02:39:32

Freecad from the repos is linked to python 3.9. Either you are doing partial upgrades, or you are using a third-party freecad. What is the output of `pacman -Qo /bin/freecad`?

Markus.N2 · 2020-12-23 03:32:34

Yes, sometimes I do a partial upgrade, e.g. only Firefox, when there is a new version, but also a new kernel and it is a bad moment to reboot. I regularly do

pacman -Syu

just to check what is available, but then cancel. For partial updates, I then do

pacman -S {list of packages}

A while ago, I also did a upgrade of all python packages this way. But since the python upgrade, I did multiple full upgrades. One of them today, including a reboot, right before I tried starting freecad.

pacman -Qo /bin/freecad
/usr/bin/freecad is owned by freecad 0.18.16158-1

I just tried explicitly reinstalling freecad. And there was indeed a new version that starts again.

Now, I'm surprised that

pacman -Syu

missed it. Do previous partial updates affect pacman when doing a full upgrade ? Up to now, I relied on pacman not missing anything when doing -Syu, independently of what I did before (that's why I haven't even tried reinstalling freecad before posting). I have no packages or groups ignored in /etc/pacman.conf.

I'd really like to understand how this can happen.

Trilby · 2020-12-23 03:56:17

The version of freecad you had installed was never available in the repos. So in addition to (deliberately) doing partial upgrades, you also rebuilt your own freecad which you should have remembered, or you are using unsupported repos.

Last edited by Trilby (2020-12-23 03:56:35)

Markus.N2 · 2020-12-23 10:20:21

Oh ... wait ... I just checked and found freecad in my yay cache. This probably means that I originally used the package from AUR before it was added to community. I know I shouldn't but sometimes I'm in a hurry and things get lost ...

Trilby · 2020-12-23 13:16:33

There's nothing wrong with using AUR packages, but you are responsible for upgrading them yourself. In this case, you were also hit by an odd and exceedingly rare coincidence that when it was imported into [community] the version number decreased due to replacing the revision count with an actual third-level version number - otherwise pacman would have replaced it for you anytime you did a proper full upgrade.

Markus.N2 · 2020-12-23 15:10:24

On my last week's full upgrade, pacman asked me if I want to replace a package installed from AUR with the (seemingly newly added) one from community. I would have expected this to happen also when freecad was added to community.

Last edited by Markus.N2 (2020-12-23 15:10:46)

Scimmia · 2020-12-23 15:28:18

Instead it warned you that the version you had was newer than what's in Community. 0.18.16158-1 > 0.18.5, so the version number you had from the AUR was bad and that's what caused it to not update.

Ignoring things pacman tells you is never a good idea.

Last edited by Scimmia (2020-12-23 15:30:59)

GSMiller · 2020-12-23 18:58:42

Markus.N2 wrote:

Yes, sometimes I do a partial upgrade, e.g. only Firefox, when there is a new version, but also a new kernel and it is a bad moment to reboot.

MarkusN2, partial upgrades are not supported. I wonder why Trilby did not point that out already, it is so important in Archlinux.
Always do -Syu before you install software.
After that, all should work.

Markus.N2 · 2020-12-23 19:47:06

And what should I do when it's a really bad moment to reboot, but a new Firefox (Chromium, Opera, ...) version is available ?

Updating the kernel, libraries, xorg, ... without rebooting can also cause problems. On the other hand, browsers are one the most security sensitive software these days and really should be updated as soon as available.

Scimmia · 2020-12-23 19:49:22

Sure, and go ahead and start chromium right now without updating icu as well.

You're risking the browser crapping out completely

eschwartz · 2020-12-27 02:44:22

Markus.N2 wrote:

And what should I do when it's a really bad moment to reboot, but a new Firefox (Chromium, Opera, ...) version is available ?
Updating the kernel, libraries, xorg, ... without rebooting can also cause problems. On the other hand, browsers are one the most security sensitive software these days and really should be updated as soon as available.

In pacman.conf, add "IgnorePkg = linux" and optionally, linux-headers or any compiled kernel module packages you have installed.

pacman -Syu will then update all packages other than the kernel itself, which is safe because it is the singular exception to the usual partial updates rule. (In fact updating a kernel does nothing until you reboot anyway.)

You then need to explicitly pacman -S linux in order to update the kernel. Do this right before rebooting.

...

The only reason any of this matters is because after upgrading a kernel, the old modules cannot be modprobed, preventing the hotplugging of new devices. There is NO other danger or "problems" with updating the kernel without rebooting.

Updating libraries without rebooting does not matter. Just restart the program (or Xorg server), and you'll be running the new code. Or don't restart, and be running the old version without problems. Old versions aren't broken, are they??? Needed libraries etc. are unlinked on disk, but still open in the still-running program for as long as they are needed.

Arch Linux

#1 2020-12-23 02:29:48

[SOLVED] Can't start freecad, probably due to python 3.8 ->3.9 upgrade

#2 2020-12-23 02:39:32

Re: [SOLVED] Can't start freecad, probably due to python 3.8 ->3.9 upgrade

#3 2020-12-23 03:32:34

Re: [SOLVED] Can't start freecad, probably due to python 3.8 ->3.9 upgrade

#4 2020-12-23 03:56:17

Re: [SOLVED] Can't start freecad, probably due to python 3.8 ->3.9 upgrade

#5 2020-12-23 10:20:21

Re: [SOLVED] Can't start freecad, probably due to python 3.8 ->3.9 upgrade

#6 2020-12-23 13:16:33

Re: [SOLVED] Can't start freecad, probably due to python 3.8 ->3.9 upgrade

#7 2020-12-23 15:10:24

Re: [SOLVED] Can't start freecad, probably due to python 3.8 ->3.9 upgrade

#8 2020-12-23 15:28:18

Re: [SOLVED] Can't start freecad, probably due to python 3.8 ->3.9 upgrade

#9 2020-12-23 18:58:42

Re: [SOLVED] Can't start freecad, probably due to python 3.8 ->3.9 upgrade

#10 2020-12-23 19:47:06

Re: [SOLVED] Can't start freecad, probably due to python 3.8 ->3.9 upgrade

#11 2020-12-23 19:49:22

Re: [SOLVED] Can't start freecad, probably due to python 3.8 ->3.9 upgrade

#12 2020-12-27 02:44:22

Re: [SOLVED] Can't start freecad, probably due to python 3.8 ->3.9 upgrade

Board footer