I agree as well, it is great that we have .d function at all, but it could be
better.
As reported there is no control yet at what goes early or late and that would
be a great enhancement. Just including it late isn't an easy option either as
you might unintentionally to a different section that
** Tags removed: server-triage-discuss
--
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/2002994
Title:
sshd_config makes some changes awkward
Status in openssh package in
** Description changed:
+ Window actions (like maximize) no more work in wayland for QEMU using
+ GTK backend once the guest UI is intialized.
+
+ This can be seen by running an installed or even a trial Ubuntu from an
+ ISO like:
+
+ $ qemu-system-x86_64 \
+ -boot d \
+ -cdrom
FYI proposed migration tests should be happy as soon as the migration-
reference run for ubuntu-fan completed (but queues are long)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
@SRU team - please consider accepting and merging the test hint [1] to
resolve the current blocker for this SRU.
[1]: https://code.launchpad.net/~paelzer/britney/+git/hints-
ubuntu/+merge/433770
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Great finding Miriam,
I've looked into it and fully agree.
Since I had all the data at that moment I filed bug 1998184 for ubuntu-fan.
Based on that we need to mask the tests and we can ignore them here in regard
to this SRU (until fixed in ubuntu-fan).
--
You received this bug notification
** Changed in: pcsc-lite (Ubuntu)
Status: New => Incomplete
--
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 opensc pcsc-lite
Status in
Hi Marius,
> What actually is the effect of the denial? Will qemu not use more than one
> CPU,
> or is it something less harmful?
Since the new interface is arch specific and new the code does fall back
tot he old way.
226 /* On some architectures it is possible to distinguish between
Submitted upstream:
https://lists.ubuntu.com/archives/apparmor/2022-November/012528.html
Once discussed and accepted there I suggest a backport to Kinetic.
I hope this debug and patch helps, but to manage expectations, I'd
hope/expect that someone usually looking after apparmor does that follow
Reported upstream at https://gitlab.com/apparmor/apparmor/-/issues/283
** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #283
https://gitlab.com/apparmor/apparmor/-/issues/283
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
That is the commit causing the change [1] in behavior.
That is pretty low level (in libc6) and will probably hit anything that
links against libnuma.
I think the fix should therefore go into
/etc/apparmor.d/abstractions/base
Today it has:
# glibc's sysconf(3) routine to determine free
** Changed in: openssh (Ubuntu Jammy)
Assignee: (unassigned) => Bryce Harrington (bryce)
--
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/1986521
Title:
ssh client
** Changed in: apparmor (Ubuntu Jammy)
Assignee: Michał Małoszewski (michal-maloszewski99) => Andreas Hasenack
(ahasenack)
** Changed in: apparmor (Ubuntu)
Assignee: Michał Małoszewski (michal-maloszewski99) => Andreas Hasenack
(ahasenack)
--
You received this bug notification
** Tags added: cetest
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1989803
Title:
Adjust apport for the new Ubuntu debuginfod service
Status in Apport:
Fix Released
Focal:
- apparmor 2.13.3-7ubuntu5.1
- kernel5.4.0-109-generic
- libvirt:
a) base 6.0.0-0ubuntu8.16
b) server-backport 8.0.0-1ubuntu7.2~backport20.04.202210042317~ubuntu20.04.1
c) UCA Yoga 8.0.0-1ubuntu7.1~cloud0
With none did a restart trigger an issue as reported.
libvirtd is
I'll have a look for the same in server-backports ppa, but it might be
as easy as the old apparmor not knowing about these and failing. If that
is true we might need to remove them on the backports.
@Security - is there more to know about these particular features (will
they come to focal, is
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1989803
Title:
Adjust apport for the new Ubuntu debuginfod service
Status in Apport:
Fix
** Changed in: dnsmasq (Ubuntu Kinetic)
Assignee: (unassigned) => Lena Voytek (lvoytek)
** Changed in: dnsmasq (Ubuntu Jammy)
Assignee: (unassigned) => Lena Voytek (lvoytek)
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch
FYI: I've today had two systems exposing that issue.
The cleanup in comment #32 helped, but I wonder what caused it initially.
Sadly I can't recreate it anymore with a new system/container - might have been
related to the keying update to 2021.03.26 a few days ago.
--
You received this bug
With Michal: Marked block-proposed, added SRU content, re-reviewed and
sponsored the upload to Focal-unapproved.
--
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/1871465
** Tags added: block-proposed
--
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/1871465
Title:
ssh_config(5) contains outdated information
Status in openssh package in
@Michal
Sponsored for Kinetic, once complete there please have a look at considering an
SRU.
This might be on the brink between fix and feature depending on someones
POV.
Make your own decision and add some arguments for it to the SRU template
(if that is what you go for). Or explain why you
I was asked to add a Jammy task, I did so - the details and if that will
be done is up to your consideration/discussion/decision.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
--
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/1897932
Title:
systemd-repart not
as I hoped :-/
Yielding back to Sergio
** Changed in: rsync (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Sergio Durigan Junior
(sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in
Test build in PPA: https://launchpad.net/~paelzer/+archive/ubuntu/kinetic-rsync
Once built I'll also run the autopkgtests there ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
/rsync/-/commit/34390672fadd347f157148deb3b66cbf27ae6ed1
** Tags removed: needs-merge
** Tags added: needs-sync
** Changed in: rsync (Ubuntu)
Assignee: Sergio Durigan Junior (sergiodj) => Christian Ehrhardt
(paelzer)
--
You received this bug notification because you are a mem
** No longer affects: libmnl (Ubuntu Impish)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Title:
Static build does not work for libmnl (-lmnl)
Status in libmnl
Due to a ping on IRC I wanted to summarize the situation here as it
seems this still affects people.
In nested LXD container we seem to have multiple issues:
- apparmor service failing to start (might need to work with LXD to sort out
why and how to fix it)
- if it doesn't work at least fail
Hi,
I come by trying to clear old bugs that were dormant for too long either
resolving or reviving them.
First of all I can confirm what you have found (insmod vs modprobe
changes), but I also found why.
I've found that this makes modprobe work like before:
modprobe dummy numdummies=1
So I
FYI - related but not a dup - bug 1828749
--
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/1937953
Title:
systemd forcibly disables use of dummy/bond interfaces
Status in
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1805115
Title:
problem with (ubuntu/cosmic)mawk /^[[:space:]]*http://archive.ubuntu.com/ubuntu
Thank you Lars,
Debian maintainer confirmed the issue and agreed on making the necessary
changes which is great as we do not have to deviate. They didn't land yet, but
once they do (which will update the now linked Debian bug).
>From there we can then consider SRUs - I added bug tasks for
Waiting for an answer, setting incomplete to reflect that
** Changed in: openldap (Ubuntu Bionic)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
Hi,
I'm revisiting bugs that have been dormant for too long trying to retriage them.
In this case the current situation to me looks like:
- openldap change 3cd50fa having landed in v2.5.8 and later
- cyrus-sasl change 975edbb6 still isn't in any release AFAICS
- that is odd as
Thanks Simon to pick this up with your SME,
have you opened a tracker bug for this in Debian or Upstream so that we can
track it if it is implemented some day.
** Tags removed: server-triage-discuss
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: dnsmasq
Andreas fixed that in 2.4.49+dfsg-2ubuntu1 [Focal] which started to have
profile in openldap and include ssl_cert which (as Christian Bolz
outlined above) do include those paths.
# grep ssl_c /etc/apparmor.d/usr.sbin.slapd
#include
# grep enc /etc/apparmor.d/abstractions/ssl_certs
** Tags added: network-online-ordering
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1588915
Title:
ifup does not block for interface to be up with static addresses
We are - as always - trying to clean and recheck old bugs.
This - sadly - clearly is one of them.
The situation is still correct, but with the full switch to networkd and
netplan as well as the demotion of ifupdown in later versions of Ubuntu this
has become even less important. And it didn#t
Oh I assumed this was running s390x VM on s390x Host.
@Ryan - is this s390x emulation on a non-s390x host?
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Indeed (thanks Richard) that is enabled since 3.6-1.
It is unlikely though due to the associated symbol changes (see e.g. the
old changelogs) that this can be provided as an SRU for older releases.
I'm not saying impossible, just unlikely as that evaluation has to be
done and checked in depth for
@Ryan - Before going deeper since I read
"readconf.c:read_config_file_depth" in there. Does the same happen on a
fresh Jammy guest that has all-default config files? Or only to this
particular guest that you have?
--
You received this bug notification because you are a member of Ubuntu
Touch
(gdb) bt
#0 __GI__IO_default_xsputn (n=, data=,
f=) at libioP.h:947
#1 __GI__IO_default_xsputn (f=0x3ffcbc7c2e8, data=,
n=2929360903402) at genops.c:370
#2 0x03ffa6c7896c in outstring_func (done=11, length=2929360903402,
string=0x2aa0b841cea <__func__.3.lto_priv.14>
Hi,
for comparison on another system I've taken a Host (was impish before upgrade)
and created guests with Xenial, Bionic, Focal, Jammy.
All worked fine at this stage - ssh login and health of guests/hosts was good.
Then I upgraded the Host to Jammy (as the reporter did).
Example of the simple
As with the other case - Since we couldn't get a hold how to fix/debug
this I'm glad to hear that!
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1893716
Title:
scripts in /etc/update-motd.d/ run even on login via non-interactive
scp and sftp
FYI: Filed upstream at https://github.com/linux-pam/linux-pam/issues/452
** Bug watch added: github.com/linux-pam/linux-pam/issues #452
https://github.com/linux-pam/linux-pam/issues/452
** Also affects: pam via
https://github.com/linux-pam/linux-pam/issues/452
Importance: Unknown
Overall the majority of this is now fixed and mitigated with the combination of:
ubuntu-release-upgrader | 1:22.04.8 | jammy | source
landscape-client | 19.12-0ubuntu13| jammy | source, amd64,
arm64, armhf, ppc64el, riscv64, s390x
update-notifier | 3.192.54 |
Pengpeng/Yuhua - I have internally asked (at the same time I added the tag a
few days ago) for someone to look after it.
Nothing happened yet, so I pinged again.
In preparation of this - since most of Ubuntu developers won't have a
vsphere around to reproduce this. Is there any other way to
I re-installed the former package content, rebooted the system and gave
it some more memory to get rid of any concerns in that regard (from the
perf data).
The diff of the actual content before/after was all reasonable (new
times, different package counts, but otherwise the same)
Consumption
fier (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: landscape-client (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt
#3 50-landscape-sysinfo
The landscape part already has a statement about "when it is from" as it
is not re-executed on high load. This is handy as it will also ensure
there is no confusion "from when" this info is if we skip for too
frequent invocations.
Since it has an alternate less useful
#2 95-hwe-eol / update-motd-hwe-eol
Sadly this already does some caching in update-motd-hwe-eol by checking
if the last of these checks is older than an update to the source lists.
But to do so it has already executed the - relatively - rather expensive
apt-config calls.
Since it comes down to
Collecting snippets:
This one worked, proven by eliminating lsb_release on the consumption
charts.
#1 Caching for 91-release-upgrade:
--- orig/91-release-upgrade 2022-03-30 07:53:26.560515795 +
+++ /etc/update-motd.d/91-release-upgrade 2022-03-30 07:59:05.819971148
+
@@ -1,7
Summarizing the low hanging fruits here:
- Add caching to 50-landscape-sysinfo
- Add caching to 95-hwe-eol
- /usr/lib/update-notifier/update-motd-hwe-eol calls apt-config multiple times.
consider reducing those calls
- 91-release-upgrade unconditionally calls lsb_release which is expensive.
Analysis has spotted 91-release-upgrade as the most likely expensive remainder.
pam_motd enabled, but disabled:
- 50-landscape-sysinfo
- 91-release-upgrade
- 95-hwe-eol disabled
Bionic
real0m18.669s
us sy id wa st
22 23 55 0 0
Focal
real0m23.821s
us sy id wa st
40 39 21 0 0
pam_motd enabled, but 50-landscape-sysinfo and 95-hwe-eol disabled
Bionic
real0m25.952s
us sy id wa st
41 22 37 0 0
Focal
real0m30.592s
us sy id wa st
49 33 19 0 0
Jammy
real0m25.395s
us sy id wa st
44 28 29 0 0
That is still quite some overhead (~+60% to no motd)
pam_motd completely disabled in /etc/pam.d/sshd
Bionic
real0m15.540s
us sy id wa st
18 14 68 0 0
Focal
real0m16.937s
us sy id wa st
43 40 17 0 0
Jammy
real0m16.260s
us sy id wa st
36 19 45 0 0
The remaining difference of those is in the noise-range.
Time and CPU consumption (results are rather consistent BTW):
Bionic
real1m11.714s
user0m2.577s
sys 0m0.410s
procs ---memory-- ---swap-- -io
-system-- cpu -timestamp-
r b swpd free buff
I wanted to get a better feeling about this before jumping to action.
Therefore I have created three 1G/1vcpu KVM guests Bionic/Focal/Jammy to test
and compare this on.
I do not need hot-loop analysis or anything down to instructions, so no debug
symbols needed.
For now I only want to know:
1.
I can't test this reliably (as stated in the SRU description), but at
least I can say I haven't seen it in the last 24h :-) I think this is on
@gjolly to try to reproduce it in the mentioned azure test environment.
--
You received this bug notification because you are a member of Ubuntu
Touch
The only current interactivity detection code in pam is part of a
pam.conf -> pam.d conversion tool that won't be useful here.
The pam_motd code emits content via things like try_to_display_fd.
A message is created and then printed via pam_info.
Which is actually pam_prompt which wraps
** Tags added: rls-jj-incoming
--
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/1962843
Title:
Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to
This is still present in jammy as
debian/patches/debian/UBUNTU-Revert-namespace-be-more-careful-when-handling-namespacin.patch
If we want to keep this as long as there could be an 18.04 that is like 2028 at
least.
So AFAIU this bug is actually asking LXD to consider a backport (if
possible) to
See bug 1965758 this also breaks focal-backports - please upload the fix
there as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhelper restarts
Thanks for the ping on this old case Alexander!
Can you confirm that this is what you see on 22.04 with the there recent
2:11.3.5-1ubuntu4 version of open-vm-tools?
I have subscribed John Wolfe who looks after open-vm-tools from VMwares
side and might have more details.
Further I added a bug
There was a bad tag update before, this is verified on Focal as well.
Fixed now ...
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
** Changed in: rsync (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: rsync (Ubuntu Bionic)
Importance:
Thanks to Scott this is Fixed in version postfix/3.6.3-5
And since the package is in sync this is in Jammy now:
postfix | 3.6.3-5ubuntu2| jammy | source, amd64, arm64, armhf,
ppc64el, riscv64, s390x
** Changed in: postfix (Ubuntu)
Status: Triaged => Fix Released
--
You
** Changed in: libvirt (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: libvirt (Ubuntu Jammy)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Tags removed: server-todo
** Tags added: server-next
--
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/1959126
Title:
Consider update to 3.68.2
Status in nss package in
Robie will take a look, but likely not immediately, more like next week.
** Tags removed: server-triage-discuss
** Changed in: six (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
** Changed in: pyyaml (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
--
You received this
Server-Team: As you see in the bug-history we (Server Team) have
ourselves stopped working on this believing it might be too much of a
corner case waiting for it to come back. But that come-back has happened
by even more people reporting to be affected. Therefore - as much as it
initially seems to
@Miriam - thanks for the check of this case (FYI we are trying to
recheck many old forgotten bugs). Seems this one is a great candidate
for a fix now since we have a testcase, a fix and interested community.
Given this is open for quite some time there is no need to rush it, but
as time permits
I struggled as well to use that syncpackage behavior right. The time you
trigger the sync is often too far away from the actual migration to
-release to happen. I happened to find my own way around (Not perfect,
but a suggestion).
I call it with --bug and once it has built (but not yet migrated)
** Changed in: nss (Ubuntu)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
--
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/1959126
Title:
Consider update to
I can also confirm that it is good not for libvirt again - Thanks for
the quick fix!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1959325
Title:
New binutils causes
.85-1ubuntu2) impish; urgency=medium
* Revert: 'src/radv.c: avoid leases to be issued forever when not set'
(LP 1894619) according to the bug and upstream discussion.
-- Christian Ehrhardt Tue, 22 Jun
2021 07:18:30 +0200
dnsmasq (2.85-1ubuntu1) impish; urgency=medium
* Me
** Tags removed: server-next
--
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/1957086
Title:
Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
Status in dnsmasq
** Changed in: openssh (Ubuntu Bionic)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
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/1863930
Title:
For xen itself we know now how to "work around it" which is retry until running
on one of the new builders. Leaving the bug open as it clearly seems to be a
real issue.
I also leave the PPA as-is so that you can grab sources from there for
recreating this binutils issue.
--
You received this
Hi Michael,
it seems suspicious as it is the same test that fails.
But the assertion is different.
In the referred Debian bug it is
AssertionError: b'megasearch.net: 192.168.42.1' not found in
In the Ubuntu fail it is
subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']'
Being a platform dependent (thereby rather severe, but easy to miss)
crash in binutils I feel it is time to bump priority of this to get it
onto the radar avoiding to ship it that way (potentially breaking more)
in our next LTS.
** Changed in: binutils (Ubuntu)
Importance: Undecided =>
1894619) according to the bug and upstream discussion.
-- Christian Ehrhardt Tue, 22 Jun
2021 07:18:30 +0200
dnsmasq (2.85-1ubuntu1) impish; urgency=medium
* Merge with Debian unstable. Remaining changes:
- src/radv.c: avoid leases to be issued forever when not set
(LP
This build ran 10:26 -> 10:33 and the crash happened "in between". As i
said in local sbuild those are not fatal but on LP they are. Therefore
attaching the build log ...
** Attachment added: "build log that did not exit fatally, but triggered the
crash we also see on LP (there fatally)"
The build log I attached above shall help to spot the versions needed
for debug symbols to read this crash correctly.
** Attachment added: "Crash file of x86_64-linux-gnu-ld.bfd as seen in local
sbuild"
Thanks for the hint,
in case anyone needs to do the same - you can see the associated builder right
when the build starts - then abort it immediately, refresh and rebuild.
That way you get 1 build try <1min, I got
lgw01 018
lgw01 044
lgw01 023
lcy02 001
And the build on the latter I let finish
Thanks Colin, even without debug symbols that still is probably enough
to confirm it is actually the same crash that I see on my laptop.
While I do not see why it is fatal for the build on LP but not on local
sbuild or dpkg-buildpkg in a local VM it means that most likely someone
looking into
And as comment #8 and #3 outlined the use of it in boost is not a real
problem for build or usage in the distribution, setting that task to
invalid.
** Changed in: boost1.74 (Ubuntu)
Status: New => Invalid
** Changed in: grub-legacy-ec2 (Ubuntu)
Assignee: Miriam España Acebal
Per comment #7 and
bzip2 | 1.0.8-5| jammy | source, amd64, arm64, armhf,
i386, ppc64el, riscv64, s390x
Setting that to fix released.
** Changed in: bzip2 (Ubuntu)
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of
** Changed in: grub-legacy-ec2 (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
** Changed in: ceph (Ubuntu)
Assignee: Miriam España Acebal (mirespace) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Hi Colin,
so far I've seen it only on lgw01, but I didn't mass-submit it yet to try the
other builders.
Is there a better way than re-building/re-submitting to get onto the lcy02?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
FYI: I've seen some shortening of the reported crashes going on.
For example in journal it was "x86_64-linux-gn" and in the build log it was
after "x86_64-linux-gnu-ld". The local (non fatal) crash I got eventually was
in "x86_64-linux-gnu-ld.bfd".
This might or might not be the same crash on
Public bug reported:
FTBFS in Jammy on LP infra:
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
Related PPA:
I tested the test of 249.5-2ubuntu2 (running autopkgtest against the dsc
file of 249.5-2ubuntu2) vs the binary systemd build in your PPA
(systemd_249.7-1ubuntu1~slyon0) + the dnsmasq from proposed.
And I got:
resolved: domain-restricted DNS servers ... ok
That means:
1. the fix is not in
** Tags added: server-next
--
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/1957086
Title:
Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
Status in dnsmasq package
** Tags removed: server-next
** Tags added: server-todo
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bzip2 in Ubuntu.
https://bugs.launchpad.net/bugs/1951779
Title:
tempfile command removed from
As usual once you know what you search for the results are much better.
It turns out that it might be related to one of those reports:
- https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q1/016015.html
- https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q1/016069.html
But
# FYI cleanup
# Minimal Reset (e.g. when switching dnsmasq)
killall dnsmasq
rm /tmp/dnsmasq*
dnsmasq --no-daemon --log-queries --log-facility=/tmp/dnsmasq.log
--conf-file=/dev/null --dhcp-leasefile=/tmp/dnsmasq.leases --bind-interfaces
--interface=router_eth42 --except-interface=lo
Detailed Logs:
Before the test:
dnsmasq.log is identical
dnsmasq-vpn.log as well, except the version number
Good Case:
ubuntu@autopkgtest:~$ resolvectl query math.lab
math.lab: 10.241.3.3 -- link: testvpnrouter
-- Information acquired via protocol DNS in 20.8ms.
-- Data
Reproducing the case outside the systemd tests
(Commands on Ubuntu 22.04, with root permissions)
jammy-Proposed has dnsmasq 2.86 right now
apt update; apt upgrade -y; apt install dnsmasq-base
systemctl reset-failed systemd-networkd systemd-resolved
mkdir /run/systemd/resolved.conf.d
cat >
1 - 100 of 1166 matches
Mail list logo
