[Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2022-01-15 Thread invernosantigos
And just to embitter a bit, on Debian, there are complaints about this bug 
dating back 3 years...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2022-01-15 Thread invernosantigos
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 install 
a maximum of 3 depes together at once with this option (using the * replaces 
the package name -- instead of typing each name one- by one, with risk of 
error, we use *, in place of the name of the packages and dpkg installs all the 
dependencies that are in the folder ). Then you have to install 
gconf-service-backend and gconf-service TOGETHER in the same folder, folder 2, 
BECAUSE IT HAS CIRCULAR DEPENDENCE, and it is only possible to install circular 
dependency without breaking with "sudo dpkg --force-breaks - i *" and installed 
both together at the same time. Finally, in a third folder and with a third 
terminal, we install gconf2. If after all this installation you test with "sudo 
dpkg --configure -a" in a terminal, there is no response back, because there is 
no more configuration of pending files.

Well, that's all (Whew...) but the really bad thing is that you can't do it 
in a virtual machine, you have to risk your neck. Why ? Because this type of 
bug, like many others, tends not to happen with a fresh install, just a few 
updates after installing gconf2-commom bugs. If you install everything in one 
session, no problem, but after you update dpkg and restart the machine, the new 
version of dpkg -- much more error intolerant -- bugs gconf2-common... That's 
why I said it was the developer's unforgivable sloppiness: He wrote the package 
triggers for the system's native install dpkg version (the install CdRom) but 
not for the working version, the current version of dpkg. So, on the first 
update, it fucked up!

An eternal classic of this type of error, are the appimage packages, WHICH 
DOES NOT WORK IN LINUX MINT after some updates... They are simply not 
recognized as executables, no matter how 

Re: [Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2017-12-04 Thread Mac Abdul
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 <
1688...@bugs.launchpad.net> 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: boun...@canonical.com  em nome de Mac Abdul <
> 1688...@bugs.launchpad.net>
> Enviado: quinta-feira, 6 de julho de 2017 08:45:19
> Para: carlosbenevid...@hotmail.com
> 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 <
> 1688...@bugs.launchpad.net> 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   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 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
> >
>
>
> ** Attachment added: "Screenshot from 2017-07-06 15-34-29.png"
>https://bugs.launchpad.net/bugs/1688721/+attachment/
> 4910281/+files/Screenshot%20from%202017-07-06%2015-34-29.png
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1701257).
> 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 

Re: [Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2017-07-06 Thread carlos roberto alves benevides
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: boun...@canonical.com  em nome de Mac Abdul 
<1688...@bugs.launchpad.net>
Enviado: quinta-feira, 6 de julho de 2017 08:45:19
Para: carlosbenevid...@hotmail.com
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 <
1688...@bugs.launchpad.net> 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   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
>


** Attachment added: "Screenshot from 2017-07-06 15-34-29.png"
   
https://bugs.launchpad.net/bugs/1688721/+attachment/4910281/+files/Screenshot%20from%202017-07-06%2015-34-29.png

--
You received this bug notification because you are subscribed to a
duplicate bug report (1701257).
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 

Re: [Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2017-07-06 Thread Mac Abdul
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 <
1688...@bugs.launchpad.net> 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   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
>


** Attachment added: "Screenshot from 2017-07-06 15-34-29.png"
   
https://bugs.launchpad.net/bugs/1688721/+attachment/4910281/+files/Screenshot%20from%202017-07-06%2015-34-29.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2017-06-29 Thread Launchpad Bug Tracker
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   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 a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2017-06-29 Thread Launchpad Bug Tracker
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   Wed, 24 May 2017
09:49:56 +1200

** Changed in: gnome-software (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
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 Committed
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2017-06-29 Thread Launchpad Bug Tracker
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   Wed, 24 May 2017
09:49:56 +1200

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
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 Committed
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2017-06-27 Thread Jeremy Bicha
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


** Tags removed: verification-needed
** Tags added: verification-done-xenial verification-done-yakkety

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
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 Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2017-06-27 Thread Jeremy Bicha
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.

** Tags added: verification-done-zesty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
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 Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2017-06-21 Thread Brian Murray
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!

** Changed in: gnome-software (Ubuntu Zesty)
   Status: Incomplete => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
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 Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2017-06-20 Thread Robert Ancell
Yeah, this is just a typo copying the changelog from a artful back to
zesty. The fix is in the 0002 patch.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
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 Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Incomplete
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2017-06-16 Thread Brian Murray
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!

** Changed in: gnome-software (Ubuntu Zesty)
   Status: Fix Committed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
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 Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Incomplete
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2017-06-15 Thread Brian Murray
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!

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
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 Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2017-05-26 Thread Pier Luigi Bonucci
Sorry, I can't understand how to fix the bug. Can you clarify me what to
do?

Pier Luigi Bonucci

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
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 Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

2017-05-24 Thread Iain Lane
Well done!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
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 Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp