apt-get update ERRORS

[NickVeit]

I am not familiar with Ubuntu. My hosted Jamulus server 3.12.2 is now giving errors on upgrade. I've tried to install the new 3.12.3 but the same errors occur. Can anyone please advise?

root@localhost:~# sudo apt-get update
Hit:1 http://mirrors.linode.com/ubuntu noble InRelease
Hit:2 http://mirrors.linode.com/ubuntu noble-updates InRelease
Hit:3 http://mirrors.linode.com/ubuntu noble-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu noble-security InRelease
Get:5 https://github.com/jamulussoftware/jamulus/releases/latest/download ./ InR elease [1,698 B]
Err:5 https://github.com/jamulussoftware/jamulus/releases/latest/download ./ InR elease
The following signatures were invalid: EXPKEYSIG B1EF072B7BD7F31F The Jamulus Development Team (GPG key for signing Jamulus releases generated by the official deb repository) team@jamulus.io
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://github.com/jamulussoftware/jamulus/releases/latest/download ./ InRelease: The following signatures were invalid: EXPKEYSIG B1EF072B7BD7F31F The Jamulus Development Team (GPG key for signing Jamulus releases generated by the official deb repository) team@jamulus.io
W: Failed to fetch https://github.com/jamulussoftware/jamulus/releases/latest/download/./InRelease The following signatures were invalid: EXPKEYSIG B1EF072B7BD7F31F The Jamulus Development Team (GPG key for signing Jamulus releases generated by the official deb repository) team@jamulus.io
W: Some index files failed to download. They have been ignored, or old ones used instead.

[ann0see]

EXPKEYSIG

The key might have expired.

@corrados could you please regenerate and re add the GPG key? You were the one that created it initially

[ann0see]

No. Remove the files from your drive (GPG key, sources file). Then re run the script.

Probably something like

sudo rm /etc/apt/trusted.gpg.d/jamulus.asc /etc/apt/sources.list.d/jamulus.list
sudo ./setup_repo.sh && sudo apt install jamulus-headless

[NickVeit]

I removed those two files but the install script errored the same way. For info, are these "keyring" files OK?

root@localhost:/etc/apt/trusted.gpg.d# dir
jamulus.asc ubuntu-keyring-2012-cdimage.gpg
setup_repo.sh ubuntu-keyring-2018-archive.gpg

[ann0see]

Yes. Please do not remove the keyring files.
You should probably also try to see if the keys are in the keyring instead.

E.g:

apt-key list
sudo apt-key del <jamulus key you saw from the above command>

These commands may not work.

Please provide your exact outputs and commands.

[ann0see]

Otherwise next alternatives:

• install the Deb manually
• clear apt caches
• ask some LLM by giving it the exact error message.

LLM:

# 1. Wipe any stale Jamulus repo state (key + source list + cached metadata)
sudo rm -f /etc/apt/trusted.gpg.d/jamulus.asc /etc/apt/sources.list.d/jamulus.list
sudo rm -rf /var/lib/apt/lists/jamulus
sudo apt-get clean

# 2. Re-run the official setup script (downloads the current key + repo file fresh)
curl https://raw.githubusercontent.com/jamulussoftware/jamulus/main/linux/setup_repo.sh > setup_repo.sh
chmod +x setup_repo.sh
sudo ./setup_repo.sh

# 3. Confirm the key that actually landed matches the new one (not the old expired one)
gpg --show-keys /etc/apt/trusted.gpg.d/jamulus.asc

# 4. Force a completely fresh update (bypasses any leftover cached release data)
sudo apt-get update

# 5. Install/upgrade
sudo apt install jamulus-headless

[NickVeit]

Many thanks. Below is what I got with "apt-key list". I'm uncertain what to "apt-key del". I'm also providing the output from "gpg --show-keys /etc/apt/trusted.gpg.d/jamulus.asc" for your info. I will now try to wipe and rerun per your second posting.

root@localhost:~# apt-key list
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (s         ee apt-key(8)).
/etc/apt/trusted.gpg.d/jamulus.asc
----------------------------------
pub   rsa4096 2026-07-27 [SC] [expires: 2030-07-26]
      1FC2 EFC5 F888 68F6 FC6A  0639 8E85 16F9 26E4 AD0E
uid           [ unknown] The Jamulus Development Team (GPG key for signing Jamul         us releases generated by the official deb repository) <team@jamulus.io>
sub   rsa4096 2026-07-27 [E] [expires: 2030-07-26]

/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg
------------------------------------------------------
pub   rsa4096 2012-05-11 [SC]
      8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
uid           [ unknown] Ubuntu CD Image Automatic Signing Key (2012) <cdimage@u         buntu.com>

/etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
------------------------------------------------------
pub   rsa4096 2018-09-17 [SC]
      F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
uid           [ unknown] Ubuntu Archive Automatic Signing Key (2018) <ftpmaster@         ubuntu.com>


--------------------------------------------------------------------------------------------------------------------------------

root@localhost:~# gpg --show-keys /etc/apt/trusted.gpg.d/jamulus.asc
pub   rsa4096 2026-07-27 [SC] [expires: 2030-07-26]
      1FC2EFC5F88868F6FC6A06398E8516F926E4AD0E
uid                      The Jamulus Development Team (GPG key for signing Jamulus releases generated by the official deb repository) <team@jamulus.io>
sub   rsa4096 2026-07-27 [E] [expires: 2030-07-26]

[NickVeit]

Thanks so much for apparently resolving this matter with:
install the Deb manually
clear apt caches
ask some LLM by giving it the exact error message.

I can see it upgraded to 3.12.3 , no more key errors and updates work fine....very relieved and appreciative of your clear instructional steps.

[ann0see]

Great. Thanks!

[pcar75]

I have a similar problem. On Ubuntu Studio 22.04 , I run v3.11 (from a std install) and v4.0.0beta2 (executable extracted from .deb in a separate Download sub-directory) . Trying to install 3.12.4 over 3.11 fails due to missing public keys.
If I apply the above recipe , will it compromise running the 4.... installation ?

• I'm not linux-savvy.

[ann0see]

Beta 4.0/2 should not show up on the repo. Just install the deb manually after you've executed the steps above.

[bugith]

For me (v3.12.1 @ Ubuntu22.04) the reason was key expired on 2026/07/26 - I got error NO_PUBKEY 8E8516F926E4AD0E :

me@nux:~$ sudo apt-key list |grep -A5 jamulus
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
/etc/apt/trusted.gpg.d/jamulus.asc
--------------------
pub   rsa4096 2023-07-27 [SC] [expirée : 2026-07-26]
      DC5A A15A 46D0 90CA 884F  8143 B1EF 072B 7BD7 F31F
uid          [ expired ] The Jamulus Development Team (GPG key for signing Jamulus releases generated by the official deb repository) redacted at jamulus.oi

list command above still works although man apt-key explicitly states it as deprecated.
del command below works as man apt-key states it as mostly deprecated.

Fixed with tweaked commands from the official setuprepo.sh:

sudo apt-key del  DC5A A15A 46D0 90CA 884F  8143 B1EF 072B 7BD7 F31F
sudo rm /etc/apt/trusted.gpg.d jamulus.asc~
sudo curl --fail --show-error -sLo /etc/apt/trusted.gpg.d/jamulus.asc https://github.com/jamulussoftware/jamulus/releases/latest/download/key.asc
sudo apt-get update && sudo apt-get upgrade -y

Updated to 3.12.4 OK

[pljones]

Thanks.

[pljones]

https://github.com/orgs/jamulussoftware/discussions/3670 updated with information about apt repo keys.

[pcar75]

Note that @bugith remedial may not work everywhere.
In my UbuntuStudio 22.04 , I was finally able to update jamulus by downloading the 3.12.4 '.deb' file locally and double-clicking it in Dolphin (file explorer).
There are still no jamulus keys installed even after completing the suggested commands.
There is no jamulus.asc~ file in /etc/apt/trusted.gpg.d or elsewhere.
Discover (showing available updates for system and applications) still reports the missing key and eschews possible jamulus update.