[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Same issue with: Ubuntu 20.04.1 LTS Dell XPS 9500 Sennheiser HD 450BT I would like to stay on LTS version. Any workarounds? -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1903808] Re: GSettings like mouse acceleration are not restored after suspend
*** This bug is a duplicate of bug 1899206 *** https://bugs.launchpad.net/bugs/1899206 ** This bug is no longer a duplicate of bug 1899509 Mouse/touchpad settings not applied on hotplug/reconnect/resume ** This bug has been marked a duplicate of bug 1899206 Keyboard and mouse configuration not persisting on USB keyboard unplug/reconnect -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1903808 Title: GSettings like mouse acceleration are not restored after suspend Status in xorg package in Ubuntu: New Bug description: I have customised some options like mouse acceleration and compose keys using gsettings. # Disable mouse acceleration gsettings set org.gnome.desktop.peripherals.mouse accel-profile flat gsettings set org.gnome.desktop.peripherals.mouse speed 0 # Enable Compose key gsettings set org.gnome.desktop.input-sources xkb-options "['compose:caps']" After around end of August, those settings were not active anymore after suspending. A workaround was to open gnome-tweaks and change the settings to another value and back to the desired value again. If there is something I can do to locate the problem, please let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..3c.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3c:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 06:38:24 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.4.0-51-generic, x86_64: installed evdi, 1.7.0, 5.4.0-52-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-51-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2278] Subsystem: Lenovo GP108M [GeForce MX250] [17aa:2278] InstallationDate: Installed on 2020-05-02 (192 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20N3S4AH00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET87W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S4AH00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET87W(1.65):bd04/07/2020:svnLENOVO:pn20N3S4AH00:pvrThinkPadT490:rvnLENOVO:rn20N3S4AH00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S4AH00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1903808/+subscriptions --
Re: [Touch-packages] [Bug 1901926] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
Hello, my alsa is 1.2.2-1ubuntu2, but i had this problem since ubuntu 18.04. Now I'm using 20.04. Em qui., 5 de nov. de 2020 às 16:03, Marcus Aurelius < 1901...@bugs.launchpad.net> escreveu: > I'm facing a similar problem. May I ask your alsa-utils version? Is it > 1.2.2-1ubuntu2 or 1.2.2-1ubuntu1? > > My issues started when the system updated to alsa-utils 1.2.2-1ubuntu2. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1901926 > > Title: > [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones > > Status in alsa-driver package in Ubuntu: > Confirmed > > Bug description: > There is no sound at all from the headphones (p3 out). Speakers work > fine. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 > Uname: Linux 5.4.0-52-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.10 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: sartojr2255 F pulseaudio >/dev/snd/controlC0: sartojr2255 F pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Wed Oct 28 13:48:59 2020 > InstallationDate: Installed on 2020-01-14 (287 days ago) > InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 > (20190805) > PackageArchitecture: all > ProcEnviron: >LANGUAGE=pt_BR:pt:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=pt_BR.UTF-8 >SHELL=/bin/bash > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH > successful > Symptom_Card: HDA NVidia - HDA NVidia > Symptom_DevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: sartojr2255 F pulseaudio >/dev/snd/controlC0: sartojr2255 F pulseaudio > Symptom_PulsePlaybackTest: PulseAudio playback test successful > Symptom_Type: No sound at all > Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all > UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago) > dmi.bios.date: 11/04/2019 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: P03REZ.041.191104.FL > dmi.board.asset.tag: No Asset Tag > dmi.board.name: NP760XBE-XW1BR > dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. > dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: > dmi.product.family: Notebook 7 Series > dmi.product.name: 760XBE > dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ > dmi.product.version: P03REZ > dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. > mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+subscriptions > -- 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/1901926 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: There is no sound at all from the headphones (p3 out). Speakers work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 13:48:59 2020 InstallationDate: Installed on 2020-01-14 (287 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title:
[Touch-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
I can confirm that the updated packages fix the issue for me (Groovy on a ThinkPad T14 w/ Ryzen 7 Pro 4750U). However, the LED on the keyboard for muting the microphone (on the F4 key) doesn't work for the internal microphone. It works as expected when another microphone is present and selected as input device (I plugged a headset into the audio jack). -- 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/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor:
[Touch-packages] [Bug 1902427] Re: systemd pauses for unspecified reason
The issue was indeed /etc/fstab, which contained a UUID inserted by the installer. Removing the UUID by the actual device name removed the 1:30 minutes delay. You might argue that this is a bug by itself, but it's good enough for me. -- 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/1902427 Title: systemd pauses for unspecified reason Status in systemd package in Ubuntu: Incomplete Bug description: I recently installed Kubuntu 20.04 on a new Ryzen 3900X system. I noticed that the boot time (time between entering LUKS credentials and appearance of login screen) took more than 1 minute. Using `systemd-analyze`, I found the following: ``` cassiopeia:~# systemd-analyze Startup finished in 24.819s (kernel) + 1min 32.150s (userspace) = 1min 56.969s graphical.target reached after 1min 32.144s in userspace cassiopeia:~# systemd-analyze blame 4.721s fstrim.service 2.949s apt-daily-upgrade.service 2.380s systemd-cryptsetup@store.service 1.739s NetworkManager-wait-online.service 439ms apt-daily.service 421ms man-db.service 398ms systemd-logind.service 323ms dev-mapper-root.device 294ms systemd-fsck@dev-mapper-store.service 204ms logrotate.service 153ms systemd-journald.service ... cassiopeia:~# systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. graphical.target @1min 32.144s └─multi-user.target @1min 32.144s └─fetchmail.service @1min 32.128s +16ms └─network-online.target @1min 32.127s └─NetworkManager-wait-online.service @1min 30.388s +1.739s └─NetworkManager.service @1min 30.282s +105ms └─dbus.service @1min 30.279s └─basic.target @1min 30.265s └─sockets.target @1min 30.265s └─snapd.socket @1min 30.264s +370us └─sysinit.target @1min 30.262s └─systemd-timesyncd.service @1min 30.219s +42ms └─systemd-tmpfiles-setup.service @1min 30.202s +15ms └─systemd-journal-flush.service @288ms +49ms └─systemd-journald.service @131ms +153ms └─systemd-journald.socket @129ms └─-.mount @127ms └─blockdev@dev-mapper-root.target @410ms └─systemd-cryptsetup@root.service @401ms +8ms └─dev-nvme0n1p2.device @398ms ``` This didn't really help, but `systemd-analyze plot > boot.svg` produced an SVG file (see attachment) that shows a gap between store.mount (completes within 38 ms) and apparmor.service of almost 1:30 minutes. What did systemd do during this gap? I think it is either a bug in systemd that idles, or in systemd- analyze that doesn't disclose the actions in that gap. (Note: I have posted this question in two well-known Ubuntu forums, but I didn't receive any answers.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902427/+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
Re: [Touch-packages] [Bug 1901926] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
In my case unplugging and puggling the headphones makes no difference at all, and doesn't pop up anything. Em sex., 6 de nov. de 2020 às 13:55, Marcus Aurelius < 1901...@bugs.launchpad.net> escreveu: > While generating the logs I found out that maybe it's not alsa-utils > version. > > It could also be a combination of the following: > > - Booting up with earphones plugged in makes the sound come out from the > internal speakers (and not the earphones). > - Changing the sound output device in the settings app to the earphones > doesn't work (they remain silent - I tested using the test window) > - Unplugging the earphones and plugging them back in works, but only if > the settings app is closed. In all cases a window pops up asking what kind > of device I plugged in (phones, phones+mic, mic), but the end result > differs. > - Audacity seems to reset _something_ when it starts up so whatever state > the system was in before launching Audacity might need to be set up again > (e.g. unplugging and plugging my earphones yet again). > - There was another update in the meantime including libasound2, > libasound2-data, systemd, libudev1, etc. so that could be related too. > > Of course I performed most tests using the settings app, that would > explain why I couldn't get any sound on my earphones by normal means. > > I will upload my logs when I have some kind of consistent and > reproducible state (unless you want me to send them anyway). > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1901926 > > Title: > [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones > > Status in alsa-driver package in Ubuntu: > Confirmed > > Bug description: > There is no sound at all from the headphones (p3 out). Speakers work > fine. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 > Uname: Linux 5.4.0-52-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.10 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: sartojr2255 F pulseaudio >/dev/snd/controlC0: sartojr2255 F pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Wed Oct 28 13:48:59 2020 > InstallationDate: Installed on 2020-01-14 (287 days ago) > InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 > (20190805) > PackageArchitecture: all > ProcEnviron: >LANGUAGE=pt_BR:pt:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=pt_BR.UTF-8 >SHELL=/bin/bash > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH > successful > Symptom_Card: HDA NVidia - HDA NVidia > Symptom_DevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: sartojr2255 F pulseaudio >/dev/snd/controlC0: sartojr2255 F pulseaudio > Symptom_PulsePlaybackTest: PulseAudio playback test successful > Symptom_Type: No sound at all > Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all > UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago) > dmi.bios.date: 11/04/2019 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: P03REZ.041.191104.FL > dmi.board.asset.tag: No Asset Tag > dmi.board.name: NP760XBE-XW1BR > dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. > dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: > dmi.product.family: Notebook 7 Series > dmi.product.name: 760XBE > dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ > dmi.product.version: P03REZ > dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. > mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+subscriptions > -- 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/1901926 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: There is no sound at all from the headphones (p3 out). Speakers work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux
[Touch-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
Hi, I have tested the updated package on Focal and it solved my problem (Lenovo Yoga Slim 7 AMD 4800u) -- 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/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
[Touch-packages] [Bug 1904286] [NEW] Updated UBUNTU to 20.04 : No sound when HDMI connected [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
Public bug reported: I have loudspeakers connected on green output, on motherboard, and TV connected with HDMI in another room. With UBUNTU 18.04, I had to change manually sound output in parameters, sound board. I have just upgraded to UBUNTU 20.04. Change output seems now automatic. When I connect TV with HDMI, I have sound on TV, but no more possibility to have sound with loudspeakers connected to PC. I must disconnect HDMI cable to find again sound on PC. And change manually sound output in parameters, sound board doesn't work. Thanking you in advance for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 14 16:28:24 2020 InstallationDate: Installed on 2019-01-12 (671 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 126: Error executing command as another user: Request dismissed Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to focal on 2020-11-14 (0 days ago) dmi.bios.date: 01/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3803 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3803:bd01/22/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1904286 Title: Updated UBUNTU to 20.04 : No sound when HDMI connected [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: I have loudspeakers connected on green output, on motherboard, and TV connected with HDMI in another room. With UBUNTU 18.04, I had to change manually sound output in parameters, sound board. I have just upgraded to UBUNTU 20.04. Change output seems now automatic. When I connect TV with HDMI, I have sound on TV, but no more possibility to have sound with loudspeakers connected to PC. I must disconnect HDMI cable to find again sound on PC. And change manually sound output in parameters, sound board doesn't work. Thanking you in advance for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 14 16:28:24 2020 InstallationDate: Installed on 2019-01-12 (671 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c',
[Touch-packages] [Bug 1891479] [pycurl/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1891479 Title: pycurl ftbfs in focal (wait-deps) Status in pycurl package in Ubuntu: Confirmed Status in pycurl source package in Focal: Fix Committed Bug description: [SRU Justification] This package is unbuildable due to unsatisfiable build-dependencies, as seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19799602 Missing build dependencies: python-sphinx This makes the package unsupportable in the event a security update needs to be applied. [Test case] 1. let the package attempt to build in focal 2. check if it succeeds. [Regression potential] Because the missing build-dependency is python-sphinx, which is only used for building the package documentation, the risk of regression is confined to a misbuild of the documentation. Regardless, this package will be held in -proposed because the runtime impact of a FTBFS is non-existent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1891479/+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 1895584] Re: fstab does not schedule fsck
Excuse me, It was complete since the very beginning at the moment it was marked incomplete ** Changed in: base-files (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1895584 Title: fstab does not schedule fsck Status in base-files package in Ubuntu: New Bug description: Current live server installer (20.04 / 20.04.1) creates fstab which never schedules fsck. when actual power failure occurs half of systems dont boot, other half come up with scary errors in boot log. fstab manual (in "mount" package) says explicitly that / filesystem whould be with fsck preference 1 and other disk-based filesystems with 2, if that is corrected, in cases from external boot media, fsck and good system boot proceeds correctly PS package "mount 2.34-0.1ubuntu9 amd64" cannot be selected in the box above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1895584/+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 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
I, too, confirm that the proposed updates solve the audio issue (for my system info, please see the initial information in the bug report). -- 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/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias:
[Touch-packages] [Bug 1742482] Re: firefox is used to open ftp share files
The bug is still there in Ubuntu 20.10. I'm even almost certain it was fixed and re-appeared recently. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1742482 Title: firefox is used to open ftp share files Status in glib2.0 package in Ubuntu: Triaged Bug description: Ubuntu 18.04 Nautilus 1:3.26.0-0ubuntu1 Bluefish 2.2.10 When I open a .php file from a FTP server browsed with Nautilus, Chrome is opened instead of the default application Bluefish. Steps to reproduce: 1. Connect to an FTP server via Nautilus 2a. Double-click on a .php file: chrome opens and the file is downloaded 2b. Right click and select 'open with' and then Bluefish: the file is opened in bluefish as expected So, on the double-click from Nautilus the wrong app (chrome!) is opened even if the .php files are associated with bluefish. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluefish 2.2.9-1 ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12 Uname: Linux 4.14.0-15-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 10 17:12:27 2018 ExecutablePath: /usr/bin/bluefish InstallationDate: Installed on 2015-12-07 (765 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: bluefish UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1742482/+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 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly
** Changed in: procps (Ubuntu) Importance: Undecided => Medium ** Also affects: procps (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: procps (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: procps (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: procps (Ubuntu Groovy) Importance: Undecided => Medium -- 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/1903351 Title: ignore_eacces and ignore_erofs patches don't work properly Status in procps package in Ubuntu: Confirmed Status in procps source package in Focal: New Status in procps source package in Groovy: New Bug description: The patches used to ignore errors in containers no longer work as of 3.3.16 due to upstream commit https://gitlab.com/procps- ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932 The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not WriteSetting Both patches ignore the change that rc is no longer propagated up and instead everything is trapped by: if (!ignore_failure && errno != ENOENT) rc = -1; Versions affected: focal+ root@bfee89058713:/tmp# cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy root@bfee89058713:/# dpkg -l procps Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 255 root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+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 1900255] Re: accountsservice drop privileges denial of service (GHSL-2020-187, GHSL-2020-188)
** CVE removed: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2018-14036
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1900255
Title:
accountsservice drop privileges denial of service (GHSL-2020-187,
GHSL-2020-188)
Status in accountsservice package in Ubuntu:
Fix Released
Bug description:
# GitHub Security Lab (GHSL) Vulnerability Report: `GHSL-2020-187`,
`GHSL-2020-188`
The [GitHub Security Lab](https://securitylab.github.com) team has
identified potential security vulnerabilities in
[accountsservice](https://git.launchpad.net/ubuntu/+source/accountsservice/).
We are committed to working with you to help resolve these issues. In
this report you will find everything you need to effectively
coordinate a resolution of these issues with the GHSL team.
If at any point you have concerns or questions about this process,
please do not hesitate to reach out to us at `security...@github.com`
(please include `GHSL-2020-187` or `GHSL-2020-188` as a reference).
If you are _NOT_ the correct point of contact for this report, please
let us know!
## Summary
The accountsservice daemon drops privileges to perform certain
operations. For example while performing the
`org.freedesktop.Accounts.User.SetLanguage` D-Bus method, which can be
triggered by an unprivileged user, accounts-daemon temporarily drops
privileges to the same UID as the user, to avoid being tricked into
opening a file which the unprivileged user should not be able to
access. Unfortunately, by changing its
[RUID](https://en.wikipedia.org/wiki/User_identifier#Real_user_ID) it
has given the user permission to send it signals. This means that the
unprivileged user can send accounts-daemon a `SIGSTOP` signal, which
stops the process and causes a denial of service.
## Product
[accountsservice](https://git.launchpad.net/ubuntu/+source/accountsservice/)
## Tested Version
* accountsservice, version 0.6.55-0ubuntu12~20.04.1
* Tested on Ubuntu 20.04.1 LTS
Note: I believe these issues only exist in Ubuntu's version of
accountsservice. I couldn't find the vulnerable functions in the git
repos maintained by
[freedesktop](https://gitlab.freedesktop.org/accountsservice/accountsservice)
or [debian](https://salsa.debian.org/freedesktop-
team/accountsservice). I originally discovered the vulnerable code in
the version of the code that I had obtained by running `apt-get source
accountsservice`, but I struggled to figure out where it came from
when I started searching the official repositories. I eventually
tracked it down to this patch file: [0010-set-
language.patch](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010
-set-language.patch?h=ubuntu/focal-
updates=e0347185d4c5554b026c13ccca691577c239afd5).
## Details
### Issue 1: accountsservice drop privileges `SIGSTOP` denial of
service (`GHSL-2020-187`)
A [source code
patch](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010
-set-language.patch?h=ubuntu/focal-
updates=e0347185d4c5554b026c13ccca691577c239afd5) that (as far as I
know) only exists in Ubuntu's version of accountsservice, adds a
function named
[`user_drop_privileges_to_user`](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010
-set-language.patch?h=ubuntu/focal-
updates=e0347185d4c5554b026c13ccca691577c239afd5#n66):
```c
static gboolean
user_drop_privileges_to_user (User *user)
{
if (setresgid (user->gid, user->gid, -1) != 0) {
g_warning ("setresgid() failed");
return FALSE;
}
if (setresuid (accounts_user_get_uid (ACCOUNTS_USER (user)),
accounts_user_get_uid (ACCOUNTS_USER (user)), -1) != 0) {
g_warning ("setresuid() failed");
return FALSE;
}
return TRUE;
}
```
This function is used to drop privileges while doing operations on
behalf of an unprivileged user. Dropping the
[EUID](https://en.wikipedia.org/wiki/User_identifier#Effective_user_ID)
is a sensible precaution, which prevents accountsservice from
accessing a file which the unprivileged user cannot access themselves.
Unfortunately, dropping the
[RUID](https://en.wikipedia.org/wiki/User_identifier#Real_user_ID) has
the opposite effect of making security worse, because it enables the
unprivileged user to send signals to accountsservice. For example,
they can send a `SIGSTOP` which stops the accountsservice daemon and
causes a denial of service.
The vulnerability can be triggered via multiple different D-Bus
methods. Many of them involve precise timing to send the `SIGSTOP`
signal at just the right moment. But there is a much simpler and more
reliable way to reproduce the vulnerability by
[Touch-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+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 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
@tdaitx asked me to take a look at this problem, and here is what I
found.
1) As he said above, the problem is that Debian/Ubuntu generate
.gnu_debugaltlink sections containing full pathnames to the DWZ alt
debug files. IMO, we should be using dwz's "--relative" option when
invoking it via dh_dwz. I will send a merge request on Salsa and
propose that we adopt this flag as a distro.
2) While we could use the workaround described in the last comment, I
think it is better if GDB is adjusted to cope with this scenario (i.e.,
having a full pathname on .gnu_debugaltlink, but having the actual DWZ
file in another directory that is also provided as the debug-file-
directory to GDB). I went ahead and submitted a patch to GDB to do just
that:
https://sourceware.org/pipermail/gdb-patches/2020-November/173276.html
I think searching for the DWZ files using the debug-file-directory
provided by the user is a sensible approach, and is also something that
other projects (namely elfutils) seem to do.
All in all, as I said in (1), I think the best long-term solution is to
adjust dh_dwz to put relative pathnames in the .gnu_debugaltlink.
Arguably, we could also create a symlink in /usr/lib/debug/.build-id/
and make it point to the corresponding file inside /usr/lib/debug/.dwz/,
but that is an orthogonal issue and would not help with this specific
bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Confirmed
Bug description:
As far as I can tell gdb version 8.2.90 isn't searching the debug-
file-directory, which I set, for the '.gnu_debugaltlink' which is in
the debug symbols. Here's the error I'm seeing:
Type "apropos word" to search for commands related to "word".
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
could not find '.gnu_debugaltlink' file for
/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
(No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)
Here's part of an strace of what's going on behind the scenes:
lstat("/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
{st_mode=S_IFREG|0644, st_size=839744, ...}) = 0
openat(AT_FDCWD,
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
This is the only time "/usr/lib/debug" is searched, generally
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/lib/debug/" is used. I'll attach the full strace though.
For completeness here's the gdb command I'm using:
Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
/report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
--ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
--ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
-linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox//usr/bin/gnome-calculator"' --ex 'core-file
/tmp/apport_core_1b6dn6np'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1818918/+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 1754671] Re: Full-tunnel VPN DNS leakage regression
** Changed in: network-manager Status: Confirmed => Expired -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in network-manager source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1754671]
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited). -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in network-manager source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1903614] Re: Please merge kbd 2.3.0-3 from Debian unstable
** Changed in: kbd (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1903614 Title: Please merge kbd 2.3.0-3 from Debian unstable Status in kbd package in Ubuntu: New Bug description: Please merge kbd 2.3.0-3 from Debian unstable. Updated changelog and diff against Debian unstable is attached below. Test build available from https://launchpad.net/~waveform/+archive/ubuntu/kbd/+packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1903614/+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 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+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 1815036] Re: uri defined for connectivity check does not have IPv6 address
As of now connectivity-check.ubuntu.com has still no record and... it causes no IPv6 problem on Ubuntu 20.04. I doubt it ever did. "ping www.google.com" and "getent ahosts www.google.com" show that the system prefers IPv6 anyway. As expected, only changing /etc/gai.conf makes "ping www.google.com" and "getent ahosts www.google.com" prefer IPv4. Nothing else does. I also tried to change the connectivity uri to http://fedoraproject.org/static/hotspot.txt (which has ) and it made no difference whatsoever anywhere compared to connectivity- check.ubuntu.com > As a result, the IPv6 default routes will be heavily deprioritised (ie: having 2 added to the metric) My default IPv6 route had a 20100 metric in every single combination I tried. Using fedoraproject.org made no difference. Note I have a single wired interface, no wifi. AFAIK IPv6 route metrics are only compared to other IPv6 routes, not to IPv4 routes. It's not like each packet has a choice between the two. PS: see #1880258 for another, unrelated connectivity-check.ubuntu.com issue. -- 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/1815036 Title: uri defined for connectivity check does not have IPv6 address Status in network-manager package in Ubuntu: Confirmed Bug description: As per subject. This package defines the file /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf, which defines the uri for the connectivity check to be http://connectivity- check.ubuntu.com This hostname does not resolve to an IPv6 address. Therefore, even if the user has fully working IPv6, the connectivity check for IPv6 will fail. As a result, the IPv6 default routes will be heavily deprioritised (ie: having 2 added to the metric) rendering them effectively inoperable absent a deliberate effort to use IPv6-only addresses. NB: This was discovered by-the-by during reporting of bug #1814262 upstream at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/116#note_114448 It seems to be irrelevant to the main thrust of that bug, which is that IPv4 wired routes are not being identified as working correctly. In fact, when I switch to network-manager-config-connectivity-debian, the hostname defined there *does* have a working IPv6 address, and the issue actually being reported in that other bug does not affect the IPv6 routes, only the IPv4 ones. The bug here probably doesn't need any change made to the package itself, but rather to the networking of the actual target URL. It needs an IPv6 () DNS record, and for it to function on that address. I note in passing the debian connectivity check URL resolves to several IP addresses - four IPv4 addresses and 3 IPv6 addresses, presumably geographically diverse. (It's actually a CNAME to static.debian.org) This looks like it would be a more reliable target for connectivity checks. The ubuntu URL only resolves to a single IPv4 address. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager-config-connectivity-ubuntu 1.15.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 12:35:24 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-09-11 (148 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) IpRoute: default via 192.168.1.254 dev enp63s0 proto dhcp metric 100 default via 192.168.1.254 dev wlp2s0 proto dhcp metric 20600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev enp63s0 proto kernel scope link src 192.168.1.106 metric 100 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PackageArchitecture: all SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-13 (24 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.15.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815036/+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
