Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

screen sharing doesn't work on Centos #64

Closed
chrisgns opened this issue Mar 18, 2019 · 14 comments
Closed

screen sharing doesn't work on Centos #64

chrisgns opened this issue Mar 18, 2019 · 14 comments
Labels
help wanted Extra attention is needed

Comments

@chrisgns
Copy link

Hi,
I am using teams-for-linux-0.1.16-181.x86_64 on Centos 7, but trying to get screen sharing working I get the message that screen sharing is not supported by the browser version.
On the system bot chromium and google-chrome is installed, and having both extensions
https://chrome.google.com/webstore/detail/microsoft-teams-screen-sh/dhheiegalgcabbcobinipgmhepkkeidk and
https://chrome.google.com/webstore/detail/enable-teams-calling/ifgnnjhhfdpjpjokajkolhioakajhidc
the screen sharing works in google-chrome.

Is there anything can do, to get teams-for-linux working?

Christoph

@IsmaelMartinez
Copy link
Owner

Hi, is this on 1to1 or group chat? I have seen that the 1st page that the app loads sometimes don't get the "screensharing" enabled. Can you check if by going to another group chat and then back to the one you where trying to use it works? Might need to increase the "timeout" that waits to enable the feature.

@chrisgns
Copy link
Author

It just doesn't work, not 1to1 not in a meeting. It works in Chrome, anyway to enable some kind of debugging?

@IsmaelMartinez
Copy link
Owner

you can start the app with --webDebug and you will get the chrome devtools

@IsmaelMartinez
Copy link
Owner

Also, if you where using a previous version, you probably need to clean the cache/history.

https://github.com/IsmaelMartinez/teams-for-linux#no-history

Let me know how you get on with that. I had a similar issue while testing the user agent just now and had to clean the "history"

@IsmaelMartinez
Copy link
Owner

Hi @chrisgns , I assume this is sorted, so I will close the issue. Reopen otherwise.

@chrisgns
Copy link
Author

chrisgns commented Mar 21, 2019

Sorry, I was away on a business trip. It doesn't work, I tried a second computer and deleted the history completely, but the camera for starting the video calls is still greyed out and is showing the tooltip that video is not yet supported in my browser.
@IsmaelMartinez , I don't know to reopen, but it is not solved, using 0.1.16.

@IsmaelMartinez IsmaelMartinez added the help wanted Extra attention is needed label Mar 21, 2019
@IsmaelMartinez
Copy link
Owner

Have you tried running from source? or dowloading the tar.gz and running it from there..

Or installing another package type... (snap or AppImage).

@chrisgns
Copy link
Author

chrisgns commented Mar 21, 2019 via email

@julian-alarcon
Copy link
Collaborator

Hi, I tried the master branch today on a VM with Centos 7, I can share the screen with no issues (some warnings but nothing critical), I even made a one to one and works with good quality (maybe the bug #61 is related with screen resolution as the VM has lower resolution)

[user@server1 teams-for-linux]$ yarn start
yarn run v1.15.2
$ yarn install && electron ./app
[1/4] Resolving packages...
success Already up-to-date.
$ electron-builder install-app-deps
  • electron-builder version=20.38.5
  • loaded configuration file=package.json ("build" field)
  • rebuilding native production dependencies platform=linux arch=x64
  • rebuilding native dependency name=spellchecker

[8608:0322/095728.036972:ERROR:adm_helpers.cc(73)] Failed to query stereo recording.
[OpenH264] this = 0x0x174f5d0e6660, Warning:ParamValidation(), AdaptiveQuant(1) is not supported yet for screen content, auto turned off
[OpenH264] this = 0x0x174f5d0e6660, Warning:ParamValidation(), BackgroundDetection(1) is not supported yet for screen content, auto turned off
[OpenH264] this = 0x0x174f5d0e6660, Warning:bEnableFrameSkip = 0,bitrate can't be controlled for RC_QUALITY_MODE,RC_BITRATE_MODE and RC_TIMESTAMP_MODE without enabling skip frame.
[OpenH264] this = 0x0x174f5d0e6660, Warning:Change QP Range from(0,51) to (26,35)
[OpenH264] this = 0x0x174f5d0e6660, Warning:ParamValidation(), AdaptiveQuant(1) is not supported yet for screen content, auto turned off
[OpenH264] this = 0x0x174f5d0e6660, Warning:ParamValidation(), BackgroundDetection(1) is not supported yet for screen content, auto turned off
[OpenH264] this = 0x0x174f5d0e6660, Warning:bEnableFrameSkip = 0,bitrate can't be controlled for RC_QUALITY_MODE,RC_BITRATE_MODE and RC_TIMESTAMP_MODE without enabling skip frame.
[OpenH264] this = 0x0x174f5d0e6660, Warning:Change QP Range from(0,51) to (26,35)
[OpenH264] this = 0x0x174f5d0e6660, Warning:Actual input framerate 6.166700 is different from framerate in setting 15.000000, suggest to use other rate control modes
[8608:0322/095810.838240:ERROR:stunport.cc(87)] Binding request timed out from 192.168.100.x:47996 (eth1)

But the version 0.1.16 doesn't show the screen sharing option and the voice call option pop ups a warning about browser support.

Also, packaged master (currently 0.1.17) branch on .rpm, used it and worked fine.

So, I think that this can be mark as fixed and the next build version will fix your issue @chrisgns

BTW, @chrisgns , if you want to test the source you have to install yarn, Nodejs, gcc-c++, make and libXScrnSaver. Then run yarn install && yarn start on the source code folder.

@IsmaelMartinez
Copy link
Owner

Hi @chrisgns ,

Can you check if the screenshare work if you set chrome as your default browser?

It should not be needed... but is one of those things that might be the reason... hope helps,

Ismael

@chrisgns
Copy link
Author

chrisgns commented Apr 1, 2019

Sorry for the late reply, but it still does not work. I was setting Chrome as default, bus nothing changed.

@jynolen
Copy link

jynolen commented Apr 16, 2019

Hello I got the same issue on fedora, I am using cinnamon desktop and it fails.
But it tried in oopenbox and it works

@IsmaelMartinez
Copy link
Owner

You might need to start then teams with and argument to tell it to use another "desktop".

I don't have the time this week but have a look at other close issues related to the icon don't looking right. It wasn't the solution but one of those "try this".

Sorry I can't be more useful this week.

@IsmaelMartinez
Copy link
Owner

#35 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants