ArchLinux aarch64 chroot and how to psetup dbus professionally

Tue Mar 21 06:41:15 UTC 2023

Dear Dbus developers,
	I Am using Termux version 119, Android 9.0 and Proot to execute ArchLinux container.
My device is not rooted.
I Am using The following X11 development client app for Android, because it support keyboard much more best than todays professional Android VNC client apps.
https://github.com/termux/termux-x11

Author has dropped previous Xwayland protocol support but he did not updated his readme file on GIthub branch.

How to setup Dbus professionally on Archlinux so I will not be fvroced to start Mate by typing
Dbus-run-session mate-session &
Is it possible to setup Dbus professionaly even on chroot containers, where original Linux kernel is not being used?

I also have issue with aat-spi, because Orca screen reader complains, that it can not find sockets in /home.
I have created normal user account on Archlinux by using -m and -wheel options.
But Orca is very unstable.
Why?
Even if I execute mate-session by typing
Dbus-run-session mate-session &
D
Bus-run-session orca &
When I terminate Mate by using Logout function or if I quit Orca by using provided Orca shortcut key build in to Orca, I can not start Orca again.
May be, that it is because Proot uses special option sharedtmp, so my Tmp folder is accessed from chroot container. So I have two tmp folders. In termux Android app and also in Archlinux chroot.

Any instructions how to setup Dbus in chroot container so it will work as it should, so sockets will not be automatically deleted and it wil be never lost from flash chips file systém will be very welcomed.
Thank you very much for your answer.
With kindness regards.

Janusz Chmiel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dbus/attachments/20230321/4ee3e841/attachment.htm>