[Touch-packages] [Bug 2077290] Re: [SRU] GLArea transparency broken
Couldn't work out why they aren't updating automatically but manually installing the .debs shows the issue fixed, thanks! ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2077290 Title: [SRU] GLArea transparency broken Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Noble: Fix Committed Bug description: [Impact] In Noble a GtkGlArea widget with transparency doesn't show the GTK widgets beneath it correctly. This was a regression fixed in https://gitlab.gnome.org/GNOME/gtk/-/commit/6754765a5a849ecbdd5c5fa60b5a6f80a968133e (released in 3.24.42). [Test Case] Run gdkgears: $ apt source gtk+3.0 $ cd src/gtk+3.0-3.24.41 $ meson _build $ ninja -C _build $ ./_build/tests/gdkgears Click "Alpha" checkbox. Expected results: Gears are shown with Gtk window background behind them. Observed results: Uninitialized buffer is shown behind gears (commonly looks like repeated contents of old window frames). [Regression potential] Issues can be expected in GTK3 widgets with a transparent background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2077290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2077290] Re: [SRU] GLArea transparency broken
Attempted to verify this today but 3.24.41-4ubuntu1.2 is not downloading from proposed - is it held due to the autopkgtest results above? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2077290 Title: [SRU] GLArea transparency broken Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Noble: Fix Committed Bug description: [Impact] In Noble a GtkGlArea widget with transparency doesn't show the GTK widgets beneath it correctly. This was a regression fixed in https://gitlab.gnome.org/GNOME/gtk/-/commit/6754765a5a849ecbdd5c5fa60b5a6f80a968133e (released in 3.24.42). [Test Case] Run gdkgears: $ apt source gtk+3.0 $ cd src/gtk+3.0-3.24.41 $ meson _build $ ninja -C _build $ ./_build/tests/gdkgears Click "Alpha" checkbox. Expected results: Gears are shown with Gtk window background behind them. Observed results: Uninitialized buffer is shown behind gears (commonly looks like repeated contents of old window frames). [Regression potential] Issues can be expected in GTK3 widgets with a transparent background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2077290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2077290] [NEW] GLArea transparency broken
Public bug reported: In Noble a GtkGlArea widget with transparency doesn't show the GTK widgets beneath it correctly. This was a regression fixed in https://gitlab.gnome.org/GNOME/gtk/-/commit/6754765a5a849ecbdd5c5fa60b5a6f80a968133e (released in 3.24.42). Test Case: Run gdkgears: $ apt source gtk+3.0 $ cd src/gtk+3.0-3.24.41 $ meson _build $ ninja -C _build $ ./_build/tests/gdkgears Click "Alpha" checkbox. Expected results: Gears are shown with Gtk window background behind them. Observed results: Uninitialized buffer is shown behind gears (commonly looks like repeated contents of old window frames). ** Affects: gtk+3.0 (Ubuntu) Importance: High Status: Fix Released ** Affects: gtk+3.0 (Ubuntu Noble) Importance: High Status: Triaged ** Tags: noble ** Also affects: gtk+3.0 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released ** Changed in: gtk+3.0 (Ubuntu Noble) Status: New => Triaged ** Changed in: gtk+3.0 (Ubuntu Noble) Importance: Undecided => High ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => High ** Description changed: In Noble a GtkGlArea widget with transparency doesn't show the GTK widgets beneath it correctly. This was a regression fixed in - https://gitlab.gnome.org/GNOME/gtk/-/commit/6754765a5a849ecbdd5c5fa60b5a6f80a968133e. + https://gitlab.gnome.org/GNOME/gtk/-/commit/6754765a5a849ecbdd5c5fa60b5a6f80a968133e + (released in 3.24.42). Test Case: Run gdkgears: $ apt source gtk+3.0 $ cd src/gtk+3.0-3.24.41 $ meson _build $ ninja -C _build $ ./_build/tests/gdkgears Click "Alpha" checkbox. Expected results: Gears are shown with Gtk window background behind them. Observed results: Uninitialized buffer is shown behind gears (commonly looks like repeated contents of old window frames). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2077290 Title: GLArea transparency broken Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Noble: Triaged Bug description: In Noble a GtkGlArea widget with transparency doesn't show the GTK widgets beneath it correctly. This was a regression fixed in https://gitlab.gnome.org/GNOME/gtk/-/commit/6754765a5a849ecbdd5c5fa60b5a6f80a968133e (released in 3.24.42). Test Case: Run gdkgears: $ apt source gtk+3.0 $ cd src/gtk+3.0-3.24.41 $ meson _build $ ninja -C _build $ ./_build/tests/gdkgears Click "Alpha" checkbox. Expected results: Gears are shown with Gtk window background behind them. Observed results: Uninitialized buffer is shown behind gears (commonly looks like repeated contents of old window frames). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2077290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998267] Re: glib not aware of snap confinement
Correct, this fix is valuable for core22, so kinetic was skipped. There should be no issues for anyone updating from jammy to kinetic. Though this will affect core20, we expect most snaps to be using core22 so no plan to backport it to focal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Released Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998267] Re: glib not aware of snap confinement
Yes, these specific steps performed in a core desktop VM. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998267] Re: glib not aware of snap confinement
I tested a standard jammy desktop in a VM by running various apps including calculator to confirm they were still working (i.e. looking for regressions). I tested the core desktop behaviour by building the core22-desktop snap from https://github.com/canonical/core-base-desktop/ (locally modified to use updates) and then installing that into a core desktop. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998267] Re: glib not aware of snap confinement
I've looked at the autopkgtests and the failures don't seem to be related to this change. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998267] Re: glib not aware of snap confinement
Tested glib2.0 2.72.4-0ubuntu2 in a jammy VM and working. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998267] Re: glib not aware of snap confinement
** Changed in: glib2.0 (Ubuntu Kinetic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: New Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998267] Re: glib not aware of snap confinement
** Description changed: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] + + (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: New Status in glib2.0 source package in Kinetic: New Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998267] [NEW] glib not aware of snap confinement
Public bug reported: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. ** Affects: glib2.0 (Ubuntu) Importance: High Assignee: Robert Ancell (robert-ancell) Status: New ** Affects: glib2.0 (Ubuntu Jammy) Importance: High Assignee: Robert Ancell (robert-ancell) Status: New ** Affects: glib2.0 (Ubuntu Kinetic) Importance: High Assignee: Robert Ancell (robert-ancell) Status: New ** Affects: glib2.0 (Ubuntu Lunar) Importance: High Assignee: Robert Ancell (robert-ancell) Status: New ** Also affects: glib2.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: glib2.0 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: glib2.0 (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: New Status in glib2.0 source package in Jammy: New Status in glib2.0 source package in Kinetic: New Status in glib2.0 source package in Lunar: New Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998267] Re: glib not aware of snap confinement
Targeting 22.04 so this can become part of the core22 snap fixing the issue for most modern snaps. ** Changed in: glib2.0 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: glib2.0 (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: glib2.0 (Ubuntu Lunar) Importance: Undecided => High ** Changed in: glib2.0 (Ubuntu Jammy) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: glib2.0 (Ubuntu Kinetic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: glib2.0 (Ubuntu Lunar) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: New Status in glib2.0 source package in Jammy: New Status in glib2.0 source package in Kinetic: New Status in glib2.0 source package in Lunar: New Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()
Investigated this, it is due to the theming code failing to get a settings object, probably due to the shell not running at the time. The GTK functions that return the settings object are allowed to return NULL, and this case was not being handled in GTK. The attached patch contains three fixes in GTK to handle these cases. These cases were found by forcing the settings object to be NULL and then running a test program and fixing the segfaults. ** Patch added: "fix-no-shell.patch" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+attachment/5629117/+files/fix-no-shell.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1842439 Title: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value() Status in apport package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in apport source package in Focal: Triaged Status in gtk+3.0 source package in Focal: Confirmed Bug description: Steps to reproduce -- 1. Use GNOME with GNOME shell 2. killall -11 gnome-shell Suspicious Apport log: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Error tracker - https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5 https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22 Original report --- Session suddenly stopped and came back to login screen, all opened windows lost. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: apport-gtk 2.20.11-0ubuntu7 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashReports: 640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash 640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 16:20:13 2019 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2018-06-16 (443 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 SegvAnalysis: Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax PC (0x7f532548f8c4) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990448] Re: Show Ubuntu Pro settings
This bug is a bit of a placeholder at the moment - we'll get this landed into kinetic first and then update this to SRU the change back to the older releases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1990448 Title: Show Ubuntu Pro settings Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Jammy: Incomplete Status in software-properties source package in Kinetic: New Bug description: Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead of just Livepatch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990448] Re: Show Ubuntu Pro settings
** Also affects: software-properties (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1990448 Title: Show Ubuntu Pro settings Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Jammy: New Status in software-properties source package in Kinetic: New Bug description: Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead of just Livepatch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990448] [NEW] Show Ubuntu Pro settings
Public bug reported: Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead of just Livepatch. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1990448 Title: Show Ubuntu Pro settings Status in software-properties package in Ubuntu: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Jammy: New Status in software-properties source package in Kinetic: New Bug description: Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead of just Livepatch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981042] Re: /etc/localtime symlink not correctly handled when using /etc/writable
Installed systemd 249.11-0ubuntu3.6 on a jammy VM and confirmed everything working as expected, thanks! ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981042 Title: /etc/localtime symlink not correctly handled when using /etc/writable Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink to /etc/writable/localtime (which in itself if a symlink). Systemd doesn't handle this correctly when doing firstboot or using inotify to watch for changes to localtime. [Test Plan] This is somewhat hard to test, the following situations need to be reproduced: - On firstboot the timezone link will not be read correctly, it will with this change. - Starting a timer unit and then changing timezone will cause it not to occur at the correct time. [Where problems could occur] This could potentially break other users of localtime, however the change is similar to existing changes which have been in Ubuntu's version of systemd for some time. The change detects the /etc/writable case and if not should have the same existing behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981042] Re: /etc/localtime symlink not correctly handled when using /etc/writable
** Description changed: - When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink - to /etc/writable/localtime (which in itself if a symlink). Systemd - doesn't handle this correctly when doing firstboot or using inotify to - watch for changed to localtime. + [Impact] + When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink to /etc/writable/localtime (which in itself if a symlink). Systemd doesn't handle this correctly when doing firstboot or using inotify to watch for changes to localtime. + + [Test Plan] + This is somewhat hard to test, the following situations need to be reproduced: + - On firstboot the timezone link will not be read correctly, it will with this change. + - Starting a timer unit and then changing timezone will cause it not to occur at the correct time. + + [Where problems could occur] + This could potentially break other users of localtime, however the change is similar to existing changes which have been in Ubuntu's version of systemd for some time. The change detects the /etc/writable case and if not should have the same existing behaviour. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981042 Title: /etc/localtime symlink not correctly handled when using /etc/writable Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: New Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink to /etc/writable/localtime (which in itself if a symlink). Systemd doesn't handle this correctly when doing firstboot or using inotify to watch for changes to localtime. [Test Plan] This is somewhat hard to test, the following situations need to be reproduced: - On firstboot the timezone link will not be read correctly, it will with this change. - Starting a timer unit and then changing timezone will cause it not to occur at the correct time. [Where problems could occur] This could potentially break other users of localtime, however the change is similar to existing changes which have been in Ubuntu's version of systemd for some time. The change detects the /etc/writable case and if not should have the same existing behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981042] [NEW] /etc/localtime symlink not correctly handled when using /etc/writable
Public bug reported: When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink to /etc/writable/localtime (which in itself if a symlink). Systemd doesn't handle this correctly when doing firstboot or using inotify to watch for changed to localtime. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981042 Title: /etc/localtime symlink not correctly handled when using /etc/writable Status in systemd package in Ubuntu: New Bug description: When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink to /etc/writable/localtime (which in itself if a symlink). Systemd doesn't handle this correctly when doing firstboot or using inotify to watch for changed to localtime. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978042] Re: adduser doesn't support extrausers for group management
Ugh, turns out I don't need to SRU these back to focal - we will be
using Ubuntu Core 22 which already includes these changes. Sorry for the
noise.
** Changed in: shadow (Ubuntu Focal)
Status: In Progress => Won't Fix
** Changed in: adduser (Ubuntu Focal)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launchpad.net/bugs/1978042
Title:
adduser doesn't support extrausers for group management
Status in adduser package in Ubuntu:
Fix Released
Status in shadow package in Ubuntu:
Fix Released
Status in adduser source package in Focal:
Won't Fix
Status in shadow source package in Focal:
Won't Fix
Status in adduser source package in Impish:
Fix Released
Status in shadow source package in Impish:
Fix Released
Status in adduser source package in Jammy:
Fix Released
Status in shadow source package in Jammy:
Fix Released
Status in adduser source package in Kinetic:
Fix Released
Status in shadow source package in Kinetic:
Fix Released
Bug description:
[Impact]
When using adduser --extrausers on Ubuntu Core the command attempts to
use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
following commands will fail:
$ adduser --extrausers user group
$ adduser --extrausers --ingroup group user
[Test Plan]
1. Install libnss-extrausers
2. Edit /etc/nsswitch.conf to use extrausers as shown in
/usr/share/doc/libnss-extrausers/README
3. Add a new group:
$ sudo adduser --extrausers --group test-group
4. Create a new user with this group:
$ sudo adduser --extrausers --ingroup test-group test-user1
5. Create a new user and add them to this group:
$ sudo adduser --extrausers test-user2
$ sudo adduser --extrausers test-user2 test-group
Expected result:
Two new users (test-user1 and test-user2) are successfully added to the
system and are entered in /var/lib/extrausers/{passwd,shadow}.
A new group (test-group) is successfully added to /var/lib/extrausers/group
and contains the new users.
[Where problems could occur]
Existing users of adduser and gpasswd that don't use --extrausers are
unlikely to hit any issues, as their codepath is unchanged.
Existing users that use --extrausers will have a behavior change, but the
existing behavior was to fail so this is unlikely to introduce any new issues.
There is the risk of introducing new bugs by this change, but it has used
since impish without any issues being detected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1978042/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978042] Re: adduser doesn't support extrausers for group management
** Description changed:
[Impact]
When using adduser --extrausers on Ubuntu Core the command attempts to
use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
following commands will fail:
$ adduser --extrausers user group
$ adduser --extrausers --ingroup group user
[Test Plan]
1. Install libnss-extrausers
- 2. Add a new group:
+ 2. Edit /etc/nsswitch.conf to use extrausers as shown in
/usr/share/doc/libnss-extrausers/README
+ 3. Add a new group:
$ sudo adduser --extrausers --group test-group
- 3. Create a new user with this group:
+ 4. Create a new user with this group:
$ sudo adduser --extrausers --ingroup test-group test-user1
- 4. Create a new user and add them to this group:
+ 5. Create a new user and add them to this group:
$ sudo adduser --extrausers test-user2
$ sudo adduser --extrausers test-user2 test-group
Expected result:
Two new users (test-user1 and test-user2) are successfully added to the
system and are entered in /var/lib/extrausers/{passwd,shadow}.
A new group (test-group) is successfully added to /var/lib/extrausers/group
and contains the new users.
[Where problems could occur]
Existing users of adduser and gpasswd that don't use --extrausers are
unlikely to hit any issues, as their codepath is unchanged.
Existing users that use --extrausers will have a behavior change, but the
existing behavior was to fail so this is unlikely to introduce any new issues.
There is the risk of introducing new bugs by this change, but it has used
since impish without any issues being detected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launchpad.net/bugs/1978042
Title:
adduser doesn't support extrausers for group management
Status in adduser package in Ubuntu:
Fix Released
Status in shadow package in Ubuntu:
Fix Released
Status in adduser source package in Focal:
In Progress
Status in shadow source package in Focal:
In Progress
Status in adduser source package in Impish:
Fix Released
Status in shadow source package in Impish:
Fix Released
Status in adduser source package in Jammy:
Fix Released
Status in shadow source package in Jammy:
Fix Released
Status in adduser source package in Kinetic:
Fix Released
Status in shadow source package in Kinetic:
Fix Released
Bug description:
[Impact]
When using adduser --extrausers on Ubuntu Core the command attempts to
use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
following commands will fail:
$ adduser --extrausers user group
$ adduser --extrausers --ingroup group user
[Test Plan]
1. Install libnss-extrausers
2. Edit /etc/nsswitch.conf to use extrausers as shown in
/usr/share/doc/libnss-extrausers/README
3. Add a new group:
$ sudo adduser --extrausers --group test-group
4. Create a new user with this group:
$ sudo adduser --extrausers --ingroup test-group test-user1
5. Create a new user and add them to this group:
$ sudo adduser --extrausers test-user2
$ sudo adduser --extrausers test-user2 test-group
Expected result:
Two new users (test-user1 and test-user2) are successfully added to the
system and are entered in /var/lib/extrausers/{passwd,shadow}.
A new group (test-group) is successfully added to /var/lib/extrausers/group
and contains the new users.
[Where problems could occur]
Existing users of adduser and gpasswd that don't use --extrausers are
unlikely to hit any issues, as their codepath is unchanged.
Existing users that use --extrausers will have a behavior change, but the
existing behavior was to fail so this is unlikely to introduce any new issues.
There is the risk of introducing new bugs by this change, but it has used
since impish without any issues being detected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1978042/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978042] Re: adduser doesn't support extrausers for group management
I realized after generating the debdiffs that I didn't have the bug
number in the changelog - this is fixed in the version uploaded to
focal.
** Changed in: adduser (Ubuntu Focal)
Status: New => In Progress
** Changed in: shadow (Ubuntu Focal)
Status: New => In Progress
** Description changed:
[Impact]
When using adduser --extrausers on Ubuntu Core the command attempts to
use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
following commands will fail:
$ adduser --extrausers user group
$ adduser --extrausers --ingroup group user
[Test Plan]
1. Install libnss-extrausers
2. Add a new group:
$ sudo adduser --extrausers --group test-group
3. Create a new user with this group:
- $ adduser --extrausers --ingroup test-group test-user1
+ $ sudo adduser --extrausers --ingroup test-group test-user1
4. Create a new user and add them to this group:
- $ adduser --extrausers test-user2
- $ adduser --extrausers test-user2 test-group
+ $ sudo adduser --extrausers test-user2
+ $ sudo adduser --extrausers test-user2 test-group
Expected result:
Two new users (test-user1 and test-user2) are successfully added to the
system and are entered in /var/lib/extrausers/{passwd,shadow}.
A new group (test-group) is successfully added to /var/lib/extrausers/group
and contains the new users.
[Where problems could occur]
Existing users of adduser and gpasswd that don't use --extrausers are
unlikely to hit any issues, as their codepath is unchanged.
- Existing users that use --extrausers will have a behavior change, but the
existing behavior was to fail so this is unlikely to introduce any new issues.
+ Existing users that use --extrausers will have a behavior change, but the
existing behavior was to fail so this is unlikely to introduce any new issues.
There is the risk of introducing new bugs by this change, but it has used
since impish without any issues being detected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launchpad.net/bugs/1978042
Title:
adduser doesn't support extrausers for group management
Status in adduser package in Ubuntu:
Fix Released
Status in shadow package in Ubuntu:
Fix Released
Status in adduser source package in Focal:
In Progress
Status in shadow source package in Focal:
In Progress
Status in adduser source package in Impish:
Fix Released
Status in shadow source package in Impish:
Fix Released
Status in adduser source package in Jammy:
Fix Released
Status in shadow source package in Jammy:
Fix Released
Status in adduser source package in Kinetic:
Fix Released
Status in shadow source package in Kinetic:
Fix Released
Bug description:
[Impact]
When using adduser --extrausers on Ubuntu Core the command attempts to
use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
following commands will fail:
$ adduser --extrausers user group
$ adduser --extrausers --ingroup group user
[Test Plan]
1. Install libnss-extrausers
2. Add a new group:
$ sudo adduser --extrausers --group test-group
3. Create a new user with this group:
$ sudo adduser --extrausers --ingroup test-group test-user1
4. Create a new user and add them to this group:
$ sudo adduser --extrausers test-user2
$ sudo adduser --extrausers test-user2 test-group
Expected result:
Two new users (test-user1 and test-user2) are successfully added to the
system and are entered in /var/lib/extrausers/{passwd,shadow}.
A new group (test-group) is successfully added to /var/lib/extrausers/group
and contains the new users.
[Where problems could occur]
Existing users of adduser and gpasswd that don't use --extrausers are
unlikely to hit any issues, as their codepath is unchanged.
Existing users that use --extrausers will have a behavior change, but the
existing behavior was to fail so this is unlikely to introduce any new issues.
There is the risk of introducing new bugs by this change, but it has used
since impish without any issues being detected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1978042/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978042] Re: adduser doesn't support extrausers for group management
** Patch added: "adduser.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/adduser/+bug/1978042/+attachment/5595790/+files/adduser.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launchpad.net/bugs/1978042
Title:
adduser doesn't support extrausers for group management
Status in adduser package in Ubuntu:
Fix Released
Status in shadow package in Ubuntu:
Fix Released
Status in adduser source package in Focal:
New
Status in shadow source package in Focal:
New
Status in adduser source package in Impish:
Fix Released
Status in shadow source package in Impish:
Fix Released
Status in adduser source package in Jammy:
Fix Released
Status in shadow source package in Jammy:
Fix Released
Status in adduser source package in Kinetic:
Fix Released
Status in shadow source package in Kinetic:
Fix Released
Bug description:
[Impact]
When using adduser --extrausers on Ubuntu Core the command attempts to
use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
following commands will fail:
$ adduser --extrausers user group
$ adduser --extrausers --ingroup group user
[Test Plan]
1. Install libnss-extrausers
2. Add a new group:
$ sudo adduser --extrausers --group test-group
3. Create a new user with this group:
$ adduser --extrausers --ingroup test-group test-user1
4. Create a new user and add them to this group:
$ adduser --extrausers test-user2
$ adduser --extrausers test-user2 test-group
Expected result:
Two new users (test-user1 and test-user2) are successfully added to the
system and are entered in /var/lib/extrausers/{passwd,shadow}.
A new group (test-group) is successfully added to /var/lib/extrausers/group
and contains the new users.
[Where problems could occur]
Existing users of adduser and gpasswd that don't use --extrausers are
unlikely to hit any issues, as their codepath is unchanged.
Existing users that use --extrausers will have a behavior change, but the
existing behavior was to fail so this is unlikely to introduce any new issues.
There is the risk of introducing new bugs by this change, but it has used
since impish without any issues being detected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1978042/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978042] Re: adduser doesn't support extrausers for group management
** Patch added: "shadow.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/adduser/+bug/1978042/+attachment/5595787/+files/shadow.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launchpad.net/bugs/1978042
Title:
adduser doesn't support extrausers for group management
Status in adduser package in Ubuntu:
Fix Released
Status in shadow package in Ubuntu:
Fix Released
Status in adduser source package in Focal:
New
Status in shadow source package in Focal:
New
Status in adduser source package in Impish:
Fix Released
Status in shadow source package in Impish:
Fix Released
Status in adduser source package in Jammy:
Fix Released
Status in shadow source package in Jammy:
Fix Released
Status in adduser source package in Kinetic:
Fix Released
Status in shadow source package in Kinetic:
Fix Released
Bug description:
[Impact]
When using adduser --extrausers on Ubuntu Core the command attempts to
use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
following commands will fail:
$ adduser --extrausers user group
$ adduser --extrausers --ingroup group user
[Test Plan]
1. Install libnss-extrausers
2. Add a new group:
$ sudo adduser --extrausers --group test-group
3. Create a new user with this group:
$ adduser --extrausers --ingroup test-group test-user1
4. Create a new user and add them to this group:
$ adduser --extrausers test-user2
$ adduser --extrausers test-user2 test-group
Expected result:
Two new users (test-user1 and test-user2) are successfully added to the
system and are entered in /var/lib/extrausers/{passwd,shadow}.
A new group (test-group) is successfully added to /var/lib/extrausers/group
and contains the new users.
[Where problems could occur]
Existing users of adduser and gpasswd that don't use --extrausers are
unlikely to hit any issues, as their codepath is unchanged.
Existing users that use --extrausers will have a behavior change, but the
existing behavior was to fail so this is unlikely to introduce any new issues.
There is the risk of introducing new bugs by this change, but it has used
since impish without any issues being detected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1978042/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978042] Re: adduser doesn't support extrausers for group management
LP: #195375 adds extrausers groups support to the usermod command, this
SRU adds support to gpasswd (which is used by useradd).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launchpad.net/bugs/1978042
Title:
adduser doesn't support extrausers for group management
Status in adduser package in Ubuntu:
Fix Released
Status in shadow package in Ubuntu:
Fix Released
Status in adduser source package in Focal:
New
Status in shadow source package in Focal:
New
Status in adduser source package in Impish:
Fix Released
Status in shadow source package in Impish:
Fix Released
Status in adduser source package in Jammy:
Fix Released
Status in shadow source package in Jammy:
Fix Released
Status in adduser source package in Kinetic:
Fix Released
Status in shadow source package in Kinetic:
Fix Released
Bug description:
[Impact]
When using adduser --extrausers on Ubuntu Core the command attempts to
use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
following commands will fail:
$ adduser --extrausers user group
$ adduser --extrausers --ingroup group user
[Test Plan]
1. Install libnss-extrausers
2. Add a new group:
$ sudo adduser --extrausers --group test-group
3. Create a new user with this group:
$ adduser --extrausers --ingroup test-group test-user1
4. Create a new user and add them to this group:
$ adduser --extrausers test-user2
$ adduser --extrausers test-user2 test-group
Expected result:
Two new users (test-user1 and test-user2) are successfully added to the
system and are entered in /var/lib/extrausers/{passwd,shadow}.
A new group (test-group) is successfully added to /var/lib/extrausers/group
and contains the new users.
[Where problems could occur]
Existing users of adduser and gpasswd that don't use --extrausers are
unlikely to hit any issues, as their codepath is unchanged.
Existing users that use --extrausers will have a behavior change, but the
existing behavior was to fail so this is unlikely to introduce any new issues.
There is the risk of introducing new bugs by this change, but it has used
since impish without any issues being detected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1978042/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978042] [NEW] adduser doesn't support extrausers for group management
Public bug reported:
[Impact]
When using adduser --extrausers on Ubuntu Core the command attempts to
use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
following commands will fail:
$ adduser --extrausers user group
$ adduser --extrausers --ingroup group user
[Test Plan]
1. Install libnss-extrausers
2. Add a new group:
$ sudo adduser --extrausers --group test-group
3. Create a new user with this group:
$ adduser --extrausers --ingroup test-group test-user1
4. Create a new user and add them to this group:
$ adduser --extrausers test-user2
$ adduser --extrausers test-user2 test-group
Expected result:
Two new users (test-user1 and test-user2) are successfully added to the system
and are entered in /var/lib/extrausers/{passwd,shadow}.
A new group (test-group) is successfully added to /var/lib/extrausers/group and
contains the new users.
[Where problems could occur]
Existing users of adduser and gpasswd that don't use --extrausers are unlikely
to hit any issues, as their codepath is unchanged.
Existing users that use --extrausers will have a behavior change, but the
existing behavior was to fail so this is unlikely to introduce any new issues.
There is the risk of introducing new bugs by this change, but it has used since
impish without any issues being detected.
** Affects: adduser (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: shadow (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: adduser (Ubuntu Focal)
Importance: Medium
Status: New
** Affects: shadow (Ubuntu Focal)
Importance: Medium
Status: New
** Affects: adduser (Ubuntu Impish)
Importance: Undecided
Status: Fix Released
** Affects: shadow (Ubuntu Impish)
Importance: Undecided
Status: Fix Released
** Affects: adduser (Ubuntu Jammy)
Importance: Undecided
Status: Fix Released
** Affects: shadow (Ubuntu Jammy)
Importance: Undecided
Status: Fix Released
** Affects: adduser (Ubuntu Kinetic)
Importance: Undecided
Status: Fix Released
** Affects: shadow (Ubuntu Kinetic)
Importance: Undecided
Status: Fix Released
** Also affects: adduser (Ubuntu)
Importance: Undecided
Status: New
** Also affects: adduser (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: shadow (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: adduser (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: shadow (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: adduser (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: shadow (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: adduser (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: shadow (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: adduser (Ubuntu Impish)
Status: New => Fix Released
** Changed in: adduser (Ubuntu Jammy)
Status: New => Fix Released
** Changed in: adduser (Ubuntu Kinetic)
Status: New => Fix Released
** Changed in: shadow (Ubuntu Impish)
Status: New => Fix Released
** Changed in: shadow (Ubuntu Jammy)
Status: New => Fix Released
** Changed in: shadow (Ubuntu Kinetic)
Status: New => Fix Released
** Changed in: shadow (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: adduser (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1978042
Title:
adduser doesn't support extrausers for group management
Status in adduser package in Ubuntu:
Fix Released
Status in shadow package in Ubuntu:
Fix Released
Status in adduser source package in Focal:
New
Status in shadow source package in Focal:
New
Status in adduser source package in Impish:
Fix Released
Status in shadow source package in Impish:
Fix Released
Status in adduser source package in Jammy:
Fix Released
Status in shadow source package in Jammy:
Fix Released
Status in adduser source package in Kinetic:
Fix Released
Status in shadow source package in Kinetic:
Fix Released
Bug description:
[Impact]
When using adduser --extrausers on Ubuntu Core the command attempts to
use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
following commands will fail:
$ adduser --extrausers user group
$ adduser --extrausers --ingroup group user
[Test Plan]
1. Install libnss-extrausers
2. Add a new group:
$ sudo adduser --extrausers --group test-group
3. Create a new user with this group:
$ adduser --extrausers --ingroup test-group test-user1
4. Create a new user and add them to this group:
$ adduser --extrausers test-user2
$ adduser --extrausers test-user2 test-group
[Touch-packages] [Bug 1965993] Re: Remove Ubuntu Pro settings
Note to self to update the PPA with this change re-enabled once this lands. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965993 Title: Remove Ubuntu Pro settings Status in software-properties package in Ubuntu: New Bug description: Due to backend delay, we want to remove the Ubuntu Pro settings and only show Livepatch settings as were previously shown. This feature will be re-added at a future time. This change will rename the "Ubuntu Pro" page to "Livepatch" and hide various UI elements. This adds the following new strings for translations: "This machine is not covered by an Ubuntu Advantage subscription." "Ubuntu Advantage subscription attached." "Livepatch" All existing strings for the Ubuntu Pro settings remain, so should remain translated when this change is reverted. See below for screenshots of the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965993] Re: Remove Ubuntu Pro settings
Change ready for release in the software-properties git: https://git.launchpad.net/software-properties/commit/?id=f2f4a566ee2cf45c35a1d1ed0849fde16553cc28 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965993 Title: Remove Ubuntu Pro settings Status in software-properties package in Ubuntu: New Bug description: Due to backend delay, we want to remove the Ubuntu Pro settings and only show Livepatch settings as were previously shown. This feature will be re-added at a future time. This change will rename the "Ubuntu Pro" page to "Livepatch" and hide various UI elements. This adds the following new strings for translations: "This machine is not covered by an Ubuntu Advantage subscription." "Ubuntu Advantage subscription attached." "Livepatch" All existing strings for the Ubuntu Pro settings remain, so should remain translated when this change is reverted. See below for screenshots of the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965993] Re: Remove Ubuntu Pro settings
Sent to mailing lists: https://lists.ubuntu.com/archives/ubuntu-doc/2022-March/020814.html https://lists.ubuntu.com/archives/ubuntu-translators/2022-March/007807.html ** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965993 Title: Remove Ubuntu Pro settings Status in software-properties package in Ubuntu: New Bug description: Due to backend delay, we want to remove the Ubuntu Pro settings and only show Livepatch settings as were previously shown. This feature will be re-added at a future time. This change will rename the "Ubuntu Pro" page to "Livepatch" and hide various UI elements. This adds the following new strings for translations: "This machine is not covered by an Ubuntu Advantage subscription." "Ubuntu Advantage subscription attached." "Livepatch" All existing strings for the Ubuntu Pro settings remain, so should remain translated when this change is reverted. See below for screenshots of the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965993] Re: Remove Ubuntu Pro settings
** Attachment added: "Current Ubuntu Pro page in jammy" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965993/+attachment/5572008/+files/Screenshot%20from%202022-03-23%2012-04-48.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965993 Title: Remove Ubuntu Pro settings Status in software-properties package in Ubuntu: New Bug description: Due to backend delay, we want to remove the Ubuntu Pro settings and only show Livepatch settings as were previously shown. This feature will be re-added at a future time. This change will rename the "Ubuntu Pro" page to "Livepatch" and hide various UI elements. This adds the following new strings for translations: "This machine is not covered by an Ubuntu Advantage subscription." "Ubuntu Advantage subscription attached." "Livepatch" All existing strings for the Ubuntu Pro settings remain, so should remain translated when this change is reverted. See below for screenshots of the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965993] Re: Remove Ubuntu Pro settings
** Attachment added: "Page with Ubuntu Pro settings removed." https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965993/+attachment/5572009/+files/Screenshot%20from%202022-03-23%2012-05-11.png ** Description changed: Due to backend delay, we want to remove the Ubuntu Pro settings and only show Livepatch settings as were previously shown. This feature will be re-added at a future time. This change will rename the "Ubuntu Pro" page to "Livepatch" and hide various UI elements. This adds the following new strings for translations: "This machine is not covered by an Ubuntu Advantage subscription." "Ubuntu Advantage subscription attached." "Livepatch" All existing strings for the Ubuntu Pro settings remain, so should - remain translated if this change is reverted. + remain translated when this change is reverted. See below for screenshots of the change. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965993 Title: Remove Ubuntu Pro settings Status in software-properties package in Ubuntu: New Bug description: Due to backend delay, we want to remove the Ubuntu Pro settings and only show Livepatch settings as were previously shown. This feature will be re-added at a future time. This change will rename the "Ubuntu Pro" page to "Livepatch" and hide various UI elements. This adds the following new strings for translations: "This machine is not covered by an Ubuntu Advantage subscription." "Ubuntu Advantage subscription attached." "Livepatch" All existing strings for the Ubuntu Pro settings remain, so should remain translated when this change is reverted. See below for screenshots of the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965993] [NEW] Remove Ubuntu Pro settings
Public bug reported:
Due to backend delay, we want to remove the Ubuntu Pro settings and only
show Livepatch settings as were previously shown. This feature will be
re-added at a future time.
This change will rename the "Ubuntu Pro" page to "Livepatch" and hide various
UI elements. This adds the following new strings for translations:
"This machine is not covered by an Ubuntu Advantage subscription."
"Ubuntu Advantage subscription attached."
"Livepatch"
All existing strings for the Ubuntu Pro settings remain, so should
remain translated when this change is reverted.
See below for screenshots of the change.
** Affects: software-properties (Ubuntu)
Importance: High
Assignee: Robert Ancell (robert-ancell)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1965993
Title:
Remove Ubuntu Pro settings
Status in software-properties package in Ubuntu:
New
Bug description:
Due to backend delay, we want to remove the Ubuntu Pro settings and
only show Livepatch settings as were previously shown. This feature
will be re-added at a future time.
This change will rename the "Ubuntu Pro" page to "Livepatch" and hide various
UI elements. This adds the following new strings for translations:
"This machine is not covered by an Ubuntu Advantage subscription."
"Ubuntu Advantage subscription attached."
"Livepatch"
All existing strings for the Ubuntu Pro settings remain, so should
remain translated when this change is reverted.
See below for screenshots of the change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965993/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965138] Re: Desktop application should check for service available information before listing it
The following PR should hopefully fix this:
https://github.com/canonical/ubuntu-advantage-desktop-daemon/pull/14
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
** Changed in: software-properties (Ubuntu)
Importance: Undecided => High
** Changed in: software-properties (Ubuntu)
Status: New => In Progress
** Package changed: software-properties (Ubuntu) => ubuntu-advantage-
desktop-daemon (Ubuntu)
** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu)
Assignee: Robert Ancell (robert-ancell) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1965138
Title:
Desktop application should check for service available information
before listing it
Status in ubuntu-advantage-desktop-daemon package in Ubuntu:
In Progress
Bug description:
Currently, it seems that software-properties is incorrectly assuming
that both ESM and Livepatch services can be enabled in a Jammy
machine. Those services are not yet available in Jammy and we are
attaching an image showing that the Desktop message is that we had an
error enabling then and that the user should try again.
It seems that software-proporties source `/var/lib/ubuntu-
advantage/status.json` and assumes the services is available if it
appears on the services list and the `entitled` field has the `yes`
value. However, it is perfectly possible for a service to be entitled
to an user, but not available in the user's machine.
We are now suggesting that software-properties also looks at the
`available` field in the services json output to make that assumption,
this will probably solve the issue we are seeing on Jammy.
Another approach would be using the output of `ua status --format
json` directly. However, this command will make a request to the
contract's server if the user is unattached and maybe it is not wise
to use it in that context. However, the output of that command only
show services that are available, so we would not need to apply that
extra available filter to it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-desktop-daemon/+bug/1965138/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959667] Re: non informative error message when enabling a non available UA service
The ua client doesn't currently provide any information about failures so we can't pass this information onto software-properties. There is an improvement being added to ua to give error codes and messages which we will take advantage of when it is available. ** Changed in: software-properties (Ubuntu) Status: New => Triaged ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: software-properties (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1959667 Title: non informative error message when enabling a non available UA service Status in software-properties package in Ubuntu: Triaged Bug description: Jammy / software-properties-gtk: Installed: 0.99.17 When trying to enable a service that is not available the error message provide no useful information about what went wrong (cf screenshot) and in the journal: ubuntu-advantag[1461382]: Failed to parse UA status: Operation was cancelled In both cases the error message should be similar to UA CLI: UA Infra: ESM is not available for Ubuntu 22.04 (Jammy Jellyfish). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1959667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958311] Re: Show all Ubuntu Advantage services
Currently available for testing in https://launchpad.net/~robert- ancell/+archive/ubuntu/ubuntu-pro -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1958311 Title: Show all Ubuntu Advantage services Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Bionic: In Progress Status in software-properties source package in Focal: In Progress Status in software-properties source package in Jammy: In Progress Bug description: Replace the Livepatch page with an "Ubuntu Pro" page that shows full status and control of Ubuntu Advantage services. This gives graphical control of features that the 'ua' command line tool provides. [Test Plan] 1. Open software-properties 2. Go to Ubuntu Pro page. 3. Check able to attach and detach this machine from an Ubuntu Advantage subscription. Check status matches what the 'ua' command line tool shows. Check graphical attachment status updates when performed from the command line. 4. Check able to enable/disable services. Check graphical service status updates when performed from the command line. [Where problems could occur] This is a major structural change in how Livepatch is enabled, and thus could break this existing feature (however this also removes a lot of the work currently performed to enable Livepatch and leaves that to the 'ua' tool). The new features could introduce new bugs, such as causing software-properties to crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1958311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958311] Re: Show all Ubuntu Advantage services
Blocked on ubuntu-advantage-desktop-daemon MIR (LP: #1954909) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1958311 Title: Show all Ubuntu Advantage services Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Bionic: In Progress Status in software-properties source package in Focal: In Progress Status in software-properties source package in Jammy: In Progress Bug description: Replace the Livepatch page with an "Ubuntu Pro" page that shows full status and control of Ubuntu Advantage services. This gives graphical control of features that the 'ua' command line tool provides. [Test Plan] 1. Open software-properties 2. Go to Ubuntu Pro page. 3. Check able to attach and detach this machine from an Ubuntu Advantage subscription. Check status matches what the 'ua' command line tool shows. Check graphical attachment status updates when performed from the command line. 4. Check able to enable/disable services. Check graphical service status updates when performed from the command line. [Where problems could occur] This is a major structural change in how Livepatch is enabled, and thus could break this existing feature (however this also removes a lot of the work currently performed to enable Livepatch and leaves that to the 'ua' tool). The new features could introduce new bugs, such as causing software-properties to crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1958311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958311] Re: Show all Ubuntu Advantage services
** Changed in: software-properties (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: software-properties (Ubuntu Focal) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: software-properties (Ubuntu Jammy) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: software-properties (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: software-properties (Ubuntu Focal) Importance: Undecided => High ** Changed in: software-properties (Ubuntu Bionic) Importance: Medium => High ** Changed in: software-properties (Ubuntu Jammy) Importance: Undecided => High ** Changed in: software-properties (Ubuntu Bionic) Status: New => Triaged ** Changed in: software-properties (Ubuntu Focal) Status: New => In Progress ** Changed in: software-properties (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: software-properties (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1958311 Title: Show all Ubuntu Advantage services Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Bionic: In Progress Status in software-properties source package in Focal: In Progress Status in software-properties source package in Jammy: In Progress Bug description: Replace the Livepatch page with an "Ubuntu Pro" page that shows full status and control of Ubuntu Advantage services. This gives graphical control of features that the 'ua' command line tool provides. [Test Plan] 1. Open software-properties 2. Go to Ubuntu Pro page. 3. Check able to attach and detach this machine from an Ubuntu Advantage subscription. Check status matches what the 'ua' command line tool shows. Check graphical attachment status updates when performed from the command line. 4. Check able to enable/disable services. Check graphical service status updates when performed from the command line. [Where problems could occur] This is a major structural change in how Livepatch is enabled, and thus could break this existing feature (however this also removes a lot of the work currently performed to enable Livepatch and leaves that to the 'ua' tool). The new features could introduce new bugs, such as causing software-properties to crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1958311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958311] [NEW] Show all Ubuntu Advantage services
Public bug reported: Replace the Livepatch page with an "Ubuntu Pro" page that shows full status and control of Ubuntu Advantage services. This gives graphical control of features that the 'ua' command line tool provides. [Test Plan] 1. Open software-properties 2. Go to Ubuntu Pro page. 3. Check able to attach and detach this machine from an Ubuntu Advantage subscription. Check status matches what the 'ua' command line tool shows. Check graphical attachment status updates when performed from the command line. 4. Check able to enable/disable services. Check graphical service status updates when performed from the command line. [Where problems could occur] This is a major structural change in how Livepatch is enabled, and thus could break this existing feature (however this also removes a lot of the work currently performed to enable Livepatch and leaves that to the 'ua' tool). The new features could introduce new bugs, such as causing software-properties to crash. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1958311 Title: Show all Ubuntu Advantage services Status in software-properties package in Ubuntu: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Jammy: New Bug description: Replace the Livepatch page with an "Ubuntu Pro" page that shows full status and control of Ubuntu Advantage services. This gives graphical control of features that the 'ua' command line tool provides. [Test Plan] 1. Open software-properties 2. Go to Ubuntu Pro page. 3. Check able to attach and detach this machine from an Ubuntu Advantage subscription. Check status matches what the 'ua' command line tool shows. Check graphical attachment status updates when performed from the command line. 4. Check able to enable/disable services. Check graphical service status updates when performed from the command line. [Where problems could occur] This is a major structural change in how Livepatch is enabled, and thus could break this existing feature (however this also removes a lot of the work currently performed to enable Livepatch and leaves that to the 'ua' tool). The new features could introduce new bugs, such as causing software-properties to crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1958311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931582] Re: Add LOGO to /etc/os-release
The format seems clear, from the os-release spec: "...the name of an icon as defined by freedesktop.org Icon Theme Specification" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1931582 Title: Add LOGO to /etc/os-release Status in base-files package in Ubuntu: Triaged Status in base-files package in Debian: New Bug description: /etc/os-release can provide a logo file, this is now used by gnome- control-center to show the logo into the info panel. If ubuntu would provide its logo name in such file we would be able to remove the downstream patch that forces the usage of /usr/share/pixmaps/ubuntu-logo-icon.png References --- https://www.freedesktop.org/software/systemd/man/os-release.html https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/985 GNOME Control Center, as of version 41, can look for variations of the named LOGO. So we should offer those variations if possible too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1931582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
Tested software-properties-gtk 0.96.24.32.18 on bionic. Confirmed banner shows with correct link and can be dismissed. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Bug description: [Impact] Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. Note that this is not shown in current releases, as this feature only applies to older versions. [Test Case] 1. Open Software Properties. 2. Go to Livepatch tab. Expected result: A banner is shown directing the user to Ubuntu Pro. The banner can be dismissed, and doesn't return when restarting software-properties. [Regression Potential] Some risk of introducing a new bug, however the change is quite small and doesn't have any complex interactions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
This has been uploaded as 0.96.24.32.18. SRU team please reject 0.96.24.32.17 in proposed as no need for that SRU to delay this one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Status in software-properties source package in Impish: Fix Committed Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
Tested software-properties-gtk 0.99.9.8 on focal. Confirmed banner shows with correct link and can be dismissed. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Bug description: [Impact] Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. Note that this is not shown in current releases, as this feature only applies to older versions. [Test Case] 1. Open Software Properties. 2. Go to Livepatch tab. Expected result: A banner is shown directing the user to Ubuntu Pro. The banner can be dismissed, and doesn't return when restarting software-properties. [Regression Potential] Some risk of introducing a new bug, however the change is quite small and doesn't have any complex interactions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
Tested software-properties-gtk 0.96.24.32.17 on bionic. Confirmed banner shows with correct link and can be dismissed. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Bug description: [Impact] Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. Note that this is not shown in current releases, as this feature only applies to older versions. [Test Case] 1. Open Software Properties. 2. Go to Livepatch tab. Expected result: A banner is shown directing the user to Ubuntu Pro. The banner can be dismissed, and doesn't return when restarting software-properties. [Regression Potential] Some risk of introducing a new bug, however the change is quite small and doesn't have any complex interactions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
@chad.smith - agreed, these changes as currently proposed will need to be updated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934199] Re: Switch from Livepatch service to UA client
I had a WIP branch done as part of the ESM work. That's now been rescheduled to April 2022, and the Livepatch migration will be done as part of that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934199 Title: Switch from Livepatch service to UA client Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: Won't Fix Status in software-properties source package in Impish: Won't Fix Bug description: software-properties currently uses a HTTP over Unix domain socket service from the livepatch snap to get the status and enable/disable it. This service is being deprecated with the 'ua' command line tool now providing this functionality. software-properties also installed the snap to gain access to this service. This is no longer required as the 'ua' tool does this. (*) The Livepatch service is a HTTP over Unix domain service running on livepatchd.sock inside the livepatch snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
@chad.smith - can you make merge requests for the required changes to the ubuntu/hirsute, ubuntu/focal etc branches (https://git.launchpad.net/ubuntu/+source/software-properties)? I can then review those and do the uploads as required. If you need any UI changes I can make those, but I think at this point it's just how to interact with the ua client correctly which is something you have a lot more information on than I do. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
Confirmed here that /var/lib/ubuntu-advantage/status.json is only updated when running 'ua status' as root. No desktop software is running as root, in the few cases that root privileges are required a small service is run as root and that is communicated with via D-Bus. The warning doesn't show for the majority of users, since they aren't going to be running from the command line so I would leave it for now, and remove in the next revision of this code. I think there is a case where this won't work - if you have a fresh machine that you haven't done a 'ua attach' on then software-properties is going to not offer ESM as it's not going to think it's available. In https://code.launchpad.net/~robert-ancell/software- properties/+git/software-properties/+merge/400153 that 'ua status' can timeout and return empty values, which is why we are accessing /var/lib/ubuntu-advantage/status.json. Is there a reason why the ua client doesn't do this itself internally, i.e. it gives you fresh json or returns the cached copy if it can't do the update? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
A couple of points about putting it into Impish: - What mechanism can we use to determine if it should show? - Since the banner refers to a beta feature, it will be replaced at some point with a new banner, is it worth bringing that into Impish or waiting for the more complete feature. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Bug description: [Impact] Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. Note that this is not shown in current releases, as this feature only applies to older versions. [Test Case] 1. Open Software Properties. 2. Go to Livepatch tab. Expected result: A banner is shown directing the user to Ubuntu Pro. The banner can be dismissed, and doesn't return when restarting software-properties. [Regression Potential] Some risk of introducing a new bug, however the change is quite small and doesn't have any complex interactions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
** Description changed: - Add a banner to the Livepatch page to invite users to join the Ubuntu - Pro for Desktop. + [Impact] + Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. Note that this is not shown in current releases, as this feature only applies to older versions. + + [Test Case] + 1. Open Software Properties. + 2. Go to Livepatch tab. + Expected result: + A banner is shown directing the user to Ubuntu Pro. + The banner can be dismissed, and doesn't return when restarting software-properties. + + [Regression Potential] + Some risk of introducing a new bug, however the change is quite small and doesn't have any complex interactions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Bug description: [Impact] Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. Note that this is not shown in current releases, as this feature only applies to older versions. [Test Case] 1. Open Software Properties. 2. Go to Livepatch tab. Expected result: A banner is shown directing the user to Ubuntu Pro. The banner can be dismissed, and doesn't return when restarting software-properties. [Regression Potential] Some risk of introducing a new bug, however the change is quite small and doesn't have any complex interactions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
Lech - the Xenial version doesn't have a Livepatch page, should it be placed somewhere else? ** Changed in: software-properties (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: software-properties (Ubuntu Focal) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Bug description: [Impact] Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. Note that this is not shown in current releases, as this feature only applies to older versions. [Test Case] 1. Open Software Properties. 2. Go to Livepatch tab. Expected result: A banner is shown directing the user to Ubuntu Pro. The banner can be dismissed, and doesn't return when restarting software-properties. [Regression Potential] Some risk of introducing a new bug, however the change is quite small and doesn't have any complex interactions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
** No longer affects: software-properties (Ubuntu Hirsute) ** No longer affects: software-properties (Ubuntu Impish) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Bug description: Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
Thanks for the feedback. Which distribution(s) should this be targetting? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Status in software-properties source package in Impish: New Bug description: Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
Information required for implementation: - Where does the link go to, http://ubuntu.com/desktop/pro? - Does the banner only show if you haven't already attached this machine to Ubuntu Advantage? - When closing the banner, does it return next time? - Does it make sense for this to be in the "Livepatch" tab - should that tab be renamed to "Ubuntu Pro" at the same time? - When will this feature no-longer be a preview? Will that require a second SRU or can we determine that at runtime? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Status in software-properties source package in Impish: New Bug description: Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
Implementation at https://code.launchpad.net/~robert-ancell/software- properties/+git/software-properties/+ref/ubuntu-pro-beta -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Status in software-properties source package in Impish: New Bug description: Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
** Attachment added: "Screenshot of implementation" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+attachment/5508533/+files/Screenshot%20from%202021-07-02%2016-58-30.png ** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Status in software-properties source package in Impish: New Bug description: Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934439] [NEW] Add Ubuntu Pro banner to Livepatch page
Public bug reported: Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Status in software-properties source package in Impish: New Bug description: Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
** Attachment added: "Mockup of banner" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+attachment/5508532/+files/ubuntu-pro-mockup.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Status in software-properties source package in Impish: New Bug description: Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934199] Re: Switch from Livepatch service to UA client
The current implementation shows "Last check for updates". As far as I can tell this information is not available via the UA client. It also shows a list of applied CVE fixes, which again I don't think is available from the UA client. See attached screenshot of current implementation in 18.04 LTS. ** Attachment added: "Screenshot from 2021-07-01 12-28-24.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+attachment/5508251/+files/Screenshot%20from%202021-07-01%2012-28-24.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934199 Title: Switch from Livepatch service to UA client Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Status in software-properties source package in Impish: New Bug description: software-properties currently uses a HTTP over Unix domain socket service from the livepatch snap to get the status and enable/disable it. This service is being deprecated with the 'ua' command line tool now providing this functionality. software-properties also installed the snap to gain access to this service. This is no longer required as the 'ua' tool does this. (*) The Livepatch service is a HTTP over Unix domain service running on livepatchd.sock inside the livepatch snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934199] [NEW] Switch from Livepatch service to UA client
Public bug reported: software-properties currently uses a HTTP over Unix domain socket service from the livepatch snap to get the status and enable/disable it. This service is being deprecated with the 'ua' command line tool now providing this functionality. software-properties also installed the snap to gain access to this service. This is no longer required as the 'ua' tool does this. (*) The Livepatch service is a HTTP over Unix domain service running on livepatchd.sock inside the livepatch snap. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934199 Title: Switch from Livepatch service to UA client Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Status in software-properties source package in Impish: New Bug description: software-properties currently uses a HTTP over Unix domain socket service from the livepatch snap to get the status and enable/disable it. This service is being deprecated with the 'ua' command line tool now providing this functionality. software-properties also installed the snap to gain access to this service. This is no longer required as the 'ua' tool does this. (*) The Livepatch service is a HTTP over Unix domain service running on livepatchd.sock inside the livepatch snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
The warnings about the status.json file are due to the ubuntu-advantage client on these older systems not yet having the feature to write this file. When updated, this should work - that's correct, right @chad.smith? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
Bionic and focal branches/PPA also updated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
I've updated the xenial branch and version in the PPA with the fixes requested, thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
This change is based on the expectation that UA tools will be the version that is about to be SRUd. The old version gracefully fails with `ua status --format=json`, so should already effectively return (False, False). I didn't do an explicit check on the version as it's non-trivial to do and I'd be more worried about introducing a bug in the version number parsing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
Merge request for master: https://code.launchpad.net/~robert-ancell/software-properties/+git/software-properties/+merge/400153 Other branches for SRUing: https://code.launchpad.net/~robert-ancell/software-properties/+git/software-properties/+ref/esm-focal https://code.launchpad.net/~robert-ancell/software-properties/+git/software-properties/+ref/esm-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
Code is in: https://code.launchpad.net/~robert-ancell/software-properties/+git/software-properties/+ref/esm https://code.launchpad.net/~robert-ancell/software-properties/+git/software-properties/+ref/esm-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
I've made a PPA to test this: https://launchpad.net/~robert- ancell/+archive/ubuntu/software-properties -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
** Also affects: software-properties (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
** Description changed: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] - 1. Open Software Properties - 2. Go to Updates tab. + 1. Install latest version of Ubuntu advantage: + $ sudo add-apt-repository ppa:ua-client/stable + $ sudo apt update + $ sudo apt upgrade + 2. Open Software Properties + 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: New Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
** Attachment added: "New UI in xenial with ESM applied." https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+attachment/5479359/+files/Screenshot%20from%202021-03-23%2012-31-56.png ** Description changed: [Impact] - There is not currently a graphical method of determining if a system is subscribed to Extended Security Maintenance updates. This is resolved by adding some new UI to the software properties application (design https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance). + There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Open Software Properties 2. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: New Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Open Software Properties 2. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
** Attachment added: "New UI in xenial with ESM available" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+attachment/5479358/+files/Screenshot%20from%202021-03-23%2012-32-22.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: New Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Open Software Properties 2. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] [NEW] Show Extended Security Maintenence status
Public bug reported: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Open Software Properties 2. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: New Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Open Software Properties 2. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
** Attachment added: "Current UI in xenial" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+attachment/5479357/+files/Screenshot%20from%202021-03-23%2012-32-37.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: New Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Open Software Properties 2. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892455] Re: [MIR] libselinux1
Oops, I thought it was in universe. This is not required then. ** Changed in: libselinux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libselinux in Ubuntu. https://bugs.launchpad.net/bugs/1892455 Title: [MIR] libselinux1 Status in libselinux package in Ubuntu: Invalid Bug description: Many applications have Flatpak integration using libflatpak. The Ubuntu desktop team would like libflatpak in main so we can easily build such applications (LP: #1812456). libselinux is a dependency of this, so it would also need to be in main. We don't need SELinux functionality, and do not expect any other SELinux packages to be installed by default. Availability In Universe, builds for all architectures and in sync with Debian. Rationale = Required for libostree-1-1 being in main (LP: #1892454) Security This will need a Security review. Quality Assurance = Should be subscribed to by Ubuntu Desktop Bugs. Contains a single .so and doesn't have any debconf prompts. Package is maintained in Debian. No major bugs in Debian or Ubuntu. UI Standards N/A Dependencies All in main. Standards Compliance Package uses standards version 4.5.0. Maintenance === Actively developed upstream https://github.com/SELinuxProject/selinux. Packages actively maintained in Debian. Security Checks === 41 CVEs found in http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=selinux, but they seem to relate to actual SELinux functionality, not issues in libselinux. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libselinux/+bug/1892455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892455] Re: [MIR] libselinux1
** Description changed: Many applications have Flatpak integration using libflatpak. The Ubuntu desktop team would like libflatpak in main so we can easily build such applications (LP: #1812456). libselinux is a dependency of this, so it would also need to be in main. We don't need SELinux functionality, and do not expect any other SELinux packages to be installed by default. Availability In Universe, builds for all architectures and in sync with Debian. Rationale = Required for libostree-1-1 being in main (LP: #1892454) Security This will need a Security review. Quality Assurance = Contains a single .so and doesn't have any debconf prompts. Package is maintained in Debian. No major bugs in Debian or Ubuntu. UI Standards N/A Dependencies All in main. Standards Compliance Package uses standards version 4.5.0. Maintenance === - Maintained in Debian. + Actively developed upstream https://github.com/SELinuxProject/selinux. + Packages actively maintained in Debian. Security Checks === No CVEs found in http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libselinux. ** Changed in: libselinux (Ubuntu) Importance: Undecided => Medium ** Description changed: Many applications have Flatpak integration using libflatpak. The Ubuntu desktop team would like libflatpak in main so we can easily build such applications (LP: #1812456). libselinux is a dependency of this, so it would also need to be in main. We don't need SELinux functionality, and do not expect any other SELinux packages to be installed by default. Availability In Universe, builds for all architectures and in sync with Debian. Rationale = Required for libostree-1-1 being in main (LP: #1892454) Security This will need a Security review. Quality Assurance = Contains a single .so and doesn't have any debconf prompts. Package is maintained in Debian. No major bugs in Debian or Ubuntu. UI Standards N/A Dependencies All in main. Standards Compliance Package uses standards version 4.5.0. Maintenance === Actively developed upstream https://github.com/SELinuxProject/selinux. Packages actively maintained in Debian. Security Checks === - No CVEs found in http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libselinux. + 41 CVEs found in http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=selinux, but they seem to relate to actual SELinux functionality, not issues in libselinux. ** Description changed: Many applications have Flatpak integration using libflatpak. The Ubuntu desktop team would like libflatpak in main so we can easily build such applications (LP: #1812456). libselinux is a dependency of this, so it would also need to be in main. We don't need SELinux functionality, and do not expect any other SELinux packages to be installed by default. Availability In Universe, builds for all architectures and in sync with Debian. Rationale = Required for libostree-1-1 being in main (LP: #1892454) Security This will need a Security review. Quality Assurance = - Contains a single .so and doesn't have any debconf prompts. Package is maintained in Debian. No major bugs in Debian or Ubuntu. + Should be subscribed to by Ubuntu Desktop Bugs. + + Contains a single .so and doesn't have any debconf prompts. Package is + maintained in Debian. No major bugs in Debian or Ubuntu. UI Standards N/A Dependencies All in main. Standards Compliance Package uses standards version 4.5.0. Maintenance === Actively developed upstream https://github.com/SELinuxProject/selinux. Packages actively maintained in Debian. Security Checks === 41 CVEs found in http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=selinux, but they seem to relate to actual SELinux functionality, not issues in libselinux. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libselinux in Ubuntu. https://bugs.launchpad.net/bugs/1892455 Title: [MIR] libselinux1 Status in libselinux package in Ubuntu: New Bug description: Many applications have Flatpak integration using libflatpak. The Ubuntu desktop team would like libflatpak in main so we can easily build such applications (LP: #1812456). libselinux is a dependency of this, so it would also need to be in main. We don't need SELinux functionality, and do not expect any other SELinux packages to be installed by default. Availability In Universe, builds for all architectures an
[Touch-packages] [Bug 1892455] [NEW] [MIR] libselinux1
Public bug reported: Many applications have Flatpak integration using libflatpak. The Ubuntu desktop team would like libflatpak in main so we can easily build such applications (LP: #1812456). libselinux is a dependency of this, so it would also need to be in main. We don't need SELinux functionality, and do not expect any other SELinux packages to be installed by default. Availability In Universe, builds for all architectures and in sync with Debian. Rationale = Required for libostree-1-1 being in main (LP: #1892454) Security This will need a Security review. Quality Assurance = Contains a single .so and doesn't have any debconf prompts. Package is maintained in Debian. No major bugs in Debian or Ubuntu. UI Standards N/A Dependencies All in main. Standards Compliance Package uses standards version 4.5.0. Maintenance === Maintained in Debian. Security Checks === No CVEs found in http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libselinux. ** Affects: libselinux (Ubuntu) Importance: Undecided Status: New ** Description changed: Availability In Universe, builds for all architectures and in sync with Debian. Rationale = Required for libostree-1-1 being in main (LP: #1892454) Security - TBD + This will need a Security review. Quality Assurance = Contains a single .so and doesn't have any debconf prompts. Package is maintained in Debian. No major bugs in Debian or Ubuntu. UI Standards N/A Dependencies All in main. Standards Compliance Package uses standards version 4.5.0. Maintenance === Maintained in Debian. Security Checks === TBD ** Description changed: Availability In Universe, builds for all architectures and in sync with Debian. Rationale = Required for libostree-1-1 being in main (LP: #1892454) Security This will need a Security review. Quality Assurance = Contains a single .so and doesn't have any debconf prompts. Package is maintained in Debian. No major bugs in Debian or Ubuntu. UI Standards N/A Dependencies All in main. Standards Compliance Package uses standards version 4.5.0. Maintenance === Maintained in Debian. Security Checks === - TBD + No CVEs found in http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libselinux. ** Description changed: + Many applications have Flatpak integration using libflatpak. The Ubuntu + desktop team would like libflatpak in main so we can easily build such + application (LP: #1812456). libselinux is a dependency of this, so it + would also need to be in main. We don't need SELinux functionality, and + do not expect it to be installed by default. + Availability In Universe, builds for all architectures and in sync with Debian. Rationale = Required for libostree-1-1 being in main (LP: #1892454) Security This will need a Security review. Quality Assurance = Contains a single .so and doesn't have any debconf prompts. Package is maintained in Debian. No major bugs in Debian or Ubuntu. UI Standards N/A Dependencies All in main. Standards Compliance Package uses standards version 4.5.0. Maintenance === Maintained in Debian. Security Checks === No CVEs found in http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libselinux. ** Description changed: Many applications have Flatpak integration using libflatpak. The Ubuntu desktop team would like libflatpak in main so we can easily build such - application (LP: #1812456). libselinux is a dependency of this, so it + applications (LP: #1812456). libselinux is a dependency of this, so it would also need to be in main. We don't need SELinux functionality, and do not expect it to be installed by default. Availability In Universe, builds for all architectures and in sync with Debian. Rationale = Required for libostree-1-1 being in main (LP: #1892454) Security This will need a Security review. Quality Assurance = Contains a single .so and doesn't have any debconf prompts. Package is maintained in Debian. No major bugs in Debian or Ubuntu. UI Standards N/A Dependencies All in main. Standards Compliance Package uses standards version 4.5.0. Maintenance === Maintained in Debian. Security Checks === No CVEs found in http://cve.mitre.org/cgi-bin
[Touch-packages] [Bug 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno
Confirmed fixed in Bionic with json-glib 1.4.2-3ubuntu0.18.04.1 ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: Fix Released Status in json-glib source package in Bionic: Fix Committed Status in json-glib source package in Eoan: Fix Committed Status in json-glib source package in Focal: Fix Released Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Errors are not shown on the command line Observed result: The following errors are shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno
Confirmed fixed in Eoan with json-glib 1.4.4-2ubuntu0.19.10.1 ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: Fix Released Status in json-glib source package in Bionic: Fix Committed Status in json-glib source package in Eoan: Fix Committed Status in json-glib source package in Focal: Fix Released Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Errors are not shown on the command line Observed result: The following errors are shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno
** Changed in: json-glib (Ubuntu Bionic) Status: Fix Committed => In Progress ** Changed in: json-glib (Ubuntu Eoan) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: Fix Committed Status in json-glib source package in Bionic: In Progress Status in json-glib source package in Eoan: In Progress Status in json-glib source package in Focal: Fix Committed Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Errors are not shown on the command line Observed result: The following errors are shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno
** Changed in: json-glib (Ubuntu Eoan) Status: New => Fix Committed ** Changed in: json-glib (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: Fix Committed Status in json-glib source package in Bionic: Fix Committed Status in json-glib source package in Eoan: Fix Committed Status in json-glib source package in Focal: Fix Committed Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Errors are not shown on the command line Observed result: The following errors are shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno
** Description changed: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: - Postman is shown with correct data + Errors are not shown on the command line Observed result: - Not all channels shown, the following shown on the command line: + The following errors are shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: Fix Committed Status in json-glib source package in Bionic: New Status in json-glib source package in Eoan: New Status in json-glib source package in Focal: Fix Committed Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Errors are not shown on the command line Observed result: The following errors are shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno
** Changed in: json-glib (Ubuntu Focal) Status: New => Fix Committed ** Changed in: json-glib (Ubuntu Focal) Importance: Undecided => High ** Changed in: json-glib (Ubuntu Eoan) Importance: Undecided => High ** Changed in: json-glib (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: Fix Committed Status in json-glib source package in Bionic: New Status in json-glib source package in Eoan: New Status in json-glib source package in Focal: Fix Committed Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Postman is shown with correct data Observed result: Not all channels shown, the following shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno
** Changed in: json-glib (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: json-glib (Ubuntu Eoan) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: json-glib (Ubuntu Focal) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: New Status in json-glib source package in Bionic: New Status in json-glib source package in Eoan: New Status in json-glib source package in Focal: New Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Postman is shown with correct data Observed result: Not all channels shown, the following shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871023] [NEW] json_gvariant_deserialize can fail due to unrelated code setting errno
Public bug reported: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Postman is shown with correct data Observed result: Not all channels shown, the following shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. ** Affects: json-glib (Ubuntu) Importance: Undecided Status: New ** Affects: json-glib (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: json-glib (Ubuntu Eoan) Importance: Undecided Status: New ** Affects: json-glib (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: json-glib (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: json-glib (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: json-glib (Ubuntu Eoan) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: New Status in json-glib source package in Bionic: New Status in json-glib source package in Eoan: New Status in json-glib source package in Focal: New Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Postman is shown with correct data Observed result: Not all channels shown, the following shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1086783] Re: New PolicyKit 0.106 changes configuration file format
I've made a forum post asking for feedback from users of polkit in Ubuntu (https://discourse.ubuntu.com/t/use-of-javascript-rules-in- polkit/13892). If you have comments please add them there instead of this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1086783 Title: New PolicyKit 0.106 changes configuration file format Status in policykit-1 package in Ubuntu: Triaged Status in policykit-1 package in Debian: Fix Released Bug description: From the NEWS file: This is polkit 0.106. There's a major change in this release which is a switch from .pkla files (keyfile-format) to .rules files (JavaScript). We may want to hold off on the new version because it requires rewriting the configuration files, and adds a dependency on mozjs185, which will need a MIR (and getting a MIR may be problematic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1086783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1086783] Re: New PolicyKit 0.106 changes configuration file format
An update on the current state of this: - polkit upstream currently depends on mozjs60 - mozjs60 is in main, but only for the use of GNOME Shell. - The current polkit Debian/Ubuntu package has 61 patches in it, backporting lots of changes from version 106 to 116. - There are upstream requests for running polkit without a JS interpreter. - There is an open MR to switch from mozjs to duktape (https://gitlab.freedesktop.org/polkit/polkit/merge_requests/35). - Debian experimental has polkit 116 packaged (i.e. with JS backend). - I've made a proof of concept branch which reinstates the local backend (https://gitlab.freedesktop.org/rancell/polkit/tree/traditional-backend) which works. It's desirable that we run the latest version in Debian/Ubuntu, which requires one of: - We re-assess the use of mozjs and decide if it's acceptable in this case. - We support the switch from mozjs to duktape if that's a safer option. - We propose the old local backend upstream as an alternative to the JS backend. - We carry the local backend as a patch on upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1086783 Title: New PolicyKit 0.106 changes configuration file format Status in policykit-1 package in Ubuntu: Triaged Status in policykit-1 package in Debian: Fix Released Bug description: From the NEWS file: This is polkit 0.106. There's a major change in this release which is a switch from .pkla files (keyfile-format) to .rules files (JavaScript). We may want to hold off on the new version because it requires rewriting the configuration files, and adds a dependency on mozjs185, which will need a MIR (and getting a MIR may be problematic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1086783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1742997] Re: Newly installed applications are not showing in "Installed"
Confirmed in bionic that gnome-software 3.28.1-0ubuntu4.18.04.12 after removing and re-installing moon-buggy it shows in the installed page. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1742997 Title: Newly installed applications are not showing in "Installed" Status in GNOME Software: Expired Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Invalid Status in gnome-software source package in Bionic: Fix Committed Status in packagekit source package in Bionic: Invalid Bug description: [Impact] Removing and installing an app stops it showing in the installed apps page. [Test Case] 1. Open GNOME Software 2. Go to installed tab 3. Click on an installed app 4. Remove this app 5. Install this app 6. Click back button to return to installation page. Expected result: App shows on page. Observed result: App does not show on page. [Regression Potential] Change is small, and just fixes and ordering issue. Unlikely to trigger other major issues. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1742997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843730] Re: dee ftbfs in eoan (all architectures)
The patch from ricotz makes sense to me. The particular properties are construct only and unlikely to be used by a Vala app. So disabling them works fine. ** Changed in: dee (Ubuntu Eoan) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dee in Ubuntu. https://bugs.launchpad.net/bugs/1843730 Title: dee ftbfs in eoan (all architectures) Status in dee package in Ubuntu: Fix Committed Status in dee source package in Eoan: Fix Committed Bug description: https://launchpadlibrarian.net/441262638/buildlog_ubuntu-eoan- amd64.dee_1.2.7+17.10.20170616-4ubuntu1_BUILDING.txt.gz deprecated glib/gtk symbols To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dee/+bug/1843730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1742997] Re: Newly installed applications are not showing in "Installed"
** Changed in: gnome-software (Ubuntu Bionic) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1742997 Title: Newly installed applications are not showing in "Installed" Status in GNOME Software: Expired Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Invalid Status in gnome-software source package in Bionic: Fix Committed Status in packagekit source package in Bionic: Invalid Bug description: [Impact] Removing and installing an app stops it showing in the installed apps page. [Test Case] 1. Open GNOME Software 2. Go to installed tab 3. Click on an installed app 4. Remove this app 5. Install this app 6. Click back button to return to installation page. Expected result: App shows on page. Observed result: App does not show on page. [Regression Potential] Change is small, and just fixes and ordering issue. Unlikely to trigger other major issues. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1742997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1742997] Re: Newly installed applications are not showing in "Installed"
** Changed in: gnome-software (Ubuntu Bionic) Status: Confirmed => Triaged ** Description changed: - If you install any application using GNOME Software (Ubuntu Software), - the newly installed application is not displayed on the "Installed" tab. - It starts showing after the next system reboot. + [Impact] + Removing and installing an app stops it showing in the installed apps page. - Steps to Reproduce: - 1. Find any application that is not installed and install it. - 2. Switch to the "Installed" tab and try to find the newly installed application. + [Test Case] + 1. Open GNOME Software + 2. Go to installed tab + 3. Click on an installed app + 4. Remove this app + 5. Install this app + 6. Click back button to return to installation page. + + Expected result: + App shows on page. + + Observed result: + App does not show on page. + + [Regression Potential] + Change is small, and just fixes and ordering issue. Unlikely to trigger other major issues. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1742997 Title: Newly installed applications are not showing in "Installed" Status in GNOME Software: Expired Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Invalid Status in gnome-software source package in Bionic: Triaged Status in packagekit source package in Bionic: Invalid Bug description: [Impact] Removing and installing an app stops it showing in the installed apps page. [Test Case] 1. Open GNOME Software 2. Go to installed tab 3. Click on an installed app 4. Remove this app 5. Install this app 6. Click back button to return to installation page. Expected result: App shows on page. Observed result: App does not show on page. [Regression Potential] Change is small, and just fixes and ordering issue. Unlikely to trigger other major issues. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1742997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules
@chrisccoulson - I sponsored the changes as per normal, so they're in
the queue for -proposed in bionic and disco. Can I upload to the
security pocket? Does that just require debian/changelog to be changed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1842651
Title:
Regression: after Uprade from udev_237-3ubuntu10.25 to
udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
-persistent-network.rules
Status in OEM Priority Project:
In Progress
Status in systemd package in Ubuntu:
In Progress
Bug description:
[Impact]
* Many server users upgraded from previous Ubuntu LTS series, such as
14.04 and 16.04, will be affected by this regression.
* Because there is /etc/udev/rules/70-persistent-network.rules or
/etc/udev/rules.d/70-persistent-net.rules generated by
/lib/udev/write_net_rules left.
* The previous SRU commit of LP: #1837700 doesn't cover this
persistent network rule.
[Test Case]
* It needs to have two Ethernet devices and provides
/etc/udev/rules.d/70-persistent-net.rules as below.
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
[Regression Potential]
* When users upgrade to next LTS 20.04, they may also encounter this
issue because Debian has dropped the same patch.
* We need to figure another way to avoid this regression for next LTS
20.04.
* Adding back the origial patch from Debian will casue another issue.
(LP: #1837700)
[Other Info]
Since the latest update from udev_237-3ubuntu10.25 and
systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
systemd_237-3ubuntu10.26 the renaming of network interfaces by
/etc/udev/rules/70-persistent-network.rules does not work.
/etc/udev/rules/70-persistent-network.rules:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
/var/log/syslog:
systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File
exists
When I downgrade the packages to the version with 237-3ubuntu10.25 the
following messages are in /var/log/syslog:
Sep 4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2:
renamed from eth0
Sep 4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed
from eth1
The latest version does not rename the interfaces temporary if there
is a conflict!
Manually installing the old packages with
dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
did fix the problem temporary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6
The main issue is when I updated to 0.6.55 the new Meson based build systemd didn't build with systemd support by default. So I've uploaded a build with this enabled. There may still be an underlying issue, but this should fix the eoan issues. ** Changed in: accountsservice (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1841382 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 Status in accountsservice: New Status in accountsservice package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1841382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6
Upstream bug report opened: https://gitlab.freedesktop.org/accountsservice/accountsservice/issues/80 ** Bug watch added: gitlab.freedesktop.org/accountsservice/accountsservice/issues #80 https://gitlab.freedesktop.org/accountsservice/accountsservice/issues/80 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1841382 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1841382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6
If the above theory is correct then this commit caused the bug: https://gitlab.freedesktop.org/accountsservice/accountsservice/commit/9b4108755a6e1f5f04d80fef92dd3f81423857ad This commit came when we migrated from 0.6.45 to 0.6.50, which explains why this is being seen in disco and eoan. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1841382 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1841382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6
It looks like it's crashing in this code:
username = act_user_get_user_name (user);
if (g_hash_table_lookup (priv->system_users_by_name, username) != NULL)
{
and username is probably NULL.
A possible cause of this is the user object for some reason might not
have a DBus proxy backing it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1841382
Title:
Various programs crashed with SIGSEGV in g_str_hash() from
g_hash_table_lookup_node() / g_hash_table_lookup() from
accountsservice 0.6.55-0ubuntu5/6
Status in accountsservice package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d
I do not know what triggered the crash.
ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.32.2-2ubuntu1
ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
Uname: Linux 5.2.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 25 20:45:09 2019
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2019-08-24 (1 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
?? ()
?? ()
Title: gnome-shell crashed with SIGSEGV in g_str_hash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1841382/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6
** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1841382 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1841382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841079] Re: Speech Dispatcher and other non-human users should not be shown on LightdDM login screen and session menus
Can you please test accountsservice 0.6.55-0ubuntu7 and confirm if this fixes these users? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1841079 Title: Speech Dispatcher and other non-human users should not be shown on LightdDM login screen and session menus Status in accountsservice package in Ubuntu: Triaged Status in accountsservice source package in Eoan: Triaged Bug description: Steps to reproduce: 1. Download Ubuntu MATE 19.10 alpha ISO - 20190822 2. Install it using Entire-disk erase scenario with default settings 3. Reboot system Expected results: * LightDM shows only just created username Actual results: * LightDM shows two user names, Speech Dispatcher is selected by default Note: problem occurs on VM and on real hardware; Minimal desktop installation is affected too; OEM installation is affected by bug 1840971 . ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: speech-dispatcher 0.9.1-2 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Thu Aug 22 19:02:42 2019 InstallationDate: Installed on 2019-08-22 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822) SourcePackage: speech-dispatcher UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1841079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837700] Re: Dell system takes a long time to connect network with external dock
** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Shih-Yuan Lee (fourdollars) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837700 Title: Dell system takes a long time to connect network with external dock Status in HWE Next: New Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Bug description: update for SRU process: [Impact] 1. On system featured mac passthrough, e.g., Dell/Lenovo laptop, or system occasionally install two USB ethernet with same MAC address, the system will suffer 90 seconds for network interface renaming mechanism before the last USB ethernet interface to activate. [Test Case] 1. Install ubuntu on Dell laptop. 2. Connect the Dell laptop with two Realtek 8153 USB ethernet dongle. Users can observe the last one will take 90 seconds for renaming to rename0. 3. Users can also find that the two USB ethernet have the same MAC address. [Regression Potential] To resolve the issue, drop a debian patch from systemd package. The debian patch is to revert an upstream commit to support 75-persistent-net-generator.rules udev rule. Since the udev rule is deprecated, the regression potential should be relatively low. --- Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]: https://salsa.debian.org/systemd-team/systemd/blo
[Touch-packages] [Bug 1742997] Re: Newly installed applications are not showing in "Installed"
Note that this bug occurs on all versions of GNOME Software. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1742997 Title: Newly installed applications are not showing in "Installed" Status in GNOME Software: Expired Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Invalid Status in gnome-software source package in Bionic: Confirmed Status in packagekit source package in Bionic: Invalid Bug description: If you install any application using GNOME Software (Ubuntu Software), the newly installed application is not displayed on the "Installed" tab. It starts showing after the next system reboot. Steps to Reproduce: 1. Find any application that is not installed and install it. 2. Switch to the "Installed" tab and try to find the newly installed application. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1742997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1742997] Re: Newly installed applications are not showing in "Installed"
https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/291 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1742997 Title: Newly installed applications are not showing in "Installed" Status in GNOME Software: Expired Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Invalid Status in gnome-software source package in Bionic: Confirmed Status in packagekit source package in Bionic: Invalid Bug description: If you install any application using GNOME Software (Ubuntu Software), the newly installed application is not displayed on the "Installed" tab. It starts showing after the next system reboot. Steps to Reproduce: 1. Find any application that is not installed and install it. 2. Switch to the "Installed" tab and try to find the newly installed application. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1742997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1742997] Re: Newly installed applications are not showing in "Installed"
I've managed to find a bug that stops apps appearing in the installed list when they are *reinstalled*. To reproduce: 1. Open GNOME Software 2. Go to installed tab 3. Click on an installed app 4. Remove this app 5. Install this app 6. Click back button to return to installation page. The app won't show in the installation page, this is because the app row was animated to collapse, but not removed. When the app is installed again G-S thinks the row is already there and it doesn't show it. If you've had G-S open for a long time then you might be installing an app you had previously installed at launch time or after. Can anyone reproduce this issue with an app that was *not* previously installed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1742997 Title: Newly installed applications are not showing in "Installed" Status in GNOME Software: Expired Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Invalid Status in gnome-software source package in Bionic: Confirmed Status in packagekit source package in Bionic: Invalid Bug description: If you install any application using GNOME Software (Ubuntu Software), the newly installed application is not displayed on the "Installed" tab. It starts showing after the next system reboot. Steps to Reproduce: 1. Find any application that is not installed and install it. 2. Switch to the "Installed" tab and try to find the newly installed application. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1742997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
