[Touch-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Hello You-Sheng, or anyone else affected, Accepted libmbim into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libmbim/1.28.0-1~ubuntu20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: libmbim (Ubuntu) Importance: Undecided Status: New ** Also affects: libqmi (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: modemmanager (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libqmi (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libmbim (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: libmbim (Ubuntu) Status: New => Fix Released ** Changed in: libqmi (Ubuntu) Status: New => Fix Released ** Changed in: libmbim (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Jammy: Fix Committed Status in libqmi source package in Jammy: New Status in linux source package in Jammy: New Status in modemmanager source package in Jammy: New Bug description: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case - install modemmanager, libmbim, and libqmi from -proposed - reboot and try WWAN function to see if any regression there. - perform dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) The verification should be done on FM350 to ensure it's correctly handled but also on other hardware to verify that there are no regressions * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no regression. --- :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon runnin
[Touch-packages] [Bug 1993396] Re: Sync dnsmasq from Debian unstable for lunar
$ rmad dnsmasq dnsmasq | 2.86-1.1ubuntu2 | kinetic dnsmasq | 2.88-1 | lunar dnsmasq| 2.85-1 | stable dnsmasq| 2.88-1 | testing dnsmasq| 2.88-1 | unstable ** Changed in: dnsmasq (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 dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1993396 Title: Sync dnsmasq from Debian unstable for lunar Status in dnsmasq package in Ubuntu: Fix Released Bug description: Scheduled-For: ubuntu-23.01 Upstream: tbd Debian: 2.87-1.1 Ubuntu: 2.86-1.1ubuntu2 ### New Debian Changes ### dnsmasq (2.87-1.1) unstable; urgency=medium * Non-maintainer upload. * No source change upload to rebuild with debhelper 13.10. -- Michael Biebl Sat, 15 Oct 2022 12:01:25 +0200 dnsmasq (2.87-1) unstable; urgency=low * New upstream. (closes: #1001209, #1003156) * Include new NFTset support in the build. * Fix crash on netboot with DNS server disabled. (closes: #996332) * Fix rare lockup in DNSSEC. (closes: #1001576) * Close old bug. (closes: #902963) -- Simon Kelley Wed, 25 Sep 2022 23:11:25 + dnsmasq (2.86-1.1) unstable; urgency=medium * Non-maintainer upload. * Fix --address=/#/.. which was lost in 2.86. (closes: #995655) -- Michael Biebl Wed, 10 Nov 2021 22:05:45 +0100 dnsmasq (2.86-1) unstable; urgency=low * Fix debian/changelog format error. (closes: #986626) -- Simon Kelley Thu, 08 Apr 2021 22:39:00 +0100 dnsmasq (2.85-1) unstable; urgency=low * New upstream. * Includes fix to CVE-2021-3448. * Fix manpage typos. (closes: #986150) -- Simon Kelley Sat, 03 Apr 2021 22:17:23 +0100 dnsmasq (2.84-1.2) unstable; urgency=medium * Non-maintainer upload. * Bump old-version in dpkg-maintscript-helper dir_to_symlink calls to also clean up after upgrades to an earlier version in testing. -- Andreas Beckmann Thu, 01 Apr 2021 16:01:51 +0200 dnsmasq (2.84-1.1) unstable; urgency=medium * Non-maintainer upload. * Fix symlink to directory conversion for /usr/share/doc/dnsmasq. This is achieved by directly calling dpkg-maintscript-helper in the preinst, postinst, and postrm scripts, since the package does not use debhelper. (Closes: #985282) -- Sébastien Villemot Sun, 28 Mar 2021 10:55:07 +0200 dnsmasq (2.84-1) unstable; urgency=low * New upstream. -- Simon Kelley Sun, 24 Jan 2021 22:02:01 + dnsmasq (2.83-1) unstable; urgency=high * New upstream. * Includes fixes to CVE-2020-25681 - CVE-2020-25687 inclusive. -- Simon Kelley Fri, 15 Jan 2021 22:22:41 + dnsmasq (2.82-1) unstable; urgency=low * New upstream. -- Simon Kelley Fri, 26 Jun 2020 22:22:41 + dnsmasq (2.81-4) unstable; urgency=low * Remove runit support when building for Ubuntu. (closes: #960401) -- Simon Kelley Fri, 26 Jun 2020 21:52:44 + dnsmasq (2.81-3) unstable; urgency=low * Fixes to control file for bug 958100 -- Simon Kelley Sun, 19 Apr 2020 21:44:12 + dnsmasq (2.81-2) unstable; urgency=low * Fix FTBFS on kFreeBSD. (closes: #958100) -- Simon Kelley Sat, 18 Apr 2020 18:34:15 + dnsmasq (2.81-1) unstable; urgency=low * New upstream. * Fix nodocs/nodoc confusion in rules. (closes: #922758) * Add Vcs-* fields to control. (closes: #922422) * Add systemd support for multiple daemon instances. (closes: #914305) * Add note explaining that ENABLED is SYSV-init only. (closes: #914755) ### Old Ubuntu Delta ### dnsmasq (2.86-1.1ubuntu2) kinetic; urgency=medium * src/forward.c: Do not refuse retries from client DNS queries. Behaviour to stop infinite loops when all servers return REFUSED was wrongly activated on client retries, resulting in incorrect REFUSED replies to client retries. The code added here is a cherry pick released in upstream version 2.87, originating at https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2561f9fe0eb9c0be (LP: #1981794) -- Lena Voytek Fri, 30 Sep 2022 08:42:39 -0700 dnsmasq (2.86-1.1ubuntu1) kinetic; urgency=medium * SECURITY UPDATE: Heap use after free - 03345ecefeb0d82e3c3a4c28f27c3554f0611b39: Fix write-after-free error in DHCPv6 code in src/rfc3315.c. - CVE-2022-0934 -- Leonidas Da Silva Barbosa Wed, 13 Jul 2022 12:10:53 -0300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1993396/+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/ListHe
[Touch-packages] [Bug 1999782] Re: Add ACCEL_LOCATION=base property for Dell clamshell models
** Package changed: systemd-hwe (Ubuntu) => systemd (Ubuntu) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) -- 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/1999782 Title: Add ACCEL_LOCATION=base property for Dell clamshell models Status in OEM Priority Project: New Status in systemd package in Ubuntu: New Bug description: [ Impact ] * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerator. [ Test Plan ] * On Dell laptops with model SKU 0C00 or 0C02 * Rotate the laptop and the display 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. [ Other info ] * Commit backport from Upstream: https://github.com/systemd/systemd/pull/25724 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1999782/+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 1999782] [NEW] Add ACCEL_LOCATION=base property for Dell clamshell models
You have been subscribed to a public bug: [ Impact ] * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerator. [ Test Plan ] * On Dell laptops with model SKU 0C00 or 0C02 * Rotate the laptop and the display 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. [ Other info ] * Commit backport from Upstream: https://github.com/systemd/systemd/pull/25724 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1998072 somerville -- Add ACCEL_LOCATION=base property for Dell clamshell models https://bugs.launchpad.net/bugs/1999782 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd 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 1988730] Re: package libsasl2-modules provides only unsafe SASL bind mechanims
** Changed in: cyrus-sasl2 (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1988730 Title: package libsasl2-modules provides only unsafe SASL bind mechanims Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Jammy: In Progress Status in cyrus-sasl2 package in Debian: Fix Released Bug description: [ Impact ] The SASL SCRAM mechanism is incorrectly part of the libsasl2-modules- gssapi-mit package. It has nothing to do with MIT or GSSAPI, and should be in libsasl2-modules. Normally this would just be an annoyance, but it just so happens that this also prevents to have the SCRAM mechanism coexist with the GSSAPI Heimdal one, because libsasl2-modules-gssapi-{mit,heimdal} conflict with each other. This change is moving a file from one package to another, so appropriate breaks/replaces changes have to be made. This move follows case #10 from the package transition table[1]. [ Test Plan ] This test plan revolves around dependency checking and upgrades, to make sure we don't: - have conflicting files which would break an upgrade - have no loss of functionality after an upgrade (since a plugin moved between packages) a) SCRAM remains installed # Install the package that provides SCRAM in jammy $ sudo apt install libsasl2-modules-gssapi-mit # Confirm mechanism is there and belongs to libsasl2-modules-gssapi- mit: $ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 lrwxrwxrwx 1 root root 18 Aug 16 20:08 /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25 $ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 libsasl2-modules-gssapi-mit:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 # list installed sasl2 packages: $ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}' libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1 libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1 libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1 libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1 # dist-upgrade or install the new sasl2 packages from proposed # Confirm the same packages are installed as before the upgrade, just at their newer versions: libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1 libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1 libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1 libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.1 # Confirm the scram mechanism is still there, as before: $ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 lrwxrwxrwx 1 root root 18 Aug 16 20:08 /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25 # But now it belongs to the libsasl2-modules package: $ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 b) Following (a), perform a release-upgrade to kinetic, and confirm that the same sasl2 packages remain installed, but now at the kinetic version: $ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}' libsasl2-2:amd64 2.1.28+dfsg-6ubuntu2 libsasl2-modules:amd64 2.1.28+dfsg-6ubuntu2 libsasl2-modules-db:amd64 2.1.28+dfsg-6ubuntu2 libsasl2-modules-gssapi-mit:amd64 2.1.28+dfsg-6ubuntu2 And that the scram mechanism is there, and still belongs to the libsasl2-modules package: $ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 lrwxrwxrwx 1 root root 18 Aug 16 20:08 /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25 $ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 c) A jammy system WITHOUT the SCRAM mechanism available (i.e., libsasl2-modules-gssapi-mit is NOT installed), will get SCRAM available after the upgrade, but without installing any new package. # Start with these sasl2 packages installed on jammy: libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1 libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1 libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1 # Confirm SCRAM is not installed: $ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 ls: cannot access '/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2': No such file or directory # Upgrade to the packages in proposed # Confirm no new sasl2 packages were installed: $ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}' libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1 libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1 libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1 # Verify that SCRAM is now available, and part of the libsasl2-modules package: $ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 lrwxrwxrwx 1 root root 18 Aug 16 20:08 /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25 $ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 libsasl2-modules:amd64: /usr/lib/x86_64-lin
[Touch-packages] [Bug 1993800] Re: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2>
** Changed in: llvm-toolchain-15 (openSUSE) Status: Unknown => Fix Released -- 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/1993800 Title: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> Status in LLVM: Fix Released Status in llvm-toolchain-15 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in llvm-toolchain-15 package in openSUSE: Fix Released Bug description: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> 0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 0x2f84090:1, Constant:i32<4> 0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), > 0x2aad434, 0x2f63a30, Constant:i32<64> 0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23 0x2f51c10: i32 = Register %23 0x2f82500: i32 = Constant<64> 0x2f81b28: i32 = Constant<4> 0x2f81e40: i32 = Constant<2> In function: fs_variant_partial [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic- armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz] Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't determine what project "fs_variant_partial" is in. Sounds like it might be in some old version of Mesa? The start of the log suggests it's running on focal. To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1993800/+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 1993800]
openQA test passes. -- 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/1993800 Title: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> Status in LLVM: Fix Released Status in llvm-toolchain-15 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in llvm-toolchain-15 package in openSUSE: Fix Released Bug description: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> 0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 0x2f84090:1, Constant:i32<4> 0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), > 0x2aad434, 0x2f63a30, Constant:i32<64> 0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23 0x2f51c10: i32 = Register %23 0x2f82500: i32 = Constant<64> 0x2f81b28: i32 = Constant<4> 0x2f81e40: i32 = Constant<2> In function: fs_variant_partial [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic- armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz] Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't determine what project "fs_variant_partial" is in. Sounds like it might be in some old version of Mesa? The start of the log suggests it's running on focal. To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1993800/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
The proposed packages evince and evince-common versions 42.3-0ubuntu3 from jammy-proposed fixes the problem for me on MATE 22.04. Much obliged. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Fix Released Status in libproxy package in Ubuntu: Invalid Status in evince source package in Jammy: Fix Committed Status in evince source package in Kinetic: Fix Committed Status in evince package in Debian: New Bug description: * Impact Evince hangs when opening the printing dialog for some users with a remote printer configured and connected * Test case - configure a remote printer and turn it on - open a pdf - try to print the document the print dialog shouldn't freeze the viewer * What could go wrong The change is only allowing access to one extra system binary from the apparmor profile so shouldn't really have an impact on the software behaviour. If the syntax or content of the change was incorrect it could make the apparmor profile not been loaded anymore or block access to thing that should be allowed, so ensure that opening documents, printing and thumbnailing are still working -- audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1999275] Re: systemd-binfmt.service fails in tests-in-lxd
This has been resolved upstream[1] and I will bring the patches into lunar. [1] https://github.com/systemd/systemd/pull/25693 ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- 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/1999275 Title: systemd-binfmt.service fails in tests-in-lxd Status in systemd package in Ubuntu: Triaged Bug description: The systemd-binfmt.service requires read-write access to /proc/sys/fs/binfmt_misc, but this is not possible in unprivileged LXD containers without binfmt_misc namespace support in the kernel [1]. When this service is triggered, we get the following failure from test_no_failed within tests-in-lxd: No failed units ... journal for failed service systemd-binfmt.service --- Dec 08 10:43:37 autopkgtest-lxd-qicaxl systemd[1]: Starting Set Up Additional Binary Formats... Dec 08 10:43:37 autopkgtest-lxd-qicaxl systemd-binfmt[99]: Failed to flush binfmt_misc rules, ignoring: Permission denied Dec 08 10:43:37 autopkgtest-lxd-qicaxl systemd-binfmt[99]: /usr/lib/binfmt.d/python3.10.conf:1: Failed to delete rule 'python3.10', ignoring: Permission denied Dec 08 10:43:37 autopkgtest-lxd-qicaxl systemd-binfmt[99]: /usr/lib/binfmt.d/python3.10.conf:1: Failed to add binary format 'python3.10': Permission denied Dec 08 10:43:37 autopkgtest-lxd-qicaxl systemd[1]: systemd-binfmt.service: Main process exited, code=exited, status=1/FAILURE Dec 08 10:43:37 autopkgtest-lxd-qicaxl systemd[1]: systemd-binfmt.service: Failed with result 'exit-code'. Dec 08 10:43:37 autopkgtest-lxd-qicaxl systemd[1]: Failed to start Set Up Additional Binary Formats. FAIL test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.METFVA/build.LjB/real-tree/debian/tests/boot-and-services", line 74, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['systemd-binfmt.service loaded failed failed Set Up Additional Binary Formats'] != [] First list contains 1 additional elements. First extra element 0: 'systemd-binfmt.service loaded failed failed Set Up Additional Binary Formats' - ['systemd-binfmt.service loaded failed failed Set Up Additional Binary Formats'] + [] The systemd-binfmt.service is only started if there is a configuration to be loaded from one of the valid configuration directories (e.g. /usr/lib/binfmt.d/python3.10.conf). Previously, no such file was installed in the test LXD images, but a recent upload of python3.10 added support for systemd-binfmt [2]. [1] https://discuss.linuxcontainers.org/t/3-1-0-binfmt-support-service-in-unprivileged-guest-requires-write-access-on-hosts-proc-sys-fs-binfmt-misc/5249 [2] https://launchpadlibrarian.net/632281245/python3.10_3.10.8-1_3.10.8-3.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1999275/+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 1889443] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1889443 Title: "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...` Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Triaged Status in apport source package in Focal: Incomplete Status in apport source package in Jammy: Fix Released Bug description: [ Impact ] Extracting a crash file will always fail in case the crash report was processed. [ Test plan ] 1. Create crash (e.g. with divide-by-zero): ``` sudo apt install chaos-marmosets divide-by-zero ``` 2. Click on "show details" in Apport crash UI, then close it 3. exract crash report: ``` tmpdir=$(mktemp -d) apport-unpack /var/crash/_usr_bin_divide-by-zero.1000.crash "$tmpdir" rm -rf "$tmpdir" ``` The extraction should work and not print a stack trace. [ Where problems could occur ] The change touches the problem report reading code which is used in several places. This could cause regressions in reading the problem report. [ Original report ] The crash file I'm using is as-produced by the system (on groovy), and appears to have an empty value for separator: $ grep separator /var/crash/_usr_bin_neomutt.1000.crash separator: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 77, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 269, in extract_keys raise ValueError('%s has no binary content' % ValueError: ['separator'] has no binary content ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu42 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:117:1620030:2020-07-29 12:16:57.045274496 -0400:2020-07-29 12:19:15.559243636 -0400:/var/crash/_usr_bin_neomutt.1000.crash 640:1000:117:4399480:2020-07-23 10:30:21.433552906 -0400:2020-07-23 10:30:18.921508067 -0400:/var/crash/_usr_bin_pavucontrol.1000.crash 640:1000:117:29909:2020-07-29 12:19:15.603244279 -0400:2020-07-29 12:19:15.603244279 -0400:/var/crash/_usr_bin_apport-unpack.1000.crash CurrentDesktop: i3 Date: Wed Jul 29 12:22:54 2020 InstallationDate: Installed on 2019-05-07 (448 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to groovy on 2020-06-22 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1889443/+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 1889443] Re: "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...`
This bug was fixed in the package apport - 2.20.11-0ubuntu82.3 --- apport (2.20.11-0ubuntu82.3) jammy; urgency=medium * Replace deprecated 'imp' module (LP: #1947425) * Fix KeyError: 'CasperMD5json' (LP: #1964828) * apport-kde: Fix inverse order of choices (LP: #1967965) * apport-unpack: Fix ValueError: ['separator'] has no binary content (LP: #1889443) * test: - Mock add_gdb_info calls in KDE UI tests - Fix KDE UI tests if whoopsie.path is disabled - Fix race with progress dialog in KDE UI tests - Run UI KDE tests again - Determine source package dynamically in test_run_crash_kernel (LP: #1992172) -- Benjamin Drung Thu, 24 Nov 2022 12:47:19 +0100 ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1889443 Title: "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...` Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Triaged Status in apport source package in Focal: Incomplete Status in apport source package in Jammy: Fix Released Bug description: [ Impact ] Extracting a crash file will always fail in case the crash report was processed. [ Test plan ] 1. Create crash (e.g. with divide-by-zero): ``` sudo apt install chaos-marmosets divide-by-zero ``` 2. Click on "show details" in Apport crash UI, then close it 3. exract crash report: ``` tmpdir=$(mktemp -d) apport-unpack /var/crash/_usr_bin_divide-by-zero.1000.crash "$tmpdir" rm -rf "$tmpdir" ``` The extraction should work and not print a stack trace. [ Where problems could occur ] The change touches the problem report reading code which is used in several places. This could cause regressions in reading the problem report. [ Original report ] The crash file I'm using is as-produced by the system (on groovy), and appears to have an empty value for separator: $ grep separator /var/crash/_usr_bin_neomutt.1000.crash separator: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 77, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 269, in extract_keys raise ValueError('%s has no binary content' % ValueError: ['separator'] has no binary content ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu42 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:117:1620030:2020-07-29 12:16:57.045274496 -0400:2020-07-29 12:19:15.559243636 -0400:/var/crash/_usr_bin_neomutt.1000.crash 640:1000:117:4399480:2020-07-23 10:30:21.433552906 -0400:2020-07-23 10:30:18.921508067 -0400:/var/crash/_usr_bin_pavucontrol.1000.crash 640:1000:117:29909:2020-07-29 12:19:15.603244279 -0400:2020-07-29 12:19:15.603244279 -0400:/var/crash/_usr_bin_apport-unpack.1000.crash CurrentDesktop: i3 Date: Wed Jul 29 12:22:54 2020 InstallationDate: Installed on 2019-05-07 (448 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to groovy on 2020-06-22 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1889443/+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 1947425] Re: Use of deprecated 'imp' module
This bug was fixed in the package apport - 2.20.11-0ubuntu82.3 --- apport (2.20.11-0ubuntu82.3) jammy; urgency=medium * Replace deprecated 'imp' module (LP: #1947425) * Fix KeyError: 'CasperMD5json' (LP: #1964828) * apport-kde: Fix inverse order of choices (LP: #1967965) * apport-unpack: Fix ValueError: ['separator'] has no binary content (LP: #1889443) * test: - Mock add_gdb_info calls in KDE UI tests - Fix KDE UI tests if whoopsie.path is disabled - Fix race with progress dialog in KDE UI tests - Run UI KDE tests again - Determine source package dynamically in test_run_crash_kernel (LP: #1992172) -- Benjamin Drung Thu, 24 Nov 2022 12:47:19 +0100 ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1947425 Title: Use of deprecated 'imp' module Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Fix Released Bug description: Impact -- The deprecation warning is just a warning, but it clutters the output and can lead to misattributions in case something does not work as expected. Test Case - 1. apt install apport 2. Execute following command: python3 -Wonce -c "import apport.report" 3. There should be no output. Where problems could occur -- Except for changes to the test cases, _check_interpreted is the only consumer for the changed code. Breakage in this code paths can lead to wrongly assume that the crashing Python code is an interpreted script or not. This can lead to reports that have only ExecutablePath set (and not InterpreterPath). Original Description Code using apport/report.py will see the following warning: $ python3 -Wonce -c "import apport.report" /usr/lib/python3/dist-packages/apport/report.py:13 /usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import fnmatch, glob, traceback, errno, sys, atexit, locale, imp, stat The 'imp' module is slated for removal in Python 3.12. https://github.com/python/cpython/blob/main/Lib/imp.py#L31 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1947425/+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 1947425] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1947425 Title: Use of deprecated 'imp' module Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Fix Released Bug description: Impact -- The deprecation warning is just a warning, but it clutters the output and can lead to misattributions in case something does not work as expected. Test Case - 1. apt install apport 2. Execute following command: python3 -Wonce -c "import apport.report" 3. There should be no output. Where problems could occur -- Except for changes to the test cases, _check_interpreted is the only consumer for the changed code. Breakage in this code paths can lead to wrongly assume that the crashing Python code is an interpreted script or not. This can lead to reports that have only ExecutablePath set (and not InterpreterPath). Original Description Code using apport/report.py will see the following warning: $ python3 -Wonce -c "import apport.report" /usr/lib/python3/dist-packages/apport/report.py:13 /usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import fnmatch, glob, traceback, errno, sys, atexit, locale, imp, stat The 'imp' module is slated for removal in Python 3.12. https://github.com/python/cpython/blob/main/Lib/imp.py#L31 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1947425/+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 1964828] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1964828 Title: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json' Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: New Status in apport source package in Jammy: Fix Released Bug description: [Impact] If the user reports a bug and rejects to enter the root password for collecting information (like the CasperMD5json), the Ubuntu add_info hook will fail with a stack trace. The remaining code for collecting more information is not executed. So the resulting bug reports will be less helpful. The check_for_disk_error call is not reached and therefore skipped. [Test Plan] 1. Install Ubuntu (e.g. from ubuntu-22.04-desktop-amd64.iso) 2. Open a terminal 3. Run: ubuntu-bug -f 4. Select "installer" and click on OK 5. Click on "abort" when ask for the password 6. The terminal should not show a stacktrace [Where problems could occur] The changed code is the Ubuntu add_info hook. So this hook could fail due to a regression or reveal bugs in the later code path. The later code path could cause more more load on the users machine (but only when the user wants to report the issue). Apport will catch failing add_info hooks and store the failure in the report. [Orinial report] ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in attach_casper_md5check check = json.loads(report['CasperMD5json']) File "/usr/lib/python3.10/collections/__init__.py", line 1102, in __getitem__ raise KeyError(key) KeyError: 'CasperMD5json' kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module "colorreload-gtk-module" ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperVersion: 1.467 CurrentDesktop: KDE Date: Mon Mar 14 21:22:23 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220314) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1964828/+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 1964828] Re: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'
This bug was fixed in the package apport - 2.20.11-0ubuntu82.3 --- apport (2.20.11-0ubuntu82.3) jammy; urgency=medium * Replace deprecated 'imp' module (LP: #1947425) * Fix KeyError: 'CasperMD5json' (LP: #1964828) * apport-kde: Fix inverse order of choices (LP: #1967965) * apport-unpack: Fix ValueError: ['separator'] has no binary content (LP: #1889443) * test: - Mock add_gdb_info calls in KDE UI tests - Fix KDE UI tests if whoopsie.path is disabled - Fix race with progress dialog in KDE UI tests - Run UI KDE tests again - Determine source package dynamically in test_run_crash_kernel (LP: #1992172) -- Benjamin Drung Thu, 24 Nov 2022 12:47:19 +0100 ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1964828 Title: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json' Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: New Status in apport source package in Jammy: Fix Released Bug description: [Impact] If the user reports a bug and rejects to enter the root password for collecting information (like the CasperMD5json), the Ubuntu add_info hook will fail with a stack trace. The remaining code for collecting more information is not executed. So the resulting bug reports will be less helpful. The check_for_disk_error call is not reached and therefore skipped. [Test Plan] 1. Install Ubuntu (e.g. from ubuntu-22.04-desktop-amd64.iso) 2. Open a terminal 3. Run: ubuntu-bug -f 4. Select "installer" and click on OK 5. Click on "abort" when ask for the password 6. The terminal should not show a stacktrace [Where problems could occur] The changed code is the Ubuntu add_info hook. So this hook could fail due to a regression or reveal bugs in the later code path. The later code path could cause more more load on the users machine (but only when the user wants to report the issue). Apport will catch failing add_info hooks and store the failure in the report. [Orinial report] ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in attach_casper_md5check check = json.loads(report['CasperMD5json']) File "/usr/lib/python3.10/collections/__init__.py", line 1102, in __getitem__ raise KeyError(key) KeyError: 'CasperMD5json' kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module "colorreload-gtk-module" ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperVersion: 1.467 CurrentDesktop: KDE Date: Mon Mar 14 21:22:23 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220314) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1964828/+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 1967965] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1967965 Title: apport-kde: "Other problem" and "Display" options are swapped Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Confirmed Status in apport source package in Jammy: Fix Released Bug description: [ Impact ] Due to this bug, users on KDE have hard times to report generic problems against Ubuntu. [ Testcase ] 1. Run: /usr/share/apport/apport-kde -f 2. Select "Display (X.org)" and click OK 3. Then a window asking "What display problem do you observe?" should be presented. [ Where problems could occur ] Since this fix enables users to properly report generic problems, it can reveal bugs in the later stage. [ Other Info ] Since this fix touched the KDE part, the SRU will also enable the KDE UI tests again and repair them to make them run. [ Original report ] When attempting to report https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967963 I was unable to use `ubuntu-bug firefox`, so I just ran `ubuntu-bug`. However doing so gave me a menu with unrelated option (as expected) and an "Other problem..." option. I assumed this was for generic other bugs, as I think is reasonable; however, it brings me to a menu that only makes sense for display-related bugs. I think this text should be changed to note that; perhaps "Other display problem...". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:124:13488049:2022-03-30 13:20:08.905176436 -0500:2022-03-30 13:20:07.977480154 -0500:/var/crash/_usr_bin_telegram-desktop.1000.crash 640:0:124:755694:2022-03-30 13:17:26.598466630 -0500:2022-03-30 13:17:26.258453989 -0500:/var/crash/_usr_libexec_udisks2_udisksd.0.crash CurrentDesktop: KDE Date: Tue Apr 5 19:58:56 2022 InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1967965/+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 1967965] Re: apport-kde: "Other problem" and "Display" options are swapped
This bug was fixed in the package apport - 2.20.11-0ubuntu82.3 --- apport (2.20.11-0ubuntu82.3) jammy; urgency=medium * Replace deprecated 'imp' module (LP: #1947425) * Fix KeyError: 'CasperMD5json' (LP: #1964828) * apport-kde: Fix inverse order of choices (LP: #1967965) * apport-unpack: Fix ValueError: ['separator'] has no binary content (LP: #1889443) * test: - Mock add_gdb_info calls in KDE UI tests - Fix KDE UI tests if whoopsie.path is disabled - Fix race with progress dialog in KDE UI tests - Run UI KDE tests again - Determine source package dynamically in test_run_crash_kernel (LP: #1992172) -- Benjamin Drung Thu, 24 Nov 2022 12:47:19 +0100 ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1967965 Title: apport-kde: "Other problem" and "Display" options are swapped Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Confirmed Status in apport source package in Jammy: Fix Released Bug description: [ Impact ] Due to this bug, users on KDE have hard times to report generic problems against Ubuntu. [ Testcase ] 1. Run: /usr/share/apport/apport-kde -f 2. Select "Display (X.org)" and click OK 3. Then a window asking "What display problem do you observe?" should be presented. [ Where problems could occur ] Since this fix enables users to properly report generic problems, it can reveal bugs in the later stage. [ Other Info ] Since this fix touched the KDE part, the SRU will also enable the KDE UI tests again and repair them to make them run. [ Original report ] When attempting to report https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967963 I was unable to use `ubuntu-bug firefox`, so I just ran `ubuntu-bug`. However doing so gave me a menu with unrelated option (as expected) and an "Other problem..." option. I assumed this was for generic other bugs, as I think is reasonable; however, it brings me to a menu that only makes sense for display-related bugs. I think this text should be changed to note that; perhaps "Other display problem...". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:124:13488049:2022-03-30 13:20:08.905176436 -0500:2022-03-30 13:20:07.977480154 -0500:/var/crash/_usr_bin_telegram-desktop.1000.crash 640:0:124:755694:2022-03-30 13:17:26.598466630 -0500:2022-03-30 13:17:26.258453989 -0500:/var/crash/_usr_libexec_udisks2_udisksd.0.crash CurrentDesktop: KDE Date: Tue Apr 5 19:58:56 2022 InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1967965/+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 1992172] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1992172 Title: test_run_crash_kernel fails on ppc64el Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: New Status in apport source package in Focal: New Status in apport source package in Jammy: Fix Released Bug description: [Impact] The autopkgtest for apport 2.23.1-0ubuntu1 fails on ppc64el: ``` == FAIL: test_run_crash_kernel (tests.integration.test_ui.T) run_crash() for a kernel error -- Traceback (most recent call last): File "/usr/lib/python3.10/unittest/mock.py", line 1369, in patched return func(*newargs, **newkeywargs) File "/tmp/autopkgtest.W5WLIN/autopkgtest_tmp/tests/integration/test_ui.py", line 1617, in test_run_crash_kernel self.assertEqual( AssertionError: 'http://linux.bugs.example.com/5' != 'http://linux-signed.bugs.example.com/5' - http://linux.bugs.example.com/5 + http://linux-signed.bugs.example.com/5 ? +++ -- ``` Full log: https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/ppc64el/a/apport/20221007_113450_023d9@/log.gz [Test Plan] Check that the autopkgtest succeed all architectures (except for i386). [Where problems could occur] The test cases are only part of the apport source package and are not copied in any binary packages. Changes to the test will only affect the package build and test execution. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1992172/+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 1992172] Re: test_run_crash_kernel fails on ppc64el
This bug was fixed in the package apport - 2.20.11-0ubuntu82.3 --- apport (2.20.11-0ubuntu82.3) jammy; urgency=medium * Replace deprecated 'imp' module (LP: #1947425) * Fix KeyError: 'CasperMD5json' (LP: #1964828) * apport-kde: Fix inverse order of choices (LP: #1967965) * apport-unpack: Fix ValueError: ['separator'] has no binary content (LP: #1889443) * test: - Mock add_gdb_info calls in KDE UI tests - Fix KDE UI tests if whoopsie.path is disabled - Fix race with progress dialog in KDE UI tests - Run UI KDE tests again - Determine source package dynamically in test_run_crash_kernel (LP: #1992172) -- Benjamin Drung Thu, 24 Nov 2022 12:47:19 +0100 ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1992172 Title: test_run_crash_kernel fails on ppc64el Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: New Status in apport source package in Focal: New Status in apport source package in Jammy: Fix Released Bug description: [Impact] The autopkgtest for apport 2.23.1-0ubuntu1 fails on ppc64el: ``` == FAIL: test_run_crash_kernel (tests.integration.test_ui.T) run_crash() for a kernel error -- Traceback (most recent call last): File "/usr/lib/python3.10/unittest/mock.py", line 1369, in patched return func(*newargs, **newkeywargs) File "/tmp/autopkgtest.W5WLIN/autopkgtest_tmp/tests/integration/test_ui.py", line 1617, in test_run_crash_kernel self.assertEqual( AssertionError: 'http://linux.bugs.example.com/5' != 'http://linux-signed.bugs.example.com/5' - http://linux.bugs.example.com/5 + http://linux-signed.bugs.example.com/5 ? +++ -- ``` Full log: https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/ppc64el/a/apport/20221007_113450_023d9@/log.gz [Test Plan] Check that the autopkgtest succeed all architectures (except for i386). [Where problems could occur] The test cases are only part of the apport source package and are not copied in any binary packages. Changes to the test will only affect the package build and test execution. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1992172/+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 1991761] Re: Backport packages for 22.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted spirv-llvm-translator-15 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/spirv-llvm- translator-15/15.0.0-1~ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: spirv-llvm-translator-15 (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in libdrm source package in Jammy: In Progress Status in llvm-toolchain-15 source package in Jammy: In Progress Status in mesa source package in Jammy: In Progress Status in spirv-headers source package in Jammy: Fix Committed Status in spirv-llvm-translator-14 source package in Jammy: In Progress Status in spirv-llvm-translator-15 source package in Jammy: Fix Committed Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-headers - needed by s-l-t-15 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. spirv-headers: - test reverse-build-deps that they still build Reverse-Build-Depends * glslang * intel-graphics-compiler * spirv-llvm-translator-14 * spirv-llvm-translator-15 * spirv-tools * vkbasalt * vkd3d * vulkan-validationlayers [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 1724623] Re: Update ubuntu cloud info
Upstream merge request for parsing /etc/cloud/build.info: https://github.com/canonical/apport/pull/50 Please review https://github.com/canonical/apport/pull/50/commits/76e0f3475074a44fddd9e299489a1c32a811ba9d and let me know if you are happy with _BUILD_INFO_KEY_MAPPING or if there are better names. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1724623 Title: Update ubuntu cloud info Status in apport package in Ubuntu: New Status in cloud-init package in Ubuntu: New Bug description: add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul. Issues: - Using the presence of cloud-init to flag an image as a cloud image is incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images) - Using the presence of EC2 metadata source is incorrect as many non-EC2 clouds provide EC2 metadata. Thus we have bugs like bug #1722946 that are tagged as an 'ec2-images' bug which are clearly on openstack - Marking all bugs that have cloud-init but no EC2 metadata source as an 'uec-images' bug uses a name that no longer has meaning. Solution: - If cloud-init is present, check for /etc/cloud/build.info to indicate an Ubuntu cloud images, tag as 'cloud-images'. Pull the build_name and serial from that file into the bug comments. - If cloud-init is present, check for the presence of /run/cloud-init/cloud.cfg. Parse this yaml to determine the datasource type. Add the datasource used to the bug comment. I have filed bug #1724626 to ask cloud-init development to surface more information from ds-identify to help ID the cloud so that we can better tag/annotate the bug. There may also be some info we can get to indicate the image ID on more clouds than just AWS. At a minimum I would like to see dsidentify make the EC2 platform it found available for consumers in cloud.cfg. This would allow us to identify AWS EC2 from look-alike datasources so that we can tag a bug as ec2-images for bug really on AWS and add EC2 specific fields to the description/attachments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1724623/+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 1999104] Re: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort
** Tags removed: sts-sponsor-halves -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1999104 Title: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort Status in libunwind package in Ubuntu: Fix Released Status in libunwind source package in Bionic: In Progress Status in libunwind source package in Focal: In Progress Bug description: [Impact] On architectures other than i386 and amd64, the C++ exception support in libunwind appears to be broken, always failing and calling std::terminate() which leads to the program aborting. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0xf7c2daac in __GI_abort () at abort.c:79 #2 0xf7e21868 in __gnu_cxx::__verbose_terminate_handler() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #3 0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6 #4 0xf7e1f280 in std::terminate() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #5 0xf7e1f5e0 in __cxa_rethrow () from /lib/aarch64-linux-gnu/libstdc++.so.6 #6 0xf7e21804 in __gnu_cxx::__verbose_terminate_handler() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #7 0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6 #8 0xf7e1f280 in std::terminate() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #9 0xf7e1f574 in __cxa_throw () from /lib/aarch64-linux-gnu/libstdc++.so.6 #10 0xf7fb9f50 in function_throws_int () at lib.cpp:9 #11 0x0d54 in main (argc=1, argv=0xfab8) at main.cpp:9 Compiling libunwind with --enable-cxx-exceptions enabled leads to _Unwind_RaiseException being called during __cxa_throw(), which fails to find a handler, and the generic std::terminate() is called instead, aborting the program. On i386 and amd64 this doesn't seem to be the case, and the libunwind handlers seem to be present. To fix, we only enable the configure option --enable-cxx-exceptions on i386 and amd64 only, in debian/rules. This lets other architectures fall back to the symbols provided by libgcc_s, which implementation works correctly. [Testcase] Ali Sadi has provided a reproducer program. Start an arm64 instance, for example, a c6g.medium instance on AWS, with either Bionic or Focal. $ wget https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635122/+files/libunwind.tar.gz $ sudo apt install -y build-essential libunwind-dev $ tar xvf libunwind.tar.gz && cd test $ make all There are two executable, main and main_unwind. main is not linked to libunwind, and main_unwind is linked to libunwind. $ ./main int throws lib int caught main $ ./main_unwind terminate called after throwing an instance of 'int' terminate called recursively Aborted (core dumped) If you install the test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf350246-test $ make clean $ sudo apt install -y libunwind-dev $ make all $ ./main int throws lib int caught main $ ./main_unwind int throws lib int caught main The exception is caught as expected the program does not abort. [Where problems could occur] For architectures other than i386 and amd64, we are changing from libunwind provided exception handlers for __cxa_throw(), and using those provided by libgcc_s instead. There are a few reverse dependencies for libunwind-dev and libunwind8, which need to be considered: $ apt rdepends libunwind-dev libunwind-dev Reverse Depends: Depends: libunwind-setjmp0-dev (= 1.2.1-9build1) Depends: libefl-all-dev t$ apt rdepends libunwind-dev8 libunwind8 Reverse Depends: Depends: libunwind-dev (= 1.2.1-9build1) Depends: xvfb Depends: xnest Depends: xdmx Depends: xwayland Depends: xserver-xorg-core Depends: xserver-xephyr Depends: linux-tools-5.4.0-* Depends: linux-raspi-tools-* Depends: linux-raspi2-tools-5.4.0-* Depends: linux-raspi2-5.4-tools-5.4.0-* Depends: linux-oracle-5.15-tools-5.15.0-* Depends: linux-lowlatency-hwe-5.15-tools-5.15.0-* Depends: linux-hwe-5.8-tools-5.8.0-* Depends: linux-hwe-5.15-tools-5.15.0-* Depends: linux-gke-tools-5.4.0-* Depends: linux-gke-5.15-tools-5.15.0-* Depends: linux-gcp-tools-5.4.0-* Depends: linux-gcp-5.15-tools-5.15.0-* Depends: linux-azure-tools-5.4.0-* Depends: linux-azure-5.15-tools-5.15.0-* Depends: linux-aws-tools-5.4.0-* Depends: linux-aws-5.8-tools-5.8.0-* Depends: linux-aws-5.15-tools-5.15.0-* Depends: xvfb Depends: xnest Depends: xdmx Depends: trafficserver Depends: tilix Depends: tigervnc-standalone-server Depends: tarantool Depends
[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info
> Which component is responsible for generating /etc/cloud/build.info? livecd-rootfs, during image creation time. https://git.launchpad.net/livecd-rootfs/tree/live-build/auto/build#n452 it'll have at least 1 value, serial (in the case of an OCI container), normally 2: serial, build_name > From my perspective add_cloud_init_data and get_ec2_data should be shipped by cloud-init, because they access data generated by cloud-init. I'll leave the cloud-init team to comment, but I actually disagree. `/run/cloud-init/instance-data.json` is one of several user parseable files generated by cloud-init. the "native" cloud-init error reporting would be to, as smoser said (back in 2018) is to do `cloud-init collect- logs`. That produces a tar file so it can't directly be added to the `apport` report. I'm not against shipping the cloud-init logs along with any cloud image based issue being reported. I'd have to dig in a little to see how `apport` currently creates a bundle, and how easy it'd be to add the cloud-init bundle as well. But know that we'll be delivering a _lot_ more information in the apport bug report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1724623 Title: Update ubuntu cloud info Status in apport package in Ubuntu: New Status in cloud-init package in Ubuntu: New Bug description: add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul. Issues: - Using the presence of cloud-init to flag an image as a cloud image is incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images) - Using the presence of EC2 metadata source is incorrect as many non-EC2 clouds provide EC2 metadata. Thus we have bugs like bug #1722946 that are tagged as an 'ec2-images' bug which are clearly on openstack - Marking all bugs that have cloud-init but no EC2 metadata source as an 'uec-images' bug uses a name that no longer has meaning. Solution: - If cloud-init is present, check for /etc/cloud/build.info to indicate an Ubuntu cloud images, tag as 'cloud-images'. Pull the build_name and serial from that file into the bug comments. - If cloud-init is present, check for the presence of /run/cloud-init/cloud.cfg. Parse this yaml to determine the datasource type. Add the datasource used to the bug comment. I have filed bug #1724626 to ask cloud-init development to surface more information from ds-identify to help ID the cloud so that we can better tag/annotate the bug. There may also be some info we can get to indicate the image ID on more clouds than just AWS. At a minimum I would like to see dsidentify make the EC2 platform it found available for consumers in cloud.cfg. This would allow us to identify AWS EC2 from look-alike datasources so that we can tag a bug as ec2-images for bug really on AWS and add EC2 specific fields to the description/attachments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1724623/+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 1995137] Re: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64
Hello Isaac, or anyone else affected, Accepted mesa into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Kinetic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- 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/1995137 Title: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: Fix Committed Bug description: [Impact] lima driver is missing from riscv64, but in order to enable it we need to disable anything that uses JIT on riscv64: swrast for vulkan, and draw-use-llvm for gallium. JIT for riscv64 is buggy and should be fixed in a future llvm release. [Test case] Check that sun4i-drm_dri.so is in libgl1-mesa-dri deb for riscv64, and that it works. [Where things could go wrong] This is a new driver for the architecture, so there's little chance of breakage. -- "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+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 1999336] Re: New bugfix release 22.2.5
Hello Timo, or anyone else affected, Accepted mesa into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Kinetic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- 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/1999336 Title: New bugfix release 22.2.5 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Kinetic: Fix Committed Bug description: [Impact] Update Mesa to the latest bugfix release of the 22.2.x series for kinetic, and backport it to jammy for 22.04.2 image. diffstat: 177 files changed, 2100 insertions(+), 617 deletions(-) 191 commits [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1999336/+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 1996958] Re: [Azure] 18.04 - non-unique ID_PATH for SCSI disks
We haven't heard back from the original reporter (see comment #5). Thus, marking this as `Won't Fix` for now, and attaching debdiff for documentation purposes only (not for sponsoring). ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Won't Fix ** Changed in: systemd (Ubuntu Bionic) Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned) -- 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/1996958 Title: [Azure] 18.04 - non-unique ID_PATH for SCSI disks Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Won't Fix Bug description: [Impact] * The PATH_ID for SCSI disks on Azure/Hyper-V might not be unique with the systemd/udev version in Ubuntu 18.04 LTS (Bionic Beaver). * This cause issues on applications that require unique PATH_IDs; for example Veritas Dynamic Multi-Pathing (DMP). * The fix introduces changes to PATH_ID format/values for VMBUS, which would break stable names/links, so it must be an opt-in. * The kernel command line option 'udev.new_vmbus_path_id' (boolean) can be used to opt in to (different) unique PATH_IDs. * It's not used by default (i.e., no behavior change by default). [Test Plan] 1. Launch an Ubuntu 18.04 VM on Azure 2. Add extra disks to the VM 3. Check the disks PATH_ID for (non-)unique values 4. (Opt-in for the fix with kernel cmdline option; repeat 3.) * Before: $ lsscsi | grep /dev/sd [0:0:0:0]diskMsft Virtual Disk 1.0 /dev/sdc [0:0:0:1]diskMsft Virtual Disk 1.0 /dev/sdd [1:0:0:0]diskMsft Virtual Disk 1.0 /dev/sda [1:0:0:1]diskMsft Virtual Disk 1.0 /dev/sdb $ for sd in /dev/sd?; do \ udevadm test-builtin path_id /block/${sd#/dev} \ 2>/dev/null | grep ID_PATH=; \ done | sort | uniq -c 2 ID_PATH=acpi-VMBUS:00-scsi-0:0:0:0 2 ID_PATH=acpi-VMBUS:00-scsi-0:0:0:1 * After: Opt-in mechanism: $ cat
[Touch-packages] [Bug 1996958] Re: [Azure] 18.04 - non-unique ID_PATH for SCSI disks
** Patch added: "lp1996958-bionic-systemd.debdiff" https://bugs.launchpad.net/ubuntu/bionic/+source/systemd/+bug/1996958/+attachment/5635743/+files/lp1996958-bionic-systemd.debdiff -- 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/1996958 Title: [Azure] 18.04 - non-unique ID_PATH for SCSI disks Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Won't Fix Bug description: [Impact] * The PATH_ID for SCSI disks on Azure/Hyper-V might not be unique with the systemd/udev version in Ubuntu 18.04 LTS (Bionic Beaver). * This cause issues on applications that require unique PATH_IDs; for example Veritas Dynamic Multi-Pathing (DMP). * The fix introduces changes to PATH_ID format/values for VMBUS, which would break stable names/links, so it must be an opt-in. * The kernel command line option 'udev.new_vmbus_path_id' (boolean) can be used to opt in to (different) unique PATH_IDs. * It's not used by default (i.e., no behavior change by default). [Test Plan] 1. Launch an Ubuntu 18.04 VM on Azure 2. Add extra disks to the VM 3. Check the disks PATH_ID for (non-)unique values 4. (Opt-in for the fix with kernel cmdline option; repeat 3.) * Before: $ lsscsi | grep /dev/sd [0:0:0:0]diskMsft Virtual Disk 1.0 /dev/sdc [0:0:0:1]diskMsft Virtual Disk 1.0 /dev/sdd [1:0:0:0]diskMsft Virtual Disk 1.0 /dev/sda [1:0:0:1]diskMsft Virtual Disk 1.0 /dev/sdb $ for sd in /dev/sd?; do \ udevadm test-builtin path_id /block/${sd#/dev} \ 2>/dev/null | grep ID_PATH=; \ done | sort | uniq -c 2 ID_PATH=acpi-VMBUS:00-scsi-0:0:0:0 2 ID_PATH=acpi-VMBUS:00-scsi-0:0:0:1 * After: Opt-in mechanism: $ cat
[Touch-packages] [Bug 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
** Changed in: lvm2 (Ubuntu Focal) Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned) ** Tags removed: sts-sponsor-mfo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1834250 Title: update-grub complains about non-existent drives (due to cardreader) Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Focal: Fix Committed Bug description: [Impact] * `update-grub` (actually `vgs`) complains about 'No medium found' on systems with card readers that have no card in. * This may confuse users who aren't sure whether it means problems occurred with the bootloader, and concern their ability to safely boot again. * The workaround is to add a filter to LVM config, but this might be hard to find and error prone. (And not even seem relate to `update-grub` at all, specially on non-LVM storage layouts.) [See comment #16] * The fix replaces calls to `dev_open_readonly()` with `dev_open_readonly_quiet()` in scan path, where such errors are not a problem. [Test Plan] * Run `vgs` on a system with a card reader and check for 'No medium found' messages. * Run `strace -f -e openat vgs` to confirm system calls/error codes have no changes. * [See comment #20] [Where problems could occur] * The patch changes syscall error reporting on the 'scan' path, so problems could occur when listing LVM resources in block devices (e.g., list volume groups with `vgs`). * There's little to no changes upstream on this area, and the change is present in Jammy; both help with a lower chance of regression. [Other Info] * `block-proposed-focal`: The upload is being staged as it's just a cosmetic change, but affects `lvm2`, which is present in so many systems, triggering a lot of upgrades/boot risk (in case something else broke and this upgrade could reveal it indirectly). * So, it will probably only be released once a more serious issue has to be fixed in `lvm2`. * Scope: Jammy has the fix, and Impish will EOL soon. [Original Bug Description] sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Found linux image: /boot/vmlinuz-5.0.0-17-generic Found initrd image: /boot/initrd.img-5.0.0-17-generic Found linux image: /boot/vmlinuz-5.0.0-16-generic Found initrd image: /boot/initrd.img-5.0.0-16-generic /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Adding boot menu entry for EFI firmware configuration done -- lsblk NAME MAJ:MIN RM
[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info
Took some time to understand the diff until I noticed that the diff is inverse (apply with -R). From my perspective add_cloud_init_data and get_ec2_data should be shipped by cloud-init, because they access data generated by cloud-init. Which component is responsible for generating /etc/cloud/build.info? ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1724623 Title: Update ubuntu cloud info Status in apport package in Ubuntu: New Status in cloud-init package in Ubuntu: New Bug description: add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul. Issues: - Using the presence of cloud-init to flag an image as a cloud image is incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images) - Using the presence of EC2 metadata source is incorrect as many non-EC2 clouds provide EC2 metadata. Thus we have bugs like bug #1722946 that are tagged as an 'ec2-images' bug which are clearly on openstack - Marking all bugs that have cloud-init but no EC2 metadata source as an 'uec-images' bug uses a name that no longer has meaning. Solution: - If cloud-init is present, check for /etc/cloud/build.info to indicate an Ubuntu cloud images, tag as 'cloud-images'. Pull the build_name and serial from that file into the bug comments. - If cloud-init is present, check for the presence of /run/cloud-init/cloud.cfg. Parse this yaml to determine the datasource type. Add the datasource used to the bug comment. I have filed bug #1724626 to ask cloud-init development to surface more information from ds-identify to help ID the cloud so that we can better tag/annotate the bug. There may also be some info we can get to indicate the image ID on more clouds than just AWS. At a minimum I would like to see dsidentify make the EC2 platform it found available for consumers in cloud.cfg. This would allow us to identify AWS EC2 from look-alike datasources so that we can tag a bug as ec2-images for bug really on AWS and add EC2 specific fields to the description/attachments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1724623/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
@seb Sorry, I did not see the modemmanager (1.20.0-1ubuntu1) in jammy-proposed, would you please confirm the process? % rmadison modemmanager modemmanager | 1.0.0-2ubuntu1| trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el modemmanager | 1.0.0-2ubuntu1.1 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el modemmanager | 1.4.12-1ubuntu1 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x modemmanager | 1.6.4-1ubuntu0.16.04.1| xenial-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x modemmanager | 1.6.8-2ubuntu1| bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x modemmanager | 1.10.0-1~ubuntu18.04.2| bionic-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x modemmanager | 1.12.8-1 | focal| source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x modemmanager | 1.18.6-1~ubuntu20.04.1| focal-updates| source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x modemmanager | 1.18.6-1 | jammy| source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x modemmanager | 1.19~git20220905-0ubuntu2 | kinetic | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x modemmanager | 1.20.0-1~ubuntu22.10.1| kinetic-proposed | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x modemmanager | 1.20.0-1ubuntu1 | lunar| source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Yao Wei (medicalwei) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Fix Released Bug description: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case - install modemmanager, libmbim, and libqmi from -proposed - reboot and try WWAN function to see if any regression there. - perform dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) The verification should be done on FM350 to ensure it's correctly handled but also on other hardware to verify that there are no regressions * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no regression. --- :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Cor
[Touch-packages] [Bug 1997093] Re: bash 5.2 regression too-aggressive optimizing of forks in an `eval' command inside a (command) subshell
https://lists.gnu.org/archive/html/bug-bash/2022-12/msg00050.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1997093 Title: bash 5.2 regression too-aggressive optimizing of forks in an `eval' command inside a (command) subshell Status in bash package in Ubuntu: New Status in ovn package in Ubuntu: New Bug description: OVN makes use of GNU autotest for its testsuite. This in turn is a heavy user of bash. For some reason, when the 'ovn-controller incremental processing' test is executed using bash 5.2 on Debian experimental or Ubuntu Kinetic/Lunar, the `eval` [0] in the `counter_delta_` function misinterprets successful execution of commands [1], leading to a false negative for the 'ovn-controller incremental processing' test [2]. Backporting the bash 5.1 package from Jammy, or compiling bash 5.1 from upstream sources and rerunning the test makes it succeed. This does come across as a regression in bash. 0: https://github.com/ovn-org/ovn/blob/a042aa23e79a0d36f1ce7b0ccfcf0a5995b045cd/tests/ovn-performance.at#L116 1: https://github.com/ovn-org/ovn/blob/a042aa23e79a0d36f1ce7b0ccfcf0a5995b045cd/tests/ovn-performance.at#L479 2: https://github.com/ovn-org/ovn/blob/a042aa23e79a0d36f1ce7b0ccfcf0a5995b045cd/tests/ovn-performance.at#L227 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1997093/+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 1998950] Re: GPU hang on Alder Lake laptop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1998950 Title: GPU hang on Alder Lake laptop Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1998950/+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 1998950] Re: GPU hang on Alder Lake laptop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1998950 Title: GPU hang on Alder Lake laptop Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1998950/+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