You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2020-05-24 03:04:53
- Altoid
- Member
- Registered: 2017-05-07
- Posts: 1,592
Application start-up script problem - ARM64
Hello:
I'm having a problem with the script that starts an application I want to run on my RPi3B+ with Devuan ascii 2.0.0.
It installs without issues on the SDCard with a Raspbian Buster Lite image.
Cannot see why it cannot run on the SDCard with the devuan_ascii_2.0.0_arm64_raspi3.img.
The first problem I had was with not having added the armhf architecture.
This was solved by means of dpkg --add-architecture armhf.
But other problems cropped up and ralph.ronnquist suggested that I needed to install zlib1g:armhf, which I did.
More problems appeared and HoS suggested I install libstdc++6:armhf which I did.
Q:
Shouldn't these :armhf libraries for part of what gets installed along with the architecture?
So much crap gets pulled in small dumb applications ...
You can see what went on here.
----
So, once I wrote the Devuan image to the SDCard again, I did everything I had learned I had to do thanks to ralph and HoS.
As things stood, the architecture issue was apparently solved:
root@rpidevuan:/home/pi# uname -a
Linux rpidevuan 4.16.14-v8+ #1 SMP PREEMPT Tue Jun 5 18:50:10 CEST 2018 aarch64 GNU/Linux
root@rpidevuan:/home/pi# root@rpidevuan:/home/pi# dpkg --print-architecture
arm64
root@rpidevuan:/home/pi# root@rpidevuan:/home/pi# dpkg --print-foreign-architectures
armhf
root@rpidevuan:/home/pi# The system is up to date and pyhton3.5 (needed but not listed as a dependency of the software) is installed.
root@rpidevuan:/home/pi# apt-get update
Hit:1 http://pkgmaster.devuan.org/merged ascii InRelease
Hit:2 http://pkgmaster.devuan.org/merged ascii-updates InRelease
Hit:3 http://pkgmaster.devuan.org/merged ascii-security InRelease
Reading package lists... Done
root@rpidevuan:/home/pi# root@rpidevuan:/home/pi# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.root@rpidevuan:/home/pi# apt-get update --fix-missing
Hit:1 http://pkgmaster.devuan.org/merged ascii InRelease
Hit:2 http://pkgmaster.devuan.org/merged ascii-updates InRelease
Hit:3 http://pkgmaster.devuan.org/merged ascii-security InRelease
Reading package lists... Done
root@rpidevuan:/home/pi# So, as far as I could see, everything is was it should have been Devuan ascii + armhf architecture wise
------------------------------------------------------
The problem is that the software won't start.
------------------------------------------------------
As per the autor's suggestion (the software is not supported for Devuan, just Raspian) in order to get some output, I started it directly via /usr/bin/artisan and got this:
Traceback (most recent call last):
File "artisan.py", line 68, in <module>
File "/home/pi/.local/lib/python3.5/site-packages/PyInstaller/loader/pyimod03_importers.py", line 631, in exec_module
File "artisanlib/main.py", line 86, in <module>
File "/home/pi/.local/lib/python3.5/site-packages/PyInstaller/loader/pyimod03_importers.py", line 714, in load_module
ImportError: libglib-2.0.so.0: cannot open shared object file: No such file or directory
[2510] Failed to execute script artisanI had to look around the web for a good while to get that the libglib-2.0.so.0 library the script cannot find seems to be a 32bit library included in the libglib2.0-0 package, which is installed ...
root@rpidevuan:/home/pi# apt-get install libglib2.0-0
Reading package lists... Done
Building dependency tree
Reading state information... Done
libglib2.0-0 is already the newest version (2.50.3-2+deb9u2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@rpidevuan:/home/pi# ... but not for armhf: (!)
root@rpidevuan:/home/pi# apt-get install libglib2.0-0:armhf
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libblkid1:armhf libffi6:armhf libmount1:armhf libpcre3:armhf libselinux1:armhf libuuid1:armhf uuid-runtime
The following NEW packages will be installed:
libblkid1:armhf libffi6:armhf libglib2.0-0:armhf libmount1:armhf libpcre3:armhf libselinux1:armhf libuuid1:armhf uuid-runtime
0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
Need to get 3475 kB of archives.
After this operation, 5621 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:2 http://pkgmaster.devuan.org/merged ascii/main arm64 uuid-runtime arm64 2.29.2-1+devuan2.1 [89.1 kB]
Get:3 http://pkgmaster.devuan.org/merged ascii/main armhf libuuid1 armhf 2.29.2-1+devuan2.1 [79.4 kB]
Get:4 http://pkgmaster.devuan.org/merged ascii/main armhf libblkid1 armhf 2.29.2-1+devuan2.1 [161 kB]
Get:6 http://pkgmaster.devuan.org/merged ascii/main armhf libmount1 armhf 2.29.2-1+devuan2.1 [169 kB]
Get:1 http://pkgmaster.devuan.org/merged ascii/main armhf libpcre3 armhf 2:8.39-3 [317 kB]
Get:5 http://pkgmaster.devuan.org/merged ascii/main armhf libselinux1 armhf 2.6-3+b3 [93.4 kB]
Get:7 http://pkgmaster.devuan.org/merged ascii/main armhf libffi6 armhf 3.2.1-6 [18.9 kB]
Get:8 http://pkgmaster.devuan.org/merged ascii/main armhf libglib2.0-0 armhf 2.50.3-2+deb9u2 [2548 kB]
Fetched 3475 kB in 30s (116 kB/s)
Selecting previously unselected package libpcre3:armhf.
(Reading database ... 41526 files and directories currently installed.)
Preparing to unpack .../0-libpcre3_2%3a8.39-3_armhf.deb ...
Unpacking libpcre3:armhf (2:8.39-3) ...
Selecting previously unselected package uuid-runtime.
Preparing to unpack .../1-uuid-runtime_2.29.2-1+devuan2.1_arm64.deb ...
Unpacking uuid-runtime (2.29.2-1+devuan2.1) ...
Selecting previously unselected package libuuid1:armhf.
Preparing to unpack .../2-libuuid1_2.29.2-1+devuan2.1_armhf.deb ...
Unpacking libuuid1:armhf (2.29.2-1+devuan2.1) ...
Selecting previously unselected package libblkid1:armhf.
Preparing to unpack .../3-libblkid1_2.29.2-1+devuan2.1_armhf.deb ...
Unpacking libblkid1:armhf (2.29.2-1+devuan2.1) ...
Selecting previously unselected package libselinux1:armhf.
Preparing to unpack .../4-libselinux1_2.6-3+b3_armhf.deb ...
Unpacking libselinux1:armhf (2.6-3+b3) ...
Selecting previously unselected package libmount1:armhf.
Preparing to unpack .../5-libmount1_2.29.2-1+devuan2.1_armhf.deb ...
Unpacking libmount1:armhf (2.29.2-1+devuan2.1) ...
Selecting previously unselected package libffi6:armhf.
Preparing to unpack .../6-libffi6_3.2.1-6_armhf.deb ...
Unpacking libffi6:armhf (3.2.1-6) ...
Selecting previously unselected package libglib2.0-0:armhf.
Preparing to unpack .../7-libglib2.0-0_2.50.3-2+deb9u2_armhf.deb ...
Unpacking libglib2.0-0:armhf (2.50.3-2+deb9u2) ...
Setting up libuuid1:armhf (2.29.2-1+devuan2.1) ...
Processing triggers for libglib2.0-0:arm64 (2.50.3-2+deb9u2) ...
Setting up libpcre3:armhf (2:8.39-3) ...
Setting up libblkid1:armhf (2.29.2-1+devuan2.1) ...
Setting up uuid-runtime (2.29.2-1+devuan2.1) ...
Adding group `uuidd' (GID 111) ...
Done.
Warning: The home dir /run/uuidd you specified can't be accessed: No such file or directory
Adding system user `uuidd' (UID 106) ...
Adding new user `uuidd' (UID 106) with group `uuidd' ...
Not creating home directory `/run/uuidd'.
[ ok ] Starting uuid generator: uuidd.
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Setting up libselinux1:armhf (2.6-3+b3) ...
Setting up libffi6:armhf (3.2.1-6) ...
Setting up libmount1:armhf (2.29.2-1+devuan2.1) ...
Setting up libglib2.0-0:armhf (2.50.3-2+deb9u2) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
root@rpidevuan:/home/pi# With that done, yet another error cropped up ...
--- snip ---
ImportError: libdrm.so.2: cannot open shared object file: No such file or directory
[2510] Failed to execute script artisan
root@rpidevuan:/home/pi# ... so, guessing that it was another armhf library, I installed it:
root@rpidevuan:/home/pi# apt-get install libdrm2:armhf
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
libdrm2:armhf
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 32.6 kB of archives.
After this operation, 81.9 kB of additional disk space will be used.
Get:1 http://pkgmaster.devuan.org/merged ascii/main armhf libdrm2 armhf 2.4.74-1 [32.6 kB]
Fetched 32.6 kB in 1s (24.0 kB/s)
Selecting previously unselected package libdrm2:armhf.
(Reading database ... 41568 files and directories currently installed.)
Preparing to unpack .../libdrm2_2.4.74-1_armhf.deb ...
Unpacking libdrm2:armhf (2.4.74-1) ...
Setting up libdrm2:armhf (2.4.74-1) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
root@rpidevuan:/home/pi# Things seemed to be getting better but still no cigar:
root@rpidevuan:/home/pi# /usr/share/artisan/artisan
This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".
Reinstalling the application may fix this problem.
Aborted
root@rpidevuan:/home/pi# It was nice to see the error message getting shorter ...
... but the shorter it got the less it said.
I've sort of reached the end here and don't know where to go from here.
This is the software's startup script:
pi@rpidevuan:~$ cat /usr/bin/artisan
#!/bin/sh
if [ -f /etc/os-release ]; then
grep Raspbian /etc/os-release >/dev/null
# Workaround for issue #187
if [ $? -eq 0 ]; then
unset XDG_CURRENT_DESKTOP
fi
fi
exec /usr/bin/env QT_PLUGIN_PATH=/usr/share/artisan/PyQt5/Qt/plugins LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/gtk-3.0/modules:/usr/share/artisan:$LD_LIBRARY_PATH LIBOVERLAY_SCROLLBAR=0 GTK2_RC_FILES="$HOME/.gtkrc-2.0" /usr/share/artisan/artisan "$@" 2>/dev/null
pi@rpidevuan:~$ The Qt plugins are there ...
pi@rpidevuan:~$ ls /usr/share/artisan/PyQt5/Qt/plugins
bearer iconengines imageformats platforms platformthemes printsupport
pi@rpidevuan:~$ pi@rpidevuan:~$ ls /usr/share/artisan/PyQt5/Qt/plugins/bearer
libqconnmanbearer.so libqgenericbearer.so libqnmbearer.so
pi@rpidevuan:~$pi@rpidevuan:~$ ls /usr/share/artisan/PyQt5/Qt/plugins/iconengines
libqsvgicon.so
pi@rpidevuan:~$pi@rpidevuan:~$ ls /usr/share/artisan/PyQt5/Qt/plugins/imageformats
libqgif.so libqico.so libqjpeg.so libqsvg.so
pi@rpidevuan:~$pi@rpidevuan:~$ ls /usr/share/artisan/PyQt5/Qt/plugins/platforms
libqeglfs.so libqlinuxfb.so libqminimal.so libqminimalegl.so libqoffscreen.so libqxcb.so
pi@rpidevuan:~$pi@rpidevuan:~$ ls /usr/share/artisan/PyQt5/Qt/plugins/platformthemes
libqgtk3.so
pi@rpidevuan:~$pi@rpidevuan:~$ ls /usr/share/artisan/PyQt5/Qt/plugins/printsupport
libcupsprintersupport.so
pi@rpidevuan:~$ The plugin (xcb) that the script is not finding may be /usr/share/artisan/PyQt5/Qt/plugins/platforms libqxcb.so but I have no idea if this is so.
Could anyone possibly shed some light on this for me?
Thanks in advance,
A.
Last edited by Altoid (2020-05-24 03:10:58)
Offline
#2 2020-05-24 12:04:21
- Head_on_a_Stick
- Member
- From: London
- Registered: 2019-03-24
- Posts: 3,125
- Website
Re: Application start-up script problem - ARM64
I think you should have continued this in the old thread rather than start a new one about essentially the same issue.
The plugin (xcb) that the script is not finding may be /usr/share/artisan/PyQt5/Qt/plugins/platforms libqxcb.so but I have no idea if this is so.
So have you tried installing the libqt5gui5:armhf package?
Brianna Ghey — Rest In Power
Offline
#3 2020-05-24 14:29:19
- Altoid
- Member
- Registered: 2017-05-07
- Posts: 1,592
Re: Application start-up script problem - ARM64
Hello:
... continued this in the old thread ...
I thought for a while about doing exactly that.
But what I originally saw as an ARM64 dependency issue no longer seemed to be that.
To me, it now looked more like a problem with an application's start-up script.
But you're the one with the know how, I'm just here (stubbornly) poking in the dark.
If you think all this should go as a continuation of the old thread, please let me know and I'll ask fsmithred to move it over.
... tried installing the libqt5gui5:armhf package?
No.
How could I have possibly known?
I was chasing the missing xcb Qt plugin, there's a whole lot of that and qt.conf on the web.
Now I do. 8^D
root@rpidevuan:/home/pi# apt-get install libqt5gui5:armhf
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
libglew2.0
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
libbsd0:armhf libdatrie1:armhf libdbus-1-3:armhf libdouble-conversion1:armhf libdrm-amdgpu1:armhf
libdrm-freedreno1:armhf libdrm-nouveau2:armhf libdrm-radeon1:armhf libedit2:armhf libegl1-mesa:armhf
libelf1:armhf libeudev1:armhf libevdev2:armhf libexpat1:armhf libfontconfig1:armhf libfreetype6:armhf
libgbm1:armhf libgcrypt20:armhf libgl1-mesa-dri:armhf libgl1-mesa-glx:armhf libglapi-mesa:armhf
libgles2-mesa:armhf libglew2.0:armhf libglu1-mesa:armhf libgpg-error0:armhf libgpm2:armhf libgraphite2-3:armhf
libgudev-1.0-0:armhf libharfbuzz0b:armhf libice6:armhf libicu57:armhf libinput10:armhf libjpeg62-turbo:armhf
libllvm3.9:armhf libmtdev1:armhf libncurses5:armhf libpcre16-3:armhf libpng16-16:armhf libproxy1v5:armhf
libqt5core5a:armhf libqt5dbus5:armhf libqt5network5:armhf libqt5svg5:armhf libqt5widgets5:armhf
libsensors4:armhf libsm6:armhf libssl1.0.2:armhf libthai0:armhf libtinfo5:armhf libtxc-dxtn-s2tc:armhf
libwacom2:armhf libwayland-client0:armhf libwayland-server0:armhf libx11-6:armhf libx11-xcb1:armhf
libxau6:armhf libxcb-dri2-0:armhf libxcb-dri3-0:armhf libxcb-glx0:armhf libxcb-icccm4:armhf libxcb-image0:armhf
libxcb-keysyms1:armhf libxcb-present0:armhf libxcb-randr0:armhf libxcb-render-util0:armhf libxcb-render0:armhf
libxcb-shape0:armhf libxcb-shm0:armhf libxcb-sync1:armhf libxcb-util0:armhf libxcb-xfixes0:armhf
libxcb-xinerama0:armhf libxcb-xkb1:armhf libxcb1:armhf libxdamage1:armhf libxdmcp6:armhf libxext6:armhf
libxfixes3:armhf libxi6:armhf libxkbcommon-x11-0:armhf libxkbcommon0:armhf libxshmfence1:armhf
libxxf86vm1:armhf mesa-utils:armhf
Suggested packages:
rng-tools:armhf glew-utils:armhf gpm:armhf qt5-image-formats-plugins:armhf qtwayland5:armhf lm-sensors:armhf
Recommended packages:
qttranslations5-l10n:armhf qt5-gtk-platformtheme:armhf
The following packages will be REMOVED:
mesa-utils
The following NEW packages will be installed:
libbsd0:armhf libdatrie1:armhf libdbus-1-3:armhf libdouble-conversion1:armhf libdrm-amdgpu1:armhf
libdrm-freedreno1:armhf libdrm-nouveau2:armhf libdrm-radeon1:armhf libedit2:armhf libegl1-mesa:armhf
libelf1:armhf libeudev1:armhf libevdev2:armhf libexpat1:armhf libfontconfig1:armhf libfreetype6:armhf
libgbm1:armhf libgcrypt20:armhf libgl1-mesa-dri:armhf libgl1-mesa-glx:armhf libglapi-mesa:armhf
libgles2-mesa:armhf libglew2.0:armhf libglu1-mesa:armhf libgpg-error0:armhf libgpm2:armhf libgraphite2-3:armhf
libgudev-1.0-0:armhf libharfbuzz0b:armhf libice6:armhf libicu57:armhf libinput10:armhf libjpeg62-turbo:armhf
libllvm3.9:armhf libmtdev1:armhf libncurses5:armhf libpcre16-3:armhf libpng16-16:armhf libproxy1v5:armhf
libqt5core5a:armhf libqt5dbus5:armhf libqt5gui5:armhf libqt5network5:armhf libqt5svg5:armhf
libqt5widgets5:armhf libsensors4:armhf libsm6:armhf libssl1.0.2:armhf libthai0:armhf libtinfo5:armhf
libtxc-dxtn-s2tc:armhf libwacom2:armhf libwayland-client0:armhf libwayland-server0:armhf libx11-6:armhf
libx11-xcb1:armhf libxau6:armhf libxcb-dri2-0:armhf libxcb-dri3-0:armhf libxcb-glx0:armhf libxcb-icccm4:armhf
libxcb-image0:armhf libxcb-keysyms1:armhf libxcb-present0:armhf libxcb-randr0:armhf libxcb-render-util0:armhf
libxcb-render0:armhf libxcb-shape0:armhf libxcb-shm0:armhf libxcb-sync1:armhf libxcb-util0:armhf
libxcb-xfixes0:armhf libxcb-xinerama0:armhf libxcb-xkb1:armhf libxcb1:armhf libxdamage1:armhf libxdmcp6:armhf
libxext6:armhf libxfixes3:armhf libxi6:armhf libxkbcommon-x11-0:armhf libxkbcommon0:armhf libxshmfence1:armhf
libxxf86vm1:armhf mesa-utils:armhf
0 upgraded, 85 newly installed, 1 to remove and 0 not upgraded.
Need to get 35.9 MB of archives.
After this operation, 180 MB of additional disk space will be used.
pi@rpidevuan:~$ And then ...
... after a whole 180mb of libxwhatever:armhf files, the "#$%& coffee roasting application finally went > live < . 8^D !!!
There's a warning when I start it directly via # /usr/share/artisan/artisan:
root@rpidevuan:/home/pi# /usr/share/artisan/artisan
libEGL warning: DRI2: failed to authenticate
root@rpidevuan:/home/pi#I'll have to run some tests to see if it all works, but now things are looking good.
This software now works only because I got help from you and fsmithred and was led to install a huge list of :armhf files missing from Devuan ascii ARM64, even after adding the armhf architecture and making sure there were no unmet dependencies.
Makes me wonder why all these libraries were not pulled in at some time or another, some with the installation of the software and some with the armhf architecture.
It would have saved us all (especially me) a lot of time and hair pulling. 8^7
There are probably quite a few applications that, having been written for armhf RPis, could also run on ARM64 RPis if it were not for this mess I waded into.
Maybe it would be a good idea to make a sticky with the basics of what happened and why?
I could do that, you guys could previously check it's accuracy.
I'll check to see if the software runs as expected and report back.
In the meanwhile, thank you very much for your help with this matter.
Cheers,
A.
Offline
#4 2020-05-24 15:33:27
- Head_on_a_Stick
- Member
- From: London
- Registered: 2019-03-24
- Posts: 3,125
- Website
Re: Application start-up script problem - ARM64
Head_on_a_Stick wrote:... tried installing the libqt5gui5:armhf package?
No.
How could I have possibly known?
Ah yes, of course, my apologies:
E485:~$ apt-file search libqxcb.so
libqt5gui5: /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
E485:~$Brianna Ghey — Rest In Power
Offline
#5 2020-05-24 17:46:33
- Altoid
- Member
- Registered: 2017-05-07
- Posts: 1,592
Re: Application start-up script problem - ARM64
Hello:
Ah yes, of course, my apologies:
E485:~$ apt-file search libqxcb.so libqt5gui5: /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so E485:~$
Yes ...
But as I mentioned in my OP, the plugins were in the system:
pi@rpidevuan:~$ ls /usr/share/artisan/PyQt5/Qt/plugins bearer iconengines imageformats platforms platformthemes printsupport pi@rpidevuan:~$---- snip ----
pi@rpidevuan:~$ ls /usr/share/artisan/PyQt5/Qt/plugins/platforms libqeglfs.so libqlinuxfb.so libqminimal.so libqminimalegl.so libqoffscreen.so libqxcb.so pi@rpidevuan:~$
The only one that looked like it could be (xcb) was that one.
ie: /usr/share/artisan/PyQt5/Qt/plugins/platforms/libqxcb.so
No matter, the problem is now solved. 8^)
Any idea as what to do with the warning?
root@rpidevuan:/home/pi# /usr/share/artisan/artisan
libEGL warning: DRI2: failed to authenticate
root@rpidevuan:/home/pi#From what I have seen it is a common issue with RPis and Broadmcom chips.
It crops up if the application is started from the terminal but it could be that it is not a RPi issue.
And again, thanks a lot.
Cheers,
A.
Last edited by Altoid (2020-05-24 17:47:22)
Offline
#6 2020-05-25 00:07:21
- Head_on_a_Stick
- Member
- From: London
- Registered: 2019-03-24
- Posts: 3,125
- Website
Re: Application start-up script problem - ARM64
Looks like QT_PLUGIN_PATH & LD_LIBRARY_PATH isn't being passed to /usr/share/artisan/artisan by the startup script.
Can you do that manually?
QT_PLUGIN_PATH=/usr/share/artisan/PyQt5/Qt/plugins LD_LIBRARY_PATH=/usr/share/artisan:$LD_LIBRARY_PATH LIBOVERLAY_SCROLLBAR=0 GTK2_RC_FILES="$HOME/.gtkrc-2.0" /usr/share/artisan/artisanEDIT: removed superfluous x86_64 LD_LIBRARY_PATH entry.
Last edited by Head_on_a_Stick (2020-05-25 00:12:40)
Brianna Ghey — Rest In Power
Offline
#7 2020-05-25 02:12:03
- Altoid
- Member
- Registered: 2017-05-07
- Posts: 1,592
Re: Application start-up script problem - ARM64
Hello:
... QT_PLUGIN_PATH & LD_LIBRARY_PATH isn't being passed to /usr/share/artisan/artisan ...
I see ...
Can you do that manually?
Of course.
Now the start-up script read like this:
root@rpidevuan:/usr/bin# cat artisan
#!/bin/sh
if [ -f /etc/os-release ]; then
grep Raspbian /etc/os-release >/dev/null
# Workaround for issue #187
if [ $? -eq 0 ]; then
unset XDG_CURRENT_DESKTOP
fi
fi
exec /usr/bin/env QT_PLUGIN_PATH=/usr/share/artisan/PyQt5/Qt/plugins LD_LIBRARY_PATH=/usr/share/artisan:$LD_LIBRARY_PATH LIBOVERLAY_SCROLLBAR=0 GTK2_RC_FILES="$HOME/.gtkrc-2.0" /usr/share/artisan/artisan
root@rpidevuan:/usr/bin# As it is not in your stanza, I left out this part:
"$@" 2>/dev/nullWhen I run the script directly via # /usr/share/artisan/artisan the application starts but I still get the same warning.
I've found posts on the web referring to this in RPis which would seem to indicate that it is something from as back as 2017, related to OpenGL and actually keeps some Qt based applications from running. Fortunately, it is not my case.
See here:
https://www.reddit.com/r/voidlinux/comm … lications/
My system does not have a /usr/share/X11/xorg.conf.d/99-fbturbo.conf to rename, so it is a dead end.
https://raspberrypi.stackexchange.com/q … -to-libegl
This involves more complicated stuff like symlinking libraries.
Tonight there was yet another :armhf issue regarding USB communication between the temperature logger and the software but fortunately I was able to solve it by installing usbutils:armhf which removed usbutils and installed a dependency.
I wonder how many more of these libraries I should install?
Thanks for your input.
Much appreciated.
Cheers,
A.
Last edited by Altoid (2020-05-25 02:36:19)
Offline
#8 2020-05-25 10:24:19
- Head_on_a_Stick
- Member
- From: London
- Registered: 2019-03-24
- Posts: 3,125
- Website
Re: Application start-up script problem - ARM64
Now the start-up script read like this
I meant to just run my posted command directly rather than modifying the startup script.
Brianna Ghey — Rest In Power
Offline
#9 2020-05-25 10:49:08
- Altoid
- Member
- Registered: 2017-05-07
- Posts: 1,592
Re: Application start-up script problem - ARM64
Hello:
... run my posted command directly rather than modifying ...
Ah.
Sorry.
I always keep a *.bak.
Same result.
Cheers,
A.
Offline
Pages: 1
