Dear elite Proot developers,
Your deep C language knowledge is always The guarantee, that Proot is working better and better. I Am facing very complex issue today.
I Am running latest Termux from Github. I Am using latest up to date Script to install ArchLinux from MR Rausty.
I AM running Android 8.0, Huawei Mate 10 mate.
I Am using tigervnc and startarch script execute shared memory support of Proot by default.
Everything work smoothly when I Am using VNC protocol and Bvnc PRO on my android system as a VNC client.
Unfortunately, seamonkey can not be started.
This was never been possible to get such crytical error.
I have installed
mate mate-extra
seamonkey
Firefox work, even though there are some warnings related to memory access and graphics, because I Am using Tigervnc so no real graphics drivers from The kernel.
Who of us would have so good heart and who of us could try to find The reason, why latest stable Seamonkey AArch64 Bit installable from The repositoryes do not work now?
It would be a good ida to disable sable shared memory support inside startarch script from MR Rausty.
If it will not help, some Seamonkey developers make some system calls which are not compatible with Termux and Proot.
Any help would be very appreciated.
FIrefox work, even Libreoffice apps or many Mate desktop based applications.
Dear elite Proot developers, Your deep C language knowledge is always The guarantee, that Proot is working better and better. I Am facing very complex issue today. I Am running latest Termux from Github. I Am using latest up to date Script to install ArchLinux from MR Rausty. I AM running Android 8.0, Huawei Mate 10 mate. I Am using tigervnc and startarch script execute shared memory support of Proot by default. Everything work smoothly when I Am using VNC protocol and Bvnc PRO on my android system as a VNC client. Unfortunately, seamonkey can not be started. This was never been possible to get such crytical error. I have installed mate mate-extra seamonkey Firefox work, even though there are some warnings related to memory access and graphics, because I Am using Tigervnc so no real graphics drivers from The kernel. Who of us would have so good heart and who of us could try to find The reason, why latest stable Seamonkey AArch64 Bit installable from The repositoryes do not work now?
It would be a good ida to disable sable shared memory support inside startarch script from MR Rausty. If it will not help, some Seamonkey developers make some system calls which are not compatible with Termux and Proot. Any help would be very appreciated. FIrefox work, even Libreoffice apps or many Mate desktop based applications.