[Touch-packages] [Bug 1961857] Re: compiz crashed with SIGSEGV in nir_lower_uniforms_to_ubo() from draw_create_vs_llvm() from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from r300_
It appears this crash has only been reported twice, ever. It's also in an unsupported package (compiz). If you are using a desktop then I would recommend replacing the graphics card so as to get a different driver. Otherwise please use GNOME (regular Ubuntu). -- 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/1961857 Title: compiz crashed with SIGSEGV in nir_lower_uniforms_to_ubo() from draw_create_vs_llvm() from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from r300_create_vs_state() Status in compiz package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding compiz. This problem was most recently seen with package version 1:0.9.14.1+20.04.20200211-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/253612f74aa79d2e52b8f27505f04cb72de285c1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1961857/+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 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
** Attachment added: "ldd -r" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+attachment/5566868/+files/Screenshot%20from%202022-03-08%2011-02-12.png -- 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/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Incomplete Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+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 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
Hi: Please see the attachment. -- 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/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Incomplete Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+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 1963818] Re: Upgrading to 22.04 on wayland session closes session
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: wayland (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 wayland in Ubuntu. https://bugs.launchpad.net/bugs/1963818 Title: Upgrading to 22.04 on wayland session closes session Status in Ubuntu: Incomplete Bug description: Just tried to upgrade Kubuntu from 21.10 to 22.04 in a konsole on a Wayland session (using do-release-upgrade) and while setting up one of the packages I lost the Wayland session and was left with a tiny cursor in the upper left corner. No way to restart a new session or connect a tty to inspect the running upgrade process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1963818/+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 1778695] Re: ristretto ignores cr2 files
Fixed in ristretto 0.8.5 https://gitlab.xfce.org/apps/ristretto/-/blob/master/NEWS#L235 ** Changed in: ristretto (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 file in Ubuntu. https://bugs.launchpad.net/bugs/1778695 Title: ristretto ignores cr2 files Status in file package in Ubuntu: Invalid Status in ristretto package in Ubuntu: Fix Released Bug description: Ristretto does not show canon .cr2 files, neither on 16.04.4 nor on 18.04. For 16.04: lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 apt-cache policy ristretto ristretto: Installed: 0.8.0-1 Candidate: 0.8.0-1 Version table: *** 0.8.0-1 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status for 18.04 lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apt-cache policy ristretto ristretto: Installed: 0.8.2-1ubuntu1 Candidate: 0.8.2-1ubuntu1 Version table: *** 0.8.2-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1778695/+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 1964040] Re: package linux-firmware 1.187.26 failed to install/upgrade: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de er
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 A number of your details as provided don't align (bionic or 18.04 packages on a focal or 20.04 system), so I'm marking this bug as "Incomplete" as it reads like you need support. If you believe I'm in error, please leave a comment explaining why, and the status can be returned to "New". The report can be changed to a question; which is a support request. ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete -- 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/1964040 Title: package linux-firmware 1.187.26 failed to install/upgrade: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de error 1 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: When I run apt-get autoremove command a problems happen. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.26 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-tools-common:amd64: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1593 F pulseaudio rolando2195 F pulseaudio CasperMD5CheckResult: skip Date: Mon Mar 7 19:55:15 2022 Dependencies: ErrorMessage: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de error 1 HibernationDevice: RESUME=UUID=8bf13fc7-285e-42ac-a5aa-730d1ecadca1 InstallationDate: Installed on 2018-04-27 (1410 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04ca:3018 Lite-On Technology Corp. Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G Keyboard Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X542UN PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic root=UUID=d72ca49b-f913-4292-9cb4-fa7e3d62ff1d 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 N/A SourcePackage: initramfs-tools Title: package linux-firmware 1.187.26 failed to install/upgrade: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X542UN.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X542UN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX542UN.300:bd09/19/2017:svnASUSTeKCOMPUTERINC.:pnX542UN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X542UN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1964040/+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 1964040] [NEW] package linux-firmware 1.187.26 failed to install/upgrade: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de
Public bug reported: When I run apt-get autoremove command a problems happen. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.26 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-tools-common:amd64: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1593 F pulseaudio rolando2195 F pulseaudio CasperMD5CheckResult: skip Date: Mon Mar 7 19:55:15 2022 Dependencies: ErrorMessage: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de error 1 HibernationDevice: RESUME=UUID=8bf13fc7-285e-42ac-a5aa-730d1ecadca1 InstallationDate: Installed on 2018-04-27 (1410 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04ca:3018 Lite-On Technology Corp. Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G Keyboard Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X542UN PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic root=UUID=d72ca49b-f913-4292-9cb4-fa7e3d62ff1d 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 N/A SourcePackage: initramfs-tools Title: package linux-firmware 1.187.26 failed to install/upgrade: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X542UN.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X542UN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX542UN.300:bd09/19/2017:svnASUSTeKCOMPUTERINC.:pnX542UN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X542UN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER 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/1964040 Title: package linux-firmware 1.187.26 failed to install/upgrade: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de error 1 Status in initramfs-tools package in Ubuntu: New Bug description: When I run apt-get autoremove command a problems happen. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.26 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-tools-common:amd64: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1593 F pulseaudio rolando2195 F pulseaudio CasperMD5CheckResult: skip Date: Mon Mar 7 19:55:15 2022 Dependencies: ErrorMessage: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de error 1 HibernationDevice: RESUME=UUID=8bf13fc7-285e-42ac-a5aa-730d1ecadca1 InstallationDate: Installed on 2018-04-27 (1410 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04ca:3018 Lite-On Technology Corp. Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G Keyboard Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X542UN PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic root=UUID=d72ca49b-f913-4292-9cb4-fa7e3d62ff1d ro quiet splash vt.handoff=7
[Touch-packages] [Bug 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency
> To upgrade to webkit2gtk 2.34.6-0ubuntu0.20.04.1, u-a must install libopengl0, either 1.3.1-1 from the main archive or 1.3.2-1~ubuntu0.20.04.1 from -updates. However, -updates is not a trusted source for u-a when configured like this, so the only candidate is 1.3.1-1. Unfortunately libopengl0 1.3.1-1 depends on libglvnd0=1.3.1-1, but 1.3.2-1~ubuntu0.20.04.1 is already installed, so u-a would have to downgrade it which is I guess a decision well beyond its pay-grade. Oh, I believe this is the actually issue here. Unattended-upgrades only updates from the -security pocket, so a security update can't rely on something that is only in -updates. I will look into pushing the binary packages from libglvnd to the -security pocket so that the upgrade can be handled properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1963751 Title: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Version: 2.34.6-0ubuntu0.20.04.1 This security update for focal does not seem to be automatically upgradeable by unattended-upgrades: 2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:38,031 INFO No packages found that can be upgraded unattended and no pending auto-removals 2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back because a related package is kept back or due to local apt_preferences(5). 2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back because a related package is kept back or due to local apt_preferences(5). apt-mark showhold lists no held packages, and there are no apt_preferences set. The actual cause seems to be an extra dependency on libopengl0 which has been added with the upgrade. Is this intentional? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 5 14:39:24 2022 InstallationDate: Installed on 2018-06-15 (1358 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: webkit2gtk UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1963751/+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 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency
Thanks for doing the digging to confirm the cause; I suspect unattended- upgrades should be modified to perform something similar to apt upgrade, rather than apt-get upgrade, and bring in new dependencies when necessary. A lot of systems never have interactive users any more. Thanks ** Changed in: unattended-upgrades (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1963751 Title: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Version: 2.34.6-0ubuntu0.20.04.1 This security update for focal does not seem to be automatically upgradeable by unattended-upgrades: 2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:38,031 INFO No packages found that can be upgraded unattended and no pending auto-removals 2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back because a related package is kept back or due to local apt_preferences(5). 2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back because a related package is kept back or due to local apt_preferences(5). apt-mark showhold lists no held packages, and there are no apt_preferences set. The actual cause seems to be an extra dependency on libopengl0 which has been added with the upgrade. Is this intentional? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 5 14:39:24 2022 InstallationDate: Installed on 2018-06-15 (1358 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: webkit2gtk UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1963751/+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 1960608] Re: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10
This new sysconfig-debian-schemes.diff has broken virtual environments (venv and virtualenv). Please take a look at the fix in https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1960608 Title: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10 Status in automake-1.16 package in Ubuntu: Fix Released Status in dh-python package in Ubuntu: Fix Released Status in python-pip package in Ubuntu: Fix Released Status in python3.10 package in Ubuntu: Fix Released Bug description: pip3-root.sh expects world package to be installed in /usr/local/lib/python3.*/dist-packages whereas it is actually installed into /usr/lib/python3.10/site-packages/. It even fails to uninstall the package right after installing it: ubuntu@autopkgtest:~$ sudo python3 -m pip install world Collecting world Using cached world-4.1.1-py3-none-any.whl Collecting atpublic Using cached atpublic-3.0.1-py3-none-any.whl (4.8 kB) Installing collected packages: atpublic, world Successfully installed atpublic-3.0.1 world-4.1.1 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv ubuntu@autopkgtest:~$ sudo python3 -m pip uninstall world WARNING: Skipping world as it is not installed. WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/automake-1.16/+bug/1960608/+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 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency
The other option in u-a might be to split Unattended-Upgrade::Allowed- Origins into "Automatic origins" and "permitted origins", so only packages in the former will be automatically installed, but upgraded dependencies could be pulled from the latter if required? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1963751 Title: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Version: 2.34.6-0ubuntu0.20.04.1 This security update for focal does not seem to be automatically upgradeable by unattended-upgrades: 2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:38,031 INFO No packages found that can be upgraded unattended and no pending auto-removals 2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back because a related package is kept back or due to local apt_preferences(5). 2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back because a related package is kept back or due to local apt_preferences(5). apt-mark showhold lists no held packages, and there are no apt_preferences set. The actual cause seems to be an extra dependency on libopengl0 which has been added with the upgrade. Is this intentional? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 5 14:39:24 2022 InstallationDate: Installed on 2018-06-15 (1358 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: webkit2gtk UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1963751/+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 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency
Digging a bit further - this machine was manually dist-upgraded on 30-May-2021 (it has -updates enabled, but is set to install only security updates automatically.) That update pulled in libglvnd 1.3.2-1~ubuntu0.20.04.1 (source for libegl1, libglvnd0, etc.) To upgrade to webkit2gtk 2.34.6-0ubuntu0.20.04.1, u-a must install libopengl0, either 1.3.1-1 from the main archive or 1.3.2-1~ubuntu0.20.04.1 from -updates. However, -updates is not a trusted source for u-a when configured like this, so the only candidate is 1.3.1-1. Unfortunately libopengl0 1.3.1-1 depends on libglvnd0=1.3.1-1, but 1.3.2-1~ubuntu0.20.04.1 is already installed, so u-a would have to downgrade it which is I guess a decision well beyond its pay-grade. I suppose the solution is to find a way to lose the new dependency, obvious answer would be to backport the fixes in webkit2gtk 2.34.6 to 2.34.4? I assume there is some sort of policy on adding new dependencies in security updates? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1963751 Title: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Version: 2.34.6-0ubuntu0.20.04.1 This security update for focal does not seem to be automatically upgradeable by unattended-upgrades: 2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:38,031 INFO No packages found that can be upgraded unattended and no pending auto-removals 2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back because a related package is kept back or due to local apt_preferences(5). 2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back because a related package is kept back or due to local apt_preferences(5). apt-mark showhold lists no held packages, and there are no apt_preferences set. The actual cause seems to be an extra dependency on libopengl0 which has been added with the upgrade. Is this intentional? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 5 14:39:24 2022 InstallationDate: Installed on 2018-06-15 (1358 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: webkit2gtk UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1963751/+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 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency
I suppose there's an argument to be made that if the user is prepared to periodically manually install non-security updates, then they should be prepared to check for held back security updates too. I tend to work from the command-line so don't know what the GUI interface(s) allow and indicate in this scenario. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1963751 Title: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Version: 2.34.6-0ubuntu0.20.04.1 This security update for focal does not seem to be automatically upgradeable by unattended-upgrades: 2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:38,031 INFO No packages found that can be upgraded unattended and no pending auto-removals 2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back because a related package is kept back or due to local apt_preferences(5). 2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back because a related package is kept back or due to local apt_preferences(5). apt-mark showhold lists no held packages, and there are no apt_preferences set. The actual cause seems to be an extra dependency on libopengl0 which has been added with the upgrade. Is this intentional? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 5 14:39:24 2022 InstallationDate: Installed on 2018-06-15 (1358 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: webkit2gtk UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1963751/+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 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency
The new dependency on libopengl0 is expected. The new version of WebKitGTK fixed opengl detection and the new dependency is now required. I am going to re-assign this bug to unattended-upgrades. If it's not willing to install new dependencies, it definitely should get fixed as some security updates will always get held back. ** Package changed: webkit2gtk (Ubuntu) => unattended-upgrades (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1963751 Title: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Version: 2.34.6-0ubuntu0.20.04.1 This security update for focal does not seem to be automatically upgradeable by unattended-upgrades: 2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:38,031 INFO No packages found that can be upgraded unattended and no pending auto-removals 2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back because a related package is kept back or due to local apt_preferences(5). 2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back because a related package is kept back or due to local apt_preferences(5). apt-mark showhold lists no held packages, and there are no apt_preferences set. The actual cause seems to be an extra dependency on libopengl0 which has been added with the upgrade. Is this intentional? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 5 14:39:24 2022 InstallationDate: Installed on 2018-06-15 (1358 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: webkit2gtk UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1963751/+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 1963751] [NEW] focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency
*** This bug is a security vulnerability *** You have been subscribed to a public security bug: Version: 2.34.6-0ubuntu0.20.04.1 This security update for focal does not seem to be automatically upgradeable by unattended-upgrades: 2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:38,031 INFO No packages found that can be upgraded unattended and no pending auto-removals 2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back because a related package is kept back or due to local apt_preferences(5). 2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back because a related package is kept back or due to local apt_preferences(5). apt-mark showhold lists no held packages, and there are no apt_preferences set. The actual cause seems to be an extra dependency on libopengl0 which has been added with the upgrade. Is this intentional? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 5 14:39:24 2022 InstallationDate: Installed on 2018-06-15 (1358 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: webkit2gtk UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago) ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal -- focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency https://bugs.launchpad.net/bugs/1963751 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades 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 1963834] Re: openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
It looks like this was added in:
https://github.com/openssl/openssl/commit/72d2670bd21becfa6a64bb03fa55ad82d6d0c0f3
in order to address servers that have not yet been updated for
CVE-2009-3555.
It's possible to add a flag at the C level to connect insecurely,
SSL_OP_LEGACY_SERVER_CONNECT, but I don't see this added to python:
https://bugs.python.org/issue44888
https://github.com/python/cpython/pull/27776
Thus it might not be easily reachable from Python programs.
Best would be to update the remote server to address CVE-2009-3555 (it
might also be known as "support RFC 5746"). I'm not sure what to suggest
for programs written in Python.
Thanks
** Bug watch added: Python Roundup #44888
http://bugs.python.org/issue44888
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-3555
--
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/1963834
Title:
openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
Status in openssl package in Ubuntu:
New
Bug description:
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
openssl:
Installé : 3.0.1-0ubuntu1
Candidat : 3.0.1-0ubuntu1
Table de version :
*** 3.0.1-0ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
Using Ubuntu 22.04, I now get the following error message when
attempting to connect to our office VPN using "gp-saml-gui
(https://github.com/dlenski/gp-saml-gui)" :
#
dominique@Doombuntu:~$ .local/bin/gp-saml-gui server_url
Looking for SAML auth tags in response to
https://server_url/global-protect/prelogin.esp...
usage: gp-saml-gui [-h] [--no-verify] [-C COOKIES | -K] [-g | -p] [-c CERT]
[--key KEY] [-v | -q] [-x | -P | -S] [-u] [--clientos {Windows,Linux,Mac}] [-f
EXTRA] server [openconnect_extra ...]
gp-saml-gui: error: SSL error: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
unsafe legacy renegotiation disabled (_ssl.c:997)
#
#
#
gp-saml-gui uses python module requests.
Using python ide, I can get the same results :
#
>>> r = requests.get('https://server_url')
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699,
in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382,
in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012,
in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 411, in
connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in
ssl_wrap_socket
ssl_sock = _ssl_wrap_socket_impl(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in
_ssl_wrap_socket_impl
return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/lib/python3.10/ssl.py", line 512, in wrap_socket
return self.sslsocket_class._create(
File "/usr/lib/python3.10/ssl.py", line 1070, in _create
self.do_handshake()
File "/usr/lib/python3.10/ssl.py", line 1341, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy
renegotiation disabled (_ssl.c:997)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in
send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755,
in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in
increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='server_url',
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1,
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation
disabled (_ssl.c:997)')))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/requests/api.py", line 76, in get
return request('get', url, params=params, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in
send
r = adapter.send(request, **kwargs)
File
[Touch-packages] [Bug 1964035] Re: no image on monitor on laptop with two graphics card (onboard intel+nvidia rtx3050) if run nvidia only
** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New -- 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/1964035 Title: no image on monitor on laptop with two graphics card (onboard intel+nvidia rtx3050) if run nvidia only Status in linux-hwe-5.13 package in Ubuntu: New Status in linux-signed-hwe-5.8 package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: i have laptop (Vendor:MSI / Model:Katana GF76 11UC) with two graphics card (onboard intel+nvidia rtx3050) I didn't like how intel (i915) works (flickering problem has not yet been overcome) so I decided to try using nvidia only. I spent a long time dealing with the "xorg" settings in order to run "x" on nvidia only: * disable the i915 driver with kernel settings: `modprobe.blacklist=i915 i915.modeset=0` * rename /usr/share/X11/xorg.conf.d/20-intel.conf to *.bak * then modify /usr/share/X11/xorg.conf.d/10-nvidia.conf (set Identifier "Card0" ) after starting startx on the screen, the image freezes when switching to tty2 and back to tty1, the server does not render anything, and if you open `top` in tty2, you can see: ``` MiB Mem : 31808,1 total, 24998,2 free, 5471,6 used, 1338,3 buff/cache MiB Swap:954,0 total,954,0 free, 0,0 used. 25914,7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2547 root 20 0 2880328 156160 86076 R 100,3 0,5 6:19.96 kwin_x11 3033 hetman20 0 3052116 350728 186196 S 1,0 1,1 0:06.43 firefox 3314 hetman20 0 2477080 140688 93056 S 1,0 0,4 0:01.23 Isolated Web Co 306 root 20 0 0 0 0 I 0,3 0,0 0:00.36 kworker/6:2-events 776 message+ 20 09044 6032 3828 S 0,3 0,0 0:01.62 dbus-daemon 801 root 20 0 16852 7828 6892 S 0,3 0,0 0:00.17 systemd-logind 2967 hetman20 0 5771360 4,4g 124548 S 0,3 14,1 2:04.60 plasmashell 3000 hetman20 0 340504 63760 50732 S 0,3 0,2 0:00.37 kwalletd5 3207 hetman20 0 2427008 110324 89080 S 0,3 0,3 0:00.30 Privileged Cont 3607 root 20 0 0 0 0 I 0,3 0,0 0:00.03 kworker/u24:2-events_power_efficient ``` nvidia-smi ``` hetman@katana-lin:/mnt/giga/xorg_nvidia$ cat mvidia-smi.log Mon Mar 7 23:03:53 2022 +-+ | NVIDIA-SMI 510.47.03Driver Version: 510.47.03CUDA Version: 11.6 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA GeForce ... Off | :01:00.0 Off | N/A | | N/A 41CP8N/A / N/A |132MiB / 4096MiB | 0% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 2847 G /usr/lib/xorg/Xorg 12MiB | |0 N/A N/A 2967 G /usr/bin/plasmashell8MiB | |0 N/A N/A 3033 G /usr/lib/firefox/firefox 85MiB | |0 N/A N/A 4436 G ...bexec/kscreenlocker_greet 12MiB | +-+ ``` Thus, I stated that the X's started up and are working, but the image is not displayed. if return modprobe i915.modeset=1 /usr/share/X11/xorg.conf.d/20-intel.conf /usr/share/X11/xorg.conf.d/10-nvidia.conf - otherwise the output always goes through only intel (i915) nvidia not uses even if use `prime-select nvidia` - this option ignoring -
[Touch-packages] [Bug 1959508] Re: enable BMFF support in exiv2
I can confirm CR3 support is not enabled in exiv2 0.27.5-1. It very much appears the steps outlined by Robin Mills (aka clanmills) have not been undertaken by the Debian packager. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1959508 Title: enable BMFF support in exiv2 Status in exiv2 package in Ubuntu: Incomplete Status in exiv2 package in Debian: Fix Released Bug description: On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that Ubuntu 22.04 currently includes exiv2 0.27.3 Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3 file format has been the Canon camera-raw file format since mid 2018, and is probably one of the most common raw image file formats today. Applications such as darktable, amongst others, use exiv2 to extract image metadata, thumbnails and previews, and can only open CR3 files when linked with exiv2 0.27.5 or later. Note that exiv2 0.27.5 needs to be built with -DEXIV2_ENABLE_BMFF=On to enable *.CR3 support. Would it be possible to get Exiv2 v0.27.5 with BMFF support enabled included in Ubuntu 22.04? Note that a similar request exists for Debian in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000788 References https://github.com/exiv2/exiv2#2-19 https://github.com/Exiv2/exiv2/issues/1229 https://github.com/darktable-org/darktable/pull/10332 https://github.com/Beep6581/RawTherapee/issues/6248#issuecomment-869208918 https://answers.launchpad.net/ubuntu/+source/exiv2/+question/700398 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+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 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
** Package changed: ubuntu => systemd (Ubuntu) -- 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/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket Status in systemd package in Ubuntu: Confirmed Bug description: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+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 1962843] [NEW] Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
You have been subscribed to a public bug: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment -- Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket https://bugs.launchpad.net/bugs/1962843 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 1906642] Re: Xorg crashes with abort in iris_dri.so
*** This bug is a duplicate of bug 1871959 *** https://bugs.launchpad.net/bugs/1871959 i have problem like this but Xorg didn't crash only on some Applications like: * Discover (plasma-discover), * Сістэмныя настаўленні (systemsettings5) some etc. Crash report has iris_dri.so [KCrash Handler] #6 0x7f44730525fe in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #7 0x7f44731fafba in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #8 0x7f4472fe9b08 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #9 0x7f4472feb186 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #10 0x7f447292d1b3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #11 0x7f447292d37a in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #12 0x7f44729319db in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #13 0x7f447293280b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #14 0x7f4472350422 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #15 0x7f44724fda1f in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #16 0x7f4472500959 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #17 0x7f4472506699 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #18 0x7f448af52bac in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7f448af53068 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #20 0x7f448af5352a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 ... this problem on newest kernel 5.16.12-051612-generic #202203030915-Ubuntu -- 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/1906642 Title: Xorg crashes with abort in iris_dri.so Status in mesa package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: System is crashing, logging out and i am constantly losing all my work if it's not saved Description: Ubuntu 20.04 LTS (fossa-beric-icl X31) Release: 20.04 N: Unable to locate package pkgname I expect not to happen (crash->log out) Instead, it happened ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 12:33:11 2020 DistUpgraded: Fresh install 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 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a2a] InstallationDate: Installed on 2020-09-19 (74 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 3501 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=6b577a12-8585-4836-a5fc-abc3857f42ce ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 01D26F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd07/06/2020:svnDellInc.:pnVostro3501:pvr:rvnDellInc.:rn01D26F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3501 dmi.product.sku: 0A2A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/+source/mesa/+bug/1906642/+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 1964021] [NEW] pulseaudio crashes when using Spotify (from Snap)
Public bug reported: pulseaudio crashed twice while listening to Spotify (snap package). It was automatically respawn via systemd ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 5.15.21-051521-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Mar 7 19:17:36 2022 InstallationDate: Installed on 2012-02-27 (3660 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-01-11 (55 days ago) dmi.bios.date: 01/15/2010 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.10F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:br8.15:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-07-11T22:52:45.088258 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1964021 Title: pulseaudio crashes when using Spotify (from Snap) Status in pulseaudio package in Ubuntu: New Bug description: pulseaudio crashed twice while listening to Spotify (snap package). It was automatically respawn via systemd ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 5.15.21-051521-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Mar 7 19:17:36 2022 InstallationDate: Installed on 2012-02-27 (3660 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-01-11 (55 days ago) dmi.bios.date: 01/15/2010 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.10F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:br8.15:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-07-11T22:52:45.088258 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1964021/+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 1962332] Re: xenial systemd fails to start if cgroup2 is mounted
Backporting 099619957a0 to xenial will mean that systemd will gain ability to use cgroups2 as shipped in the xenial's ga v4.4 kernel. it will mean that xenial containers on top of bionic's ga kernel will fail to use cgroups2. however at the time it was an experimental feature which was not widely used at all, and there are likely to be very few users of it. it would be nice to if backport of 099619957a0 was done in a backwards- compatible way and allow using cgroups2 like code paths using both pre-v4.4 and v4.4+ kernels. -- 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/1962332 Title: xenial systemd fails to start if cgroup2 is mounted Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Bug description: [impact] now that jammy has moved to using unified cgroup2, containers started on jammy must also use unified cgroup2 (since the cgroup subsystems can only be mounted as v1 or v2 throughout the entire system, including inside containers). However, the systemd in xenial does not include support for cgroup2, and doesn't recognize its magic (added in upstream commit 099619957a0), so it fails to start completely. [workaround] On Jammy host edit default kernel command line to include systemd.unified_cgroup_hierarchy=false update your bootloader configuration; and reboot then hybrid cgroups will be on the host, and one can launch xenial container then. [test case] create a jammy system, that has unified cgroup2 mounted. Then: $ lxc launch ubuntu:xenial test-x ... $ lxc shell test-x (inside xenial container): $ mv /sbin/init /sbin/init.old $ cat > /sbin/init <+a q Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems, freezing. Freezing execution. [regression potential] any regression would likely break xenial containers from starting at all, or cause cgroup-related problems with systemd starting and/or managing services. [scope] this is needed only for xenial. However, as xenial is out of standard support, this would need to be an exception. this is fixed upstream with commit 099619957a0 (and possibly others - needs closer investigation and testing) which is first included in v230, so this is fixed already in b and later. this is not needed - by default - for trusty because upstart is used there; however, I think it's possible to change trusty over to use systemd instead of upstart. But since trusty is out of standard support, and it doesn't fail by default, it doesn't seem like it should be fixed. [other info] An alternative appears to be to change the host system back to using the 'hybrid' cgroup, however that obviously is awful and would remove the benefits of cgroup v2 from the host system, and force all containers on the host system to also use the 'hybrid' cgroup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+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 1963904] Re: /usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup
The attachment "01_fix-single-candidate-pkgid-emission.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 packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1963904 Title: /usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup Status in packagekit package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.2.5-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/e43a7af1acb9c04a2066e00f2785c7c200145bcc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1963904/+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 1962332] Re: xenial systemd fails to start if cgroup2 is mounted
** Description changed: [impact] now that jammy has moved to using unified cgroup2, containers started on jammy must also use unified cgroup2 (since the cgroup subsystems can only be mounted as v1 or v2 throughout the entire system, including inside containers). However, the systemd in xenial does not include support for cgroup2, and doesn't recognize its magic (added in upstream commit 099619957a0), so it fails to start completely. + + [workaround] + On Jammy host edit default kernel command line to include + + systemd.unified_cgroup_hierarchy=false + + update your bootloader configuration; and reboot + + then hybrid cgroups will be on the host, and one can launch xenial + container then. + [test case] create a jammy system, that has unified cgroup2 mounted. Then: $ lxc launch ubuntu:xenial test-x ... $ lxc shell test-x (inside xenial container): $ mv /sbin/init /sbin/init.old $ cat > /sbin/init <+a q Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems, freezing. Freezing execution. [regression potential] any regression would likely break xenial containers from starting at all, or cause cgroup-related problems with systemd starting and/or managing services. [scope] this is needed only for xenial. However, as xenial is out of standard support, this would need to be an exception. this is fixed upstream with commit 099619957a0 (and possibly others - needs closer investigation and testing) which is first included in v230, so this is fixed already in b and later. this is not needed - by default - for trusty because upstart is used there; however, I think it's possible to change trusty over to use systemd instead of upstart. But since trusty is out of standard support, and it doesn't fail by default, it doesn't seem like it should be fixed. [other info] An alternative appears to be to change the host system back to using the 'hybrid' cgroup, however that obviously is awful and would remove the benefits of cgroup v2 from the host system, and force all containers on the host system to also use the 'hybrid' cgroup. -- 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/1962332 Title: xenial systemd fails to start if cgroup2 is mounted Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Bug description: [impact] now that jammy has moved to using unified cgroup2, containers started on jammy must also use unified cgroup2 (since the cgroup subsystems can only be mounted as v1 or v2 throughout the entire system, including inside containers). However, the systemd in xenial does not include support for cgroup2, and doesn't recognize its magic (added in upstream commit 099619957a0), so it fails to start completely. [workaround] On Jammy host edit default kernel command line to include systemd.unified_cgroup_hierarchy=false update your bootloader configuration; and reboot then hybrid cgroups will be on the host, and one can launch xenial container then. [test case] create a jammy system, that has unified cgroup2 mounted. Then: $ lxc launch ubuntu:xenial test-x ... $ lxc shell test-x (inside xenial container): $ mv /sbin/init /sbin/init.old $ cat > /sbin/init <+a q Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems, freezing. Freezing execution. [regression potential] any regression would likely break xenial containers from starting at all, or cause cgroup-related problems with systemd starting and/or managing services. [scope] this is needed only for xenial. However, as xenial is out of standard support, this would need to be an exception. this is fixed upstream with commit 099619957a0 (and possibly others - needs closer investigation and testing) which is first included in v230, so this is fixed already in b and later. this is not needed - by default - for trusty because upstart is used there; however, I think it's possible to change trusty over to use systemd instead of upstart. But since trusty is out of standard support, and it doesn't fail by default, it doesn't seem like it should be fixed. [other info] An alternative appears to be to change the host system back to using the 'hybrid' cgroup, however that obviously is awful and would remove the benefits of cgroup v2 from the host system, and force all containers on the host system to also use the 'hybrid' cgroup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam
Eduroam is a WPA2 Enterprise network. It supported different EAP methods (https://wiki.geant.org/pages/viewpage.action?pageId=121346284): - EAP TTLS-PAP - PEAP - EAP TLS - EAP-pwd I always use the default option selected in Ubuntu Wi-Fi Settings, which is labeled "Tunneled TLS". But I double-checked some guides and most recommend PEAP, which I've now also tried and had the same issue with. Guide from my institution: https://it.umn.edu/services-technologies/how-tos/wifi-connect-unix-or-linux-most-major Another guide: https://www.ucl.ac.uk/isd/how-to/connecting-to-eduroam-wi-fi-linux I usually use the "No CA certificate is required" option as shown in the second guide. The "Inner authentication" is the default option, MSCHAPv2. Log attached. Thanks! ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+attachment/5566574/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network eduroam Status in wpa package in Ubuntu: Incomplete Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
Don't know if this is possible, but would there be a way to have gdb stop at the point where the segfault occurs in the updated library when using the previous release to see what differs? I want to help you track this down, but I am unsure what else I can do at this point. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+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 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
I gave a try and I can confirm that following the modemmanager docs to enable FCC unlock procedure at ModemManager level, the modem is properly unlocked and connects to the internet. However, this is another issue, but the firmware crashing persist when trying to make use of the LTE connection a bit more than just sending a ping. -- 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/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1955997] Re: The airplane hotkey has no function on a HP platform
Hi Robie, any update on this?
As Jeremy described earlier, we choose to implement the safe way for the
SRUs by keeping an allow-list of supported devices, instead of switching
over to the upstream solution.
--
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/1955997
Title:
The airplane hotkey has no function on a HP platform
Status in OEM Priority Project:
Triaged
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
In Progress
Status in systemd source package in Impish:
In Progress
Status in systemd source package in Jammy:
Fix Released
Bug description:
[Impact]
The airplane hokey doesn't work on HP new generation machines.
[Test Plan]
Press airplane hokey.
Before the patch, nothing happens.
After the patch, the rfkill works as expected.
In some old HP platforms (contains Intel-HID and HPQ6001 in same
machine), the user will aware the airplane mode toggled very quickly
e.g. turn-on and turn-off immediately (or works good without problem,
depends on how DM handles multiple rfkill events).
In this case, you could check:
1. sudo evtest
# You probably could see
# ...
# /dev/input/event8: Intel HID events
# ...
# /dev/input/event11: Wireless hotkeys
# or "HP Wireless hotkeys" depends on your kernel version
2. try to listen these events when pressing airplane key, you will
probably see these two events will send the keycode out.
3. check the components own this event
$ sudo udevadm info -a /dev/input/event11
# ...
# ATTRS{phys}=="hpq6001/input0"
$ sudo udevadm info -a /dev/input/event8
# ...
#DRIVERS=="intel-hid"
4. check your hwdb is affect.
$ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
# If you didn't see anything then it means your intel-hid is unmask.
5. You could report a bug to your DM for dealing with two rfkill events (same
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as
workaround (but it will be overwritten in next upgrade) by adding:
```
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
```
to /lib/udev/hwdb.d/60-keyboard.hwdb
then
$ systemd-hwdb update
$ udevadm trigger
[Where problems could occur]
In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will
not work but HP confirmed the new HP generation won't contain the HPQ6001 and
also each DM still need to deal with multi-rfkill events because upstream
changes[2].
---
In the last year, HP mentions HP machines need to use hp-wireless
(HPQ6001) as the rfkill source[1].
However, HP confirms the HPQ6001 has been retired in the platforms
since 2022.
In the platforms after 2022, there are two sources of rkfill events
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
Therefore, the upstream already accept the patch[2] to unmask intel-hid and
mention this big change in the NEWS.
This change makes the pre-2022 HP platforms meet the regression since they
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing
function key.
Thus, there is a patch[3] to make sure the GNOME could deal with this case
smoothly.
However, the systemd change will still cause other DEs meet the regression
(xfce, KDE, lxde, etc..).
Backport systemd change to make HP 2022 platforms work is not the best choice
on stable version (focal in this case).
We still need a solution to make airplane key works on 2022 HP platforms
(intel-hid and atkbd only).
The potential solution from my mind that is to maintain a whitelist to unmask
intel-hid in ubuntu-patch in focal, something like:
```
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
KEYBOARD_KEY_8=wlan # Use hp-wireless instead
```
after "KEYBOARD_KEY_8=unkown".
[1] https://bugs.launchpad.net/bugs/1883846
[2] https://github.com/systemd/systemd/pull/20219
[3]
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955997/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam
Thank you for your bug report, do you have details on what sort of configuration and security options is eduroam using? Could you edit /lib/systemd/system/wpa_supplicant.service to add a '-d' to the ExecStart cmd, restart, try to connect and share the 'journalctl -b 0' log from the system? ** Changed in: wpa (Ubuntu) Importance: Undecided => High ** Changed in: wpa (Ubuntu) Status: Confirmed => Incomplete ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network eduroam Status in wpa package in Ubuntu: Incomplete Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
There was a bad tag update before, this is verified on Focal as well.
Fixed now ...
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
** Changed in: rsync (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: rsync (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync:
Unknown
Status in rsync package in Ubuntu:
Fix Released
Status in rsync source package in Bionic:
Fix Released
Status in rsync source package in Focal:
Fix Committed
Bug description:
[Impact]
What the user suffering from this bug experiences is that the big
amount of informative messages related to the copy process with the
three spawned processes(sender, receiver and generator) exhaust the
I/O buffer and the sync gets stuck, either because there are too many
files to synchronise and/or because too many detail messages (levels
of verbose mode) have been requested in the output.
The fix, that comes from upstream and is applied there since version
3.2.0., increments the size of the receiver's I/O buffer.
[Test Plan]
This test plan is for Focal, but it's the same for Bionic.
0.Preparing the test environment:
#Preparing the container
lxc launch images:ubuntu/focal rsync-iobuffer-focal
lxc shell rsync-iobuffer-focal
apt update -y
apt upgrade -y
#Installing necessary tools
apt install rsync
#Get test cases from comments #16 and #19 on this LP bug: As test case
#16 covers both aspects (a lot of files and upper verbosity) and test
#19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19
scenario (but, please, feel to reach me it if you consider it
necessary and I'll provide the steps and bad/good scenarios).
cd /tmp/
#16
Paste the contents of https://pastebin.com/raw/ctzJJGwt:
#!/bin/bash
mkdir source_dir
pushd source_dir
dd if=/dev/zero of=source bs=600K count=1
for i in `seq 1 11500`;
do
cp -v source file_$i;
done
rm source
for i in `seq 1 10`;
do
dd if=/dev/zero of=file_large_$i bs=200M count=1
done
popd
echo "Created 11500 files with size 600K and 10 files with size 200M, try the
following command:"
echo "rsync -avvvz --delete source_dir target_dir"
in a new file script_comment16.sh
chmod +x script_comment16.sh
./script_comment16.sh
1. Bad cases (without and with using strace):
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /root/source_dir/
[sender] make_file(source_dir/file_3048,*,2)
[sender] make_file(source_dir/file_11358,*,2)
[sender] make_file(source_dir/file_5914,*,2)
[sender] make_file(source_dir/file_5880,*,2)
[sender] make_file(source_dir/file_9318,*,2)
[sender] make_file(source_dir/file_5539,*,2)
[...]
sending file_sum
false_alarms=0 hash_hits=0 matches=0
sender finished source_dir/file_10807
send_files(903, source_dir/file_10808)
send_files mapped source_dir/file_10808 of size 614400
calling match_sums source_dir/file_10808
source_dir/file_10808
It hangs here, where using strace we can see:
$ strace rsync -avvvz --delete source_dir target_dir
source_dir/file_11280
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 90112) =
90112
select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 1 (in [5], left
{tv_sec=59, tv_usec=96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"...,
1900) = 1900
select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(5, [], [4], [], {tv_sec=60, tv_usec=0}
1. Good cases:
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /tmp/source_dir/
[sender] make_file(source_dir/file_3052,*,2)
[sender] make_file(source_dir/file_1766,*,2)
[sender] make_file(source_dir/file_10466,*,2)
[sender] make_file(source_dir/file_9375,*,2)
[sender] make_file(source_dir/file_7260,*,2)
[sender] make_file(source_dir/file_5554,*,2)
[sender] make_file(source_dir/file_5523,*,2)
[sender] make_file(source_dir/file_1685,*,2)
[sender] make_file(source_dir/file_7217,*,2)
[sender] make_file(source_dir/file_10411,*,2)
[...]
generate_files finished
sent 9,555,678 bytes received 3,599,560 bytes
[Touch-packages] [Bug 1915238] Re: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ
Thanks to Scott this is Fixed in version postfix/3.6.3-5 And since the package is in sync this is in Jammy now: postfix | 3.6.3-5ubuntu2| jammy | source, amd64, arm64, armhf, ppc64el, riscv64, s390x ** Changed in: postfix (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1915238 Title: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ Status in ca-certificates package in Ubuntu: Invalid Status in postfix package in Ubuntu: Fix Released Status in postfix package in Debian: Fix Released Bug description: Postfix package doesn't utilize update-ca-certificate's hooks mechanism. By simply copying certs from /etc/ssl/certs/ca- certificates.crt to /var/spool/postfix/etc/ssl/certs/ca- certificates.crt, this warning and potential security issues could be avoided. Something like this would be a start: $ cat /etc/ca-certificates/update.d/postfix #!/bin/bash if [ -e /var/spool/postfix/etc/ssl/certs/ca-certificates.crt ]; then echo "Updating postfix chrooted certs" cp /etc/ssl/certs/ca-certificates.crt /var/spool/postfix/etc/ssl/certs/ca-certificates.crt systemctl reload postfix fi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1915238/+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 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
Thanks, I just saw that Jammy has 1.26.2. I might try and give it a try to verify the behavior of the LTE modem there. -- 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/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1963904] Re: /usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup
** Patch added: "01_fix-single-candidate-pkgid-emission.patch" https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1963904/+attachment/5566548/+files/01_fix-single-candidate-pkgid-emission.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1963904 Title: /usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup Status in packagekit package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.2.5-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/e43a7af1acb9c04a2066e00f2785c7c200145bcc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1963904/+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 1963904] Re: /usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup
Looks like PK needs an updated `fix-single-candidate-pkgid-emission.patch` patch (attached). I queued it for Debian, but I am secretly waiting whether we will get another PK bugfix release in time (there's a few things left that I need to have a look at). In any case, I believe the attached patch should fix this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1963904 Title: /usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup Status in packagekit package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.2.5-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/e43a7af1acb9c04a2066e00f2785c7c200145bcc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1963904/+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 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
The new versions are in the current Ubuntu series, there is no plan to backport to impish though since that's a non LTS serie and there is limited demand for a such change ** Changed in: modemmanager (Ubuntu) Status: New => Fix Released ** Changed in: libmbim (Ubuntu) Status: New => Fix Released ** Changed in: modemmanager (Ubuntu) Importance: Undecided => Low ** Changed in: libmbim (Ubuntu) Importance: Undecided => Low -- 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/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1963903] Re: expat relax fix for CVE-2022-25236 and possible regressions
https://github.com/exxamalte/python-aio-georss-client/issues/29 ** Bug watch added: github.com/exxamalte/python-aio-georss-client/issues #29 https://github.com/exxamalte/python-aio-georss-client/issues/29 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1963903 Title: expat relax fix for CVE-2022-25236 and possible regressions Status in expat package in Ubuntu: In Progress Bug description: Sebastian Pipping report to us that these additional fixes are required to fix properly CVE-2022-25236 in regard to RCF 3986 URI characters and possibly regressions as the merge request points. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1963903/+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 1963904] Re: /usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup
** Changed in: packagekit (Ubuntu) Importance: Undecided => High ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1963904 Title: /usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup Status in packagekit package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.2.5-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/e43a7af1acb9c04a2066e00f2785c7c200145bcc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1963904/+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 1963904] [NEW] /usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.2.5-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/e43a7af1acb9c04a2066e00f2785c7c200145bcc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: packagekit (Ubuntu) Importance: High Status: New ** Tags: jammy rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1963904 Title: /usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup Status in packagekit package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.2.5-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/e43a7af1acb9c04a2066e00f2785c7c200145bcc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1963904/+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 1963903] Re: expat relax fix for CVE-2022-25236 and possible regressions
https://github.com/libexpat/libexpat/pull/577 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1963903 Title: expat relax fix for CVE-2022-25236 and possible regressions Status in expat package in Ubuntu: In Progress Bug description: Sebastian Pipping report to us that these additional fixes are required to fix properly CVE-2022-25236 in regard to RCF 3986 URI characters and possibly regressions as the merge request points. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1963903/+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 1963903] [NEW] expat relax fix for CVE-2022-25236 and possible regressions
Public bug reported: Sebastian Pipping report to us that these additional fixes are required to fix properly CVE-2022-25236 in regard to RCF 3986 URI characters and possibly regressions as the merge request points. ** Affects: expat (Ubuntu) Importance: Undecided Assignee: Leonidas S. Barbosa (leosilvab) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1963903 Title: expat relax fix for CVE-2022-25236 and possible regressions Status in expat package in Ubuntu: In Progress Bug description: Sebastian Pipping report to us that these additional fixes are required to fix properly CVE-2022-25236 in regard to RCF 3986 URI characters and possibly regressions as the merge request points. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1963903/+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 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed
** Changed in: lightdm (Ubuntu) Status: Incomplete => Invalid ** Changed in: lightdm-gtk-greeter (Ubuntu) Status: Incomplete => Invalid ** Changed in: upstart (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1322275 Title: lightdm sessions started by dm-tool lock (or a session locker) never get closed Status in Light Display Manager: New Status in lightdm package in Ubuntu: Invalid Status in lightdm-gtk-greeter package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Bug description: dm-tool lock starts a new lightdm greeter (for unlocking) and a new logind session. After unlocking the greeter disappears, but the logind session never closes. loginctl session status c24 reports something like: c24 - lightdm (103) Since: Thu 2014-05-22 18:38:27 CEST; 30min ago Leader: 7872 Seat: seat0; vc8 Display: :1 Service: lightdm-greeter; type x11; class greeter State: closing CGroup: systemd:/user/103.user/c24.session └─7907 init --user --startup-event indicator-services-start This results in an accumulation of stale lightdm sessions after using e.g. a session locker for a while. I get this issue on a freshly installed and fully updated Xubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1322275/+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 1963834] Re: openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
** Tags added: openssl3
--
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/1963834
Title:
openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
Status in openssl package in Ubuntu:
New
Bug description:
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
openssl:
Installé : 3.0.1-0ubuntu1
Candidat : 3.0.1-0ubuntu1
Table de version :
*** 3.0.1-0ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
Using Ubuntu 22.04, I now get the following error message when
attempting to connect to our office VPN using "gp-saml-gui
(https://github.com/dlenski/gp-saml-gui)" :
#
dominique@Doombuntu:~$ .local/bin/gp-saml-gui server_url
Looking for SAML auth tags in response to
https://server_url/global-protect/prelogin.esp...
usage: gp-saml-gui [-h] [--no-verify] [-C COOKIES | -K] [-g | -p] [-c CERT]
[--key KEY] [-v | -q] [-x | -P | -S] [-u] [--clientos {Windows,Linux,Mac}] [-f
EXTRA] server [openconnect_extra ...]
gp-saml-gui: error: SSL error: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
unsafe legacy renegotiation disabled (_ssl.c:997)
#
#
#
gp-saml-gui uses python module requests.
Using python ide, I can get the same results :
#
>>> r = requests.get('https://server_url')
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699,
in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382,
in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012,
in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 411, in
connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in
ssl_wrap_socket
ssl_sock = _ssl_wrap_socket_impl(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in
_ssl_wrap_socket_impl
return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/lib/python3.10/ssl.py", line 512, in wrap_socket
return self.sslsocket_class._create(
File "/usr/lib/python3.10/ssl.py", line 1070, in _create
self.do_handshake()
File "/usr/lib/python3.10/ssl.py", line 1341, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy
renegotiation disabled (_ssl.c:997)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in
send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755,
in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in
increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='server_url',
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1,
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation
disabled (_ssl.c:997)')))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/requests/api.py", line 76, in get
return request('get', url, params=params, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in
send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, in
send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='server_url',
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1,
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation
disabled (_ssl.c:997)')))
#
#
#
I believe in OpenSSL 3.0 that SSL_OP_LEGACY_SERVER_CONNECT is now
disabled by default, as opposed to the version used in earlier Ubuntu
versions (tested to work fine with 20.04 and 21.10).
I can't tell what should be done here. Is there something I can do to
allow enable "SSL_OP_LEGACY_SERVER_CONNECT" for this connection ? Can
something be done in the python module, or does this require
[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow
@re discussion, there has been some posts about the topic at least on https://lists.ubuntu.com/archives/ubuntu-devel/2021-December/041726.html it feels like we would need a feature freeze exception at this point for a such change, or at least an ack from ubuntu release -- 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/1958148 Title: mkinitramfs is too slow Status in initramfs-tools package in Ubuntu: Confirmed Bug description: On the Nezha board creating an initrd takes more than 1 hour. The compression level -19 for zstd is unwisely chosen. Here are durations and compression results for an SiFive Unmatched board with four cores using zstd: -T0 -1 => 13.92s, 136298155 bytes -T0 -2 => 15.73s, 131717830 bytes -T0 -3 => 26.11s, 127434653 bytes -T0 -4 => 29.31s, 126924540 bytes -T0 -5 => 36.44s, 125296557 bytes -T0 -6 => 39.36s, 124781669 bytes -T0 -7 => 46.56s, 116200665 bytes -T0 -8 => 51.95s, 113172941 bytes -T0 -9 => 55.89s, 112835937 bytes -T0 -10 => 61.32s, 108326876 bytes -T0 -11 => 64.32s, 108115060 bytes -T0 -12 => 76.37s, 108016478 bytes -T0 -13 => 148.99s, 109121308 bytes -T0 -14 => 156.58s, 108908574 bytes -T0 -15 => 228.64s, 109213554 bytes -T0 -16 => 380.26s, 107260643 bytes -T0 -17 => 453.36s, 103679714 bytes -T0 -18 => 714.79s, 100402249 bytes -T0 -19 => 1046.58s, 100188713 bytes Compression level between -2 to -10 offer a good compromise between CPU time and compression results. Ideally there would be a parameter that we could pass to mkinitfs. But for as fast solution we should simply replace -19 by -9 in mkinitramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+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 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63
Thank you, I was plagued by this issue on my Bose NC700 cans. In my case bluetoothd isn't crashing btw. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63 Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: Bose quietcomfort 35 is a common headset that can no longer connect to a jammy system after just one suspend. This started at the end of January but just now really debugging the issue. Side note that my bluetooth mouse works fine without problem after any amount of suspends. The headset is only trying to connect to the jammy system (no other bluetooth devices it's paired with has active bluetooth, to isolate only the jammy <-> headset issue). This is jammy running on a T590, up to date, not proposed. heather@fenrir:~$ dpkg -l | grep bluetooth ii gir1.2-gnomebluetooth-1.0:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii libbluetooth-dev:amd64 5.63-0ubuntu1 amd64Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd645.63-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.34.5-4 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1 amd64Bluetooth module for PulseAudio sound server On a fresh boot (not suspended yet), I can connect the headset successfully. Here are the logs of that: Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input30 Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on /dev/input/event22 (Bose QuietComfort 35 (AVRCP)) Mar 01 09:44:03 fenrir NetworkManager[1536]: [1646124243.8660] platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 (Permission denied) Mar 01 09:44:04 fenrir bluetoothd[1532]: /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of process 2708 owned by '1000' RT at priority 5. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume' Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70% Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked But then if I close the laptop lid and reopen, login, and try to connect the headset the device is found invalid with the following logs: Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input152 Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on /dev/input/event19 (Bose QuietComfort 35 (AVRCP)) Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for /org/bluez/hci0/dev_60_AB_D2_07_DB_9F Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() Hands-Free Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist
[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow
** Changed in: initramfs-tools (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1958148 Title: mkinitramfs is too slow Status in initramfs-tools package in Ubuntu: Confirmed Bug description: On the Nezha board creating an initrd takes more than 1 hour. The compression level -19 for zstd is unwisely chosen. Here are durations and compression results for an SiFive Unmatched board with four cores using zstd: -T0 -1 => 13.92s, 136298155 bytes -T0 -2 => 15.73s, 131717830 bytes -T0 -3 => 26.11s, 127434653 bytes -T0 -4 => 29.31s, 126924540 bytes -T0 -5 => 36.44s, 125296557 bytes -T0 -6 => 39.36s, 124781669 bytes -T0 -7 => 46.56s, 116200665 bytes -T0 -8 => 51.95s, 113172941 bytes -T0 -9 => 55.89s, 112835937 bytes -T0 -10 => 61.32s, 108326876 bytes -T0 -11 => 64.32s, 108115060 bytes -T0 -12 => 76.37s, 108016478 bytes -T0 -13 => 148.99s, 109121308 bytes -T0 -14 => 156.58s, 108908574 bytes -T0 -15 => 228.64s, 109213554 bytes -T0 -16 => 380.26s, 107260643 bytes -T0 -17 => 453.36s, 103679714 bytes -T0 -18 => 714.79s, 100402249 bytes -T0 -19 => 1046.58s, 100188713 bytes Compression level between -2 to -10 offer a good compromise between CPU time and compression results. Ideally there would be a parameter that we could pass to mkinitfs. But for as fast solution we should simply replace -19 by -9 in mkinitramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+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 1960863] Re: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances
This bug was fixed in the package openssl - 1.1.1f-1ubuntu2.11 --- openssl (1.1.1f-1ubuntu2.11) focal; urgency=medium * Fixup pointer authentication for armv8 systems that support it when using the poly1305 MAC, preventing segmentation faults. (LP: #1960863) - d/p/lp-1960863-crypto-poly1305-asm-fix-armv8-pointer-authenticat.patch -- Matthew Ruffell Tue, 15 Feb 2022 10:10:01 +1300 ** Changed in: openssl (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1960863 Title: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Released Bug description: [Impact] Support for hardware pointer authentication for armv8 systems was merged in openssl 1.1.1f, but it contains a bug in the implementation for poly1305 message authenticated code routines, which causes the calling program to fail pointer authentication, which causes the program to crash with a segmentation fault. You can easily test it by accessing any website that uses poly1305. There is no workaround except use a different MAC. [Testcase] This bug applies to armv8 systems which support pointer authentication. Start an armv8 instance, such as a c7g graviton 3 instance on AWS, and make sure the paca flag is present in lscpu: $ grep paca /proc/cpuinfo Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm ssbs paca pacg dcpodp svei8mm svebf16 i8mm bf16 dgh rng Next, attempt to connect to any website that uses poly1305 MAC. $ curl https://services.gradle.org/distributions/gradle-7.2-bin.zip --output gradle-7.2.bin % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Segmentation fault (core dumped) There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf327917-test Install it, and poly1305 operations will no longer segfault. [Where problems could occur] The patch changes the order of operations for loading the SP and checking the AUTIASP against it, from checking the AUTIASP against nothing then loading the correct SP to check with, to the correct loading the SP and then checking the AUTIASP against the SP. This only changes one code path for armv8 systems, and other architectures are not affected. This is also only limited to poly1305 MAC. If a regression were to occur, it would only affect users of poly1035 MAC on armv8 with pacs support. [Other info] The fix landed upstream in openssl 1.1.1i with the following commit: commit 5795acffd8706e1cb584284ee5bb3a30986d0e75 Author: Ard Biesheuvel Date: Tue Oct 27 18:02:40 2020 +0100 Subject: crypto/poly1305/asm: fix armv8 pointer authentication Link: https://github.com/openssl/openssl/commit/5795acffd8706e1cb584284ee5bb3a30986d0e75 This commit is already present in Impish onward. Only Focal needs the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960863/+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 1960863] Update Released
The verification of the Stable Release Update for openssl 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 openssl in Ubuntu. https://bugs.launchpad.net/bugs/1960863 Title: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Released Bug description: [Impact] Support for hardware pointer authentication for armv8 systems was merged in openssl 1.1.1f, but it contains a bug in the implementation for poly1305 message authenticated code routines, which causes the calling program to fail pointer authentication, which causes the program to crash with a segmentation fault. You can easily test it by accessing any website that uses poly1305. There is no workaround except use a different MAC. [Testcase] This bug applies to armv8 systems which support pointer authentication. Start an armv8 instance, such as a c7g graviton 3 instance on AWS, and make sure the paca flag is present in lscpu: $ grep paca /proc/cpuinfo Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm ssbs paca pacg dcpodp svei8mm svebf16 i8mm bf16 dgh rng Next, attempt to connect to any website that uses poly1305 MAC. $ curl https://services.gradle.org/distributions/gradle-7.2-bin.zip --output gradle-7.2.bin % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Segmentation fault (core dumped) There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf327917-test Install it, and poly1305 operations will no longer segfault. [Where problems could occur] The patch changes the order of operations for loading the SP and checking the AUTIASP against it, from checking the AUTIASP against nothing then loading the correct SP to check with, to the correct loading the SP and then checking the AUTIASP against the SP. This only changes one code path for armv8 systems, and other architectures are not affected. This is also only limited to poly1305 MAC. If a regression were to occur, it would only affect users of poly1035 MAC on armv8 with pacs support. [Other info] The fix landed upstream in openssl 1.1.1i with the following commit: commit 5795acffd8706e1cb584284ee5bb3a30986d0e75 Author: Ard Biesheuvel Date: Tue Oct 27 18:02:40 2020 +0100 Subject: crypto/poly1305/asm: fix armv8 pointer authentication Link: https://github.com/openssl/openssl/commit/5795acffd8706e1cb584284ee5bb3a30986d0e75 This commit is already present in Impish onward. Only Focal needs the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960863/+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 1957104] Re: updating openssh-server fails, because port 22 is in use by systemd
sshd is started by systemd. No special configurations besides defaults by Ubuntu/xUbuntu. Only change in /etc/ssh/sshd_config: "PermitRootLogin prohibit-password" -> "PermitRootLogin yes" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1957104 Title: updating openssh-server fails, because port 22 is in use by systemd Status in openssh package in Ubuntu: Incomplete Bug description: openssh-server tries to restart itself, but openssh-server reports port 22 in use. This is true: systemd has taken port 22 to start sshd if one connects to port 22. two solutions: 1. dont start sshd after installing. configure it without starting it afterwards. 2. stop systemd listening on port 22 before starting sshd, then start sshd, terminate it after configuring, then start systemd listening on port 22 again. Second problem: starting ssh.service does not check if "/run/sshd" exists. This directory has to be created before sshd is started. Unclear if this is an error with sshd not creating this directory before dropping privileges or if this has to be done once while installing. IMHO the first is the case. Workaround: systemctl stop ssh.service systemctl disable ssh.service apt upgrade systemctl enable ssh.service killall sshd mkdir /run/sshd systemctl start ssh.service ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: openssh-server 1:8.4p1-6ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 11 19:11:47 2022 InstallationDate: Installed on 2021-08-18 (146 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1957104/+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
