You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 10, 2021. It is now read-only.
Please, does somebody of you know, why dbus can not work so smoothly and perfectly like while I have used Ubuntu 18.04 in chroot by using Proot on Android?
Now I Am getting errors related to DBUs sockets and even when i type
dbus-launch orca &
it hanks and report something has hunks aborting.
Is it becase Dbus call some routines, which are not compatible with Android bionic library? Or Is it because new Dbus have been recoded so it will never work by using ANdroid chroots?
Or do you think, that there is some way which will force Dbus to work as it should?
Sure. Even Ubuntu 18.04 have some issues. Update-manager could not be executed because of Dbus errors.
But now, it is much more bad behaviour of Dbus.
The text was updated successfully, but these errors were encountered:
aOh great, thank you very much for yours good advice.
Xfce is excellent, but unfortunately for Me, I can not enable assistive
technology support. It is necessary to run some Xfce binary tool which show
GUI where is tick box to enable it. You have true, XFCE even allocates less
RAM and is more simple it do not contain so many modules like Mate.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Please, does somebody of you know, why dbus can not work so smoothly and perfectly like while I have used Ubuntu 18.04 in chroot by using Proot on Android?
Now I Am getting errors related to DBUs sockets and even when i type
dbus-launch orca &
it hanks and report something has hunks aborting.
Is it becase Dbus call some routines, which are not compatible with Android bionic library? Or Is it because new Dbus have been recoded so it will never work by using ANdroid chroots?
Or do you think, that there is some way which will force Dbus to work as it should?
Sure. Even Ubuntu 18.04 have some issues. Update-manager could not be executed because of Dbus errors.
But now, it is much more bad behaviour of Dbus.
The text was updated successfully, but these errors were encountered: