Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
Ubuntu linux repository failure
I'm updating Dropbox through apt on Ubuntu 22.04, and run my usual command for updating all my packages. This time, I received the following error message: E: The repository 'http://linux.dropb...
It works now, but I am not sure why. The following are steps:
* The original not-working configuration are URL: https://linux.dropbox.com/debian, suite: sid.
* I change URL to https://linux.dropbox.com/ubuntu, and suite to disco, and run `apt update` to test if the problem is in debian repository only. It works.
* I change URL to https://linux.dropbox.com/debian, and suite to bookworm, and run `apt update` to test if the problem is in sid suite only. It works.
* I rollback all configuration (URL: https://linux.dropbox.com/debian, suite: sid), and run `apt update`. It works.
I guess maybe some broken configuration is fixed when running `apt update` with new configuration.
Hi there,
I'm facing the same issue here. It seems the keyring for Dropbox is expired!? In the past I followed the instruction at this link, but now with the March update it seems to not be working anymore... Let me know whether is an issue form Dropbox side, thanks
Matteo
BenDBX
Community Manager
Community ManagerHello and thanks for reporting these issues,
Graeme T.1 the repository issue was fixed last week. You should be able to update without receiving this error message.
matte90 Our engineering team says that this is a warning message that shouldn't cause a block. They are currently investigating why this is happening. In the meantime, it would help us if you could tell us what OS you are using and the specific error message you're receiving.
Regards,
Ben
Hi BenDBX,
I'm currently on Ubuntu 22.04.2 "Jammy Jellyfish". Unfortunately, I uninstalled DB because it prevented me from running successfully sudo apt update. In fact, what I was getting was a warning related to deprecated keyring.
However, playing around I got to the same issue Graeme T.1 was facing, without any option to solve concretely. Before I relied on an external GPG key as per here.
Hi, everyone.
I have the same issue with @matte90 on the same environment (Ubuntu 22.04.2 LTS).
I have updated my /etc/apt/sources.list.d/dropbox.list like this:
-deb [arch=i386,amd64] http://linux.dropbox.com/ubuntu disco main +deb [arch=i386,amd64] http://linux.dropbox.com/ubuntu jammy mainThen, I've run `apt update` and it says:
W: GPG error: http://linux.dropbox.com/ubuntu jammy Release: The following signatures were invalid: BADSIG FC918B335044912E Dropbox Automatic Signing Key <linux@dropbox.com> E: The repository 'http://linux.dropbox.com/ubuntu jammy Release' is not signed.Any solutions?
I downloaded Release and Release.gpg from https://linux.dropbox.com/ubuntu/dists/jammy/ and verified the signature with the GPG key `1C61A2656FB57B7E4DE0F4C1FC918B335044912E` , but it was invalid.
```
$ gpg --verify jammy/Release.gpg jammy/Release
gpg: Signature made Thu Mar 5 08:22:09 2020 JST
gpg: using RSA key FC918B335044912E
gpg: BAD signature from "Dropbox Automatic Signing Key <linux@dropbox.com>" [unknown]```
BenDBX wrote:...
Graeme T.1 the repository issue was fixed last week. You should be able to update without receiving this error message.
...
Hi BenDBX,
What you mean "fixed"? 🧐 Did you take a look on the Release.gpg file both in "disco" and in "jammy" sections of the repository? 🤔 Did you see that they are the same file actually (or 2 copies of the same file)? 😯 How you expect this key to match 2 different Release files simultaneously? That would be a big security issue! 🤫 Fortunately it's not.
BenDBX wrote:...
matte90 Our engineering team says that this is a warning message that shouldn't cause a block. They are currently investigating why this is happening. In the meantime, it would help us if you could tell us what OS you are using and the specific error message you're receiving.
...
Can you ask your "engineering team" how incorrect signing key depends on OS or anything else out of signing algorithm? 🤷🤦 Ask them why the key file is copied instead of recreated (corresponding to what's signed), as has to be... Do you and some of your neighbors have the same door' keys? In the same context you have to be surprised why you can't unlock your neighbor' door using the key of your door! Would you do it there? Why are you doing it here? It's the same!... In this context - "warning message" - 🧐 what's a warning for you?
All others: Why do you intent use particular name? Using any available release name, that works (signed with proper key), would be fine. 😉 All they point to the same pool; there are no different pools/application releases for different OS' releases, so the name doesn't matter (if we ignore wrong signing 😁).
Good luck.
I am using Ubuntu 20.04 (Focal Fossa) and I am having this same issue since April 10.
W: GPG error: https://linux.dropbox.com/ubuntu focal Release: The following signatures were invalid: BADSIG FC918B335044912E Dropbox Automatic Signing Key <linux@dropbox.com>
Any idea how to solve it?
hugolia wrote:...
W: GPG error: https://linux.dropbox.com/ubuntu focal Release: The following signatures were invalid: BADSIG FC918B335044912E Dropbox Automatic Signing Key <linux@dropbox.com>
Any idea how to solve it?
Hi hugolia,
Yes, replace "focal" to "disco" in Dropbox repository settings. 😉 Should be enough.
Hope this helps.
I am having similar results. I am running Debian GNU/Linux 12 (bookworm) with kernel 6.1.0-7-amd64 and gnome 43.3.
The error message I get isE: The repository 'http://linux.dropbox.com/debian bookworm Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.This has been happening a lot recently, specially on al my new updates.
