[Touch-packages] [Bug 1945645] Re: cups-pdf prints blank pages
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ghostscript (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: Confirmed Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: Confirmed Status in ghostscript package in Debian: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+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 1945645] Re: cups-pdf prints blank pages
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: Confirmed Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: Confirmed Status in ghostscript package in Debian: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+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 1788459] [gssproxy/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libselinux in Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd Status in gssproxy package in Ubuntu: In Progress Status in libselinux package in Ubuntu: Invalid Status in gssproxy source package in Focal: Fix Committed Status in libselinux source package in Focal: Invalid Status in gssproxy source package in Hirsute: Fix Committed Status in libselinux source package in Hirsute: Invalid Bug description: [ Impact ] gssproxy users on Focal and Hiruste who configure the package to handle NFS mountpoints using Kerberos authentication will experience a segmentation fault when invoking the service either through systemd or by hand. [ Test Case] Inside a Focal LXD container: $ lxc launch images:ubuntu/focal gssproxy-bug1788459-focal $ lxc shell gssproxy-bug1788459-focal # apt update # apt install -y gssproxy nfs-kernel-server # cat > /etc/gssproxy/gssproxy.conf << __EOF__ [gssproxy] debug = true debug_level = 3 __EOF__ # cat >> /etc/gssproxy/25-nfs-server.conf << __EOF__ [service/nfs-server] mechs = krb5 socket = /run/gssproxy.sock cred_store = keytab:/etc/krb5.keytab trusted = yes kernel_nfsd = yes euid = 0 __EOF__ # /usr/sbin/gssproxy --interactive --debug --debug-level=3 --socket=/run/gssproxy.sock [2021/06/30 14:34:14]: Debug Enabled (level: 3) [2021/06/30 14:34:14]: Keytab /etc/krb5.keytab has no content (-1765328203) [2021/06/30 14:34:14]: Service: nfs-server, Enckey: [ephemeral], Enctype: 18 [2021/06/30 14:34:14]: Client [2021/06/30 14:34:14]: (/usr/sbin/gssproxy) [2021/06/30 14:34:14]: connected (fd = 12)[2021/06/30 14:34:14]: (pid = 3428) (uid = 0) (gid = 0)Segmentation fau lt (core dumped) [ Where problems could occur ] * The backported patch is simple and it is very unlikely that it will introduce a regression. * As usual, it is always risky to rebuild a package that hasn't been touched for more than 1 year, albeit in this case the risk is very low because the package is not very complex. [ Original Description ] I have apache configured to perform a kerberized NFS4 mount using rpc.gssd and gssproxy. If I request a web page that requires NFS4 access, then gssproxy crashes, reporting a segfault in libselinux.so.1 and the web request generates a 403 error. gssproxy[6267]: segfault at 0 ip 7f2f5bb1951a sp 7ffe861da150 error 4 in libselinux.so.1[7f2f5bb0d000+25000] If I run gssproxy at debug level = 3, and then load a web page, I can see the uid/principal request for www-data come in from rpc.gssd: # gssproxy -d --debug-level=3 -i -C /etc/gssproxy [2018/08/22 17:51:40]: Debug Enabled (level: 3) [2018/08/22 17:52:06]: Client [2018/08/22 17:52:06]: (/usr/sbin/rpc.gssd) [2018/08/22 17:52:06]: connected (fd = 10)[2018/08/22 17:52:06]: (pid = 4548) (uid = 33) (gid = 33)Segmentation fault (core dumped) Since gssproxy is required to initiate kerberos principals for any local application services - Ubuntu 18.04 does not currently support running application services with NFS4 kerberos dependencies. This has a fairly significant impact on anyone attempting to implement kerberos on Ubuntu 18.04 Ubuntu 18.04.1 LTS gssproxy 0.8.0-1 libselinux1:amd64 2.7-2build2 libgssrpc4:amd64 1.16-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+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 1945801] Re: Netplan doesn't work with DHCP DNS server
** Package changed: ubuntu => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1945801 Title: Netplan doesn't work with DHCP DNS server Status in network-manager package in Ubuntu: New Bug description: Network/hardware setup: pihole running on pi4 with local dns entries. Ex. somehost 192.168.1.10 udm pro configured with a manual dhcp name server giving the pihole's ip address fresh install ubuntu server on a VMware ESXi host using dhcp Problem: from the ubuntu server "ping somehost" and "nslookup somehost" are both unable to resolve the local ip from the pihole. this functionality works fine from both windows and osx "systemd-resolve --status" shows the correct pihole ip address in "Current DNS Server" and "DNS Servers" for the network interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1945801/+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 1945801] [NEW] Netplan doesn't work with DHCP DNS server
You have been subscribed to a public bug: Network/hardware setup: pihole running on pi4 with local dns entries. Ex. somehost 192.168.1.10 udm pro configured with a manual dhcp name server giving the pihole's ip address fresh install ubuntu server on a VMware ESXi host using dhcp Problem: from the ubuntu server "ping somehost" and "nslookup somehost" are both unable to resolve the local ip from the pihole. this functionality works fine from both windows and osx "systemd-resolve --status" shows the correct pihole ip address in "Current DNS Server" and "DNS Servers" for the network interface ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Netplan doesn't work with DHCP DNS server https://bugs.launchpad.net/bugs/1945801 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager 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 1945815] [NEW] package linux-firmware 1.187.17 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: i ran the following commands in terminal: $ sudo apt update Fetched 870 kB in 3s (344 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. so it looks like everything was ok. but then a pop up appeared to "send report to canonical" ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.17 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1921 F pulseaudio mihai 7654 F pulseaudio /dev/snd/controlC0: gdm1921 F pulseaudio mihai 7654 F pulseaudio CasperMD5CheckResult: skip Date: Fri Oct 1 17:45:52 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=bf1a75bb-adef-4754-9fff-9f27a46732d6 InstallationDate: Installed on 2020-11-01 (334 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 7590 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-37-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.17 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2020 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd07/03/2020:br1.8:svnDellInc.:pnXPS157590:pvr:sku0905:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1945815 Title: package linux-firmware 1.187.17 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: i ran the following commands in terminal: $ sudo apt update Fetched 870 kB in 3s (344 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. so it looks like everything was ok. but then a pop up appeared to "send report to canonical" ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.17 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1921 F pulseaudio mihai 7654 F pulseaudio /dev/snd/controlC0: gdm1921 F pulseaudio mihai 7654 F pulseaudio CasperMD5CheckResult: skip Date: Fri Oct 1 17:45:52 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=bf1a75bb-adef-4754-9fff-9f27a46732d6 InstallationDate: Installed on 2020-11-01 (334 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 7590 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine:
[Touch-packages] [Bug 1945795] Re: krb5: Fail to build against OpenSSL 3.0
The attachment "0001-Fix-softpkcs11-build-issues-with-openssl-3.0.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1945795 Title: krb5: Fail to build against OpenSSL 3.0 Status in krb5 package in Ubuntu: New Bug description: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22098576/+files/buildlog_ubuntu- impish-amd64.krb5_1.18.3-6.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. You can find general migration informations at https://www.openssl.org/docs/manmaster/man7/migration_guide.html For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 Looking into the upstream master branch, I was able to find the following commits related to OpenSSL3: https://github.com/krb5/krb5/commit/00de1aad7b3647b91017c7009b0bc65cd0c8b2e0 https://github.com/krb5/krb5/commit/d6bf42279675100e3e4fe7c6e08eef74d49624cb https://github.com/krb5/krb5/commit/aa9b4a2a64046afd2fab7cb49c346295874a5fb6 Perhaps a simple cherry-pick of those would suffice? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1945795/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
Honestly, to announce this one month before release without feature parity, is baffling. As it looks this puts us in a position where we probably have to stop supporting Ubuntu after more than a decade, as the available browsers can't work with our Belgian Identity Card. And this because of a packaging format. It is honestly mind-boggling. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1943840 Title: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Impish: Fix Released Status in ubuntu-release-upgrader source package in Impish: Fix Released Status in ubuntu-settings source package in Impish: Fix Released Bug description: Per Canonical's distribution agreement with Mozilla, we're making the snap¹ the default installation of firefox on desktop ISOs starting with Ubuntu 21.10. The snap is built and published for amd64, armhf and arm64. It is jointly maintained by Mozilla and the Ubuntu desktop team, and published by Mozilla. This requires updating the desktop-minimal seed, as well as ubuntu- release-upgrader. ¹ https://snapcraft.io/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1850804] Re: Tab completion warnings with ubuntu-bug
This still happens after upgrading to Ubuntu 21.10. Is there any news on fixing it? -- 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/1850804 Title: Tab completion warnings with ubuntu-bug Status in apport package in Ubuntu: Confirmed Bug description: When running ubuntu-bug on the command line, and tab completing the package name, the following warnings are printed: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 31 10:54:43 2019 InstallationDate: Installed on 2017-08-16 (805 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850804/+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 1945787] Re: heimdal: fails to build, symbols don't match
** Patch added: "heimdal_7.7.0+dfsg-2ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1945787/+attachment/5529892/+files/heimdal_7.7.0+dfsg-2ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1945787 Title: heimdal: fails to build, symbols don't match Status in heimdal package in Ubuntu: New Bug description: heimdal 7.7.0+dfsg-2ubuntu1 fails to build with dpkg-gensymbols: warning: debian/libroken18-heimdal/DEBIAN/symbols doesn't match completely debian/libroken18-heimdal.symbols --- debian/libroken18-heimdal.symbols (libroken18-heimdal_7.7.0+dfsg-2ubuntu1_riscv64) +++ dpkg-gensymbolsYtlvSr 2021-10-01 12:31:59.102451503 + @@ -42,7 +42,7 @@ rk_cloexec_dir@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_cloexec_file@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_cloexec_socket@HEIMDAL_ROKEN_1.0 1.6~git20131117 - rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 +#MISSING: 7.7.0+dfsg-2ubuntu1# rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_copyhostent@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_dns_free_data@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_dns_lookup@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1945787/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1945795] [NEW] krb5: Fail to build against OpenSSL 3.0
Hi Sam, Quoting Sam Hartman (2021-10-01 16:13:18) > > "Simon" == Simon Chopin <1945...@bugs.launchpad.net> writes: > Simon> We're planning to transition to OpenSSL 3.0 for the 22.04 > Simon> release, and consider this issue as blocking for this > Simon> transition. > > I expect things to be fixed in Debian within the next couple of months. > > I attach the upstream patch for this issue in case Ubuntu needs to move > faster than Debian. Thank you for this quick response, I appreciate it! I'll probably prepare an Ubuntu-specific debdiff+PPA just in case, but it would be really nice to keep in sync with Debian. Cheers, Simon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1945795 Title: krb5: Fail to build against OpenSSL 3.0 Status in krb5 package in Ubuntu: New Bug description: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22098576/+files/buildlog_ubuntu- impish-amd64.krb5_1.18.3-6.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. You can find general migration informations at https://www.openssl.org/docs/manmaster/man7/migration_guide.html For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 Looking into the upstream master branch, I was able to find the following commits related to OpenSSL3: https://github.com/krb5/krb5/commit/00de1aad7b3647b91017c7009b0bc65cd0c8b2e0 https://github.com/krb5/krb5/commit/d6bf42279675100e3e4fe7c6e08eef74d49624cb https://github.com/krb5/krb5/commit/aa9b4a2a64046afd2fab7cb49c346295874a5fb6 Perhaps a simple cherry-pick of those would suffice? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1945795/+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 1945805] [NEW] Screen Won't Come Back After Blank Screen
Public bug reported: The Power Saving option was set for the screen to go blank after five minutes. After the update, the screen will now not come back on when the mouse or keyboard is utilized. The computer appears to be still operational as it's registering keystrokes, but it must be restarted in order for the screen to come back up. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22 Uname: Linux 5.11.0-1019-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:22:59 2021 DistUpgraded: 2021-08-11 11:39:13,437 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 248a:8367 Maxxter Telink Wireless Receiver Bus 001 Device 003: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC) Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1680x1050M@60 video=HDMI-A-2:1680x1050M@60 smsc95xx.macaddr=DC:A6:32:B4:5C:3E vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-08-11 (50 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image hirsute raspi-image ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1945805 Title: Screen Won't Come Back After Blank Screen Status in xorg package in Ubuntu: New Bug description: The Power Saving option was set for the screen to go blank after five minutes. After the update, the screen will now not come back on when the mouse or keyboard is utilized. The computer appears to be still operational as it's registering keystrokes, but it must be restarted in order for the screen to come back up. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22 Uname: Linux 5.11.0-1019-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:22:59 2021 DistUpgraded: 2021-08-11 11:39:13,437 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 248a:8367 Maxxter Telink Wireless Receiver Bus 001 Device 003: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC) Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1680x1050M@60 video=HDMI-A-2:1680x1050M@60 smsc95xx.macaddr=DC:A6:32:B4:5C:3E vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage:
Re: [Touch-packages] [Bug 1945795] [NEW] krb5: Fail to build against OpenSSL 3.0
> "Simon" == Simon Chopin <1945...@bugs.launchpad.net> writes: Simon> We're planning to transition to OpenSSL 3.0 for the 22.04 Simon> release, and consider this issue as blocking for this Simon> transition. I expect things to be fixed in Debian within the next couple of months. I attach the upstream patch for this issue in case Ubuntu needs to move faster than Debian. ** Patch added: "0001-Fix-softpkcs11-build-issues-with-openssl-3.0.patch" https://bugs.launchpad.net/bugs/1945795/+attachment/5529874/+files/0001-Fix-softpkcs11-build-issues-with-openssl-3.0.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1945795 Title: krb5: Fail to build against OpenSSL 3.0 Status in krb5 package in Ubuntu: New Bug description: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22098576/+files/buildlog_ubuntu- impish-amd64.krb5_1.18.3-6.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. You can find general migration informations at https://www.openssl.org/docs/manmaster/man7/migration_guide.html For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 Looking into the upstream master branch, I was able to find the following commits related to OpenSSL3: https://github.com/krb5/krb5/commit/00de1aad7b3647b91017c7009b0bc65cd0c8b2e0 https://github.com/krb5/krb5/commit/d6bf42279675100e3e4fe7c6e08eef74d49624cb https://github.com/krb5/krb5/commit/aa9b4a2a64046afd2fab7cb49c346295874a5fb6 Perhaps a simple cherry-pick of those would suffice? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1945795/+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 1945787] Re: heimdal: fails to build, symbols don't match
** Tags added: fr-1760 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1945787 Title: heimdal: fails to build, symbols don't match Status in heimdal package in Ubuntu: New Bug description: heimdal 7.7.0+dfsg-2ubuntu1 fails to build with dpkg-gensymbols: warning: debian/libroken18-heimdal/DEBIAN/symbols doesn't match completely debian/libroken18-heimdal.symbols --- debian/libroken18-heimdal.symbols (libroken18-heimdal_7.7.0+dfsg-2ubuntu1_riscv64) +++ dpkg-gensymbolsYtlvSr 2021-10-01 12:31:59.102451503 + @@ -42,7 +42,7 @@ rk_cloexec_dir@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_cloexec_file@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_cloexec_socket@HEIMDAL_ROKEN_1.0 1.6~git20131117 - rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 +#MISSING: 7.7.0+dfsg-2ubuntu1# rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_copyhostent@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_dns_free_data@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_dns_lookup@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1945787/+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 1942764] Re: Enable riscv64 build of mesa-opencl-icd
This bug was fixed in the package mesa - 21.2.2-1ubuntu1 --- mesa (21.2.2-1ubuntu1) impish; urgency=medium * Merge from Debian. - use -O2 for ppc64el -- Timo Aaltonen Tue, 28 Sep 2021 10:35:10 +0300 ** Changed in: mesa (Ubuntu) Status: In Progress => 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/1942764 Title: Enable riscv64 build of mesa-opencl-icd Status in mesa package in Ubuntu: Fix Released Bug description: Ubuntu release: impish Package version: 21.2.1-2ubuntu1 `mesa-opencl-icd` is needed for `libhmsbeagle` to be installable, so is it possible to enable this package as I have done here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12687486/+listing- archive-extra ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1942764/+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 1945795] [NEW] krb5: Fail to build against OpenSSL 3.0
Public bug reported: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22098576/+files/buildlog_ubuntu- impish-amd64.krb5_1.18.3-6.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. You can find general migration informations at https://www.openssl.org/docs/manmaster/man7/migration_guide.html For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 Looking into the upstream master branch, I was able to find the following commits related to OpenSSL3: https://github.com/krb5/krb5/commit/00de1aad7b3647b91017c7009b0bc65cd0c8b2e0 https://github.com/krb5/krb5/commit/d6bf42279675100e3e4fe7c6e08eef74d49624cb https://github.com/krb5/krb5/commit/aa9b4a2a64046afd2fab7cb49c346295874a5fb6 Perhaps a simple cherry-pick of those would suffice? ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New ** Tags: transition-openssl3-jj -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1945795 Title: krb5: Fail to build against OpenSSL 3.0 Status in krb5 package in Ubuntu: New Bug description: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22098576/+files/buildlog_ubuntu- impish-amd64.krb5_1.18.3-6.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. You can find general migration informations at https://www.openssl.org/docs/manmaster/man7/migration_guide.html For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 Looking into the upstream master branch, I was able to find the following commits related to OpenSSL3: https://github.com/krb5/krb5/commit/00de1aad7b3647b91017c7009b0bc65cd0c8b2e0 https://github.com/krb5/krb5/commit/d6bf42279675100e3e4fe7c6e08eef74d49624cb https://github.com/krb5/krb5/commit/aa9b4a2a64046afd2fab7cb49c346295874a5fb6 Perhaps a simple cherry-pick of those would suffice? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1945795/+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 1945787] [NEW] heimdal: fails to build, symbols don't match
Public bug reported: heimdal 7.7.0+dfsg-2ubuntu1 fails to build with dpkg-gensymbols: warning: debian/libroken18-heimdal/DEBIAN/symbols doesn't match completely debian/libroken18-heimdal.symbols --- debian/libroken18-heimdal.symbols (libroken18-heimdal_7.7.0+dfsg-2ubuntu1_riscv64) +++ dpkg-gensymbolsYtlvSr 2021-10-01 12:31:59.102451503 + @@ -42,7 +42,7 @@ rk_cloexec_dir@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_cloexec_file@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_cloexec_socket@HEIMDAL_ROKEN_1.0 1.6~git20131117 - rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 +#MISSING: 7.7.0+dfsg-2ubuntu1# rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_copyhostent@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_dns_free_data@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_dns_lookup@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1945787 Title: heimdal: fails to build, symbols don't match Status in heimdal package in Ubuntu: New Bug description: heimdal 7.7.0+dfsg-2ubuntu1 fails to build with dpkg-gensymbols: warning: debian/libroken18-heimdal/DEBIAN/symbols doesn't match completely debian/libroken18-heimdal.symbols --- debian/libroken18-heimdal.symbols (libroken18-heimdal_7.7.0+dfsg-2ubuntu1_riscv64) +++ dpkg-gensymbolsYtlvSr 2021-10-01 12:31:59.102451503 + @@ -42,7 +42,7 @@ rk_cloexec_dir@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_cloexec_file@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_cloexec_socket@HEIMDAL_ROKEN_1.0 1.6~git20131117 - rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 +#MISSING: 7.7.0+dfsg-2ubuntu1# rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_copyhostent@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_dns_free_data@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 rk_dns_lookup@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1945787/+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 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
for later reference, i'd discussed this with nick and asked him to check if the 'status_request' reply contained any kind of valid data in the specific cases where this patch will disable it; my concern is if there is valid data in it, it's possible there are applications out there that might currently expect and/or use it, even if it's against the RFC, which might result in a regression after this patch. However, if the reply is empty or just has garbage, it's unlikely that any application is using it for anything currently, so there would be less chance of causing a regression. ** Tags added: sts-sponsor-ddstreet -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: New Bug description: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 The issue leads to various client failures with TLS 1.3 as described in, e.g. https://github.com/golang/go/issues/35722 https://github.com/golang/go/issues/34040 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1921518] Re: OpenSSL "double free" error
Also I seem to be getting a SIGBUS signal only when function addresses are not 4-byte aligned: Thread 1 "curl" received signal SIGBUS, Bus error. 0x006358f58d277bf1 in ?? () Thread 1 "curl" received signal SIGBUS, Bus error. 0xb1b30b5cc1eb2dda in ?? () Thread 1 "curl" received signal SIGBUS, Bus error. 0x006358f58d277bf1 in ?? () Thread 1 "curl" received signal SIGBUS, Bus error. 0x4fc81bc04dc15a0d in ?? () When they are 4-byte aligned, I get SIGSEGV instead: Thread 1 "curl" received signal SIGSEGV, Segmentation fault. 0x0023c42279cdf718 in ?? () Thread 1 "curl" received signal SIGSEGV, Segmentation fault. 0x0078cdaa17700aa4 in ?? () -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1921518 Title: OpenSSL "double free" error Status in openssl package in Ubuntu: Incomplete Status in openssl source package in Focal: Incomplete Bug description: "double free" error is seen when using curl utility. Error is from libcrypto.so which is part of the OpenSSL package. This happens only when OpenSSL is configured to use a dynamic engine. OpenSSL version is 1.1.1f The issue is not encountered if http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead. OpenSSL can be configured to use a dynamic engine by editing the default openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu systems. On Bluefield systems, config diff to enable PKA dynamic engine, is as below: +openssl_conf = conf_section + # Extra OBJECT IDENTIFIER info: #oid_file = $ENV::HOME/.oid oid_section= new_oids +[ conf_section ] +engines = engine_section + +[ engine_section ] +bf = bf_section + +[ bf_section ] +engine_id=pka +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so +init=0 + engine_id above refers to dynamic engine name/identifier. dynamic_path points to the .so file for the dynamic engine. # curl -O https://tpo.pe/pathogen.vim double free or corruption (out) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518/+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 1921518] Re: OpenSSL "double free" error
Vladimir,
stracing reveals that si_code is set to BUS_ADRALN so there is a problem
with address alignment.
strace curl https://example.com
--- SIGBUS {si_signo=SIGBUS, si_code=BUS_ADRALN, si_addr=0x3efd151115865b} ---
+++ killed by SIGBUS (core dumped) +++
Bus error (core dumped)
The fault is raised by the CPU in response to a misaligned address and
the respective handler in the kernel is being invoked to assert a signal
to the process:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=52d7523d84d534c241ebac5ac89f5c0a6cb51e41
https://paste.ubuntu.com/p/yHJrJW2gSF/ (package & distro details)
By the looks of it the alignment fault is caused by just trying to call
the public key method init function in the PKA engine.
Below we have:
1) pmeth->init is at 0xc82028bf65604647
When it is attempted to be called, si_addr has the same value:
2) _sigfault = {si_addr = 0x2028bf65604647}
(gdb) r
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /usr/bin/curl https://example.com
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
[New Thread 0xf6372f90 (LWP 2486506)]
[Thread 0xf6372f90 (LWP 2486506) exited]
Thread 1 "curl" hit Breakpoint 1, int_ctx_new (pkey=pkey@entry=0x0,
e=e@entry=0x0, id=1034) at ../crypto/evp/pmeth_lib.c:113
113 if (id == -1) {
(gdb) n
119 if (e == NULL && pkey != NULL)
(gdb)
122 if (e) {
(gdb)
128 e = ENGINE_get_pkey_meth_engine(id);
(gdb)
135 if (e)
(gdb)
136 pmeth = ENGINE_get_pkey_meth(e, id);
(gdb)
141 if (pmeth == NULL) {
(gdb)
149 ret = OPENSSL_zalloc(sizeof(*ret));
(gdb)
150 if (ret == NULL) {
(gdb)
157 ret->engine = e;
(gdb)
159 ret->operation = EVP_PKEY_OP_UNDEFINED;
(gdb)
161 if (pkey != NULL)
(gdb)
164 if (pmeth->init) {
(gdb)
165 if (pmeth->init(ret) <= 0) {
(gdb) print *pmeth
$10 = {pkey_id = -1784943492, flags = -364887078, init = 0xc82028bf65604647,
copy = 0x9c17b192eb068c0b, cleanup = 0xedbe7dcdf413f1c0, paramgen_init =
0xc28e015828ce4282, paramgen = 0x6fce6fa0a7ee471f,
keygen_init = 0xdf9a9579438d24eb, keygen = 0xc63719742b8964b9, sign_init =
0x78f4d90cba7ad854, sign = 0xb0d4f1b3df1a9e13, verify_init =
0x7b5f10ffa4c58586, verify = 0x96e16d3250d67446,
verify_recover_init = 0xe11ef96099ea206c, verify_recover =
0x8ed096c03e046773, signctx_init = 0xc6ea05c3bdb5153c, signctx =
0xdd1cb7963c7185, verifyctx_init = 0xd19718983089e1f8,
verifyctx = 0x6143e92bef937feb, encrypt_init = 0x94450e0e52af0bcd, encrypt =
0x2a4633c02797f8b, decrypt_init = 0xa69b08bdbfea813, decrypt =
0x84b9264be5facf60, derive_init = 0x99bcf2700df9fc7e,
derive = 0x9961eec79bc58dfb, ctrl = 0x1779f7901d10471b, ctrl_str =
0x763a1ebbf28338f0, digestsign = 0xacc57ce435798e94, digestverify =
0xae611fd83700f11f, check = 0x6b8d5f0b7cf4a89b,
public_check = 0xef347940990e67fb, param_check = 0xe, digest_custom =
0xf797ec60 }
(gdb) print pmeth->init
$11 = (int (*)(EVP_PKEY_CTX *)) 0xc82028bf65604647
(gdb) n
Thread 1 "curl" received signal SIGBUS, Bus error.
0x002028bf65604647 in ?? ()
(gdb) p $_siginfo
$12 = {si_signo = 7, si_errno = 0, si_code = 1, _sifields = {_pad =
{1700808263, 2107583, 0 }, _kill = {si_pid = 1700808263,
si_uid = 2107583}, _timer = {si_tid = 1700808263,
si_overrun = 2107583, si_sigval = {sival_int = 0, sival_ptr = 0x0}}, _rt
= {si_pid = 1700808263, si_uid = 2107583, si_sigval = {sival_int = 0, sival_ptr
= 0x0}}, _sigchld = {si_pid = 1700808263,
si_uid = 2107583, si_status = 0, si_utime = 0, si_stime = 0}, _sigfault =
{si_addr = 0x2028bf65604647}, _sigpoll = {si_band = 9052001759413831, si_fd =
0}}}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1921518
Title:
OpenSSL "double free" error
Status in openssl package in Ubuntu:
Incomplete
Status in openssl source package in Focal:
Incomplete
Bug description:
"double free" error is seen when using curl utility. Error is from
libcrypto.so which is part of the OpenSSL package. This happens only
when OpenSSL is configured to use a dynamic engine.
OpenSSL version is 1.1.1f
The issue is not encountered if
http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead.
OpenSSL can be configured to use a dynamic engine by editing the default
openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu
systems.
On Bluefield systems, config diff to enable PKA dynamic engine, is as
below:
+openssl_conf = conf_section
+
# Extra OBJECT IDENTIFIER info:
#oid_file = $ENV::HOME/.oid
oid_section= new_oids
+[ conf_section ]
+engines = engine_section
+
+[ engine_section ]
+bf = bf_section
+
+[ bf_section ]
+engine_id=pka
+dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so
+init=0
+
engine_id above refers
[Touch-packages] [Bug 1314160] Re: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb
I can confirm as well for 18.04. Still there, and #11 still solves it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1314160 Title: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb Status in cups package in Ubuntu: Confirmed Bug description: When I print to my smb printer, I get a dbus notification of the following entries in my syslog: Apr 29 12:27:15 tinker kernel: [ 3359.467314] type=1400 audit(1398770835.923:150): apparmor="DENIED" operation="mknod" profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7 Apr 29 12:27:15 tinker kernel: [ 3359.467453] type=1400 audit(1398770835.923:151): apparmor="DENIED" operation="mknod" profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7 Apr 29 12:27:15 tinker kernel: [ 3359.469047] type=1400 audit(1398770835.923:152): apparmor="DENIED" operation="mknod" profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7 I get new entries every time I print. I'm running Ubuntu 14.04 with cups-daemon 1.7.2-0ubuntu1 on btrfs, fwiw. I saw this replicated on http://www.dedoimedo.com/computers/ubuntu- trusty-tahr-laptop-ultrabook.html . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1314160/+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 1945645] Re: cups-pdf prints blank pages
** Changed in: ghostscript (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: New Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: New Status in ghostscript package in Debian: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+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 1945645] Re: cups-pdf prints blank pages
** Bug watch added: Debian Bug tracker #990210 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990210 ** Also affects: cups-pdf (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990210 Importance: Unknown Status: Unknown ** Package changed: cups-pdf (Debian) => ghostscript (Debian) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: New Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: New Status in ghostscript package in Debian: Unknown Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+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 1945645] Re: cups-pdf prints blank pages
** Also affects: cups (Ubuntu) Importance: Undecided Status: New ** Also affects: ghostscript (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: New Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+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 1945749] Re: Xorg freeze
Thanks for the bug report. Next time the problem happens, please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. 5. Check for crash reports using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1945749 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: System randomly freezes, no clue how to reproduce it. Multiple people have the same issue. Dell Precision 5550 running Ubuntu 20.04.3 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:41:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-36-generic, x86_64: installed nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:097e] Subsystem: Dell TU117GLM [Quadro T1000 Mobile] [1028:097e] InstallationDate: Installed on 2021-08-27 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=42e96b11-9efb-45e0-ace2-85fe35b2047b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnPrecision5550:pvr:sku097E:rvnDellInc.:rn0V6K79:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5550 dmi.product.sku: 097E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1945749/+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 1945749] [NEW] Xorg freeze
Public bug reported: System randomly freezes, no clue how to reproduce it. Multiple people have the same issue. Dell Precision 5550 running Ubuntu 20.04.3 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:41:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-36-generic, x86_64: installed nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:097e] Subsystem: Dell TU117GLM [Quadro T1000 Mobile] [1028:097e] InstallationDate: Installed on 2021-08-27 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=42e96b11-9efb-45e0-ace2-85fe35b2047b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnPrecision5550:pvr:sku097E:rvnDellInc.:rn0V6K79:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5550 dmi.product.sku: 097E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu ** Description changed: - System randomly freezes, no clue how to reproduce it. Dell Precision - 5550 running Ubuntu 20.04.3 LTS. + System randomly freezes, no clue how to reproduce it. Multiple people + have the same issue. Dell Precision 5550 running Ubuntu 20.04.3 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 - GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 + GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:41:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu
[Touch-packages] [Bug 1856428] Re: Disable TLS below 1.2 by default
** No longer affects: golang-1.13 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1856428 Title: Disable TLS below 1.2 by default Status in NSS: Fix Released Status in gnutls28 package in Ubuntu: Fix Released Status in nss package in Ubuntu: Fix Released Status in openssl package in Ubuntu: Fix Released Status in nss package in Debian: Confirmed Bug description: Disable TLS 1.0, TLS1.1, DTLS1.0 As part of focal commitment, we shall disable obsolete protocols by default. Users can override this behaviour with a config file. To manage notifications about this bug go to: https://bugs.launchpad.net/nss/+bug/1856428/+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
