Hello Anadon, or anyone else affected, Accepted gnome-shell into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/46.0-0ubuntu6~24.04.8 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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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. ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2039340 Title: gnome-shell crashes on startup with SIGSEGV in __GI_getenv("EXPAT_ACCOUNTING_DEBUG") from getDebugLevel() from parserInit() Status in Mutter: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Noble: Fix Committed Bug description: [ Impact ] gnome-shell may crash on startup due to multiple threads writing and reading environment variables. gnome-shell adds variables like DISPLAY, XAUTHORITY, WAYLAND_DISPLAY to its own environment. However it might do so while libraries running in other threads are trying to read environment variables that may affect their behaviour. If a call to `getenv` is interrupted by a call to `setenv` that causes re-allocation of memory, it will trigger a crash. To mitigate the issue, we avoid starting the fontconfig thread right before setting the environment variables. [ Test Plan ] There are no reproducer steps that trigger the crash reliably enough to be verified. Instead, we are going to verify that the patch does not introduce regressions, and will verify the effectiveness of the fix by monitoring errors.ubuntu.com after the update has landed. 1. Install the gnome-shell update 2. Reboot 3. Verify that the log-in screen loaded correctly 4. Log-in 5. Verify that the desktop loaded correctly 6. Verify that the font rendering quality is not degraded [ Where problems could occur ] The patch delays the disablement of text mipmapping to the first time a font is rendered, instead of doing so on startup. A mistake in the patch could thus affect font rendering. The test plan asks to verify that that is not the case. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2039340/+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
