Hi!

Le 08/09/2020 à 11:24, Simon McVittie a écrit :
> Which version? Please send details of the version you are now using
> (the output of "reportbug --template python3-nautilus").

Here is the system information:
> Package: python3-nautilus
> Version: 1.2.3-3
> Severity: wishlist
> 
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'testing'), (200, 'unstable'), 
> (150, 'stable'), (100, 'experimental')
> Architecture: i386 (i686)
> 
> Kernel: Linux 5.7.0-3-686-pae (SMP w/4 CPU threads)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages python3-nautilus depends on:
> ii  gir1.2-nautilus-3.0      3.36.3-1
> ii  libc6                    2.31-3
> ii  libglib2.0-0             2.64.4-1
> ii  libgtk-3-0               3.24.22-1
> ii  libnautilus-extension1a  3.36.3-1
> ii  libpython3.8             3.8.5-2
> ii  python3-gi               3.36.1-1
> 
> python3-nautilus recommends no packages.
> 
> python3-nautilus suggests no packages.



>>> (org.gnome.Nautilus:16118): Nautilus-Python-WARNING **: 09:32:47.414: 
>>> g_module_open libpython failed: /usr/lib/libpython3.8.so.1.0: Ne peut 
>>> ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
> 
> That looks like a bug in python3-nautilus. It assumes that it can load
> libpython3.8.so.1.0 from /usr/lib for some reason, but Debian does not
> install libpython3.8.so.1.0 in that location.
OK. It's possible. Note that previous version (libpython2.*.so.* had a
symlink in /usr/lib/). It could be the origin of this bug.

> Python extensions do not normally need to do this, so nautilus-python
> is doing something weird here.
OK.

>> So, I've just created a symbolic link like this and it works now. :-)
>>> ln -s i386-linux-gnu/libpython3.8.so.1.0 /usr/lib/
> 
> Please remember that you have done this so that you can undo the workaround
> when testing later versions. Modifying /usr should never be necessary.
Sure I will remember. Thanks for your advice.

--
Ludo

Reply via email to