[Impact]
Come to find out that the desktop's graphical-session.target is not working in Bionic nor in Ubuntu 17.10. The update-notifier-release check (.path and .service files) are part of that and subsequently are not working. These raise a dialog letting the user know of the availability of a new release of Ubuntu. They should be fixed for both releases.
[Test Case]
1) Run 'systemctl --user status update-notifier-release.path and observe that is dead
With the version of update-notifier from -proposed that service should be active. A complete test of the job involves:
1) Ensure /etc/update-manager/release-upgrades has Prompt=normal
2) Modify /usr/lib/systemd/user/update-notifier-release.service so that '-d' is passed to check-new-release-gtk (because bionic is still in development)
3) Run 'sudo touch /var/lib/ubuntu-release-upgrader/release-upgrade-available'
4) Observe a dialog regarding Ubuntu 18.04 being available
[Regression Potential]
The job is already broken and users won't get the check-new-release-gtk dialog about the next release. Its possible that since we are switching the .path job from graphical-session.target that check-new-release-gtk will be called when a user is not logged in and it will crash. However, that seems like an acceptable risk.
[Impact] session. target is not working in Bionic nor in Ubuntu 17.10. The update- notifier- release check (.path and .service files) are part of that and subsequently are not working. These raise a dialog letting the user know of the availability of a new release of Ubuntu. They should be fixed for both releases.
Come to find out that the desktop's graphical-
[Test Case] notifier- release. path and observe that is dead
1) Run 'systemctl --user status update-
With the version of update-notifier from -proposed that service should be active. A complete test of the job involves:
1) Ensure /etc/update- manager/ release- upgrades has Prompt=normal systemd/ user/update- notifier- release. service so that '-d' is passed to check-new- release- gtk (because bionic is still in development) ubuntu- release- upgrader/ release- upgrade- available'
2) Modify /usr/lib/
3) Run 'sudo touch /var/lib/
4) Observe a dialog regarding Ubuntu 18.04 being available
[Regression Potential] release- gtk dialog about the next release. Its possible that since we are switching the .path job from graphical- session. target that check-new- release- gtk will be called when a user is not logged in and it will crash. However, that seems like an acceptable risk.
The job is already broken and users won't get the check-new-