Alessandro Astone

All the logs are perfectly clean, no evidence of any faults, on the andriod side nor on the host system. What you should look into is `Wayland display: None` Consider...

I'm gonna need some trace of the segfault. Also what repository are you installing waydroid from?

arm64 debian is currently lagging behind in automated builds. You can try building libglibutil and libgbinder from source: https://github.com/waydroid/libglibutil https://github.com/waydroid/libgbinder Make sure to export `LIBDIR=/usr/lib/aarch64-linux-gnu` to target 64 bit

@max1220 The debian packages were all updated, please try again

Hi, is `waydroid app install` the only issue you have when running on a different user than 1000:1000?

`waydroid app install` is fixed by: https://github.com/waydroid/android_vendor_waydroid/commit/fa1d1e9b0ccc2628de72d7b5dd8c29251106b973

``` 08-03 16:36:05.232 900 2235 I SignInPerformer-0: Successfully authorized djb{clientPackageName=com.YoStarEN.Arknights, clientUid=10131, account=Account {[email protected], type=com.google}, requestedScopes=[https://www.googleapis.com/auth/drive.appdata, https://www.googleapis.com/auth/games_lite], shouldIncludeAllGrantedScopes=false, gamesAutoSignInPolicyAction=APPLY, serverClientId=null, forceRefreshToken=false} [CONTEXT service_id=1 ] 08-03 16:36:05.234 900 3209 W PlayGamesServices[UiUtils]: AppVersion:...

Waydroid requires the binder kernel module. You can compile the module or refer to your distro.

This is an issue with your distribution package. You can also just run `waydroid container start &` as root

You cut down the logcat to only 18 lines so it contains no valuable information. But I can guess this is probably fixed in the upcoming Android 11 release with...