xed requires python!

Post#1 by **Ed_P** » 21 Feb 2023, 21:39

When did this happen?

(xed:2252): libpeas-WARNING **: 16:34:53.770: Failed to load module 'python3loader': libpython3.10.so.1.0: cannot open shared object file: No such file or directory

(xed:2252): libpeas-WARNING **: 16:34:53.770: Could not load plugin loader 'python3'

** (xed:2252): WARNING **: 16:34:53.770: Failed to load builtin plugin: Text Size

** (xed:2252): WARNING **: 16:34:53.770: Failed to load builtin plugin: Open URI

** (xed:2252): WARNING **: 16:34:53.770: Failed to load builtin plugin: Join Lines

Post#2 by **beny** » 21 Feb 2023, 22:21

i have seen the arch package and xed need the python3.10 to work with plugin try if exist a slackbuild for this software sorry the slackbuild is orphaned - no maintainer

Post#3 by **ncmprhnsbl** » 22 Feb 2023, 00:48

first off, to be clear, these are just warnings, xed works fine. just some plugins fail to load.
hard to say exactly, where when or how i built libpeas wanting python 3.10, since even slackware current is still at python 3.9..
i have a vague recollection that slackware current briefly tried python-3.10 then reverted to 3.9 some time ago(though i can't find reference to it in the logs), perhaps i compiled libpeas in that brief window ..idk
anyway, my bad for not updating libpeas for so long

a quick and dirty hack for now: (as root)

Code: Select all

cd /usr/lib64
ln -s libpython3.9.so.1.0 libpython3.10.so.1.0

no warnings, plugins load and appear to work.

also, since i used the same libpeas for mate, there may be similar issues with pluma.

Post#4 by **Ed_P** » 22 Feb 2023, 05:31

Thank you guys. But isn't python in the 05-devel.xzm module? So doesn't it then need to be active to use xed?

Post#5 by **ncmprhnsbl** » 22 Feb 2023, 06:14

Ed_P wrote: ↑
22 Feb 2023, 05:31
But isn't python in the 05-devel.xzm module?

python has never been in 05-devel. it's in 001-core. perhaps you're thinking of something else? perl maybe..
if you want to know which module a package is in try:

Code: Select all

pkginfo -w python3

will work most of the time.
even so, as i said xed doesn't need python to run, only those complaining plugins don't load.
if your xed is not working at all, it's not because of that.

Post#6 by **Ed_P** » 22 Feb 2023, 18:17

ncmprhnsbl wrote: ↑
22 Feb 2023, 06:14
python has never been in 05-devel. it's in 001-core. perhaps you're thinking of something else? perl maybe..
if you want to know which module a package is in try:
Code: Select all
pkginfo -w python3

Yes, I was probably thinking perl. Nice command pkginfo. I've don't remember reading about it before.

Code: Select all

guest@porteus:~$ pkginfo -w python

 Package:  python-urllib3-1.26.8-x86_64-1  
 located in Module:  001-core.xzm 

guest@porteus:~$ pkginfo -w perl

 Package:  perl-5.34.0-x86_64-1  
 located in Module:  05-devel.xzm 

guest@porteus:~$

Added in 8 minutes 21 seconds:

ncmprhnsbl wrote: ↑
22 Feb 2023, 00:48
a quick and dirty hack for now: (as root)
Code: Select all
cd /usr/lib64
ln -s libpython3.9.so.1.0 libpython3.10.so.1.0

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# ./xedfix.sh
root@porteus:/home/guest# xed /home/guest/.mozilla/firefox/profiles.ini

(xed:3681): dconf-WARNING **: 13:31:18.007: failed to commit changes to dconf: The connection is closed

(xed:3681): dconf-WARNING **: 13:31:18.071: failed to commit changes to dconf: The connection is closed
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)

(xed:3681): dconf-WARNING **: 13:31:18.113: failed to commit changes to dconf: The connection is closed

(xed:3681): dconf-WARNING **: 13:31:18.114: failed to commit changes to dconf: The connection is closed

(xed:3681): dconf-WARNING **: 13:31:18.114: failed to commit changes to dconf: The connection is closed

(xed:3681): dconf-WARNING **: 13:31:23.336: failed to commit changes to dconf: The connection is closed

** (xed:3681): WARNING **: 13:31:23.351: Set document metadata failed: Setting attribute metadata::xed-position not supported
root@porteus:/home/guest#

xedfix.sh

Code: Select all

#!/bin/sh
# https://forum.porteus.org/viewtopic.php?p=93011#p93011
  
cd /usr/lib64
ln -s libpython3.9.so.1.0 libpython3.10.so.1.0

Post#7 by **beny** » 22 Feb 2023, 22:10

xed in my porteus need this package gtksourceview4 and don't seem too light in linked libs

Code: Select all

  guest@porteus:~$ ldd /usr/bin/xed
	linux-vdso.so.1 (0x00007ffc90be3000)
	libxed.so => /usr/lib/xed/libxed.so (0x00007f1473cdf000)
	libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007f1473ad7000)
	libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f1473a77000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f1473857000)
	libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f147371f000)
	libgtk-3.so.0 => /usr/lib64/libgtk-3.so.0 (0x00007f1472f67000)
	libgdk-3.so.0 => /usr/lib64/libgdk-3.so.0 (0x00007f1472e5f000)
	libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x00007f1472df7000)
	libatk-1.0.so.0 => /usr/lib64/libatk-1.0.so.0 (0x00007f1472dc7000)
	libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007f1472c8f000)
	libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007f1472c5f000)
	libgtksourceview-4.so.0 => /usr/lib/libgtksourceview-4.so.0 (0x00007f1472bc7000)
	libpeas-1.0.so.0 => /usr/lib64/libpeas-1.0.so.0 (0x00007f1472baf000)
	libgirepository-1.0.so.1 => /usr/lib64/libgirepository-1.0.so.1 (0x00007f1472b77000)
	libpeas-gtk-1.0.so.0 => /usr/lib64/libpeas-gtk-1.0.so.0 (0x00007f1472b67000)
	libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007f14729f7000)
	libxapp.so.1 => /usr/lib64/libxapp.so.1 (0x00007f14729b7000)
	libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f1472877000)
	libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007f147286f000)
	libz.so.1 => /lib64/libz.so.1 (0x00007f147284f000)
	libmount.so.1 => /lib64/libmount.so.1 (0x00007f14727ef000)
	libffi.so.8 => /usr/lib64/libffi.so.8 (0x00007f14727df000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f1473d7f000)
	libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f1472767000)
	libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x00007f147274f000)
	libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 (0x00007f1472657000)
	libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x00007f1472637000)
	libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007f14725e7000)
	libfribidi.so.0 => /usr/lib64/libfribidi.so.0 (0x00007f14725c7000)
	libcairo-gobject.so.2 => /usr/lib64/libcairo-gobject.so.2 (0x00007f14725b7000)
	libepoxy.so.0 => /usr/lib64/libepoxy.so.0 (0x00007f147247f000)
	libm.so.6 => /lib64/libm.so.6 (0x00007f1472397000)
	libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007f147237f000)
	libatk-bridge-2.0.so.0 => /usr/lib64/libatk-bridge-2.0.so.0 (0x00007f1472347000)
	libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007f1472337000)
	libxkbcommon.so.0 => /usr/lib64/libxkbcommon.so.0 (0x00007f14722ef000)
	libwayland-client.so.0 => /usr/lib64/libwayland-client.so.0 (0x00007f14722d7000)
	libwayland-cursor.so.0 => /usr/lib64/libwayland-cursor.so.0 (0x00007f14722c7000)
	libwayland-egl.so.1 => /usr/lib64/libwayland-egl.so.1 (0x00007f14722bf000)
	libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f14722a7000)
	libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007f1472297000)
	libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007f147228f000)
	libXcomposite.so.1 => /usr/lib64/libXcomposite.so.1 (0x00007f1472287000)
	libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007f1472277000)
	libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007f147226f000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f1472267000)
	libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007f14721bf000)
	libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007f14720f7000)
	libEGL.so.1 => /usr/lib64/libEGL.so.1 (0x00007f14720df000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007f14720d7000)
	libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x00007f147209f000)
	libxcb-shm.so.0 => /usr/lib64/libxcb-shm.so.0 (0x00007f1472097000)
	libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f1472067000)
	libxcb-render.so.0 => /usr/lib64/libxcb-render.so.0 (0x00007f1472057000)
	libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007f1472047000)
	libGL.so.1 => /usr/lib64/libGL.so.1 (0x00007f1471fb7000)
	librt.so.1 => /lib64/librt.so.1 (0x00007f1471faf000)
	libjpeg.so.62 => /usr/lib64/libjpeg.so.62 (0x00007f1471f07000)
	libffi.so.7 => /usr/lib64/libffi.so.7 (0x00007f1471ef7000)
	liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f1471ecf000)
	libgnomekbdui.so.8 => /usr/lib64/libgnomekbdui.so.8 (0x00007f1471eaf000)
	libblkid.so.1 => /lib64/libblkid.so.1 (0x00007f1471e57000)
	libgraphite2.so.3 => /usr/lib64/libgraphite2.so.3 (0x00007f1471e27000)
	libdbus-1.so.3 => /usr/lib64/libdbus-1.so.3 (0x00007f1471dcf000)
	libatspi.so.0 => /usr/lib64/libatspi.so.0 (0x00007f1471d8f000)
	libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f1471d77000)
	libbrotlidec.so.1 => /usr/lib64/libbrotlidec.so.1 (0x00007f1471d67000)
	libGLdispatch.so.0 => /usr/lib64/libGLdispatch.so.0 (0x00007f1471ca7000)
	libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f1471c9f000)
	libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f1471c97000)
	libGLX.so.0 => /usr/lib64/libGLX.so.0 (0x00007f1471c5f000)
	libgnomekbd.so.8 => /usr/lib64/libgnomekbd.so.8 (0x00007f1471c4f000)
	libxklavier.so.16 => /usr/lib64/libxklavier.so.16 (0x00007f1471c2f000)
	libelogind.so.0 => /lib64/libelogind.so.0 (0x00007f1471b7f000)
	libbrotlicommon.so.1 => /usr/lib64/libbrotlicommon.so.1 (0x00007f1471b57000)
	libxkbfile.so.1 => /usr/lib64/libxkbfile.so.1 (0x00007f1471b2f000)
	libcap.so.2 => /lib64/libcap.so.2 (0x00007f1471b1f000)
guest@porteus:~$

Post#8 by **Ed_P** » 22 Feb 2023, 23:27

Wow!

78 module links with my xed also. And not to mislead, xed does edit .ini files on my system and in GUI mode I never see the errors. But when I executed xed in a script run in terminal I got to see all the errors and was surprised.

Post#9 by **ncmprhnsbl** » 25 Feb 2023, 04:43

not sure why you'd use root xed to edit /home/guest/.mozilla/firefox/profiles.ini..
but if want to silence those other dconf warnings, try using dbus-launch :

Code: Select all

root@porteus: dbus-launch --exit-with-session xed /blah/blah.txt

Post#10 by **Ed_P** » 25 Feb 2023, 07:14

I used root because I thought the xedfix.sh script's "ln -s libpython3.9.so.1.0 libpython3.10.so.1.0" required it. Did it not?

As for the dbus-launch option:

Code: Select all

guest@porteus:~$ dbus-launch --exit-with-session xed /home/guest/.mozilla/firefox/profiles.ini

(xed:2568): libpeas-WARNING **: 01:59:55.844: Failed to load module 'python3loader': libpython3.10.so.1.0: cannot open shared object file: No such file or directory

(xed:2568): libpeas-WARNING **: 01:59:55.844: Could not load plugin loader 'python3'

** (xed:2568): WARNING **: 01:59:55.853: Failed to load builtin plugin: Text Size

** (xed:2568): WARNING **: 01:59:55.853: Failed to load builtin plugin: Open URI

** (xed:2568): WARNING **: 01:59:55.853: Failed to load builtin plugin: Join Lines

guest@porteus:~$

If the warnings are non-important this approach works:

Code: Select all

guest@porteus:~$ xed /home/guest/.mozilla/firefox/profiles.ini > /dev/null 2>&1 
guest@porteus:~$

As guest even.