apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1430055/+attachment/4340437/+files/Lspci.txt
--
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/1430055
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1430055/+attachment/4340442/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1430055/+attachment/4340446/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
On Tue, Mar 10, 2015 at 2:14 PM, Fred Warren wrote:
> apport information
>
> ** Tags added: apport-collected trusty
>
> ** Description changed:
>
> Dell ACS11 USB Soundbar with USB ID 413C:A503 works fine in linux kernel
> 3.13-0-45-generic and earlier kernel releases.
which was not available. After deleting "snd-usb-audio
index=0" everything is working fine.
On Tue, Mar 10, 2015 at 2:31 PM, Fred Warren
wrote:
> Hi,
>
> I loaded the 4.0.0-04rc3-generic amd64 kernel and then ran
> apport-collect 1430055. No audio via the soundbar
>
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Just wanted to add that upgrading my kernel to a newer version fixed the
problem for me, too.
Host: 2x E5-2620V2, Ubuntu 14.04 LTS
Guest: 24 virtual cores, Windows Server 2008 R2
Before fix:
sudo uname -a
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same here, had issues with 3.13.0-44-generic, upgraded to
3.16.0-23-generic and the problem was solved. Followed this tutorial
http://askubuntu.com/questions/541775/how-can-i-install-ubuntu-14-10s-
kernel-in
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same bluescreen again on day 9 after the kernel upgrade.
So upgrading Kernel from 3.13 to 3.16 did not help.
Still looking for a fix.
--
You received this bug notification because you are a member of Ke
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same bluescreen STOP: 0x005c again on day 9. So it has not been
fixed by a kernel upgrade to 3.16.0-23-generic with above method from
askubuntu.com.
--
You received this bug notification because you ar
Public bug reported:
I've recently started using 16.04 on a Dell XPS 15 9550 and I'm unable
to pair my Bose Soundlink II headphones. I've tried using the stock and
blueman bluetooth managers and neither will work.
When I use bluetoothctl and run "pair [Device ID]" I get the following
error:
Fai
** Summary changed:
- Can't connect Bose Soundlink II Headphones to Ubuntu
+ Can't connect/pair Bose Soundlink II Headphones to Ubuntu 16.04
--
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/
*** This bug is a duplicate of bug 1589889 ***
https://bugs.launchpad.net/bugs/1589889
I have followed the fix suggestion in bug #1589889. This has resulted in
some progress in that I can now connect to the headphones, and once the
headphones did register the laptop. But they disconnected stra
** This bug is no longer a duplicate of bug 1589889
Bluetooth search gets nothing on Dell XPS 15 9550
--
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/1590798
Title:
Can't connect/pair
Attached dmesg with complete kernel errors with stack traces
** Attachment added: "kernel dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631719/+attachment/4757952/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Attach Xorg.log for completeness although this does not show any
problems
** Attachment added: "Xorg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631719/+attachment/4757953/+files/Xorg.0.log
--
You received this bug notification because you are a member of Kernel
Packages, whic
Public bug reported:
Upgrades to Yakkety in feature freeze with kernel 4.8.0-21-generic.
System regularly hangs for 10 second intervals which is very noticeable in boot
process. Cause seems to be the Intel GMA965 DRM support causing regular kernel
warnings:
WARNING: CPU: 0 PID: 1183 at
/build
As the problem report shows the system was upgraded, over many releases
originally from Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
The lastest 16.04 kernel did not have the problem. I guess that gives us two
bisection points.
--
You received this bug notification because you are a memb
Tried to install Ubuntu Gnome 16.04.1 with NVIDIA Driver 367.xx using
the GDM display manager yesterday and resulted in black screen at login.
Did the same today with the newly released NVIDIA Driver 370.23 (beta, I
think) and everything is actually working fine - no black screens, but
the login s
I think the non-existant firmware is not relevant for the older Intel
Chips such as GMA965. This firmware is only for the latest chips.
--
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/163171
One interesting data point is that if you go into the bluetooth menu
during the call and disconnect the device then the audio is correctly
routed. I suspect the fundamental problem is the same for blue headset
and speaker no be automatically routed when autoconnected.
--
You received this bug not
** Changed in: linux (Ubuntu)
Status: Expired => New
--
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/1172065
Title:
12.04.2 incorrect file name signed efi amd6.deb
Status in “linu
In my case, this installation failed due to lack of space on the /boot
partition
apt-get -f install failed:
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.8.0-30-generic
/boot/vmlinuz-3.8.0-30-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.8.0-30-generic
/boot/vmlinu
Orginal error was in ISO itself.
Above error seems to be just when written with certain tools that file
name is too long to be converted from ISO correctly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=f25cda9a-ab3e-4
PID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=f25cda9a-ab3e-4873-9752-74587b66e784
InstallationDate: Installed on 2010-05-26 (1245 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid
It now looks like in 12.04.3 that both 6 and 4 are missing from end of file
name. The change from 3.9 to 3.10 added a character, so one more was dropped
from end of file.
Seems like an issue with file name length on ISO.
Original file on server is probably correct.
--
You received this bug no
This user found more issues and created a perl script to rename files
correctly.
http://cirrus.ucsd.edu/~pierce/fix_ubuntu_usb/
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
Public bug reported:
Using 13.10 on my laptop (Asus EeePC 1005HA), the system goes into
suspend mode when I close the lid. When opening the lid and pressing a
key, the system wakes up and asks me for my password. This is the
expected behavior.
However, if the laptop is running on battery, the sys
Upon further testing, I can add the following details the this 'suspend
loop' issue.
- It does not matter if the laptop was running on battery or on power when put
into suspend mode for this suspend loop to happen.
- When is 'suspend loop', the network is deactivated (only lo is shown from
ifcon
ected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
is acting as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/contro
ected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
acting as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
+ ---
+ ApportVersion: 2.12.5-0ubuntu2
+ Architecture: i386
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: fred 3205 F pulseaudio
+ DistroRelease: Ubuntu
acting as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
ected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
acting as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
acting as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
acting as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
s expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
acting as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
acting as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
PSU, it is acting as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/contro
s expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
s expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
uch problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RES
Package: linux-image-3.19.0-29-generic 3.19.0-29.31
ProcVersionSignature: Ubuntu 3.19.0-29.31-generic 3.19.8-ckt6
Uname: Linux 3.19.0-29-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
linux-image-3.19.0-29-generic. If the problem can
> be reproduced, please include instructions to do so.
>
> This appears to be a weird interaction between Chrome and Telepathy
> that might itself warrant investigation, but the primary issue is that
> there is a
Problem lies in the Intel kernel driver 'snd_soc_avs' which is becoming
active but fail to support the HDA sound hardware correctly.
Workaround is to blacklist 'snd_soc_avs'.
Problem is well know and seems to be already in Kernel 6.7. See for
example https://bbs.archlinux.org/viewtopic.php?id=294
alsa-info from a Dell Precision 5520
** Attachment added: "alsa-info.txt.1IMNEYShPL"
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2063150/+attachment/5770168/+files/alsa-info.txt.1IMNEYShPL
--
You received this bug notification because you are a member of Kernel
Packages, which is
Bug occurs with released 24.04 where the kernel is 6.8.0-31-generic
Strangely the live version of 24.04 booted on same machine form the
released desktop ISO image does NOT have the problem with the same
kernel version.
The Precision 5520 had hybrid graphics with both integrated Intel (HD
P630) an
Strangely changing the installed system to use the 'nouveau' Nvidia
driver does NOT fix the problem.
If it help I can try a fresh 24.04 install without initially installing
the propitiatory Nvidia driver.
--
You received this bug notification because you are a member of Kernel
Packages, which is
I think this bug also affects Intel GPUs. I did an installation today that
resulted in a black screen without "nomodeset". See:
https://bugs.launchpad.net/ubuntu/+bug/2063877
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
... oh yes, I had the same problem with AMD Radeon Integrated Graphics; see the
same bug report:
https://bugs.launchpad.net/ubuntu/+bug/2063877
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
I followed this advice (mentioned above):
https://www.reddit.com/r/Kubuntu/comments/1cdko49/comment/l1uf573/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
It seems that "quiet splash" is the actual problem, not "nomodeset"
(solution).
I edited the GRUB en
If you tell me how to "gather the full kernel log from when the system
booted to black screen", I might try that.
--
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/2063983
Title:
24.04 Upgr
I have confirmed that our internal test team have completed 28 testcases
and not find any bug. now also are adding some testcase to test this
Roce module.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
Public bug reported:
I added the same mounting commands in fstab as I used for Kernel v5.15.0.52.
However the mounting will not complete. I can't get to the login window (it
hangs on the Linux-Mint-Logo..
nfs-common is installed on the system.
I used the syntax:
:/ nfs _netdev defaults 0 0
Tha
+ ApportVersion: 2.20.11-0ubuntu82.2
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC2: fred 1669 F pulseaudio
+ /dev/snd/controlC1: fred 1669 F pulseaudio
+ /dev/snd/controlC0: fred 1669 F pulseaudio
sion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
C
2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
Dis
ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X
2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
Dis
2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
Dis
2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
Dis
2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
Dis
2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
Dis
ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnam
sion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X
ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnam
2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
sion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
C
2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
Dis
2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnam
ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnam
2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: fred 1669 F pulseaudio
/dev/snd/controlC1: fred 1669 F pulseaudio
/dev/snd/controlC0: fred 1669 F pulseaudio
CasperMD5json: {
CurrentDesktop:
ax:
:/ nfs _netdev defaults 0 0
Thanks
PS. I report this under Kernel v 5.15.0.52 since I can't login into v
5.15.0.53
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/con
https://lists.cs.columbia.edu/pipermail/kvmarm/2020-September/042543.html
this patch will slove this bug。 Can you test it？
** Changed in: linux (Ubuntu)
Status: Expired => New
** Also affects: kunpeng920
Importance: Undecided
Status: New
--
You received this bug notification b
Public bug reported:
merci!
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-63-generic 3.13.0-63.103
ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
Uname: Linux 3.13.0-63-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.13
Architecture: amd64
AudioDevic
101 - 180 of 180 matches
Mail list logo
