[gbinder] Service manager /dev/anbox-binder has appeared *than hangs*

[rabaimorp]

Describe the bug

When I try to start stock waydroid I get:

[11:22:15] Starting waydroid session
[gbinder] Service manager /dev/anbox-binder has appeared

and than it hangs indefinitely. This might be duplicate (or a regression) of https://github.com/waydroid/waydroid/issues/758 but I just can't find any solution. And no, I'ts not my kernel causing it. I've tried this with linuz-zen, linux-xanmod (binder built in) linux (with binder_linux_dkms) and now I'm on the tkg kernel built with binder modules. Previously I also tested with the zen kernel with both of my laptops and I had it on my old laptop working just fine (that was on hyprland arch linux as well), I really don't get it. The only difference I can think of that is my old laptop had an intel cpu. I have an amd cpu: AMD Ryzen 5 7645HX

Waydroid version

1.4.2

Device

Linux Desktop

Operating System

Arch Linux x86_64

Kernel version

6.10.0-273-tkg-eevdf

Desktop Environment

Hyprland

GPU

NVIDIA GeForce RTX 4050 Max-Q / Mobile [Discrete]

Logs

/var/lib/waydroid/waydroid.cfg /var/lib/waydroid/waydroid.prop /var/lib/waydroid/waydroid_base.prop /var/lib/waydroid/waydroid.log sudo waydroid shell -- logcat -d | tee logcat.txt sudo dmesg | tee dmesg.txt dmesg.txt logcat.txt waydroid.cfg.txt waydroid.log waydroid.prop.txt waydroid_base.prop.txt

(renamed extensions to .txt that github woulnt let me upload)

[TanX-009]

Same here Archlinux x86_64: Linux 6.10.0-zen1-2-zen

Asus Strix G17 Ryzen 7 4800h RTX 3050

waydroid: 1.4.2-1(aur) using Integrated only using supergfxctl

/var/lib/waydroid/waydroid.cfg /var/lib/waydroid/waydroid.prop /var/lib/waydroid/waydroid_base.prop /var/lib/waydroid/waydroid.log logcat dmesg

[mistrmochov]

It just doesn't work right now with Arch Linux on some AMD gpus for some reason, mine too. It has been really long time from when people has been reporting it, but still no fix. For example on Fedora, there are no issues.

[rabaimorp]

I have an amd cpu with a integrated graphics as well, but I use my dedicated nvidia gpu

[zyrusx]

Same issue, I have a Ryzen 5 4600h and using integrated graphics.

[Candlest]

Me too Env: AMD Ryzen 7 8845H w/ Radeon 780M Graphics

[yshui]

I see surfaceflinger crashing with SIGABRT in the background, I think most likely is a mesa version issue.

Switching to software rendering makes waydroid to at least boot.

[Candlest]

I see surfaceflinger crashing with SIGABRT in the background, I think most likely is a mesa version issue.

Switching to software rendering makes waydroid to at least boot.

you are right. the moment I replaced mesa by swiftshader Waydroid could be used in my computer (AMD Ryzen 7 8845H w/ Radeon 780M Graphics)

[Fujitime]

Describe the bug

When I try to start stock waydroid I get:

[11:22:15] Starting waydroid session
[gbinder] Service manager /dev/anbox-binder has appeared

and than it hangs indefinitely. This might be duplicate (or a regression) of #758 but I just can't find any solution. And no, I'ts not my kernel causing it. I've tried this with linuz-zen, linux-xanmod (binder built in) linux (with binder_linux_dkms) and now I'm on the tkg kernel built with binder modules. Previously I also tested with the zen kernel with both of my laptops and I had it on my old laptop working just fine (that was on hyprland arch linux as well), I really don't get it. The only difference I can think of that is my old laptop had an intel cpu. I have an amd cpu: AMD Ryzen 5 7645HX

Waydroid version

1.4.2

Device

Linux Desktop

Operating System

Arch Linux x86_64

Kernel version

6.10.0-273-tkg-eevdf

Desktop Environment

Hyprland

GPU

NVIDIA GeForce RTX 4050 Max-Q / Mobile [Discrete]

Logs

/var/lib/waydroid/waydroid.cfg /var/lib/waydroid/waydroid.prop /var/lib/waydroid/waydroid_base.prop /var/lib/waydroid/waydroid.log sudo waydroid shell -- logcat -d | tee logcat.txt sudo dmesg | tee dmesg.txt dmesg.txt logcat.txt waydroid.cfg.txt waydroid.log waydroid.prop.txt waydroid_base.prop.txt

(renamed extensions to .txt that github woulnt let me upload)

Me too

[0x42697262]

I see surfaceflinger crashing with SIGABRT in the background, I think most likely is a mesa version issue. Switching to software rendering makes waydroid to at least boot.

you are right. the moment I replaced mesa by swiftshader Waydroid could be used in my computer (AMD Ryzen 7 8845H w/ Radeon 780M Graphics)

I did this, it still didn't work ... but I just forgot to restart the container.

Steps to fix on my end:

1. sudo nvim waydroid_base.prop
2. Change ro.hardware.gralloc=default and ro.hardware.egl=swiftshader.
3. sudo waydroid container restart

I no longer have these errors:

$ waydroid session start
/nix/store/nfwkrb9vnnl1dwyg6a3jc9avilmp07n6-waydroid-1.4.2/lib/waydroid/tools/helpers/net.py:34: SyntaxWarning: invalid escape sequence '\d'
  return re.search("(\d{1,3}\.){3}\d{1,3}\s", f.read()).group().strip()
[gbinder] Service manager /dev/binder has appeared

(ignore the nixos issue lol)

$ waydroid show-full-ui
041942) [23:35:53] Failed to get service waydroidplatform, trying again...
(041942) [23:35:54] Failed to get service waydroidplatform, trying again...
(041942) [23:35:55] Failed to get service waydroidplatform, trying again...
(041942) [23:35:56] Failed to get service waydroidplatform, trying again...
(041942) [23:35:57] Failed to get service waydroidplatform, trying again...
(041942) [23:35:58] Failed to get service waydroidplatform, trying again...
(041942) [23:35:59] Failed to get service waydroidplatform, trying again...

[rabaimorp]

2. swiftshader

This works 👍