firefox black window on wayland

[Michelet]

[ 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)

[Olivier Tilloy (osomon)]

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

[Michelet (nicomich)]

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?

[Michelet (nicomich)]

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

[Olivier Tilloy (osomon)]

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`.

[Michelet (nicomich)]

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

[Michelet (nicomich)]

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

[Michelet (nicomich)]

Let me try once again the attachment...

[Michelet (nicomich)]

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

[Michelet (nicomich)]

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

[Olivier Tilloy (osomon)]

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?

[Michelet (nicomich)]

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?

[Michelet (nicomich)]

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!

[Olivier Tilloy (osomon)]

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?

[Michelet (nicomich)]

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.

[Michelet (nicomich)]

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

[Michelet (nicomich)]

Let me try the upstream bug report...

[Michelet (nicomich)]

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.

[Michelet (nicomich)]

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

[Release-mgmt-account-bot (release-mgmt-account-bot)]

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.

[Olivier Tilloy (osomon)]

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.

[Olivier Tilloy (osomon)]

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

[Olivier Tilloy (osomon)]

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?

[Olivier Tilloy (osomon)]

Thanks!

[Michelet (nicomich)]

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

[Michelet (nicomich)]

Thank you!

[Michelet (nicomich)]

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

[Olivier Tilloy (osomon)]

Better in bugzilla, please.

[Michelet (nicomich)]

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.

[Michelet (nicomich)]

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

[Michelet (nicomich)]

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????

[Michelet (nicomich)]

Created attachment 9293002
CaptureBugzilla1788205_2.png

[Michelet (nicomich)]

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??

[Lissyx+mozillians (lissyx+mozillians)]

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

[Olivier Tilloy (osomon)]

Can you share the output of the following commands?

    apt policy firefox

    snap info firefox

[Michelet (nicomich)]

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 -

[Michelet (nicomich)]

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 -

[Olivier Tilloy (osomon)]

Does Ubuntu Software still offer an update for firefox?

[Michelet (nicomich)]

Created attachment 9294284
Capture2022-09-12.png

No update offered anymore.

[Michelet (nicomich)]

I mean: for Firefox.

[Release-mgmt-account-bot (release-mgmt-account-bot)]

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

[Alan Jenkins (aj504)]

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

[Alan Jenkins (aj504)]

(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.

[Lissyx+mozillians (lissyx+mozillians)]

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

[Vishal Singh Panesar (vishal-panesar)]

[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

[Gwatson-r (gwatson-r)]

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

[Robert Mader (robert.posteo)]

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?

[Robert Mader (robert.posteo)]

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.

[Ttanasoaia (ttanasoaia)]

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

[W-jan-k (w-jan-k)]

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

[Release-mgmt-account-bot (release-mgmt-account-bot)]

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).

[Stransky (stransky)]

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

[corrado venturini (corradoventu)]

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'

[W-jan-k (w-jan-k)]

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

[Gunnar Hjalmarsson (gunnarhj)]

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.

[Marco Trevisan (Treviño) (3v1n0)]

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)]

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.

[Łukasz Zemczak (sil2100)]

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.

[Gunnar Hjalmarsson (gunnarhj)]

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.

[Lissyx+mozillians (lissyx+mozillians)]

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.

[Lissyx+mozillians (lissyx+mozillians)]

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

[Gunnar Hjalmarsson (gunnarhj)]

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

[Andreas Hasenack (ahasenack)]

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

[Gunnar Hjalmarsson (gunnarhj)]

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

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

[W-jan-k (w-jan-k)]

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

[Launchpad Janitor (janitor)]

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

[Timo Aaltonen (tjaalton)]

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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

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!

[Gunnar Hjalmarsson (gunnarhj)]

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.

[Norbert (asterix52)]

Firefox works fine with the new mutter version on lunar.

Thanks

[W-jan-k (w-jan-k)]

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

[W-jan-k (w-jan-k)]

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

[Angel D. Segarra (angel-segarra)]

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

[Gunnar Hjalmarsson (gunnarhj)]

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.

[Angel D. Segarra (angel-segarra)]

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

[W-jan-k (w-jan-k)]

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

[Launchpad Janitor (janitor)]

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

[Brian Murray (brian-murray)]

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.

[W-jan-k (w-jan-k)]

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

[W-jan-k (w-jan-k)]

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