[Touch-packages] [Bug 1958502] Re: Please merge newt 0.52.21-5 (main) from Debian unstable (main)
New diff that contains the LP bug number in changelog. ** Patch added: "debdiff_oldubuntu_ubuntu.diff" https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+attachment/5557898/+files/debdiff_oldubuntu_ubuntu.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1958502 Title: Please merge newt 0.52.21-5 (main) from Debian unstable (main) Status in newt package in Ubuntu: New Bug description: Please merge newt 0.52.21-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+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 1958502] Re: Please merge newt 0.52.21-5 (main) from Debian unstable (main)
New diff that contains the LP bug number in the changelog. ** Patch added: "debdiff_debian_ubuntu.diff" https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+attachment/5557899/+files/debdiff_debian_ubuntu.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1958502 Title: Please merge newt 0.52.21-5 (main) from Debian unstable (main) Status in newt package in Ubuntu: New Bug description: Please merge newt 0.52.21-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+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 1959343] Re: deprecation of the Canonical partner archive
** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-release-upgrader (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1959343 Title: deprecation of the Canonical partner archive Status in subiquity: Invalid Status in cloud-init package in Ubuntu: In Progress Status in curtin package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: In Progress Status in ubuntu-release-upgrader package in Ubuntu: In Progress Bug description: The Canonical partner archive is no longer being used for publishing new packages, and is empty from Ubuntu 20.10 on. We should stop including it in the default sources.list, and clean up references to it in our codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1959343] Re: deprecation of the Canonical partner archive
** Merge proposal linked: https://code.launchpad.net/~ubuntu-core-dev/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/414711 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1959343 Title: deprecation of the Canonical partner archive Status in subiquity: Invalid Status in cloud-init package in Ubuntu: In Progress Status in curtin package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: In Progress Status in ubuntu-release-upgrader package in Ubuntu: In Progress Bug description: The Canonical partner archive is no longer being used for publishing new packages, and is empty from Ubuntu 20.10 on. We should stop including it in the default sources.list, and clean up references to it in our codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1959365] [NEW] openssh-client tab completion faills if shopt failglob is set
Public bug reported: $ ssh ends up looking like $ ssh bash: no match: /etc/ssh/ssh_config.d/*.conf $ _ I have shopt failglob set in my bashrc as a personal preference and most other packages' tab completion can deal with that. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/1959365 Title: openssh-client tab completion faills if shopt failglob is set Status in openssh package in Ubuntu: New Bug description: $ ssh ends up looking like $ ssh bash: no match: /etc/ssh/ssh_config.d/*.conf $ _ I have shopt failglob set in my bashrc as a personal preference and most other packages' tab completion can deal with that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1959365/+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 1959363] [NEW] Update to libXfixes 6.x
Public bug reported: Update to libXfixes 6.x https://gitlab.freedesktop.org/xorg/lib/libxfixes/-/tags It is a prerequisite to build mutter 42. ** Affects: libxfixes (Ubuntu) Importance: Undecided Status: New ** Tags: jammy needs-packaging ** Tags added: needs-packaging -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxfixes in Ubuntu. https://bugs.launchpad.net/bugs/1959363 Title: Update to libXfixes 6.x Status in libxfixes package in Ubuntu: New Bug description: Update to libXfixes 6.x https://gitlab.freedesktop.org/xorg/lib/libxfixes/-/tags It is a prerequisite to build mutter 42. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1959363/+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 1959343] Re: deprecation of the Canonical partner archive
This bug was fixed in the package python-apt - 2.3.0ubuntu1 --- python-apt (2.3.0ubuntu1) jammy; urgency=medium * Drop references to archive.canonical.com; we should no longer support configuring this as a repository in new releases. LP: #1959343. -- Steve Langasek Thu, 27 Jan 2022 14:46:53 -0800 ** Changed in: python-apt (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 python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1959343 Title: deprecation of the Canonical partner archive Status in subiquity: Invalid Status in cloud-init package in Ubuntu: In Progress Status in curtin package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: In Progress Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: The Canonical partner archive is no longer being used for publishing new packages, and is empty from Ubuntu 20.10 on. We should stop including it in the default sources.list, and clean up references to it in our codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1955797] Re: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.
** Description changed: [Impact] Some 4G/5G mobile networks(for ex., AT&T) requires a specific MTU setting, this setting will be exposed by the ModemManager for network- manger to configure the MTU of the modem network interface . - The current modem-manager v1.22.10-1ubuntu2.2 in focal can’t pass + The current network-manager v1.22.10-1ubuntu2.2 in focal can’t pass AT&T’s modem system certification. [Fix] This upstream patch can resolve this bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631 [Test Plan] 1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an AT&T SIM card in US 2. Enable 4G modem and connect to AT&T apn $ sudo mmcli -i 0 --pin= $ sudo mmcli --modem 0 --enable $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome" $ sudo nmcli radio wwan on $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn emome $ sudo nmcli connection up id mymodem 3. Check if the MTU got from the following results are the same: $ sudo mmcli --bearer 5 | mtu $ ifconfig mhi_mbim0 | grep mtu * Expected result: Both MTUs are the same value 1430 * Actual tested result: Different values (one is 1430 , another is 1500) [Where problems could occur] Very low. This is a simple fix: network-manager gets the MTU from the ModemManager then sets the MTU of the modem interface. [Other info] 1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1955797 Title: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems. Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] Some 4G/5G mobile networks(for ex., AT&T) requires a specific MTU setting, this setting will be exposed by the ModemManager for network- manger to configure the MTU of the modem network interface . The current network-manager v1.22.10-1ubuntu2.2 in focal can’t pass AT&T’s modem system certification. [Fix] This upstream patch can resolve this bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631 [Test Plan] 1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an AT&T SIM card in US 2. Enable 4G modem and connect to AT&T apn $ sudo mmcli -i 0 --pin= $ sudo mmcli --modem 0 --enable $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome" $ sudo nmcli radio wwan on $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn emome $ sudo nmcli connection up id mymodem 3. Check if the MTU got from the following results are the same: $ sudo mmcli --bearer 5 | mtu $ ifconfig mhi_mbim0 | grep mtu * Expected result: Both MTUs are the same value 1430 * Actual tested result: Different values (one is 1430 , another is 1500) [Where problems could occur] Very low. This is a simple fix: network-manager gets the MTU from the ModemManager then sets the MTU of the modem interface. [Other info] 1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+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 1959337] Re: install sysvinit_utils does not end
** Tags added: mate ** Summary changed: - install sysvinit_utils does not end + [mate] install sysvinit_utils does not end -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1959337 Title: [mate] install sysvinit_utils does not end Status in sysvinit package in Ubuntu: New Bug description: Get a new version on Jammy; but got stuck at triggers for man-db sudo apt-get install --reinstall sysvinit-utils [sudo] Mot de passe de bilal : Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait 0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 4 non mis à jour. Il est nécessaire de prendre 0 o/20,6 ko dans les archives. Après cette opération, 0 o d'espace disque supplémentaires seront utilisés. (Lecture de la base de données... 316349 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../sysvinit-utils_3.01-1ubuntu1_amd64.deb ... Dépaquetage de sysvinit-utils (3.01-1ubuntu1) sur (3.01-1ubuntu1) ... Paramétrage de sysvinit-utils (3.01-1ubuntu1) ... Traitement des actions différées (« triggers ») pour man-db (2.9.4-4) ... Reconfiguring the package does not solve that issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1959337/+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 1959343] Re: deprecation of the Canonical partner archive
This bug was fixed in the package livecd-rootfs - 2.752 --- livecd-rootfs (2.752) jammy; urgency=medium * Remove references to archive.canonical.com, which is no longer used and should not be included in the default sources.list. LP: #1959343. -- Steve Langasek Thu, 27 Jan 2022 14:26:52 -0800 ** Changed in: livecd-rootfs (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 python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1959343 Title: deprecation of the Canonical partner archive Status in subiquity: Invalid Status in cloud-init package in Ubuntu: In Progress Status in curtin package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: In Progress Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: The Canonical partner archive is no longer being used for publishing new packages, and is empty from Ubuntu 20.10 on. We should stop including it in the default sources.list, and clean up references to it in our codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed
Yes the kernel graphics driver provides the path to the monitor audio device so that might be it. Although history makes me suspect PulseAudio more. ** Tags added: amdgpu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1957816 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in pulseaudio package in Ubuntu: New Bug description: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 1959340] Re: frequent color snowing on screen after resuming from suspend
*** This bug is a duplicate of bug 1958591 *** https://bugs.launchpad.net/bugs/1958591 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 1958412, 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. ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** This bug has been marked a duplicate of bug 1958412 [amdgpu] Flickering/noise on screen started in kernel 5.13 ** This bug is no longer a duplicate of bug 1958412 [amdgpu] Flickering/noise on screen started in kernel 5.13 ** This bug has been marked a duplicate of bug 1958591 [amdgpu] Random noise 'static' display after internal display turned off/on -- 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/1959340 Title: frequent color snowing on screen after resuming from suspend Status in linux-hwe-5.13 package in Ubuntu: New Bug description: For the last 2 days my Thinkpad X13 laptop frequently opens with snowing pixels across the whole screen. The only way to stop it seems to be to hard-reset my laptop. $ uname -a Linux X13 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux 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:56:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-09-23 (126 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20UF0014US ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=8e981ab2-e4f0-4607-b2c4-587a6db04c7d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1CET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1959340/+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 1959343] Re: deprecation of the Canonical partner archive
No references to archive.canonical.com in the subiquity source. ** Changed in: cloud-init (Ubuntu) Status: New => In Progress ** Changed in: subiquity Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1959343 Title: deprecation of the Canonical partner archive Status in subiquity: Invalid Status in cloud-init package in Ubuntu: In Progress Status in curtin package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Committed Status in python-apt package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: In Progress Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: The Canonical partner archive is no longer being used for publishing new packages, and is empty from Ubuntu 20.10 on. We should stop including it in the default sources.list, and clean up references to it in our codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1959343] Re: deprecation of the Canonical partner archive
** Merge proposal linked: https://code.launchpad.net/~vorlon/cloud-init/+git/cloud-init/+merge/414703 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1959343 Title: deprecation of the Canonical partner archive Status in subiquity: Invalid Status in cloud-init package in Ubuntu: In Progress Status in curtin package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Committed Status in python-apt package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: In Progress Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: The Canonical partner archive is no longer being used for publishing new packages, and is empty from Ubuntu 20.10 on. We should stop including it in the default sources.list, and clean up references to it in our codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1959343] Re: deprecation of the Canonical partner archive
It was thought that curtin would need an update for this, but I can find no references to archive.canonical.com in the current curtin source. ** Changed in: curtin (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1959343 Title: deprecation of the Canonical partner archive Status in subiquity: New Status in cloud-init package in Ubuntu: New Status in curtin package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Committed Status in python-apt package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: In Progress Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: The Canonical partner archive is no longer being used for publishing new packages, and is empty from Ubuntu 20.10 on. We should stop including it in the default sources.list, and clean up references to it in our codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1959343] Re: deprecation of the Canonical partner archive
** Merge proposal linked: https://code.launchpad.net/~vorlon/ubiquity/+git/ubiquity/+merge/414702 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1959343 Title: deprecation of the Canonical partner archive Status in subiquity: New Status in cloud-init package in Ubuntu: New Status in curtin package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Committed Status in python-apt package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: In Progress Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: The Canonical partner archive is no longer being used for publishing new packages, and is empty from Ubuntu 20.10 on. We should stop including it in the default sources.list, and clean up references to it in our codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1959343] Re: deprecation of the Canonical partner archive
** Changed in: ubiquity (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) ** Changed in: ubiquity (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1959343 Title: deprecation of the Canonical partner archive Status in subiquity: New Status in cloud-init package in Ubuntu: New Status in curtin package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Committed Status in python-apt package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: In Progress Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: The Canonical partner archive is no longer being used for publishing new packages, and is empty from Ubuntu 20.10 on. We should stop including it in the default sources.list, and clean up references to it in our codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1959340] Re: frequent color snowing on screen after resuming from suspend
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1959340 Title: frequent color snowing on screen after resuming from suspend Status in xorg package in Ubuntu: New Bug description: For the last 2 days my Thinkpad X13 laptop frequently opens with snowing pixels across the whole screen. The only way to stop it seems to be to hard-reset my laptop. $ uname -a Linux X13 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux 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:56:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-09-23 (126 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20UF0014US ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=8e981ab2-e4f0-4607-b2c4-587a6db04c7d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1CET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1959340/+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 1959340] [NEW] frequent color snowing on screen after resuming from suspend
You have been subscribed to a public bug: For the last 2 days my Thinkpad X13 laptop frequently opens with snowing pixels across the whole screen. The only way to stop it seems to be to hard-reset my laptop. $ uname -a Linux X13 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux 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:56:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-09-23 (126 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20UF0014US ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=8e981ab2-e4f0-4607-b2c4-587a6db04c7d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1CET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 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 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 corruption focal ubuntu -- frequent color snowing on screen after resuming from suspend https://bugs.launchpad.net/bugs/1959340 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959343] Re: deprecation of the Canonical partner archive
** Changed in: python-apt (Ubuntu) Status: New => Fix Committed ** Changed in: python-apt (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1959343 Title: deprecation of the Canonical partner archive Status in subiquity: New Status in cloud-init package in Ubuntu: New Status in curtin package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Committed Status in python-apt package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: The Canonical partner archive is no longer being used for publishing new packages, and is empty from Ubuntu 20.10 on. We should stop including it in the default sources.list, and clean up references to it in our codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1959325] Re: New binutils causes build failures for many RISC-V packages
Looks like this will cause most KDE things to FTBFS -- 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/1959325 Title: New binutils causes build failures for many RISC-V packages Status in binutils package in Ubuntu: Confirmed Bug description: binutils 2.37.90.20220126-0ubuntu1 changes the -march flags. We see a lot of packages not building in proposed anymore: OpenSBI, ktexteditor, ... Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1959325/+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 1959343] Re: deprecation of the Canonical partner archive
** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1959343 Title: deprecation of the Canonical partner archive Status in subiquity: New Status in cloud-init package in Ubuntu: New Status in curtin package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Committed Status in python-apt package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: The Canonical partner archive is no longer being used for publishing new packages, and is empty from Ubuntu 20.10 on. We should stop including it in the default sources.list, and clean up references to it in our codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1959325] Re: New binutils causes build failures for many RISC-V packages
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: binutils (Ubuntu) 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/1959325 Title: New binutils causes build failures for many RISC-V packages Status in binutils package in Ubuntu: Confirmed Bug description: binutils 2.37.90.20220126-0ubuntu1 changes the -march flags. We see a lot of packages not building in proposed anymore: OpenSBI, ktexteditor, ... Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1959325/+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 1959343] [NEW] deprecation of the Canonical partner archive
Public bug reported: The Canonical partner archive is no longer being used for publishing new packages, and is empty from Ubuntu 20.10 on. We should stop including it in the default sources.list, and clean up references to it in our codebase. ** Affects: subiquity Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Affects: curtin (Ubuntu) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Assignee: Steve Langasek (vorlon) Status: Fix Committed ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Also affects: subiquity Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1959343 Title: deprecation of the Canonical partner archive Status in subiquity: New Status in cloud-init package in Ubuntu: New Status in curtin package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Committed Status in python-apt package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: The Canonical partner archive is no longer being used for publishing new packages, and is empty from Ubuntu 20.10 on. We should stop including it in the default sources.list, and clean up references to it in our codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1959343/+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"
Historically, we have sought to avoid publishing to -updates of SRUs that only fix autopkgtests because fixing the autopkgtests does not change the behavior of the package in a way that benefits the end user and justifies the download cost. However, between the fact that this is initramfs-tools, and the recent changes to the behavior of proposed-migration, I think it's important that an exception be made here. The initramfs-tools package is critical to how our systems boot, and we cannot afford to have regressions in test coverage of this package. If an update to the Linux kernel has the consequence that the baseline (i.e. in -updates) for initramfs-tools has regressed, this means that any future packages which trigger initramfs- tools autopkgtests will NOT have their SRUs blocked by test failures, whether or not they have introduced further regressions in initramfs- tools. Unless we land this package in -updates, ensuring that we have a green baseline. ** Tags removed: 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 1959160] Re: package systemd 245.4-4ubuntu3.11 failed to install/upgrade: no se pudieron copiar los datos extraídos de './bin/systemctl' a '/bin/systemctl.dpkg-new': fin de fiche
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment to this bug report it seems that there may be a problem with your hardware. I'd recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu) Importance: Undecided => Low ** Tags added: hardware-error ** Information type changed from Private Security to Public Security -- 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/1959160 Title: package systemd 245.4-4ubuntu3.11 failed to install/upgrade: no se pudieron copiar los datos extraídos de './bin/systemctl' a '/bin/systemctl.dpkg-new': fin de fichero o de flujo inesperado Status in systemd package in Ubuntu: Invalid Bug description: I cant to use ubuntus store ProblemType: Package DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.11 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.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 26 23:23:33 2022 ErrorMessage: no se pudieron copiar los datos extraídos de './bin/systemctl' a '/bin/systemctl.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2022-01-27 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 2466RA9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=aeba2232-8f7b-4fcc-bc3a-7a15409cdcc0 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: package systemd 245.4-4ubuntu3.11 failed to install/upgrade: no se pudieron copiar los datos extraídos de './bin/systemctl' a '/bin/systemctl.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2019 dmi.bios.release: 2.76 dmi.bios.vendor: LENOVO dmi.bios.version: G3ETB6WW(2.76) dmi.board.asset.tag: Not Available dmi.board.name: 2466RA9 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG3ETB6WW(2.76):bd09/18/2019:br2.76:svnLENOVO:pn2466RA9:pvrThinkPadL430:rvnLENOVO:rn2466RA9:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2466: dmi.product.family: ThinkPad L430 dmi.product.name: 2466RA9 dmi.product.sku: LENOVO_MT_2466 dmi.product.version: ThinkPad L430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959160/+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 1959337] Re: install sysvinit_utils does not end
** Tags added: jammy upgrade -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1959337 Title: install sysvinit_utils does not end Status in sysvinit package in Ubuntu: New Bug description: Get a new version on Jammy; but got stuck at triggers for man-db sudo apt-get install --reinstall sysvinit-utils [sudo] Mot de passe de bilal : Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait 0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 4 non mis à jour. Il est nécessaire de prendre 0 o/20,6 ko dans les archives. Après cette opération, 0 o d'espace disque supplémentaires seront utilisés. (Lecture de la base de données... 316349 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../sysvinit-utils_3.01-1ubuntu1_amd64.deb ... Dépaquetage de sysvinit-utils (3.01-1ubuntu1) sur (3.01-1ubuntu1) ... Paramétrage de sysvinit-utils (3.01-1ubuntu1) ... Traitement des actions différées (« triggers ») pour man-db (2.9.4-4) ... Reconfiguring the package does not solve that issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1959337/+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 1953052] Re: In Jammy sound level reset after reboot
It's a bit weird, trying in a VM in a simple wmaker session, changing the level in pavucontrol and restarting the machine the sound is correctly restored on the same position after the restart so the systemd unit seems to be working as expected. Could someone having the issue change the level, restart, check that the level is indeed wrong and if it is get a log from the previous session with 'journalctl -b 1 > log' and add the log file to the report? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (
[Touch-packages] [Bug 1959337] [NEW] install sysvinit_utils does not end
Public bug reported: Get a new version on Jammy; but got stuck at triggers for man-db sudo apt-get install --reinstall sysvinit-utils [sudo] Mot de passe de bilal : Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait 0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 4 non mis à jour. Il est nécessaire de prendre 0 o/20,6 ko dans les archives. Après cette opération, 0 o d'espace disque supplémentaires seront utilisés. (Lecture de la base de données... 316349 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../sysvinit-utils_3.01-1ubuntu1_amd64.deb ... Dépaquetage de sysvinit-utils (3.01-1ubuntu1) sur (3.01-1ubuntu1) ... Paramétrage de sysvinit-utils (3.01-1ubuntu1) ... Traitement des actions différées (« triggers ») pour man-db (2.9.4-4) ... Reconfiguring the package does not solve that issue. ** Affects: sysvinit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1959337 Title: install sysvinit_utils does not end Status in sysvinit package in Ubuntu: New Bug description: Get a new version on Jammy; but got stuck at triggers for man-db sudo apt-get install --reinstall sysvinit-utils [sudo] Mot de passe de bilal : Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait 0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 4 non mis à jour. Il est nécessaire de prendre 0 o/20,6 ko dans les archives. Après cette opération, 0 o d'espace disque supplémentaires seront utilisés. (Lecture de la base de données... 316349 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../sysvinit-utils_3.01-1ubuntu1_amd64.deb ... Dépaquetage de sysvinit-utils (3.01-1ubuntu1) sur (3.01-1ubuntu1) ... Paramétrage de sysvinit-utils (3.01-1ubuntu1) ... Traitement des actions différées (« triggers ») pour man-db (2.9.4-4) ... Reconfiguring the package does not solve that issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1959337/+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 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3
** Tags removed: server-todo -- 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/1863930 Title: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3 Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: Incomplete Bug description: [Impact] * The version check in ssh was broken no more following RFC 4253 and thereby denying some clients that it shouldn't. https://datatracker.ietf.org/doc/html/rfc4253#section-5.1 * It is intended for clients reporting SSH-1.99 to be treated as if they were advertising SSH-2.0, but with some backwards compatibility. * Upstream fixed that, and this request is to back-port the changes into 18.04 Bionic. * In practice this is affecting clients using the SolarWinds monitoring agent. Solarwinds SSH client advertises SSH-1.99 and Ubuntu 18.04 openssh-server is refusing the connection. * This results in the following error in the auth.log, and a failed connection from the agent. Protocol major versions differ for port : SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-WeOnlyDo.Net * More information from SolarWinds at the link below. They call out 18.04 as affected and recommend upgrading OpenSSH-server to 7.7 or greater. https://support.solarwinds.com/SuccessCenter/s/article/SAM-s-Linux- Unix-Script-monitor-fails-to-connect-on-a-server-running- OpenSSH-7-6?language=en_US [Test Case] # Prep * configure the ssh server to generally work # Testcase $ wget https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+attachment/5332797/+files/test_bug_1863930.py $ apt install python3-paramiko $ python3 test_bug_1863930.py localhost (or whatever your host is) Will report "Server is not patched." or "Server is patched. * for an extra regression check it might be worth to do some "normal" ssh connections as well [Regression Potential] * The change is very small and reviewable as well as being upstream and in all Ubuntu releases >=Cosmic for a while now so it seems safe. If anything the kind of regression to expect is that some former (wrong) connection denials will then succeed. I can only think of that being an issue in test suites but not in the real world. [Other Info] * n/a -- SSHD closes the connection and logs the error message below when a client presents a protoversion of "1.99": Protocol major versions differ for X.X.X.X port X: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX RFC 4253 only states that clients should treat a server's protoversion of "1.99" as equivalent to "2.0"; however, some backward-compatible clients send a protoversion of "1.99" and expect the server to treat it as "2.0". This regression was introduced in openssh-portable 7.6p1 from commit 97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06. I've attached a patch with both of those fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+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 1958666] Re: Please merge sysvinit 3.01-1 (main) from Debian unstable (main)
This bug was fixed in the package sysvinit - 3.01-1ubuntu1 --- sysvinit (3.01-1ubuntu1) jammy; urgency=low * Merge from Debian unstable. (Closes: LP: #1958666) Remaining changes: - When building for Ubuntu, skip all binaries except for sysvinit-utils - Define the DEB_HOST_* variables in d/rules if not defined already sysvinit (3.01-1) unstable; urgency=medium * Update upstream signing key. * New upstream version 3.01 * Remove patch applied upstream. sysvinit (3.00-2~exp1) experimental; urgency=medium * Remove time served support for converting /etc/rc.local to conffile (Closes: #987732). * Provisional upstream patch to restore pidof reporting D processes (Closes: #926896). sysvinit (3.00-1) unstable; urgency=medium * New upstream version 3.00 * d/changelog: fix typo in previous version. sysvinit (3.00~beta-1) experimental; urgency=medium [ Mark Hindley ] * Add myself to uploaders. * New upstream version 3.00~beta. * d/patches: remove patch applied upstream. * d/patches: refresh patches. * initscripts: remove -t option from telinit invocation (Closes: #990019). * bootmisc.sh: set SE Linux context after utmp file creation. Thanks to Russell Coker. (Closes: #950459) * Remove obsolete lintian overrides. * Update to Standards Version 4.6.0 (no changes). [ Ian Jackson ] * mountkernfs.sh: mount /sys/firmware/efi/efivars if possible (Closes: #783990). [ Dr. Tobias Quathamer ] * Rename manpage tmpfs.5 to tmpfs-config.5 (Closes: #848121, #951596). [ Trek ] * init-d-script: fix PIDFILE argument to status_of_proc (Closes: #962649). * init-d-script: allow disabling --exec or --name options. * init-d-script: fix do_status when DAEMON=none. * init-d-script: policy compliant exit values (Closes: #968038). * init-d-script: fix force-reload if do_reload is an alias. * init-d-script: added do_reload_cmd interface. * init-d-script: added RELOAD_SIGNAL interface. Thanks to Robbie Harwood (Closes: #807311). * init-d-script: send SIGCONT after SIGTERM. Thanks to Jan Braun . * init-d-script: fix try-restart output and more verbosity. * init-d-script: /bin/sh as interpreter and small optimizations. -- Olivier Gayot Tue, 14 Dec 2021 21:17:22 + ** Changed in: sysvinit (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1958666 Title: Please merge sysvinit 3.01-1 (main) from Debian unstable (main) Status in sysvinit package in Ubuntu: Fix Released Bug description: https://merges.ubuntu.com/s/sysvinit/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1958666/+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 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed
I just tested it on a laptop with intel graphics, and sound and playback is perfectly normal on 60Hz when playing through the HDMI (playing on the television). Same cable, same television - only connected to my laptop instead. This makes me wonder whether this could be an issue in the kernel driver, amdgpu? Hardware: CPU: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz GPU: Intel(R) HD Graphics 4400 (HSW GT2) OS: Ubuntu 21.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1957816 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in pulseaudio package in Ubuntu: New Bug description: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 1861250] Re: Apparmor error failed to start profiles
Looks like the profile for cups-browsed has a syntax error. (Did you change something in the profile, or is it the original profile as shipped in the package?) Also, AFAIK this profile is shipped with the cups package, therefore I'm adding that package. ** Also affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1861250 Title: Apparmor error failed to start profiles Status in apparmor package in Ubuntu: Confirmed Status in cups package in Ubuntu: New Bug description: OS Ubuntu focal fossa 20.04 On boot error message - Apparmor Failed to start profiles. Steps attempted to correct 1.sudo as status lee@lee-desktop:~$ sudo aa-status apparmor module is loaded. 53 profiles are loaded. 51 profiles are in enforce mode. /sbin/dhclient /snap/core/8268/usr/lib/snapd/snap-confine /snap/core/8268/usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/bin/evince /usr/bin/evince-previewer /usr/bin/evince-previewer//sanitized_helper /usr/bin/evince-thumbnailer /usr/bin/evince//sanitized_helper /usr/bin/man /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/NetworkManager/nm-dhcp-helper /usr/lib/connman/scripts/dhclient-script /usr/lib/cups/backend/cups-pdf /usr/lib/lightdm/lightdm-guest-session /usr/lib/lightdm/lightdm-guest-session//chromium /usr/lib/snapd/snap-confine /usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/lib/telepathy/mission-control-5 /usr/lib/telepathy/telepathy-* /usr/lib/telepathy/telepathy-*//pxgsettings /usr/lib/telepathy/telepathy-*//sanitized_helper /usr/lib/telepathy/telepathy-ofono /usr/sbin/cups-browsed /usr/sbin/cupsd /usr/sbin/cupsd//third_party /usr/sbin/ippusbxd /usr/sbin/tcpdump /usr/share/hplip/plugin.py /usr/share/hplip/sendfax.py /usr/share/hplip/setup.py /usr/share/hplip/systray.py /usr/share/hplip/toolbox.py libreoffice-senddoc libreoffice-soffice//gpg libreoffice-xpdfimport lsb_release man_filter man_groff nvidia_modprobe nvidia_modprobe//kmod snap-update-ns.core snap-update-ns.gnome-calculator snap-update-ns.gnome-characters snap-update-ns.gnome-logs snap-update-ns.gnome-system-monitor snap.core.hook.configure snap.gnome-calculator.gnome-calculator snap.gnome-characters.gnome-characters snap.gnome-logs.gnome-logs snap.gnome-system-monitor.gnome-system-monitor system_tor 2 profiles are in complain mode. libreoffice-oopslash libreoffice-soffice 3 processes have profiles defined. 3 processes are in enforce mode. /usr/lib/telepathy/mission-control-5 (3090) /usr/sbin/cupsd (1646) /usr/bin/tor (1861) system_tor 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. lee@lee-desktop:~$ 2.sudo /etc/init.d/apparmor restart lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. failed! lee@lee-desktop:~$ 3.sudo rm -rf /etc/apparmor.d/cache/* 4. sudo /etc/init.d/apparmor restart lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. failed! lee@lee-desktop:~$ Thanks, Lee ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apparmor 2.13.3-7ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 23:19:19 2020 InstallationDate: Installed on 2013-08-08 (2365 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=d2e1abc4-e044-467e-8cc2-57cbe4ef3115 ro drm.debug=0xe plymouth:debug SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1861250/+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/List
[Touch-packages] [Bug 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3
** Changed in: openssh (Ubuntu Bionic) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Changed in: openssh (Ubuntu Bionic) Importance: Low => High ** Changed in: openssh (Ubuntu Bionic) Importance: High => Medium -- 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/1863930 Title: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3 Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: Incomplete Bug description: [Impact] * The version check in ssh was broken no more following RFC 4253 and thereby denying some clients that it shouldn't. https://datatracker.ietf.org/doc/html/rfc4253#section-5.1 * It is intended for clients reporting SSH-1.99 to be treated as if they were advertising SSH-2.0, but with some backwards compatibility. * Upstream fixed that, and this request is to back-port the changes into 18.04 Bionic. * In practice this is affecting clients using the SolarWinds monitoring agent. Solarwinds SSH client advertises SSH-1.99 and Ubuntu 18.04 openssh-server is refusing the connection. * This results in the following error in the auth.log, and a failed connection from the agent. Protocol major versions differ for port : SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-WeOnlyDo.Net * More information from SolarWinds at the link below. They call out 18.04 as affected and recommend upgrading OpenSSH-server to 7.7 or greater. https://support.solarwinds.com/SuccessCenter/s/article/SAM-s-Linux- Unix-Script-monitor-fails-to-connect-on-a-server-running- OpenSSH-7-6?language=en_US [Test Case] # Prep * configure the ssh server to generally work # Testcase $ wget https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+attachment/5332797/+files/test_bug_1863930.py $ apt install python3-paramiko $ python3 test_bug_1863930.py localhost (or whatever your host is) Will report "Server is not patched." or "Server is patched. * for an extra regression check it might be worth to do some "normal" ssh connections as well [Regression Potential] * The change is very small and reviewable as well as being upstream and in all Ubuntu releases >=Cosmic for a while now so it seems safe. If anything the kind of regression to expect is that some former (wrong) connection denials will then succeed. I can only think of that being an issue in test suites but not in the real world. [Other Info] * n/a -- SSHD closes the connection and logs the error message below when a client presents a protoversion of "1.99": Protocol major versions differ for X.X.X.X port X: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX RFC 4253 only states that clients should treat a server's protoversion of "1.99" as equivalent to "2.0"; however, some backward-compatible clients send a protoversion of "1.99" and expect the server to treat it as "2.0". This regression was introduced in openssh-portable 7.6p1 from commit 97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06. I've attached a patch with both of those fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+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 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3
As per Mark's description, this seems to fall in the > - some reasonable cases exists, but are very rare: SRU it but hold the release in block-proposed until the next "important" update comes case described above. ** Tags added: server-todo -- 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/1863930 Title: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3 Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: Incomplete Bug description: [Impact] * The version check in ssh was broken no more following RFC 4253 and thereby denying some clients that it shouldn't. https://datatracker.ietf.org/doc/html/rfc4253#section-5.1 * It is intended for clients reporting SSH-1.99 to be treated as if they were advertising SSH-2.0, but with some backwards compatibility. * Upstream fixed that, and this request is to back-port the changes into 18.04 Bionic. * In practice this is affecting clients using the SolarWinds monitoring agent. Solarwinds SSH client advertises SSH-1.99 and Ubuntu 18.04 openssh-server is refusing the connection. * This results in the following error in the auth.log, and a failed connection from the agent. Protocol major versions differ for port : SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-WeOnlyDo.Net * More information from SolarWinds at the link below. They call out 18.04 as affected and recommend upgrading OpenSSH-server to 7.7 or greater. https://support.solarwinds.com/SuccessCenter/s/article/SAM-s-Linux- Unix-Script-monitor-fails-to-connect-on-a-server-running- OpenSSH-7-6?language=en_US [Test Case] # Prep * configure the ssh server to generally work # Testcase $ wget https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+attachment/5332797/+files/test_bug_1863930.py $ apt install python3-paramiko $ python3 test_bug_1863930.py localhost (or whatever your host is) Will report "Server is not patched." or "Server is patched. * for an extra regression check it might be worth to do some "normal" ssh connections as well [Regression Potential] * The change is very small and reviewable as well as being upstream and in all Ubuntu releases >=Cosmic for a while now so it seems safe. If anything the kind of regression to expect is that some former (wrong) connection denials will then succeed. I can only think of that being an issue in test suites but not in the real world. [Other Info] * n/a -- SSHD closes the connection and logs the error message below when a client presents a protoversion of "1.99": Protocol major versions differ for X.X.X.X port X: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX RFC 4253 only states that clients should treat a server's protoversion of "1.99" as equivalent to "2.0"; however, some backward-compatible clients send a protoversion of "1.99" and expect the server to treat it as "2.0". This regression was introduced in openssh-portable 7.6p1 from commit 97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06. I've attached a patch with both of those fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+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 1959015] Re: Switch to new HTTPS-capable domains for PPAs
** Tags removed: 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 Status in software-properties source package in Jammy: 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
[Touch-packages] [Bug 1955084] Re: systemd unit leaves a process running for the system lifetime but it only does anything at shutdown
** Tags added: fr-2007 ** Tags removed: rls-jj-incoming -- 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/1955084 Title: systemd unit leaves a process running for the system lifetime but it only does anything at shutdown Status in unattended-upgrades package in Ubuntu: New Status in unattended-upgrades source package in Jammy: New Bug description: The /lib/systemd/system/unattended-upgrades.service unit leaves a process, /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal, running from system start until shutdown. This increases the minimum memory footprint of every host, VM, or container where unattended-upgrades is installed. The motivation for having this systemd unit is clear in terms of the practicalities of implementing what this unit needs to do, but we should try to find some way to achieve this which does not rely on increasing the low water mark of system memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1955084/+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 1959325] [NEW] New binutils causes build failures for many RISC-V packages
Public bug reported: binutils 2.37.90.20220126-0ubuntu1 changes the -march flags. We see a lot of packages not building in proposed anymore: OpenSBI, ktexteditor, ... Best regards Heinrich ** Affects: binutils (Ubuntu) Importance: Undecided Status: New ** Tags: fr-2006 riscv64 ** Tags added: fr-2006 -- 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/1959325 Title: New binutils causes build failures for many RISC-V packages Status in binutils package in Ubuntu: New Bug description: binutils 2.37.90.20220126-0ubuntu1 changes the -march flags. We see a lot of packages not building in proposed anymore: OpenSBI, ktexteditor, ... Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1959325/+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 1861250] Re: Apparmor error failed to start profiles
I found the same issue in my dmesg output. Here is outupt of suggested command # apparmor_parser -r /etc/apparmor.d/ AppArmor parser error for /etc/apparmor.d/ in profile /etc/apparmor.d//usr.sbin.cups-browsed at line 23: syntax error, unexpected TOK_CLOSE, expecting TOK_ID or TOK_END_OF_RULE Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1861250 Title: Apparmor error failed to start profiles Status in apparmor package in Ubuntu: Confirmed Bug description: OS Ubuntu focal fossa 20.04 On boot error message - Apparmor Failed to start profiles. Steps attempted to correct 1.sudo as status lee@lee-desktop:~$ sudo aa-status apparmor module is loaded. 53 profiles are loaded. 51 profiles are in enforce mode. /sbin/dhclient /snap/core/8268/usr/lib/snapd/snap-confine /snap/core/8268/usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/bin/evince /usr/bin/evince-previewer /usr/bin/evince-previewer//sanitized_helper /usr/bin/evince-thumbnailer /usr/bin/evince//sanitized_helper /usr/bin/man /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/NetworkManager/nm-dhcp-helper /usr/lib/connman/scripts/dhclient-script /usr/lib/cups/backend/cups-pdf /usr/lib/lightdm/lightdm-guest-session /usr/lib/lightdm/lightdm-guest-session//chromium /usr/lib/snapd/snap-confine /usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/lib/telepathy/mission-control-5 /usr/lib/telepathy/telepathy-* /usr/lib/telepathy/telepathy-*//pxgsettings /usr/lib/telepathy/telepathy-*//sanitized_helper /usr/lib/telepathy/telepathy-ofono /usr/sbin/cups-browsed /usr/sbin/cupsd /usr/sbin/cupsd//third_party /usr/sbin/ippusbxd /usr/sbin/tcpdump /usr/share/hplip/plugin.py /usr/share/hplip/sendfax.py /usr/share/hplip/setup.py /usr/share/hplip/systray.py /usr/share/hplip/toolbox.py libreoffice-senddoc libreoffice-soffice//gpg libreoffice-xpdfimport lsb_release man_filter man_groff nvidia_modprobe nvidia_modprobe//kmod snap-update-ns.core snap-update-ns.gnome-calculator snap-update-ns.gnome-characters snap-update-ns.gnome-logs snap-update-ns.gnome-system-monitor snap.core.hook.configure snap.gnome-calculator.gnome-calculator snap.gnome-characters.gnome-characters snap.gnome-logs.gnome-logs snap.gnome-system-monitor.gnome-system-monitor system_tor 2 profiles are in complain mode. libreoffice-oopslash libreoffice-soffice 3 processes have profiles defined. 3 processes are in enforce mode. /usr/lib/telepathy/mission-control-5 (3090) /usr/sbin/cupsd (1646) /usr/bin/tor (1861) system_tor 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. lee@lee-desktop:~$ 2.sudo /etc/init.d/apparmor restart lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. failed! lee@lee-desktop:~$ 3.sudo rm -rf /etc/apparmor.d/cache/* 4. sudo /etc/init.d/apparmor restart lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. failed! lee@lee-desktop:~$ Thanks, Lee ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apparmor 2.13.3-7ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 23:19:19 2020 InstallationDate: Installed on 2013-08-08 (2365 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=d2e1abc4-e044-467e-8cc2-57cbe4ef3115 ro drm.debug=0xe plymouth:debug SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1861250/+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.launchpa
[Touch-packages] [Bug 1946878] Re: Merge net-tools from Debian unstable for 22.04
Nothing to merge yet ** Changed in: net-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1946878 Title: Merge net-tools from Debian unstable for 22.04 Status in net-tools package in Ubuntu: Incomplete Bug description: Upstream: 1.60+git20210422.dfc41e0 Debian: 1.60+git20181103.0eebece-1 Ubuntu: 1.60+git20181103.0eebece-1ubuntu2 Debian updates this package infrequently, and last updated it 20.10. There is a new upstream version, however, so may be worth going ahead of debian and/or updating it in Debian and syncing it. ### New Debian Changes ### net-tools (1.60+git20181103.0eebece-1) unstable; urgency=medium * New upstream version 1.60+git20181103.0eebece - Fix nstrcmp() to prevent ifconfig from showing duplicate interfaces. (Closes: #812886) * Fix d/watch to point to upstream git repository * Add patch to fix decoding of MII vendor ids. (Closes: #549397) - Thanks, Ben Hutchings, for the patch. * Add patch to fix Japanese translation which uses a wrong Kanji character. (Closes: #621752) - Thanks, Takeshi Hamasaki, for the patch. * Add patch to fix wrong indentation of 'collisions' in the Japanese translation. (Closes: #653117) - Thanks, NODA, Kai, for the patch. * Fix Uploaders' field. - Add myself as an uploader. - Fix Tina's details. -- Utkarsh Gupta Fri, 02 Oct 2020 15:01:04 +0530 net-tools (1.60+git20180626.aebd88e-1) unstable; urgency=medium * New upstream snapshot * Refresh patches. * Fix typos in German manpages. Thanks to Prof. Dr. Steffen Wendzel and Dr. Tobias Quathamer for the patch. Closes: #900962. -- Martín Ferrari Mon, 24 Sep 2018 19:08:57 + net-tools (1.60+git20161116.90da8a0-4) unstable; urgency=medium * Update maintainer email address. Closes: #899617. * Update Standards-Version with no changes. -- Martín Ferrari Mon, 24 Sep 2018 17:16:31 + net-tools (1.60+git20161116.90da8a0-3) unstable; urgency=medium * debian/control: Update Vcs-* and Standards-Version. * debian/control: remove references to ancient package ja-trans. * debian/gbp.conf: Update repo layout. -- Martín Ferrari Tue, 31 Jul 2018 19:09:00 + net-tools (1.60+git20161116.90da8a0-2) unstable; urgency=medium * Fix typo in French manpage. Thanks to Michel Grigaut for the patch. * Add manpage for iptunnel, thanks to Sergio Durigan Junior. Closes: #88910 * Rename patches so CME does not choke on them. * Automated cme fixes; packaging improvements. * Remove unused and ancient patch. -- Martín Ferrari Sun, 11 Feb 2018 17:29:24 + net-tools (1.60+git20161116.90da8a0-1) unstable; urgency=medium * New upstream snapshot. * Re-synced translations.patch. * Acknowledge NMUs. Thanks a lot to Andrey Rahmatullin for the fixes and uploads. Closes: 846509. * Fix FTCBFS, thanks to Helmut Grohne for the patch. Closes: #811561. + Really assign CC for cross compilation. + Use triplet prefixed pkg-config. * Add debian/NEWS warning about changing output in net-tools commands. Closing bugs that reported problems in 3rd-party scripts arising from these changes. Closes: #845153, #843892, #820212. * Update Standards-Version, with no changes. -- Martín Ferrari Mon, 26 Dec 2016 05:58:42 + net-tools (1.60+git20150829.73cef8a-2.2) unstable; urgency=medium * Non-maintainer upload. * Apply an additional fix for the previous FTBFS for some architectures. -- Andrey Rahmatullin Thu, 01 Dec 2016 22:49:27 +0500 net-tools (1.60+git20150829.73cef8a-2.1) unstable; urgency=medium * Non-maintainer upload. * Fix FTBFS by applying the upstream patch (Closes: #844073). -- Andrey Rahmatullin Sun, 20 Nov 2016 15:23:12 +0500 net-tools (1.60+git20150829.73cef8a-2) unstable; urgency=medium [ Laurent Bigonville ] * Enable SELinux support. Closes: #666204. [ Martín Ferrari ] * Mark the package 'Multi-Arch: foreign', thanks to Frédéric Brière . Closes: #752584. * Fix bug in Portuguese man page, thanks to julianofisc...@gmail.com. Closes: #805377. -- Martín Ferrari Thu, 19 Nov 2015 14:48:47 + net-tools (1.60+git20150829.73cef8a-1) unstable; urgency=medium ### Old Ubuntu Delta ### net-tools (1.60+git20181103.0eebece-1ubuntu2) hirsute; urgency=medium * No change rebuild with fixed ownership. -- Dimitri John Ledkov Tue, 16 Feb 2021 15:18:30 + net-tools (1.60+git20181103.0eebece-1ubuntu1) hirsute; urgency=low * Merge from Debian unstable. Remaining changes: - Ubuntu_unit_conversion.patch: + Ubuntu Policy: output using standard SI unit multiples: KB (10^3), MB (
[Touch-packages] [Bug 1959015] Re: Switch to new HTTPS-capable domains for PPAs
** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Jammy) Importance: Undecided => Medium -- 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 Status in software-properties source package in Jammy: 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
[Touch-packages] [Bug 1955084] Re: systemd unit leaves a process running for the system lifetime but it only does anything at shutdown
** Also affects: unattended-upgrades (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: unattended-upgrades (Ubuntu Jammy) Importance: Undecided => High -- 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/1955084 Title: systemd unit leaves a process running for the system lifetime but it only does anything at shutdown Status in unattended-upgrades package in Ubuntu: New Status in unattended-upgrades source package in Jammy: New Bug description: The /lib/systemd/system/unattended-upgrades.service unit leaves a process, /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal, running from system start until shutdown. This increases the minimum memory footprint of every host, VM, or container where unattended-upgrades is installed. The motivation for having this systemd unit is clear in terms of the practicalities of implementing what this unit needs to do, but we should try to find some way to achieve this which does not rely on increasing the low water mark of system memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1955084/+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 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders
** Also affects: binutils (Ubuntu Jammy) Importance: Critical Status: New ** Also affects: xen (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags removed: rls-jj-incoming -- 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/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders Status in binutils: Confirmed Status in launchpad-buildd: New Status in binutils package in Ubuntu: New Status in xen package in Ubuntu: Invalid Status in binutils source package in Jammy: New Status in xen source package in Jammy: Invalid Status in binutils package in Debian: New Bug description: FTBFS in Jammy on LP infra: https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz Related PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages Summary: - Build reliably fails on LP - Build in local sbuild works reliably on my Laptop - Build in local VM (sizing like LP builders) works (other crashes but works) - Build on AMD server (chip more similar to LP) works reliably Failing step: On Launchpad build infrastructure it breaks on ld: $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0 --heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /<>/xen/.xen.efi.0x82d04000.0 && : Segmentation fault (core dumped --- Steps to recreate (result depends on platform) # you can grab the package from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4760/+packages sudo vim /etc/apt/sources.list sudo apt update sudo apt dist-upgrade -y sudo apt build-dep xen sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts apport-retrace sudo mkdir /mnt/build sudo chmod go+w /mnt/build cd /mnt/build # copy in things from host scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 ubuntu@:/mnt/build dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0 cd xen_4.16.0 dpkg-buildpackage -i -us -uc -b --- In a jammy VM 4cpu/8G I get some avx2 crashes but the build works: Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000] Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 0x7fa98d63c2d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x7fa98d6021e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x7fa98d602509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x7fa98d6033bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x562bdaaae3bf in ?? () #6 0x7fa98d2e8fd0 in __libc_start_call_main (main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58 #7 0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, argc=8, argv=0x7ffc797f2968, init=, fini=, rtld_fini=, stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409 #8 0x562bdaaad515 in ?? () ^^ that is a different crash than on th LP builders ! And despite those crashes the build does appear to work oO?! The same crashes I see on my local sbuild runs, the full set of one build is Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in libc.so.6[7f566e74+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in libc.so.6[7fbba2571000+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in libc.so.6[7fe368044000+194000] Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 ip 7f241f4
[Touch-packages] [Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work
** Also affects: initramfs-tools (Ubuntu Jammy) Importance: Critical Status: Confirmed ** Tags removed: rls-jj-incoming -- 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/1958594 Title: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools source package in Jammy: Confirmed Bug description: [Bug description] On a jammy installation, which was upgraded from focal, after a full- upgrade and a reboot, I enter the LUKS password to decrypt the disk. Then I get the following error: libgcc_s.so.1 must be installed for pthread_exit to work After the error is shown, the system asks for the password again (which never works, always throwing the same error). [Root cause] I was able to decrypt the disk with the same password by booting from a live usb. Which allowed further investigation. The error shown in the LUKS password prompt menu comes from https://github.com/bminor/glibc/blob/glibc-2.34/nptl/pthread_exit.c#L31-L32, which indeed shows that pthread_exit fails when libgcc_s.so.1 is missing. From https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/hook-functions?h=import/0.140ubuntu10#n260, we noticed that libgcc_s.so.1 is only copied if 1) copy_exec is called for a binary directly linked to libgcc_s.so.1, or 2) copy_exec is called for a binary linked to libpthread The cryptsetup initramfs hook, calls copy_exec for /sbin/cryptsetup, which is linked to libargon2.so.1, which is linked to libpthread.so.0. This covers case (2) above. As a consequence, libgcc_s.so.1 is copied to the initrd image and the error reported here is not seen. However, since glibc 2.34, libpthread is shipped within glibc, and the binaries are no longer linked to libpthread.so.0. As a consequence, an argon2 package built with glibc 2.32 will no longer be linked to libpthread.so.0 and libgcc_s.so.1 will no longer be copied to the initrd image. Triggering the reported error. This can be verified in these two argon2 builds, from the same sources, but with different glibc versions: https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build21.04.0/+build/21066610 https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build22/+build/22255217 Still lvm2 is a seeded package, which Recommends thin-provisioning- tools. thin-provisioning-tools ships a initramfs hook that calls copy_exec for /usr/sbin/pdata_tools, which is directly linked to libgcc_s.so.1. This covers the case (1) above and should suffice to ensure the boot process works properly. Since thin-provisioning-tools is just a recommends for lvm2, it could be removed from the system (and indeed, for some reason, was not present in my focal=>jammy installation). In this case, a new kernel installation should trigger the reported error. [Reproducer] - Install jammy with a LUKS encrypted disk - remove thin-provisioning-tools - perform a full-upgrade (make sure the kernel was upgraded or run update-initramfs manually) - reboot and verify you can no longer get past the decrypt password prompt screen [Workaround] A workaround for anyone affected would be to install thin- provisioning-tools and run update-initramfs. [Impact] Users upgrading from focal to jammy will eventually be locked out of their systems in case they are using LUKS encryption. [Additional information] While this issue is similar to https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861757, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254, and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950551, This is a different bug, with a different root cause. Thanks to sergiodj for the pairing session on the root cause analysis. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958594/+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 1958710] Re: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main)
the definition of the serie we want to use is a manual process, it has been updated now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1958710 Title: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main) Status in network-manager package in Ubuntu: Triaged Bug description: There are some differences between versions from Debian and Ubuntu. A new version has been released a week ago. Debian Changelog: network-manager (1.34.0-2) unstable; urgency=medium * Demote wpasupplicant to Recommends. There are enough use cases for network-manager not involving Wi-Fi which justifies to make this dependency optional. (Closes: #919619, #980218) -- Michael Biebl Tue, 18 Jan 2022 20:59:36 +0100 network-manager (1.34.0-1) unstable; urgency=medium * New upstream version 1.34.0 * Rebase patches * Install nm-priv-helper service * Update symbols file for libnm0 -- Michael Biebl Fri, 14 Jan 2022 00:18:58 +0100 NM ChangeLog: = NetworkManager-1.34 Overview of changes since NetworkManager-1.32 = * initrd: wait for both IPv4 and IPv6 with "ip=dhcp,dhcp6". * core: better handle sd-resolved errors when resolving hostnames. * nmcli: fix import WireGuard profile with DNS domain and address family disabled. * ndisc: send router solicitations before expiry. * policy: send earlier the ip configs to the DNS manager. * core: support linking with LLD 13. * wireguard: importing wg-quick configuration files with nmcli no longer sets a negative, exclusive "dns-priority". This plays better with common split DNS setups that use systemd-resolved. Adjust the "dns-priority" to your liking after import yourself. * NetworkManager no longer listens for netlink events for traffic control objects (qdiscs and filters). * core: add internal nm-priv-helper service for separating privileges and have a way to drop capabilities from NetworkManager daemon. * bond: add support for setting queue-id of bond port. * dns: support configuring DNS over TLS (DoT) with systemd-resolved. * nmtui: add support for WireGuard profiles. * nmcli: add aliases `nmcli device up|down` beside connect|disconnect. * conscious language: Deprecate 'Device.Slaves' D-Bus property in favor of new 'Device.Ports' property. Depracate 'nm_device_*_get_slaves()' in favor of 'nm_device_get_ports()' in libnm. * nmcli: invoking nmcli command without arguments will now show 'default' instead of null address in route4 or route6 section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1958710/+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 1959015] Re: Switch to new HTTPS-capable domains for PPAs
** Tags added: fr-2003 -- 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
[Touch-packages] [Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work
** Tags added: fr-2002 -- 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/1958594 Title: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work Status in initramfs-tools package in Ubuntu: Confirmed Bug description: [Bug description] On a jammy installation, which was upgraded from focal, after a full- upgrade and a reboot, I enter the LUKS password to decrypt the disk. Then I get the following error: libgcc_s.so.1 must be installed for pthread_exit to work After the error is shown, the system asks for the password again (which never works, always throwing the same error). [Root cause] I was able to decrypt the disk with the same password by booting from a live usb. Which allowed further investigation. The error shown in the LUKS password prompt menu comes from https://github.com/bminor/glibc/blob/glibc-2.34/nptl/pthread_exit.c#L31-L32, which indeed shows that pthread_exit fails when libgcc_s.so.1 is missing. From https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/hook-functions?h=import/0.140ubuntu10#n260, we noticed that libgcc_s.so.1 is only copied if 1) copy_exec is called for a binary directly linked to libgcc_s.so.1, or 2) copy_exec is called for a binary linked to libpthread The cryptsetup initramfs hook, calls copy_exec for /sbin/cryptsetup, which is linked to libargon2.so.1, which is linked to libpthread.so.0. This covers case (2) above. As a consequence, libgcc_s.so.1 is copied to the initrd image and the error reported here is not seen. However, since glibc 2.34, libpthread is shipped within glibc, and the binaries are no longer linked to libpthread.so.0. As a consequence, an argon2 package built with glibc 2.32 will no longer be linked to libpthread.so.0 and libgcc_s.so.1 will no longer be copied to the initrd image. Triggering the reported error. This can be verified in these two argon2 builds, from the same sources, but with different glibc versions: https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build21.04.0/+build/21066610 https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build22/+build/22255217 Still lvm2 is a seeded package, which Recommends thin-provisioning- tools. thin-provisioning-tools ships a initramfs hook that calls copy_exec for /usr/sbin/pdata_tools, which is directly linked to libgcc_s.so.1. This covers the case (1) above and should suffice to ensure the boot process works properly. Since thin-provisioning-tools is just a recommends for lvm2, it could be removed from the system (and indeed, for some reason, was not present in my focal=>jammy installation). In this case, a new kernel installation should trigger the reported error. [Reproducer] - Install jammy with a LUKS encrypted disk - remove thin-provisioning-tools - perform a full-upgrade (make sure the kernel was upgraded or run update-initramfs manually) - reboot and verify you can no longer get past the decrypt password prompt screen [Workaround] A workaround for anyone affected would be to install thin- provisioning-tools and run update-initramfs. [Impact] Users upgrading from focal to jammy will eventually be locked out of their systems in case they are using LUKS encryption. [Additional information] While this issue is similar to https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861757, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254, and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950551, This is a different bug, with a different root cause. Thanks to sergiodj for the pairing session on the root cause analysis. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958594/+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 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders
** Tags added: fr-2001 -- 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/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders Status in binutils: Confirmed Status in launchpad-buildd: New Status in binutils package in Ubuntu: New Status in xen package in Ubuntu: Invalid Status in binutils package in Debian: New Bug description: FTBFS in Jammy on LP infra: https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz Related PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages Summary: - Build reliably fails on LP - Build in local sbuild works reliably on my Laptop - Build in local VM (sizing like LP builders) works (other crashes but works) - Build on AMD server (chip more similar to LP) works reliably Failing step: On Launchpad build infrastructure it breaks on ld: $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0 --heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /<>/xen/.xen.efi.0x82d04000.0 && : Segmentation fault (core dumped --- Steps to recreate (result depends on platform) # you can grab the package from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4760/+packages sudo vim /etc/apt/sources.list sudo apt update sudo apt dist-upgrade -y sudo apt build-dep xen sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts apport-retrace sudo mkdir /mnt/build sudo chmod go+w /mnt/build cd /mnt/build # copy in things from host scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 ubuntu@:/mnt/build dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0 cd xen_4.16.0 dpkg-buildpackage -i -us -uc -b --- In a jammy VM 4cpu/8G I get some avx2 crashes but the build works: Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000] Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 0x7fa98d63c2d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x7fa98d6021e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x7fa98d602509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x7fa98d6033bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x562bdaaae3bf in ?? () #6 0x7fa98d2e8fd0 in __libc_start_call_main (main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58 #7 0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, argc=8, argv=0x7ffc797f2968, init=, fini=, rtld_fini=, stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409 #8 0x562bdaaad515 in ?? () ^^ that is a different crash than on th LP builders ! And despite those crashes the build does appear to work oO?! The same crashes I see on my local sbuild runs, the full set of one build is Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in libc.so.6[7f566e74+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in libc.so.6[7fbba2571000+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in libc.so.6[7fe368044000+194000] Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 ip 7f241f455f3d sp 7ffd05c2e7c8 error 4 in libc.so.6[7f241f2e2000+194000] Jan 19 07:44:57 Keschdeichel kernel: x86_64-linux-gn[4171794]: segfault at 0 ip 7fcbe1f2bf3d sp 7fff62005aa8 error 4 in libc.so.6[7fcbe1db8000+194000] Jan 19 07:44:57 Keschdeichel kernel: x86_64-l
[Touch-packages] [Bug 1840375] Re: groupdel doesn't support extrausers
This bug was fixed in the package shadow - 1:4.5-1ubuntu2.2
---
shadow (1:4.5-1ubuntu2.2) bionic-security; urgency=medium
* SECURITY UPDATE: Access to privileged information
- debian/patches/CVE-2018-7169.patch: newgidmap:
enforce setgroups=deny if self-mapping a group in
src/newgidmap.c.
- CVE-2018-7169
-- Leonidas Da Silva Barbosa Tue, 25 Jan
2022 13:26:21 -0300
** Changed in: shadow (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-7169
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1840375
Title:
groupdel doesn't support extrausers
Status in snapd:
Fix Released
Status in shadow package in Ubuntu:
Fix Released
Status in shadow source package in Xenial:
Fix Committed
Status in shadow source package in Bionic:
Fix Released
Status in shadow source package in Disco:
Won't Fix
Bug description:
snapd needs the ability to call 'groupdel --extrausers foo' to clean
up after itself, but --extrausers is currently unsupported.
[Impact]
On ubuntu-core systems we want to be able to manage "extrausers" in the same
way as regular users. This requires updates to the various
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.
This is an important feature for Ubuntu Core
[Test Case]
0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
1. install the libnss-extrausers and add "extrauers" to the passwd and shadow
line (see /usr/share/doc/libnss-extrausers/README for the modifications in
sswitch.conf)
2. run "groupadd --extrausers foo" and verify "grep foo
/var/lib/extrausers/group"
3 check /var/lib/extrausers/group for the new "foo" group
4. run "groupdel --extrausers foo"
5. check /var/lib/extrausers/group and ensure the "foo" group is removed
[Regression Potential]
* low: this adds a new (optional) option which is off by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840375/+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 1952107] Re: Google Contacts API Deprecated
Same here. 3.36.5-0ubuntu2 in focal. "Connecting to address book failed: Unauthorized" ** Attachment added: "Screenshot from 2021-10-17 08-18-38.png" https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1952107/+attachment/5557805/+files/Screenshot%20from%202021-10-17%2008-18-38.png -- 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
Re: [Touch-packages] [Bug 1574354] Re: playing .mp4 in VLC freezes machine
Toimii nykyisin. Works now. Thanks. Juha to 27. tammik. 2022 klo 15.35 Timo Aaltonen (1574...@bugs.launchpad.net) kirjoitti: > vlc works just fine on several machines here, closing > > if you have further issues, open a new bug > > ** Changed in: mesa (Ubuntu) >Status: Confirmed => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1574354 > > Title: > playing .mp4 in VLC freezes machine > > Status in mesa package in Ubuntu: > Invalid > > Bug description: > VLC was running fine on 15.10 but since upgrading, video files (e.g. > .mp4) play for a few minutes and then crash the whole machine (i.e. I > have to power off and on). Possibly linked is that audio (in web pages > or playing audio files thru Banshee) loops (stutters) for about a > second every few minutes (but doesn't crash the machine). > > vlc-nox: /usr/bin/vlc > > Description: Ubuntu 16.04 LTS > Release: 16.04 > > vlc: > Installed: 2.2.2-5 > Candidate: 2.2.2-5 > Version table: >*** 2.2.2-5 500 > 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 > Packages > 100 /var/lib/dpkg/status > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: vlc 2.2.2-5 > ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 > Uname: Linux 4.4.0-21-generic x86_64 > NonfreeKernelModules: wl > ApportVersion: 2.20.1-0ubuntu2 > Architecture: amd64 > CurrentDesktop: Unity > Date: Sun Apr 24 19:20:41 2016 > InstallationDate: Installed on 2014-02-17 (797 days ago) > InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 > (20131016.1) > ProcEnviron: >LANGUAGE=en_GB:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_GB.UTF-8 >SHELL=/bin/bash > SourcePackage: vlc > UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+subscriptions > > -- --J.K-- -- 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/1574354 Title: playing .mp4 in VLC freezes machine Status in mesa package in Ubuntu: Invalid Bug description: VLC was running fine on 15.10 but since upgrading, video files (e.g. .mp4) play for a few minutes and then crash the whole machine (i.e. I have to power off and on). Possibly linked is that audio (in web pages or playing audio files thru Banshee) loops (stutters) for about a second every few minutes (but doesn't crash the machine). vlc-nox: /usr/bin/vlc Description: Ubuntu 16.04 LTS Release: 16.04 vlc: Installed: 2.2.2-5 Candidate: 2.2.2-5 Version table: *** 2.2.2-5 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.2-5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 19:20:41 2016 InstallationDate: Installed on 2014-02-17 (797 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+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 1952970] Re: mesa GLX change leads to wine showing GLXBadFBConfig
looks like it's still unresolved upstream ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1952970 Title: mesa GLX change leads to wine showing GLXBadFBConfig Status in mesa package in Ubuntu: Confirmed Bug description: A mesa GLX change (somewhere between the 20.0.4 and 21.0.3) causes both wine and Proton (on an older system that does not have Vulkan.. SandyBridge, OpenGL 3.3..) to exit with GLXBadFBConf when it tries to fire up OpenGL. Wine, for Direct3D support it tries to fire up (in order) Vulkan then progressively older OpenGL versions fro 4.5 down to 2.1 or maybe even 1.4 (of course the older the OpenGL the lower supported Direct3D version). Wine does not like getting an error back with the same transaction serial number as it sent out. See https://gitlab.freedesktop.org/mesa/mesa/-/issues/3969 Mesa issue 3969, The patch there throws in an "XNoOp()" to increment the transaction serial number. But the patch there caused issues in other apps, per https://gitlab.freedesktop.org/mesa/mesa/-/issues/4763 Mes issue 4763, They found XNoOp() increments the serial number, but xcb keeps a "shadow copy" of the serial number which is not incremented, causing problems. XFlush() increments the serial number, keeps xcb in sync and happy, with no real side effects (running XFlush() frequently would slow things down, but this code only runs when a GLX context is being created anyway which just doesn't happen all that frequently.) Please find attached a patch implementing the updated patch suggested in issue 4763. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libglx-mesa0 21.0.3-0ubuntu0.3~20.04.5 ProcVersionSignature: Ubuntu 5.13.0-22.22~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-22-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: GNOME-Flashback:GNOME Date: Wed Dec 1 18:59:43 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Dell Picasso [1028:0a12] InstallationDate: Installed on 2020-05-05 (575 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 3505 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=57669cb0-fd65-4eb0-9898-ed10f33d44d0 ro quiet splash nvme_core.io_timeout=300 nosmt vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.7 dmi.board.asset.tag: not specified dmi.board.name: 0RV9WY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.7 dmi.modalias: dmi:bvnDellInc.:bvr1.4.7:bd05/31/2021:br5.3:svnDellInc.:pnInspiron3505:pvr1.4.7:rvnDellInc.:rn0RV9WY:rvrA00:cvnDellInc.:ct10:cvr1.4.7:sku0A12: dmi.product.family: Inspiron dmi.product.name: Inspiron 3505 dmi.product.sku: 0A12 dmi.product.version: 1.4.7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.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.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+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 1574354] Re: playing .mp4 in VLC freezes machine
vlc works just fine on several machines here, closing if you have further issues, open a new bug ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- 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/1574354 Title: playing .mp4 in VLC freezes machine Status in mesa package in Ubuntu: Invalid Bug description: VLC was running fine on 15.10 but since upgrading, video files (e.g. .mp4) play for a few minutes and then crash the whole machine (i.e. I have to power off and on). Possibly linked is that audio (in web pages or playing audio files thru Banshee) loops (stutters) for about a second every few minutes (but doesn't crash the machine). vlc-nox: /usr/bin/vlc Description: Ubuntu 16.04 LTS Release: 16.04 vlc: Installed: 2.2.2-5 Candidate: 2.2.2-5 Version table: *** 2.2.2-5 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.2-5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 19:20:41 2016 InstallationDate: Installed on 2014-02-17 (797 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+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 1959211] Re: Please merge dbus 1.12.20-3 from Debian unstable
Attaching patch against Debian unstable. For ease of review, relevant commits and tags have been pushed to the following repository: https://code.launchpad.net/~waveform/ubuntu/+source/dbus/+git/dbus Specifically: * logical/1.12.20-2ubuntu2 represents our split-out delta on top of old/debian (1.12.20-2) * logical/1.12.20-3ubuntu1 represents our rebased delta on top of new/debian (1.12.20-3) * merge/1.12.20-3ubuntu1 just adds changelog and maintainer changes on top of logical/1.12.20-3ubuntu1 Hence, the following command may produce output useful to the purposes of review: git range-diff old/debian..logical/1.12.20-2ubuntu2 new/debian..logical/1.12.20-3ubuntu1 ** Patch added: "1-1959211.debdiff" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+attachment/5557772/+files/1-1959211.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1959211 Title: Please merge dbus 1.12.20-3 from Debian unstable Status in dbus package in Ubuntu: New Bug description: Please merge dbus 1.12.20-3 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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 1959211] [NEW] Please merge dbus 1.12.20-3 from Debian unstable
Public bug reported: Please merge dbus 1.12.20-3 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. ** Affects: dbus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1959211 Title: Please merge dbus 1.12.20-3 from Debian unstable Status in dbus package in Ubuntu: New Bug description: Please merge dbus 1.12.20-3 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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 1959085] Re: Ubuntu 21.10 boot stuck in initramfs
I'm guessing that this might be the right package if you want to investigate this further. ** Package changed: ubuntu => initramfs-tools (Ubuntu) -- 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/1959085 Title: Ubuntu 21.10 boot stuck in initramfs Status in initramfs-tools package in Ubuntu: New Bug description: Hi, I just installed the latest Ubuntu desktop from iso file ubuntu-21.10-desktop-amd64.iso inside of VMWare workstation. I chose ZFS and native ZFS encryption of the filesystem. The installation went fine. Everything worked as expected. Then I upgraded the packages to the latest version via the Software updater. After reboot I'm stuck in the initramfs prompt. The following command fails: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_gtw63h /root// Permission denied. And the system never asks me for the password to unlock the root fs. So, I'm guessing that there is something wrong with the new initramfs disk: initrd.img-5.13.0-27-generic When I reboot and select the previous version in grub: initrd.img-5.13.0-27-generic, the system asks for the password and boots without a problem. Thanks. To summarize: 1. Installed new VM using the Ubuntu iso image. Chose ZFS native encryption. Minimal install. 2. As soon as the system came up, I hit the update/upgrade prompt. Rebooted and failed to boot the new version. I didn't customize anything or installed anything extra. root@ubud01:/var# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@ubud01:/var# dpkg -l | grep zfs ii libzfs4linux 2.0.6-1ubuntu2 amd64OpenZFS filesystem library for Linux ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed2.0.6-1ubuntu2 amd64OpenZFS Event Daemon ii zfsutils-linux 2.0.6-1ubuntu2 amd64command-line tools to manage OpenZFS filesystems root@ubud01:/var# dpkg -l | grep init ii busybox-initramfs 1:1.30.1-6ubuntu3.1 amd64Standalone shell setup for initramfs ii cryptsetup-initramfs 2:2.3.6-0ubuntu1 all disk encryption support - initramfs integration ii gnome-initial-setup40.4-1ubuntu1 amd64Initial GNOME system setup helper ii init 1.60build1 amd64metapackage ensuring an init system is installed ii init-system-helpers1.60build1 all helper tools for all init systems ii initramfs-tools0.140ubuntu6 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu6 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu6 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.4-1.1ubuntu3.1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.8-6.1ubuntu2 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu3 all Linux Standard Base init script functionality ii ncurses-base 6.2+20201114-2build1 all basic terminal type definitions ii sysvinit-utils 2.96-7ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu3 amd64X server initialisation tool ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs root@ubud01:/var# zfs list NAME USED AVAIL REFER MOUNTPOINT bpool 290M 542M 96K /boot bpool/BOOT 289M 542M 96K none bpool/BOOT/ubuntu_gtw63h 288M 542M 156M /boot rpool 6.39G 10.6G 192K / r
[Touch-packages] [Bug 1959085] [NEW] Ubuntu 21.10 boot stuck in initramfs
You have been subscribed to a public bug: Hi, I just installed the latest Ubuntu desktop from iso file ubuntu-21.10-desktop-amd64.iso inside of VMWare workstation. I chose ZFS and native ZFS encryption of the filesystem. The installation went fine. Everything worked as expected. Then I upgraded the packages to the latest version via the Software updater. After reboot I'm stuck in the initramfs prompt. The following command fails: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_gtw63h /root// Permission denied. And the system never asks me for the password to unlock the root fs. So, I'm guessing that there is something wrong with the new initramfs disk: initrd.img-5.13.0-27-generic When I reboot and select the previous version in grub: initrd.img-5.13.0-27-generic, the system asks for the password and boots without a problem. Thanks. To summarize: 1. Installed new VM using the Ubuntu iso image. Chose ZFS native encryption. Minimal install. 2. As soon as the system came up, I hit the update/upgrade prompt. Rebooted and failed to boot the new version. I didn't customize anything or installed anything extra. root@ubud01:/var# lsb_release -rd Description:Ubuntu 21.10 Release:21.10 root@ubud01:/var# dpkg -l | grep zfs ii libzfs4linux 2.0.6-1ubuntu2 amd64OpenZFS filesystem library for Linux ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed2.0.6-1ubuntu2 amd64OpenZFS Event Daemon ii zfsutils-linux 2.0.6-1ubuntu2 amd64command-line tools to manage OpenZFS filesystems root@ubud01:/var# dpkg -l | grep init ii busybox-initramfs 1:1.30.1-6ubuntu3.1 amd64Standalone shell setup for initramfs ii cryptsetup-initramfs 2:2.3.6-0ubuntu1 all disk encryption support - initramfs integration ii gnome-initial-setup40.4-1ubuntu1 amd64Initial GNOME system setup helper ii init 1.60build1 amd64metapackage ensuring an init system is installed ii init-system-helpers1.60build1 all helper tools for all init systems ii initramfs-tools0.140ubuntu6 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu6 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu6 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.4-1.1ubuntu3.1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.8-6.1ubuntu2 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu3 all Linux Standard Base init script functionality ii ncurses-base 6.2+20201114-2build1 all basic terminal type definitions ii sysvinit-utils 2.96-7ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu3 amd64X server initialisation tool ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs root@ubud01:/var# zfs list NAME USED AVAIL REFER MOUNTPOINT bpool 290M 542M 96K /boot bpool/BOOT 289M 542M 96K none bpool/BOOT/ubuntu_gtw63h 288M 542M 156M /boot rpool 6.39G 10.6G 192K / rpool/ROOT5.64G 10.6G 192K none rpool/ROOT/ubuntu_gtw63h 5.64G 10.6G 3.45G / rpool/ROOT/ubuntu_gtw63h/srv 192K 10.6G 192K /srv rpool/ROOT/ubuntu_gtw63h/usr 660K 10.6G 192K /usr rpool/ROOT/ubuntu_gtw63h/usr/local 468K 10.6G 388K /usr/local rpool/ROOT/ubuntu_gtw63h/var 1.53G 10.6G 192K /var rpool/ROOT/ubuntu_gtw63h/var/games
[Touch-packages] [Bug 1952107] Re: Google Contacts API Deprecated
The same here. Upgraded to 3.36.5-0ubuntu2 in focal. When starting Evolution I get "Connecting to address book failed: Unauthorized". Pressing button [Reconnect] clears the message but Address book is 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 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders
** Changed in: binutils (Debian) Status: Unknown => New -- 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/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders Status in binutils: Confirmed Status in launchpad-buildd: New Status in binutils package in Ubuntu: New Status in xen package in Ubuntu: Invalid Status in binutils package in Debian: New Bug description: FTBFS in Jammy on LP infra: https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz Related PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages Summary: - Build reliably fails on LP - Build in local sbuild works reliably on my Laptop - Build in local VM (sizing like LP builders) works (other crashes but works) - Build on AMD server (chip more similar to LP) works reliably Failing step: On Launchpad build infrastructure it breaks on ld: $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0 --heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /<>/xen/.xen.efi.0x82d04000.0 && : Segmentation fault (core dumped --- Steps to recreate (result depends on platform) # you can grab the package from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4760/+packages sudo vim /etc/apt/sources.list sudo apt update sudo apt dist-upgrade -y sudo apt build-dep xen sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts apport-retrace sudo mkdir /mnt/build sudo chmod go+w /mnt/build cd /mnt/build # copy in things from host scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 ubuntu@:/mnt/build dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0 cd xen_4.16.0 dpkg-buildpackage -i -us -uc -b --- In a jammy VM 4cpu/8G I get some avx2 crashes but the build works: Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000] Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 0x7fa98d63c2d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x7fa98d6021e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x7fa98d602509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x7fa98d6033bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x562bdaaae3bf in ?? () #6 0x7fa98d2e8fd0 in __libc_start_call_main (main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58 #7 0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, argc=8, argv=0x7ffc797f2968, init=, fini=, rtld_fini=, stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409 #8 0x562bdaaad515 in ?? () ^^ that is a different crash than on th LP builders ! And despite those crashes the build does appear to work oO?! The same crashes I see on my local sbuild runs, the full set of one build is Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in libc.so.6[7f566e74+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in libc.so.6[7fbba2571000+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in libc.so.6[7fe368044000+194000] Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 ip 7f241f455f3d sp 7ffd05c2e7c8 error 4 in libc.so.6[7f241f2e2000+194000] Jan 19 07:44:57 Keschdeichel kernel: x86_64-linux-gn[4171794]: segfault at 0 ip 7fcbe1f2bf3d sp 7fff62005aa8 error 4 in libc.so.6[7fcbe1db8000+194000] Jan 1
[Touch-packages] [Bug 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders
Launchpad has imported 1 comments from the remote bug at https://sourceware.org/bugzilla/show_bug.cgi?id=28826. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2022-01-27T11:12:58+00:00 Matthias Klose wrote: seen with the 2.38 branch 20220123 and 20220126, https://bugs.debian.org/1004269 https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1958389 The Debian report contains the more useful stack trace. The Ubuntu report suggests that this is only seen on Intel hardware, not AMD hardware. Reply at: https://bugs.launchpad.net/launchpad- buildd/+bug/1958389/comments/12 ** Changed in: binutils Status: Unknown => Confirmed ** Changed in: binutils Importance: Unknown => Medium -- 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/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders Status in binutils: Confirmed Status in launchpad-buildd: New Status in binutils package in Ubuntu: New Status in xen package in Ubuntu: Invalid Status in binutils package in Debian: Unknown Bug description: FTBFS in Jammy on LP infra: https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz Related PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages Summary: - Build reliably fails on LP - Build in local sbuild works reliably on my Laptop - Build in local VM (sizing like LP builders) works (other crashes but works) - Build on AMD server (chip more similar to LP) works reliably Failing step: On Launchpad build infrastructure it breaks on ld: $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0 --heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /<>/xen/.xen.efi.0x82d04000.0 && : Segmentation fault (core dumped --- Steps to recreate (result depends on platform) # you can grab the package from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4760/+packages sudo vim /etc/apt/sources.list sudo apt update sudo apt dist-upgrade -y sudo apt build-dep xen sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts apport-retrace sudo mkdir /mnt/build sudo chmod go+w /mnt/build cd /mnt/build # copy in things from host scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 ubuntu@:/mnt/build dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0 cd xen_4.16.0 dpkg-buildpackage -i -us -uc -b --- In a jammy VM 4cpu/8G I get some avx2 crashes but the build works: Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000] Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 0x7fa98d63c2d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x7fa98d6021e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x7fa98d602509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x7fa98d6033bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x562bdaaae3bf in ?? () #6 0x7fa98d2e8fd0 in __libc_start_call_main (main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58 #7 0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, argc=8, argv=0x7ffc797f2968, init=, fini=, rtld_fini=, stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409 #8 0x562bdaaad515 in ?? () ^^ that is a different crash than on th LP builders ! And despite those crashes the build does appear to work oO?! The s
[Touch-packages] [Bug 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders
** Bug watch added: Sourceware.org Bugzilla #28826 https://sourceware.org/bugzilla/show_bug.cgi?id=28826 ** Also affects: binutils via https://sourceware.org/bugzilla/show_bug.cgi?id=28826 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1004269 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004269 ** Also affects: binutils (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004269 Importance: Unknown Status: Unknown -- 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/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders Status in binutils: Unknown Status in launchpad-buildd: New Status in binutils package in Ubuntu: New Status in xen package in Ubuntu: Invalid Status in binutils package in Debian: Unknown Bug description: FTBFS in Jammy on LP infra: https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz Related PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages Summary: - Build reliably fails on LP - Build in local sbuild works reliably on my Laptop - Build in local VM (sizing like LP builders) works (other crashes but works) - Build on AMD server (chip more similar to LP) works reliably Failing step: On Launchpad build infrastructure it breaks on ld: $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0 --heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /<>/xen/.xen.efi.0x82d04000.0 && : Segmentation fault (core dumped --- Steps to recreate (result depends on platform) # you can grab the package from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4760/+packages sudo vim /etc/apt/sources.list sudo apt update sudo apt dist-upgrade -y sudo apt build-dep xen sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts apport-retrace sudo mkdir /mnt/build sudo chmod go+w /mnt/build cd /mnt/build # copy in things from host scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 ubuntu@:/mnt/build dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0 cd xen_4.16.0 dpkg-buildpackage -i -us -uc -b --- In a jammy VM 4cpu/8G I get some avx2 crashes but the build works: Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000] Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 0x7fa98d63c2d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x7fa98d6021e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x7fa98d602509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x7fa98d6033bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x562bdaaae3bf in ?? () #6 0x7fa98d2e8fd0 in __libc_start_call_main (main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58 #7 0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, argc=8, argv=0x7ffc797f2968, init=, fini=, rtld_fini=, stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409 #8 0x562bdaaad515 in ?? () ^^ that is a different crash than on th LP builders ! And despite those crashes the build does appear to work oO?! The same crashes I see on my local sbuild runs, the full set of one build is Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in libc.so.6[7f566e74+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in libc.so.6[7fbba2571000+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[413
[Touch-packages] [Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange
That PR is still pending review, no movements there unfortunately. -- 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: private host key #0: ssh-rsa SHA256:REDACTED debug1: private host key #1: ecdsa-sha2-nistp256 SHA256:R
[Touch-packages] [Bug 1958642] Re: New 2.37.50.20220119-0ubuntu1 Produces RWE load header on s390x
** Changed in: binutils (Debian) Status: Confirmed => 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: Fix Released 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 1848237] Re: amd64-only test running on i386
Fixed generally in 1.6.0-5
** Changed in: python-pyeclib (Ubuntu)
Status: New => Fix Released
--
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/1848237
Title:
amd64-only test running on i386
Status in python-pyeclib package in Ubuntu:
Fix Released
Status in six package in Ubuntu:
Invalid
Bug description:
Some tests in d/t/control are not meant to be run on non-amd64 architectures.
The test script tries to detect this and skip them:
arch = platform.machine()
if sys.argv[1].startswith('isa_') and arch == 'x86_64':
print("Skipping {} test for {} architecture".format(sys.argv[1], arch))
else:
...
In eoan, at some point during the development cycle, the VM running i386
tests is actually on an amd64 kernel:
"""
...
-name adt-eoan-i386-python-pyeclib-20191014-091043 --image
adt/ubuntu-eoan-i386-server
...
Get:5 http://ftpmaster.internal/ubuntu eoan-proposed/universe Sources [127 kB]
Get:6 http://ftpmaster.internal/ubuntu eoan-proposed/main amd64 Packages
[18.0 kB]
Get:7 http://ftpmaster.internal/ubuntu eoan-proposed/main i386 Packages [12.9
kB]
...
linux-generic:amd64 is already the newest version (5.3.0.18.21).
...
utopkgtest [09:11:51]: testbed running kernel: Linux 5.3.0-18-generic
#19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019
autopkgtest [09:11:51]: testbed dpkg architecture: i386
"""
In such an environment, platform.machine() will return "x86_64", and the test
will be run, but fail:
autopkgtest [09:22:26]: test command7: python debian/tests/encode-decode.py
isa_l_rs_vand
autopkgtest [09:22:26]: test command7: [---
Traceback (most recent call last):
File "debian/tests/encode-decode.py", line 15, in
ec = ECDriver(k=3, m=3, hd=3, ec_type=sys.argv[1])
File "/usr/lib/python2.7/dist-packages/pyeclib/ec_iface.py", line 212, in
__init__
validate=int(self.validate)
File "/usr/lib/python2.7/dist-packages/pyeclib/utils.py", line 73, in
create_instance
instance = object_class(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pyeclib/core.py", line 61, in
__init__
validate)
pyeclib.ec_iface.ECBackendInstanceNotAvailable: pyeclib_c_init ERROR: Backend
instance not found. Please inspect syslog for liberasurecode error report.
init: autopkgtest [09:22:26]: test command7: ---]
It's probably best to use "dpkg --architecture" for this check.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pyeclib/+bug/1848237/+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 889889] Re: Use PNG or SVG instead of GIF
Marking the charset task as invalid - 4.0.0 does not appear to have any gif files. ** Changed in: chardet (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/889889 Title: Use PNG or SVG instead of GIF Status in Adium Theme Ubuntu: Fix Released Status in OpenSSL: New Status in ace package in Ubuntu: New Status in app-install-data-ubuntu package in Ubuntu: Confirmed Status in blender package in Ubuntu: Fix Released Status in chardet package in Ubuntu: Invalid Status in cups package in Ubuntu: New Status in dvd+rw-tools package in Ubuntu: New Status in foo2zjs package in Ubuntu: New Status in libcgi-pm-perl package in Ubuntu: New Status in openssl package in Ubuntu: Won't Fix Status in python3.4 package in Ubuntu: Won't Fix Status in software-center package in Ubuntu: Invalid Bug description: Use modern file formats such as PNG or SVG instead of the legacy GIF file formats. $ find /usr -name "*.gif" To manage notifications about this bug go to: https://bugs.launchpad.net/adium-theme-ubuntu/+bug/889889/+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 1443527] Re: package python-chardet 2.0.1-2build1 failed to install/upgrade: package python-chardet is already installed and configured
Closing this bug as it related to a Ubuntu release with is EOL - please re-open if its still a problem. ** Changed in: chardet (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/1443527 Title: package python-chardet 2.0.1-2build1 failed to install/upgrade: package python-chardet is already installed and configured Status in chardet package in Ubuntu: Won't Fix Bug description: no information ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-chardet ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic i686 ApportVersion: 2.14.1-0ubuntu3.8 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: i386 Date: Mon Apr 13 21:40:48 2015 DuplicateSignature: package:python-chardet:2.0.1-2build1:package python-chardet is already installed and configured ErrorMessage: package python-chardet is already installed and configured InstallationDate: Installed on 2015-04-13 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) PackageArchitecture: all SourcePackage: chardet Title: package python-chardet 2.0.1-2build1 failed to install/upgrade: package python-chardet is already installed and configured UpgradeStatus: Upgraded to trusty on 2015-04-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/1443527/+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 1648263] Re: package python-chardet 2.3.0-2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Closing this bug as it related to a Ubuntu release with is EOL - please re-open if its still a problem. ** Changed in: chardet (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/1648263 Title: package python-chardet 2.3.0-2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 Status in chardet package in Ubuntu: Won't Fix Bug description: What i do? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-chardet 2.3.0-2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Wed Dec 7 21:27:50 2016 Dependencies: python-pkg-resources 20.7.0-1 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-12-07 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: chardet Title: package python-chardet 2.3.0-2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/1648263/+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 421073] Re: package python-chardet 1.0.1-1.1 failed to install/upgrade: subprocess post-installation script returned errorcode 1
Closing this bug as it related to a Ubuntu release with is EOL - please re-open if its still a problem. ** Changed in: chardet (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/421073 Title: package python-chardet 1.0.1-1.1 failed to install/upgrade: subprocess post-installation script returned errorcode 1 Status in chardet package in Ubuntu: Invalid Bug description: Tried to install screenlets and installed python-chardet at same time. Anyway that failed with this error: Compiling /usr/lib/python2.5/site-packages/chardet/gb2312freq.py ... File "/usr/lib/python2.5/site-packages/chardet/gb2312freq.py", line 471 ^ SyntaxError: invalid syntax pycentral: pycentral pkginstall: error byte-compiling files (36) pycentral pkginstall: error byte-compiling files (36) ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 9.04 ErrorMessage: aliprosessi post-installation script palautti virhetilakoodin 1 NonfreeKernelModules: nvidia Package: python-chardet 1.0.1-1.1 PackageArchitecture: all SourcePackage: chardet Title: package python-chardet 1.0.1-1.1 failed to install/upgrade: aliprosessi post-installation script palautti virhetilakoodin 1 Uname: Linux 2.6.28-15-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/421073/+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 623026] Re: package python-chardet 1.0.1-1.1 failed to install/upgrade: ErrorMessage: Package is in a very bad inconsistent state - you should reinstall it before attempting conf
Closing this bug as it related to a Ubuntu release with is EOL - please re-open if its still a problem. ** Changed in: chardet (Ubuntu) Status: New => Opinion ** Changed in: chardet (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/623026 Title: package python-chardet 1.0.1-1.1 failed to install/upgrade: ErrorMessage: Package is in a very bad inconsistent state - you should reinstall it before attempting configuration. Status in chardet package in Ubuntu: Invalid Bug description: seems to be important- i'#m not sure whi this is happening. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: python-chardet 1.0.1-1.1 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Aug 23 22:03:36 2010 ErrorMessage: ErrorMessage: Package is in a very bad inconsistent state - you should reinstall it before attempting configuration. InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) PackageArchitecture: all SourcePackage: chardet Title: package python-chardet 1.0.1-1.1 failed to install/upgrade: ErrorMessage: Package is in a very bad inconsistent state - you should reinstall it before attempting configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/623026/+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 353560] Re: Using synaptic package manager crashes
As this bug related to a release which is no longer supported (8.10) closing - please re-open if this is still a problem on supported Ubuntu releases. ** Changed in: chardet (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/353560 Title: Using synaptic package manager crashes Status in chardet package in Ubuntu: Invalid Bug description: chardet (python) installation led to synaptic package installation error ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 8.10 ErrorMessage: subprocess post-installation script returned error exit status 1 Package: python-chardet 1.0.1-1 PackageArchitecture: all SourcePackage: chardet Title: package python-chardet 1.0.1-1 failed to install/upgrade: subprocess post-installation script returned error exit status 1 Uname: Linux 2.6.27-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/353560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1955347] Re: rsync works bad with encfs now
Hi Bryce and Sergio
I did not downgrade rsync yet, so I will do it using
apt-get install rsync=3.1.3-8
I will do the test with this previous version, but how can I provide a
step-by-step reproducer for this bug ?
With --verbose option or something else ?
Thanks.
Claude
Le lundi 24 janvier 2022 à 19:16 +, Bryce Harrington a écrit :
> Hi Claude,
>
> Were you able to downgrade to see if the prior version works
> properly,
> as Lucas suggested? If you haven't yet done so, I'd recommend using
> apt
> rather than co-installation from a tarball in this case both because
> it'd be a better apples-to-apples check, and because the behavior
> will
> be more predictable (co-installation can mess up config files and
> such).
> For example, downgrade using a command somewhat like this:
>
> $ apt-cache policy rsync
> rsync:
> Installed: 3.1.3-8ubuntu0.1
> Candidate: 3.1.3-8ubuntu0.1
> Version table:
> *** 3.1.3-8ubuntu0.1 500
> 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main
> amd64 Packages
> 100 /var/lib/dpkg/status
> 3.1.3-8 500
> 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64
> Packages
>
> $ sudo apt-get install rsync=3.1.3-8
> [sudo] password for bryce:
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages will be DOWNGRADED:
> rsync
> 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 26
> not upgraded.
> Need to get 322 kB of archives.
> After this operation, 12.3 kB of additional disk space will be
> used.
> Do you want to continue? [Y/n]
>
> Let us know when you've completed the check.
>
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1955347
Title:
rsync works bad with encfs now
Status in rsync package in Ubuntu:
Incomplete
Bug description:
Hello,
I think rsync works bad with encfs now.
When root uses it, rsync cannot read a directory encrypted with encfs
by a user. More precisely, it cannot read the mounted directory, the
virtual one where the user can read the datas.
Until now there was only a warning like this
"rsync: readlink_stat("/home/claude/Documents_chiffres") failed:
Permission denied (13)"
and the software went on working (only ignoring the content of the mounted
directory and of course without saving this content)
But recently there is this more:
"IO error encountered -- skipping file deletion"
and because of this "skipping file deletion", the software can't work
normally. The destination gets bigger more and more because the deleted files
in the source are not deleted in the destination.
Thanks for reading me.
rsync 3.1.3-8ubuntu0.1
Description:Ubuntu 20.04.3 LTS
Release:20.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1955347/+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 1937019] Re: FIDO2 tokens not supported on this build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1937019 Title: FIDO2 tokens not supported on this build Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Fix Released Bug description: I'm trying to test systemd-cryptenroll with FIDO2 keys in the new systemd version 248 on impish. Running "systemd-cryptenroll --fido2-device=list" results in the message: FIDO2 tokens not supported on this build. Would it be possible to build systemd with FIDO support in time for the impish release? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937019/+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 1946878] Re: Merge net-tools from Debian unstable for 22.04
** Changed in: net-tools (Ubuntu) Milestone: ubuntu-21.11 => ubuntu-22.02 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1946878 Title: Merge net-tools from Debian unstable for 22.04 Status in net-tools package in Ubuntu: New Bug description: Upstream: 1.60+git20210422.dfc41e0 Debian: 1.60+git20181103.0eebece-1 Ubuntu: 1.60+git20181103.0eebece-1ubuntu2 Debian updates this package infrequently, and last updated it 20.10. There is a new upstream version, however, so may be worth going ahead of debian and/or updating it in Debian and syncing it. ### New Debian Changes ### net-tools (1.60+git20181103.0eebece-1) unstable; urgency=medium * New upstream version 1.60+git20181103.0eebece - Fix nstrcmp() to prevent ifconfig from showing duplicate interfaces. (Closes: #812886) * Fix d/watch to point to upstream git repository * Add patch to fix decoding of MII vendor ids. (Closes: #549397) - Thanks, Ben Hutchings, for the patch. * Add patch to fix Japanese translation which uses a wrong Kanji character. (Closes: #621752) - Thanks, Takeshi Hamasaki, for the patch. * Add patch to fix wrong indentation of 'collisions' in the Japanese translation. (Closes: #653117) - Thanks, NODA, Kai, for the patch. * Fix Uploaders' field. - Add myself as an uploader. - Fix Tina's details. -- Utkarsh Gupta Fri, 02 Oct 2020 15:01:04 +0530 net-tools (1.60+git20180626.aebd88e-1) unstable; urgency=medium * New upstream snapshot * Refresh patches. * Fix typos in German manpages. Thanks to Prof. Dr. Steffen Wendzel and Dr. Tobias Quathamer for the patch. Closes: #900962. -- Martín Ferrari Mon, 24 Sep 2018 19:08:57 + net-tools (1.60+git20161116.90da8a0-4) unstable; urgency=medium * Update maintainer email address. Closes: #899617. * Update Standards-Version with no changes. -- Martín Ferrari Mon, 24 Sep 2018 17:16:31 + net-tools (1.60+git20161116.90da8a0-3) unstable; urgency=medium * debian/control: Update Vcs-* and Standards-Version. * debian/control: remove references to ancient package ja-trans. * debian/gbp.conf: Update repo layout. -- Martín Ferrari Tue, 31 Jul 2018 19:09:00 + net-tools (1.60+git20161116.90da8a0-2) unstable; urgency=medium * Fix typo in French manpage. Thanks to Michel Grigaut for the patch. * Add manpage for iptunnel, thanks to Sergio Durigan Junior. Closes: #88910 * Rename patches so CME does not choke on them. * Automated cme fixes; packaging improvements. * Remove unused and ancient patch. -- Martín Ferrari Sun, 11 Feb 2018 17:29:24 + net-tools (1.60+git20161116.90da8a0-1) unstable; urgency=medium * New upstream snapshot. * Re-synced translations.patch. * Acknowledge NMUs. Thanks a lot to Andrey Rahmatullin for the fixes and uploads. Closes: 846509. * Fix FTCBFS, thanks to Helmut Grohne for the patch. Closes: #811561. + Really assign CC for cross compilation. + Use triplet prefixed pkg-config. * Add debian/NEWS warning about changing output in net-tools commands. Closing bugs that reported problems in 3rd-party scripts arising from these changes. Closes: #845153, #843892, #820212. * Update Standards-Version, with no changes. -- Martín Ferrari Mon, 26 Dec 2016 05:58:42 + net-tools (1.60+git20150829.73cef8a-2.2) unstable; urgency=medium * Non-maintainer upload. * Apply an additional fix for the previous FTBFS for some architectures. -- Andrey Rahmatullin Thu, 01 Dec 2016 22:49:27 +0500 net-tools (1.60+git20150829.73cef8a-2.1) unstable; urgency=medium * Non-maintainer upload. * Fix FTBFS by applying the upstream patch (Closes: #844073). -- Andrey Rahmatullin Sun, 20 Nov 2016 15:23:12 +0500 net-tools (1.60+git20150829.73cef8a-2) unstable; urgency=medium [ Laurent Bigonville ] * Enable SELinux support. Closes: #666204. [ Martín Ferrari ] * Mark the package 'Multi-Arch: foreign', thanks to Frédéric Brière . Closes: #752584. * Fix bug in Portuguese man page, thanks to julianofisc...@gmail.com. Closes: #805377. -- Martín Ferrari Thu, 19 Nov 2015 14:48:47 + net-tools (1.60+git20150829.73cef8a-1) unstable; urgency=medium ### Old Ubuntu Delta ### net-tools (1.60+git20181103.0eebece-1ubuntu2) hirsute; urgency=medium * No change rebuild with fixed ownership. -- Dimitri John Ledkov Tue, 16 Feb 2021 15:18:30 + net-tools (1.60+git20181103.0eebece-1ubuntu1) hirsute; urgency=low * Merge from Debian unstable. Remaining changes: - Ubuntu_unit_conversion.patch: + Ubuntu Policy: output using standard SI unit multiples: KB (10^3), MB (10^6), GB (10^9),
[Touch-packages] [Bug 1959179] Re: Video driver not working properly
Thanks for the bug report. There is no backlight control for desktops with external monitors. Although in Xorg sessions you can use this to simulate it: xrandr --output NAME --brightness VALUE Also "the screen has pathches" sounds like bug 1867668. You need to remove the old 'intel' driver and use the newer default 'modesetting' driver instead. ** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Invalid -- 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 xserver-xorg-video-intel package in Ubuntu: Invalid 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1959179/+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
