[Touch-packages] [Bug 1932010] Re: [21.10 FEAT] zlib CRC32 optimization for s390x
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1932010 Title: [21.10 FEAT] zlib CRC32 optimization for s390x Status in Ubuntu on IBM z Systems: Fix Released Status in zlib package in Ubuntu: Fix Released Bug description: Use SIMD instructions to accelerate the zlib CRC32 implementation. Business value: Performance improvement in database area The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng: https://github.com/zlib-ng/zlib-ng/pull/912 The patch for zlib will be based on that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+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 1941938] [NEW] systemd trying to unmount non-existent file system
Public bug reported: This output is copied from here: https://github.com/systemd/systemd/issues/20516 because I have not been able to capture the error messages. However what I am seeing is identical. sd-umoun[2406]: Failed to unmount /oldroot: Device or resource busy sd-umoun[2407]: Failed to unmount /oldroot/dev/pts: Device or resource busy sd-umoun[2408]: Failed to unmount /oldroot/dev: Device or resource busy shutdown[1]: Failed to finalize file systems, ignoring This has happened consistently since I upgraded to Ubuntu 20.04 two weeks ago, and is really annoying. Is there an actual problem or is it just noise that can be safely ignored? The only other thing referencing oldroot in its config was snap, which I have completely uninstalled to isolate the problem. /lib/systemd/systemd-shutdown also contains this string: # strings systemd-shutdown |grep old /oldroot sigprocmask(SIG_BLOCK, , ) == 0 sigprocmask(SIG_SETMASK, , NULL) == 0 I have never had an /oldroot mount and there isn't one now. I gather it is something the upgrade process might create, or it could perhaps be something broken in finalrd. Bin Li, who posted the above error to the systemd bug portal, got short shrift there and was told to contact the distro. So I am, as my version of systemd is 245, same as his. This problem is 100% repeateable and I see it every time I shutdown or restart. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Aug 28 14:28:03 2021 InstallationDate: Installed on 2017-05-26 (1554 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:0708 Acer, Inc Integrated Camera Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 7: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 7: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 20EVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=3be3-50c9-41cc-94b5-eab06cff1d17 ro quiet splash SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-08-05 (22 days ago) dmi.bios.date: 12/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R00ET49W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR00ET49W(1.24):bd12/01/2016:svnLENOVO:pn20EVCTO1WW:pvrThinkPadE560:rvnLENOVO:rn20EVCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E560 dmi.product.name: 20EVCTO1WW dmi.product.sku: LENOVO_MT_20EV_BU_Think_FM_ThinkPad E560 dmi.product.version: ThinkPad E560 dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1941938 Title: systemd trying to unmount non-existent file system Status in systemd package in Ubuntu: New Bug description: This output is copied from here: https://github.com/systemd/systemd/issues/20516 because I have not been able to capture the error messages. However what I am seeing is identical. sd-umoun[2406]: Failed to unmount /oldroot: Device or resource busy sd-umoun[2407]: Failed to unmount /oldroot/dev/pts: Device or resource busy sd-umoun[2408]: Failed to unmount /oldroot/dev: Device or resource busy shutdown[1]: Failed to finalize file systems, ignoring This has happened consistently since I upgraded to Ubuntu 20.04 two weeks ago, and is really annoying. Is there an actual problem or is it just noise that can be safely ignored? The only other thing referencing oldroot in its config was snap, which I have completely uninstalled to isolate the problem. /lib/systemd/systemd-shutdown also contains this string: # strings systemd-shutdown |grep old /oldroot sigprocmask(SIG_BLOCK, , ) == 0 sigprocmask(SIG_SETMASK, , NULL) == 0 I have never had an /oldroot mount and there isn't one now. I gather it is something the upgrade process might create, or it could perhaps be something broken in finalrd. Bin Li, who posted the above error to the
[Touch-packages] [Bug 1869961] Re: systemd-networkd ignores RA preference and creates multipath routes anyway
[Expired for systemd (Ubuntu Bionic) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu Bionic) Status: Incomplete => Expired -- 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/1869961 Title: systemd-networkd ignores RA preference and creates multipath routes anyway Status in systemd package in Ubuntu: Expired Status in systemd source package in Bionic: Expired Bug description: When IPv6 ND RAs are sent from two different routers, one with Medium and one with High preferences, systemd-networkd will ignore the fact they have different preferences and create two multipath routes with the same weight. I ran a tcpdump of the RAs and confirmed that both have different preferences sent. i.e. nms-mon1:~$ ip -6 route 2a0d:1a40:7551:6010::/64 dev ens18 proto ra metric 100 pref medium fe80::/64 dev ens18 proto kernel metric 256 pref medium default proto ra metric 100 nexthop via fe80::c030:9cff:fe10:3492 dev ens18 weight 1 nexthop via fe80::215:5dff:fe83:c81c dev ens18 weight 1 Ubuntu version: Ubuntu 18.04.4 LTS systemd version: 237-3ubuntu10.39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869961/+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 1869961] Re: systemd-networkd ignores RA preference and creates multipath routes anyway
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1869961 Title: systemd-networkd ignores RA preference and creates multipath routes anyway Status in systemd package in Ubuntu: Expired Status in systemd source package in Bionic: Expired Bug description: When IPv6 ND RAs are sent from two different routers, one with Medium and one with High preferences, systemd-networkd will ignore the fact they have different preferences and create two multipath routes with the same weight. I ran a tcpdump of the RAs and confirmed that both have different preferences sent. i.e. nms-mon1:~$ ip -6 route 2a0d:1a40:7551:6010::/64 dev ens18 proto ra metric 100 pref medium fe80::/64 dev ens18 proto kernel metric 256 pref medium default proto ra metric 100 nexthop via fe80::c030:9cff:fe10:3492 dev ens18 weight 1 nexthop via fe80::215:5dff:fe83:c81c dev ens18 weight 1 Ubuntu version: Ubuntu 18.04.4 LTS systemd version: 237-3ubuntu10.39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869961/+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 1941933] Re: sticks the mouse pointer when using the touchpad
** Package changed: ubuntu => xorg (Ubuntu) -- 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/1941933 Title: sticks the mouse pointer when using the touchpad Status in xorg package in Ubuntu: New Bug description: Periodicaly sticks the mouse pointer when using the touchpad. Ubuntu 21.04 on laptop Honor BDR-WFH9HN. When I use a mouse - everything is fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 28 08:43:04 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: QUANTA Computer Inc Iris Xe Graphics [152d:127d] InstallationDate: Installed on 2021-08-08 (19 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:1040 Quanta Computer, Inc. ov9734_techfront_camera Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HONOR BOD-WXX9 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=2eeed0ae-6ec0-453a-95f4-20c82c0509ad ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2021 dmi.bios.release: 3.2 dmi.bios.vendor: HONOR dmi.bios.version: 3.02 dmi.board.asset.tag: N/A dmi.board.name: BOD-WXX9-PCB dmi.board.vendor: HONOR dmi.board.version: M1050 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HONOR dmi.chassis.version: M1050 dmi.ec.firmware.release: 3.2 dmi.modalias: dmi:bvnHONOR:bvr3.02:bd02/22/2021:br3.2:efr3.2:svnHONOR:pnBOD-WXX9:pvrM1050:rvnHONOR:rnBOD-WXX9-PCB:rvrM1050:cvnHONOR:ct10:cvrM1050: dmi.product.family: MagicBook dmi.product.name: BOD-WXX9 dmi.product.sku: C171 dmi.product.version: M1050 dmi.sys.vendor: HONOR version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1941933/+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 1941933] [NEW] sticks the mouse pointer when using the touchpad
You have been subscribed to a public bug: Periodicaly sticks the mouse pointer when using the touchpad. Ubuntu 21.04 on laptop Honor BDR-WFH9HN. When I use a mouse - everything is fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 28 08:43:04 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: QUANTA Computer Inc Iris Xe Graphics [152d:127d] InstallationDate: Installed on 2021-08-08 (19 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:1040 Quanta Computer, Inc. ov9734_techfront_camera Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HONOR BOD-WXX9 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=2eeed0ae-6ec0-453a-95f4-20c82c0509ad ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2021 dmi.bios.release: 3.2 dmi.bios.vendor: HONOR dmi.bios.version: 3.02 dmi.board.asset.tag: N/A dmi.board.name: BOD-WXX9-PCB dmi.board.vendor: HONOR dmi.board.version: M1050 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HONOR dmi.chassis.version: M1050 dmi.ec.firmware.release: 3.2 dmi.modalias: dmi:bvnHONOR:bvr3.02:bd02/22/2021:br3.2:efr3.2:svnHONOR:pnBOD-WXX9:pvrM1050:rvnHONOR:rnBOD-WXX9-PCB:rvrM1050:cvnHONOR:ct10:cvrM1050: dmi.product.family: MagicBook dmi.product.name: BOD-WXX9 dmi.product.sku: C171 dmi.product.version: M1050 dmi.sys.vendor: HONOR version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang freeze hirsute ubuntu wayland-session -- sticks the mouse pointer when using the touchpad https://bugs.launchpad.net/bugs/1941933 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1941932] [NEW] Reverting to nouveau driver leaves dead nvidia links causing suspend and shutdown to fail
Public bug reported: After having problems with the nvidia driver 470, I reverted to the nouveau driver, only to find that using suspend or shutdown in the XFCE4 menu just returned to the login page. However, I found that using the 'shutdown' or 'pm-suspend' commands worked OK. Checking syslog after a failed suspend lead me to /etc/systemd/system directory: lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-hibernate.service -> /dev/null lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-resume.service -> /dev/null lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-suspend.service -> /dev/null Also, there were two directories containing links to the above 'masked' services. Deleting those links restored suspend and shutdown functionality. drwxr-xr-x 2 root root 4096 Aug 26 18:14 systemd-hibernate.service.requires/ drwxr-xr-x 2 root root 4096 Aug 26 18:08 systemd-suspend.service.requires/ Obviously a problem in removing all the nvidia settings. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: 20.04.2 software-properties xubuntu ** Tags added: 20.04.2 software-properties xubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1941932 Title: Reverting to nouveau driver leaves dead nvidia links causing suspend and shutdown to fail Status in software-properties package in Ubuntu: New Bug description: After having problems with the nvidia driver 470, I reverted to the nouveau driver, only to find that using suspend or shutdown in the XFCE4 menu just returned to the login page. However, I found that using the 'shutdown' or 'pm-suspend' commands worked OK. Checking syslog after a failed suspend lead me to /etc/systemd/system directory: lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-hibernate.service -> /dev/null lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-resume.service -> /dev/null lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-suspend.service -> /dev/null Also, there were two directories containing links to the above 'masked' services. Deleting those links restored suspend and shutdown functionality. drwxr-xr-x 2 root root 4096 Aug 26 18:14 systemd-hibernate.service.requires/ drwxr-xr-x 2 root root 4096 Aug 26 18:08 systemd-suspend.service.requires/ Obviously a problem in removing all the nvidia settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1941932/+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 1932010] Re: [21.10 FEAT] zlib CRC32 optimization for s390x
This bug was fixed in the package zlib - 1:1.2.11.dfsg-2ubuntu7 --- zlib (1:1.2.11.dfsg-2ubuntu7) impish; urgency=medium [ Simon Chopin ] * d/rules: use configure options for dfltcc instead of hardcoding the CFLAGS * d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch ported from zlib-ng #912, adding a vectorized implementation of CRC32 on s390x architectures based on kernel code. LP: #1932010 [ Michael Hudson-Doyle ] * d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch: adjust to not make a PLT call in an ifunc on s390/s390x. -- Simon Chopin Thu, 12 Aug 2021 15:45:49 +1200 ** Changed in: zlib (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 zlib in Ubuntu. https://bugs.launchpad.net/bugs/1932010 Title: [21.10 FEAT] zlib CRC32 optimization for s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in zlib package in Ubuntu: Fix Released Bug description: Use SIMD instructions to accelerate the zlib CRC32 implementation. Business value: Performance improvement in database area The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng: https://github.com/zlib-ng/zlib-ng/pull/912 The patch for zlib will be based on that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921518] Re: OpenSSL "double free" error
@Vladimir This is an improvement. Previously we were getting: double free or corruption (out) But now it is: Bus error So some progress has been made. Can you please install debug symbols, and generate a complete traceback with debug symbols? or a core dump with debug symbols? (libcurl4-dbgsym curl-dbgsym libssl1.1-dbgsym) Also which libpka are you using? Were debug symbols compiled for it, and can you share it? Is it just the latest build from github? I have not previously seen Bus error when debugging this issue => on arm64 it is usually non-aligned memory access coming from somewhere. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1921518 Title: OpenSSL "double free" error Status in openssl package in Ubuntu: Incomplete Status in openssl source package in Focal: Incomplete Bug description: "double free" error is seen when using curl utility. Error is from libcrypto.so which is part of the OpenSSL package. This happens only when OpenSSL is configured to use a dynamic engine. OpenSSL version is 1.1.1f The issue is not encountered if http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead. OpenSSL can be configured to use a dynamic engine by editing the default openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu systems. On Bluefield systems, config diff to enable PKA dynamic engine, is as below: +openssl_conf = conf_section + # Extra OBJECT IDENTIFIER info: #oid_file = $ENV::HOME/.oid oid_section= new_oids +[ conf_section ] +engines = engine_section + +[ engine_section ] +bf = bf_section + +[ bf_section ] +engine_id=pka +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so +init=0 + engine_id above refers to dynamic engine name/identifier. dynamic_path points to the .so file for the dynamic engine. # curl -O https://tpo.pe/pathogen.vim double free or corruption (out) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928989] Re: expiring trust anchor compatibility issue
Attempted trusty backport, but failing at making it pass all the existing unit tests. Asking for help. At the moment it seems to me that trusty will remain unfixed. -- 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/1928989 Title: expiring trust anchor compatibility issue Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Trusty: New Status in openssl source package in Xenial: Fix Released Bug description: [Impact] * openssl fails to talk to letsencrypt website past September 2021, despite trusting the letsencrypt root certificate. [Test Plan] * Import staging cert equivalent to ISRG Root X1 https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem * Import expired staging cert equivalen tto DST Root CA X3 https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem * Test connectivity to the expired-root-ca test website https://expired-root-ca-test.germancoding.com setup: apt install openssl ca-certificates wget wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem cat letsencrypt-stg-root-x1.pem letsencrypt-stg-root-dst.pem >> ca.pem test case: openssl s_client -connect expired-root-ca-test.germancoding.com:443 -servername expired-root-ca-test.germancoding.com -verify 1 -verifyCAfile ca.pem bad result: connection failed verify depth is 1 CONNECTED(0003) depth=3 C = US, O = (STAGING) Internet Security Research Group, CN = (STAGING) Doctored Durian Root CA X3 verify error:num=10:certificate has expired notAfter=Jan 30 14:01:15 2021 GMT 140672978626200:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:s3_clnt.c:1264: good result: connection successful verify depth is 1 CONNECTED(0003) depth=2 C = US, O = (STAGING) Internet Security Research Group, CN = (STAGING) Pretend Pear X1 verify return:1 depth=1 C = US, O = (STAGING) Let's Encrypt, CN = (STAGING) Artificial Apricot R3 verify return:1 depth=0 CN = expired-root-ca-test.germancoding.com verify return:1 --- Certificate chain 0 s:/CN=expired-root-ca-test.germancoding.com i:/C=US/O=(STAGING) Let's Encrypt/CN=(STAGING) Artificial Apricot R3 1 s:/C=US/O=(STAGING) Let's Encrypt/CN=(STAGING) Artificial Apricot R3 i:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Pretend Pear X1 2 s:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Pretend Pear X1 i:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Doctored Durian Root CA X3 --- Server certificate -BEGIN CERTIFICATE- Connection should be successful and trusted with correctly working openssl s_client that can manage to ignore expired CA, and build a valid trust path using non-expired CA in the chain. [Testcase #2] $ sudo apt install ca-certificates wget faketime # Good connectivity $ wget -O /dev/null https://canonical.com --2021-07-13 11:54:20-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2b, 2001:67c:1360:8001::2c, 91.189.88.181, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2b|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 30933 (30K) [text/html] Saving to: '/dev/null' /dev/null 100%[>] 30.21K --.-KB/sin 0.001s 2021-07-13 11:54:20 (22.3 MB/s) - '/dev/null' saved [30933/30933] # Jump to october to experience failure $ faketime '2021-10-01' wget -O /dev/null https://canonical.com --2021-10-01 00:00:00-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2b, 2001:67c:1360:8001::2c, 91.189.88.181, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2b|:443... connected. ERROR: cannot verify canonical.com's certificate, issued by 'CN=R3,O=Let\'s Encrypt,C=US': Issued certificate has expired. To connect to canonical.com insecurely, use `--no-check-certificate'. # upgrade to new openssl, to see that connectivity is restored, even in october $ dpkg-query -W libssl1.0.0 libssl1.0.0:amd64 1.0.2g-1ubuntu4.20 $ faketime '2021-10-01' wget -O /dev/null https://canonical.com --2021-10-01 00:00:00-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2c, 2001:67c:1360:8001::2b, 91.189.88.180, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2c|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 30933 (30K) [text/html] Saving to: '/dev/null' /dev/null 100%[>] 30.21K --.-KB/sin 0.001s 2021-10-01 00:00:00 (21.9 MB/s) - '/dev/null' saved
[Touch-packages] [Bug 1939751] Re: openssh FTBFS with glibc >= 2.34
paelzer: I worked the merge under https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799 -- 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/1939751 Title: openssh FTBFS with glibc >= 2.34 Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: Fix Released Bug description: Due to an incompatible function prototype in openbsd-compat tests, this package FTBFS with glibc >= 2.34. There is an upstream patch already in place to address this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1939751/+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 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable
** Patch added: "Diff from 1:8.4p1-5ubuntu2" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+attachment/5521261/+files/lp1941799-ubuntu-ubuntu.debdiff ** Changed in: openssh (Ubuntu) Assignee: William Wilson (jawn-smith) => (unassigned) ** Changed in: openssh (Ubuntu) Status: In Progress => Confirmed -- 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/1941799 Title: Please merge openssh 1:8.4p1-6 from Debian unstable Status in openssh package in Ubuntu: Confirmed Bug description: This merge is needed because there are changes in Ubuntu that are not present in Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+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 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable
This diff from Debian still includes the seccomp fixes pulled in for glibc 2.33, as they are still relevant with glibc 2.34. These are in upstream openssh version 8.5, so when Debian gets to 8.5 we can sync and drop the diff. ** Patch added: "Diff from Debian" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+attachment/5521260/+files/lp1941799-debian-ubuntu.debdiff -- 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/1941799 Title: Please merge openssh 1:8.4p1-6 from Debian unstable Status in openssh package in Ubuntu: Confirmed Bug description: This merge is needed because there are changes in Ubuntu that are not present in Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+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 1940635] Re: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf
Beginner error on my part : there are debug logs in networkd, I didn't
even check them. As often, it turns out part of the answer lies in
there.
Here are the logs from 2.33:
autopkgtest systemd-networkd[942]: test_eth42: Gained IPv6LL
autopkgtest systemd-networkd[942]: test_eth42: link_check_ready(): DHCP4, DHCP6
or IPv4LL is enabled but no dynamic address is assigned yet.
autopkgtest systemd-networkd[942]: test_eth42: Discovering IPv6 routers
autopkgtest systemd-networkd[942]: NDISC: Started IPv6 Router Solicitation
client
autopkgtest systemd-networkd[942]: test_eth42: Remembering foreign route: dst:
fe80::dcad:beff:feef:4711/128, src: n/a, gw: n/a, prefsrc: n/a, scope: global,
table: local(255), proto: kernel, type: local, nexthop: 0
autopkgtest systemd-networkd[942]: NDISC: Sent Router Solicitation, next
solicitation in 4s
autopkgtest systemd-networkd[942]: rtnl: received non-static neighbor, ignoring.
autopkgtest systemd-networkd[942]: NDISC: Received Router Advertisement: flags
MANAGED preference medium lifetime 1800 sec
autopkgtest systemd-networkd[942]: NDISC: Invoking callback for 'router' event.
autopkgtest systemd-networkd[942]: DHCPv6 CLIENT: Started in Managed mode
autopkgtest systemd-networkd[942]: test_eth42: Acquiring DHCPv6 lease on NDisc
request
autopkgtest systemd-networkd[942]: test_eth42: Configuring route: dst: n/a,
src: n/a, gw: fe80::6051:85ff:fe70:4c03, prefsrc: n/a, scope: global, table:
main(254), proto: ra, type: unicast, nexthop: 0
And the equivalent in 2.34:
Aug 27 14:28:27 autopkgtest systemd-networkd[939]: test_eth42: Gained IPv6LL
Aug 27 14:28:27 autopkgtest systemd-networkd[939]: test_eth42:
link_check_ready(): DHCP4, DHCP6 or IPv4LL is enabled but no dynamic address is
assigned yet.
Aug 27 14:28:27 autopkgtest systemd-networkd[939]: test_eth42: Discovering IPv6
routers
Aug 27 14:28:27 autopkgtest systemd-networkd[939]: NDISC: Started IPv6 Router
Solicitation client
Aug 27 14:28:27 autopkgtest systemd-networkd[939]: test_eth42: Remembering
foreign route: dst: fe80::dcad:beff:feef:4711/128, src: n/a, gw: n/a, prefsrc:
n/a, scope: global, table: local(255), proto: kernel, type: local, nexthop: 0
Aug 27 14:28:29 autopkgtest systemd-networkd[939]: NDISC: Sent Router
Solicitation, next solicitation in 4s
Aug 27 14:28:29 autopkgtest systemd-networkd[939]: rtnl: received non-static
neighbor, ignoring.
Aug 27 14:28:29 autopkgtest systemd-networkd[939]: NDISC: Unexpected error
while reading from ICMPv6, ignoring: Exchange full
Looking through the code, one can trace the EXFULL error to this
function:
https://github.com/systemd/systemd/blob/main/src/basic/socket-
util.c#L1260
Which checks the msg flags and finds MSG_CTRUNC.
The thing is, the recvmsg in strace looks like this:
recvmsg(20, {msg_name={sa_family=AF_INET6, sin6_port=htons(0),
sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "fe80::6051:85ff:fe70:4c03",
_addr), sin6_scope_id=if_nametoindex("test_eth42")},
msg_namelen=128->28,
msg_iov=[{iov_base="\206\\276@\300\7\10\0\0\0\0\0\0\0\0\3\4@\200\377\377\377\377\377\377\377\377\0\0\0\0"...,
iov_len=88}], msg_iovlen=1, msg_control=[{cmsg_len=20,
cmsg_level=SOL_SOCKET, cmsg_type=SO_TIMESTAMP_OLD,
cmsg_data={tv_sec=1630055833, tv_usec=877754}}, {cmsg_len=16,
cmsg_level=SOL_IPV6, cmsg_type=0x34}], msg_controllen=36, msg_flags=0},
MSG_DONTWAIT) = 88
You'll note the msg_flags=0 at the end.
So... What the hell?
--
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/1940635
Title:
systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on
armhf
Status in glibc package in Ubuntu:
New
Status in netplan.io package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
systemd-networkd is failing to acquire a DCHP6 lease from dnsmasq on
armhf since glibc 2.34-0ubuntu1, failing systemd (tests-name=networkd-
test.py) and netplan.io (test-name=ethernets) tests on armhf.
Reproducer:
* Setup an armhf container, e.g. via:
autopkgtest systemd --test-name=networkd-test.py --shell -U
--apt-pocket=proposed=src:systemd,src:glibc -s -- lxd
autopkgtest/ubuntu/impish/armhf
* It will fail and drop you into the shell
* cd test/ && apt install python3-nose
* nosetests3 -v -s -m "test_.*_dhcp_ip6" networkd-test.py
This is unrelated to the recent dnsmasq changes (LP: #1894619), as that would
fail on all architectures, not just armhf.
It still passes inside an amd64 LXD container, so it is also not related to
armhf being tested inside a container. But it shows the difference between
armhf vs amd64 container, that on armhf we're missing the DHCPSOLICIT (and
therefore DHCPREPLY) messages, as can be seen from the dnsmasq log:
dnsmasq-dhcp[]: DHCPSOLICIT(router_eth42)
00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34
dnsmasq-dhcp[]: DHCPREPLY(router_eth42) 2600::1f
[Touch-packages] [Bug 1940818] Re: FFe diffutils 3.8
** Changed in: diffutils (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to diffutils in Ubuntu. https://bugs.launchpad.net/bugs/1940818 Title: FFe diffutils 3.8 Status in diffutils package in Ubuntu: Fix Committed Bug description: diffutils ftbfs with glibc 2.34 because of gnulib issues around SIGSTKSZ no longer being constant. diffutils 3.8 was released with an updated gnulib and builds fine with glibc 2.34 (https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?field.name_filter=diffutils) so I'd prefer to upload that rather than try to cherry pick the (large and not completely straightforward) gnulib fixes. The changelog for 3.8 indicates one obscure incompatible change: https://savannah.gnu.org/forum/forum.php?forum_id=10031 but as we're only just past FF, this seems like the best way forward to me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/diffutils/+bug/1940818/+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 1940999] Re: FTBFS against glibc 2.34
Ah, sorry. I saw "disable-regex" and thought that was a description of the resolution to the failing stack-overflow test! If updating grep to 3.7 is the easiest way to fix the problem then we can consider that. But since we're in Feature Freeze for Impish, this needs an assessment for feature changes. I see you posted the changes from 3.6 to 3.7. Does this mean you already made the assessment and if so, what was your conclusion? If feature changes exist then we'll need a freeze exception from the release team to proceed down this path. > With the new information above, I think the way I have structured it > matches the problem I'm trying to address - what do you think? It's certainly closer but I still think it's a little misleading. Maybe if we expanded the text it'd be closer. How about: * New upstream version 3.7 to fix FTBFS (LP: #1940999) * Add d/p/06-disable-test-regex.patch to disable failing test-regex But in any case, we can leave it until we've concluded the question on the best approach to take. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940999 Title: FTBFS against glibc 2.34 Status in grep package in Ubuntu: Confirmed Bug description: The package grep failed to build in a recent archive rebuild, see https://people.canonical.com/~doko/ftbfs-report/test- rebuild-20210805-impish-impish.html#foundations-bugs . The failure is in automated test, as follows: stack-overflow: failed test: grep never printed "stack overflow" FAIL: stack-overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
Relevant terminal output from crash: terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = gwenview path = /usr/bin pid = 108229 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Status in gwenview package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
CVE-2021-37620-3.patch is responsible. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-37620 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Status in gwenview package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887655] Re: unattended-upgrades triggers reboot despite configuration
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => 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/1887655
Title:
unattended-upgrades triggers reboot despite configuration
Status in unattended-upgrades package in Ubuntu:
Confirmed
Bug description:
I've been having problems with my Ubuntu machine suddenly rebooting
without any warning. To my knowledge Ubuntu Desktop is not supposed
to reboot without warning by default.
I believe this is being triggered by unattended-upgrades
unattended-upgrades 2.3 (amd64)
Ubuntu Desktop:
Description: Ubuntu 20.04 LTS
Release: 20.04
One pattern that emerges is that the reboot happens right after
unattended-upgrades completes successfully. There are multiple
examples in my /var/log/syslog, but all show "unattended-
upgrades.service: Succeeded." the same second everything begins to
shut down, with nothing for a minute or two prior. Example:
Jul 15 11:17:01 pc systemd[2065]: Starting Notification regarding a new
release of Ubuntu...
Jul 15 11:17:14 pc charon: 08[IKE] sending keep alive to 10.10.10.10[4500]
Jul 15 11:17:22 pc check-new-release-gtk[71843]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:30: PyGIWarning: Gtk was
imported without specifying a version first. Use gi.require_version('Gtk'
, '3.0') before import to ensure that the right version gets loaded.
Jul 15 11:17:22 pc check-new-release-gtk[71843]: from gi.repository import
Gtk
Jul 15 11:17:22 pc check-new-release-gtk[71843]: WARNING:root:timeout
reached, exiting
Jul 15 11:17:22 pc systemd[2065]: update-notifier-release.service: Succeeded.
Jul 15 11:17:22 pc systemd[2065]: Finished Notification regarding a new
release of Ubuntu.
Jul 15 11:17:48 pc mysql-workbench[33350]: gtk_tree_view_unref_tree_helper:
assertion 'node != NULL' failed
Jul 15 11:17:54 pc charon: 09[IKE] sending keep alive to 10.10.10.10[4500]
Jul 15 11:18:03 pc systemd[1]: unattended-upgrades.service: Succeeded.
Jul 15 11:18:03 pc systemd[1]: Stopping Session 3 of user philip.
Jul 15 11:18:03 pc systemd[1]: Removed slice
system-clean\x2dmount\x2dpoint.slice.
Jul 15 11:18:03 pc systemd[1]: Removed slice system-getty.slice.
Jul 15 11:18:03 pc systemd[1]: Removed slice system-modprobe.slice.
Jul 15 11:18:03 pc systemd[1]: Stopped target Block Device Preparation for
/dev/mapper/ubuntu.
Jul 15 11:18:03 pc systemd[2065]: Stopped target GNOME Wayland Session
(session: gnome).
From memory I've never edited the contents of /etc/apt/apt.conf.d/ and
the configuration for unattended upgrades claims to be default (NOT to
reboot):
$ grep -irnC4 reboot /etc/apt/apt.conf.d/
/etc/apt/apt.conf.d/50unattended-upgrades-88-// Do automatic removal of
unused packages after the upgrade
/etc/apt/apt.conf.d/50unattended-upgrades-89-// (equivalent to apt-get
autoremove)
/etc/apt/apt.conf.d/50unattended-upgrades-90-//Unattended-Upgrade::Remove-Unused-Dependencies
"false";
/etc/apt/apt.conf.d/50unattended-upgrades-91-
/etc/apt/apt.conf.d/50unattended-upgrades:92:// Automatically reboot *WITHOUT
CONFIRMATION* if
/etc/apt/apt.conf.d/50unattended-upgrades:93:// the file
/var/run/reboot-required is found after the upgrade
/etc/apt/apt.conf.d/50unattended-upgrades:94://Unattended-Upgrade::Automatic-Reboot
"false";
/etc/apt/apt.conf.d/50unattended-upgrades-95-
/etc/apt/apt.conf.d/50unattended-upgrades:96:// Automatically reboot even if
there are users currently logged in
/etc/apt/apt.conf.d/50unattended-upgrades:97:// when
Unattended-Upgrade::Automatic-Reboot is set to true
/etc/apt/apt.conf.d/50unattended-upgrades:98://Unattended-Upgrade::Automatic-Reboot-WithUsers
"true";
/etc/apt/apt.conf.d/50unattended-upgrades-99-
/etc/apt/apt.conf.d/50unattended-upgrades:100:// If automatic reboot is
enabled and needed, reboot at the specific
/etc/apt/apt.conf.d/50unattended-upgrades-101-// time instead of immediately
/etc/apt/apt.conf.d/50unattended-upgrades-102-// Default: "now"
/etc/apt/apt.conf.d/50unattended-upgrades:103://Unattended-Upgrade::Automatic-Reboot-Time
"02:00";
/etc/apt/apt.conf.d/50unattended-upgrades-104-
/etc/apt/apt.conf.d/50unattended-upgrades-105-// Use apt bandwidth limit
feature, this example limits the download
/etc/apt/apt.conf.d/50unattended-upgrades-106-// speed to 70kb/sec
/etc/apt/apt.conf.d/50unattended-upgrades-107-//Acquire::http::Dl-Limit "70";
journalctl -u unattended-upgrades
Jul 10 07:52:31 PC systemd[1]: Started Unattended Upgrades Shutdown.
Jul 14 10:03:03 PC systemd[1]: unattended-upgrades.service: Succeeded.
-- Reboot --
Jul 14 10:04:11 PC systemd[1]: Started Unattended Upgrades Shutdown.
Jul 15 11:18:03 PC systemd[1]:
[Touch-packages] [Bug 1933979] Re: [MIR] busybox package
Hello, Thank you for the review, comments, and suggestions, Seth. We'll investigate other options and see what can be worked out. Closing this until then. Thanks, again. ** Changed in: busybox (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1933979 Title: [MIR] busybox package Status in busybox package in Ubuntu: Invalid Bug description: [Availability] == src:busybox was introduced in Dapper (2006) and has been in main since then. src:busybox & bin:busybox-static are in main, to be more precise. And this request is to promote bin:busybox from src:busybox in main, too. It only depends on the libc6 package, which is in main already. The package builds on all the architectures; is Arch:any. [Rationale] === This package is to be included in our partner's cloud images, going back to Bionic. As cloud images are to ship only packages from main this request is to see that happen. [Security] == The binary doesn't install services / daemons (/etc/init.d/*, /etc/init/*, /lib/systemd/system/*). Just ships the "busybox" binary, its docs, and a man page. [Dependencies] == libc6, which is in main already. [Maintenance] = Server team. [Background information] Tiny utilities for small and embedded systems. --- Upstream: https://git.busybox.net/busybox/ Launchpad page: https://launchpad.net/ubuntu/+source/busybox Ubuntu bugs: https://bugs.launchpad.net/ubuntu/+source/busybox Debian Package Tracker: https://tracker.debian.org/pkg/busybox Debian bugs: https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=busybox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1933979/+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 1940635] Re: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf
** Attachment added: "networkd-glib-2.34-3.trace" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+attachment/5521156/+files/networkd-glib-2.34-3.trace ** Attachment removed: "networkd-glib-2.34.trace" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+attachment/5520981/+files/networkd-glib-2.34.trace ** Attachment removed: "networkd-glib-2.33.trace" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+attachment/5520980/+files/networkd-glib-2.33.trace -- 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/1940635 Title: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf Status in glibc package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: systemd-networkd is failing to acquire a DCHP6 lease from dnsmasq on armhf since glibc 2.34-0ubuntu1, failing systemd (tests-name=networkd- test.py) and netplan.io (test-name=ethernets) tests on armhf. Reproducer: * Setup an armhf container, e.g. via: autopkgtest systemd --test-name=networkd-test.py --shell -U --apt-pocket=proposed=src:systemd,src:glibc -s -- lxd autopkgtest/ubuntu/impish/armhf * It will fail and drop you into the shell * cd test/ && apt install python3-nose * nosetests3 -v -s -m "test_.*_dhcp_ip6" networkd-test.py This is unrelated to the recent dnsmasq changes (LP: #1894619), as that would fail on all architectures, not just armhf. It still passes inside an amd64 LXD container, so it is also not related to armhf being tested inside a container. But it shows the difference between armhf vs amd64 container, that on armhf we're missing the DHCPSOLICIT (and therefore DHCPREPLY) messages, as can be seen from the dnsmasq log: dnsmasq-dhcp[]: DHCPSOLICIT(router_eth42) 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 dnsmasq-dhcp[]: DHCPREPLY(router_eth42) 2600::1f 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 autopkgtest-lxd-rtypaf The issue is most probably the same that causes the currently failing netplan.io/ethernets autopkgtest on armhf, if tested against glibc 2.34-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+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 1940635] Re: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf
** Attachment added: "networkd-glib-2.33-3.trace" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+attachment/5521155/+files/networkd-glib-2.33-3.trace -- 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/1940635 Title: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf Status in glibc package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: systemd-networkd is failing to acquire a DCHP6 lease from dnsmasq on armhf since glibc 2.34-0ubuntu1, failing systemd (tests-name=networkd- test.py) and netplan.io (test-name=ethernets) tests on armhf. Reproducer: * Setup an armhf container, e.g. via: autopkgtest systemd --test-name=networkd-test.py --shell -U --apt-pocket=proposed=src:systemd,src:glibc -s -- lxd autopkgtest/ubuntu/impish/armhf * It will fail and drop you into the shell * cd test/ && apt install python3-nose * nosetests3 -v -s -m "test_.*_dhcp_ip6" networkd-test.py This is unrelated to the recent dnsmasq changes (LP: #1894619), as that would fail on all architectures, not just armhf. It still passes inside an amd64 LXD container, so it is also not related to armhf being tested inside a container. But it shows the difference between armhf vs amd64 container, that on armhf we're missing the DHCPSOLICIT (and therefore DHCPREPLY) messages, as can be seen from the dnsmasq log: dnsmasq-dhcp[]: DHCPSOLICIT(router_eth42) 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 dnsmasq-dhcp[]: DHCPREPLY(router_eth42) 2600::1f 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 autopkgtest-lxd-rtypaf The issue is most probably the same that causes the currently failing netplan.io/ethernets autopkgtest on armhf, if tested against glibc 2.34-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+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 1940635] Re: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf
Attached are new strace logs, I'll remove the previous files as there was something wrong with my test setup, so the captured trace isn't necessarily during the DHCPv6 tests. -- 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/1940635 Title: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf Status in glibc package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: systemd-networkd is failing to acquire a DCHP6 lease from dnsmasq on armhf since glibc 2.34-0ubuntu1, failing systemd (tests-name=networkd- test.py) and netplan.io (test-name=ethernets) tests on armhf. Reproducer: * Setup an armhf container, e.g. via: autopkgtest systemd --test-name=networkd-test.py --shell -U --apt-pocket=proposed=src:systemd,src:glibc -s -- lxd autopkgtest/ubuntu/impish/armhf * It will fail and drop you into the shell * cd test/ && apt install python3-nose * nosetests3 -v -s -m "test_.*_dhcp_ip6" networkd-test.py This is unrelated to the recent dnsmasq changes (LP: #1894619), as that would fail on all architectures, not just armhf. It still passes inside an amd64 LXD container, so it is also not related to armhf being tested inside a container. But it shows the difference between armhf vs amd64 container, that on armhf we're missing the DHCPSOLICIT (and therefore DHCPREPLY) messages, as can be seen from the dnsmasq log: dnsmasq-dhcp[]: DHCPSOLICIT(router_eth42) 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 dnsmasq-dhcp[]: DHCPREPLY(router_eth42) 2600::1f 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 autopkgtest-lxd-rtypaf The issue is most probably the same that causes the currently failing netplan.io/ethernets autopkgtest on armhf, if tested against glibc 2.34-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+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 1941813] Re: Several potential bugs of NULL Pointer Dereference
There's no test-program which demonstrates the problem, so there is no possibility to analyze these comments. By the way, Ubuntu provides by itself no solutions or improvements of any type for ncurses. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1941813 Title: Several potential bugs of NULL Pointer Dereference Status in ncurses package in Ubuntu: New Bug description: Ubuntu version: 18.04 ncurses version:6.1 Hello,I found some potential bugs in package ncurses-6.1 .Would you help me check whether the bugs mentioned below are true? Thank you very much for your patience. step 1 : In file ncurses-6.1/ncurses/tinfo/lib_data.c , function _nc_screen_of line 287 : Select the false branch at this point (win!=null is false) step 2 : In file ncurses-6.1/ncurses/tinfo/lib_data.c , function _nc_screen_of line 290 : null assigned to sp reaches here step 3 : In file ncurses-6.1/ncurses/tinfo/lib_data.c , function _nc_screen_of line 290 : Return sp to caller, which can be null step 4 : In file ncurses-6.1/ncurses/base/resizeterm.c , function adjust_window line 218 : Function _nc_screen_of executes and returns step 5 : In file ncurses-6.1/ncurses/base/resizeterm.c , function adjust_window line 218 : Load value from _nc_screen_of(win)->_topstolen step 1 : In file ncurses-6.1/ncurses/base/nc_panel.c , function _nc_panelhook line 42 : Select the false branch at this point (SP!=null is false) step 2 : In file ncurses-6.1/ncurses/base/nc_panel.c , function _nc_panelhook line 40 : Return null to caller step 3 : In file ncurses-6.1/panel/p_new.c , function root_panel line 56 : Function _nc_panelhook executes and stores the return value to ph (ph can be null) step 4 : In file ncurses-6.1/panel/p_new.c , function root_panel line 62 : Load value from ph->stdscr_pseudo_panel （_nc_stdscr_pseudo_panel is defined in panel.priv.h） step 1 : In file ncurses-6.1/ncurses/base/nc_panel.c , function _nc_panelhook line 42 : Select the false branch at this point (SP!=null is false) step 2 : In file ncurses-6.1/ncurses/base/nc_panel.c , function _nc_panelhook line 40 : Return null to caller step 3 : In file ncurses-6.1/panel/p_move.c , function move_panel line 51 : Function _nc_panelhook_sp executes and stores the return value to ph (ph can be null) in file panel.priv.h(#define GetHook(pan) SCREEN* sp = _nc_screen_of(pan->win); ) step 4 : In file ncurses-6.1/panel/p_move.c , function move_panel line 52 : Load value from ph->bottom_panel in file panel.priv.h(#define IS_LINKED(p) (((p)->above || (p)->below ||((p)==_nc_bottom_panel)) ? TRUE : FALSE)) step 1 : In file ncurses-6.1/ncurses/tinfo/lib_data.c , function _nc_screen_of line 287 : Select the false branch at this point (win!=null is false) step 2 : In file ncurses-6.1/ncurses/tinfo/lib_data.c , function _nc_screen_of line 290 : null assigned to sp reaches here step 3 : In file ncurses-6.1/ncurses/tinfo/lib_data.c , function _nc_screen_of line 290 : Return sp to caller, which can be null step 4 : In file ncurses-6.1/menu/m_sub.c , function set_menu_sub line 68 : Function _nc_screen_of executes and stores the return value to sp (sp can be null) step 5 : In file ncurses-6.1/menu/m_sub.c , function set_menu_sub line 70 : Load value from sp->_stdscr step 1 : In file ncurses-6.1/ncurses/base/nc_panel.c , function _nc_panelhook_sp line 42 : Select the false branch at this point (SP!=null is false) step 2 : In file ncurses-6.1/ncurses/base/nc_panel.c , function _nc_panelhook_sp line 40 : Return null to
