cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Want to know what we learned at IBC? Check out our learnings on media, remote working and more right here.

Apps and Installations

Have a question about a Dropbox app or installation? Reach out to the Dropbox Community and get solutions, help, and advice from members.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Re: Ubuntu linux repository failure

Ubuntu linux repository failure

Graeme T.1
Collaborator | Level 9
Go to solution

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?

29 Replies 29

hugolia
Explorer | Level 3
Go to solution

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?

Здравко
Legendary | Level 20
Go to solution

@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
Explorer | Level 4
Go to solution

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
New member | Level 2
Go to solution

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

 

Ubuntu 22.04.2

Tyler B.12
Explorer | Level 3
Go to solution

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
Community Manager
Go to solution

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
Explorer | Level 4
Go to solution

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?

Здравко
Legendary | Level 20
Go to solution

@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
Explorer | Level 4
Go to solution
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.

Здравко
Legendary | Level 20
Go to solution

@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.

Need more support?