** Description changed: - error message on start up + [Impact] + Closing an application using PackageKit or aptdaemon to install packages kills the debconf endpoint (because it's a subprocess that's cleaned up), causing debconf to use defaults which might lead to wrong results, or even cause installations to fail. - ProblemType: Package - DistroRelease: Ubuntu 16.04 - Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 - ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 - Uname: Linux 4.10.0-37-generic x86_64 - .proc.sys.kernel.moksbstate_disabled: 0 - ApportVersion: 2.20.1-0ubuntu2.10 - Architecture: amd64 - Date: Sun Oct 22 12:33:48 2017 - DpkgHistoryLog: - Start-Date: 2017-10-22 12:31:01 - Commandline: aptdaemon role='role-commit-packages' sender=':1.94' - Install: linux-image-generic:amd64 (4.4.0.97.102, automatic), libcuda1-387:amd64 (387.12-0ubuntu0~gpu16.04.1, automatic), linux-image-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), linux-image-extra-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), nvidia-prime:amd64 (0.8.2, automatic), libxnvctrl0:amd64 (384.90-0ubuntu0~gpu16.04.1, automatic), lib32gcc1:amd64 (1:6.0.1-0ubuntu1, automatic), libc6-i386:amd64 (2.23-0ubuntu9, automatic), screen-resolution-extra:amd64 (0.17.1, automatic), ocl-icd-libopencl1:amd64 (2.2.8-1, automatic), libjansson4:amd64 (2.7-3, automatic), bbswitch-dkms:amd64 (0.8-3ubuntu1, automatic), linux-generic:amd64 (4.4.0.97.102), nvidia-opencl-icd-387:amd64 (387.12-0ubuntu0~gpu16.04.1, automatic), nvidia-387:amd64 (387.12-0ubuntu0~gpu16.04.1), nvidia-settings:amd64 (384.90-0ubuntu0~gpu16.04.1, automatic) - EFITables: - Oct 22 12:34:32 crs-Ubuntu kernel: efi: EFI v2.40 by American Megatrends - Oct 22 12:34:32 crs-Ubuntu kernel: efi: ESRT=0x77e72f98 ACPI=0x77591000 ACPI 2.0=0x77591000 SMBIOS=0x77e71000 SMBIOS 3.0=0x77e70000 - Oct 22 12:34:32 crs-Ubuntu kernel: esrt: Reserving ESRT space from 0x0000000077e72f98 to 0x0000000077e72fd0. - Oct 22 12:34:32 crs-Ubuntu kernel: Secure boot enabled - ErrorMessage: subprocess installed post-installation script returned error exit status 1 - InstallationDate: Installed on 2017-05-16 (159 days ago) - InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) - RelatedPackageVersions: - dpkg 1.18.4ubuntu1.2 - apt 1.2.24 - SecureBoot: 6 0 0 0 1 - SourcePackage: shim-signed - Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - UpgradeStatus: No upgrade log present (probably fresh install) + [Solution] + The solution is to move the end point into a socket-activated systemd unit, so that it is independent of the graphical frontend that started the transaction. The other advantage is that this offers us restart if the end point crashes. + + [Test case] + 1. Install opera deb using packagekit, ensure service is activated + 2. Install opera deb using aptdaemon, ensure service is activated + + Alternatively, you might use another deb that has debconf prompts. + + [Regression potential] + Systems that do not yet use systemd will fall back to the old method, so should not regress. + + Otherwise, if there are bugs, they'd affect the ability to show debconf + prompts, and behavior would revert to using the defaults. + + There might be some uncertainty if you restart your desktop while the + helper is running and it does not pick up the new X/Wayland display + until it restarts (it should fail to connect and restart). Given that + the helper times out, this should not be an issue in practice, as you'd + have to logout, login, and start a new install within 60 seconds.
-- 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/1726068 Title: debconf socket closes if aptdaemon/PK client exits Status in apper package in Ubuntu: New Status in aptdaemon package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Invalid Status in apper source package in Bionic: New Status in aptdaemon source package in Bionic: New Status in packagekit source package in Bionic: New Status in apper source package in Disco: New Status in aptdaemon source package in Disco: New Status in packagekit source package in Disco: In Progress Bug description: [Impact] Closing an application using PackageKit or aptdaemon to install packages kills the debconf endpoint (because it's a subprocess that's cleaned up), causing debconf to use defaults which might lead to wrong results, or even cause installations to fail. [Solution] The solution is to move the end point into a socket-activated systemd unit, so that it is independent of the graphical frontend that started the transaction. The other advantage is that this offers us restart if the end point crashes. [Test case] 1. Install opera deb using packagekit, ensure service is activated 2. Install opera deb using aptdaemon, ensure service is activated Alternatively, you might use another deb that has debconf prompts. [Regression potential] Systems that do not yet use systemd will fall back to the old method, so should not regress. Otherwise, if there are bugs, they'd affect the ability to show debconf prompts, and behavior would revert to using the defaults. There might be some uncertainty if you restart your desktop while the helper is running and it does not pick up the new X/Wayland display until it restarts (it should fail to connect and restart). Given that the helper times out, this should not be an issue in practice, as you'd have to logout, login, and start a new install within 60 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apper/+bug/1726068/+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
