Bug 31625 - Chromium Browser : Screen share using Teams in teams.microsoft.com is no longer working
Summary: Chromium Browser : Screen share using Teams in teams.microsoft.com is no long...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: christian barranco
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 31645
Blocks:
  Show dependency treegraph
 
Reported: 2023-03-03 18:40 CET by Adelson Oliveira
Modified: 2023-03-12 10:16 CET (History)
5 users (show)

See Also:
Source RPM: chromium-browser-stable-110.0.5481.177-1.mga8
CVE:
Status comment:


Attachments

Description Adelson Oliveira 2023-03-03 18:40:59 CET
After updating to this new rpm,

chromium-browser-stable-110.0.5481.177-1.mga8
 
screen share and camera capture no longer works when using Teams (microsoft).

Teams says "Screen is being shared" and I can see what my camera capture but no one else in a meeting can see anything.

thanks
Adelson Oliveira 2023-03-03 19:18:49 CET

Summary: Screen share using Teams in teams.microsoft.com is no longer working => Chromium Browser : Screen share using Teams in teams.microsoft.com is no longer working

Comment 1 Adelson Oliveira 2023-03-03 19:19:47 CET
And I can't see anybody else's screen when shared...
Comment 2 Lewis Smith 2023-03-03 20:26:16 CET
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

Comment 3 Lewis Smith 2023-03-03 20:46:38 CET
Just to confirm that after a system update, I am now seeing:
 chromium-browser-stable-110.0.5481.177-1.mga8
Comment 4 Morgan Leijström 2023-03-03 23:32:40 CET
christian barranco maintain chromium nowadays

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

Comment 5 Adelson Oliveira 2023-03-04 01:00:42 CET
(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...
Comment 6 christian barranco 2023-03-04 11:37:54 CET
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?
Comment 7 Adelson Oliveira 2023-03-04 13:32:56 CET
Yes, I have tainted repos on. As an additional info, firefox works fine with teams.
Comment 8 Adelson Oliveira 2023-03-04 13:35:15 CET
I usually install as many codecs as there are a available
Comment 9 Lewis Smith 2023-03-05 21:30:15 CET
Can we leave this on hold until Chromium 111 is available?
Not forgetting the possibility of downgrading it as per comment 2.
Comment 10 christian barranco 2023-03-05 22:00:31 CET
(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.
Comment 11 Christiaan Welvaart 2023-03-05 23:34:25 CET
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.
Comment 12 Adelson Oliveira 2023-03-06 00:41:55 CET
(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.
Comment 13 Adelson Oliveira 2023-03-06 02:23:26 CET
(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
Comment 14 Dave Hodgins 2023-03-06 03:03:29 CET
It should be
# urpmi --downgrade chromium-browser-stable-109.0.5414.119-1.mga8

CC: (none) => davidwhodgins

Comment 15 Adelson Oliveira 2023-03-06 17:22:07 CET
(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
Comment 16 Lewis Smith 2023-03-06 19:58:09 CET
My fault for omitting the .mga8 in comment 2. Thanks Dave for correcting.
Await v111, comment 10.
Comment 17 christian barranco 2023-03-06 23:33:43 CET
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?
Comment 18 Lewis Smith 2023-03-07 20:22:15 CET
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.
christian barranco 2023-03-08 19:56:14 CET

Depends on: (none) => 31645

Comment 19 christian barranco 2023-03-08 19:57:21 CET
Hi. It solved for me with Chromium 111. Please, test it when you can (available in core/updates_testing).
Comment 20 Lewis Smith 2023-03-08 20:23:37 CET
Thanks for your work.
I cannot test this because of no connection with M$ Teams.
@Adelson : please try this new version 111.
Comment 21 Adelson Oliveira 2023-03-09 22:02:47 CET
(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.
Comment 22 Lewis Smith 2023-03-10 21:37:34 CET
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?
Comment 23 Dave Hodgins 2023-03-10 21:49:19 CET
The update and advisory are in bug 31645
Comment 24 Lewis Smith 2023-03-12 10:16:26 CET
Thanks. So we can close this bug.

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


Note You need to log in before you can comment on or make changes to this bug.