W: GPG error: https://repo.skype.com stable InRelease

I am running Debian 8 latest updates.

I recently upgraded to this latest Alpha version offering  and am intermittently getting system error messages as follows:-

A security trust relationship is not present

W: GPG error: https://repo.skype.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1F3045A5DF7587C3

The installation process as per Debian website at https://wiki.debian.org/skype#Installing_Skype:-

# dpkg -i skypeforlinux-64.deb

(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M^M(Reading database ... 60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 520298 files and directories currently installed.)

Preparing to unpack skypeforlinux-64.deb ...
Unpacking skypeforlinux (5.3.0.1) over (5.3.0.1) ...
Setting up skypeforlinux (5.3.0.1) ...
Processing triggers for hicolor-icon-theme (0.13-1) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for gnome-menus (3.13.3-6) ...
Processing triggers for mime-support (3.58) ...
root@debacertb:/home/alex/dwhelper#

Skype worked fine after sorting out some sound issues (just finding where to configure / test sound is NOT intuitive, whereas Skype 4.3 was).

Contrary to the advice in point 6 on the Debian 'Installing_Skype' website, no repository changes were made, and even after adding:-

deb https://repo.skype.com/deb stable main

to /etc/apt/sources.list, the error persists.  Commenting the above repository out in sources.list, made no difference.

I even tried the following to try to get rid of these error messages using:-

# wget -q "https://repo.skype.com/deb/stable skypeforlinux" -O - | apt-key add -
gpg: no valid OpenPGP data found.

# wget -q "https://repo.skype.com/deb/dists/stable/Release.gpg" -O - | apt-key add -
gpg: no valid OpenPGP data found.

# wget -q "https://repo.skype.com/deb/dists/stable/InRelease.gpg" -O - | apt-key add -
gpg: no valid OpenPGP data found.

Questions:-

Why was there no modification of my sources.list, despite it being stated on the Debian Skype web page.  Are these instructions correct, and if not please notify Debian.

Why am I intermittently getting these gpg system error messages and how can I get rid of them, permanently?

Thanking you in anticipation

Alex

P.S. Further research revealed the following:-

skype-stable.list had been added to /etc/apt/sources.list.d/ and was thus being read by apper, synaptic etc..

This, of course, is why sources.list had not been modified.

As a temporary WORKAROUND until this issue is fixed:-

# mv /etc/apt/sources.list.d/skype-stable.list .etc_apt_sources.list.d_skype-stable.list

Tested with synaptic -> reload

No more repository errors.

Skype 4.3 WORKED!!!

Why the change?

In the rural environment where I live, we have a very simple philosophy:-
  "If it ain't broke, DON'T fix it!!!!

Particularly when offering an Alpha (testing) version of something with a far less intuitive or useful interface.

I look forward to the resolution of this 'trust relationship' issue.

Alex

 

Question Info


Last updated July 17, 2019 Views 1,918 Applies to:

you can try to manually add the missing repository public key with this command:

$ apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 1F3045A5DF7587C3

Executing: /tmp/apt-key-gpghome.POubQeQoQU/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 1F3045A5DF7587C3
gpg: key 1F3045A5DF7587C3: public key "Skype Linux Client Repository <*** Email address is removed for privacy ***>" imported
gpg: Total number processed: 1
gpg:               imported: 1

from https://atkdinosaurus.wordpress.com/2017/06/15/skype-for-linux-beta-doesnt-add-the-repository-public-key-to-apt-on-ubuntu/


or follow the 'official' guide:

https://repo.skype.com/

$ curl https://repo.skype.com/data/SKYPE-GPG-KEY | sudo apt-key add -

sunny greetings

stefan

4 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thanks for that, Stefan.

I used:-

curl https://repo.skype.com/data/SKYPE-GPG-KEY | sudo apt-key add -

Then added back skype-stable.list  to /etc/apt/sources.list.d/

Tested with synaptic -> reload

No more repository errors.

This worked very well, thank you Stefan.

PS

NB!

Please would Microsoft compile this sort of issue into some sort of USEFUL and meaningful installation instructions / hints / tips / manual which is made available on the skypeforlinux download page, as a pdf and html.

Linux is a reality, Microsoft. Get over it.

Given that your own Steve Ballmer is quoted as saying:-

"he "loved" the SQL for Linux announcement and had emailed Microsoft CEO Satya Nadella to congratulate him on the move" at http://www.zdnet.com/article/ballmer-i-may-have-called-linux-a-cancer-but-now-i-love-it/

it might be an idea to actually offer some REAL support on your Linux based offerings.

Having spent most of my working life in Customer Support for diverse IT corporations, at both national and international level, I wish to offer Microsoft a piece of advice:-

"Real Customer Support is to a corporation, like the sonar is to a torpedo - the steering guidance mechanism."

This issue can now be closed.

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.