[Bug 2096653] Re: Xwayland raised SIGSEGV in drmFreeDevice from xwl_glamor_gbm_cleanup from xwl_glamor_gbm_init_egl

[Ubuntu Foundations Team Bug Bot]

The attachment "xwayland_24.1.4-3.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2096653

Title:
  Xwayland raised SIGSEGV in drmFreeDevice from xwl_glamor_gbm_cleanup
  from xwl_glamor_gbm_init_egl

Status in X.Org X server:
  New
Status in xwayland package in Ubuntu:
  Fix Committed
Status in xwayland source package in Jammy:
  In Progress
Status in xwayland source package in Noble:
  In Progress
Status in xwayland source package in Oracular:
  In Progress

Bug description:
  [ Impact ]

  After applying the patch for bug 2043517, it is now possible for Xwayland to end up in a situation where it frees memory twice and crashes.
  Prior to the patch, the code was still wrong but Xwayland got stuck waiting forever before it could reach the point where it double-frees, so the problem was not visible.

  Under normal operation, if Xwayland crashes then gnome-shell will recover by simply restarting it (printing "X Wayland crashed; attempting to recover" to the system journal).
  When instead gnome-shell is not started by systemd, and possibly when running other desktop environments, if Xwayland crashes then the whole desktop may quit.

  [ Test Plan ]

  It is unclear how to reproduce this bug.
  We will be monitoring errors.ubuntu.com for new errors submitted after the update is released to judge whether the bug is fixed.
  Instead, the test plan will only verify that Xwayland keeps working normally.

  1. Log-in to a GNOME Wayland session
  2. Run `glxgears`
  3. Verify that you did not receive a crash notification
  4. Verify that glxgears is showing

  [ Where problems could occur ]

  Xwayland is the compatibility layer for running X11 applications in a Wayland desktop. These are typically legacy applications, usually old Electron or Java based apps.
  If Xwayland is not working, those legacy applications will stop working, or at worst some desktops may crash or exit.

  [ Other Info ]

  The SRU for bug 2043517 targeting oracular was halted during phasing;
  this patch resolves that issue. But this bug applies to all the series
  where the patch was released, and indeed errors.ubuntu.com has
  received a crash from noble too (after phasing had already finished,
  so it did not halt the update)

  The Ubuntu Error Tracker has been receiving reports about a problem regarding xwayland.  This problem was most recently seen with package version 2:24.1.2-1ubuntu0.2, the problem page at https://errors.ubuntu.com/problem/aca5889551d3148812052f829ac9a979432a4a54 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/2096653/+subscriptions