Open JanuszChmiel opened 4 years ago
The same issue exist even for Fedora container 31. I do not know how to overide this.
Dear @JanuszChmiel I am really unsure how to fix this. I had many issues with dbus in termux and had to downgrade at some points (when fedora was around version 21), you can find about this on my blog.
So sadly I don't think it is easy to do what you imagined. :(
I will tell you about my experiences. It is possible to install mate by using Debian operating system. Its build in template recalled by using apt install task-mate-desktop miracly configures Marco window manager, so I can execute export DISPLAY=:0 Install and run Xserver XSDL on my Android device. Then running from chrooted Debian
as non root user marco & orca && miracly, Orca speak and I can run other GTK based apps such as caja, mate-control-center or pluma and many other GTK applications. But it is only true for Debian which have been created by using debootstrap and if mate-desktop have been installed by using apt install task-mate-desktop So for our problem, I should install gnome instead of Mate, because Gnome have been officially created with support for Orca. The question is, which window manager have been used by Gnome in fedora after typing dnf install @gnome-desktop-environment But I can not determine which window manager is being used in this case. Metacity no, compiz also no. So I could not test to simply run metacity & orca & Because I do not know which window manager name is being used for Gnome. If this will not work for Me, it is possible that no. In this case, installation template do not configure The desktop environment like in Debian. I have tried to run many GTK apps. Sure, there are many limitations. I can not record sound from microphone, but I can play it even without crashes thanks to The build in Pulseaudio sound server for Termux. It is very robust solution which work without issues. But I have much more complex problem. Huavei 10 mate lite have very strange Android kernel. Which is causing that file system which is being write or read by using Proot module for Termux behaves as case file insensitive file system. As A result many packages can not be installed no matter which Linux distro is being used. Fedora install The most packages, but unfortunately, many of them also no. As A result I can not install Gnome-desktop-environment. I hhave The chance to install all packages when using other Android device which uses other Android kernel, which do not cause The problems with case file names insensitivity. Sure, fedora differs from Debian or Ubuntu. Tigervnc for example can be only controled by using sysinit so I can not use it from chroot. VNC protocol do not support XKBT X11 protocol part so I can not use Orca and keyboard for my experiments.
I Am sad, that it is impossible to create one big file by using Proot by using DD, which would create Linux compatible file system inside this big file container. And I AM sad that it is impossible to work with this container without rooted Android kernel. If somebody would invent technique, which would contain loop kernel module inside .so library, which Android app could call to overcome The fact, that Android kernel is not rooted, I would have The chance to install every Linux distro to big only one file name, file container. But I know, that it would be work for big expert.
Dear Milosev, I Am visually impaired with no sight at all and I have found A opportunity to use Linux distributions with Orca screen reader as A very promising task. Why? Because many specific Android apps do not support so many keyboard shortcuts and Orca screen reader have significant advantages while editing text when comparing with Android screen readers. But I can not install my favourite Mate desktop environment at all. LXDE and other desktops do not set at-spi communicatin with dbus so I can not use my system with Orca. Here is my log.
[termux@fedora home]$ dnf install @mate-desktop
Last metadata expiration check: 0:20:02 ago on Sun 15 Dec 2019 06:23:20 PM UTC. Error:
Problem: problem with installed package fedora-release-container-30-6.noarch
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)