Recent Posts

Pages: [1] 2 3 ... 10

Updates / Re: NO_PUBKEY E88979FB9B30ACF2

« Last post by DesertWinds on Today at 08:51:13 AM »

Thanks Stevef it works

Quote from: stevef on April 25, 2024, 11:00:33 AM

There may be a problem with the source repository - it is giving a 404 error which is odd..
I expect they will resolve it in due course.

In the short term - if you need to allow the updates to run, try this.

Click Menu and begin typing 'Software & Updates' in the search box
When you see 'Software & Updates' click on it.
In the Window that opens select 'Other Software' tab

Uncheck the entry for Chrome and enter your password to authenticate the change if asked.
Click Close on the 'Software & Updates' window and then 'Reload' to refresh the cache.

Then try update/upgrade again. This should now skip the Chrome update.

Once done, I'd leave it 24 hours or so, then go through the above again but re-enable the Chrome repository.

If it isn't working then let us know.

Security & Bug Fixes / Top-notch Сasual Dating - Authentic Maidens

« Last post by donbrew on Today at 07:55:59 AM »

Make dating stress-free and enjoyable with the best casual dating experience.
Verified Damsels
Optimal Сasual Dating

Other / Re: Help NEWBIE Screwed up repositories

« Last post by stevef on Today at 04:56:47 AM »

There's an inbuilt utility which is a quick fix attempt but it may not be able to undone what you've done.
It is rated with caution as it involves changing system files.

Click Menu and begin typing 'Lite Tweaks' into the search box.
When you see 'Lite Tweaks' offered, click on it.

In the window that opens scroll down to find and check 'Package System Repair' then click begin and follow the instructions.

If that doesn't work, we could try to debug, but starting from scratch may be quickest.

Other / Help NEWBIE Screwed up repositories

« Last post by Dan Brown on Today at 03:33:49 AM »

Hi There

I have been distro hopping for a long time but finally settled on LL.

I keep using timeshift to make restore points but I think I screwed up my Repositories
and need to fix it or start from scratch again. I have googled and searched but never
certain I won't make it worse. I am hoping for a quick fix.

Here's the problem when I try and run updates

===========================
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://repo.linuxliteos.com/linuxlite fluorite InRelease
Err:1 http://repo.linuxliteos.com/linuxlite fluorite InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 22AAEA0A86A02625
Get:2 http://archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:3 http://archive.canonical.com jammy InRelease [11.4 kB]
Err:3 http://archive.canonical.com jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Hit:4 https://ppa.launchpadcontent.net/alessandro-strada/ppa/ubuntu jammy InRelease
Err:4 https://ppa.launchpadcontent.net/alessandro-strada/ppa/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AD5F235DF639B041
Hit:5 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease
Err:5 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9BDB3D89CE49EC21
Err:2 http://archive.ubuntu.com/ubuntu jammy-security InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Hit:6 https://ppa.launchpadcontent.net/teejee2008/foss/ubuntu jammy InRelease
Get:7 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Err:6 https://ppa.launchpadcontent.net/teejee2008/foss/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B5B116B72D0F61F0
Hit:8 https://ppa.launchpadcontent.net/tomtomtom/conky-manager/ubuntu jammy InRelease
Err:8 https://ppa.launchpadcontent.net/tomtomtom/conky-manager/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B90E9186F0E836FB
Err:7 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Get:9 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
Err:9 http://archive.ubuntu.com/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Get:10 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]
Err:10 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
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: http://repo.linuxliteos.com/linuxlite fluorite InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 22AAEA0A86A02625
W: GPG error: http://archive.canonical.com jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.canonical.com jammy InRelease' is not signed.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://ppa.launchpadcontent.net/alessandro-strada/ppa/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AD5F235DF639B041
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9BDB3D89CE49EC21
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-security InRelease' is not signed.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://ppa.launchpadcontent.net/teejee2008/foss/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B5B116B72D0F61F0
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://ppa.launchpadcontent.net/tomtomtom/conky-manager/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B90E9186F0E836FB
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is not signed.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' is not signed.

Lenovo M73 Thinkcentre mini - i5-4690K Intel CPU - Onboard Intel GPU - 256Gb SSD - 16Gb DDR3 RAM

Other / Re: re-Touchscreen

« Last post by keiaa on April 25, 2024, 07:21:25 PM »

Good day! Please refer to the following documentation for your instance. Cheers!

https://wiki.ubuntu.com/Touchscreen

Other / re-Touchscreen on Chromebook

« Last post by Jesse Bassett on April 25, 2024, 11:11:36 AM »

So I successfully installed LL on a lenovo flex 5i chromebook. Everything works right out-of-the-box EXCEPT the touchscreen. Are there any commands I can try to enable the touchscreen on my laptop?

Updates / Re: NO_PUBKEY E88979FB9B30ACF2

« Last post by stevef on April 25, 2024, 11:00:33 AM »

There may be a problem with the source repository - it is giving a 404 error which is odd..
I expect they will resolve it in due course.

In the short term - if you need to allow the updates to run, try this.

Click Menu and begin typing 'Software & Updates' in the search box
When you see 'Software & Updates' click on it.
In the Window that opens select 'Other Software' tab

Uncheck the entry for Chrome and enter your password to authenticate the change if asked.
Click Close on the 'Software & Updates' window and then 'Reload' to refresh the cache.

Then try update/upgrade again. This should now skip the Chrome update.

Once done, I'd leave it 24 hours or so, then go through the above again but re-enable the Chrome repository.

If it isn't working then let us know.

Updates / NO_PUBKEY E88979FB9B30ACF2

« Last post by DesertWinds on April 25, 2024, 09:42:24 AM »

New linux user beginning to regret changing from windows, but staying open.

Cant update software seems a public keys issue.

Changed to better closer server, same error

speed checked net, is fine

tried codes in other fixes on this forum, same errors

log below ..help

===========================
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 a new or existing thread for assistance.

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

Hit:1 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy InRelease
Hit:2 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy-updates InRelease
Hit:3 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy-backports InRelease
Hit:4 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy-security InRelease
Get:5 https://dl.google.com/linux/chrome/deb stable InRelease [1,825 B]
Hit:6 http://repo.linuxliteos.com/linuxlite fluorite InRelease
Err:5 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 E88979FB9B30ACF2
Hit:7 http://archive.canonical.com/ubuntu jammy InRelease
Reading package lists...
W: 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 E88979FB9B30ACF2
E: The repository 'https://dl.google.com/linux/chrome/deb stable InRelease' is not signed.

from Terminal same error

sudo apt update
[sudo] password for geoff:
Hit:1 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy InRelease
Hit:2 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy-updates InRelease
Hit:3 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy-backports InRelease
Hit:4 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy-security InRelease
Hit:5 http://repo.linuxliteos.com/linuxlite fluorite InRelease
Get:6 https://dl.google.com/linux/chrome/deb stable InRelease [1,825 B]
Err:6 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 E88979FB9B30ACF2
Hit:7 http://archive.canonical.com/ubuntu jammy InRelease
Reading package lists... Done
W: 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 E88979FB9B30ACF2
E: The repository 'https://dl.google.com/linux/chrome/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(

manpage for repository creation and user configuration details.

Other / re-Touchscreen

« Last post by Jesse Bassett on April 25, 2024, 09:28:58 AM »

bump...

Security & Bug Fixes / Re: Major issue with the Linux Lite 6.6 and GTX 660 (not sure if bug).

« Last post by keiaa on April 25, 2024, 08:05:21 AM »

Sorry to update this post. I'm afraid this is not a bug, nor a major one if it is.

As per the hardware section of the Linux Lite Help Manual, the distribution only includes a handful of open source drivers for some AMDGPU products. Setting that aside, nVidia GPUs don't really have a lot of fully functional open source counterparts.

This drivers can't be integrated to Linux Lite and set to run out-of-the-box due to licensing issues. It is a standard and a must to always check for proprietary drivers upon a clean install. You have to do it yourself, not the machine nor anyone would have to do it for you. It's just a couple of clicks anyways my fellow.

Cheers!

Pages: [1] 2 3 ... 10