Joining jitsi meeting with Firefox forces the screen on

**NOTE**

Issues relating to the **general OS** can be filed under:
* [OS issues](https://source.puri.sm/Librem5/OS-issues)

Issues for **core apps** can be filed in their respective existing repositories:
* [Libhandy](https://source.puri.sm/Librem5/libhandy/issues) - GTK+ library for developing UIs for applications
* [Calls](https://source.puri.sm/Librem5/calls/issues) - phone calling application
* [Chatty](https://source.puri.sm/Librem5/chatty/issues) - messaging application
* [Phosh](https://source.puri.sm/Librem5/phosh/issues) - shell
* [wlroots](https://source.puri.sm/Librem5/wlroots/) - compositor
* [Virtboard](https://source.puri.sm/Librem5/virtboard/issues) - onscreen keyboard

Use this template for actual problems in other applications.
Use the "wishlist" template (still this repo) for requesting applications to be added/ported to the Librem 5.

What application is this relating to?

Firefox

What problem did you encounter

Screen cannot be locked while attending an audio conference via jitsi meet (meet.fsci.in instance tested)

What is the actual behaviour?

Audio gets cut.

What is the expected behaviour?

I should be able to listen and talk with screen turned off (to save battery).

How to reproduce

Please provide steps to reproduce the issue. If it's a graphical issue please attach screenshots.

Join any jitsi conference on meet.fsci.in and lock screen while someone is talking.

Which version did you encounter the bug in?

• I compiled it myself. If you compiled the application from source please provide the git revision via e.g. by running git log -1 --pretty=oneline and pasting the output below.

• I used a precompiled Debian package. Please paste the output of dpkg -s <package name> below.

• I used a prebuilt flatpak. Please paste the output of flatpak info <application-id> below.

• I used something else (please elaborate).

  Application version (output of `dpkg -l | grep <application name>`):
  Kernel version (output of `uname -a`):

What hardware are you running on?

• amd64 qemu image
• Librem5 devkit (please list what build number you are running)
• other (please elaborte)

Librem 5 evergreen.

Relevant logfiles

Please provide relevant logs. Since the relevant log files can vary depending on the application, here are some tips for gathering helpful logs:

• If you compiled the application yourself, the build log would be helpful.
• If you used a prebuilt debian package, you can provide the logs on an app with journalctl -b 0 | grep "<application-name>".