I tried to install ArchLabs (archlabs-2018.12.17.iso) on VirtualBox 6.0 twice and got an error during the actual installation:
ERROR: /bin/bash: error while loading shared libraries: libreadline.so.7: cannot open shared object file: No such file or directory
Is anyone aware of this problem? Did I anything wrong or is it a bug?
I tried to install it in virtualbox to see and I had no luck too, graphical glitch appears, forced extinction, and grub recovery at rebootā¦
try this:
I solved by not mounting my previous /var partition. It was causing all those problems.
if it does not work check if this package is described in this post
OP made me want to try again, this time in vmware
This is interesting, during the install it said that it couldnāt detect root, and in the middle of the process many things had failed to install
Also grub is here (that was not the case with virtualbox) but it wonāt detect the UUID of the virtual disk at reboot.
Iām not good enough to use Qemu, if someone wants to tryā¦
PS: This is not a call for help, I just wanted to share an experiment, maybe it could be interesting for the dev.
Edit:
This time I donāt use automatic partitionning
Iām now manually trying with a full /
No /boot or else
Error: Installation for i386-pc platform
Installation finished, without error (uh?)
Option āātarget=i386-pcā not recognized
hum ok letās what happens just after that.
no reboot or anything, it says that these /tmp/ai are deleted
I try a reboot, grub-rescue
Last Edit: Trying with Clover OS so you can see Iām not totally in fault, it (vmware) works.
I stop trying (had enough fun), you can try from your side.
Iāll have a look at it, seems the readline object file is out of date causing linkage issues. Well likely have another iso refresh with a few small fixes.
Ah, thatās weird. Iām at work for another few hours but once home Iāll see if I can figure out whatās going wrong.
Yeah. Been having this issue all day on both of my machines. VMWare Fusion and Workstation, both having the same "Error: device āā not found. Skipping fsck. canāt find UUIDā issue. Tried everything over multiple installs and cant get it to work in a vm.
It reassures me, I had the impression to have missed something or to have messed up with the partitionning
@kenokenobingo thatās just autism lel, I pretend more than I know.
@natemaia good courage to you
