Backporters: I uploaded backports from noble-proposed to mantic and
jammy. They didn't propagate yet due to noble being jammed so much, but
we do validate them on both releases upstream. I'll let you decide
whether to accept or stall them.
--
You received this bug notification because you are a
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059080
Title:
Add Real-time Linux Analysis tool (rtla) to linux-tools
To
Hello Julian, or anyone else affected,
Accepted nullboot into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nullboot/0.5.0-0ubuntu0.22.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
So something changed to add -Werror=implicit-function-declaration at
build time (gcc didn't change so maybe dpkg?), which should have caused
the other arches to fail as well but since they ran at different times
they pulled different versions of build dependencies. This will likely
get fixed on a
Hi all,
This should be fixed on the latest driver 550.67 -
https://www.nvidia.com/Download/driverResults.aspx/223429/en-us/.
Please help verify if this is resolved on your systems. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
No need to reinstall the OS. I've posted a script for downgrading mutter
packages for Ubuntu 23.10, 23.04, and 22.04 here:
https://askubuntu.com/a/1509288/96411
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for tmux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: tmux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048983
*** This bug is a duplicate of bug 1284654 ***
https://bugs.launchpad.net/bugs/1284654
** This bug is no longer a duplicate of private bug 1051264
** This bug has been marked a duplicate of private bug 1284654
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1284654 ***
https://bugs.launchpad.net/bugs/1284654
** This bug is no longer a duplicate of private bug 1051264
** This bug has been marked a duplicate of private bug 1284654
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1284654 ***
https://bugs.launchpad.net/bugs/1284654
** This bug is no longer a duplicate of private bug 1051264
** This bug has been marked a duplicate of private bug 1284654
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I wonder if this is related to bug 1284654.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060089
Title:
[noble] plymouthd crashed with SIGSEGV in
ply_event_loop_stop_watching_fd() from
Public bug reported:
plymouthd crashed with SIGSEGV in:
ply_event_loop_stop_watching_fd () from /lib/x86_64-linux-gnu/libply.so.5
ply_kmsg_reader_stop () from /lib/x86_64-linux-gnu/libply-splash-core.so.5
https://errors.ubuntu.com/oops/23775f22-f0fd-11ee-9d81-fa163ec44ecd
** Affects: plymouth
Public bug reported:
plymouthd crashed with SIGSEGV in:
ply_terminal_set_disabled_input () from
/lib/x86_64-linux-gnu/libply-splash-core.so.5
?? () from /usr/lib/x86_64-linux-gnu/plymouth/renderers/drm.so
ply_renderer_open_input_source () from
/lib/x86_64-linux-gnu/libply-splash-core.so.5
??
Hello,
A gentle ping on this issue, it still shows up on jammy security report
and looks like 2ubuntu2.3 here
https://changelogs.ubuntu.com/changelogs/pool/main/a/apparmor/apparmor_3.0.4-2ubuntu2.3/changelog
doesn't have the fix.
@jjohansen can we please advise on when the fix will be backported
Hi Jeff,
Again, I apologise for introducing this regression, but we are on our
way to getting this fixed.
The fixes are:
commit 1e3ca7fe199531a372bb8e1c1033d8973097be50
Author: NeilBrown
Date: Wed Jul 26 13:47:42 2017 -0400
Subject: mount: move handling of "-t nfs4" into nfs_nfs_version()
this is no longer a problem... though in 23.10, my desktops will switch
occasionally on its own. I'll wait for 24.04 to see if that's still a
problem before reporting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached is a debdiff for Focal which fixes this issue.
** Summary changed:
- Issue with nfs4.0 mounts after upgrade to 3.6
+ Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together
** Summary changed:
- Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used
If it lands in 46.1 then Ubuntu 24.04 will get it after that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040453
Title:
Gnome 45 crash on restart in X11 session [Window manager error:
Another
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3329
It seems the developer team of gnome will fix this bug in version 46.1.
Any progress or plan for ubuntu? Will it be fixed in Ubuntu 24.04 LTS?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
We now have a follow-up SRU. Removing the block-proposed tags.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1989078
Title:
libvirt-qemu apparmor profile doesn't allow locking of AAVMF firmware
To
Hello Paride, or anyone else affected,
Accepted libvirt into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/6.0.0-0ubuntu8.18 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Mauricio, or anyone else affected,
Accepted libvirt into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/6.0.0-0ubuntu8.18 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thanks everybody for reporting this issue. It has now been resolved. PDF
downloads are now built with GitHub Pages.
** Changed in: xubuntu-docs (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
how to reduce:
1. Stop clock synchronization
systemctl stop chrony
2. Set the timezone to Dublin
timedatectl set-timezone Europe/Dublin
3. Change the time to waitting for Daylight saving time switch
timedatectl set-time "2024-03-30 23:59:50"
At 0 o'clock, the system is executing atop
the
bugfix to v249 or update 255 version in Jammy Jellyfish to fix it. thank
you.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "systemd atop"
https://bugs.launchpad.net/bugs/2060082/+attachment/5761387/+files/screenshot-20240402-
** Summary changed:
- Bluetooth earbuds not being 'set up' on new machine
+ T60 Bluetooth earbuds not being 'set up' on new machine
** Changed in: bluez (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks!
** Changed in: tracker-miners (Ubuntu Jammy)
Assignee: (unassigned) => Talha Can Havadar (tchavadar)
** Changed in: tracker-miners (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
All autopkgtests for the newly accepted linux-meta-nvidia-tegra
(5.15.0.1023.23) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/249.11-0ubuntu3.12 (arm64)
wireguard/unknown (amd64)
Please visit the excuses page listed
Everyone is very busy with the 24.04 release as well as other
responsibilities. So don't take silence to imply anything :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2028165
Title:
nvidia-dkms-*
Hi Jeff,
I believe this is a valid bug. I can reproduce it:
On Focal:
$ sudo mount -t nfs4 -o vers=4.1 -vvv jammy-nfs-server:/ /mnt
mount.nfs4: timeout set for Wed Apr 3 00:51:23 2024
mount.nfs4: trying text-based options
'vers=4.2,addr=192.168.122.217,clientaddr=192.168.122.9'
On Jammy:
$
This bug was fixed in the package gcc-14 - 14-20240330-1ubuntu2
---
gcc-14 (14-20240330-1ubuntu2) noble; urgency=medium
* No-change rebuild for CVE-2024-3094
-- Steve Langasek Sun, 31 Mar 2024
01:02:56 +
** Changed in: gcc-14 (Ubuntu)
Status: In Progress => Fix
** Description changed:
[ Impact ]
* GDB 10.0 introduced a regression where it cannot inspect any global
variables in any D programs compiled by any D compiler.
* LDC2 and GDC upstream stated Focal does not have such a problem and stuck
to this release for their test images.
[
** Description changed:
- Summary:
+ [ Impact ]
- * GDB 10.0 introduced a regression where it cannot inspect any global
variables in any D programs compiled by any D compiler.
- * LDC2 and GDC upstream stated Focal does not have such a problem and stuck
to this release for their test
Public bug reported:
The armhf build fails with the following build error:
../subprojects/mocklibc-1.0/src/netgroup-debug.c: In function
‘netgroup_debug_print_entry’:
../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit
declaration of function ‘print_indent’
** Changed in: libfolks
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060073
Title:
folks build test failures with glib 2.80
To manage notifications about this bug
I've found a workaround:
I conducted a fresh installation of Ubuntu 22.04.4 and subsequently
marked specific packages for holding using the following commands:
$ sudo apt-mark hold gir1.2-mutter-10
$ sudo apt-mark hold libmutter-10-0
$ sudo apt-mark hold mutter-common
Following this, I
I can confirm that the xmms2 package in mantic-proposed has fixed the
bug for me.
Test done:
1. Install xmms2 from mantic-proposed
2. create a playlist
3. Add few mp3 to the playlist according to the testplan
4. Switch the test playlist with the command "xmms2 playlist switch"
5. Execute "xmms2
I can confirm that the xmms2 package in jammy-proposed has fixed the bug
for me.
Test done:
1. Install xmms2 from jammy-proposed
2. create a playlist
3. Add few mp3 to the playlist according to the testplan
4. Switch the test playlist with the command "xmms2 playlist switch"
5. Execute "xmms2
This bug is awaiting verification that the linux/4.15.0-224.236 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-bionic-linux' to 'verification-done-bionic-linux'.
If the problem still
This bug is awaiting verification that the linux/4.15.0-224.236 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-bionic-linux' to 'verification-done-bionic-linux'.
If the problem still
I can confirm that the lcov package in mantic-proposed has fixed the bug
for me.
Test done:
1. Install lcov on a Mantic image
2. Execute "lcov -h" and confirmed the issue is still seen
3. Add mantic-proposed to apt sources.list
4. Install lcov from mantic-proposed
5. Execute "lcov -h" again to
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059738
Title:
Kernel 6.8 - Shutdown/Reboot hangs
** Changed in: linux-signed-hwe-6.5 (Ubuntu)
Assignee: (unassigned) => Anthony Wong (anthonywong)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059973
Title:
my touch pad doesn't wok at all.
** Changed in: linux-nvidia (Ubuntu)
Assignee: (unassigned) => Jose Ogando Justo (joseogando)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059814
Title:
Enable GDS in the 6.8 based
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Anthony Wong (anthonywong)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059827
Title:
System hung indefinitely during a Software
** Changed in: linux-bluefield (Ubuntu)
Assignee: (unassigned) => Jose Ogando Justo (joseogando)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059951
Title:
mlxbf_gige: stop interface during
** Changed in: linux-bluefield (Ubuntu)
Assignee: (unassigned) => Jose Ogando Justo (joseogando)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059961
Title:
genetlink: fix single op policy
** Changed in: linux-hwe-6.5 (Ubuntu)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2047154
Title:
[amdgpu][drm] *ERROR*
** Changed in: linux-signed-hwe-6.5 (Ubuntu)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059353
Title:
kernel
** Changed in: linux-signed-hwe-6.5 (Ubuntu)
Assignee: (unassigned) => Anthony Wong (anthonywong)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059820
Title:
package
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059712
Title:
`perf report` complains about
I can confirm that the sagemath package in mantic-proposed has fixed the
bug for me.
Test done according to the testplan:
$ sage
┌┐
│ SageMath version 9.5, Release Date: 2022-01-30 │
│ Using Python 3.11.6.
** Changed in: thunderbird (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059873
Title:
Thunderbird needs custom css to match Yaru colors
To manage
Reading this upstream bug, it looks like it's fixed in 1.4.0, which will be
available in 24.04/Noble or 22.04/Jammy with the Lubuntu Backports PPA added to
it.
https://github.com/lxqt/lxqt/issues/2391#issuecomment-1533247900
** Changed in: lxqt-config (Ubuntu)
Status: Confirmed => Fix
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (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/2048517
Title:
> For me the biggest problem was the socket unit beeing re-enabled when
I had it disabled it but still running sshd.service (ie without socket
activation) - now you're unexpectidly switched back to using socket
activation - something I explicitly opted out of.
Okay. We could probably adjust the
Upstream released Sigil 2.1.0, carrying this patch, so it's no longer
necessary if an upgrade is planned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055345
Title:
sigil < 2.1.0 plugin support
As 23.04 is no longer a supported release of Lubuntu, is this still a
problem with 23.10?
** Changed in: lxqt-config (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is this still an issue? If so, I have two questions:
1. None of the listed resolutions work?
2. When you try to change the resolution in `xrandr`, what specific command do
you use and what is the response?
** Changed in: lxqt-config (Ubuntu)
Status: New => Incomplete
--
You received
Public bug reported:
Unable to load podcast feeds in Rythmbox.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: rhythmbox 3.4.7-2ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
** Changed in: procps (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057792
Title:
Some Games are crashing linked to a vm_max_map_count too low
To manage
Can't reproduce in the oldest currently supported version of Lubuntu:
22.04/Jammy.
** Changed in: lxqt-config (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is this still an issue?
** Changed in: lxqt-config (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/1876503
Title:
Keyboard input suddenly stops to work, but
** Bug watch added: github.com/lxqt/lxqt-config/issues #756
https://github.com/lxqt/lxqt-config/issues/756
** Also affects: lxqt via
https://github.com/lxqt/lxqt-config/issues/756
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
** Tags removed: verification-needed-focal-linux-aws-5.15
verification-needed-focal-linux-nvidia-tegra-5.15
verification-needed-jammy-linux-aws-fips
verification-needed-jammy-linux-nvidia-tegra
** Tags added: verification-done-focal-linux-aws-5.15
Looking at the upstream bug, I believe this to be fixed in 1.4.0 which
will be available in Noble/24.04 and is also available in Jammy/22.04
with the Lubuntu backports (https://launchpad.net/~lubuntu-
dev/+archive/ubuntu/backports).
If this issue persists in 1.4.0, please reopen.
** Changed in:
Is this still an issue in 22.04/Jammy or beyond?
** Changed in: lxqt-config (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857946
Title:
windows
** Changed in: lxqt-config (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/1835595
Title:
Cannot turn off laptop LED using Monitor Settings
To manage
Is this still an issue in Jammy, Mantic or Noble?
** Changed in: lxqt-config (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/1855517
Title:
xscreensaver -
While still present in 22.04/Jammy, 23.10/Mantic (and beyond) is not
affected.
The only thing that's not known: where the fix came from. There was some
suggestion that the bug existed in Qt, so that's probably where the fix
is. In any case, I think that means a backport is likely out of the
I was able to reproduce the bug on Focal, and since we seem to carry the
same version on Jammy/Mantic (and likely Noble), it's probable that the
bug also happens in those releases.
For future reference:
# apt install -y libvirt-daemon-system bind9 dnsmasq
Reboot, and try bringing up the
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2050083
Title:
generate and ship vmlinux.h to
Public bug reported:
folks build tests are failing.
I reported this issue upstream. It appears to be triggered by glib 2.80
and gobject-introspection 1.80.
We worked around this issue for Ubuntu 24.04 LTS by ignoring build test
failures because it was essential that we build folks to clear
Public bug reported:
ruby-faraday-middleware was marked as deprecated by ruby-faraday 2.x:
https://github.com/lostisland/faraday_middleware?tab=readme-ov-
file#faraday-middleware
As expected, the tests do not work with the new version. We need to follow
Debian and request its removal:
The attachment "python-pytest-flake8_1.1.1-4ubuntu1.debdiff" seems to be
a debdiff. The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff. If
the attachment isn't a patch, please remove the "patch" flag from the
attachment,
I'm not that invested in the having openssh-server installed but not
running use-case, but in general people do not like their local
configuration beeing overridden on package upgrades in this manner.
I could image people having it installed for the man-pages, or maybe
using other units for it
Public bug reported:
We want to enable tracks for different versions of the out-of-tree
modules. For now we only have R36.3, so create the meta packages for
that version.
These meta packages include:
* linux-nvidia-tegra-igx-r36.3-igpu: for non-realtime kernel, R36.3 OOTM, and
iGPU display
Compressing a folder in nemo works now with 44-2 and it works with 43
for me also. Thank you for testing and reporting that issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059335
Title:
FFe:
now in proposed
** Changed in: numpy (Ubuntu)
Status: Triaged => 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/2059714
Title:
FFe: update numpy to 1.26.x
To manage
Public bug reported:
ruby-behance/0.6.1-4 does not support ruby-faraday 2.x and last upstream
commit in the Github repo was from 6 years ago:
https://github.com/amedrz/behance
Apparently, there will not be any further developement. In Debian, the
Ruby team is planning to remove it from the
All autopkgtests for the newly accepted linux-meta-aws-6.5
(6.5.0.1017.17~22.04.2) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-aws-6.5/unknown (arm64)
Please visit the excuses page listed below and investigate the
Not sure who all the upstream(s) involved might be, but from my personal
PoV at least you can add all the options you like… the topic gets harder
if we talk defaults & changing (e.g.) the lists completely (like that
tabular verbose-explosion thingy from apk or whatever it was). At some
point it
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~20.04.1 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-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~20.04.1 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-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~20.04.1 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-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~20.04.1 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-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~20.04.1 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-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~20.04.1 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-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~20.04.1 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-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~20.04.1 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-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~20.04.1 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-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~20.04.1 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-
nvidia-tegra-5.15' to
1 - 100 of 378 matches
Mail list logo
