I seem to be suffering from the same issue after upgrading to 22.04.1,
but only on one device. My OnePlus Nord N10 (running Android 11) fails
to connect to the Ubuntu hotspot, showing the message WPA3 (SAE
Transition Mode). However, my iPad Pro (iOS 15.6) and my Roku (11.0.0)
have no trouble
Hey Tommy, I'm in a similar boot to Frederick.
Thanks for taking the time to list your steps.
What command did you use to unpack your initrd?
After copying over the drivers what command or tool did you use to repack it?
Was it dracut, initramfs-tools, or something else entirely?
Thanks again!
i wonder if things work fine if called with pkexec.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1958055
Title:
sudo apport-kde is in a different design (stripped
Ah! The rule
```
audit dbus bus=system,
```
is the problem. It is tagging every dbus match to be audited. You can
drop that rule entirely, and just add dbus allow rules as needed, like
the first 3 rules. Or you could allow all dbus system bus accesses by
dropping the ```audit``` keyword, in
Public bug reported:
Error just popped up while I was browsing, i.e. I was not upgrading at
the time.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: initramfs-tools 0.140ubuntu13
ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
Uname: Linux 5.15.0-33-generic x86_64
with in the profile block, eg.
profile redshift {
or something similar, add the following rules
dbus send bus="system" path="/org/freedesktop/DBus"
interface="org.freedesktop.DBus"
member="{GetNameOwner,StartServiceByName,AddMatch}",
dbus send bus="system"
There was another security upload on 27th of may which is built on all
arches, thus this rebuild is no longer needed.
please reject cups from focal unapproved.
** Changed in: cups (Ubuntu Focal)
Status: In Progress => Fix Released
** Changed in: cups (Ubuntu Focal)
Status: Fix
Ah - is it that the same version is now built and published in Groovy
and we can't safely copy the binary backwards? => correct.
I didn't check if we can or cannot safely copy the binary backwards, but
imho we should not.
This is not going via focal-security, because the security issue has
For me I have 32GB of ram and it was killing my entire user session and
dropping me back to the GDM. (It took me over a week to realise this was
happening and I was kicked back to login losing all work at least 15
times, having to log back in produced a lot of log spam that hid the OOM
message, I
@rikka0w0 are you willing to test a kernel patch for this issue?
--
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/1784499
Title:
AppArmor treats regular NFS file access as
Yes, unfortunately the network work was deferred, its still a wip but is
not scheduled as a work item for the cycle. With that said we still hope
to get this fixed, I just can't promise it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Tags added: rls-kk-incoming
** Description changed:
In Ubuntu, we execute the full iptables shell testcases across all
architectures.
They seem to all pass everywhere, however
iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-
bitwise_0
is currently
Public bug reported:
In Ubuntu, we execute the full iptables shell testcases across all
architectures.
They seem to all pass everywhere, however
iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-
bitwise_0
is currently failing on s390x like so:
command17FAIL
Public bug reported:
[Impact]
* FTBFS on riscv64 in focal in unittest of volume test
* Disable that unit test, as later releases do not run unittests on riscv64,
and it's better to have up to date pulseaudio on riscv64 (with many security
fixes), even if it doesn't completely correctly work.
Public bug reported:
no change rebuild to get riscv64 build out
[Impact]
* riscv64 build of cups security update failed, and then succeeded in groovy.
See https://launchpad.net/ubuntu/+source/cups/2.3.1-9ubuntu1.1
* it means that focal-updates & focal-security are lacking a security update
@georgiag we could move the abstraction include to "include if exists"
to take care of the depends. Generally speaking evince shouldn't depend
on apparmor, but of course make use of it if it is available.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I've attempted to prepare naive SRUs and it doesn't get me far yet. The
issue is that unified cgroups2 support in xenial's systemd is
rudimental, and falls apart very quickly with none of the xenial
userspace expecting or able to work correctly with unified cgroups2
setup.
I fear that it will not
Usually we try to avoid using embedded copies of code. Is it at all
possible to convert some of the affected packages to use/reuse a shared
library instead?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
Just adding my support to those rallying for change on this issue.
I tried colas' script in the background, but whilst it does report that
it's resetting location-mode, it doesn't seem to be solving the problem
for me (on Jammy Jellyfish).
I also noticed there's another schema/key,
Public bug reported:
playback of mkv/h264 is corrupt. Works fine in VLC
Description:Ubuntu 22.04 LTS
Release:22.04
totem:
Installed: 42.0-1ubuntu1
Candidate: 42.0-1ubuntu1
Version table:
*** 42.0-1ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64
** Description changed:
[impact]
now that jammy has moved to using unified cgroup2, containers started on
jammy must also use unified cgroup2 (since the cgroup subsystems can
only be mounted as v1 or v2 throughout the entire system, including
inside containers).
However, the
Public bug reported:
This has happened more than once while using the Google Chrome Browser.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
And s390x =(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows incorrect counters with iptables-nft
Status in iptables package in
The newly enabled autopkgtest appears to regress on i386 =/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows incorrect counters with
# dpkg-query -W kmod
kmod27-1ubuntu2
# modinfo ./zstd.ko.zst
modinfo: ERROR: Module alias ./zstd.ko.zst not found.
upgraded to new kmod:
# dpkg-query -W kmod
kmod27-1ubuntu2.1
# modinfo ./zstd.ko.zst
filename: /lib/modules/5.4.0-109-generic/kernel/crypto/./zstd.ko.zst
alias:
initramfs-tools ADT test passed on retry.
the kernel tests mentioned above are now for EOL kernels that have since
all rolled to 5.13.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
1) downgraded openssl to 1.1.1f-1ubuntu2.9 such that it doesn't have
double free fix that was released in
https://launchpad.net/ubuntu/+source/openssl/1.1.1f-1ubuntu2.10
2) installed old pka module from commit
b0f32fa05298bf9e3997ea43fc1c11b90e0d662f
3) installed focal-updates version of curl
It seems that view, as provided by vim.tiny now attempts to load
defaults.vim, which is shipped in the large vim-runtime package. All
vims depend on vim-common. It would seem to me that we should move
defaults.vim from vim-runtime to vim-common.
--
You received this bug notification because you
Private bug reported:
Random System freeze which required a hard refresh like unplugging The
Power Totally and then restarting it
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19
Uname: Linux
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-meta (Ubuntu)
Importance: Undecided => Critical
** Changed in: ubuntu-meta (Ubuntu)
Milestone: None => ubuntu-22.04
** Tags added: rls-ff-incoming
** Tags removed: rls-ff-incoming
**
** Changed in: iptables (Ubuntu Impish)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows
I managed to get the card back with pulseaudio:
- logout of desktop session/xrdp
- systemctl restart xrdp
- unplug usb sound card from Ubuntu (this is not a usb redirection issue)
- login to xrdp
- run pulseaudio-dlna python script (not sure if it's related but was running
previously for dlna,
Public bug reported:
This device was working fine until I applied the latest patches/kernel
Bus 001 Device 013: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like
Sound Device
Before: logged in to Ubuntu desktop with xrdp. Plugged in the USB sound card
and pulseaudio detected the card as
** Tags added: rls-jj-incoming
--
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/1965180
Title:
apt-add-repository requires --login for private repos, breaking
** Tags added: rls-ii-incoming
** 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/1965293
Title:
systemd/248.3-1ubuntu8.2 ADT test failure
Public bug reported:
On Focal, in an automated environment (such as a launchpad builder), a
used can do the following workflow:
curl
"https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb
Backporting 099619957a0 to xenial will mean that systemd will gain
ability to use cgroups2 as shipped in the xenial's ga v4.4 kernel.
it will mean that xenial containers on top of bionic's ga kernel will
fail to use cgroups2.
however at the time it was an experimental feature which was not
** Description changed:
[impact]
now that jammy has moved to using unified cgroup2, containers started on
jammy must also use unified cgroup2 (since the cgroup subsystems can
only be mounted as v1 or v2 throughout the entire system, including
inside containers).
However, the
hm, $ lxc launch --vm ubuntu:xenial fails for me
** Description changed:
[impact]
now that jammy has moved to using unified cgroup2, containers started on
jammy must also use unified cgroup2 (since the cgroup subsystems can
only be mounted as v1 or v2 throughout the entire system,
** Description changed:
[impact]
now that jammy has moved to using unified cgroup2, containers started on
jammy must also use unified cgroup2 (since the cgroup subsystems can
only be mounted as v1 or v2 throughout the entire system, including
inside containers).
However, the
Irrespective of ESM status, we have always had extremely long support
overlaps both backwards and forwards between ubuntu releases.
At the moment, my only solution is to use lxd vms; i.e.
do
$ lxc launch --vm ubuntu:xenial
However, I say for the sake of ease of development, testing, upgrades,
On 21.10, zfs-linux packages 2.0.6-1ubuntu2 generate incorrect boot
entries for snapshoted systems, please upgrade to 2.0.6-1ubuntu2.1.
Snapshots created with the broken old version are not bootable.
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in:
Ubuntu 22.04 daily images testing issues have been resolved and a new
image promoted, jammy installs are now working correctly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
This is fixed release in pending images; which are failing installation due to
other bugs.
Once those bugs are resolved, and a new image is promoted, it shouldn't
experience this zfs issue.
So we are blocked on getting Ubuntu Desktop ISO passing the daily automated
testing and getting promoted.
sorry, I was confused a bit about the issue. I have no objection to
uploading the diff from #7. Still while the patch makes the immediate
mctp issue go away from the current tests it isn't a full fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
"To unblock kernel development we need apparmor to never fail ADT
testing in devel series, as new kernel is developed. We do not want to
hint to ignore it, because we must never regress apparmor."
unfortunately this is just not possible with the way kernel development
works. The addition of new
Ah, it is president's day & night time in australia.
I will upload this, to unblock releasing jammy kernels. And we can
revisit this once everyone is back to back this out; or get a different
implementation in.
Blocking kernel testing with app armor test suite is developer time
critical, and
@alexmurray @jjohansen
When are updated apparmor going to be upload that continues to pass
existing test-suites / adt?
At this point failing apparmor ADT, blocks releasing all kernels in
jammy, preventing development of all kernels, and prevents security
kernel fixes.
To unblock kernel
I should note that mctp is NOT part of the abi change in 3.0.4. This
means by default mctp mediation will not be enforced by policy. It will
be accepted in rules if present but since policy was not developed with
mctp in mind, turning it on by default for the policy would be an abi
break and
@arighi: mctp is already supported in the 3.0.4 release that @alexmurray
is working on merging
--
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/1961196
Title:
apparmor
systemd stuff did either partition or fs but not both.
we used the cloud initramfs implementation on the desktop, because yes,
it doesn't do cloud-init.
probably moving that out of the common seed will help.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Downloaded the iso today doesn't mean the iso was built today, or if it
contains this update.
jammy installer iso are attempted to be built daily, but are only
published once they pass automated smoke testing and validation. The
last image that passed that was built on 2nd of February. And builds
Fix was released in busybox 1:1.30.1-7ubuntu3 and requires initramfs
rebuild
your screenshot clearly shows version number 1:1.30.1-7ubuntu2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
It should be fixed as of the AppArmor 3.0 release. With 3.0 the handling
of jobs doesn't stop with an error unless --abort-on-error is specified.
Instead the parser will keep track of the last error and return that
there was an error, but it will keep processing the rest of the jobs.
We did not
Indeed https://bugs.launchpad.net/apparmor/+bug/1384746/comments/2
should be tracked else where. It really should split out into two
separate tracking issues.
1. either generating the feature file from the kernel on build. To track
this I have opened
This is indeed upstream, and works as far as it goes. There are
currently issues when crossing system namespace boundaries but those are
being treated as separate issues. The stacking it self works policy when
crossing ns boundaries has to be aware of it and more relaxed than we
would like.
--
To be fair we don't need the empty pthread in the initramfs, we only
need the non-empty dynamically opened libgcc_s, but it shouldn't hurt
either.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Changed in: initramfs-tools (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1950996
Title:
Missing
** Changed in: initramfs-tools (Ubuntu Jammy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958594
Title:
Boot error:
With above, when testing I now get:
Adding binary /usr/lib/initramfs-tools/bin/gcc_s1-stub
Adding binary /lib/x86_64-linux-gnu/libgcc_s.so.1
Adding binary /lib/x86_64-linux-gnu/libc.so.6
Adding binary-link /usr/lib64/ld-linux-x86-64.so.2
Adding binary
$ gcc -Wl,--no-as-needed -shared -l:libpthread.so.0 -l:libgcc_s.so.1 -o
bla
$ ldd bla
linux-vdso.so.1 (0x7ffe0e7e6000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7feeeaa32000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
With that branch rebased, and typpos fixed up testing locally does
produce this:
Adding binary /usr/lib/initramfs-tools/bin/gcc_s1-stub
Adding binary /lib/x86_64-linux-gnu/libgcc_s.so.1
Adding binary /lib/x86_64-linux-gnu/libc.so.6
Adding binary-link /usr/lib64/ld-linux-x86-64.so.2
Adding binary
** Changed in: initramfs-tools (Ubuntu Jammy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1950996
Title:
Missing all
We have been bitten by this before. And Last time I did proposed to do
this:
- create a stub binary tha tis linked with pthread and libgcc_s
- copy_exec that into the initramfs
https://code.launchpad.net/~xnox/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+merge/385243
This ensures that
Autopkgtests completed successfully on both impish and focal.
** Tags removed: verification-needed verification-needed-focal
verification-needed-impish
** Tags added: verification-done verification-done-focal
verification-done-impish
--
You received this bug notification because you are a
@sil2100
--disable-test-modules \
override_dh_auto_test:
+ dh_auto_test --builddir=build-deb
are needed together to enable building and running unittests during
build.
Note previously focal builds did not run unittests at all.
The autoconf help text for the option says "disable
** Bug watch added: Debian Bug tracker #990092
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990092
** Also affects: kmod (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990092
Importance: Unknown
Status: Unknown
--
You received this bug notification because
It feels like we should just copy libgcc_s.so.1 and libpthread always.
It is tiny in size and something is bound to use them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
: Dimitri John Ledkov (xnox)
Status: In Progress
** Also affects: initramfs-tools (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Impish)
** No longer affects: linux
** Description changed:
+ -- initramfs-tools
+
+ [Impact]
+
+ * linux supports xz compressed linux-firmware which saves disk space.
+ In focal, initramfs-tools only knows how to included uncompressed
+ firmware files (even when kernel supports loading compressed ones).
+ Newer releases of
** Description changed:
- kmod add zstd support
+ [Impact]
- * v27+ needs patches cherrypicked from v28
+ * To safe diskspace, upcoming devel series / hwe kernels may turn on
+ zstd kernel module compression. Kmod since impish support zstd support.
+ But in order to keep hwe kernels at
I wonder if I should have included feature backports to support
compressed kernel modules & coompressed firmware files
https://launchpad.net/ubuntu/+source/initramfs-tools/0.140ubuntu8
This would be actually useful, and would allow us to enable compressed
kernel modules for jammy and hwe-5.15
uploaded into unapproved queue
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958904
Title:
autopkgtest is failing on jammy with "no space left on device"
@brian-murray
Unfortunately, it would mean that kernel-teams adt-matrix would still
need to be hinted, as it does strict adt test runs against each kernel
flavour, against packages in updates only, and enforces that every
kernel flavour is tested. However, I also think that this adt test may
not
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Committed
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Critical
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug not
I guess i can modify init-system-helpers again, to dump journal from the
build such that we can see what is going on.
** Also affects: launchpad-buildd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Summary changed:
- Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142.
+ error: too early for operation, device not yet seeded or device model not
acknowledged Install failed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
even with reverted init-system-helps snapd units fail to start during
launchpad-buildd
https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650698
Setting up snapd (2.54.2+22.04ubuntu1) ...
Created symlink
/etc/systemd/system/multi-user.target.wants/snapd.apparmor.service →
Public bug reported:
https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565
New deb-systemd-invoke added functionality for systemd v250 which ubuntu
does not have yet. But it also appears to break postinst calls to deb-
systemd-invoke, at least as seen during snap builds in lxd
Jammy has not had any changes to the apparmor packages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1955434
Title:
Driverless printing detection does not work
Status in
Public bug reported:
Sometimes if I run `pulseaudio -k` a few times, sound returns.
Sometimes if I run `sudo alsa force-reload`, sound returns.
Sometimes if I shutdown and start the laptop, sound returns.
This first occurred a few months ago when I was running 20.04, and I
upgraded to 21.10 in
** Description changed:
[Impact]
- * Engine crashes when loading the configuration more than once
+ * Engine crashes when loading the configuration more than once
- * Upstream started to avoid loading engines twice by using dynamic ids
+ * Upstream started to avoid loading engines
** Changed in: iptables (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows incorrect
On Tue, Nov 23, 2021 at 1:40 PM Jason A. Donenfeld
<1892...@bugs.launchpad.net> wrote:
>
> I think he meant to post this on
> https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1950317
>
That makes a lot more sense. Commented my opinion there about the need
for key generation tooling.
@ahasenack I feel a bit lost here. This bug report is about how one
should or shouldn't propagate DNS servers after establishing a wireguard
based connection.
This has nothing to do w.r.t. creating keys.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thank you for working with OpenSSL upstream, explaining the issue at
hand, for everyone to eventually understand what is going on, and
finally coming up with a solution on the OpenSSL side of the APIs that
is accepted by upstream into development v3 branch and stable 1.1.1
branch.
I have started
Public bug reported:
[Impact]
* Engine crashes when loading the configuration more than once
* Upstream started to avoid loading engines twice by using dynamic ids
to track the loaded engines correctly
* OpenSSL 3 merge https://github.com/openssl/openssl/pull/17073 (bugfix
& testcase)
*
> Do we even know for sure this krb5-k5tls is enough for fips
compliance, and that it replaces *all* crypto code in kerberos with
openssl calls?
No it does not. But intention is to make the over the network
communications with TLS to be FIPS-TLS compliant which is cheaper to
certify when reusing
Autopkgtests have now all passed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1940528
Title:
curl 7.68 does not init OpenSSL correctly
Status in curl package in Ubuntu:
@arighi suggests used to be installed when one used to provide "needs-
suggests" restrictions or some such, but that got deprecated, so no
suggests are not getting installed by default.
However, we have a multi year MIR to seed and install nftables by
default let me check the status of that
** Changed in: initramfs-tools (Ubuntu)
Status: New => Triaged
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Also affects: initramfs-tools (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: initramfs
> How will you test that the change does not regress any wget behavior?
In default Ubuntu configuration, either no openssl configuration is provided,
or it contains no settings that affect wget. This code path changes how/when
openssl configuration is loaded and used by openssl. One should
Not only patch was missing, it was partially missing. reuploading again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1940528
Title:
curl 7.68 does not init OpenSSL
Reuploaded curl into focal proposed, with series fix & on top of
security upload that has happened since.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1940528
Title:
curl
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
I currently do not have a more regular smartcard setup to test out a
hardware pk11 engine with openssl, which is typically the most common
one. But I can use software gost engine to test out that algos provided
by the engine operate correctly.
Installed openssl from proposed, and gost engine.
$
In addition to the changelog versions it seems to me that the debdiff is
potentially a bit missleading:
1) the shell testcases are not executed neither during build, nor during
autopkgtest. As they seem to need root, it would be nice to add
autopkgtest that would do:
cd iptables/tests/shell;
The proposed patch looks ok.
The version numbers are interesting. Impish release is at
1.8.7-1ubuntu2, and impish upload 1.8.7-1ubuntu3 got only published
into Jammy.
So the correct version numbers to use will be ubuntu4 for jammy and 2.1
for impish, I will correct that for SRU.
--
You
There is now only a transient ADT regression in Regression in linux-
hwe-5.13 (armhf), which is not a valid ADT because armhf ADT runs in lxd
containers and does not boot the requested kernel.
Please release this package.
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
When playing any video other than a youtube video, the sound quality is
terrible. It's very tinny and screechy as if it were blowing out the
speakers, but even at quiet noise levels. I've tried numerous fixes
including editing the config files for pulse audio,
301 - 400 of 4696 matches
Mail list logo
