[Touch-packages] [Bug 1998040] [NEW] srtsink and srtsrc are missing
Public bug reported: Although gstreamer1.0-plugins-bad_1.20.3-1ubuntu6 is compiled against libsrt1.5-gnutls, the related srt gstreamer bad plugins are not available (i.e. srtsink, srtsrc, srtserversink, srtserversrc, etc.). ~$ gst-inspect-1.0 srtsink No such element or plugin 'srtsink' ** Affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: kinetic ** Tags added: kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998040 Title: srtsink and srtsrc are missing Status in gst-plugins-bad1.0 package in Ubuntu: New Bug description: Although gstreamer1.0-plugins-bad_1.20.3-1ubuntu6 is compiled against libsrt1.5-gnutls, the related srt gstreamer bad plugins are not available (i.e. srtsink, srtsrc, srtserversink, srtserversrc, etc.). ~$ gst-inspect-1.0 srtsink No such element or plugin 'srtsink' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1998040/+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 1996619] Re: Setfont error due to deprecated PIO_FONTX ioctl
This bug was fixed in the package kbd - 2.5.1-1ubuntu1 --- kbd (2.5.1-1ubuntu1) lunar; urgency=medium * Merge from Debian unstable. Remaining changes: - Add setfont, kbd_mode, and loadkeys to initramfs for console-setup. - Added initramfs hook to have setfont/loadkeys available in initramfs. - Use ckbcomp to get the keyboard layout if other data files are not available. - Change loadkeys to find any console not in raw mode when invoked without an explicit console parameter, in case the foreground console is in raw mode. - Add setvtrgb to kbd-udeb. - Fix incorrect keymap sanity check in loadkeys_ckbcomp.diff. - debian/control: Depend on console-setup | console-setup-mini, since console-setup-mini also Depends on kbd now through console-setup-linux. - debian/patches/loadkeys_find_usable_console.diff: fix wrong type argument to ioctl(..., KDGKBMODE), which causes consoles to not be correctly detected on 64-bit archs. LP: #1621824. * Removed obsolete patches/changes: - d/p/fix_use_after_free.patch to clean up a use-after-free of pipe_cmd, now merged upstream. * New upstream release drops deprecated ioctls removed in Linux v5.12. LP: #1996619. kbd (2.5.1-1) unstable; urgency=medium * Team upload. [ Andreas Henriksson ] * New upstream release. * Unfuzz debian/patches/Miscellaneous-manpage-corrections-and-additions.patch * Unfuzz debian/patches/Check-for-X-in-kbd_mode.patch * Revert "Cherry-pick no install libtswrap internal library" * Let `gbp pq ` refresh patches * Bump debhelper from old 10 to 13. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit. * debian/copyright: Update paths of moved files [ nick black ] * refer to deallocvt(8), not disalloc(8) (Closes: #989525) [ Osamu Aoki ] * update d/control for console-setup (Closes: #998086) -- dann frazier Tue, 15 Nov 2022 17:21:19 -0700 ** Changed in: kbd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1996619 Title: Setfont error due to deprecated PIO_FONTX ioctl Status in subiquity: New Status in kbd package in Ubuntu: Fix Released Status in kbd source package in Jammy: New Bug description: There is an error message that get thrown in in syslog. There is a suggestion to fix by upgrading the KDB package to version 2.5.1+ or to understand the root cause and troubleshoot as to why it's broken and resolve it there. It is caused by this line in subiquity https://github.com/canonical/subiquity/blob/46f671d14d57a5da6bc3d60b1da6715b43954f0d/bin/subiquity-service#L11 It's due to PIO_FONTX ioctl removed from kernel since 5.12 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff2047fb755d4415ec3c70ac799889371151796d In 2.4.5 of kbd which provide setfont in user space, they already switched over to use KDFONTOP only. ### REPRODUCER STEPS ### # install libvirt sudo apt install qemu qemu-kvm libvirt-clients libvirt-daemon-system virtinst bridge-utils sudo systemctl enable libvirtd sudo systemctl start libvirtd # check libvirtd process is running virsh virsh list # get iso wget https://releases.ubuntu.com/22.04/ubuntu-22.04.1-live-server-amd64.iso # install vm sudo virt-install --cdrom='./ubuntu-22.04.1-live-server-amd64.iso' --name=setfont-repo --vcpus=2 --memory=2048 --disk size=20 --serial pty --graphics none --boot=uefi --debug # you can either do the full install, the error will be in the /var/log/installer.log file # or on the first page of the installer press Tab-> go to Help, -> Shell and cd /var/log/ grep setfont* syslog # to show error message cd to /snap/subiquity/3698 #execute setfont $SNAP/subiquity.psf # error root@ubuntu-server:/snap/subiquity/3698# setfont $SNAP/subiquity.psf setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device # grep grep setfont* syslog Nov 14 18:22:11 ubuntu-server console-setup.sh[1107]: setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device Nov 14 18:22:29 ubuntu-server subiquity.subiquity-service[1878]: setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1996619/+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 1998001] Re: Missing tests from libdrm-tests
Thanks for taking your time to report this issue and help making Ubuntu better. I can confirm this behaviour on Ubuntu 22.10. The package suggestions come from command-not-found, maybe the list of available binaries hasn't been updated. ** Also affects: command-not-found (Ubuntu) Importance: Undecided Status: New ** Changed in: libdrm (Ubuntu) Status: New => Confirmed ** Changed in: command-not-found (Ubuntu) Status: New => Confirmed ** Tags added: kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1998001 Title: Missing tests from libdrm-tests Status in command-not-found package in Ubuntu: Confirmed Status in libdrm package in Ubuntu: Confirmed Bug description: It is advertised by the OS that kms-universal-planes can be installed via libdrm-tests but this is false: $ kms-universal-planes Command 'kms-universal-planes' not found, but can be installed with: sudo apt install libdrm-tests $ sudo apt install libdrm-tests [sudo] password for stolk: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: libdrm-tests 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 47.5 kB of archives. After this operation, 193 kB of additional disk space will be used. Get:1 http://ca.archive.ubuntu.com/ubuntu kinetic/universe amd64 libdrm-tests amd64 2.4.113-2 [47.5 kB] Fetched 47.5 kB in 0s (142 kB/s) Selecting previously unselected package libdrm-tests. (Reading database ... 308766 files and directories currently installed.) Preparing to unpack .../libdrm-tests_2.4.113-2_amd64.deb ... Unpacking libdrm-tests (2.4.113-2) ... Setting up libdrm-tests (2.4.113-2) ... $ kms-universal-planes Command 'kms-universal-planes' not found, but can be installed with: sudo apt install libdrm-tests OS: Ubuntu 22.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1998001/+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 1998042] [NEW] package python2-minimal 2.7.18-3 failed to install/upgrade: installed python2-minimal package post-installation script subprocess returned error exit status 1
You have been subscribed to a public bug: when upgrading from 20.04 to 22.04 the updater throws an error relating to python2 (see report attached) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python2-minimal 2.7.18-3 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Nov 27 10:19:16 2022 DuplicateSignature: package:python2-minimal:2.7.18-3 Setting up python2-minimal (2.7.18-3) ... dpkg: error processing package python2-minimal (--configure): installed python2-minimal package post-installation script subprocess returned error exit status 1 ErrorMessage: installed python2-minimal package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-07-06 (509 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 3.3.3, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.0.9 SourcePackage: python-defaults Title: package python2-minimal 2.7.18-3 failed to install/upgrade: installed python2-minimal package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-11-27 (0 days ago) ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check third-party-packages uec-images -- package python2-minimal 2.7.18-3 failed to install/upgrade: installed python2-minimal package post-installation script subprocess returned error exit status 1 https://bugs.launchpad.net/bugs/1998042 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults 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 1998042] Re: package python2-minimal 2.7.18-3 failed to install/upgrade: installed python2-minimal package post-installation script subprocess returned error exit status 1
** Package changed: ubuntu => python-defaults (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1998042 Title: package python2-minimal 2.7.18-3 failed to install/upgrade: installed python2-minimal package post-installation script subprocess returned error exit status 1 Status in python-defaults package in Ubuntu: New Bug description: when upgrading from 20.04 to 22.04 the updater throws an error relating to python2 (see report attached) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python2-minimal 2.7.18-3 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Nov 27 10:19:16 2022 DuplicateSignature: package:python2-minimal:2.7.18-3 Setting up python2-minimal (2.7.18-3) ... dpkg: error processing package python2-minimal (--configure): installed python2-minimal package post-installation script subprocess returned error exit status 1 ErrorMessage: installed python2-minimal package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-07-06 (509 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 3.3.3, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.0.9 SourcePackage: python-defaults Title: package python2-minimal 2.7.18-3 failed to install/upgrade: installed python2-minimal package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-11-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1998042/+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 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid
I can confirm, that deleting the cert. also solve my printing problem on 22.10! -- 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/1973441 Title: Printing does not work on Ubuntu 22.04 - cups-pki-invalid Status in cups package in Ubuntu: Confirmed Bug description: After upgrading to 22.04 printing did not work. There is cups-pki- invalid error and printer goes to paused state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sun May 15 15:34:47 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (214 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) Lpstat: device for HP_Color_LaserJet_M552_5F80BF: implicitclass://HP_Color_LaserJet_M552_5F80BF/ MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+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 1997533] Re: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep
diff -Nru flac-1.4.2+ds/debian/changelog flac-1.4.2+ds/debian/changelog --- flac-1.4.2+ds/debian/changelog 2022-11-11 09:10:23.0 +0100 +++ flac-1.4.2+ds/debian/changelog 2022-11-24 19:56:12.0 +0100 @@ -1,3 +1,16 @@ +flac (1.4.2+ds-2ubuntu1) lunar; urgency=medium + + * Do not build and install manpages on i386. Build dep pandoc is +not available in Ubuntu for i386. (LP: #1997533) +- debian/control: + + Exclude pandoc build dep on i386. + + Add dh-exec build dep. +- debian/flac.install + + Make executable and add '#!/usr/bin/dh-exec'. + + Exclude installing manpages on i386. + + -- Rik Mills Thu, 24 Nov 2022 18:56:12 + + flac (1.4.2+ds-2) unstable; urgency=medium [ Fabian Greffrath ] diff -Nru flac-1.4.2+ds/debian/control flac-1.4.2+ds/debian/control --- flac-1.4.2+ds/debian/control2022-10-26 07:37:11.0 +0200 +++ flac-1.4.2+ds/debian/control2022-11-24 19:56:12.0 +0100 @@ -1,7 +1,8 @@ Source: flac Section: sound Priority: optional -Maintainer: Debian Multimedia Maintainers +Maintainer: Ubuntu Developers +XSBC-Original-Maintainer: Debian Multimedia Maintainers Uploaders: Joshua Kwan , Fabian Greffrath , @@ -9,8 +10,9 @@ doxygen, Build-Depends: debhelper-compat (= 13), + dh-exec, libogg-dev, - pandoc, + pandoc [!i386], Standards-Version: 4.6.1 Vcs-Git: https://salsa.debian.org/multimedia-team/flac.git Vcs-Browser: https://salsa.debian.org/multimedia-team/flac this is the diff ** Changed in: flac (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flac in Ubuntu. https://bugs.launchpad.net/bugs/1997533 Title: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep Status in flac package in Ubuntu: Fix Committed Bug description: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep which is not built in Ubuntu for i386 https://launchpad.net/ubuntu/+source/flac/1.4.2+ds-2/+build/24644410 Change made in flac (1.4.1-1) "Replace docbook-to-man with pandoc as B-D" This prevents migration of flac (if/once tests succeed), and will block migration of packages that now build in proposed and depend on the bumped libs in flac 1.4 (libflac++10 and libflac12) https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#flac e.g.amongst several others so far https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#kwave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flac/+bug/1997533/+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 1997533] Re: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep
sponsored and unsubscribing sponsors. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flac in Ubuntu. https://bugs.launchpad.net/bugs/1997533 Title: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep Status in flac package in Ubuntu: Fix Committed Bug description: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep which is not built in Ubuntu for i386 https://launchpad.net/ubuntu/+source/flac/1.4.2+ds-2/+build/24644410 Change made in flac (1.4.1-1) "Replace docbook-to-man with pandoc as B-D" This prevents migration of flac (if/once tests succeed), and will block migration of packages that now build in proposed and depend on the bumped libs in flac 1.4 (libflac++10 and libflac12) https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#flac e.g.amongst several others so far https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#kwave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flac/+bug/1997533/+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 1997533] Re: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep
** Changed in: flac (Ubuntu) Assignee: (unassigned) => Rik Mills (rikmills) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flac in Ubuntu. https://bugs.launchpad.net/bugs/1997533 Title: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep Status in flac package in Ubuntu: Fix Committed Bug description: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep which is not built in Ubuntu for i386 https://launchpad.net/ubuntu/+source/flac/1.4.2+ds-2/+build/24644410 Change made in flac (1.4.1-1) "Replace docbook-to-man with pandoc as B-D" This prevents migration of flac (if/once tests succeed), and will block migration of packages that now build in proposed and depend on the bumped libs in flac 1.4 (libflac++10 and libflac12) https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#flac e.g.amongst several others so far https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#kwave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flac/+bug/1997533/+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 1998058] [NEW] dpkg error libflac8_1.3.2-1ubuntu0.1_i386.deb
Public bug reported: Hi the Recent security patch for libflac8 is not installing : Preparing to unpack .../libflac8_1.3.2-1ubuntu0.1_i386.deb ... dpkg: error processing archive /var/cache/apt/archives/libflac8_1.3.2-1ubuntu0.1_i386.deb (--unpack): triggers ci file contains unknown directive 'libcrypto' Errors were encountered while processing: /var/cache/apt/archives/libflac8_1.3.2-1ubuntu0.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I am running : Distributor ID: Ubuntu Description:Ubuntu 18.04.6 LTS Release:18.04 Codename: bionic 4.15.0-191-generic libflac8: Installed: 1.3.2-1 Candidate: 1.3.2-1ubuntu0.1 Version table: 1.3.2-1ubuntu0.1 500 500 http://ca.archive.ubuntu.com/ubuntu bionic-security/main i386 Packages 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages *** 1.3.2-1 500 500 http://ca.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status Thank you ** Affects: flac (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flac in Ubuntu. https://bugs.launchpad.net/bugs/1998058 Title: dpkg error libflac8_1.3.2-1ubuntu0.1_i386.deb Status in flac package in Ubuntu: New Bug description: Hi the Recent security patch for libflac8 is not installing : Preparing to unpack .../libflac8_1.3.2-1ubuntu0.1_i386.deb ... dpkg: error processing archive /var/cache/apt/archives/libflac8_1.3.2-1ubuntu0.1_i386.deb (--unpack): triggers ci file contains unknown directive 'libcrypto' Errors were encountered while processing: /var/cache/apt/archives/libflac8_1.3.2-1ubuntu0.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I am running : Distributor ID: Ubuntu Description: Ubuntu 18.04.6 LTS Release: 18.04 Codename: bionic 4.15.0-191-generic libflac8: Installed: 1.3.2-1 Candidate: 1.3.2-1ubuntu0.1 Version table: 1.3.2-1ubuntu0.1 500 500 http://ca.archive.ubuntu.com/ubuntu bionic-security/main i386 Packages 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages *** 1.3.2-1 500 500 http://ca.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flac/+bug/1998058/+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 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly
** Changed in: openvpn Status: New => Fix Released -- 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/1917887 Title: Network Manager OpenVPN nested connections fail to setup routes correctly Status in OpenVPN: Fix Released Status in network-manager package in Ubuntu: Triaged Status in openvpn package in Ubuntu: Invalid Bug description: Setup: Host lan: 192.168.0.238/24 Host Default gw: 192.168.0.1 ip route: default via 192.168.0.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 Primary OpenVPN (check "Use this connection only for resources on its network"): server ip: public a.b.c.d OpenVPN Tunnel: 192.168.1.0/24 routes pushed: 192.168.100.0/24 First VPN works OK: default via 192.168.0.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 Secondary OpenVPN (check "Use this connection only for resources on its network"): server ip: private 192.168.100.10 OpenVPN Tunnel: 192.168.20.0/24 routes pushed: 192.168.200.0/24 Second VPN Connect OK, routing table is wrong: default via 192.168.0.1 dev eno1 proto dhcp metric 100 192.168.200.0/24 via 192.168.20.1 dev tun1 192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is wrong, the openVPN#2 Gateway is not on the local lan Correct routing table using "sudo /usr/sbin/openvpn /path/to/config.openvpn" (same a Network Manager) default via 192.168.0.1 dev eno1 proto dhcp metric 100 192.168.200.0/24 via 192.168.20.1 dev tun1 192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 It seems that Network Manager add a wrong additional route not added by the openvpn bin: 192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openvpn 2.4.7-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 12:44:39 2021 InstallationDate: Installed on 2021-02-19 (13 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/1917887/+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 1998063] [NEW] package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127
Public bug reported: hh ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tzdata 2022f-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 28 09:40:25 2022 DpkgTerminalLog: 正在设置 tzdata (2022f-0ubuntu0.22.04.1) ... /var/lib/dpkg/info/tzdata.config: 394: head: not found dpkg: 处理软件包 tzdata (--configure)时出错： 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127 ErrorMessage: 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127 InstallationDate: Installed on 2022-06-06 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: tzdata Title: package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998063 Title: package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127 Status in tzdata package in Ubuntu: New Bug description: hh ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tzdata 2022f-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 28 09:40:25 2022 DpkgTerminalLog: 正在设置 tzdata (2022f-0ubuntu0.22.04.1) ... /var/lib/dpkg/info/tzdata.config: 394: head: not found dpkg: 处理软件包 tzdata (--configure)时出错： 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127 ErrorMessage: 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127 InstallationDate: Installed on 2022-06-06 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: tzdata Title: package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998063/+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 1649604] Re: package libmp3lame0:amd64 3.99.5+repack1-9build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c
[Expired for lame (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lame (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1649604 Title: package libmp3lame0:amd64 3.99.5+repack1-9build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in lame package in Ubuntu: Expired Bug description: audio package error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libmp3lame0:amd64 3.99.5+repack1-9build1 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Tue Dec 13 20:14:44 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu5 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libmp3lame0:amd64:3.99.5+repack1-9build1 Processing triggers for desktop-file-utils (0.22-1ubuntu5) ... dpkg: error processing package libmp3lame0:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-12-03 (10 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: lame Title: package libmp3lame0:amd64 3.99.5+repack1-9build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1649604/+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 1998063] Re: package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: tzdata (Ubuntu) Importance: Undecided => Low ** Changed in: tzdata (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998063 Title: package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127 Status in tzdata package in Ubuntu: Invalid Bug description: hh ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tzdata 2022f-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 28 09:40:25 2022 DpkgTerminalLog: 正在设置 tzdata (2022f-0ubuntu0.22.04.1) ... /var/lib/dpkg/info/tzdata.config: 394: head: not found dpkg: 处理软件包 tzdata (--configure)时出错： 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127 ErrorMessage: 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127 InstallationDate: Installed on 2022-06-06 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: tzdata Title: package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998063/+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 1871959] Re: Crash with SIGABRT in _iris_batch_flush from iris_fence_flush()
Yes we know 20.04 is still crashing, but Fix Released is still the correct status if it's fixed in any later release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Crash with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+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 1871959] Re: Crash with SIGABRT in _iris_batch_flush from iris_fence_flush()
If you encounter any issues in 22.04 then please be sure to report separate bugs for each. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Crash with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+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]
Hello, I'll follow up with you guys probably tomorrow (but possibly as soon as later today). I've just been having an eventful holiday weekend. As tomorrow is a normal weekday that I have off, I'll finally reach out to Lenovo again tomorrow myself. Doing a quick search, I don't think anyone has shared their Legion Slim 7 Gen 7 AMD alsa-info. Can someone do that? It's likely still the CSC3551, but it would be good to confirm. As for those ACPI messages... Looks like you have ACPI some stuff that isn't supported under Linux yet. It's a fairly new laptop, so that's to be expected. I don't really see that on my current laptop, but I do see it with my current desktop which I've had for under a month (Asus Crosshair x670 Extreme). The CCP messages means Linux can't utilize the AMD Crypto Co-Processor on your CPU. I've had this message for my current desktop as well as my previous (AMD 7950 and 5950 CPU's respectively). From my research, the motherboard vendor (both Asus in my case) need to fix the BIOS. Maybe it's a similar issue to what we're seeing with our laptops. While unfortunately, it hasn't really impacted me. On 11/26/22 11:28, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #720 from antide...@gmail.com --- > (In reply to Blake Lee from comment #719) >> (In reply to Cameron Berkenpas from comment #711) >>> It does not, which is unfortunate, as the 6th gen model recently finally >>> got support. >>> >>> The gen 7 uses the CSC3551 and the gen 7 is missing the properties in >>> the _DSD tables. >>> >>> Do you already have the Gen 7? Try submitting a Lenovo support ticket >>> asking them to add the properties. I have a ticket they haven't follow >>> up on yet so I added a comment to the ticket I think less than an hour ago. >>> >>> On 10/24/22 09:55, bugzilla-dae...@kernel.org wrote: https://bugzilla.kernel.org/show_bug.cgi?id=208555 --- Comment #710 from Howard Chu (h...@highlandsun.com) --- Hi, I might've missed this but - do we know for certain that the 7th gen Legion 7 (2022 model) uses the same amplifier chip as the 6th gen (2021 model)? >> Hi Cameron, >> >> I got my Legion Slim 7 Gen 7 AMD version yesterday and when I excitedly >> installed Fedora, I found the audio did not work. I would like to throw my >> weight behind this to get it fixed, but I don't know what to say to support >> exactly in my ticket. What do I need to ask them for? >> >> I would really prefer not to have to send this laptop back. Is there >> anything else I can do to help? > I wish I knew. My understanding is that they have to add DSD entries in the > next BIOS update. Maybe someone could elaborate further. When I put a ticket > in they just sent me a generic sound troubleshooting guide for Windows. I am > currently dualbooting hoping for an eventual solution (other than headphones > or > a bluetooth speaker). > > Nov 25 21:36:05 [redacted] kernel: ACPI BIOS Error (bug): Could not resolve > symbol [\_SB.PCI0.LPC0.EC0.OKEC], AE_NOT_FOUND (20220331/psargs-330) > Nov 25 21:36:05 [redacted] kernel: ccp :07:00.2: ccp: unable to access > the > device: you might be running a broken BIOS. > Nov 26 00:18:21 [redacted] kernel: ACPI BIOS Error (bug): Could not resolve > symbol [\_SB.PCI0.LPC0.EC0.OKEC], AE_NOT_FOUND (20220331/psargs-330) > Nov 26 11:55:07 [redacted] kernel: ACPI BIOS Error (bug): Could not resolve > symbol [\_SB.PCI0.LPC0.EC0.OKEC], AE_NOT_FOUND (20220331/psargs-330) > -- 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
[Touch-packages] [Bug 1958019]
(In reply to Cameron Berkenpas from comment #721) > Hello, > > > Doing a quick search, I don't think anyone has shared their Legion Slim > 7 Gen 7 AMD alsa-info. Can someone do that? It's likely still the > CSC3551, but it would be good to confirm. check the comment 700 -- 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 1988364] Re: Missing the A2DP profile and defaults to low quality
Also added this to our internal tracker so we don't forget to patch jammy. ** Tags added: dt-859 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality https://github.com/bluez/bluez/issues/313 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+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
