Hmm odd maybe something's in the journal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790613
Title:
Regression: packagekit crashes updating itself to
1.1.9-1ubuntu2.18.04.1
To manage notificati
All I can say: If you treat USN reports as binaries then you are
definitely missing security updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788486
Title:
apt behaviour when package with str
I mean, consider the apt one. It lists apt, but the fix is in the binary
libapt-pkg5.0.
I assume you can specify --only-upgrade or what it's called too to
prevent removals (but also new installs). In any case, there is no
solution here.
--
You received this bug notification because you are a mem
** Also affects: packagekit (Ubuntu Bionic)
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/1790671
Title:
/usr/lib/packagekit/packagekitd:11:std::__cxx11:
systemd pull request: https://github.com/systemd/systemd/pull/10033
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787495
Title:
no explanation for the events in the networkd-dispatcher manpage
To
packagekit postinst is restarting packagekit:
deb-systemd-invoke try-restart 'packagekit-offline-update.service'
'packagekit.service'
so yes, that's what's causing the issue. I don't think I agree with the
importance High, though. PackageKit is not normally used for upgrading,
only for installing
Public bug reported:
See attached screenshot. If I search for Downloads, I also get symlinks
to ~/Downloads generated in ~/snap/spotify/16/Downloads, for example.
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Affects: tracker (Ubuntu)
Importance: Undeci
** Attachment added: "Screenshot from 2018-09-07 13-32-59.png"
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1791289/+attachment/5186007/+files/Screenshot%20from%202018-09-07%2013-32-59.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787495
Title:
no explanation for the events in the networkd-dispatcher manpage
To ma
I could successfully chainload grub from shim by using virtio-net and
disabling iPXE. Minimal reproducer:
sudo kvm -bios /usr/share/OVMF/OVMF_CODE.fd -device virtio-net,netdev=n1
-netdev user,id=n1,tftp=/boot/efi/EFI/ubuntu,bootfile=shimx64.efi
-global virtio-net-pci.romfile=""
if I remove the la
Thanks Laszlo, ipxe built with CONFIG=qemu successfully makes shim load
grub.
** Changed in: shim (Ubuntu)
Status: Triaged => Invalid
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: ipxe (Ubuntu)
Status: Triaged => In Progress
--
You received this
I just uploaded -0ubuntu4 (and -0ubuntu3 earlier to fix FTBFS), that
enables CONFIG=qemu for our qemu roms. This means QEMU will work fine,
but grub/efi binaries and the CD-ROM images would still fail to load
grub via shim I think. Not sure there's much that can be done there.
** Changed in: ipxe
** Changed in: ipxe (Ubuntu Bionic)
Status: New => In Progress
** Description changed:
- libvirt supports creating virtual machines running in UEFI mode and uses
- iPXE to enable network booting. When MAAS gives shimx64.efi, as it does
- on all UEFI systems, to iPXE it chainloads grub but
Yes, I think there's a bug in the iPXE network driver, but now it only
applies to bare-metal users essentially. If that is a problem to anyone
in practice, I'd suggest opening a new bug for that (or directly going
upstream, maybe); so we can use this one to track the fix for MAAS VM
stuff.
--
You
Ugh. Let's try to make this clear. Nothing here does http boot. There
are three scenarios, all do PXE TFTP booting:
(1) iPXE network stack replaces firmware one - caused this bug
(2) iPXE without replacing firmware's network stack (CONFIG=qemu) - this works
fine
(3) No iPXE, use OVMF's native imp
JFTR, in case anyone is looking at this:
The fix for xenial and trusty has been merged into the fix for 1737441,
and was fixed there, as the regression that manifested in this bug due
to the fix for 1737441 never manifested in those releases, as there was
no upload with just that fix.
--
You rec
Verified that -ubuntu2 fails and -ubuntu2.1 from proposed works by
running the command specified in the test case in a bionic system.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification be
Seems to be fixed upstream in 3.0.8, possibly earlier; which is in
cosmic
** Changed in: gnu-efi (Ubuntu)
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/1741996
Titl
I don't think there is a solution for this problem. We can stop
restarting packagekit to fix the crash, but then you end up with old
packagekitd's running. So if there is a security update in packagekit or
one of its libraries, it would not take effect. Not sure how to fix this
properly.
--
You r
Of course we do:
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" =
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
if [ -n "$2" ]; then
The default changed to restart in debhelper 10. I think we need (one
of?) --no-restart-on-upgrade --no-restart-after-upgrade passed to
dh_installsystemd.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.n
Putting this on hold a bit; once we have a fix for the other PackageKit
bug in the SRU queue, so we don't cause breakage again.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launch
Public bug reported:
[Impact]
networkd-dispatcher in bionic does not support overriding scripts or placing
custom scripts in /etc, making it not configurable for a system administrator
[Test case]
1. Check that /etc/networkd-dispatcher/$event/$foo overrides
/usr/lib/networkd-dispatcher/$event/$
** Description changed:
+ [Impact]
Bionic: 18.04
Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1
Updating with pkcon upgrade or plasma-discover crashes packagekit mid
transaction, requiring user intervention on the command line.
In plasma-discover the gui reports
FWIW, the option to pass is --no-restart-after-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790613
Title:
Regression: packagekit crashes updating itself to a new version
To manage notific
Uploaded, both in unapproved
** Changed in: packagekit (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: packagekit (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: packagekit (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notifi
xenial
==
With 1.2.27
---
root@glowing-mastodon:~# python3 a.py
total 0
[...]
lrwx-- 1 root root 64 Oct 18 12:15 3 -> /var/lib/dpkg/lock
l-wx-- 1 root root 64 Oct 18 12:15 6 -> pipe:[27632799]
Reading package lists... Done
Building dependency tree
Reading state informat
The included autopkgtest has successfully passed for both 1.6.6/bionic
and 1.2.29/xenial
** Tags removed: verification-needed verification-needed-bionic
verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-xenial
--
You received this bug notifi
bionic (1.6.3ubuntu0.1 -> 1.6.6):
root@dashing-panda:~# python3 a.py
total 0
[...]
lrwx-- 1 root root 64 Oct 18 12:07 3 -> /var/lib/dpkg/lock
l-wx-- 1 root root 64 Oct 18 12:07 6 -> 'pipe:[27578280]'
Reading package lists... Done
Building dependency tree
Reading state information..
Marking verification-done-xenial again, this got reset by 1.2.29.
FWIW; I also retested: after upgrading apt to 1.2.29 in the xenial
container, and rerunning the kernel hook that creates the file, I also
see
"^linux-cloud-tools-4\.18\.0-8-generic$";
in the list.
** Tags removed: verificatio
apt 1.6.6 from bionic: I verified that lock-frontend was opened and
locked at the beginning, that lock was locked after it, lock released
before dpkg is called, and that lock-frontend was not released until the
end.
[...]
openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW,
The specified tests passed on both:
bionic (1.6.6):
(187/248) Testcase test-frontend-lock: P P P P P P P P P P P P P P P P
P P P P P P P P P P P P P P P P P P P P P P
xenial (1.2.29):
(165/220) Testcase test-frontend-lock: P P P P P P P P P P P P P P P P
P P P P P P P P P P P P P P P P P P P
Same with 1.2.29 from xenial:
open("/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
fcntl(4, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
open("/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5
fcntl(5,
Well, timing broke the test - it no longer fails in the unfixed version.
ugh.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790671
Title:
/usr/lib/packagekit/packa
But well, the verification of 2.18.04.2 is still valid, the change to
the postinst does not invalidate it, so let's ignore that I'm not lucky
enough to end up with a broken apt cache.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done
>From release to updates:
# pkcon install packagekit
Resolving [=]
Testing changes [=]
Finished [ ] (0%)
The following packages have to be updated:
pa
(that was 1.1.9-1ubuntu2.18.04.3 in bionic)
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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:
packagek
I verified by creating a prerm script for packagekit-tools with sleep 20
in it, and then looked at the locks while that was sleeping:
# lslocks
COMMAND PID TYPE SIZE MODE M START END PATH
cron 415 FLOCK 4B WRITE 0 0 0 /run/crond.pid
packagekitd 3374 POSIX 0B
Same on xenial (0.8.17-4ubuntu6~gcc5.4ubuntu1.4):
root@xxx:~# lslocks
COMMAND PID TYPE SIZE MODE M START END PATH
iscsid396 POSIX 4B WRITE 0 0 0 /run/iscsid.pid
atd 390 POSIX 4B WRITE 0 0 0 /run/atd.pid
cron 392 FLOCK 4B WRITE 0
Before:
1. with /var/lib/dpkg/lock locked:
dpkg: error: dpkg status database is locked by another process
2. with lock-frontend locked (not yet recognized):
dpkg: error: --install needs at least one package archive file argument
3. same as 2
after upgrade to 1.18.4ubuntu1.5:
1.
root@xxx:~#
Same with bionic (1.19.0.5ubuntu2.1)
1. lock locked:
root@bbb:~# dpkg -i /var/cache/apt/archives/dpkg_1.19.0.5ubuntu2.1_amd64.deb
dpkg: error: dpkg status database is locked by another process
2. Frontend locked
root@bbb:~# dpkg -i /var/cache/apt/archives/dpkg_1.19.0.5ubuntu2.1_amd64.deb
dpkg:
bionic 1.6.3:
1. Verified that the lock is hold during dpkg run added lslocks to
aptitude prerm:
$ lxc exec bbb -- strace -o $PWD/log -e openat,open,close,fcntl python3
$PWD/foo.py
(Reading database ... 28970 files and directories currently installed.)
Removing aptitude (0.8.10-6ubuntu1) ...
COM
FTR, with the locking with statement, without the SRU, it fails, as
expected (both in bionic and xenial), e.g.:
dpkg: error: dpkg status database is locked by another process
E:Sub-process /usr/bin/dpkg returned an error code (2)
Traceback (most recent call last):
File "/home/jak/Projects/Ubunt
Same for xenial (1.1.0~beta1ubuntu0.16.04.3).
Also, strace logs look like this, in case we want to see how we can be
sure it's kept locked all the time:
[...]
open("/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 39
fcntl(39, F_SETFD, FD_CLOEXEC) = 0
fcntl(39, F_SETLK, {
** Description changed:
[Impact]
Downloading many packages on archive.ubuntu.com or some other mirrors seems
to close the connection after every 100 or so packages. APT prior to 1.7.0~rc1
(commit df696650b7a8c58bbd92e0e1619e956f21010a96), treats a connection closure
with a 200 response as m
Here is a short graphical comparison of before/after in the bionic SRU
in a container. I modified the container's network bridge to add 300ms
delay using
sudo tc qdisc add dev lxdbr0 root netem delay 300ms
which made things quite more visible on a slower 12 Mbit/s connection.
I could clearly see
Same for xenial; 1.2.27 shows the symptoms, and the 1.2.29 SRU fixes
them. Not going to attach more images or text as it basically looks
identical.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-xenial
** Tags added: verification-done verification-done-bionic
** Attachment added: "bionic: network bandwidth before (1.6.3ubuntu0.1)"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794957/+attachment/5203090/+files/Screenshot%20from%202018-10-19%2015-55-47.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
[Impact]
- networkd-dispatcher in bionic does not support overriding scripts or placing
custom scripts in /etc, making it not configurable for a system administrator
+ networkd-dispatcher in bionic does not support overriding scripts or placing
custom scripts in /etc, m
** Summary changed:
- {SRU] overrides in /etc
+ [SRU] overrides in /etc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797884
Title:
[SRU] overrides in /etc
To manage notifications about this bug
I created three scripts:
(1) override in both /usr and /etc
(2) usr-only in /usr
(3) etc-only in /etc
doing "echo $0 >&2"
and then ran networkd-dispatcher with -T (triggering scripts for current
state) to run them:
# networkd-dispatcher -v -
No valid path found for iwconfig
No valid path fo
I generated a bionic container, and then ran apt upgrade against the
dpkg status file in it, that is:
lxc exec splendid-flea -- apt -o Dir::State::Status=$PWD/var/lib/apt-
clone/dpkg-status dist-upgrade
I have the -proposed repository enabled and pinned to -1 to make apt not use
it, and the up
Downgrading libapt-private especially should not make a difference, as
it's in the same package as apt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644643
Title:
apt failed to run due to link tim
apt 1.2.15ubuntu0.2 properly depends on libapt-pkg5.0 (>=
1.2.15ubuntu0.2), so assuming that this apt is installed, and the system
is not broken, this must be working (as it passed verification).
In any case, this bug is incomplete, as it does not clearly mention
which versions of apt, libapt-pkg
I have confirmed that the autopkgtest regressions in xenial are not
actual regressions from that upload, but in release. (bionic next)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796081
Title:
dp
Same in bionic. In both cases, not all errors are exactly regressions in
release, but some (sbuild, pbuilder) fail because they want to do stuff
with devel, but there is no devel yet:
Please check for an update for distro-info-data. See /usr/share/doc
/distro-info-data/README.Debian for details.
So, 1.5.1 is from artful (and that's EOL), and 1.2.29 is from xenial.
Partial upgrades are not supported. I suggest you find some help
returning your system to xenial, such as forums, mailing lists, or IRC.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I do not believe that apt 1.2.29 with libapt-pkg5.0 1.5.1 fails with
that error, btw. I believe it fails with:
symbol _ZN9pkgSystem9LockInnerEv version APTPKG_5.0 not defined in file
libapt-pkg.so.5.0 with link time reference
Which is expected (since 1.2.29 gained a new frontend locking symbol),
tobst4r, then your system is broken. You are mixing artful and xenial,
which is not a supported thing to do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644643
Title:
apt failed to run due to lin
So for anyone affected by this bug:
1. Make sure it actually is this bug (mentions precisely
_ZlsRSoRKN3APT9PrettyPkgE, not another mangled name)
2. Provide output of apt-cache policy apt libapt-pkg5.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Public bug reported:
[Impact]
Releases prior to cosmic mark almost all packages manually installed, meaning
that obsolete packages are not autoremoved when they should. We fixed this in
cosmic, in trunk r1695, by including a new script that marks as automatically
installed all dependencies of m
apt-side fix in
https://salsa.debian.org/apt-
team/apt/commit/a4b0ce5a4f5068f780b3aa94473230b5093a837d
** Changed in: apt (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
MrMe01 wrote:
> apt-cache policy is the same, and so is apt libapt-pkg5.0.
The same as what?
> What can I do to rectify this?
It depends on what you have installed. But generally, you have mixed two
Ubuntu versions on one system, so you have to make sure to upgrade or
downgrade packages so you
I have contacted Zentyal and asked them to stop doing that. By having
the old 1.5 version from artful, zentyal users are missing out on
important bug and security fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Public bug reported:
[Impact]
_pythonSymlinkCheck() checks that python links to the default python version.
In cosmic, python links to python2 however, so we need to check if that's the
case, and then check what python2 links to.
This breaks upgrades from cosmic to later versions, and partial u
We probably should sanity check all of python, python2, python3; not
just the most recent one. The python sanity checking exists to make sure
pyclean and friends work and don't cause a ton of upgrade failure
reports.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
To further expand on the "all symlinks":
> [Regression Potential]
> The code is just being updated to use python3 instead of python so there
> isn't any change of a regression.
That's wrong. You can now clearly symlink python to python3 (or 2.6) and
you'd get a ton of errors from postinsts.
--
*** This bug is a duplicate of bug 1799839 ***
https://bugs.launchpad.net/bugs/1799839
** This bug has been marked a duplicate of bug 1799839
not possible to use "Repair broken packages"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I think that's actually the same bug as the one I just opened: bug
1800823, but as mentioned, the solution should cover all python symlinks
and not just python3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
So, you want to execute python in a subprocess and read its output?
cosmic is also broken as documented in bug 1800823, as python is a
symlink to python2.
We probably should sanity check all of python, python2, python3.
--
You received this bug notification because you are a member of Ubuntu
Bu
We don't plan to. Trusty does not run unattended-upgrades by default, so
there's no strong need for frontend locking in there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795407
Title:
python-apt
me-tv is not included after 16.04, so the bug is invalid.
** Changed in: me-tv (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/1800951
Title:
Me-TV on 18.10
To
Closing as per David's comment from 2012
** Changed in: apt (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/1004541
Title:
apt-get update did not run even after
For unknown reasons, this bug was never marked as fix released in
cosmic, but it was:
https://launchpad.net/ubuntu/+source/python-apt/1.7.0~alpha2
** Changed in: python-apt (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ub
** No longer affects: dpkg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781169
Title:
frontend locking
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
Public bug reported:
[Impact]
foo
[Test case]
bar
[Regression potential]
baz
** Affects: python-apt (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: python-apt (Ubuntu Xenial)
Importance: Undecided
Status: Triaged
** Affects: python-apt (Ubuntu Bioni
** Description changed:
[Impact]
- foo
+ Add support to python-apt for frontend locking. This is a bit more
complicated, and also requires some other restructuring:
+
+ (1) The archives lock was only taken for a short time, when it should
+ have been kept for the duration of an installation, a
** Changed in: python-apt (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: python-apt (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Description changed:
- When running kernel version 4.4.0-78 (for example) and the unattended-
- upgrade packages installs a new kernel 4.4.0-79 (for example) the linux-
- cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are
- removed by the Remove-Unused-Dependencies rule, b
Public bug reported:
[Impact]
PackageKit needs an adjustment for frontend locking, so it does not release the
frontend lock during dpkg invocations, but only the normal dpkg lock.
[Test case]
1. Install a package
2. Modify prerm to sleep
3. Remove package via pkcon and check that packagekitd pro
** Also affects: packagekit (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/1790671
Title:
/usr/lib/packagekit/packagekitd:11:std::__cxx11:
Oh misread, xenial was not affected.
** Changed in: packagekit (Ubuntu Xenial)
Status: New => Invalid
** No longer affects: packagekit (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Hi,
Could you please provide some details? It's not clear what "same bug"
refers to that you are confirming, and what kind of bug you are trying
to report. Marking the bug as Incomplete until you have provided further
information.
Note that this is a bug tracker, not a forum or a support channel.
** Description changed:
+ [Impact]
+ pkcon what-provides and other tools querying codecs do not work, they crash
(unless you happen to be lucky with your apt cache)
+
+ [Test case]
+ The daemon should not crash as below, but should print a useful message.
+
+ $ lxc launch -e ubuntu:bionic bbb
+
** Description changed:
[Impact]
- pkcon what-provides and other tools querying codecs do not work, they crash
(unless you happen to be lucky with your apt cache)
+ pkcon what-provides and other tools querying codecs do not work, they crash
(unless you happen to be lucky with your apt cache).
** Changed in: networkd-dispatcher (Ubuntu)
Status: New => Fix Released
** Also affects: networkd-dispatcher (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: networkd-dispatcher (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification
Oh, I followed this on the repositories, but I never subscribed to bugs
after uploading the package. Thanks for letting us know, and sorry
nobody responded to this earlier.
** Changed in: networkd-dispatcher (Ubuntu)
Status: New => Fix Released
--
You received this bug notification becaus
It was a conscious decision to use /usr/lib as we wanted to be able to
package our system-provided scripts outside of /etc first, and deal with
system-local configuration later. I recently added support for overrides
in /etc in cosmic and upstream, so we search both and /etc overrides
/usr.
I'll u
There needs to be some more information. Could you
(1) add -vv to networkd_dispatcher_args= in /etc/default/networkd-dispatcher
and restart it?
(2) include the output of networkctl list
(3) a kernel log
(4) log of systemd-networkd
or just a journal excerpt with everything mixed together, from +/-
The networkd-dispatcher errors are not causing your connection issues -
networkd dispatcher just starts scripts after network changes. I wonder
if the connection issues are causing the networkd-dispatcher issues.
There needs to be some more information. Could you
(1) add -vv to networkd_dispatcher
** Description changed:
[Impact]
PackageKit needs an adjustment for frontend locking, so it does not release
the frontend lock during dpkg invocations, but only the normal dpkg lock.
+
+ Frontend locking prevents race conditions between multiple dpkg
+ frontends, which can cause other fronte
** Description changed:
[Impact]
PackageKit needs an adjustment for frontend locking, so it does not release
the frontend lock during dpkg invocations, but only the normal dpkg lock.
Frontend locking prevents race conditions between multiple dpkg
frontends, which can cause other fronte
dpkg is moving to its own bug to be able to better track the SRUs
** No longer affects: dpkg (Ubuntu Xenial)
** No longer affects: dpkg (Ubuntu Bionic)
** Summary changed:
- frontend locking
+ apt frontend locking
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Added some more details, but I'm really at a loss what else you could
want to know than it screwing up installations.
--
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:
packagekit frontend
Public bug reported:
[Impact]
Frontends of dpkg such as apt and programs using the apt libraries currently
acquire the dpkg "lock" lock file. They need to release it before running dpkg,
as dpkg also acquires it. Therefore, there is a race condition: In case the
application needs to run dpkg mu
** Description changed:
[Impact]
apt acquires /var/lib/dpkg/lock but has to release it while running dpkg,
offering a short window for other clients to acquire the lock. This implements
/var/lib/dpkg/lock-frontend which will be acquired earlier and not released by
apt for dpkg to run.
** Description changed:
[Impact]
Add support to python-apt for frontend locking. This is a bit more
complicated, and also requires some other restructuring:
(1) The archives lock was only taken for a short time, when it should
have been kept for the duration of an installation, as othe
** Description changed:
[Impact]
PackageKit needs an adjustment for frontend locking, so it does not release
the frontend lock during dpkg invocations, but only the normal dpkg lock.
Frontend locking prevents race conditions between multiple dpkg
frontends, which can cause other fronte
** Changed in: dpkg (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: dpkg (Ubuntu Xenial)
Status: Triaged => In Progress
** Description changed:
[Impact]
Frontends of dpkg such as apt and programs using the apt libraries currently
acquire the dpkg "lock" lock file
** Description changed:
[Impact]
Add support to python-apt for frontend locking. This is a bit more
complicated, and also requires some other restructuring:
(1) The archives lock was only taken for a short time, when it should
have been kept for the duration of an installation, as othe
801 - 900 of 5951 matches
Mail list logo
