Cannot install Waydroid on Linux Mint 21

[Chrysolite Azalea]

Hello everyone! I have a problem with installing Waydroid. During the upgrade, it was removed due to unresolved dependencies and cannot be installed back.

The problem seems to be that Waydroid depends on python3-gbinder, which can't be installed because Python is "too new" now (3.10.4, while python3-gbinder package requires it to be older than 3.9). How can it be resolved? Is python3-gbinder incompatible with newer versions of Python?

[Chrysolite Azalea]

I've resolved this problem by doing the following:

1. Building the of python3-gbinder from Waydroid repository and installing the package through pip.
2. Installing the Waydroid from official repository

[charltonstanley]

Hi there!

I have the same problem. By chance could you share the compiled version python module you mentioned? Also, how did you get around the Wayland dependency?

Thanks in advance.

[Chrysolite Azalea]

Hi there!

I have the same problem. By chance could you share the compiled version python module you mentioned? Also, how did you get around the Wayland dependency?

Thanks in advance.

I've installed them using instructions and Makefiles from official repositories. And to work around the Wayland dependency, you can run the Wayland compositor (such as Weston or Cage) inside an X11 session.

[ovrflo]

Hi I tried to install Waydroid using these instructions:

Code: Select all

#
#  Installation of Wayland on Linux Mint 21
#  Installation instructions from: https://docs.waydro.id/usage/install-on-desktops
#  Ubuntu/Debian and derivatives
#

export DISTRO="jammy"
sudo curl --proto '=https' --tlsv1.2 -Sf https://repo.waydro.id/waydroid.gpg --output /usr/share/keyrings/waydroid.gpg
echo "deb [signed-by=/usr/share/keyrings/waydroid.gpg] https://repo.waydro.id/ $DISTRO main" | sudo tee /etc/apt/sources.list.d/waydroid.list
sudo apt update
sudo apt install waydroid -y
#
#  Then start Waydroid from the applications menu.
#

I got the initialization dialog, and selected the Vanilla version and it seemed to work fine, but I couldn't get the app to start and syslog was full of errors

Code: Select all

Jan  5 01:38:12 evergreen kernel: [449800.490823] init: createProcessGroup(1000, 334) failed for service 'vendor.hwcomposer-2-1': Read-only file system
Jan  5 01:38:12 evergreen systemd[1]: Started Process Core Dump (PID 1576631/UID 0).
Jan  5 01:38:13 evergreen systemd-coredump[1576632]: Process 1576628 (android.hardwar) of user 1000 dumped core.#012#012Found module /vendor/bin/hw/and
roid.hardware.graphics.composer@2.1-service with build-id: a32e1de0330563f17ec4838c5c4e28dc#012Found module /vendor/lib64/hw/hwcomposer.waydroid.so wit
h build-id: e4a0b53a3df19aaf33f310527d7d253d#012Found module /system/lib64/libui.so with build-id: 89933dce774e59640725ba2da68a2cea#012Found module /sy
stem/lib64/android.hardware.graphics.allocator@3.0.so with build-id: 660c5f3b4e154ea7e5ee2929180e1b5e#012Found module /system/lib64/libgralloctypes.so 
with build-id: d5899bda04e0acb821cf6c0652d1048e#012Found module /system/lib64/libandroid_runtime_lazy.so with build-id: 149f0e2b52775e27c23041652fdc058
d#012Found module /system/lib64/libbinder_ndk.so with build-id: 08c36f9afa6ae6bb4317c05f1a15e22b#012Found module /system/lib64/android.hardware.graphic
s.allocator@2.0.so with build-id: 53a52ad718fe071bf2ac41a632d575d6#012Found module /system/lib64/android.hardware.graphics.common-V1-ndk_platform.so wi
th build-id: 68fa9479fe773fad16a398e8522af1c0#012Found module /system/lib64/android.hardware.graphics.mapper@2.1.so with build-id: b7734fa459574bfb6945
6298dd730650#012Found module /vendor/lib64/vendor.waydroid.window@1.0.so with build-id: 04828dd1d2083134b783df69dfe70bff#012Found module /vendor/lib64/
libdrm.so with build-id: 3438c01f48c5a4158f02b64c146c2089#012Found module /vendor/lib64/vendor.waydroid.task@1.0.so with build-id: 300f78a4ad6326b652cd
3408c6b54232#012Found module /vendor/lib64/libhidltransport.so with build-id: 28709c4b11b011dfc4e8cb14a7624275#012Found module /vendor/lib64/libhwbinde
r.so with build-id: 3b18bf19e7ab37a91698aa93e611aa45#012Found module /system/lib64/android.hardware.common-V1-ndk_platform.so with build-id: fe84887827
ee721b33b120d5600c1fd8#012Found module /vendor/lib64/vendor.waydroid.display@1.0.so with build-id: 373e19c37291fd62f7a04c16c7ed7e65#012Found module /sy
stem/lib64/android.hardware.graphics.allocator@4.0.so with build-id: 9ee37c5c3c4814eb5f9a4db1c614835a#012Found module /system/lib64/libnetd_client.so w
ith build-id: b2c62d7cb99d4c762271c28e8f0e8f10#012Found module /apex/com.android.runtime/lib64/bionic/libdl_android.so with build-id: 4dd58f6e6df0de811
e48f7315746f134#012Found module /system/lib64/libhidlbase.so with build-id: e119f67164acc83a3754e81b423d3ca2#012Found module /system/lib64/android.hard
ware.graphics.mapper@2.0.so with build-id: c5c00b9c48c55fec1cbaaf3d690999fc#012Found module /system/lib64/android.hardware.graphics.composer@2.1.so wit
h build-id: 8b363e7ab3262d8bca00f7a86ede2e16#012Found module /system/lib64/libsync.so with build-id: 503dc951bb82e7873675ce1b72ae6710#012Found module /
system/lib64/libcutils.so with build-id: fd5d13a8a0810a74d43fb53305f8e976#012Found module /system/lib64/libvndksupport.so with build-id: e7c752fedaa7e1
9cb3215eca7d251bde#012Found module /system/lib64/liblog.so with build-id: 374d9e397670e2455c4ed6d03ad0adae#012Found module /system/lib64/android.hardwa
re.graphics.mapper@3.0.so with build-id: d01ed7aeb132d9d350786fcf435951e2#012Found module /system/lib64/libbase.so with build-id: 9a9d3184c731d3edaaf56
8f9f1cdcdcc#012Found module /apex/com.android.runtime/lib64/bionic/libc.so with build-id: 082396c74061b06f8ce2a645b3a60e84#012Found module /system/lib6
4/libbinder.so with build-id: 77556c9211423425a76193318cf9d590#012Found module /system/lib64/libutils.so with build-id: 0c4c3cd44b8128c649dc5c494577e7e
5#012Found module /apex/com.android.runtime/lib64/bionic/libdl.so with build-id: 61f35ee4161de100ac5723b17fb1efb3#012Found module /system/lib64/android
.hardware.graphics.mapper@4.0.so with build-id: 1e26ddabe7b926d77af9261e0c79aff5#012Found module /system/lib64/android.hardware.graphics.common@1.1.so 
with build-id: 51aee6f20da92acbe1627f70440b40ce#012Found module /system/lib64/android.hardware.graphics.common@1.2.so with build-id: a53d898738cd866667
ca940eff1af18c#012Found module /system/lib64/libfmq.so with build-id: 82666b4986ec78f643d4f9f40b340b90#012Found module /vendor/lib64/android.hardware.g
raphics.composer@2.1-resources.so with build-id: 9b81acedf9821e3bfcfe800d0c17f5c2#012Found module /system/lib64/libc++.so with build-id: f6b9efbc6d03f0
1d073cac072b6671c4#012Found module /system/lib64/libcgrouprc.so with build-id: ded0b2d711f291addb230fa6fc8a8f29#012Found module /system/lib64/libproces
sgroup.so with build-id: 216f396cf6f860f6e3edbd76dcc4069b#012Found module /system/lib64/libhardware.so with build-id: 7d836f9efb36346d0f6d34f29b1d3bc3#
012Found module /apex/com.android.runtime/lib64/bionic/libm.so with build-id: 58d2fa60dcbeae9a85160c5cf3a3c8d5#012Found module /vendor/lib64/libhwc2onf
badapter.so with build-id: 2d08676afe116ce3a9641f929855253c#012Found module /system/lib64/android.hardware.graphics.common@1.0.so with build-id: 0e0c6d
14481f5e2ef643178a473577f9#012Found module /vendor/lib64/libhwc2on1adapter.so with build-id: 9878f0e24aed0bb414bafd52df163c17#012Found module /apex/com
.android.runtime/bin/linker64 with build-id: 3000cb18b9c8d113b458396f12b50d9a#012Found module [vdso] with build-id: 21a2739157f98ff49d8920f47723a6a3ddb
1f4d1#012Stack trace of thread 334:#012#0  0x00007fd739ba1983 n/a (/vendor/lib64/hw/hwcomposer.waydroid.so + 0x1c983)
Jan  5 01:38:13 evergreen systemd[1]: systemd-coredump@67-1576631-0.service: Deactivated successfully.
Jan  5 01:38:16 evergreen kernel: [449803.903397] init: Control message: Could not find 'android.hardware.graphics.composer@2.1::IComposer/default' for ctl.interface_start from pid: 19 (/system/bin/hwservicemanager)
Jan  5 01:38:17 evergreen kernel: [449805.492241] init: starting service 'vendor.hwcomposer-2-1'...
Jan  5 01:38:17 evergreen systemd[1]: Started Process Core Dump (PID 1576663/UID 0).
Jan  5 01:38:18 evergreen systemd-coredump[1576664]: Process 1576660 (android.hardwar) of user 1000 dumped core.#012#012Found module /vendor/bin/hw/android.hardware.graphics.composer@2.1-service with build-id: a32e1de0330563f17ec4838c5c4e28dc#012Found module /system/lib64/libbinder_ndk.so with build-id: 08c36f9afa6ae6bb4317c05f1a15e22b#012Found module /system/lib64/android.hardware.common-V1-ndk_platform.so with build-id: fe84887827ee721b33b120d5600:

I assume this is because the Wayland compositor mentioned in the post below is missing???

Hi there!

I have the same problem. By chance could you share the compiled version python module you mentioned? Also, how did you get around the Wayland dependency?

Thanks in advance.

I've installed them using instructions and Makefiles from official repositories. And to work around the Wayland dependency, you can run the Wayland compositor (such as Weston or Cage) inside an X11 session.

I was wondering if you could elaborate on 'run the Wayland compositor (such as Weston or Cage) inside an X11 session.'
What is the impact on the system? Can I do this without messing up other apps? Can you point me to some info on how to do this without boring my system.

I have docker installed and I am making use of KVM/QEMU/Virt-Manager - Are these going to interfere with Waydroid?

I've resolved this problem by doing the following:

1. Building the of python3-gbinder from Waydroid repository and installing the package through pip.
2. Installing the Waydroid from official repository

I have looked at these links but there is a bit of context missing. I'm not too familiar with building from source/installing software.
These instructions leave out a lot of detail, and assume a lot of prerequisite knowledge. Did you keep any notes or partial scripts that might give me a hint as to how to do this?

Can I keep going with the install, or do I need to follow the removal instructions:
https://docs.waydro.id/usage/install-on ... g-waydroid

Any assistance would be much appreciated.

[Chrysolite Azalea]

Waydroid requires a running Wayland composer to work and won't work if it cannot connect to the Wayland socket. It won't interact with the X11 server directly. However, some Wayland composers (such as Weston) can work inside the existing X11 sessions. You can install Weston and run it, and **then** run Waydroid.

You can also switch to Sway -- it is a completely Wayland-based environment.