I did "apt update", but received this error message where signatures were invalid.

Report Bugs, Issues and non- package Requests
Post Reply
Message
Author
User avatar
Raccoon_JS
Posts: 8
Joined: Thu Jul 11, 2019 8:30 pm

I did "apt update", but received this error message where signatures were invalid.

#1 Post by Raccoon_JS »

I updated my system on terminal, then I received this error message.
An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://mega.nz/linux/MEGAsync/Debian_9.0 ./ InRelease: The following signatures were invalid: [signature] MegaLimited <support@mega.co.nz>
Any idea?

User avatar
Eadwine Rose
Administrator
Posts: 11962
Joined: Wed Jul 12, 2006 2:10 am

Re: I did "apt update", but received this error message where signatures were invalid.

#2 Post by Eadwine Rose »

Yep. Disable the repo for Mega for a bit, and then enable again tomorrow to see if the issue has sorted itself.


The fix gpg bit won't work, already tried that.
MX-23.2_x64 July 31 2023 * 6.1.0-20-amd64 ext4 Xfce 4.18.1 * 8core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 525.147.05 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 860EVO * Samsung S24D330 & P2250 * HP Envy 5030

User avatar
Raccoon_JS
Posts: 8
Joined: Thu Jul 11, 2019 8:30 pm

Re: I did "apt update", but received this error message where signatures were invalid.

#3 Post by Raccoon_JS »

Eadwine Rose wrote: Tue Jul 30, 2019 3:04 pm Yep. Disable the repo for Mega for a bit, and then enable again tomorrow to see if the issue has sorted itself.
But how do I disable the repo for Mega?

User avatar
Eadwine Rose
Administrator
Posts: 11962
Joined: Wed Jul 12, 2006 2:10 am

Re: I did "apt update", but received this error message where signatures were invalid.

#4 Post by Eadwine Rose »

Open synaptic, settings - repositories - uncheck the mega one and OK out.
MX-23.2_x64 July 31 2023 * 6.1.0-20-amd64 ext4 Xfce 4.18.1 * 8core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 525.147.05 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 860EVO * Samsung S24D330 & P2250 * HP Envy 5030

User avatar
Eadwine Rose
Administrator
Posts: 11962
Joined: Wed Jul 12, 2006 2:10 am

Re: I did "apt update", but received this error message where signatures were invalid.

#5 Post by Eadwine Rose »

Re-enabled mega repo, reloaded and there was an update to it. Still a message popped up.


Not authenticated, but I kinda knew what this was.. so I let it update.

Reload and messages are now gone. They fixed it.
MX-23.2_x64 July 31 2023 * 6.1.0-20-amd64 ext4 Xfce 4.18.1 * 8core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 525.147.05 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 860EVO * Samsung S24D330 & P2250 * HP Envy 5030

greyowl
Posts: 13
Joined: Thu Jun 04, 2015 8:41 pm

Re: I did "apt update", but received this error message where signatures were invalid.

#6 Post by greyowl »

I am having continuing problem. I tried your method of removing Mega repo and then adding it back, but it did not work.
I got the following message:
GPG error: https://mega.nz/linux/MEGAsync/Debian_9.0 ./ InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 03C3AD3A7F068E5DThe repository 'https://mega.nz/linux/MEGAsync/Debian_9.0 ./ InRelease' is not signed.

User avatar
Eadwine Rose
Administrator
Posts: 11962
Joined: Wed Jul 12, 2006 2:10 am

Re: I did "apt update", but received this error message where signatures were invalid.

#7 Post by Eadwine Rose »

Didn't you receive the email from mega?


https://mega.nz/blog_55
MX-23.2_x64 July 31 2023 * 6.1.0-20-amd64 ext4 Xfce 4.18.1 * 8core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 525.147.05 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 860EVO * Samsung S24D330 & P2250 * HP Envy 5030

greyowl
Posts: 13
Joined: Thu Jun 04, 2015 8:41 pm

Solved--Re: I did "apt update", but received this error message where signatures were invalid.

#8 Post by greyowl »

Thank you for the reference of the MEGA blog on this issue: https://mega.nz/blog_55
I followed the instructions and now everything is working again.
Thank you for the help.
Last edited by greyowl on Fri Aug 02, 2019 10:43 pm, edited 1 time in total.

User avatar
JayM
Qualified MX Guide
Posts: 6793
Joined: Tue Jan 08, 2019 4:47 am

Re: I did "apt update", but received this error message where signatures were invalid.

#9 Post by JayM »

If this solves your issue or answers your question please edit your original post (via the pencil icon at the top right) and add [SOLVED] to its subject. This makes it easier for others when they're searching the forum looking for solutions to the same question or problem. Thanks.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

Post Reply

Return to “Bugs and Non-Package Requests Forum”