Thanks. I eventually removed enough packages from the system to allow the
upgrade to work. It was a long time ago so I don't remember the details
anymore and I think I threw out my notes.
Since then, apt upgrades, including kernel upgrades, have been working
fine.
Just one more year, and we get
I've just noticed an additional problem - do-release-upgrade did not
restore third-party repositories to /etc/apt/sources.list, so all my
third party packages have silently stopped being updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks for checking. I have submitted the bug report. It is bug
#1902767.
On Tue, Nov 3, 2020 at 12:36 PM Brian Murray <1246...@bugs.launchpad.net>
wrote:
> Please submit a new bug using 'ubuntu-bug ubuntu-release-upgrader' as
> that will add log files which I can examine to help sort out the
>
Public bug reported:
This error comes up both before and after removing two ppas using ppa-
purge. Note that I am using a low-latency kernel with bionic. I would
suspect this but I upgraded another system running this kernel with no
problems.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package:
I added the PPA packages back in, reinstalled the related software, and
removed them with ppa-purge. Followed that with apt update, autoremove
and a necessary reboot. After all that, I got the same "unresolvable
problem" error when I tried to do-release-upgrade.
--
You received this bug
I added the PPA packages back in, reinstalled the related software, and
removed them with ppa-purge. Followed that with apt update, autoremove
and a necessary reboot. After all that, I got the same "unresolvable
problem" error when I tried to do-release-upgrade.
--
You received this bug
I followed instructions and removed all ppas using add-apt-repository
--remove followed by ppa-purge. Nothing changed in the flow of do-
release-upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Interesting. I never manually changed the configuration. If any conversion
was done, it was by the installation. There may be a bug after all.
Thanks
Rich
On Mon, Dec 3, 2018 at 4:45 AM Karl Stenerud
wrote:
> Hi Rich,
>
> Thanks for reporting this. It looks from the logs to be a
Public bug reported:
I was able to partially mitigate the bug by replacing smb.conf with the
pre-upgrade version. That allowed access to drives and printers from a
Windows 7 computer, but did not help with a file share attached from a
fully patched Windows 10 computer. The Win 10 upgrade may be
