Ubuntu – Dell Canonical repository is not signed (GPG error)

aptdellgnupgrepositorysignature

With the update to 19.04 my dell repository is not working as it is marked as not signed. This is the error I get:

Ign:11 http://dell.archive.canonical.com/updates xenial-dell Release.gpg

W: GPG error: http://dell.archive.canonical.com/updates xenial-dell Release: Detached signature file '/var/lib/apt/lists/partial/dell.archive.canonical.com_updates_dists_xenial-dell_Release.gpg' is in unsupported binary format
    E: The repository 'http://dell.archive.canonical.com/updates xenial-dell 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.

I've tried with the xenial-dell and bionic-dell. You can see all the repos here.

There are Release and Release.gpg files in both repositories:

I've searched on Ask Ubuntu and elsewhere but I have not been able to find a working solution.

Best Answer

The error occurs because the Dell repository at the time of this writing has no content for Ubuntu 19.04. When we add a PPA the package manager APT expects to find a folder for our release and if it's not there it fails to authenticate. It won't do any other search.

According to Dell's customer service, support - including the PPA - is given for the preinstalled Ubuntu release, 16.04. This is a LTS release supported until April 2021. The computer is likely to work fine with newer releases because hardware support tends to improve with each new kernel version so drivers and other software provided by Dell's PPA may not be necessary or redundant in newer Ubuntu releases.

Related Solutions

Ubuntu – Wine won’t install, Does not have valid release file

18.04 has been out for less than a week. As such, many developers haven't caught up to the new release yet. To that end, WineHQ has a bug for this already requesting 18.04 packaging in their repository.

There is Wine 3.0 in the Ubuntu repositories, you can use that in the interim by executing sudo apt install wine. Once the upstream WineHQ repositories catch up you can use them.

Once that time is available, you can follow the instructions for installing from their repos. From their instructions page are the instructions to follow at that time:

If you have previously installed a Wine package from another repository, please remove it and any packages that depend on it (e.g., wine-mono, wine-gecko, winetricks) before attempting to install the WineHQ packages, as they may cause dependency conflicts.

If your system is 64 bit, enable 32 bit architecture (if you haven't already):
sudo dpkg --add-architecture i386 
Add the repository:
wget -nc https://dl.winehq.org/wine-builds/Release.key
sudo apt-key add Release.key
sudo apt-add-repository https://dl.winehq.org/wine-builds/ubuntu/
Update packages:
sudo apt-get update
Then install one of the following packages:

Stable Branch:
sudo apt-get install --install-recommends winehq-stable
Development Branch:
sudo apt-get install --install-recommends winehq-devel
Staging Branch:
sudo apt-get install --install-recommends winehq-staging
If apt-get complains about missing dependencies, install them, then repeat the last two steps (update and install).

Staging isn't really used anymore, so use either Stable or Devel.

There will be differences though:

Files are installed to /opt/wine-devel.

Menu items are not created for Wine's builtin programs (winecfg, etc.), and if you are upgrading from a distro package that had added them, they will be removed. You can recreate them yourself using your menu editor.

Binfmt_misc registration is not added. Consult your distro's documentation for update-binfmts if you wish to do this manually.

WineHQ does not at present package wine-gecko or wine-mono. When creating a new wine prefix, you will be asked if you want to download those components. For best compatibility, it is recommended to click Yes here. If the download doesn't work for you, please follow the instructions on the Gecko and Mono wiki pages to install them manually.

Ubuntu – How to fix not signed repos which worked before

Okay, I fixed it with the help of dino99. The Google and Jenkins repositories needed https. To fix the Security repository I replaced http://security.ubuntu.com/ubuntu xenial-security Release with http://de.archive.ubuntu.com/ubuntu xenial-security main restricted universe multiverse. Not sure what the exact issue is, but it worked.

Best Answer

Related Solutions

Ubuntu – Wine won’t install, Does not have valid release file

Ubuntu – How to fix not signed repos which worked before

Related Question