[Touch-packages] [Bug 1959179] [NEW] Video driver not working properly
Public bug reported: I cant change the brightness and after each start the screen has pathches. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 27 13:09:47 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2022-01-18 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120 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/4p, 2M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 4: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 4: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=1fb62a44-b30c-40e9-a7f2-507dd6b4d6f7 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 10.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1017 dmi.board.asset.tag: Default string dmi.board.name: PRIME H510M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1017:bd07/12/2021:br10.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH510M-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1959179 Title: Video driver not working properly Status in xorg package in Ubuntu: New Bug description: I cant change the brightness and after each start the screen has pathches. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 27 13:09:47 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2022-01-18 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120 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/4p, 2M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 4: Dev 3, If 1, Class=Human Interface
[Touch-packages] [Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
** Changed in: pyyaml (Ubuntu) Assignee: Rolf Leggewie (r0lf) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy Status in pyyaml package in Ubuntu: In Progress Status in six package in Ubuntu: New Bug description: The packages python3-yaml and python-is-python2 are not co-installable in jammy and I believe they should be. This currently prevents me from upgrading one of my machines from focal to jammy. Further analysis with the help of Stefano Rivera revealed that what- is-python no longer produces a python-is-python2 package and the changelog hints at that being intentional. Jammy still has a python2 package, though. python3-yaml in jammy breaks on python (<2.7.18). The python-is- python2 package in focal is version 2.7.17-4 and in impish it is 2.7.18-9 and thus will be forcefully removed when going to jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+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 1954649] Re: autopkgtest regressions with python3.10 as supported
** Changed in: vorta (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: New Status in pygobject package in Ubuntu: Fix Released Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: Fix Released Status in python-taskflow package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: Invalid Status in supysonic package in Ubuntu: Fix Released Status in vorta package in Ubuntu: Fix Released Status in ipywidgets package in Debian: New Status in pygobject package in Debian: Fix Released Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: Confirmed Status in python-hypothesis package in Debian: Fix Released Status in supysonic package in Debian: Fix Released Status in vorta package in Debian: Confirmed Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
** Tags removed: hirsute ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: Confirmed Status in synaptic source package in Xenial: Confirmed Status in update-notifier source package in Xenial: Fix Released Status in apt source package in Hirsute: Fix Released Status in aptitude source package in Hirsute: Fix Released Status in synaptic source package in Hirsute: Won't Fix Status in update-notifier source package in Hirsute: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is only a regression on a cosmetic level. Previous versions of apt did not have any sandboxing whatsoever, so this means apt reverted back to that old behavior. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1959173] [NEW] Vulnerability in af_packet handling
Public bug reported: CVE-2021-22600 A vulnerability, which was classified as critical, was found in Linux Kernel. Affected is the function packet_set_ring of the file net/packet/af_packet.c. The manipulation with an unknown input leads to a memory corruption vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The weakness was released 01/26/2022. The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2021-22600 since 01/05/2021. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is required for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 01/26/2022). Applying a patch is able to eliminate this problem. The fix is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=ec6af094ea28f0f2dda1a6a33b14cd57e36a9755 More information at: https://partnerissuetracker.corp.google.com/issues/215427453 ** Affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gke (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** No longer affects: klibc (Ubuntu) ** Also affects: linux-gke (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1959173 Title: Vulnerability in af_packet handling Status in linux-gke package in Ubuntu: New Status in linux-gke source package in Focal: New Bug description: CVE-2021-22600 A vulnerability, which was classified as critical, was found in Linux Kernel. Affected is the function packet_set_ring of the file net/packet/af_packet.c. The manipulation with an unknown input leads to a memory corruption vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The weakness was released 01/26/2022. The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2021-22600 since 01/05/2021. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is required for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 01/26/2022). Applying a patch is able to eliminate this problem. The fix is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=ec6af094ea28f0f2dda1a6a33b14cd57e36a9755 More information at: https://partnerissuetracker.corp.google.com/issues/215427453 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1959173/+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 1959079] Re: The UI crashes after suspend
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: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1959079 Title: The UI crashes after suspend Status in Ubuntu: Incomplete Bug description: All was working OK until I installed nvidia cuda drivers. Afterwards on lid open the system crashes. On lid close it exhausted the battery too fast. Now I have them deleted and have reverted to nouveau drivers but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Jan 26 10:37:23 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fa0] NVIDIA Corporation Device [10de:1f95] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fa0] MachineType: LENOVO 82D4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=1c371a7d-438b-4e79-8a3b-218cba05e945 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2020 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: EGCN25WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Creator 5 15IMH05 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrEGCN25WW:bd04/28/2020:br1.25:efr1.25:svnLENOVO:pn82D4:pvrIdeaPadCreator515IMH05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadCreator515IMH05:skuLENOVO_MT_82D4_BU_idea_FM_IdeaPadCreator515IMH05: dmi.product.family: IdeaPad Creator 5 15IMH05 dmi.product.name: 82D4 dmi.product.sku: LENOVO_MT_82D4_BU_idea_FM_IdeaPad Creator 5 15IMH05 dmi.product.version: IdeaPad Creator 5 15IMH05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1959079/+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 1958970] Re: [HP ENVY x360 Convertible 13-ar0xxx] Auto-rotation does not work anymore
*** This bug is a duplicate of bug 1806396 *** https://bugs.launchpad.net/bugs/1806396 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1806396, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - Auto-rotation does not work anymore + [HP ENVY x360 Convertible 13-ar0xxx] Auto-rotation does not work anymore ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1806396 lis3lv02d: unknown sensor type 0x0 in HP x360 machines -- 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/1958970 Title: [HP ENVY x360 Convertible 13-ar0xxx] Auto-rotation does not work anymore Status in linux package in Ubuntu: New Bug description: With my Radeon Vega graphics card auto-rotation of the screen used to work in 21.04 but does not work anymore in 21.10. Also Cinnamon (which I have uninstall now) shows an error, saying that hardware acceleration does not work. This bug relates to https://bugs.launchpad.net/ubuntu/+bug/1958852 I reinstalled my system but still auto-rotation does not work. dmesg shows [1.990767] lis3lv02d: unknown sensor type 0x0 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 25 10:46:21 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=4bbf320c-9d1b-4cb2-a03e-a7f170d88509 ro quiet nosplash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.release: 15.19 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 41.36 dmi.modalias: dmi:bvnAMI:bvrF.19:bd12/26/2019:br15.19:efr41.36:svnHP:pnHPENVYx360Convertible13-ar0xxx:pvr:rvnHP:rn85DE:rvr41.36:cvnHP:ct31:cvrChassisVersion:sku7BR48EA#ABD: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ar0xxx dmi.product.sku: 7BR48EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958970/+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 1787368] Re: Caja does not show previews of text files on Bionic and newer versions
This functionality was dropped from GTK and while there was some upstream effort to re-implement this capability no forward progress has been made in 3 years. Closing this. ** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Invalid ** Changed in: caja (Ubuntu) Status: Confirmed => Won't Fix ** No longer affects: mate-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1787368 Title: Caja does not show previews of text files on Bionic and newer versions Status in caja package in Ubuntu: Won't Fix Status in gtk+3.0 package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu MATE 18.04 LTS (or upgrade from 16.04 LTS) 2. Create text file somewhere (in home folder for example) with `echo text > ~/file.txt`. 3. Open Caja in home folder Expected results: * Caja shows preview (the contents) of `file.txt` in Icon view. Actual results: * Caja does not show preview of `file.txt`. Notes: 1. all settings in Preview tab are set to *Local Only* 2. this happens on clean user profile and/or after `dconf reset -f /` and `gsettings reset-recursively org.mate.caja` 3. Problem first seen on AskUbuntu ( https://askubuntu.com/q/1065825/66509 ). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: caja 1.20.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Thu Aug 16 12:36:57 2018 InstallationDate: Installed on 2018-04-26 (111 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: caja UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1787368/+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 1854383] Re: Extra window decorations are created on windows with client-side decorations.
Does this happen with Yaru MATE on Jammy daily? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1854383 Title: Extra window decorations are created on windows with client-side decorations. Status in Ubuntu MATE: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Bug description: Steps to reproduce after a minimal/full install of Ubuntu MATE: 1. Start up a Gtk3 application with a header bar (tested with Gnome Software) or a browser (such as Firefox) without using a standard window title bar that saves the position and size of the window before it was closed. 2. Maximize the application window, then close it without changing the window size 3. Relaunch the application and resize/unmaximize it After this, dummy window decorations will be created around the window. This issue has been tested on a Dell XPS 9570 and using Gnome Boxes 3.34. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1854383/+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 1958642] Re: New 2.37.50.20220119-0ubuntu1 Produces RWE load header on s390x
This bug was fixed in the package binutils - 2.37.90.20220126-0ubuntu1 --- binutils (2.37.90.20220126-0ubuntu1) jammy; urgency=medium * New upstream snapshot, taken from the 2.38 release branch. - Fix PR ld/28743, PR ld/28819. Closes: #1004272. LP: #1958642. -- Matthias Klose Sun, 23 Jan 2022 19:03:09 +0100 ** Changed in: binutils (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1958642 Title: New 2.37.50.20220119-0ubuntu1 Produces RWE load header on s390x Status in binutils package in Ubuntu: Fix Released Status in binutils package in Debian: Confirmed Bug description: Building libxcrypt with the new binutils upload 2.37.50.20220119-0ubuntu1 in proposed produces binaries with one RWE LOAD header instead of two LOAD headers (one RE, one RW); causing it to fail to load in services that use MemoryDenyWriteExecute=yes, thus breaking a ton of systemd services. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1958642/+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 1958904] Re: autopkgtest is failing on jammy with "no space left on device"
uploaded into unapproved queue -- 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/1958904 Title: autopkgtest is failing on jammy with "no space left on device" Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Impish: In Progress Bug description: [Impact] In debian/tests/prep-image we create an image file of 1GB, but recent jammy/focal cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... Example of a test failure: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. [Test Plan] Run autotestpkg tests from initramfs-tools package. The "net" test is the one that depends on the image created by 'prep-image'. The testcase should complete successfully without the temporary image running out of space. [Where problems could occur] The creation of a larger image for the tests could fail if the filesystem of the test system is low on disk space. However, as mentioned before, as the image file is created using 'truncate', only the necessary space needed to uncompress the cloudimg will be used on the filesystem. Apart from that, we assume that 2GB of free space should be available on every test system used for Ubuntu autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+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 1958904] Re: autopkgtest is failing on jammy with "no space left on device"
@brian-murray Unfortunately, it would mean that kernel-teams adt-matrix would still need to be hinted, as it does strict adt test runs against each kernel flavour, against packages in updates only, and enforces that every kernel flavour is tested. However, I also think that this adt test may not be relevant, given that the kernel used in the qemu image is not actually the requested kernel flavour under test from adt-matrix point of view. I will sponsor these uploads, but i guess kernel team will still need to apply adt-matrix hints to make things nice. -- 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/1958904 Title: autopkgtest is failing on jammy with "no space left on device" Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Impish: In Progress Bug description: [Impact] In debian/tests/prep-image we create an image file of 1GB, but recent jammy/focal cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... Example of a test failure: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. [Test Plan] Run autotestpkg tests from initramfs-tools package. The "net" test is the one that depends on the image created by 'prep-image'. The testcase should complete successfully without the temporary image running out of space. [Where problems could occur] The creation of a larger image for the tests could fail if the filesystem of the test system is low on disk space. However, as mentioned before, as the image file is created using 'truncate', only the necessary space needed to uncompress the cloudimg will be used on the filesystem. Apart from that, we assume that 2GB of free space should be available on every test system used for Ubuntu autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+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 1958904] Re: autopkgtest is failing on jammy with "no space left on device"
Given that this is just a test fix I've tagged the bug block-proposed so that if the new package only contains this change it won't be pushed to -updates. ** Tags added: block-proposed-focal block-proposed-impish -- 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/1958904 Title: autopkgtest is failing on jammy with "no space left on device" Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Impish: In Progress Bug description: [Impact] In debian/tests/prep-image we create an image file of 1GB, but recent jammy/focal cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... Example of a test failure: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. [Test Plan] Run autotestpkg tests from initramfs-tools package. The "net" test is the one that depends on the image created by 'prep-image'. The testcase should complete successfully without the temporary image running out of space. [Where problems could occur] The creation of a larger image for the tests could fail if the filesystem of the test system is low on disk space. However, as mentioned before, as the image file is created using 'truncate', only the necessary space needed to uncompress the cloudimg will be used on the filesystem. Apart from that, we assume that 2GB of free space should be available on every test system used for Ubuntu autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+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 1856480] Re: "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu
** Information type changed from Public to Private ** Attachment removed: "Image of printing error" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+attachment/5312547/+files/Screenshot%20from%202019-12-15%2015-07-59.png ** Attachment removed: "CupsErrorLog.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+attachment/5312548/+files/CupsErrorLog.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+attachment/5312549/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+attachment/5312550/+files/Dependencies.txt ** Attachment removed: "KernLog.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+attachment/5312551/+files/KernLog.txt ** Attachment removed: "CupsErrorLog.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+attachment/5313397/+files/CupsErrorLog.txt ** Information type changed from Private to Public ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1856480 Title: "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu Status in cups package in Ubuntu: New Bug description: Whenever I attempt to print a document to a printer over the network, Ubuntu finds the printer and acts as if it is configured until I actually send a print job. When I do this, I get a message that says "Printing" in LibreOffice, but then nothing happens because the printers are not configured according to Ubuntu. I expected the document I sent over the network to print without issue. However, I am unable to on ubuntu because it is apparently not configured. Description: Ubuntu 19.10 Release: 19.10 cups: Installed: 2.2.12-2ubuntu1 Candidate: 2.2.12-2ubuntu1 Version table: *** 2.2.12-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Dec 15 15:01:50 2019 InstallationDate: Installed on 2019-11-20 (25 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for Officejet_Pro_8600_AB0C33_: ipp://HP843497AB0C33.local:631/ipp/printer Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 Papersize: letter ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-20 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for Officejet_Pro_8600_AB0C33_: ipp://HP843497AB0C33.local:631/ipp/printer Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 Package: cups 2.2.12-2ubuntu1 PackageArchitecture: amd64 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash
[Touch-packages] [Bug 1934552] Re: Graphical glitches on Radeon RX 6700 XT
The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release. ** Changed in: mesa (Ubuntu Hirsute) Status: Incomplete => Won't Fix -- 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/1934552 Title: Graphical glitches on Radeon RX 6700 XT Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Hirsute: Won't Fix Bug description: Ubuntu 21.04, mesa 21.0.1-2 amd64 Upstream MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9568 Graphical glitches can be seen occasionally on screen with the RX 6700 XT graphics card. This is fixed upstream with the above merged MR, so please backport it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934552/+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 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange
The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release. ** Changed in: openssh (Ubuntu Hirsute) Status: Triaged => Won't Fix -- 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/1938144 Title: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Status in openssh source package in Focal: Triaged Status in openssh source package in Hirsute: Won't Fix Bug description: I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and server) with the option "GSSAPIKeyExchange=yes", and this causes the connection to fail. The server has GSSAPI (Kerberos authentication) enabled, but is is only used for non-root users (root uses SSH keys). Client command: ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex root@server -v -p -o GSSAPIKeyExchange=yes Client log: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020 debug1: Reading configuration data /home/user/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: Connecting to compute-test [130.75.80.46] port . debug1: Connection established. debug1: identity file /home/rother/.ssh/id_rsa type 0 debug1: identity file /home/rother/.ssh/id_rsa-cert type -1 debug1: identity file /home/rother/.ssh/id_dsa type -1 debug1: identity file /home/rother/.ssh/id_dsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa type -1 debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519 type -1 debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_xmss type -1 debug1: identity file /home/rother/.ssh/id_xmss-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400 debug1: Authenticating to server: as 'root' debug1: Offering GSSAPI proposal: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q== debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g== debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: Doing group exchange debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Received GSSAPI_COMPLETE debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Rekey has happened - updating saved versions debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent debug1: Will attempt key: /home/user/.ssh/id_dsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk debug1: Will attempt key: /home/user/.ssh/id_ed25519 debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk debug1: Will attempt key: /home/user/.ssh/id_xmss debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Next authentication method: gssapi-with-mic debug1: Delegating credentials debug1: Delegating credentials debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Next authentication method: gssapi-keyex Connection closed by 1.2.3.4 port Server log: debug1: sshd version OpenSSH_8.2, OpenSSL 1.1.1f 31 Mar 2020 debug1:
[Touch-packages] [Bug 1938058] Re: systemd-time-wait-sync.service should be part of systemd-timesyncd package
The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release. ** Changed in: systemd (Ubuntu Hirsute) Status: New => Won't Fix -- 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/1938058 Title: systemd-time-wait-sync.service should be part of systemd-timesyncd package Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: New Bug description: [impact] systemd-time-wait-sync service never completes when systemd-timesyncd package is not installed [test case] remove the systemd-timesyncd package and enable the systemd-time-wait- sync service, and reboot. Check status of the service to see it's stuck in 'activating' state, e.g.: ubuntu@lp1937238-f:~$ sudo systemctl status systemd-time-wait-sync.service ● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; enabled; vendor preset: enabled) Active: activating (start) since Fri 2021-07-23 15:32:12 UTC; 19s ago [regression potential] TBD [scope] this is needed in f and later the systemd-timesyncd package was split out from the main systemd package starting in focal, so this problem exists in f and later the service doesn't exist in b, so this is not needed there [other info] originally noticed in bug 1937238, but create this new bug in case that bug was actually a separate problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938058/+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 1522675] Re: Warning messages about unsandboxed downloads
The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release. ** Changed in: synaptic (Ubuntu Hirsute) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: Confirmed Status in synaptic source package in Xenial: Confirmed Status in update-notifier source package in Xenial: Fix Released Status in apt source package in Hirsute: Fix Released Status in aptitude source package in Hirsute: Fix Released Status in synaptic source package in Hirsute: Won't Fix Status in update-notifier source package in Hirsute: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is only a regression on a cosmetic level. Previous versions of apt did not have any sandboxing whatsoever, so this means apt reverted back to that old behavior. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release. ** Changed in: dbus (Ubuntu Hirsute) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Incomplete Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19
[Touch-packages] [Bug 1881207] Re: systemd-networkd brings eno1 up and down repeatedly
The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release. ** Changed in: systemd (Ubuntu Hirsute) Status: In Progress => Won't Fix -- 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/1881207 Title: systemd-networkd brings eno1 up and down repeatedly Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: Won't Fix Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: Won't Fix Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: In Progress Bug description: [impact] a system using dhcp for an interface where (1) the interface 'resets' itself during mtu setting (meaning it briefly drops carrier during mtu change), and (2) the dhcp server provides a non-standard (i.e. other than 1500) mtu, will continually loop changing mtu between 1500 and the dhcp-privded mtu. [test case] The e1000e nic is one such nic where the driver briefly drops carrier when changing the mtu, so this can be reproduced by creating a VM and setting the interface to the 'e1000e' emulated hardware. Then configure a dhcp server to provide dhcp service to the VM, and set the mtu to e.g. 9000 (anything other than the default 1500). When the VM runs dhcp, it will loop with: Feb 22 15:18:58 lp1881207-upstream systemd-networkd[992]: ens8: Gained carrier Feb 22 15:18:58 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv4 address 1.2.3.133/24 via 1.2.3.1 Feb 22 15:18:59 lp1881207-upstream systemd-networkd[992]: ens8: Lost carrier Feb 22 15:18:59 lp1881207-upstream systemd-networkd[992]: ens8: DHCP lease lost Feb 22 15:18:59 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv6 lease lost Feb 22 15:19:01 lp1881207-upstream systemd-networkd[992]: ens8: Gained carrier Feb 22 15:19:01 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv4 address 1.2.3.133/24 via 1.2.3.1 Feb 22 15:19:02 lp1881207-upstream systemd-networkd[992]: ens8: Lost carrier Feb 22 15:19:02 lp1881207-upstream systemd-networkd[992]: ens8: DHCP lease lost Feb 22 15:19:02 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv6 lease lost Feb 22 15:19:04 lp1881207-upstream systemd-networkd[992]: ens8: Gained carrier Feb 22 15:19:04 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv4 address 1.2.3.133/24 via 1.2.3.1 Feb 22 15:19:05 lp1881207-upstream systemd-networkd[992]: ens8: Lost carrier Feb 22 15:19:05 lp1881207-upstream systemd-networkd[992]: ens8: DHCP lease lost Feb 22 15:19:05 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv6 lease lost [regression potential] any regression would likely involve an issue with dhcpv4 service; possibly not setting the mtu correctly, or possibly not completing dhcpv4 at all. [scope] this is not fixed upstream yet, so (once fixed upstream) it will be needed for b/f/g/h [original description] Running on a NUC (BOXNUC8i7BEH3). After updating the `systemd` package past `237-3ubuntu10.32`, I see the onboard NIC link being taken down / up repeatedly, as shown below (dates are from my original notes, but the issue remains the same today). The NIC fails to remain up, and all networking is out of action. Running `systemctl stop systemd-netword` stops this and leaves the NIC in an unknown state. Subsequently running `ifconfig eno1 up && dhclient eno1` allows networking to continue basic operation, albeit without systemd's oversight. My original solution was to downgrade both the `libsystemd0` and `systemd` packages to `237-3ubuntu10.28`. After attempting an `apt update && apt upgrade` again today, exactly the same thing is happening with `237-3ubuntu10.41`. Good versions: - 237-3ubuntu10.28 - 237-3ubuntu10.32 (currently in use, and held) Bad versions: - 237-3ubuntu10.33 - 237-3ubuntu10.38 - 237-3ubuntu10.41 dmesg: [ 360.711367] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 360.714370] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000 [ 360.726189] e1000e :00:1f.6: Interrupt Throttle Rate off [ 361.733073] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500 [ 361.744146] e1000e :00:1f.6: Interrupt Throttle Rate on [ 366.760198] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 366.763375] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000 [ 366.776060] e1000e :00:1f.6: Interrupt Throttle Rate off [ 367.781718] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500 [ 367.792796] e1000e :00:1f.6: Interrupt Throttle Rate on [ 372.808660] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[Touch-packages] [Bug 1917677] Re: ubuntu: ucf tracking of valid known md5sums should be limited to only those md5sums that affect a given distro release
The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release. ** Changed in: unattended-upgrades (Ubuntu Hirsute) Status: New => Won't Fix -- 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/1917677 Title: ubuntu: ucf tracking of valid known md5sums should be limited to only those md5sums that affect a given distro release Status in unattended-upgrades package in Ubuntu: New Status in unattended-upgrades source package in Bionic: New Status in unattended-upgrades source package in Focal: New Status in unattended-upgrades source package in Groovy: New Status in unattended-upgrades source package in Hirsute: Won't Fix Bug description: Currently the project tracks all valid md5sums of permutations of 50unattended-upgrades.conf in a single md5sum file that contains every md5sum of every historic version of all unique distros: 50unattended-upgrades.Debian 50unattended-upgrades.Devuan 50unattended-upgrades.Raspbian 50unattended-upgrades.Ubuntu Ultimately ucf for a given packaging release should only track the applicable md5sums which are expected to be seen on that particular distribution and release. For example: On Ubuntu Bionic: valid md5sums should be limited to the md5sum of the most recent Ubuntu Xenial 50unattended-upgrades.conf and the md5sums of previous Ubuntu Bionic releases to allow Xenial->Bionic and Bionic->Bionic upgrades without prompt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1917677/+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 1923485] Re: unable to reconize Asgard NVME with short serial
The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release. ** Changed in: systemd (Ubuntu Hirsute) Status: New => Won't Fix -- 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/1923485 Title: unable to reconize Asgard NVME with short serial Status in curtin: New Status in systemd: Unknown Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Status in systemd source package in Groovy: Won't Fix Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: New Bug description: check this: https://discourse.maas.io/t/unable-to-deploy-valueerror-failed-to-find-storage-volume-id-nvme0n1/4442/4 Maybe the line os.listdir should be changed with os.walk to discover all child directories? Or maybe this is just a BUG of MAAS? To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1923485/+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 1928733] Re: Starting systemd Network Service fails with "Invalid argument"
The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release. ** Changed in: systemd (Ubuntu Hirsute) Status: Triaged => Won't Fix -- 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/1928733 Title: Starting systemd Network Service fails with "Invalid argument" Status in systemd: Unknown Status in systemd package in Ubuntu: Triaged Status in systemd source package in Bionic: Triaged Status in systemd source package in Focal: Triaged Status in systemd source package in Groovy: Won't Fix Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: Triaged Bug description: This server has a new install of Ubuntu 18.04 server. Sometimes (around 50% of the time) when it boots systemd-networkd.service initially fails to start with an error as below. It then tries again and succeeds, however other services which depend on systemd-networkd have already failed on the dependency by then. From the output of "journalctl -u systemd-networkd": -- Reboot -- May 17 19:44:28 server1 systemd[1]: Starting Network Service... May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed to set up mount namespacing: Invalid argument May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-networkd: Invalid argument May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=226/NAMESPACE May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. May 17 19:44:30 server1 systemd[1]: Failed to start Network Service. May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1. May 17 19:44:30 server1 systemd[1]: Stopped Network Service. May 17 19:44:30 server1 systemd[1]: Starting Network Service... May 17 19:44:30 server1 systemd-networkd[2321]: Enumeration completed May 17 19:44:30 server1 systemd[1]: Started Network Service. May 17 19:44:30 server1 systemd-networkd[2321]: eno2: IPv6 successfully enabled May 17 19:44:30 server1 systemd-networkd[2321]: eno1: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: eno1: IPv6 successfully enabled May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not managed by us May 17 19:44:31 server1 systemd-networkd[2321]: eno2: Link UP May 17 19:44:31 server1 systemd-networkd[2321]: eno1: Link UP May 17 19:44:34 server1 systemd-networkd[2321]: eno2: Gained carrier May 17 19:44:34 server1 systemd-networkd[2321]: eno1: Gained carrier May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Gained IPv6LL May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Configured May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Gained IPv6LL May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Configured ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.46 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Mon May 17 19:53:11 2021 InstallationDate: Installed on 2021-03-18 (60 days ago) InstallationMedia: Ubuntu-Server 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 004: ID 1604:10c0 Tascam Bus 001 Device 003: ID 1604:10c0 Tascam Bus 001 Device 002: ID 1604:10c0 Tascam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic root=/dev/mapper/vg1-lv_root ro processor.max_cstate=1 intel_idle.max_cstate=0 transparent_hugepage=never SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.3 dmi.board.name: 04JN2K dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.3:bd09/23/2020:svnDellInc.:pnPowerEdgeR440:pvr:rvnDellInc.:rn04JN2K:rvrA06:cvnDellInc.:ct23:cvr:
[Touch-packages] [Bug 1952107] Re: Google Contacts API Deprecated
I upgrade to 3.36.5-0ubuntu in focal: Contacts in evolution are EMPTY. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1958806] Re: Fails to include libgcc, resulting in cryptsetup failures
*** This bug is a duplicate of bug 1958594 *** https://bugs.launchpad.net/bugs/1958594 ** This bug has been marked a duplicate of bug 1958594 Boot error: libgcc_s.so.1 must be installed for pthread_exit to work -- 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/1958806 Title: Fails to include libgcc, resulting in cryptsetup failures Status in initramfs-tools package in Ubuntu: New Bug description: I recently rebooted my laptop, and couldn't unlock my (cryptsetup- managed) root filesystem; after entering my passphrase, the plymouth prompt would always say “unable to unlock /dev/nvme0n1p3_crypt”. Dropping to text mode, I can see that cryptsetup is failing with a message like: "libgcc_s: missing library, needed for pthread_exit”. Indeed, in the recovery console cryptsetup will immediately crash with that message. I note that initramfs-tools already has some logic for detecting when libgcc_s is needed but isn't in DT_NEEDED, but this seems to have gone out of date. Adding an initramfs hook to manually add libgcc_s to the initramfs results in a bootable system again. I don't reboot this laptop often, so I unfortunately can't narrow down *when* this started failing better than “sometime in the last 2 months”. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu10 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 12:08:34 2022 InstallationDate: Installed on 2021-06-26 (211 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to jammy on 2021-10-28 (87 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958806/+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 1959126] [NEW] Consider update to 3.68.2
Public bug reported: Debian is shipping nss 3.73.1, but that is not an ESR release. Ubuntu is on 3.68, which is ESR, but two releases behind: upstream has 3.68.2. Here are upstream's release notes: 3.68.1: https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/jFIuiWbCphk Changes: - Bug 1735028 - check for missing signedData field. - Bug 1737470 - Ensure DER encoded signatures are within size limits. 3.68.2: https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/uGRwqw6Ove8 Change: - Bug 966856 - Add SHA-2 support to mozilla::pkix's OCSP implementation Our 3.68 package has a patch for CVE-2021-43527. It's unclear if any of the above changes is that CVE. The most promising one was bug 1737470, but the bug is private. The request here is to investigate if our patched 3.68 has one or more of the fixes in the above point releases, and if it would be worth it to go to 3.68.2. I think we should not go to 3.7x. Ubuntu has been on 3.68 since impish. ** Affects: nss (Ubuntu) Importance: Undecided Status: New ** Tags: server-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1959126 Title: Consider update to 3.68.2 Status in nss package in Ubuntu: New Bug description: Debian is shipping nss 3.73.1, but that is not an ESR release. Ubuntu is on 3.68, which is ESR, but two releases behind: upstream has 3.68.2. Here are upstream's release notes: 3.68.1: https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/jFIuiWbCphk Changes: - Bug 1735028 - check for missing signedData field. - Bug 1737470 - Ensure DER encoded signatures are within size limits. 3.68.2: https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/uGRwqw6Ove8 Change: - Bug 966856 - Add SHA-2 support to mozilla::pkix's OCSP implementation Our 3.68 package has a patch for CVE-2021-43527. It's unclear if any of the above changes is that CVE. The most promising one was bug 1737470, but the bug is private. The request here is to investigate if our patched 3.68 has one or more of the fixes in the above point releases, and if it would be worth it to go to 3.68.2. I think we should not go to 3.7x. Ubuntu has been on 3.68 since impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1959126/+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 1958904] Re: autopkgtest is failing on jammy with "no space left on device"
debdiff for Focal (0.136ubuntu6.7). Compile-tested in my ppa and locally tested with autopkgtest. ** Patch added: "debdiff for Focal (0.136ubuntu6.7)" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+attachment/5557652/+files/initramfs-tools_0.136ubuntu6.7.debdiff ** Changed in: initramfs-tools (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: initramfs-tools (Ubuntu Impish) Status: Triaged => In Progress -- 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/1958904 Title: autopkgtest is failing on jammy with "no space left on device" Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Impish: In Progress Bug description: [Impact] In debian/tests/prep-image we create an image file of 1GB, but recent jammy/focal cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... Example of a test failure: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. [Test Plan] Run autotestpkg tests from initramfs-tools package. The "net" test is the one that depends on the image created by 'prep-image'. The testcase should complete successfully without the temporary image running out of space. [Where problems could occur] The creation of a larger image for the tests could fail if the filesystem of the test system is low on disk space. However, as mentioned before, as the image file is created using 'truncate', only the necessary space needed to uncompress the cloudimg will be used on the filesystem. Apart from that, we assume that 2GB of free space should be available on every test system used for Ubuntu autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+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 1958904] Re: autopkgtest is failing on jammy with "no space left on device"
debdiff for Impish (0.140ubuntu6.1). Compile-tested in my ppa and locally tested with autopkgtest. ** Description changed: - In debian/tests/prep-image we create an image file of 1GB, but recent - jammy cloud images are (barely) bigger than that, for example the - current one uncompressed is 1001MB... + [Impact] + In debian/tests/prep-image we create an image file of 1GB, but recent jammy cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. + + [Test Plan] + Run autotestpkg tests from initramfs-tools package. The "net" test is the one that depends on the image created by 'prep-image'. The testcase should complete successfully without the temporary image running out of space. + + [Where problems could occur] + The creation of a larger image for the tests could fail if the filesystem of the test system is low on disk space. However, as mentioned before, as the image file is created using 'truncate', only the necessary space needed to uncompress the cloudimg will be used on the filesystem. Apart from that, we assume that 2GB of free space should be available on every test system used for Ubuntu autopkgtest. ** Description changed: [Impact] - In debian/tests/prep-image we create an image file of 1GB, but recent jammy cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... + In debian/tests/prep-image we create an image file of 1GB, but recent jammy/focal cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... + + Example of a test failure: + https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. [Test Plan] Run autotestpkg tests from initramfs-tools package. The "net" test is the one that depends on the image created by 'prep-image'. The testcase should complete successfully without the temporary image running out of space. [Where problems could occur] The creation of a larger image for the tests could fail if the filesystem of the test system is low on disk space. However, as mentioned before, as the image file is created using 'truncate', only the necessary space needed to uncompress the cloudimg will be used on the filesystem. Apart from that, we assume that 2GB of free space should be available on every test system used for Ubuntu autopkgtest. ** Patch added: "debdiff for Impish (0.140ubuntu6.1)" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+attachment/5557651/+files/initramfs-tools_0.140ubuntu6.1.debdiff -- 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/1958904 Title: autopkgtest is failing on jammy with "no space left on device" Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Impish: In Progress Bug description: [Impact] In debian/tests/prep-image we create an image file of 1GB, but recent jammy/focal cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... Example of a test failure: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. [Test Plan] Run autotestpkg tests from initramfs-tools package. The "net" test is the one that depends on the image created by 'prep-image'. The testcase should complete successfully without the temporary image running out of space. [Where problems could occur] The creation of a larger image for the tests could fail if the filesystem of the test system is low on disk space. However, as mentioned before, as the image file is created using 'truncate', only the necessary space needed to uncompress the cloudimg will be used on the filesystem. Apart from that, we assume that 2GB of free space should be available on every test system used for Ubuntu autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1958904] Re: autopkgtest is failing on jammy with "no space left on device"
initramgs-tools in bionic doesn't have debian/tests/. ** Changed in: initramfs-tools (Ubuntu Bionic) Status: Triaged => Invalid -- 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/1958904 Title: autopkgtest is failing on jammy with "no space left on device" Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: Triaged Status in initramfs-tools source package in Impish: Triaged Bug description: In debian/tests/prep-image we create an image file of 1GB, but recent jammy cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+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 1946883] Re: Merge openldap from Debian unstable for 22.04
This bug was fixed in the package openldap - 2.5.11+dfsg-1~exp1ubuntu1 --- openldap (2.5.11+dfsg-1~exp1ubuntu1) jammy; urgency=medium * Merge with Debian unstable (LP: #1946883). Remaining changes: - Enable AppArmor support: + d/apparmor-profile: add AppArmor profile + d/rules: use dh_apparmor + d/control: Build-Depends on dh-apparmor + d/slapd.README.Debian: add note about AppArmor - Enable ufw support: + d/control: suggest ufw. + d/rules: install ufw profile. + d/slapd.ufw.profile: add ufw profile. - d/{rules,slapd.py}: Add apport hook. - d/rules: better regexp to match the Maintainer tag in d/control, needed in the Ubuntu case because of XSBC-Original-Maintainer (Closes #960448, LP #1875697) -- Sergio Durigan Junior Tue, 25 Jan 2022 17:06:12 -0500 ** Changed in: openldap (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1946883 Title: Merge openldap from Debian unstable for 22.04 Status in openldap package in Ubuntu: Fix Released Bug description: Upstream: 2.5.8 Debian: 2.4.59+dfsg-12.5.8+dfsg-1~exp1 Ubuntu: 2.5.6+dfsg-1~exp1ubuntu1 Debian experimental has 2.5.8+dfsg-1~exp1 ### New Debian Changes ### openldap (2.4.59+dfsg-1) unstable; urgency=medium * New upstream release. * Fix FTBFS with autoconf 2.71 (Closes: #993032): - Backport upstream changes to support Autoconf 2.69 instead of simply disabling automake in debian/rules. Fixes FTBFS due to autoreconf thinking files required by Automake are missing, even though Automake is not actually used. - Stop running autoreconf in contrib/ldapc++ since we don't build it. - Drop custom config.{guess,sub} handling. dh_update_autotools_config does the right thing for us. * Update Standards-Version to 4.6.0; no changes required. * Add a superficial autopkgtest for smbk5pwd. * Stop disabling test060-mt-hot on ppc64el. The underlying kernel bug (#866122) is fixed in all relevant suites by now. -- Ryan Tandy Fri, 27 Aug 2021 09:42:31 -0700 openldap (2.4.57+dfsg-3) unstable; urgency=medium * Link smbk5pwd with -lkrb5. (Closes: #988565) -- Ryan Tandy Sat, 15 May 2021 16:03:34 -0700 openldap (2.4.57+dfsg-2) unstable; urgency=medium * Fix slapd assertion failure in Certificate List Exact Assertion validation (ITS#9454) (CVE-2021-27212) -- Ryan Tandy Sun, 14 Feb 2021 09:26:41 -0800 openldap (2.4.57+dfsg-1) unstable; urgency=medium * New upstream release. - Fixed slapd crashes in Certificate Exact Assertion processing (ITS#9404, ITS#9424) (CVE-2020-36221) - Fixed slapd assertion failures in saslAuthzTo validation (ITS#9406, ITS#9407) (CVE-2020-36222) - Fixed slapd crash in Values Return Filter control handling (ITS#9408) (CVE-2020-36223) - Fixed slapd crashes in saslAuthzTo processing (ITS#9409, ITS#9412, ITS#9413) (CVE-2020-36224, CVE-2020-36225, CVE-2020-36226) - Fixed slapd assertion failure in X.509 DN parsing (ITS#9423) (CVE-2020-36230) - Fixed slapd crash in X.509 DN parsing (ITS#9425) (CVE-2020-36229) - Fixed slapd crash in Certificate List Exact Assertion processing (ITS#9427) (CVE-2020-36228) - Fixed slapd infinite loop with Cancel operation (ITS#9428) (CVE-2020-36227) -- Ryan Tandy Sat, 23 Jan 2021 08:57:07 -0800 openldap (2.4.56+dfsg-1) unstable; urgency=medium * New upstream release. - Fixed slapd abort due to assertion failure in Certificate List syntax validation (ITS#9383) (CVE-2020-25709) - Fixed slapd abort due to assertion failure in CSN normalization with invalid input (ITS#9384) (CVE-2020-25710) -- Ryan Tandy Wed, 11 Nov 2020 09:13:56 -0800 openldap (2.4.55+dfsg-1) unstable; urgency=medium * New upstream release. - Fixed slapd normalization handling with modrdn (ITS#9370) (CVE-2020-25692) -- Ryan Tandy Tue, 27 Oct 2020 21:07:29 -0700 openldap (2.4.54+dfsg-1) unstable; urgency=medium * New upstream release. * Change upstream Homepage and get-orig-source URLs to HTTPS. * Create debian/gbp.conf. -- Ryan Tandy Sun, 18 Oct 2020 16:03:46 + openldap (2.4.53+dfsg-1) unstable; urgency=medium * New upstream release. -- Ryan Tandy Mon, 07 Sep 2020 09:47:28 -0700 openldap (2.4.51+dfsg-1) unstable; urgency=medium * New upstream release. - Add ldap_parse_password_expiring_control to libldap-2.4-2.symbols. * Merge some changes from Ubuntu: - slapd.default, slapd.README.Debian: update to refer to slapd.d instead of slapd.conf. - debian/slapd.scripts-common: dump_databases: make slapcat_opts a
[Touch-packages] [Bug 1958904] Re: autopkgtest is failing on jammy with "no space left on device"
This bug was fixed in the package initramfs-tools - 0.140ubuntu11 --- initramfs-tools (0.140ubuntu11) jammy; urgency=medium * Increase image file to 2GB in autopkgtest (LP: #1958904) -- Andrea Righi Tue, 25 Jan 2022 15:03:39 + ** Changed in: initramfs-tools (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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1958904 Title: autopkgtest is failing on jammy with "no space left on device" Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Triaged Status in initramfs-tools source package in Focal: Triaged Status in initramfs-tools source package in Impish: Triaged Bug description: In debian/tests/prep-image we create an image file of 1GB, but recent jammy cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
** Tags added: connection-refused -- 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/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in apport source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when
[Touch-packages] [Bug 1957086] Re: Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
** Tags removed: server-next -- 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/1957086 Title: Autopkgtest systemd fail against dnsmasq 2.86 (22.04) Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: In Progress Bug description: Full log (same on all architectures): https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/systemd/20220106_214401_24d29@/log.gz The test is from systemd: https://github.com/systemd/systemd/blob/main/test/networkd-test.py#L619 Tail of the log: ``` ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.NdIvJq/build.fBQ/src/test/networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.9/subprocess.py", line 424, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.9/subprocess.py", line 528, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. ``` Tagging update-excuse to be shown in excuses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1957086/+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 1946883] Re: Merge openldap from Debian unstable for 22.04
** Changed in: openldap (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1946883 Title: Merge openldap from Debian unstable for 22.04 Status in openldap package in Ubuntu: In Progress Bug description: Upstream: 2.5.8 Debian: 2.4.59+dfsg-12.5.8+dfsg-1~exp1 Ubuntu: 2.5.6+dfsg-1~exp1ubuntu1 Debian experimental has 2.5.8+dfsg-1~exp1 ### New Debian Changes ### openldap (2.4.59+dfsg-1) unstable; urgency=medium * New upstream release. * Fix FTBFS with autoconf 2.71 (Closes: #993032): - Backport upstream changes to support Autoconf 2.69 instead of simply disabling automake in debian/rules. Fixes FTBFS due to autoreconf thinking files required by Automake are missing, even though Automake is not actually used. - Stop running autoreconf in contrib/ldapc++ since we don't build it. - Drop custom config.{guess,sub} handling. dh_update_autotools_config does the right thing for us. * Update Standards-Version to 4.6.0; no changes required. * Add a superficial autopkgtest for smbk5pwd. * Stop disabling test060-mt-hot on ppc64el. The underlying kernel bug (#866122) is fixed in all relevant suites by now. -- Ryan Tandy Fri, 27 Aug 2021 09:42:31 -0700 openldap (2.4.57+dfsg-3) unstable; urgency=medium * Link smbk5pwd with -lkrb5. (Closes: #988565) -- Ryan Tandy Sat, 15 May 2021 16:03:34 -0700 openldap (2.4.57+dfsg-2) unstable; urgency=medium * Fix slapd assertion failure in Certificate List Exact Assertion validation (ITS#9454) (CVE-2021-27212) -- Ryan Tandy Sun, 14 Feb 2021 09:26:41 -0800 openldap (2.4.57+dfsg-1) unstable; urgency=medium * New upstream release. - Fixed slapd crashes in Certificate Exact Assertion processing (ITS#9404, ITS#9424) (CVE-2020-36221) - Fixed slapd assertion failures in saslAuthzTo validation (ITS#9406, ITS#9407) (CVE-2020-36222) - Fixed slapd crash in Values Return Filter control handling (ITS#9408) (CVE-2020-36223) - Fixed slapd crashes in saslAuthzTo processing (ITS#9409, ITS#9412, ITS#9413) (CVE-2020-36224, CVE-2020-36225, CVE-2020-36226) - Fixed slapd assertion failure in X.509 DN parsing (ITS#9423) (CVE-2020-36230) - Fixed slapd crash in X.509 DN parsing (ITS#9425) (CVE-2020-36229) - Fixed slapd crash in Certificate List Exact Assertion processing (ITS#9427) (CVE-2020-36228) - Fixed slapd infinite loop with Cancel operation (ITS#9428) (CVE-2020-36227) -- Ryan Tandy Sat, 23 Jan 2021 08:57:07 -0800 openldap (2.4.56+dfsg-1) unstable; urgency=medium * New upstream release. - Fixed slapd abort due to assertion failure in Certificate List syntax validation (ITS#9383) (CVE-2020-25709) - Fixed slapd abort due to assertion failure in CSN normalization with invalid input (ITS#9384) (CVE-2020-25710) -- Ryan Tandy Wed, 11 Nov 2020 09:13:56 -0800 openldap (2.4.55+dfsg-1) unstable; urgency=medium * New upstream release. - Fixed slapd normalization handling with modrdn (ITS#9370) (CVE-2020-25692) -- Ryan Tandy Tue, 27 Oct 2020 21:07:29 -0700 openldap (2.4.54+dfsg-1) unstable; urgency=medium * New upstream release. * Change upstream Homepage and get-orig-source URLs to HTTPS. * Create debian/gbp.conf. -- Ryan Tandy Sun, 18 Oct 2020 16:03:46 + openldap (2.4.53+dfsg-1) unstable; urgency=medium * New upstream release. -- Ryan Tandy Mon, 07 Sep 2020 09:47:28 -0700 openldap (2.4.51+dfsg-1) unstable; urgency=medium * New upstream release. - Add ldap_parse_password_expiring_control to libldap-2.4-2.symbols. * Merge some changes from Ubuntu: - slapd.default, slapd.README.Debian: update to refer to slapd.d instead of slapd.conf. - debian/slapd.scripts-common: dump_databases: make slapcat_opts a local variable. * Drop paragraph about patch gnutls-altname-nulterminated (#465197) from slapd.README.Debian. The patch referred to was dropped in 2.4.7-6. * debian/patches/set-maintainer-name: Extract maintainer address dynamically from debian/control. (Closes: #960448) * Fix Torsten's email address in a historic debian/changelog entry to resolve a Lintian error (bogus-mail-host-in-debian-changelog). ### Old Ubuntu Delta ### openldap (2.5.6+dfsg-1~exp1ubuntu1) impish; urgency=medium * Merge with Debian unstable. Remaining changes: - Enable AppArmor support: + d/apparmor-profile: add AppArmor profile + d/rules: use dh_apparmor + d/control: Build-Depends on dh-apparmor + d/slapd.README.Debian: add note about AppArmor - Enable ufw support: + d/control:
[Touch-packages] [Bug 1958904] Re: autopkgtest is failing on jammy with "no space left on device"
** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Bionic) Status: New => Triaged ** Changed in: initramfs-tools (Ubuntu Bionic) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu Impish) Status: New => Triaged ** Changed in: initramfs-tools (Ubuntu Impish) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu Bionic) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: initramfs-tools (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: initramfs-tools (Ubuntu Impish) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1958904 Title: autopkgtest is failing on jammy with "no space left on device" Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Bionic: Triaged Status in initramfs-tools source package in Focal: Triaged Status in initramfs-tools source package in Impish: Triaged Bug description: In debian/tests/prep-image we create an image file of 1GB, but recent jammy cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+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 1959103] [NEW] polkitd crashes with segfault with specific config file
Public bug reported: The following config file in `/etc/polkit-1/localauthority.conf.d/02-allow-colord.conf` can cause a segfault in `polkitd`. ``` polkit.addRule(function(action, subject) { if ((action.id == "org.freedesktop.color-manager.create-device" || action.id == "org.freedesktop.color-manager.create-profile" || action.id == "org.freedesktop.color-manager.delete-device" || action.id == "org.freedesktop.color-manager.delete-profile" || action.id == "org.freedesktop.color-manager.modify-device" || action.id == "org.freedesktop.color-manager.modify-profile") && subject.isInGroup("{group}")) { return polkit.Result.YES; } }); ``` 1. As normal user: `systemctl restart cron.service` 2. Error message `Failed to restart cron.service: Message recipient disconnected from message bus without replying` 3. `dmesg` reports: ``` 58.003893] polkitd[963]: segfault at 8 ip 558a96789856 sp 7ffda31e45f0 error 4 in polkitd[558a96784000+f000] [ 58.003899] Code: 50 c7 ff ff 4d 89 e5 48 89 44 24 08 eb 53 66 0f 1f 44 00 00 48 8b 44 24 10 48 89 e9 be 10 00 00 00 31 ff 48 8d 15 0b af 00 00 <4c> 8b 40 08 31 c0 e8 af cb ff ff 48 8b 7c 24 10 e8 65 c9 ff ff 4c `` If you remove the 02-allow-colord.conf the segfault goes away and you are normally prompted for a password. You can also find a couple of references in the internet, e.g http://c-nergy.be/blog/?p=12043. ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "crash file" https://bugs.launchpad.net/bugs/1959103/+attachment/5557607/+files/_usr_lib_policykit-1_polkitd.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1959103 Title: polkitd crashes with segfault with specific config file Status in policykit-1 package in Ubuntu: New Bug description: The following config file in `/etc/polkit-1/localauthority.conf.d/02-allow-colord.conf` can cause a segfault in `polkitd`. ``` polkit.addRule(function(action, subject) { if ((action.id == "org.freedesktop.color-manager.create-device" || action.id == "org.freedesktop.color-manager.create-profile" || action.id == "org.freedesktop.color-manager.delete-device" || action.id == "org.freedesktop.color-manager.delete-profile" || action.id == "org.freedesktop.color-manager.modify-device" || action.id == "org.freedesktop.color-manager.modify-profile") && subject.isInGroup("{group}")) { return polkit.Result.YES; } }); ``` 1. As normal user: `systemctl restart cron.service` 2. Error message `Failed to restart cron.service: Message recipient disconnected from message bus without replying` 3. `dmesg` reports: ``` 58.003893] polkitd[963]: segfault at 8 ip 558a96789856 sp 7ffda31e45f0 error 4 in polkitd[558a96784000+f000] [ 58.003899] Code: 50 c7 ff ff 4d 89 e5 48 89 44 24 08 eb 53 66 0f 1f 44 00 00 48 8b 44 24 10 48 89 e9 be 10 00 00 00 31 ff 48 8d 15 0b af 00 00 <4c> 8b 40 08 31 c0 e8 af cb ff ff 48 8b 7c 24 10 e8 65 c9 ff ff 4c `` If you remove the 02-allow-colord.conf the segfault goes away and you are normally prompted for a password. You can also find a couple of references in the internet, e.g http://c-nergy.be/blog/?p=12043. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1959103/+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 1670313] Re: armhf unit tests as root fail on adt tests, never run on builders
thanks all ! -- 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/1670313 Title: armhf unit tests as root fail on adt tests, never run on builders Status in systemd package in Ubuntu: Won't Fix Bug description: armhf unit tests as root fail on adt tests, never run on builders xnox should fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1670313/+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 1959101] [NEW] sync/merge krb5
Public bug reported: We went ahead of debian because of openssl3: krb5 (1.19.2-0ubuntu1) jammy; urgency=medium [ Sam Hartman ] * New Upstream version * Depend on tex-gyre, Closes: #997407 [Simon Chopin] * d/p/0012-Fix-softpkcs11-build-issues-with-openssl-3.0.patch: Cherry-picked from upstream master to fix OpenSSL3 build. Closes: #995152, LP: #1945795 -- Simon Chopin Tue, 30 Nov 2021 10:54:17 +0100 Debian unstable still has 1.18.3-7, but experimental got 1.19.2-1: krb5 (1.19.2-1) experimental; urgency=medium * New Upstream version * Include patch to work with OpenSSL 3.0, Closes: #995152 * Depend on tex-gyre, Closes: #997407 -- Sam Hartman Wed, 27 Oct 2021 14:04:42 -0600 Since we are already at 1.19.2, we might as well merge/sync with experimental. ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New ** Tags: needs-merge ** Changed in: krb5 (Ubuntu) Milestone: None => ubuntu-22.01 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1959101 Title: sync/merge krb5 Status in krb5 package in Ubuntu: New Bug description: We went ahead of debian because of openssl3: krb5 (1.19.2-0ubuntu1) jammy; urgency=medium [ Sam Hartman ] * New Upstream version * Depend on tex-gyre, Closes: #997407 [Simon Chopin] * d/p/0012-Fix-softpkcs11-build-issues-with-openssl-3.0.patch: Cherry-picked from upstream master to fix OpenSSL3 build. Closes: #995152, LP: #1945795 -- Simon Chopin Tue, 30 Nov 2021 10:54:17 +0100 Debian unstable still has 1.18.3-7, but experimental got 1.19.2-1: krb5 (1.19.2-1) experimental; urgency=medium * New Upstream version * Include patch to work with OpenSSL 3.0, Closes: #995152 * Depend on tex-gyre, Closes: #997407 -- Sam Hartman Wed, 27 Oct 2021 14:04:42 -0600 Since we are already at 1.19.2, we might as well merge/sync with experimental. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1959101/+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 1823053] Re: wpasupplicant 2.6 w/ openssl 1.1.1 triggers TLSv1.3 version intolerance on WPA2-Enterprise networks on Cosmic and Disco
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: wpa (Ubuntu) Importance: Undecided => High ** Changed in: wpa (Ubuntu) Status: New => Fix Released -- 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/1823053 Title: wpasupplicant 2.6 w/ openssl 1.1.1 triggers TLSv1.3 version intolerance on WPA2-Enterprise networks on Cosmic and Disco Status in wpa package in Ubuntu: Fix Released Bug description: Ubuntu 18.10 "Cosmic" and 19.04 "Disco" currently ship with both wpasupplicant 2.6 and openssl/libssl 1.1.1, although upstream only supports OpenSSL 1.1.1 starting with wpasupplicant 2.7. OpenSSL 1.1.1 introduced support for TLS 1.3, and introduced new APIs to configure the parameters governing TLS connections using TLS >= 1.3. OpenSSL also decided that it would enable TLS 1.3 by default even for software that had only been built for libssl <= 1.1.0 and hence couldn't "know" about the new APIs. This leads to a situation where software that was designed/built for OpenSSL 1.1.0 and TLS 1.2 will also offer TLS 1.3, without any possibility for end users to disable such behavior. One case where this causes problems is wpasupplicant: wpasupplicant 2.7 officially introduced support for OpenSSL 1.1.1, which mainly consists of disabling TLS 1.3 by default and adding a configuration flag allowing end users to selectively enable it for connections when they see fit. wpasupplicant 2.6, however, as shipped with Ubuntu 18.10 and 19.04, does not offer such a possibility, and hence tries negotiating TLS 1.3 (alongside with older versions all the way down to TLS 1.0). Sadly, there are RADIUS servers which suffer from TLS version intolerance and will refuse authentication when the client offers TLS 1.3. I know of such a case with a German university's eduroam wifi, but I doubt this is the only case where this causes problems. As a dirty stopgap measure, I've installed the wpasupplicant 2.7 package from Debian Buster (https://packages.debian.org/buster/wpasupplicant), and I've asked the NOC at the affected university to upgrade/reconfigure their RADIUS server to make the version intolerance go away - but still, this is a bug that should be fixed in Ubuntu, preferably by backporting wpasupplicant 2.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1823053/+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 1959097] [NEW] Check for updates right after boot, if Automatically check for updates: Daily is chosen
Public bug reported: If "Software & Updates" > "Updates" > "Automatically check for updates" is set to "Daily" as a user, I would expect it to check right after start up, and perhaps every third hour? Currently, you need to manually trigger a check by opening "Software Updater", for example by hitting "Super" button, type "upda ..." and select the grey "Software Updater" icon. Also, maybe a new option "Every hour" could be added for those extra security conscious? $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- 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/1959097 Title: Check for updates right after boot, if Automatically check for updates: Daily is chosen Status in software-properties package in Ubuntu: New Bug description: If "Software & Updates" > "Updates" > "Automatically check for updates" is set to "Daily" as a user, I would expect it to check right after start up, and perhaps every third hour? Currently, you need to manually trigger a check by opening "Software Updater", for example by hitting "Super" button, type "upda ..." and select the grey "Software Updater" icon. Also, maybe a new option "Every hour" could be added for those extra security conscious? $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1959097/+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 1958642] Re: New 2.37.50.20220119-0ubuntu1 Produces RWE load header on s390x
** Changed in: binutils (Debian) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1958642 Title: New 2.37.50.20220119-0ubuntu1 Produces RWE load header on s390x Status in binutils package in Ubuntu: New Status in binutils package in Debian: Confirmed Bug description: Building libxcrypt with the new binutils upload 2.37.50.20220119-0ubuntu1 in proposed produces binaries with one RWE LOAD header instead of two LOAD headers (one RE, one RW); causing it to fail to load in services that use MemoryDenyWriteExecute=yes, thus breaking a ton of systemd services. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1958642/+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 1945713] Re: Flaky test brotli/basic on focal amd64?
I'm going to set as wontfix so it stops showing up in rlsbugs reports, the issue isn't important enough at this point for us to justify doing the work figuring out what was the fix and SRUing it to focal ** Changed in: libsoup2.4 (Ubuntu Focal) Status: New => Won't Fix ** Changed in: libsoup2.4 (Ubuntu Focal) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1945713 Title: Flaky test brotli/basic on focal amd64? Status in libsoup2.4 package in Ubuntu: Fix Released Status in libsoup2.4 source package in Focal: Won't Fix Bug description: The brotli/basic test case periodically fails. It appears that a few retriggers can result in a pass: https://autopkgtest.ubuntu.com/packages/libs/libsoup2.4/focal/amd64 The failures look like this in autopkgtest logs: ERROR:../tests/brotli-decompressor-test.c:59:test_brotli: assertion failed ((char*)out_bytes->data == contents): ("***\nU" == "***\n") I've replaced most of the text with '***' to highlight the difference is a 'U' character appended. The test case is essentially doing a decompression of 'brotli- data/compressed.br' and comparing that it matches 'brotli- data/uncompressed.txt'. I've done this manually using the brotli cli, and the files do indeed have the same content. I've also built the package and run the test case locally in a focal lxc container on amd64: $ cd libsoup2.4-gu/debian/libsoup2.4-tests/usr/libexec/installed-tests/libsoup-2.4 $ while : ; do ./brotli-decompressor-test | grep 'brotli/basic'; sleep 0.1; done I left that to run several hundred cycles but no failures reported at all. There are a bunch of instances of this failure, here's a few for reference: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210602_152107_d1d56@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210531_201241_8b1be@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20200508_211619_2aec8@/log.gz That last link is the earliest instance I've been able to find. You'll notice in the second two links they also have a failure "not ok 2 /ssl/tls-interaction", but the first link shows only the brotli failure. Interestingly, I've not found instances of this failure against other architectures than amd64, nor have I seen it on releases other than focal. No dice from googling for bug reports or other reports of test failures with libsoup2.4 + brotli. The test's code is doing this, basically: SoupBrotliDecompressor *dec = soup_brotli_decompressor_new (); do { result = g_converter_convert (G_CONVERTER (dec), in_buf, length, out_buf, sizeof out_buf, 0, _read, _written, ); g_byte_array_append (out_bytes, out_buf, bytes_written); in_buf += bytes_read; length -= bytes_read; } while (result == G_CONVERTER_CONVERTED); soup_brotli_decompressor's code is here: https://gitlab.gnome.org/GNOME/libsoup/-/blob/master/libsoup/content- decoder/soup-brotli-decompressor.c But I'm not spotting anything that would obviously cause a 'U' to be randomly appended sometimes. And why 'U'? UINT? Unknown? User error? There are some interesting bug reports in GNOME about brotli in libsoup's bug tracker (e.g. #106, #146, #119, and #193), but none that match this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1945713/+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
** Changed in: systemd (Ubuntu Jammy) Status: New => In Progress -- 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: In Progress Status in systemd source package in Focal: New Status in systemd source package in Impish: New Status in systemd source package in Jammy: In Progress 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. [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 1959082] [NEW] package python2.7-minimal (not installed) failed to install/upgrade: new python2.7-minimal package pre-installation script subprocess returned error exit status 1
Public bug reported: always happened an deny me to install applications ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python2.7-minimal (not installed) ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: python2.7-minimal:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 26 10:51:38 2022 DpkgHistoryLog: Start-Date: 2022-01-26 10:51:38 Commandline: apt --fix-broken install Requested-By: rbit (1000) Install: python2.7-minimal:amd64 (2.7.18-1~20.04.1, automatic) ErrorMessage: new python2.7-minimal package pre-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/local/bin/python2.7, Python 2.7.8, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: python2.7 Title: package python2.7-minimal (not installed) failed to install/upgrade: new python2.7-minimal package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python2.7 (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 python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1959082 Title: package python2.7-minimal (not installed) failed to install/upgrade: new python2.7-minimal package pre-installation script subprocess returned error exit status 1 Status in python2.7 package in Ubuntu: New Bug description: always happened an deny me to install applications ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python2.7-minimal (not installed) ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: python2.7-minimal:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 26 10:51:38 2022 DpkgHistoryLog: Start-Date: 2022-01-26 10:51:38 Commandline: apt --fix-broken install Requested-By: rbit (1000) Install: python2.7-minimal:amd64 (2.7.18-1~20.04.1, automatic) ErrorMessage: new python2.7-minimal package pre-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/local/bin/python2.7, Python 2.7.8, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: python2.7 Title: package python2.7-minimal (not installed) failed to install/upgrade: new python2.7-minimal package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1959082/+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 1959079] [NEW] The UI crashes after suspend
Public bug reported: All was working OK until I installed nvidia cuda drivers. Afterwards on lid open the system crashes. On lid close it exhausted the battery too fast. Now I have them deleted and have reverted to nouveau drivers but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Jan 26 10:37:23 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fa0] NVIDIA Corporation Device [10de:1f95] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fa0] MachineType: LENOVO 82D4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=1c371a7d-438b-4e79-8a3b-218cba05e945 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2020 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: EGCN25WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Creator 5 15IMH05 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrEGCN25WW:bd04/28/2020:br1.25:efr1.25:svnLENOVO:pn82D4:pvrIdeaPadCreator515IMH05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadCreator515IMH05:skuLENOVO_MT_82D4_BU_idea_FM_IdeaPadCreator515IMH05: dmi.product.family: IdeaPad Creator 5 15IMH05 dmi.product.name: 82D4 dmi.product.sku: LENOVO_MT_82D4_BU_idea_FM_IdeaPad Creator 5 15IMH05 dmi.product.version: IdeaPad Creator 5 15IMH05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1959079 Title: The UI crashes after suspend Status in xorg package in Ubuntu: New Bug description: All was working OK until I installed nvidia cuda drivers. Afterwards on lid open the system crashes. On lid close it exhausted the battery too fast. Now I have them deleted and have reverted to nouveau drivers but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Jan 26 10:37:23 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fa0] NVIDIA Corporation Device [10de:1f95] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fa0] MachineType: LENOVO 82D4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=1c371a7d-438b-4e79-8a3b-218cba05e945 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2020 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: EGCN25WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Creator 5 15IMH05 dmi.ec.firmware.release: 1.25 dmi.modalias:
[Touch-packages] [Bug 1959015] Re: Switch to new HTTPS-capable domains for PPAs
** Tags added: rls-jj-incoming -- 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/1959015 Title: Switch to new HTTPS-capable domains for PPAs Status in software-properties package in Ubuntu: New Bug description: As described in bug 1473091, PPAs are now being served from new domains that aren't under launchpad.net and so can safely serve HTTPS without risk of compromising Launchpad session cookies. The old domains will keep working indefinitely, but nevertheless it would be good if we could arrange for add-apt-repository to use the new domains as of 22.04. The changes are: * http://ppa.launchpad.net/ → https://ppa.launchpadcontent.net/ (or http:// works too, but we should prefer https://) * https://private-ppa.launchpad.net/ → https://private-ppa.launchpadcontent.net/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1959015/+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