ed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt
ure: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
+ /dev/snd/controlC1: matt 2754 F pulseaudio
+ /dev/snd/controlC0: matt 2754 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ Ecryptfs
t doesn't get flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt 275
t flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: ma
t flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd
t flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: ma
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt 275
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt 275
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt 275
t flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: ma
o a hard
reset to regain control of the system and the output doesn't get flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/
ed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt 275
** Attachment added: "Here's the 4.18.0-15 kernel log, showing a stuck thread"
https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1819918/+attachment/5246718/+files/kern.log-20190308
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
Ubuntu 18.04 w/ kernel 4.18.0-15 or 4.19.28 w/ nouveau driver on top of
Xen 4.11.1 regularly deadlocks system. It's reachable via network for a
bit, then becomes completely unresponsive.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kerneloops
I reported this incorrectly, since the actual traces aren't included.
Here's the kernel log.
** Attachment added: "kern.log-20190313"
https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1819918/+attachment/5245858/+files/kern.log-20190313
--
You received this bug notification because
reset to regain control of the system and the output doesn't get flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p:
This broke my ability to build the Xenial HWE kernel offline using the
default kernel configuration (trying to build binary-lowlatency
specifically). Building a package shouldn't require me to have an
internet connection.
I am also concerned about complying with the CDDL license since the ZFS
I tried both 5.2.11 and 5.3-rc6. Same result with both.
--
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/1839856
Title:
Screen resolution on external monitor won't go above 2560 x 1080
ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2519 F pulseaudio
/dev/snd/controlC0: matt 2519 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 7 11:54:57 2019
InstallationDate: Installed on 2019-09-04 (
I went back pretty far, into the 4.x versions, and still had the same
results, so I'm guessing this isn't kernel-related. Any suggestion on
what else to try?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
nelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2519 F pulseaudio
/dev/snd/controlC0: matt 2519 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date:
I've now been using an Xorg session rather than Wayland and haven't seen
the repeated keys issue. I do get some very nasty screen tearing when
scrolling (e.g. websites) on Xorg however, so ideally I'd like to
continue using Wayland.
Does that mean that this is likely a mutter bug, rather than
After some more research I found out that this is actually due to an
unimpelmented feature in Nvidia's drivers.
On this model of laptop, the video output ports all connect directly to
the discrete Nvidia GPU, and Nvidia's drivers do not yet support the GPU
being used as a sink from the integrated
I believe this bug affected my Dell XPS 13" 7390 (2-in-1). I also
verified this by updating to use the bionic-proposed linux-firmware
package and bluetooth now works! thank you all so much!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
untu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: matt 2211 F pulseaudio
/dev/snd/controlC1: matt
ia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: matt 2211 F pulseaudio
/dev/snd/controlC1: matt 2211 F pulseaudio
/dev/snd/controlC0: matt 2211 F
I had this problem occur recently and was able to work with one of my
System Administrators to narrow it down. I saw the floppy text in the
output so I asked my Sys Admin to connect the Floppy Drive in VCenter to
the VMs that were having this issue (3 new 18.04 installs) and the issue
is now
Public bug reported:
In a recent driver, Nvidia finally added Linux support for render
offload, where most graphics are rendered on the CPU-onboard GPU and
only certain applications are rendered on the discrete Nvidia GPU. I
know that Ubuntu 19.10 started shipping some updated Xorg packages to
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1849214/+attachment/5299051/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in
apport information
** Tags added: apport-collected
** Description changed:
In a recent driver, Nvidia finally added Linux support for render
offload, where most graphics are rendered on the CPU-onboard GPU and
only certain applications are rendered on the discrete Nvidia GPU. I
know
Public bug reported:
I have a Microsoft Surface bluetooth keyboard, and semi-frequently (e.g.
around every 10-15mins) end up with repeated keypresses being made (e.g.
apppt get update).
This seems to happen when the machine is under slight stress, or when a
new notification pops up in
** Also affects: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu.
https://bugs.launchpad.net/bugs/1849214
Title:
"nvidia
ure: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: matt 2211 F pulseaudio
/dev/snd/controlC1: matt 2211 F pulseaudio
/dev/snd/controlC0: matt 2211 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 18 13:44:33 2019
Instal
: Ubuntu 5.0.0-27.28-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2519 F pulseaudio
/dev/
ortVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gdm7450 F pulseaudio
matt 8011 F pulseaudio
/dev/snd/controlC0: gdm7450 F pulseaudio
matt
Public bug reported:
The target subsystem (LIO) can hang if multiple threads try to destroy
iSCSI sessions simultaneously. This is reproducible on systems that have
multiple targets with initiators regularly connecting/disconnecting.
This may happen when a "targetcli iscsi/iqn.../tpg1 disable"
** Attachment added: "output of `lspci -vvnn`"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871688/+attachment/5349846/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "contents of /proc/version_signature"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871688/+attachment/5349844/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "dmesg output shortly after booting"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871688/+attachment/5349845/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: bionic focal
** Description changed:
The target subsystem (LIO) can hang if multiple threads try to destroy
iSCSI sessions simultaneously. This is reproducible on systems that have
multiple targets with initiators regularly connecting/disconnecting.
This may happen when
The only machines I've reproduced this bug on are running Xenial. For
the past few months, I've been applying these patches to the Xenial HWE
kernels and building packages for my dev/test systems.
These systems frequently add and remove targets (around 125 per hour)
with separate initiators
I built and installed the package on one of my Xenial systems from the
source available here:
https://launchpad.net/ubuntu/+source/linux/4.15.0-100.101
If the system is still stable a day from now, is it okay for me to set
the 'verification-done-bionic' tag, even though I'm testing on Xenial?
--
The Xenial system that I installed the binary packages from the proposed
Bionic repository on has been running properly and stable since the 7th.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
My Xenial system is still stable after almost two days with the kernel
package I built from the proposed Bionic kernel's source.
--
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/1871688
I installed the proposed Bionic packages on my Xenial system and have
confirmed that basic functionality is working properly. If the system
remains stable for >24h, I will consider the issue to be fixed in this
kernel.
--
You received this bug notification because you are a member of Kernel
I think I see the same bug on Dell Inc. Latitude 7390 2-in-1/0YNG30,
BIOS 1.10.0 07/04/2019
Distributor ID: Pop
Description:Pop!_OS 20.04 LTS
Release:20.04
Codename: focal
Observed on the latest four kernel versions:
vmlinuz-5.4.0-7618-generic
vmlinuz-5.4.0-7629-generic
me: Linux 5.3.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: matt 2211 F pulseaudio
/dev/snd/controlC1: matt 2211 F pulseaudio
/dev/
Thank you for fixing this bug. Installing mutter 3.36.4-0ubuntu0.20.04.1
and libmutter 3.36.4-0ubuntu0.20.04.1 from focal-proposed has resolved
this issue for me.
Note: The updated libmutter from focal-proposed also had to be
explicitly installed by me, as it was not automatically pulled in when
I can pair successfully if I enable LE Privacy:
sudo btmgmt power off
sudo btmgmt privacy on
sudo btmgmt power on
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638
Title:
Xbox
Public bug reported:
I believe we maybe missing the 386 library:
E: Package 'libnvidia-gl-465:i386' has no installation candidate
Steam app will not launch without it on Pop OS
** Affects: nvidia-graphics-drivers-455 (Ubuntu)
Importance: Undecided
Status: New
--
You received
I should also note that after this happens, attempting to "rmmod
ath11k_pci" results in a wait of several minutes before then getting a
segmentation fault error.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
Adding log snippet form kernel.log - where the following is repeated:
Sep 18 11:46:57 perseverance kernel: [314619.796128] ath11k_pci :72:00.0:
wmi command 16387 timeout
Sep 18 11:46:57 perseverance kernel: [314619.796134] ath11k_pci :72:00.0:
failed to send WMI_PDEV_SET_PARAM cmd
Sep
Public bug reported:
Sometimes when my Dell XPS 13 9310 resumes from suspend, the display
fails to show anything for a short while. When the display does show,
the wireless network is no longer working.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-modules-5.10.0-1045-oem
Public bug reported:
Trying to install a package using Ubuntu Software catalogue, and the
installation was interrupted by a message saying that "E: dpkg was
interrupted, you must manually run 'dpkg --configure -a' to correct the
problem." I tried to run this command in Terminal, but it wouldn't
Public bug reported:
I have been using linux-oem-20.04c with my XPS 9310 with no problems,
but the recent update to 5.13.0-1019-oem caused my wifi to become
inoperative (ath11k_pci, 72:00.0 Network controller: Qualcomm Device
1101 (rev 01)). Choosing 5.13.0-1017-oem from the grub menu is my
The issue is happening even after I would have a fresh install of the
operating system.
--
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/1791908
Title:
uvcvideo: Failed to query
I'm running Ubuntu Budgie 21.10 & I'm having the same issue with my
computer always having same error in the log that is causing me to have
to restart my computer every time, I was seeing that there was mention
about the webcam, does that seem to be the issue most of the time with
this bug?
--
It does seem to be at least when I just brought my computer out of sleep
that the issue somehow is from a conflict with Linux & a webcam being
plugged in, because when I saw last night that there seemed to be a link
to the webcam, I unplugged my webcam from my computer & it was not
frozen like it
It appears installing linux-oem-20.04c resolves this issue for me (it
installs kernel 5.13).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1944018
Title:
ath11k_pci sometimes
I can confirm the same behavior (unable to select on the same headphones
(Sony WH-1000XM5). When I look at the device in the "pacmd list-cards"
output I see:
profiles:
a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40,
available: yes)
need a kvm/virtual/minimal image(s) that includes this from 20.04 and up
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1950878
Title:
Enable ptp_kvm module for time
0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: matt 1793 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Sep 29 23:41:46 2023
InstallationD
d64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: matt 1793 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Sep 29 23:41:46 2023
InstallationDate: Installed on 2023-09-26 (4 days ago)
InstallationMe
ion: 2.27.0-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: matt 1793 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Sep 29 23:41:46 2023
InstallationDate: Installed on 2
Public bug reported:
[Impact]
20230323.gitbcdcfbcf-0ubuntu1.7 borks amdgpu during boot, it completely
hangs the entire kernel on a RX 7900 XTX. Reverting back to
20230323.gitbcdcfbcf-0ubuntu1.2 made the kernel boot properly again.
[Fix]
Revert AMD firmware updates.
[Test Case]
Boot a
I am impacted by this bug as well, as reported in my Tomcat 9-based
application logs:
[2022-04-18 21:45:44.764] ERROR [http-nio-9083-Acceptor ]
org.apache.tomcat.util.net.Acceptor Socket accept failed
java.io.IOException: Duplicate accept detected. This is a known OS bug.
Please
Public bug reported:
Some newer Dell systems (I experienced this on an Optiplex 7000) include
an Intel I219-LM NIC that is not supported by the 5.4.0 kernel. Later
versions of the HWE kernel do support this NIC.
That makes it impossible to use these systems with the FIPS kernel.
Since our
Public bug reported:
d
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-kernel-source-525-open 525.60.11-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
Uname: Linux 5.15.0-57-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
It still doesn't work on 5.19.0-40-generic. If i revert back to
5.19.0-32 the sound works but the nvidia graphics driver stops working.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
Kernel panic occurs at initial boot before terminal window is available
to enter command.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Do we have any updates when we will see this released for Ubuntu 22.04?
We are seeing an increase in inquires.
--
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/2049220
Title:
Okay Bug Bot, updated.
** Also affects: linux-meta-oem-6.5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2051612
Title:
For the Framework 13 (using MT7921 WiFi), we'd like to see this to be
with linux-oem-6.1 (Ubuntu) and/or linux-oem-6.5 (Ubuntu) as this is our
official path for 22.04.3 LTS.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware
Appreciate the update, Leszek. Glad to hear linux-
firmware_20220329.git681281e4-0ubuntu3.29 has this sorted for you.
--
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/2049220
I too am suffering with a Samsung R40 that usually fails to recover from
suspend, even now in Ubuntu 14.04 LTS. Has anybody managed to figure out
why this happens, and what can be done about it? I've submitted about a
dozen crash reports, but I've no idea who's taking any notice. Ok, it's
an
@mlx I'm running eth0 in bridge, and also using a tunnel broker ipv6
tunnel like the original poster. How would I go about running the
testing kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
I can confirm having the same issue, including on multiple raspberry pi
3s, one with an IPv6 tunnel from tunnelbroker.net, and one without. It
can be triggered by a lot of IPv4 traffic for me as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is
301 - 379 of 379 matches
Mail list logo