> /usr/lib/systemd/systemd --switched-root --system --deserialize=40
splash
Ok, --switched-root is there in PID 1, it's something I was looking to
confirm.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
** Changed in: cyrus-sasl2 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/2064399
Title:
Me
** Changed in: heimdal (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/2064407
Title:
Merge heim
** Changed in: krb5 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/2064411
Title:
Merge krb5 from Deb
** Package changed: software-properties (Ubuntu) => linux-raspi (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2064370
Title:
Blank screen after boot
I think neither rsyslog, nor cups, or sssd, are the correct packages for
this bug, but I agree that spreading out the investigation over two
different bugs is not good.
I'll mark https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088 as
a duplicate, and add cups and sssd tasks to this one
** Description changed:
+ What's known so far:
+ - 24.04 desktop deployed with TPM+FDE shows this bug
+ - services confined with apparmor that need to access something in
/run/systemd (like the notify socket) fail to do so, even if the apparmor
profile is in complain mode
+ - only after running
So far it's rsyslog, cups, and sssd (just confirmed via
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/2064096
Ryan, I think you are experiencing
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197 which
is a regression on focal from a previous update that also tried to
address the version negotiation. There is a new nfs-utils package in
focal-proposed to address that, would you mind trying it
Public bug reported:
pam_lastlog.so was dropped by upstream in 1.5.3[1][4]. It's still there
in the code, but not built by default.
And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2)
does.
This does not prevent console logins, but generates an error in the logs:
Apr 23 20:02:09
I'm surprised this wasn't caught by the DEP8 tests. Care to also perhaps
add a simple smoke test, like (note it's not using ssh or any network):
$ rsync -F --delete-after --archive /etc/os-release /tmp/
*** buffer overflow detected ***: terminated
rsync: connection unexpectedly closed (34 bytes
https://launchpad.net/ubuntu/+source/cups/2.4.7-1.2ubuntu6 is in noble-
proposed claiming to fix this bug.
Comment #6 above says there is a missing patch still.
In any case, doesn't look like there is anything to sponsor here, so
unsubscribing ubuntu-sponsors.
--
You received this bug
And unsubscribing sponsors.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/2060335
Title:
upower/1.90.2-8build3 autopkgtest failure on arm64
Status in upower package in
At the moment, noble-proposed has
https://launchpad.net/ubuntu/+source/upower/1.90.3-1, uploaded a few
hours ago:
upower (1.90.3-1) unstable; urgency=medium
* New upstream version 1.90.3
* Drop patches, merged upstream
* Bump Build-Depends on meson to (>= 0.60.0) and libglib2.0-dev to (>=
New pam package uploaded to noble-proposed. It's in the unapproved
queue.
--
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/2059859
Title:
pam_env(sshd:session): deprecated
: Undecided
Status: New
** Changed in: openssh (Ubuntu)
Milestone: None => later
** Changed in: pam (Ubuntu)
Status: New => In Progress
** Changed in: pam (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: pam (Ubuntu)
Milest
Commit that added the warning to pam_env.c: https://github.com/linux-
pam/linux-pam/commit/ecd526743a27157c5210b0ce9867c43a2fa27784
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Deprecation warning introduced here: https://github.com/linux-pam/linux-
pam/releases/tag/v1.5.0
Release notes for all releases up to 1.6.1 don't mention this again, so
it's still there: https://github.com/linux-pam/linux-pam/releases
--
You received this bug notification because you are a
Fixing this in noble at this time will require a feature freeze
exception, because we would be changing behavior.
The default for user_readenv in pam_env is 0 (off). In the sshd config,
ubuntu/debian ship a pam config that sets it to on (1), therefore
~/.pam_environment will be read if it exists.
Mantic verification
In all architectures, except i386, the new test passed.
Here is a log from the amd64 run[1]:
4333s autopkgtest [16:47:27]: test ssh-gssapi: [---
4333s ## Setting up test environment
4333s ## Creating Kerberos realm EXAMPLE.FAKE
4333s Initializing database
Jammy verification
In all architectures (except i386, which is a known failure everywhere)
the new ssh-gssapi test passed.
Here is the run on amd64[1]:
3438s autopkgtest [16:33:21]: test ssh-gssapi: [---
3438s ## Setting up test environment
3438s ## Creating Kerberos realm
** Description changed:
[ Impact ]
The gssapi-keyex authentication mechanism has been inadvertently broken
in openssh. It comes from a distro patch[1], and while the patch still
applied, it was no longer correct.
Without the fix, sshd will fail to start if gssapi-keyex is listed
I added an sssd task due to the workaround we had to add to it in
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2058576 (we don't
install faketime). Should faketime be fixed, then we can revert that
change in sssd.
** Also affects: sssd (Ubuntu)
Importance: Undecided
Status: New
The verification of the Stable Release Update for apt has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for apt has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/openssh/+git/openssh/+merge/462619
--
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/2058276
Assignee: Andreas Hasenack (ahasenack)
Status: In Progress
--
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/2058276
Title:
Improve ssh-gssapi DEP8 test
Status
> Andreas Hasenack (ahasenack)
** Changed in: openssh (Ubuntu Mantic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
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.n
** Description changed:
[ Impact ]
- * An explanation of the effects of the bug on users and
+ The gssapi-keyex authentication mechanism has been inadvertently broken
+ in openssh. It comes from a distro patch[1], and while the patch still
+ applied, it was no longer correct.
- *
** Description changed:
- The Authmethod struct now have 4 entries but the initialization of the
- method_gsskeyex in the debian/patches/gssapi.patch only have 3 entries.
+ [ Impact ]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to
I just looked at the changes, and I would prefer to have a new SRU bug
for those, yes please.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2029473
Title:
Queued where? I don't see it in xenial unapproved. If it's just fixing
the autopkgtests, not the software-properties code or anything else in
debian/*, then no need for a new SRU bug. Just make sure to build it
with the appropriate -v parameter to include all changes since
0.96.20.10 (IIRC).
--
Ah, software-properties, sorry, I still had update-manager in my mind.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2029473
Title:
Backport Ubuntu Pro to
Version 0.96.20.10 passed in xenial/amd64 about 10 days ago (via an
ubuntu-advantage-tools update), but version 0.96.20.12 failed a few days
before. I triggered another run just in case.
If that new run also fails, then something is going on, and it has to be
sorted out before this update can be
The verification of the Stable Release Update for python2.7 has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for openldap has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
I think you missed the extra arg to userauth_gsskeyex()
--
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/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss patch for
I have an autopkgtest for gssapi, adding one now for keyex.
--
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/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss patch for
Quick test with
https://launchpad.net/~ahasenack/+archive/ubuntu/openssh-
gsskeyex-2053146/+packages on jammy (but there are builds for other
releases too), seems to work:
Mar 13 20:52:58 j-keyex sshd[1638]: Authorized to ubuntu, krb5 principal
andreas@LOWTECH (krb5_kuserok)
Mar 13 20:52:58
Prepping builds, and I also want to add an autopkgtest for this.
--
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/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss patch for
** Also affects: openssh (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu Noble)
Importance: Critical
Assignee: Andreas Hasenack (ahasenack)
Status: In Progress
** Also affects: openssh (Ubuntu Mantic)
Importance: Undecided
https://src.fedoraproject.org/rpms/openssh/c/c04e468b07b38471377fc7a648e1737021ea7148
--
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/2053146
Title:
openssh 8.9p1 for
Checked and focal-fips and bionic-fips are not affected.
Jammy is, as reported here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/2054609
Title:
package ntp Jammy
** Changed in: openssh (Ubuntu)
Status: Incomplete => In Progress
--
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/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss
Checking the jammy amd64 autopkgtest runs[1], we can see that the top
most one is the run for this sru. Its log[2] is showing, at the end, a
good run, but if you look more carefully, there are some test failures
that apparently are being ignored.
In particular:
1910s
Taking a look at another focal result from the table in comment 49:
focal amd64 pam-python 1.0.7-1ubuntu1 4 python2.7/2.7.18-1~20.04.4
No hints in the hints-ubuntu repository, focal branch.
But there is a migration-reference/0 run that failed that exact same
version:
1.0.7-1ubuntu1
> So that would explain it not being flagged for s390x, but not for amd64. I'm
> still puzzled: I didn't find
> another hint.
Ah, it's because of a migration-reference/0 run from last year:
5.3.1-1ubuntu1 migration-reference/0 None2023-06-20 09:25:36 UTC
0h 37m 11s schopin fail
I grabbed one of the focal failures from comment #49, mercurial:
focal amd64 mercurial 5.3.1-1ubuntu1 4 python2.7/2.7.18-1~20.04.4
That is indeed mostly red in [1], including the recent run with
python2.7 from this SRU.
And it's not showing up as a failure in the excuses[2] report.
But it's
I noticed this SRU was prepared without the SRU Template[1] filled in.
While most of the data we want is in the bug description as is (what's
wrong, test plan), it's lacking an analysis of what could go wrong.
That boat has sailed now, and doing an analysis of the patch right now,
basically what
The verification of the Stable Release Update for cups has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
** Changed in: tzdata (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- Regression after update: timezone changed unexpectedly
+ timezone changed unexpectedly
** Description changed:
A user reported this regression on
Given
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/comments/5,
I don't think it's a regression in the update. Removing the regression-
update tag.
** Tags removed: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
That happens also with the current version of tzdata.
Starting with:
$ dpkg -l tzdata|grep tzdata
ii tzdata 2022a-0ubuntu1 all
$ date
Mon Mar 4 12:22:38 UTC 2024
# the current timezone (UTC) was configured via dpkg-reconfigure tzdata
$ sudo apt reinstall tzdata=2022a-0ubuntu1
Sponsored for noble.
** Changed in: ppa-purge (Ubuntu Noble)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2036761
> d/control is used on the official gtk desktops such as budgie.
Excuse my unfamiliarity with desktop packages, but I don't understand the above
statement. Until someone from desktop reviews this, my question would be very
basic: what is the problem this is trying to solve? What is happening,
Left comments in the MP.
** Changed in: console-setup (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/2054681
Title:
Merge
I did a quick test in a jammy VM, and didn't observe this change:
ubuntu@j:~$ date
Fri Mar 1 13:29:18 EST 2024
ubuntu@j:~$ dpkg -l tzdata
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required
Hi Vladimir,
I'm sorry to hear that. What was the previously timezone that you had
set? Just EST?
I filed https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718
about your report, if you could please amend it with more details.
** Tags added: regression-update
--
You received this bug
Public bug reported:
A user reported this regression on
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739:
"""
Hello.
After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to
2024a-0ubuntu0.22.04
the previously set EST time zone was automatically changed to "America/Adak" or
The verification of the Stable Release Update for tzdata has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The 7 day aging period will be hit later today. Releasing it now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2052739
Title:
tzdata 2024a release
Status in tzdata
@security, could you please sign off on this tzdata SRU, according to
the SRU procedure[1] for this package?
1. https://wiki.ubuntu.com/StableReleaseUpdates#tzdata
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in
Hello Benjamin, or anyone else affected,
Accepted tzdata into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2024a-0ubuntu0.20.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Benjamin, or anyone else affected,
Accepted tzdata into mantic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2024a-0ubuntu0.23.10 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Benjamin, or anyone else affected,
Accepted tzdata into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2024a-0ubuntu0.22.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Finally, the SRU doc also says this: "Uploads should also be made to any
releases supported via ESM."
Are you going to drive that as well?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
I'm not familiar with this package, so maybe not the best person to
review this SRU, but here is another question. The SRU docs on tzdata
also mention python3-icu, but I don't see an update for that package
here or in the unapproved queue. Is that necessary? Or is it just about
verifying that
The SRU documentation[1] on tzdata describes other, or additional, tests, to be
performed in this package. Is that:
a) assumed, and will be done?
b) autopkgtests cover it?
c) was forgotten, and should be added to the test plan?
1. https://wiki.ubuntu.com/StableReleaseUpdates#tzdata
--
You
Hello Bryce, or anyone else affected,
Accepted openldap into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openldap/2.5.17+dfsg-0ubuntu0.22.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
You can add something obvious, like -DMITCHELL_WAS_HERE :)
On Thu, 8 Feb 2024, 18:35 Mitchell Dzurick, <2002...@bugs.launchpad.net>
wrote:
> That's a great idea Andreas! It's a little difficult to pinpoint the
> exact OPT flags as they are bunched up with the other compiler flags, so
> I'll add
Hello Nafees, or anyone else affected,
Accepted python2.7 into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python2.7/2.7.18-1~20.04.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Maybe it's just me, but could we please clarify in the test plan exactly
what flag changes are we expecting? Given the change is to honor or not
the "OPT" flags, I was expecting an additional test plan that would set
those, and then show that they are included when the workaround var is
set.
mantic is releseable, but I'll wait for the jammy results until the end
of my shift. If they are still red, I can release just mantic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
The migration-reference/0 runs passed, to the dep8 results are still not
good. I retriggered the failing arm64 tests one more time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
> Quick question: is pkcs11.txt a default filename used anywhere else?
Where did the filename come from?
¯\_(ツ)_/¯
There is a lot (a lot) of history here, buried deep somewhere in the
internet...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Tags removed: verification-done-jammy
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037604
Title:
Backport packages for 22.04.4
Technically, the verification from prior comments was performed on
23.2.1-1ubuntu3.1~22.04.1, not 23.2.1-1ubuntu3.1~22.04.2. I think they
need to be done on the mesa package that is in proposed now, which is
.2.
--
You received this bug notification because you are a member of Ubuntu
Touch
Hello Timo, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1~22.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Lee, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1~22.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Please amend the test case to test with both the GA and the (affected)
6.1 OEM kernels.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2051068
Title:
GUI crashed after
In the ubuntu armhf DEP8 infrastructure, this is what /proc/self/status
looks like when that failing test starts (I added a "cat
/proc/self/status" to debug):
Name: cat
Umask: 0002
State: R (running)
Tgid: 1105
Ngid: 0
Pid:1105
PPid: 1102
TracerPid: 0
Uid:100010001000
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/2051118
Title:
DEP8 error on armhf
Status in libseccomp package in Ubuntu:
In Progress
libseccomp/20231225_015646_12139@/log.gz
** Affects: libseccomp (Ubuntu)
Importance: Undecided
Assignee: Andreas Hasenack (ahasenack)
Status: In Progress
** Tags: update-excuse
** Changed in: libseccomp (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack
Reproducing the bug
root@j-dnsmasq-2042587:~# apt-cache policy dnsmasq
dnsmasq:
Installed: 2.86-1.1ubuntu0.4
Candidate: 2.86-1.1ubuntu0.4
Version table:
*** 2.86-1.1ubuntu0.4 500
500 http://br.archive.ubuntu.com/ubuntu jammy-updates/universe amd64
Packages
100
Reproducing the bug
root@j-dnsmasq-2045570:~# apt-cache policy dnsmasq
dnsmasq:
Installed: 2.86-1.1ubuntu0.4
Candidate: 2.86-1.1ubuntu0.4
Version table:
*** 2.86-1.1ubuntu0.4 500
500 http://br.archive.ubuntu.com/ubuntu jammy-updates/universe amd64
Packages
100
Ah, I now understand what happened in the comment above. I only upgraded
the bin:dnsmasq package, and not bin:dnsmasq-base. Both need to be
upgraded, i.e., like a normal "apt ugprade" or "apt dist-upgrade" would
do.
--
You received this bug notification because you are a member of Ubuntu
Touch
While performing the jammy verification, it happened once again what I
first saw in
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2045570/comments/4:
dnsmasq doesn't crash, but starts spinning 100% CPU and becomes
unresponsive.
I double checked that the source package contains the patch
The autopkgtests are green now.
--
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/2042587
Title:
jammy's version breaks existing dhcp scripts with relay
Status in dnsmasq
I updated the tasks on this bug after having verified what has LXC_DEVEL
set to 1, so we should be good now in terms of affected releases.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Food for thought for an SRU, here is an example of an upstream that
noted[1] this problem:
NOTE: If you use the `liblxc-dev` package and get compile time errors
when building the `go-lxc` module,
ensure that the value for `LXC_DEVEL` is `0` for your `liblxc` build. To check
that, look
I imported your noble debdiff and pushed to this branch:
https://code.launchpad.net/~ahasenack/ubuntu/+source/lxc/+git/lxc/+ref/noble-
lxc-drop-devel-2039873
If you run "git ubuntu clone lxc; cd lxc; git ubuntu remote add
ahasenack; git checkout noble-lxc-drop-devel-2039873" you should have a
** Also affects: lxc (Ubuntu Noble)
Importance: Undecided
Status: Confirmed
** Also affects: lxc (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Mantic)
Importance: Undecided
Status: New
--
You received this bug notification because
Hello dann, or anyone else affected,
Accepted util-linux into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.37.2-4ubuntu3.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
I'll also note that the patch actually disables `libreadline` support in
chfn/chsh, so whoever was rebuilding these from source will get this
change in behavior. But that's how upstream decided to handle this going
forward.
** Changed in: util-linux (Ubuntu Jammy)
Status: In Progress =>
Hello Joao, or anyone else affected,
Accepted util-linux into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.37.2-4ubuntu3.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
The verification of the Stable Release Update for modemmanager has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Thank you for the detailed and unambiguous verification!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/2047008
Title:
[SRU] Add Telit FN990 compositions
Status in
Public bug reported:
The zlib detection code seems faulty:
checking for possibly buggy zlib... yes
configure: error: *** zlib too old - check config.log ***
Your reported zlib version has known security problems. It's possible your
vendor has fixed these problems without changing the version
> However, some users are known to build their own binaries from this Ubuntu
> source and therefore could be
> impacted.
Do you know of users rebuilding specifically util-linux and enabling
those tools? What was it about this specific CVE and specifically util-
linux that caught your attention
Hello Michael, or anyone else affected,
Accepted fluidsynth into mantic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/fluidsynth/2.3.3-2.1ubuntu0.23.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
1 - 100 of 1175 matches
Mail list logo
