[Touch-packages] [Bug 1983185] Re: Recent commit breaks /etc/X11/Xsession
** Changed in: xorg (Debian) Status: Unknown => New -- 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/1983185 Title: Recent commit breaks /etc/X11/Xsession Status in xorg package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: The following command: $/etc/X11/Xsession true opens a dialog with the following error message: "Xsession: unable to launch "true" X session --- "true" not found; falling back to default session." There is a "Okay" button on this message, and clicking it does bad things if one happens to be running Ubuntu 22.04 on Xorg (or running Gnome on Xorg, which is seemingly a different option for the the low latency installation I am running: 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux). See Brendan O'Dea's related comment about this behavior on debian- bugs-dist: https://www.mail-archive.com/debian-bugs- d...@lists.debian.org/msg1857023.html This has consequences in my use of xpra. For example, if I use xpra via the run_scaled-master script to magnify a single application's interface for a 4K display I get the error dialog mentioned above, often with resulting system instability. This behavior cropped up last month. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sat Jul 30 10:14:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.34, 5.15.0-41-lowlatency, x86_64: installed virtualbox/6.1.34, 5.15.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:3e94] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2269] NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GP104GLM [Quadro P5200 Mobile] [17aa:2269] InstallationDate: Installed on 2022-07-13 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20MBCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_aze0rg@/vmlinuz-5.15.0-43-generic root=ZFS=rpool/ROOT/ubuntu_aze0rg ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: N2CET64W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MBCTO1WW 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.16 dmi.modalias: dmi:bvnLENOVO:bvrN2CET64W(1.47):bd06/10/2022:br1.47:efr1.16:svnLENOVO:pn20MBCTO1WW:pvrThinkPadP72:rvnLENOVO:rn20MBCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20MB_BU_Think_FM_ThinkPadP72: dmi.product.family: ThinkPad P72 dmi.product.name: 20MBCTO1WW dmi.product.sku: LENOVO_MT_20MB_BU_Think_FM_ThinkPad P72 dmi.product.version: ThinkPad P72 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1983185/+subscriptions -- Mailing list: h
[Touch-packages] [Bug 1981042] Re: /etc/localtime symlink not correctly handled when using /etc/writable
** Description changed: - When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink - to /etc/writable/localtime (which in itself if a symlink). Systemd - doesn't handle this correctly when doing firstboot or using inotify to - watch for changed to localtime. + [Impact] + When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink to /etc/writable/localtime (which in itself if a symlink). Systemd doesn't handle this correctly when doing firstboot or using inotify to watch for changes to localtime. + + [Test Plan] + This is somewhat hard to test, the following situations need to be reproduced: + - On firstboot the timezone link will not be read correctly, it will with this change. + - Starting a timer unit and then changing timezone will cause it not to occur at the correct time. + + [Where problems could occur] + This could potentially break other users of localtime, however the change is similar to existing changes which have been in Ubuntu's version of systemd for some time. The change detects the /etc/writable case and if not should have the same existing behaviour. -- 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/1981042 Title: /etc/localtime symlink not correctly handled when using /etc/writable Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: New Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink to /etc/writable/localtime (which in itself if a symlink). Systemd doesn't handle this correctly when doing firstboot or using inotify to watch for changes to localtime. [Test Plan] This is somewhat hard to test, the following situations need to be reproduced: - On firstboot the timezone link will not be read correctly, it will with this change. - Starting a timer unit and then changing timezone will cause it not to occur at the correct time. [Where problems could occur] This could potentially break other users of localtime, however the change is similar to existing changes which have been in Ubuntu's version of systemd for some time. The change detects the /etc/writable case and if not should have the same existing behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981042/+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 1967009] Re: Missing support for Georgian uppercase characters
[Expired for fonts-dejavu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: fonts-dejavu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1967009 Title: Missing support for Georgian uppercase characters Status in fonts-dejavu package in Ubuntu: Expired Bug description: Georgian uppercase letters are encoded in Unicode 11 (2018), but there are no fonts in Ubuntu that can display these characters. Version info: Ubuntu 21.04 To reproduce: 1. add Georgian keyboard layout 2. open any text editor 3. type Georgian letters, then change them to uppercase Expected: Readable text Actual result: Shows squares Some other Linux distributions switched to Google-Noto-Georgian, which covers all Georgian characters. Can it be used in Ubuntu too? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1967009/+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 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time
no activity for 2 years. ** Changed in: oem-priority Importance: Critical => Medium -- 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/1868915 Title: [focal] nm-online -s --timeout=10 timeout every time Status in MAAS: Invalid Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Triaged Bug description: Also created bug on upstream : https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398 This issue will cause "NetworkManager-wait-online.service: Failed with result 'exit-code'." And cloud-init.service is counting on this service for network status. So this issue will finally cause MaaS deploying failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 [modified: lib/systemd/system/NetworkManager-wait-online.service] ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Wed Mar 25 12:43:13 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09 IfupdownConfig: source /etc/network/interfaces.d/*.cfg InstallationDate: Installed on 2020-03-25 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200316-08:40 IpRoute: default via 192.168.101.1 dev eno1 proto static metric 100 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected starting full enabled disabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1868915/+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 1983292] Re: No sound from laptop speakers with Ubuntu 22.04 LTS
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- 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/1983292 Title: No sound from laptop speakers with Ubuntu 22.04 LTS Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have sound through bluetooth devices and external headphones but I cannot get sound output from my laptop speakers, at the begining I had "Dummy sound" as the only output device, after some modifications now the default device is HDMI/Display Port but still with no sound , My laptop is a HUAWEI MateBook D15 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: felipe 1485 F pulseaudio /dev/snd/pcmC0D3p: felipe 1485 F...m pulseaudio CasperMD5CheckResult: pass Date: Mon Aug 1 17:30:03 2022 InstallationDate: Installed on 2022-08-01 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=es_CO:es TERM=xterm-256color PATH=(custom, no user) LANG=es_CO.UTF-8 SHELL=/bin/bash 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: 11/11/2021 dmi.bios.release: 1.38 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.38 dmi.board.asset.tag: NULL dmi.board.name: BOHB-WAX9-PCB-B2 dmi.board.vendor: HUAWEI dmi.board.version: M1080 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1080 dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnHUAWEI:bvr1.38:bd11/11/2021:br1.38:efr1.38:svnHUAWEI:pnBOHB-WAX9:pvrM1080:rvnHUAWEI:rnBOHB-WAX9-PCB-B2:rvrM1080:cvnHUAWEI:ct10:cvrM1080:skuC331: dmi.product.family: MateBook D dmi.product.name: BOHB-WAX9 dmi.product.sku: C331 dmi.product.version: M1080 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1983292/+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 1962135] Re: [SRU] gstreamer 1.16.3 series
This bug was fixed in the package gst-plugins-bad1.0 - 1.16.3-0ubuntu1 --- gst-plugins-bad1.0 (1.16.3-0ubuntu1) focal; urgency=medium * Updated to upstream 1.16.3 (LP: #1962135) - Remove debian/patches/pcfile-requires-plugins-good (upstreamed) - Updated gstreamer dependencies to 1.16.3 * Added 04_openexr_remove_override.patch which disables the C++ standard override check for some versions of openexr. Newer versions in focal have backported security patches which introduce a requirement for compiling with -std=c++11, rendering this check obsolete and causing a compile failure. -- Isaac True Wed, 02 Mar 2022 16:06:49 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962135 Title: [SRU] gstreamer 1.16.3 series Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 source package in Focal: Fix Released Status in gst-plugins-base1.0 source package in Focal: Fix Released Status in gst-plugins-good1.0 source package in Focal: Fix Released Status in gstreamer1.0 source package in Focal: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.16 series that 20.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2, though gstreamer has subsequent minor version gst-1.16.3 with fixes incorporated. Hence, Ideally default gstreamer-1.16 minor version support with ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+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 1962135] Re: [SRU] gstreamer 1.16.3 series
This bug was fixed in the package gst-plugins-good1.0 - 1.16.3-0ubuntu1 --- gst-plugins-good1.0 (1.16.3-0ubuntu1) focal; urgency=medium * New upstream stable release (LP: #1962135) -- Jeremy Bicha Tue, 01 Mar 2022 11:48:14 +0100 ** Changed in: gst-plugins-base1.0 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962135 Title: [SRU] gstreamer 1.16.3 series Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 source package in Focal: Fix Released Status in gst-plugins-base1.0 source package in Focal: Fix Released Status in gst-plugins-good1.0 source package in Focal: Fix Released Status in gstreamer1.0 source package in Focal: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.16 series that 20.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2, though gstreamer has subsequent minor version gst-1.16.3 with fixes incorporated. Hence, Ideally default gstreamer-1.16 minor version support with ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+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 1962135] Re: [SRU] gstreamer 1.16.3 series
This bug was fixed in the package gst-plugins-base1.0 - 1.16.3-0ubuntu1 --- gst-plugins-base1.0 (1.16.3-0ubuntu1) focal; urgency=medium * New stable version (lp: #1962135), requires gstreamer 1.16.3 -- Sebastien Bacher Tue, 01 Mar 2022 11:33:10 +0100 ** Changed in: gst-plugins-bad1.0 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962135 Title: [SRU] gstreamer 1.16.3 series Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 source package in Focal: Fix Released Status in gst-plugins-base1.0 source package in Focal: Fix Released Status in gst-plugins-good1.0 source package in Focal: Fix Released Status in gstreamer1.0 source package in Focal: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.16 series that 20.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2, though gstreamer has subsequent minor version gst-1.16.3 with fixes incorporated. Hence, Ideally default gstreamer-1.16 minor version support with ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+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 1962135] Re: [SRU] gstreamer 1.16.3 series
This bug was fixed in the package gstreamer1.0 - 1.16.3-0ubuntu1 --- gstreamer1.0 (1.16.3-0ubuntu1) focal; urgency=medium * New upstream stable release (LP: #1962135) - Drop patches 0001-Revert-device-Enforce-that-elements-created-by-gst_d and 0002-Revert-element-Enforce-that-elements-created-by-gst_ (applied upstream). -- Loïc Minier Tue, 01 Mar 2022 11:08:10 +0100 ** Changed in: gstreamer1.0 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: gst-plugins-good1.0 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962135 Title: [SRU] gstreamer 1.16.3 series Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 source package in Focal: Fix Released Status in gst-plugins-base1.0 source package in Focal: Fix Released Status in gst-plugins-good1.0 source package in Focal: Fix Released Status in gstreamer1.0 source package in Focal: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.16 series that 20.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2, though gstreamer has subsequent minor version gst-1.16.3 with fixes incorporated. Hence, Ideally default gstreamer-1.16 minor version support with ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+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 1962135] Update Released
The verification of the Stable Release Update for gstreamer1.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962135 Title: [SRU] gstreamer 1.16.3 series Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 source package in Focal: Fix Released Status in gst-plugins-base1.0 source package in Focal: Fix Released Status in gst-plugins-good1.0 source package in Focal: Fix Released Status in gstreamer1.0 source package in Focal: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.16 series that 20.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2, though gstreamer has subsequent minor version gst-1.16.3 with fixes incorporated. Hence, Ideally default gstreamer-1.16 minor version support with ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+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 1983417] Re: Bluetooth volume low on reconnection
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1983417 Title: Bluetooth volume low on reconnection Status in alsa-driver package in Ubuntu: New Bug description: How to reproduce: So as to start from a fresh base setting, restart Bluetooth service by opening up a terminal and typing: sudo service bluetooth restart Connect Bluetooth audio device (I'm using Xbox Wireless Headset) Adjust volume to maximum (non amplified) Disconnect Bluetooth audio device by turning it off Reconnect Bluetooth audio device and adjust volume back up to maximum (non amplified) if it has lowered automatically (I believe this is a known hearing safety feature) Notice the volume is lower than before even though it is set to maximum. Again, restart the Bluetooth service like before. Reconnect Bluetooth audio device and adjust volume back up to maximum (non amplified). Notice the volume is as high as it originally was. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eodeluga 1600 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 2 23:19:08 2022 InstallationDate: Installed on 2022-03-28 (127 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Xbox Wireless Headset Symptom_PulseAudioLog: Aug 02 23:15:03 tecra-z40-c-106 dbus-daemon[536]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.80" (uid=1000 pid=1600 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.14" (uid=0 pid=534 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Aug 02 23:15:03 tecra-z40-c-106 dbus-daemon[536]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.80" (uid=1000 pid=1600 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.14" (uid=0 pid=534 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [Xbox Wireless Headset, playback] volume slider problem UpgradeStatus: Upgraded to jammy on 2022-07-31 (2 days ago) dmi.bios.date: 06/20/2016 dmi.bios.release: 5.80 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 5.80 dmi.board.asset.tag: 00 dmi.board.name: TECRA Z40-C dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion5.80:bd06/20/2016:br5.80:efr1.20:svnTOSHIBA:pnTECRAZ40-C:pvrPT465E-00301QEN:rvnTOSHIBA:rnTECRAZ40-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:skuPT465E: dmi.product.family: 00 dmi.product.name: TECRA Z40-C dmi.product.sku: PT465E dmi.product.version: PT465E-00301QEN dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1983417/+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 1983417] [NEW] Bluetooth volume low on reconnection
You have been subscribed to a public bug: How to reproduce: So as to start from a fresh base setting, restart Bluetooth service by opening up a terminal and typing: sudo service bluetooth restart Connect Bluetooth audio device (I'm using Xbox Wireless Headset) Adjust volume to maximum (non amplified) Disconnect Bluetooth audio device by turning it off Reconnect Bluetooth audio device and adjust volume back up to maximum (non amplified) if it has lowered automatically (I believe this is a known hearing safety feature) Notice the volume is lower than before even though it is set to maximum. Again, restart the Bluetooth service like before. Reconnect Bluetooth audio device and adjust volume back up to maximum (non amplified). Notice the volume is as high as it originally was. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eodeluga 1600 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 2 23:19:08 2022 InstallationDate: Installed on 2022-03-28 (127 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Xbox Wireless Headset Symptom_PulseAudioLog: Aug 02 23:15:03 tecra-z40-c-106 dbus-daemon[536]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.80" (uid=1000 pid=1600 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.14" (uid=0 pid=534 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Aug 02 23:15:03 tecra-z40-c-106 dbus-daemon[536]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.80" (uid=1000 pid=1600 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.14" (uid=0 pid=534 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [Xbox Wireless Headset, playback] volume slider problem UpgradeStatus: Upgraded to jammy on 2022-07-31 (2 days ago) dmi.bios.date: 06/20/2016 dmi.bios.release: 5.80 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 5.80 dmi.board.asset.tag: 00 dmi.board.name: TECRA Z40-C dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion5.80:bd06/20/2016:br5.80:efr1.20:svnTOSHIBA:pnTECRAZ40-C:pvrPT465E-00301QEN:rvnTOSHIBA:rnTECRAZ40-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:skuPT465E: dmi.product.family: 00 dmi.product.name: TECRA Z40-C dmi.product.sku: PT465E dmi.product.version: PT465E-00301QEN dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- Bluetooth volume low on reconnection https://bugs.launchpad.net/bugs/1983417 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- 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 1845797]
This is still an issue; running pop_os with 5.18.15-051815-generic. -- 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/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+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 1261211]
Several kernels later and it still seems that randomly the port configuration works on boot and other times not. It seems like maybe a race condition after loading the DSP firmware? Maybe there needs to be a waiting period before resetting the device after the firmware download? There's code in there for other chipsets that seems to suggest that's happening elsewhere. -- 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/1261211 Title: No multichannel support on Creative CA0132 Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Multichannel sound is not working on my Creative CA0132 sound card. Stereo is working just fine but I cannot get 5.1 to work. when I run 'speaker-test -c 6' sound only comes out of the front 2 speakers and if I add '-Dsurround51' it returns "Channels count (6) not available for playbacks: Invalid argument". My alsa info http://www.alsa- project.org/db/?f=3a5ca77035da6be08769128daa43dcbc59badb93 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: somedude 1605 F lxpanel somedude 4927 F firefox /dev/snd/pcmC0D0p: somedude 4927 F...m firefox /dev/snd/timer: somedude 4927 f firefox Date: Sun Dec 15 15:58:33 2013 InstallationDate: Installed on 2013-12-15 (0 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: Z87 Professional 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.:bvrP1.50:bd07/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Professional: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/alsa-driver/+bug/1261211/+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 1958019]
The Lenovo Legion 7i Gen 7 (2022) model is now available in the USA: https://www.lenovo.com/us/en/p/laptops/legion-laptops/legion-7-series/legion-7i-gen-7-(16-inch-intel)/len101g0018 If you have one of these laptops, please share your alsa-info here. I strongly suspect it has Cirrus Logic cs35l41 amplifier chips in it. Hopefully the more generic approaches will work here (such as cs35l41_fixup_i2c_two()). -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
https://mailman.alsa-project.org/pipermail/alsa- devel/2022-July/204315.html The patch has been applied by a 'SOUND' subsystem maintainer. It will probably be merged in the next merge window (Linux 5.20). You can see the entry for the 'model' parameter in the 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
A note on the 'model' and 'patch' options of of the 'snd_hda_intel' module. The 'model' option can be used to apply a fixup written for another device. You can check the fixups available for the ALC287 in the docs or in the 'alc269_fixup_models' array at sound/pci/hda/pathch_realtek.c:9551. See https://www.kernel.org/doc/html/latest/sound/hd-audio/notes.html#model-option The 'patch' option is similar, but way more powerful. I used it to try a lot of configurations before I got the sound working. See https://www.kernel.org/doc/html/latest/sound/hd-audio/notes.html#early-patching I'd like to see the patch merged so people with devices for which the fixup might work can try the module option instead of compiling a patched kernel. Something along the lines of --- # /etc/modprobe.d/snd.conf # use snd_hda_intel instead of snd_sof options snd_intel_dspcfg dsp_driver=1 # enable the fixup options snd_hda_intel model=alc287-yoga9-bass-spk-pin --- should then work to apply the fixup until a PCI_QUIRK is added. I'll give an update when I know when it's going mainline. There were actually three problems with the bass speakers on the Lenovo Yoga9 14IAP7: 1. The Pin Complex node of the codec with NID 0x17 on which the bass speakers are connected reported itself as unconnected. 2. The bass speakers have amplifiers which need to be enabled via NID 0x20 of the codec. (similar to the Lenovo Yoga 7 14ITL5 fixup) 3. The driver connected the bass speaker Pin Complex to the DAC on NID 0x06 of the codec which has no volume control. (bass speakers always on max volume) You can check whether your device is affected by problem 1 by checking the 'Pin Default' on 'Node 0x17' in the 'HDA-Intel Codec information' in your alsa-info.txt. e.g. $ grep -A6 'Node 0x17' < alsa-info.txt A 'Pin Default' that starts with 0x4, 0x5, 0x6 or 0x7 indicates and unconnected pin and thus problem 1 assuming the bass speakers are really on NID 0x17 on your device. If your device is not affected by problem 1, the mainline fixes for the 'Yoga 7 ITL5' or 'Legion 7i' might already work. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sy
[Touch-packages] [Bug 1958019]
Created attachment 301503 attachment-965-0.html Feel sorry to hear that. Is that because your machine is not an Intel cpu? i'm just wondering..(i'm not an expert) On Thu, Jul 28, 2022 at 8:32 PM wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > durbg...@gmail.com changed: > >What|Removed |Added > > > CC||durbg...@gmail.com > > --- Comment #672 from durbg...@gmail.com --- > (In reply to cris223 from comment #665) > > tested linux-mainline v5.19-rc7 --Works perfect! > > here is the github link: > > > > https://github.com/322sirc/linux-mainline > > > > For everyone new: you have to change your config file according to your > > machine kernel modules (unless you use the original one) and modify the > > patch with your machine sound card Subsystem Id: 0x17aa38XX (easily found > > info in /proc/asound/card0)in bottomspeakers-for-14iap7-kernel*.patch on > > line 169 and line 311. > > > > I'll make an update on my github for linux-xanmod-edge too. > > I tested this on the Lenovo Carbon 14ACN6 and it did not appear to work. > Card0 > is a digital and card has subsystem ID 0x17aa3856, which is what I updated > in > the patch file. > > -- > You may reply to this email to add a comment. > > You are receiving this mail because: > You are on the CC list for the bug. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
Created attachment 301501 attachment-17412-0.html I would vote for it 100%! For sure this patch becoming a module in the next kernel release would help not only Lenovo machines with this kind of audio hardware. On Thu, Jul 28, 2022 at 11:00 AM wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #668 from Philipp Jungkamp (p.jungk...@gmx.net) --- > I'd prefer to submit my patch as soon as possible myself to have the > fixup/quirk mainlined. Other people can then just use a module parameter to > enable the patch and check if it works properly for their devices. You can > then > submit the 'PCI_QUIRK' line for your hardware yourself. The module > parameter > should be an acceptable tradeoff until other devices' quirk lines are > mainlined. > > -- > You may reply to this email to add a comment. > > You are receiving this mail because: > You are on the CC list for the bug. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
(In reply to cris223 from comment #665) > tested linux-mainline v5.19-rc7 --Works perfect! > here is the github link: > > https://github.com/322sirc/linux-mainline > > For everyone new: you have to change your config file according to your > machine kernel modules (unless you use the original one) and modify the > patch with your machine sound card Subsystem Id: 0x17aa38XX (easily found > info in /proc/asound/card0)in bottomspeakers-for-14iap7-kernel*.patch on > line 169 and line 311. > > I'll make an update on my github for linux-xanmod-edge too. I tested this on the Lenovo Carbon 14ACN6 and it did not appear to work. Card0 is a digital and card has subsystem ID 0x17aa3856, which is what I updated in the patch file. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
@Philipp Why not submit all the patches from this thread? So it's easier for the maintainers of the kernel and there will be more devices supported by default in the future if somebody installs Linux on his Lenovo device. To be honest I wouldn't even know how to submit a patch, I just learned compiling a kernel...I would really appreciate your help with this. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
That sounds good. I hadn't thought of the possibility of a module option. I haven't submitted any patches myself and suggested sending several PCI_QUIRKs together (at least the ones identified in this thread for Yoga 9i 14IAP7) because I don't know the delays involved in the submission process.. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
I'd prefer to submit my patch as soon as possible myself to have the fixup/quirk mainlined. Other people can then just use a module parameter to enable the patch and check if it works properly for their devices. You can then submit the 'PCI_QUIRK' line for your hardware yourself. The module parameter should be an acceptable tradeoff until other devices' quirk lines are mainlined. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1315559] Re: UpgradeStatus can be incorrect
** Tags added: rls-kk-incoming
--
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/1315559
Title:
UpgradeStatus can be incorrect
Status in apport package in Ubuntu:
Confirmed
Bug description:
In the general hook for ubuntu there is the following code:
log = '/var/log/dist-upgrade/main.log'
if os.path.exists(log):
mtime = os.stat(log).st_mtime
human_mtime = time.strftime('%Y-%m-%d', time.gmtime(mtime))
delta = time.time() - mtime
# Would be nice if this also showed which release was originally
installed
report['UpgradeStatus'] = 'Upgraded to %s on %s (%d days ago)' %
(release_codename, human_mtime, delta / 86400)
else:
report['UpgradeStatus'] = 'No upgrade log present (probably fresh
install)'
This does no checking of main.log to see if the upgrade was actually
successful, so if someone is reporting a bug about a failed upgrade of
ubuntu-release-upgrader they'll have a confusing 'UpgradeStatus' of
today for the previous release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1315559/+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 1982545] Re: FTBFS on riscv64
** Changed in: curl (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1982545 Title: FTBFS on riscv64 Status in curl package in Ubuntu: New Status in curl package in Debian: New Bug description: As can be seen here [1], the build on riscv64 fails now that we use gcc12 with the following error: libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Werror-implicit-function-declaration -Wno-system-headers -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/curl slist_wc.o tool_binmode.o tool_bname.o tool_cb_dbg.o tool_cb_hdr.o tool_cb_prg.o tool_cb_rea.o tool_cb_see.o tool_cb_wrt.o tool_cfgable.o tool_dirhie.o tool_doswin.o tool_easysrc.o tool_filetime.o tool_findfile.o tool_formparse.o tool_getparam.o tool_getpass.o tool_help.o tool_helpers.o tool_hugehelp.o tool_libinfo.o tool_listhelp.o tool_main.o tool_msgs.o tool_operate.o tool_operhlp.o tool_panykey.o tool_paramhlp.o tool_parsecfg.o tool_progress.o tool_strdup.o tool_setopt.o tool_sleep.o tool_urlglob.o tool_util.o tool_vms.o tool_writeout.o tool_writeout_json.o tool_xattr.o ../lib/strtoofft.o ../lib/timediff.o ../lib/nonblock.o ../lib/warnless.o ../lib/curl_ctype.o ../lib/curl_multibyte.o ../lib/version_win32.o ../lib/dynbuf.o ../lib/.libs/libcurl.so -lssl -lcrypto -lz /usr/bin/ld: ../lib/.libs/libcurl.so: undefined reference to `__atomic_exchange_1' collect2: error: ld returned 1 exit status make[4]: *** [Makefile:991: curl] Error 1 There exists a bug report and a fix for that upstream here: https://github.com/curl/curl/pull/9061 I'm currently building a package with this patch here [2]. [1] https://launchpadlibrarian.net/612746451/buildlog_ubuntu-kinetic-riscv64.curl_7.84.0-2_BUILDING.txt.gz [2] https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13822857/+listing-archive-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1982545/+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 1983414] [NEW] [BPO] dh-python 5.20220403 to focal
Public bug reported: [Impact] * This is needed to refresh the yt-dlp package as it has support for 'environment markers' * This version could also be useful for other projects as it adds support for pyproject. [Scope] Backport from: * To me it makes sense to backport from jammy (LTS), though the version currently is the same as devel. Backport to: * focal [Other Info] * I have created a test backport in ppa:unit193/staging and have already utilized. [Testing] * focal: [x] Package builds without modification [x] dh-python installs cleanly and runs [?] pybuild-plugin-pyproject installs cleanly and runs ** Affects: dh-python (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1983414 Title: [BPO] dh-python 5.20220403 to focal Status in dh-python package in Ubuntu: New Bug description: [Impact] * This is needed to refresh the yt-dlp package as it has support for 'environment markers' * This version could also be useful for other projects as it adds support for pyproject. [Scope] Backport from: * To me it makes sense to backport from jammy (LTS), though the version currently is the same as devel. Backport to: * focal [Other Info] * I have created a test backport in ppa:unit193/staging and have already utilized. [Testing] * focal: [x] Package builds without modification [x] dh-python installs cleanly and runs [?] pybuild-plugin-pyproject installs cleanly and runs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1983414/+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 1980836] Re: Regression in Ubuntu 22.04: Content of form field stored invisibly
** Changed in: poppler Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1980836 Title: Regression in Ubuntu 22.04: Content of form field stored invisibly Status in Poppler: Fix Released Status in evince package in Ubuntu: Invalid Status in poppler package in Ubuntu: Triaged Bug description: Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly anymore that it was able to handle on Ubuntu 21.10 and on Ubuntu 20.04. The symptom is that one can edit the form content and also save it, but that the entered text is only visible when the form field is focused and in edit mode. Otherwise the text it is invisible, also on printouts. Such bugs have been reported against Evince for a long time (e.g., https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/265033) but I am reporting this as a new bug because for the current form with which I am experiencing this it is a regression. I have attached the problematic form with two form fields filled out, one in the upper left corner and the big one in the lower half. I have produced this by taking the original, empty form (produced by somebody else) and first opened it in Evince 41.4, which I have installed from the snap package (revision 1017) on Ubuntu 22.04. I entered text in the upper left field and saved the form. Then I opened the PDF in Evince 42.3 from the apt package of Ubuntu 22.04 and entered text in the big field and saved the form. Evince 3.36 on Ubuntu 20.04 has the same (correct) behavior as Evince 41.4. When I open the PDF again, only the text in the first field is visible. The text in the second field is visible only if I click into the field. The visibility of the field contents is the same for Evince 41.4 (snap), Evince 42.3 (apt), and Okular 20.12.3 (snap). So it seems that the problem is with Evince 42.3 incorrectly saving the field content, not with displaying it. Firefox shows and prints the content of both fields, though. Note that I cannot switch back to Evince 41 because for some other forms that I have the exact same problem happens only with the old version and the new version fixes it. So it seems that something changed that fixed it for some forms and broke it for others. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:32:27 2022 InstallationDate: Installed on 2021-11-26 (222 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: ID Status Spawn Bereit Zusammenfassung 137 Done2022-07-06T12:48:33+02:00 2022-07-06T12:48:41+02:00 Installiere "evince" Snap SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-06-22 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1980836/+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 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible
I just used tar as I manually did it and not any tool such as dracut or initramfs-tools. You can probably just use file-roller if you don't know how to unpack the file. I'm on my phone on vacation so don't have it in front of me right now. On August 2, 2022 5:51:09 PM GMT+02:00, John Doe <1950...@bugs.launchpad.net> wrote: >Hey Tommy, I'm in a similar boot to Frederick. >Thanks for taking the time to list your steps. >What command did you use to unpack your initrd? >After copying over the drivers what command or tool did you use to repack it? >Was it dracut, initramfs-tools, or something else entirely? > >Thanks again! > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1950996 > >Title: > Missing all modules for usb nics in initrd which makes PXE boot > impossible > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950996/+subscriptions > -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1950996 Title: Missing all modules for usb nics in initrd which makes PXE boot impossible Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Confirmed Status in initramfs-tools source package in Hirsute: Confirmed Status in initramfs-tools source package in Impish: Won't Fix Status in initramfs-tools source package in Jammy: Fix Released Status in initramfs-tools package in Debian: Unknown Bug description: initrd taken from the live iso for PXE boot does not contain USB NIC drivers which makes PXE installation/netboot impossible via usb. This is the case on 20.04 server iso (both hwe and normal kernel/initrd) and desktop iso. "kernel/drivers/net/usb" is empty and needs to be included in the initramfs build. As most modern thin laptops lack physical rj45 ethernet this is a big issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18 Uname: Linux 5.8.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 16:47:45 2021 PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to focal on 2020-05-11 (552 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950996/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1924251 ** Tags added: iso-testing -- 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/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: On the hirsute Pi desktop, under a wayland session with the "full" KMS overlay enabled, and "kms-modifiers" present in the org.gnome.mutter/experimental-features, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible
Hey Tommy, I'm in a similar boot to Frederick. Thanks for taking the time to list your steps. What command did you use to unpack your initrd? After copying over the drivers what command or tool did you use to repack it? Was it dracut, initramfs-tools, or something else entirely? Thanks again! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1950996 Title: Missing all modules for usb nics in initrd which makes PXE boot impossible Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Confirmed Status in initramfs-tools source package in Hirsute: Confirmed Status in initramfs-tools source package in Impish: Won't Fix Status in initramfs-tools source package in Jammy: Fix Released Status in initramfs-tools package in Debian: Unknown Bug description: initrd taken from the live iso for PXE boot does not contain USB NIC drivers which makes PXE installation/netboot impossible via usb. This is the case on 20.04 server iso (both hwe and normal kernel/initrd) and desktop iso. "kernel/drivers/net/usb" is empty and needs to be included in the initramfs build. As most modern thin laptops lack physical rj45 ethernet this is a big issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18 Uname: Linux 5.8.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 16:47:45 2021 PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to focal on 2020-05-11 (552 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950996/+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 1923893] Re: After rescheduling an event, calendar alerts appear for the old time
This continues to be an issue in 22.04. ** Tags removed: impish ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1923893 Title: After rescheduling an event, calendar alerts appear for the old time Status in evolution-data-server: New Status in evolution-data-server package in Ubuntu: Confirmed Bug description: I use google calendar. Events are created and updated via the browser. The calendar feed is configured through settings/online accounts. I can see upcoming events in the calendar drop down. The calendar and desktop are configured for the same timezone, and alerts normally appear simultaneously on my phone and desktop. I know sometimes stale calendar entries can be a factor, but I don't *think* that's an issue at this time (the change was made almost 24 hours ago, I don't see the API limit errors I used to see in logs). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 15:02:11 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (666 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-49-generic linux-base RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1923893/+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 1982086] Re: package linux-image-5.4.0-1080-aws 5.4.0-1080.87 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1982086 Title: package linux-image-5.4.0-1080-aws 5.4.0-1080.87 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Ubuntu 18 to 20 version update failed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-1080-aws 5.4.0-1080.87 ProcVersionSignature: Ubuntu 5.4.0-1081.88~18.04.1-aws 5.4.192 Uname: Linux 5.4.0-1081-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jul 19 07:33:31 2022 Ec2AMI: ami-04a019398ef05fc20 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2b Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.4.0-1080-aws 5.4.0-1080.87 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to focal on 2022-07-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1982086/+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 1982086] Re: package linux-image-5.4.0-1080-aws 5.4.0-1080.87 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
I'm seeing the same thing just trying to update via apt update && apt upgrade -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1982086 Title: package linux-image-5.4.0-1080-aws 5.4.0-1080.87 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Ubuntu 18 to 20 version update failed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-1080-aws 5.4.0-1080.87 ProcVersionSignature: Ubuntu 5.4.0-1081.88~18.04.1-aws 5.4.192 Uname: Linux 5.4.0-1081-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jul 19 07:33:31 2022 Ec2AMI: ami-04a019398ef05fc20 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2b Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.4.0-1080-aws 5.4.0-1080.87 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to focal on 2022-07-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1982086/+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 1703821] Re: Dovecot and Apparmor complains at operation file_inherit
** Description changed: [Impact] Users report that while running dovecot there are some issues reported by AppArmor, specifically regarding "file_inherit" operations: Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400 audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit" profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/sbin/dovecot" Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400 audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit" profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/lib/dovecot/anvil" This is likely caused by an anonymous socket communication channel between dovecot and anvil. A fix in the dovecot AppArmor policy was already merged upstream in commit 1ce8cd21, which is being backported in this SRU. There was a change upstream that renamed the dovecot profile, so it was necessary to make a small change on the backport to reference the correct profile name. [Test Plan] - The bug can be reproduced by setting up a multi-purpose VM according - to the README file on QRT, and then running the QRT dovecot tests. + Clone the qa-regression-testing repo + https://git.launchpad.net/qa-regression-testing + Setup the machine according to the instructions in the README.multipurpose-vm - specifically the Email section. + + Run the dovecot tests from the qa-regression-testing repo: + python3 ./script test-dovecot.py + + After running the tests, check dmesg for no DENIED messages: + dmesg | grep DENIED [Where problems could occur] This update broadens the dovecot policy, so it won't to cause any issues regarding a behavior that was previously allowed and it is now denied. In addition, the dovecot policy is already in complain mode in bionic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1703821 Title: Dovecot and Apparmor complains at operation file_inherit Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Expired Status in dovecot package in Ubuntu: Fix Released Status in apparmor source package in Bionic: New Status in dovecot source package in Bionic: Fix Released Bug description: [Impact] Users report that while running dovecot there are some issues reported by AppArmor, specifically regarding "file_inherit" operations: Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400 audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit" profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/sbin/dovecot" Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400 audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit" profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/lib/dovecot/anvil" This is likely caused by an anonymous socket communication channel between dovecot and anvil. A fix in the dovecot AppArmor policy was already merged upstream in commit 1ce8cd21, which is being backported in this SRU. There was a change upstream that renamed the dovecot profile, so it was necessary to make a small change on the backport to reference the correct profile name. [Test Plan] Clone the qa-regression-testing repo https://git.launchpad.net/qa-regression-testing Setup the machine according to the instructions in the README.multipurpose-vm - specifically the Email section. Run the dovecot tests from the qa-regression-testing repo: python3 ./script test-dovecot.py After running the tests, check dmesg for no DENIED messages: dmesg | grep DENIED [Where problems could occur] This update broadens the dovecot policy, so it won't to cause any issues regarding a behavior that was previously allowed and it is now denied. In addition, the dovecot policy is already in complain mode in bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1703821/+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 1983292] Re: No sound from laptop speakers with Ubuntu 22.04 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1983292 Title: No sound from laptop speakers with Ubuntu 22.04 LTS Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have sound through bluetooth devices and external headphones but I cannot get sound output from my laptop speakers, at the begining I had "Dummy sound" as the only output device, after some modifications now the default device is HDMI/Display Port but still with no sound , My laptop is a HUAWEI MateBook D15 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: felipe 1485 F pulseaudio /dev/snd/pcmC0D3p: felipe 1485 F...m pulseaudio CasperMD5CheckResult: pass Date: Mon Aug 1 17:30:03 2022 InstallationDate: Installed on 2022-08-01 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=es_CO:es TERM=xterm-256color PATH=(custom, no user) LANG=es_CO.UTF-8 SHELL=/bin/bash 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: 11/11/2021 dmi.bios.release: 1.38 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.38 dmi.board.asset.tag: NULL dmi.board.name: BOHB-WAX9-PCB-B2 dmi.board.vendor: HUAWEI dmi.board.version: M1080 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1080 dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnHUAWEI:bvr1.38:bd11/11/2021:br1.38:efr1.38:svnHUAWEI:pnBOHB-WAX9:pvrM1080:rvnHUAWEI:rnBOHB-WAX9-PCB-B2:rvrM1080:cvnHUAWEI:ct10:cvrM1080:skuC331: dmi.product.family: MateBook D dmi.product.name: BOHB-WAX9 dmi.product.sku: C331 dmi.product.version: M1080 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1983292/+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 1983128] Re: linux-lowlatency fals to build on arm64 due to kernel option settings
So yes, this is a new feature / kernel option for (arm only) introduced with
the migration to gcc 12:
[v3,1/2] AARCH64: Add gcc Shadow Call Stack support
https://patchwork.kernel.org/project/linu
x-hardening/patch/20220303074323.86282-1-ashim...@linux.alibaba.com/#24774364
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1983128
Title:
linux-lowlatency fals to build on arm64 due to kernel option settings
Status in linux-lowlatency package in Ubuntu:
New
Status in zlib package in Ubuntu:
New
Bug description:
The 'linux-lowlatency' kernel build (incl. autopkgtest) was triggered in a
kinetic-proposed migration process (for zlib) and runs into a 'regression':
"autopkgtest for linux-lowlatency/5.19.0-1001.1: amd64: Pass, arm64:
Regression ♻"
The regression is highly likely not due to zlib itself, but due to NEW kernel
options, that don't have a default yet and a check-config FAIL, see:
...
check-config:
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian/build/build-lowlatency/.config:
loading config
check-config:
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian.lowlatency/config/annotations
loading annotations
check-config: FAIL (n != -): CONFIG_KCOV policy<{'amd64': 'n', 'arm64':
-, 'armhf': 'n', 'ppc64el': '-', 'riscv64': 'n', 's390x': '-'}>
check-config: 11323/11324 checks passed -- exit 1
...
Shadow Call Stack (SHADOW_CALL_STACK) [N/y/?] (NEW)
Error in reading or end of file.
...
Initialize kernel stack variables at function entry
> 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE)
2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) (NEW)
3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) (NEW)
choice[1-3?]:
Error in reading or end of file.
...
Full log is here:
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/l/linux-lowlatency/20220728_135536_c2061@/log.gz
(this might be caused by the recent compiler update)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1983128/+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
