Support Requests - CLICK TO READ BEFORE POSTING


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Install Updates Error Log - Chrome NO_PUBKEY and PPA (thopiekar)
#1

System Specs
Operating System – Linux LiteLinux Lite 6.6
Operating System – OtherUbuntu
CPU / ProcessorIntel Centrino Duo
Memory (RAM)2 GB
StorageSATA SSD (2.5")
Graphics (GPU)Nvidia Geforce 7300
Network deviceIntel PRO/Wireless 3945ABG [Golan] Network Connection
============ Log ===========

Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease
Get:2 https://dl.google.com/linux/chrome/deb stable InRelease [2.548 B]
Hit:3 https://dl.google.com/linux/chrome-stable/deb stable InRelease
Hit:5 http://archive.canonical.com/ubuntu jammy InRelease
Err:2 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 FD533C07C264648F
Hit:6 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Ign:7 https://ppa.launchpadcontent.net/thopiek...601/ubuntu jammy InRelease
Hit:8 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Err:9 https://ppa.launchpadcontent.net/thopiek...601/ubuntu jammy Release
  404  Not Found [IP: 185.125.189.188 443]
Hit:4 https://repo.linuxliteos.com/linuxlite fluorite InRelease
Hit:10 http://us.archive.ubuntu.com/ubuntu jammy-backports 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 FD533C07C264648F
E: The repository 'https://ppa.launchpadcontent.net/thopiekar/mt7601/ubuntu jammy Release' does not have a Release file.
Reply
#2

This shows a couple of problems.  One is a warning, the other an error.  The error needs to be addressed before update/upgrade can be run properly.

The warning relates to chrome
There should be a key stored on your system which is used to verify any updates to chrome.
To see what key the system is trying to use open a terminal by pressing 'Ctrl', 'Alt' and 'T' together.
Type or paste in this command followed by Enter to list the chrome sources file

Code:
cat /etc/apt/sources.list.d/google-chrome.sources

Review the output. There should be a line beginning 'Signed-By' which may look like this.
Quote:Signed-By: /usr/share/keyrings/google-chrome.gpg

If it does use the command below to check the file.  If the line is different on your system replace the location with your specific information.

Code:
gpg --show-keys /usr/share/keyrings/google-chrome.gpg

Post the results back to this thread.

The error relates to some software (thopiekar MT7601 STA driver ?) that you have installed using a PPA (Personal Project Archive). When using PPA software, it is important that the PPA has a release that is compatible with the OS.
The version of Linux Lite on your system is based on an Ubuntu release named jammy.  The thopiekar software does not have a release compatible with jammy.  This conflict is causing the update process to error.

The incompatible thopiekar software should be removed from the system.

After removing the thopiekar software, ensure that the thopiekar PPA reference is removed from the update list.  Removing the PPA reference from the update list should allow the update to run (provided we can fix the chrome issue).

Try this
To remove a ppa from the update list.
Click Menu and begin typing 'software' into the search box.
When you see 'Software & Updates' offered as a choice, click on it.
In the window that opens, click on the 'Other Software' tab.
Locate the PPA that is causing the problem. Click once on the ticked line which references the PPA.
Ensure ONLY the 'ticked' line referencing the PPA you wish to remove is highlighted.
Then click the 'Remove' button and enter your password (if asked) to authorise the removal.
Click Close on the Software & Updates window. You will then be prompted to reload the software sources.
Click 'Reload' and enter your password (if asked).  After the reload is complete, the Software & Updates window should close.

stevef
clueless
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)