1
0
Fork 0
mirror of https://github.com/pikvm/pikvm.git synced 2026-03-02 18:16:56 -05:00

error: GPGME error: No data #1086

Open
opened 2026-02-20 14:10:54 -05:00 by deekerman · 24 comments
Owner

Originally created by @dtech77pl on GitHub (Nov 21, 2025).

Originally assigned to: @mdevaev on GitHub.

Describe the bug
A clear and concise description of what the bug is.
When I try to update to the latest with pacman -Syu
Get this error message:

error: GPGME error: No data

To Reproduce
Steps to reproduce the behavior, like:

  1. Go to '...'
    start: pacman -Syu
  2. See error
    pacman -Syy
    error: GPGME error: No data
    error: GPGME error: No data
    error: GPGME error: No data
    error: GPGME error: No data
    error: GPGME error: No data
    :: Synchronizing package databases...
    core 15.5 KiB 12.8 KiB/s 00:01 [########################################################] 100%
    extra 15.5 KiB 387 KiB/s 00:00 [########################################################] 100%
    community 15.5 KiB 352 KiB/s 00:00 [########################################################] 100%
    alarm 15.5 KiB 323 KiB/s 00:00 [########################################################] 100%
    aur 15.5 KiB 352 KiB/s 00:00 [########################################################] 100%
    pikvm 14.5 KiB 78.7 KiB/s 00:00 [########################################################] 100%
    error: GPGME error: No data
    error: GPGME error: No data
    error: GPGME error: No data
    error: GPGME error: No data
    error: GPGME error: No data
    error: failed to synchronize all databases (unexpected error)

PiKVM info:

Base: Raspberry Pi Compute Module 4 Rev 1.1
Platform: v4mini-hdmi-rpi4

  • Raspberry Pi board version [e.g. RPi 4]

  • PiKVM platform [e.g. v2-hdmi]

  • Video capture type [e.g. CSI bridge]

  • KVMD version: pacman -Q | grep kvmd
    kvmd 4.111-1
    kvmd-fan 0.32-1
    kvmd-platform-v4mini-hdmi-rpi4 4.111-1
    kvmd-webterm 0.50-1

  • uStreamer version: pacman -Q | grep ustreamer
    ustreamer 6.41-1

  • Linux kernel: uname -a
    6.6.45-13-rpi #1 SMP PREEMPT Tue May 27 17:29:07 UTC 2025 aarch64 GNU/Linux

Additional context
Add any other context about the problem here.
I try this one, but no luck still the same issue.

rw
pacman-key --init
pacman-key --populate
pacman-key --keyserver hkps://keyserver.ubuntu.com -r 912C773ABBD1B584
pacman-key --lsign-key 912C773ABBD1B584
ro

Originally created by @dtech77pl on GitHub (Nov 21, 2025). Originally assigned to: @mdevaev on GitHub. **Describe the bug** A clear and concise description of what the bug is. When I try to update to the latest with pacman -Syu Get this error message: error: GPGME error: No data **To Reproduce** Steps to reproduce the behavior, like: 1. Go to '...' start: pacman -Syu 5. See error pacman -Syy error: GPGME error: No data error: GPGME error: No data error: GPGME error: No data error: GPGME error: No data error: GPGME error: No data :: Synchronizing package databases... core 15.5 KiB 12.8 KiB/s 00:01 [########################################################] 100% extra 15.5 KiB 387 KiB/s 00:00 [########################################################] 100% community 15.5 KiB 352 KiB/s 00:00 [########################################################] 100% alarm 15.5 KiB 323 KiB/s 00:00 [########################################################] 100% aur 15.5 KiB 352 KiB/s 00:00 [########################################################] 100% pikvm 14.5 KiB 78.7 KiB/s 00:00 [########################################################] 100% error: GPGME error: No data error: GPGME error: No data error: GPGME error: No data error: GPGME error: No data error: GPGME error: No data error: failed to synchronize all databases (unexpected error) **PiKVM info:** Base: Raspberry Pi Compute Module 4 Rev 1.1 Platform: v4mini-hdmi-rpi4 - Raspberry Pi board version [e.g. RPi 4] - PiKVM platform [e.g. v2-hdmi] - Video capture type [e.g. CSI bridge] - KVMD version: `pacman -Q | grep kvmd` kvmd 4.111-1 kvmd-fan 0.32-1 kvmd-platform-v4mini-hdmi-rpi4 4.111-1 kvmd-webterm 0.50-1 - uStreamer version: `pacman -Q | grep ustreamer` ustreamer 6.41-1 - Linux kernel: `uname -a` 6.6.45-13-rpi #1 SMP PREEMPT Tue May 27 17:29:07 UTC 2025 aarch64 GNU/Linux **Additional context** Add any other context about the problem here. I try this one, but no luck still the same issue. rw pacman-key --init pacman-key --populate pacman-key --keyserver hkps://keyserver.ubuntu.com -r 912C773ABBD1B584 pacman-key --lsign-key 912C773ABBD1B584 ro
Author
Owner

@dtech77pl commented on GitHub (Nov 21, 2025):

Even try this one, and no luck

sudo rm -R /var/lib/pacman/sync

@dtech77pl commented on GitHub (Nov 21, 2025): Even try this one, and no luck sudo rm -R /var/lib/pacman/sync
Author
Owner

@mdevaev commented on GitHub (Nov 21, 2025):

If you have a physicall access to your device, a recommend to replace memory SD card and perform reflashing.

If the device is far away from you, then it is better not to update it, and wait until you have physical access.

@mdevaev commented on GitHub (Nov 21, 2025): If you have a physicall access to your device, a recommend to replace memory SD card and perform reflashing. If the device is far away from you, then it is better not to update it, and wait until you have physical access.
Author
Owner

@dtech77pl commented on GitHub (Nov 22, 2025):

Unfortunately I do not have physical access, will have to manage it.
Thank you for information.
Do you know why this happened?, and what can be done to avoid it in future?

@dtech77pl commented on GitHub (Nov 22, 2025): Unfortunately I do not have physical access, will have to manage it. Thank you for information. Do you know why this happened?, and what can be done to avoid it in future?
Author
Owner

@mdevaev commented on GitHub (Nov 22, 2025):

Most likely, the memory card is dying. When this happens, it can cause strange and unpredictable errors. This rarely happens, but if I see something atypical, it's the memory card's fault. If you want, you can buy a new Kingston Industrial series card, I use these, and they work great.

@mdevaev commented on GitHub (Nov 22, 2025): Most likely, the memory card is dying. When this happens, it can cause strange and unpredictable errors. This rarely happens, but if I see something atypical, it's the memory card's fault. If you want, you can buy a new Kingston Industrial series card, I use these, and they work great.
Author
Owner

@dtech77pl commented on GitHub (Nov 22, 2025):

Much appreciated your support, will go with the Kingston Industrial cards.

@dtech77pl commented on GitHub (Nov 22, 2025): Much appreciated your support, will go with the Kingston Industrial cards.
Author
Owner

@mdevaev commented on GitHub (Nov 22, 2025):

Ur welcome 👌

@mdevaev commented on GitHub (Nov 22, 2025): Ur welcome 👌
Author
Owner

@dtech77pl commented on GitHub (Feb 7, 2026):

HI,

I replaced the card with a new one, but the problem persists. I have used the Kingston Industrial card with the new setup, but I am still receiving the same error.

error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
:: Synchronizing package databases...
core 15.5 KiB 52.3 KiB/s 00:00 [########################################################] 100%
extra 15.5 KiB 277 KiB/s 00:00 [########################################################] 100%
community 15.5 KiB 387 KiB/s 00:00 [########################################################] 100%
alarm 15.5 KiB 387 KiB/s 00:00 [########################################################] 100%
aur 15.5 KiB 352 KiB/s 00:00 [########################################################] 100%
PikVM is up to date
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: failed to synchronize all databases (unexpected error)

Was able to complete all updates on the master site. When the card was sent to the destination, all problems started immediately.
Do you have any idea what can be done?

@dtech77pl commented on GitHub (Feb 7, 2026): HI, I replaced the card with a new one, but the problem persists. I have used the Kingston Industrial card with the new setup, but I am still receiving the same error. error: GPGME error: No data error: GPGME error: No data error: GPGME error: No data error: GPGME error: No data error: GPGME error: No data :: Synchronizing package databases... core 15.5 KiB 52.3 KiB/s 00:00 [########################################################] 100% extra 15.5 KiB 277 KiB/s 00:00 [########################################################] 100% community 15.5 KiB 387 KiB/s 00:00 [########################################################] 100% alarm 15.5 KiB 387 KiB/s 00:00 [########################################################] 100% aur 15.5 KiB 352 KiB/s 00:00 [########################################################] 100% PikVM is up to date error: GPGME error: No data error: GPGME error: No data error: GPGME error: No data error: GPGME error: No data error: GPGME error: No data error: failed to synchronize all databases (unexpected error) Was able to complete all updates on the master site. When the card was sent to the destination, all problems started immediately. Do you have any idea what can be done?
Author
Owner

@mdevaev commented on GitHub (Feb 7, 2026):

Where did you get this OS image? I don't like this part of message:

PikVM is up to date

Maybe you downloaded some fake image from third-party sites? Please use an image from this page: https://docs.pikvm.org/flashing_os

@mdevaev commented on GitHub (Feb 7, 2026): Where did you get this OS image? I don't like this part of message: ``` PikVM is up to date ``` Maybe you downloaded some fake image from third-party sites? Please use an image from this page: https://docs.pikvm.org/flashing_os
Author
Owner

@dtech77pl commented on GitHub (Feb 7, 2026):

As this was a new card, I had to reimage it from scract scratch.
I have followed the link you shared.

@dtech77pl commented on GitHub (Feb 7, 2026): As this was a new card, I had to reimage it from scract scratch. I have followed the link you shared.
Author
Owner

@dtech77pl commented on GitHub (Feb 7, 2026):

I have installed Border0 on it and can update this service without any trouble.

@dtech77pl commented on GitHub (Feb 7, 2026): I have installed Border0 on it and can update this service without any trouble.
Author
Owner

@mdevaev commented on GitHub (Feb 7, 2026):

I confused, is everything fine now?

@mdevaev commented on GitHub (Feb 7, 2026): I confused, is everything fine now?
Author
Owner

@dtech77pl commented on GitHub (Feb 7, 2026):

Still the same, I cannot update using:
pikvm-update or
pacman -Syu

The same error

@dtech77pl commented on GitHub (Feb 7, 2026): Still the same, I cannot update using: pikvm-update or pacman -Syu The same error
Author
Owner

@dtech77pl commented on GitHub (Feb 7, 2026):

Image
this is how it looks

@dtech77pl commented on GitHub (Feb 7, 2026): ![Image](https://github.com/user-attachments/assets/263f5f3d-e43e-4ed6-aab2-7a927ae5a167) this is how it looks
Author
Owner

@mdevaev commented on GitHub (Feb 7, 2026):

Which image exactly you tested? Give me a link.

@mdevaev commented on GitHub (Feb 7, 2026): Which image exactly you tested? Give me a link.
Author
Owner

@dtech77pl commented on GitHub (Feb 7, 2026):

This is a link:

https://files.pikvm.org/images/v4mini-hdmi-rpi4/aarch64/v4mini-hdmi-rpi4-aarch64-latest.img.xz

and the current version is:

Linux Tallinn-KVM 6.12.56-2-rpi #1 SMP PREEMPT Sat Nov 29 01:21:44 UTC 2025 aarch64 GNU/Linux

@dtech77pl commented on GitHub (Feb 7, 2026): This is a link: [https://files.pikvm.org/images/v4mini-hdmi-rpi4/aarch64/v4mini-hdmi-rpi4-aarch64-latest.img.xz](url) and the current version is: Linux Tallinn-KVM 6.12.56-2-rpi #1 SMP PREEMPT Sat Nov 29 01:21:44 UTC 2025 aarch64 GNU/Linux
Author
Owner

@mdevaev commented on GitHub (Feb 7, 2026):

What do you do immediately after flashing?

@mdevaev commented on GitHub (Feb 7, 2026): What do you do immediately after flashing?
Author
Owner

@dtech77pl commented on GitHub (Feb 7, 2026):

Update using the pikvm-update. To give you a complete picture:

  1. A brand new Kingston Industrial card was used.
  2. I have used an image from the shared link
  3. After installation, I did all updates, and all was working fine without any trouble.
  4. I keep a couple of days in my home before shipment, and no issues were found
  5. The SD card was sent to the destination and replaced.
  6. Immediately after the new SD card was installed in the destination, this problem happened.
@dtech77pl commented on GitHub (Feb 7, 2026): Update using the pikvm-update. To give you a complete picture: 1. A brand new Kingston Industrial card was used. 2. I have used an image from the shared link 3. After installation, I did all updates, and all was working fine without any trouble. 4. I keep a couple of days in my home before shipment, and no issues were found 5. The SD card was sent to the destination and replaced. 6. Immediately after the new SD card was installed in the destination, this problem happened.
Author
Owner

@mdevaev commented on GitHub (Feb 7, 2026):

Please try to remember what exactly you could have set or changed in the settings? This is a very specific problem and apparently it was caused by something that could be installed. Some specific settings or third-party software.

@mdevaev commented on GitHub (Feb 7, 2026): Please try to remember what exactly you could have set or changed in the settings? This is a very specific problem and apparently it was caused by something that could be installed. Some specific settings or third-party software.
Author
Owner

@dtech77pl commented on GitHub (Feb 7, 2026):

The only add-on software is:

I have the exact same setup at home with the same software, and everything works fine. These are all changes I have applied:

nano /etc/kvmd/override.yaml
kvmd:
tax:
click_delay: 1
long_click_delay: 11
hid:
mouse_alt:
device: /dev/kvmd-hid-mouse-alt
jiggler:
active: true

atx:
    click_delay: 1
    long_click_delay: 11
@dtech77pl commented on GitHub (Feb 7, 2026): The only add-on software is: - Tailscale [https://tailscale.com/](url) - Border0 [https://www.border0.com/](url) I have the exact same setup at home with the same software, and everything works fine. These are all changes I have applied: nano /etc/kvmd/override.yaml kvmd: tax: click_delay: 1 long_click_delay: 11 hid: mouse_alt: device: /dev/kvmd-hid-mouse-alt jiggler: active: true atx: click_delay: 1 long_click_delay: 11
Author
Owner

@mdevaev commented on GitHub (Feb 7, 2026):

How did you install tailscale and border0? From their repos?

@mdevaev commented on GitHub (Feb 7, 2026): How did you install tailscale and border0? From their repos?
Author
Owner

@intelfx commented on GitHub (Feb 7, 2026):

@dtech77pl Hi. This looks like a pacman-key database problem, not a pacman database problem. Dropping /var/lib/pacman/sync won't help.

  • Verify that the files in /usr/share/pacman/keyrings are superficially intact (ls -la /usr/share/pacman/keyrings, check for files with zero size)
  • pkill -9 gpg-agent && pkill -9 dirmngr, just for a good measure
  • rm -rf /etc/pacman.d/gnupg/* && pacman-key --init && pacman-key --populate archlinux && pacman-key --populate archlinuxarm

Then try updating again. If it persists, we'd like to investigate closer.

@intelfx commented on GitHub (Feb 7, 2026): @dtech77pl Hi. This looks like a pacman-key database problem, not a pacman database problem. Dropping `/var/lib/pacman/sync` won't help. - Verify that the files in `/usr/share/pacman/keyrings` are superficially intact (`ls -la /usr/share/pacman/keyrings`, check for files with zero size) - `pkill -9 gpg-agent && pkill -9 dirmngr`, just for a good measure - `rm -rf /etc/pacman.d/gnupg/* && pacman-key --init && pacman-key --populate archlinux && pacman-key --populate archlinuxarm` Then try updating again. If it persists, we'd like to investigate closer.
Author
Owner

@dtech77pl commented on GitHub (Feb 7, 2026):

Can this be related to the country? The device is located in Estonia/Tallinn.

After the first command:

Image

And after the change database:

Image

error still persist, even after reboot

@dtech77pl commented on GitHub (Feb 7, 2026): Can this be related to the country? The device is located in Estonia/Tallinn. After the first command: ![Image](https://github.com/user-attachments/assets/8443920a-de86-45b7-866c-1c665cb5b36e) And after the change database: ![Image](https://github.com/user-attachments/assets/56fdacdd-788d-4329-9eda-c5b1db3e9dd3) error still persist, even after reboot
Author
Owner

@dtech77pl commented on GitHub (Feb 7, 2026):

How did you install tailscale and border0? From their repos?

Tailscale:
pacman -Syu tailscale-pikvm

Border0:
bash <(curl https://download.border0.com/device-install.sh)
Then I need to add a connector:
sh <(curl -fsSL https://download.border0.com/connector/install.sh) --invite c**********

@dtech77pl commented on GitHub (Feb 7, 2026): > How did you install tailscale and border0? From their repos? Tailscale: pacman -Syu tailscale-pikvm Border0: bash <(curl https://download.border0.com/device-install.sh) Then I need to add a connector: sh <(curl -fsSL https://download.border0.com/connector/install.sh) --invite c**********
Author
Owner

@dtech77pl commented on GitHub (Feb 20, 2026):

Do you have any idea how to make it run?

@dtech77pl commented on GitHub (Feb 20, 2026): Do you have any idea how to make it run?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/pikvm-pikvm#1086
No description provided.