Packages that trigger multiple debconf prompts fail to install

Status changed to 'Confirmed' because the bug affects multiple users.

I got this same problem on Ubuntu GNOME 17.10 64-bit when trying to run the following in the terminal:

sudo apt update && sudo apt upgrade -y

Affects me while testing 17.10.

setting to high given the frequency of this defect.

Robert, can you look please? Sounds to me like it's something to do with debconf support which you've worked on lately. The testcase in the original report was on zesty - not sure if it's still there in artful.

Added to Trello: https://trello.com/c/SbWAfmKA/12-bug-1688721-package-gconf2-common-3-2-6-3ubuntu7-failed-to-install-upgrade-subprocess-installed-post-installation-script-returne

Status changed to 'Confirmed' because the bug affects multiple users.

I could reproduce in Zesty, but not Artful or Xenial.

All current duplicates are for Zesty, except for bug 1691599 (Artful) and bug 1692344 (Yakkety).

By purging gconf2-common, I can reproduce in Artful.

i.e.
$ sudo apt purge gconf2-common
$ gnome-software --local-filename ~/Downloads/google-chrome-stable_current_amd64.deb

Using the purge technique I can also reproduce in Xenial. I suspect this problem isn't being seen much pre-Zesty because gconf is already installed (pulled in by aisleriot and probably other older pacakges).

I reproduced the same defect on Artful. Also while installing updates the libpam-systemd also failed to install with a similar trace.

Cause is due to there being multiple debconf connections when gconf-common is configured (all of which close without any content being sent). The gnome-software debconf code only handled the first connection.

This bug was fixed in the package gnome-software - 3.24.3-0ubuntu3

---------------
gnome-software (3.24.3-0ubuntu3) artful; urgency=medium

  * debian/patches/0006-Add-an-APT-plugin.patch:
    - Handle multiple debconf connections (LP: #1688721)

 -- Robert Ancell <email address hidden> Tue, 23 May 2017 21:28:12 +1200

See https://errors.ubuntu.com/problem/95c5d509e333a0e080eaf9e58e755a510e0c9c0f for error reports.

Well done!

Sorry, I can't understand how to fix the bug. Can you clarify me what to do?

Pier Luigi Bonucci

Hello Rafael, or anyone else affected,

Accepted gnome-software into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-software/3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Rafael, or anyone else affected,

Accepted gnome-software into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-software/3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

An upload of gnome-software to zesty-proposed has been rejected from the upload queue for the following reason: "This upload also includes version 3.22.7-0ubuntu3.17.04.3 of gnome-software which fixes bug 1689425, however this bug does not appear in the Launchpad-Bugs-Fixed section of the .changes file (https://launchpadlibrarian.net/320895234/gnome-software_3.22.7-0ubuntu3.17.04.4_source.changes) as such that bug won't be tracked as a part of the SRU when it should be. Subsequently, I'm rejecting this upload.".

The latest upload to the zesty queue of gnome-software now contains the following in the changelog:

+ * debian/patches/0006-Add-an-APT-plugin.patch:
+ - Handle multiple debconf connections (LP: #1688721)

However, there isn't actually a 0006-Add-an-APT-plugin.patch file in the diff. There is a 0002-Add-an-APT-plugin.patch file in the diff and it looks to me (based off looking at the yakkety diff of the package in -proposed) like the multiple debconf connections work is included in the 0002 patch. If that is correct I'm happy to accept the package into -proposed with the typo in the changelog, I just want to confirm we really are getting the fix for this bug in zesty. Thanks!

Yeah, this is just a typo copying the changelog from a artful back to zesty. The fix is in the 0002 patch.

Hello Rafael, or anyone else affected,

Accepted gnome-software into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-software/3.22.7-0ubuntu3.17.04.5 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.

Thank you!

I verified that I can install Google Chrome now with 3.22.7-0ubuntu3.17.04.5 on Ubuntu GNOME 17.04 where gconf was not already pre-installed.

I also verified that Google Chrome now installs successfully with
3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.10.1 on Ubuntu GNOME 16.10
3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1 on Ubuntu GNOME 16.04 LTS

This bug was fixed in the package gnome-software - 3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1

---------------
gnome-software (3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1) xenial; urgency=medium

  * New upstream snapshot from the wip/ubuntu-3-20 branch at
    git://git.gnome.org/gnome-software.
    - Handle multiple debconf connections (LP: #1688721)
    - Limit search entry in case of accidental input (LP: #1692398)

 -- Robert Ancell <email address hidden> Wed, 24 May 2017 09:49:56 +1200

The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package gnome-software - 3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.10.1

---------------
gnome-software (3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.10.1) yakkety; urgency=medium

  * New upstream snapshot from the wip/ubuntu-3-20 branch at
    git://git.gnome.org/gnome-software.
    - Handle multiple debconf connections (LP: #1688721)
    - Limit search entry in case of accidental input (LP: #1692398)

 -- Robert Ancell <email address hidden> Wed, 24 May 2017 09:49:56 +1200

This bug was fixed in the package gnome-software - 3.22.7-0ubuntu3.17.04.5

---------------
gnome-software (3.22.7-0ubuntu3.17.04.5) zesty; urgency=medium

  * debian/patches/0001-snap-Fix-icons-not-being-converted-to-pixbufs.patch:
    - Fix snaps without icons not showing reliably (LP: #1697565)
  * debian/patches/0001-snap-Backport-fixes-from-master.patch:
    - Show featured snaps (LP: #1663097)
  * debian/patches/0017-Use-snap-name-field-for-app-name.patch:
    - Dropped, merged into above patch

gnome-software (3.22.7-0ubuntu3.17.04.4) zesty; urgency=medium

  * debian/patches/0006-Add-an-APT-plugin.patch:
    - Handle multiple debconf connections (LP: #1688721)
  * debian/patches/0018-Limit-search-entry-to-100-characters.patch:
    - Limit search entry in case of accidental input (LP: #1692398)

gnome-software (3.22.7-0ubuntu3.17.04.3) zesty; urgency=medium

  * debian/patches/0002-Add-an-APT-plugin.patch:
    - Fix crash when debconf socket fails (LP: #1689425)

 -- Robert Ancell <email address hidden> Fri, 16 Jun 2017 13:42:12 +1200

Whenever i try to install any appliacation i have face this problem ?
Note : See the screenshot

On Fri, Jun 30, 2017 at 1:06 AM, Launchpad Bug Tracker <
<email address hidden>> wrote:

> This bug was fixed in the package gnome-software -
> 3.22.7-0ubuntu3.17.04.5
>
> ---------------
> gnome-software (3.22.7-0ubuntu3.17.04.5) zesty; urgency=medium
>
> * debian/patches/0001-snap-Fix-icons-not-being-converted-to-
> pixbufs.patch:
> - Fix snaps without icons not showing reliably (LP: #1697565)
> * debian/patches/0001-snap-Backport-fixes-from-master.patch:
> - Show featured snaps (LP: #1663097)
> * debian/patches/0017-Use-snap-name-field-for-app-name.patch:
> - Dropped, merged into above patch
>
> gnome-software (3.22.7-0ubuntu3.17.04.4) zesty; urgency=medium
>
> * debian/patches/0006-Add-an-APT-plugin.patch:
> - Handle multiple debconf connections (LP: #1688721)
> * debian/patches/0018-Limit-search-entry-to-100-characters.patch:
> - Limit search entry in case of accidental input (LP: #1692398)
>
> gnome-software (3.22.7-0ubuntu3.17.04.3) zesty; urgency=medium
>
> * debian/patches/0002-Add-an-APT-plugin.patch:
> - Fix crash when debconf socket fails (LP: #1689425)
>
> -- Robert Ancell <email address hidden> Fri, 16 Jun 2017
> 13:42:12 +1200
>
> ** Changed in: gnome-software (Ubuntu Zesty)
> Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1694521).
> https://bugs.launchpad.net/bugs/1688721
>
> Title:
> Packages that trigger multiple debconf prompts fail to install
>
> Status in gnome-software package in Ubuntu:
> Fix Released
> Status in gnome-software source package in Xenial:
> Fix Released
> Status in gnome-software source package in Yakkety:
> Fix Released
> Status in gnome-software source package in Zesty:
> Fix Released
> Status in gnome-software source package in Artful:
> Fix Released
>
> Bug description:
> [Impact]
> Some packages stall on installing. These are packages that generate
> multiple debconf prompts (the prompts may be empty and so not user visible,
> e.g. gconf2-common).
>
> [Test Case]
> 1. Remove gconf2-common (warning, may uninstall packages like
> gnome-terminal):
> $ sudo apt purge gconf2-common
> 2. Download the debian package of Chrome from www.google.com/chrome.
> 3. Install the package (browser will prompt, or double click on package
> in Nautilus).
>
> Expected result:
> Chrome installs correctly.
>
> Observed result:
> The installation hangs on 51%.
>
> [Regression Potential]
> The debconf conde was modified to support multiple requests. This could
> expose other debconf issues or break other .deb install code.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-software/
> +bug/1688721/+subscriptions
>

Dear Sir. Mac Abdul,

This issue was solved as per previous instructions and correct way to install the program. Thanks all team involved for their efforts and results to provide a quick answer.

________________________________
De: <email address hidden> <email address hidden> em nome de Mac Abdul <email address hidden>
Enviado: quinta-feira, 6 de julho de 2017 08:45:19
Para: <email address hidden>
Assunto: Re: [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

Whenever i try to install any appliacation i have face this problem ?
Note : See the screenshot

On Fri, Jun 30, 2017 at 1:06 AM, Launchpad Bug Tracker <
<email address hidden>> wrote:

> This bug was fixed in the package gnome-software -
> 3.22.7-0ubuntu3.17.04.5
>
> ---------------
> gnome-software (3.22.7-0ubuntu3.17.04.5) zesty; urgency=medium
>
> * debian/patches/0001-snap-Fix-icons-not-being-converted-to-
> pixbufs.patch:
> - Fix snaps without icons not showing reliably (LP: #1697565)
> * debian/patches/0001-snap-Backport-fixes-from-master.patch:
> - Show featured snaps (LP: #1663097)
> * debian/patches/0017-Use-snap-name-field-for-app-name.patch:
> - Dropped, merged into above patch
>
> gnome-software (3.22.7-0ubuntu3.17.04.4) zesty; urgency=medium
>
> * debian/patches/0006-Add-an-APT-plugin.patch:
> - Handle multiple debconf connections (LP: #1688721)
> * debian/patches/0018-Limit-search-entry-to-100-characters.patch:
> - Limit search entry in case of accidental input (LP: #1692398)
>
> gnome-software (3.22.7-0ubuntu3.17.04.3) zesty; urgency=medium
>
> * debian/patches/0002-Add-an-APT-plugin.patch:
> - Fix crash when debconf socket fails (LP: #1689425)
>
> -- Robert Ancell <email address hidden> Fri, 16 Jun 2017
> 13:42:12 +1200
>
> ** Changed in: gnome-software (Ubuntu Zesty)
> Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1694521).
> https://bugs.launchpad.net/bugs/1688721
>
> Title:
> Packages that trigger multiple debconf prompts fail to install
>
> Status in gnome-software package in Ubuntu:
> Fix Released
> Status in gnome-software source package in Xenial:
> Fix Released
> Status in gnome-software source package in Yakkety:
> Fix Released
> Status in gnome-software source package in Zesty:
> Fix Released
> Status in gnome-software source package in Artful:
> Fix Released
>
> Bug description:
> [Impact]
> Some packages stall on installing. These are packages that generate
> multiple debconf prompts (the prompts may be empty and so not user visible,
> e.g. gconf2-common).
>
> [Test Case]
> 1. Remove gconf2-common (warning, may uninstall packages like
> gnome-terminal):
> $ sudo apt purge gconf2-common
> 2. Download the debian package of Chrome from www.google.com/chrome<http://www.google.com/chrome>.
> 3. Install the package (browser will prompt, or double click on package
> in Nautilus).
>
> Expected result:
> Chrome installs correctly.
>
> Observed result:
> The installation hangs on 51%.
>
> [Regression Potential]
> The debconf conde was modi...

In Ubuntu 17.10 the "show application" should have on top-left instead of
bottom-left and "minimize-maximize-close" buttons should have been on the
left side of the window instead of right side.

On Thu, Jul 6, 2017 at 5:49 PM, carlos roberto alves benevides <
<email address hidden>> wrote:

> Dear Sir. Mac Abdul,
>
>
> This issue was solved as per previous instructions and correct way to
> install the program. Thanks all team involved for their efforts and results
> to provide a quick answer.
>
> ________________________________
> De: <email address hidden> <email address hidden> em nome de Mac Abdul <
> <email address hidden>>
> Enviado: quinta-feira, 6 de julho de 2017 08:45:19
> Para: <email address hidden>
> Assunto: Re: [Bug 1688721] Re: Packages that trigger multiple debconf
> prompts fail to install
>
> Whenever i try to install any appliacation i have face this problem ?
> Note : See the screenshot
>
> On Fri, Jun 30, 2017 at 1:06 AM, Launchpad Bug Tracker <
> <email address hidden>> wrote:
>
> > This bug was fixed in the package gnome-software -
> > 3.22.7-0ubuntu3.17.04.5
> >
> > ---------------
> > gnome-software (3.22.7-0ubuntu3.17.04.5) zesty; urgency=medium
> >
> > * debian/patches/0001-snap-Fix-icons-not-being-converted-to-
> > pixbufs.patch:
> > - Fix snaps without icons not showing reliably (LP: #1697565)
> > * debian/patches/0001-snap-Backport-fixes-from-master.patch:
> > - Show featured snaps (LP: #1663097)
> > * debian/patches/0017-Use-snap-name-field-for-app-name.patch:
> > - Dropped, merged into above patch
> >
> > gnome-software (3.22.7-0ubuntu3.17.04.4) zesty; urgency=medium
> >
> > * debian/patches/0006-Add-an-APT-plugin.patch:
> > - Handle multiple debconf connections (LP: #1688721)
> > * debian/patches/0018-Limit-search-entry-to-100-characters.patch:
> > - Limit search entry in case of accidental input (LP: #1692398)
> >
> > gnome-software (3.22.7-0ubuntu3.17.04.3) zesty; urgency=medium
> >
> > * debian/patches/0002-Add-an-APT-plugin.patch:
> > - Fix crash when debconf socket fails (LP: #1689425)
> >
> > -- Robert Ancell <email address hidden> Fri, 16 Jun 2017
> > 13:42:12 +1200
> >
> > ** Changed in: gnome-software (Ubuntu Zesty)
> > Status: Fix Committed => Fix Released
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1694521).
> > https://bugs.launchpad.net/bugs/1688721
> >
> > Title:
> > Packages that trigger multiple debconf prompts fail to install
> >
> > Status in gnome-software package in Ubuntu:
> > Fix Released
> > Status in gnome-software source package in Xenial:
> > Fix Released
> > Status in gnome-software source package in Yakkety:
> > Fix Released
> > Status in gnome-software source package in Zesty:
> > Fix Released
> > Status in gnome-software source package in Artful:
> > Fix Released
> >
> > Bug description:
> > [Impact]
> > Some packages stall on installing. These are packages that generate
> > multiple debconf prompts (the prompts may be empty and so not user
> visible,
> > e.g. gconf2-common).
> >
> > [Test Case]
> > 1. Remove gconf2-common (w...

   So far, the solution has been to apply
          sudo dpkg --configure -a
          sudo apt --fix-broken install
          sudo dpkg --configure -a

Which doesn't seem like something that will bring happiness to anyone.
     But the worst is that these solutions have not worked for everyone. A lot of people gave up and had to reinstall. I was left out, for example, and I was killing myself with this problem until I almost reincarnated. I'm sure when I die, I'll be canonized...

  I found ! I found the problem (and a better solution than what the veterans have recommended): Manually installing gconf2-common via dpkg -- which is normally considered dangerous and not recommended because of the risks. dconf2-common is definitely bugged, but it's not empty or false bug reports as some veterans and developers have said out there -- it's much more serious : The configuration is incomplete and errors go up to initramfs, which accumulates errors, until installation break. this accumulation even prevents the complete and correct installation of packages in the following updates, and these errors also go up to Initramfs, in a vicious circle that ends up breaking the installation. And the unfortunate gconf-service-backend and gconf-service have a circular dependency between them. In short, gconf is all shit by sheer sloppiness of the developer. A mistake is fine, but 2, including circular dependency is just plain sloppiness, really, indefensible! The difficulty here is "Dreadful" level. But I've had a lot of practice installing packages by hand, since the time of the legendary Build-Essential bug in Trusty Tahr, which broke the system every time you tried to install the damn thing, and took 2 years to solve... challenge, and I had to download all the packages by hand and install them one-by-one, in order of dependencies, until I found the bugs. More than 20 depes... At the time, the bugs were, for example: a circular dependency on libc++-6-dev, and a dependency on it that was rotten and had to install the Lucid version, a brutal downgrade, 2 versions below. It was a school! I applied the same method here, although I don't miss the thing at all. The trick itself is to download the dependencies and place them in individual numbered folders, following the order they were installed in the dependency chain, and then open a terminal in each one and apply the dreaded "sudo dpkg --force-breaks -i *". This option is very dangerous, and it takes a lot of marijuana to face this adventure... So I first test with the "sudo dpkg -i *" version to see if there are any other pending dependencies. When approved, then yes, I reinstall with the option sudo dpkg --force-breaks -i * to ensure the package configuration without false or "semi-false" error warnings (which look fake, but generate errors in the initramfs ). The package gconf2-common can only be installed by this option in a folder ONLY with it. Otherwise, it is unconfigured, and it fucks all dependents of it that comes after... The option * should install all the packages that are in the folder together. But the new version of dpkg has one of those security features of dubious utility, which allows you to...

    And just to embitter a bit, on Debian, there are complaints about this bug dating back 3 years...