[Touch-packages] [Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
Tested on SKU 0A36 (Latitude 7420) and is PASS for both focal and impish. -- 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/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models Status in OEM Priority Project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: This hwdb update is to avoid unwanted screen rotation when tilting the laptop. This is the update to the previously rolled back SRU LP: #1938259 [Impact] * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerometer. [Test Plan] * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install this package and ensure the kernel is updated to the latest. * Screen should be correct side up in login screen and desktop. * Tilt the laptop and the screen should not be rotated. [Where problems could occur] * This is to add parameters for certain models in hwdb, and does not affect any other part of systemd. * Only models with the same Dell SKU would be affected. [scope] this is needed for all releases this is being added to upstream by https://github.com/systemd/systemd/pull/20314 and https://github.com/systemd/systemd/pull/20661 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+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 1926547] Re: Add Dell Privacy Mic Mute Key mapping
It should also use oem kernel which mentioned in comment #15 -- 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/1926547 Title: Add Dell Privacy Mic Mute Key mapping Status in OEM Priority Project: Fix Released Status in OEM Priority Project focal series: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd source package in Impish: Fix Committed Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * The change can only work with kernel commit on some specific hardware, ex. Latitude 9520. The commit series is "hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree. https://patchwork.kernel.org/project/alsa-devel/list/?series=465445 * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1926547/+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 1926547] Re: Add Dell Privacy Mic Mute Key mapping
After adding impish-proposed to /etc/apt/source.list and updating the systemd to 248.3-1 ubunutu8.1, GUI still doesn't pop up "Mic Mute" icon. dmesg: Unknown key with type 0x0012 and code 0x000e pressed -- 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/1926547 Title: Add Dell Privacy Mic Mute Key mapping Status in OEM Priority Project: Fix Released Status in OEM Priority Project focal series: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd source package in Impish: Fix Committed Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * The change can only work with kernel commit on some specific hardware, ex. Latitude 9520. The commit series is "hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree. https://patchwork.kernel.org/project/alsa-devel/list/?series=465445 * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1926547/+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 1892825] Autopkgtest regression report (glibc/2.31-0ubuntu9.4)
All autopkgtests for the newly accepted glibc (2.31-0ubuntu9.4) for focal have finished running. The following regressions have been reported in tests triggered by the package: snapd-glib/1.58-0ubuntu0.20.04.0 (armhf) apt/2.0.6 (armhf) libmath-mpfr-perl/4.13-1 (armhf) art-nextgen-simulation-tools/20160605+dfsg-4 (armhf) ruby-nokogiri/1.10.7+dfsg1-2build1 (armhf) r-cran-rgdal/1.4-8-1build2 (armhf) arrayfire/3.3.2+dfsg1-4ubuntu4 (armhf) libpango-perl/1.227-3build1 (armhf) libimage-sane-perl/5-1 (s390x) ruby-bootsnap/1.4.6-1 (arm64) mle/1.4.3-1 (ppc64el, arm64) libsyntax-keyword-try-perl/0.11-1build1 (armhf) awesome/4.3-4 (armhf) cysignals/1.10.2+ds-4 (arm64) gvfs/1.44.1-1ubuntu1 (ppc64el) libuv1/1.34.2-1ubuntu1.3 (amd64) bali-phy/3.4.1+dfsg-2build1 (arm64, s390x) g10k/0.5.7-1 (armhf) litl/0.1.9-7 (amd64) ruby-libxml/3.1.0-2 (armhf) ffmpeg/7:4.2.4-1ubuntu0.1 (armhf) yorick/2.2.04+dfsg1-10 (ppc64el, s390x) linux-ibm/5.4.0-1010.11 (amd64) liborcus/0.15.3-3build2 (armhf) node-nodedbi/1.0.13+dfsg-1build1 (amd64) r-bioc-delayedarray/0.12.2+dfsg-1 (armhf) postgresql-unit/7.2-2 (armhf) python-freecontact/1.1-5build2 (armhf) r-cran-rwave/2.4-8-2 (armhf) libproc-fastspawn-perl/1.2-1build2 (armhf) linux-hwe-5.11/5.11.0-44.48~20.04.2 (armhf) foo2zjs/20171202dfsg0-4 (armhf) r-cran-erm/1.0-0-1 (armhf) libsys-cpuload-perl/0.03-8build5 (armhf) libhttp-parser-xs-perl/0.17-1build5 (armhf) php-luasandbox/3.0.3-2build2 (armhf) pynfft/1.3.2-3build1 (armhf) r-cran-processx/3.4.2-1 (ppc64el) r-bioc-multtest/2.42.0-1 (armhf) linux-hwe-5.13/5.13.0-23.23~20.04.2 (armhf) python-blosc/1.7.0+ds1-2ubuntu2 (armhf) gyoto/1.4.4-3 (armhf) r-cran-sem/3.1.9-2build1 (armhf) libtext-reflow-perl/1.17-1build3 (armhf) python3.9/3.9.5-3ubuntu0~20.04.1 (armhf) r-cran-samr/3.0-1 (armhf) r-cran-dplyr/0.8.4-1 (armhf) python3.8/3.8.10-0ubuntu1~20.04.2 (armhf) findent/3.1.1-1build1 (armhf) mercurial/5.3.1-1ubuntu1 (amd64) libmemcached-libmemcached-perl/1.001801+dfsg-2build4 (armhf) openbabel/3.0.0+dfsg-3ubuntu3 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#glibc [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1892825 Title: update-locale not perform correctly sanity checks Status in glibc package in Ubuntu: In Progress Status in pam package in Ubuntu: New Status in glibc source package in Bionic: New Status in pam source package in Bionic: New Status in glibc source package in Focal: Fix Committed Status in pam source package in Focal: New Status in glibc source package in Hirsute: New Status in pam source package in Hirsute: New Status in glibc source package in Impish: New Status in pam source package in Impish: New Bug description: [impact] A simple typo using the update-locale script can render a system inoperable without booting into single user mode or similar: $ sudo update-locale LANGUAGE = en_US.UTF-8 $ sudo -s sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization [test case] $ cp /etc/default/locale /tmp/locale $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8 "diff -u /etc/default/locale /tmp/locale" should be empty. [original description] By passing wrong input as following: sudo update-locale LANGUAGE = en_US.UTF-8 result is: ... #LANGUAGE=en = This "equal" sign that was added makes system completely unusable(can't run sudo anymore): bentzy@bentzy-nb:~$ sudo vim /etc/default/locale sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization Fixed it booting from installation disk and fixing corrupted /etc/default/locale ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: locales 2.31-0ubuntu9 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Aug 25 09:36:03 2020 InstallationDate: Installed on 2020-08-17 (7 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+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 1927192] Autopkgtest regression report (glibc/2.31-0ubuntu9.4)
All autopkgtests for the newly accepted glibc (2.31-0ubuntu9.4) for focal have finished running. The following regressions have been reported in tests triggered by the package: snapd-glib/1.58-0ubuntu0.20.04.0 (armhf) apt/2.0.6 (armhf) libmath-mpfr-perl/4.13-1 (armhf) art-nextgen-simulation-tools/20160605+dfsg-4 (armhf) ruby-nokogiri/1.10.7+dfsg1-2build1 (armhf) r-cran-rgdal/1.4-8-1build2 (armhf) arrayfire/3.3.2+dfsg1-4ubuntu4 (armhf) libpango-perl/1.227-3build1 (armhf) libimage-sane-perl/5-1 (s390x) ruby-bootsnap/1.4.6-1 (arm64) mle/1.4.3-1 (ppc64el, arm64) libsyntax-keyword-try-perl/0.11-1build1 (armhf) awesome/4.3-4 (armhf) cysignals/1.10.2+ds-4 (arm64) gvfs/1.44.1-1ubuntu1 (ppc64el) libuv1/1.34.2-1ubuntu1.3 (amd64) bali-phy/3.4.1+dfsg-2build1 (arm64, s390x) g10k/0.5.7-1 (armhf) litl/0.1.9-7 (amd64) ruby-libxml/3.1.0-2 (armhf) ffmpeg/7:4.2.4-1ubuntu0.1 (armhf) yorick/2.2.04+dfsg1-10 (ppc64el, s390x) linux-ibm/5.4.0-1010.11 (amd64) liborcus/0.15.3-3build2 (armhf) node-nodedbi/1.0.13+dfsg-1build1 (amd64) r-bioc-delayedarray/0.12.2+dfsg-1 (armhf) postgresql-unit/7.2-2 (armhf) python-freecontact/1.1-5build2 (armhf) r-cran-rwave/2.4-8-2 (armhf) libproc-fastspawn-perl/1.2-1build2 (armhf) linux-hwe-5.11/5.11.0-44.48~20.04.2 (armhf) foo2zjs/20171202dfsg0-4 (armhf) r-cran-erm/1.0-0-1 (armhf) libsys-cpuload-perl/0.03-8build5 (armhf) libhttp-parser-xs-perl/0.17-1build5 (armhf) php-luasandbox/3.0.3-2build2 (armhf) pynfft/1.3.2-3build1 (armhf) r-cran-processx/3.4.2-1 (ppc64el) r-bioc-multtest/2.42.0-1 (armhf) linux-hwe-5.13/5.13.0-23.23~20.04.2 (armhf) python-blosc/1.7.0+ds1-2ubuntu2 (armhf) gyoto/1.4.4-3 (armhf) r-cran-sem/3.1.9-2build1 (armhf) libtext-reflow-perl/1.17-1build3 (armhf) python3.9/3.9.5-3ubuntu0~20.04.1 (armhf) r-cran-samr/3.0-1 (armhf) r-cran-dplyr/0.8.4-1 (armhf) python3.8/3.8.10-0ubuntu1~20.04.2 (armhf) findent/3.1.1-1build1 (armhf) mercurial/5.3.1-1ubuntu1 (amd64) libmemcached-libmemcached-perl/1.001801+dfsg-2build4 (armhf) openbabel/3.0.0+dfsg-3ubuntu3 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#glibc [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Released Status in gdb source package in Focal: Fix Committed Status in glibc source package in Focal: Fix Committed Status in gdb source package in Groovy: Won't Fix Status in glibc source package in Groovy: Won't Fix Status in gdb source package in Hirsute: Won't Fix Status in glibc source package in Hirsute: Won't Fix Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Released Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1955087] [NEW] bluetooth cannot transfer files to phone although connected
Public bug reported: Ubuntu version: 20.4 Not sure of package (bluez)? (Whatever handles Bluetooth) What I expected: File is transferred. What happened: transfer fails with mysterious error code (0x53) which sometimes shows up on phone and sometimes doesn't. In any case the transfer fails. Additional notes: Error was observed before, see https://bbs.archlinux.org/viewtopic.php?id=202815, however suggested solution on that page doesn't work for me so I assume there is some difference. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 18:50:38 2021 InstallationDate: Installed on 2021-01-27 (323 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP Pavilion Desktop TP01-0xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=d2279364-889e-4dd0-9766-948e06f4ab3d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.release: 15.35 dmi.bios.vendor: AMI dmi.bios.version: F.23 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.41 dmi.modalias: dmi:bvnAMI:bvrF.23:bd07/07/2020:br15.35:efr52.41:svnHP:pnHPPavilionDesktopTP01-0xxx:pvr:sku3UQ92AA#ABA:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion Desktop PC dmi.product.name: HP Pavilion Desktop TP01-0xxx dmi.product.sku: 3UQ92AA#ABA dmi.sys.vendor: HP hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:15:83:4E:03:27 ACL MTU: 384:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:5837051 acl:16480 sco:0 events:6085 errors:0 TX bytes:44273 acl:1706 sco:0 commands:1272 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bluetooth focal -- 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/1955087 Title: bluetooth cannot transfer files to phone although connected Status in bluez package in Ubuntu: New Bug description: Ubuntu version: 20.4 Not sure of package (bluez)? (Whatever handles Bluetooth) What I expected: File is transferred. What happened: transfer fails with mysterious error code (0x53) which sometimes shows up on phone and sometimes doesn't. In any case the transfer fails. Additional notes: Error was observed before, see https://bbs.archlinux.org/viewtopic.php?id=202815, however suggested solution on that page doesn't work for me so I assume there is some difference. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 18:50:38 2021 InstallationDate: Installed on 2021-01-27 (323 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP Pavilion Desktop TP01-0xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=d2279364-889e-4dd0-9766-948e06f4ab3d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.release: 15.35 dmi.bios.vendor: AMI dmi.bios.version: F.23 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.41 dmi.modalias: dmi:bvnAMI:bvrF.23:bd07/07/2020:br15.35:efr52.41:svnHP:pnHPPavilionDesktopTP01-0xxx:pvr:sku3UQ92AA#ABA:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion Desktop PC dmi.product.name: HP Pavilion Desktop TP01-0xxx dmi.product.sku: 3UQ92AA#ABA dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:15:83:4E:03:27 ACL MTU: 384:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:5837051 acl:16480 sco:0 events:6085 errors:0 TX bytes:44273 acl:1706 sco:0 commands:1272 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1955087/+subscriptions --
[Touch-packages] [Bug 1947452] Re: Please remove maliit from Ubuntu
> The project doesn’t look dead to me… Nevertheless, it's clear it is no longer being maintained as a package in Ubuntu, with only distro maintenance uploads (rebuilds for ABI changes, etc) since at least 2017 and no one pulling new upstream versions into Ubuntu since 2015. If someone is interested in actually maintaining this in Ubuntu, we can always see about getting it reuploaded. Removing packages from jammy: maliit-framework 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy gir1.2-maliit-1.0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy amd64 gir1.2-maliit-1.0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy arm64 gir1.2-maliit-1.0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy armhf gir1.2-maliit-1.0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy i386 gir1.2-maliit-1.0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy ppc64el gir1.2-maliit-1.0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy riscv64 gir1.2-maliit-1.0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy s390x libmaliit-glib-dev 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy amd64 libmaliit-glib-dev 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy arm64 libmaliit-glib-dev 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy armhf libmaliit-glib-dev 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy ppc64el libmaliit-glib-dev 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy riscv64 libmaliit-glib-dev 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy s390x libmaliit-glib0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy amd64 libmaliit-glib0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy arm64 libmaliit-glib0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy armhf libmaliit-glib0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy ppc64el libmaliit-glib0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy riscv64 libmaliit-glib0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy s390x libmaliit-plugins0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy amd64 libmaliit-plugins0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy arm64 libmaliit-plugins0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy armhf libmaliit-plugins0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy ppc64el libmaliit-plugins0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy riscv64 libmaliit-plugins0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy s390x libmaliit0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy amd64 libmaliit0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy arm64 libmaliit0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy armhf libmaliit0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy i386 libmaliit0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy ppc64el libmaliit0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy riscv64 libmaliit0 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy s390x maliit-dbus-activation 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy amd64 maliit-dbus-activation 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy arm64 maliit-dbus-activation 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy armhf maliit-dbus-activation 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy i386 maliit-dbus-activation 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy ppc64el maliit-dbus-activation 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy riscv64 maliit-dbus-activation 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy s390x maliit-framework 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy amd64 maliit-framework 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy arm64 maliit-framework 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy armhf maliit-framework 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy ppc64el maliit-framework 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy riscv64 maliit-framework 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy s390x maliit-framework-dbg 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy amd64 maliit-framework-dbg 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy arm64 maliit-framework-dbg 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy armhf maliit-framework-dbg 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy ppc64el maliit-framework-dbg 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy riscv64 maliit-framework-dbg 0.99.1+git20151118+62bd54b-0ubuntu30 in jammy s390x maliit-framework-dev
[Touch-packages] [Bug 1947452] Re: Please remove maliit from Ubuntu
Removing packages from jammy: maliit-inputcontext-gtk 0.99.1-0ubuntu2 in jammy maliit-inputcontext-gtk2 0.99.1-0ubuntu2 in jammy amd64 maliit-inputcontext-gtk2 0.99.1-0ubuntu2 in jammy arm64 maliit-inputcontext-gtk2 0.99.1-0ubuntu2 in jammy armhf maliit-inputcontext-gtk2 0.99.1-0ubuntu2 in jammy ppc64el maliit-inputcontext-gtk2 0.99.1-0ubuntu2 in jammy riscv64 maliit-inputcontext-gtk2 0.99.1-0ubuntu2 in jammy s390x maliit-inputcontext-gtk3 0.99.1-0ubuntu2 in jammy amd64 maliit-inputcontext-gtk3 0.99.1-0ubuntu2 in jammy arm64 maliit-inputcontext-gtk3 0.99.1-0ubuntu2 in jammy armhf maliit-inputcontext-gtk3 0.99.1-0ubuntu2 in jammy ppc64el maliit-inputcontext-gtk3 0.99.1-0ubuntu2 in jammy riscv64 maliit-inputcontext-gtk3 0.99.1-0ubuntu2 in jammy s390x Comment: Ubuntu-specific, unmaintained, part of a discontinued product; LP: #1947452 1 package successfully removed. ** Changed in: maliit-inputcontext-gtk (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1947452 Title: Please remove maliit from Ubuntu Status in maliit-framework package in Ubuntu: Fix Released Status in maliit-inputcontext-gtk package in Ubuntu: Fix Released Bug description: Please remove maliit-framework & maliit-inputcontext-gtk from Ubuntu. They have no reverse dependencies. https://tracker.debian.org/pkg/maliit-framework was uploaded to Debian experimental once but was removed. I think the packages were added as part of the Unity 8 project and aren't actively maintained in Ubuntu since Canonical stopped work there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1947452/+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 1954320] Re: Add privacy screen modules to the initrd
** Also affects: initramfs-tools (Ubuntu Jammy) Importance: High Status: Confirmed ** Tags removed: rls-jj-incoming -- 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/1954320 Title: Add privacy screen modules to the initrd Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools source package in Jammy: Confirmed Bug description: Starting with kernel 5.17 the kernel supports the builtin privacy screens built into the LCD panel of some new laptop models. This means that the drm drivers will now return -EPROBE_DEFER from their probe() method on models with a builtin privacy screen when the privacy screen provider driver has not been loaded yet. To avoid any regressions Ubuntu should modify its initrd generation tool to include privacy screen provider drivers in the initrd (at least on systems with a privacy screen), before 5.17 kernels start showing up in the Ubuntu repos. If this change is not made, then users using a graphical bootsplash (plymouth) will get an extra boot-delay of up to 8 seconds (DeviceTimeout in plymouthd.defaults) before plymouth will show and when using disk-encryption where the LUKS password is requested from the initrd, the system may fallback to text-mode after these 8 seconds. I've written a patch with the necessary changes for dracut, which might be useful as an example for how to deal with this, see: https://github.com/dracutdevs/dracut/pull/1666 ATM the only kms driver using privacy screens is the i915 driver and the only provider is the thinkpad_acpi driver. But both are likely to change (and change soon!), so the detection really should be made dynamic as has been done in the dracut patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1954320/+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 1951519] Re: ubiquity 20.04.15.17 fails to build (test_timezone)
Confirmed this issue as attempt was made for an OEM and failed. See
build log at https://launchpadlibrarian.net/574391158/buildlog_ubuntu-
focal-amd64.ubiquity_20.04.15.17+kfocus2_BUILDING.txt.gz
** Also affects: ubiquity (Ubuntu Jammy)
Importance: Undecided
Status: Confirmed
** Also affects: tzdata (Ubuntu Jammy)
Importance: Undecided
Status: Confirmed
** Also affects: ubiquity (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu Focal)
Status: New => Confirmed
** Changed in: ubiquity (Ubuntu Jammy)
Status: Confirmed => New
** Changed in: tzdata (Ubuntu Focal)
Status: New => Confirmed
** Changed in: tzdata (Ubuntu Jammy)
Status: Confirmed => New
** Tags added: rls-ff-incoming rls-jj-incoming
--
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/1951519
Title:
ubiquity 20.04.15.17 fails to build (test_timezone)
Status in tzdata package in Ubuntu:
New
Status in ubiquity package in Ubuntu:
New
Status in tzdata source package in Focal:
Confirmed
Status in ubiquity source package in Focal:
Confirmed
Status in tzdata source package in Jammy:
New
Status in ubiquity source package in Jammy:
New
Bug description:
Description: Ubuntu 20.04.3 LTS
Release: 20.04
When trying to build ubiquity from source,
sudo apt update
sudo apt -y dist-upgrade
sudo apt-get build-dep ubiquity
sudo apt install -y fakeroot
apt source ubiquity
cd ubiquity-*
dpkg-buildpackage -us -uc
[...]
test_has_battery (test_upower.UPowerTests) ... ok
test_check_hostname (test_usersetup.UserSetupTests) ... ok
test_check_username (test_usersetup.UserSetupTests) ... ok
test_default_username (test_usersetup.UserSetupTests) ... ok
test_default_username_strips_invalid_characters
(test_usersetup.UserSetupTests) ... ok
test_hostname_check (test_usersetup.UserSetupTests) ... ok
test_hostname_check_bogus_dns (test_usersetup.UserSetupTests) ... ok
test_hostname_check_exists (test_usersetup.UserSetupTests) ... ok
test_unicode (test_usersetup.UserSetupTests) ... ok
==
FAIL: test_city_entry (test_timezone.TimezoneTests)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/home/ark/ubiquity-20.04.15.17/tests/test_timezone.py", line 58, in
test_city_entry
self.assertEqual(set(results), set(expected))
AssertionError: Items in the first set but not the second:
('Eastern', 'Bahamas')
Items in the second set but not the first:
('Eastern', 'Canada')
--
Ran 89 tests in 19.319s
FAILED (failures=1)
xauth/Xrdb output:
make: *** [debian/rules:228: tests] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned
exit status 2
It keeps failing regardless of release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1951519/+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 1954320] Re: Add privacy screen modules to the initrd
** Tags added: fr-1938 -- 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/1954320 Title: Add privacy screen modules to the initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Starting with kernel 5.17 the kernel supports the builtin privacy screens built into the LCD panel of some new laptop models. This means that the drm drivers will now return -EPROBE_DEFER from their probe() method on models with a builtin privacy screen when the privacy screen provider driver has not been loaded yet. To avoid any regressions Ubuntu should modify its initrd generation tool to include privacy screen provider drivers in the initrd (at least on systems with a privacy screen), before 5.17 kernels start showing up in the Ubuntu repos. If this change is not made, then users using a graphical bootsplash (plymouth) will get an extra boot-delay of up to 8 seconds (DeviceTimeout in plymouthd.defaults) before plymouth will show and when using disk-encryption where the LUKS password is requested from the initrd, the system may fallback to text-mode after these 8 seconds. I've written a patch with the necessary changes for dracut, which might be useful as an example for how to deal with this, see: https://github.com/dracutdevs/dracut/pull/1666 ATM the only kms driver using privacy screens is the i915 driver and the only provider is the thinkpad_acpi driver. But both are likely to change (and change soon!), so the detection really should be made dynamic as has been done in the dracut patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1954320/+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 1955085] [NEW] package systemd 245.4-4ubuntu3.13 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127
Public bug reported: New to Ubuntu/linux, got an error that asked to report. I did. I do not have any detailed information about this error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.13 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 15 03:31:02 2021 DuplicateSignature: package:systemd:245.4-4ubuntu3.13 Installing new version of config file /etc/dhcp/dhclient-enter-hooks.d/resolved ... systemd-machine-id-setup: error while loading shared libraries: libpam.so.0: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 127 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2021-12-15 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=5a0eb9db-11d1-4e63-a3c3-c001c342f9fe ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/open-vm-tools.service → /usr/lib/systemd/system/open-vm-tools.service.d/desktop.conf [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. Title: package systemd 245.4-4ubuntu3.13 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1955085 Title: package systemd 245.4-4ubuntu3.13 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127 Status in systemd package in Ubuntu: New Bug description: New to Ubuntu/linux, got an error that asked to report. I did. I do not have any detailed information about this error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.13 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 15 03:31:02 2021 DuplicateSignature: package:systemd:245.4-4ubuntu3.13 Installing new version of config file /etc/dhcp/dhclient-enter-hooks.d/resolved ... systemd-machine-id-setup: error while loading shared libraries: libpam.so.0: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 127 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2021-12-15 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic
[Touch-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+
This bug was fixed in the package ubuntu-settings - 22.04.1 --- ubuntu-settings (22.04.1) jammy; urgency=medium * Reinstate changes from 21.04.3: - Adding 99-gpio.rules udev rules for Raspberry Pi GPIO functionality (LP: #1923672) - Replace netplan eth0 renaming rules for raspi with networkd link unit (LP: #1922266) * Override initramfs compression to lz4 to prevent OOM on 512MB platforms, and add a dependency on lz4 to d/control (LP: #1950214) * d/control: Correct spelling of raspberry -- Dave Jones Wed, 15 Dec 2021 15:29:10 +0100 ** Changed in: ubuntu-settings (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1922266 Title: eth0 interface name change fails on Pi 3/3+ Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Hirsute: Fix Released Status in ubuntu-settings source package in Hirsute: Fix Released Status in ubuntu-meta source package in Impish: Fix Released Status in ubuntu-settings source package in Impish: New Status in ubuntu-meta source package in Jammy: Fix Released Status in ubuntu-settings source package in Jammy: Fix Released Bug description: The netplan configuration in ubuntu-raspi-settings (and more widely, the network-config in the gadget used on the server images) fails to rename the internal ethernet interface on Pi 3B and 3B+ models from "en" to "eth0". In the netplan case this is because the driver matching logic doesn't handle space-separate driver matches (although the underlying networkd system does); in the cloud-init case it simply refuses to rename interfaces that aren't matched by full MAC address. The intended fix is to stop attempting to do this via netplan or cloud-init, and simply handle this via a networkd .link file in ubuntu-raspi-settings. This will require an update to the relevant seeds as this package is currently only pulled into ubuntu-desktop- raspi, not ubuntu-server-raspi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1922266/+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 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd
This bug was fixed in the package ubuntu-settings - 22.04.1 --- ubuntu-settings (22.04.1) jammy; urgency=medium * Reinstate changes from 21.04.3: - Adding 99-gpio.rules udev rules for Raspberry Pi GPIO functionality (LP: #1923672) - Replace netplan eth0 renaming rules for raspi with networkd link unit (LP: #1922266) * Override initramfs compression to lz4 to prevent OOM on 512MB platforms, and add a dependency on lz4 to d/control (LP: #1950214) * d/control: Correct spelling of raspberry -- Dave Jones Wed, 15 Dec 2021 15:29:10 +0100 ** Changed in: ubuntu-settings (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1950214 Title: raspi 64 bit Impish image fails update-initramfs with OOM on zstd Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Impish: Confirmed Status in ubuntu-settings source package in Jammy: Fix Released Bug description: When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish image and nothing new installed to it, update-initramfs fails like so: Setting up linux-firmware (1.201.1) ... update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 A simple workaround for now is to switch to the old lz4 default: $ sudo apt install lz4 $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' /etc/initramfs-tools/initramfs.conf Original Workaround === Adding a swap file to the setup allowed 'apt -f install' to run successfully. How the device was setup 1) xzcat | dd the sdcard with the impish 64 bit server image 2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, link getty@ttyGS0.service ) as suggested in https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console 3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest of the 16GB flash, e2fsck, resize2fs 4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html 5) boot, connect to wireless, ssh in 6) apt update && apt upgrade 7) observe above issue ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.201.1 ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 Uname: Linux 5.13.0-1009-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 19:47 seq crw-rw 1 root audio 116, 33 Nov 8 19:47 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-1009-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Mon Nov 8 21:00:59 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20211013 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M PackageArchitecture: all PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash modules-load=dwc2,g_serial Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 bcm2835_codec vc_sm_cma Title: package linux-firmware 1.201.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1950214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1923672] Re: [FFe] Provide access to GPIO to default user
This bug was fixed in the package ubuntu-settings - 22.04.1 --- ubuntu-settings (22.04.1) jammy; urgency=medium * Reinstate changes from 21.04.3: - Adding 99-gpio.rules udev rules for Raspberry Pi GPIO functionality (LP: #1923672) - Replace netplan eth0 renaming rules for raspi with networkd link unit (LP: #1922266) * Override initramfs compression to lz4 to prevent OOM on 512MB platforms, and add a dependency on lz4 to d/control (LP: #1950214) * d/control: Correct spelling of raspberry -- Dave Jones Wed, 15 Dec 2021 15:29:10 +0100 ** Changed in: ubuntu-settings (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1923672 Title: [FFe] Provide access to GPIO to default user Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Hirsute: Fix Released Status in ubuntu-settings source package in Impish: New Status in ubuntu-settings source package in Jammy: Fix Released Bug description: At present, access to the GPIO pins is provided to the dialout group by the udev rules from the rpi.gpio-common package. However, rpi.gpio is a single GPIO library, and the device(s) it provides access to are not specific to it. Moreover, the interface used is deprecated and the /dev/gpiochip* interface is now the favoured mechanism for controlling the GPIO pins. The choice of the dialout group appears reasonable (historically it's used to provide access to the serial ports, and indeed the serial ports are part of the GPIO header on Raspberry Pi devices), but the rules should be extended to cover the modern /dev/gpiochip* devices, the related /dev/spidev* and /dev/i2c-* devices, and should be placed in a central location (i.e. ubuntu-raspi-settings) rather than in a specific GPIO library (like rpi.gpio). Related to this is LP: #1923363 which seeks to ensure equal access across images (the default user is currently granted "dialout" group membership on the pi server images, but not the desktop ones). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1923672/+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 1955084] [NEW] systemd unit leaves a process running for the system lifetime but it only does anything at shutdown
Public bug reported: The /lib/systemd/system/unattended-upgrades.service unit leaves a process, /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal, running from system start until shutdown. This increases the minimum memory footprint of every host, VM, or container where unattended-upgrades is installed. The motivation for having this systemd unit is clear in terms of the practicalities of implementing what this unit needs to do, but we should try to find some way to achieve this which does not rely on increasing the low water mark of system memory. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: rls-jj-incoming ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1955084 Title: systemd unit leaves a process running for the system lifetime but it only does anything at shutdown Status in unattended-upgrades package in Ubuntu: New Bug description: The /lib/systemd/system/unattended-upgrades.service unit leaves a process, /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal, running from system start until shutdown. This increases the minimum memory footprint of every host, VM, or container where unattended-upgrades is installed. The motivation for having this systemd unit is clear in terms of the practicalities of implementing what this unit needs to do, but we should try to find some way to achieve this which does not rely on increasing the low water mark of system memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1955084/+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 1951519] Re: ubiquity 20.04.15.17 fails to build (test_timezone)
** Also affects: tzdata (Ubuntu)
Importance: Undecided
Status: New
** Changed in: tzdata (Ubuntu)
Status: New => Confirmed
--
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/1951519
Title:
ubiquity 20.04.15.17 fails to build (test_timezone)
Status in tzdata package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Bug description:
Description: Ubuntu 20.04.3 LTS
Release: 20.04
When trying to build ubiquity from source,
sudo apt update
sudo apt -y dist-upgrade
sudo apt-get build-dep ubiquity
sudo apt install -y fakeroot
apt source ubiquity
cd ubiquity-*
dpkg-buildpackage -us -uc
[...]
test_has_battery (test_upower.UPowerTests) ... ok
test_check_hostname (test_usersetup.UserSetupTests) ... ok
test_check_username (test_usersetup.UserSetupTests) ... ok
test_default_username (test_usersetup.UserSetupTests) ... ok
test_default_username_strips_invalid_characters
(test_usersetup.UserSetupTests) ... ok
test_hostname_check (test_usersetup.UserSetupTests) ... ok
test_hostname_check_bogus_dns (test_usersetup.UserSetupTests) ... ok
test_hostname_check_exists (test_usersetup.UserSetupTests) ... ok
test_unicode (test_usersetup.UserSetupTests) ... ok
==
FAIL: test_city_entry (test_timezone.TimezoneTests)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/home/ark/ubiquity-20.04.15.17/tests/test_timezone.py", line 58, in
test_city_entry
self.assertEqual(set(results), set(expected))
AssertionError: Items in the first set but not the second:
('Eastern', 'Bahamas')
Items in the second set but not the first:
('Eastern', 'Canada')
--
Ran 89 tests in 19.319s
FAILED (failures=1)
xauth/Xrdb output:
make: *** [debian/rules:228: tests] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned
exit status 2
It keeps failing regardless of release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1951519/+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 1941752]
Here is my proposed fix in Gwenview: https://invent.kde.org/graphics/gwenview/-/merge_requests/125 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752]
Created attachment 144593 sample image that is causing the crash Here is jpg file that is causing the the crash. It is clear that libexiv is throwing exception when it tries to parse date. This exception is not catched in gwenview. $ exiv2 -P X print test.jpg Xmp.tiff.SoftwareXmpText13 digiKam-7.1.0 Xmp.tiff.DateTimeXmpText19 2014-09-13T14:36:40 Xmp.tiff.ImageWidth XmpText 4 3110 Xmp.tiff.ImageLength XmpText 4 1553 Xmp.xmp.CreatorTool XmpText13 digiKam-3.5.0 Xmp.xmp.CreateDate XmpText19 2014-09-13T14:36:40 Xmp.xmp.MetadataDate XmpText19 2014-09-13T14:36:40 Xmp.xmp.ModifyDate XmpText19 2014-09-13T14:36:40 Xmp.xmp.Rating XmpText 1 2 Xmp.exif.DateTimeOriginalXmpText19 Uncaught exception: basic_string::at: __n (which is 19) >= this->size() (which is 19) $ echo $? 1 So, fix is obvious. But where it should be fixed? In libexiv or gwenview? Ubuntu 21.10 exiv2 0.27.3 gwenview 21.08.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1953301] Re: Segfault on AArch64 caused by OpenSSL affecting numerous packages
** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1953301 Title: Segfault on AArch64 caused by OpenSSL affecting numerous packages Status in openssl package in Ubuntu: Incomplete Bug description: OpenSSL causes crashes when reaching to some URLs on AArch64 platform, affecting Ubuntu, but not Fedora for instance. Initially reported in https://mediasoup.discourse.group/t/mediasoup- worker-default-make-failed/3647/12, more details and reproductions in https://github.com/mesonbuild/meson/issues/9690 Affects curl, wget, python and probably everything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1953301/+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 1955068] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 12
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/1955068 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 127 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 16 06:15:30 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2021-12-05 (11 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1955068/+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 1955068] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 16 06:15:30 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2021-12-05 (11 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1955068 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 127 Status in initramfs-tools package in Ubuntu: New Bug description: libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 16 06:15:30 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2021-12-05 (11 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1955068/+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 1953301] Re: Segfault on AArch64 caused by OpenSSL affecting numerous packages
** Tags added: fr-1933 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1953301 Title: Segfault on AArch64 caused by OpenSSL affecting numerous packages Status in openssl package in Ubuntu: Incomplete Bug description: OpenSSL causes crashes when reaching to some URLs on AArch64 platform, affecting Ubuntu, but not Fedora for instance. Initially reported in https://mediasoup.discourse.group/t/mediasoup- worker-default-make-failed/3647/12, more details and reproductions in https://github.com/mesonbuild/meson/issues/9690 Affects curl, wget, python and probably everything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1953301/+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 1650688] Re: timedatectl set-timezone fails on UC16
Thank you very much Ratchanan for the verification on Bionic & Focal. I re-triggered those autopkgtest and they are now resolved. ** Tags removed: verification-needed-bionic verification-needed-focal ** Tags added: verification-done-bionic verification-done-focal -- 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/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: Won't Fix Status in systemd source package in Jammy: Fix Released Bug description: SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. (Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [1] on the system.) [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- core/hooks/08-etc-writable.chroot?h=ubuntu/focal * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. - The timedated itself is likely used by the programs that involves in time-related functions. If a crash occur, in the worst case users won't be able to set time or timezone via timedated. However, users should still be able to e.g. set time using `date` or set timezone using /etc/localtime (assuming online guides still consider systems without systemd). Timedated is DBus-activated, and thus a crash should be self-healing. * The set part would also affects the clasic systems. However, I believe nothing else actually rely on /etc/localtime being a relative path, otherwise the /etc/writable redirection would causes even more problem, and would have been reported. [3] Yes, I'm surprised that there's a DHCP server inside systemd codebase. [Other Info] * This is also useful for UBports's Ubuntu Touch. We continue using system-image system where the rootfs is read-only, and thus is affected by this bug similarly to Ubuntu Core. I've tested the Focal version of the package on our (currently in development) Focal Ubuntu Touch image, and the fix works. [Original bug description] On a system running UC16, the file /etc/localtime is a link that points to /etc/writable/localtime. On a freshly installed system, /etc/writable/localtime is a fully- qualified link that points at /usr/share/zoneinfo/UTC. If timedatectl is used to set the timezone to something else, timedated updates the
[Touch-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported
** Changed in: vorta (Debian) Status: Unknown => Confirmed ** Changed in: python-hypothesis (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: New Status in pygobject package in Ubuntu: New Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: New Status in python-taskflow package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: Invalid Status in supysonic package in Ubuntu: New Status in vorta package in Ubuntu: New Status in ipywidgets package in Debian: New Status in pygobject package in Debian: New Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: New Status in python-hypothesis package in Debian: New Status in supysonic package in Debian: New Status in vorta package in Debian: Confirmed Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+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 1955049] [NEW] Xorg crash
Public bug reported: System crashes about 3 times a day; no appearant relation to application or process or triggering situation. Happens constantly. Random time between incidents normally several hours. This is a problem for month now. Description:Ubuntu 21.04 Release:21.04 GUI crashed: Operation ceses, monitor becomes dark. In this case the monitor shows a static picture after some seconds of darkness. Remote access via SSH is possible up to some extend. Expected: GUI does not crash. dmesg says: [ 2284.101478] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 2289.993462] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=132409, emitted seq=132410 [ 2289.993826] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 [ 2289.994175] amdgpu :0a:00.0: amdgpu: GPU reset begin! [ 2290.169982] [drm] free PSP TMR buffer [ 2290.198611] amdgpu :0a:00.0: amdgpu: MODE2 reset [ 2290.198656] amdgpu :0a:00.0: amdgpu: GPU reset succeeded, trying to resume [ 2290.198943] [drm] PCIE GART of 1024M enabled. [ 2290.198945] [drm] PTB located at 0x00F40090 [ 2290.199115] [drm] PSP is resuming... [ 2290.218996] [drm] reserve 0x40 from 0xf45700 for PSP TMR [ 2290.262318] amdgpu :0a:00.0: amdgpu: RAS: optional ras ta ucode is not available [ 2290.266897] amdgpu :0a:00.0: amdgpu: RAP: optional rap ta ucode is not available [ 2290.266899] amdgpu :0a:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 2290.468265] [drm] kiq ring mec 2 pipe 1 q 0 [ 2290.602777] [drm] VCN decode and encode initialized successfully(under SPG Mode). [ 2290.602784] amdgpu :0a:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 [ 2290.602787] amdgpu :0a:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 2290.602788] amdgpu :0a:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 2290.602790] amdgpu :0a:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [ 2290.602791] amdgpu :0a:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [ 2290.602792] amdgpu :0a:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [ 2290.602793] amdgpu :0a:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [ 2290.602793] amdgpu :0a:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [ 2290.602795] amdgpu :0a:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [ 2290.602796] amdgpu :0a:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [ 2290.602797] amdgpu :0a:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1 [ 2290.602798] amdgpu :0a:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1 [ 2290.602798] amdgpu :0a:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1 [ 2290.602799] amdgpu :0a:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1 [ 2290.602800] amdgpu :0a:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 [ 2290.609397] amdgpu :0a:00.0: amdgpu: recover vram bo from shadow start [ 2290.609400] amdgpu :0a:00.0: amdgpu: recover vram bo from shadow done [ 2290.609464] amdgpu :0a:00.0: amdgpu: GPU reset(1) succeeded! [ 2290.609926] kfd kfd: amdgpu: Allocated 3969056 bytes on gart [ 2290.609979] kfd kfd: amdgpu: error getting iommu info. is the iommu enabled? [ 2290.609981] kfd kfd: amdgpu: Error initializing iommuv2 [ 2290.610175] kfd kfd: amdgpu: device 1002:15d8 NOT added due to errors [ 2317.591058] rfkill: input handler enabled [ 2412.382743] show_signal_msg: 29 callbacks suppressed [ 2412.382746] apport-gtk[16593]: segfault at 18 ip 7f7f7e90e194 sp 7fff2ca56790 error 4 in libgtk-3.so.0.2404.21[7f7f7e805000+385000] [ 2412.382753] Code: c4 08 5b 5d c3 90 f3 0f 1e fa 48 8b 7f 10 48 85 ff 74 0b e9 ce c6 ff ff 66 0f 1f 44 00 00 48 83 ec 08 48 89 d7 e8 8c 3c 17 00 <48> 8b 40 18 48 8b 78 10 e8 df 03 09 00 48 83 c4 08 48 89 c7 e9 a3 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Dec 16 14:34:43 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20211023, 5.11.0-42-generic, x86_64: installed vhba, 20211023, 5.11.0-44-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (365 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine:
[Touch-packages] [Bug 1955026] Re: Upgrade openssl to 3.0.1 on Jammy
** Changed in: openssl (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1955026 Title: Upgrade openssl to 3.0.1 on Jammy Status in openssl package in Ubuntu: Fix Committed Bug description: Upstream has released a new version 3.0.1, including a security fix. https://mta.openssl.org/pipermail/openssl-announce/2021-December/000212.html https://mta.openssl.org/pipermail/openssl-announce/2021-December/000213.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1955026/+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 1955026] Re: Upgrade openssl to 3.0.1 on Jammy
Attached is a debdiff for this upgrade. Alternatively, a packaged version has been uploaded to the following PPA, just pop the last changelog entry to get the proper uploadable version: https://launchpad.net/~schopin/+archive/ubuntu/test- ppa/+sourcepub/13051752/+listing-archive-extra ** Patch added: "openssl.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1955026/+attachment/5547978/+files/openssl.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1955026 Title: Upgrade openssl to 3.0.1 on Jammy Status in openssl package in Ubuntu: New Bug description: Upstream has released a new version 3.0.1, including a security fix. https://mta.openssl.org/pipermail/openssl-announce/2021-December/000212.html https://mta.openssl.org/pipermail/openssl-announce/2021-December/000213.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1955026/+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 1955026] [NEW] Upgrade openssl to 3.0.1 on Jammy
*** This bug is a security vulnerability *** Public security bug reported: Upstream has released a new version 3.0.1, including a security fix. https://mta.openssl.org/pipermail/openssl-announce/2021-December/000212.html https://mta.openssl.org/pipermail/openssl-announce/2021-December/000213.html ** Affects: openssl (Ubuntu) Importance: High Status: New ** Tags: transition-openssl3-jj -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1955026 Title: Upgrade openssl to 3.0.1 on Jammy Status in openssl package in Ubuntu: New Bug description: Upstream has released a new version 3.0.1, including a security fix. https://mta.openssl.org/pipermail/openssl-announce/2021-December/000212.html https://mta.openssl.org/pipermail/openssl-announce/2021-December/000213.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1955026/+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 1953301] Re: Segfault on AArch64 caused by OpenSSL affecting numerous packages
Sounds suspiciously similar to https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1951279 but I'd like confirmation that the situation described in the meson issue comment (TLS 1.2 with ECDHE-RSA-CHACHA20-POLY1305) also applies there before marking as duplicate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1953301 Title: Segfault on AArch64 caused by OpenSSL affecting numerous packages Status in openssl package in Ubuntu: Incomplete Bug description: OpenSSL causes crashes when reaching to some URLs on AArch64 platform, affecting Ubuntu, but not Fedora for instance. Initially reported in https://mediasoup.discourse.group/t/mediasoup- worker-default-make-failed/3647/12, more details and reproductions in https://github.com/mesonbuild/meson/issues/9690 Affects curl, wget, python and probably everything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1953301/+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 1953301] Re: Segfault on AArch64 caused by OpenSSL affecting numerous packages
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1953301 Title: Segfault on AArch64 caused by OpenSSL affecting numerous packages Status in openssl package in Ubuntu: Incomplete Bug description: OpenSSL causes crashes when reaching to some URLs on AArch64 platform, affecting Ubuntu, but not Fedora for instance. Initially reported in https://mediasoup.discourse.group/t/mediasoup- worker-default-make-failed/3647/12, more details and reproductions in https://github.com/mesonbuild/meson/issues/9690 Affects curl, wget, python and probably everything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1953301/+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 1077796] Re: /bin/kill no longer works with negative PID
Most shells (including bash, zsh) have a built-in for kill so it's done internally. Some shells don't so it executes /bin/kill instead which has this issue. One comment noted this was fixed at some point in 2013 in version 3.3.4 but it apparently broke again at some point and is broken at least in 20.04 Focal's v3.3.16. This was recently fixed again upstream here: https://gitlab.com/procps-ng/procps/-/merge_requests/77 Upstream v3.3.16 (in 20.04 Focal and 20.10 Hirsute) was released Dec 2019 without this fix. That fix was submitted upstream 3 years ago but only merged 11 months ago and was included in the v3.3.17 release which was made in Feb 2021 so not included in 20.04 Focal. 3.3.17 with the fix is already in 21.10 Impish. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1077796 Title: /bin/kill no longer works with negative PID Status in procps package in Ubuntu: Triaged Bug description: Incorrectly gives a usage message, eg: /bin/kill -1 -4321 ==> /bin/kill: invalid option -- '4' A workaround appears to be to use "--" before the PID, but this is unsatisfactory, as existing scripts would have to be modified when they shouldn't have to be. This problem has only appeared recently in 12.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1077796/+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
