[Touch-packages] [Bug 1938005] Re: ufw ignores rules
[Expired for ufw (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ufw (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1938005 Title: ufw ignores rules Status in ufw package in Ubuntu: Expired Bug description: With my setting I shouldn't be able to surf web, but I can do it (without proxy/vpn) This problem happens after `iptables -F` and only way to solve it, is to reboot PC. I tried `ufw reload` , too ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ufw 0.36-7.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Mon Jul 26 11:53:17 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-06-17 (38 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2021-07-25T22:22:29.221649 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1938005/+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 1947434] [NEW] Windows always open across monitors in a multi-monitor setup
Public bug reported: I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor (Dell U2719DC). Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu 21.04 too. If I log in using Wayland (the default), the initial window position of any app is always in the middle (half on the internal display and half on the external monitor). No setting that I have found appears to be able to change this behavior. If I switch to Xorg, this problem does not exist. With Xorg, the app window always opens on the primary monitor (the external one, in my case). This is the preferred behavior. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1947434 Title: Windows always open across monitors in a multi-monitor setup Status in xorg package in Ubuntu: New Bug description: I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor (Dell U2719DC). Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu 21.04 too. If I log in using Wayland (the default), the initial window position of any app is always in the middle (half on the internal display and half on the external monitor). No setting that I have found appears to be able to change this behavior. If I switch to Xorg, this problem does not exist. With Xorg, the app window always opens on the primary monitor (the external one, in my case). This is the preferred behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1947434/+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 1947432] [NEW] Display backlight and brightness controls are not working
Public bug reported: The screen brightness is stuck at 50% of the max output and the brightness controls/slider do nothing at all. This issue started happening with the nvidia-driver-470 package even before I upgraded from 21.04, and it doesn't happen with 465. The bug manifests in both X11 and Wayland. (and GDM itself before logging in) Setting nvidia-drm.modeset to 1 doesn't seem to affect it either. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-lowlatency 5.13.14 Uname: Linux 5.13.0-19-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.74 Mon Sep 13 23:09:15 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 03:46:49 2021 DistUpgraded: 2021-10-16 03:03:33,254 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.11.0-37-generic, x86_64: installed acpi-call, 1.1.0, 5.11.0-37-lowlatency, x86_64: installed acpi-call, 1.1.0, 5.13.0-19-generic, x86_64: installed acpi-call, 1.1.0, 5.13.0-19-lowlatency, x86_64: installed nvidia, 470.74, 5.13.0-19-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP106BM [GeForce GTX 1060 Mobile 6GB] [103c:846a] InstallationDate: Installed on 2020-08-06 (436 days ago) InstallationMedia: MachineType: HP OMEN by HP Laptop ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-lowlatency root=UUID=4d38cd06-3a59-420a-be51-f664f12d213d ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) dmi.bios.date: 05/11/2018 dmi.bios.release: 15.3 dmi.bios.vendor: AMI dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 846A dmi.board.vendor: HP dmi.board.version: 68.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 68.19 dmi.modalias: dmi:bvnAMI:bvrF.03:bd05/11/2018:br15.3:efr68.19:svnHP:pnOMENbyHPLaptop:pvr:sku4PM48EA#ABV:rvnHP:rn846A:rvr68.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop dmi.product.sku: 4PM48EA#ABV dmi.sys.vendor: HP nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish possible-manual-nvidia-install ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1947432 Title: Display backlight and brightness controls are not working Status in xorg package in Ubuntu: New Bug description: The screen brightness is stuck at 50% of the max output and the brightness controls/slider do nothing at all. This issue started happening with the nvidia-driver-470 package even before I upgraded from 21.04, and it doesn't happen with 465. The bug manifests in both X11 and Wayland. (and GDM itself before logging in) Setting nvidia-drm.modeset to 1 doesn't seem to affect it either. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-lowlatency 5.13.14 Uname: Linux 5.13.0-19-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was n
[Touch-packages] [Bug 1947429] [NEW] linux-object-* not autoremoved on upgrade
Public bug reported: After upgrading my kernel, directories are left behind in /lib/modules for previous kernel because with the kernel packaging layout, not all binary packages are autoremoved: $ dpkg -S /lib/modules/5.11.0-34-generic linux-objects-nvidia-460-5.11.0-34-generic: /lib/modules/5.11.0-34-generic $ sudo apt autoremove --purge linux-objects-nvidia-460-5.11.0-34-generic Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: linux-objects-nvidia-460-5.11.0-34-generic* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Requesting to save current system state Successfully saved as "autozsys_sdijbm" (Reading database ... 362960 files and directories currently installed.) Purging configuration files for linux-objects-nvidia-460-5.11.0-34-generic (5.11 .0-34.36) ... dpkg: warning: while removing linux-objects-nvidia-460-5.11.0-34-generic, directory '/lib/modules/5.11.0-34-generic' not empty so not removed ZSys is adding automatic system snapshot to GRUB menu $ ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: apt 2.3.9 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 14:36:40 2021 InstallationDate: Installed on 2019-12-23 (661 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apt UpgradeStatus: Upgraded to impish on 2021-10-15 (0 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1947429 Title: linux-object-* not autoremoved on upgrade Status in apt package in Ubuntu: New Bug description: After upgrading my kernel, directories are left behind in /lib/modules for previous kernel because with the kernel packaging layout, not all binary packages are autoremoved: $ dpkg -S /lib/modules/5.11.0-34-generic linux-objects-nvidia-460-5.11.0-34-generic: /lib/modules/5.11.0-34-generic $ sudo apt autoremove --purge linux-objects-nvidia-460-5.11.0-34-generic Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: linux-objects-nvidia-460-5.11.0-34-generic* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Requesting to save current system state Successfully saved as "autozsys_sdijbm" (Reading database ... 362960 files and directories currently installed.) Purging configuration files for linux-objects-nvidia-460-5.11.0-34-generic (5.11 .0-34.36) ... dpkg: warning: while removing linux-objects-nvidia-460-5.11.0-34-generic, directory '/lib/modules/5.11.0-34-generic' not empty so not removed ZSys is adding automatic system snapshot to GRUB menu $ ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: apt 2.3.9 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 14:36:40 2021 InstallationDate: Installed on 2019-12-23 (661 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apt UpgradeStatus: Upgraded to impish on 2021-10-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1947429/+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 1947415] Re: A blackscreen is displayed after login.
** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1947415 Title: A blackscreen is displayed after login. Status in ubuntu-meta package in Ubuntu: New Bug description: A blackscreen is displayed after login. This error happens with Xorg and Wayland. The only way to get the ubuntu-desktop to work is login into textmode and then running startx. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-desktop 1.472 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Oct 15 15:25:16 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1947415/+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 1947415] [NEW] A blackscreen is displayed after login.
You have been subscribed to a public bug: A blackscreen is displayed after login. This error happens with Xorg and Wayland. The only way to get the ubuntu-desktop to work is login into textmode and then running startx. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-desktop 1.472 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Oct 15 15:25:16 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages -- A blackscreen is displayed after login. https://bugs.launchpad.net/bugs/1947415 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta 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 1946667] Re: resolved reports Failed to send hostname reply: Invalid argument
Why is this marked invalid? -- 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/1946667 Title: resolved reports Failed to send hostname reply: Invalid argument Status in Canonical SSO provider: Invalid Status in systemd package in Ubuntu: New Bug description: According to https://github.com/systemd/systemd/issues/11626 this is fixed in version 248 of systemd. Please make that version available to LTS 20.04.3 Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-identity-provider/+bug/1946667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
Olivier, I am not sure what is the reasoning here. That you obviously want to land this in a non-LTS version has nothing to do with the fact the base product is not ready and that the change was announced unacceptably late here. The Flutter-based installer is a nice example. You can obviously develop something for years ánd still land it in a non-LTS. Locking out users is not just about "the deb still being available". Some people will have the snap, others the deb, and others both. If they have both I have no idea which one is run when they click the FF icon. The upgrade scenario you mention in comment #7 does not seem to be the real world case either. We just got teleported back in time, where the only way for our helpdesk to know what happens when a user calls the helpdesk, is to open a terminal and run "apt-get" and "ps aux". This is a support hell, especially at scale. Because of a non-critical move to another package format. And so far no guarantees on the LTS either. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1943840 Title: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Impish: Fix Released Status in ubuntu-release-upgrader source package in Impish: Fix Released Status in ubuntu-settings source package in Impish: Fix Released Bug description: Per Canonical's distribution agreement with Mozilla, we're making the snap¹ the default installation of firefox on desktop ISOs starting with Ubuntu 21.10. The snap is built and published for amd64, armhf and arm64. It is jointly maintained by Mozilla and the Ubuntu desktop team, and published by Mozilla. This requires updating the desktop-minimal seed, as well as ubuntu- release-upgrader. ¹ https://snapcraft.io/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Hi, I really do not remember any more how that somehow disappeared. Could it be that changing the channel at the wifi router could help? Unfortunately I did not remember that I reported the problem otherwise I would have immediately reported a possible workaround. Best regards, Martin. -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+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 1947394] Re: package ca-certificates 20210119ubuntu0.21.04.1 failed to install/upgrade: triggers looping, abandoned
** Package changed: ca-certificates (Ubuntu) => ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1947394 Title: package ca-certificates 20210119ubuntu0.21.04.1 failed to install/upgrade: triggers looping, abandoned Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: failed on upgrade to 21.10 on machine with AMD GPUs ProblemType: Package DistroRelease: Ubuntu 21.04 Package: ca-certificates 20210119ubuntu0.21.04.1 Uname: Linux 5.11.0-051100-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Oct 15 11:24:28 2021 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2020-12-18 (301 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: ca-certificates Title: package ca-certificates 20210119ubuntu0.21.04.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to hirsute on 2021-10-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1947394/+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 1947408] [NEW] Xorg freeze
Public bug reported: My system completely freezes requiring a hard reset if I do the following: 1. Launch Runelite (Installed using "snap install runelite") 2. Right click on the Runelite icon on the sidebar 3. System freezes ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 13:43:37 2021 DistUpgraded: 2021-10-14 15:16:12,934 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1043:0521] InstallationDate: Installed on 2021-07-08 (99 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: MSI MS-7850 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.13.0-19-generic root=UUID=dd4950a5-dc48-42ca-a4ff-e804e6199425 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (0 days ago) dmi.bios.date: 07/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.8:bd07/21/2014:br4.6:svnMSI:pnMS-7850:pvr1.0:skuTobefilledbyO.E.M.:rvnMSI:rnZ87-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze impish ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1947408 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: My system completely freezes requiring a hard reset if I do the following: 1. Launch Runelite (Installed using "snap install runelite") 2. Right click on the Runelite icon on the sidebar 3. System freezes ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 13:43:37 2021 DistUpgraded: 2021-10-14 15:16:12,934 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1043:0521] InstallationDate: Installed on 2021-07-08 (99 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: MSI MS-7850 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot
[Touch-packages] [Bug 1947405] Re: pm-suspend does not lock screen
Oh! On the 18.04 machine I actually executed: `xfce4-session-logout --suspend` Now realizing this, I'm asking myself if this issue should be closed since "pm-suspend" isn't supposed to lock, because that's "xflock4" job, right? :| Sorry for the noise. Yet, I hope it may at least point others towards "xfce4-session-logout" when suspending by command :D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1947405 Title: pm-suspend does not lock screen Status in pm-utils package in Ubuntu: New Bug description: System: Xubuntu 20.04.3 (64bit) When suspending my notebook by calling "/usr/sbin/pm-suspend", there is **no login dialog** after resuming. If I suspend using the graphical XFCE logout menu, the screen is locked properly. I've checked on my other 18.04 machine: There, pm-suspend locks the screen as expected. Is this something to be configured or a parameter? Grateful for any hints :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pm-utils 1.4.1-19 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Oct 15 19:39:23 2021 InstallationDate: Installed on 2021-01-16 (271 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1947405/+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 1947405] [NEW] pm-suspend does not lock screen
Public bug reported: System: Xubuntu 20.04.3 (64bit) When suspending my notebook by calling "/usr/sbin/pm-suspend", there is **no login dialog** after resuming. If I suspend using the graphical XFCE logout menu, the screen is locked properly. I've checked on my other 18.04 machine: There, pm-suspend locks the screen as expected. Is this something to be configured or a parameter? Grateful for any hints :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pm-utils 1.4.1-19 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Oct 15 19:39:23 2021 InstallationDate: Installed on 2021-01-16 (271 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1947405 Title: pm-suspend does not lock screen Status in pm-utils package in Ubuntu: New Bug description: System: Xubuntu 20.04.3 (64bit) When suspending my notebook by calling "/usr/sbin/pm-suspend", there is **no login dialog** after resuming. If I suspend using the graphical XFCE logout menu, the screen is locked properly. I've checked on my other 18.04 machine: There, pm-suspend locks the screen as expected. Is this something to be configured or a parameter? Grateful for any hints :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pm-utils 1.4.1-19 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Oct 15 19:39:23 2021 InstallationDate: Installed on 2021-01-16 (271 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1947405/+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 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Affects me too at WeWork in 2021! -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+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 1931747] Re: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/impish
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- 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/1931747 Title: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/impish Status in software-properties package in Ubuntu: Confirmed Bug description: Could not find reasion for error. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: software-properties-gtk 0.99.11 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: MATE Date: Fri Jun 11 22:14:43 2021 ExecutablePath: /usr/bin/software-properties-gtk InterpreterPath: /usr/bin/python3.9 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/impish UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1931747/+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 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute)
Please provide an SRU template for this bug per https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: libsignon-glib (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute) Status in libsignon-glib package in Ubuntu: Incomplete Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+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 1944741] Re: HiFive Unmatched partitions are named "Unleashed"
Hello Alexandre, or anyone else affected, Accepted util-linux into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/util- linux/2.36.1-8ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: util-linux (Ubuntu Impish) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944741 Title: HiFive Unmatched partitions are named "Unleashed" Status in util-linux package in Ubuntu: New Status in util-linux source package in Impish: Fix Committed Status in util-linux package in Debian: Confirmed Bug description: [Impact] Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same UUIDs to load the next stage bootloader: the current name makes partitions on Unmatched board appear as 'Unleashed'. This issue gives the feeling that the Ubuntu RISC-V images made specifically for those 2 boards were assembled in a rushed manner. The attached patch fixes this by removing the 'Unleashed' part of the current name so that it fits both, it was build againt all architectures here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12783067/+listing-archive-extra [Test Plan] 1. Download the SiFive Unmatched image here: https://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/pending/impish-preinstalled-server-riscv64+unmatched.img.xz 2. Follow instructions here to launch a riscv64 VM: https://wiki.ubuntu.com/RISC-V 3. Execute the following command: ubuntu@ubuntu:~$ sudo fdisk -l Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 0F66C0C3-A5E4-439B-907E-ABAD106FE4A7 Device Start End Sectors Size Type /dev/vda1 235554 83886046 83650493 39.9G Linux filesystem /dev/vda12 227362 235553 81924M Linux filesystem /dev/vda13 34 2081 20481M HiFive Unleashed FSBL /dev/vda14 208210273 81924M HiFive Unleashed BBL /dev/vda15 10274 227361 217088 106M EFI System Partition table entries are not in disk order. 4. Download and install the new packages that contain the fix here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/libfdisk1_2.36.1-8ubuntu4_riscv64.deb https://launchpad.net/~alexg
[Touch-packages] [Bug 1947394] [NEW] package ca-certificates 20210119ubuntu0.21.04.1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: failed on upgrade to 21.10 on machine with AMD GPUs ProblemType: Package DistroRelease: Ubuntu 21.04 Package: ca-certificates 20210119ubuntu0.21.04.1 Uname: Linux 5.11.0-051100-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Oct 15 11:24:28 2021 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2020-12-18 (301 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: ca-certificates Title: package ca-certificates 20210119ubuntu0.21.04.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to hirsute on 2021-10-15 (0 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1947394 Title: package ca-certificates 20210119ubuntu0.21.04.1 failed to install/upgrade: triggers looping, abandoned Status in ca-certificates package in Ubuntu: New Bug description: failed on upgrade to 21.10 on machine with AMD GPUs ProblemType: Package DistroRelease: Ubuntu 21.04 Package: ca-certificates 20210119ubuntu0.21.04.1 Uname: Linux 5.11.0-051100-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Oct 15 11:24:28 2021 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2020-12-18 (301 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: ca-certificates Title: package ca-certificates 20210119ubuntu0.21.04.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to hirsute on 2021-10-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1947394/+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 1947377] [NEW] Desktop Icons disappear
Public bug reported: When using Gedit to edit a text file. After saving the file, some of my Desktop icons disappear. I can restore them by logging in, again using 'switch user accounts' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 09:00:16 2021 DistUpgraded: 2021-07-18 14:54:01,305 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:047e] MachineType: Dell Inc. OptiPlex 990 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=c86e2158-f3a1-4357-85c5-1175cf0b9d52 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2021-07-18 (88 days ago) dmi.bios.date: 08/26/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd08/26/2015:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 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.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal possible-manual-nvidia-install third-party-packages 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/1947377 Title: Desktop Icons disappear Status in xorg package in Ubuntu: New Bug description: When using Gedit to edit a text file. After saving the file, some of my Desktop icons disappear. I can restore them by logging in, again using 'switch user accounts' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 09:00:16 2021 DistUpgraded: 2021-07-18 14:54:01,305 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:047e] MachineType: Dell Inc. OptiPlex 990 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=c86e2158-f3a1-4357-85c5-1175cf0b9d52 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2021-07-18 (88 days ago) dmi.bios.date: 08/26/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd08/26/2015:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 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.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xs
[Touch-packages] [Bug 1946343] Re: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
** Changed in: oem-priority Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1946343 Title: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3 Status in Dell Ubuntu Project: Confirmed Status in OEM Priority Project: In Progress Status in base-files package in Ubuntu: Invalid Bug description: Refer: https://answers.launchpad.net/ubuntu/+question/698949 I recently bought a Dell laptop with Ubuntu pre-installed in it. Looks like it came with Ubuntu 20.04.2 and OEM Linux Kernel in it. After my initial login (on October 1, 2021), the 'Software Updater' GUI prompted me for updates, which I went ahead with. However at the end of it, I noticed that I was still at 20.04.2 with Linux Kernel at 5.10.0-1045-oem. lsb_release -a --- No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal uname -a - Linux dev-linux 5.10.0-1045-oem #47-Ubuntu SMP Wed Aug 18 10:41:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Then I manually tried sudo apt update and sudo apt upgrade / dist- upgrade from the terminal, but nothing got upgraded. When I invoked the GUI 'Software Updater' again, it showed me that my system was already up-to-date. However, as 20.04.3 was released end of Aug 2021, I was expecting that I should be at that release after my initial updates. Since that didn't happen, I asked a question regarding this in askubuntu followed by launchpad https://answers.launchpad.net/ubuntu/+question/698949, thinking my update had failed for some unknown reason. However, based on some inputs from other users, we were able to narrow down the problem to /usr/lib/os-release file not having the right contents in it. Every other file including /usr/lib/os-release.oem- release, /etc/issue, /etc/issue.net specifies that I am on 20.04.3. Whereas only /usr/lib/os-release (and its symlink /etc/release) specifies my current release as 20.04.2. Even the lsb_release -a command always displays the output of /usr/lib/os-release file only. $ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /usr/lib/os-release.oem-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /etc/issue Ubuntu 20.04.3 LTS \n \l $ cat /etc/issue.net Ubuntu 20.04.3 LTS If you look at the timestamp of these files, strangely os-release had a newer timestamp of Oct 1 compared to other files. $ ls -l /usr/lib/os-release -rw-r--r-- 1 root root 406 Oct 1 20:31 /usr/lib/os-release $ ls -l /usr/lib/os-release.oem-release -rw-r--r-- 1 root root 382 Aug 4 07:53 /usr/lib/os-release.oem-release $ ls -l /etc/issue -rw-r--r-- 1 root root 26 Aug 4 07:53 /etc/issue $ ls -l /etc/issue.net -rw-r--r-- 1 root root 19 Aug 4 07:53 /etc/issue.net Please note that, other software package updates, and linux kernel updates are happening automatically without any issues so far for me. Few days back even got a new kernel update. $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Workarounds Attempted - 1. Commented out all non-ubuntu external sources from /etc/apt/*.list. Then performed an apt clean + update + upgrade. But still nothing happened and the same issue remained. 2. Tried performing apt-install --reinstall base-files. But still nothing changed: $ sudo apt install --reinstall base-files Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 4 not upgraded. Need to get 60.6 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 base-files amd64 11ubuntu5.4 [60.6 kB] Fetched 60.6 kB in 1s (55.7 kB/s) (Reading database ... 191154 files and directories currently installed.) Preparing t
[Touch-packages] [Bug 1886809] Re: Pulse connect VPN exists because unwanted avahi network starts
Hi @dbungert, Sadly the company decided to move out from pulse secure usage, so I can't help anymore with tests. But I can give some insights. The main issue is that AVAHI_DAEMON_DETECT_LOCAL set as 0 isn't avoiding avahi to change routes. It shouldn't happen. My patch isn't this direction and it is much more specific for the use case I had that time. My suggestion for long term solution instead is to just call `return` or `exit 0` once the AVAHI_DAEMON_DETECT_LOCAL value is 0. What do you think? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1886809 Title: Pulse connect VPN exists because unwanted avahi network starts Status in avahi package in Ubuntu: New Bug description: Pulse VPNs exists very often because avahi enforces network 192.250.0.0/0 over tun0 interface. The message error is: rmon.error Unauthorized new route to 169.254.0.0/0.0.0.0 has been added (conflicts with our route to 0.0.0.0), disconnecting (routemon.cpp:598) No matter the options to skip avahi on /etc/default/avahi-daemon, it always calls /etc/network/if-up.d/avahi-autoipd and raises this discovery network. A fix can be done patching /etc/network/if-up.d/avahi-autoipd to skip any tunnel interface. --- /etc/network/if-up.d/avahi-autoipd.dpkg-old 2020-07-08 13:25:41.834569800 +0200 +++ /etc/network/if-up.d/avahi-autoipd 2020-07-07 10:07:37.68581 +0200 @@ -11,6 +11,10 @@ [ -x /usr/sbin/avahi-autoipd ] || exit 0 +case "$IFACE" in + tun*) exit 0 ;; +esac + [ "$IFACE" != "lo" ] || exit 0 case "$ADDRFAM" in inet) ;; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1886809/+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 1947329] [NEW] package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
Public bug reported: Pop up comes in just after turn on. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 15 01:40:29 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2021-10-05 (10 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: python3-defaults Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to focal on 2021-10-15 (0 days ago) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1947329 Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: New Bug description: Pop up comes in just after turn on. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 15 01:40:29 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2021-10-05 (10 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: python3-defaults Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to focal on 2021-10-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1947329/+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 1890572] Re: USB backend never ends if the printer is not connected
Hi Till,
the issue was reported in the Apple repository:
https://github.com/apple/cups/issues/5817
I will check whether this was already fixed in OpenPrinting or not.
--
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/1890572
Title:
USB backend never ends if the printer is not connected
Status in cups package in Ubuntu:
Fix Released
Bug description:
USB backend never ends if the printer is not connected. We have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while ((g.printer = find_device(print_cb, uri)) == NULL)
{
_cupsLangPrintFilter(stderr, "INFO",
_("Waiting for printer to become available."));
sleep(5);
}
```
It's also easy to test by invoking the backend by hand:
```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...
```
Setting a job timeout policy or manually stopping work are not options
for us. We may have jobs that take hours to complete.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+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 1941708] Re: BlueZ 5.62 release
5.62 is now prepared here: https://git.launchpad.net/~bluetooth/bluez/log/?h=ubuntu-next ** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1941708 Title: BlueZ 5.62 release Status in bluez package in Ubuntu: Fix Committed Bug description: BlueZ 5.62 release is out: https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941708/+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 1947318] [NEW] ip xfrm policy help gives invalid output
Public bug reported:
On Ubuntu Focal, the `ip x p h` command from iproute2 (5.5.0-1ubuntu1)
gives the following output:
UPSPEC := proto { { tcp | tcp | tcp | tcp } [ sport PORT ] [ dport PORT ] |
{ icmp | icmp | icmp } [ type NUMBER ] [ code NUMBER ] |
gre [ key { DOTTED-QUAD | NUMBER } ] | PROTO }
I don't think the proto is intended to be "{ tcp | tcp | tcp | tcp }" or
"{ icmp | icmp | icmp }"
The same command provided by iproute2 in Debian Buster
(4.20.0-2+deb10u1), Bullseye (5.10.0-4) and Ubuntu Groovy
(5.7.0-1ubuntu1) generates the following output, which looks like
intended.
UPSPEC := proto { { tcp | udp | sctp | dccp } [ sport PORT ] [ dport PORT ]
|
{ icmp | ipv6-icmp | mobility-header } [ type NUMBER ] [
code NUMBER ] |
gre [ key { DOTTED-QUAD | NUMBER } ] | PROTO }
It certainly makes more sense that proto may be one of "{ tcp | udp |
sctp | dccp }" than "{ tcp | tcp | tcp | tcp }".
Should any relevant fix be ported to the LTS version, Focal, too?
** Affects: iproute2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1947318
Title:
ip xfrm policy help gives invalid output
Status in iproute2 package in Ubuntu:
New
Bug description:
On Ubuntu Focal, the `ip x p h` command from iproute2 (5.5.0-1ubuntu1)
gives the following output:
UPSPEC := proto { { tcp | tcp | tcp | tcp } [ sport PORT ] [ dport PORT ]
|
{ icmp | icmp | icmp } [ type NUMBER ] [ code NUMBER ] |
gre [ key { DOTTED-QUAD | NUMBER } ] | PROTO }
I don't think the proto is intended to be "{ tcp | tcp | tcp | tcp }"
or "{ icmp | icmp | icmp }"
The same command provided by iproute2 in Debian Buster
(4.20.0-2+deb10u1), Bullseye (5.10.0-4) and Ubuntu Groovy
(5.7.0-1ubuntu1) generates the following output, which looks like
intended.
UPSPEC := proto { { tcp | udp | sctp | dccp } [ sport PORT ] [ dport PORT
] |
{ icmp | ipv6-icmp | mobility-header } [ type NUMBER ]
[ code NUMBER ] |
gre [ key { DOTTED-QUAD | NUMBER } ] | PROTO }
It certainly makes more sense that proto may be one of "{ tcp | udp |
sctp | dccp }" than "{ tcp | tcp | tcp | tcp }".
Should any relevant fix be ported to the LTS version, Focal, too?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1947318/+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
