Description of problem: I do not succeed to make waydroid working in spite of a lot of searching on the internet to understand how to start it How reproducible: Oh, a lot, I have already tried many times! Steps to Reproduce: Enter: waydroid session start and enjoy the errors' show. I am assigning the bug to myself because I know what to do to fix that.
Packages libgbinder and python-gbinder were needing an update on mga9 to match the version of waydroid. In its present state, waydroid is not starting and pops out multiple errors. To test, please follow that procedure. 1) Install waydroid * this will trigger the installation of dkms-anbox, which compiles a kernel module, everything should run smoothly (was mga#29611) * this will trigger the install of lib(64)gbinder and python3-gbinder, please check that the versions installed are really the new ones, coming from updates_testing 2) Install plasma-wayland, the wayland version of KDE (waydroid only works under wayland) 2) Reboot your system, halt the boot at the grub2 bootloader to change kernel options, and, there, add the kernel parameter option: psi=1 PS: I cannot give much details how to do that here, but internet will help you if you don't know what I am talking about. Then, Press CTRL+X to go on with that boot having psi=1 set. 3) Login into Plasma *Wayland* (it should have appeared on the list on possible window managers) 4) In a root terminal * set permission of the devices present under /dev/binderfs/ to 666: chmod 666 /dev/binderfs/* * make a simlink: ln -s /dev/binderfs/anbox-binder /dev/binder * start the service: systemctl start waydroid-container and then fire up the image install: waydroid first-launch A menu appears, pick up the image named "GAPP" (the one named VANILLA is bugged). This downloads many things that will be put into /var/lib/waydroid/ Now, we fix more bugs that are not on mageia but upstreams: a) Within that directory: /var/lib/waydroid/lxc/waydroid Edit the file "config" and comment that line (add a # before) #lxc.apparmor.profile = unconfined b) As root, restart the container service: systemctl restart waydroid-container c) As user, in a terminal start a session waydroid session start d) As user, in another terminal, start the show waydroid show-full-ui Good luck, works for me (tm). NB: waydroid does not (yet?) support bluetooth, so long for the traxxas charger :(((((((((( Update advisory: ------------------ python3-gbinder and libgbinder packages updated to latest version allowing waydroid to run on mga9. Updated packages: ------------------ RPMS: lib(64)gbinder1-1.1.34-1.mga9 lib(64)gbinder-devel-1.1.34-1.mga9 python3-gbinder-1.1.2-1.mga9 SRPMS: libgbinder-1.1.34-1.mga9.src.rpm python-gbinder-1.1.2-1.mga9.src.rpm
Assignee: eatdirt => qa-bugs
CC: (none) => eatdirt
Advisory based on comment 1 added to SVN. Please remove the "advisory" keyword if it needs to be changed. It also helps when obsolete advisories are tagged as "obsolete"
Keywords: (none) => advisoryCC: (none) => marja11
Adding the has_procedure flag because of the excellent instructions in comment 1.
Keywords: (none) => has_procedureCC: (none) => andrewsfarm
Regarding comment 1, the RPM for python-gbinder appears to match the name for the SRPM - no python3. I shall have a go at this tomorrow.
CC: (none) => tarazed25
Tried to install waydroid before updating but failed at the module build stage. $ sudo urpmi waydroid To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "Core Release") dkms-anbox 0.0.3 1.mga9 noarch dnsmasq 2.89 2.mga9 x86_64 lib64nftables1 1.0.6 1.mga9 x86_64 lxc 5.0.2 1.mga9 x86_64 nftables 1.0.6 1.mga9 x86_64 python3-pyclip 0.5.4 3.mga9 noarch waydroid 1.3.2 1.mga9 noarch ...... /var/tmp/rpm-tmp.i4s8hk: line 1: fg: no job control /var/tmp/rpm-tmp.i4s8hk: line 2: fg: no job control /var/tmp/rpm-tmp.i4s8hk: line 3: fg: no job control warning: %post(lxc-1:5.0.2-1.mga9.x86_64) scriptlet failed, exit status 1 ERROR: 'script' failed for lxc-1:5.0.2-1.mga9.x86_64 5/7: dkms-anbox ################################## Creating symlink /var/lib/dkms/anbox-ashmem/0.0.3-1.mga9/source -> /usr/src/anbox-ashmem-0.0.3-1.mga9 DKMS: add Completed. Preparing kernel 6.4.9-desktop-4.mga9 for module build: (This is not compiling a kernel, just preparing kernel symbols) /sbin/dkms: line 939: warning: command substitution: ignored null byte in input Storing current .config to be restored when complete Running Generic preparation routine make mrproper.... using /proc/config.gz make oldconfig.... make prepare.... Building module: cleaning build area.... make -j20 KERNELRELEASE=6.4.9-desktop-4.mga9 all KERNEL_SRC=/lib/modules/6.4.9-desktop-4.mga9/build....(bad exit status: 2) Error! Bad return status for module build on kernel: 6.4.9-desktop-4.mga9 (x86_64) Consult the make.log in the build directory /var/lib/dkms/anbox-ashmem/0.0.3-1.mga9/build/ for more information. Error! Could not locate ashmem_linux.ko.xz for module anbox-ashmem in the DKMS tree. You must run a dkms build for kernel 6.4.9-desktop-4.mga9 (x86_64) first. Creating symlink /var/lib/dkms/anbox-binder/0.0.3-1.mga9/source -> /usr/src/anbox-binder-0.0.3-1.mga9 DKMS: add Completed. Preparing kernel 6.4.9-desktop-4.mga9 for module build: (This is not compiling a kernel, just preparing kernel symbols) /sbin/dkms: line 939: warning: command substitution: ignored null byte in input Storing current .config to be restored when complete Running Generic preparation routine make mrproper.... using /proc/config.gz make oldconfig.... make prepare.... Building module: cleaning build area.... make -j20 KERNELRELEASE=6.4.9-desktop-4.mga9 all KERNEL_SRC=/lib/modules/6.4.9-desktop-4.mga9/build....(bad exit status: 2) Error! Bad return status for module build on kernel: 6.4.9-desktop-4.mga9 (x86_64) Consult the make.log in the build directory /var/lib/dkms/anbox-binder/0.0.3-1.mga9/build/ for more information. Error! Could not locate binder_linux.ko.xz for module anbox-binder in the DKMS tree. You must run a dkms build for kernel 6.4.9-desktop-4.mga9 (x86_64) first. warning: %post(dkms-anbox-0.0.3-1.mga9.noarch) scriptlet failed, exit status 4 ERROR: 'script' failed for dkms-anbox-0.0.3-1.mga9.noarch 6/7: dnsmasq ################################## 7/7: waydroid ################################## Follow-up later.
It looks you're not up to date Len, the version of dkms-anbox should be: dkms-0.0.3-1.1.mga9 (see #mga29611) Also check the version of the python3-gbinder package:1.1.2-1.mga9
@Chris. Yes, you are correct. Updated dkms-anbox. $ rpm -q dkms-anbox dkms-anbox-0.0.3-1.1.mga9 $ rpm -q python3-gbinder package python3-gbinder is not installed lcl@yildun:~ $ sudo urpmi python3-gbinder No package named python3-gbinder But I was able to install python-gbinder. $ ls -l /usr/bin/python lrwxrwxrwx 1 root root 9 Apr 16 2023 /usr/bin/python -> ./python3* Tried installing waydroid again and hit the same scriptlet failure at lxc but waydroid was installed apparently. $ rpm -q waydroid waydroid-1.3.2-1.mga9 Now I need to investigate if I have a partition with plasma-wayland installed or if it can be installed. Running Mate currently and # urpmi plasma-wayland No package named plasma-wayland
Note also that I am still at the pre-update stage, preparing the ground.
@Len: Try plasma-workspace-wayland. Unknown if that's enough, though. @Chris: Confirmed that the original package is python-gbinder, but the package you put in updates_testing is python3-gbinder. Looks like you changed the name. You'll need to change things to use the original name, or our tools won't update it.
(In reply to Thomas Andrews from comment #9) > @Len: Try plasma-workspace-wayland. Unknown if that's enough, though. > > @Chris: Confirmed that the original package is python-gbinder, but the > package you put in updates_testing is python3-gbinder. > > Looks like you changed the name. You'll need to change things to use the > original name, or our tools won't update it. Removing the advisory keyword, because this means it'll need to get changed. Also setting the feedback keyword, to be removed when this is solved
Keywords: advisory => feedback
Status comment: (none) => The procedure is in comment 1, but the advisory there will need to be replaced
Ok, this is weird. It is true that I have changed the name of the package to python3 to match our python policy, but I have added a Provides: python-gbinder with version-release, so I would expect it to be selected on update. I'll check that more carefully.
OK, I didn't think of that. Len, if you get the original package installed, give the updates a try. They might install after all.
I see the package on distrib-coffee, so I guess that is just mirrors not being: https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/9/x86_64/media/core/updates_testing/python3-gbinder-1.1.2-1.mga9.x86_64.rpm You can test already (with python3-gbinder), but I do see that I should push a new package adding an Obsolete to the old python package.
Another 5 hours work, one unbootable partition and finally gave up and switched to update mode using another partition. qarepo could not find python3-gbinder so I went to the mirror and grabbed it manually. # rpm -q waydroid waydroid-1.3.2-1.mga9 # dkms status anbox-binder, 0.0.3-1.1.mga9: added After the reboot with the added kernel parameter could not find the file /dev/binderfs Go through the loop again: # urpme dkms-anbox which removed waydroid as well. # urpmi waydroid To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "Core Release") waydroid 1.3.2 1.mga9 noarch (medium "Core Updates") dkms-anbox 0.0.3 1.1.mga9 noarch .... Creating symlink /var/lib/dkms/anbox-binder/0.0.3-1.1.mga9/source -> /usr/src/anbox-binder-0.0.3-1.1.mga9 DKMS: add Completed. Error! Your kernel devel files for kernel 6.4.9-desktop-4.mga9 cannot be found at /lib/modules/6.4.9-desktop-4.mga9/build or /lib/modules/6.4.9-desktop-4.mga9/source. You can use the --kernelsourcedir option to tell DKMS where it's located. Error! Could not locate binder_linux.ko.xz for module anbox-binder in the DKMS tree. You must run a dkms build for kernel 6.4.9-desktop-4.mga9 (x86_64) first. warning: %post(dkms-anbox-0.0.3-1.1.mga9.noarch) scriptlet failed, exit status 4 ERROR: 'script' failed for dkms-anbox-0.0.3-1.1.mga9.noarch 2/2: waydroid ########################################################################### I have had enough for tonight. Going to bed. Will try to boot the newer kernel tomorrow after cleaning the slate.
OK, resuming. Reinstalled Mageia 9. # urpmi dkms-anbox That seemed to work, anbox installed. Installed Plasma Wayland: # urpmi plasma-workspace-wayland Installed python3-gbinder from local RPM. # urpmi waydroid Rebooted and added psi=1 to kernel options. Tried logging in to Plasma Wayland and that failed. Screen blanked for a while then returned to login. Plasma X11 is OK. This is an nVidia machine so maybe it would work better on an Intel or Ryzen hardware. It is unexpected. I thought Wayland was meant to be hardware agnostic. There is an option to allow Wayland to use an nVidia GPU but that has to be built in to the kernel I believe, and probably for a restricted range of cards.
Something else to note, switching from sddm back to lightdm removes the Plasma Wayland entry from the login menu. gdm does not acknowledge Plasma Wayland either.
Thanks Len for your tests. That is weird to have missing kernel-devel packages because dkms should trigger the install of the kernel-devel. For wayland not starting, it is very well possible that wayland does not work on some hardware, I have the same problem with one of my machine having a GTX1080, but it works on my laptop.
So, it would be worth trying one of my other machines. I'll get back to you.
Restarting on AMD Ryzen 7 5700. Followed the procedure as closely as possible. On reboot logged in to Plasma Wayland without a problem. # journalctl -xb | grep psi Nov 04 17:21:30 rutilicus kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.4.16-desktop-3.mga9 root=UUID=939406c6-c2d2-4514-b321-4775711ff5f9 ro psi=1 splash quiet noiswmd resume=UUID=a0fbfb32-252e-4df4-b2e8-45d34fe4ca8a audit=0 vga=791 Updated the three packages, which removed python-gbinder. Again there is no /dev/binderfs. Tried removing dkms-anbox and reinstalling waydroid. Still no /dev/binderfs so another boot may be in order.
Still no sign of binderfs in /dev and nothing reported in the boot journal.
The problem of Len Lawrence could be that the module binder_linux is not loaded after reboot lsmod|grep bin binfmt_misc 28672 1 modprobe binder_linux lsmod|grep bin binder_linux 221184 0 binfmt_misc 28672 1 I'll check dkms-anbox package to see if I can fix that, maybe making the correction that was made to dkms-vhba about the same issue
The module not loading may be a config file missing, indeed. Anyway, yes, please try to load the module manually, /dev/binderfs should appear then!
OK, tried loading the binder_linux module but all that produced was /dev/binder. # ll /dev/binder crw------- 1 root root 10, 122 Nov 5 12:43 binder Started the waydroid container alright. Chose GAPPS from the download menu and it is still downloading. /var/lib/waydroid has no lxc directory, just a log and a cfg file. Surprising that it gets this far with an incompletely configured system but at least it now starts. Leaving thissys ex until the infrastructure is better defined for the user. Thanks Chris for the detailed instructions.
I get dkms-anbox load the module at boot but still can't make waydroid works after download the GAPPS In terminal 1 I get waydroid session start [gbinder] Service manager /dev/binder has appeared [gbinder] WARNING: Service manager /dev/binder has died In terminal 2 I get aydroid show-full-ui [11:59:53] Failed to get service waydroidplatform, trying again... [11:59:54] Failed to get service waydroidplatform, trying again... [11:59:55] Failed to get service waydroidplatform, trying again... [11:59:56] Failed to get service waydroidplatform, trying again... [11:59:57] Failed to get service waydroidplatform, trying again... [11:59:58] Failed to get service waydroidplatform, trying again... [11:59:59] Failed to get service waydroidplatform, trying again... [12:00:00] Failed to get service waydroidplatform, trying again... [12:00:01] Failed to get service waydroidplatform, trying again... [12:00:02] Failed to get service waydroidplatform, trying again... ^CTraceback (most recent call last): File "/usr/bin/waydroid", line 9, in <module> sys.exit(tools.main()) File "/usr/share/waydroid/tools/__init__.py", line 111, in main actions.app_manager.showFullUI(args) File "/usr/share/waydroid/tools/actions/app_manager.py", line 118, in showFullUI maybeLaunchLater(args, showFullUI, justShow) File "/usr/share/waydroid/tools/actions/app_manager.py", line 53, in maybeLaunchLater launchNow() File "/usr/share/waydroid/tools/actions/app_manager.py", line 108, in justShow platformService = IPlatform.get_service(args) File "/usr/share/waydroid/tools/interfaces/IPlatform.py", line 309, in get_service time.sleep(1) KeyboardInterrupt I will try updating dkms-anbox latter
The same with new dkms-anbox, sorry I can't help more on this bug, but I made a report to fix dkms-anbox
@kanatec: thank you for your tests, I would say that after having downloaded the GAPPS, you should edit the config files inside /var/lib/waydroid a) b) etc... I clearly remember having the same errors as you quoted!
(In reply to Chris Denice from comment #26) > @kanatec: thank you for your tests, I would say that after having downloaded > the GAPPS, you should edit the config files inside /var/lib/waydroid a) b) > etc... > > I clearly remember having the same errors as you quoted! I think the only I miss is the grub parameter, I'll try again with that
(In reply to Chris Denice from comment #26) > @kanatec: thank you for your tests, I would say that after having downloaded > the GAPPS, you should edit the config files inside /var/lib/waydroid a) b) > etc... > > I clearly remember having the same errors as you quoted! Good news: With the kernel option and my changes to dkms-anbox don't need to touch /dev/binder and /dev/binder don't die Bad news: Still fail, perhaps we must update to waydroid 1.4.2 and test again I found a curious workaround to error (lock/unlock screen https://github.com/waydroid/waydroid/issues/282#issuecomment-1451590219) but I can't apply it, once start to fail take a lot of resources and I most end the process on terminal 2 and run, waydroid session stop Perhaps It's also a hardware limitation, I don't know
*** Bug 32522 has been marked as a duplicate of this bug. ***
CC: (none) => saveurlinux
what I did is: in /etc/default/grub, i added to GRUB_CMDLINE_LINUX_DEFAULT: psi=1 Reboot look if binder_linux is load: lsmod | grep binder_linux it was not I loaded: modprobe binder_linux look if ashmem_linux is load, it was not try to load it but was not found modprobe ashmem_linux modprobe: FATAL: Module ashmem_linux not found in directory /lib/modules/6.4.16-desktop-3.mga9 init waydroid: waydroid init > 07:52:05] Downloading https://sourceforge.net/projects/waydroid/files/images/system/lineage/waydroid_x86_64/lineage-18.1-20231111-VANILLA-waydroid_x86_64-system.zip/download >[Downloading] 766.77 MB/767.07 MB 38419.3 kbps(approx.)[07:52:28] Validating system image > [07:52:28] Extracting to /var/lib/waydroid/images > [07:52:36] Downloading https://sourceforge.net/projects/waydroid/files/images/vendor/waydroid_x86_64/lineage-18.1-20231111-MAINLINE-waydroid_x86_64-vendor.zip/download [Downloading] 177.67 MB/177.87 MB 19695.27 kbps(approx.)[07:52:45] Validating vendor image > [07:52:45] Extracting to /var/lib/waydroid/images as normal user and under plasma wayland, tryed to launch waydroid: waydroid session start nothing happend, in the log I read: tail -f /var/lib/waydroid/waydroid.log > Save session config: /var/lib/waydroid/session.cfg > (116330) [08:05:42] UserMonitor service is not even started > (116330) [08:05:42] Clipboard service is not even started
(In reply to david Cossé from comment #30) You miss some steps, check comment#1
(In reply to katnatek from comment #31) > (In reply to david Cossé from comment #30) > You miss some steps, check comment#1 (In reply to katnatek from comment #31) > (In reply to david Cossé from comment #30) > You miss some steps, check comment#1 Yes it works now What I missed up is to allowed updates_testing to be able to install python3-gbinder At first I did not have to do the following steps: > 4) In a root terminal > > * set permission of the devices present under /dev/binderfs/ to 666: > > chmod 666 /dev/binderfs/* > > * make a simlink: > > ln -s /dev/binderfs/anbox-binder /dev/binder As I didn't have /dev/binderfs/ folder What I had to do and it is not describe in comment#1 is to manually install the devel kernel package that suit the current running kernel and reinstall dkms-anbox as it world not automatically build I also have to manually load binder_linux module and I had in /dev folder a file /dev/binder then I could follow the tuto But after reboot things are different ! I do not have anymore the /dev/binder file I have to do systemctl start waydroid-container chmod 666 /dev/binderfs/* ln -s /dev/binderfs/anbox-binder /dev/binder before to be able to run as normal user waydroid session start
(In reply to david Cossé from comment #32) > (In reply to katnatek from comment #31) > > (In reply to david Cossé from comment #30) > > You miss some steps, check comment#1 > > (In reply to katnatek from comment #31) > > (In reply to david Cossé from comment #30) > > You miss some steps, check comment#1 > > Yes it works now > What I missed up is to allowed updates_testing to be able to install > python3-gbinder > > At first I did not have to do the following steps: > > 4) In a root terminal > > > > * set permission of the devices present under /dev/binderfs/ to 666: > > > > chmod 666 /dev/binderfs/* > > > > * make a simlink: > > > > ln -s /dev/binderfs/anbox-binder /dev/binder > > As I didn't have /dev/binderfs/ folder > > What I had to do and it is not describe in comment#1 is to manually install > the devel kernel package that suit the current running kernel > and reinstall dkms-anbox as it world not automatically build > Usually the devel flavour is required when you install for first time dkms > I also have to manually load binder_linux module > and I had in /dev folder a file > /dev/binder > Is reported in other test in this report and in bug#32496
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=32496
CC: (none) => mageia
I test again with the packages of https://bugs.mageia.org/show_bug.cgi?id=32687#c8 and https://bugs.mageia.org/show_bug.cgi?id=32496#c16 Is not needed anymore touch the binder devices Still is needed add psi=1 to kernel parameters Still need to edit /var/lib/waydroid/lxc/waydroid/config Still have the issues in comment#c24 with my "new" x86_64 system, but I don't understand how to make the workaround (I did think they mean the desktop screen, but is not so) And even I have to disconnect and reconnect the network because the network of this system dies after the error :(
Update advisory: ------------------ python3-gbinder and libgbinder packages updated to latest version allowing waydroid to run on mga9. Updated packages: ------------------ RPMS: i586: libgbinder-devel-1.1.34-1.mga9.i586.rpm libgbinder1-1.1.34-1.mga9.i586.rpm python3-gbinder-1.1.2-2.mga9.i586.rpm x86_64: lib64gbinder-devel-1.1.34-1.mga9.x86_64.rpm lib64gbinder1-1.1.34-1.mga9.x86_64.rpm python3-gbinder-1.1.2-2.mga9.x86_64.rpm SRPMS: libgbinder-1.1.34-1.mga9.src.rpm python-gbinder-1.1.2-2.mga9.src.rpm
Status comment: The procedure is in comment 1, but the advisory there will need to be replaced => The procedure is in comment 1, new advisory and packages in comment#34
I find new python3-gbinder package and update and make some changes recommended here https://wiki.archlinux.org/title/Waydroid#Software_rendering Now I can start waydroid (I use the vanilla image), I need to test again without the changes for software rendering and with the GAPPS image but it works!
I still lost the network after run and close waydroid but perhaps is just an issue in my hardware
Interesting with the GAPPS image the browser can't connect to internet and with the VANILLA I can surf the web
Advisory updated to match comment 35. Is the "feedback" keyword still needed?
Keywords: (none) => advisory
(In reply to Marja Van Waes from comment #39) > Advisory updated to match comment 35. > > Is the "feedback" keyword still needed? I think not, but I add depends on other bugs related
Depends on: (none) => 32687, 32496Keywords: feedback => (none)
I wished I found these bugs sooner, I've got bitten with some of the bugs described on comment 1. Just to add: It's very inconvenient not to know what hardware is really compatible with the the android images we find pre-built. I was advised to use x86 images, but apparently for sse2, it's not suitable either. journald tells something got wrong. But I just know it won't work. systemd-coredump[690520]: [🡕] Process 690493 (init) of user 0 dumped core. Also don't use grep -R in /var/lib/waydroid or alias grep='grep --devices=skip --color' maybe.
CC: (none) => geex+mageia
We must add a page in the wiki to document the steps to try make waydroid works once this updates become official, perhaps we can import some things from the archlinux wiki like https://wiki.archlinux.org/title/Waydroid#Software_rendering and https://wiki.archlinux.org/title/Waydroid#Troubleshooting Remember that need the packages in comment#35 , the packages in https://bugs.mageia.org/show_bug.cgi?id=32687#c8 and the current version of dkms-anbox already in updates https://bugs.mageia.org/show_bug.cgi?id=32496#c16 Preparation installl or start a wayland session, for plasma plasma-workspace-wayland Add psi=1 to kernel options https://wiki.mageia.org/en/How_to_set_up_kernel_options Install waydroid Reboot you system In a root terminal systemctl start waydroid-container waydroid first-launch A menu appears, pick up one of the images, I have issues with the network in the named "GAPP" (the one named VANILLA is reported as bugged, but I have network on it), (perhaps the images delivered depend on the detected hardware) Previous step downloads many things that will be put into /var/lib/waydroid/ Now, we fix more bugs that are not on mageia but upstreams: a) Edit the file "/var/lib/waydroid/lxc/waydroid/config" Comment that line (add a # before) #lxc.apparmor.profile = unconfined b) As root, restart the container service: systemctl restart waydroid-container c) As user, in a terminal start a session waydroid session start d) As user, in another terminal, start the show waydroid show-full-ui Good luck, works for me (tm). NB: waydroid does not (yet?) support bluetooth, so long for the traxxas charger
Status comment: The procedure is in comment 1, new advisory and packages in comment#34 => The procedure is in comment 42, new advisory and packages in comment#34
HP Pavillion Adding psi=1 to kernel options of reFind blocks wifi completely and this laptop is wifi-only, looking for another way.
CC: (none) => herman.viaene
On Lenovo B50 Same problem after reboot and made sure the changes in the files are there. In the log I see: % ln -s /dev/binderfs/anbox-hwbinder /dev/binderfs/anbox-vndbinder /dev/binderfs/binder /dev/binderfs/binder-control /dev/ ln: failed to create symbolic link '/dev/binder': File exists and then later lxc-start: waydroid: ../src/lxc/conf.c: run_buffer: 322 Script exited with status 126 lxc-start: waydroid: ../src/lxc/start.c: lxc_end: 985 Failed to run lxc.hook.post-stop for container "waydroid"
(In reply to Herman Viaene from comment #44) > On Lenovo B50 > Same problem after reboot and made sure the changes in the files are there. > In the log I see: > > % ln -s /dev/binderfs/anbox-hwbinder /dev/binderfs/anbox-vndbinder > /dev/binderfs/binder /dev/binderfs/binder-control /dev/ > ln: failed to create symbolic link '/dev/binder': File exists > > and then later > lxc-start: waydroid: ../src/lxc/conf.c: run_buffer: 322 Script exited with > status 126 > lxc-start: waydroid: ../src/lxc/start.c: lxc_end: 985 Failed to run > lxc.hook.post-stop for container "waydroid" If you see the updated instructions in comment#42 , is no longer necessary to make that step Did you use the lxc and binder packages in testing?, if you have current lxc packages they have a bug liblxc-devel-5.0.3-1.mga9 liblxc1-5.0.3-1.mga9 lib64lxc-devel-5.0.3-1.mga9 lib64lxc1-5.0.3-1.mga9 lxc-5.0.3-1.mga9 lxc-doc-5.0.3-1.mga9.noarch.rpm i586: libgbinder-devel-1.1.34-1.mga9.i586.rpm libgbinder1-1.1.34-1.mga9.i586.rpm python3-gbinder-1.1.2-2.mga9.i586.rpm x86_64: lib64gbinder-devel-1.1.34-1.mga9.x86_64.rpm lib64gbinder1-1.1.34-1.mga9.x86_64.rpm python3-gbinder-1.1.2-2.mga9.x86_64.rpm And one last thing, this must be used in wayland session
dkms-anbox update request: Bug 32797
Depends on: (none) => 32797CC: (none) => fri
This is nightmare never have get it working.. Would be very usefull if getting it working...
Sending this back to Chris Denice until the dkms-anbox and other issues can be resolved. It just is not ready for QA yet.
Assignee: qa-bugs => eatdirt
https://wiki.mageia.org/en/Mageia_9_Errata#Various_software
Whiteboard: (none) => IN_ERRATA9
Let's start again from scratch. You need: * kernel version >= 6.6 * waydroid version 1.4.2 on core/updates_testing * lib64gbinder1-1.1.34 on core/updates_testing * python3-gbinder-1.1.2 on core/updates_testing * Plasma running on wayland NB: remove a possible old directory /var/lib/waydroid To test, hopefully a bit simpler than before, up to the (waydroid upstream bugs) 0) Boot a kernel 6.6 with the option "psi=1" 1) Install the waydroid package of updates_testing (1.4.2), check out the correct gbinder packages are also installed 2) As root, start the container systemctl start waydroid-container 3) Install the image (GAPPS) using the menu: waydroid first-launch 4) After the image is installed, edit the file "/var/lib/waydroid/lxc/waydroid/config" Comment that line (add a # before) #lxc.apparmor.profile = unconfined 5) As root, restart the container systemctl restart waydroid-container 6) As *an user* waydroid show-full-ui This is working for me! Good luck folks :) --------------- The packages required for this update advisory are: RPMS: i586: libgbinder-devel-1.1.34-1.mga9.i586.rpm libgbinder1-1.1.34-1.mga9.i586.rpm python3-gbinder-1.1.2-2.mga9.i586.rpm x86_64: lib64gbinder-devel-1.1.34-1.mga9.x86_64.rpm lib64gbinder1-1.1.34-1.mga9.x86_64.rpm python3-gbinder-1.1.2-2.mga9.x86_64.rpm noarch: waydroid-1.4.2-1.mga9.noarch.rpm SRPMS: libgbinder-1.1.34-1.mga9.src.rpm python-gbinder-1.1.2-2.mga9.src.rpm waydroid-1.4.2-1.mga9.src.rpm
(In reply to Chris Denice from comment #50) > Let's start again from scratch. > > You need: > > * kernel version >= 6.6 > * waydroid version 1.4.2 on core/updates_testing > * lib64gbinder1-1.1.34 on core/updates_testing > * python3-gbinder-1.1.2 on core/updates_testing > * Plasma running on wayland > > NB: remove a possible old directory /var/lib/waydroid > > To test, hopefully a bit simpler than before, up to the (waydroid upstream > bugs) > > 0) Boot a kernel 6.6 with the option "psi=1" > > 1) Install the waydroid package of updates_testing (1.4.2), check out the > correct gbinder packages are also installed > > 2) As root, start the container > systemctl start waydroid-container > > 3) Install the image (GAPPS) using the menu: > waydroid first-launch > > 4) After the image is installed, edit the file > "/var/lib/waydroid/lxc/waydroid/config" > > Comment that line (add a # before) > #lxc.apparmor.profile = unconfined > > 5) As root, restart the container > systemctl restart waydroid-container > > 6) As *an user* > > waydroid show-full-ui > > > This is working for me! Good luck folks :) > > --------------- > The packages required for this update advisory are: > > RPMS: > i586: > libgbinder-devel-1.1.34-1.mga9.i586.rpm > libgbinder1-1.1.34-1.mga9.i586.rpm > python3-gbinder-1.1.2-2.mga9.i586.rpm > > x86_64: > lib64gbinder-devel-1.1.34-1.mga9.x86_64.rpm > lib64gbinder1-1.1.34-1.mga9.x86_64.rpm > python3-gbinder-1.1.2-2.mga9.x86_64.rpm > > noarch: > waydroid-1.4.2-1.mga9.noarch.rpm > > > SRPMS: > libgbinder-1.1.34-1.mga9.src.rpm > python-gbinder-1.1.2-2.mga9.src.rpm > waydroid-1.4.2-1.mga9.src.rpm Due the issues with current version of lxc https://bugs.mageia.org/show_bug.cgi?id=32687 is recommended before the test remove the current lxc https://bugs.mageia.org/show_bug.cgi?id=32687#c10 and add to the previous list this packages from https://bugs.mageia.org/show_bug.cgi?id=32687#c8 i586: liblxc-devel-5.0.3-1.mga9.i586.rpm liblxc1-5.0.3-1.mga9.i586.rpm lxc-5.0.3-1.mga9.i586.rpm lxc-doc-5.0.3-1.mga9.noarch.rpm x86_64: lib64lxc-devel-5.0.3-1.mga9.x86_64.rpm lib64lxc1-5.0.3-1.mga9.x86_64.rpm lxc-5.0.3-1.mga9.x86_64.rpm lxc-doc-5.0.3-1.mga9.noarch.rpm
Keywords: advisory => (none)
Status comment: The procedure is in comment 42, new advisory and packages in comment#34 => The procedure is in comment 50, packages in comment 50 y 51
I assume: § For kernel 6.6.x, dkms-anbox must be uninstalled Closed: Bug 32797 - dkms-anbox need updating for kernel 6.6 § Waydroid is only intended to work for kernel 6.6+ ? § Per comment 50, ready for QA
Source RPM: waydroid-1.3.2-1.mga9.src.rpm => libgbinder, python-gbinder, waydroid-1.3.2-1.mga9.src.rpmSee Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=32797Assignee: eatdirt => qa-bugs
> Waydroid is only intended to work for kernel 6.6+ ? No necessarily, but if you're using kernel < 6.6, you will need to install dkms-anbox and toy with my earliest procedure. Since almost no-one was able to reproduce my working steps, let's say that, yes, waydroid is going to be tested for kernel >=6.6 only :)
So, while this is being tested as working with kernels 6.6 and above, and we have left dkms-anbox in place for those using kernels below 6.6, what do we do for those who, say, install MGA9 today from the netinstall iso, (which will install only kernel 6.6.14-2) and then decide to try waydroid because it sounds interesting - only to have dkms-anbox make their systems unusable? I'm thinking of new users, inexperienced in using Mageia. *I* could get myself out of that predicament with little trouble, but then I'm not exactly an inexperienced Mageia user.
Let's start by testing waydroid for kernel 6.6. The new users won't have dkms-anbox installed because it is not triggered anymore by waydroid installed. And, we could have another work on dkms-anbox to prevent its installation for kernel-6.6, although the bug you're mentioning is likely to be fixed upstream soon. Let us try to not mix issues now that we have put dkms-anbox out of the current problem!
Making the dkms-android package to conflict kernel 6.6+ sounds good. But if really fixed soon for kernel 6.6+ then wait a little...
Tested in Real Hardware Magei 9 x86_64 Before test remove dkms-anbox , current waydroid make some cleaning as root rm -rf /var/lib/waydroid rm -rfv /home/katnatek/waydroid /home/katnatek/.share/waydroid /home/katnatek/.local/share/applications/*aydroid* /home/katnatek/.local/share/waydroid Reboot on kernel desktop with psi=1 Make sure I have all needed packages in qarepo Install waydroid Follow steps in comment#50 In step 6) As *an user* waydroid show-full-ui waydroid works navigation works install an apk works sound works Side note vanilla image fail to install After close the application, still have to disconnect and reconnect the network from draknetcenter because I lose the internet For me is as good as was with dkms-anbox in kernel 6.6.14 server or in kernel desktop 6.5
After update packages in bug#32838 still works
Thanks Katnatek!
Advisory updated to the SRPMs from comment 50
Chris Denice 2024-02-13 00:35:52 CET Let's start again from scratch. You need: * UNINSTALL dkms-anbox before boot on kernel 6.6 if you are under kernel 6.5 and you test before waydroid. * kernel version >= 6.6 * waydroid version 1.4.2 on core/updates_testing * lib64gbinder1-1.1.34 on core/updates_testing * python3-gbinder-1.1.2 on core/updates_testing * Plasma running on wayland NB: remove a possible old directory /var/lib/waydroid To test, hopefully a bit simpler than before, up to the (waydroid upstream bugs) 0) Boot a kernel 6.6 with the option "psi=1" 1) Install the waydroid package of updates_testing (1.4.2), check out the correct gbinder packages are also installed 2) As root, start the container systemctl start waydroid-container 3) Install the image (GAPPS) using the menu: waydroid first-launch 4) After the image is installed, edit the file "/var/lib/waydroid/lxc/waydroid/config" Comment that line (add a # before) #lxc.apparmor.profile = unconfined 5) As root, restart the container systemctl restart waydroid-container 6) As *an user* waydroid show-full-ui This is working for me! Good luck folks :) --------------- The packages required for this update advisory are: RPMS: i586: libgbinder-devel-1.1.34-1.mga9.i586.rpm libgbinder1-1.1.34-1.mga9.i586.rpm python3-gbinder-1.1.2-2.mga9.i586.rpm liblxc-devel-5.0.3-1.mga9.i586.rpm liblxc1-5.0.3-1.mga9.i586.rpm lxc-5.0.3-1.mga9.i586.rpm lxc-doc-5.0.3-1.mga9.noarch.rpm x86_64: lib64gbinder-devel-1.1.34-1.mga9.x86_64.rpm lib64gbinder1-1.1.34-1.mga9.x86_64.rpm python3-gbinder-1.1.2-2.mga9.x86_64.rpm lib64lxc-devel-5.0.3-1.mga9.x86_64.rpm lib64lxc1-5.0.3-1.mga9.x86_64.rpm lxc-5.0.3-1.mga9.x86_64.rpm lxc-doc-5.0.3-1.mga9.noarch.rpm noarch: waydroid-1.4.2-1.mga9.noarch.rpm SRPMS: libgbinder-1.1.34-1.mga9.src.rpm python-gbinder-1.1.2-2.mga9.src.rpm waydroid-1.4.2-1.mga9.src.rpm
Status comment: The procedure is in comment 50, packages in comment 50 y 51 => The procedure and required packages in comment 61
@Chris Denice I add the note of unistall dkms-anbox before test with kernel 6.6, just because a user fall in dkms-anbox bug in a VM
Progress in Bug 32797 - dkms-anbox need updating for kernel 6.6 It do seem we need a wiki page for how to use Waydroid.
Status comment: The procedure and required packages in comment 61 => Usage in comment 61, would be nice as Wiki page
@Chris Denice, due the changes in kernel desktop 6.6.17-3 is needed add to waydroid spec a binder.conf file (or the name you like) with binder_linux And install the file in %{_modulesloaddir}
@Chris Denice, what you think, we push this update now, but you will need to adjust waydroid again when new kernel arrive or you make that adjust before ?
Let's wait a bit to test with kernel 6.6.17, I'll redo a full test on my side.
waydroid-1.4.2-2.mga9.src.rpm landing on updates_testing, designed to work for kernels 6.6.18! If this does not work, please report ls -l /dev/binderfs/* Thank you. NB: no need to add anything in modprobe*, everything is triggered by mounting the binderfs by the kernel.
Maybe the config created /var/lib/waydroid/lxc/waydroid/config can be patched to have by default the "lxc.apparmor.profile = unconfined" commented.
CC: (none) => ghibomgx
I don't know how to do that, and it will be sure to fail at some point. Indeed, these guys are created when downloading the image, we do not ship these files, they are from waydroid guys. To be honest, I really don't care about waydroid, I just wanted to control my stupid traxxas RC charger, and, at the end, waydroid is not even supporting bluetooth. The good side is that it allowed me to see that it was seriously broken on mga, now it works with minimal effort. If this is really still working for 6.6.18, let's push this update. Anyone with interests can now make it work (the pb with lxc is known upstream, why they don't fix it is out of our light-cone) :)
Let's start again from scratch. You need: * UNINSTALL dkms-anbox before if you will test on kernel 6.6.14 and, if you are under kernel 6.5 and you test before waydroid. * kernel version >= 6.6.18 (to confirm) * waydroid-1.4.2-2.mga9 on core/updates_testing * lib64gbinder1-1.1.34 on core/updates_testing * python3-gbinder-1.1.2 on core/updates_testing * lxc-5.0.3-1.mga9, See https://bugs.mageia.org/show_bug.cgi?id=32687#c10 if ypu have previous version of lxc before * Plasma running on wayland NB: remove a possible old directory /var/lib/waydroid To test, hopefully a bit simpler than before, up to the (waydroid upstream bugs) 0) Boot a kernel 6.6 with the option "psi=1" 1) Install the waydroid package of updates_testing (1.4.2), check out the correct gbinder packages are also installed 2) As root, start the container systemctl start waydroid-container 3) Install the image (GAPPS) using the menu: waydroid first-launch 4) After the image is installed, edit the file "/var/lib/waydroid/lxc/waydroid/config" Comment that line (add a # before) #lxc.apparmor.profile = unconfined 5) As root, restart the container systemctl restart waydroid-container 6) As *an user* waydroid show-full-ui This is working for me! Good luck folks :) --------------- The packages required for this update advisory are: RPMS: i586: libgbinder-devel-1.1.34-1.mga9.i586.rpm libgbinder1-1.1.34-1.mga9.i586.rpm python3-gbinder-1.1.2-2.mga9.i586.rpm x86_64: lib64gbinder-devel-1.1.34-1.mga9.x86_64.rpm lib64gbinder1-1.1.34-1.mga9.x86_64.rpm python3-gbinder-1.1.2-2.mga9.x86_64.rpm noarch: waydroid-1.4.2-2.mga9.noarch.rpm SRPMS: libgbinder-1.1.34-1.mga9.src.rpm python-gbinder-1.1.2-2.mga9.src.rpm waydroid-1.4.2-2.mga9.mga9.src.rpm
Status comment: Usage in comment 61, would be nice as Wiki page => Usage in comment 70, would be nice as Wiki page
Test related to this bug Mageia 9 x86_64 Plasma session uname -a Linux phoenix 6.6.18-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC Sat Feb 24 02:17:35 UTC 2024 x86_64 GNU/Linux rpm -q dkms-anbox dkms-anbox-0.0.3-6.mga9 (custom build) Not panics and waydroid works (I not perform cleaning, just test the image I get in previous test)
Test related to this bug Mageia 9 x86_64 Plasma session uname -a Linux phoenix 6.6.14-desktop-2.mga9 #1 SMP PREEMPT_DYNAMIC Tue Jan 30 15:48:16 UTC 2024 x86_64 GNU/Linux LC_ALL=C rpm -q dkms-anbox package dkms-anbox is not installed Waydroid works here too, wait to 6.6.18 is not necessary
Indeed: kernel-desktop-6.6.18-1.mga9 works regardless of any dkms-anbox kernel-desktop-6.6.14-1.mga9 works only without dkms-anbox
(In reply to Chris Denice from comment #69) > I don't know how to do that, and it will be sure to fail at some point. > Indeed, these guys are created when downloading the image, we do not ship > these files, they are from waydroid OK. Apparently the config is created from profiles not from the downloaded image. This patch in attach should change the lxc.apparmor.profile line in config.
Created attachment 14421 [details] fix for default config
Test related to this bug Mageia 9 x86_64 Plasma session uname -a Linux phoenix 6.6.18-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC Sat Feb 24 02:17:35 UTC 2024 x86_64 GNU/Linux LC_ALL=C rpm -q dkms-anbox package dkms-anbox is not installed Works here, wait to update the advisory in case Chris Denice want to include the Giuseppe patch in another build of waydroid
> fix for default config Good Job (TM)!! waydroid-1.4.2-3.mga9 landing in update_testings!!
(In reply to Chris Denice from comment #77) > > fix for default config > > Good Job (TM)!! > > waydroid-1.4.2-3.mga9 landing in update_testings!! The advisory in SVN has been updated accordingly
BTW, the image I tried that working was vanilla, in fact in /var/lib/waydroid/config there is the entry: system_ota = https://ota.waydro.id/system/lineage/waydroid_x86_64/VANILLA.json I used that (as it was the default one) before learning there was another image that could be used: GAPPS (which I guess has just more apps). Curiosly with AnTuTu 10.2 is gives a score of 610000, which is pretty high for an android emulator (but score 0 for GPU). Within waydroid also it proposed the update of the images to current, and worked. I think we can add the upgraded notes of comments #70 to some wiki pages, so other mageia users can try quickly. For Xorg users that do not want to start Xwayland, the simple extra step is to to install package weston, and to run step 3) and step 6) [step 3) is also as user] within a 'weston''s terminal, having started the command 'weston' from command line.
Let's start again from scratch. You need: * UNINSTALL dkms-anbox before if you will test on kernel 6.6.14 and, if you are under kernel 6.5 and you test before waydroid. * kernel desktop version >= 6.6.14 * waydroid-1.4.2-3.mga9 on core/updates_testing * lib64gbinder1-1.1.34 on core/updates_testing * python3-gbinder-1.1.2 on core/updates_testing * lxc-5.0.3-1.mga9, See https://bugs.mageia.org/show_bug.cgi?id=32687#c10 if ypu have previous version of lxc before * Plasma (GNOME?) running on wayland or in X11/Xorg session install weston (comment#79) NB: remove a possible old directory /var/lib/waydroid To test, hopefully a bit simpler than before 0) From Giuseppe "A little bit difficult to get the networking: a quick workaround is to disable shorewall" (note from katnatek I already have firewall disabled) 1) Boot a kernel desktop 6.6 with the option "psi=1" 2) Install the waydroid package of updates_testing (1.4.2), check out the correct gbinder packages are also installed 3) As root, start the container systemctl start waydroid-container 4) Install the image (GAPPS) using the menu (run as user): waydroid first-launch 5) If all works fine, the waydroid window should start automatically ! 5.1) If not make some cleaning (see comment#57) repeat step 4 ,test with VANILLA image 5.2) If you lost connection, run MCC -> Network & Internet -> Network center , disconnect and connect the network This is working for me! Good luck folks :) --------------- The packages required for this update advisory are: RPMS: i586: libgbinder-devel-1.1.34-1.mga9.i586.rpm libgbinder1-1.1.34-1.mga9.i586.rpm python3-gbinder-1.1.2-2.mga9.i586.rpm x86_64: lib64gbinder-devel-1.1.34-1.mga9.x86_64.rpm lib64gbinder1-1.1.34-1.mga9.x86_64.rpm python3-gbinder-1.1.2-2.mga9.x86_64.rpm noarch: waydroid-1.4.2-3.mga9.noarch.rpm SRPMS: libgbinder-1.1.34-1.mga9.src.rpm python-gbinder-1.1.2-2.mga9.src.rpm waydroid-1.4.2-2.mga9.mga9.src.rpm
Let's start again from scratch. You need: * UNINSTALL dkms-anbox before if you will test on kernel 6.6.14 and, if you are under kernel 6.5 and you test before waydroid. * kernel desktop version >= 6.6.14 * waydroid-1.4.2-3.mga9 on core/updates_testing * lib64gbinder1-1.1.34 on core/updates_testing * python3-gbinder-1.1.2 on core/updates_testing * lxc-5.0.3-1.mga9, See https://bugs.mageia.org/show_bug.cgi?id=32687#c10 if ypu have previous version of lxc before * Plasma (GNOME?) running on wayland or in X11/Xorg session install weston (comment#79) NB: remove a possible old directory /var/lib/waydroid To test, hopefully a bit simpler than before 0) From Giuseppe "A little bit difficult to get the networking: a quick workaround is to disable shorewall" (note from katnatek I already have firewall disabled) 1) Boot a kernel desktop 6.6 with the option "psi=1" 2) Install the waydroid package of updates_testing (1.4.2), check out the correct gbinder packages are also installed 3) As root, start the container systemctl start waydroid-container 4) Install the image (GAPPS) using the menu (run as user): waydroid first-launch 5) If all works fine, the waydroid window should start automatically ! 5.1) If not make some cleaning (see comment#57) repeat step 4 ,test with VANILLA image 5.2) If you lost connection, run MCC -> Network & Internet -> Network center , disconnect and connect the network This is working for me! Good luck folks :) --------------- The packages required for this update advisory are: RPMS: i586: libgbinder-devel-1.1.34-1.mga9.i586.rpm libgbinder1-1.1.34-1.mga9.i586.rpm python3-gbinder-1.1.2-2.mga9.i586.rpm x86_64: lib64gbinder-devel-1.1.34-1.mga9.x86_64.rpm lib64gbinder1-1.1.34-1.mga9.x86_64.rpm python3-gbinder-1.1.2-2.mga9.x86_64.rpm noarch: waydroid-1.4.2-3.mga9.noarch.rpm SRPMS: libgbinder-1.1.34-1.mga9.src.rpm python-gbinder-1.1.2-2.mga9.src.rpm waydroid-1.4.2-3.mga9.mga9.src.rpm
Status comment: Usage in comment 70, would be nice as Wiki page => Usage in comment 81, would be nice as Wiki page
Already tested and I modify the steps with the results that I see in the test Is OK for me Mageia 9 x86_64 Plasma Wayland
Whiteboard: IN_ERRATA9 => IN_ERRATA9,MGA9-64-OK
Well done guys!
Validating, at last...
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0074.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED