If it had happened only once, I would call it a coincidence or result of another error (probably my fault, once I fiddle a lot with my kubuntu).
However, it happened twice in two different machines (PC, 64 bits). So, here is what happened:
I was upgrading from 15.04, but I had to leave the computers unattended. Coincidently, I got away from them while they were installing the packages (after downloading them).
When I came back, they were both locked. I unlocked the screen and the installation process was stuck on libsane-common (75% in one computer and 78% in the other). The windows was not responding to clicks. So, I rebooted both. They loaded perfectly fine (as nothing have ever happened), but I had to run dpkg --configure -a before using apt-get. One I did it, everything seems to be perfectly fine.
I cant imagine the reason why the installer would crash exactly at the same (apparently unimportant) point, but it seems to be a bug...
However, it happened twice in two different machines (PC, 64 bits). So, here is what happened:
I was upgrading from 15.04, but I had to leave the computers unattended. Coincidently, I got away from them while they were installing the packages (after downloading them).
When I came back, they were both locked. I unlocked the screen and the installation process was stuck on libsane-common (75% in one computer and 78% in the other). The windows was not responding to clicks. So, I rebooted both. They loaded perfectly fine (as nothing have ever happened), but I had to run dpkg --configure -a before using apt-get. One I did it, everything seems to be perfectly fine.
I cant imagine the reason why the installer would crash exactly at the same (apparently unimportant) point, but it seems to be a bug...
Comment