Public bug reported:
There are many reports out there about mate panel crashes.
Ubuntu Version used: Mantic
People taking care about this package should make a decision and use the latest
mate-panel sourcecode in order to not duplicate developer efforts to fix bugs.
Mate-panel is a highly
Public bug reported:
dconf-editor crashes with Ubuntu Mantic and the Mate Desktop
environment. The solution was to install the latest dconf-editor from
source.
https://gitlab.gnome.org/GNOME/dconf-editor
** Affects: dconf-editor (Ubuntu)
Importance: Undecided
Status: New
--
You
Public bug reported:
Coasting is the kind of automatic afterscroll like on the iphone, it doesn't
work properly with the version provided by Ubuntu Mantic amd64.
Sometimes it scrolls automatically sometimes it just stops immediately.
Solution => install the xserver-xorg-input-synaptics git
@sldayo Can you help? This is what I get:
$ sudo apt install gir1.2-mutter-10/jammy-proposed libmutter-10-0/jammy-proposed
[sudo] password for donn:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package gir1.2-mutter-10 is not available, but is
Public bug reported:
A short while after this clean installation of Ubuntu 24.04 LTS, a
strange unknown display appeared both in GNOME Settings and in NVIDIA X
Server Settings. I noticed it because I could see my mouse cursor
disappear beyond the boundaries of my monitor as if it is being
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]
** Changed in: calamares (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gnome-shell-extension-tiling-assistant
Status: Unknown => 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/2064646
Title:
Click on the topbar invokes the enhanced
I was unable to test another graphics card in the pcie slot, but the
intel graphics from the cpu do not reproduce this issue.
I've also tested with another monitor with similar specs and the issue
doesn't occur on that one, so I think it's isolated to only one monitor
I have (the affected monitor
Still an issue in 23.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513244
Title:
"Split in volumes" option is grayed out
To manage notifications about this bug go to:
Yes. I don't know how to close the bug or mark it as resolved. I don't
see an option for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049242
Title:
CIFS Mounts Keep Load Average at n+1
To
The qemu backport to jammy regressed in the final weeks of noble
development. The build dependency error is:
The following packages have unmet dependencies:
librdmacm1t64 : Breaks: librdmacm1 (<
50.0-2build2~backport22.04.202403311003~ubuntu22.04.1) but
Une erreur s'est produite lors de la création de la base de données.
│[97m[40m [6;41H[30m[47m│
│[97m[40m [7;41H[30m[47m│ mysql said: ERROR 1819 (HY000) at line 1:
Your password does not satisfy the current policy requirements
** Changed in: phpmyadmin (Ubuntu)
Assignee:
** Changed in: mutter
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/2026194
Title:
When clicking on some maximized or tiled windows, focus on roughly the
lower
the issues in Comment #10 appear to be closed, and they are not mentioned
anyway on
https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043
so it is confusing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
All autopkgtests for the newly accepted linux-meta-nvidia (6.8.0-1006.6+1) for
noble have finished running.
The following regressions have been reported in tests triggered by the package:
zfs-linux/2.2.2-0ubuntu9 (arm64)
Please visit the excuses page listed below and investigate the failures,
Oh, and Oracular indeed just migrated while I posted the comment (#21
#22); nice timing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064580
Title:
Please update the package to 20240320.00
To
This bug was fixed in the package google-osconfig-agent -
20240320.00-0ubuntu1~20.04.0
---
google-osconfig-agent (20240320.00-0ubuntu1~20.04.0) focal; urgency=medium
* Rebuild for Focal. (LP: #2064580)
- d/{rules,control}: use Go 1.21 for using the "slices" module.
This bug was fixed in the package google-osconfig-agent -
20240320.00-0ubuntu1~22.04.0
---
google-osconfig-agent (20240320.00-0ubuntu1~22.04.0) jammy; urgency=medium
* Rebuild for Jammy. (LP: #2064580)
* d/{rules,control}: use Go 1.21 for using the "slices" module.
This bug was fixed in the package google-osconfig-agent -
20240320.00-0ubuntu1~23.10.0
---
google-osconfig-agent (20240320.00-0ubuntu1~23.10.0) mantic; urgency=medium
* Rebuild for Mantic. (LP: #2064580)
google-osconfig-agent (20240320.00-0ubuntu1) oracular; urgency=medium
[
The verification of the Stable Release Update for google-osconfig-agent
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that
This bug was fixed in the package google-osconfig-agent -
20240320.00-0ubuntu1~24.04.0
---
google-osconfig-agent (20240320.00-0ubuntu1~24.04.0) noble; urgency=medium
* Rebuild for Noble. (LP: #2064580)
google-osconfig-agent (20240320.00-0ubuntu1) oracular; urgency=medium
[
Summary for SRU release.
Autopkgtests: OK
- Devel/O: proposed migration was blocked in a test queued since early May;
re-triggered it and it passed; this should migrate soon.
- Stable/NMJF: re-triggered/cleared autopkgtests pending; all series/archs
passed.
Builds/FTBFS: OK
- Focal/riscv64:
This bug was fixed in the package google-osconfig-agent -
20240320.00-0ubuntu1
---
google-osconfig-agent (20240320.00-0ubuntu1) oracular; urgency=medium
[ Chloé 'kajiya' Smith ]
* New upstream version for upstream tag 20240320.00. (LP: #2064580)
[ Mitchell Dzurick ]
*
The result of this is usually that the user gets frustrated waiting for
updates that never finish installing, so they just turn off the
computer. Then next time there are even more updates, making he problem
worse.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
It isn't clear to me why apt-check is so slow, but from systemctl I can
see that it runs lsb-release to get the release name at least 10 to 20
times per invocation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For example look at .var.log.apt.history.log.txt
Many packages take less than a second to install. But in between each
one is a 15 to 20 second delay. That delay is the time during which apt-
check is running.
You can watch this happening by running "watch systemctl status apt-
daily-upgrade"
Public bug reported:
The unattended upgrade services runs "apt-check" to update the MOTD
where a summary of available updates is displayed. It does this after
every package that is installed. Unfortunately, apt-check is extremely
expensive - it takes about 15 seconds to run.
If you have a
And my error in log was:
pam_radius_auth: Failed to open RADIUS IPv6 socket: Address family not
supported by protocol
This is with ipv6 disabled, trying both ipv4 alias and ipv4 address
directly in conf.
18.04 packaging works
This was tested on 22.04 LTS packages.
enabling ipv6 on system and
Thanks for the update Nicolas.
Is there any further progress on this as we are past April now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2028864
Title:
[snap] chromium browser does not work
Public bug reported:
Disabling ipv6 causes the radius module to fail and thus the authentication if
using radius.
Usually CIS or STIG involves disabling ipv6 if not used in network which
this situation is found out in.
Requesting to pull change to allow ipv6=no option in
pam_radius_auth.conf
one of the best information https://premiereautoglass.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628204
Title:
linux: 4.4.0-41.61 -proposed tracker
To manage notifications about this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: console-setup (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/2065679
All autopkgtests for the newly accepted ubuntu-advantage-tools (32.1~16.04) for
xenial have finished running.
The following regressions have been reported in tests triggered by the package:
software-properties/unknown (i386)
ubuntu-advantage-tools/unknown (arm64, i386)
Please visit the excuses
All autopkgtests for the newly accepted ubuntu-advantage-tools (32.1~16.04) for
xenial have finished running.
The following regressions have been reported in tests triggered by the package:
software-properties/unknown (i386)
ubuntu-advantage-tools/unknown (arm64, i386)
Please visit the excuses
All autopkgtests for the newly accepted ubuntu-advantage-tools (32.1~16.04) for
xenial have finished running.
The following regressions have been reported in tests triggered by the package:
software-properties/unknown (i386)
ubuntu-advantage-tools/unknown (arm64, i386)
Please visit the excuses
All autopkgtests for the newly accepted ubuntu-advantage-tools (32.1~16.04) for
xenial have finished running.
The following regressions have been reported in tests triggered by the package:
software-properties/unknown (i386)
ubuntu-advantage-tools/unknown (arm64, i386)
Please visit the excuses
All autopkgtests for the newly accepted ubuntu-advantage-tools (32.1~16.04) for
xenial have finished running.
The following regressions have been reported in tests triggered by the package:
software-properties/unknown (i386)
ubuntu-advantage-tools/unknown (arm64, i386)
Please visit the excuses
Public bug reported:
Please sync aqemu 0.9.2-4 (universe) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* No-change rebuild for CVE-2024-3094
* Drop explicit libqt5dbus5 dependency, there does not appear any dbus code?
The Ubuntu delta dropping
Hi Sebastien,
it freezes
at first i just logout
then i actually open process to kill the process
then i figure if i click on the location bar /home/Documents on the same
window, it allows me to get back control
but i have to tap a few times which is still annoying and this is just
to regain
Public bug reported:
Please sync adonthell 0.3.8-3 (universe) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* No-change rebuild for CVE-2024-3094
* d/p/drop-deprecated-swig-flags.patch: fix FTBFS caused by dropped
swig flag (LP: #2059154)
*
Public bug reported:
# System Details Report
---
## Report details
- **Date generated:** 2024-05-14 16:11:26
## Hardware Information:
- **Hardware Model:** ASUS TUF GAMING X570-PRO
_WI-FI_
- **Memory:**
** Tags removed: verification-needed-jammy-linux-nvidia-6.8
** Tags added: verification-done-jammy-linux-nvidia-6.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054809
Title:
linux: please move
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-6.8' to
1 - 100 of 352 matches
Mail list logo
