Oh, I didn't close this sorry. I agreed with Julian a few months ago
about the regression potential, and we decided to leave it there. This
should be okay in Noble+ due to switching to deb822 sources, which has
much better support for options.
** Changed in: python-apt (Ubuntu)
Status: New
No worries Krister, I'm sorry that it dragged out as long as it did, but
we got there in the end.
Thanks for tracking down the bug in the first place and getting the
patch merged upstream!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
Tested version 24.04.5 from https://launchpad.net/ubuntu/+source/ubuntu-
settings/24.04.5
Following the first few steps in the testplan
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeInitialSetup I:
- Created a 24.04.1 VM and preformed normal installation
- Installed ubuntu-settings 24.04.5
-
** Description changed:
[ Impact ]
While using Gnome-Initial-Setup launched from GDM (when no user > 1000
is present on the machine), no background is set on GNOME-Greeter,
leading to a solid blue background wallpaper.
Gnome-Initial-Setup is currently used on OEM shipped devices to
** Description changed:
+ [ Impact ]
+
While using Gnome-Initial-Setup launched from GDM (when no user > 1000
is present on the machine), no background is set on GNOME-Greeter,
leading to a solid blue background wallpaper.
- Could we set the background here to the Ubuntu default? By upda
architectures. I probably need to
retry them a few times. I don't have permissions to trigger the tests
though, so I will ask around.
I'll try get the update released soon. I do understand this has been in
the works for a very long time, sorry about that.
Thanks,
Matthew
--
You receive
** Changed in: ubuntu-settings (Ubuntu)
Milestone: None => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2077741
Title:
No default background se
Public bug reported:
While using Gnome-Initial-Setup launched from GDM (when no user > 1000
is present on the machine), no background is set on GNOME-Greeter,
leading to a solid blue background wallpaper.
Could we set the background here to the Ubuntu default? By updating
/usr/share/glib-2.0/sche
Performing verification for Jammy.
So, I had forgotten all about these instances, so let's check them now.
The instance with -updates:
It failed with:
+ resize2fs /dev/nvme1n1p1
resize2fs 1.46.5 (30-Dec-2021)
resize2fs: Superblock checksum does not match superblock while trying to open
/dev/nvm
Performing verification for Noble.
So, I had forgotten all about these instances, so let's check them now.
The instance with -updates:
It failed with:
+ resize2fs /dev/nvme1n1p1
resize2fs 1.47.0 (5-Feb-2023)
resize2fs: Superblock checksum does not match superblock while trying to open
/dev/nvme
Performing verification for Focal.
So, I had forgotten all about these instances, so let's check them now.
The instance with -updates:
It failed with:
+ resize2fs /dev/nvme1n1p1
resize2fs 1.45.5 (07-Jan-2020)
resize2fs: Superblock checksum does not match superblock while trying to open
/dev/nvm
Beginning verification for noble
I started two c5.large instances on us-west-2 on AWS, the same parameters that
we used in previous tests. Each has a 60gb GP3 volume attached to it.
Each instance is running the GA kernel, 6.8.0-1012-aws.
One is -updates, the other is e2fsprogs from -proposed:
-
Beginning verification for jammy
I started two c5.large instances on us-west-2 on AWS, the same parameters that
we used in previous tests. Each has a 60gb GP3 volume attached to it.
I downgraded the HWE kernels down to GA kernels, and each is running
5.15.0-1066-aws.
One is -updates, the other
Beginning verification for focal
I started two c5.large instances on us-west-2 on AWS, the same parameters that
we used in previous tests. Each has a 60gb GP3 volume attached to it.
I downgraded the HWE kernels down to GA kernels, and each is running
5.4.0-1129-aws.
One is -updates, the other i
Attached is a V2 patch for Noble for e2fsprogs.
** Patch added: "Debdiff for e2fsprogs on noble V2"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5772258/+files/lp2036467_noble_V2.debdiff
** Patch removed: "Debdiff for e2fsprogs on noble"
https://bugs.launch
submit the patches for SRU to noble, mantic,
jammy and focal. Should be a few days.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/2036467
Title
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Importance: Low => Medium
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Tags added: sts
--
You received this bug not
Thank you for the help sorting autopkgtests Mauricio.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2033892
Title:
ls -l triggers mount of autofs shares when --ghost op
Performing verification for Jammy
I set up two Jammy VMs, one a nfs-server and the other an autofs/nfs-
client.
The client is using coreutils 8.32-4.1ubuntu1.1 from -updates.
$ apt-cache policy coreutils | grep Installed
Installed: 8.32-4.1ubuntu1.1
I set up the nfs server and autofs mounts
Attached is a debdiff for mantic which fixes this issue.
** Patch added: "Debdiff for gtkpod on mantic"
https://bugs.launchpad.net/ubuntu/+source/gtkpod/+bug/2044420/+attachment/5757356/+files/lp2044420_mantic.debdiff
** Changed in: glib2.0 (Ubuntu Noble)
Status: Triaged => Fix Release
gtkpod has been removed from debian, and thus removed from noble, so no
need to fix there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2044420
Title:
gtkpod segfaults w
I came across this after being offered an upgrade prematurely (which
appears to be another bug). Please note #9 in
https://answers.launchpad.net/ubuntu/+question/709594 if you are
fettling the postinst for polkitd.
--
You received this bug notification because you are a member of Ubuntu
Touch see
I have been running the test packages on AWS with the reproducer running
for 20 days now, and they are still running great. The change to direct
IO really does fix this issue, and my testing has removed any and all
concerns of causing a regression.
Previously focal wouldn't last more than 20 minut
** Description changed:
- Release: 22.04.3 LTS
- coreutils 8.32-4.1ubuntu1
+ [Impact]
- ls triggers unwanted mounts of autofs filesystems
+ Issuing a 'ls -l' or a 'stat' on an autofs share when you have set
+ --ghost in the auto.master file, or browse_mode=yes in autofs.conf will
+ lead to the
Attached is a debdiff that solves this issue on Jammy.
** Patch added: "Debdiff for coreutils on Jammy"
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2033892/+attachment/5745181/+files/lp2033892_jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
signee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2033892
Title:
ls -l triggers mount of autofs shares when --ghost option i
Hi Krister,
Fascinating. I'm in New Zealand, so I use ap-southeast-2 in Sydney,
Australia for all my instances, and I never gave it any thought that
this could depend on how busy EBS is on the availability zone.
I'll move my instances to us-west-2.
Thanks,
Matthew
--
You receive
anted to see it fail on Jammy, Mantic
and Noble before we go patching them.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/2036467
Title:
Resizi
Public bug reported:
As of writing, the current provided version of e2fsck (provided by
e2fsprogs) is 1.46.5 (2021-12-30). The latest version of e2fsck is
1.47.0 (2023-02-05), which I believe contains a few updates to supported
features.
My older version of fsck failed to run successfully during
g.
If you want to help test, there are test packages for all releases in:
https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test
Regardless, I'll try move this forwards.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Attached is a patch for noble that solves this issue.
** Patch added: "Debdiff for e2fsprogs on noble"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5738302/+files/lp2036467_noble.debdiff
--
You received this bug notification because you are a member of Ubuntu
Attached is a V2 patch for mantic with a different version number, due
to it no longer being the devel release.
** Patch removed: "Debdiff for e2fsprogs on mantic"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707893/+files/lp2036467_mantic.debdiff
** Patch add
Upstream bug: https://gitlab.gnome.org/GNOME/glib/-/issues/3185
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3185
https://gitlab.gnome.org/GNOME/glib/-/issues/3185
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2044420
Title:
gtkpod segfaults when attemptin
There is a workaround described at
https://groups.google.com/g/linux.debian.bugs.dist/c/g1OZeZ_wWAU/m/eE0XZBWoBgAJ
copy_exec /sbin/mount.fuse3 /sbin || true
However the upstream maintainer should probably address this.
Affects the AWS Focal AMI, so a lot of people may be impacted but just
not k
Possibly related to DEBIAN Bug#1022252.
--
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/2035385
Title:
update-initramfs fails: /usr/share/initramfs-tools/hooks/fuse
** Description changed:
[Impact]
This is a long running bug plaguing cloud-images, where on a rare
occasion resize2fs would fail and the image would not resize to fit the
entire disk.
Online resizes would fail due to a superblock checksum mismatch, where
the superblock in memory
@juliank I'm just doing a little bit more testing for the moment, as I
really want to make sure this isn't going to cause any issues in the
cloud images. It would be nice to have this bug fixed though, I have
seen a few cases related to it over the years.
I'll ask my SEG colleagues for help with s
** Summary changed:
- superblock checksum mismatch in resize2fs
+ Resizing cloud-images occasionally fails due to superblock checksum mismatch
in resize2fs
** Description changed:
- Hi,
- We run ext4 on EBS volumes on EC2. During provisioning, cloud-init will
occasionally report that resize2f
Attached is a debdiff for e2fsprogs on trusty which fixes this issue.
** Patch added: "Debdiff for e2fsprogs on trusty"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707900/+files/lp2036467_trusty.debdiff
--
You received this bug notification because you are a
Attached is a debdiff for e2fsprogs on xenial which fixes this issue.
** Patch added: "Debdiff for e2fsprogs on xenial"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707899/+files/lp2036467_xenial.debdiff
--
You received this bug notification because you are a
Attached is a debdiff for e2fsprogs on bionic which fixes this issue.
** Patch added: "Debdiff for e2fsprogs on bionic"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707898/+files/lp2036467_bionic.debdiff
--
You received this bug notification because you are a
Attached is a debdiff for e2fsprogs on focal which fixes this issue.
** Patch added: "Debdiff for e2fsprogs on focal"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707896/+files/lp2036467_focal.debdiff
--
You received this bug notification because you are a me
Attached is a debdiff for e2fsprogs on jammy which fixes this issue.
** Patch added: "Debdiff for e2fsprogs on jammy"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707895/+files/lp2036467_jammy.debdiff
--
You received this bug notification because you are a me
Attached is a debdiff for e2fsprogs on lunar which fixes this issue.
** Patch added: "Debdiff for e2fsprogs on lunar"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707894/+files/lp2036467_lunar.debdiff
--
You received this bug notification because you are a me
Attached is a debdiff for e2fsprogs on mantic which fixes this issue.
** Patch added: "Debdiff for e2fsprogs on mantic"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707893/+files/lp2036467_mantic.debdiff
--
You received this bug notification because you are a
n: e2fsprogs (Ubuntu Mantic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: e2fsprogs (Ubuntu Lunar)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: e2fsprogs (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
**
sudo chmod -Rc 755 /opt/epson-inkjet-printer-escpr2 worked for me.
There is a temptation when writing under /opt to go 777 when untaring to make
the drag and drop.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubunt
Public bug reported:
Upgrading from 22.10 to 23.04
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: nvidia-kernel-common-525 525.105.17-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zco
you waiting for so long, and I
thank you for your patience and understanding while I debugged
autopkgtest.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bug
This is indeed a defect--marking it "wontfix" is not helpful.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1930914
Title:
ubuntu-minimal depends on ubuntu-advantage-
aseUpdates#Autopkgtest_Regressions
In which case, I may as well invoke this clause, since I don't wish to
keep you waiting any longer.
I will try and get this package released within the week.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
It seems like this has stalled again and I don't understand why. Patches
were posted about 1 month ago and they got some testing feedback within
2 days of availability.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer
henever sockets are constructed, and
+ isc-dhcp-server could also be affected.
+
+ We have mitigated the risks of regression as best as possible by adding
+ as much detail as possible to this launchpad bug, so it is clear how the
+ race operates and how the patch fixes the issue.
+
+ Mauricio has addit
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1926139
Title:
dhclient: thread concurrency race leads to DHCPOFFER packets not being
received
Screenshot of wireshark.
** Attachment added: "Screenshot of wireshark"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5641811/+files/Screenshot_2023-01-17-16-14-21_1920x1200%250A1920x1080%250A1920x1080.png
** Description changed:
[Impact]
Occasionally, du
packet capture from a reproduction run
** Description changed:
- Platform: Qemu/libvirt on AMD64
- Ubuntu version: 20.04
- isc-dhcp-client version: 4.4.1-2.1ubuntu5
- Problem: When dhclient is used during boot every few reboots the DHCP OFFER
packets aren't pushed from the kernel to dhclient. Th
** Summary changed:
- dhclient doesn't receive dhcp offer from kernel
+ dhclient: thread concurrency race leads to DHCPOFFER packets not being
received
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
http
untu Jammy)
Importance: Undecided => High
** Changed in: bind9-libs (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: bind9-libs (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification becaus
Attached is a debdiff for Focal which fixes this bug.
** Patch added: "Debdiff for bind9-libs for Focal"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5641515/+files/lp1926139_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Performing verification for Bionic.
I started two instances on AWS, one c6g.medium (arm64) and a t2.micro
(amd64).
I went through the reproducer listed in the testcase with libunwind-dev
1.2.1-8 from -release.
$ wget
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5
Performing verification for Focal.
I started two instances on AWS, one c6g.medium (arm64) and a t2.micro
(amd64).
I went through the reproducer listed in the testcase with libunwind-dev
1.2.1-9build1 from -release.
$ wget
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachm
@binli - here are my testing results with patches:
- gstreamer1.0_1.20.3-0ubuntu2.debdiff
- gst-plugins-base1.0_1.20.1-2.debdiff
- pipewire_0.3.48-1ubuntu4.debdiff
Gnome Shell screen recorder: pass
gst-launch-1.0 video preview: pass
Gnome Shell screen recorder while gst-launch-1.0 video preview is
@binli - I'm still on pipewire from jammy-updates:
$ apt-cache policy pipewire
pipewire:
Installed: 0.3.48-1ubuntu2
Candidate: 0.3.48-1ubuntu2
Version table:
*** 0.3.48-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
100 /var/lib/dpkg/
@binli - I never found a need to update pipewire; the gstreamer patches
(for gstreamer and gst-plugins-base) seem to be sufficient in my
testing.
I tested your gstreamer & gst-plugins-base packages and they work the same as
the ones I built. I think you could drop "-0ubuntu1binli1" from the symbo
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1999104
Title:
arm64: broken c++ exception handler support leads to std::terminate()
being ca
** Summary changed:
- libunwind causes crashes on arm64
+ arm64: broken c++ exception handler support leads to std::terminate() being
called and program abort
** Description changed:
- There is a bug in libunwind in both 18.04 and 20.04 on arm64 where when
- linked with libunwind instead of cat
e: Undecided => Medium
** Changed in: libunwind (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: libunwind (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Patch added: "Debdiff for libunwind on Bionic"
ht
Attached is a debdiff which fixes this problem on Focal.
** Patch added: "Debdiff for libunwind on Focal"
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635451/+files/lp1999104_focal.debdiff
--
You received this bug notification because you are a member of Ubun
Attached is an improvement on the previous patch revision. Output is now
forwarded to logger, we use shell expansion to enumerate network
devices, we omit loopback, and we added a udevadm settle to wait for any
thunderstorms to resolve before we continue installing the new udev
package.
** Patch a
Attached is the second patch required to fully fix this bug. It adds a
check on preinstall to see if ID_NET_DRIVER is present on the network
interface, and if it is missing, call udevadm trigger -c add on the
interface to add it.
** Patch added: "Debdiff for systemd on Bionic part two"
https:/
The failure mode still exists if "udevadm trigger" has been issued
before the package upgrade to systemd 237-3ubuntu10.55.
That is, if unattended-upgrades or the user had installed open-vm-tools,
and has not rebooted yet, they will lose network connection on upgrade
to 237-3ubuntu10.55.
We need t
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Released => Fix Committed
--
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/1988119
Title:
systemd-udevd: Run net_se
e on how it went. Again, please don't put the
package into production until it has had a little more testing, and we
will get this released to the world as quickly and safely as we can.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Touch seed
Attached is a debdiff for systemd on Bionic which fixes this bug.
** Description changed:
- Two servers today that updated systemd to "systemd 237-3ubuntu10.54"
- https://ubuntu.com/security/notices/USN-5583-1
+ [Impact]
- could not resolve dns anymore.
- no dns servers, normally set through
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Tags added: bionic sts
--
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/b
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided =
I think there are multiple bugs in play here. My system-connections dir
is a symlink within the same filesystem, and whenever I try to save a
new connection I get the "settings plugin does not support adding
connections" message.
Aug 18 17:11:08 workhorse4 NetworkManager[4092654]:
[1660857068.13
Public bug reported:
Firefox does not scroll with the usual touch gesture of swiping up or
down on the screen. This action just selects text on the page as though
the left mouse button was depressed and the cursor moved across the
page.
lsb_release -rd
Description:Ubuntu 22.04 LTS
Release:
I've just installed 2:2.10-9ubuntu1 amd64 and I can confirm that it
works on Kubuntu 22.04 LTS for my university's WPA2 Enterprise network.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.
As I've noted in my duplicate bug report, this effects snaps (Firefox,
Brave) but not apts (Evince, Thunderbird).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1971112
Titl
This issue is no longer present in Ubuntu 22.04. Wile using Ubuntu 21.10, the
following workarounds also remedied the issue:
- Run a mainline 5.15.x kernel from
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
- Run the Jammy Jellyfish kernel from
https://packages.ubuntu.com/jammy/linux-i
It's a bit of an 'own goal' if this gets marked as 'won't fix'. As students
upgrade to 22.04 where I work they will find they can't connect to the
institutions or research centre wireless network. They won't care that the SSL
change is protecting them from an old SSL bug, they will just come bac
I installed software-properties 0.99.20 from -proposed, and opened
software-properties-gtk, and clicked the "Additional Drivers" tab. The
tab loaded correctly and did not crash.
The package in -proposed fixes the issue, happy to mark verified.
--
You received this bug notification because you ar
*** This bug is a duplicate of bug 1958410 ***
https://bugs.launchpad.net/bugs/1958410
** This bug has been marked a duplicate of bug 1958410
bytcr_rt5640 sound not working with kernel >= 5.13
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
*** This bug is a duplicate of bug 1958410 ***
https://bugs.launchpad.net/bugs/1958410
** This bug has been marked a duplicate of bug 1958410
bytcr_rt5640 sound not working with kernel >= 5.13
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
Opened up "Software & Updates" and clicked the "Additional Drivers Tab",
for the tab to crash.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: software-properties-gtk 0.99.19
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_
Performing verification for openssl on Focal.
An affected user performed the verification, due to c7g instance types
being in "Preview" state on Amazon AWS, and not generally accessible.
The user started a c7g instance, and checked they had openssl
1.1.1f-1ubuntu2.10 from -updates.
They attempte
Attached is a debdiff for Jammy util-linux.
** Patch added: "debdiff for util-linux on Jammy"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1961542/+attachment/5562373/+files/lp1961542_jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch se
870.html
ubuntu-devel had strong support for option (3).
Hence, we will revert the below commit to ensure Jammy can be deployed on all
existing MAAS releases.
58b510e580 libsmartcols: sanitize variable names on export output
** Affects: util-linux (Ubuntu)
Importance: High
Assigne
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1960863
Title:
armv8 paca: poly1305 users see segfaults when pointer authentication
in use on A
Attached is a debdiff for openssl on Focal
** Patch added: "debdiff for openssl on Focal"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960863/+attachment/5560898/+files/lp1960863_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
.
** Affects: openssl (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: openssl (Ubuntu Focal)
Importance: High
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: focal sts
** Also affects: openssl (Ubuntu Focal)
Importance
This has been fixed as of ubuntu-meta 1.474
https://launchpad.net/ubuntu/+source/ubuntu-meta/1.474
$ sudo apt rdepends unattended-upgrades
unattended-upgrades
Reverse Depends:
Recommends: python3-software-properties
Recommends: ubuntu-mate-desktop
Recommends: ubuntu-mate-core
Depends: free
I compiled several Ubuntu-5.13.0-x.x tags from
https://kernel.ubuntu.com/git/ubuntu/ubuntu-impish.git/refs/ but the backlight
issue seems to go far back in time. I tested:
- Ubuntu-5.13.0-25.26
- Ubuntu-5.13.0-21.21
- Ubuntu-5.13.0-20.20
- Ubuntu-5.13.0-19.19
- Ubuntu-5.13.0-16.16
In Ubuntu-5.13
I just tested signed Ubuntu kernel 5.13.0-28-generic which is in
Proposed right now, but it does not fix the issue. Brightness
adjustments work, but service fails during startup and screen is at full
brightness every boot (at gdm and at GNOME 3 desktop).
--
You received this bug notification beca
I tested some mainline 5.13.x kernels from
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D and was able to
find a point release where this issue is resolved. Testing results:
Signed Ubuntu kernel 5.13.0-27-generic: brightness adjustments work, but
service fails during startup and screen is
Public bug reported:
Hi,
I'm running Ubuntu MATE 18.04.6 LTS. The bug information was sadly
collected from the working configuration of the system after dropping to
an earlier kernel.
This bug is a display bug where 1-pixel horizontal lines of multicolored
corruption or occasionally incorrect sc
I enabled debug logging for systemd with kernel cmdline:
systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M printk.devkmsg=on
New log attached to bug report is the output of 'journalctl -b':
systemd-debug.log
Filtering on "backlight" and omitting systemd-logind, this portion looks
int
** Description changed:
On Impish and later, removing unattended-upgrades also removes ubuntu-
server-minimal due to ubuntu-server-minimal depending on unattended-
upgrades
$ sudo apt remove unattended-upgrades
...
The following packages will be REMOVED:
- ubuntu-server-minimal un
1 - 100 of 1489 matches
Mail list logo
