Pamac to install a systemd app.

Topic: Pamac to install a systemd app. (Read 1594 times) previous topic - next topic

0 Members and 2 Guests are viewing this topic.

Pamac to install a systemd app.

25 October 2021, 05:57:09

When trying to install app image viewer found this:

Cloning xnviewmp build files...

** (pamac:7765): WARNING **: 10:53:28.641: database.vala:1887: Failed to execute child process “systemd-run” (No such file or directory)

Is there workaround solution on it ?

Re: Pamac to install a systemd app.

Reply #1 – 25 October 2021, 07:14:35

Obligatory reminder that the AUR isn't officially supported.

With that out of the way, if I recall correctly, the artix-archlinux-support package (and it's 32 bit equivalent) have some dummy systemd files for programs that check for the presence of systemd as a dependency. Do you have it installed? If not, can you install it and see if it works?

Re: Pamac to install a systemd app.

Reply #2 – 25 October 2021, 11:41:18

Quote from: mardiyah – on 25 October 2021, 05:57:09

When trying to install app image viewer found this:
Code: [Select]
Cloning xnviewmp build files...

** (pamac:7765): WARNING **: 10:53:28.641: database.vala:1887: Failed to execute child process “systemd-run” (No such file or directory)
Is there workaround solution on it ?

You have to edit your xnviewmp PKGBUILD and replace the systemd commands with your init equivalents. AUR helpers are unsupported, both here and in Arch.

Re: Pamac to install a systemd app.

Reply #3 – 25 October 2021, 13:07:54

How to replace the systemd commands with our OpenRC init equivalents ?

Among OpenRC, runit and s6 which one the easiest to quickly provide the replacement for systemd

Re: Pamac to install a systemd app.

Reply #4 – 25 October 2021, 20:34:37

Quote from: mardiyah – on 25 October 2021, 05:57:09

trying to install app image viewer

Will you try to install xnviewmp-system-libs (from AUR).
This version works very correctly.

Re: Pamac to install a systemd app.

Reply #5 – 26 October 2021, 08:57:39

Quote from: mardiyah – on 25 October 2021, 13:07:54

How to replace the systemd commands with our OpenRC init equivalents ?

RTFM.
We are not nannies, you are supposed read up how to do it.
Educate yourself if you want to use artix effectively, this implies you go reading.
We cannot and will not start explaining the basics.

Re: Pamac to install a systemd app.

Reply #6 – 26 October 2021, 16:57:27

Quote from: x230 – on 25 October 2021, 20:34:37

Will you try to install xnviewmp-system-libs (from AUR).
This version works very correctly.

here stumble into Qt

Code: [Select]

qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be initialized

any knowledge to fix this ?

Re: Pamac to install a systemd app.

Reply #7 – 26 October 2021, 21:57:49

OK, so first off I have these packages installed, and the arch repos enabled as detailed in the ARTIX WIKI
archlinux-keyring archlinux-mirrorlist artix-archlinux-support
Also I have the build essential stuff and git and those kind of things you would expect to have to build AUR packages.
Then using pakku-git, not regular pakku (you can probably use most aur helpers for a similar result) I do:

Code: [Select]

$ pakku -Syu
...update
$ pakku -Ss xnview
...see what options there are
$ pakku -S xnviewmp xnviewmp-system-libs
...warning: removing 'xnviewmp-system-libs' from target list because it conflicts with 'xnviewmp'
...but I wanted that according to what x230 said? so type 'n' to  abort...
$ pakku -S xnviewmp-system-libs
...installs deps, builds, removes deps, installs built package...

And go look in my Applications drop down menu and under Graphics (this is Mate so not even a QT based desktop) there is XnView Multi Platform which starts and apparently works. It did have a start up wizard which had the option to send logs enabled by default so there may be some privacy concerns for those concerned about that, you can uncheck the box.
So no problems here, just works ootb.

Re: Pamac to install a systemd app.

Reply #8 – 27 October 2021, 00:47:20

Exactly the same

so try Qt debug

Code: [Select]

$ export QT_DEBUG_PLUGINS=1; xnviewmp 
QFactoryLoader::QFactoryLoader() checking directory path "/opt/xnviewmp/platforms" ...
qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem..

then google for one with the same problem, hints to:

Code: [Select]

$ ldd /opt/xnviewmp/lib/platforms/libqxcb.so  | grep "not found"
	libicui18n.so.56 => not found
	libicuuc.so.56 => not found
	libicudata.so.56 => not found

but so weird

Code: [Select]

$ sudo pacman -S libicui18n.so
warning: icu-69.1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) icu-69.1-1

Total Installed Size:  37.92 MiB
Net Upgrade Size:       0.00 MiB

$ sudo pacman -S libicuuc.so
warning: icu-69.1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) icu-69.1-1

Total Installed Size:  37.92 MiB
Net Upgrade Size:       0.00 MiB


$ sudo pacman -S libicudata.so
warning: icu-69.1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) icu-69.1-1

Total Installed Size:  37.92 MiB
Net Upgrade Size:       0.00 MiB

A clear insight on the trouble ?

Re: Pamac to install a systemd app.

Reply #9 – 27 October 2021, 07:29:18

Hello,
Why bother to install a buggy viewer, when there is everything you need in the artix and arch repositories ...

Re: Pamac to install a systemd app.

Reply #10 – 28 October 2021, 03:47:18

I think you need to uninstall xnviewmp, and install xnviewmp-system-libs instead, like x230 said much earlier:

Code: [Select]

$ ldd /opt/xnviewmp/lib/platforms/libqxcb.so  | grep "not found"
ldd: /opt/xnviewmp/lib/platforms/libqxcb.so: No such file or directory

The xnviewmp-system-libs package is the same app but built with the system libs so it's a bit different, avoids that problem, and it works properly.

Either the app has to bundle the lib if it needs it or it has to be built against the installed version, ie system libs

Code: [Select]

$ locate libicudata.so
/home/me/.aspera/connect/lib/libicudata.so.42         <  example of bundled lib at required version for another app
/usr/lib/libicudata.so
/usr/lib/libicudata.so.69              < these are the right libs but the wrong versions for your xnviewmp
/usr/lib/libicudata.so.69.1
/usr/lib32/libicudata.so
/usr/lib32/libicudata.so.69
/usr/lib32/libicudata.so.69.1