I had already verified the media, but tried it again with different media and
got the same results.
I was using the btrfs option, still got the ubi-console warning and proceded
anyway. There was a grub failure.
I was able to chroot into the ssyem by adding the '@' subvolume to the mount
Public bug reported:
Same failure point (ubi-console creation) on different mobo, different media,
different daily build. (this was 13May2016).
There was a warning when the ubi-console step failed, with option to try again
or continue. tried twice with same results and continued ... files
Public bug reported:
I received a warning of potential crash after the installer correct
handled keyboard identification, but continued anyway and it crashed.
Iso checksum was OK.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.1
ProcVersionSignature: Ubuntu
Public bug reported:
Previous update asked me to correct missing dependencies for plymouth.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: plymouth 0.9.2-3ubuntu4
ProcVersionSignature: Ubuntu 4.3.0-2.11-lowlatency 4.3.0
Uname: Linux 4.3.0-2-lowlatency x86_64
ApportVersion:
Public bug reported:
Not much to see during shutdown logout. Have noticed that boot up is
much longer that usual sine upgrading to velvet.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: lyx 2.1.2-3
Uname: Linux 3.13.5-031305-generic x86_64
ApportVersion: 2.15.1-0ubuntu2
Architecture:
Public bug reported:
This happened during an aptitude update aptitude safe-upgrade -with-
full-resolver.
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: deluge-common 1.3.10-1
Uname: Linux 3.13.5-031305-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Fri Nov
Public bug reported:
Multiple errors after upgrading from 12.10 to 13.10. Lubuntu, after
announcing a group of error reports, allowed login, but no menu panel
appears. A right click exposes a menu (openbox?) that allows an instance
of lxterminal, but, little else. Had to start web browser from
We can close this one.
I had to add apt-build last year to use a package that was not even in
experimental repositories. I began to get errors about
bin-i386/Packages not found on updates/upgrades. I was surprised to
see that libc6 was installing both an AMD64 and and i386 version.
I solved the