[Touch-packages] [Bug 1859810] Re: [Inspiron 3268] audio esta mudo
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1859810 Title: [Inspiron 3268] audio esta mudo Status in pulseaudio package in Ubuntu: Expired Bug description: o audio esta mudo ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jan 15 08:28:41 2020 DistUpgraded: 2020-01-14 10:48:30,743 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho “./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0764] InstallationDate: Installed on 2020-01-11 (4 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 3268 ProcEnviron: LANGUAGE=pt_BR: PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=fd473502-2a31-400b-b303-9f46a74c2132 ro locale=pt_BR quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2020-01-14 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 07F37C dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd01/25/2018:svnDellInc.:pnInspiron3268:pvr:rvnDellInc.:rn07F37C:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3268 dmi.product.sku: 0764 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Jan 13 20:38:33 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8758 vendor AOC xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1859810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled. Status in Ubuntu MATE: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mate-session-manager package in Ubuntu: Confirmed Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1706770/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker
Thanks a lot for the input, Ken! You were right, it is not related to BT, but to the sound devices being added and removed. I happend to have a Zoom microphone that can be connected as USB and creates a new audio interface (both input and output). Here are my new tests and findings: 1. Plug the Zoom USB device -> it appears in the Sound Settings Output Device and is automatically selected 2. Press Test and check the sound output -> the sound outputs on the internal speakers (NOK) After some investigation using pactl, I found how to fix the issue, for both the USB audio interface and the Bluetooth speaker: 1. Make sure the audio interface you want is connected (in my case, I connected both the USB and the Bluetooth speaker): $ pactl list short sinks 1 alsa_output.pci-_00_1f.3.analog-stereo module-alsa-card.c s16le 2ch 48000Hz SUSPENDED 6 alsa_output.usb-ZOOM_Corporation_H2n_-00.iec958-stereo module-alsa-card.c s16le 2ch 44100Hz SUSPENDED 7 bluez_sink.88_C6_26_1A_9E_AF.a2dp_sink module-bluez5-device.c s16le 2ch 44100Hz SUSPENDED 2. Play an audio stream, for instance a Youtube video. The output should come from the internal speakers, and can be seen in pactl as well: $ pactl list short sink-inputs 10 1 16 protocol-native.c float32le 2ch 44100Hz 3. Ask pactl to move the stream to the desired sink (output); for instance, the Bluetooth speaker: $ pactl move-sink-input 10 7 -> The sound outputs to the Bluetooth device! \o/ However, going back to Sound Settings (where the "Output Device" shows my Bluetooth Speaker) and clicking Test still outputs to the internal speakers Do you think it could be a GNOME issue? What should I do next? ** Summary changed: - After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker + After connecting an external output device (USB audio interface, Bluetooth speaker...), it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker ** Tags removed: a2dp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: After connecting an external output device (USB audio interface, Bluetooth speaker...), it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Device CID: 201704-25503 Steps to reproduce: 1. Go to Bluetooth settings panel 2. Pair a BT device 3. Make sure it's marked as Connected, and go to the Sound settings 4. Make sure it's the one selected as "Output device" 5. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 6. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 7. Try to switch back to the BT device and click Test -> same result as in step 5 Tested with 2 different BT devices (one headset and one speaker) Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.
** Changed in: ubuntu-mate Status: New => Confirmed ** Information type changed from Public Security to Private Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled. Status in Ubuntu MATE: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mate-session-manager package in Ubuntu: Confirmed Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1706770/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=9cb7406d543b8db15e455903566fb72a23235c75 https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=6e93cf440908a87a1e30aec76bd54d52e0ad136c https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=2f2ea9613515dc90b75d32f6955dbf9d18876fde -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
Some recent commits in BlueZ 5.54 suggest wide band support is being prepared starting in kernel 5.6: https://git.kernel.org/pub/scm/bluetooth/bluez.git Unfortunately both that kernel and bluez version seem to be too new to realistically make it into Ubuntu 20.04. ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Hi @hui.wang, ok thanks, is there an ETA for -43 to be released ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
** Summary changed: - PCI/internal sound card not detected + [Dell Vostro 5590] PCI/internal sound card not detected -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867479] Re: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake
*** This bug is a duplicate of bug 1860697 *** https://bugs.launchpad.net/bugs/1860697 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1860697, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug is no longer a duplicate of bug 1867474 [Dell Vostro 5590] PCI/internal sound card not detected ** This bug has been marked a duplicate of bug 1860697 Sound doesn't work on Lenovo X1 Carbon 7th with 20.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1867479 Title: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake Status in alsa-driver package in Ubuntu: Confirmed Bug description: It looks like 20.04 is now using sound open firmware (sof), however, sof does not have a driver(?) for Intel Comet Lake processors (which my Lenovo X1 Carbon Gen 7 laptop has). Here is the relevant output of dmesg: [3.272336] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.272343] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.272485] sof-audio-pci :00:1f.3: use msi interrupt mode [3.323370] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.355159] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.355161] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.377802] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.377805] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.377808] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.377809] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 18:22:42 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET21W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET21W(1.15):bd02/25/2020:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797734] Re: slow calculator startup
That's a good case for keeping this bug logged here under gnome- calculator. Maybe we should just drop the snap and default to the deb. I'll assign this bug to ubuntu-meta for that... Although to say something is not physically possible is just inviting people to prove that statement wrong. It is technically true, but misses the main goal of just being fast enough that people don't notice. That is technically possible still. ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup Status in gnome-calculator package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: New Bug description: The calculator starts very slowly. It's a tiny program, but it runs like a very big one. In previous versions of Ubuntu, the launch was normal, very fast. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 08:40:06 2018 InstallationDate: Installed on 2018-05-06 (160 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@Paolo, Please wait for -43 kernel. (41 and 42) has some regression. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Hi everyone again, i am experiencing some APCI issues using 5.3.0-40 with sof drivers activated. It happens, almost randomly at this stage that the system is not waking up after a sleep, initiated by Gnome, what i see is just the fn led active on the X1-carbon-7h. It seems that disabling sof and loading the standard kernel modules (the blacklisted ones) the problem disappear. I saw that in 41 and 42 there are some ACPI-related fixes, but suddenly they broke the mic. Is this something tracked somewhere ? Is there something should i check to debug this error ? Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
I have Asus ROG GX501VIK laptop with same issue. Device: Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) card 0: PCH [HDA Intel PCH], device 0: ALC295 Analog [ALC295 Analog] Solution from comment #8 worked like a charm. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256 speakers work, it's just the mic not working. sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200 sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0 8 lines make mic working until reboot. thx a lot for ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Sun Jun 26 23:56:46 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 2 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
*** This bug is a duplicate of bug 1861395 ***
https://bugs.launchpad.net/bugs/1861395
Duplicate of LP:1861395
Per LP:1861395 both 5.4.0-17 (from the Kernel Team's Unstable PPA) and
5.4.0-18 (from -proposed) seems to fixes it for me.
** This bug has been marked a duplicate of bug 1861395
system hang: i915 Resetting rcs0 for hang on rcs0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for
[Touch-packages] [Bug 1609750] Re: Audio not working on Acer Chromebook R11
I can get sound to work with a 5.4 kernel - but it's still not great... I haven't found a UCM file that let's it just work yet. What does work is using the alsactl -f downloaded/asound.state.txt bit and then VLC is able to play sound with Audio device set to chtmax98090, Direct hardware device without any conversions. My most recent attempt had me force installing (to ignore other depends) the Gallium deb http://apt.galliumos.org/pool/main/g/galliumos-baytrail/galliumos-baytrail_3.0_all.deb (this still lets the above alsa restore, vlc bit work, but pulseaudio fails to load) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1609750 Title: Audio not working on Acer Chromebook R11 Status in linux: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Bug description: Audio is not working at all on Acer Chromebook R11 (codename CYAN). It's a Intel Braswell platform. snd_hda_intel messages seem normal, but Pulseaudio does not detect sound hardware. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-1.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Aug 4 14:12:03 2016 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE --- ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux-image-4.4.0-33-generic 4.4.0-33.52 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-33-generic N/A linux-backports-modules-4.4.0-33-generic N/A linux-firmware1.159 Tags: yakkety Uname: Linux 4.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering
*** This bug is a duplicate of bug 1847524 *** https://bugs.launchpad.net/bugs/1847524 I tried the workaround, and that did help, but only once. After that, the flickering returned even after uninstalling and reinstalling the Tweaks app. Rebooting after uninstalling and before reinstalling also did not help. Workaround: I discovered that widening the app window by dragging on the right side stopped the Flickering. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering Status in gnome-tweaks package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: wayland-session eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867535] [NEW] [FFe] LXC 4.0.0 LTS
Public bug reported: LXC 4.0 LTS will be tagged in the next week or so. LXC in Ubuntu is currently in universe as its main user is a snap nowadays (LXD) and builds directly from the upstream versions. We haven't written the changelog yet, but one thing worth noting is that it is 100% backward compatible, we do not break API and don't need to rebuild any of the rdepend for it. The main reason to want it in 20.04 LTS is because LXC 4.0 is itself an LTS with a matching 5 years of support. It also adds support for cgroupv2 which we expect to become more and more needed in the coming months/years. It'd be great if the release team could make a decision based on this already, if not, I will update the bug with the changelog and diff once we do have the release out. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1867535 Title: [FFe] LXC 4.0.0 LTS Status in lxc package in Ubuntu: New Bug description: LXC 4.0 LTS will be tagged in the next week or so. LXC in Ubuntu is currently in universe as its main user is a snap nowadays (LXD) and builds directly from the upstream versions. We haven't written the changelog yet, but one thing worth noting is that it is 100% backward compatible, we do not break API and don't need to rebuild any of the rdepend for it. The main reason to want it in 20.04 LTS is because LXC 4.0 is itself an LTS with a matching 5 years of support. It also adds support for cgroupv2 which we expect to become more and more needed in the coming months/years. It'd be great if the release team could make a decision based on this already, if not, I will update the bug with the changelog and diff once we do have the release out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1867535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867537] [NEW] 10-link-restrictions.conf missing - removed by postinst
Public bug reported: The file "10-link-restrictions.conf" is listed in DEBIAN/conffiles in the binary deb package, and the file is present/installed, but it is removed by the "postinst" script resulting in "debsums" flagging it as a missing config file: root@beluga:~# lsb_release -d Description:Ubuntu Focal Fossa (development branch) root@beluga:~# apt policy procps procps: Installed: 2:3.3.16-1ubuntu2 Candidate: 2:3.3.16-1ubuntu2 Version table: *** 2:3.3.16-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@beluga:~# debsums -ac procps debsums: missing file /etc/sysctl.d/10-link-restrictions.conf (from procps package) This is not an issue in 18.04: manager@brigante:~$ lsb_release -d Description:Ubuntu 18.04.4 LTS manager@brigante:~$ apt policy procps procps: Installed: 2:3.3.12-3ubuntu1.2 Candidate: 2:3.3.12-3ubuntu1.2 Version table: *** 2:3.3.12-3ubuntu1.2 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:3.3.12-3ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2:3.3.12-3ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages manager@brigante:~$ debsums -ac procps ** Affects: procps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1867537 Title: 10-link-restrictions.conf missing - removed by postinst Status in procps package in Ubuntu: New Bug description: The file "10-link-restrictions.conf" is listed in DEBIAN/conffiles in the binary deb package, and the file is present/installed, but it is removed by the "postinst" script resulting in "debsums" flagging it as a missing config file: root@beluga:~# lsb_release -d Description: Ubuntu Focal Fossa (development branch) root@beluga:~# apt policy procps procps: Installed: 2:3.3.16-1ubuntu2 Candidate: 2:3.3.16-1ubuntu2 Version table: *** 2:3.3.16-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@beluga:~# debsums -ac procps debsums: missing file /etc/sysctl.d/10-link-restrictions.conf (from procps package) This is not an issue in 18.04: manager@brigante:~$ lsb_release -d Description: Ubuntu 18.04.4 LTS manager@brigante:~$ apt policy procps procps: Installed: 2:3.3.12-3ubuntu1.2 Candidate: 2:3.3.12-3ubuntu1.2 Version table: *** 2:3.3.12-3ubuntu1.2 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:3.3.12-3ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2:3.3.12-3ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages manager@brigante:~$ debsums -ac procps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1867537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867521] Re: package unattended-upgrades 2.0 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 128
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1867521 Title: package unattended-upgrades 2.0 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 Status in unattended-upgrades package in Ubuntu: New Bug description: The installation process was stuck, and it never finished, so after forcing a restart and login back in, the error was presented and it allow me to send it to you guys, so that it is fixed. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: unattended-upgrades 2.0 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Sun Mar 15 11:45:51 2020 ErrorMessage: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-02-18 (25 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 2.0.0 SourcePackage: unattended-upgrades Title: package unattended-upgrades 2.0 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2020-03-03T15:51:02.219809 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1867521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867521] [NEW] package unattended-upgrades 2.0 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 128
Public bug reported: The installation process was stuck, and it never finished, so after forcing a restart and login back in, the error was presented and it allow me to send it to you guys, so that it is fixed. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: unattended-upgrades 2.0 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Sun Mar 15 11:45:51 2020 ErrorMessage: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-02-18 (25 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 2.0.0 SourcePackage: unattended-upgrades Title: package unattended-upgrades 2.0 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2020-03-03T15:51:02.219809 ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1867521 Title: package unattended-upgrades 2.0 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 Status in unattended-upgrades package in Ubuntu: New Bug description: The installation process was stuck, and it never finished, so after forcing a restart and login back in, the error was presented and it allow me to send it to you guys, so that it is fixed. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: unattended-upgrades 2.0 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Sun Mar 15 11:45:51 2020 ErrorMessage: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-02-18 (25 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 2.0.0 SourcePackage: unattended-upgrades Title: package unattended-upgrades 2.0 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2020-03-03T15:51:02.219809 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1867521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Has anyone found a solution to this problem? I have it too, my computer is an HP Envy x360 Convertible. Any help would be greatly appreciated! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 518966] Re: Wrong pitch and crackling sound with 5.1 output on Extigy USB card
I can confirm that there seems to be a regression in the alsa audio
driver. I was trying this soundcard directly with alsa and get
distoreted audio and rumble in *some* apps.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/518966
Title:
Wrong pitch and crackling sound with 5.1 output on Extigy USB card
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
Binary package hint: pulseaudio
Since i upgraded to Karmic, my 5.1 sound output on my creative labs extigy
USB card is broken.
The previous release did work with alsa, and was working fine.
Now with Pulseaudio, the sound is only working correctly with stereo output,
with 5.1, the sound is crackling, and the pitch is too high.
ProblemType: Bug
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Extigy [Sound Blaster Extigy], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jean-luc 2681 F pulseaudio
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA ATI HDMI at 0xfe9fc000 irq 29'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100100'
Controls : 4
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Extigy'/'Creative Technology Ltd. Sound Blaster Extigy at
usb-:00:1a.0-2, full speed'
Mixer name : 'USB Mixer'
Components : 'USB041e:3000'
Controls : 23
Simple ctrls : 17
Date: Mon Feb 8 19:48:40 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: fglrx
Package: alsa-base 1.0.20+dfsg-1ubuntu5
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: alsa-driver
Uname: Linux 2.6.31-19-generic x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/518966/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867474] Re: PCI/internal sound card not detected
Ok, I will check this once more in a few days. Thanks for your support. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1867474 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841783] Re: Update to 1.2.0?
** Description changed: - The source was split in rc2, Debian didn't follow the change and we are + The source was split in rc2, Debian didn't follow the change, and we are in sync, do we want to update? + + Speex and SpeexDSP + + https://git.xiph.org/?p=speex.git;a=summary + + https://git.xiph.org/?p=speexdsp.git;a=summary -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to speex in Ubuntu. https://bugs.launchpad.net/bugs/1841783 Title: Update to 1.2.0? Status in speex package in Ubuntu: Triaged Status in speex package in Debian: New Bug description: The source was split in rc2, Debian didn't follow the change, and we are in sync, do we want to update? Speex and SpeexDSP https://git.xiph.org/?p=speex.git;a=summary https://git.xiph.org/?p=speexdsp.git;a=summary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speex/+bug/1841783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867474] Re: PCI/internal sound card not detected
The sof-firmware was just merged to linux-firmware last week, maybe it needs to wait for a couple of more days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1867474 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862797] Re: Systemd does not allow hibernation when Chrome/chromium is running
Hello Dan, Thanks for following up! To be 100% sure (and not wasting developer cycles), I reinstalled my system with Linux Mint 19.1. I had modified (too) many files trying to solve the problem, so better start clean. The problem was 100% reproducible as per my previous messages. Then I upgraded to version of 19.3 + kernel 5.3.40 and with the upgrade came newer versions of Chromium/systemd as indicated. For the last three days I tried desperately to replicate the problem but did not succeed. Only in one instance with 126 open tabs, hibernation failed twice in a row (CanHibernate returned s "yes"), but after a (successful) standby operation, hibernation started to succeed repeatedly. That is a single failure in literally hundreds of attempts, which could very well have been a HW/Bios issue to go in deep standby for S5. Fortunately I was able to automated the testing process using session buddy advanced restore, so all I had to do was watch :-). Also switching between Linux hibernation and Windows 10 hibernation always succeeded. The hibernation speed seemed also to have improved, but I have no hard data to illustrate this. I am happy to report that with: Kernel 5.3.0.28 --> 5.3.0.40 Chromium 79.0.3945 --> 80.0.3987 Systemd 237-3ubuntu10.38 --> 237-3ubuntu10.39 the problem is SOLVED. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1862797 Title: Systemd does not allow hibernation when Chrome/chromium is running Status in systemd package in Ubuntu: Incomplete Bug description: 1/ Linux Mint 19.3/Ubuntu Bionic 18.04 LTS 2/ systemd: Installed: 237-3ubuntu10.38 3/ & 4/ Problem: hibernation stops working as soon as you start Chromium Steps to reproduce $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend s "yes" $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanHibernate s "yes" start chromium $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanHibernate s "na" $ sudo systemctl hibernate Failed to hibernate system via logind: Sleep verb not supported When this happens Cinnamon/Gnome no longer show hibernate buttons of course. $ systemd-inhibit --list Who: ecotech (UID 1000/ecotech, PID 1607/csd-media-keys) What: handle-power-key:handle-suspend-key:handle-hibernate-key Why: Cinnamon handling keypresses Mode: block Who: ModemManager (UID 0/root, PID 996/ModemManager) What: sleep Why: ModemManager needs to reset devices Mode: delay Who: ecotech (UID 1000/ecotech, PID 1656/csd-power) What: sleep Why: Cinnamon needs to lock the screen Mode: delay Who: ecotech (UID 1000/ecotech, PID 1656/csd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Who: NetworkManager (UID 0/root, PID 1012/NetworkManager) What: sleep Why: NetworkManager needs to turn off networks Mode: delay Who: UPower (UID 0/root, PID 1279/upowerd) What: sleep Why: Pause device polling Mode: delay Systemd-inhibit does not mention anything Chrome/Chromium related Stop Chromium and hibernation works again. Similar issues found: https://bugzilla.redhat.com/show_bug.cgi?id=1346908 $ cat /sys/power/state freeze mem disk $ cat /sys/power/disk [platform] shutdown reboot suspend test_resume Tried logind.conf default (all commented out) and below. No difference. $ cat /etc/systemd/logind.conf [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 HandlePowerKey=poweroff HandleSuspendKey=suspend HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchDocked=ignore PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% Can also not file a bug @ https://github.com/systemd/system since my version is more than 2 versions older than the last version (2.44.1). Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862797/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867510] [NEW] Realtek ALC255 cannot play at higher than 48 khz - defaults to generic Intel driver?
Public bug reported: Hi. I am trying to use an onboard Realtek ALC255 soundcard to play audio files that are 192khz. The card supports sampling rates up to 192khz and the machine (Asus mini PC) successfully plays them at that rate under Windows. However, under Ubuntu 18.04(and Debian 10), the sampling rate is maxed out at 48 Khz. Changing the Alsa configuration to force a higher sampling rate (or to play without resampling) has no effect. I tried to upgrade the Linux kernel to this one https://drive.google.com/drive/folders/16OBmEmWPYncLOT-QVlo6vkyy3Ar819aX (unsigned 5.021) as I hoped it contains custom drivers for ALC255, but the result is still the same. Any idea if this has been solved in any kernel version? regards Christo ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1867510 Title: Realtek ALC255 cannot play at higher than 48 khz - defaults to generic Intel driver? Status in alsa-driver package in Ubuntu: New Bug description: Hi. I am trying to use an onboard Realtek ALC255 soundcard to play audio files that are 192khz. The card supports sampling rates up to 192khz and the machine (Asus mini PC) successfully plays them at that rate under Windows. However, under Ubuntu 18.04(and Debian 10), the sampling rate is maxed out at 48 Khz. Changing the Alsa configuration to force a higher sampling rate (or to play without resampling) has no effect. I tried to upgrade the Linux kernel to this one https://drive.google.com/drive/folders/16OBmEmWPYncLOT- QVlo6vkyy3Ar819aX (unsigned 5.021) as I hoped it contains custom drivers for ALC255, but the result is still the same. Any idea if this has been solved in any kernel version? regards Christo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867474] Re: PCI/internal sound card not detected
linux-image-generic is already the newest version (5.4.0.18.22). pulseaudio is already the newest version (1:13.99.1-1ubuntu1). linux-firmware is already the newest version (1.186). alsa-ucm-conf is already the newest version (1.2.2-1). uname -a Linux Vostro-5590 5.4.0-18-generic #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux But audio is still not working dmesg shows this error: [4.126575] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cml.ri failed with error -2 [4.126578] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cml.ri failed err: -2 [4.126579] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [4.126847] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 I'm attaching complete dmesg output Thanks ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+attachment/5337136/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1867474 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
Ubuntu 18.04 should be getting automatic updates already. But that means bug fixes only, not the latest version. To ensure you have the latest updates run: sudo apt update sudo apt full-upgrade In April, Ubuntu 20.04 will be released with the very latest BlueZ version. You can try it early here: http://cdimage.ubuntu.com/daily-live/current/ But regardless, please do not use this old bug. If you experience any problems at all then please open a new bug by running: ubuntu-bug bluez -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted Status in bluez package in Ubuntu: Invalid Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl restart bluetooth $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368147] Re: Lenovo Thinkpad Twist: Mobile Broadbad not working any more
I do not use this laptop any more. So I am closing this bug. ** Changed in: network-manager (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1368147 Title: Lenovo Thinkpad Twist: Mobile Broadbad not working any more Status in network-manager package in Ubuntu: Invalid Bug description: It seems that something has changed and now the functionality for mobile broadband support got completely lost. I can create a new connection, enteringtheoperator and so on, but I cannot establish a connection. First, I click "Enable Mobile Broadband" in the network manager menu. Then I open the meu again and click the entry for my operator. Then I get a pop-up window saying "Connection activation failed, (32) The connection was not supportedby oFono". I am using Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1368147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867479] Re: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake
*** This bug is a duplicate of bug 1867474 *** https://bugs.launchpad.net/bugs/1867474 Did you install the linux-firmware from the -proposed? It is also possible the latest linux-firmware is not in the -proposed yet, please wait for a couple of more days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1867479 Title: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake Status in alsa-driver package in Ubuntu: Confirmed Bug description: It looks like 20.04 is now using sound open firmware (sof), however, sof does not have a driver(?) for Intel Comet Lake processors (which my Lenovo X1 Carbon Gen 7 laptop has). Here is the relevant output of dmesg: [3.272336] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.272343] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.272485] sof-audio-pci :00:1f.3: use msi interrupt mode [3.323370] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.355159] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.355161] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.377802] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.377805] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.377808] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.377809] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 18:22:42 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET21W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET21W(1.15):bd02/25/2020:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586771] Re: unable to On wifi (Air plane mode always ON) in ubuntu gnome 16.04.
Is this still a problem on bionic or later? ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1586771 Title: unable to On wifi (Air plane mode always ON) in ubuntu gnome 16.04. Status in network-manager package in Ubuntu: Incomplete Bug description: Previously Wifi was in working condition By adding extra packages from software updates -> Additional Drivers. But now I can not able to connect with wifi. It only shows in Air Plane mode. I am using Laptop Thinkpad T520 OS = ubuntu gnome 16.04 Network card = Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (Centrino Advanced-N 6205 AGN) Kernel version = 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Thank you. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 29 18:26:15 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-16 (42 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.1.1 dev enp0s25 proto static metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.105 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet connected/org/freedesktop/NetworkManager/Devices/1 enp0s25 dacd31ad-8949-42a6-8115-142800960f1c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp3s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1586771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
