Child Item

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.dropbox.com/ubuntu disco 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.

Obviously I'm not running Ubuntu disco (19.04) any more, but jammy (22.04). Manually deleting the line in my /etc/apt/sources.list.d/dropbox.list did stop the error occurring, but trying to add the sources line

deb https://linux.dropbox.com/ubuntu jammy main

gives a similar error:

E: The repository 'https://linux.dropbox.com/ubuntu jammy Release' does not have 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.

Will removing the line completely cause an issue with updating Dropbox for new versions?

Find more posts tagged with

Desktop

Error Messages

Linux

Insightful

AcceptAnswer

Accepted answers

czchen

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.

All comments

Walter

Hey @Graeme T.1, sorry to hear about this.

Can you please clarify if you tried updating the app by downloading and installing the latest version from this page?

If you did and still get an error or you notice an issue with the desktop app not working, please let us know.

Thanks!

Graeme T.1

I installed it using the download from the website, which added the entry to the sources list. It's been continually updated (automatically) without needing this line

Hannah

Hey @Graeme T.1, thanks for the update here and sorry for the delay in our response.

May we reach out to you via email, so we can investigate further?

matte90

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

Hello 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

matte90

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.

vhertz

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 main

Then, 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?

mitszo

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.

hugolia

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.

unicandun

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 is

E: 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.

demosnio

Today, april 28, I have had the same error.
Changing disco for jammy worked for me.

Ubuntu 22.04.2

Tyler B.12

Can confirm that changing to "disco" works on 22.04. I get the same error as the others, as of May 7, 2023.

jammy:

```

E: The repository 'https://linux.dropbox.com/ubuntu jammy Release' no longer has a Release fi
le.
N: Updating from such a repository can't be done securely, and is therefore disabled by defau
lt.

```

focal:

```

E: The repository 'https://linux.dropbox.com/ubuntu focal Release' does not have a Release fi
le.
N: Updating from such a repository can't be done securely, and is therefore disabled by defau
lt.

```

BenDBX

Hi Everybody,

I have spoken with the team who works with linux releases, and they believe they have addressed the root cause of the repository failure. Everything should be working now. If you are still experiencing any issues with the repositories, please let us know and I will pass on that information.

Regards,

Ben

Kuni11

Hi, the problem is still here 21st June 2023

Please find attached below the message I get when I run "$ sudo apt-get update" :

Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Ign:2 http://linux.dropbox.com/apt stable InRelease
Hit:3 http://deb.debian.org/debian bookworm InRelease
Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
Ign:5 http://linux.dropbox.com/debian bookworm InRelease
Err:6 http://linux.dropbox.com/apt stable Release
404 Not Found [IP:*not given on this platform for security reasons*]
Hit:7 http://linux.dropbox.com/debian bookworm Release
Reading package lists... Done
E: The repository 'http://linux.dropbox.com/apt stable Release' does not hav
e 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.

Any solution please?

Здравко

@Kuni11 wrote:
...
E: The repository 'http://linux.dropbox.com/apt stable Release' does not have a Release file.
...

Hi @Kuni11,

Where you get this repository from? 🤔 There is no such and that's why you're receiving such a error. On other side:

@Kuni11 wrote:
...
Hit:7 http://linux.dropbox.com/debian bookworm Release
...

As can be seen, the valid repository works. 😉

Remove all invalid 'repositories'. That should solve your issue.

Kuni11

Hello,
The repository appeared by itself after fresh install of dropbox yesterday. I also installed Debian 12 fresh install on my computer. I think the repository came in the dropbox installation package itself.
Could you post a link how to remove the bad one please? Thanks.

Здравко

@Kuni11 wrote:
...
The repository appeared by itself after fresh install of dropbox yesterday. I also installed Debian 12 fresh install on my computer. I think the repository came in the dropbox installation package itself.
...

Hm...🤔 To be honest I have no idea how this can happen - absolutely new installed OS and Dropbox package from 'zero'?! I just took a look in the install script and there is no something similar. The only things that gets installed, as a repository source there, is the working one. You can take a look in your repositories sources using following command:

grep dropbox /etc/apt/sources.list /etc/apt/sources.list.d/*

Take in mind that the used paths are the default; if you have changed them, correct the command accordingly. All places/files where Dropbox repositories are listed on/in will come up. Usually there should be a single file /etc/apt/sources.list.d/dropbox.list. If other file(s) bring up, find a way to clear Dropbox related lines there. In the file, just mentioned, should be a single line pointing to the working repository. If there is something different, you can override the content using something like following:

sudo bash -c 'echo "deb [arch=i386,amd64] http://linux.dropbox.com/debian bookworm main" > /etc/apt/sources.list.d/dropbox.list'

The above will set the file content as has to be done by package install script. There all path gets retrieved and used to format similar/equivalent command; here I used the default values. Again, If you have changed something in system configuration, change accordingly the command too. You can do a backup copy in advance, if you want, using following:

cp /etc/apt/sources.list.d/dropbox.list ~/

Good luck.

Kuni11

It worked, thanks a lot.
I deleted the link in the 2nd file in the /etc/apt/sources.list.d directory

This solved the problem.
Best regards

czchen

I have the following error when using `apt update` in Debian sid.

W: GPG error: http://linux.dropbox.com/debian sid Release: The following signatures were invalid: BADSIG FC918B335044912E Dropbox Automatic Signing Key <linux@dropbox.com>
E: The repository 'http://linux.dropbox.com/debian sid Release' is not signed.
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.

Hannah

Hey @czchen, sorry for the delay here.

Would you mind confirming that your device meets the minimum requirements for the Dropbox app and is running on a supported environment?

czchen

The machine fulfill the minimal requirements:

Linux version: Debian trixie/sid

Dropbox app version: 2023.09.06

file system: ext4

Jay

Hi @czchen, currently the Linux requirements for the app are Ubuntu or Fedora, not Debian, so the support we can provide is limited for your system.

Have you tried contacting the support team directly in relation to this matter?

Здравко

@czchen wrote:
I have the following error when using `apt update` in Debian sid.
W: GPG error: http://linux.dropbox.com/debian sid Release: The following signatures were invalid: BADSIG FC918B335044912E Dropbox Automatic Signing Key <linux@dropbox.com>
E: The repository 'http://linux.dropbox.com/debian sid Release' is not signed.
...

Hi @czchen,

I just checked and the previous issue (incorrect signing) seems solved (the signature of Debian sid Release.gpg matches Release file). Are you certain you have registered the signing key? 🤔 If you haven't registered correct key, you won't be able check such signature (like trying to unlock a door with unmached key). 🙋

Another way is to just install the package by hand and it will install the key for you. Download the suitable deb package and install it using whatever installer is convenient for you (dpkg, apt, etc.) or just click on the package the environment will direct you to suitable installed graphical wrapper of installer. 😉 About which one is suitable: If your environment is pre-Gtk4 based, then you have to download version 2020.03.04 of the package (i.e. dropbox_2020.03.04_amd64.deb) - latest are incompatible (don't ask me why 🤦 - one of the stupid moves of Dropbox development). For Gtk4 based environments - download the latest package version (by now - moment of this post - 2023.09.06 - i.e. dropbox_2023.09.06_amd64.deb). For other options take a look here: https://linux.dropbox.com/packages/debian/ ...

Hope this helps.

@Jay wrote:
Hi @czchen, currently the Linux requirements for the app are Ubuntu or Fedora, not Debian ...

Not Debian...🤔 And what are looking for Debian directed forks of the package on your site, as shown in previous paragraph, in such a case? 🧐😀🤫

unicandun

I was happy to see that Debian packages were added to the Dropbox app downloads, but I am also getting the GPG error, this is right after I installed the new Debian package (dropbox_2023.09.06_amd64.deb).

The message form apt is

W: GPG error: http://linux.dropbox.com/debian bookworm Release: The following signatures were invalid: BADSIG FC918B335044912E Dropbox Automatic Signing Key <linux@dropbox.com>
E: The repository 'http://linux.dropbox.com/debian bookworm Release' is not signed.
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.

The sources.list entry is in /etc/apt/sources.list.d/dropbox.list and reads

deb [arch=i386,amd64 signed-by=/etc/apt/keyrings/dropbox.asc] http://linux.dropbox.com/debian bookworm main

Any help will be very apreciated

Здравко

Hm...🤔 I just checked the repository sign validity and seems fine:

There was issue some time ago, but it's solved already and as seems it still works. Make sure your certificate looks like:

... and also place it in /etc/apt/trusted.gpg.d/dropbox.asc

After that, check what's going on. If still some issues, try change the content of dropbox.list file to:

deb https://linux.dropbox.com/ubuntu disco main

Debian and Ubuntu repositories are mirrors to each other on Dropbox servers.

Good luck.

czchen

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.

unicandun

Thank you so much!

I can confirm that doing what you did fixes the problem.

Have no idea why!

Thank you so much for your help