open waydroid from system tray (as far as I can tell, this is identical to running waydroid session start and waydroid show-full-ui)
$ sudo python main.py install libhoudini
INFO: Resizing /var/lib/waydroid/images/system.img to 3330M
INFO: Mounting /var/lib/waydroid/images/system.img to /tmp/waydroid
ERROR: umount: /tmp/waydroid: target is busy.
Traceback (most recent call last):
File "/home/kayt/waydroid_script/main.py", line 343, in <module>
main()
File "/home/kayt/waydroid_script/main.py", line 336, in main
args.func(args)
File "/home/kayt/waydroid_script/main.py", line 103, in install_app
mount("system", copy_dir)
File "/home/kayt/waydroid_script/main.py", line 40, in mount
images.mount(img, mount_point)
File "/home/kayt/waydroid_script/tools/images.py", line 9, in mount
umount(mount_point, False)
File "/home/kayt/waydroid_script/tools/images.py", line 21, in umount
run(["umount", mount_point])
File "/home/kayt/waydroid_script/tools/helper.py", line 47, in run
raise subprocess.CalledProcessError(
subprocess.CalledProcessError: Command '['umount', '/tmp/waydroid']' returned non-zero exit status 32.
At which point waydroid closes and systemctl status waydroid-contianer shows that the container is dead.
I also noticed that the install script resizes system.img by +500M every time the script is run, like in #106, even after logging out/in.
I'm trying to install libhoudini and I get the above error every time I try to install it, or anything else.
12th Gen Intel Framework Laptop
NixOS 23.05
Kernel 6.1.35
Waydroid 1.3.4
Lineage 18.1 GAPPS
Steps to reproduce (from [Nix Wiki](https://nixos.wiki/wiki/WayDroid)):
/etc/nixos/configuration.nix
```
environment.systemPackages = [
pkgs.waydroid
];
{
virtualisation = {
waydroid.enable = true;
lxd.enable = true;
};
}
```
`sudo nixos-rebuild switch`
`sudo waydroid init -s GAPPS`
`sudo systemctl start waydroid-container`
open waydroid from system tray (as far as I can tell, this is identical to running `waydroid session start` and `waydroid show-full-ui`)
```bash
$ sudo python main.py install libhoudini
INFO: Resizing /var/lib/waydroid/images/system.img to 3330M
INFO: Mounting /var/lib/waydroid/images/system.img to /tmp/waydroid
ERROR: umount: /tmp/waydroid: target is busy.
Traceback (most recent call last):
File "/home/kayt/waydroid_script/main.py", line 343, in <module>
main()
File "/home/kayt/waydroid_script/main.py", line 336, in main
args.func(args)
File "/home/kayt/waydroid_script/main.py", line 103, in install_app
mount("system", copy_dir)
File "/home/kayt/waydroid_script/main.py", line 40, in mount
images.mount(img, mount_point)
File "/home/kayt/waydroid_script/tools/images.py", line 9, in mount
umount(mount_point, False)
File "/home/kayt/waydroid_script/tools/images.py", line 21, in umount
run(["umount", mount_point])
File "/home/kayt/waydroid_script/tools/helper.py", line 47, in run
raise subprocess.CalledProcessError(
subprocess.CalledProcessError: Command '['umount', '/tmp/waydroid']' returned non-zero exit status 32.
```
At which point waydroid closes and `systemctl status waydroid-contianer` shows that the container is dead.
I also noticed that the install script resizes system.img by +500M every time the script is run, like in #106, even after logging out/in.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I'm trying to install libhoudini and I get the above error every time I try to install it, or anything else.
12th Gen Intel Framework Laptop
NixOS 23.05
Kernel 6.1.35
Waydroid 1.3.4
Lineage 18.1 GAPPS
Steps to reproduce (from Nix Wiki):
/etc/nixos/configuration.nix
sudo nixos-rebuild switchsudo waydroid init -s GAPPSsudo systemctl start waydroid-containeropen waydroid from system tray (as far as I can tell, this is identical to running
waydroid session startandwaydroid show-full-ui)At which point waydroid closes and
systemctl status waydroid-contianershows that the container is dead.I also noticed that the install script resizes system.img by +500M every time the script is run, like in #106, even after logging out/in.