Installing on Bookworm/Pi5 fails

timrowledge

I've ust tried to install and run on a new Pi 5. Initially it complained becasue 'yad' could not be installed, but running the wget install snippet again claimed to have got past that. If I run the PPT tool from the system menu and try to view an IMG it starts, fails and eventually closes the window. Runnig'vdesktop' directly results in ``` desktop /home/tim/2023-12-05-raspios-bookworm-arm64-full.img Current config: VDESKTOP_BOOT_MODE: gui VDESKTOP_UMOUNT_ON_EXIT: yes VDESKTOP_USERNAME: pi VDESKTOP_PASSWORD: raspberry VDESKTOP_AUTO_LOGIN: yes VDESKTOP_MOUNTPOINT: /media/pi/vdesktop VDESKTOP_ENABLE_ROOTMOUNT: yes VDESKTOP_ENABLE_VIRGL: no VDESKTOP_LOCAL_BINARIES: yes VDESKTOP_NSPAWN_FLAGS: Message from Botspot: Comments >/dev/null. Just kidding! Questions or suggestions? https://www.raspberrypi.org/forums/viewtopic.php?&t=251757 Given /home/tim/2023-12-05-raspios-bookworm-arm64-full.img, running in disk image mode. Here's the loop device for it: /dev/loop2 cat: /media/pi/vdesktop/etc/machine-id: No such file or directory Machine IDs equal. (b7125ef90146405da5c533b078e65049) Changing machine id to 1f541e58f8e167fb79327640659482f7 /home/tim/Pi-Power-Tools/vdesktop/vdesktop: line 368: /media/pi/vdesktop/etc/machine-id: No such file or directory /home/tim/Pi-Power-Tools/vdesktop/vdesktop: line 369: /media/pi/vdesktop/var/lib/dbus/machine-id: No such file or directory img should be mounted, but /media/pi/vdesktop/bin does not exist! Hold on... Cleaning up... Almost done... Done! ``` Advice welcomed

Botspot

Vdesktop is known to not work on Bookworm or later .img versions of Bullseye unless you have booted them first on a real device. This is due to how PiOS no longer begins with a home directory, instead creating one on first boot. But in this case it looks like vdesktop completely failed to mount the img. You should check if the file is good. Use PPT to open the img in gparted to check the partitions. Please post a screenshot of this.

timrowledge

OK, I went to the 'Edit' and told it to install gparted, which *claimed* to have failed and told me to run 'sudo apt install' without any package name. Despite that, gparted appears to have installed ok and when retrying the 'Edit' it shows this  The error sign next to the boot partition alarmed me for a moment but your excellent information window says it's just that I have no fat32 tools installed.