You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some code accessed the property 'ScreencastIface' on the module 'screencast'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Possible Solution
@somethingGoneWrong suggested a possible solution in #272. Gnome-shell maintainers commented also that loadInterfaceXML('org.gnome.Screencast') should be used and added: "As a bonus, that change will also work on 3.38, while the current code breaks (because screencasting was split out into a separate process)."
Steps to Reproduce (for bugs)
Enable the extension, start a GNOME session
Check your logs: journalctl -b0 | grep ScreencastIface
Logs
Above.
Your Environment
Where did you download the extension?
[ ] Gnome shell extension website
[X] From Git (3252312)
Gnome shell version: 3.36.6
Operating System and version: Fedora 32
Display server: X11
The text was updated successfully, but these errors were encountered:
Expected Behavior
Clean logs.
Current Behavior
The following appears in the logs:
Possible Solution
@somethingGoneWrong suggested a possible solution in #272. Gnome-shell maintainers commented also that
loadInterfaceXML('org.gnome.Screencast')
should be used and added: "As a bonus, that change will also work on 3.38, while the current code breaks (because screencasting was split out into a separate process)."Steps to Reproduce (for bugs)
journalctl -b0 | grep ScreencastIface
Logs
Above.
Your Environment
Where did you download the extension?
[ ] Gnome shell extension website
[X] From Git (3252312)
Gnome shell version: 3.36.6
Operating System and version: Fedora 32
Display server: X11
The text was updated successfully, but these errors were encountered: