{gelöst-solved} Signatur-Fehler nach letztem full-upgrade

Started by samoht, 2024/07/25, 13:47:10

Previous topic - Next topic
Print
Go Down Pages1 2
User actions

samoht

2024/07/25, 13:47:10 Last Edit: 2024/07/26, 14:27:31 by samoht
Nach dem letzen full-upgrade am Rechner eines Freundes bekomme ich den/die folgenden Fehler.

Code Select
# LANG=C apt update
Hit:1 https://linux.teamviewer.com/deb stable InRelease
Hit:2 http://dl.google.com/linux/earth/deb stable InRelease
Err:1 https://linux.teamviewer.com/deb stable InRelease
  At least one invalid signature was encountered.
Hit:3 http://deb.anydesk.com all InRelease
Hit:4 https://packages.siduction.org/extra unstable InRelease
Hit:5 https://packages.siduction.org/extra experimental InRelease
Hit:6 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:7 https://packages.siduction.org/fixes unstable InRelease
Err:2 http://dl.google.com/linux/earth/deb stable InRelease
  At least one invalid signature was encountered.
Hit:8 https://deb.debian.org/debian testing InRelease
Hit:9 https://deb.debian.org/debian unstable InRelease
Get:10 https://incoming.debian.org/debian-buildd buildd-unstable InRelease [53,8 kB]
Hit:11 https://deb.debian.org/debian experimental InRelease
Err:3 http://deb.anydesk.com all InRelease
  At least one invalid signature was encountered.
Err:4 https://packages.siduction.org/extra unstable InRelease
  At least one invalid signature was encountered.
Err:5 https://packages.siduction.org/extra experimental InRelease
  At least one invalid signature was encountered.
Err:6 https://dl.google.com/linux/chrome/deb stable InRelease
  At least one invalid signature was encountered.
Err:7 https://packages.siduction.org/fixes unstable InRelease
  At least one invalid signature was encountered.
Err:8 https://deb.debian.org/debian testing InRelease
  At least one invalid signature was encountered.
Err:9 https://deb.debian.org/debian unstable InRelease
  At least one invalid signature was encountered.
Err:11 https://deb.debian.org/debian experimental InRelease
  At least one invalid signature was encountered.
Err:10 https://incoming.debian.org/debian-buildd buildd-unstable InRelease
  At least one invalid signature was encountered.
Fetched 53,8 kB in 1s (54,6 kB/s)
All packages are up to date.
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://linux.teamviewer.com/deb stable InRelease: At least one invalid signature was encountered.
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/earth/deb stable InRelease: At least one invalid signature was encountered.
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.anydesk.com all InRelease: At least one invalid signature was encountered.
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.siduction.org/extra unstable InRelease: At least one invalid signature was encountered.
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.siduction.org/extra experimental InRelease: At least one invalid signature was encountered.
Warning: 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: At least one invalid signature was encountered.
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.siduction.org/fixes unstable InRelease: At least one invalid signature was encountered.
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.debian.org/debian testing InRelease: At least one invalid signature was encountered.
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.debian.org/debian unstable InRelease: At least one invalid signature was encountered.
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.debian.org/debian experimental InRelease: At least one invalid signature was encountered.
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://incoming.debian.org/debian-buildd buildd-unstable InRelease: At least one invalid signature was encountered.
Warning: Failed to fetch http://deb.anydesk.com/dists/all/InRelease  At least one invalid signature was encountered.
Warning: Failed to fetch https://deb.debian.org/debian/dists/testing/InRelease  At least one invalid signature was encountered.
Warning: Failed to fetch https://deb.debian.org/debian/dists/unstable/InRelease  At least one invalid signature was encountered.
Warning: Failed to fetch https://deb.debian.org/debian/dists/experimental/InRelease  At least one invalid signature was encountered.
Warning: Failed to fetch https://incoming.debian.org/debian-buildd/dists/buildd-unstable/InRelease  At least one invalid signature was encountered.
Warning: Failed to fetch https://dl.google.com/linux/chrome/deb/dists/stable/InRelease  At least one invalid signature was encountered.
Warning: Failed to fetch http://dl.google.com/linux/earth/deb/dists/stable/InRelease  At least one invalid signature was encountered.
Warning: Failed to fetch https://packages.siduction.org/extra/dists/unstable/InRelease  At least one invalid signature was encountered.
Warning: Failed to fetch https://packages.siduction.org/extra/dists/experimental/InRelease  At least one invalid signature was encountered.
Warning: Failed to fetch https://packages.siduction.org/fixes/dists/unstable/InRelease  At least one invalid signature was encountered.
Warning: Failed to fetch https://linux.teamviewer.com/deb/dists/stable/InRelease  At least one invalid signature was encountered.
Warning: Some index files failed to download. They have been ignored, or old ones used instead.

Das full-upgrade verlief ohne Fehlermeldugen und das siduction-System arbeitet normal - mit Ausnahme des kernel-remove-Befehls https://forum.siduction.org/index.php?topic=9413.0

unklarer

#1
2024/07/25, 16:24:00 Last Edit: 2024/07/25, 16:29:31 by unklarer
entferne alle (!) Fremdquellen ( # ) zeige
Code Select
inxi -rund wiederhole dann das mit debian-unstable -und siduction

inxi sollte so aussehen:
Code Select
inxi -r
Repos:
  No active apt repos in: /etc/apt/sources.list
  No active apt repos in: /etc/apt/sources.list.d/dbgsym.list
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb https://deb.debian.org/debian/ unstable main non-free-firmware
    2: deb-src https://deb.debian.org/debian/ unstable main non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/extra.list
    1: deb https://ftp.gwdg.de/pub/linux/siduction/extra unstable main non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/fixes.list
    1: deb https://ftp.gwdg.de/pub/linux/siduction/fixes unstable main non-free-firmware

michaa7

#2
2024/07/25, 19:26:30 Last Edit: 2024/07/25, 19:41:15 by michaa7
Ich habe den gleichen Fehler, auch nach heutigen d-u am morgen. Und er tritt weiter auf nach deaktivieren der Fremdrepos.

Zudem habe ich debian, fixes und extra jeweils einzeln getestet. Der Fehler tritt immer auf, egal was ich an oder ausschalte.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

unklarer

#3
2024/07/25, 19:54:21
mit anderen Spiegel auch?

michaa7

#4
2024/07/25, 19:57:58 Last Edit: 2024/07/25, 20:05:00 by michaa7
ich verwende deb.debian.org, aber der Fehler passiert ja auch wenn ich auch diesen deaktiviere und nur ein der beiden fixes oder extra repos aktiviere.

Und die mehr oder weniger gleichen repos funktionieren hier auf dem Laptop auch noch *nach* heutigem d-u, inklusive deb.debian.org.

Irgendetwas liegt also auf meinem desktop Rechner quer, aber ich habe keinen Plan was und wo ...

Ok, you can't code, but you still might be able to write a bug report for Debian's sake

unklarer

#5
2024/07/25, 20:02:46
verwende ich auch und habe den Fehler nicht.

Hier wurden heute nach einer Neuinstallation xfce (vom 15.05.2024) 808 Pakete aktualisiert, und nichts dergleichen...
Noch eine blöde Frage, auch beim neuen solver?

michaa7

#6
2024/07/25, 20:07:02 Last Edit: 2024/07/25, 20:11:53 by michaa7
Ich verwende immer den neuen solver, habe aber auch ohne probiert.  Immer das gleiche problem. Und, siehe oben, auf meinen Laptop habe ich diese Probleme nicht. Ich verwende allerdings auf dem Desktop den apt-cacher-ng, nur der tut es auch seit langem.

Nur was ist das für ein Drecks Programm, wenn es angebliche ein Fehler bemerkt, und verschweigt welche signatur angeblich ungültig ist. Das programm muss das ja wissen. Ich habe auch keinen Plan wie man das program dazu bewegen könnte gesprächiger zu sein.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

unklarer

#7
2024/07/25, 20:13:24
Hmm.

keine Lösung...   :-\    Nachdenken ist angesagt.   ;D

michaa7

#8
2024/07/25, 20:27:09
Ist es normal dass in /etc/apt/trusted.gpg.d alle möglichen signaturen vorhanden sind, aber keine für sid/unstable? Nutzen die bullseye signaturen?

Code Select
:/etc/apt/trusted.gpg.d# ls
debian-archive-bookworm-automatic.asc           siduction-archive-keyring.gpg
debian-archive-bookworm-security-automatic.asc  skype-keyring.gpg
debian-archive-bookworm-stable.asc              vivaldi-33EAAB8E.gpg
debian-archive-bullseye-automatic.asc           vivaldi-74C35BC8.gpg
debian-archive-bullseye-security-automatic.asc  vivaldi-C27AA466.gpg
debian-archive-bullseye-stable.asc              vivaldi-snapshot-33EAAB8E.gpg
debian-archive-buster-automatic.asc             vivaldi-snapshot-4218647E.gpg
debian-archive-buster-security-automatic.asc    vivaldi-snapshot-74C35BC8.gpg
debian-archive-buster-stable.asc                vivaldi-snapshot-C27AA466.gpg
packages.vivaldi.gpg


Wobei es mich wundert das signal unsigniert ist ...
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

unklarer

#9
2024/07/25, 21:44:38 Last Edit: 2024/07/25, 21:48:45 by unklarer
*guugeln* brachte diese (zwei) Lösungsansätze. Also guckst du mal bei dir.   ;)
Alles andere betrifft Docker.

https://superuser.com/questions/1746879/unable-to-run-apt-update-at-least-one-invalid-signature-was-encountered
https://askubuntu.com/questions/1489677/at-least-one-invalid-signature-was-encountered

bei mir:
Code Select
/etc/apt/trusted.gpg.d$ ls
debian-archive-bookworm-automatic.asc           debian-archive-bullseye-security-automatic.asc  debian-archive-buster-stable.asc
debian-archive-bookworm-security-automatic.asc  debian-archive-bullseye-stable.asc              obs-npreining.asc
debian-archive-bookworm-stable.asc              debian-archive-buster-automatic.asc             siduction-archive-keyring.gpg
debian-archive-bullseye-automatic.asc           debian-archive-buster-security-automatic.asc

michaa7

#11
2024/07/26, 01:34:45 Last Edit: 2024/07/26, 04:25:41 by michaa7
Quote from: Carnophage on 2024/07/25, 23:42:23
das hat mir geholfen: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071368#48

Mein Rettung :) , das war es.

Für alle die das gleiche Problem  haben (wobei ich mich über die Exklusivität wundere):
Code Select
apt purge gpgv-from-sq gpgv-sq ist die Lösung!!!

Danke!!!
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

edlin

#12
2024/07/26, 10:04:03
Quote from: michaa7 on 2024/07/26, 01:34:45... wobei ich mich über die Exklusivität wundere):
Nun, ich wundere mich, wie die Pakete gpgv-from-sq und gpgv-sq auf deine Platte kamen, bei einer Standardinstallation von Siduction KDE/Plasma sind sie jedenfalls nicht dabei. Das erklärt wohl die Exclusivität.

edlin
,,Ein kluger Mann macht nicht alle Fehler selber. Er lässt auch anderen eine Chance."

Winston Churchill

Carnophage

#14
2024/07/26, 11:48:38
Quote from: edlin on 2024/07/26, 10:04:03
Quote from: michaa7 on 2024/07/26, 01:34:45... wobei ich mich über die Exklusivität wundere):
Nun, ich wundere mich, wie die Pakete gpgv-from-sq und gpgv-sq auf deine Platte kamen, bei einer Standardinstallation von Siduction KDE/Plasma sind sie jedenfalls nicht dabei. Das erklärt wohl die Exclusivität.

edlin

Sorry for jumping in with English but my German is not good enough, well I didn't install those on purpose, they came as a part of daily upgrade

Code Select

Start-Date: 2024-07-25  09:06:11
Commandline: apt --solver 3.0 full-upgrade
Install: gpgv-sq:amd64 (0.9.0-1, automatic), gpgv-from-sq:amd64 (0.9.0-1, automatic), sq:amd64 (0.37.0-1, automatic)
Upgrade: dpkg:amd64 (1.22.8, 1.22.9), udev:amd64 (256.2-1, 256.4-1), systemd-container:amd64 (256.2-1, 256.4-1), libnss-myhostname:amd64 (256.2-1, 256.4-1), gpg:amd64 (2.2.43-7, 2.2.43-8), systemd-timesyncd:amd64 (256.2-1, 256.4-1), libpam-systemd:amd64 (256.2-1, 256.4-1), zip:amd64 (3.0-13, 3.0-14), libgs10-common:amd64 (10.03.1~dfsg-1, 10.03.1~dfsg-2), libgs10:amd64 (10.03.1~dfsg-1, 10.03.1~dfsg-2), libsystemd0:amd64 (256.2-1, 256.4-1), gnupg2:amd64 (2.2.43-7, 2.2.43-8), libnss-systemd:amd64 (256.2-1, 256.4-1), libudev-dev:amd64 (256.2-1, 256.4-1), gnupg:amd64 (2.2.43-7, 2.2.43-8), gpg-wks-server:amd64 (2.2.43-7, 2.2.43-8), systemd:amd64 (256.2-1, 256.4-1), libudev1:amd64 (256.2-1, 256.4-1), gpg-agent:amd64 (2.2.43-7, 2.2.43-8), firefox:amd64 (128.0-1, 128.0.2-1), systemd-cryptsetup:amd64 (256.2-1, 256.4-1), dpkg-dev:amd64 (1.22.8, 1.22.9), ghostscript:amd64 (10.03.1~dfsg-1, 10.03.1~dfsg-2), libnss-mymachines:amd64 (256.2-1, 256.4-1), gpgv:amd64 (2.2.43-7, 2.2.43-8), systemd-coredump:amd64 (256.2-1, 256.4-1), gpgsm:amd64 (2.2.43-7, 2.2.43-8), libdpkg-perl:amd64 (1.22.8, 1.22.9), libsystemd-shared:amd64 (256.2-1, 256.4-1), libcares2:amd64 (1.32.2-2, 1.32.3-1), dirmngr:amd64 (2.2.43-7, 2.2.43-8), systemd-sysv:amd64 (256.2-1, 256.4-1), gnupg-utils:amd64 (2.2.43-7, 2.2.43-8), gnupg-l10n:amd64 (2.2.43-7, 2.2.43-8), gpg-wks-client:amd64 (2.2.43-7, 2.2.43-8), libgs-common:amd64 (10.03.1~dfsg-1, 10.03.1~dfsg-2), gpgconf:amd64 (2.2.43-7, 2.2.43-8)
End-Date: 2024-07-25  09:07:01


it happened for 2 of my laptops, I found the issue because the third one that was not yet upgraded didn't have those issues on apt update (but it also didn't want to install those rust based rewrites, maybe it's the difference on when upgrade was to be run)
Print
Go Up Pages1 2
User actions