Bug 404878 - Plasma browser extension causes black screen for gotomeeting screen sharing
Summary: Plasma browser extension causes black screen for gotomeeting screen sharing
Status: RESOLVED FIXED
Alias: None
Product: plasma-browser-integration
Classification: Plasma
Component: Chrome (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-27 19:47 UTC by Cameron Seader
Modified: 2019-04-24 15:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cameron Seader 2019-02-27 19:47:01 UTC
I used Gotomeeting heavily and when I run a meeting from Chrome browser and want to share my screen I am unable to do so if this extension is enabled. If I disable the extension and then open the meeting in the browser then I am working again.


STEPS TO REPRODUCE
1. Install Plasma Extension
2. Run a gotomeeting and share your screen, Everyone sees a black screen share image.
3. disable Plasma Extension, Everything working again with gotomeeting

OBSERVED RESULT
Black screen when screen sharing in gotomeeting

EXPECTED RESULT
Screen sharing of my entire screen

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: openSUSE Tumbleweed latest 20190225
(available in About System)
KDE Plasma Version: 5.15.0
KDE Frameworks Version: 5.55.0
Qt Version: 5.12.0

ADDITIONAL INFORMATION
Comment 1 Kai Uwe Broulik 2019-02-28 07:53:51 UTC
Do you see any suspicious output on Developer Console (Ctrl+Shift+I)?
Do you have "Enhanced Media Controls" enabled in extension settings?
Comment 2 Cameron Seader 2019-02-28 15:25:41 UTC
(In reply to Kai Uwe Broulik from comment #1)
> Do you see any suspicious output on Developer Console (Ctrl+Shift+I)?

Here is the console message i get

--snip--

sessionEntry.js:1 2019-02-28T15:14:59.926Z [log] rtc-client 
{message: "[DualStack] publish in Mcs mode."}
message: "[DualStack] publish in Mcs mode."
__proto__: Object
 
{rtcClientAttributes: {…}}
sessionEntry.js:1 2019-02-28T15:14:59.931Z [log] rtc-client 
{message: "presenter_api_meta_data", data: {…}}
data:
hardwareConcurrency: 8
presenterAPIOptions:
browserInfo: {browserType: 2, version: 72}
byteByByteCompare: false
cacheDepth: 15
disableThrottling: false
frameStatsPercent: 5
numWorkers: 8
resizeTimeout: 100
statsCallback: ƒ (t)
statsPrecision: 2
statsPushInterval: 60000
tileHeight: 128
tileWidth: 176
unicolorEnabled: true
useCache: true
__proto__: Object
__proto__: Object
message: "presenter_api_meta_data"
__proto__:
constructor: ƒ Object()
hasOwnProperty: ƒ hasOwnProperty()
isPrototypeOf: ƒ isPrototypeOf()
propertyIsEnumerable: ƒ propertyIsEnumerable()
toLocaleString: ƒ toLocaleString()
toString: ƒ toString()
valueOf: ƒ valueOf()
__defineGetter__: ƒ __defineGetter__()
__defineSetter__: ƒ __defineSetter__()
__lookupGetter__: ƒ __lookupGetter__()
__lookupSetter__: ƒ __lookupSetter__()
get __proto__: ƒ __proto__()
set __proto__: ƒ __proto__()
 
{rtcClientAttributes: {…}}
rtcClientAttributes:
ga_id_participant_mcs: "1400001"
__proto__: Object
__proto__: Object
sessionEntry.js:1 2019-02-28T15:14:59.937Z [log] started presenting

--snip--

There are no errors in the console when the sharing is started, but the screen is black with the plasma extension enabled.

> Do you have "Enhanced Media Controls" enabled in extension settings?
If this is what you mean
chrome://flags/#enable-modern-media-controls

Mine is all defaults
Comment 3 Kai Uwe Broulik 2019-03-01 10:58:55 UTC
I meant in the extension settings, if's off by default, so I assume you don't have that enabled. Thanks, I probably need to check out that site myself.

I recall having used gotomeeting earlier this year but since I had to use Firefox where I didn't have the extension installed, I didn't notice that there might have been anything wrong with it.
Comment 4 Kai Uwe Broulik 2019-04-22 13:51:46 UTC
I just tried gotomeeting trial and while there is some general wonkiness of screen share not workig when joining a meeting with screenshare already running I cannot attribute it to this extension, I tried both the 1.4 on the store as well as my local git master checkout, as well as without the extension.
Screen sharing the entire screen works just fine in all three cases.
Comment 5 Cameron Seader 2019-04-24 14:11:15 UTC
(In reply to Kai Uwe Broulik from comment #4)
> I just tried gotomeeting trial and while there is some general wonkiness of
> screen share not workig when joining a meeting with screenshare already
> running I cannot attribute it to this extension, I tried both the 1.4 on the
> store as well as my local git master checkout, as well as without the
> extension.
> Screen sharing the entire screen works just fine in all three cases.

Not sure what to tell ya. My experience is just the opposite. I suppose it could be another extension that it has a problem with. The Hunt continues.
Comment 6 Kai Uwe Broulik 2019-04-24 14:52:13 UTC
I just uploaded an update for p-b-i to Chrome store (version 1.5), can you try with that? I did some fixes to make media controls less breaking for websites.
Comment 7 Cameron Seader 2019-04-24 14:53:28 UTC
(In reply to Kai Uwe Broulik from comment #6)
> I just uploaded an update for p-b-i to Chrome store (version 1.5), can you
> try with that? I did some fixes to make media controls less breaking for
> websites.

Yes. Will try right now.
Comment 8 Cameron Seader 2019-04-24 15:01:08 UTC
(In reply to Cameron Seader from comment #7)
> (In reply to Kai Uwe Broulik from comment #6)
> > I just uploaded an update for p-b-i to Chrome store (version 1.5), can you
> > try with that? I did some fixes to make media controls less breaking for
> > websites.
> 
> Yes. Will try right now.

This update seems to fix it. I can now do screen sharing without issue when this extension is enabled. Thank You!
Comment 9 Kai Uwe Broulik 2019-04-24 15:02:29 UTC
Interesting, some of the fixes I made between 1.4 and 1.5 for other websites must have positively influenced this, too. Thanks for reporting back and sorry for the trouble!