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 removed: verification-needed verification-needed-lunar
** Tags added: verification-done verification-done-lunar

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1987976

Title:
  firefox black window on wayland

Status in Mozilla Firefox:
  Unknown
Status in Mutter:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Lunar:
  Fix Committed

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.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to