NetInstall Installation step failed
| Proyecto: | Trisquel |
| Versión: | 8.0 |
| Componente: | Installer |
| Categoría: | informe de fallo |
| Prioridad: | normal |
| Asignado: | No asignado |
| Estado: | closed |
Saltar a:
While installing Trisquel 8 in qemu with qemu-system-x86_64 -cdrom trisquel-netinst_8.0-20170410_amd64.iso -hdd HDD.img -m 1024
I went through the installer all seemed fine and then i got to the "select and install software" part of the installer.
I selected no automatic updates and then i was prompted with a [!] Software Selection window.
I selected all the desktop environments (see attached) and hit return.
I then met the attached error screen.
I repeated the "select and install software" part of the installer twice with the same result.
I will see if the problem persists if i try running the installer again from the start.
This is the ISO i downloaded (http://jenkins.trisquel.info/makeiso/iso/trisquel-netinst_8.0-20170410_amd64.iso)
linked from this page: https://listas.trisquel.info/pipermail/trisquel-devel/2017-December/001085.html
| Adjunto | Tamaño |
|---|---|
| snapshot2.png | 114.32 KB |
| error_screen.png | 67.58 KB |
- Inicie sesión o regístrese para enviar comentarios
I have run the installer from the start again with the same result
I have repeated the select and install software step
but this time i only selected the Trisquel desktop environment and it started to download the packages and seemed fine
until it then crashed with the same error screen.
Has anyone else had such problems?
Yes, with the December ISO I had a similar problem using the text installer. See my comment here. https://trisquel.info/en/issues/23467
I have not been able to run live or install any of the Trisquel 8 ISOs since the one from last June.
This is because the trisquel-mini-data package for flidas doesn't yet exist, so Trisquel Mini isn't actually installable.
@quidam fixed this before release. I tested it then. Please re-open the bug with exact steps to recreate the problem if you still have it.
Automatically closed -- issue fixed for 2 weeks with no activity.