*** This bug is a duplicate of bug 1679435 ***
https://bugs.launchpad.net/bugs/1679435
If this is gnome-software, then this should be fixed already in gnome-
software 3.20.1+git20170427.0.3d09239-0ubuntu1~xenial1
** This bug has been marked a duplicate of bug 1679435
GNOME Software fails
** Description changed:
During a software upgrade, process was stuck on php7.0-xml configuration
for 20 minutes, after that I killed the process. I am not sure what
additional info are required, will be happy to provide any.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package:
Actually, I'm not convinced that update-manager is the front end in use
here. If we look at the JournalErrors.txt file attached to this bug we
can see the following:
dic 02 09:33:40 hostname org.debian.apt[871]: 09:33:40 AptDaemon [INFO]:
Initializing daemon
dic 02 09:33:40 hostname
** Changed in: php7.0 (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: update-manager (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: debconf (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: samba (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: php7.0 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: debconf (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: update-manager (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: samba (Ubuntu)
Status: Confirmed => Fix Released
This happened to me yesterday on a 16.04 desktop system using update-
manager. Apparently failed during setup of package unattended-upgrades.
Below is apt/history.log, apt/term.log, ps and debconf version taken
while the GUI has been hanging (greyed out and unresponsive) for ~15
hours. GUI
** Changed in: update-manager (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646739
Title:
"Use of uninitialized value" in debconf via
** Changed in: php7.0 (Ubuntu)
Status: Fix Committed => Confirmed
** Changed in: samba (Ubuntu)
Status: Fix Committed => Confirmed
** Changed in: debconf (Ubuntu)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
** Changed in: debconf (Ubuntu)
Status: Invalid => Fix Committed
** Changed in: php7.0 (Ubuntu)
Status: Invalid => Fix Committed
** Changed in: samba (Ubuntu)
Status: Invalid => Fix Committed
** Changed in: update-manager (Ubuntu)
Status: Confirmed => Fix Released
@Alberto,
why did you mark the samba task critical? As far as I can tell, there is
no bug in samba itself, all of these bugs are in update-manager and just
have been seen with various binary packages which we're marking this bug
and then indicating they are invalid.
** Changed in: samba (Ubuntu)
@Alberto,
why did you mark the samba task critical? As far as I can tell, there is
no bug in samba itself, all of these bugs are in update-manager and just
have been seen with various binary packages which we're marking this bug
and then indicating they are invalid.
** Changed in: samba (Ubuntu)
** Changed in: samba (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646739
Title:
"Use of uninitialized value" in debconf via update-manager
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646739
Title:
FYI as nacc asked, I added samba task to reflect that it showed up there
as well (I dupped another case onto this).
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: rls-aa-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646739
Title:
"Use of uninitialized value" in debconf via update-manager
To manage notifications about this bug go to:
@es20490446e: how can you have a Critical Invalid bug?
Also, "Critical" is listed as "Fix now or as soon as possible". Except
we don't have a reproducible test case and there is a fairly easy
workaround (and probably most server users are actually unaffected by
this as they are GUI-free). This
** Changed in: update-manager (Ubuntu)
Importance: Undecided => Critical
** Changed in: php7.0 (Ubuntu)
Importance: High => Critical
** Changed in: debconf (Ubuntu)
Importance: Undecided => Critical
** Changed in: php7.0 (Ubuntu)
Status: Confirmed => Invalid
** Changed in:
** Summary changed:
- package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 128
+ "Use of uninitialized value" in debconf via update-manager
--
You received this bug notification because you are a member
18 matches
Mail list logo
