Failure to finish creating Libertine container on OTA-3
-
I've tried repeatedly to create a Libertine container, both using the app in System, and in Terminal using
libertine-container-manager -v create -i focal -n "Focal Fossa"
After going through the usual long process of downloading, unpacking files etc, at the very end we get this:
E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/pool/main/g/gdk-pixbuf/libgdk-pixbuf2.0-common_2.40.0+dfsg-3ubuntu0.4_all.deb 400 Bad Request [IP: 185.125.190.36 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 0 to remove and 121 not to upgrade.
ChrootContainer.py:142: ERROR: create_libertine_container(): Failure installing 'humanity-icon-theme' during container creation
libertine-container-manager:126: ERROR: create():Failed to create container: 'destroy_libertine_container() missing 1 required positional argument: 'force''The package mentioned in the “Failed to fetch” error message,
libgdk-pixbuf2.0-common_2.40.0+dfsg-3ubuntu0.4_all.deb, is actually sitting in my Downloads folder after all that, so maybe it's the final chroot error that's fatal: Failure installing 'humanity-icon-theme'This was in both the stable channel and the release candidate channel. I am baffled and can't do any more about it by myself. Anyone here know how to fix it? Is it a problem with OTA-3?
-
@ancientsounds Do you set the screen to remain on while this is installing?
-
@Lakotaubp I think so ... In Battery Settings, “Lock When Idle” is set to “Never”
A bit of online research reveals that
“Failure installing 'humanity-icon-theme'”
is a very frequent, mysterious, and often fatal bug in building containers in e.g. docker -
Volla, after installing the last OTA update:
Tried to install a new Libertine container, both container name and password empty.
Result: endless spinning circle, nothing will be installed. Grey bar with "Installing 'Focal Fossa" is displayed. I waited 2 hours.
After a reboot spinning wheel persists and no way to stop/abort.Then I tried to install a container with a name and a password but it also didn't work.
Edit: found a way to stop by swipe the grey bar to right and select trash.
-
@Seven-of-nine It seems creating new containers on Libertine is broken at the moment. (I am on the devel channel).
EDIT:
Moved over to the stable channel and a new container is being created now, as we speak. Will report back on success / failure.EDIT2:
On the stable channel I was able to create a Libertine container. I did so on the command line via ADB. But it should work just the same from the UI. -
@arubislander Thank you very much for the hint!
I'm also on stable channel and with 'Settings/Updates' I updated EVERYTHING including all apps to the latest version and then rebooted the device twice.
After this it was possible to install a Libertine container, but it needed full an hour to download and install.
But by giving it time and waiting patiently it worked and now I have an empty but working container, will say container starts and some settings are available but no applications yet installed. -
@Seven-of-nine Glad you got it to work. Indeed the downloading and installing can take an inordinate amount of time, so patience is key.
Yes, containers start out pristine, with no installed apps listed, but some pre-installed under the hood. One that 'bleeds through' to the desktop is Vim. It comes with a launcher in regular Ubuntu, so shows up in the drawer in UT too. You cannot launch it from there though, so it is kind of taking up screen real estate. You could remove it, but that is more hassle than it is worth if you ask me.
-
@arubislander I have no vim at my drawer, and never had. Have only 'Terminal'. Do you mean this?
-
@Seven-of-nine No, I mean the two identical icons in this screen shot. I have two containers, hence two icons.
-
Oh, those were the days when I still used this beautiful system.
-
@arubislander I finally succeeded in creating a Libertine container on the Stable channel, with no repetition of the errors I had previously. So either the previously missing packages are now available again, or the network I was using was better for downloads
-
@ancientsounds said in Failure to finish creating Libertine container on OTA-3:
... the network I was using was better for downloads
Probably that.