After my desktop success in upgrading from 18 to 22, I tried to do the
same on the laptop. While the update to 20 went without incident, I am
unable to update to 22. I get the message that it can only do a partial
upgrade when using the software updater. When I click on partial
upgrade, I then get a message that it cannot upgrade from focal to jammy
not supported with this tool. Suggestions?

On 9/2/22 13:07, wAYNE wrote:
> After my desktop success in upgrading from 18 to 22, I tried to do the
> same on the laptop.  While the update to 20 went without incident, I am
> unable to update to 22.  I get the message that it can only do a partial
> upgrade when using the software updater.  When I click on partial
> upgrade, I then get a message that it cannot upgrade from focal to jammy
> not supported with this tool.  Suggestions?

Backup your data then Install from the latest media.
You can format your root partition if your /home is not on the same
partition. Have you tried to the live media to see if it recognizes
your hardware?

bliss

--
bliss dash SF 4 ever at dslextreme dot com

On 9/2/22 16:33, Bobbie Sellers wrote:
> On 9/2/22 13:07, wAYNE wrote:
>> After my desktop success in upgrading from 18 to 22, I tried to do the
>> same on the laptop.  While the update to 20 went without incident, I
>> am unable to update to 22.  I get the message that it can only do a
>> partial upgrade when using the software updater.  When I click on
>> partial upgrade, I then get a message that it cannot upgrade from
>> focal to jammy not supported with this tool.  Suggestions?
>
>     Backup your data then Install from the latest media.
>     You can format your root partition if your /home is not on the same
> partition.  Have you tried to the live media to see if it recognizes
> your hardware?
>
>     bliss
>
I'm reinstalling my backup, v18, and going to try again. I did get a
message before the aforementioned appeared and will jot it down and post
here. Unfortunately, I can't remember what it was at this time.

Ok, the message I am getting when trying to upgrade from 20 to 22 is this:

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

If none of this applies, then please report this bug using the command
'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to
investigate this yourself the log files in '/var/log/dist-upgrade' will
contain details about the upgrade. Specifically, look at 'main.log' and
'apt.log'.

Here's the main log:

2022-09-02 20:20:01,502 INFO Using config files
'['./DistUpgrade.cfg.focal',
'/etc/update-manager/release-upgrades.d/ubuntu-advantage-upgrades.cfg']'
2022-09-02 20:20:01,503 INFO uname information: 'Linux
wayne-Inspiron-1545 5.4.0-125-generic #141-Ubuntu SMP Wed Aug 10
13:42:03 UTC 2022 x86_64'
2022-09-02 20:20:01,971 INFO apt version: '2.0.9'
2022-09-02 20:20:01,971 INFO python version: '3.8.10 (default, Jun 22
2022, 20:18:18)
[GCC 9.4.0]'
2022-09-02 20:20:01,975 INFO release-upgrader version '22.04.13' started
2022-09-02 20:20:02,072 INFO locale: 'en_US' 'UTF-8'
2022-09-02 20:20:02,767 DEBUG Using 'DistUpgradeViewGtk3' view
2022-09-02 20:20:02,822 DEBUG enable dpkg --force-overwrite
2022-09-02 20:20:02,848 DEBUG creating statefile:
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'
2022-09-02 20:20:09,070 DEBUG lsb-release: 'focal'
2022-09-02 20:20:09,071 DEBUG _pythonSymlinkCheck run
2022-09-02 20:20:09,077 DEBUG openCache()
2022-09-02 20:20:09,077 DEBUG quirks: running PreCacheOpen
2022-09-02 20:20:09,077 DEBUG running Quirks.PreCacheOpen
2022-09-02 20:20:10,231 DEBUG Comparing 4.15.0-192 with
2022-09-02 20:20:10,245 DEBUG Comparing 5.4.0-125 with 4.15.0-192
2022-09-02 20:20:10,497 DEBUG /openCache(), new cache size 80260
2022-09-02 20:20:10,497 DEBUG need_server_mode(): run in 'desktop' mode,
(because of pkg 'ubuntu-desktop')
2022-09-02 20:20:10,497 DEBUG checkViewDepends()
2022-09-02 20:20:10,499 DEBUG running doUpdate() (showErrors=False)
2022-09-02 20:20:14,495 DEBUG openCache()
2022-09-02 20:20:15,611 DEBUG Comparing 4.15.0-192 with
2022-09-02 20:20:15,618 DEBUG Comparing 5.4.0-125 with 4.15.0-192
2022-09-02 20:20:15,865 DEBUG /openCache(), new cache size 80260
2022-09-02 20:20:15,865 DEBUG doPostInitialUpdate
2022-09-02 20:20:15,865 DEBUG quirks: running jammyPostInitialUpdate
2022-09-02 20:20:15,866 DEBUG running Quirks.jammyPostInitialUpdate
2022-09-02 20:20:16,807 DEBUG running
Quirks._test_and_fix_missing_nvidia_metapackage
2022-09-02 20:20:18,203 DEBUG No autoremovable libnvidia-gl found, exiting.
2022-09-02 20:20:19,172 DEBUG Snap core20 is installed
2022-09-02 20:20:19,609 DEBUG Snap gnome-3-38-2004 is installed
2022-09-02 20:20:19,609 DEBUG Snap gnome-3-38-2004 is not tracking the
release channel
2022-09-02 20:20:19,818 DEBUG Snap gtk-common-themes is installed
2022-09-02 20:20:20,055 DEBUG Snap snap-store is installed
2022-09-02 20:20:20,476 DEBUG Snap bare is installed
2022-09-02 20:20:20,477 DEBUG Snap bare is not tracking the release channel
2022-09-02 20:20:20,706 DEBUG Snap chromium is installed
2022-09-02 20:20:20,706 DEBUG Snap chromium is not tracking the release
channel
2022-09-02 20:20:20,933 DEBUG Snap core is installed
2022-09-02 20:20:20,933 DEBUG Snap core is not tracking the release channel
2022-09-02 20:20:21,145 DEBUG Snap core18 is installed
2022-09-02 20:20:21,146 DEBUG Snap core18 is not tracking the release
channel
2022-09-02 20:20:21,373 DEBUG Snap gnome-3-26-1604 is installed
2022-09-02 20:20:21,373 DEBUG Snap gnome-3-26-1604 is not tracking the
release channel
2022-09-02 20:20:21,636 DEBUG Snap gnome-system-monitor is installed
2022-09-02 20:20:21,881 DEBUG Snap guvcview-brlin is installed
2022-09-02 20:20:21,881 DEBUG Snap guvcview-brlin is not tracking the
release channel
2022-09-02 20:20:22,113 DEBUG Snap remmina is installed
2022-09-02 20:20:22,113 DEBUG Snap remmina is not tracking the release
channel
2022-09-02 20:20:22,274 DEBUG Snap simplescreenrecorder-mardy is installed
2022-09-02 20:20:22,274 DEBUG Snap simplescreenrecorder-mardy is not
tracking the release channel
2022-09-02 20:20:22,677 DEBUG Snap vlc is installed
2022-09-02 20:20:22,678 DEBUG Snap vlc is not tracking the release channel
2022-09-02 20:20:22,900 DEBUG Snap gnome-3-34-1804 is installed
2022-09-02 20:20:22,900 DEBUG Snap gnome-3-34-1804 is not tracking the
release channel
2022-09-02 20:20:23,174 DEBUG Snap gnome-calculator is installed
2022-09-02 20:20:23,485 DEBUG Snap gnome-characters is installed
2022-09-02 20:20:23,808 DEBUG Snap gnome-logs is installed
2022-09-02 20:20:26,474 DEBUG MetaPkgs: ubuntu-desktop
2022-09-02 20:20:31,084 DEBUG Foreign:
2022-09-02 20:20:31,084 DEBUG Obsolete: displaycal-0install gcc-6-base
google-earth-pro-stable jlog libavcodec57 libavutil55 libcamel-1.2-61
libcapnp-0.6.1 libevent-2.1-6 libgnome-desktop-3-12 libgssdp-1.0-3
libicu60 libmysofa0 libpasastro libpng12-0 libpng12-dev libpoppler73
libswresample2 libvpx5 libwinpr-dsparse0.1 libwinpr-handle0.1
libwinpr-heap0.1 libwinpr-library0.1 libwxgtk3.0-0v5 libx264-152
libx265-146 linux-generic-hwe-16.04 linux-headers-4.15.0-192
linux-headers-4.15.0-192-generic linux-image-4.15.0-192-generic
linux-modules-4.15.0-192-generic linux-modules-extra-4.15.0-192-generic
net.downloadhelper.coapp netlogger skychart skychart-data-dso
skychart-data-pictures skychart-data-stars unity-scope-chromiumbookmarks
unity-scope-firefoxbookmarks woeusb xserver-xorg-video-ati-hwe-16.04
xserver-xorg-video-vmware-hwe-16.04 zoom
2022-09-02 20:20:31,085 DEBUG updateSourcesList()
2022-09-02 20:20:31,104 DEBUG rewriteSourcesList() with mirror_check
2022-09-02 20:20:31,104 DEBUG ['ubuntu-minimal', 'ubuntu-standard']
2022-09-02 20:20:31,104 DEBUG Checking pkg: ubuntu-minimal
2022-09-02 20:20:31,107 DEBUG Checking pkg: ubuntu-standard
2022-09-02 20:20:31,110 DEBUG examining: 'deb
http://us.archive.ubuntu.com/ubuntu/ focal main restricted'
2022-09-02 20:20:31,110 DEBUG verifySourcesListEntry: deb
http://us.archive.ubuntu.com/ubuntu/ jammy main restricted
2022-09-02 20:20:31,110 DEBUG url_downloadable:
http://us.archive.ubuntu.com/ubuntu//dists/jammy/Release
2022-09-02 20:20:31,111 DEBUG s='http' n='us.archive.ubuntu.com'
p='/ubuntu//dists/jammy/Release' q='' f=''
2022-09-02 20:20:31,146 DEBUG entry 'deb
http://us.archive.ubuntu.com/ubuntu/ jammy main restricted' updated to
new dist
2022-09-02 20:20:31,146 DEBUG examining: 'deb
http://us.archive.ubuntu.com/ubuntu/ focal-updates main restricted'
2022-09-02 20:20:31,146 DEBUG entry 'deb http://us.agrep Broken
/var/log/dist-upgrade/apt.log
rchive.ubuntu.com/ubuntu/ jammy-updates main restricted' updated to new dist
2022-09-02 20:20:31,147 DEBUG examining: 'deb
http://us.archive.ubuntu.com/ubuntu/ focal universe'
2022-09-02 20:20:31,147 DEBUG entry 'deb
http://us.archive.ubuntu.com/ubuntu/ jammy universe' updated to new dist
2022-09-02 20:20:31,147 DEBUG examining: 'deb
http://us.archive.ubuntu.com/ubuntu/ focal-updates universe'
2022-09-02 20:20:31,147 DEBUG entry 'deb
http://us.archive.ubuntu.com/ubuntu/ jammy-updates universe' updated to
new dist
2022-09-02 20:20:31,147 DEBUG examining: 'deb
http://us.archive.ubuntu.com/ubuntu/ focal multiverse'
2022-09-02 20:20:31,147 DEBUG entry 'deb
http://us.archive.ubuntu.com/ubuntu/ jammy multiverse' updated to new dist
2022-09-02 20:20:31,148 DEBUG examining: 'deb
http://us.archive.ubuntu.com/ubuntu/ focal-updates multiverse'
2022-09-02 20:20:31,148 DEBUG entry 'deb
http://us.archive.ubuntu.com/ubuntu/ jammy-updates multiverse' updated
to new dist
2022-09-02 20:20:31,148 DEBUG examining: 'deb
http://us.archive.ubuntu.com/ubuntu/ focal-backports main restricted
universe multiverse'
2022-09-02 20:20:31,148 DEBUG entry 'deb
http://us.archive.ubuntu.com/ubuntu/ jammy-backports main restricted
universe multiverse' updated to new dist
2022-09-02 20:20:31,148 DEBUG examining: 'deb
http://security.ubuntu.com/ubuntu focal-security main restricted'
2022-09-02 20:20:31,148 DEBUG verifySourcesListEntry: deb
http://security.ubuntu.com/ubuntu jammy main restricted
2022-09-02 20:20:31,148 DEBUG url_downloadable:
http://security.ubuntu.com/ubuntu/dists/jammy/Release
2022-09-02 20:20:31,149 DEBUG s='http' n='security.ubuntu.com'
p='/ubuntu/dists/jammy/Release' q='' f=''
2022-09-02 20:20:31,273 DEBUG entry 'deb
http://security.ubuntu.com/ubuntu jammy-security main restricted'
updated to new dist
2022-09-02 20:20:31,274 DEBUG examining: 'deb
http://security.ubuntu.com/ubuntu focal-security universe'
2022-09-02 20:20:31,274 DEBUG entry 'deb
http://security.ubuntu.com/ubuntu jammy-security universe' updated to
new dist
2022-09-02 20:20:31,274 DEBUG examining: 'deb
http://security.ubuntu.com/ubuntu focal-security multiverse'
2022-09-02 20:20:31,275 DEBUG entry 'deb
http://security.ubuntu.com/ubuntu jammy-security multiverse' updated to
new dist
2022-09-02 20:20:31,284 DEBUG running doUpdate() (showErrors=True)
2022-09-02 20:21:41,304 DEBUG openCache()
2022-09-02 20:21:42,267 DEBUG Comparing 4.15.0-192 with
2022-09-02 20:21:42,269 DEBUG Comparing 5.4.0-125 with 4.15.0-192
2022-09-02 20:21:42,464 DEBUG /openCache(), new cache size 74220
2022-09-02 20:21:42,465 DEBUG need_server_mode(): run in 'desktop' mode,
(because of pkg 'ubuntu-desktop')
2022-09-02 20:21:42,466 DEBUG quirks: running PreDistUpgradeCache
2022-09-02 20:21:42,466 DEBUG running Quirks.PreDistUpgradeCache
2022-09-02 20:21:44,225 ERROR Package net.downloadhelpegrep Broken
/var/log/dist-upgrade/apt.log
r.coapp has no priority set
2022-09-02 20:21:44,682 DEBUG Running KeepInstalledSection rules
2022-09-02 20:21:45,615 DEBUG Kernel uname: '5.4.0-125-generic'
2022-09-02 20:21:45,636 DEBUG nvidiaUpdate()
2022-09-02 20:21:46,808 INFO no old nvidia driver installed, installing
no new
2022-09-02 20:21:46,809 DEBUG Removing 'gnome-cups-manager'
(ubuntu-desktop PostUpgradeRemove rule)
2022-09-02 20:21:46,810 DEBUG Removing 'powermanagement-interface'
(ubuntu-desktop PostUpgradeRemove rule)
2022-09-02 20:21:46,810 DEBUG Removing 'deskbar-applet' (ubuntu-desktop
PostUpgradeRemove rule)
2022-09-02 20:21:46,810 DEBUG Removing 'nautilus-cd-burner'
(ubuntu-desktop PostUpgradeRemove rule)
2022-09-02 20:21:46,810 DEBUG quirks: running PostDistUpgradeCache
2022-09-02 20:21:46,810 DEBUG running Quirks.PostDistUpgradeCache
2022-09-02 20:21:47,130 DEBUG Comparing 4.15.0-192 with
2022-09-02 20:21:47,131 DEBUG Comparing 5.15.0-47 with 4.15.0-192
2022-09-02 20:21:47,131 DEBUG Comparing 5.4.0-125 with 5.15.0-47
2022-09-02 20:21:47,301 DEBUG Marking 'ubuntu-desktop' for upgrade
2022-09-02 20:21:47,557 WARNING Can't mark 'ubuntu-desktop' for upgrade
(E:Unable to correct problems, you have held broken packages.)
2022-09-02 20:23:05,499 ERROR Dist-upgrade failed: 'Broken packages
after upgrade: ubuntu-desktop'
2022-09-02 20:23:05,524 DEBUG abort called
2022-09-02 20:23:05,527 DEBUG openCache()
2022-09-02 20:23:08,769 DEBUG Comparing 4.15.0-192 with
2022-09-02 20:23:08,775 DEBUG Comparing 5.4.0-125 with 4.15.0-192
2022-09-02 20:23:09,022 DEBUG /openCache(), new cache size 80260

Am Freitag, 02. September 2022, um 20:37:22 Uhr schrieb wAYNE:

> Ok, the message I am getting when trying to upgrade from 20 to 22 is
> this:
>
> Could not calculate the upgrade

Please run

sudo apt update
sudo apt upgrade #check if there are any error or "not to be upgraded"
packages.

On 9/3/2022 1:44 AM, Marco Moock wrote:
> Am Freitag, 02. September 2022, um 20:37:22 Uhr schrieb wAYNE:
>
>> Ok, the message I am getting when trying to upgrade from 20 to 22 is
>> this:
>>
>> Could not calculate the upgrade
>
> Please run
>
> sudo apt update
> sudo apt upgrade #check if there are any error or "not to be upgraded" packages.
>

In addition, if we look at this part of the log

> 2022-09-02 20:20:31,084 DEBUG Obsolete: displaycal-0install gcc-6-base google-earth-pro-stable
jlog libavcodec57 libavutil55 libcamel-1.2-61 libcapnp-0.6.1 libevent-2.1-6
libgnome-desktop-3-12 libgssdp-1.0-3 libicu60 libmysofa0 libpasastro libpng12-0
libpng12-dev libpoppler73 libswresample2 libvpx5 libwinpr-dsparse0.1 libwinpr-handle0.1
libwinpr-heap0.1 libwinpr-library0.1 libwxgtk3.0-0v5 libx264-152 libx265-146
linux-generic-hwe-16.04 linux-headers-4.15.0-192 linux-headers-4.15.0-192-generic
linux-image-4.15.0-192-generic linux-modules-4.15.0-192-generic
linux-modules-extra-4.15.0-192-generic net.downloadhelper.coapp netlogger skychart
skychart-data-dso skychart-data-pictures skychart-data-stars unity-scope-chromiumbookmarks
unity-scope-firefoxbookmarks woeusb
xserver-xorg-video-ati-hwe-16.04 <=== would this be a problem ?
xserver-xorg-video-vmware-hwe-16.04 zoom

See if, after the

sudo apt upgrade

step, there is a command mentioned at the end of that screen output
to "purge" unnecessary items. I'm really surprised 16.04 kernel
materials are sticking around in this case. You would think
after at least one attempt to run software updates, that
the kernel purging would have cleaned house and
got rid of old headers.

Paul

On 9/3/22 01:44, Marco Moock wrote:
> Am Freitag, 02. September 2022, um 20:37:22 Uhr schrieb wAYNE:
>
>> Ok, the message I am getting when trying to upgrade from 20 to 22 is
>> this:
>>
>> Could not calculate the upgrade
>
> Please run
>
> sudo apt update
> sudo apt upgrade #check if there are any error or "not to be upgraded"
> packages.
>

Ok, here's the results:

wayne@wayne-Inspiron-15:~$ sudo apt update
[sudo] password for wayne:
Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
Get:2 http://dl.google.com/linux/earth/deb stable InRelease [1,807 B]
Get:3 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:4 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]
Err:2 http://dl.google.com/linux/earth/deb stable InRelease
The following signatures couldn't be verified because the public key
is not available: NO_PUBKEY 4EB27DB2A3B88B8B
Get:6 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages [2,072 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64
DEP-11 Metadata [277 kB]
Get:8 http://us.archive.ubuntu.com/ubuntu focal-updates/universe amd64
DEP-11 Metadata [391 kB]
Get:9 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64
DEP-11 Metadata [944 B]
Get:10 http://us.archive.ubuntu.com/ubuntu focal-backports/main amd64
DEP-11 Metadata [8,008 B]
Get:11 http://us.archive.ubuntu.com/ubuntu focal-backports/universe
amd64 DEP-11 Metadata [30.5 kB]
Get:12 http://security.ubuntu.com/ubuntu focal-security/main amd64
DEP-11 Metadata [40.7 kB]
Get:13 http://security.ubuntu.com/ubuntu focal-security/universe amd64
DEP-11 Metadata [77.1 kB]
Get:14 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64
DEP-11 Metadata [2,464 B]
Reading package lists... Done
W: GPG error: http://dl.google.com/linux/earth/deb stable InRelease: The
following signatures couldn't be verified because the public key is not
available: NO_PUBKEY 4EB27DB2A3B88B8B
E: The repository 'http://dl.google.com/linux/earth/deb stable
InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user
configuration details.

wayne@wayne-Inspiron-15:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Am Samstag, 03. September 2022, um 08:40:11 Uhr schrieb wAYNE:

> On 9/3/22 01:44, Marco Moock wrote:
> > Am Freitag, 02. September 2022, um 20:37:22 Uhr schrieb wAYNE:
> >
> >> Ok, the message I am getting when trying to upgrade from 20 to 22
> >> is this:
> >>
> >> Could not calculate the upgrade
> >
> > Please run
> >
> > sudo apt update
> > sudo apt upgrade #check if there are any error or "not to be
> > upgraded" packages.
> >
>
> Ok, here's the results:
>
> wayne@wayne-Inspiron-15:~$ sudo apt update
> [sudo] password for wayne:
> Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
> Get:2 http://dl.google.com/linux/earth/deb stable InRelease [1,807 B]
> Get:3 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease
> [114 kB] Get:4 http://security.ubuntu.com/ubuntu focal-security
> InRelease [114 kB] Get:5 http://us.archive.ubuntu.com/ubuntu
> focal-backports InRelease [108 kB] Err:2
> http://dl.google.com/linux/earth/deb stable InRelease The following
> signatures couldn't be verified because the public key is not
> available: NO_PUBKEY 4EB27DB2A3B88B8B Get:6
> http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
> [2,072 kB] Get:7 http://us.archive.ubuntu.com/ubuntu
> focal-updates/main amd64 DEP-11 Metadata [277 kB]
> Get:8 http://us.archive.ubuntu.com/ubuntu focal-updates/universe
> amd64 DEP-11 Metadata [391 kB]
> Get:9 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse
> amd64 DEP-11 Metadata [944 B]
> Get:10 http://us.archive.ubuntu.com/ubuntu focal-backports/main amd64
> DEP-11 Metadata [8,008 B]
> Get:11 http://us.archive.ubuntu.com/ubuntu focal-backports/universe
> amd64 DEP-11 Metadata [30.5 kB]
> Get:12 http://security.ubuntu.com/ubuntu focal-security/main amd64
> DEP-11 Metadata [40.7 kB]
> Get:13 http://security.ubuntu.com/ubuntu focal-security/universe
> amd64 DEP-11 Metadata [77.1 kB]
> Get:14 http://security.ubuntu.com/ubuntu focal-security/multiverse
> amd64 DEP-11 Metadata [2,464 B]
> Reading package lists... Done
> W: GPG error: http://dl.google.com/linux/earth/deb stable InRelease:
> The following signatures couldn't be verified because the public key
> is not available: NO_PUBKEY 4EB27DB2A3B88B8B
> E: The repository 'http://dl.google.com/linux/earth/deb stable
> InRelease' is not signed.
> N: Updating from such a repository can't be done securely, and is
> therefore disabled by default.
> N: See apt-secure(8) manpage for repository creation and user
> configuration details.
>
> wayne@wayne-Inspiron-15:~$ sudo apt upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

The key of the Google repo is broken, run
wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -

On 9/3/22 09:51, Marco Moock wrote:
> Am Samstag, 03. September 2022, um 08:40:11 Uhr schrieb wAYNE:
>
>> On 9/3/22 01:44, Marco Moock wrote:
>>> Am Freitag, 02. September 2022, um 20:37:22 Uhr schrieb wAYNE:
>>>
>>>> Ok, the message I am getting when trying to upgrade from 20 to 22
>>>> is this:
>>>>
>>>> Could not calculate the upgrade
>>>
>>> Please run
>>>
>>> sudo apt update
>>> sudo apt upgrade #check if there are any error or "not to be
>>> upgraded" packages.
>>>
>>
>> Ok, here's the results:
>>
>> wayne@wayne-Inspiron-15:~$ sudo apt update
>> [sudo] password for wayne:
>> Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
>> Get:2 http://dl.google.com/linux/earth/deb stable InRelease [1,807 B]
>> Get:3 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease
>> [114 kB] Get:4 http://security.ubuntu.com/ubuntu focal-security
>> InRelease [114 kB] Get:5 http://us.archive.ubuntu.com/ubuntu
>> focal-backports InRelease [108 kB] Err:2
>> http://dl.google.com/linux/earth/deb stable InRelease The following
>> signatures couldn't be verified because the public key is not
>> available: NO_PUBKEY 4EB27DB2A3B88B8B Get:6
>> http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
>> [2,072 kB] Get:7 http://us.archive.ubuntu.com/ubuntu
>> focal-updates/main amd64 DEP-11 Metadata [277 kB]
>> Get:8 http://us.archive.ubuntu.com/ubuntu focal-updates/universe
>> amd64 DEP-11 Metadata [391 kB]
>> Get:9 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse
>> amd64 DEP-11 Metadata [944 B]
>> Get:10 http://us.archive.ubuntu.com/ubuntu focal-backports/main amd64
>> DEP-11 Metadata [8,008 B]
>> Get:11 http://us.archive.ubuntu.com/ubuntu focal-backports/universe
>> amd64 DEP-11 Metadata [30.5 kB]
>> Get:12 http://security.ubuntu.com/ubuntu focal-security/main amd64
>> DEP-11 Metadata [40.7 kB]
>> Get:13 http://security.ubuntu.com/ubuntu focal-security/universe
>> amd64 DEP-11 Metadata [77.1 kB]
>> Get:14 http://security.ubuntu.com/ubuntu focal-security/multiverse
>> amd64 DEP-11 Metadata [2,464 B]
>> Reading package lists... Done
>> W: GPG error: http://dl.google.com/linux/earth/deb stable InRelease:
>> The following signatures couldn't be verified because the public key
>> is not available: NO_PUBKEY 4EB27DB2A3B88B8B
>> E: The repository 'http://dl.google.com/linux/earth/deb stable
>> InRelease' is not signed.
>> N: Updating from such a repository can't be done securely, and is
>> therefore disabled by default.
>> N: See apt-secure(8) manpage for repository creation and user
>> configuration details.
>>
>> wayne@wayne-Inspiron-15:~$ sudo apt upgrade
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> Calculating upgrade... Done
>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> The key of the Google repo is broken, run
> wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
>

Tried it. Now I get a new message:

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

This was likely caused by:
* Unofficial software packages not provided by Ubuntu
Please use the tool 'ppa-purge' from the ppa-purge
package to remove software from a Launchpad PPA and
try the upgrade again.

If none of this applies, then please report this bug using the command
'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to
investigate this yourself the log files in '/var/log/dist-upgrade' will
contain details about the upgrade. Specifically, look at 'main.log' and
'apt.log'.

On 02/09/2022 21:07, Wayne wrote:
> After my desktop success in upgrading from 18 to 22, I tried to do the
> same on the laptop.  While the update to 20 went without incident, I
> am unable to update to 22.  I get the message that it can only do a
> partial upgrade when using the software updater.  When I click on
> partial upgrade, I then get a message that it cannot upgrade from
> focal to jammy not supported with this tool. Suggestions?
If you have backed up your personal data then doing a clean install
would be faster and successful IMO.

On 9/3/22 14:00, Albert Arkwright wrote:
> On 02/09/2022 21:07, Wayne wrote:
>> After my desktop success in upgrading from 18 to 22, I tried to do the
>> same on the laptop.  While the update to 20 went without incident, I
>> am unable to update to 22.  I get the message that it can only do a
>> partial upgrade when using the software updater.  When I click on
>> partial upgrade, I then get a message that it cannot upgrade from
>> focal to jammy not supported with this tool. Suggestions?
> If you have backed up your personal data then doing a clean install
> would be faster and successful IMO.
>
>
I'd rather not if I can avoid it. It took me months the last time to
get everything back where I needed it plus this is a dual boot selected
at start up either Ubuntu or Win 10. My desktop did fine with the same
upgrade (18 to 22), not sure why the laptop is giving problems.

Am Samstag, 03. September 2022, um 13:58:29 Uhr schrieb wAYNE:

> On 9/3/22 09:51, Marco Moock wrote:
> > Am Samstag, 03. September 2022, um 08:40:11 Uhr schrieb wAYNE:
> >
> >> On 9/3/22 01:44, Marco Moock wrote:
> >>> Am Freitag, 02. September 2022, um 20:37:22 Uhr schrieb wAYNE:
> >>>
> >>>> Ok, the message I am getting when trying to upgrade from 20 to 22
> >>>> is this:
> >>>>
> >>>> Could not calculate the upgrade
> >>>
> >>> Please run
> >>>
> >>> sudo apt update
> >>> sudo apt upgrade #check if there are any error or "not to be
> >>> upgraded" packages.
> >>>
> >>
> >> Ok, here's the results:
> >>
> >> wayne@wayne-Inspiron-15:~$ sudo apt update
> >> [sudo] password for wayne:
> >> Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
> >> Get:2 http://dl.google.com/linux/earth/deb stable InRelease [1,807
> >> B] Get:3 http://us.archive.ubuntu.com/ubuntu focal-updates
> >> InRelease [114 kB] Get:4 http://security.ubuntu.com/ubuntu
> >> focal-security InRelease [114 kB] Get:5
> >> http://us.archive.ubuntu.com/ubuntu focal-backports InRelease [108
> >> kB] Err:2 http://dl.google.com/linux/earth/deb stable InRelease
> >> The following signatures couldn't be verified because the public
> >> key is not available: NO_PUBKEY 4EB27DB2A3B88B8B Get:6
> >> http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64
> >> Packages [2,072 kB] Get:7 http://us.archive.ubuntu.com/ubuntu
> >> focal-updates/main amd64 DEP-11 Metadata [277 kB]
> >> Get:8 http://us.archive.ubuntu.com/ubuntu focal-updates/universe
> >> amd64 DEP-11 Metadata [391 kB]
> >> Get:9 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse
> >> amd64 DEP-11 Metadata [944 B]
> >> Get:10 http://us.archive.ubuntu.com/ubuntu focal-backports/main
> >> amd64 DEP-11 Metadata [8,008 B]
> >> Get:11 http://us.archive.ubuntu.com/ubuntu focal-backports/universe
> >> amd64 DEP-11 Metadata [30.5 kB]
> >> Get:12 http://security.ubuntu.com/ubuntu focal-security/main amd64
> >> DEP-11 Metadata [40.7 kB]
> >> Get:13 http://security.ubuntu.com/ubuntu focal-security/universe
> >> amd64 DEP-11 Metadata [77.1 kB]
> >> Get:14 http://security.ubuntu.com/ubuntu focal-security/multiverse
> >> amd64 DEP-11 Metadata [2,464 B]
> >> Reading package lists... Done
> >> W: GPG error: http://dl.google.com/linux/earth/deb stable
> >> InRelease: The following signatures couldn't be verified because
> >> the public key is not available: NO_PUBKEY 4EB27DB2A3B88B8B
> >> E: The repository 'http://dl.google.com/linux/earth/deb stable
> >> InRelease' is not signed.
> >> N: Updating from such a repository can't be done securely, and is
> >> therefore disabled by default.
> >> N: See apt-secure(8) manpage for repository creation and user
> >> configuration details.
> >>
> >> wayne@wayne-Inspiron-15:~$ sudo apt upgrade
> >> Reading package lists... Done
> >> Building dependency tree
> >> Reading state information... Done
> >> Calculating upgrade... Done
> >> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> >
> > The key of the Google repo is broken, run
> > wget -q -O - https://dl.google.com/linux/linux_signing_key.pub |
> > sudo apt-key add -
>
> Tried it. Now I get a new message:

Does sudo apt update now run fine?

On 9/3/22 15:02, Marco Moock wrote:
> Am Samstag, 03. September 2022, um 13:58:29 Uhr schrieb wAYNE:
>
>> On 9/3/22 09:51, Marco Moock wrote:
>>> Am Samstag, 03. September 2022, um 08:40:11 Uhr schrieb wAYNE:
>>>
>>>> On 9/3/22 01:44, Marco Moock wrote:
>>>>> Am Freitag, 02. September 2022, um 20:37:22 Uhr schrieb wAYNE:
>>>>>
>>>>>> Ok, the message I am getting when trying to upgrade from 20 to 22
>>>>>> is this:
>>>>>>
>>>>>> Could not calculate the upgrade
>>>>>
>>>>> Please run
>>>>>
>>>>> sudo apt update
>>>>> sudo apt upgrade #check if there are any error or "not to be
>>>>> upgraded" packages.
>>>>>
>>>>
>>>> Ok, here's the results:
>>>>
>>>> wayne@wayne-Inspiron-15:~$ sudo apt update
>>>> [sudo] password for wayne:
>>>> Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
>>>> Get:2 http://dl.google.com/linux/earth/deb stable InRelease [1,807
>>>> B] Get:3 http://us.archive.ubuntu.com/ubuntu focal-updates
>>>> InRelease [114 kB] Get:4 http://security.ubuntu.com/ubuntu
>>>> focal-security InRelease [114 kB] Get:5
>>>> http://us.archive.ubuntu.com/ubuntu focal-backports InRelease [108
>>>> kB] Err:2 http://dl.google.com/linux/earth/deb stable InRelease
>>>> The following signatures couldn't be verified because the public
>>>> key is not available: NO_PUBKEY 4EB27DB2A3B88B8B Get:6
>>>> http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64
>>>> Packages [2,072 kB] Get:7 http://us.archive.ubuntu.com/ubuntu
>>>> focal-updates/main amd64 DEP-11 Metadata [277 kB]
>>>> Get:8 http://us.archive.ubuntu.com/ubuntu focal-updates/universe
>>>> amd64 DEP-11 Metadata [391 kB]
>>>> Get:9 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse
>>>> amd64 DEP-11 Metadata [944 B]
>>>> Get:10 http://us.archive.ubuntu.com/ubuntu focal-backports/main
>>>> amd64 DEP-11 Metadata [8,008 B]
>>>> Get:11 http://us.archive.ubuntu.com/ubuntu focal-backports/universe
>>>> amd64 DEP-11 Metadata [30.5 kB]
>>>> Get:12 http://security.ubuntu.com/ubuntu focal-security/main amd64
>>>> DEP-11 Metadata [40.7 kB]
>>>> Get:13 http://security.ubuntu.com/ubuntu focal-security/universe
>>>> amd64 DEP-11 Metadata [77.1 kB]
>>>> Get:14 http://security.ubuntu.com/ubuntu focal-security/multiverse
>>>> amd64 DEP-11 Metadata [2,464 B]
>>>> Reading package lists... Done
>>>> W: GPG error: http://dl.google.com/linux/earth/deb stable
>>>> InRelease: The following signatures couldn't be verified because
>>>> the public key is not available: NO_PUBKEY 4EB27DB2A3B88B8B
>>>> E: The repository 'http://dl.google.com/linux/earth/deb stable
>>>> InRelease' is not signed.
>>>> N: Updating from such a repository can't be done securely, and is
>>>> therefore disabled by default.
>>>> N: See apt-secure(8) manpage for repository creation and user
>>>> configuration details.
>>>>
>>>> wayne@wayne-Inspiron-15:~$ sudo apt upgrade
>>>> Reading package lists... Done
>>>> Building dependency tree
>>>> Reading state information... Done
>>>> Calculating upgrade... Done
>>>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>>>
>>> The key of the Google repo is broken, run
>>> wget -q -O - https://dl.google.com/linux/linux_signing_key.pub |
>>> sudo apt-key add -
>>
>> Tried it. Now I get a new message:
>
> Does sudo apt update now run fine?
>
sudo apt update
[sudo] password for wayne:
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

On 9/3/2022 9:51 AM, Marco Moock wrote:
> Am Samstag, 03. September 2022, um 08:40:11 Uhr schrieb wAYNE:
>
>> On 9/3/22 01:44, Marco Moock wrote:
>>> Am Freitag, 02. September 2022, um 20:37:22 Uhr schrieb wAYNE:
>>>
>>>> Ok, the message I am getting when trying to upgrade from 20 to 22
>>>> is this:
>>>>
>>>> Could not calculate the upgrade
>>>
>>> Please run
>>>
>>> sudo apt update
>>> sudo apt upgrade #check if there are any error or "not to be
>>> upgraded" packages.
>>>
>>
>> Ok, here's the results:
>>
>> wayne@wayne-Inspiron-15:~$ sudo apt update
>> [sudo] password for wayne:
>> Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
>> Get:2 http://dl.google.com/linux/earth/deb stable InRelease [1,807 B]
>> Get:3 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease
>> [114 kB] Get:4 http://security.ubuntu.com/ubuntu focal-security
>> InRelease [114 kB] Get:5 http://us.archive.ubuntu.com/ubuntu
>> focal-backports InRelease [108 kB] Err:2
>> http://dl.google.com/linux/earth/deb stable InRelease The following
>> signatures couldn't be verified because the public key is not
>> available: NO_PUBKEY 4EB27DB2A3B88B8B Get:6
>> http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
>> [2,072 kB] Get:7 http://us.archive.ubuntu.com/ubuntu
>> focal-updates/main amd64 DEP-11 Metadata [277 kB]
>> Get:8 http://us.archive.ubuntu.com/ubuntu focal-updates/universe
>> amd64 DEP-11 Metadata [391 kB]
>> Get:9 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse
>> amd64 DEP-11 Metadata [944 B]
>> Get:10 http://us.archive.ubuntu.com/ubuntu focal-backports/main amd64
>> DEP-11 Metadata [8,008 B]
>> Get:11 http://us.archive.ubuntu.com/ubuntu focal-backports/universe
>> amd64 DEP-11 Metadata [30.5 kB]
>> Get:12 http://security.ubuntu.com/ubuntu focal-security/main amd64
>> DEP-11 Metadata [40.7 kB]
>> Get:13 http://security.ubuntu.com/ubuntu focal-security/universe
>> amd64 DEP-11 Metadata [77.1 kB]
>> Get:14 http://security.ubuntu.com/ubuntu focal-security/multiverse
>> amd64 DEP-11 Metadata [2,464 B]
>> Reading package lists... Done
>> W: GPG error: http://dl.google.com/linux/earth/deb stable InRelease:
>> The following signatures couldn't be verified because the public key
>> is not available: NO_PUBKEY 4EB27DB2A3B88B8B
>> E: The repository 'http://dl.google.com/linux/earth/deb stable
>> InRelease' is not signed.
>> N: Updating from such a repository can't be done securely, and is
>> therefore disabled by default.
>> N: See apt-secure(8) manpage for repository creation and user
>> configuration details.
>>
>> wayne@wayne-Inspiron-15:~$ sudo apt upgrade
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> Calculating upgrade... Done
>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> The key of the Google repo is broken, run
> wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
>

Synaptic shows in 2004...

googleearth-package package builder using Debian, which means Canonical in the name
of Ubuntu, did not want to have anything to do with packaging
it in a direct sense. They provided a lever, you move the Earth
yourself.

But in 2204, this is missing. And that means doing it in-tree, may not
have a good outcome. You could mess with that, for no positive effect
long-term. In other words, that was an interim solution suited to
two years ago.

*******

Google has a .deb here (Version 7.3.4.8738-r0 )

https://earth.google.com/download

Name: google-earth-pro-stable_current_amd64.deb
Size: 56,896,040 bytes (54 MiB)
SHA256: 86A4F43C493A872224C76DEA7CF107E0B22A1DA109B4D1A43E5C82E05437790B

sudo gdebi google-earth-pro-stable_current_amd64.deb

That installs it, but there's no option in gdebi to remove it later.

Tested, buttery smooth start means my NVidia driver accelerates OK.
I've had test results before, where it was jerky and that might
be a non-NVidia driver situation of some sort.

If I use "sudo synaptic", the package I just installed is present and
ready to be removed (if necessary). The whole situation looks clean.
If Upgrade process complains about package in any way, sudo synaptic,
remove, do Upgrade again, re-install the .deb in 2204.

*******

There are various key shenanigans here.

This is if you wanted to follow the instructions and try and fix the
keys with what you've got. And drag it forward.

https://support.google.com/earth/thread/4111328/google-earth-linux-apt-repository-not-signed?hl=en

[One poster in there reports, for LinuxMint that...]

"Fix merge list problems" in Software Sources GUI fixed it for me.

[And so on. Follow web page recipes as appropriate from there.]

Summary: Removal of the package might be easier than tackling Repository
setting and keys. But it's up to you, how much "settings" in GE
would be lost by just removing it, as to which approach is best.

Since I did my install and test in 2204 (I have both 2004 and 2204
as separate installs on Disk #29), I've tested that at least the
teaser globe appears OK. All my disk drives are numbered here, for
easy access.

Paul

On 9/3/22 15:23, wAYNE wrote:
> On 9/3/22 15:02, Marco Moock wrote:
>> Am Samstag, 03. September 2022, um 13:58:29 Uhr schrieb wAYNE:
>>
>>> On 9/3/22 09:51, Marco Moock wrote:
>>>> Am Samstag, 03. September 2022, um 08:40:11 Uhr schrieb wAYNE:
>>>>> On 9/3/22 01:44, Marco Moock wrote:
>>>>>> Am Freitag, 02. September 2022, um 20:37:22 Uhr schrieb wAYNE:
>>>>>>> Ok, the message I am getting when trying to upgrade from 20 to 22
>>>>>>> is this:
>>>>>>>
>>>>>>> Could not calculate the upgrade
>>>>>>
>>>>>> Please run
>>>>>>
>>>>>> sudo apt update
>>>>>> sudo apt upgrade #check if there are any error or "not to be
>>>>>> upgraded" packages.
>>>>>
>>>>> Ok, here's the results:
>>>>>
>>>>> wayne@wayne-Inspiron-15:~$ sudo apt update
>>>>> [sudo] password for wayne:
>>>>> Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
>>>>> Get:2 http://dl.google.com/linux/earth/deb stable InRelease [1,807
>>>>> B] Get:3 http://us.archive.ubuntu.com/ubuntu focal-updates
>>>>> InRelease [114 kB] Get:4 http://security.ubuntu.com/ubuntu
>>>>> focal-security InRelease [114 kB] Get:5
>>>>> http://us.archive.ubuntu.com/ubuntu focal-backports InRelease [108
>>>>> kB] Err:2 http://dl.google.com/linux/earth/deb stable InRelease
>>>>> The following signatures couldn't be verified because the public
>>>>> key is not available: NO_PUBKEY 4EB27DB2A3B88B8B Get:6
>>>>> http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64
>>>>> Packages [2,072 kB] Get:7 http://us.archive.ubuntu.com/ubuntu
>>>>> focal-updates/main amd64 DEP-11 Metadata [277 kB]
>>>>> Get:8 http://us.archive.ubuntu.com/ubuntu focal-updates/universe
>>>>> amd64 DEP-11 Metadata [391 kB]
>>>>> Get:9 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse
>>>>> amd64 DEP-11 Metadata [944 B]
>>>>> Get:10 http://us.archive.ubuntu.com/ubuntu focal-backports/main
>>>>> amd64 DEP-11 Metadata [8,008 B]
>>>>> Get:11 http://us.archive.ubuntu.com/ubuntu focal-backports/universe
>>>>> amd64 DEP-11 Metadata [30.5 kB]
>>>>> Get:12 http://security.ubuntu.com/ubuntu focal-security/main amd64
>>>>> DEP-11 Metadata [40.7 kB]
>>>>> Get:13 http://security.ubuntu.com/ubuntu focal-security/universe
>>>>> amd64 DEP-11 Metadata [77.1 kB]
>>>>> Get:14 http://security.ubuntu.com/ubuntu focal-security/multiverse
>>>>> amd64 DEP-11 Metadata [2,464 B]
>>>>> Reading package lists... Done
>>>>> W: GPG error: http://dl.google.com/linux/earth/deb stable
>>>>> InRelease: The following signatures couldn't be verified because
>>>>> the public key is not available: NO_PUBKEY 4EB27DB2A3B88B8B
>>>>> E: The repository 'http://dl.google.com/linux/earth/deb stable
>>>>> InRelease' is not signed.
>>>>> N: Updating from such a repository can't be done securely, and is
>>>>> therefore disabled by default.
>>>>> N: See apt-secure(8) manpage for repository creation and user
>>>>> configuration details.
>>>>>
>>>>> wayne@wayne-Inspiron-15:~$ sudo apt upgrade
>>>>> Reading package lists... Done
>>>>> Building dependency tree
>>>>> Reading state information... Done
>>>>> Calculating upgrade... Done
>>>>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>>>>
>>>> The key of the Google repo is broken, run
>>>> wget -q -O - https://dl.google.com/linux/linux_signing_key.pub |
>>>> sudo apt-key add -
>>>
>>> Tried it.  Now I get a new message:
>>
>> Does sudo apt update now run fine?
>>
> sudo apt update
> [sudo] password for wayne:
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> All packages are up to date.
>
I went ahead and tried to upgrade again and get similar messages. If I
selected "continue", I see some things being installed such as snap,
etc. if I let all of those things install, then try and upgrade again I
get this:
Not all updates can be installed. Run a partial upgrade to install as
many updates as possible.
This can be caused by:
A previous upgrade which didn't complete
Problems with some of the installed software
Unofficial software packages not provided by Ubuntu
Normal changes of a pre-release version of Ubuntu
When I then select partial upgrade, I get: Can not upgrade
An upgrade from 'focal' to 'jammy' is not supported with this tool.
When I check on version, still showing 20 and not 22 but looks like some
updates are being installed.

Please run

cat /etc/apt/sources.list

On 03/09/2022 19:19, wAYNE wrote:
> On 9/3/22 14:00, Albert Arkwright wrote:
>> On 02/09/2022 21:07, Wayne wrote:
>>> After my desktop success in upgrading from 18 to 22, I tried to do the
>>> same on the laptop.  While the update to 20 went without incident, I
>>> am unable to update to 22.  I get the message that it can only do a
>>> partial upgrade when using the software updater.  When I click on
>>> partial upgrade, I then get a message that it cannot upgrade from
>>> focal to jammy not supported with this tool. Suggestions?
>> If you have backed up your personal data then doing a clean install
>> would be faster and successful IMO.
>>
>>
>
> I'd rather not if I can avoid it.  It took me months the last time to
> get everything back where I needed it plus this is a dual boot
> selected at start up either Ubuntu or Win 10.  My desktop did fine
> with the same upgrade (18 to 22), not sure why the laptop is giving
> problems.

Did you try "sudo do-release-upgrade" just to see what it does? It might
just fix the problems automatically at a cost of time. Because it has to
do all the checking and verifications, it takes some time.

On 9/4/22 09:29, Marco Moock wrote:
> cat /etc/apt/sources.list

# deb cdrom:[Ubuntu 16.04.5 LTS _Xenial Xerus_ - Release amd64
(20180731)]/ xenial main restricted

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
# deb http://us.archive.ubuntu.com/ubuntu/ jammy main restricted
# deb-src http://us.archive.ubuntu.com/ubuntu/ xenial main restricted

## Major bug fix updates produced after the final release of the
## distribution.
# deb http://us.archive.ubuntu.com/ubuntu/ jammy-updates main restricted
# deb-src http://us.archive.ubuntu.com/ubuntu/ xenial-updates main
restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
# deb http://us.archive.ubuntu.com/ubuntu/ jammy universe
# deb-src http://us.archive.ubuntu.com/ubuntu/ xenial universe
# deb http://us.archive.ubuntu.com/ubuntu/ jammy-updates universe
# deb-src http://us.archive.ubuntu.com/ubuntu/ xenial-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
# deb http://us.archive.ubuntu.com/ubuntu/ jammy multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ xenial multiverse
# deb http://us.archive.ubuntu.com/ubuntu/ jammy-updates multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ xenial-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
# deb http://us.archive.ubuntu.com/ubuntu/ jammy-backports main
restricted universe multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ xenial-backports main
restricted universe multiverse

deb http://security.ubuntu.com/ubuntu jammy-security main restricted
# deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted
# deb http://security.ubuntu.com/ubuntu jammy-security universe
# deb-src http://security.ubuntu.com/ubuntu xenial-security universe
# deb http://security.ubuntu.com/ubuntu jammy-security multiverse
# deb-src http://security.ubuntu.com/ubuntu xenial-security multiverse
# deb http://www.ap-i.net/apt stable main # disabled on upgrade to bionic
deb http://archive.ubuntu.com/ubuntu jammy main restricted # auto
generated by ubuntu-release-upgrader
deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted #
auto generated by ubuntu-release-upgrader

On 9/4/22 11:55, Albert Arkwright wrote:
> On 03/09/2022 19:19, wAYNE wrote:
>> On 9/3/22 14:00, Albert Arkwright wrote:
>>> On 02/09/2022 21:07, Wayne wrote:
>>>> After my desktop success in upgrading from 18 to 22, I tried to do the
>>>> same on the laptop.  While the update to 20 went without incident, I
>>>> am unable to update to 22.  I get the message that it can only do a
>>>> partial upgrade when using the software updater.  When I click on
>>>> partial upgrade, I then get a message that it cannot upgrade from
>>>> focal to jammy not supported with this tool. Suggestions?
>>> If you have backed up your personal data then doing a clean install
>>> would be faster and successful IMO.
>>>
>>>
>>
>> I'd rather not if I can avoid it.  It took me months the last time to
>> get everything back where I needed it plus this is a dual boot
>> selected at start up either Ubuntu or Win 10.  My desktop did fine
>> with the same upgrade (18 to 22), not sure why the laptop is giving
>> problems.
>
> Did you try "sudo do-release-upgrade" just to see what it does? It might
> just fix the problems automatically at a cost of time. Because it has to
> do all the checking and verifications, it takes some time.
>
Here's what it says:
Checking for a new Ubuntu release
Please install all available updates for your release before upgrading.
Next step?

Another huge mess.
Place the following lines in the sources.list, ONLY these one:

deb http://de.archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
deb http://de.archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
deb http://de.archive.ubuntu.com/ubuntu jammy-security main restricted universe multiverse
deb http://de.archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse

The sudo apt update.

Am Sonntag, 04. September 2022, um 14:31:16 Uhr schrieb wAYNE:

> Next step?

Repair your sources.list, see my other post.

On 9/4/22 14:52, Marco Moock wrote:
> Another huge mess.
> Place the following lines in the sources.list, ONLY these one:
>
> deb http://de.archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
> deb http://de.archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
> deb http://de.archive.ubuntu.com/ubuntu jammy-security main restricted universe multiverse
> deb http://de.archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
>
> The sudo apt update.
>

Tried all of this. I deleted everything else in the file and left those
four lines. Here's what happens:

Can't install ubuntu desktop. It was impossible to install a required
package. Please report this as a bug....

Clicking "close", I get once again that it could not calculate the
upgrade due to an unresolvable problem... most likely a transient problem.

What gives? I'm about to ditch the whole thing. I'm been working all
weekend trying to get this cursed upgrade installed onto the laptop
without success. As I said before, I have limited Ubuntu command
knowledge. I just want things to work with minimal intervention, but
this is becoming ridiculous.

Any more suggestions would be welcome, but I'm about to do a fresh
install assuming it doesn't take me days to figure out how to keep the
grub menu intact and allow my Win system to be accessible because this
laptop is dual boot. Didn't want to go that route, but it won't update
despite all suggestions tried.

On 9/3/22 15:38, Paul wrote:
> On 9/3/2022 9:51 AM, Marco Moock wrote:
>> Am Samstag, 03. September 2022, um 08:40:11 Uhr schrieb wAYNE:
>>
>>> On 9/3/22 01:44, Marco Moock wrote:
>>>> Am Freitag, 02. September 2022, um 20:37:22 Uhr schrieb wAYNE:
>>>>> Ok, the message I am getting when trying to upgrade from 20 to 22
>>>>> is this:
>>>>>
>>>>> Could not calculate the upgrade
>>>>
>>>> Please run
>>>>
>>>> sudo apt update
>>>> sudo apt upgrade #check if there are any error or "not to be
>>>> upgraded" packages.
>>>
>>> Ok, here's the results:
>>>
>>> wayne@wayne-Inspiron-15:~$ sudo apt update
>>> [sudo] password for wayne:
>>> Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
>>> Get:2 http://dl.google.com/linux/earth/deb stable InRelease [1,807 B]
>>> Get:3 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease
>>> [114 kB] Get:4 http://security.ubuntu.com/ubuntu focal-security
>>> InRelease [114 kB] Get:5 http://us.archive.ubuntu.com/ubuntu
>>> focal-backports InRelease [108 kB] Err:2
>>> http://dl.google.com/linux/earth/deb stable InRelease The following
>>> signatures couldn't be verified because the public key is not
>>> available: NO_PUBKEY 4EB27DB2A3B88B8B Get:6
>>> http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
>>> [2,072 kB] Get:7 http://us.archive.ubuntu.com/ubuntu
>>> focal-updates/main amd64 DEP-11 Metadata [277 kB]
>>> Get:8 http://us.archive.ubuntu.com/ubuntu focal-updates/universe
>>> amd64 DEP-11 Metadata [391 kB]
>>> Get:9 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse
>>> amd64 DEP-11 Metadata [944 B]
>>> Get:10 http://us.archive.ubuntu.com/ubuntu focal-backports/main amd64
>>> DEP-11 Metadata [8,008 B]
>>> Get:11 http://us.archive.ubuntu.com/ubuntu focal-backports/universe
>>> amd64 DEP-11 Metadata [30.5 kB]
>>> Get:12 http://security.ubuntu.com/ubuntu focal-security/main amd64
>>> DEP-11 Metadata [40.7 kB]
>>> Get:13 http://security.ubuntu.com/ubuntu focal-security/universe
>>> amd64 DEP-11 Metadata [77.1 kB]
>>> Get:14 http://security.ubuntu.com/ubuntu focal-security/multiverse
>>> amd64 DEP-11 Metadata [2,464 B]
>>> Reading package lists... Done
>>> W: GPG error: http://dl.google.com/linux/earth/deb stable InRelease:
>>> The following signatures couldn't be verified because the public key
>>> is not available: NO_PUBKEY 4EB27DB2A3B88B8B
>>> E: The repository 'http://dl.google.com/linux/earth/deb stable
>>> InRelease' is not signed.
>>> N: Updating from such a repository can't be done securely, and is
>>> therefore disabled by default.
>>> N: See apt-secure(8) manpage for repository creation and user
>>> configuration details.
>>>
>>> wayne@wayne-Inspiron-15:~$ sudo apt upgrade
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> Calculating upgrade... Done
>>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>>
>> The key of the Google repo is broken, run
>> wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo
>> apt-key add -
>>
>
> Synaptic shows in 2004...
>
> googleearth-package     package builder using Debian, which means
> Canonical in the name
>                         of Ubuntu, did not want to have anything to do
> with packaging
>                         it in a direct sense. They provided a lever,
> you move the Earth
>                         yourself.
>
> But in 2204, this is missing. And that means doing it in-tree, may not
> have a good outcome. You could mess with that, for no positive effect
> long-term. In other words, that was an interim solution suited to
> two years ago.
>
> *******
>
> Google has a .deb here  (Version 7.3.4.8738-r0 )
>
> https://earth.google.com/download
>
>    Name: google-earth-pro-stable_current_amd64.deb
>    Size: 56,896,040 bytes (54 MiB)
>    SHA256:
> 86A4F43C493A872224C76DEA7CF107E0B22A1DA109B4D1A43E5C82E05437790B
>
> sudo gdebi google-earth-pro-stable_current_amd64.deb
>
> That installs it, but there's no option in gdebi to remove it later.
>
> Tested, buttery smooth start means my NVidia driver accelerates OK.
> I've had test results before, where it was jerky and that might
> be a non-NVidia driver situation of some sort.
>
> If I use "sudo synaptic", the package I just installed is present and
> ready to be removed (if necessary). The whole situation looks clean.
> If Upgrade process complains about package in any way, sudo synaptic,
> remove, do Upgrade again, re-install the .deb in 2204.
>
> *******
>
> There are various key shenanigans here.
>
> This is if you wanted to follow the instructions and try and fix the
> keys with what you've got. And drag it forward.
>
> https://support.google.com/earth/thread/4111328/google-earth-linux-apt-repository-not-signed?hl=en
>
>
>     [One poster in there reports, for LinuxMint that...]
>
>        "Fix merge list problems" in Software Sources GUI fixed it for me.
>
>     [And so on. Follow web page recipes as appropriate from there.]
>
> Summary:  Removal of the package might be easier than tackling Repository
>           setting and keys. But it's up to you, how much "settings" in GE
>           would be lost by just removing it, as to which approach is best.
>
>           Since I did my install and test in 2204 (I have both 2004 and
> 2204
>           as separate installs on Disk #29), I've tested that at least the
>           teaser globe appears OK. All my disk drives are numbered
> here, for
>           easy access.
>
>    Paul
This unfortunately didn't help at all. See my response to Marco.

On 9/4/22 16:08, wAYNE wrote:
> On 9/4/22 14:52, Marco Moock wrote:
>> Another huge mess.
>> Place the following lines in the sources.list, ONLY these one:
>>
>> deb http://de.archive.ubuntu.com/ubuntu jammy main restricted universe
>> multiverse
>> deb http://de.archive.ubuntu.com/ubuntu jammy-updates main restricted
>> universe multiverse
>> deb http://de.archive.ubuntu.com/ubuntu jammy-security main restricted
>> universe multiverse
>> deb http://de.archive.ubuntu.com/ubuntu jammy-backports main
>> restricted universe multiverse
>>
>> The sudo apt update.
>>
>
> Tried all of this.  I deleted everything else in the file and left those
> four lines.  Here's what happens:
>
> Can't install ubuntu desktop.  It was impossible to install a required
> package.  Please report this as a bug....
>
> Clicking "close", I get once again that it could not calculate the
> upgrade due to an unresolvable problem... most likely a transient problem.
>
> What gives?  I'm about to ditch the whole thing.  I'm been working all
> weekend trying to get this cursed upgrade installed onto the laptop
> without success.  As I said before, I have limited Ubuntu command
> knowledge.  I just want things to work with minimal intervention, but
> this is becoming ridiculous.
>
> Any more suggestions would be welcome, but I'm about to do a fresh
> install assuming it doesn't take me days to figure out how to keep the
> grub menu intact and allow my Win system to be accessible because this
> laptop is dual boot.  Didn't want to go that route, but it won't update
> despite all suggestions tried.

My only suggestion is to download the latest Ubuntu 22.04.1 media or
the 20.04.5 media, write it boot-ably to a flash drive
and plug it into your computer. I would not use Ubuntu myself.
But if the Media works on your hardware then copy off the contents of
your /home directory to another media and then Install the working
Flash Drive via the script to the Drive.
How old is the drive?
Have you ever used GSmartControl to evaluate the soundness of
the drive?
bliss - brought to you by the power and ease of PCLinuxOS
the Perfect Computer Linus Operating System(for me),
and a minor case of hypergraphia.

The rule is perfect: in all matters of opinion our adversaries are
insane. (Mark Twain)

--
bliss dash SF 4 ever at dslextreme dot com

On 9/4/22 19:25, Bobbie Sellers wrote:
> On 9/4/22 16:08, wAYNE wrote:
>> On 9/4/22 14:52, Marco Moock wrote:
>>> Another huge mess.
>>> Place the following lines in the sources.list, ONLY these one:
>>>
>>> deb http://de.archive.ubuntu.com/ubuntu jammy main restricted
>>> universe multiverse
>>> deb http://de.archive.ubuntu.com/ubuntu jammy-updates main restricted
>>> universe multiverse
>>> deb http://de.archive.ubuntu.com/ubuntu jammy-security main
>>> restricted universe multiverse
>>> deb http://de.archive.ubuntu.com/ubuntu jammy-backports main
>>> restricted universe multiverse
>>>
>>> The sudo apt update.
>>>
>>
>> Tried all of this.  I deleted everything else in the file and left
>> those four lines.  Here's what happens:
>>
>> Can't install ubuntu desktop.  It was impossible to install a required
>> package.  Please report this as a bug....
>>
>> Clicking "close", I get once again that it could not calculate the
>> upgrade due to an unresolvable problem... most likely a transient
>> problem.
>>
>> What gives?  I'm about to ditch the whole thing.  I'm been working all
>> weekend trying to get this cursed upgrade installed onto the laptop
>> without success.  As I said before, I have limited Ubuntu command
>> knowledge.  I just want things to work with minimal intervention, but
>> this is becoming ridiculous.
>>
>> Any more suggestions would be welcome, but I'm about to do a fresh
>> install assuming it doesn't take me days to figure out how to keep the
>> grub menu intact and allow my Win system to be accessible because this
>> laptop is dual boot.  Didn't want to go that route, but it won't
>> update despite all suggestions tried.
>
>     My only suggestion is to download the latest Ubuntu 22.04.1 media
> or the 20.04.5 media, write it boot-ably to a flash drive
> and plug it into your computer.  I would not use Ubuntu myself.
> But if the Media works on your hardware then copy off the contents of
> your /home directory to another media and then Install the working
> Flash Drive via the script to the Drive.
Maybe I will do this, but I'd feel better with some more exact
instructions as I haven't done a fresh install for over a decade plus
there is the Win 10 partition I don't want to touch. It is a dual boot
system either Ubuntu or Win 10 selected at start up.

>     How old is the drive?
>     Have you ever used GSmartControl to evaluate the soundness of
> the drive?
Three years old SSD drive. No, never evaluated it. Is it relevant to
what I'm about to do?