This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 19%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERB%3C/text%3E%3C/svg%3E)
I've been running the Teams desktop app (company account) in my Linux Laptop (openSUSE Leap 15.4) for a year now without much trouble: not only the program work, but also got all the updates through the update applet. Recently I started to get the following error while checking for system updates:
Signature verification for Repository teams failed
I tried deleting and re-importing the repository key, but to no avail. The error is clearly on the repository side, not in my system. Any idea? Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 24%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
Hi @RicardoBerlasso-6763
Does anyone else have the same problem in your organization?
Have you tried to use Teams web client to see if it can be worked?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 32%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EK%3C/text%3E%3C/svg%3E)
Update 2023-02-08: Since several months ago, the web client can make video calls in Firefox.
Same as @KDG : we are just two persons using Linux here, and both have the problem. For the second question (trying with the web client) none of the web browsers I have (Firefox, Chromium, Falkon) are officially supported, but that's not relevant to the problem: the already installed desktop client seems to work (at least for now), but the repository is "broken" so I cannot get automated updates for the software. I had to disable the repository to stop the constant error messages.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 15%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Same problem here.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 54%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAJ%3C/text%3E%3C/svg%3E)
Hi,
I also encountered that problem on OpenSUSE Leap 15.3 with the repository. Here is the complete output from zypper:
zypper refresh --repo teams
Signature verification failed for file 'repomd.xml' from repository 'teams'.
Note: Signing data enables the recipient to verify that no modifications occurred after the data
were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
and in extreme cases even to a system compromise.
Note: File 'repomd.xml' is the repositories master index file. It ensures the integrity of the
whole repo.
Warning: This file was modified after it has been signed. This may have been a malicious change,
so it might not be trustworthy anymore! You should not continue unless you know it's safe.
Signature verification failed for file 'repomd.xml' from repository 'teams'.
And that's the content of teams.repo in /etc/zypp/repos.d:
[teams]
name=teams
enabled=1
autorefresh=1
baseurl=https://packages.microsoft.com/yumrepos/ms-teams
gpgkey=https://packages.microsoft.com/keys/microsoft.asc
type=rpm-md
keeppackages=0
So the issue is clear here: The repomod.xml in Microsofts repository has been modified after it had been signed. This might be due to an error in your processes, or by an attacker.
Best
Andreas
Please check your repository!
I'll disable my teams repo until the issue had been solved.
Hi @RicardoBerlasso-6763
According to your description, it looks like the issue occurred in Teams backend server.
To get more sufficient and quickly response about this issue, we recommend you open a ticket. The engineer will collect your backend log and give you advice about it.
Thanks for your understanding!
I've been trying to use that page and ended up hitting wall after wall. I'm not an admin on the account, just a normal user trying to report a bug. I'll try again later, but honestly I cannot see how to move on.
Good morning Jimmy,
Im afraid that you don't understand the situation here. WE are telling YOU, that YOUR deployment server is broken, that YOUR supply chain is broken or possibly under attack (a file on your servers was changed after being signed, and that server might distribute malware to your customers). All your alarm bells should ring loud and you should report this immediately to the responsible teams.
Instead, you are sending us on a "permit A-38 quest" as if we were Asterix and Obelix.
So yeah, we can file support tickets at our IT departments, who may raise a support ticket at Microsoft when they find the time, and we can go on twiddling thumbs while some evildoers are comfortably taking over your servers and lash down another terrible security incident on your company. But hey, who am I to tell you how to do your job?
So which path will we take?
Best
Andreas
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 13%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECE%3C/text%3E%3C/svg%3E)
Same Problem her on all our company computers.
The error log is as follows:
[teams|https://packages.microsoft.com/yumrepos/ms-teams] No valid metadata at the mentioned URL
[2022-09-26 15:47:40] - Cannot read input. Bad stream or EOF.
[2022-09-26 15:47:40] - Can't provide /repodata/repomd.xml
Signature verification for file 'repomd.xml' from the Repository 'teams' did not work
Even an sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc does not help.
Please Fix.
Greetings Nina
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 50%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPV%3C/text%3E%3C/svg%3E)
I have the same problem on my own computer.
Has anyone a proper Microsoft-Account? The Microsoft-Chat-Support told me to open a ticket, but I could not login with our Teams account.
"Kindly create the ticket using the link below and steps
From https://admin.microsoft.com/
Click on Support > New Service request
He should type the issue then click Enter
Select Contact support
A ticket will be raised"
It seems that the main rpm linked from https://www.microsoft.com/nl-be/microsoft-teams/download-app is still signed correctly. Is it better to use this newer rpm (version teams-1.5.00.10453) rather than version teams-1.5.00.10453 that was installed from Microsoft's repository before it became corrupted?
> wget --output-document=teams.rpm https://go.microsoft.com/fwlink/p/?LinkID=2112907&clcid=0x813
> rpm --checksig teams.rpm
teams.rpm: digests signatures OK
> rpm -qpi teams.rpm
Name : teams
Version : 1.5.00.23861
Release : 1
Architecture: x86_64
Install Date: (not installed)
Group : Applications/Internet
Size : 301694124
License : Microsoft End User License Agreement
Signature : RSA/SHA256, Fri Aug 26 23:29:37 2022, Key ID eb3e94adbe1229cf
Source RPM : teams-1.5.00.23861-1.src.rpm
Build Date : Fri Aug 26 23:21:01 2022
Build Host : e0a009a05220
Relocations : (not relocatable)
Vendor : Microsoft
URL : https://teams.microsoft.com/
...
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 92%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESR%3C/text%3E%3C/svg%3E)
Same issue here. It happened quite a few months back in early 2022 also, and I made a support ticket. After some back and forth explaining to the tech that it was on the MS repo end not an install issue on my end they fixed it the same day. Not sure why this one is still broken. And I can't find the link that I was able to open a ticket with last time.
Same issue here. It happened quite a few months back in early 2022 also, and I made a support ticket. After some back and forth explaining to the tech that it was on the MS repo end not an install issue on my end they fixed it the same day. Not sure why this one is still broken. And I can't find the link that I was able to open a ticket with last time.
Problem was fixed for a few days in november, then it resurfaced and it still bugs me.
I'm on openSuse Tumbleweed. Did anyone find a solution?
It's been two months now, how long do we have to wait for Microsoft to get their acts together and fix it?
Hi all,
I made a distribution upgrade first week of January and during that course reactivated the Teams repo. It eventually works fine again since. The signatures are correct again.
Since nothing else happened in this talk, I may assume one lone ranger took heart and fixed it silently. I bow in humble reverence. Thank you.
Andreas