All autopkgtests for the newly accepted gnome-settings-daemon (43.0-1ubuntu1.1) for kinetic have finished running. The following regressions have been reported in tests triggered by the package:
mutter/43.0-1ubuntu4 (amd64, arm64) 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/kinetic/update_excuses.html#gnome-settings-daemon [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2011770 Title: [gsd-rfkill] WwanEnabled never get synced Status in OEM Priority Project: Triaged Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Jammy: Fix Committed Status in gnome-settings-daemon source package in Kinetic: Fix Committed Bug description: [ Impact ] * Sometimes on devices with WWAN card, whenever user presses the wireless function key (Fn+F8) or turn on the airplane mode radio button in Settings, the airplane mode will not be enabled, and the airplane mode icon is not shown in the status bar. * There is a unmerged upstream merge request that delivers the fix: https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/merge_requests/310 It works perfectly well on several Lenovo laptops with WWAN cards. The root causes is that the value of "WwanEnabled" under "org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should listen to "g-properties-changed" instead of "g-signal" now. [ Test Plan ] 1. Find a machine which has WWAN card. 2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not use rfkill to unblock the WWAN, and reboot. 3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio button in Settings. 4. The airplane mode should be enabled, but actually not. [ Where problems could occur ] * When user is using a very low version network-manager (< 1.20) that still broadcasting DBUS "PropertiesChanged" events on "g-signal" instead of the concurrent "g-properties-changed", the airplane mode will sometimes not be able to enable. [1]: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853 [2]: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f [ Other Info ] 1. About Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Kernel: 6.1.0-1007-oem 2. The version of packages: gnome-settings-daemon: Installed: 42.1-1ubuntu2.1 network-manager: Installed: 1.36.6-0ubuntu2 3. Expect: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and manager->wwan_enabled is set to the correct value. 4. Actual: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the initial value of manager->wwan_enabled is true, it will never be able to switch to airplane mode. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+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
