Public bug reported:
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
libsane1:
Installed: 1.0.27-1~experimental3ubuntu1
Candidate: 1.0.27-1~experimental3ubuntu1
Version table:
*** 1.0.27-1~experimental3ubuntu1 500
500 http://us.archive.ubuntu.com/ubu
I did have a set of packages held back, I unheld them and the upgrade is
working properly. A message for something that simple might be easy to
integrate into the warning messages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Public bug reported:
Cannot upgrade to 17.04, 17.10, or 18.04 all give the same message.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.23
ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
NonfreeKer
It seems like this isn't the only bug reported upgrading Trusty to
Vivid. My unique difference is the chroot session and being on the
chromebook. Is there anyone having an issue going from Trusty to WIly? I
didn't have lts as the option, and it did not suggest Utopic. I would
imagine in that case i
Public bug reported:
Running Ubuntu 14.04 (Trusty) under crouton on a Chromebook Pixel(2015)
Edited the file /etc/update-manager/release-upgrades
replaced Prompt=lts by Prompt=normal
sudo do-release-upgrade
This was the output:
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [19
