Mozilla Firefox

firefox black window on wayland

Bug #1987976 reported by Michelet
120
This bug affects 23 people
Affects Status Importance Assigned to Milestone
Mozilla Firefox
Unknown
Unknown
Mutter
Fix Released
Unknown
Release Notes for Ubuntu
Fix Released
Undecided
Unassigned
mutter (Ubuntu)
Fix Released
High
Gunnar Hjalmarsson
Lunar
Fix Released
High
Gunnar Hjalmarsson

Bug Description

[ Impact ]

On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly.

You can easily reproduce the issue in a Wayland session:

* Close Firefox
* Run the command "killall Xwayland" in terminal
* Open Firefox

An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch.

[ Test Plan ]

On an updated Ubuntu 23.04:

* Install the mutter related binaries from lunar-proposed

* Reboot and log in to an Ubuntu on Wayland session

* Run the command "killall Xwayland"

* Open the Firefox snap, and find that it starts normally

[ Where problems could occur ]

This is the upstream merge request in question:

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970

The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs.

So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited.

The merge request was accepted upstream and will be included in mutter 44.2 which should be released approximately May 29.

[ Original description ]

nicolas@nicolas-fixe:~$ lsb_release -rd
Description: Ubuntu 22.04.1 LTS
Release: 22.04

nicolas@nicolas-fixe:~$ apt-cache policy firefox
firefox:
  Installé : 1:1snap1-0ubuntu2
  Candidat : 1:1snap1-0ubuntu2
 Table de version :
 *** 1:1snap1-0ubuntu2 500
        500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status

When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment.

I am at your disposal to answer any question you have.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 28 12:42:29 2022
InstallationDate: Installed on 2022-08-25 (2 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Snap.Changes: aucun changement trouvé
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)

See original description
Revision history for this message
Michelet (nicomich) wrote :
description: updated
Revision history for this message
Olivier Tilloy (osomon) wrote :

It appears that I cannot see the attached screenshot. Can you maybe try re-attaching it?

Can you share some details about your hardware (particularly GPU and drivers in use)?

Does it make any difference if you run it like this?

    MOZ_ENABLE_WAYLAND=1 snap run firefox

Changed in firefox (Ubuntu):
status: New → Incomplete
Revision history for this message
Michelet (nicomich) wrote :

Here is the attachment again. Can you see it now?
I am going to try the command line and tell you thereafter.

Sorry but can you tell me how and where I can gather information about GPU and drivers?

Revision history for this message
Michelet (nicomich) wrote :

I've just tried the command line and it worked (no more black screen).

Though the result is :
nicolas@nicolas-fixe:~$ MOZ_ENABLE_WAYLAND=1 snap run firefox
update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied
update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot open directory "/var/lib": permission denied
Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs

Revision history for this message
Olivier Tilloy (osomon) wrote :

No, I still can't see the attachment. I wonder whether this is a Launchpad bug?

In any case, it's good to know that the command line I suggested seems to work around the problem.
Just to confirm, if you run it with:

    MOZ_ENABLE_WAYLAND=0 snap run firefox

you get the black screen again?

For GPU info, you could attach the output of `sudo lshw -C display`.

Revision history for this message
Michelet (nicomich) wrote :

Oh I found that https://doc.ubuntu-fr.org/carte_graphique. Result is:
nicolas@nicolas-fixe:~$ lspci -vnn | grep -A 12 '\[030[02]\]' | grep -Ei "vga|3d|display|kernel"
01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller])
 Kernel driver in use: radeon
 Kernel modules: radeon
nicolas@nicolas-fixe:~$ sudo lshw -enable pci -class display
[sudo] Mot de passe de nicolas :
  *-display
       description: VGA compatible controller
       produit: RS880 [Radeon HD 4200]
       fabricant: Advanced Micro Devices, Inc. [AMD/ATI]
       identifiant matériel: 5
       information bus: pci@0000:01:05.0
       nom logique: /dev/fb0
       version: 00
       bits: 32 bits
       horloge: 33MHz
       fonctionnalités: pm msi vga_controller bus_master cap_list rom fb
       configuration : depth=32 driver=radeon latency=0 resolution=1920,1080
       ressources : irq:18 mémoire:d0000000-dfffffff portE/S:d000(taille=256) mémoire:fe9f0000-fe9fffff mémoire:fe800000-fe8fffff mémoire:c0000-dffff
nicolas@nicolas-fixe:~$ xrandr
Screen 0: minimum 16 x 16, current 1920 x 1080, maximum 32767 x 32767
XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm
   1920x1080 59.96*+
   1440x1080 59.99
   1400x1050 59.98
   1280x1024 59.89
   1280x960 59.94
   1152x864 59.96
   1024x768 59.92
   800x600 59.86
   640x480 59.38
   320x240 59.52
   1680x1050 59.95
   1440x900 59.89
   1280x800 59.81
   720x480 59.71
   640x400 59.95
   320x200 58.96
   1600x900 59.95
   1368x768 59.88
   1280x720 59.86
   1024x576 59.90
   864x486 59.92
   720x400 59.55
   640x350 59.77

Revision history for this message
Michelet (nicomich) wrote :

With
MOZ_ENABLE_WAYLAND=0 snap run firefox
it works too (no black screen), although the output shows messages:

nicolas@nicolas-fixe:~$ MOZ_ENABLE_WAYLAND=0 snap run firefox
update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied
update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot open directory "/var/lib": permission denied
Gtk-Message: 10:32:53.386: Failed to load module "canberra-gtk-module"
Gtk-Message: 10:32:53.396: Failed to load module "canberra-gtk-module"
ATTENTION: default value of option mesa_glthread overridden by environment.
Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs

Revision history for this message
Michelet (nicomich) wrote :

Let me try once again the attachment...

Revision history for this message
Michelet (nicomich) wrote :

I think this time it works because I renamed the file. Any misleading character in the old name ?

Revision history for this message
Michelet (nicomich) wrote :

If applicable, I let you open a new bug description ;)

Revision history for this message
Olivier Tilloy (osomon) wrote :

Yes, I can now see the screenshot.

And if you run from a terminal with just "snap run firefox" (i.e. without any definition of MOZ_ENABLE_WAYLAND), do you get a black screen?

Revision history for this message
Michelet (nicomich) wrote :

Wow! I have tried again and again the different ways. Sometimes it works, sometimes no...

Let's summarize:
1) Boot. Open Firefox by clicking on the icon: black screen (tried 10+ times)
2) Boot. Open Terminal. Type MOZ_ENABLE_WAYLAND=1 snap run firefox: no black screen (tried 5 times)
3) Boot. Open Terminal. Type MOZ_ENABLE_WAYLAND=0 snap run firefox: sometimes black screen, sometimes no, although I try to do exactly the same steps... (tried 10+ times)
4) Boot. Open Terminal. Type snap run firefox: sometimes black screen, sometimes no, although I try to do exactly the same steps... (tried 10+ times)

Amazing.
How can I help?

Revision history for this message
Michelet (nicomich) wrote :

Two more points:
a) We should write "black window" instead of "black screen". Only the Firefox's window is black. As you can see on the screenshot.
b) After I have a black window (whatever the way I obtain it), typing Ctrl-W closes the window and Firefox menu icon doesn't have it's orange bullet nearby anymore. Then, clicking again on the Firefox's menu icon opens Firefox's window normally (no black window) EXCEPT that I lose every tabs opened in the last session (and yes, of course, I have properly configured the fact that I want to save the tabs between two sessions).

Hope that helps!

Revision history for this message
Olivier Tilloy (osomon) wrote :

Can you reproduce the problem with an upstream build of firefox (downloaded from https://download.mozilla.org/?product=firefox-latest-ssl&os=linux64&lang=fr)?

Would you mind filing an upstream bug report at https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox, and sharing the link to it here?

Revision history for this message
Michelet (nicomich) wrote :

I am so sorry, I am not sure I will be able to do that.
Let me try...
I have just downloaded FF104.0.1 with the link you provide.

Revision history for this message
Michelet (nicomich) wrote :

I doubled-click on firefox-bin. See the attachment.

Revision history for this message
Michelet (nicomich) wrote :

Let me try the upstream bug report...

Revision history for this message
In , Michelet (nicomich) wrote :

Created attachment 9292430
Capture.png

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0

Steps to reproduce:

Boot.
Enter your password's user.
Simple left-click on the Firefox's menu icon.

Actual results:

A window opens which is totally black and remains black.

Expected results:

A Firefox window should have opened correctly.

Revision history for this message
Michelet (nicomich) wrote :

Done.
https://bugzilla.mozilla.org/show_bug.cgi?id=1788205

Revision history for this message
In , Release-mgmt-account-bot (release-mgmt-account-bot) wrote :

The [Bugbug](https://github.com/mozilla/bugbug/) bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Revision history for this message
In , Olivier Tilloy (osomon) wrote :

Original issue was filed downstream, and contains more details: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987976.

This seems to happen only with the firefox snap, and not consistently.

Revision history for this message
In , Olivier Tilloy (osomon) wrote :

The reporter wrote in the Launchpad bug report that an apparently reliable workaround is to run firefox with `MOZ_ENABLE_WAYLAND=1`.

Revision history for this message
In , Olivier Tilloy (osomon) wrote :

Could you please run firefox with `MOZ_ENABLE_WAYLAND=1`, browse to `about:support`, copy the raw data into the clipboard and share it here?

Changed in firefox (Ubuntu):
status: Incomplete → New
Revision history for this message
Olivier Tilloy (osomon) wrote :

Thanks!

Revision history for this message
In , Michelet (nicomich) wrote :

Created attachment 9292447
about:support after launching with MOZ_ENABLE_WAYLAND=1

Revision history for this message
Michelet (nicomich) wrote :

Thank you!

Bug Watch Updater (bug-watch-updater)
Changed in firefox:
status: Unknown → New
Revision history for this message
Michelet (nicomich) wrote : Re: firefox black window

I have two more things to tell you. Where should I write them? In launchpad or bugzilla?

Revision history for this message
Olivier Tilloy (osomon) wrote :

Better in bugzilla, please.

Revision history for this message
In , Michelet (nicomich) wrote :

This morning I forgot to launch Firefox with the command line, I mean I launched Firefox by clicking the icon and it worked! I rebooted to try again but unfortunately it didn't work the second time.

Revision history for this message
In , Michelet (nicomich) wrote :

I've just found something which seems strange to me.
I would like to show you screenshots but I cannot attach them...

Revision history for this message
In , Michelet (nicomich) wrote :

Created attachment 9293001
CaptureBugzilla1788205_1.png

On this screenshot CaptureBugzilla1788205_1.png of Ubuntu Software, I can see one update available: Firefox!!! How is that possible whereas my system is up to date as you can see on attachment CaptureBugzilla1788205_2.png????

Revision history for this message
In , Michelet (nicomich) wrote :

Created attachment 9293002
CaptureBugzilla1788205_2.png

Revision history for this message
In , Michelet (nicomich) wrote :

Are there two different ways for updating???
Why the Firefox update does not appear in the update manager window, which is so far, for me, the only way to update my system??

Revision history for this message
In , Lissyx+mozillians (lissyx+mozillians) wrote :

That's a question for Ubuntu people, looks like the update is for Snap package while your second screenshot is the apt update status

Revision history for this message
In , Olivier Tilloy (osomon) wrote :

Can you share the output of the following commands?

    apt policy firefox

    snap info firefox

Revision history for this message
In , Michelet (nicomich) wrote :

nicolas@nicolas-fixe:~$ apt policy firefox
firefox:
  Installé : 1:1snap1-0ubuntu2
  Candidat : 1:1snap1-0ubuntu2
 Table de version :
 *** 1:1snap1-0ubuntu2 500
        500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status
nicolas@nicolas-fixe:~$ snap info firefox
name: firefox
summary: Mozilla Firefox web browser
publisher: Mozilla✓
store-url: https://snapcraft.io/firefox
contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla
license: unset
description: |
  Firefox is a powerful, extensible web browser with support for modern web
  application technologies.
commands:
  - firefox
  - firefox.geckodriver
snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
tracking: latest/stable/ubuntu-22.04
refresh-date: aujourd'hui à 09h04, heure des Rocheuses
channels:
  latest/stable: 104.0.2-1 2022-09-06 (1810) 185MB -
  latest/candidate: 104.0.2-1 2022-09-05 (1810) 185MB -
  latest/beta: 105.0b8-1 2022-09-07 (1814) 187MB -
  latest/edge: 106.0a1 2022-09-07 (1818) 183MB -
  esr/stable: 91.13.0esr-1 2022-09-02 (1791) 161MB -
  esr/candidate: 102.2.0esr-2 2022-09-02 (1793) 182MB -
  esr/beta: ↑
  esr/edge: 102.2.0esr-2 2022-09-02 (1793) 182MB -
installed: 104.0.2-1 (1810) 185MB -

Revision history for this message
In , Michelet (nicomich) wrote :

Oh sorry for the strikethrough. I thing it came automatically with the syntax. Let's try this way:

nicolas@nicolas-fixe:$ apt policy firefox
firefox:
  Installé : 1:1snap1-0ubuntu2
  Candidat : 1:1snap1-0ubuntu2
 Table de version :
 *** 1:1snap1-0ubuntu2 500
        500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status
nicolas@nicolas-fixe:$ snap info firefox
name: firefox
summary: Mozilla Firefox web browser
publisher: Mozilla✓
store-url: https://snapcraft.io/firefox
contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla
license: unset
description: |
  Firefox is a powerful, extensible web browser with support for modern web
  application technologies.
commands:
  - firefox
  - firefox.geckodriver
snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
tracking: latest/stable/ubuntu-22.04
refresh-date: aujourd'hui à 09h04, heure des Rocheuses
channels:
  latest/stable: 104.0.2-1 2022-09-06 (1810) 185MB -
  latest/candidate: 104.0.2-1 2022-09-05 (1810) 185MB -
  latest/beta: 105.0b8-1 2022-09-07 (1814) 187MB -
  latest/edge: 106.0a1 2022-09-07 (1818) 183MB -
  esr/stable: 91.13.0esr-1 2022-09-02 (1791) 161MB -
  esr/candidate: 102.2.0esr-2 2022-09-02 (1793) 182MB -
  esr/beta: ↑
  esr/edge: 102.2.0esr-2 2022-09-02 (1793) 182MB -
installed: 104.0.2-1 (1810) 185MB -

Revision history for this message
In , Olivier Tilloy (osomon) wrote :

Does Ubuntu Software still offer an update for firefox?

Revision history for this message
In , Michelet (nicomich) wrote :

Created attachment 9294284
Capture2022-09-12.png

No update offered anymore.

Revision history for this message
In , Michelet (nicomich) wrote :

I mean: for Firefox.

Revision history for this message
In , Release-mgmt-account-bot (release-mgmt-account-bot) wrote :

The severity field is not set for this bug.
:gerard-majax, could you have a look please?

For more information, please visit [auto_nag documentation](https://wiki.mozilla.org/Release_Management/autonag#workflow.2Fno_severity.py).

Revision history for this message
Launchpad Janitor (janitor) wrote : Re: firefox black window

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in firefox (Ubuntu):
status: New → Confirmed
Revision history for this message
In , Alan Jenkins (aj504) wrote :

I have the same black window problem. Can I help?

I can reproduce it with upstream "firefox" unpacked from firefox-104.0.2.tar.bz2 ! (As well as by using the snap)

It seems *not* to happen if instead of the "firefox" launcher binary, I run "firefox-bin" directly. What's the difference?

It happens the first time I start firefox after logging in. If I quit firefox and start it again, it works. (The window may *start* black, but it changes after a few seconds. As reported here: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838963 )

My GPU description is "Mesa DRI Intel(R) HD Graphics 2000 (SNB GT1)". (No secondary GPU). I use Ubuntu 22.04.1 (x86_64).

Revision history for this message
In , Alan Jenkins (aj504) wrote :

> It seems not to happen if instead of the "firefox" launcher binary, I run "firefox-bin" directly. What's the difference?

Nevermind. I think it can happen with either. It's just a bit random whether it happens or not.

Revision history for this message
In , Lissyx+mozillians (lissyx+mozillians) wrote :

(In reply to Alan Jenkins from comment #20)
> > It seems not to happen if instead of the "firefox" launcher binary, I run "firefox-bin" directly. What's the difference?
>
> Nevermind. I think it can happen with either. It's just a bit random whether it happens or not.

Just to clavify, you reproduce with both Snap and tarball downloaded from mozilla.org ?
Can you share `about:support` ? Can you verify with `MOZ_ENABLE_WAYLAND=1 firefox` if the issue disappears?

Revision history for this message
In , Alan Jenkins (aj504) wrote :

Sorry, I can't deal with the randomness. Let's simplify -

$ sudo snap disable firefox
firefox disabled

$ cat ~/.local/share/applications/firefox2.desktop
[Desktop Entry]
Version=1.0
Name=Firefox Web Browser 2
Exec=/bin/bash -c "/home/alan/firefox-104.0.2/firefox/firefox"
Terminal=false
X-MultipleArgs=false
Type=Application
Icon=firefox
Categories=GNOME;GTK;Network;WebBrowser;
MimeType=text/html;text/xml;application/xhtml+xml;application/xml;application/rss+xml;application/rdf+xml;image/gif;image/jpeg;image/png;x-scheme-handler/http;x-scheme-handler/https;video/webm;application/x-xpinstall;
StartupNotify=true
StartupWMClass=firefox
$

With the above, if I log in and click firefox, I get stuck at the black window. If I quit firefox and try again, I get a *temporary* black window, and then a working firefox.

If I edit the file and change it to "MOZ_ENABLE_WAYLAND=1 /home/alan/firefox-104.0.2/firefox/firefox", then two things change:

1. When I log in and click firefox, firefox works the first time. I don't have to quit it and click it again before I can use firefox.
2. When firefox starts, there is no *temporary* black screen either.

---

When I *was* trying to launch firefox from the terminal, I also noticed a difference in debug messages:

$ /bin/bash -c "/home/alan/firefox-104.0.2/firefox/firefox"
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[2022-09-19T12:44:36Z ERROR viaduct::backend::ffi] Missing HTTP status
[2022-09-19T12:44:36Z ERROR viaduct::backend::ffi] Missing HTTP status
$

$ /bin/bash -c "MOZ_ENABLE_WAYLAND=1 /home/alan/firefox-104.0.2/firefox/firefox"
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
[2022-09-19T12:44:43Z ERROR viaduct::backend::ffi] Missing HTTP status
[2022-09-19T12:44:43Z ERROR viaduct::backend::ffi] Missing HTTP status
$

Revision history for this message
In , Alan Jenkins (aj504) wrote :

Created attachment 9295260
about:support json from running ./firefox-104.0.2/firefox/firefox

Revision history for this message
In , Alan Jenkins (aj504) wrote :

Created attachment 9295261
about:support json from running MOZ_ENABLE_WAYLAND=1 ./firefox-104.0.2/firefox/firefox

Revision history for this message
In , Release-mgmt-account-bot (release-mgmt-account-bot) wrote :

The severity field is not set for this bug.
:gerard-majax, could you have a look please?

For more information, please visit [auto_nag documentation](https://wiki.mozilla.org/Release_Management/autonag#workflow.2Fno_severity.py).

Revision history for this message
Saptarshi Roy (sroypc) wrote :

This affects me too.

Memory: 4.0 GiB
Processor: Intel® Celeron(R) N4000 CPU @ 1.10GHz × 2
Graphics: Mesa Intel® UHD Graphics 600 (GLK 2)
Disk Capacity: 128.0 GB

OS Name: Ubuntu 22.04.1 LTS
OS Type: 64-bit
GNOME Version: 42.4
Windowing System: Wayland

Revision history for this message
Davide (tarski10) wrote : Re: firefox black window

https://www.reddit.com/r/Ubuntu/comments/voat7x/firefox_1020_snap_in_ubuntu_2204_launches_to/

Revision history for this message
In , Lissyx+mozillians (lissyx+mozillians) wrote :

(In reply to Alan Jenkins from comment #22)
> Sorry, I can't deal with the randomness. Let's simplify -
>
> $ sudo snap disable firefox
> firefox disabled
>

So you dont use Snap anymore from that point

> $ cat ~/.local/share/applications/firefox2.desktop
> [Desktop Entry]
> Version=1.0
> Name=Firefox Web Browser 2
> Exec=/bin/bash -c "/home/alan/firefox-104.0.2/firefox/firefox"

This is a mozilla-downloaded binary right?

> Terminal=false
> X-MultipleArgs=false
> Type=Application
> Icon=firefox
> Categories=GNOME;GTK;Network;WebBrowser;
> MimeType=text/html;text/xml;application/xhtml+xml;application/xml;application/rss+xml;application/rdf+xml;image/gif;image/jpeg;image/png;x-scheme-handler/http;x-scheme-handler/https;video/webm;application/x-xpinstall;
> StartupNotify=true
> StartupWMClass=firefox
> $
>
> With the above, if I log in and click firefox, I get stuck at the black window. If I quit firefox and try again, I get a *temporary* black window, and then a working firefox.

That means you repro the black window issue without using Snap, right?

>
> If I edit the file and change it to "MOZ_ENABLE_WAYLAND=1 /home/alan/firefox-104.0.2/firefox/firefox", then two things change:
>
> 1. When I log in and click firefox, firefox works the first time. I don't have to quit it and click it again before I can use firefox.
> 2. When firefox starts, there is no *temporary* black screen either.

So does it means that forcing Wayland on mozilla's binary fixes the issue completely?

Revision history for this message
In , Alan Jenkins (aj504) wrote :

Yes to all of the above.

I disabled the Firefox snap. I used this download from mozilla.org, and I still had the black window issue.

And forcing Wayland seems to fix that completely.

Revision history for this message
In , Lissyx+mozillians (lissyx+mozillians) wrote :

Alan, since you happen to repro without snap, was there a release you got working correctly? Can you try and go back in time and find with `mozregression` maybe which patch triggered the issue ? https://mozilla.github.io/mozregression/quickstart.html

Revision history for this message
In , Robert Mader (robert.posteo) wrote :

Another interesting point would be if setting `gfx.x11-egl.force-disabled` (in `about:config`) to `true` helps with the issue.

Revision history for this message
In , Robert Mader (robert.posteo) wrote :

Also, I suppose `gfx.webrender.software:true` works around the issue?

Revision history for this message
In , Alan Jenkins (aj504) wrote :

Nice tool. It seemed like nightlies default to Wayland, so I had to test with MOZ_ENABLE_WAYLAND=0.

Bisecting the *temporary* black window gave:

 9:33.09 INFO: Last good revision: d1eb6fe5a1fa5457425c5a33f212516a5eeaa381
 9:33.09 INFO: First bad revision: 498e0e6f9b19107c8c17525a3d01a659f89002e8
 9:33.09 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d1eb6fe5a1fa5457425c5a33f212516a5eeaa381&tochange=498e0e6f9b19107c8c17525a3d01a659f89002e8

With the mozilla-central (nightly?) builds downloaded by mozregression, I could not reproduce the main issue, the black window that remains black. Any suggestions there?

So the following was tested back on my 104.0.2 (originally downloaded from https://download.mozilla.org/?product=firefox-latest-ssl&os=linux64&lang=fr ) :

> Another interesting point would be if setting gfx.x11-egl.force-disabled (in about:config) to true helps with the issue.

No.

> Also, I suppose gfx.webrender.software:true works around the issue?

No.

Based on the bisection result, I also tried XDG_CURRENT_DESKTOP="". This changed the main issue but did not solve it. The window did not remain black, but it did not show firefox controls either.

Revision history for this message
In , Robert Mader (robert.posteo) wrote :

Oh, that's really interesting...so does launching with `MOZ_GTK_TITLEBAR_DECORATION=system` also solve the issue?

Revision history for this message
In , Alan Jenkins (aj504) wrote :

(In reply to Robert Mader [:rmader] from comment #32)
> Oh, that's really interesting...so does launching with `MOZ_GTK_TITLEBAR_DECORATION=system` also solve the issue?

It does about the same as XDG_CURRENT_DESKTOP="". Instead of remaining black, basically nothing gets drawn. The inside of the window just shows my desktop wallpaper.

(I think XDG_CURRENT_DESKTOP="" shows a titlebar, and MOZ_GTK_TITLEBAR_DECORATION=system doesn't).

Revision history for this message
In , Robert Mader (robert.posteo) wrote :

So the fact that even software rendering (`gfx.webrender.software:true`) is broken strongly suggest that something with the affected setup is deeply broken - disabling hardware acceleration is usually our last resort for such issues.

Alan, have you tested a few other Xwayland apps and do they all work correctly? And is this on a clean system without weird modifications? :P

Revision history for this message
In , Alan Jenkins (aj504) wrote :

Weird!

I can run xterm. Including immediately after login, which is how I've been reproducing this Firefox issue.

I can change my hacked-up .desktop file to run "WAYLAND_DISPLAY='' libreoffice" instead, and the libreoffice window seems fine.

I can run glxgears, xeyes, and xvidtune ok :-). (Didn't bother trying those immediately after login).

The system should be clean of development or debug hacks. It's a desktop that runs Ubuntu, and I'm not the person who uses it normally. I have some setup scripts (Ansible), that mostly just install the right packages.

You might have noticed from the Launchpad bug, some reddit users reported this on June 30. The poster thought it "just started happening with Firefox 102.0". I don't know if that was the problem. On the system I have, I had it as soon as I updated to Ubuntu 22.04, which was a bit later.

Reddit link: https://old.reddit.com/r/Ubuntu/comments/voat7x/firefox_1020_snap_in_ubuntu_2204_launches_to/

Of course the Launchpad bug is only voted as "affects 4 people", so it doesn't sound like it's universal.

Revision history for this message
In , Lissyx+mozillians (lissyx+mozillians) wrote :

(In reply to Alan Jenkins from comment #31)
> Nice tool. It seemed like nightlies default to Wayland, so I had to test with MOZ_ENABLE_WAYLAND=0.
>
> Bisecting the *temporary* black window gave:
>
> 9:33.09 INFO: Last good revision: d1eb6fe5a1fa5457425c5a33f212516a5eeaa381
> 9:33.09 INFO: First bad revision: 498e0e6f9b19107c8c17525a3d01a659f89002e8
> 9:33.09 INFO: Pushlog:
> https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d1eb6fe5a1fa5457425c5a33f212516a5eeaa381&tochange=498e0e6f9b19107c8c17525a3d01a659f89002e8
>

Emilio, could it be a regression from bug 1756903 ?

Revision history for this message
In , Emilio (emiliocobos) wrote :

Seems possible, but I don't know what might be going on in the reporter's machine, since that's a setup that works ~everywhere else?

To double-check, can you confirm that `MOZ_GTK_TITLEBAR_DECORATION=system` works, but `MOZ_GTK_TITLEBAR_DECORATION=client` doesn't? Also does enabling the system titlebar (from the customize page) prevent it from happening?

Revision history for this message
In , Robert Mader (robert.posteo) wrote :

(In reply to Alan Jenkins from comment #35)
> Weird!

Indeed :( But thanks for testing!

> I can run glxgears, xeyes, and xvidtune ok :-). (Didn't bother trying those immediately after login).

I think these are all apps with server side decorations (SSD). Could you try `GDK_BACKEND=x11 cheese` or `GDK_BACKEND=x11 gedit`? So we have GTK apps with client side decorations (CSD)?

Revision history for this message
In , Alan Jenkins (aj504) wrote :

Created attachment 9298516
Screenshot of firefox with MOZ_GTK_TITLEBAR_DECORATION=system

> To double-check, can you confirm that MOZ_GTK_TITLEBAR_DECORATION=system works

No, I say MOZ_GTK_TITLEBAR_DECORATION=system fails. Just slightly differently. Instead of a black window, only a border (drop shadow?) is drawn. See screenshot. The gnome notification bubble "firefox is ready" is flickering, constantly and quickly.

Revision history for this message
In , Alan Jenkins (aj504) wrote :

Created attachment 9298517
Screenshot from 2022-10-13 20-59-46.png

1. If I launch gedit with GDK_BACKEND=x11, as the first app after logging in, it appears usable. However the window is incorrectly drawn with a square window border. See screenshot.

   If I then launch firefox, using the snap for convenience, firefox is usable.

2. (As before) If I launch firefox using the snap for convenience, as the first app after logging in, it is not usable. Because the entire window is black.

   If I then launch gedit with GDK_BACKEND=x11, its window borders are drawn correctly.

Revision history for this message
In , Alan Jenkins (aj504) wrote :

It feels like the problem is to do with socket-activated Xwayland.

I can suppress the issue where firefox remains black, by editing my .desktop file to run "xlsclients" first. I.e.:

Exec=/bin/bash -c "xlsclients; MOZ_ENABLE_WAYLAND=0 /home/alan/firefox-104.0.2/firefox/firefox"

Similarly, the issue with gedit drawing square window border corners is suppressed if I use

Exec=/bin/bash -c "xlsclients; GDK_BACKEND=x11 gedit"

(With less confidence: it seemed that if I ran weston, then "Xwayland :2", then "MOZ_ENABLE_WAYLAND=0 DISPLAY=:2 firefox", then the resulting firefox window was usable).

Revision history for this message
In , Robert Mader (robert.posteo) wrote :

Hm, this pretty much sounds like Gnome-Shell bug around Xwayland-on-demand to me - so maybe a better place for that would be https://gitlab.gnome.org/GNOME/mutter/-/issues (or a Ubuntu bug, in case they ship some custom patches).

Revision history for this message
In , Release-mgmt-account-bot (release-mgmt-account-bot) wrote :

Setting `Regressed by` field after analyzing regression range found by mozregression in comment #31.

Revision history for this message
In , Alan Jenkins (aj504) wrote :

Something similar happened on Fedora. So I've reported to GNOME.

"Timing/race condition with Xwayland-on-demand breaks firefox & confuses gedit etc"
Link: https://gitlab.gnome.org/GNOME/mutter/-/issues/2472

Revision history for this message
Alan Jenkins (aj504) wrote :

Something similar happened on Fedora. So I've reported to GNOME.

"Timing/race condition with Xwayland-on-demand breaks firefox & confuses gedit etc"
Link: https://gitlab.gnome.org/GNOME/mutter/-/issues/2472

Daniel van Vugt (vanvugt)
Changed in mutter (Ubuntu):
status: New → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in mutter:
status: Unknown → New
Revision history for this message
In , Alan Jenkins (aj504) wrote :

(In reply to Robert Mader [:rmader] from comment #42)
> Hm, this pretty much sounds like Gnome-Shell bug around Xwayland-on-demand to me - so maybe a better place for that would be https://gitlab.gnome.org/GNOME/mutter/-/issues (or a Ubuntu bug, in case they ship some custom patches).

...

> Thanks @sourcejedi! I've so far been unable to reproduce this on four different systems with Fedora 36 or Manjaro,

Hi Robert. I got a new reproducer for Firefox, which doesn't use Xwayland. I ran this on my Fedora 36 system, the system that required a quick hand to reproduce with my .desktop file method.

WARNING for people with photosensitive epilepsy. This will cause full-screen flickering.

1. Make sure user X is logged out, or at least not running Firefox.
2. Switch to a text console (ctrl + alt + f6) and log in.
3. `startx /usr/bin/fvwm`
4. Left click on the desktop to open the app menu. Open an xterm.
5. Open a second xterm.
6. In xterm 1, run `while true; do picom; sleep 0.1; killall picom; done`. The screen will now start flickering.
7. In xterm 2, run `firefox`

Result: Firefox doesn't draw anything inside its window, or is completely black.

Revision history for this message
In , Lissyx+mozillians (lissyx+mozillians) wrote :

*** Bug 1797800 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Vishal Singh Panesar (vishal-panesar) wrote :

[Firefox 109]
If I am not mistaken:
1. it is consistently happening (i.e., completely black right after after boot), and
2. when closed for the first time, and reopened, it opens and asks whether to restore previous session or not, and
3. I always close Firefox before shutting down, so point 2 should not be applicable

Revision history for this message
In , Gwatson-r (gwatson-r) wrote :

Robert, do you know what we should be trying to do here? Should it remain an S2 for Firefox?

Revision history for this message
In , Robert Mader (robert.posteo) wrote :

Since this was reported for a device running the Crocus Mesa driver in situations where implicit drm modifiers are most likely used (Xwayland, X11 compositor), there's certain chance that it will be fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21209

Michelet/Alan, any chance you could test that commit?

Revision history for this message
In , Robert Mader (robert.posteo) wrote :

Oh wow, I think I just managed to reproduce this on my Iris laptop - in a fresh session with Xwayland on demand. That and comment 45 points to a race condition in the FF code regarding switching between composited and non-composited X11.

Revision history for this message
In , Ttanasoaia (ttanasoaia) wrote :

*** Bug 1817252 has been marked as a duplicate of this bug. ***

Revision history for this message
In , W-jan-k (w-jan-k) wrote :

*** Bug 1822374 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Release-mgmt-account-bot (release-mgmt-account-bot) wrote :

Redirect a needinfo that is pending on an inactive user to the triage owner.
:stransky, since the bug has high severity and recent activity, could you have a look please?

For more information, please visit [auto_nag documentation](https://wiki.mozilla.org/Release_Management/autonag#inactive_ni_pending.py).

Revision history for this message
In , Stransky (stransky) wrote :

When Bug 1725245 lands we'll test it and see results on Wayland/XWayland environment.

Revision history for this message
In , corrado venturini (corradoventu) wrote :

In Ubuntu 23.04 kernel 6.1 or 6.2 Firefox does not start at all using his .desktop file, starts with a black screen the 1st time is started from terminal with 'firefox' or 'snap run firefox' and start fine the 2nd time is started from terminal with 'firefox' or 'snap run firefox'

Bug Watch Updater (bug-watch-updater)
Changed in firefox:
status: New → Confirmed
Revision history for this message
In , W-jan-k (w-jan-k) wrote :

*** Bug 1825991 has been marked as a duplicate of this bug. ***

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote : Re: firefox black window

This fixes the issue for me:

$ cat /etc/xdg/autostart/firefox-snap-launch-xwayland.desktop
[Desktop Entry]
Name=Launch Xwayland on startup of wayland session
Comment=This allows to start the Firefox snap from the dock without a black window
Type=Application
Exec=sh -c 'if [ "$XDG_SESSION_TYPE" = "wayland" ]; then xrefresh; fi'
TryExec=xrefresh
OnlyShowIn=GNOME;
NoDisplay=true

How about letting some package install that, or maybe make use of the xrefresh command in some other way.

Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

Simple way to reproduce is:

killall XWayland # may kill other apps!
start firefox

Now, it happens in all the installation where something doesn't bring X11 on startup and firefox is the first app launched.

Gunnar Hjalmarsson (gunnarhj)
summary: - firefox black window
+ firefox black window on wayland
Changed in mutter (Ubuntu):
assignee: nobody → Gunnar Hjalmarsson (gunnarhj)
importance: Undecided → High
status: Confirmed → In Progress
Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

Marco Trevisan submitted an upstream mutter merge request with a fix of this issue. I have applied it to the Ubuntu package through a PPA, installed the resulting binaries, and accomplished some tests:

* I can no longer reproduce the issue with a black window when opening Firefox in wayland, not even after having run "killall Xwayland".

* This sequence:

  killall Xwayland; sleep 3; GDK_BACKEND=x11 gedit

  results in a normal gedit window as far as I can tell.

* I also entered an x11 session, and also there I can open Firefox without issues.

So I uploaded mutter to the lunar unapproved queue for consideration by the release team.

Changed in mutter (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Gunnar, thanks for reporting on this bug. A quick question: since the original issue got reported in 2022 before kinetic release, what was the status for this in 22.10? Was this also broken there? It's important for us to know if this is a regression or not.

Also, with a visible workaround (re-running firefox), my recommendation would be to release note it, and maybe only include it in case we will need to do a full respin of all desktop RC images for 23.04.

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

I'm not sure, but I think the issue was present in kinetic. Hence not a regression (probably).

I agree. Only this issue would not motivate a respin, and mentioning it in the release note sounds reasonable.

Revision history for this message
In , Lissyx+mozillians (lissyx+mozillians) wrote :

Upstream issue seems to be on `mutter` package and https://salsa.debian.org/gnome-team/mutter/-/blob/8fcc1a017d342e6dadd521dacfa845824a7de490/debian/patches/display-Set-compositor-selection-earlier-on-XWayland.patch seems to be a patch.

Revision history for this message
In , Lissyx+mozillians (lissyx+mozillians) wrote :

It's shipping as a SRU (23.04) this week. Older releases will come after.

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote (last edit ):

Mentioned under "Known Issues" in the lunar release notes.

Changed in ubuntu-release-notes:
status: New → Fix Released
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Hi Gunnar and others,

with Lunar just released, I'm going over the lunar unapproved queue to pick out packages that should now become SRUs for lunar.

Could someone please add the SRU template to this bug's description, and fill it out?

Since the package is in unapproved, and not proposed, I'm switching the bug task back to "in progress".

Regarding the patch, I see there is still a bit of back and forth in the upstream merge request[1]. Can we get that stabilized, hopefully even merged, before committing to an SRU?

1. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970

Changed in mutter (Ubuntu):
status: Fix Committed → In Progress
Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

@Andreas: I just wrote this on #ubuntu-desktop:

https://irclogs.ubuntu.com/2023/04/20/%23ubuntu-desktop.html#t17:57

Gunnar Hjalmarsson (gunnarhj)
description: updated
no longer affects: firefox (Ubuntu Lunar)
Changed in firefox (Ubuntu):
status: Confirmed → Invalid
Bug Watch Updater (bug-watch-updater)
Changed in firefox:
status: Confirmed → Fix Released
Revision history for this message
In , W-jan-k (w-jan-k) wrote :

*** Bug 1830482 has been marked as a duplicate of this bug. ***

Bug Watch Updater (bug-watch-updater)
Changed in firefox:
status: Fix Released → Unknown
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mutter - 44.0-2ubuntu6

---------------
mutter (44.0-2ubuntu6) mantic; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * Fix issue with Firefox opening black window in wayland sessions
    - d/p/display-Set-compositor-selection-earlier-on-XWayland.patch
      (LP: #1987976)

 -- Gunnar Hjalmarsson <email address hidden> Mon, 01 May 2023 18:27:57 +0200

Changed in mutter (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello Michelet, or anyone else affected,

Accepted mutter into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/44.0-2ubuntu4.23.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in mutter (Ubuntu Lunar):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-lunar
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (mutter/44.0-2ubuntu4.23.04.1)

All autopkgtests for the newly accepted mutter (44.0-2ubuntu4.23.04.1) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/44.0-2ubuntu4.23.04.1 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/lunar/update_excuses.html#mutter

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Mathew Hodson (mhodson)
no longer affects: firefox (Ubuntu)
Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

As regards the failed autopkgtest on amd64, it's reasonably not related to the proposed change, since also version 44.0-2ubuntu4 fails now (unlike before the 23.04 release). My impression is that it's a problem beyond the mutter package:

Running test case...
TAP version 13
# random seed: R02S29be415b178acf3a28289b5a6c5eecf4
# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation memory (GMemorySettingsBackend) for ‘gsettings-backend’
# libmutter-MESSAGE: Running Mutter Test (using mutter 44.0) as a Wayland display server
Bail out! libmutter-FATAL-WARNING: Failed to open gpu '/dev/dri/card0': Couldn't find render node device for '/dev/dri/card0'
Trace/breakpoint trap (core dumped)
FAIL: mutter-12/closed-transient-no-input-parent-delayed-focus-default-cancelled.test (Child process exited with code 133)
Running test: mutter-12/closed-transient-no-input-no-take-focus-parents.test
Starting D-Bus daemons (session & system)...
Launching required services...
Starting mocked services...
Running test case...
TAP version 13
# random seed: R02Se6b3bbfe78ba522ee4e9987b0b12eb51
# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation memory (GMemorySettingsBackend) for ‘gsettings-backend’
# libmutter-MESSAGE: Running Mutter Test (using mutter 44.0) as a Wayland display server
Bail out! libmutter-FATAL-WARNING: Failed to open gpu '/dev/dri/card0': Couldn't find render node device for '/dev/dri/card0'
Trace/breakpoint trap (core dumped)
FAIL: mutter-12/closed-transient-no-input-no-take-focus-parents.test (Child process exited with code 133)

The very same failure happens in mantic:

https://autopkgtest.ubuntu.com/packages/m/mutter/mantic/amd64

but somebody seems to have added a hint so 44.0-2ubuntu6 migrated to mantic-release, and I suppose doing so would be motivated for lunar/amd64 too.

As regards the regular verification, I successfully accomplished the steps in the test plan using version 44.0-2ubuntu4.23.04.1 (from lunar-proposed) of the binaries built by the mutter source.

tags: added: verification-done verification-done-lunar
removed: verification-needed verification-needed-lunar
Gunnar Hjalmarsson (gunnarhj)
tags: added: update-excuse-lunar
Revision history for this message
Norbert (asterix52) wrote :

Firefox works fine with the new mutter version on lunar.

Thanks

Bug Watch Updater (bug-watch-updater)
Changed in mutter:
status: New → Fix Released
Revision history for this message
In , W-jan-k (w-jan-k) wrote :

*** Bug 1832688 has been marked as a duplicate of this bug. ***

Revision history for this message
In , W-jan-k (w-jan-k) wrote :

*** Bug 1833474 has been marked as a duplicate of this bug. ***

Daniel van Vugt (vanvugt)
tags: added: fixed-in-mutter-44.2 fixed-upstream
Revision history for this message
Angel D. Segarra (angel-segarra) wrote :

On 23.04 I still get a black window on first firefox start with the proposed mutter update.

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

On 2023-05-19 18:45, Angel D. Segarra wrote:
> On 23.04 I still get a black window on first firefox start with the
> proposed mutter update.

Please note that installing the mutter binary package is not sufficient. I suspect that you need to do:

sudo apt install libmutter-12-0/lunar-proposed gir1.2-mutter-12/lunar-proposed

(and relogin)

Please try that and let us know if it helps.

Revision history for this message
Angel D. Segarra (angel-segarra) wrote :

that was it, appears to be fixed on my end. Thanks.

Revision history for this message
In , W-jan-k (w-jan-k) wrote :

*** Bug 1834232 has been marked as a duplicate of this bug. ***

Jeremy Bícha (jbicha)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mutter - 44.0-2ubuntu4.23.04.1

---------------
mutter (44.0-2ubuntu4.23.04.1) lunar; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * Fix issue with Firefox opening black window in wayland sessions
    - d/p/display-Set-compositor-selection-earlier-on-XWayland.patch
      (LP: #1987976)

 -- Gunnar Hjalmarsson <email address hidden> Mon, 24 Apr 2023 19:59:49 +0200

Changed in mutter (Ubuntu Lunar):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
In , W-jan-k (w-jan-k) wrote :

*** Bug 1829390 has been marked as a duplicate of this bug. ***

Revision history for this message
In , W-jan-k (w-jan-k) wrote :

*** Bug 1831711 has been marked as a duplicate of this bug. ***

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.