[Touch-packages] [Bug 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all
I have the same problem with a ThinkBook 13x Gen 2 with Ubuntu 23.04. The sound works properly when connecting external speakers or headset, but I couldn't get the internal speakers to work :( This laptop also has an ALC287/3306 chip with a CS35L41/CSC3551 amplifier. This seems very similar what is mentioned here: https://gist.github.com/lamperez/862763881c0e1c812392b5574727f6ff?permalink_comment_id=4526397 journalctl displays the following message: "Error: ACPI _DSD Properties are missing for HID CSC3551". I tried it with the base kernel (6.2.0) as well as the latest one (6.3.3). The issue occurs regarless of the BIOS version (factory version: HXCN49WW and 20230517 version: HXCN52WW). I used the ACPICA tools to extract the ACPI tables and noticed the entries relative to the CSC3551 did not contain the required "cirrus" and "dev-index" parameters. This is quite disapointing and I will juste return the laptop to Lenovo. -- 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 1992454] Re: iptables: segfault when renaming a chain
These new DEP8 failures are now also cleared. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1992454 Title: iptables: segfault when renaming a chain Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Bionic: Fix Committed Status in iptables source package in Focal: Fix Committed Status in iptables source package in Jammy: Fix Committed Status in iptables source package in Kinetic: Fix Committed Bug description: [ Impact ] * An explanation of the effects of the bug on users This is the description for the upstream fix of this bug[1] : This is an odd bug: If the number of chains is right and one renames the last one in the list, libiptc dereferences a NULL pointer. * justification for backporting the fix to the stable release. Without this patch, users may experience segmentation fault when using the following versions of iptables : - Bionic : iptables - Focal : iptables - Jammy : iptables-legacy - Kinetic: iptables-legacy * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. The upstream fix adjust the size of the chain_index if the element is the last chain in the list. [1] http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f [ Test Plan ] * detailed instructions how to reproduce the bug The following code (adapted from the upstream commit to work on Kinetic) may be used to reproduce the issue : 8< #!/bin/bash # # Cover for a bug in libiptc: # - the chain 'node-98-tmp' is the last in the list sorted by name # - there are 81 chains in total, so three chain index buckets # - the last index bucket contains only the 'node-98-tmp' chain # => rename temporarily removes it from the bucket, leaving a NULL bucket # behind which is dereferenced later when inserting the chain again with new # name again ( echo "*filter" for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 node-92 node-93 node-95 node-98-tmp; do echo ":$chain - [0:0]" done echo "COMMIT" ) | $XT_MULTI iptables-legacy-restore $XT_MULTI iptables-legacy -E node-98-tmp node-98 exit $? >8 Alternatively, this test has been added to the DEP8 list of tests, and will be executed automatically once the package is accepted into proposed. The DEP8 logs can be inspected for its run. Look for a test named "0006rename-segfault". [ Where problems could occur ] For Jammy and onward, only users of the -legacy commands may be affected. Since Jammy, iptables uses the new nft libraries which are not affected by the bug. For Bionic and Focal users, the regular iptables command is affected by the change. As stated in the manpage : E, --rename-chain old-chain new-chain Rename the user specified chain to the user supplied name. This is cosmetic, and has no effect on the structure of the table. In case of a problem, only the modification of the name would be affected as this is clearly outlined as a cosmetic only change. [ Other Info ] The patch is also applied to lunar and mantic, but is fixed in upstream's 1.8.9 release which so far is only in debian testing/unstable. This is being uploaded together with test fixes from bug #1992454 (bionic-specific) and bug #2019023 (focal-specific), which were found and fixed while trying out the DEP8 runs for this package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+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 2020251] [NEW] cannot install both libcurl4-gnutls-dev x64 and i386
Public bug reported: sudo aptitude install libcurl4-gnutls-dev:i386 The following NEW packages will be installed: libcurl4-gnutls-dev:i386 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/455 kB of archives. After unpacking 1653 kB will be used. Selecting previously unselected package libcurl4-gnutls-dev:i386. (Reading database ... 66367 files and directories currently installed.) Preparing to unpack .../libcurl4-gnutls-dev_7.88.1-9ubuntu1_i386.deb ... Unpacking libcurl4-gnutls-dev:i386 (7.88.1-9ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libcurl4-gnutls-dev_7.88.1-9ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/bin/curl-config', which is different from other instances of package libcurl4-gnutls-dev:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libcurl4-gnutls-dev_7.88.1-9ubuntu1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libcurl4-gnutls-dev:i386 7.88.1-9ubuntu1 Uname: Linux 5.15.90.1-microsoft-standard-WSL2 x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat May 20 18:01:39 2023 PackageArchitecture: i386 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: curl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 mantic wayland-session -- 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/2020251 Title: cannot install both libcurl4-gnutls-dev x64 and i386 Status in curl package in Ubuntu: New Bug description: sudo aptitude install libcurl4-gnutls-dev:i386 The following NEW packages will be installed: libcurl4-gnutls-dev:i386 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/455 kB of archives. After unpacking 1653 kB will be used. Selecting previously unselected package libcurl4-gnutls-dev:i386. (Reading database ... 66367 files and directories currently installed.) Preparing to unpack .../libcurl4-gnutls-dev_7.88.1-9ubuntu1_i386.deb ... Unpacking libcurl4-gnutls-dev:i386 (7.88.1-9ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libcurl4-gnutls-dev_7.88.1-9ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/bin/curl-config', which is different from other instances of package libcurl4-gnutls-dev:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libcurl4-gnutls-dev_7.88.1-9ubuntu1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libcurl4-gnutls-dev:i386 7.88.1-9ubuntu1 Uname: Linux 5.15.90.1-microsoft-standard-WSL2 x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat May 20 18:01:39 2023 PackageArchitecture: i386 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: curl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2020251/+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 1876237] Re: QDesktopServices::openUrl() fails when called on local files from within a snap
This bug was fixed in the package qtbase-opensource-src - 5.15.9+dfsg-2 --- qtbase-opensource-src (5.15.9+dfsg-2) experimental; urgency=medium * Bump years for 3rdparty copyright. * Backport upstream patch to stop using O_PATH in OpenFile portal (LP: #1876237). * Add a patch to fix capitalization error in auto-generated qdbusmacros.h include (LP: #2016703). * Make qtbase5-private-dev suggest packages providing includes which are used by some of its headers (closes: #1034830). -- Dmitry Shachnev Sat, 13 May 2023 18:27:14 +0300 ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1876237 Title: QDesktopServices::openUrl() fails when called on local files from within a snap Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: This is something we might want to fix to help people who build snaps based on Focal's Qt. The QGenericUnixServices implementation of openUrl() passes an O_PATH file descriptor to xdg-desktop-portal when it detects it is running under snap confinement. This is rejected because xdg-desktop-portal expects an O_RDONLY file descriptor, leading to the operation failing. More details are available in the upstream bug report I filed: https://bugreports.qt.io/browse/QTBUG-83939 This originated from a report on the Snapcraft forum here: https://forum.snapcraft.io/t/xdg-open-or-gvfs-open-qdesktopservices- openurl-file-somelocation-file-txt-wont-open-the-file/16824?u=jamesh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1876237/+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 2016703] Re: qbusmacros.h fails to compile: wrong case on case-sensitive include
This bug was fixed in the package qtbase-opensource-src - 5.15.9+dfsg-2 --- qtbase-opensource-src (5.15.9+dfsg-2) experimental; urgency=medium * Bump years for 3rdparty copyright. * Backport upstream patch to stop using O_PATH in OpenFile portal (LP: #1876237). * Add a patch to fix capitalization error in auto-generated qdbusmacros.h include (LP: #2016703). * Make qtbase5-private-dev suggest packages providing includes which are used by some of its headers (closes: #1034830). -- Dmitry Shachnev Sat, 13 May 2023 18:27:14 +0300 ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/2016703 Title: qbusmacros.h fails to compile: wrong case on case-sensitive include Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: /usr/include/arm-linux-gnueabihf/qt5/QtDBus/qdbusmacros.h in qtbase5-dev cannot compile: /usr/include/arm-linux-gnueabihf/qt5/QtDBus/qdbusmacros.h:8:10: fatal error: QtDbus/qtdbusglobal.h: No such file or directory 8 | #include | ^~~ compilation terminated. The correct filename is , not . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2016703/+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 1260172] Re: translation in Italian
** Changed in: gnupg (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1260172 Title: translation in Italian Status in gnupg package in Ubuntu: Fix Released Bug description: Translation in Italian is complete but I don't know how I can send it upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1260172/+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 2018538] Re: All PDFs when printed come out mirror image
Could you attach your print queue's PPD file(s), from /etc/cups/ppd/? Please do not compress the files, nor package them together. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2018538 Title: All PDFs when printed come out mirror image Status in cups package in Ubuntu: Confirmed Bug description: Since updating to Ubuntu 23.04. Whenever I try to print a PDF (regardless of application the PDF is open in) it will print the PDF in mirror image. If I enable printing mirror image in the settings, every other page become mirror image as instead. (I'm printing double sided/long edge print, so one side is normal and the other side becomes mirror image when I do this). I'm trying to print to a HP Colour LaserJet CP2025dn Note: If I print from my second device when it was running Ubuntu 22.10 it would print normally, but as soon as I updated it to 23.04, it started having the same issue as well. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:31:48 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+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
