And I can't see anybody else's screen when shared...

Thank you for the report.

I am only seeing 'chromium-browser-stable-109.0.5414.119-1.mga8', so am puzzled that you have version 110.0.5481.177. Never mind that.
If you downgrade:
 # urpmi --downgrade chromium-browser-stable-109.0.5414.119-1
does the problem disappear?

CC'ing cjw & squidf, unsure who now maintains this package.

CC: (none) => chb0, cjw, lewyssmith

Just to confirm that after a system update, I am now seeing:
 chromium-browser-stable-110.0.5481.177-1.mga8

christian barranco maintain chromium nowadays

CC: (none) => fri
Assignee: bugsquad => chb0

(In reply to Lewis Smith from comment #2)
> Thank you for the report.
> 
> I am only seeing 'chromium-browser-stable-109.0.5414.119-1.mga8', so am
> puzzled that you have version 110.0.5481.177. Never mind that.
> If you downgrade:
>  # urpmi --downgrade chromium-browser-stable-109.0.5414.119-1
> does the problem disappear?
> 
> CC'ing cjw & squidf, unsure who now maintains this package.

I use teams for homeworking only and I'm afraid I'll be able to test the downgrade only next monday...

Hi. 
Chromium 110 has been a bit "experimental". It looks like Chromium 111 has cleaned up things, in some extend.
Chromium 111 will be released next week.

That being said, Adelson, do you have the codecs installed from the Tainted repo?

Yes, I have tainted repos on. As an additional info, firefox works fine with teams.

I usually install as many codecs as there are a available

Can we leave this on hold until Chromium 111 is available?
Not forgetting the possibility of downgrading it as per comment 2.

(In reply to Lewis Smith from comment #9)
> Can we leave this on hold until Chromium 111 is available?

Hi. I would recommend so. I have successfully built locally the latest beta. It should then be on our BS from next Wednesday.

However, I cannot test at all. Even with Firefox, I cannot connect to Teams to create an invitation.
Maybe it is because I don't have a pro account?

It will be interesting to confirm whether it still works with Chromium 109.

Quite likely caused by disabling openh264 in the chromium-browser package, which was mistakenly enabled ):

Maybe nowadays an implementation of "constricted baseline profile" of h.264/MPEG4 AVC (which openh264 is) can be in the core repository, but I have not been able to find any information on this.

(In reply to christian barranco from comment #10)
> (In reply to Lewis Smith from comment #9)
> > Can we leave this on hold until Chromium 111 is available?
> 
> Hi. I would recommend so. I have successfully built locally the latest beta.
> It should then be on our BS from next Wednesday.
> 
> However, I cannot test at all. Even with Firefox, I cannot connect to Teams
> to create an invitation.
> Maybe it is because I don't have a pro account?
> 
> It will be interesting to confirm whether it still works with Chromium 109.

Tomorrow is monday and I will be able to test and report here the downgraded version 109.

(In reply to Lewis Smith from comment #2)
> Thank you for the report.
> 
> I am only seeing 'chromium-browser-stable-109.0.5414.119-1.mga8', so am
> puzzled that you have version 110.0.5481.177. Never mind that.
> If you downgrade:
>  # urpmi --downgrade chromium-browser-stable-109.0.5414.119-1
> does the problem disappear?
> 
> CC'ing cjw & squidf, unsure who now maintains this package.

It seems that the old version is no longer available. Is there a repo that still has it?

# urpmi --downgrade chromium-browser-stable-109.0.5414.119-1
No  package  chromium-browser-stable-109.0.5414.119-1 found

It should be
# urpmi --downgrade chromium-browser-stable-109.0.5414.119-1.mga8

CC: (none) => davidwhodgins

(In reply to Dave Hodgins from comment #14)
> It should be
> # urpmi --downgrade chromium-browser-stable-109.0.5414.119-1.mga8

OK.

Old version installed and screen sharing works fine with teams.

Thanks

My fault for omitting the .mga8 in comment 2. Thanks Dave for correcting.
Await v111, comment 10.

Hi. If it is related to H264, as it is most probably, I am afraid Chromium 111 will not solve it, unless I restore the H264 support like for Chromium 109.

I just check with Manjaro and Linux Mint. Teams works with both of them.
It looks like they have kept the H264 support we have removed.

Any view on restoring H264 as well for us?

I would say "Yes"; I do not understand why it was removed.
Conversely, from comment 11 "which was mistakenly enabled". Why 'mistakenly'?
I (but clueless) thought this H264 thing was quite widely used.

Hi. It solved for me with Chromium 111. Please, test it when you can (available in core/updates_testing).

Thanks for your work.
I cannot test this because of no connection with M$ Teams.
@Adelson : please try this new version 111.

(In reply to Lewis Smith from comment #20)
> Thanks for your work.
> I cannot test this because of no connection with M$ Teams.
> @Adelson : please try this new version 111.

I've tested

chromium-browser-stable-111.0.5563.64-1.mga8

and it worked fine for screen sharing and audio. 

Thanks for the help.

Thanks for your +ve feedback; and christian for his work.

I have seen a detailed Advisory for this somewhere; should it not be here?
Or is there another bug?

The update and advisory are in bug 31645

Thanks. So we can close this bug.

Status: NEW => RESOLVED
Resolution: (none) => FIXED