Done! https://github.com/canonical/Ubuntu-Sans-fonts/issues/117
** Bug watch added: github.com/canonical/Ubuntu-Sans-fonts/issues #117
https://github.com/canonical/Ubuntu-Sans-fonts/issues/117
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Many thanks for your confirmation Kowshik Jois.
With that I'm updating the tags accordingly (and set them to verification done).
** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
On a ThinkPad P16s running Noble, resuming from suspend fails about 10%
of the time. This usually leads to a reboot, and more rarely to a hang
that requires forcing a power off.
I don't recall this being the case with kernel 6.5 in Mantic.
How to reproduce:
* suspend the lap
*** This bug is a duplicate of bug 2055044 ***
https://bugs.launchpad.net/bugs/2055044
** This bug has been marked a duplicate of bug 2055044
GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Any workaround for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051574
Title:
gnome-shell-portal-helper crashed with SIGTRAP in
waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch()
Some work ongoing on resolving camera flakiness towards the end of this
thread: https://github.com/intel/ipu6-drivers/issues/187
** Bug watch added: github.com/intel/ipu6-drivers/issues #187
https://github.com/intel/ipu6-drivers/issues/187
--
You received this bug notification because you are
Hi Clémentine!
Thanks for your report and and for your help making Ubuntu better.
You seem to have a previous installation of MySQL installed and MariaDB
and MySQL should not been installed together since they may use the same
PATH (from DpkgTerminalLog.txt). So, before installing MariaDB, please
For at least fedora 39 this is resolved. Don't know witch package fixed this.
Removed env variables and all are OK.
gnome-shell 45.6-1.fc39
mutter 45.6-1.fc39
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Installed 20220329.git681281e4-0ubuntu3.31,
With patched kernel, audio works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064064
Title:
Add support of TAS2781 amp of audio
To manage notific
Sure, I can change it.
I'll do the change and reboot ... We'll have an answer in about 30
Minutes.
Another thing that I was thinking about is ... The `/etc/hostname` of
the System is `ubuntuworkstation01` and the DHCP-assigned (or should I
say "registered" ?) hostname is apparently `WORKSTATION01
Public bug reported:
(On a server with NVidia HGX platform with 8 A100 on Ubuntu 22.04.4 LTS)
The new version of the cuda-drivers-fabricmanager-535 is 535.161.08, and
the version of the nvidia-driver-535 is 535.171.04.
```
# apt-cache policy cuda-drivers-fabricmanager-535
Candidat : 535.161.0
This bug was fixed in the package ruby-fast-gettext - 2.0.3-2
Sponsored for Zixing Liu (liushuyu-011)
---
ruby-fast-gettext (2.0.3-2) unstable; urgency=medium
[ Debian Janitor ]
* Remove constraints unnecessary since buster:
+ Build-Depends: Drop versioned constraint on ruby-r
This sounds like a race condition that leads to live lock, considering
that both gpgv and apt are waiting for the other end to speak at the
same time.
I assume the protocol between these is custom made for this connection.
How the protocol is supposed to prevent this live lock situation from
happe
The oldest minimum version in currently supported Ubuntu versions is
1:2.6.16-1 in focal, which should have this bug fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886667
Title:
imapfilter fa
Public bug reported:
Please sync python-requests-unixsocket 0.3.0-4 (universe) from Debian
unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
[ Olivier Gayot ]
* Execute test-suite as part of autopkgtest (LP: #2053267)
-> The patch was included in Debian version 0
It seems, looking at `dmesg` at least, that the "frozen" / "hang" state
went from 300 Seconds to 45 Seconds.
PS: is it normal that I cannot attach multiple files at once ?
** Attachment added: "initramfs_v4.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachm
Yes, I can confirm. Without a precise clock but just counting in my
head, it's around 45 seconds. Definitively much less than before.
Maybe I'll try to quickly play with PXE Boot / TFTP Server settings on
my OPNSense Router and see if that's responsible for the slowdown
(dhcpcd reported those PXEL
** Attachment added: "dmesg_v4.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5775772/+files/dmesg_v4.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
** Changed in: imapfilter (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886667
Title:
imapfilter fails to set SNI
To manage notifications about this bug
I'm seeing the same problem on Ubuntu 22.04.4 LTS:
$ ps -eHo pid,ppid,etimes,command | grep -w [a]pt
3162391 1 3033258 /bin/sh /usr/lib/apt/apt.systemd.daily update
3162395 3162391 3033258 /bin/sh /usr/lib/apt/apt.systemd.daily lock_is_held
update
3162423 3162395 3033257 apt-get
The next version after 1:2.6.16-1 in focal is 1:2.7.5-1build1 in jammy
which should contain the fix according to its version.
** Changed in: imapfilter (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Public bug reported:
Ubuntu 18.0.6 LTS
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.45
ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18
Uname: Linux 4.15.0-213-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
CrashDB: ub
The minimum version supported in Ubuntu currently is 1:2.6.16-1 in
focal. Please check that the bug still happens on that version.
** Changed in: imapfilter (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Also affects: pygithub (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: pygithub (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Public bug reported:
May 07 11:15:35 ZB gnome-shell[330637]: Failed to create new
MetaSelectionSourceMemory: Failed to create MetaAnonymousFile
May 07 11:15:35 ZB gnome-shell[330637]: Failed to create new
MetaSelectionSourceMemory: Failed to create MetaAnonymousFile
May 07 11:15:35 ZB gnome-shel
Public bug reported:
I think this error appears when running `ubuntu-bug`.
May 07 11:57:34 ZB gnome-shell[330637]: Object .Gjs_ui_messageTray_Notification
(0x64ef65e93080), has been already disposed — impossible to emit any signal on
it. This might be caused by the object having been destroyed
** Description changed:
May 07 11:15:35 ZB gnome-shell[330637]: Failed to create new
MetaSelectionSourceMemory: Failed to create MetaAnonymousFile
May 07 11:15:35 ZB gnome-shell[330637]: Failed to create new
MetaSelectionSourceMemory: Failed to create MetaAnonymousFile
May 07 11:15:35 ZB g
Public bug reported:
In Xubuntu 24.04 when installing a deb package (Google Chrome) using
Gdebi, after checking dependencies when I click the install button Gdebi
just closes. I checked processes and it is not running.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gdebi 0.9.5.7+nmu7
ProcV
The Launchpad UI only allows to attach one file at once. So that is
normal.
I'll prepare the upload containing the fix. That your boot takes around
45 seconds instead of 15 seconds is caused by a separate issue. Please
file another bug for that. Here is the relevant log:
```
dhcpcd-10.0.6 startin
Hi
Yes, I'm using kernel 5 version because kernel 6 was braking for me, I can
retry it.
I'm using lowlatency because this machine does some streaming and storing
streams, and I noticed tiny better performance, but that's maybe my imagination.
I don't do any CPU pinning or realtime processes.
Th
Update, Id I Open Gdebi first then select File Open Deb-Package and then
click Install It prompts me fora password and installs the deb package.
Right clicking on the Deb Package, selecting Gdebi and install closes
the application.
--
You received this bug notification because you are a member o
Public bug reported:
default ssh config by provider Strato (Germany)
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: openssh-server 1:9.3p1-1ubuntu3.3
ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98
Uname: Linux 5.15.0-72-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architect
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065027
Title:
package openssh-server 1:9.3p1-1ubuntu3.3 failed to install/upgrade:
installed openssh-server pac
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdebi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065025
Title:
Gdeb
Public bug reported:
I have used Ask Ubuntu with a description of the problem
https://askubuntu.com/questions/1513034/problems-installing-24-04/1513141#1513141
I have a manual partition in order to keep separate the "/" from "/home"
and to overwrite the Ubuntu while not touching the user data. Th
Alright.
Can you please tell me what I should report in the other bug exactly
though ?
My original idea in the first post ?
>>A possible workaround would be to manually edit
>>/usr/share/initramfs-tools/scripts/functions
>>Changing this:
>>`for ROUNDTTT in 30 60 90 120; do`
>>To this:
>>`for R
Hello Rick.
Thanks for your very useful comment.
Op za 4 mei 2024 om 12:50 schreef Rik Mills
<2063...@bugs.launchpad.net>:
> I can see from the logs that you must have packages from the backports-
> extra PPA on your system, to get newest plasma 5.27. The packages in
> that are backported from 2
Hey @phausman,
could you please try to reproduce by using the openscap -proposed?
For more information:
https://bugs.launchpad.net/ubuntu/+source/openscap/+bug/2062389/comments/10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Forwarded fix upstream: https://github.com/NetworkConfiguration/dhcpcd/pull/320
and to Debian: https://salsa.debian.org/debian/dhcpcd/-/merge_requests/6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20
*** This bug is a duplicate of bug 2063841 ***
https://bugs.launchpad.net/bugs/2063841
** This bug has been marked a duplicate of bug 2063841
[SRU] virtualbox crash on network traffic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: virtualbox-hwe (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063841
Titl
Suggested title for the second bug: dhcpcd is called before interfaces
have carrier causing a 29 seconds boot delay
The bug title and description can be updated afterwards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Public bug reported:
In automatically encrypted Clevis+Tang unlock of LUKS encrypted device
(dmcrypt/cryptsetup) - on top of which the ZFS Pool for / resides,
dhcpcd is used in order to obtain automatically an IP address during
initramfs boot.
During this phase, dhcpcd is called before interfaces
** Attachment added: "dmesg_v4.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5775839/+files/dmesg_v4.debug
** Package changed: initramfs-tools (Ubuntu) => dhcpcd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs
> GNOME Remote Desktop won't work for systems that were upgraded from
earlier Ubuntu releases.
I did not upgrade from an earlier release and still experienced that
issue.
What I did was install ubuntu-24.04-live-server-arm64, then called "sudo
apt install ubuntu-desktop".
--
You received this
Super, many thanks. But I'll basically have to "patch" it locally,
because I guess this will not make it to Ubuntu before 24.10 at best,
right ?
New BUG Report at (hope I did it correctly):
https://bugs.launchpad.net/ubuntu/+source/dhcpcd/+bug/2065037
EDIT 1: I accidentally assigned it to initram
Public bug reported:
Package prometheus-blackbox-exporter/jammy-security,jammy-updates,now
0.19.0-1ubuntu0.2 amd64 contains bug which is described here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010054
Issue is short is that blackbox exporter is extensively filling the
syslog.
It was
** Package changed: dhcpcd (Ubuntu) => initramfs-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065037
Title:
dhcpcd is called before interfaces have carrier causing a 29 seconds
bo
** Changed in: dhcpcd (Ubuntu)
Status: New => Incomplete
** Changed in: dhcpcd5 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/201
Title:
Wifi 5/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sane-frontends (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893517
Titl
We can include the fix in Ubuntu 24.04 via a stable release update.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
** Also affects: dhcpcd (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Noble)
Importance: Undecided
Debdiff for noble
** Description changed:
+ [ Impact ]
+
+ Systems that use clevis will have a 5 minutes boot delay, because dhcpcd
+ fails and retries until the retry loop exits.
+
+ [ Test Plan ]
+
+ Use a system with clevis and zfs where /etc/hostname is set and differs
+ from the hostname
Yes, same here. I did a fresh installation of ubuntu-24.04-live-server-
amd64 (not arm64) on two separate machines, and both experienced this
bug on every reboot after "sudo apt install ubuntu-desktop".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Pretty sure the same/similar occurs in Mantic and probably even before
(even if I believe dhcpcd version is different).
But maybe it's too much effort for little benefit to fix those (Mantic
will be anyways EOL July 2024 so just a few months away). I had upgraded
all Systems that I own to Ubuntu 2
Public bug reported:
Bug #1520154 introduced UBUNTU_CODENAME, but the final name that landed
in the os-release specification is VERSION_CODENAME. Ubuntu specifies
VERSION_CODENAME since Ubuntu 16.04 "xenial" (see bug #1598212).
So let's finally drop UBUNTU_CODENAME from os-release starting with
U
mantic and before are not worth the backport, but noble is a LTS
release.
Once the SRU team accepts the upload, it will land in noble-proposed and
you will get asked to test the fix. See
https://wiki.ubuntu.com/StableReleaseUpdates
--
You received this bug notification because you are a member o
Can you add following function to /usr/share/initramfs-
tools/scripts/functions:
```
log_flags() {
for device in /sys/class/net/*; do
echo "*** flags for $device";
if [ -f "${device}/flags" ]; then
cat "${device}/flags";
fi;
done
}
```
Please call this
This bug was fixed in the package linux - 5.4.0-181.201
---
linux (5.4.0-181.201) focal; urgency=medium
* focal/linux: 5.4.0-181.201 -proposed tracker (LP: #2059549)
* Packaging resync (LP: #1786013)
- [Packaging] drop getabis data
* Drop fips-checks script from trees (LP:
This bug is awaiting verification that the linux-aws/5.4.0-1124.134
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-aws' to 'verification-done-focal-
linux-aws'. If the pro
This bug is awaiting verification that the linux-raspi/5.4.0-1108.120
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-raspi' to 'verification-done-focal-
linux-raspi'. If t
This bug is awaiting verification that the linux-fips/5.4.0-1098.108
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-fips' to 'verification-done-focal-
linux-fips'. If the
This bug is awaiting verification that the linux-gcp/5.4.0-1128.137
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-gcp' to 'verification-done-focal-
linux-gcp'. If the pro
This bug is awaiting verification that the linux-gkeop/5.4.0-1091.95
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-gkeop' to 'verification-done-focal-
linux-gkeop'. If th
This bug is awaiting verification that the linux-ibm/5.4.0-1071.76
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-ibm' to 'verification-done-focal-
linux-ibm'. If the prob
This bug is awaiting verification that the linux-iot/5.4.0-1036.37
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-iot' to 'verification-done-focal-
linux-iot'. If the prob
This bug is awaiting verification that the linux-kvm/5.4.0-1112.119
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-kvm' to 'verification-done-focal-
linux-kvm'. If the pro
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.4.0-1043.47 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-focal-linux-xilinx-zynqmp'
to 'verification-done-focal-lin
This bug is awaiting verification that the linux-oracle/5.4.0-1123.132
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-oracle' to 'verification-done-
focal-linux-oracle'. I
This bug was fixed in the package linux - 5.15.0-106.116
---
linux (5.15.0-106.116) jammy; urgency=medium
* jammy/linux: 5.15.0-106.116 -proposed tracker (LP: #2061812)
* CVE-2024-2201
- x86/bugs: Use sysfs_emit()
- KVM: x86: Update KVM-only leaf handling to allow for 100
This bug was fixed in the package linux - 5.15.0-106.116
---
linux (5.15.0-106.116) jammy; urgency=medium
* jammy/linux: 5.15.0-106.116 -proposed tracker (LP: #2061812)
* CVE-2024-2201
- x86/bugs: Use sysfs_emit()
- KVM: x86: Update KVM-only leaf handling to allow for 100
This bug was fixed in the package linux - 5.15.0-106.116
---
linux (5.15.0-106.116) jammy; urgency=medium
* jammy/linux: 5.15.0-106.116 -proposed tracker (LP: #2061812)
* CVE-2024-2201
- x86/bugs: Use sysfs_emit()
- KVM: x86: Update KVM-only leaf handling to allow for 100
This bug was fixed in the package linux - 5.15.0-106.116
---
linux (5.15.0-106.116) jammy; urgency=medium
* jammy/linux: 5.15.0-106.116 -proposed tracker (LP: #2061812)
* CVE-2024-2201
- x86/bugs: Use sysfs_emit()
- KVM: x86: Update KVM-only leaf handling to allow for 100
This bug was fixed in the package linux - 5.15.0-106.116
---
linux (5.15.0-106.116) jammy; urgency=medium
* jammy/linux: 5.15.0-106.116 -proposed tracker (LP: #2061812)
* CVE-2024-2201
- x86/bugs: Use sysfs_emit()
- KVM: x86: Update KVM-only leaf handling to allow for 100
This bug is awaiting verification that the linux-aws/5.4.0-1124.134
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-aws' to 'verification-done-focal-
linux-aws'. If the pro
This bug is awaiting verification that the linux-raspi/5.4.0-1108.120
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-raspi' to 'verification-done-focal-
linux-raspi'. If t
This bug is awaiting verification that the linux-fips/5.4.0-1098.108
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-fips' to 'verification-done-focal-
linux-fips'. If the
This bug is awaiting verification that the linux-gkeop/5.4.0-1091.95
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-gkeop' to 'verification-done-focal-
linux-gkeop'. If th
This bug is awaiting verification that the linux-ibm/5.4.0-1071.76
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-ibm' to 'verification-done-focal-
linux-ibm'. If the prob
This bug is awaiting verification that the linux-iot/5.4.0-1036.37
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-iot' to 'verification-done-focal-
linux-iot'. If the prob
This bug is awaiting verification that the linux-gcp/5.4.0-1128.137
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-gcp' to 'verification-done-focal-
linux-gcp'. If the pro
This bug is awaiting verification that the linux-kvm/5.4.0-1112.119
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-kvm' to 'verification-done-focal-
linux-kvm'. If the pro
This bug is awaiting verification that the linux-oracle/5.4.0-1123.132
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-oracle' to 'verification-done-
focal-linux-oracle'. I
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.4.0-1043.47 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-focal-linux-xilinx-zynqmp'
to 'verification-done-focal-lin
This bug was fixed in the package linux-azure - 5.15.0-1063.72
---
linux-azure (5.15.0-1063.72) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1063.72 -proposed tracker (LP: #2061767)
* Packaging resync (LP: #1786013)
- [Packaging] drop getabis data
* Azure: Network doe
This bug was fixed in the package linux - 5.15.0-106.116
---
linux (5.15.0-106.116) jammy; urgency=medium
* jammy/linux: 5.15.0-106.116 -proposed tracker (LP: #2061812)
* CVE-2024-2201
- x86/bugs: Use sysfs_emit()
- KVM: x86: Update KVM-only leaf handling to allow for 100
This bug was fixed in the package linux - 5.15.0-106.116
---
linux (5.15.0-106.116) jammy; urgency=medium
* jammy/linux: 5.15.0-106.116 -proposed tracker (LP: #2061812)
* CVE-2024-2201
- x86/bugs: Use sysfs_emit()
- KVM: x86: Update KVM-only leaf handling to allow for 100
This bug is awaiting verification that the linux-gcp/5.15.0-1059.67
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gcp' to 'verification-done-jammy-
linux-gcp'. If the pro
This bug is awaiting verification that the linux-gke/5.15.0-1058.63
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gke' to 'verification-done-jammy-
linux-gke'. If the pro
This bug is awaiting verification that the linux-gke/5.15.0-1058.63
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gke' to 'verification-done-jammy-
linux-gke'. If the pro
This bug is awaiting verification that the linux-ibm/5.15.0-1054.57
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-ibm' to 'verification-done-jammy-
linux-ibm'. If the pro
This bug is awaiting verification that the linux-gcp/5.15.0-1059.67
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gcp' to 'verification-done-jammy-
linux-gcp'. If the pro
This bug is awaiting verification that the linux-ibm/5.15.0-1054.57
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-ibm' to 'verification-done-jammy-
linux-ibm'. If the pro
This bug is awaiting verification that the linux-gke/5.15.0-1058.63
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gke' to 'verification-done-jammy-
linux-gke'. If the pro
This bug is awaiting verification that the linux-gcp/5.15.0-1059.67
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gcp' to 'verification-done-jammy-
linux-gcp'. If the pro
This bug is awaiting verification that the linux-ibm/5.15.0-1054.57
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-ibm' to 'verification-done-jammy-
linux-ibm'. If the pro
This bug is awaiting verification that the linux-gke/5.15.0-1058.63
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gke' to 'verification-done-jammy-
linux-gke'. If the pro
This bug is awaiting verification that the linux-gcp/5.15.0-1059.67
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gcp' to 'verification-done-jammy-
linux-gcp'. If the pro
This bug is awaiting verification that the linux-ibm/5.15.0-1054.57
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-ibm' to 'verification-done-jammy-
linux-ibm'. If the pro
This bug is awaiting verification that the linux-gke/5.15.0-1058.63
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gke' to 'verification-done-jammy-
linux-gke'. If the pro
This bug is awaiting verification that the linux-gcp/5.15.0-1059.67
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gcp' to 'verification-done-jammy-
linux-gcp'. If the pro
1 - 100 of 478 matches
Mail list logo
