At https://labwc.github.io/getting-started.html I found /usr/share/doc/labwc/ had the labwc config files, rc.xml, menu.xml, autostart, environment and themerc, which can be copied to ~/.config/labwc. rc.xml has a key binding for the foot terminal associated with [windows key][enter]. The foot package needed to be installed.
With foot installed and accessible from the key binding I was able to re-install the VirtualBox extensions but that did not improve performance. I posted on the labwc discussion board and was told QEMU seems to work just fine so labwc virtualization in general is not a problem.
Alacritty would never run and when I ran it from the foot terminal, I found it had some issues shown in this image: https://i.postimg.cc/MTW09Hyn/labwc-alacritty.gif.
Firefox was more extreme and terminated labwc when I ran it in the foot terminal. Errors shown here: https://i.postimg.cc/B6Mzgd1G/labwc-firefox.gif.
VM configuration shown here: https://i.postimg.cc/RFnfkPyC/labwc-config.gif.
I've posted a question about the errors on the labwc discussion board and will provide an update when a solution is identified.
With foot installed and accessible from the key binding I was able to re-install the VirtualBox extensions but that did not improve performance. I posted on the labwc discussion board and was told QEMU seems to work just fine so labwc virtualization in general is not a problem.
Alacritty would never run and when I ran it from the foot terminal, I found it had some issues shown in this image: https://i.postimg.cc/MTW09Hyn/labwc-alacritty.gif.
Firefox was more extreme and terminated labwc when I ran it in the foot terminal. Errors shown here: https://i.postimg.cc/B6Mzgd1G/labwc-firefox.gif.
VM configuration shown here: https://i.postimg.cc/RFnfkPyC/labwc-config.gif.
I've posted a question about the errors on the labwc discussion board and will provide an update when a solution is identified.
Statistics: Posted by CloisteredNeuron — 2024-06-05 06:09