An Error occurred during Signature Verification

Christopher_H
11 mths ago
27replies

this has been on-going for months.

the below screenshot was sent to team@ months ago (apr2023) with no response to date.

there happen to be a fix available?

os: Kubuntu2204

screenshot

Security

- R_P_M
- 11 mths ago
- Reported - view
Did you manually update the GPG key for the NextDNS repo? Problem was fixed months ago, just follow instructions on the post here:

https://help.nextdns.io/t/35hcjmf/bad-gpg-signature
- Christopher_H
  
  11 mths ago
  
  Reported - view
  i receive an error on Step 2.
  
  rm: cannot remove '/etc/apt/keyrings/nextdns.gpg': No such file or directory
- R_P_M
  
  11 mths ago
  
  Reported - view
  Ah, keyring file must be in the alternate location of:
  
  /usr/share/keyrings/nextdns.gpg
  
  Replace in steps 2 & 3 the file location.
- Christopher_H
  
  10 mths ago
  
  Reported - view
  Yes! Thank You!
  
  that subtle change effected the resolution.
  
  am now no longer seeing the error prompt when bringing up Discover. :D
  
  Follow up Questions:
  
  1. is this Signature error a one-off, never to be seen again? or is this frequent?
  
  2. if frequent, can the above steps affect the same fix?
  
  3. if frequent, what is the cause? can said cause be addresses at the User level?
- R_P_M
  
  10 mths ago
  
  Reported - view
  Ok all is good for you now.
  
  For the extra questions;
  
  1) No, I would not expect it to be very often, maybe around once every 5 years. The gpg key expiry date will tell you when it may well occur again, not checked the exact date myself yet.
  
  2) Once the key has been updated on the repo, then doing same steps again will resolve things.
  
  3) As mentioned before, the GPG key expiry date was passed so it was no longer valid. There’s not much an user can do to avoid this, if you want to keep security of your package manager intact. Just report the expiry here as soon as seen and hope NextDNS updates the key soon afterwards.
- Christopher_H
  
  11 days ago
  
  Reported - view
  Excuse me Please:
  
  in installing a new system(from image) of Kubuntu 22.04 and I am having the same problem as listed above. Needless to say, I am unsure as to what I am doing wrong to affect the resolution.
  
  I issued the following commands:
  
  sudo rm /etc/apt/keyrings/nextdns.gpg sudo wget -qO /etc/apt/keyrings/nextdns.gpg https://repo.nextdns.io/nextdns.gpg sudo apt update && sudo apt dist-upgrade -y sudo touch -m /etc/apt/sources.list.d/nextdns.list
  
  and here are the results:
  
  RESULTS:
  
  ======
  Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease
  Get:2 https://repo.nextdns.io/deb stable InRelease [8490 B]
  Err:2 https://repo.nextdns.io/deb stable InRelease
  The following signatures were invalid: EXPKEYSIG 467A7CCC8ACFA0B7 NextDNS <team@nextdns.io>
  Hit:3 http://us.archive.ubuntu.com/ubuntu jammy InRelease
  Hit:4 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
  Hit:5 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
  Fetched 8490 B in 1s (10.8 kB/s)
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  All packages are up to date.
  W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.nextdns.io/deb stable InRelease: The following signatures were invalid: EXPKEYSIG 467A7CCC8ACFA0B7 NextDNS <team@nextdns.io>
  W: Failed to fetch https://repo.nextdns.io/deb/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG 467A7CCC8ACFA0B7 NextDNS <team@nextdns.io>
  W: Some index files failed to download. They have been ignored, or old ones used instead.
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer required:
  freerdp2-x11 konversation-data kpeople-vcard libdbusmenu-glib4 libdbusmenu-gtk3-4 libfakekey0 libflashrom1 libfreerdp-client2-2
  libfreerdp2-2 libftdi1-2 libkf5contacts-data libkf5contacts5 libkf5i18nlocaledata5 libkf5pulseaudioqt3 libllvm13 libllvm13:i386
  libqt5quickparticles5 libreoffice-help-common libwinpr2-2 linux-headers-5.15.0-25 qml-module-org-kde-people
  qml-module-qtquick-particles2 sshfs
  Use 'sudo apt autoremove' to remove them.
  Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
  vlc-plugin-qt libvlc5 vlc-data libvlccore9 vlc vlc-bin vlc-l10n libopenexr25
  libpostproc55 vlc-plugin-samba libavcodec58 vlc-plugin-notify libavutil56
  libswscale5 libeditorconfig0 vlc-plugin-access-extra vlc-plugin-skins2
  vlc-plugin-video-splitter libswresample3 vlc-plugin-video-output
  libavformat58 libvlc-bin vlc-plugin-base vlc-plugin-visualization
  libavfilter7
  Learn more about Ubuntu Pro at https://ubuntu.com/pro
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
- R_P_M
  
  11 days ago
  
  Reported - view
  I’ll look at the key today (just got up) see if anything is amiss.
  
  Also it would have been better if the “touch” command was before “apt update”. Maybe try apt update again?
  
  If you did the script installer recently, it should have got the latest gpg key. That’s why I want to look at the current key, just in case.
- Christopher_H
  
  10 days ago
  
  Reported - view
  I Thank you for your continued assistance :)
  
  I ran the following:
  
  sudo touch -m /etc/apt/sources.list.d/nextdns.list [nothing happened, went back to _ prompt] sudo wget -qO /etc/apt/keyrings/nextdns.gpg https://repo.nextdns.io/nextdns.gpg [nothing happened, went back to _ prompt] sudo apt update && sudo apt dist-upgrade -y [did what appeared to download, and,...]
  
  RESULT:
  
  "0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded."
  
  \o/
  
  what exact order ought one run the above commands, and for each, what ought be the expected result(s)?
- R_P_M
  
  10 days ago
  
  Reported - view
  OK, I'll break things down for you, one step at a time and in the right order.
  
  1) "sudo wget -qO /etc/apt/keyrings/nextdns.gpg https://repo.nextdns.io/nextdns.gpg"
  
  This command will download the gpg key from the server quietly (i.e. no visual output) and store it in the file path provided.
  
  2) "sudo touch -m /etc/apt/sources.list.d/nextdns.list"
  
  This one is to fool the system that something has changed with the file (only modification date has changed in reality). It's sometimes required because the apt system still holds on to the old key for some unknown reason.
  
  3) "sudo apt update" (dist-upgrade is not required, not sure why that got in there)
  
  Well, this just updates the repos set in the apt system & is a way of checking the repo setup is working (will give errors if anything is amiss).
  
  Your result was for the dist-upgrade command (it's a 'smart' version of upgrade), look like everything was up to date at the time and no error with the repos.
- Christopher_H
  
  9 days ago
  
  Reported - view
  here are my results:
  
  (reminder, if needed, this is on Kubuntu 22.04)
  
  1) sudo wget -qO /etc/apt/keyrings/nextdns.gpg https://repo.nextdns.io/nextdns.gpg
  {no result, returned to _ prompt}
  
  2) sudo touch -m /etc/apt/sources.list.d/nextdns.list
  {no result, returned to _ prompt}
  
  3) sudo apt update
  
  Get:1 https://repo.nextdns.io/deb stable InRelease [8490 B]
  Err:1 https://repo.nextdns.io/deb stable InRelease
  The following signatures were invalid: EXPKEYSIG 467A7CCC8ACFA0B7 NextDNS <team@nextdns.io>
  Hit:2 http://us.archive.ubuntu.com/ubuntu jammy InRelease
  Get:3 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
  Get:4 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
  Get:5 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease [127 kB]
  Get:6 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages [731 kB]
  Get:7 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages [570 kB]
  Get:8 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [2193 kB]
  Get:9 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [1968 kB]
  Get:10 http://us.archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [374 kB]
  Get:11 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 DEP-11 Metadata [103 kB]
  Get:12 http://us.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [2733 kB]
  Get:13 http://security.ubuntu.com/ubuntu jammy-security/main Translation-en [314 kB]
  Get:14 http://security.ubuntu.com/ubuntu jammy-security/main amd64 DEP-11 Metadata [43.2 kB]
  Get:15 http://us.archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en [477 kB]
  Get:16 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages [2644 kB]
  Get:17 http://us.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 DEP-11 Metadata [212 B]
  Get:18 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe i386 Packages [753 kB]
  Get:19 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1180 kB]
  Get:20 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [288 kB]
  Get:21 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 DEP-11 Metadata [356 kB]
  Get:22 http://us.archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 DEP-11 Metadata [940 B]
  Get:23 http://us.archive.ubuntu.com/ubuntu jammy-backports/main amd64 DEP-11 Metadata [5340 B]
  Get:24 http://us.archive.ubuntu.com/ubuntu jammy-backports/restricted amd64 DEP-11 Metadata [216 B]
  Get:25 http://us.archive.ubuntu.com/ubuntu jammy-backports/universe amd64 DEP-11 Metadata [17.8 kB]
  Get:26 http://us.archive.ubuntu.com/ubuntu jammy-backports/multiverse amd64 DEP-11 Metadata [212 B]
  Get:27 http://security.ubuntu.com/ubuntu jammy-security/restricted Translation-en [460 kB]
  Get:28 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 DEP-11 Metadata [208 B]
  Get:29 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [958 kB]
  Get:30 http://security.ubuntu.com/ubuntu jammy-security/universe i386 Packages [648 kB]
  Get:31 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 DEP-11 Metadata [125 kB]
  Get:32 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 DEP-11 Metadata [208 B]
  Fetched 17.3 MB in 16s (1113 kB/s)
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  5 packages can be upgraded. Run 'apt list --upgradable' to see them.
  W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.nextdns.io/deb stable InRelease: The following signatures were invalid: EXPKEYSIG 467A7CCC8ACFA0B7 NextDNS <team@nextdns.io>
  W: Failed to fetch https://repo.nextdns.io/deb/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG 467A7CCC8ACFA0B7 NextDNS <team@nextdns.io>
  W: Some index files failed to download. They have been ignored, or old ones used instead.
  
  so, am i doing something amiss?
- R_P_M
  
  9 days ago
  
  Reported - view
  No, I'm not seeing anything wrong with what you've done. You have the correct GPG key, no need to update it.
  
  I do not know why it's being listed as "invalid" it's not being reported as such on my setup.
  
  A long shot, maybe check the system date is correct?
- Christopher_H
  
  9 days ago
  
  Reported - view
  date&time is accurate.
  
  (/e continues to be confused)
- R_P_M
  
  9 days ago
  
  Reported - view
  Wait a minute! I've just seen the problem. Sorry I didn't see it earlier, suffering with an allergy affecting my nose today (difficult to concentrate on things).
  
  It's the location of the GPG key file that's wrong! It should be in "/etc/apt/trusted.gpg.d/" NOT "/etc/apt/keyrings/".
  
  First copy the key file into the right location:
  
  sudo cp /etc/apt/keyrings/nextdns.gpg /etc/apt/trusted.gpg.d/nextdns.gpg
  
  Then delete old wrong location file:
  
  sudo rm -i /etc/apt/keyrings/nextdns.gpg
  
  Lastly check with:
  
  sudo apt update
- Christopher_H
  
  8 days ago
  
  Reported - view
  sorry to continue to be of bother, but, here is what occurred:
  
  sudo cp /etc/apt/keyrings/nextdns.gpg /etc/apt/trusted.gpg.d/nextdns.gpg
  {nothing happened, returned to _ prompt}
  
  sudo rm -i /etc/apt/keyrings/nextdns.gpg
  {rm: remove regular file '/etc/apt/keyrings/nextdns.gpg'? y}
  
  sudo apt update
  
  Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
  Hit:2 http://us.archive.ubuntu.com/ubuntu jammy InRelease
  Get:3 https://repo.nextdns.io/deb stable InRelease [8490 B]
  Get:4 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
  Err:3 https://repo.nextdns.io/deb stable InRelease
  The following signatures were invalid: EXPKEYSIG 467A7CCC8ACFA0B7 NextDNS <team@nextdns.io>
  Get:5 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease [127 kB]
  Get:6 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [1968 kB]
  Get:7 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [2193 kB]
  Get:8 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages [570 kB]
  Get:9 http://security.ubuntu.com/ubuntu jammy-security/main amd64 DEP-11 Metadata [43.1 kB]
  Get:10 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 DEP-11 Metadata [208 B]
  Get:11 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [958 kB]
  Get:12 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages [731 kB]
  Get:13 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 DEP-11 Metadata [103 kB]
  Get:14 http://us.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 DEP-11 Metadata [212 B]
  Get:15 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1180 kB]
  Get:16 http://security.ubuntu.com/ubuntu jammy-security/universe i386 Packages [648 kB]
  Get:17 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 DEP-11 Metadata [125 kB]
  Get:18 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 DEP-11 Metadata [208 B]
  Get:19 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe i386 Packages [753 kB]
  Get:20 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 DEP-11 Metadata [356 kB]
  Get:21 http://us.archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 DEP-11 Metadata [940 B]
  Get:22 http://us.archive.ubuntu.com/ubuntu jammy-backports/main amd64 DEP-11 Metadata [5320 B]
  Get:23 http://us.archive.ubuntu.com/ubuntu jammy-backports/restricted amd64 DEP-11 Metadata [216 B]
  Get:24 http://us.archive.ubuntu.com/ubuntu jammy-backports/universe amd64 DEP-11 Metadata [17.7 kB]
  Get:25 http://us.archive.ubuntu.com/ubuntu jammy-backports/multiverse amd64 DEP-11 Metadata [212 B]
  Fetched 10.0 MB in 10s (1011 kB/s)
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  4 packages can be upgraded. Run 'apt list --upgradable' to see them.
  W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.nextdns.io/deb stable InRelease: The following signatures were invalid: EXPKEYSIG 467A7CCC8ACFA0B7 NextDNS <team@nextdns.io>
  W: Failed to fetch https://repo.nextdns.io/deb/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG 467A7CCC8ACFA0B7 NextDNS <team@nextdns.io>
  W: Some index files failed to download. They have been ignored, or old ones used instead.
  
  does anything attempted have any relation to background services? themes or color schemes chosen? mouse pointer speed? \o/
  
  Thank you for your continued assistance to this albeit semi-clueless Kununtu user.
- R_P_M
  
  8 days ago
  
  Reported - view
  Urgh, still using old file data.
  
  sudo touch -m /etc/apt/sources.list.d/nextdns.list
  
  sudo apt update
  
  Note: This needs to be working otherwise you won’t get any new updates to the NextDNS CLI (thankfully none have been released so far while trying to fix this)
- Christopher_H
  
  8 days ago
  
  Reported - view
  sudo touch -m /etc/apt/sources.list.d/nextdns.list
  {nothing happened, returned to _ prompt}
  
  sudo apt update
  Get:1 https://repo.nextdns.io/deb stable InRelease [8490 B]
  Err:1 https://repo.nextdns.io/deb stable InRelease
  The following signatures were invalid: EXPKEYSIG 467A7CCC8ACFA0B7 NextDNS <team@nextdns.io>
  Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
  Hit:3 http://us.archive.ubuntu.com/ubuntu jammy InRelease
  Get:4 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
  Get:5 http://security.ubuntu.com/ubuntu jammy-security/main amd64 DEP-11 Metadata [43.1 kB]
  Get:6 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 DEP-11 Metadata [208 B]
  Get:7 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 DEP-11 Metadata [125 kB]
  Get:8 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 DEP-11 Metadata [208 B]
  Get:9 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease [127 kB]
  Get:10 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages [731 kB]
  Get:11 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [2193 kB]
  Get:12 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 DEP-11 Metadata [103 kB]
  Get:13 http://us.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 DEP-11 Metadata [212 B]
  Get:14 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1180 kB]
  Get:15 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 DEP-11 Metadata [356 kB]
  Get:16 http://us.archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 DEP-11 Metadata [940 B]
  Get:17 http://us.archive.ubuntu.com/ubuntu jammy-backports/main amd64 DEP-11 Metadata [5308 B]
  Get:18 http://us.archive.ubuntu.com/ubuntu jammy-backports/restricted amd64 DEP-11 Metadata [212 B]
  Get:19 http://us.archive.ubuntu.com/ubuntu jammy-backports/universe amd64 DEP-11 Metadata [17.8 kB]
  Get:20 http://us.archive.ubuntu.com/ubuntu jammy-backports/multiverse amd64 DEP-11 Metadata [212 B]
  Fetched 5148 kB in 6s (806 kB/s)
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  1 package can be upgraded. Run 'apt list --upgradable' to see it.
  W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.nextdns.io/deb stable InRelease: The following signatures were invalid: EXPKEYSIG 467A7CCC8ACFA0B7 NextDNS <team@nextdns.io>
  W: Failed to fetch https://repo.nextdns.io/deb/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG 467A7CCC8ACFA0B7 NextDNS <team@nextdns.io>
  W: Some index files failed to download. They have been ignored, or old ones used instead.
  
  what is causing the above lack of effect?
  
  i am logged into an Administrator-privileged account.
- R_P_M
  
  7 days ago
  
  Reported - view
  Aargh! Stupid thing. There’s no reason why it would be doing this.
  
  See if this command shows the NextDNS gpg key in the right location and has not been set as expired:
  
  apt-key list
  
  This will list all keys not just NextDNS one, ignore the others.
- Christopher_H
  
  7 days ago
  
  Reported - view
  apt-key list
  Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
  /etc/apt/trusted.gpg.d/nextdns.gpg
  ----------------------------------
  pub   rsa3072 2021-04-18 [SC] [expires: 2033-04-16]
        AD34 842B F3C8 0F65 6A83 3F66 467A 7CCC 8ACF A0B7
  uid           [ unknown] NextDNS <team@nextdns.io>
  sub   rsa3072 2021-04-18 [E] [expires: 2033-04-16]
  
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg
  ------------------------------------------------------
  #####
  
  [ unknown] Ubuntu CD Image Automatic Signing Key (2012) <cdimage@ubuntu.com>
  
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
  ------------------------------------------------------
  #####
  
  [unknown] Ubuntu Archive Automatic Signing Key (2018) <ftpmaster@ubuntu.com>
  
  --------------------------------------------------------------------------------------------
  
  What command need I use since Kubuntu/Ubuntu/Linux abandoned apt-key list?
- R_P_M
  
  7 days ago
  
  Reported - view
  That’s ok, it’s just a warning you can ignore. The warning just means that it (apt-key) will be removed in the future and to not write any piece of software to access it going forward (i.e. don’t rely on it being there forever).
  
  We have the info required from apt-key command anyway so not to worry.
  
  From the output details, I see nothing wrong listed with the GPG key. It’s a total mystery why it will not see it as valid.
  
  This is probably the last thing we can check before just deleting the repo and starting again.
  Check the contents of the NextDNS source repo file:
  
  cat /etc/apt/sources.list.d/nextdns.list
  
  You don’t need to know what it outputs but look out for anything in square brackets “[ ]”.
- Christopher_H
  
  7 days ago
  
  Reported - view
  output from cat /etc/apt/sources.list.d/nextdns.list is:
  
  deb [signed-by=/usr/share/keyrings/nextdns.gpg] https://repo.nextdns.io/deb stable main
- R_P_M
  
  7 days ago
  
  Reported - view
  Ah, there it is, the last piece of the puzzle. The bit within the square brackets is pointing to the wrong outdated file. That is why it kept complaining despite having an up to date version already there.
  
  Ok start by removing the contents within the square brackets and then the brackets themselves, so that the file only has "deb https://repo.nextdns.io/deb stable main" in it.
  
  sudo nano /etc/apt/sources.list.d/nextdns.list
  
  Once you have removed the square brackets, use "ctrl+s" to save and to exit use "ctrl+x".
  
  Then hopefully "sudo apt update" will no longer complain.
- Christopher_H
  
  7 days ago
  
  Reported - view
  I think some-amount of progress has been accomplished.
  
  sudo apt update
  Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
  Hit:2 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
  Hit:3 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
  Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
  Get:5 https://repo.nextdns.io/deb stable InRelease [8490 B]
  Get:6 https://repo.nextdns.io/deb stable/main i386 Packages [423 B]
  Get:7 https://repo.nextdns.io/deb stable/main amd64 Packages [426 B]
  Fetched 9339 B in 1s (8651 B/s)
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  2 packages can be upgraded. Run 'apt list --upgradable' to see them.
  
  apt list --upgradable
  Listing... Done
  nextdns/stable 1.43.5 amd64 [upgradable from: 1.37.11]
  packagekit/jammy-updates 1.2.5-2ubuntu3 amd64 [upgradable from: 1.2.5-2ubuntu2]
  
  However, running the sudo apt update does not seem to convince the operating system to actually, you know, update; with continued response of 2 packages can be upgraded. Run 'apt list --upgradable' to see them.
  
  is not apt update the same functionality as Discover / Updates program?
  
  edit:
  
  also, WHAT caused this problem? User error? Phase of the Moon? Gravity Wave? Neutrino flux? ;) So as to prevent this problem from occurring in the future,....
- Christopher_H
  
  7 days ago
  
  Reported - view
  oh, neat, rinsing & repeating Discover updating, and now it shows
  
  nextdns 1.37.11->1.43.5
  
  and now shows some other weird problem from Discover when selecting nextdns alone to update:
  
  Cannot obtain lock:
  E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
  
  sudo dpkg --configure -a
  dpkg: dependency problems prevent configuration of packagekit-tools:
  packagekit-tools depends on packagekit (= 1.2.5-2ubuntu3); however:
  Package packagekit is not installed.
  
  dpkg: error processing package packagekit-tools (--configure):
  dependency problems - leaving unconfigured
  Errors were encountered while processing:
  packagekit-tools
  
  so, WHAT are these problems coming from? I need admit, this is becoming frustrating, as i am lacking understanding as to the source of these arguably, weird, problems.
  
  edit: Discover is also complaining about packagekit 1.2.5-2ubuntu3 having crashed, i tried to submit bugreport, but only thing that happens is the browser is launched. \o/
  
  I include, as these all might be related(?)
- Christopher_H
  
  7 days ago
  
  Reported - view
  ok.
  
  in considering self-originated problems, i ran SpinRite v6.1@L2 on the hard drive, then tried installing DEBSUMS to verify all the locally-installed files,... which seemed to initially stumble, then suggested I run sudo apt --fix-broken install which seemed to fix the previously mentioned package failure, then Discover was able to complete nextdns' update, which is now at v1.43.5.
  
  SO.
  
  I think SpinRite fixed some subtle harddrive sector reading problems which was causing some of the weirdness.
  
  it SEEMS everything is working,...
  
  Thank you SOOOOOOOOOOOOOOOOOOO much for your assistance in this :D
- R_P_M
  
  7 days ago
  
  Reported - view
  Oh, interesting, I didn’t think about hard drive problems. Just how old is the hard drive and has it been used every day?

Content aside

6 days agoLast active
27Replies
101Views
2 Following

An Error occurred during Signature Verification

27 replies

Content aside

Home

Tags