cross test of lxd fails, but i386 is not supported under ESM and i'm not
sure if i386 cross-arch autopkgtest is valid at all.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
autopkgteest & general usage of lxc 3.0.3-0ubuntu1~18.04.3 works with
host kernels on bionic's GA kernel and on hwe v5.4 kernels now.
verification done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received
--disable-gpu-driver-bug-workarounds did not work for me, but deleting
GPUCache did. Keep in mind that GPUCache could be inside a profile
folder like ~/.config/google-chrome/Profile 1/.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
it must be released in bionic-updates.
bionic-proposed is insufficient.
this follows the previous SRUs that fixed adt only, which were awaiting on "an
end-user visible sru to come in the future" which never has.
autopkgtest infrastructure has no ability to always test against proposed
pocket, a
I thought as part of this work we agreed to always unpack tar with
xattrs, but i'm not sure how to check if this was done or in place. will
investigate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
Public bug reported:
Trying to fix broken install
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: python3-software-properties 0.99.22.7
ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-40-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm
it does feel too many that it should be included by default, not sure
why the rest of the tty/serial drivers are not included, or how come
this one is not scoped under usb/hid, it is fairly small, and built on
arm64 only i think, thus it is useful to include by default - as at best
it is unlikely
I was steered here by google and I guess this is the wrong place.
I did report this, if you care to follow it, here..
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1286
Otherwise feel free to delete this report.
** Bug watch added:
Public bug reported:
Software versions:
Networkmanager: 1.42.6-1
nm-connection-editor: 1.32.0-1
networkmanager-openvpn: 1.10.2-1
openvpn: 2.6.2-1
Arch Linux kernel: 6.2.13-zen-1-zen
While trying to import an ovpn file downloaded from NordVPN, nm-
connection-editor exits with a coredump.
prctl behavior was changed by
c2350a7eca5c UBUNTU: SAUCE: Stacking v38: LSM: Specify which LSM to
display
it introduces a short circuit to protect against 2 new lsm prctl
commands being invoked without a major lsm, and unfortunately makes the
mistake that using lsm_slot == 0 means there are no
Public bug reported:
$ snap connections --all | grep gnome
content -
gnome-3-28-1804:gnome-3-28-1804 -
content -
I'm not too sure if updates from sed1991s above are correct
--
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/1991975
Title:
dev file system is mounted without nosuid or
Public bug reported:
Enter code on ubuntu.com/pro/attach is not a clickable url.
however ubuntu.com/pro and "register new account" are.
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Screenshot from 2023-04-26 12-05-00.png"
vmlinuz-6.2.0-18-generic is good, so regression introduced in 6.2.0-19
abi, suspecting new apparmor stack
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012136
** Also affects: apparmor
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu)
Importance: Undecided
alexsander-souza - if you can make this on per-distro basis that would
be great. Indeed empty (thus apparmor=1) should work on jammy and up,
but yes we can never know. And having it for lunar onwards would be
super nice, because yes overlayfs apparmor things got fixed a while back
and are expected
Lunar kernel will need SRU to be fixed up.
And separately, we could check if we can get rid of apparmor=0 for all
supported releases or not, in next mass release.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Now about those bugs, it is true that apparmor and overlayfs used to not
play along.
Depending on support matrix we can attempt to turn apparmor back on.
Equally it is buggy that Ubuntu kernel does not work with apparmor
turned off.
It would be nice to investigate if we can at least enable
** Description changed:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which I
don't believe was part of the 20230319 serial. I don't have access to
the maas server, so I can't directly check any log
horay i managed to reproduce it locally.
** Also affects: linux (Ubuntu)
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/2016908
I am annoyed that i cannot reproduce this locally outside of MAAS.
--
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/2016908
Title:
Unable to deploy hosts with lunar images
nearby, and the same with the low-end 5-GHz channels. The high-
end channels in Canada from 149 to 161 are far less occupied, fully
available (not just for "indoors"), and don't have any Dynamic Frequency
Selection (DFS) or Transmit Power Control (TPC) restrictions.
John
--
You received this
> is that having a visible impact for users? like was your computer not
able to connect to some access point?
Yes. I just hit this problem on my new Raspberry Pi 400 with Ubuntu.
The Raspberry Pi OS dated February 21, 2023, based on Debian 11
(bullseye), sets my Wi-Fi region code to Canada
@brian
I'm sorry, but with block-proposed-focal set it means that affected
users on riscv64 don't have uptodata pulseaudio.
can we please release this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
arge at 77%,
status charging, and charge report increasing as expected. Reverting to
kernel-5.15.0-69 shows 76% charge, status "charging."
john@stolat:~$ upower -i /org/freedesktop/UPower/devices/battery_BAT0
native-path: BAT0
vendor: Hewlett-Packard
model:
Security's recommendation is to actually use the console abstraction, as that
way you will pick up the improvements to console mediation automatically when
they land
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog
** Changed in: cloud-images
Status: Confirmed => Fix Released
--
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/1791691
Title:
PATH broken in systemd units
Traced this down in the base-passwd package to /usr/sbin/update-passwd.
Ran the command with --verbose and it throws the same error.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-passwd in Ubuntu.
This occurred to me during an apt dist-upgrade.
The file /etc/passwd.upwd-write does not exist.
Attempting to "touch /etc/passwd.upwd-write" gives a permission denied error.
I can write other files to the /etc/ directory.
Nothing in lsof has and an fd open to this file.
Forced a
Focal is in soft freeze atm, once the soft freeze is lifted this should
land
--
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/1964636
Title:
Incorrect handling of apparmor
Focal is in soft freeze atm, once that is lifted this should land
--
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/1993353
Title:
Add posix message queue IPC mediation
> The syslog-ng profile needs flags=(attach_disconnected) added to it
I failed to reproduce this with syslog-ng, but i guess i didn't
configure syslog-ng correctly to attempt attaching to /dev/log
I am also not sure of os-prober usage of logger is correct, and if it
actually wants to use that
The syslog-ng profile needs flags=(attach_disconnected) added to it
--
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/1826294
Title:
os-prober exits prematurely with
Steps i can reproduce:
wget https://bugs.launchpad.net/ubuntu/+source/os-
prober/+bug/1826294/+attachment/5652492/+files/reproducer.sh
chmod +x reproducer.sh
sudo journalctl -f -e &
clear
sudo ./reproducer.sh
--
You received this bug notification because you are a member of Ubuntu
Touch
This is Ubuntu desktop install. rsyslog.service is active and running,
systemd-journald-dev-log.socket is running.
--
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/1826294
** Attachment added: "reproducer.sh"
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1826294/+attachment/5652492/+files/reproducer.sh
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
yeah i get apparmor="DENIED" info="Failed name loookup - disconnected
path", which breaks os-prober.
** Changed in: os-prober (Ubuntu)
Importance: Undecided => Critical
** Also affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
** Changed in: rsyslog (Ubuntu)
Public bug reported:
When I run sudo apt upgrade, I have this error :
package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade:
tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so
», qui appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1
ProblemType:
I just encountered this bug for the first time today, and it's super
annoying!
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
$ uname -a
Linux john-desktop 5.15.0-67-generi
Public bug reported:
Updating base-files at point releases is pointless, misleading, and
causes confusing and anxiety
Can we please stop updating base-files at point releases?
Building new installer media, and calling it with a new .N number is
good, and helps to differentiate what the initial
sponsored into unapproved queue
** Changed in: lxc (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1886790
Title:
lxc
One should use ubuntu-drivers CLI or Additional Drivers GUI to install
or switch nvidia graphics stacks from one major series to another. It
ensures that correct matching pre-signed kernel drivers are installed
together with the right userspace (with and without gui stacks, as
needed).
--
You
we ought to sponosr
http://launchpadlibrarian.net/453184210/lxc_3.0.4-0ubuntu1_3.0.4-0ubuntu2.diff.gz
into bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1886790
Title:
Sigh, so this one is a bit of a pita. Minimal C code uses this and it is
easy to update that. The problem comes with the SWIG interface libraries
(python, ruby, etc) have baked these names into their API. We can update
those but then we stand a good chance of breaking some external code.
so some potential low level interfaces you can try probing for more
info.
/sys/module/apparmor/parameters/enabled
with the aa-status reporting apparmor module is loaded. I expect you
have access to this directory. Which means you can also check
/sys/module/apparmor/parameters/mode
to
Is there anymore info for this? Any kernel messages?
>From the error itself we can determine
The parser has root/admin privileges as it passed an early check for that
without giving an error.
It was able to open the kernel interface to remove the profile.
The likely error here is that it is not
I'd just like to repeat, this is Linux. Just because Ubuntu offers a
feature doesn't mean you have to use it. I'm using the "Linux Wifi
Hotspot" app created by Lakinduakash:
https://github.com/lakinduakash/linux-wifi-hotspot
It works just fine on Ubuntu.
--
You received this bug notification
Public bug reported:
apt source exact-source-package doesn't download the right source
package
when specifying source package, i expect the exact source package to be
downloaded.
example:
$ apt source linux-lowlatency => incorrectly downloads linux-meta-lowlatency
$ apt source --only-source
@sil2100 marked out test case in the bug report more clearly.
** Description changed:
This is *probably* the wrong package, but it's the best I can figure for
this, so here goes.
Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5,
UEFI, no secure boot. Testing
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=ubiquity
** Also affects: ubiquity (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Jammy)
Importance:
The best we can do, is to take notAfter time of the signing certificate
and add that as the signingTime, which will then be used by the Sign
command as given.
This will ensure the signature is within valid time-series.
I don't see an easy openssl API to sign things without any signature
setting PKCS7_NOATTR is not enough, as that only removes the smime
capabilities signed attribute, whilst signature timestamp remains.
--- ./regular.text 2023-01-23 11:42:49.992929526 +
+++ noattr.text 2023-01-23 11:42:59.288981639 +
@@ -128,7 +128,7 @@
object:
** Changed in: snapd (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.
https://bugs.launchpad.net/bugs/1993318
Title:
ZFS + Encryption installations of Ubuntu
have not been
able to figure out what makes the sound system fail, and I have not
been able to make it recover. Only way to recover seems to be to do a
cold reboot. A simple warm reboot does not fix the problem, but this
can be related to problem 1.
A few dumps
john@hydra:~$ dmesg
Note, Bionic and Focal will likely require more than just that patch.
There were multiple patches for Python 3 support landed in apparmor 3. I
am not sure what the exact combination required will be.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
> Which component is responsible for generating /etc/cloud/build.info?
livecd-rootfs, during image creation time.
https://git.launchpad.net/livecd-rootfs/tree/live-build/auto/build#n452
it'll have at least 1 value, serial (in the case of an OCI container),
normally 2: serial, build_name
> From
Attached is a possible patch to remedy some of the issues (and a few
other bugs i've seen in the backlog with errors re: EC2 and other
clouds). the gist:
1. change how we check if something is a cloud-image, generally
2. use /etc/cloud/build.info as a check if something is a Canonical cloud image
@sil2100, there is some additional testing. qa-regression-testing, pulls
in the apparmor regression tests. And they contain tests for
capabilities and mqueue behavior. These have not shown any regressions.
And have been tested on multiple machines.
These patches have also gone through the build
This bug does not seem to be present in Ubuntu 22.10, on the same
hardware.
--
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/1989602
Title:
Delay in updating charge status
In the triggered logs
PASS: test-execute
is present with new kernel and new systemd
-env=ADT_TEST_TRIGGERS=linux-meta-hwe-5.15/5.15.0.53.59~20.04.21 linux-
hwe-5.15/5.15.0-53.59~20.04.1 linux-signed-hwe-5.15/5.15.0-53.59~20.04.1
systemd/245.4-4ubuntu3.19'
all autopkgtests now pass https://people.canonical.com/~ubuntu-
archive/proposed-migration/focal/update_excuses.html#systemd
now testing if the new testcase is fixed with v5.15 kernels in focal.
Test request submitted.
Result history
https://autopkgtest.ubuntu.com/packages/systemd/focal/amd64
imho focal users on riscv64 deserve new pulseaudio
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1973734
Title:
FTBFS on riscv64 in focal
Status in pulseaudio
build successful
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.14/+build/23853226
** 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
This has now landed upstream, on the master branch as
c159d0925 Allow access to possible cpus for glibc-2.36
and has been cherry-picked back to 3.1, 3.0, 2.13, and 2.12 branches.
This schedules it for release in the 2.12.4 and 2.13.7, 3.0.8 releases
this week. Unfortunately 3.1.2 was cut last
Sorry if I'm missing something obvious but I've done a full apt upgrade
and tried to build wine again and the problem still persists so I don't
think the fix has released and the status is incorrect.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
name="apparmor/.null" is used to remove access to an already open file
that is being inherited and should no longer be available. Whether
because policy doesn't allow it. AppArmor can't just close the file
because the fd for the file might have meaning and closing the file
would free up the fd
@hypothetical-lemon you can try the fix if you want it is in the ppa
https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
@hypothetical-lemon yes we plan to SRU the fix to focal however a fix is
only needed in the userspace. The fix is in the apparmor userspace
policy compiler, the kernel is just enforcing what the compiler is
incorrectly telling it to enforce.
--
You received this bug notification because you are
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://code.launchpad.net/~xnox/ubiquity/+git/ubiquity/+merge/431831
should solve first boot post-install.
However, I don't think that will solve booting snapshot, or whenever on-
disk cached is missing/corrupted/out of date, and one tries to boot.
Seems quite scary.
--
You received this bug
on first boot /etc/zfs/zfs-list.cache/rboot /etc/zfs/zfs-
list.cache/bpool are either missing or empty.
this causes daemon-reload to go bananzas, as zfs generator runs for the
first time and generates many essential mount units. After that if cache
is populated, generators on boot & daemon-reload
subsequent boots are fine.
i wonder if we have a race somewhere, for example. On first boot zfs
cache is out of date. And zfs mount generator doesn't generate mounts
for all the mounted file systems.
then the first daemon-reload ever, will happen after zfs cache is
populated and the zfs volumes
1) doing first boot of encrypted zfs kinetic, edit boot cmdline to
include:
systemd.mask=snapd.service systemd.snapd.seeded.service
systemd.mask=snapd.socket
crutially this prevents snapd seeding to complete which calls systemctl
daemon-relaod.
system boots normally
2) login into tty and check
** Attachment added: "system.journal"
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1993318/+attachment/5624966/+files/system.journal
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status:
@paelzer sorry missed your question earlier, yes this is known. The
newer capability support for apparmor is being backported to focal.
Hopefully we will see the SRU for it this week.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I too have upgraded to Ubunutu 22.04 and have GlobalProtect 5.2.6-18 and
@frulz instructions above helped me correct the issue. Thank you!
Hopefully PAN will get this fixed in an updated version.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
*** This bug is a duplicate of bug 1991691 ***
https://bugs.launchpad.net/bugs/1991691
** This bug has been marked a duplicate of bug 1991691
cannot change mount namespace
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
*** This bug is a duplicate of bug 1991691 ***
https://bugs.launchpad.net/bugs/1991691
It is not a duplicate of
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1991691
** This bug is no longer a duplicate of bug 1991691
cannot change mount namespace
--
You received this bug
initramfs-tools also mounts /dev with nosuid, without noexec
> mount -t devtmpfs -o nosuid,mode=0755 udev /dev
I believe all of these should be the same, thus kernel can mount /dev
with nosuid, but should not mount it with noexec.
--
You received this bug notification because you are a member
./src/nspawn/nspawn-mount.c missing NO_EXEC on /dev
./src/shared/mount-setup.c missing NO_EXEC on /dev
when booting containers
** Changed in: systemd (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
./src/nspawn/nspawn-mount.c missing NO_EXEC on /dev
./src/shared/mount-setup.c missing NO_EXEC on /dev
when booting containers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
@juliank please test initrd-less boot; for example lxc launch --vm which
uses linux-kvm flavour booted without initrd.
There are differences of the mount options as applied by initramfs-
tools; systemd; and kernel itself.
--
You received this bug notification because you are a member of Ubuntu
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu)
Importance: Undecided => High
** Changed in: apparmor (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
initramfs-tools in Bionic+, when mounting the filesystem, mounts /run
with noexec
Cloud images run without initramfs and rely on systemd for the mounts.
systemd, however, mounts /run without noexec. Snip from mount-setup.c
(either in src/core/mount-setup.c < 248 or
Public bug reported:
Trying to upgrade to the latest image.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-48-generic 5.15.0-48.54
ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203
Uname: Linux 5.4.0-126-generic x86_64
AlsaDevices:
total 0
crw-rw 1
On my machine, I didn't need to modify my firewall to get around the
issue; just use a different mechanism to create a hotspot. The app
"Wifi Hotspot" (available on Ubuntu Software) worked just fine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
So in short yes we are talking blocking this however its not as bad as
that makes it sound. There is the immediate technical side, and the
reason we must do that, and then there is longer term practical use
side.
So the technical short answer is yes that will be blocked at least
without
we do not need or want libnss-resolve anymore, because we created stub-
resolv.conf which exports 1) local nameserver resolver 2) with correct
options 3) and search domains. We only needed libnss-resolve back when
we dind't have /run/systemd/resolve/stub-resolv.conf
--
You received this bug
It will affect both. The exact effect will depend on how things are set
up. Unconfined privileged processes will still have access to create
user namespaces as they see fit. The processes within the user namespace
will be subject to similar restrictions.
There is still room for refinement of the
Additionally, I also have better "luck" hitting the problem when I use
an instance with arm64 (aarch64) architecture.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
https://bugs.launchpad.net/bugs/1989599
I'm seeing this happen too and it's very frustrating. I've been able to
get auditd to start by commenting out the audit backlog limit in the
rules file and reboot. But when I restore the statement and reboot,
auditd still starts. I didn't expect it to start after I restored the
audit backlog
In short unprivileged user namespaces a vector for exploit chains, as
they expose interfaces that otherwise would not be available.
4 out 5 exploits chains in pwn2own 2022 used unprivileged user
namespaces. They were also used in 2021, 2020, ... Yes the actual
vulnerabilities were in other
As you say there are many new things in there. At this point its
probably better to just land the two things we care about
1. posix ipc mediation
2. user namespace mediation
on top of the existing 3.0.7. That would give us a clear set of
important features, with a we defined set of patches
Not a regression, or at least an intended regression (ie. it is doing
exactly what is intended). This is exactly what has been talked about
for 6+ months. unprivileged user_namespaces are going away, but instead
of the big system level sysctl we can allow them on a per application
basis.
The only
Public bug reported:
I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS.
When plugging in the charger, the current charge status in the top bar and
Settings shows 'Not Charging' for a few minutes and then shows that the system
is charging normally.
When unplugging the charger the
This is fixed upstream in 2.39... can we have updated packages for
ubuntu? Some other distros have it already.
--
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/1971901
I can add maintainer script to check and remove expired copies of
0xC8CAB6595FDFF622 and then like print a message that one needs to
install ubuntu-dbgsym-keyring
Unfortunately, I cannot automatically ask apt to install ubuntu-dbgsym-
keyring if expired dbgsym key is detected on disk =/
--
You
Used systemd packaging repo's ./debian/git-cherry-pick and gbp dch + gbp
tag to convert the cherry-pick request into a typical looking systemd
sru backport.
Submitted merge proposal to https://code.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/+git/systemd/+merge/429491
will ask for
** Description changed:
+ [Impact]
+
+ * Optimization features included in jammy cause atypical alignment of
+ LOAD ELF sections. This in turn causes failure to execute binaries on
+ WSL1. Upstream have since integrated the optimization features included
+ in jammy, but also reverted alignment
I found if the Max TOLUD is set to 1GB or higher in the BIOS (anything
other than dynamic) then Ubuntu 22.04 ISO will not get this out of
memory error
--
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 also affecting the MSI MEG Z690I Unify motherboard; can not boot
any live disk images of Ubuntu 22.04
--
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/1842320
201 - 300 of 4696 matches
Mail list logo
