done ** Description changed:
* Impact On some configs registration to the geoclue service might fail because the agent is started too late/after the registration timeout * Test case - - log into an Ubuntu/GNOME session and check that the geolocation - feature is working (used to adjust the timezone for example) + log into an Ubuntu/GNOME session and check that the geolocation feature is working (used to adjust the timezone for example) + - log into your Ubuntu/GNOME session + - go to gnome-control-center, enable the geolocation and automatic timezone adjustement options + - reboot to gdm (without login in) + - go to a vt + - change the timezone to be not matching the actual location + - go back to gdm and log in + + -> verify that the timezone get adjusted automatically to match your + real location one or from the original report - - log into xfce with redshift and check if it's working + - install xubuntu + - install redshift and start it/configure it to change your screen profile/colors at night + - log into your xfce session at a time configured to color the screen red + + -> the screen color should change according to the calibration * Regression potential The change is only to increase a timeout delay ----------------------- Due to an upstream bug (https://gitlab.freedesktop.org/geoclue/geoclue/issues/84) GeoClue times out upon startup and certain applications (such as Redshift) do not function as intended. This has already been fixed upstream (version 2.5.0) and that version is available in Debian. Please pull the latest Debian version to fix this bug. ** Changed in: geoclue-2.0 (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1799339 Title: GeoClue times out on start Status in geoclue-2.0 package in Ubuntu: Fix Committed Status in geoclue-2.0 package in Debian: Fix Released Bug description: * Impact On some configs registration to the geoclue service might fail because the agent is started too late/after the registration timeout * Test case log into an Ubuntu/GNOME session and check that the geolocation feature is working (used to adjust the timezone for example) - log into your Ubuntu/GNOME session - go to gnome-control-center, enable the geolocation and automatic timezone adjustement options - reboot to gdm (without login in) - go to a vt - change the timezone to be not matching the actual location - go back to gdm and log in -> verify that the timezone get adjusted automatically to match your real location one or from the original report - install xubuntu - install redshift and start it/configure it to change your screen profile/colors at night - log into your xfce session at a time configured to color the screen red -> the screen color should change according to the calibration * Regression potential The change is only to increase a timeout delay ----------------------- Due to an upstream bug (https://gitlab.freedesktop.org/geoclue/geoclue/issues/84) GeoClue times out upon startup and certain applications (such as Redshift) do not function as intended. This has already been fixed upstream (version 2.5.0) and that version is available in Debian. Please pull the latest Debian version to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1799339/+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
