Public bug reported:
not sure?
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture:
** Changed in: linux (Ubuntu)
Status: Confirmed => New
** Description changed:
- HP hotkeys does not work at all on HP 15-da1071ne laptop. Brightness
- keys returns the same scancode, airplane mode returns nothing at all,
- closing the lid toggles airplane mode.
+ Some HP hotkeys does not
Hi Tim,
thanks for your afford!
Best regards,
Kai.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1959665
Title:
linux-image-5.4.0-97.110 freezes by accessing cifs shares
Status in
Closing the LXC side of this bug as there's nothing we can really do here.
It's either a kernel issue (needs support for their socket option within a
network namespace) or an open-iscsi issue where they could have some kind of
fallback mechanism.
** Changed in: lxc (Ubuntu)
Status:
Moving over to the kernel as a userspace process shouldn't be able to
cause such a hang regardless of what it does so this looks like a kernel
bug (lock related by the looks of it).
** Package changed: lxc (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member
You have been subscribed to a public bug:
If I have umask 007 (or any other value that masks the world-execute
bit) when I run lxc-start for the first time after logging in, my host
system enters a state with the following problems:
* lxc-stop hangs forever instead of stopping any container,
It looks like I lost track of this browser tab a lot longer than I
expected.
Thanks Hangyu Hua for the fixes! :)
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
All autopkgtests for the newly accepted linux-meta-hwe-5.11 (5.11.0.60.61) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64, amd64)
nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64)
Something new (2 hours old) for you to try:
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1950720
** Description changed:
- All ftrace tests from selftests are failing with bionic:linux
- 4.15.0-168.176 on s390x:
+ SRU Justification
+
+ [Impact]
+
+ There seems to have been a typo in Commit 85bf17b28f97
+ ("recordmcount.pl: look for jgnop instruction as well as bcrl on s390")
+ that causes
All autopkgtests for the newly accepted linux-meta-gcp (5.13.0.1014.13) for
impish have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/248.3-1ubuntu8.2 (amd64)
Please visit the excuses page listed below and investigate the failures,
Ah, I see the report refers to a Core Duo processor and that is what the
T61p has too (Intel T7700 to be precise).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1910927
Title:
Suspend
Recently I installed Ubuntu 20.04.3 LTS on an old Lenovo laptop (T61p).
I was disappointed to discover that suspend did not work (as described
in this report, black screen and no way to recover). I tried two
version 5 kernels (5.13.0-27-generic and 5.8.0-43-generic).
As a wild guess I downloaded
yes, great we finally got there. thumbs up.
works on my e15 gen 2 amd.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and
Public bug reported:
I installed ubuntu on my pc, and since then my touchpad is not working.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1
ProcVersionSignature: User Name 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux
Thank you!
After yesterday's updates my computer can shutdown correctly,
Antonio
On Tue, Jan 18, 2022 at 3:30 PM Ubuntu Foundations Team Bug Bot <
1958...@bugs.launchpad.net> wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. It seems that your bug
Sorry Mr Launchpad Janitor, you are mistaken.
This bug is NOT FIXED in impish 5.13.0-28.31 ...
my laptop proves you wrong!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1927808
Power cable unplug as comment #2
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/comments/2
did the trick
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1859592
Title:
The regression was introduced by the following commit applied to
bionic:linux:
commit 699bf409d4d2895733d3e2f2eb01166d141650ce
Author: Jerome Marchand
Date: Fri Dec 10 10:38:27 2021 +0100
recordmcount.pl: look for jgnop instruction as well as bcrl on s390
BugLink:
20.04, 5.4.0-96-generic. The bug exists.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1814003
Title:
kernel BUG at fs/ext4/inode.c:2679!
Status in linux package in Ubuntu:
Seems the same as #1814003.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1959519
Title:
kernel BUG at fs/ext4/inode.c:2633!
Status in linux-signed-hwe-5.13 package in
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions
Tested the proposed focal kernel - looks good as well:
$ uname -r
5.4.0-98-generic
$ apt policy linux-image-5.4.0-98-generic
linux-image-5.4.0-98-generic:
Installed: 5.4.0-98.111
Candidate: 5.4.0-98.111
Version table:
*** 5.4.0-98.111 500
500
Hi All,
I confirm also in my case the bug is fixed with 5.13.0-28-generic.
Thank you all guys!
Marco
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1958289
Title:
[amdgpu]
Tried the proposed impish kernel - looks good:
$ uname -r
5.13.0-29-generic
$ apt policy linux-image-5.13.0-29-generic
linux-image-5.13.0-29-generic:
Installed: 5.13.0-29.32
Candidate: 5.13.0-29.32
Version table:
*** 5.13.0-29.32 500
500
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1958155
Title:
Pod traffic not taking advantage of
** Summary changed:
- Using Touchscreen creates soft lockup - Lenovo Yoga 9i
+ Using Touchscreen creates soft lockup - Lenovo Yoga 9i - KDE
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the linux-hwe-5.11/5.11.0-60.60
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
The linux-firmware package in jammy grew considerably and is now almost
1GB in size.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1958518
Title:
split some large, lesser-used
Juerg, thank you for picking this up and my apologies for the late
response.
You are of course right that there is no scientific answer or approach
to this question. I'd simply look at the biggest directories with ncdu
and make a decision if I thought that hardware was common when going
down the
** Attachment added: "complete-error-report-2 - Keyboard affected"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958295/+attachment/5558765/+files/complete-error-report-2
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification
** Description changed:
1)lsbrelease -rd:
- Description:Ubuntu 21.10
- Release:21.10
+ Description:Ubuntu 21.10
+ Release:21.10
2) i dont know if it is the kernel or an KDE problem, but i would guess the
kernel
3) Use the touchscreen without errors
4) The
*** This bug is a duplicate of bug 1956401 ***
https://bugs.launchpad.net/bugs/1956401
Re-added duplicate mark, as on 5.13.0-28(5.13.0.28.31~20.04.15) suspend
is working fine again.
** This bug has been marked a duplicate of bug 1956401
amdgpu hangs for 90 seconds at a time in 5.13.0-23,
Yup, can confirm this on my end as well for
5.13.0-28-generic(5.13.0.28.31~20.04.15) suspend is working fine again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956401
Title:
amdgpu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-450 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1957790
Title:
NVIDIA CVE-2022-{21813|21814}
Status in
Hi all - thanks for the quick testing. We are evaluating the best course
of action. In the short term that will likely be a respin with these
patches reverted. Longer term I will work to figure out the error and
find a correction.
rtg
--
You received this bug notification because you are a
JFYI, I've sent an SRU email to apply the kernel fix also to Impish
5.13, just to be safe in case the gcc patch lands in Impish:
https://lists.ubuntu.com/archives/kernel-team/2022-February/127652.html
** Also affects: zfs-linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also
I would reapply the gcc patch. It should not affect most userspace
binaries - for example, it did not produce any changes whatsoever in
SPEC suite. Even if there are some binaries that are built with kernel-
like options and get extra relocations as a result, ld.so processes such
relocations
@fheimes @iii-i
thank you for this, we will include that patch into our kernels. Do you
expect that the toolchain change may have affected any other binaries
(ie. userspace binaries)? Or should we re-apply the reverted patch back
in our gcc-11 (given the improvements that it brings)?
--
You
current version as of now is 5.14.0.1020.17, was there any activity
which could affect this issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1955591
Title:
gpu hang
This bug is awaiting verification that the linux/5.4.0-98.111 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 exists, change
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Jammy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Also affects: linux-azure-5.11 (Ubuntu)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390
** Changed in: linux-azure (Ubuntu Impish)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Impish)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-azure (Ubuntu Focal)
Op 02-02-2022 om 13:59 schreef Isaac True:
> This seems to be related to
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849
>
> The dmesg output is the same as mine when the host controller stops
> working:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/comments/13
>
** Changed in: linux-azure (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu Focal)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in
I have also fixed the part of the test-plan that Chris mentioned.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1957094
Title:
on-demand mode doesn't work with nvidia-390
I suppose I could simply detect the version in nvidia-settings. I
already have code that does that in a different patch that I wrote for
nvidia-settings.
** Description changed:
[Impact]
* In any Ubuntu series, if user using a old GPU (which supported by
nvidia-390 only) then issuing
This seems to be related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849
The dmesg output is the same as mine when the host controller stops
working:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/comments/13
Are you using the 5.13 HWE kernel?
--
You received this
Public bug reported:
[Impact]
Backported to bionic/linux commit f83baa0cb6cf ("HID: add hid_is_usb() function
to make it simpler for USB detection") brings to HID_ASUS usage of hid_is_usb()
which is provided by USB_HID. If HID_ASUS is built as module but USB_HID is
not, the kernel build will
** Description changed:
bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev
PPA and installed in pi-kernel snaps.
Some of the firmware files shipped in bluez-firmware are not present in
neither src:linux-firmware nor src:linux-firmware-raspi
It seems like it is
Public bug reported:
Using Dell D3100 docking station with dell xps13 with latest version of the
Displayport drivers.
After kernel installation on reboot external monitor not detected anymore
Last working kernel is 5.11
lsb_release -rd
Description:Linux Mint 20.3
Release:20.3
**
Public bug reported:
bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev
PPA and installed in pi-kernel snaps.
Some of the firmware files shipped in bluez-firmware are not present in
neither src:linux-firmware nor src:linux-firmware-raspi
It seems like it is an oversight, and
You have been subscribed to a public bug:
bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev
PPA and installed in pi-kernel snaps.
Some of the firmware files shipped in bluez-firmware are not present in
neither src:linux-firmware nor src:linux-firmware-raspi
It seems like it
** Package changed: ubuntu => linux-signed-hwe-5.13 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1959746
Title:
touchpad/keyboard actions not working
Status
You have been subscribed to a public bug:
Touchpad not working and not appearing inside xinput list and cat
/proc/bus/input/devices.
Battery percentage not appearing on the top bar.
Keyboard actions not working.
Computer : HP ENVY x360 Convert 15-eu0020nf.
ProblemType: Bug
DistroRelease:
Just a quick heads up on my tests with different kernel versions. I have
installed all available Updates for Ubuntu 20.04 (including samba-*=
2:4.13.17~dfsg-0ubuntu0.21.04.1; CVE-2022-0336). These are the results:
GA:
5.4.0-98.111~lp1959665.1 -> no freezes in 3 hours of testing
5.4.0-97.110 ->
This bug was fixed in the package linux-bluefield - 5.4.0-1026.29
---
linux-bluefield (5.4.0-1026.29) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1026.29 -proposed tracker (LP:
#1955220)
* [BlueField] Unable to set TCP MD5SIG option on socket (LP: #1956238)
-
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
*
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1029.36
---
linux-oem-5.13 (5.13.0-1029.36) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1029.36 -proposed tracker (LP:
#1955196)
* support signed v4l2loopback dkms build (LP: #1938531)
- support v4l2loopback
Public bug reported:
All ftrace tests from selftests are failing with bionic:linux
4.15.0-168.176 on s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-
bionic/bionic/s390x/l/linux/20220201_190955_5689e@/log.gz
==
I am also affected by this bug on my Lenovo laptop
I have an external monitor plugged in all the time, that means after the
display manager starts, the internal monitor is unusable (showing "snow"
and lines).
fixed this temporarily by booting 5.11 kernel instead of 5.13
*-display
Thanks for the response,
The G-SYNC mode does work for applications that utilise it, such as
games. It just drops sync like that. I've commented on this thread which
has since gone cold:
https://forums.developer.nvidia.com/t/nvidia-470-74-breaks-gsync-
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-5.13 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
** Summary changed:
- ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
+ ubuntu_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Thanks for the details and video.
I've only ever seen G-SYNC on a Windows machine, in which case the
display would blank whenever G-SYNC was enabled, just like you describe.
So if the same happens in both Windows and Linux then maybe it's not a
bug?...
If you didn't see the blanking in the past
** Tags added: impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1950720
Title:
GSYNC bug regression in 495.44 Ubuntu 21.10
Status in
Same thing for me: Dell XPS 13 with QCA6174 wlan card
It often crashes after the laptop suspend
No porblem if I manually switch off the wlan before suspending.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks a bunch. It also works on a ThinkPad E14 Gen 2 with Ryzen 7 4700u
and AMD Renoir.
When I started with the new kernel I first had graphics issues. No
animations, only internal monitor working, black screen after sleep.
That was caused by a missing graphics driver. Software Updater suggested
Thank you very much! Works for me on ThinkPad E15 Gen 2.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint
Hi,
thanks for the quick reply.
I can confirm, that while running on 5.4.0-98-generic #111~lp1959665.1 I
was able to access all of our cifs shares without issues.
A script, which creates, reads, modifies and deletes files on different
cifs shares also works without any issue.
Removing the
79 matches
Mail list logo
