Following the instructions in this thread
https://ubuntuforums.org/showthread.php?t=2382832 to point
/etc/apt/sources.list to the moved zesty sources allows the process to
resume.
Surely the upgrade script could be modified to check if the current rev
sources have been move to "old" and re-point
I also have this problem trying to upgrade from 17.04 to 17.10.
I do not have ubuntu-mate-core or ubuntu-mate-desktop or kubuntu-desktop
installed.
The file /var/log/dist-upgrade/apt.log contains 1212 lines and 145 references
to "broken" but no explanation as to why it failed.
** Attachment
I also have this bug running 16.04 (4.4.0-34-generic).
Very annoying to have your network just fall out of the sky randomly
when your home directories are remote.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Fell over during Software Updater
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture:
Public bug reported:
Probably the PAE issue I reported before again
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-23-generic (not installed)
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
Uname: Linux 4.2.0-22-generic i686
ApportVersion: 2.19.1-0ubuntu5
Working around the problem for now with this:
cat /proc/cpuinfo | sed 's/flags\t*:/& pae/' > /tmp/cpuinfo_pae
sudo mount -o bind /tmp/cpuinfo_pae /proc/cpuinfo
sudo mount -o remount,ro,bind /proc/cpuinfo
But would like a more permanent solution
--
You received this bug
Public bug reported:
This machine (I believe) has PAE capabilities (Pentium-M), but 15.10 has become
very unforgiving of machines that don't report PAE flags in /proc/cpuinfo.
I had a royal pain in the behind upgrading from 15.04 (where --forcepae just
did the business) to 15.10 because this
A fix for 12.10 would be great, because I'm having this problem as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/868904
Title:
Redshift fails to start with session due to geoclue failure
To
I can confirm this in Quantal with LO 3.6.1 and that is has cleared with
the upgrade to 3.6.2.2. Needed a dist-upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1049025
Title:
Can't select
