Hi,
thanks for the report but IMHO there is not much to do, port 22 is SSHs port
and it is right to default to it. If your local configuration has port 22 bound
to something else (Docker in your case) you need to adapt the configuration of
either (ssh in its half installed state or your
Awesome, thanks for updating the bug tasks and tracking bug already
Alkis!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1902109
Title:
rsync uses lchmod and fails in
Maintainers are free to remove python2 if there are no reverse dependencies
left for the obvious unsupportability.
This happened here in [1] to resolve [2]
There also is no installation candidate left in a recent archive. Maybe
replaces/breaks was a bit too much (as users like you could be happy
I can confirm the behavior
** Changed in: python3-chardet (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-chardet in Ubuntu.
https://bugs.launchpad.net/bugs/1901295
Title:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Now to your actual question of "how to order after a given bond interface",
that is actually a systemd-networkd/systemd question (reminder question, not a
bug - so not a bug report actually).
I'll add bug tasks but think they are incomplete as that is a
config/consulting question more than
Thanks Axel,
I think I didn't closed a terminal windows with anything other but CTRL+D for
years (which is an implicit call to exit), but you are absolutely right. It
could be "click on the X on the window decoration to close the terminal".
Thanks for making me see that ... :-)
@Gustavo - never
FYI since comment #6 not a lot happened in Debian other than other bugs
being merged.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1744328
Title:
libfreebl3.so should be
I just re-debugged into the same case - now marked as dup.
You might consider using
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1898590/comments/7 as
test steps to verify that once uploaded to focal-proposed.
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1897744 ***
https://bugs.launchpad.net/bugs/1897744
@Dan - now I saw your update - that might have shortened my dnssec trip :-)
It indeed is a duplicate of that - marking as such.
** This bug has been marked a duplicate of bug 1897744
VerifyHostKeyDNS
*** This bug is a duplicate of bug 1897744 ***
https://bugs.launchpad.net/bugs/1897744
Summary:
- we understand what happened
- we have a workaround for users by changing a config
- we have a systemd change that can be considered to be backported by the
systemd package maintainers
** Tags
*** This bug is a duplicate of bug 1897744 ***
https://bugs.launchpad.net/bugs/1897744
TL;DR:
one affected by this upgrade triggered behavior change needs to set
options edns0 trust-ad
in /etc/resolv.conf to fix the issue.
And as usual, once you already know what things are about - then
*** This bug is a duplicate of bug 1897744 ***
https://bugs.launchpad.net/bugs/1897744
ok up/downgrading just "libc6" is enough to trigger.
I also found that libc6 from Eoan version 2.30-0ubuntu2.2 is good.
So it is new in 2.31!
The changelog mentions soem DNSSEC
As a first step I tried to make sure this actually is a change in openssh.
Because my reading of the issues referred above has shown that not all of the
verification is done inside ssh but partially in glibc.
So I upgraded on the bionic test system step by step.
The upgrade dependency list for
Something helpful for anyone looking into this later I found what seems
a good testcase without requiring too much a local setup (of a dnssec
dns server):
To get unbound (brute force) do:
apt install unbound
sudo systemctl stop systemd-resolved
sudo systemctl disable systemd-resolved
sudo
Turns out this seems to be a never ending story and you might have found
a comeback of that issue for your particular configuration as you say
this worked on 18.04 but fails on 20.04.
This goes way back
https://bugzilla.mindrot.org/show_bug.cgi?id=1455
Or half way back
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1898590
Title:
Verify DNS fingerprints not working
Status in openssh package in Ubuntu:
New
Hi Seth and Joy,
I see you cleared the list a lot - awesome!
You have subscribed and pinged the remaining ones which is a reasonable
approach as most might be no more real issues as of today.
I'm ok for the Ubuntu side of the pcsc-lite bugs now, what still needs
to be addressed is
Since so many components are involved a fix/change might have been missed.
And since I recently didn't hear anything about this otherwise rather hot bug I
was giving focal a try.
It turns out that this was indeed improved. Only the user of pkg:ifmail user
fdt name "Fidonet" is still visible.
Tested the change - works as expected, prepping an MP
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1895967
Title:
Apparmor 3.0.0 does not load profiles in containers
That patch by Christian Bolz is already applied (which seems reasonable after
that much time),
but when merging 3.0 the old patch for bug 1824812 should have been dropped.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
As refrence, it is a re-occurrence of
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1824812 , look
who filed that bug :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://gitlab.com/apparmor/apparmor/-/commit/61c27d8808f0589beb6a319cc04073e8bb32d860
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1895967
Title:
Apparmor 3.0.0 does
And we are back with Christian Bolz :-)
commit 61c27d8808f0589beb6a319cc04073e8bb32d860
Author: Christian Boltz
Date: Fri Jun 21 19:22:15 2019 +0200
Fix and simplify setting SFS_MOUNTPOINT
The question is why isn't this in the apparmor 3.0 package in groovy-
proposed ?
--
You received
Isn't that "Not starting AppArmor in container" message just in:
/lib/apparmor/apparmor.systemd
-> /lib/apparmor/rc.apparmor.functions
-> function is_container_with_internal_policy()
That looks unchanged (except a comment) but it behaves differently:
root@testguest-apparmor-good:~# .
Bad case:
$ ./repro.sh bad
+ '[' bad == bad ']'
+ echo 'Bad case: Using apparmor from proposed'
Bad case: Using apparmor from proposed
+ BADCASE=1
+ lxc stop --force testguest-apparmor-bad
+ lxc delete --force testguest-apparmor-bad
+ lxc launch ubuntu-daily:groovy/amd64 testguest-apparmor-bad
It seems it comes down to a change in /lib/apparmor/apparmor.systemd
which now refuses to load profiles when running in a container.
Example with 3.0:
$ /lib/apparmor/apparmor.systemd reload
Not starting AppArmor in container
Example with 2.x
/lib/apparmor/apparmor.systemd reload
Restarting
FYI - other testing might miss this as "starting a guest on groovy"
works with the new versions, but it will be without apparmor. Migrating
from focal or a pre-upgrade groovy shows the issues broken by apparmor
not being enabled.
** Changed in: apparmor (Ubuntu)
Status: Incomplete => New
I have backed up this container and its snapshot for later and re-run
the whole automation which got me that bad state.
That allowed me to run my automation again without removing this
container (in case we need it for debugging later). So I ran everything
again to check if it would happen again
Ok, I have definitely a snapshot left that has "conserved" the bad
state.
$ lxc stop testkvm-groovy-from
$ lxc restore testkvm-groovy-from orig
$ lxc start testkvm-groovy-from
$ lxc exec testkvm-groovy-from
# aa-status
apparmor module is loaded.
15 profiles are loaded.
15 profiles are in enforce
Hi Christian Bolz o/
I'd have such rules but this isn't the problem here as that would matter only
much later.
I libvirtd itself isn't confined it refuses to go on confining the guests and
that is here the problem.
The current question really comes down to "how did I manage to have
everything
I knew from my former tests:
1. apparmor 3.0 = bad
2. downgrading to 2.13.3-7ubuntu6 and back up to 3.0 = good
3. aa-enforce + service restart = good
I checked the logs on the affected systems how this got into the bad
state:
$ grep -E 'configure (lib)?(apparmor|libvirt)' /var/log/dpkg.log
Sorry, while being about evaluating the new apparmor this got posted to
the wrong bug :-/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1895060
Title:
[FFe] apparmor 3
I knew from my former tests:
1. apparmor 3.0 = bad
2. downgrading to 2.13.3-7ubuntu6 and back up to 3.0 = good
3. aa-enforce + service restart = good
I checked the logs on the affected systems how this got into the bad
state:
$ grep -E 'configure (lib)?(apparmor|libvirt)' /var/log/dpkg.log
Yeah and the comment above this function pointed the right way:
Good case (libvirt is enforced):
oot@testkvm-groovy-to:~# aa-status
apparmor module is loaded.
31 profiles are loaded.
31 profiles are in enforce mode.
/snap/snapd/9279/usr/lib/snapd/snap-confine
This gets me back to a working system
$ aa-enforce /etc/apparmor.d/usr.sbin.libvirtd
$ systemctl restart libvirtd
And this also explains why on the system where I re-installed libvirt things
might have worked.
The re-install runs dh_apparmor which has loaded and enforced it.
--
You
Sorry my system broke down in various way stalling debugging of this for a few
days.
Back on it ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1895967
Title:
This is the failing function
221 /* returns -1 on error or profile for libvirtd is unconfined, 0 if
complain
222 * mode and 1 if enforcing. This is required because at present you cannot
223 * aa_change_profile() from a process that is unconfined.
224
Lookup fails:
(gdb) fin
Run till exit from #0 virSecurityDriverLookup (name=name@entry=0x0,
virtDriver=virtDriver@entry=0x7fffd26ae1b2 "QEMU") at
../../../src/security/security_driver.c:50
virSecurityManagerNew (name=name@entry=0x0,
virtDriver=virtDriver@entry=0x7fffd26ae1b2 "QEMU",
Need to check the init of the bunch in qemuSecurityInit and qemuSecurityNew.
But that happens at daemon start and not later when probing caps.
virQEMUDriverConfigLoadSecurityEntry load this from config and it includes
apparmor in both:
/etc/libvirt/qemu.conf:# security_driver = [
Good:
(gdb) p *((virSecurityStackDataPtr)(((virQEMUDriverPtr)conn->privateData
)->securityManager->privateData))->itemsHead->securityManager
$7 = {parent = {parent = {parent_instance = {g_type_instance = {g_class =
0x7f430805ddf0}, ref_count = 1, qdata = 0x0}}, lock = {lock = {__data = {__lock
for (i = 0; sec_managers[i]; i++) {
...
VIR_DEBUG("Initialized caps for security driver \"%s\" with "
Good:
- apparmor
- dac
Bad:
- none
- dac
In function virQEMUDriverCreateCapabilities.
So it isn't probing apparmor because it isn't even in the list.
That list is from
It seems once fixed the system is ok and I can't get into the bad state
again :/
I tried on another bad system (withotu changing back to the former version)
1. A restart of the service
2. Trying to force capabilities reset (remove cache) + service restart
None of these got it into the good case,
Public bug reported:
Hi,
I stumbled over this due to automatic tests checking proposed.
I found that Focal no more could migrate to Groovy with:
$ virsh migrate --unsafe --live fguest qemu+ssh://10.162.30.163/system
error: unsupported configuration: Security driver model 'apparmor' is not
The tests confirmed the issue that Iain reported and that the fix works.
Also no other issues popped up in the NM test using it.
autopkgtest [08:47:12]: summary
wpa-dhclient PASS
nm.pyPASS
killswitches-no-urfkill PASS
urfkill-integration PASS
And
For now the hint is in groovy, but the next systemd upload needs to
resolve it one (fix) or the other (mark this one as flaky) way.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
FYI: builds complete - Running the test builds of network-
manager_1.26.2-1ubuntu1.dsc in groovy against the proposed and the PPA
version.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
Ok changed MP and PPA to work for 1.0 source
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1894619
Title:
[2.82 regression] router announcements have 'forever' lifetime
Arrr 1.0 source, need to apply differently
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1894619
Title:
[2.82 regression] router announcements have 'forever'
BTW I randomly picked the latter patch of the two as no one seems to
have jumped on the first one and said "yes let us apply it".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
The patch suggested at
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2020q3/014346.html
isn't applied yet.
I guess this waits for feedback if it worked before they apply it.
To get this going here a PPA and an associated MP:
PPA:
Sorry, I forgot to update one section for pcsc-lite on packaging:
- important open bugs (crashers, etc) in Debian or Ubuntu
There are quite some:
in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- no embedded source copies
- not part of the UI for extra checks
** Changed in: pcsc-lite (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Ubuntu Security Team
(ubuntu-security)
** Bug watch added: Debian Bug tr
The retries were reproducible failing as well.
[09:20] rbalint: btw the test on s390x really seems still broken
[09:20] we need either a fix or a test hint
[09:21] --> falcojr (~falcojr@184.55.64.152) has joined this channel.
[09:24] cpaelzer, i'm ok with the hint and i've retriggered the
Old hints we only had:
# failing due to multiple reasons LP: #1892358
force-badtest systemd/246-2ubuntu1
# failing due to livecd-rootfs creating broken LXD images LP: #1877078
force-reset-test systemd/246.2-1ubuntu1
But was then removed in
revno: 4988
committer: Steve Langasek
branch nick:
Also please do note that while almost all of the recent tests failed - almost
all of the packages already migrated. Why is that - there is no test hint in
place.
For example gdm3/3.37.90-1ubuntu1 and iptables/1.8.4-3ubuntu3 (but more than
just those, policykit-1, dpdk, util-linux, ...) NEVER
And on Bionic we only need to do so for amd64
Here is a new MP for Bionic:
https://code.launchpad.net/~paelzer/britney/hints-ubuntu-bionic-disable-systemd-v2/+merge/390793
** Branch linked: lp:~paelzer/britney/hints-ubuntu-bionic-disable-
systemd-v2
--
You received this bug notification because
The problem with Xenial is that there it isn't just flaky "systemd-
fsckd" much more seems to be broken. I'll revise my Bionic MP, but for
Xenial I'd like to hear from ddstreet/rbalint how they think we should
go on there ...
--
You received this bug notification because you are a member of
@Rbalint - hi the two most recent tests confirm that it still seems broken.
Maybe the good run was a one-off lucky run ... :-/
I'd ask you to look into that a bit deeper as it will again hold back
plenty of things in groovy soon.
--
You received this bug notification because you are a member of
Focal test hint was accepted tonight and things moved there.
@Kelsey - Steve denied the hint as a reset since recently a few results were
good.
Maybe you want to submit the same as force-badtest and bring it up like that
for X?
The results for xenial really look similarly bad ...
xenial
** Changed in: pcsc-lite (Ubuntu)
Assignee: Seth Arnold (seth-arnold) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1892559
Ti
** Branch linked: lp:~paelzer/britney/hints-ubuntu-focal-disable-systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1892358
Title:
autopkgtest success rate dropped
Thanks rbalint for pointing me to the other bug for the s390x fail we see now.
I'll continue there and consider the Groovy portion of this one closed again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Thanks for this bug Rbalint.
That the new glibc/cryptsetup worked is odd as nothing on the issue indicates
they are related. There was nothing in the queue - for the sake of some test
data I have restarted the packages currently blocked on this with all-proposed
which will pull in e.g.
Groovy
It seems this isn't over for groovy, it was mentioned that the issues in the
subtest "tests-in-lxd" would be related to some fstab issues in those issues.
But recently all architectures, but s390x recovered. I assume that the fstab
issue is fixed but something else surfaces now.
groovy
[15:17] ddstreet: any updates on 1892358?
[15:18] @paelzer sorry not yet, i'll have systemd ready for upload
next week including fixing the autopkgtests
[15:21] ok
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/390398
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
@ddstret - any update how to proceed?
If you have no time yet, then the MPs to ignore the fail until we have a new
version are up - just ack them and I guess the SRU Team will follow.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 1894172 ***
https://bugs.launchpad.net/bugs/1894172
** This bug has been marked a duplicate of bug 1894172
isc-dhcp-server using wrong env variable for INTERFACES
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thanks for --no-ask-password Sergio.
I like the suggestion of making /etc/resolvconf/update-libc.d/squid systemd
aware.
>From similar checks I know that you also want to check if it is active:
if [ -d /run/systemd/system ]; then
! systemctl is-active -q squid.service || systemctl reload
As already reported dnsmasq hangs on the hooks:
├─2089 /bin/sh /etc/init.d/dnsmasq systemd-start-resolvconf
├─2097 run-parts --arg=-a --arg=lo.dnsmasq /etc/resolvconf/update.d
├─2116 run-parts /etc/resolvconf/update-libc.d
├─2129 /bin/sh
Since Sergio mentioned groovy, this really only is a xenial issue:
Test:
1. install dnsqmasq+squid
2. ensure dnsmasq is able to run (port collision >=Focal)
3. stop/start dnsmasq in a loop
for i in $(seq 1 4); do date; echo "-"; systemctl stop dnsmasq; date;
echo "+"; systemctl start dnsmasq;
Sergio:
> "squid takes 30 seconds to restart regardless of dnsmasq/resolvconf (this is
> still true nowadays, with groovy)"
I'm ashamed - it seems I have taken the most complex way to resolve a simple
thing.
Imagine a very complex debugging through strace and gdb to reach a trivial
config
Sergio:
> ... reload" actually exits successfully ... systemctl ... keeps waiting
For the systemd side I'd wonder as there are so myn type= options if it is not
getting that squid is restarted.
(https://www.freedesktop.org/software/systemd/man/systemd.service.html#Options)
maybe worth to
assigning pcsc-lite back to sarnold for the decision if you really
need/want it for "pcscd" or not.
** Changed in: pcsc-lite (Ubuntu)
Assignee: (unassigned) => Seth Arnold (seth-arnold)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
hanged in: pcsc-perl (Ubuntu)
Status: New => Invalid
** Changed in: pcsc-tools (Ubuntu)
Status: New => Invalid
** Changed in: pcsc-perl (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
** Changed in: pcsc-tools (Ubuntu)
Assignee: Christian Ehrhar
I asked about it in comment #2 already.
pcsc-lite was MIRed in bug 250245 but pcscd explcitly excluded.
One either needs to:
1. step up and say "yes we want to own it" (in that case please add a request
to the description)
2. say this isn't needed for what you want to achieve (Essentially
no use of setuid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- no embedded source copies
- not part of the UI for extra checks
** Changed in: pam-pkcs11 (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Ubuntu Sec
n)
** Changed in: opensc (Ubuntu)
Status: New => Incomplete
** Changed in: opensc (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Ubuntu Security Team
(ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
do, gksu, pkexec, or LD_LIBRARY_PATH
- no use of user nobody
- no use of setuid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- no embedded source copies
- not part of the UI for extra checks
** Changed in: ccid (Ubuntu)
Assignee: Ch
If not going for marking the subtest flaky as in groovy, I have prepared
force-reset-test as alternatives in:
-
https://code.launchpad.net/~paelzer/britney/hints-ubuntu-focal-disable-systemd/+merge/390005
-
To match the open packages blocked on this in active releases I added
linux-meta for BIonic (thanks Kleber for the hint) and Focal (Thanks
Kelsey for the hint).
I think all of those had enough of retry-until-success and I'd ask again
for how we should proceed there. Masking/Resetting the test via
Util-linux SRU in Focal blocked as well, updating tags.
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: util-linux (Ubuntu Focal)
Status: New => Confirmed
** Changed in: util-linux (Ubuntu)
Status: New => Invalid
--
You received
True @Kleber, here the stats of Bionic - at least on x86 you seem to
have barely a chance.
bionic
amd64
boot-smoke (F 40% S 0% B 0% => P 60%/)
...F.FFF.FF.FF..
upstream (F 5% S 0% B 0% => P 95%/)
..F.
systemd-fsckd
: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1892559
Title:
[MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools p
Here an (monospace) overview of recent focal tests.
focal
amd64
networkd-testpy(F 5% S 0% B 5% => P 90%/)
.B...F..
boot-and-services (F 5% S 0% B 5% => P 90%/)
.B...F..
upstream (F 5% S 0% B 5% =>
https://launchpad.net/ubuntu/+source/systemd/246.2-1ubuntu1 is still in
proposed and I was looking forward to a bunch of custom triggers this
morning.
But I found everything migrated this morning despite those new tests not being
done.
What is left is the similar situation in Focal (as mentioned before).
I have updated the tasks to reflect that properly and get update-excuse tagging
there.
In Focal it is currently blocking qemu and build-essential SRUs and I
wanted to ask if the plan is to do the same upload+test-reset there
[16:34] seb128, cpaelzer ahasenack sorry, i was out and apparently
forgot setting that in my email. the last systemd upload should fix everything
except for the livecd-rootfs revert that made fstab in lxd images invalide
[16:45] rbalint: " the last systemd upload" means groovy I guess,
what
** Changed in: libselinux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libselinux in Ubuntu.
https://bugs.launchpad.net/bugs/1892455
Title:
[MIR] libselinux1
Status in
This no more affects libvirt, marking it as such to not show up in
excuses.
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Adding glib2.0 as it had a rebuild for libffi and will be blocke dby
this as well.
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glib2.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Added another two packages that are blocked by this so they are
marked/linked in update excuses :-/
** Also affects: iputils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: iputils (Ubuntu)
Status: New => Confirmed
** Also affects: ntpsec (Ubuntu)
Importance:
Adding update-excuse tag so that one can find this issue from update-excuses
page.
To show up at the packages that fail I also add an qemu and kbd task (more
might pile up)
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
** Also affects: kbd (Ubuntu)
Importance: Undecided
Thank you Rbalint.
Thanks to xnox I already found 1891716 and 1886886 which are sort of
remotely related (to the next upload), I guess this bug will serve for
the "marking systemd-fsckd test as flaky" task then.
Can we do something about this bad fstab in LXD or is there a bug to
track?
Public bug reported:
Hi,
we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130
is about the same as well. There were more but I didn't want to search for all
of them - what I checked is that there are no open ones clearly pointing out
the recent further drop in
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/389531
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1869796
Adding slapd task since it is mentioned to break there.
Seems to be a regression from 18.04 -> 20.04 as far as a I read it,
tagging as such for now.
@Andreas - any chance to recreate this on your side?
** Also affects: openldap (Ubuntu)
Importance: Undecided
Status: New
--
You
** Summary changed:
- Kernel panic booting after 18.04 to 20.04 upgrade
+ systemd breaks due to old libsecomp libs left on the system
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
The problem is Ubuntu only, as [1] is good.
And the real fix should be in dbus-test-runner, but without repro it will be
unclear if anyone gets to that or if we just hope it resolves itslef (again).
But due to the above it makes no sense to submit the fix to Debian - as
for them it would reduce
1 - 100 of 835 matches
Mail list logo
