** Description changed:
+ The Nvidia driver corrupts and/or forgets its textures when resuming
+ from suspend. Unfortunately for the moment it's a "feature" of the
+ Nvidia driver documented here:
+
+
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt
+
** Changed in: gdm3 (Ubuntu)
Importance: Medium => High
** Changed in: gdm3 (Ubuntu)
Milestone: None => ubuntu-22.04
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Jeremy Bicha (jbicha)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Package changed: ubuntu => dpdk (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969342
Title:
running dpdk-testpmd shows "Failed to execute command of
OP_SET_RSS_HENA" in vm with
Public bug reported:
the expected result is packets are distributed to the specified queue
and marked with specified FDIR matched ID, but the actual result is NOT.
-DPDK 21.11 or DPDK 20.11, the same result.
-we have tried at least out-of-tree driver 1.8.3, it works as expected.
So basically
I also noticed this by launching "view /var/log/installer/syslog" on a
freshly installed Ubuntu desktop system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968912
Title:
vim.tiny reports 'E1187:
given how zfs works, to me this is normal and expected.
Also this is expected on btrfs, and on xfs with cow turned on.
zfs is copy on write filesystem, thus calling fallocate to "reserve" a
large amount of free space doesn't make sense. As the created file is
immutable in zfs, and any writes to
Public bug reported:
Fresh installation of 20.04.4 with installer created zfs native encrypted root
zfsutils-linux: 0.8.3-1ubuntu12.13
On reboot, zvol /dev/zvol entries are not being created. This seems to
effect different zvols each reboot.
Example logs:
```
-- A start job for unit
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
This bug was fixed in the package linux-azure - 5.4.0-1077.80
---
linux-azure (5.4.0-1077.80) focal; urgency=medium
* focal/linux-azure: 5.4.0-1077.80 -proposed tracker (LP: #1968796)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux-azure-cvm - 5.4.0-1076.79+cvm1
---
linux-azure-cvm (5.4.0-1076.79+cvm1) focal; urgency=medium
* focal/linux-azure-cvm: 5.4.0-1076.79+cvm1 -proposed tracker (LP:
#1968347)
* Packaging resync (LP: #1786013)
- debian/dkms-versions --
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
Commit "s390/pci: move pseudo-MMIO to prevent MIO overlap" landed in impish
with hash 35705e7746d4 and is included in impish's kernel 'Ubuntu-5.13.0-36.41'
and later.
Latest kernel in impish-updates is linux-generic | 5.13.0.40.49 |
impish-updates
hence this incl. the needed commit.
With that
Hi Jose
I've checked debian/copyright and Lintian output and both packages seem
fine.
I've uploaded ignition-gazebo with some minor changes. I changed the
version to 6.4.0+ds-0ubuntu1, as this package is not yet in Debian. I
also allowed sed to fail without failing the build, to allow building
Another quick update: in recent days we've gone from "blank white space"
back to "incorrect stride corruption" in all documented cases (embedded
browsers, help windows, MiniBrowser, etc).
I note in the dpkg logs, libglx-mesa0 got updated a few days ago, but
unfortunately I'm unsure exactly when
ok, thanks for moving this around. Feel free to let me know if you need
further info to debug this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969342
Title:
running dpdk-testpmd shows
After my bug report was put in status invalid (i.e. SPAM) I responded politely
(and asked
to read this bug report carefully) - which seems to be deleted (censorship? all
the calls
I have seen in my life had all deatails by customers in it) - and I was
informed via mail:
~~
Thank you for your
Minimal reproducer:
#!/bin/bash
# prints information about the current php environment
# php -d opcache.enable_cli=1 -d opcache.file_cache_only=1 -d
opcache.file_cache="/root/php-cache" -i
php -d opcache.enable_cli=1 -d opcache.file_cache_only=1 -d
opcache.file_cache="/root/php-cache" file1.php
I read the comment #19 and I was able to suspend correctly using s0ix
method. The problem is: The method requires using "echo mem |sudo tee
/sys/power/state" to enter on suspend mode, but I think the default
method, when using menu option and "systemctl suspend", is "freeze", not
"mem". Using
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
Will it be in the upcoming 22.04 release?
Because i see no
. /scripts/casper-helpers
in:
https://git.launchpad.net/casper/tree/scripts/casper-premount/20iso_scan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
I tried reproducing the issue on a Rpi4, cloning a repository via ssh
using pubkey authentication with a rsa2048 key stored in ssh-agent, it
worked fine. If you believe there's actually a bug here please provide
some steps we can follow to reproduce the issue from a clean Jammy
system, and we'll
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the
problem still exists,
Impish kernel on zfs:
andreas@nsnx:~$ rm foo.img
andreas@nsnx:~$ touch foo.img
andreas@nsnx:~$ fallocate -z -l 10M foo.img
fallocate: fallocate failed: Operation not supported
Jammy kernel on zfs:
root@j1:~# touch foo.img
root@j1:~# fallocate -z -l 10M foo.img
root@j1:~# ll foo.img
Public bug reported:
Hi,
It seems the Docler/Moby team is about to release Docker 22.04 (they
have recently updated the milestone name from 21.x). This release will
bring among many other things, the support for zstd compressed images.
Zstd support is something we would like to leverage in our
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968929
Title:
No Wayland support on NVIDIA systems
To manage notifications about this bug
It seems that view, as provided by vim.tiny now attempts to load
defaults.vim, which is shipped in the large vim-runtime package. All
vims depend on vim-common. It would seem to me that we should move
defaults.vim from vim-runtime to vim-common.
--
You received this bug notification because you
the recent update suggests the white rendering was indeed bug #1966418
which is resolved now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924251
Title:
Embedded browser display corruption under
This bug was fixed in the package linux-gcp - 5.4.0-1072.77
---
linux-gcp (5.4.0-1072.77) focal; urgency=medium
* focal/linux-gcp: 5.4.0-1072.77 -proposed tracker (LP: #1968829)
* Miscellaneous Ubuntu changes
- [packaging] Update annotations for arm64
- [packaging]
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
This bug was fixed in the package linux-gcp - 5.4.0-1072.77
---
linux-gcp (5.4.0-1072.77) focal; urgency=medium
* focal/linux-gcp: 5.4.0-1072.77 -proposed tracker (LP: #1968829)
* Miscellaneous Ubuntu changes
- [packaging] Update annotations for arm64
- [packaging]
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
** Description changed:
- 1) Ubuntu 22.04
- 2) software-properties-gtk 0.99.22
- 3) No crash when using Additional Drivers with
ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320
- 4) It can install libcamhal-ipu6ep0 from Additional Drivers without any
problem.
+ 1) The release of Ubuntu
Launchpad has imported 49 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1751363.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
However there is now also this:
https://github.com/openzfs/zfs/pull/13338/files
which seems to indicate that my / zfs understanding of the fallocate
kernel flags are not what is done on other filesystems (and expected by
stuff).
If needed, we can look into pulling in
imho, mysql should still gain zfs specific knowledge that doing
fallocate on CoW filesystems doesn't do what one expects it to do.
** Changed in: mysql-8.0 (Ubuntu)
Status: Invalid => Triaged
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug
DPDK 20.11 or DPDK 21.11, the same result
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969454
Title:
dpdk-testpmd test shows "init vf failed" with in-tree driver on
ubuntu22.04
To manage
Public bug reported:
run ./dpdk-testpmd -c 0x0f -n 4 -- -i --portmask=0x3 with vf port ,the
detail log
root@sp:/opt/APP/utility/dpdk-stable-20.11.3/build/app# ./dpdk-testpmd
-c 0x0f -n 4 -- -i --portmask=0x3
EAL: Detected 128 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Detected static linkage
/root/dpdk-21.11/build/app/dpdk-testpmd -c 0xff -n 6 -a 00:06.0
--file-prefix=vf -- -i --rxq=16 --txq=16
testpmd> set fwd rxonly
testpmd> set verbose 1
testpmd> start
the flow director rule examples are like below:
flow create 0 ingress pattern eth / ipv4 src is 192.168.100.1 dst is
This bug is awaiting verification that the linux-
intel-5.13/5.13.0-1011.11 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' to 'verification-
done-focal'. If the problem still
This bug is awaiting verification that the linux-
intel-5.13/5.13.0-1011.11 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' to 'verification-
done-focal'. If the problem still
This bug is awaiting verification that the linux-
intel-5.13/5.13.0-1011.11 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' to 'verification-
done-focal'. If the problem still
This bug is awaiting verification that the linux-
intel-5.13/5.13.0-1011.11 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' to 'verification-
done-focal'. If the problem still
Here you can see the GNOME extension Vitals showing corrupted values
after a suspend
** Attachment added: "Corrupted screen"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929/+attachment/5581433/+files/Screenshot%20from%202022-04-19%2008-21-28.png
--
You received this bug
I read the comment #19 and I was able to suspend correctly using s0ix
method. The problem is: The method requires using "echo mem |sudo tee
/sys/power/state" to enter on suspend mode, but I think the default
method, when using menu option and "systemctl suspend", is "freeze", not
"mem". Using
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968912
Title:
vim.tiny reports 'E1187: Failed to source defaults.vim' on execution
in default install
To manage
** Changed in: ubuntu-z-systems
Status: Fix Committed => 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/1962831
Title:
[UBUNTU 20.04] KVM: Enable storage key checking for
** Changed in: ubuntu-z-systems
Status: Fix Committed => 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/1962578
Title:
[UBUNTU 20.04] Fix SIGP processing on KVM/s390
To manage
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1969455
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package linux - 4.15.0-176.185
---
linux (4.15.0-176.185) bionic; urgency=medium
* bionic/linux: 4.15.0-176.185 -proposed tracker (LP: #1966771)
* Bionic update: upstream stable patchset 2022-03-04 (LP: #1963717)
- can: bcm: fix UAF of bcm op
-
This bug was fixed in the package linux - 4.15.0-176.185
---
linux (4.15.0-176.185) bionic; urgency=medium
* bionic/linux: 4.15.0-176.185 -proposed tracker (LP: #1966771)
* Bionic update: upstream stable patchset 2022-03-04 (LP: #1963717)
- can: bcm: fix UAF of bcm op
-
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.60.02-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1966093):
- Added support for the following GPUs:
NVIDIA RTX
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.147-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-390 (390.147-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1966093):
- Fixed a bug where vkCreateSwapchain could cause the X Server to
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.147-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-390 (390.147-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1966093):
- Fixed a bug where vkCreateSwapchain could cause the X Server to
The jammy RC (20220418.2) looks good for Ampere Mt. Jade Altra (bizzy).
I can pxe install the server successfully.
By the way autoinstall of subiquity also works like a charm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Ubuntu 22.04 was working fine until todays update.
The following packages will be upgraded:
casper
1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
56 not fully installed or removed.
Need to get 0 B/52.0 kB of archives.
After this operation, 3,072 B of
Steve, let's remove vmware-nsx as well.
** Summary changed:
- [RM] neutron-fwaas
+ [RM] neutron-fwaas, vmware-nsx
** Changed in: vmware-nsx (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not an apt bug in either case if it crashes your system
** Package changed: apt (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The old logo is used for the "Install Ubuntu" picture when ubiquity
first launches.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.15
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules:
** Attachment added: "Screenshot from 2022-04-19 12-02-44.png"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1969455/+attachment/5581431/+files/Screenshot%20from%202022-04-19%2012-02-44.png
** Tags added: rls-jj-incoming
** Changed in: ubiquity (Ubuntu)
Status: New =>
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.60.02-0ubuntu0.21.10.2
---
nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.21.10.2) impish; urgency=medium
[ Jeremy Szu ]
* Fix regex in modalias addition, since it does not work
in dash (LP: #1964756)
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.60.02-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.20.04.2) focal; urgency=medium
[ Jeremy Szu ]
* Fix regex in modalias addition, since it does not work
in dash (LP: #1964756).
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux-azure - 5.4.0-1077.80
---
linux-azure (5.4.0-1077.80) focal; urgency=medium
* focal/linux-azure: 5.4.0-1077.80 -proposed tracker (LP: #1968796)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
The verification of the Stable Release Update for nvidia-graphics-
drivers-510 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
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.60.02-0ubuntu0.21.10.2
---
nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.21.10.2) impish; urgency=medium
[ Jeremy Szu ]
* Fix regex in modalias addition, since it does not work
in dash (LP: #1964756)
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.60.02-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.20.04.2) focal; urgency=medium
[ Jeremy Szu ]
* Fix regex in modalias addition, since it does not work
in dash (LP: #1964756).
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.147-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-390 (390.147-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1966093):
- Fixed a bug where vkCreateSwapchain could cause the X Server to
This bug was fixed in the package linux-azure - 5.4.0-1077.80
---
linux-azure (5.4.0-1077.80) focal; urgency=medium
* focal/linux-azure: 5.4.0-1077.80 -proposed tracker (LP: #1968796)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux-azure - 5.4.0-1077.80
---
linux-azure (5.4.0-1077.80) focal; urgency=medium
* focal/linux-azure: 5.4.0-1077.80 -proposed tracker (LP: #1968796)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the
problem still exists,
Public bug reported:
1) Ubuntu 22.04
2) software-properties-gtk 0.99.22
3) No crash when using Additional Drivers with
ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320
4) It can install libcamhal-ipu6ep0 from Additional Drivers without any problem.
** Affects: oem-priority
The impish kernel returns "not supported" when fallocate is used in the
way mysql does it. That makes mysql aware of the problem, and switch
strategies, and it works.
The jammy kernel is saying all is fine with the call and its results,
but it isn't. Mysql, or any userspace, shouldn't be second
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
** Tags added: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969460
Title:
software-properties-gtk crashed with TypeError in
on_driver_selection_changed(): Expected a string or a
** Tags added: needs-packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969450
Title:
[needs-packaging] rshell
To manage notifications about this bug go to:
Note: you can test if zstd support works (or not) by trying to use this
zstd:chunked image produced by the zstd:chunked developer in the podman
team:
docker run --rm --pull=always gscrivano/zstd-chunked:fedora whoami
Which for now fails with:
fedora: Pulling from gscrivano/zstd-chunked
asaik casper is now 1.470 in the iso, there I see till 1.469. Maybe it's
correct
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960457
Title:
Please remove lupin from the archive
To manage
If you see the source code of casper 1.470 it's correct.
http://archive.ubuntu.com/ubuntu/pool/main/c/casper/casper_1.470.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960457
Title:
Please
I'm also having this with Jammy. I am using Wayland with the AMD opensource
GPU drivers.
The following appears in syslog:
Apr 19 15:45:56 ROC-Cube kernel: [ 1629.677203] evolution[23936]: segfault at 0
ip 7fef9c195536 sp 7ffe2be1cf88 error 4 in
What file or binary package does this bug report related to?
Also what version of Ubuntu are you using?
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 373 matches
Mail list logo