search

IsmaelMartinez / teams-for-linux

Unofficial Microsoft Teams for Linux client
GNU General Public License v3.0
2.94k stars 239 forks source link

Ubuntu 22.04 wayland unable to share screen #629

Closed yudjinn closed 1 year ago

yudjinn commented 2 years ago

Describe the bug Unable to share screen from the deb package. It does create the "screen is being shared" notification in the gnome task bar, but no image is shown to viewer. No black screen, nothing. My syslog shows Oct 13 10:57:51 101451 xdg-desktop-por[564390]: Unhandled parent window type Oct 13 10:57:51 101451 xdg-desktop-por[564390]: Failed to associate portal window with parent window Oct 13 10:58:03 101451 xdg-desktop-por[564390]: Unhandled parent window type Oct 13 10:58:03 101451 xdg-desktop-por[564390]: Failed to associate portal window with parent window

To Reproduce Steps to reproduce the behavior:

  1. Install newest deb package using sudo dpkg -i
  2. Login
  3. Start meeting and click share screen
  4. UI pops up to choose window
  5. No matter what is selected, nothing is streamed to viewer.

Expected behavior screen is shared

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Additional context should note that using the debug level flag shows: [2210227:1013/110507.008457:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed [2210227:1013/110507.008532:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed [2210227:1013/110507.008556:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed [2210227:1013/110507.008577:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed [2210227:1013/110507.008603:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [DEBUG] did-finish-load [DEBUG] did-finish-load on startup but no errors when attempting to screenshare

This was a machine on 20.04 that I upgraded (not clean install) to 22.04, and had a few issues but I validated I am missing no packages from a clean install

jijojosephk commented 2 years ago

Looks like something gone wrong on the upgrade path. Can you start with flag --clearStorage?

yudjinn commented 2 years ago

no change, unfortunately

jijojosephk commented 2 years ago

If you have tray icon, can you click on debug and see what's happening when you click on screenshare? There will be many warning, logs and errors. Make sure you clear everything just before clicking on screenshare. If it's has something to do with the script you won't see logs in the terminal.

pallebone commented 2 years ago

@yudjinn I actually installed the deb version yesterday for the first time and it worked for me... Im thinking something must have changed on your system because it should be working.

yudjinn commented 2 years ago

@pallebone i agree, I had the same problem on 1.0.41 and I have colleagues that have no issue. I'm assuming something broke with my upgrade from 20.04 and want to understand and resolve it.

yudjinn commented 2 years ago

@jijojosephk here are the errors that pop up when I click "share screen": 0.2-angular-jquery.min-14969ec.js:114 2022-10-14T16:10:47.585Z InvisionWhiteboardProvider: getGroupChatAppDefinition - No registeredApp found with appId (67cf2c5a-db0e-4256-a423-14010cbeafdd) for chat (19:meeting_NWFmYjZmZDYtNDFlYy00ZGZiLWJmODItNTZiNWM3MWYxMzgx@thread.v2), callerContext: (meetings) (anonymous) @ 0.2-angular-jquery.min-14969ec.js:114 e.logMessage @ 3.2-app.min-84ed0b3.js:1 e.error @ 3.2-app.min-84ed0b3.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 f @ 0.2-angular-jquery.min-14969ec.js:127 (anonymous) @ 0.2-angular-jquery.min-14969ec.js:128 $eval @ 0.2-angular-jquery.min-14969ec.js:142 $digest @ 0.2-angular-jquery.min-14969ec.js:140 v.$digest @ 3.2-app.min-84ed0b3.js:1 (anonymous) @ 0.2-angular-jquery.min-14969ec.js:143 e @ 0.2-angular-jquery.min-14969ec.js:42 (anonymous) @ 0.2-angular-jquery.min-14969ec.js:45 setTimeout (async) k.defer @ 0.2-angular-jquery.min-14969ec.js:45 $evalAsync @ 0.2-angular-jquery.min-14969ec.js:143 (anonymous) @ 0.2-angular-jquery.min-14969ec.js:127 g @ 0.2-angular-jquery.min-14969ec.js:128 $$resolve @ 0.2-angular-jquery.min-14969ec.js:130 resolve @ 0.2-angular-jquery.min-14969ec.js:129 (anonymous) @ 0.2-angular-jquery.min-14969ec.js:127 (anonymous) @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 a @ 3.1-app.min-cca9e51.js:1 o._resolveCallback @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 o._resolveSuccesses @ 3.1-app.min-cca9e51.js:1 o.resolve @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 a @ 3.1-app.min-cca9e51.js:1 o._resolveCallback @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 o._resolveSuccesses @ 3.1-app.min-cca9e51.js:1 o.resolve @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 a @ 3.1-app.min-cca9e51.js:1 o._resolveCallback @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 o._resolveSuccesses @ 3.1-app.min-cca9e51.js:1 o.resolve @ 3.1-app.min-cca9e51.js:1 t.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) i.get @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.2-app.min-84ed0b3.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 a @ 3.1-app.min-cca9e51.js:1 o._resolveCallback @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 o._resolveSuccesses @ 3.1-app.min-cca9e51.js:1 o._addCallbackSet @ 3.1-app.min-cca9e51.js:1 o.then @ 3.1-app.min-cca9e51.js:1 t.getCustomAppDefinitions @ 3.2-app.min-84ed0b3.js:1 (anonymous) @ 3.2-app.min-84ed0b3.js:1 f @ 0.2-angular-jquery.min-14969ec.js:127 (anonymous) @ 0.2-angular-jquery.min-14969ec.js:128 $eval @ 0.2-angular-jquery.min-14969ec.js:142 $digest @ 0.2-angular-jquery.min-14969ec.js:140 v.$digest @ 3.2-app.min-84ed0b3.js:1 (anonymous) @ 0.2-angular-jquery.min-14969ec.js:143 e @ 0.2-angular-jquery.min-14969ec.js:42 (anonymous) @ 0.2-angular-jquery.min-14969ec.js:45 setTimeout (async) k.defer @ 0.2-angular-jquery.min-14969ec.js:45 $evalAsync @ 0.2-angular-jquery.min-14969ec.js:143 (anonymous) @ 0.2-angular-jquery.min-14969ec.js:127 g @ 0.2-angular-jquery.min-14969ec.js:128 $$resolve @ 0.2-angular-jquery.min-14969ec.js:130 resolve @ 0.2-angular-jquery.min-14969ec.js:129 (anonymous) @ 0.2-angular-jquery.min-14969ec.js:127 (anonymous) @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 a @ 3.1-app.min-cca9e51.js:1 o._resolveCallback @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 o._resolveSuccesses @ 3.1-app.min-cca9e51.js:1 o.resolve @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 a @ 3.1-app.min-cca9e51.js:1 o._resolveCallback @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 o._resolveSuccesses @ 3.1-app.min-cca9e51.js:1 o.resolve @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 a @ 3.1-app.min-cca9e51.js:1 o._resolveCallback @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 o._resolveSuccesses @ 3.1-app.min-cca9e51.js:1 o.resolve @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 a @ 3.1-app.min-cca9e51.js:1 o._resolveCallback @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 o._resolveSuccesses @ 3.1-app.min-cca9e51.js:1 o.resolve @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 a @ 3.1-app.min-cca9e51.js:1 o._resolveCallback @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 o._resolveSuccesses @ 3.1-app.min-cca9e51.js:1 o.resolve @ 3.1-app.min-cca9e51.js:1 s @ 3.1-app.min-cca9e51.js:1 o.<computed> @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 a @ 3.1-app.min-cca9e51.js:1 o._resolveCallback @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 o._resolveSuccesses @ 3.1-app.min-cca9e51.js:1 o.resolve @ 3.1-app.min-cca9e51.js:1 d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 IndexedDB (async) d.onsuccess @ 3.1-app.min-cca9e51.js:1 0.2-angular-jquery.min-14969ec.js:114 2022-10-14T16:10:54.992Z [screenSharing][control] screenSharingControlService: unexpected, cannot find the call, teamsCallId [1] (anonymous) @ 0.2-angular-jquery.min-14969ec.js:114 e.logMessage @ 3.2-app.min-84ed0b3.js:1 e.error @ 3.2-app.min-84ed0b3.js:1 Na.getSharingCall @ 3.1-app.min-cca9e51.js:1 Na.setSharingSource @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 3.1-app.min-cca9e51.js:1 Aq @ 3.1-app.min-cca9e51.js:1 Tl.startScreenSharingOnCall @ 3.1-app.min-cca9e51.js:1 r.startSharing @ 3.1-app.min-cca9e51.js:1 a.startSharing @ 3.1-app.min-cca9e51.js:1 (anonymous) @ 0.2-angular-jquery.min-14969ec.js:248 b @ 0.2-angular-jquery.min-14969ec.js:123 e @ 0.2-angular-jquery.min-14969ec.js:271 $eval @ 0.2-angular-jquery.min-14969ec.js:142 $apply @ 0.2-angular-jquery.min-14969ec.js:143 (anonymous) @ 0.2-angular-jquery.min-14969ec.js:271 dispatch @ 0.2-angular-jquery.min-14969ec.js:1 v.handle @ 0.2-angular-jquery.min-14969ec.js:1 0.2-angular-jquery.min-14969ec.js:114 TypeError: Cannot read properties of undefined (reading 'send') at a.startSharing (https://statics.teams.cdn.office.net/hashed/3.1-app.min-cca9e51.js:1:7469490) at https://statics.teams.cdn.office.net/hashed/0.2-angular-jquery.min-14969ec.js:248:181 at b (https://statics.teams.cdn.office.net/hashed/0.2-angular-jquery.min-14969ec.js:123:28) at e (https://statics.teams.cdn.office.net/hashed/0.2-angular-jquery.min-14969ec.js:271:394) at m.$eval (https://statics.teams.cdn.office.net/hashed/0.2-angular-jquery.min-14969ec.js:142:512) at m.$apply (https://statics.teams.cdn.office.net/hashed/0.2-angular-jquery.min-14969ec.js:143:228) at HTMLDivElement.<anonymous> (https://statics.teams.cdn.office.net/hashed/0.2-angular-jquery.min-14969ec.js:271:446) at HTMLDivElement.dispatch (https://statics.teams.cdn.office.net/hashed/0.2-angular-jquery.min-14969ec.js:1:43090) at v.handle (https://statics.teams.cdn.office.net/hashed/0.2-angular-jquery.min-14969ec.js:1:41074) undefined

jijojosephk commented 2 years ago

Do you have a dedicated graphics card?

DGrothe-PhD commented 2 years ago

@pallebone i agree, I had the same problem on 1.0.41 and I have colleagues that have no issue. I'm assuming something broke with my upgrade from 20.04 and want to understand and resolve it.

Yes, with 20.04 screen sharing worked fine. It affects 21.04 as well and (web) screen sharing itself, not just for teams, but iirc for other browser-based screen-sharing applications as well, see https://askubuntu.com/questions/1313369/screen-sharing-with-wayland . You may try those workarounds. I also could not share screen from Microsoft's own teams app on ubuntu 22.04, whereas with 20.04 it worked fine.

jijojosephk commented 2 years ago

@yudjinn can you try export LIBVA_DRIVER_NAME=iHD and run teams-for-linux from there?

yudjinn commented 2 years ago

@yudjinn can you try export LIBVA_DRIVER_NAME=iHD and run teams-for-linux from there?

I have tried that (as well as i986), no change in behavior.

There is a dedicated graphics card, yes. The strange thing is my colleague has the exact same laptop and is having no issues on a fresh install

jijojosephk commented 2 years ago

@yudjinn yeah, then the upgrade didn't work just right. Do yours and your friend's OS kernel versions differ? I'm not sure if that matters. Also you can try other screen sharing or screen recording apps like Kazam or something similar and see if your'e facing any issues there. Looks like it's not easily identifiable by the community, you might wanna try really hard to identify the cause.

yudjinn commented 2 years ago

Using the browser i am able to share, but only the browser window so nothing outside of that. If I switch to xorg i can share just fine using the desktop client. It's only on Wayland that this is breaking. Also, we are on the same kernel yes.

jijojosephk commented 2 years ago

Can journalctl help you in anyway?

jijojosephk commented 2 years ago

journalctl -b | grep teams-for-linux anything there?

yudjinn commented 2 years ago

sorry, was away for the weekend, heres journal: Oct 14 12:40:35 101451 ubuntu-appindicators@ubuntu.com[3096]: unable to update icon for teams-for-linux1 Oct 14 12:40:36 101451 teams-for-linux.desktop[28315]: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) Oct 14 12:40:38 101451 teams-for-linux.desktop[28315]: [28315:1014/124038.051088:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! Oct 14 12:40:40 101451 teams-for-linux.desktop[28315]: [28315:1014/124040.134246:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! Oct 14 12:41:06 101451 teams-for-linux.desktop[28315]: [28315:1014/124106.041138:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! Oct 14 12:41:11 101451 teams-for-linux.desktop[28765]: [28765:1014/124111.950193:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed Oct 14 12:41:11 101451 teams-for-linux.desktop[28765]: [28765:1014/124111.950328:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed Oct 14 12:41:11 101451 teams-for-linux.desktop[28765]: [28765:1014/124111.950373:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed Oct 14 12:41:11 101451 teams-for-linux.desktop[28765]: [28765:1014/124111.950410:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed Oct 14 12:41:11 101451 teams-for-linux.desktop[28765]: [28765:1014/124111.950450:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed Oct 14 12:41:11 101451 ubuntu-appindicators@ubuntu.com[3096]: unable to update icon for teams-for-linux1 Oct 14 12:41:12 101451 teams-for-linux.desktop[28825]: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) Oct 14 12:41:16 101451 teams-for-linux.desktop[28825]: [28825:1014/124116.471319:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! Oct 14 12:41:23 101451 teams-for-linux.desktop[28825]: [28825:1014/124123.273056:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! Oct 14 12:41:24 101451 teams-for-linux.desktop[28825]: [28825:1014/124124.561995:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! Oct 14 12:45:05 101451 ubuntu-appindicators@ubuntu.com[3096]: unable to update icon for teams-for-linux1 Oct 14 12:45:14 101451 teams-for-linux.desktop[34258]: [34258:1014/124514.334997:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed Oct 14 12:45:14 101451 teams-for-linux.desktop[34258]: [34258:1014/124514.335281:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed Oct 14 12:45:14 101451 teams-for-linux.desktop[34258]: [34258:1014/124514.335357:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed Oct 14 12:45:14 101451 teams-for-linux.desktop[34258]: [34258:1014/124514.335423:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed Oct 14 12:45:14 101451 teams-for-linux.desktop[34258]: [34258:1014/124514.335499:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed Oct 14 12:45:14 101451 ubuntu-appindicators@ubuntu.com[3096]: unable to update icon for teams-for-linux1 Oct 14 12:45:14 101451 teams-for-linux.desktop[34319]: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) Oct 14 12:45:38 101451 teams-for-linux.desktop[34319]: [34319:1014/124538.980804:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! Oct 14 12:45:38 101451 teams-for-linux.desktop[34319]: [34319:1014/124538.989745:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! Oct 14 12:45:38 101451 teams-for-linux.desktop[34319]: [34319:1014/124538.990040:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!

jgmGit commented 2 years ago

I have the same issue as well.

teams-for-linux.desktop[118095]: [118095:1026/141419.755308:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
teams-for-linux.desktop[118095]: [118095:1026/141419.755477:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
teams-for-linux.desktop[118095]: [118095:1026/141419.755537:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
teams-for-linux.desktop[118095]: [118095:1026/141419.755600:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
teams-for-linux.desktop[118095]: [118095:1026/141419.755653:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
teams-for-linux.desktop[118248]: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
teams-for-linux.desktop[118248]: [118248:1026/141628.396681:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
teams-for-linux.desktop[118248]: [118248:1026/141644.367744:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
teams-for-linux.desktop[118248]: [118248:1026/141644.380446:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
teams-for-linux.desktop[118250]: [118250:1026/141752.604485:ERROR:socket_tcp.cc(328)] Error when reading from TCP socket: -101
teams-for-linux.desktop[124852]: [124852:1026/142459.374430:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
teams-for-linux.desktop[124852]: [124852:1026/142459.374558:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
teams-for-linux.desktop[124852]: [124852:1026/142459.374598:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
teams-for-linux.desktop[124852]: [124852:1026/142459.374634:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
teams-for-linux.desktop[124852]: [124852:1026/142459.374668:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
teams-for-linux.desktop[124919]: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
teams-for-linux.desktop[124919]: [124919:1026/142501.924839:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
teams-for-linux.desktop[124919]: [124919:1026/142514.221742:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
teams-for-linux.desktop[124919]: [124919:1026/142514.232358:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!

Operating System: Manjaro Linux
Kernel: Linux 5.15.74-3-MANJARO Architecture: x86-64 Hardware Vendor: Lenovo Hardware Model: ThinkPad E480

joaquinodz commented 2 years ago

I managed to make it work in Google Chrome by going to chrome://flags/#enable-webrtc-pipewire-capturer and setting it to Enabled.

jgmGit commented 2 years ago

I managed to make it work in Google Chrome by going to chrome://flags/#enable-webrtc-pipewire-capturer and setting it to Enabled.

@joaquinodz I tried the same. It didn't help

pallebone commented 2 years ago

I managed to make it work in Google Chrome by going to chrome://flags/#enable-webrtc-pipewire-capturer and setting it to Enabled.

Did that fix the snap package or just chrome?

joaquinodz commented 2 years ago

I managed to make it work in Google Chrome by going to chrome://flags/#enable-webrtc-pipewire-capturer and setting it to Enabled.

Did that fix the snap package or just chrome?

Just Chrome. I'm using Fedora 36

pallebone commented 2 years ago

Im glad you got teams working in chrome via ms website, that is great news, but Im confused as to how this is related to the teams-for-linux package. Perhaps clarify what clue this gives us in fixing the deb or snap package?

joaquinodz commented 2 years ago

Im glad you got teams working in chrome via ms website, that is great news, but Im confused as to how this is related to the teams-for-linux package. Perhaps clarify what clue this gives us in fixing the deb or snap package?

I thought there was something like the chrome:flags in electron that could be enabled by default to fix this i don't know much about Electron so i apologize in advance if this isn't relevant ^^'

pallebone commented 2 years ago

Im glad you got teams working in chrome via ms website, that is great news, but Im confused as to how this is related to the teams-for-linux package. Perhaps clarify what clue this gives us in fixing the deb or snap package?

I thought there was something like the chrome:flags in electron that could be enabled by default to fix this i don't know much about Electron so i apologize in advance if this isn't relevant ^^'

Interesting. I dont know either.

IsmaelMartinez commented 2 years ago

did you try with another package? like deb or rpm? snap installations can be a bit iffy. Thanks

yudjinn commented 2 years ago

I ended up just fresh installing and it works fine. Was unable to figure out what was causing my issues. I used the base install, not snap

IsmaelMartinez commented 2 years ago

@yudjinn , thanks for the update. @jgmGit / @pallebone do you still have the issue? Thanks

jgmGit commented 2 years ago

I switched over to Ubuntu 22.10 with Wayland and there it works properly. I can share the screen etc.

I think the problem, when I installed Manjaro was maybe because of the missing pipe-wire installation. I am not 100 percent sure of this. But I suspect this.

yudjinn commented 2 years ago

I definitely had pipe wire, so I don't know if that was the same issue

enricojonas commented 1 year ago

Same issue here, screen sharing when installing with snap is not working. Screen sharing dialog pops up but when you select something it just doesn't share it. I have now re-installed 1.0.46 .deb package and screen sharing works on Ubuntu 22.10 under Wayland. Got also the new Teams UI, some good improvements have been done.

IsmaelMartinez commented 1 year ago

It must be something todo with the permissions or pipewire. strange but glad its working with the deb package.

enricojonas commented 1 year ago

Yes in a way it's working. However I just tried and it seems that I cannot stop sharing my screen... It was still showing the screen sharing icon on the top right (Ubuntu bar, system icon), so I guess it was still sharing in some way.

DerXteMensch commented 1 year ago

I can confirm that while using the deb package, it works. When using the snap version, it doesn't. Working with Ubuntu 22.04.

zeitounator commented 1 year ago

The .deb package does not work for me. When I click on screen sharing, nothing is shown. But if I do this while a screen sharing is ongoing from an other participant, the screen sharing stops as if I started to take it over but never succeeded.

Currently, I'm exploring the error reported by libva to see if this would fix the problem and there is something I quite don't understand. Here is where I am.

  1. I was seeing in my teams-for-linux output the following error: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
  2. I ran vainfo for my user which was giving the folllowing output 
    $ vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_10
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.14 (libva 2.12.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Desktop - 2.4.1
vainfo: Supported profile and entrypoints
  VAProfileMPEG2Simple            : VAEntrypointVLD
  VAProfileMPEG2Simple            : VAEntrypointEncSlice
  VAProfileMPEG2Main              : VAEntrypointVLD
  VAProfileMPEG2Main              : VAEntrypointEncSlice
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264Main               : VAEntrypointVLD
  VAProfileH264Main               : VAEntrypointEncSlice
  VAProfileH264High               : VAEntrypointVLD
  VAProfileH264High               : VAEntrypointEncSlice
  VAProfileH264MultiviewHigh      : VAEntrypointVLD
  VAProfileH264MultiviewHigh      : VAEntrypointEncSlice
  VAProfileH264StereoHigh         : VAEntrypointVLD
  VAProfileH264StereoHigh         : VAEntrypointEncSlice
  VAProfileVC1Simple              : VAEntrypointVLD
  VAProfileVC1Main                : VAEntrypointVLD
  VAProfileVC1Advanced            : VAEntrypointVLD
  VAProfileNone                   : VAEntrypointVideoProc
  VAProfileJPEGBaseline           : VAEntrypointVLD
  3. Following some instructions I could find on AskUbuntu, I removed the unnecessary livba drivers provided by intel-media-va-driver, intel-media-va-driver-non-free (i.e. apt remove --purge).
  4. Following @jijojosephk advice, I've set LIBVA_DRIVER_NAME=i965 in my environment. Here's the new vainfo output after the above steps: 
    $ vainfo 
libva info: VA-API version 1.14.0
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_10
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.14 (libva 2.12.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Desktop - 2.4.1
vainfo: Supported profile and entrypoints
  VAProfileMPEG2Simple            : VAEntrypointVLD
  VAProfileMPEG2Simple            : VAEntrypointEncSlice
  VAProfileMPEG2Main              : VAEntrypointVLD
  VAProfileMPEG2Main              : VAEntrypointEncSlice
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264Main               : VAEntrypointVLD
  VAProfileH264Main               : VAEntrypointEncSlice
  VAProfileH264High               : VAEntrypointVLD
  VAProfileH264High               : VAEntrypointEncSlice
  VAProfileH264MultiviewHigh      : VAEntrypointVLD
  VAProfileH264MultiviewHigh      : VAEntrypointEncSlice
  VAProfileH264StereoHigh         : VAEntrypointVLD
  VAProfileH264StereoHigh         : VAEntrypointEncSlice
  VAProfileVC1Simple              : VAEntrypointVLD
  VAProfileVC1Main                : VAEntrypointVLD
  VAProfileVC1Advanced            : VAEntrypointVLD
  VAProfileNone                   : VAEntrypointVideoProc
  VAProfileJPEGBaseline           : VAEntrypointVLD
  5. But now I get a new error when launching a fresh teams for linux which seems to fail intializing the driver despite vainfo reporting everything looks fine 
    
$ teams-for-linux --trace-warnings --clearStorage
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
[3577107:0114/103350.106586:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[3577107:0114/103350.106825:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[3577107:0114/103350.106929:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[3577107:0114/103350.107002:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[3577107:0114/103350.107073:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[3577223:0114/103355.030827:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[3577223:0114/103404.757674:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
Maher4Ever commented 1 year ago

I can also confirm that on Ubuntu 22.10 screen sharing doesn't work when installing through snap. Switching to the deb package from the release page resolved the issue. Both packages are at version 1.0.49.

zeitounator commented 1 year ago

I have strictly no idea what has changed on my system since I posted my above comment but I tried screen sharing yesterday and it now works with the deb package.

jijojosephk commented 1 year ago

@yudjinn can you confirm if this is working now? There are issues related to snap. #765 Closing this for now. Re-open if you think deb also having the issue. I have not seen people reporting issues with deb or other native packages.

celvin commented 1 year ago

still can't share desktop without disabling Wayland :(

jijojosephk commented 1 year ago

@celvin if the problem you're facing on snap ? the we suggest you to switch to another package.