[Touch-packages] [Bug 1990040] Re: Bass speakers not enabled on Lenovo Yoga 7 Gen 7 (14ARB7)
Interestingly, somebody found a workaround; see https://github.com/PJungkamp/yoga9-linux/issues/8. ** Bug watch added: github.com/PJungkamp/yoga9-linux/issues #8 https://github.com/PJungkamp/yoga9-linux/issues/8 -- 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/1990040 Title: Bass speakers not enabled on Lenovo Yoga 7 Gen 7 (14ARB7) Status in pulseaudio package in Ubuntu: New Bug description: The Lenovo Yoga 7 Gen 7 (14ARB7) has 4 speakers - 2 trebles and 2 basses. The treble speakers work, but the bass ones don't. I think this is very similar to https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165, but that patch does not solve the problem, I suppose because the chipset is not the same (ALC245 on this machine vs ALC295 on that. This report has been sent from a system with Pipewire (and kernel 6.0), but this can be ignored, as the problem reproduces the same way on a system without Pipewire (kernel 6.0 is needed because of keyboard issues). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 6.0.0-06rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio2016 F wireplumber /dev/snd/controlC0: saverio2016 F wireplumber /dev/snd/seq:saverio2014 F pipewire CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Sep 18 00:08:29 2022 InstallationDate: Installed on 2022-09-15 (2 days ago) InstallationMedia: Ubuntu-MATE 22.04.1-6.0rc3 "Custom Jammy Jellyfish" (20220910) 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/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrK5CN27WW:bd05/08/2022:br1.27:efr1.27:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7: dmi.product.family: Yoga 7 14ARB7 dmi.product.name: 82QF dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7 dmi.product.version: Yoga 7 14ARB7 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.default.apport: 2022-09-15T11:39:08.571662 mtime.conffile..etc.pulse.default.pa: 2022-09-15T11:39:08.207685 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1990040/+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 1989989] Re: Microphone not working on Lenovo Yoga 7 Gen 7 AMD (14ARB7)
This patch: https://bugzilla.kernel.org/show_bug.cgi?id=216299#c3 fixes the problem. The volume is low, but better than not working at all :) ** Bug watch added: Linux Kernel Bug Tracker #216299 https://bugzilla.kernel.org/show_bug.cgi?id=216299 -- 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/1989989 Title: Microphone not working on Lenovo Yoga 7 Gen 7 AMD (14ARB7) Status in alsa-driver package in Ubuntu: New Bug description: On my Lenovo Yoga 7 Gen 7 AMD (14ARB7), the microphone doesn't work. I'm not familiar with the area, but I think that there is no recognized input device at all. When I try to record with any program, no sound is recorded. I think that this problem affects other Lenovo Yoga laptops. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.0.0-06rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio1949 F pulseaudio /dev/snd/controlC0: saverio1949 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Sep 16 18:15:09 2022 InstallationDate: Installed on 2022-09-15 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04.1-6.0rc3 "Custom Jammy Jellyfish" (20220910) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 8 3 1 : a u d i o o p e n e r r o r : N o s u c h f i l e o r d i r e c t o r y Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio1949 F pulseaudio /dev/snd/controlC0: saverio1949 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrK5CN27WW:bd05/08/2022:br1.27:efr1.27:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7: dmi.product.family: Yoga 7 14ARB7 dmi.product.name: 82QF dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7 dmi.product.version: Yoga 7 14ARB7 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-09-15T11:39:08.571662 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1989989/+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 1990040] [NEW] Bass speakers not enabled on Lenovo Yoga 7 Gen 7 (14ARB7)
Public bug reported: The Lenovo Yoga 7 Gen 7 (14ARB7) has 4 speakers - 2 trebles and 2 basses. The treble speakers work, but the bass ones don't. I think this is very similar to https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165, but that patch does not solve the problem, I suppose because the chipset is not the same (ALC245 on this machine vs ALC295 on that. This report has been sent from a system with Pipewire (and kernel 6.0), but this can be ignored, as the problem reproduces the same way on a system without Pipewire (kernel 6.0 is needed because of keyboard issues). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 6.0.0-06rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio2016 F wireplumber /dev/snd/controlC0: saverio2016 F wireplumber /dev/snd/seq:saverio2014 F pipewire CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Sep 18 00:08:29 2022 InstallationDate: Installed on 2022-09-15 (2 days ago) InstallationMedia: Ubuntu-MATE 22.04.1-6.0rc3 "Custom Jammy Jellyfish" (20220910) 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/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrK5CN27WW:bd05/08/2022:br1.27:efr1.27:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7: dmi.product.family: Yoga 7 14ARB7 dmi.product.name: 82QF dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7 dmi.product.version: Yoga 7 14ARB7 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.default.apport: 2022-09-15T11:39:08.571662 mtime.conffile..etc.pulse.default.pa: 2022-09-15T11:39:08.207685 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1990040 Title: Bass speakers not enabled on Lenovo Yoga 7 Gen 7 (14ARB7) Status in pulseaudio package in Ubuntu: New Bug description: The Lenovo Yoga 7 Gen 7 (14ARB7) has 4 speakers - 2 trebles and 2 basses. The treble speakers work, but the bass ones don't. I think this is very similar to https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165, but that patch does not solve the problem, I suppose because the chipset is not the same (ALC245 on this machine vs ALC295 on that. This report has been sent from a system with Pipewire (and kernel 6.0), but this can be ignored, as the problem reproduces the same way on a system without Pipewire (kernel 6.0 is needed because of keyboard issues). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 6.0.0-06rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio2016 F wireplumber /dev/snd/controlC0: saverio2016 F wireplumber /dev/snd/seq:saverio2014 F pipewire CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Sep 18 00:08:29 2022 InstallationDate: Installed on 2022-09-15 (2 days ago) InstallationMedia: Ubuntu-MATE 22.04.1-6.0rc3 "Custom Jammy Jellyfish" (20220910) 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/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrK5CN27WW:bd05/08/2022:br1.27:efr1.27:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7: dmi.produc
[Touch-packages] [Bug 1989989] [NEW] Microphone not working on Lenovo Yoga 7 Gen 7 AMD (14ARB7)
Public bug reported: On my Lenovo Yoga 7 Gen 7 AMD (14ARB7), the microphone doesn't work. I'm not familiar with the area, but I think that there is no recognized input device at all. When I try to record with any program, no sound is recorded. I think that this problem affects other Lenovo Yoga laptops. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.0.0-06rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio1949 F pulseaudio /dev/snd/controlC0: saverio1949 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Sep 16 18:15:09 2022 InstallationDate: Installed on 2022-09-15 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04.1-6.0rc3 "Custom Jammy Jellyfish" (20220910) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 8 3 1 : a u d i o o p e n e r r o r : N o s u c h f i l e o r d i r e c t o r y Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio1949 F pulseaudio /dev/snd/controlC0: saverio1949 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrK5CN27WW:bd05/08/2022:br1.27:efr1.27:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7: dmi.product.family: Yoga 7 14ARB7 dmi.product.name: 82QF dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7 dmi.product.version: Yoga 7 14ARB7 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-09-15T11:39:08.571662 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1989989 Title: Microphone not working on Lenovo Yoga 7 Gen 7 AMD (14ARB7) Status in alsa-driver package in Ubuntu: New Bug description: On my Lenovo Yoga 7 Gen 7 AMD (14ARB7), the microphone doesn't work. I'm not familiar with the area, but I think that there is no recognized input device at all. When I try to record with any program, no sound is recorded. I think that this problem affects other Lenovo Yoga laptops. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.0.0-06rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio1949 F pulseaudio /dev/snd/controlC0: saverio1949 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Sep 16 18:15:09 2022 InstallationDate: Installed on 2022-09-15 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04.1-6.0rc3 "Custom Jammy Jellyfish" (20220910) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 8 3 1 : a u d i o o p e n e r r o r : N o s u c h f i l e o r d i r e c t o r y Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio1949 F pulseaudio /dev/snd/controlC0: saverio1949 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis
[Touch-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
I have the same problem on a Yoga 7 Gen 7 AMD (14ARB7), which may be the same problem. @pjungkamp In order to test on my machine, can I just apply the same set of patches (¹ and ²), or do I need to do something like search/replace, or I just can't apply them at all? Thanks! ¹=https://github.com/PJungkamp/yoga9-linux/blob/main/kernel-patches/0006-ALSA-hda-realtek-Add-quirk-for-Lenovo-Yoga9-14IAP7.patch ²=https://github.com/PJungkamp/yoga9-linux/blob/main/kernel-patches/0007-ALSA-hda-realtek-Add-quirk-for-Yoga-devices.patch -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) 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_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1768488] Re: dependency problem lightdm -> pam
Still present in Focal and Jammy. -- 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/1768488 Title: dependency problem lightdm -> pam Status in lightdm package in Ubuntu: Confirmed Bug description: Hi, I've installed Lubuntu 18.04 and found that problem: the display-manager service complains: ● lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor preset: enabled) Active: active (running) since Wed 2018-05-02 11:36:27 CEST; 1min 22s ago Docs: man:lightdm(1) Process: 1717 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, status=0/SUCCESS) Main PID: 1720 (lightdm) Tasks: 6 (limit: 4915) CGroup: /system.slice/lightdm.service ├─1720 /usr/sbin/lightdm ├─1726 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch └─1786 lightdm --session-child 12 19 Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM adding faulty module: pam_kwallet5.so Mai 02 11:36:29 pcdanisch lightdm[1735]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: pam_gnome_keyring.so Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: pam_kwallet.so Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: pam_kwallet5.so Mai 02 11:36:30 pcdanisch lightdm[1786]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "danisch" It's because /etc/pam.d/lightdm and /etc/pam.d/lightdm-greeter try to load pam modules which are not installed since there are not dependencies to libpam-gnome-keyring libpam-kwallet4 libpam-kwallet5 If it is not intended to let things run into error message (and possible further trouble), you should either remove these lines from the config files or add dependencies to pull in that packages. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: LXDE Date: Wed May 2 12:21:26 2018 InstallationDate: Installed on 2018-04-30 (2 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1768488/+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 1960709] Re: Recent bluez update broke Bluetooth for setups using a BT dongle
Thanks for the reply, by the way :) -- 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/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: A recent upgrade (seemingly 5.53-0ubuntu3.5) broke Bluetooth functionality for certain setups. Specifically, the `ConditionPathIsDirectory=` parameter has been added to the `bluetooth` Systemd unit. This breaks setups where users use a Bluetooth dongle, since when the system starts, the BT device may not be connected, and due to the condition, the `bluetooth` unit won't start at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+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 1960709] Re: Recent bluez update broke Bluetooth for setups using a BT dongle
Hello! I think the bug can be closed: > BTW, "ConditionPathIsDirectory" is not new. It's been there for two years already in Ubuntu 20.04. On the same date of the bluez package upgrade, I had to revert to an older kernel version due to the amdgpu driver incompatibility, so that should be the cause. The version was the Ubuntu mainline 5.11.16 (the latest compatible with 20.04 and with the amdgpu official drivers as of today), which I don't know if it's of any interest (if so, I can upload the information). -- 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/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: A recent upgrade (seemingly 5.53-0ubuntu3.5) broke Bluetooth functionality for certain setups. Specifically, the `ConditionPathIsDirectory=` parameter has been added to the `bluetooth` Systemd unit. This breaks setups where users use a Bluetooth dongle, since when the system starts, the BT device may not be connected, and due to the condition, the `bluetooth` unit won't start at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+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 1960709] [NEW] Recent bluez update broke Bluetooth for setups using a BT dongle
Public bug reported: A recent upgrade (seemingly 5.53-0ubuntu3.5) broke Bluetooth functionality for certain setups. Specifically, the `ConditionPathIsDirectory=` parameter has been added to the `bluetooth` Systemd unit. This breaks setups where users use a Bluetooth dongle, since when the system starts, the BT device may not be connected, and due to the condition, the `bluetooth` unit won't start at all. ** 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/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle Status in bluez package in Ubuntu: New Bug description: A recent upgrade (seemingly 5.53-0ubuntu3.5) broke Bluetooth functionality for certain setups. Specifically, the `ConditionPathIsDirectory=` parameter has been added to the `bluetooth` Systemd unit. This breaks setups where users use a Bluetooth dongle, since when the system starts, the BT device may not be connected, and due to the condition, the `bluetooth` unit won't start at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+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 1830079] Re: PAM errors logged when pam_kwallet is not installed
*** This bug is a duplicate of bug 1768488 *** https://bugs.launchpad.net/bugs/1768488 ** This bug has been marked a duplicate of bug 1768488 dependency problem lightdm -> pam -- 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/1830079 Title: PAM errors logged when pam_kwallet is not installed Status in lightdm package in Ubuntu: New Bug description: ii lightdm1.18.3-0ubuntu amd64 Display Manager VERSION="16.04.6 LTS (Xenial Xerus)" Running with XFCE installed, I see the following in /var/log/auth.log: May 21 15:52:09 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory May 21 15:52:09 lightdm: PAM adding faulty module: pam_kwallet.so May 21 15:52:09 lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory May 21 15:52:09 lightdm: PAM adding faulty module: pam_kwallet5.so These can be avoided by prefixing the optional components in /etc/pam.d/lightdm (and lightdm-greeter) by a "-" as follows: #%PAM-1.0 authrequisite pam_nologin.so authsufficient pam_succeed_if.so user ingroup nopasswdlogin @include common-auth -authoptionalpam_gnome_keyring.so @include common-account session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close #session requiredpam_loginuid.so session requiredpam_limits.so @include common-session session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open -session optionalpam_gnome_keyring.so auto_start -session optionalpam_kwallet.so auto_start -session optionalpam_kwallet5.so auto_start session requiredpam_env.so readenv=1 session requiredpam_env.so readenv=1 user_readenv=1 envfile=/etc/default/locale @include common-password From man pam.conf: If the type value from the list above is prepended with a - character the PAM library will not log to the system log if it is not possible to load the module because it is missing in the system. This can be useful especially for modules which are not always installed on the system and are not required for correct authentication and authorization of the login session. Also, isn't it required to have: -auth optional pam_kwallet.so for pam_kallet to work, as it needs access to the password? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1830079/+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 1861598] Re: lightdm assumes pam-kwallet to be always installed
*** This bug is a duplicate of bug 1768488 *** https://bugs.launchpad.net/bugs/1768488 ** This bug has been marked a duplicate of bug 1768488 dependency problem lightdm -> pam -- 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/1861598 Title: lightdm assumes pam-kwallet to be always installed Status in lightdm package in Ubuntu: New Bug description: During boot, I see this error: > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: pam_kwallet.so > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: pam_kwallet5.so which I guess it's caused by this: > # grep kwallet /etc/pam.d/lightd* > /etc/pam.d/lightdm:authoptionalpam_kwallet.so > /etc/pam.d/lightdm:authoptionalpam_kwallet5.so > /etc/pam.d/lightdm:session optionalpam_kwallet.so auto_start > /etc/pam.d/lightdm:session optionalpam_kwallet5.so auto_start > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet.so > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet5.so > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet.so auto_start > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet5.so auto_start kwallet is a KDE program, which is not installed on MATE (and I think it shouldn't be), so I guess that such modules should not be [attempted to be] loaded. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sun Feb 2 11:03:53 2020 InstallationDate: Installed on 2020-01-20 (12 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1861598/+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 1889085] [NEW] GTK File chooser search doesn't find files with a dot
Public bug reported: (I'm not sure this is the correct package to file the bug against) The (I assume) GTK 3.0 File chooser dialog doesn't allow searching files with a dot. In the previous, but working, File chooser, in order to search files, the typeahead would be used. In order to search dotfiles (files starting with dot), one would enable display of hidden files if required, then just type the filename (starting with the dot character). With the new search functionality, the dot character is not searched (or not considered valid, it's not clear), so one can't search dotfiles, and they need to manually go through the files in order to find the intended one(s). In order to reproduce, for example: - Open a webpage in Firefox - Click "Save As..." on an image - Tap Ctrl+H, if the hidden files are not displayed - Tap Ctrl+F, in order to search - Tap dot (`.`) no files show. I hope this is not another case of the (in)famous group of devs who's trying to reduce the whole desktop experience to a single blinking dot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Jul 27 15:52:53 2020 InstallationDate: Installed on 2020-07-01 (26 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1889085 Title: GTK File chooser search doesn't find files with a dot Status in gtk+3.0 package in Ubuntu: New Bug description: (I'm not sure this is the correct package to file the bug against) The (I assume) GTK 3.0 File chooser dialog doesn't allow searching files with a dot. In the previous, but working, File chooser, in order to search files, the typeahead would be used. In order to search dotfiles (files starting with dot), one would enable display of hidden files if required, then just type the filename (starting with the dot character). With the new search functionality, the dot character is not searched (or not considered valid, it's not clear), so one can't search dotfiles, and they need to manually go through the files in order to find the intended one(s). In order to reproduce, for example: - Open a webpage in Firefox - Click "Save As..." on an image - Tap Ctrl+H, if the hidden files are not displayed - Tap Ctrl+F, in order to search - Tap dot (`.`) no files show. I hope this is not another case of the (in)famous group of devs who's trying to reduce the whole desktop experience to a single blinking dot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Jul 27 15:52:53 2020 InstallationDate: Installed on 2020-07-01 (26 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1889085/+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 1861598] [NEW] lightdm assumes pam-kwallet to be always installed
Public bug reported: During boot, I see this error: > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file or > directory > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: pam_kwallet.so > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet5.so): > /lib/security/pam_kwallet5.so: cannot open shared object file: No such file > or directory > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: > pam_kwallet5.so which I guess it's caused by this: > # grep kwallet /etc/pam.d/lightd* > /etc/pam.d/lightdm:authoptionalpam_kwallet.so > /etc/pam.d/lightdm:authoptionalpam_kwallet5.so > /etc/pam.d/lightdm:session optionalpam_kwallet.so auto_start > /etc/pam.d/lightdm:session optionalpam_kwallet5.so auto_start > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet.so > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet5.so > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet.so auto_start > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet5.so auto_start kwallet is a KDE program, which is not installed on MATE (and I think it shouldn't be), so I guess that such modules should not be [attempted to be] loaded. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sun Feb 2 11:03:53 2020 InstallationDate: Installed on 2020-01-20 (12 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1861598 Title: lightdm assumes pam-kwallet to be always installed Status in lightdm package in Ubuntu: New Bug description: During boot, I see this error: > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: pam_kwallet.so > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: pam_kwallet5.so which I guess it's caused by this: > # grep kwallet /etc/pam.d/lightd* > /etc/pam.d/lightdm:authoptionalpam_kwallet.so > /etc/pam.d/lightdm:authoptionalpam_kwallet5.so > /etc/pam.d/lightdm:session optionalpam_kwallet.so auto_start > /etc/pam.d/lightdm:session optionalpam_kwallet5.so auto_start > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet.so > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet5.so > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet.so auto_start > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet5.so auto_start kwallet is a KDE program, which is not installed on MATE (and I think it shouldn't be), so I guess that such modules should not be [attempted to be] loaded. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sun Feb 2 11:03:53 2020 InstallationDate: Installed on 2020-01-20 (12 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1861598/+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 1637107] Re: Wrong audio profile (on a Skylake system), causing volume problems.
Works on 18.04, closing. ** Changed in: alsa-driver (Ubuntu) Status: New => Fix Released -- 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/1637107 Title: Wrong audio profile (on a Skylake system), causing volume problems. Status in alsa-driver package in Ubuntu: Fix Released Bug description: I have a Skylake system (ASRock Z170 Gaming-ITX/ac) with (x)Ubuntu 16.04. My speakers are connected via the SPDIF port, but there is a problem. When I inspect the audio profile (in `pavucontrol`), I see that `Analog Stereo Output (unplugged)` is selected. The speakers play regularly, even if this profile is wrong, but the volume doesn't work correctly - anything above mute will cause the speakers to play at maximum volume. If I choose the `Digital Stereo (IEC958)`, the speakers won't receive any signal at all. Debug info: ~$ lspci -vv # extract 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) Subsystem: ASRock Incorporation Sunrise Point-H HD Audio Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ~$ dmesg | grep 00:1f.3 [0.181004] pci :00:1f.3: [8086:a170] type 00 class 0x040300 [0.181034] pci :00:1f.3: reg 0x10: [mem 0xdf14-0xdf143fff 64bit] [0.181062] pci :00:1f.3: reg 0x20: [mem 0xdf12-0xdf12 64bit] [0.181091] pci :00:1f.3: PME# supported from D3hot D3cold [0.181176] pci :00:1f.3: System wakeup disabled by ACPI [0.579846] iommu: Adding device :00:1f.3 to group 8 [3.126041] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915_bpo]) [4.185983] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1f.3/sound/card0/input11 [4.186034] input: HDA Intel PCH Rear Mic as /devices/pci:00/:00:1f.3/sound/card0/input12 [4.186081] input: HDA Intel PCH Line as /devices/pci:00/:00:1f.3/sound/card0/input13 [4.186135] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input14 [4.186188] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1f.3/sound/card0/input15 [4.186228] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input16 [4.186267] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input17 [4.186304] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input18 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: saverio3012 F...m pulseaudio /dev/snd/controlC0: saverio3012 F pulseaudio /dev/snd/controlC1: saverio3012 F pulseaudio CurrentDesktop: XFCE Date: Thu Oct 27 10:21:31 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-11 (108 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Microsoft® LifeCam VX-2000 - Microsoft® LifeCam VX-2000 Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.10 dmi.board.name: Z170 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.10:bd09/30/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1637107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@l