[Touch-packages] [Bug 1943189] Re: "cannot refresh whilst network offline" bug
Ok, that sounds good. I'm just curious because I'm on Impish and experiencing issues with PackageKit due to this bug. So far I've been restarting the service after I boot. -- 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/1943189 Title: "cannot refresh whilst network offline" bug Status in packagekit package in Ubuntu: In Progress Status in packagekit source package in Focal: Confirmed Status in packagekit source package in Hirsute: Confirmed Status in packagekit source package in Impish: In Progress Bug description: [Impact] In Ubuntu Impish, an issue has been noted in regards to refreshing packages in Plasma Discover for upgrade or installation. An error appears upon initialization of the Discover interface: "cannot refresh whilst network offline" This will happen regardless of if a system is online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. [Test Plan] * Install Kubuntu or Ubuntu Studio * While connected to network, Run Discover * Discover will complain about "cannot refresh whilst offline", which is being communicated from PackageKit. All functionality in Discover is hindered from this point forward. This is due to a hung packagekitd process which sees the network offline, even though this is false. [Where problems could occur] * packagekitd's systemd service will time-out after 90 seconds if systemd finds no network, which means any update notifications will not automatically start until packagekitd is manually started. Luckily, Discover and GNOME Software both attempt to start packagekitd for the user when run. I'd consider this to be expected behavior for an offline system. The fix is mostly to prevent the false-negative of the system being offline when it's really not. [Other Info] * This fix has been accepted upstream by the PackageKit maintainers as a sane workaround for when gio misbehaves or otherwise. It's a decent safety net. https://github.com/PackageKit/PackageKit/pull/506 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu1 [modified: lib/systemd/system/packagekit.service] ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 9 16:34:12 2021 InstallationDate: Installed on 2021-03-20 (172 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+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 1943189] Re: "cannot refresh whilst network offline" bug
Nice! When do you think the Ubuntu package will be updated? -- 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/1943189 Title: "cannot refresh whilst network offline" bug Status in packagekit package in Ubuntu: In Progress Status in packagekit source package in Focal: Confirmed Status in packagekit source package in Hirsute: Confirmed Status in packagekit source package in Impish: In Progress Bug description: [Impact] In Ubuntu Impish, an issue has been noted in regards to refreshing packages in Plasma Discover for upgrade or installation. An error appears upon initialization of the Discover interface: "cannot refresh whilst network offline" This will happen regardless of if a system is online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. [Test Plan] * Install Kubuntu or Ubuntu Studio * While connected to network, Run Discover * Discover will complain about "cannot refresh whilst offline", which is being communicated from PackageKit. All functionality in Discover is hindered from this point forward. This is due to a hung packagekitd process which sees the network offline, even though this is false. [Where problems could occur] * packagekitd's systemd service will time-out after 90 seconds if systemd finds no network, which means any update notifications will not automatically start until packagekitd is manually started. Luckily, Discover and GNOME Software both attempt to start packagekitd for the user when run. I'd consider this to be expected behavior for an offline system. The fix is mostly to prevent the false-negative of the system being offline when it's really not. [Other Info] * This fix has been accepted upstream by the PackageKit maintainers as a sane workaround for when gio misbehaves or otherwise. It's a decent safety net. https://github.com/PackageKit/PackageKit/pull/506 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu1 [modified: lib/systemd/system/packagekit.service] ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 9 16:34:12 2021 InstallationDate: Installed on 2021-03-20 (172 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+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 1943189] Re: "cannot refresh whilst network offline" bug
Did you also submit this fix for the previous patch upstream? -- 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/1943189 Title: "cannot refresh whilst network offline" bug Status in packagekit package in Ubuntu: In Progress Status in packagekit source package in Focal: Confirmed Status in packagekit source package in Hirsute: Confirmed Status in packagekit source package in Impish: In Progress Bug description: [Impact] In Ubuntu Impish, an issue has been noted in regards to refreshing packages in Plasma Discover for upgrade or installation. An error appears upon initialization of the Discover interface: "cannot refresh whilst network offline" This will happen regardless of if a system is online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. [Test Plan] * Install Kubuntu or Ubuntu Studio * While connected to network, Run Discover * Discover will complain about "cannot refresh whilst offline", which is being communicated from PackageKit. All functionality in Discover is hindered from this point forward. This is due to a hung packagekitd process which sees the network offline, even though this is false. [Where problems could occur] * packagekitd's systemd service will time-out after 90 seconds if systemd finds no network, which means any update notifications will not automatically start until packagekitd is manually started. Luckily, Discover and GNOME Software both attempt to start packagekitd for the user when run. I'd consider this to be expected behavior for an offline system. The fix is mostly to prevent the false-negative of the system being offline when it's really not. [Other Info] * This fix has been accepted upstream by the PackageKit maintainers as a sane workaround for when gio misbehaves or otherwise. It's a decent safety net. https://github.com/PackageKit/PackageKit/pull/506 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu1 [modified: lib/systemd/system/packagekit.service] ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 9 16:34:12 2021 InstallationDate: Installed on 2021-03-20 (172 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+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 1835809] Re: AMD Ryzen 3000 series fails to boot
I tested 240-6ubuntu5.2, it fixes the issue on Ubuntu 19.04 ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco ** Tags removed: verification-needed -- 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/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * Systems with AMD Ryzen 3000 series CPUs don't boot. [Test Case] * Boot with fixed systemd on an AMD Ryzen 3000 series system. [Regression Potential] * The fix itself is very small, it ignores known to be faulty random values returned by the rdrand instruction and use a different random source. Those values can still be returned by a properly working rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in 2^64 cases on 64 bit arches, but the fallback to the other random source ensures that in those rare occasions a random number can be generated. [Original Bug Text] On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1835809] Re: AMD Ryzen 3000 series fails to boot
Thanks, I will get it tested soon -- 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/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * Systems with AMD Ryzen 3000 series CPUs don't boot. [Test Case] * Boot with fixed systemd on an AMD Ryzen 3000 series system. [Regression Potential] * The fix itself is very small, it ignores known to be faulty random values returned by the rdrand instruction and use a different random source. Those values can still be returned by a properly working rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in 2^64 cases on 64 bit arches, but the fallback to the other random source ensures that in those rare occasions a random number can be generated. [Original Bug Text] On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1835809] Re: AMD Ryzen 3000 series fails to boot
Sebastien, thanks for getting eyes on it! Éric, these systems will not boot the 19.04 ISO without either new firmware fixing the rdrand instruction, or a new ISO updating systemd with this patch. -- 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/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: New Bug description: On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1835809] Re: AMD Ryzen 3000 series fails to boot
I have tested the patch posted, and it produces a bootable system with 19.04. We will be releasing the patched version of systemd in the following PPAs: Pop!_OS - https://launchpad.net/~system76/+archive/ubuntu/pop Ubuntu support for System76 computers - https://launchpad.net/~system76-dev/+archive/ubuntu/stable Please let me know what needs to happen to get this patch into Ubuntu 19.04 -- 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/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: New Bug description: On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1835809] Re: AMD Ryzen 3000 series fails to boot
A systemd package with this patch applied is building here: - amd64 - https://launchpad.net/~system76/+archive/ubuntu/proposed/+build/17236776 - i386 - https://launchpad.net/~system76/+archive/ubuntu/proposed/+build/17236777 -- 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/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: New Bug description: On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1835809] [NEW] AMD Ryzen 3000 series fails to boot
Public bug reported: On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Patch added: "Rebase of https://github.com/systemd/systemd/pull/12536; https://bugs.launchpad.net/bugs/1835809/+attachment/5275667/+files/rdrand-workaround-on-amd.patch -- 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/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: New Bug description: On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1740894] Re: KEY_RFKILL is not passed to userspace
When can we expect a release of the proposed xkb-data? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Status in xkeyboard-config source package in Disco: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
I can confirm that xkb-data 2.23.1-1ubuntu1.18.04.1 fixes this issue for me on bionic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Status in xkeyboard-config source package in Disco: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
I will try it out on bionic in a few hours -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Status in xkeyboard-config source package in Disco: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
I can confirm that xkb-data 2.23.1-1ubuntu1.18.10.1 fixes this issue for me on cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Status in xkeyboard-config source package in Disco: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
That sounds great! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in gnome-settings-daemon package in Ubuntu: Triaged Status in libxkbcommon package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Bug description: There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
Yes, this is still an issue. Please see the above scripts. I am not aware of why gnome-settings-daemon does not receive the keypress and trigger airplane mode, if those X11 packages are up to date. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in gnome-settings-daemon package in Ubuntu: Incomplete Status in libxkbcommon package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Bug description: There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1740894/+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 1787272] [NEW] Administrators are not added to adm group
Public bug reported: Currently administrators are only added to the sudo group. This was fixed a long time ago by https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/810907, but there has likely been a regression. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- 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/1787272 Title: Administrators are not added to adm group Status in accountsservice package in Ubuntu: New Bug description: Currently administrators are only added to the sudo group. This was fixed a long time ago by https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/810907, but there has likely been a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1787272/+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 1749546] Re: Booting a live session is slow - fontconfig regenerates its font cache
I can also confirm that this fixed the issue in Pop!_OS and elementary OS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1749546 Title: Booting a live session is slow - fontconfig regenerates its font cache Status in Fontconfig: Confirmed Status in fontconfig package in Ubuntu: Fix Released Status in fontconfig source package in Bionic: Fix Released Bug description: On Bionic Ubuntu Desktop booting to a live session is slow. It takes roughly 2 min on my test machine to boot from the "Try or Install Ubuntu" boot menu to a usable session. It also takes 1 minute to logout and 17s to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: casper 1.388 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 16:43:19 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/1749546/+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 1699216] Re: Encrypted home support
There is no issue with that. We will be able to keep our patches in initial setup without any effort from Ubuntu and minimal effort from Pop. We are going to be encouraging full disk encryption, the same as Ubuntu. -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Won't Fix Status in gnome-control-center package in Ubuntu: Won't Fix Status in gnome-initial-setup package in Ubuntu: Won't Fix Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1740894] Re: KEY_RFKILL is not passed to userspace
In artful and later, a number of kernel drivers send KEY_RFKILL - which is being ignored by the userspace handling code. https://elixir.free-electrons.com/linux/v4.13.16/ident/KEY_RFKILL ** Also affects: libxkbcommon (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** Also affects: x11proto-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in gnome-settings-daemon package in Ubuntu: New Status in libxkbcommon package in Ubuntu: New Status in x11proto-core package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
This may also be the cause of https://bugs.launchpad.net/ubuntu/+source /gnome-settings-daemon/+bug/1722034 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in gnome-settings-daemon package in Ubuntu: New Status in libxkbcommon package in Ubuntu: New Status in x11proto-core package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1740894/+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 1699216] Re: Encrypted home support
Thanks for the feedback Robert. I will work on updating my patch. That does sound like a much cleaner approach. -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
Here is a patch without symbol changes or whitespace changes ** Patch added: "accountsservice_encrypt_home.debdiff" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4997109/+files/accountsservice_encrypt_home.debdiff -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1724370] Re: NVME model does not show up
Finally, the kernel model from a SATA drive: $ cat /sys/block/sda/device/model Samsung SSD 850 And from an NVME drive: $ cat /sys/block/nvme0n1/device/model Samsung SSD 950 PRO 256GB -- 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/1724370 Title: NVME model does not show up Status in gnome-disk-utility package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: The Model field for NVME drives is blank. I believe this issue comes from udisks2, and then from udev. udisks2 has a function for getting the model which returns blank, udisks_drive_get_model udev has a parameter that should be returned for a disk if it has a model, ID_MODEL The Linux kernel exposes the true model in a sys file, /sys/block/nvme0n1/device/model This data should be displayed in GNOME Disks when available, but is not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1724370/+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 1724370] Re: NVME model does not show up
Here is the information from an NVME drive. Note that ID_MODEL is missing: $ udevadm info /dev/nvme0n1 P: /devices/pci:00/:00:1d.0/:6f:00.0/nvme/nvme0/nvme0n1 N: nvme0n1 S: disk/by-id/nvme-Samsung_SSD_950_PRO_256GB_S2GLNX0H717763V S: disk/by-id/nvme-eui.0025385761b084ef S: disk/by-path/pci-:6f:00.0-nvme-1 E: DEVLINKS=/dev/disk/by-path/pci-:6f:00.0-nvme-1 /dev/disk/by-id/nvme-Samsung_SSD_950_PRO_256GB_S2GLNX0H717763V /dev/disk/by-id/nvme-eui.0025385761b084ef E: DEVNAME=/dev/nvme0n1 E: DEVPATH=/devices/pci:00/:00:1d.0/:6f:00.0/nvme/nvme0/nvme0n1 E: DEVTYPE=disk E: ID_PART_TABLE_TYPE=gpt E: ID_PART_TABLE_UUID=713ba820-c08d-478b-bd6c-e589cc8159e3 E: ID_PATH=pci-:6f:00.0-nvme-1 E: ID_PATH_TAG=pci-_6f_00_0-nvme-1 E: ID_SERIAL=Samsung SSD 950 PRO 256GB_S2GLNX0H717763V E: ID_SERIAL_SHORT=S2GLNX0H717763V E: ID_WWN=eui.0025385761b084ef E: MAJOR=259 E: MINOR=0 E: SUBSYSTEM=block E: TAGS=:systemd: E: USEC_INITIALIZED=1212332 ** Also affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Also 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/1724370 Title: NVME model does not show up Status in gnome-disk-utility package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: The Model field for NVME drives is blank. I believe this issue comes from udisks2, and then from udev. udisks2 has a function for getting the model which returns blank, udisks_drive_get_model udev has a parameter that should be returned for a disk if it has a model, ID_MODEL The Linux kernel exposes the true model in a sys file, /sys/block/nvme0n1/device/model This data should be displayed in GNOME Disks when available, but is not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1724370/+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 1699216] Re: Encrypted home support
12:36 seb128 dmj_s76, right, we are likely to get it reviewed next cycle 12:37 seb128 it hasn't been high priority for us since we don't use gnome-inital-setup and don't plan to for next cycle either 12:37 seb128 but we should be able to review those changes anyways 12:51 jackpot51 seb128 what about for creating new users? It is not supported in gnome-control-center either 12:52 seb128 jackpot51, that would be a nice improvement to get 12:52 seb128 but for next cycle now -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
IRC Log: 10:39 jackpot51 Can we talk about this patch again? https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216 ··· 10:39 ubot5 Ubuntu bug 1699216 in gnome-initial-setup (Ubuntu) "Encrypted home support" [Wishlist,Confirmed] 10:40 jackpot51 I just saw a new accountsservice show up, superseding my patches for encrypted home. 10:40 jackpot51 Here is a debdiff of the patch I want to keep in accountsservice, one that allows gnome-initial-setup and gnome-control-center to support Encrypted Home https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4945507/+files/accountsservice_encrypt_home.debdiff ··· 10:40 ubot5 Ubuntu bug 1699216 in gnome-initial-setup (Ubuntu) "Encrypted home support" [Wishlist,Confirmed] 10:41 jackpot51 GunnarHj and others would you mind taking a look? 10:44 seb128 jackpot51, sounds a bit late in this cycle for such changes 10:47 jackpot51 All I want is the accountsservice patch, so we don't have to hold a forked accountsservice 10:52 jbicha we never found anyone willing to review the accountsservice patch :( 10:53 jackpot51 Well, every time accountsservice gets updated in Ubuntu, I get fucked. Why? Because I cannot rename the package. 10:53 jackpot51 So I am probably going to have to drop the patches for encrypted home entirely 10:56 jbicha once Ubuntu 17.10 is released, any SRUs for accountsservice will have to age in -proposed for at least 7 days first. That gives you time to update your PPA. 10:56 jackpot51 Ok, that would be good 10:57 jackpot51 Many users are getting pop-gnome-initial-setup removed if they dist-upgrade 10:58 jackpot51 It doesn't break their systems, but it introduces a significant amount of maintenance work 11:54 GunnarHjHi jackpot51, sorry if you felt ignored by my accountsservice upload. That was not my intention. 11:54 GunnarHjI have noticed your patches previously, but unfortunately they are too complex for me to review. The change I uploaded was a trivial one, and that's what I do - trivial stuff. :) 11:54 GunnarHjHopefully some experienced developer will find the time in the beginning of next cycle. 11:57 jackpot51 I dropped all our patches. Users will have to wait until Ubuntu can merge the patch, it is too much maintenance work to have encrypted home in gnome-initial-setup and gnome-control-center 11:59 jackpot51 The only other alternative was to use an epoch, which would make it impossible to go back to the Ubuntu version if the patches are merged 12:00 dmj_s76 This patch represents a fairly important feature for us. -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
This one updates the symbol names - they did not get updated with a debuild -S ** Patch added: "accountsservice_encrypt_home.debdiff" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4966858/+files/accountsservice_encrypt_home.debdiff -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
Here is an updated version of the patch for accountsservice -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
** Patch added: "accountsservice_encrypt_home.debdiff" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4966857/+files/accountsservice_encrypt_home.debdiff -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1720256] Re: Wrong display of fonts in Gnome Tweak Tool after installing cantarell fonts
This affects pop-session as well, which uses session overrides similar to how ubuntu-session does. The desktop icon settings are also incorrect. -- 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/1720256 Title: Wrong display of fonts in Gnome Tweak Tool after installing cantarell fonts Status in glib2.0 package in Ubuntu: Confirmed Bug description: When cantarell fonts are installed, Gnome Tweak Tools shows as if "Cantarell" was the font being used when it is actually "Ubuntu". Before that, it showed "None". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1720256/+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 1699216] Re: Encrypted home support
I have extra whitespace changes in there, I will resubmit with `-w` -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
tsimonq2, here id a debdiff file ** Patch added: "Accountservice Encrypt Home Debdiff" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4945505/+files/accountsservice_encrypt_home.debdiff -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
Here is a better patch, ignoring whitespace changes. ** Patch added: "accountsservice_encrypt_home.debdiff" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4945507/+files/accountsservice_encrypt_home.debdiff -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
tsimonq2, I have subscribed ubuntu-release. We have modifications in our PPA that utilize this patch to accountsservice. If the patch to accountsservice is not merged in Ubuntu's version, our version will be overridden when there is another accountsservice release. Since this is a feature that is desired in Ubuntu, I think it would be best to allow for the patch to accountsservice to be merged in for use by others, regardless of the patches to gnome-control-center or gnome- initial-setup. At the moment, we have a safely forked version of these packages that cannot be overridden. The issue with accountservice, is that it cannot be forked, renamed, and then use a Provides Conflicts Replaces. This leaves us in a dangerous place where we may have to revert our changes to add encrypted home to gnome-control-center and gnome-initial-setup. -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
ximion, as I already said here: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/comments/11 Encrypted home cannot go upstream, as adduser --encrypt-home is only implemented on Ubuntu. -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
Simon, it is critical for our efforts that the accountsservice patches make it upstream before 17.10. Can we focus only on those, leaving inotial setup and control center patches for 18.04? -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
Yes, I believe this still affects 16.04. I applied the patch on machines that System76 ships, but it is not upstream. It is the same patch as was applied to 17.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Status in wpa package in Ubuntu: Fix Released Status in network-manager source package in Xenial: New Status in ubiquity source package in Xenial: New Status in wpa source package in Xenial: New Bug description: * Steps to reproduce: 1. Install image 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1699216] Re: Encrypted home support
seb128: I subscribed ubuntu-sponsors. Is there anything else I can do? -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
Would anyone like to comment on my patches? -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
I made a mistake in the accountsservice patch. Here is an updated version. ** Patch added: "encrypt_home.patch" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1699216/+attachment/4899663/+files/encrypt_home.patch -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
Ok, here are new patches that do not break the current API. It is a little bit messier in accountsservice due to this. ** Patch added: "accountsservice_encrypt_home.patch" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4899522/+files/accountsservice_encrypt_home.patch -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
** Patch added: "gnome-initial-setup_encrypt_home.patch" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4899524/+files/gnome-initial-setup_encrypt_home.patch -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
** Patch added: "gnome-control-center_encrypt_home.patch" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4899523/+files/gnome-control-center_encrypt_home.patch -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
ximion, I am working on a more compatible patch, one that does not break libaccountsservice API. As for going upstream, I would like to go into Ubuntu first, as --encrypt-home is not implemented in other distros right now. -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
If you would like to test these patches in action, you can add this PPA and update: https://launchpad.net/~system76/+archive/ubuntu/pop/ -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
Attached find a proposed patch for this, allowing for two more patches to gnome-initial-setup and gnome-control-center that add encrypted home support when creating users. I have tested it on Ubuntu GNOME 17.04, and it works. ** Patch added: "encrypted_home.patch" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4899421/+files/encrypted_home.patch ** Also affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
Attached you will find a patch for encrypted home support in gnome- control-center. This patch will add a switch for "Encrypted Home Folder", and send the correct value to CreateUser in accountsservice. ** Patch added: "encrypt_home.patch" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1699216/+attachment/4899423/+files/encrypt_home.patch -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
Attached you will find a patch for encrypted home support in gnome- initial-setup. This patch will add a switch for "Encrypted Home Folder", and send the correct value to CreateUser in accountsservice. ** Patch added: "encrypt_home.patch" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1699216/+attachment/4899422/+files/encrypt_home.patch -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] [NEW] Encrypted home support
Public bug reported: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: Confirmed -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
Would it be acceptable to have a patch to `wpa` to add `IgnoreOnIsolate` for the time being? If we hold it in the Ubuntu debian/patches then we can wait for a better solution to be done upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Triaged Status in ubiquity package in Ubuntu: Incomplete Status in wpa package in Ubuntu: Incomplete Bug description: * Steps to reproduce: 1. Install image 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
Here is how I have been working around this bug for System76's machines: https://launchpadlibrarian.net/303137969/wpa_2.4-0ubuntu6_2.4-0ubuntu7~system76~1.diff.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Triaged Status in ubiquity package in Ubuntu: Incomplete Status in wpa package in Ubuntu: Incomplete Bug description: * Steps to reproduce: 1. Install image 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
Yes, I am. I just need to know what is permissible - we can add IgnoreOnIsolate in a ubuntu patch but it seems like the source of the issue is in network manager - it should detect that wpa supplicant is not running and restart it dynamically. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Triaged Bug description: * Steps to reproduce: 1. Install image 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
By the way, it is possible to trigger the bug running on your own system. All you have to do is run `sudo systemctl isolate default.target` while connected to WiFi Bluetooth may also go down. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Confirmed Bug description: * Steps to reproduce: 1. Install image 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
This is caused by wpa_supplicant being killed by systemctl isolate in oem-config-firstboot A potential fix is to add IgnoreOnIsolate=true to [Unit] in wpa_supplicant.service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Confirmed Bug description: * Steps to reproduce: 1. Install image 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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
