[SOLVED] No pubkey / Jammy / 6.6 / repository not updated

[cerulean]

===========================
Install Updates Error log
===========================
Install Updates could not fetch the package cache information lists.
Go to https://www.linuxliteos.com/forums/ and paste the log below into the Software - Support - Updates section for assistance.

============ Log ===========

Hit:1 http://archive.canonical.com/ubuntu jammy InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:6 https://updates.signal.org/desktop/apt xenial InRelease
Hit:7 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Get:8 https://dl.google.com/linux/chrome/deb stable InRelease [1,825 B]
Ign:9 https://ppa.launchpadcontent.net/transmi...ppa/ubuntu jammy InRelease
Err:8 https://dl.google.com/linux/chrome/deb stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 32EE5355A6BC6E42
Err:10 https://ppa.launchpadcontent.net/transmi...ppa/ubuntu jammy Release
  404  Not Found [IP: 185.125.190.80 443]
Hit:5 https://repo.linuxliteos.com/linuxlite fluorite InRelease
Reading package lists...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.google.com/linux/chrome/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 32EE5355A6BC6E42
E: The repository 'https://ppa.launchpadcontent.net/transmissionbt/ppa/ubuntu jammy Release' does not have a Release file.


I'm not sure how to fix the PUBKEY issue... I'm on Linux Lite 6.6.  Thank you in advance for any help 

[stevef]

I'm not sure how to fix the PUBKEY issue

It looks like you have at least two problems, as well as the NO_PUBKEY there is also an error caused by the transmissionbt PPA.
If you need any help with the PPA error, let us know.

For the google chrome issue, can you run a command to check the key on your system ?
Open a terminal by pressing Ctrl, Alt and T together.
In the window that opens type or paste in this command followed by enter

Code:

file /etc/apt/trusted.gpg.d/google-chrome.gpg

Please post back the outcome.

[cerulean]

I'm not sure how to fix the PUBKEY issue

It looks like you have at least two problems, as well as the NO_PUBKEY there is also an error caused by the transmissionbt PPA.
If you need any help with the PPA error, let us know.

For the google chrome issue, can you run a command to check the key on your system ?
Open a terminal by pressing Ctrl, Alt and T together.
In the window that opens type or paste in this command followed by enter

Code:

file /etc/apt/trusted.gpg.d/google-chrome.gpg

Please post back the outcome.

Thank you for responding! 

The line of code you sent returned the following - 

Open PGP Public Key Version 4, Created Tue Apr 12 05:51:15 2016, RSA (Encrypt or Sign, 4096 bits); User ID; Signature; Open PGP Certificate 

I don't know if it's relevant but I don't have google chrome on my computer - I use Firefox for everything. Do you think that could be part of the problem? 

Thanks again!

[stevef]

I don't know if it's relevant but I don't have google chrome on my computer - I use Firefox for everything. Do you think that could be part of the problem?

Linux Lite version 6.x was released with Google Chrome as the default browser.
Instructions on how to install Firefox were provided at the time.
If you don't have google chrome on your computer, what steps did you take to uninstall it ?
Were there any significant system changes before the update problem involving the google chrome key started ?

[cerulean]

I don't know if it's relevant but I don't have google chrome on my computer - I use Firefox for everything. Do you think that could be part of the problem?

Linux Lite version 6.x was released with Google Chrome as the default browser.
Instructions on how to install Firefox were provided at the time.
If you don't have google chrome on your computer, what steps did you take to uninstall it ?
Were there any significant system changes before the update problem involving the google chrome key started ?

It was a while ago now, I don't remember the uninstall process specifically, but it is completely gone.

No big system changes.. I was trying to get a torrent to run a little while ago (a friends' film project) and couldn't make it work, so was trying some stuff from online that I didn't totally understand. That might have been around the same time? But I'm not sure. I've been having the update issue for quite a while and only now thought to come to the forum for help ?

Ended up solving the issue though! Grabbed a pal in real life who's a little more experienced than me and she was able to make it work. Updates now running smooth. Will post the commands in another comment.

[stevef]

Thanks for getting back to us.

It was a while ago now, I don't remember the uninstall process specifically, but it is completely gone.

Chrome hadn't been completely removed - it was still part of the update process and the signing key was still in place.
It is possible that partially removing chrome left you with the problem.
Glad you got it sorted.

[cerulean]

Commands used to resolve the issue:

sudo apt update
man do-releases-upgrade
lsb_release -a
cat /etc/apt/sources.list.d|grep transmissionbt
ls /etc/apt/sources.list.d/transmissionbt-ubuntu-ppa-jammy.list
sudo vi /etc/apt/sources.list.d/transmissionbt-ubuntu-ppa-jammy.list
sudo apt update
sudo apt upgrade
sudo apt upgrade --fix-missing
ls /etc/apt/sources.list

So I think basically what she did is manually run the upgrades and then push through the error with "fix-missing." That worked, the list of updates cleared through and then today when I logged in there were a few more updates waiting, so I ran it just with the update button, and they all went through with no issues.

---

Thanks for getting back to us.

It was a while ago now, I don't remember the uninstall process specifically, but it is completely gone.

Chrome hadn't been completely removed - it was still part of the update process and the signing key was still in place.
It is possible that partially removing chrome left you with the problem.
Glad you got it sorted.

Ahhh interesting. That would make sense. I'm a bit of a google-phobe so I prefer it not to be on my computer at all - do you know how I would go about properly uninstalling it? Or is there any reason why that wouldn't be recommended while using Linux Lite?

I really appreciate all your help and thoughts!

[stevef]

Completely uninstalling any distribution's default browser should be technically possible but prepare for issues because the browser is a component of the system. It is effectively making a personal distribution.

I think it is recognized that browser choice can be highly subjective and there was an interesting debate before Chrome became the browser in LL. For those Linux Lite users who don't want to use Chrome, adding their preferred browser is generally the way forward.

I can't be sure without seeing the context, but the instructions you've posted seem to be addressing the transmissionbt PPA problem.