All autopkgtests for the newly accepted gtk4 (4.14.5+ds-0ubuntu0.3) for noble have finished running. The following regressions have been reported in tests triggered by the package:
gsequencer/6.5.2-1build3 (arm64) gtk4/4.14.5+ds-0ubuntu0.3 (ppc64el) libreoffice/4:24.2.7-0ubuntu0.24.04.4 (amd64, arm64, ppc64el) libspelling/unknown (ppc64el) mutter/unknown (ppc64el) nfoview/unknown (ppc64el) rust-gdk4-wayland-sys/unknown (ppc64el) rust-gtk4-sys/unknown (ppc64el) 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/noble/update_excuses.html#gtk4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Debcrafters packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2119005 Title: Accessibility groups aren't honored in Noble Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Noble: Fix Committed Bug description: [ Impact ] In Noble, after the last Gtk4 update, some accessibility details have stopped working. Specifically, when a container is marked as a group and an inner element gets the focus, now the screen reader only reads the label of the focused element. Before, if the focus went from outside the group to inside, the label of the group element was read before, thus helping to get context. The bug is due to the change of the ATSPI_ROLE value for GTK_ACCESSIBLE_ROLE_GROUP, from PANEL to GROUPING. The version of the `orca` screen reader in Noble does not support ATSPI_ROLE_GROUPING, so revert back to ATSPI_ROLE_PANEL. This bug affects all those users that rely on a screen reader. The screen reader will not give enough context to know where the focus is, which can make more complex for them to navigate and use the computer. [ Test plan ] * Enable the screen reader * Open Gnome Control Center * Go to System -> Users * Using the keyboard TAB and cursors, go to the "Unlock" button * If the bug has been fixed, the screen reader should say first "Some options are locked" and only then "Unlock pushbutton". If the bug is still there, only "Unlock pushbutton" will be read. [ Where problems could occur ] The change only affects users that rely on screen readers. Regressions would be observed in the screen reader announcements of nested UI elements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2119005/+subscriptions -- Mailing list: https://launchpad.net/~debcrafters-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~debcrafters-packages More help : https://help.launchpad.net/ListHelp
