Hello errors.ubuntu.com, or anyone else affected, Accepted xwayland into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xwayland/2:22.1.1-1ubuntu0.16 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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: xwayland (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. 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 Released Status in xwayland source package in Jammy: Fix Committed Status in xwayland source package in Noble: Fix Committed Status in xwayland source package in Oracular: Fix Committed 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
