It is quite strange but it is not an unattended-upgrades bug. Do you
still observe it?
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Reassigning to update-manager since it started the installation, u-u
does not seem to be at fault here.
** Package changed: unattended-upgrades (Ubuntu) => update-manager
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
I agree that it should be fixed in u-u. Patches are welcome.
** Changed in: unattended-upgrades (Ubuntu)
Importance: Medium => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583537
Title:
Fixed in this commit: https://github.com/mvo5/unattended-
upgrades/commit/7c5e5476711fab6b9977116792262e16efe626ec
** Changed in: unattended-upgrades (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Debconf executes scripts from /tmp by default but you can try continuing
securing the system by changing apt's temp file configuration:
https://serverfault.com/questions/72356/how-useful-is-mounting-tmp-noexec
Anyway this is definitely not a bug in u-u, maybe a wishlist one for
debconf.
** Chang
** Changed in: aptdaemon
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276777
Title:
aptdaemon ftbfs in trusty (test failures)
To manage notifications about this
Unattended-upgrade uses ufc(1) to manage the related conffiles and ucf
creates those copies during the update.
Starting with u-u 1.4 README.md recommends creating separate
configuration files in /etc/apt/apt.conf.d to avoid updates to conflict
with local changes.
Latest apt ignores the .ucf-* fil
Verified with 1:16.04.15 on Xenial.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Verified with 1:16.04.15 on Xenial.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Marking the bug as invalid for later releases because we don't exercise
this code upgrade path in later releases and in later releases lazy
loading of the backend code is fixed in LP: #1795898.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Verified with 1:16.04.15 on Xenial.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
** Changed in: update-manager (Ubuntu)
Status: New => Fix Released
** Changed in: update-manager (Ubuntu)
Status: Fix Releas
Verified with 1:16.04.15 on Xenial. With 1:16.04.14 the verification
steps still trigger the blank list.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ub
@u-karl Thanks for the follow-up, closing this bug then.
** Changed in: wireshark (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800071
Title:
Wireshark fails
** Description changed:
[Impact]
* When Secure Boot is enabled and MOK is not set and a new dkms module
is installed sim-signed asks for a Secure Boot MOK, or aborts package
installation in non-interactive mode. When unattended-upgrades performed
the upgrade the aborted installation
** Summary changed:
- After doing updates, update manager propose to install an empty list of
updates
+ [FFe] After doing updates, update manager propose to install an empty list of
updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Summary changed:
- Can't select only kernel package removals when other updates are present
+ [FFe] Can't select only kernel package removals when other updates are present
** Patch added:
"0001-Allow-unselecting-updates-and-performing-only-remova.patch"
https://bugs.launchpad.net/ubuntu/
** Patch added:
"0003-Keep-or-delete-packages-after-looping-over-all-of-th.patch"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1072136/+attachment/5195292/+files/0003-Keep-or-delete-packages-after-looping-over-all-of-th.patch
--
You received this bug notification because you
Public bug reported:
There are many PEP 8 warnings when running:
autopkgtest update-manager -U -- lxd autopkgtest/ubuntu/cosmic/amd64
...
autopkgtest [14:27:57]: test nose-tests: [---
(nosetests3:3729): dbind-WARNING **: 12:27:58.256: Error retrieving
accessibility bus addre
** Patch added: "0004-Fix-PEP-8-warnings.patch"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1795384/+attachment/5195294/+files/0004-Fix-PEP-8-warnings.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Public bug reported:
Lock() can succeed when update-manager is ran as root (not recommended
and not done by default) potentially taking the lock blocking other dpkg
frontends.
Update-manager is typically ran as a normal user thus lock operations
fail and are ignored already.
Dropping the locking
** Patch added:
"0002-Stop-trying-apt_pkg.pkgsystem_-un-lock-as-a-normal-u.patch"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1795387/+attachment/5195295/+files/0002-Stop-trying-apt_pkg.pkgsystem_-un-lock-as-a-normal-u.patch
--
You received this bug notification because you
** Branch linked: lp:~rbalint/update-manager/no-apt-lock
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795387
Title:
[FFe] Stop trying apt_pkg.pkgsystem_(un)lock()
To manage notifications about th
** Branch linked: lp:~rbalint/update-manager/fix-pep8-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795384
Title:
[FFe] Autopkgtest fails with cosmic's pep8
To manage notifications about th
** Description changed:
- Frontend lock support for apt and dpkg is tracked in LP: #1781169, this
- bug tracks unattended-upgrades changes
+ [Impact]
+
+ Apt and dpkg implemented the Frontend Locking API and unattended-
+ upgrades needs to adopt it to not leave the packaging system unlocked
+ whi
Public bug reported:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py",
line 242, in _on_finished
trans_failed=trans_failed)
TypeError: _action_done() got an unexpected keyword argument 'trans_failed'
** Affects: upd
** Branch linked: lp:~rbalint/update-
manager/lp-1795898-lp-1790670-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795898
Title:
TypeError: _action_done() got an unexpected keyword argument
** Branch linked: lp:~rbalint/update-
manager/lp-1795898-lp-1790670-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790670
Title:
/usr/bin/update-
manager:aptdaemon.errors.AptDaemonError(or
** Description changed:
+ [Impact]
+ Lazy imports made update-manager crash when an update-manager
+ update changed the backend API and an updated incompatible backend
+ was loaded to the not updated running update-manager process.
+
+ The issue causes crashes upon update-manager updates harmi
** Description changed:
+ [Impact]
+
+ Closing the GUI of update-manager tries to cancel the running
+ transaction then raises an Exception since cancellation fails.
+
+ Users experience crashes after closing the GUI and many of them send
+ error reports about the issue while nothing can be done
** Branch linked: lp:~rbalint/update-
manager/lp-1795898-lp-1790670-lp-1072136-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795898
Title:
TypeError: _action_done() got an unexpected keyword
** Branch linked: lp:~rbalint/update-
manager/lp-1795898-lp-1790670-lp-1072136-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790670
Title:
/usr/bin/update-
manager:aptdaemon.errors.AptDae
** Branch linked: lp:~rbalint/update-
manager/lp-1795898-lp-1790670-lp-1072136-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1072136
Title:
[FFe] After doing updates, update manager propose t
@rbasak If unattended-upgrades runs at the same time as software updater
is updating apt caches then unattended upgrades crashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795614
Title:
package
Tested 20180905+dfsg1-0ubuntu1~14.04.0 on Trusty:
root@t:~# apt show gce-compute-image-packages | grep rsyslog
WARNING: apt does not have a stable CLI interface yet. Use with caution
in scripts.
Recommends: rsyslog | system-log-daemon
** Tags removed: verification-needed verification-needed-tr
** Branch linked: lp:~rbalint/update-manager/lp-1795898-upgrade-
workaround
** Branch linked: lp:~rbalint/update-manager/lp-1795898-upgrade-
workaround-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Description changed:
+ [Impact]
+
+ The backend API change made update-manager crash when the updated
+ incompatible backend was loaded to the not updated running update-
+ manager process.
+
+ The issue causes crashes upon update-manager updates harming the upgrade
+ experience for users.
+
** Description changed:
+ [Impact]
+
+ An empty list of updates is shown to the user when phased updates
+ depending on each other are kept back from installation.
+
+ The blank list confuses users.
+
+ [Test Case]
+
+ 1. Start with a fully upgraded system and downgrade a few phased
interdepe
** Description changed:
[Impact]
- unattended-upgrades does not work (reliably) in (bionic and) cosmic with the
mirror:// method, as it tries to open the mirror file - which recent apt
versions store in auxfiles - as a .deb:
+ unattended-upgrades does not work (reliably) in (bionic and) cos
*** This bug is a duplicate of bug 1072136 ***
https://bugs.launchpad.net/bugs/1072136
** This bug has been marked a duplicate of bug 1072136
[FFe] After doing updates, update manager propose to install an empty list
of updates
--
You received this bug notification because you are a memb
** Changed in: shim-signed (Ubuntu)
Status: Triaged => In Progress
** Changed in: shim-signed (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact] (WIP)
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [T
** Description changed:
- [Impact] (WIP)
+ [Impact]
- * An explanation of the effects of the bug on users and
+ * When Secure Boot is enabled and a new dkms module is installed sim-
+ signed asks for a new Secure Boot key, or aborts package installation in
+ non-interactive mode. When unatten
@vorlon My bad, thought that a generic solution would be useful in u-u,
but now I'm implementing now the special case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726803
Title:
unattended-upgrade
** Description changed:
[Impact]
* Unattended-upgrades may keep running during shutdown even beyond
unmounting local filesystems potentially leaving a broken installation behind.
* The fix reverts the original fix of LP: #1778219 and applies a different
one startin unattended-upgrades
** Also affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803168
Title:
package udev 229-4ubuntu21.8 failed to install/
*** This bug is a duplicate of bug 1778219 ***
https://bugs.launchpad.net/bugs/1778219
** This bug has been marked a duplicate of bug 1778219
unattended-upgrades hangs on shutdown, leaves system in a broken state
--
You received this bug notification because you are a member of Ubuntu
Bug
Public bug reported:
Installation of latest systemd update in -security hangs with current
versions of unattended-upgrades in supported releases. The u-u-side fix
is tracked in LP: #1778219.
Reproduction:
rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown
Creating uu-systemd-onshutdow
systemctl(1) does not say that try-restart must not hang and --no-block
in maintainer scripts would make maintainer scripts continue and execute
actions in highly unpredictable states.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** This bug is no longer a duplicate of bug 1778219
unattended-upgrades hangs on shutdown, leaves system in a broken state
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803168
Title:
package ude
** Patch added:
"0001-debian-systemd.postinst-Skip-daemon-reexec-and-try-r.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1803391/+attachment/5212859/+files/0001-debian-systemd.postinst-Skip-daemon-reexec-and-try-r.patch
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1778219 ***
https://bugs.launchpad.net/bugs/1778219
Since this issue is marked as invalid for linux i'm setting it as a
duplicate of the u-u bug where SRU-ing the fix is tracked.
** This bug has been marked a duplicate of bug 1778219
unattended-upgrades h
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803168
Title:
package udev 229-4ubuntu21.8 failed to install/upgrade: subproc
** Changed in: unattended-upgrades (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734285
Title:
unattended-upgrades.service ignores (changes in)
/et
** Description changed:
[Impact]
* Unattended-upgrades may keep running during shutdown even beyond
unmounting local filesystems potentially leaving a broken installation behind.
- * The fix reverts the original fix of LP: #1778219 and applies a different
one startin unattended-upgrades
Public bug reported:
When a user logged in to the GUI session and she/he request shutdown of
the system a PrepareForShutdown() signal is emitted by logind:
https://www.freedesktop.org/wiki/Software/systemd/inhibit/
Processes holding delay inhibitor locks can start their pre-shutdown
operations a
** Description changed:
[Impact]
* Unattended-upgrades may keep running during shutdown even beyond
unmounting local filesystems potentially leaving a broken installation behind.
* The fix reverts the original fix of LP: #1778219 and applies a different
one starting unattended-upgrade
Could you please attach the relavant part of dpkg history log a and dpkg
terminal log?
It is possible, that the last run of u-u/u-m installed kernel packages
triggering /etc/kernel/postinst.d/apt-auto-removal which resulted
kernels to be removed in the _next_ apt/u-u/u-m run.
--
You received thi
Public bug reported:
While triaging LP: #1803587 I found that originally autoremovable
packages were handled as newly autoremovable ones by unattended-upgrades
due to not finding all of them at the beginning of u-u's run.
The root cause seems to be cache.clear() resetting pkg.is_auto_removable
to
@vorlon: OK, let's use this bug to track the improvement for u-m.
While triaging I found LP: #1803749 , which you may have hit if you have
Unattended-Upgrade::Remove-New-Unused-Dependencie set to False. Is that
the case on your system?
--
You received this bug notification because you are a memb
@vorlon: OK, being commented out (and not set elsewhere) makes it default to
True.
The misleading comment is fixed in later releases.
** Changed in: update-manager (Ubuntu)
Importance: Undecided => Wishlist
** Summary changed:
- kernel from bionic did not get autoremoved by either unattended
In my tests u-u successfully removed the kernels as new unused packages
even when hitting LP: #1803749 for the record.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803587
Title:
Update-manager doe
Public bug reported:
app crashed after close
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: wireshark-qt 2.6.3-1~ubuntu14.04.1
ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
Uname: Linux 3.16.0-77-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd6
This is also reported as an error many times:
https://errors.ubuntu.com/problem/ac9b86e48c6b6b5792c1128a836ba63213d62b44
One workaround I found was installing gtk2-engines-oxygen, with this
package present the Qt interface does not crash on Trusty.
** Description changed:
app crashed after clo
The crash is observed only in the Unity session.
** Summary changed:
- wireshark crashed with SIGSEGV in QIcon::~QIcon()
+ wireshark crashed with SIGSEGV in QIcon::~QIcon() under Unity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I reported the GDM issue upstream, but LP does not handle Gitlab URLs
yet: https://gitlab.gnome.org/GNOME/gdm/issues/443
** Description changed:
When a user logged in to the GUI session and she/he request shutdown of
the system a PrepareForShutdown() signal is emitted by logind:
https://
** Package changed: unity (Ubuntu) => appmenu-qt5 (Ubuntu)
** Changed in: appmenu-qt5 (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803808
Title:
wireshark
A possible other workaround that works on Xenial, too, is removing the
appmenu-qt5 package until appmenu-qt5 is fixed.
** Changed in: wireshark (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
@mikesalvatore: I have uploaded the backported packages to:
https://launchpad.net/~rbalint/+archive/ubuntu/wireshark-sru/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801666
Title:
FTBFS
The bug seems to be in appmenu-qt rather than in Wireshark.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803808
Title:
wireshark crashed with SIGSEGV in QIcon::~QIcon() under Unity
To manage noti
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803391
Title:
Systemd update installation hangs in unattended-upgr
Progress
** Changed in: unattended-upgrades (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
** Changed in: unattended-upgrades (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The upgrade on Xenial fails in udev.postint, the attached patch should
fix that. (Under test)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803391
Title:
Systemd update installation hangs in unatte
Should better be this patch.
** Patch added:
"0001-debian-udev.postinst-Don-t-always-trigger-systemctl-.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1803391/+attachment/5214307/+files/0001-debian-udev.postinst-Don-t-always-trigger-systemctl-.patch
--
You received this bug n
** Patch removed:
"0001-debian-udev.postinst-Don-t-always-trigger-systemctl-.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1803391/+attachment/5214307/+files/0001-debian-udev.postinst-Don-t-always-trigger-systemctl-.patch
** Patch added:
"0001-debian-udev.postinst-Don-t-alway
That last patch works for me on Xenial and fixes the upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803391
Title:
Systemd update installation hangs in unattended-upgrades
InstallOnShutdow
: High
Assignee: Balint Reczey (rbalint)
Status: In Progress
** Changed in: rax-nova-agent (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
** Changed in: rax-nova-agent (Ubuntu)
Status: New => In Progress
** Changed in: rax-nova-agent (Ubuntu)
Importance:
** Changed in: rax-nova-agent (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** Changed in: rax-nova-agent (Ubuntu Artful)
Status: Fix Committed => Won't Fix
** Changed in: rax-nova-agent (Ubuntu)
Status: New => Fix Released
--
You received this bug notification beca
** Description changed:
+ [Impact]
+
+ * Originally autoremovable packages can be removed as newly autoremovable
ones by unattended-upgrades
+ * This can surprise users potentially removing packages which are needed for
the system's operation.
+
+ [Test Case]
+
+ * WIP, see Original Bug Te
@slashd (and all) the fix caused regressions elsewhere and it is being
partially reverted and the issue is fixed in a different way. Please
don't backport the current fix.
The candidate for fixing the issue without the regressions introduced:
https://github.com/mvo5/unattended-upgrades/pull/148
Verified with shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1:
...
ubuntu@autopkgtest:/var/cache/apt/archives$ sudo rm
/var/lib/shim-signed/mok/MOK.der
ubuntu@autopkgtest:/var/cache/apt/archives$ sudo update-secureboot-policy
--new-key
Generating a new Secure Boot signing key:
Generati
*** This bug is a duplicate of bug 1726803 ***
https://bugs.launchpad.net/bugs/1726803
Thanks for the bug report. The next version of shim-signed contains the
fix and it is tracked under LP: #1726803.
** This bug has been marked a duplicate of bug 1726803
unattended-upgrades + nvidia stac
Unattended-upgrade uses ufc(1) to manage the related conffiles and ucf
creates those copies during the update.
Starting with u-u 1.4 README.md recommends creating separate
configuration files in /etc/apt/apt.conf.d to avoid updates to
conflict with local changes.
Latest apt ignores the .ucf-* file
This occurs when the configuration contains invalid data.
** Changed in: unattended-upgrades (Ubuntu)
Importance: Undecided => Low
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
** Summary changed:
-
/usr/bin/unattended-upgrade:ValueError:/usr/bin/unattended-upg
The bug here is that debconf can't connect to the X server to ask the user
about replacing u-u's configuration file.
While this is not a bug in unattended-upgrades, u-u 1.8 will include a fix to
avoid triggering the debconf question when the configuration file is intact:
https://github.com/mvo5/u
** Changed in: unattended-upgrades (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autoremove may remove current kernel
To manag
The first error in DpkgTerminalLog.txt:
Configurando samba-common (2:4.7.6+dfsg~ubuntu-0ubuntu2.2) ...
dpkg: erro ao processar o pacote samba-common (--configure):
installed samba-common package post-installation script subprocess returned
error exit status 10
Configurando libgdm1 (3.28.3-0ubunt
@paelzer: The FTBFS is caused by libwireshark-dev missing dependency on
libwiretap-dev and the fix is this:
https://salsa.debian.org/debian/wireshark/commit/e774085a2a363f43d4e4b437f065077f1d737cf4
I just uploaded 2.6.4-2 that can be backported to Bionic and Xenial or I can
cherry-pick the change
** Summary changed:
-
/usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended-upgrade@2005:main:mark_upgrade_adjusted:call_adjusted
+ Unhandled NoAllowedOriginError when checking black- and whitelist
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Fixed in u-u 1.6.
** Changed in: unattended-upgrades (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599646
Title:
E-mail report contains repeat
*** This bug is a duplicate of bug 1638234 ***
https://bugs.launchpad.net/bugs/1638234
** This bug has been marked a duplicate of bug 1638234
package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade:
subprocesso script post-installation instalado retornou erro do status de saída
*** This bug is a duplicate of bug 1638234 ***
https://bugs.launchpad.net/bugs/1638234
** This bug has been marked a duplicate of bug 1638234
package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade:
subprocesso script post-installation instalado retornou erro do status de saída
*** This bug is a duplicate of bug 1638234 ***
https://bugs.launchpad.net/bugs/1638234
** This bug has been marked a duplicate of bug 1638234
package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade:
subprocesso script post-installation instalado retornou erro do status de saída
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706530
Title:
package vlc-nox 2.2.2-5ubuntu0.16.04.2 failed to install/upg
*** This bug is a duplicate of bug 1322382 ***
https://bugs.launchpad.net/bugs/1322382
This is an apt resolver issue. There are several bugs reported against
apt's resolver and I picked one as the duplicate.
Traceback
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", l
The fix is already released in 1.7ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803137
Title:
Unattended-upgrades may keep running after unmounting local
filesystems in InstallOnShutdown
devices.list: Operation not permitted
Nov 13 12:42:02 cc-uu-onshutdown systemd[1]: Starting Unattended Upgrades
Shutdown...
..
** Affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Assignee: Balint Reczey (rbalint)
Status: Fix Released
** Changed in: unattended-upgr
For the record the shim-signed fix alone is enough to fix the reported
issue, i.e. installation failing when the nvidia module changes dirs.
The u-u fix is an attempt to fix the generic case, when an update brings
in a new dkms module, but this is not happening in the archive at the
moment and is
** Description changed:
[Impact]
- * Unattended-upgrades may keep running during shutdown even beyond
unmounting local filesystems potentially leaving a broken installation behind.
- * The fix reverts the original fix of LP: #1778219 and applies a different
one startin unattended-upgrades
*** This bug is a duplicate of bug 1317164 ***
https://bugs.launchpad.net/bugs/1317164
** This bug is no longer a duplicate of private bug 1203562
** This bug has been marked a duplicate of bug 1317164
Show reason of TransactionFailed and let the user try again instead of
crashing
--
You
*** This bug is a duplicate of bug 1317164 ***
https://bugs.launchpad.net/bugs/1317164
** This bug is no longer a duplicate of private bug 1203562
** This bug has been marked a duplicate of bug 1317164
Show reason of TransactionFailed and let the user try again instead of
crashing
--
You
501 - 600 of 3234 matches
Mail list logo
