[Touch-packages] [Bug 1971916] Re: error in the system
Thanks for the bug report. Please explain in more detail what messages or errors you are seeing. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1971916 Title: error in the system Status in Ubuntu: Incomplete Bug description: I get several messages when I start the UBUNTU OS ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu May 5 21:42:12 2022 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3410/3430] [1002:95c2] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RV620/M82 [Mobility Radeon HD 3410/3430] [103c:30e9] InstallationDate: Installed on 2022-05-02 (3 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: Hewlett-Packard HP Compaq 6830s (FR883LA#ABM) ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-142-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZD Ver. F.0F dmi.board.name: 30E9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 95.1D dmi.chassis.asset.tag: CNU8504GHF dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZDVer.F.0F:bd06/24/2009:svnHewlett-Packard:pnHPCompaq6830s(FR883LA#ABM):pvrF.0F:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP Compaq 6830s (FR883LA#ABM) dmi.product.version: F.0F dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu May 5 21:31:49 2022 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputLVDS VGA-0 xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1971916/+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 1971916] [NEW] error in the system
Public bug reported: I get several messages when I start the UBUNTU OS ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu May 5 21:42:12 2022 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3410/3430] [1002:95c2] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RV620/M82 [Mobility Radeon HD 3410/3430] [103c:30e9] InstallationDate: Installed on 2022-05-02 (3 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: Hewlett-Packard HP Compaq 6830s (FR883LA#ABM) ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-142-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZD Ver. F.0F dmi.board.name: 30E9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 95.1D dmi.chassis.asset.tag: CNU8504GHF dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZDVer.F.0F:bd06/24/2009:svnHewlett-Packard:pnHPCompaq6830s(FR883LA#ABM):pvrF.0F:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP Compaq 6830s (FR883LA#ABM) dmi.product.version: F.0F dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu May 5 21:31:49 2022 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputLVDS VGA-0 xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- 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/1971916 Title: error in the system Status in xorg package in Ubuntu: New Bug description: I get several messages when I start the UBUNTU OS ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu May 5 21:42:12 2022 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3410/3430] [1002:95c2] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RV620/M82 [Mobility Radeon HD 3410/3430] [103c:30e9] InstallationDate: Installed on 2022-05-02 (3 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: Hewlett-Packard HP Compaq 6830s (FR883LA#ABM) ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-142-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZD Ver. F.0F dmi.board.name: 30E9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC
[Touch-packages] [Bug 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]
** Summary changed: - gnome-extensions-app fails to start (Protocol error) + gnome-extensions-app fails to start [Error reading events from display: Protocol error] -- 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/1965563 Title: gnome-extensions-app fails to start [Error reading events from display: Protocol error] Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1971888] [NEW] Can not ssh to github.com or gitlab.com when upgrading to 22.04
On Thu, May 05, 2022 at 09:09:07PM -, Alvaro wrote: > acs@lsp-022:~$ ssh -vT g...@github.com > ... > debug1: connect to address 140.82.121.4 port 22: Connection timed out Note that "Connection timed out" is an error at the TCP level, that indicates that your computer wasn't able to establish a TCP session. ssh's algorithm choices aren't involved yet. Are you sure this machine can communicate with 140.82.121.4:22 at all? $ nc 140.82.112.4 22 SSH-2.0-babeld-78a8149e ^C Thanks -- 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/1971888 Title: Can not ssh to github.com or gitlab.com when upgrading to 22.04 Status in openssh package in Ubuntu: New Bug description: Dear all, After the upgrading to Ubuntu 22.04 I can not use git over ssh. The best way to reproduce the error is: ``` acs@lsp-022:~$ ssh -vT g...@github.com OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022 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 github.com [140.82.121.4] port 22. debug1: connect to address 140.82.121.4 port 22: Connection timed out ``` Before the upgrading I can connect correctly with: ``` ssh -vT g...@github.com OpenSSH_8.2p1 Ubuntu-4ubuntu0.4, OpenSSL 1.1.1f 31 Mar 2020 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 23: Applying options for * debug1: Connecting to github.com [140.82.121.4] port 22. debug1: Connection established ``` The same issue is happening with gitlab.com. Probably it is related with the OpenSSL version. Cheers! -- Alvaro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ssh 1:8.9p1-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 5 23:00:33 2022 InstallationDate: Installed on 2021-03-08 (423 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: Upgraded to jammy on 2022-05-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1971888/+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 1971895] Re: Warning messages from stat printed on installation with no user crontabs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cron (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1971895 Title: Warning messages from stat printed on installation with no user crontabs Status in cron package in Ubuntu: Confirmed Bug description: On installation of cron on a new system, or (I expect) an upgrade with no user crontab files the following is printed: Setting up cron (3.0pl1-128.1ubuntu1.1) ... stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory Warning: * is not a regular file! This is related to the fix for CVE-2017-9525 introduced in 3.0pl1-128.1ubuntu1.1. The for loop at line 66 of cron.postinst needs to have a guard like the following added to it: [ "$tab_name" = "*" ] && continue We have observed this with Bionic, I haven't checked any other Ubuntu releases. Cheers, Andrew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1971895/+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 1971895] Re: Warning messages from stat printed on installation with no user crontabs
I was just in the process of writing David Fernandez Gonzalez an Email about this problem when I came across this ticket. I can confirm this problem on Ubuntu 18.04.6. My 20.x machines did not get the update, so I cannot verify on other releases: Unpacking cron (3.0pl1-128.1ubuntu1.1) over (3.0pl1-128.1ubuntu1) ... Setting up cron (3.0pl1-128.1ubuntu1.1) ... stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory Warning: * is not a regular file! Every single sysadmin should be concerned. ANY TIME we see asterisk wildcards being used in this fashion, where [ or test operators are behaving in this manner, we have reason to become concerned. To me, this smells of a shell script trying to parse crontab entries, which is inherently dangerous. I am now questioning whether or not this postinst script potentially nuked something it shouldn't have. How this was missed is beyond me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1971895 Title: Warning messages from stat printed on installation with no user crontabs Status in cron package in Ubuntu: Confirmed Bug description: On installation of cron on a new system, or (I expect) an upgrade with no user crontab files the following is printed: Setting up cron (3.0pl1-128.1ubuntu1.1) ... stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory Warning: * is not a regular file! This is related to the fix for CVE-2017-9525 introduced in 3.0pl1-128.1ubuntu1.1. The for loop at line 66 of cron.postinst needs to have a guard like the following added to it: [ "$tab_name" = "*" ] && continue We have observed this with Bionic, I haven't checked any other Ubuntu releases. Cheers, Andrew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1971895/+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
*** This bug is a duplicate of bug 1971296 *** https://bugs.launchpad.net/bugs/1971296 ** This bug has been marked a duplicate of bug 1971296 Merge net-tools from Debian unstable for kinetic -- 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: -
[Touch-packages] [Bug 1971895] [NEW] Warning messages from stat printed on installation with no user crontabs
Public bug reported: On installation of cron on a new system, or (I expect) an upgrade with no user crontab files the following is printed: Setting up cron (3.0pl1-128.1ubuntu1.1) ... stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory Warning: * is not a regular file! This is related to the fix for CVE-2017-9525 introduced in 3.0pl1-128.1ubuntu1.1. The for loop at line 66 of cron.postinst needs to have a guard like the following added to it: [ "$tab_name" = "*" ] && continue We have observed this with Bionic, I haven't checked any other Ubuntu releases. Cheers, Andrew ** Affects: cron (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1971895 Title: Warning messages from stat printed on installation with no user crontabs Status in cron package in Ubuntu: New Bug description: On installation of cron on a new system, or (I expect) an upgrade with no user crontab files the following is printed: Setting up cron (3.0pl1-128.1ubuntu1.1) ... stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory Warning: * is not a regular file! This is related to the fix for CVE-2017-9525 introduced in 3.0pl1-128.1ubuntu1.1. The for loop at line 66 of cron.postinst needs to have a guard like the following added to it: [ "$tab_name" = "*" ] && continue We have observed this with Bionic, I haven't checked any other Ubuntu releases. Cheers, Andrew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1971895/+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 1946847] Re: Merge bridge-utils from Debian unstable for 22.04
*** This bug is a duplicate of bug 1971264 *** https://bugs.launchpad.net/bugs/1971264 ** This bug has been marked a duplicate of bug 1971264 Merge bridge-utils from Debian unstable for kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1946847 Title: Merge bridge-utils from Debian unstable for 22.04 Status in bridge-utils package in Ubuntu: Incomplete Bug description: Upstream: 1.7.1 Debian: 1.7-1 Ubuntu: 1.7-1ubuntu2 Debian typically updates bridge-utils every 4 months on average, but it was last updated 21.02 and looks overdue. Check back in on this monthly. ### New Debian Changes ### bridge-utils (1.7-1) unstable; urgency=medium * New upstream version. Only messages related changes and compilation fixes. * Remove preserve_gcc_flags patch (in upstream now). * Bump standards, no change needed. * Clarify portprio and fix example. * Update upstream url. * Fix NEWS versioning of last entry :-? -- Santiago Garcia Mantinan Wed, 24 Feb 2021 12:34:03 +0100 bridge-utils (1.6-6) unstable; urgency=medium * Fix IPv6 address getting assigned on hotplug devices. Closes: #980752. * Fix waiting so that DAD works again. Closes: #982943. * Move mac setting before brctl addif to ensure mac setting. Closes: #980856. * Update documentation and add examples. Closes: #765098. * Update manpages. Closes: #981253. * Add a note on MTU settings. Closes: #292088. * Hook also on down to recreate the bridge so that multiple stanzas work Ok on ifdown. Closes: #319832. -- Santiago Garcia Mantinan Tue, 16 Feb 2021 13:29:04 +0100 bridge-utils (1.6-5) unstable; urgency=low * Overload bridge_hw to allow do specify an interface as well as the MAC address. Closes: #966244. * Change man page for bridge-utils-interfaces and news fileto document this overloading. -- Santiago Garcia Mantinan Fri, 22 Jan 2021 11:08:47 +0100 bridge-utils (1.6-4) unstable; urgency=low * Add en* to the device regex so that all catches them. Closes: #966319. * Document MAC address changes on news. Closes: #980505. -- Santiago Garcia Mantinan Thu, 21 Jan 2021 10:51:31 +0100 bridge-utils (1.6-3) unstable; urgency=medium * Support VLAN aware setups where we need vlan filtering. Thanks Benedikt Spranger for the patch. Closes: #950879. * Clarify on manual page that stp will get IPv6 lost. Closes: #736336. * Add a 1 second sleep if hw address needs to be changed. Closes: #945466. -- Santiago Garcia Mantinan Thu, 30 Apr 2020 10:06:38 +0200 bridge-utils (1.6-2) unstable; urgency=medium * Bump Standards-Version. * Preserve gcc flags set when building the lib. -- Santiago Garcia Mantinan Mon, 28 Jan 2019 00:25:14 +0100 bridge-utils (1.6-1) unstable; urgency=low * New upstream version. * Change default back to not hotplug. Closes: #892277. * Allow mtu to be set on the bridge by propagating it to the bridged interfaces. Closes: #661711. * Remove kernel headers from the package. -- Santiago Garcia Mantinan Tue, 15 Jan 2019 13:18:33 +0100 bridge-utils (1.5-16) unstable; urgency=medium * Don't set dev globally at bridge-utils.sh. Closes: #873086. -- Santiago Garcia Mantinan Sun, 08 Apr 2018 23:06:30 +0200 bridge-utils (1.5-15) unstable; urgency=medium * Fix substrings on interfaces. Closes: #873087. * Make it lintian clean sticking to 1.0 source format for now. No time to properly comment all the patches right now. -- Santiago Garcia Mantinan Fri, 02 Mar 2018 22:08:20 +0100 bridge-utils (1.5-14) unstable; urgency=low * Fix a problem with some vlan interfaces not being created. -- Santiago Garcia Mantinan Mon, 26 Jun 2017 17:48:37 +0200 bridge-utils (1.5-13) unstable; urgency=low * Fix a hardcoded interface name on bridge-utils.sh. Closes: #854841. -- Santiago Garcia Mantinan Sat, 11 Feb 2017 00:16:45 +0100 bridge-utils (1.5-12) unstable; urgency=medium * Add vlan support so that old setups using vlans as ports don't break. -- Santiago Garcia Mantinan Sun, 22 Jan 2017 00:23:50 +0100 ### Old Ubuntu Delta ### bridge-utils (1.7-1ubuntu2) impish; urgency=medium * No-change rebuild to build packages with zstd compression. -- Matthias Klose Thu, 07 Oct 2021 12:09:41 +0200 bridge-utils (1.7-1ubuntu1) impish; urgency=low * Merge from Debian unstable. Remaining changes: - Don't call ifup from bridge-network-interface, instead just call brctl and let udev/upstart bring the interface up. - debian/ifupdown.sh: Handle bridge params which use port and value - debian/bridge-utils-interface.5: + Update max, default value for path cost +
[Touch-packages] [Bug 1971763] Re: www-browser is not satisfied by the default Firefox snap
Thank you for your bug report. Do you have the firefox deb installed? It's not providing the software but ensuring the snap is installed and providing www-browser ** Changed in: apt (Ubuntu) Status: New => Incomplete -- 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/1971763 Title: www-browser is not satisfied by the default Firefox snap Status in apt package in Ubuntu: Incomplete Bug description: When installing a package that has the virtual-package www-browser as a dependency, the Firefox snap is not taken into account. This leads to wslu being installed on Ubuntu 22.04 Desktop (notably when installing the GIMP translation packages), which breaks the ding desktop behaviour: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1971757 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1971763/+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 1971632] Re: Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect; pulseautio crashes every time
Igor Kovalenko managed to identify the problem, and and fixed it. See https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1354 for details. ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1354 -- 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/1971632 Title: Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect; pulseautio crashes every time Status in pulseaudio package in Ubuntu: New Bug description: On a fresh install of Kubuntu 22.04, when I turn my properly paired bluetooth headphones on they automatically connect to the system, then immediately disconnect again. The headphones thus have to be manually 're-connected' every time. Best as I understand it from the logs (appended below), pulseaudio showing up killed just after the headphones turn up as an unregistered sender ... 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE ... is responsible for the observed problem, i.e. the disconnect, probably triggered when pulseaudio restarts ... 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. So it seems either an internal pulseaudio problem, or a problem triggered by the division by 0 in the bluetooth module ... 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] or some combination of the two ... but again, I'm only guessing here. ___ System Logs after switching headphones on: 4/30/22 7:33 PM kernel input: Nat's Flex (AVRCP) as /devices/virtual/input/input31 4/30/22 7:33 PM systemd-logind Watching system buttons on /dev/input/event19 (Nat's Flex (AVRCP)) 4/30/22 7:33 PM bluetoothd /org/bluez/hci0/dev_A8_91_3D_DF_A8_F4/fd3: fd(43) ready 4/30/22 7:33 PM rtkit-daemonSupervising 0 threads of 0 processes of 0 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8884 of process 3426 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Failed with result 'signal'. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM acpid input device has been disconnected, fd 20 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. 4/30/22 7:33 PM systemd Stopped Sound Service. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM systemd Starting Sound Service... 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8889 of process 8889 owned by '1000' high priority at nice level -11. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM pulseaudio Stale PID file, overwriting. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8890 of process 8889 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 2 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSupervising 2 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread
[Touch-packages] [Bug 1971763] Re: www-browser is not satisfied by the default Firefox snap
** Description changed: - When installing a package that has the virtual-packages www-browser as a + When installing a package that has the virtual-package www-browser as a dependency, the Firefox snap is not taken into account. This leads to wslu being installed on Ubuntu 22.04 Desktop (notably when installing the GIMP translation packages), which breaks the ding desktop behaviour: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1971757 -- 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/1971763 Title: www-browser is not satisfied by the default Firefox snap Status in apt package in Ubuntu: New Bug description: When installing a package that has the virtual-package www-browser as a dependency, the Firefox snap is not taken into account. This leads to wslu being installed on Ubuntu 22.04 Desktop (notably when installing the GIMP translation packages), which breaks the ding desktop behaviour: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1971757 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1971763/+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 1971888] [NEW] Can not ssh to github.com or gitlab.com when upgrading to 22.04
Public bug reported: Dear all, After the upgrading to Ubuntu 22.04 I can not use git over ssh. The best way to reproduce the error is: ``` acs@lsp-022:~$ ssh -vT g...@github.com OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022 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 github.com [140.82.121.4] port 22. debug1: connect to address 140.82.121.4 port 22: Connection timed out ``` Before the upgrading I can connect correctly with: ``` ssh -vT g...@github.com OpenSSH_8.2p1 Ubuntu-4ubuntu0.4, OpenSSL 1.1.1f 31 Mar 2020 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 23: Applying options for * debug1: Connecting to github.com [140.82.121.4] port 22. debug1: Connection established ``` The same issue is happening with gitlab.com. Probably it is related with the OpenSSL version. Cheers! -- Alvaro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ssh 1:8.9p1-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 5 23:00:33 2022 InstallationDate: Installed on 2021-03-08 (423 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: Upgraded to jammy on 2022-05-05 (0 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1971888 Title: Can not ssh to github.com or gitlab.com when upgrading to 22.04 Status in openssh package in Ubuntu: New Bug description: Dear all, After the upgrading to Ubuntu 22.04 I can not use git over ssh. The best way to reproduce the error is: ``` acs@lsp-022:~$ ssh -vT g...@github.com OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022 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 github.com [140.82.121.4] port 22. debug1: connect to address 140.82.121.4 port 22: Connection timed out ``` Before the upgrading I can connect correctly with: ``` ssh -vT g...@github.com OpenSSH_8.2p1 Ubuntu-4ubuntu0.4, OpenSSL 1.1.1f 31 Mar 2020 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 23: Applying options for * debug1: Connecting to github.com [140.82.121.4] port 22. debug1: Connection established ``` The same issue is happening with gitlab.com. Probably it is related with the OpenSSL version. Cheers! -- Alvaro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ssh 1:8.9p1-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 5 23:00:33 2022 InstallationDate: Installed on 2021-03-08 (423 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: Upgraded to jammy on 2022-05-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1971888/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
Same issue with evince 42.1-3 and apparmor 3.0.4-2ubuntu2 on cinnamon 5.2.7-4 from Ubuntu 22.04 (Jammy Jellyfish) The apparmor workaround fixes it for me. Thanks Karsten. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1971650] Re: wrong check for "server" in libssl3.postinst
Possibly related to https://bugs.launchpad.net/bugs/1832421 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1971650 Title: wrong check for "server" in libssl3.postinst Status in openssl package in Ubuntu: New Bug description: A security update has just been applied to my system for openssl, and the 'reboot required' message just popped on my desktop. I looked to see why this was, and found the following code in the libssl3 postinst: # Here we issue the reboot notification for upgrades and # security updates. We do want services to be restarted when we # update for a security issue, but planned by the sysadmin, not # automatically. # Only issue the reboot notification for servers; we proxy this by # testing that the X server is not running (LP: #244250) if ! pidof /usr/lib/xorg/Xorg > /dev/null && [ -x /usr/share/update-notifier/notify-reboot-required ]; then /usr/share/update-notifier/notify-reboot-required fi Now, AFAIK this is the only package that interfaces with notify- reboot-required but omits the notification on desktops, so that seems to be an inconsistent policy; but even if we thought that was the correct policy to apply, the above check for a desktop is not because it doesn't match in the case the user is running Xwayland, which most users not using the nvidia driver will be doing now by default. Also, this is now inside a block that checks for the presence of needrestart, which is part of the server seed; so in effect this notification now *never* fires on servers, it *only* fires on desktops. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 5 05:39:06 2022 InstallationDate: Installed on 2019-12-23 (863 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-15 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1971650/+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 1970244] Re: [SRU] Enable support for Zed Cloud Archive
This has been successfully verified. root@j1:~# apt policy software-properties-common software-properties-common: Installed: 0.99.22.1 Candidate: 0.99.22.1 Version table: *** 0.99.22.1 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.99.22 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages root@j1:~# apt policy keystone-common root@j1:~# sudo add-apt-repository cloud-archive:zed-proposed --yes ... root@j1:~# sudo add-apt-repository cloud-archive:zed --yes ... root@j1:~# sudo apt install keystone-common --yes ... root@j1:~# apt policy keystone-common keystone-common: Installed: 2:21.0.0+git2022050409.884f88148-0ubuntu1~cloud0 Candidate: 2:21.0.0+git2022050409.884f88148-0ubuntu1~cloud0 Version table: *** 2:21.0.0+git2022050409.884f88148-0ubuntu1~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-proposed/zed/main amd64 Packages 500 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/zed/main amd64 Packages 100 /var/lib/dpkg/status 2:21.0.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1970244 Title: [SRU] Enable support for Zed Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Committed Bug description: Please add support for: cloud-archive:zed cloud-archive:zed-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the zed cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:zed sudo add-apt-repository cloud-archive:zed-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970244/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
The 'unsafe legacy renegotiation disabled' error is one of error mentioned in this bug report. Another one is 'SSL_connect error:0A0C0103:SSL routines::internal error' after enabling legacy renegotiation. This issue is discussed in Fedora's Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2069239 Adding patches: - https://src.fedoraproject.org/rpms/openssl/blob/rawhide/f/0049-Allow-disabling-of-SHA1-signatures.patch - https://src.fedoraproject.org/rpms/openssl/blob/rawhide/f/0052-Allow-SHA1-in-seclevel-1-if-rh-allow-sha1-signatures.patch and including `rh-allow-sha1-signatures = true` in `openssl.cnf` fixed problem for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Status in wpa package in Debian: Unknown Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971669] Re: Can't even launch `ubuntu-bug` console application to report any other bug!
Your log shows:
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/home/khteh/.local/lib/python3.10/site-packages/httplib2/__init__.py", line
52, in
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: from . import auth
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/home/khteh/.local/lib/python3.10/site-packages/httplib2/auth.py", line 20, in
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: auth_param_name =
token.copy().setName("auth-param-name").addParseAction(pp.downcaseTokens)
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: AttributeError:
module 'pyparsing' has no attribute 'downcaseTokens'
So, you have a locally-installed httplib2 in your home directory which
is not compatible with the pyparsing from the system. You will need to
remove this.
** Package changed: update-notifier (Ubuntu) => apport (Ubuntu)
** Changed in: apport (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1971669
Title:
Can't even launch `ubuntu-bug` console application to report any other
bug!
Status in apport package in Ubuntu:
Invalid
Bug description:
$ ubuntu-bug
Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 596, in
app = GTKUserInterface()
File "/usr/share/apport/apport-gtk", line 56, in __init__
apport.ui.UserInterface.__init__(self)
File "/usr/lib/python3/dist-packages/apport/ui.py", line 209, in __init__
self.crashdb = apport.crashdb.get_crashdb(None)
File "/usr/lib/python3/dist-packages/apport/crashdb.py", line 842, in
get_crashdb
return load_crashdb(auth_file, settings['databases'][name])
File "/usr/lib/python3/dist-packages/apport/crashdb.py", line 850, in
load_crashdb
m = __import__('apport.crashdb_impl.' + spec['impl'], globals(),
locals(), ['CrashDatabase'])
File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py",
line 15, in
from httplib2 import FailedToDecompressContent
File
"/home/khteh/.local/lib/python3.10/site-packages/httplib2/__init__.py", line
52, in
from . import auth
File "/home/khteh/.local/lib/python3.10/site-packages/httplib2/auth.py",
line 20, in
auth_param_name =
token.copy().setName("auth-param-name").addParseAction(pp.downcaseTokens)
AttributeError: module 'pyparsing' has no attribute 'downcaseTokens'
$ cat /proc/version_signature
Ubuntu 5.15.0-27.28-generic 5.15.30
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04 LTS
Release: 22.04
Codename: jammy
$ sudo journalctl -f
May 05 14:43:38 khteh-p17-2i systemd[1885]: Started Tracker metadata
extractor.
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: Traceback (most
recent call last):
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/usr/share/apport/apport-gtk", line 596, in
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: app =
GTKUserInterface()
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/usr/share/apport/apport-gtk", line 56, in __init__
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]:
apport.ui.UserInterface.__init__(self)
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/usr/lib/python3/dist-packages/apport/ui.py", line 209, in __init__
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: self.crashdb
= apport.crashdb.get_crashdb(None)
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/usr/lib/python3/dist-packages/apport/crashdb.py", line 842, in get_crashdb
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: return
load_crashdb(auth_file, settings['databases'][name])
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/usr/lib/python3/dist-packages/apport/crashdb.py", line 850, in load_crashdb
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: m =
__import__('apport.crashdb_impl.' + spec['impl'], globals(), locals(),
['CrashDatabase'])
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 15, in
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: from
httplib2 import FailedToDecompressContent
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/home/khteh/.local/lib/python3.10/site-packages/httplib2/__init__.py", line
52, in
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: from .
import auth
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/home/khteh/.local/lib/python3.10/site-packages/httplib2/auth.py", line 20, in
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]:
[Touch-packages] [Bug 1971669] [NEW] Can't even launch `ubuntu-bug` console application to report any other bug!
You have been subscribed to a public bug:
$ ubuntu-bug
Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 596, in
app = GTKUserInterface()
File "/usr/share/apport/apport-gtk", line 56, in __init__
apport.ui.UserInterface.__init__(self)
File "/usr/lib/python3/dist-packages/apport/ui.py", line 209, in __init__
self.crashdb = apport.crashdb.get_crashdb(None)
File "/usr/lib/python3/dist-packages/apport/crashdb.py", line 842, in
get_crashdb
return load_crashdb(auth_file, settings['databases'][name])
File "/usr/lib/python3/dist-packages/apport/crashdb.py", line 850, in
load_crashdb
m = __import__('apport.crashdb_impl.' + spec['impl'], globals(), locals(),
['CrashDatabase'])
File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line
15, in
from httplib2 import FailedToDecompressContent
File "/home/khteh/.local/lib/python3.10/site-packages/httplib2/__init__.py",
line 52, in
from . import auth
File "/home/khteh/.local/lib/python3.10/site-packages/httplib2/auth.py", line
20, in
auth_param_name =
token.copy().setName("auth-param-name").addParseAction(pp.downcaseTokens)
AttributeError: module 'pyparsing' has no attribute 'downcaseTokens'
$ cat /proc/version_signature
Ubuntu 5.15.0-27.28-generic 5.15.30
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04 LTS
Release:22.04
Codename: jammy
$ sudo journalctl -f
May 05 14:43:38 khteh-p17-2i systemd[1885]: Started Tracker metadata extractor.
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: Traceback (most
recent call last):
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/usr/share/apport/apport-gtk", line 596, in
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: app =
GTKUserInterface()
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/usr/share/apport/apport-gtk", line 56, in __init__
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]:
apport.ui.UserInterface.__init__(self)
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/usr/lib/python3/dist-packages/apport/ui.py", line 209, in __init__
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: self.crashdb =
apport.crashdb.get_crashdb(None)
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/usr/lib/python3/dist-packages/apport/crashdb.py", line 842, in get_crashdb
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: return
load_crashdb(auth_file, settings['databases'][name])
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/usr/lib/python3/dist-packages/apport/crashdb.py", line 850, in load_crashdb
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: m =
__import__('apport.crashdb_impl.' + spec['impl'], globals(), locals(),
['CrashDatabase'])
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 15, in
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: from httplib2
import FailedToDecompressContent
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/home/khteh/.local/lib/python3.10/site-packages/httplib2/__init__.py", line
52, in
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: from . import
auth
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File
"/home/khteh/.local/lib/python3.10/site-packages/httplib2/auth.py", line 20, in
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]:
auth_param_name =
token.copy().setName("auth-param-name").addParseAction(pp.downcaseTokens)
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: AttributeError:
module 'pyparsing' has no attribute 'downcaseTokens'
** Affects: apport (Ubuntu)
Importance: Undecided
Status: Invalid
** Tags: 22.04 bot-comment
--
Can't even launch `ubuntu-bug` console application to report any other bug!
https://bugs.launchpad.net/bugs/1971669
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to apport 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 1971763] [NEW] www-browser is not satisfied by the default Firefox snap
Public bug reported: When installing a package that has the virtual-packages www-browser as a dependency, the Firefox snap is not taken into account. This leads to wslu being installed on Ubuntu 22.04 Desktop (notably when installing the GIMP translation packages), which breaks the ding desktop behaviour: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1971757 ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: dependencies dependency desktop ding firefox wslu www-browser -- 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/1971763 Title: www-browser is not satisfied by the default Firefox snap Status in apt package in Ubuntu: New Bug description: When installing a package that has the virtual-packages www-browser as a dependency, the Firefox snap is not taken into account. This leads to wslu being installed on Ubuntu 22.04 Desktop (notably when installing the GIMP translation packages), which breaks the ding desktop behaviour: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1971757 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1971763/+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 1971756] [NEW] libzmqpp-dev release on jammy
Public bug reported: libzmqpp-dev is still not available on jammy. ** Affects: zmqpp (Ubuntu) Importance: Undecided Status: New ** Also affects: zmqpp (Ubuntu) Importance: Undecided Status: New ** No longer affects: zeromq3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1971756 Title: libzmqpp-dev release on jammy Status in zmqpp package in Ubuntu: New Bug description: libzmqpp-dev is still not available on jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zmqpp/+bug/1971756/+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 1214787] Re: busybox crashed with signal 7
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1214787 Title: busybox crashed with signal 7 Status in busybox package in Ubuntu: New Bug description: busybox crashed with signal 7 ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: busybox-static 1:1.20.0-8.1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic i686 ApportVersion: 2.12.1-0ubuntu2 Architecture: i386 CasperVersion: 1.336 Date: Wed Aug 21 12:56:53 2013 Dependencies: Disassembly: => 0x80a7990:Cannot access memory at address 0x80a7990 ExecutablePath: /bin/busybox LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130821) MarkForUpload: True ProcCmdline: /bin/busybox tail -f /var/log/installer/debug -f /var/log/syslog -q ProcEnviron: LANG=en_US.UTF-8 TERM=xterm PATH=(custom, no user) ProcMaps: 08048000-081fc000 r-xp 07:00 12 /bin/busybox 081fc000-081fe000 rw-p 001b3000 07:00 12 /bin/busybox 081fe000-08203000 rw-p 00:00 0 b771c000-b771d000 r-xp 00:00 0 [vdso] bfa43000-bfa64000 rw-p 00:00 0 [stack] Signal: 7 SourcePackage: busybox StacktraceTop: ?? () ?? () ?? () Title: busybox crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1214787/+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 1970050] Re: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1970050 Title: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: After upgrading today from 20.04 LTS to 22.04 HDMI Audio does not work at all. Audio from speakers from a headphone jack works fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 23 21:13:23 2022 InstallationDate: Installed on 2020-04-24 (729 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Built-in Audio - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to jammy on 2022-04-23 (0 days ago) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97M-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH97M-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97M-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H97M-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970050/+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 1971749] [NEW] package zlib1g:amd64 1:1.2.11.dfsg-2ubuntu1.3 failed to install/upgrade: package zlib1g:amd64 is already installed and configured
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zlib1g:amd64 1:1.2.11.dfsg-2ubuntu1.3 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.3 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:125:3190589:2022-05-03 14:29:19.678773641 -0300:2022-05-03 14:29:20.678773641 -0300:/var/crash/_usr_bin_node.1000.crash 640:0:125:150359:2022-05-05 13:43:07.279695749 -0300:2022-05-05 13:43:08.279695749 -0300:/var/crash/liblzma5:amd64.0.crash 600:0:125:137976:2022-05-02 17:08:59.743741035 -0300:2022-05-02 17:09:00.743741035 -0300:/var/crash/zlib1g:amd64.0.crash Date: Mon May 2 17:09:00 2022 ErrorMessage: package zlib1g:amd64 is already installed and configured InstallationDate: Installed on 2022-02-19 (74 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/local/bin/python3.10, Python 3.10.3, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: zlib Title: package zlib1g:amd64 1:1.2.11.dfsg-2ubuntu1.3 failed to install/upgrade: package zlib1g:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zlib (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1971749 Title: package zlib1g:amd64 1:1.2.11.dfsg-2ubuntu1.3 failed to install/upgrade: package zlib1g:amd64 is already installed and configured Status in zlib package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zlib1g:amd64 1:1.2.11.dfsg-2ubuntu1.3 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.3 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:125:3190589:2022-05-03 14:29:19.678773641 -0300:2022-05-03 14:29:20.678773641 -0300:/var/crash/_usr_bin_node.1000.crash 640:0:125:150359:2022-05-05 13:43:07.279695749 -0300:2022-05-05 13:43:08.279695749 -0300:/var/crash/liblzma5:amd64.0.crash 600:0:125:137976:2022-05-02 17:08:59.743741035 -0300:2022-05-02 17:09:00.743741035 -0300:/var/crash/zlib1g:amd64.0.crash Date: Mon May 2 17:09:00 2022 ErrorMessage: package zlib1g:amd64 is already installed and configured InstallationDate: Installed on 2022-02-19 (74 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/local/bin/python3.10, Python 3.10.3, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: zlib Title: package zlib1g:amd64 1:1.2.11.dfsg-2ubuntu1.3 failed to install/upgrade: package zlib1g:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1971749/+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 1971409] Re: value_copy: Assertion `arg->contents != nullptr' failed.
Got the same issue in VSCode using gdb 12.0.90. I compiled gdb 12.1 and it works. Can we get it updated to 12.1? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1971409 Title: value_copy: Assertion `arg->contents != nullptr' failed. Status in gdb package in Ubuntu: New Bug description: When debugging RP2040 with vscode this assert makes gdb crash. This is a new assert, that wasn't present in gdb 11. The fix is easy, replace `if (!value_lazy (val))` to `if (!value_lazy (val) && arg->contents != nullptr) `. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971409/+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 1872063] Re: NetworkManager IWD, wpa_supplicant backends
** Package changed: iwd (Ubuntu) => network-manager (Ubuntu) ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1872063 Title: NetworkManager IWD, wpa_supplicant backends Status in network-manager package in Ubuntu: Confirmed Bug description: focal, network-manager 1.22.10, NetworkManager now support (alternative) IWD backend via `wifi.backend=iwd`, but the package still depends on wpa_supplicant. NM should require [iwd OR wpa_supplicant]. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1872063/+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 1872063] [NEW] NetworkManager IWD, wpa_supplicant backends
You have been subscribed to a public bug: focal, network-manager 1.22.10, NetworkManager now support (alternative) IWD backend via `wifi.backend=iwd`, but the package still depends on wpa_supplicant. NM should require [iwd OR wpa_supplicant]. ** Affects: network-manager (Ubuntu) Importance: Low Status: Confirmed ** Tags: packaging -- NetworkManager IWD, wpa_supplicant backends https://bugs.launchpad.net/bugs/1872063 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager 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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in snapd package in Debian: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
Same problem in 21.10 with Firefox, Chromium, and Waterfox Classic. All have suddenly stopped working with error /user.slice/user-1000.slice/session-30.scope is not a snap cgroup I'm running MATE inside X2Go -- 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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in snapd package in Debian: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+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 1814072] Re: software-properties-gtk does not recognize https mirrors under Ubuntu Software
The mirror list is shipped in python-apt and updated with each python- apt update, and with each Ubuntu point release based on the launchpad mirror feed https://launchpad.net/ubuntu/+archivemirrors-rss. Additional updates to just the mirror list are not made. The mirror method is supported using the official mirror://mirrors.ubuntu.com/mirrors.txt url. Additional urls are custom modifications and not recognized by aptsources as Ubuntu mirrors. It might be possible to make aptsources look at Origin field in the Release file if you have downloaded them, however that's prone to breakage if you switch releases, so it's not optimal. In any case this is not a bug in software-properties. Please open a bug against python- apt if you believe we have reasonable means of supporting unofficial mirrors like official ones. -- 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/1814072 Title: software-properties-gtk does not recognize https mirrors under Ubuntu Software Status in software-properties package in Ubuntu: Invalid Bug description: How to reproduce: 1. Change main Ubuntu mirrors to https in /etc/apt/sources.list and do "apt update" 2. Run software-properties-gtk 3. Go to "Ubuntu Software" tab What happens: The tab "Ubuntu Software" does not list https mirrors. The corresponding boxes are not checked, the correct "Download from" entry is not selected and falls back to "Main server". The correct sources are just listed under "Other Software". What should happen: The tab "Ubuntu Software" should recognize the https mirrors from apt and tick the corresponding boxes and select the correct server in the "Download from" list. Ubuntu 18.04 software-properties-gtk 0.96.24.32.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1814072/+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 1970402] Re: Initrd out of memory error after upgrade to 22.04
** Tags added: fr-2355 ** Tags removed: fr-2355 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/1970402 Title: Initrd out of memory error after upgrade to 22.04 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: After upgrading to 22.04 system is unbootable because of "out of memory" error when loading initial ramdisk. I was able to fix it by editing cat /etc/initramfs-tools/initramfs.conf and changing configuration to: MODULES=dep COMPRESS=xz RUNSIZE=15% Not sure which one helped, but I can test it if needed. System information: Description:Ubuntu 22.04 LTS Release:22.04 initramfs-tools: Installed: 0.140ubuntu13 Candidate: 0.140ubuntu13 Version table: *** 0.140ubuntu13 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+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 574287] Re: tasksel: forcefully removes packages when tasks overlap
** Tags added: fr-1988 -- 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/574287 Title: tasksel: forcefully removes packages when tasks overlap Status in apt package in Ubuntu: Invalid Status in tasksel package in Ubuntu: Confirmed Status in tasksel package in Debian: Fix Released Bug description: TEST CASE 1. Boot Lucid LiveCD 2. run "sudo tasksel" and select "virtual machine host" 3. run "sudo tasksel" and deselect "virtual machine host" 4. watch how tasksel uninstalls your system OBSERVATIONS What seems to happen is that apt vengefully removes ALL of the items associated with one task, including several base dependencies of other tasks (e.g. ubuntu-desktop) One illustrative example is the openssh-server task: This one includes the packages openssh-server, tcpd and libwrap0. From a normal ubuntu-desktop (e.g. ~liveCD) both tcpd and libwrap0 are already installed, and the task-install pulls in only openssh-server. However when the task is removed, all these three packages (openssh-server, tcpd and libwrap0) are forcefully removed. Since libwrap0 is a core dependency of gnome, a large part of gnome will be removed alongside the removal of the task. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/574287/+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 1814072] Re: software-properties-gtk does not recognize https mirrors under Ubuntu Software
** Changed in: software-properties (Ubuntu) Status: Confirmed => Invalid -- 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/1814072 Title: software-properties-gtk does not recognize https mirrors under Ubuntu Software Status in software-properties package in Ubuntu: Invalid Bug description: How to reproduce: 1. Change main Ubuntu mirrors to https in /etc/apt/sources.list and do "apt update" 2. Run software-properties-gtk 3. Go to "Ubuntu Software" tab What happens: The tab "Ubuntu Software" does not list https mirrors. The corresponding boxes are not checked, the correct "Download from" entry is not selected and falls back to "Main server". The correct sources are just listed under "Other Software". What should happen: The tab "Ubuntu Software" should recognize the https mirrors from apt and tick the corresponding boxes and select the correct server in the "Download from" list. Ubuntu 18.04 software-properties-gtk 0.96.24.32.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1814072/+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 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon
** Tags added: fr-2353 ** Tags removed: rls-kk-incoming -- 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/1969976 Title: DynamicUser=1 doesn't get along with services that need dbus-daemon Status in Fwupd: Fix Released Status in systemd: New Status in fwupd package in Ubuntu: New Status in systemd package in Ubuntu: Won't Fix Status in fwupd source package in Focal: New Status in systemd source package in Focal: Won't Fix Status in fwupd source package in Impish: New Status in systemd source package in Impish: Won't Fix Status in fwupd source package in Jammy: New Status in systemd source package in Jammy: Won't Fix Bug description: Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu 20.04, that fwupd-refresh.service always fails to run. This has been root caused down to the changes in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 Unfortunately this is an upstream issue introduced by stable systemd. https://github.com/systemd/systemd/issues/22737 The problem also occurs in Ubuntu 22.04 with a newer systemd release. As discussed in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61 it's a tradeoff of issues. So within Ubuntu something probably needs to be done about fwupd-refresh.service. One proposal is to remove DynamicUser=yes from the systemd unit, but this will mean fwupdgmr refresh runs as root. It's relatively sandboxed by other security mechanisms, but still not ideal. Could we repurpose any other service account? Or alternatively we can make a new fwupd service account that this systemd unit uses. To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1969976/+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 1964483] Re: Update supported mirror protocol according to official archive mirrors list
*** This bug is a duplicate of bug 1814072 *** https://bugs.launchpad.net/bugs/1814072 charite did not support https at the time the mirror list in python-apt was created. The mirror list is updated with each python-apt update, and with each Ubuntu point release. With the next update, only https will be supported on the charite mirror as advertised by the launchpad mirror feed https://launchpad.net/ubuntu/+archivemirrors-rss ** This bug has been marked a duplicate of bug 1814072 software-properties-gtk does not recognize https mirrors under Ubuntu Software -- 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/1964483 Title: Update supported mirror protocol according to official archive mirrors list Status in software-properties package in Ubuntu: New Bug description: While mirrors listed on https://launchpad.net/ubuntu/+archivemirrors support https, this is not reflected in software-properties-gtk -> Download from -> other dialogue. Example: Charite Berlin supports https, but only http is available from the "Protocol" dialogue. Editing /etc/apt/sources.list mitigates the issue, though https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/1814072 is still unresolved. lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.99.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1964483/+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 1971523] Re: Static build does not work for libmnl (-lmnl)
Reported in; https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010616 ** Bug watch added: Debian Bug tracker #1010616 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010616 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libmnl in Ubuntu. https://bugs.launchpad.net/bugs/1971523 Title: Static build does not work for libmnl (-lmnl) Status in libmnl package in Ubuntu: Triaged Bug description: Example; # gcc -o /tmp/hello /tmp/hello.c -lmnl (dynamic libs work) # gcc -static -o /tmp/hello /tmp/hello.c -lmnl /usr/bin/ld: cannot find -lmnl: No such file or directory My program uses both -lmnl and -lnetfilter_queue and in Ubuntu 20.04 the -lnetfilter_queue did not work and -lmnl worked for static builds. In Ubuntu 22.04 the problem is reversed, -lnetfilter_queue works but -lmnl doesn't for static builds. This is very awkward during the transition 20.04->22.04 when both should be supported. I compensated in Ubuntu 20.04 by building netfilter_queue locally; https://github.com/Nordix/nfqueue-loadbalancer#build ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libmnl0:amd64 1.0.4-3build2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed May 4 07:33:26 2022 InstallationDate: Installed on 2018-09-07 (1334 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: libmnl UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/1971523/+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 1967965] Re: "Other problem" and "Display" options are swapped
** Tags added: fr-2351 ** Tags removed: rls-kk-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1967965 Title: "Other problem" and "Display" options are swapped Status in apport package in Ubuntu: New Bug description: When attempting to report https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967963 I was unable to use `ubuntu-bug firefox`, so I just ran `ubuntu-bug`. However doing so gave me a menu with unrelated option (as expected) and an "Other problem..." option. I assumed this was for generic other bugs, as I think is reasonable; however, it brings me to a menu that only makes sense for display-related bugs. I think this text should be changed to note that; perhaps "Other display problem...". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:124:13488049:2022-03-30 13:20:08.905176436 -0500:2022-03-30 13:20:07.977480154 -0500:/var/crash/_usr_bin_telegram-desktop.1000.crash 640:0:124:755694:2022-03-30 13:17:26.598466630 -0500:2022-03-30 13:17:26.258453989 -0500:/var/crash/_usr_libexec_udisks2_udisksd.0.crash CurrentDesktop: KDE Date: Tue Apr 5 19:58:56 2022 InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1967965/+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 1971650] Re: wrong check for "server" in libssl3.postinst
** Tags added: fr-2350 ** Tags removed: fr-2350 rls-jj-incoming rls-kk-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1971650 Title: wrong check for "server" in libssl3.postinst Status in openssl package in Ubuntu: New Bug description: A security update has just been applied to my system for openssl, and the 'reboot required' message just popped on my desktop. I looked to see why this was, and found the following code in the libssl3 postinst: # Here we issue the reboot notification for upgrades and # security updates. We do want services to be restarted when we # update for a security issue, but planned by the sysadmin, not # automatically. # Only issue the reboot notification for servers; we proxy this by # testing that the X server is not running (LP: #244250) if ! pidof /usr/lib/xorg/Xorg > /dev/null && [ -x /usr/share/update-notifier/notify-reboot-required ]; then /usr/share/update-notifier/notify-reboot-required fi Now, AFAIK this is the only package that interfaces with notify- reboot-required but omits the notification on desktops, so that seems to be an inconsistent policy; but even if we thought that was the correct policy to apply, the above check for a desktop is not because it doesn't match in the case the user is running Xwayland, which most users not using the nvidia driver will be doing now by default. Also, this is now inside a block that checks for the presence of needrestart, which is part of the server seed; so in effect this notification now *never* fires on servers, it *only* fires on desktops. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 5 05:39:06 2022 InstallationDate: Installed on 2019-12-23 (863 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-15 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1971650/+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 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore
is this going to be published for focal ever? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1918044 Title: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore Status in libgweather: Unknown Status in gnome-weather package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: Fix Released Status in gnome-weather source package in Focal: Confirmed Status in libgweather source package in Focal: Confirmed Status in gnome-weather package in Fedora: New Bug description: [Impact] The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS == Version 3.36.2 == This version switches the yr.no backend to use met.no instead. Please note that this backport is only meant as a compatibility layer. Where at all possible, the newer libgweather 40 should be used as applications cannot fully comply with the met.no ToS otherwise. [Test case] - gnome-weather shows the weather forecast - gnome-shell shows the weather forecast in the calendar menu [Regression potential] - Weather forecast is totally broken now and can't be more broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+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 1971523] Re: Static build does not work for libmnl (-lmnl)
Hello Lars and thanks for this bug report. I can confirm this: libmnl- dev 1.0.4-2 installs /usr/lib/x86_64-linux-gnu/libmnl.a while libmnl-dev 1.0.4-3 does not. I tracked this down to this Debian packaging change (see the debian/libmnl-dev.install diff): https://salsa.debian.org/pkg-netfilter-team/pkg- libmnl/-/commit/3526970e4dfb5598a9023496211c908e9ab7c9dc Dropping the .a file looks like unintentional to me, at least by reading the commit message. Ideally this should be fixed in Debian, to make Debian benefit from the fix and keep the packages in sync, lowering the maintenance work from the Ubuntu side. Do you you think you can file a bug in Debian against the libmnl source package and report it back here? This would speed up things. Thanks! ** Tags added: server-todo ** Changed in: libmnl (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libmnl in Ubuntu. https://bugs.launchpad.net/bugs/1971523 Title: Static build does not work for libmnl (-lmnl) Status in libmnl package in Ubuntu: Triaged Bug description: Example; # gcc -o /tmp/hello /tmp/hello.c -lmnl (dynamic libs work) # gcc -static -o /tmp/hello /tmp/hello.c -lmnl /usr/bin/ld: cannot find -lmnl: No such file or directory My program uses both -lmnl and -lnetfilter_queue and in Ubuntu 20.04 the -lnetfilter_queue did not work and -lmnl worked for static builds. In Ubuntu 22.04 the problem is reversed, -lnetfilter_queue works but -lmnl doesn't for static builds. This is very awkward during the transition 20.04->22.04 when both should be supported. I compensated in Ubuntu 20.04 by building netfilter_queue locally; https://github.com/Nordix/nfqueue-loadbalancer#build ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libmnl0:amd64 1.0.4-3build2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed May 4 07:33:26 2022 InstallationDate: Installed on 2018-09-07 (1334 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: libmnl UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/1971523/+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 1971715] [NEW] 22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8
Public bug reported: On Ubuntu 22.04 Jammy: idn -a "xxx-tést.eu" idn: could not convert from ASCII to UTF-8 And idn -u "xn--xxx-tst-fya.eu" idn: could not convert from UTF-8 to ASCII Expected: Successfully conversion from ASCII to UTF-8 Ubuntu 20.04 / 18.04 it works fine Also with idn2 from UTF-8 to ASCII works as expected how ever support lacks from ASCII to UTF-8 Description:Ubuntu 22.04 LTS Release:22.04 root@test:~# echo $LC_ALL C.UTF-8 root@test:~# apt-cache policy idn idn: Installed: 1.38-4build1 Candidate: 1.38-4build1 Version table: *** 1.38-4build1 500 500 https://mirror.hetzner.com/ubuntu/packages jammy/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: libidn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1971715 Title: 22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8 Status in libidn package in Ubuntu: New Bug description: On Ubuntu 22.04 Jammy: idn -a "xxx-tést.eu" idn: could not convert from ASCII to UTF-8 And idn -u "xn--xxx-tst-fya.eu" idn: could not convert from UTF-8 to ASCII Expected: Successfully conversion from ASCII to UTF-8 Ubuntu 20.04 / 18.04 it works fine Also with idn2 from UTF-8 to ASCII works as expected how ever support lacks from ASCII to UTF-8 Description: Ubuntu 22.04 LTS Release: 22.04 root@test:~# echo $LC_ALL C.UTF-8 root@test:~# apt-cache policy idn idn: Installed: 1.38-4build1 Candidate: 1.38-4build1 Version table: *** 1.38-4build1 500 500 https://mirror.hetzner.com/ubuntu/packages jammy/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1971715/+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 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
** Changed in: openssl (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Jammy: In Progress Status in openssl source package in Kinetic: Fix Committed Bug description: [Impact] Due to the case comparison differences in the Turkish locale, some routines in OpenSSL fail to recognize some algorithm names as valid, unexpectedly breaking crypto. [Test Plan] This bug is really easy to trigger: sudo locale-gen tr_TR.UTF-8 LANG=C curl https://ubuntu.com/ > /dev/null # This work LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This fails The error is curl: (35) error:0372:digital envelope routines::decode error [Where problems could occur] This patch set is relatively massive, and can cause regressions, as illustrated by the patch #5 which fixes one such regression. Those regressions would likely show up as either libssl crashes, in case of uninitialized objects, or as algorithm selection failures if somehow the case comparison is buggy. [Other Info] The fix has already been released upstream as part of their 3.0.3 release. [Original report] I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUS DESCRIPTION cc-eal yes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+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 1971712] [NEW] Add support for Intel DG2
Public bug reported: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New -- 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/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in linux-oem-5.17 source package in Jammy: New Status in mesa source package in Jammy: New Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1971704] [NEW] Wayland/Gnome Shell freezes propably on displaying Gnome Setting
Public bug reported: I got occasional freeze on new Ubuntu 22.04 LTS. The machine is Lenovo 7/8th gen Carbon with 10th gen Intel. But after the latest freeze and reboot (because of the freeze) I logged in and then it freezes everytime, propably when loading gnome setting, I see the icon emerging on the dock and freezing. Just before the freeze there was kernel and some packages upgrade) The report is from previous kernel which I thought it was culprit but it seems not. I can login to the machine with SSH therefore I produced this report. There"s process getting 100% of 1 cpu core: gnome-shell After a while it blanks (as schedules) to login manager and I can login back and same story. I see following error in syslog May 5 14:02:13 graf gnome-shell[1740]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed May 5 14:02:13 graf gnome-shell[1740]: cr_declaration_parse_list_from_buf: assertion 'parser' failed May 5 14:02:13 graf gnome-shell[1740]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed May 5 14:02:13 graf gnome-shell[1740]: cr_declaration_parse_list_from_buf: assertion 'parser' failed May 5 14:02:13 graf gnome-shell[1740]: ATK Bridge is disabled but a11y has already been enabled. May 5 14:02:14 graf gnome-shell[1740]: Registering session with GDM May 5 14:02:17 graf gnome-shell[1740]: Could not open device /dev/input/event17: Could not get device info for path /dev/input/event17: No such file or directory May 5 14:02:17 graf gnome-shell[1740]: Could not open device /dev/input/event16: GDBus.Error:System.Error.ENODEV: No such device May 5 14:02:19 graf gnome-shell[1740]: Removing a network device that was not added May 5 14:02:19 graf gnome-shell[1740]: Removing a network device that was not added May 5 14:02:27 graf gnome-shell[3287]: Running GNOME Shell (using mutter 42.0) as a Wayland display server May 5 14:02:27 graf gnome-shell[3287]: Device '/dev/dri/card0' prefers shadow buffer May 5 14:02:27 graf gnome-shell[3287]: Added device '/dev/dri/card0' (i915) using atomic mode setting. May 5 14:02:27 graf gnome-shell[3287]: Created gbm renderer for '/dev/dri/card0' May 5 14:02:27 graf gnome-shell[3287]: Boot VGA GPU /dev/dri/card0 selected as primary May 5 14:02:27 graf gnome-shell[3287]: Using public X11 display :0, (using :1 for managed services) May 5 14:02:27 graf gnome-shell[3287]: Using Wayland display name 'wayland-0' May 5 14:02:27 graf gnome-shell[3287]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. May 5 14:02:27 graf gnome-shell[3287]: Will monitor session 2 May 5 14:02:27 graf dbus-daemon[3106]: [session uid=1000 pid=3106] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.36' (uid=1000 pid=3287 comm="/usr/bin/gnome-shell " label="unconfined") May 5 14:02:27 graf dbus-daemon[3106]: [session uid=1000 pid=3106] Activating service name='org.gnome.Shell.CalendarServer' requested by ':1.36' (uid=1000 pid=3287 comm="/usr/bin/gnome-shell " label="unconfined") May 5 14:02:27 graf dbus-daemon[3106]: [session uid=1000 pid=3106] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.39' (uid=1000 pid=3334 comm="/usr/libexec/gnome-shell-calendar-server " label="unconfined") May 5 14:02:27 graf gnome-shell[3287]: Telepathy is not available, chat integration will be disabled. May 5 14:02:27 graf dbus-daemon[3106]: [session uid=1000 pid=3106] Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar8' unit='evolution-calendar-factory.service' requested by ':1.39' (uid=1000 pid=3334 comm="/usr/libexec/gnome-shell-calendar-server " label="unconfined") May 5 14:02:27 graf dbus-daemon[3106]: [session uid=1000 pid=3106] Activating service name='org.freedesktop.FileManager1' requested by ':1.36' (uid=1000 pid=3287 comm="/usr/bin/gnome-shell " label="unconfined") May 5 14:02:28 graf dbus-daemon[3106]: [session uid=1000 pid=3106] Activating service name='org.gnome.Shell.Notifications' requested by ':1.36' (uid=1000 pid=3287 comm="/usr/bin/gnome-shell " label="unconfined") May 5 14:02:28 graf at-spi-dbus-bus.desktop[3293]: dbus-daemon[3293]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=3287 comm="/usr/bin/gnome-shell " label="unconfined") May 5 14:02:28 graf gnome-shell[3287]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation May 5 14:02:28 graf gnome-shell[3646]: (WW) Option "-listen" for file descriptors is deprecated May 5 14:02:28 graf gnome-shell[3646]: Please use "-listenfd" instead. May 5 14:02:28 graf gnome-shell[3646]: (WW) Option "-listen" for file descriptors is deprecated May 5 14:02:28 graf gnome-shell[3646]: Please use "-listenfd" instead. May 5 14:02:28 graf
[Touch-packages] [Bug 1953065] Re: 2.13.0 FTBFS
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/ust/+git/ust/+merge/421513
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ust in Ubuntu.
https://bugs.launchpad.net/bugs/1953065
Title:
2.13.0 FTBFS
Status in LTTng-UST:
Unknown
Status in ust package in Ubuntu:
Fix Released
Bug description:
I tried to merge ust from debian into ubuntu, to fix a build-time
dependency, but stumbled on an FTBFS with that version.
I filed upstream bug at https://bugs.lttng.org/issues/1337
It basically happens in some new test cases that were added in 2.13.0
and crash when we build it using our default -Wl,-Bsymbolic-flags
linker option, which we have been using for years in Ubuntu.
Here is the testsuite log output:
lttng-ust 2.14.0-pre: tests/test-suite.log
# TOTAL: 246
# PASS: 241
# SKIP: 0
# XFAIL: 0
# FAIL: 4
# XPASS: 0
# ERROR: 1
.. contents:: :depth: 2
ERROR: regression/abi0-conflict/test_abi0_conflict
==
1..22
# LD_PRELOAD
# regression/abi0-conflict/test_abi0_conflict: LD_PRELOAD
ok 1 - LD_PRELOAD: no-ust app works
PASS: regression/abi0-conflict/test_abi0_conflict 1 - LD_PRELOAD: no-ust app
works
ok 2 - LD_PRELOAD: no-ust app with abi0 preload succeeds
PASS: regression/abi0-conflict/test_abi0_conflict 2 - LD_PRELOAD: no-ust app
with abi0 preload succeeds
./regression/abi0-conflict/test_abi0_conflict: line 56: 592651 Aborted
(core dumped) LD_PRELOAD="${LIBFAKEUST0}:${LIBUST1}"
"${CURDIR}/app_noust" > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 3 - LD_PRELOAD: no-ust app with abi0 and abi1 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 3 - LD_PRELOAD: no-ust app
with abi0 and abi1 preload fails
./regression/abi0-conflict/test_abi0_conflict: line 59: 592652 Aborted
(core dumped) LD_PRELOAD="${LIBUST1}:${LIBFAKEUST0}"
"${CURDIR}/app_noust" > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 4 - LD_PRELOAD: no-ust app with abi1 and abi0 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 4 - LD_PRELOAD: no-ust app
with abi1 and abi0 preload fails
ok 5 - LD_PRELOAD: ust app works
PASS: regression/abi0-conflict/test_abi0_conflict 5 - LD_PRELOAD: ust app
works
./regression/abi0-conflict/test_abi0_conflict: line 68: 592669 Aborted
(core dumped) LD_PRELOAD="${LIBFAKEUST0}" "${CURDIR}/app_ust" >
"$STD_OUTPUT" 2> "$STD_ERROR"
ok 6 - LD_PRELOAD: ust app with abi0 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 6 - LD_PRELOAD: ust app
with abi0 preload fails
./regression/abi0-conflict/test_abi0_conflict: line 71: 592683 Aborted
(core dumped) LD_PRELOAD="${LIBFAKEUST0}:${LIBUST1}"
"${CURDIR}/app_ust" > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 7 - LD_PRELOAD: ust app with abi0 and abi1 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 7 - LD_PRELOAD: ust app
with abi0 and abi1 preload fails
./regression/abi0-conflict/test_abi0_conflict: line 74: 592684 Aborted
(core dumped) LD_PRELOAD="${LIBUST1}:${LIBFAKEUST0}"
"${CURDIR}/app_ust" > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 8 - LD_PRELOAD: ust app with abi1 and abi0 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 8 - LD_PRELOAD: ust app
with abi1 and abi0 preload fails
# dlopen
# regression/abi0-conflict/test_abi0_conflict: dlopen
ok 9 - dlopen: no-ust app works
PASS: regression/abi0-conflict/test_abi0_conflict 9 - dlopen: no-ust app works
ok 10 - dlopen: no-ust app with abi1 and abi1 succeeds
PASS: regression/abi0-conflict/test_abi0_conflict 10 - dlopen: no-ust app
with abi1 and abi1 succeeds
./regression/abi0-conflict/test_abi0_conflict: line 92: 592689 Aborted
(core dumped) LD_LIBRARY_PATH="$LIBFAKEUST0_PATH:$LIBUST1_PATH"
"${CURDIR}/app_noust_dlopen" abi0_abi1 > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 11 - dlopen: no-ust app with abi0 and abi1 fails
PASS: regression/abi0-conflict/test_abi0_conflict 11 - dlopen: no-ust app
with abi0 and abi1 fails
not ok 12 - dlopen: no-ust app with abi1 and abi0 fails
FAIL: regression/abi0-conflict/test_abi0_conflict 12 - dlopen: no-ust app
with abi1 and abi0 fails
# Failed test 'dlopen: no-ust app with abi1 and abi0 fails'
# regression/abi0-conflict/test_abi0_conflict: Failed test 'dlopen: no-ust
app with abi1 and abi0 fails'
# in /home/ubuntu/git/packages/ust/lttng-ust/tests/utils/tap.sh:isnt() at
line 300.
# regression/abi0-conflict/test_abi0_conflict: in
/home/ubuntu/git/packages/ust/lttng-ust/tests/utils/tap.sh:isnt() at line 300.
# got: '0'
# regression/abi0-conflict/test_abi0_conflict: got: '0'
# expected: '0'
# regression/abi0-conflict/test_abi0_conflict: expected: '0'
ok 13 - dlopen:
[Touch-packages] [Bug 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
** Changed in: openssl (Ubuntu Jammy) Assignee: (unassigned) => Graham Inggs (ginggs) ** Changed in: openssl (Ubuntu Kinetic) Assignee: Simon Chopin (schopin) => Graham Inggs (ginggs) ** Changed in: openssl (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: openssl (Ubuntu Kinetic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: In Progress Status in openssl source package in Jammy: In Progress Status in openssl source package in Kinetic: In Progress Bug description: [Impact] Due to the case comparison differences in the Turkish locale, some routines in OpenSSL fail to recognize some algorithm names as valid, unexpectedly breaking crypto. [Test Plan] This bug is really easy to trigger: sudo locale-gen tr_TR.UTF-8 LANG=C curl https://ubuntu.com/ > /dev/null # This work LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This fails The error is curl: (35) error:0372:digital envelope routines::decode error [Where problems could occur] This patch set is relatively massive, and can cause regressions, as illustrated by the patch #5 which fixes one such regression. Those regressions would likely show up as either libssl crashes, in case of uninitialized objects, or as algorithm selection failures if somehow the case comparison is buggy. [Other Info] The fix has already been released upstream as part of their 3.0.3 release. [Original report] I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUS DESCRIPTION cc-eal yes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+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 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
** Changed in: openssl (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: openssl (Ubuntu Jammy) Status: In Progress => Confirmed ** Changed in: openssl (Ubuntu Kinetic) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: In Progress Status in openssl source package in Jammy: In Progress Status in openssl source package in Kinetic: In Progress Bug description: [Impact] Due to the case comparison differences in the Turkish locale, some routines in OpenSSL fail to recognize some algorithm names as valid, unexpectedly breaking crypto. [Test Plan] This bug is really easy to trigger: sudo locale-gen tr_TR.UTF-8 LANG=C curl https://ubuntu.com/ > /dev/null # This work LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This fails The error is curl: (35) error:0372:digital envelope routines::decode error [Where problems could occur] This patch set is relatively massive, and can cause regressions, as illustrated by the patch #5 which fixes one such regression. Those regressions would likely show up as either libssl crashes, in case of uninitialized objects, or as algorithm selection failures if somehow the case comparison is buggy. [Other Info] The fix has already been released upstream as part of their 3.0.3 release. [Original report] I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUS DESCRIPTION cc-eal yes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+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 1953065] Re: 2.13.0 FTBFS
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/ust/+git/ust/+merge/421513
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ust in Ubuntu.
https://bugs.launchpad.net/bugs/1953065
Title:
2.13.0 FTBFS
Status in LTTng-UST:
Unknown
Status in ust package in Ubuntu:
Fix Released
Bug description:
I tried to merge ust from debian into ubuntu, to fix a build-time
dependency, but stumbled on an FTBFS with that version.
I filed upstream bug at https://bugs.lttng.org/issues/1337
It basically happens in some new test cases that were added in 2.13.0
and crash when we build it using our default -Wl,-Bsymbolic-flags
linker option, which we have been using for years in Ubuntu.
Here is the testsuite log output:
lttng-ust 2.14.0-pre: tests/test-suite.log
# TOTAL: 246
# PASS: 241
# SKIP: 0
# XFAIL: 0
# FAIL: 4
# XPASS: 0
# ERROR: 1
.. contents:: :depth: 2
ERROR: regression/abi0-conflict/test_abi0_conflict
==
1..22
# LD_PRELOAD
# regression/abi0-conflict/test_abi0_conflict: LD_PRELOAD
ok 1 - LD_PRELOAD: no-ust app works
PASS: regression/abi0-conflict/test_abi0_conflict 1 - LD_PRELOAD: no-ust app
works
ok 2 - LD_PRELOAD: no-ust app with abi0 preload succeeds
PASS: regression/abi0-conflict/test_abi0_conflict 2 - LD_PRELOAD: no-ust app
with abi0 preload succeeds
./regression/abi0-conflict/test_abi0_conflict: line 56: 592651 Aborted
(core dumped) LD_PRELOAD="${LIBFAKEUST0}:${LIBUST1}"
"${CURDIR}/app_noust" > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 3 - LD_PRELOAD: no-ust app with abi0 and abi1 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 3 - LD_PRELOAD: no-ust app
with abi0 and abi1 preload fails
./regression/abi0-conflict/test_abi0_conflict: line 59: 592652 Aborted
(core dumped) LD_PRELOAD="${LIBUST1}:${LIBFAKEUST0}"
"${CURDIR}/app_noust" > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 4 - LD_PRELOAD: no-ust app with abi1 and abi0 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 4 - LD_PRELOAD: no-ust app
with abi1 and abi0 preload fails
ok 5 - LD_PRELOAD: ust app works
PASS: regression/abi0-conflict/test_abi0_conflict 5 - LD_PRELOAD: ust app
works
./regression/abi0-conflict/test_abi0_conflict: line 68: 592669 Aborted
(core dumped) LD_PRELOAD="${LIBFAKEUST0}" "${CURDIR}/app_ust" >
"$STD_OUTPUT" 2> "$STD_ERROR"
ok 6 - LD_PRELOAD: ust app with abi0 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 6 - LD_PRELOAD: ust app
with abi0 preload fails
./regression/abi0-conflict/test_abi0_conflict: line 71: 592683 Aborted
(core dumped) LD_PRELOAD="${LIBFAKEUST0}:${LIBUST1}"
"${CURDIR}/app_ust" > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 7 - LD_PRELOAD: ust app with abi0 and abi1 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 7 - LD_PRELOAD: ust app
with abi0 and abi1 preload fails
./regression/abi0-conflict/test_abi0_conflict: line 74: 592684 Aborted
(core dumped) LD_PRELOAD="${LIBUST1}:${LIBFAKEUST0}"
"${CURDIR}/app_ust" > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 8 - LD_PRELOAD: ust app with abi1 and abi0 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 8 - LD_PRELOAD: ust app
with abi1 and abi0 preload fails
# dlopen
# regression/abi0-conflict/test_abi0_conflict: dlopen
ok 9 - dlopen: no-ust app works
PASS: regression/abi0-conflict/test_abi0_conflict 9 - dlopen: no-ust app works
ok 10 - dlopen: no-ust app with abi1 and abi1 succeeds
PASS: regression/abi0-conflict/test_abi0_conflict 10 - dlopen: no-ust app
with abi1 and abi1 succeeds
./regression/abi0-conflict/test_abi0_conflict: line 92: 592689 Aborted
(core dumped) LD_LIBRARY_PATH="$LIBFAKEUST0_PATH:$LIBUST1_PATH"
"${CURDIR}/app_noust_dlopen" abi0_abi1 > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 11 - dlopen: no-ust app with abi0 and abi1 fails
PASS: regression/abi0-conflict/test_abi0_conflict 11 - dlopen: no-ust app
with abi0 and abi1 fails
not ok 12 - dlopen: no-ust app with abi1 and abi0 fails
FAIL: regression/abi0-conflict/test_abi0_conflict 12 - dlopen: no-ust app
with abi1 and abi0 fails
# Failed test 'dlopen: no-ust app with abi1 and abi0 fails'
# regression/abi0-conflict/test_abi0_conflict: Failed test 'dlopen: no-ust
app with abi1 and abi0 fails'
# in /home/ubuntu/git/packages/ust/lttng-ust/tests/utils/tap.sh:isnt() at
line 300.
# regression/abi0-conflict/test_abi0_conflict: in
/home/ubuntu/git/packages/ust/lttng-ust/tests/utils/tap.sh:isnt() at line 300.
# got: '0'
# regression/abi0-conflict/test_abi0_conflict: got: '0'
# expected: '0'
# regression/abi0-conflict/test_abi0_conflict: expected: '0'
ok 13 - dlopen:
[Touch-packages] [Bug 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
I struggled with this issue for a while until I discovered thar the issue is with the color profile as described in this question https://askubuntu.com/questions/1404516/screen-turns-yellow-even-using- the-live-option-ubuntu-22-04. The way to solve it for me was to add a new color profile in Setting/Color tab -> Add profile for a display. "Standard Space - sRGB" works just right for my Dell XPS 9560 laptop. The issue must be with how the default color profiles are generated for a screen. I have an external monitor and there were no issue with colors there. -- 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/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+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 1421760] Re: /usr/bin/env hangs when a variable is set
workaround: add -S #! /usr/bin/env -S A=B python import os; print(os.environ["A"]) why? shebangs have the limitation (or feature) that you can pass only one argument so #! /usr/bin/env A=B python is parsed as argv[0] = "/usr/bin/env" argv[1] = "A=B python" you can see this with #! /usr/bin/printf A=B '(%s) ' 1 2 3 4 which prints A=B '(./test.sh) ' 1 2 3 4 and #! /usr/bin/env -S printf '(%s) ' 1 2 3 4 prints (1) (2) (3) (4) (./test.sh) now the question is, why does `argv[1] = "A=B python"` lead to infinite recursion? expected result: /usr/bin/env: ‘A=B python’: No such file or directory /usr/bin/env: use -[v]S to pass options in shebang lines just like #! /usr/bin/env hello world throws /usr/bin/env: ‘hello world’: No such file or directory /usr/bin/env: use -[v]S to pass options in shebang lines -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1421760 Title: /usr/bin/env hangs when a variable is set Status in coreutils package in Ubuntu: New Bug description: /usr/bin/env hangs when a variable is set. To reproduce this, create a file with the following contents: #!/usr/bin/env A=B python ; !# (display "wtf") (newline) lets say the file was "wtf.sh". Then chmod ugo+x wtf.sh and then execute it: ./wtf.sh This will hang and spin and burn cpu time. Removing the A=B will cause the script to run just fine (and spew errors, because the conents is not valid python, but that's OK. Instead of python, you could say guile. Its valuid guile. Or you could say bash. whatever, it does not matter) According to gdb, it is stuck in an infinite loop in the dynamic linker-loader, where /usr/bin/env is calling itself over and over. I can't quite tell if this is a bug in env, or in ld.so or in thelinux kernel. FWIW #!/usr/bin/env python 42 also gives unexpeted results: it searches for the interpreter "python 42" instead of searching for "python" and passing it the argument "42". Also the following does not work: #!/usr/bin/env -i python -- it spews an error about the -i flag. This is on both trusty and precise Attaching gdb to the hung pid gives the following: gdb -p 27957 (gdb) bt #0 0x7fa5286c92d0 in _start () from /lib64/ld-linux-x86-64.so.2 #1 0x0003 in ?? () #2 0x7fff36b5ac89 in ?? () #3 0x7fff36b5ac96 in ?? () #4 0x7fff36b5aca0 in ?? () #5 0x in ?? () (gdb) c Continuing. process 27957 is executing new program: /usr/bin/env process 27957 is executing new program: /usr/bin/env process 27957 is executing new program: /usr/bin/env ... ctrl-C ^C__GI__dl_debug_state () at dl-debug.c:74 74dl-debug.c: No such file or directory. Quit (gdb) bt #0 __GI__dl_debug_state () at dl-debug.c:74 #1 0x7f7292b3396a in dl_main (phdr=, phdr@entry=0x400040, phnum=, phnum@entry=9, user_entry=user_entry@entry=0x7fff11adf818, auxv=) at rtld.c:2305 #2 0x7f7292b47565 in _dl_sysdep_start ( start_argptr=start_argptr@entry=0x7fff11adf900, dl_main=dl_main@entry=0x7f7292b31910 ) at ../elf/dl-sysdep.c:249 #3 0x7f7292b34cf8 in _dl_start_final (arg=0x7fff11adf900) at rtld.c:332 #4 _dl_start (arg=0x7fff11adf900) at rtld.c:558 #5 0x7f7292b312d8 in _start () from /lib64/ld-linux-x86-64.so.2 #6 0x0003 in ?? () #7 0x7fff11ae0c89 in ?? () #8 0x7fff11ae0c96 in ?? () #9 0x7fff11ae0ca0 in ?? () #10 0x in ?? () (gdb) c Continuing. process 27957 is executing new program: /usr/bin/env process 27957 is executing new program: /usr/bin/env process 27957 is executing new program: /usr/bin/env process 27957 is executing new program: /usr/bin/env process 27957 is executing new program: /usr/bin/env ^C__GI__dl_debug_state () at dl-debug.c:74 74dl-debug.c: No such file or directory. Quit (gdb) Quit (gdb) Quit (gdb) bt #0 __GI__dl_debug_state () at dl-debug.c:74 #1 0x7f990150396a in dl_main (phdr=, phdr@entry=0x400040, phnum=, phnum@entry=9, user_entry=user_entry@entry=0x7fff61a966a8, auxv=) at rtld.c:2305 #2 0x7f9901517565 in _dl_sysdep_start ( start_argptr=start_argptr@entry=0x7fff61a96790, dl_main=dl_main@entry=0x7f9901501910 ) at ../elf/dl-sysdep.c:249 #3 0x7f9901504cf8 in _dl_start_final (arg=0x7fff61a96790) at rtld.c:332 #4 _dl_start (arg=0x7fff61a96790) at rtld.c:558 #5 0x7f99015012d8 in _start () from /lib64/ld-linux-x86-64.so.2 #6 0x0003 in ?? () #7 0x7fff61a97c89 in ?? () #8 0x7fff61a97c96 in ?? () #9 0x7fff61a97ca0 in ?? () #10 0x in ?? () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1421760/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1965636] Re: libfuse2 no longer included in jammy, required for AppImages
fuse has been demoted from Ubuntu main in favor of fuse3; it would not be appropriate to re-promote it to main and expand the security surface of a default Ubuntu install (fuse is a very security-relevant facility), and Ubuntu images build only from main. So this is a wontfix for the Ubuntu desktop, libfuse2 is not going to be brought back into the default install and users who want to use libfuse2-dependent AppImages will need to install this library themselves beforehand. Our community flavors are free to make their own decisions about whether to bundle libfuse2 by default, as several of them did before the release. ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: ubuntu-meta (Ubuntu Jammy) Status: Confirmed => Won't Fix -- 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/1965636 Title: libfuse2 no longer included in jammy, required for AppImages Status in kubuntu-meta package in Ubuntu: Fix Released Status in lubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-budgie-meta package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in ubuntukylin-meta package in Ubuntu: Confirmed Status in ubuntustudio-meta package in Ubuntu: Fix Released Status in xubuntu-meta package in Ubuntu: Fix Released Status in kubuntu-meta source package in Jammy: Fix Released Status in lubuntu-meta source package in Jammy: Confirmed Status in ubuntu-budgie-meta source package in Jammy: Fix Released Status in ubuntu-meta source package in Jammy: Won't Fix Status in ubuntukylin-meta source package in Jammy: Confirmed Status in ubuntustudio-meta source package in Jammy: Fix Released Status in xubuntu-meta source package in Jammy: Fix Released Bug description: Attempting to run an AppImage in Xubuntu 22.04 displays the following error: $ ./cryptomator-1.6.5-x86_64.AppImage dlopen(): error loading libfuse.so.2 AppImages require FUSE to run. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information --- Simply installing libfuse2 resolves this issue. Some flavors seem to still include it. I noticed that today's Ubuntu MATE daily still does. Ubuntu and Xubuntu do not. Ubuntu: https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-arm64.manifest Xubuntu: https://cdimage.ubuntu.com/xubuntu/daily-live/current/jammy-desktop-amd64.manifest Ubuntu MATE: https://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/jammy-desktop-amd64.manifest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1965636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1963834] Re: openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
FYI, to restart wpa-supplicant after these edits:
systemctl restart wpa_supplicant
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1963834
Title:
openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
Status in openssl package in Ubuntu:
Won't Fix
Bug description:
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
openssl:
Installé : 3.0.1-0ubuntu1
Candidat : 3.0.1-0ubuntu1
Table de version :
*** 3.0.1-0ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
Using Ubuntu 22.04, I now get the following error message when
attempting to connect to our office VPN using "gp-saml-gui
(https://github.com/dlenski/gp-saml-gui)" :
#
dominique@Doombuntu:~$ .local/bin/gp-saml-gui server_url
Looking for SAML auth tags in response to
https://server_url/global-protect/prelogin.esp...
usage: gp-saml-gui [-h] [--no-verify] [-C COOKIES | -K] [-g | -p] [-c CERT]
[--key KEY] [-v | -q] [-x | -P | -S] [-u] [--clientos {Windows,Linux,Mac}] [-f
EXTRA] server [openconnect_extra ...]
gp-saml-gui: error: SSL error: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
unsafe legacy renegotiation disabled (_ssl.c:997)
#
#
#
gp-saml-gui uses python module requests.
Using python ide, I can get the same results :
#
>>> r = requests.get('https://server_url')
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699,
in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382,
in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012,
in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 411, in
connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in
ssl_wrap_socket
ssl_sock = _ssl_wrap_socket_impl(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in
_ssl_wrap_socket_impl
return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/lib/python3.10/ssl.py", line 512, in wrap_socket
return self.sslsocket_class._create(
File "/usr/lib/python3.10/ssl.py", line 1070, in _create
self.do_handshake()
File "/usr/lib/python3.10/ssl.py", line 1341, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy
renegotiation disabled (_ssl.c:997)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in
send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755,
in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in
increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='server_url',
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1,
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation
disabled (_ssl.c:997)')))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/requests/api.py", line 76, in get
return request('get', url, params=params, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in
send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, in
send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='server_url',
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1,
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation
disabled (_ssl.c:997)')))
#
#
#
I believe in OpenSSL 3.0 that SSL_OP_LEGACY_SERVER_CONNECT is now
disabled by default, as opposed to the version used in earlier Ubuntu
versions (tested to work fine with 20.04 and 21.10).
I can't tell what should be done here. Is there something I can do to
allow enable "SSL_OP_LEGACY_SERVER_CONNECT" for this connection ?
[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
** Bug watch added: Debian Bug tracker #1010603 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010603 ** Also affects: wpa (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010603 Importance: Unknown Status: Unknown ** Changed in: wpa (Debian) Importance: Unknown => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Status in wpa package in Debian: Unknown Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
** Patch added: "openssl.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+attachment/5586942/+files/openssl.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: In Progress Status in openssl source package in Jammy: In Progress Status in openssl source package in Kinetic: In Progress Bug description: [Impact] Due to the case comparison differences in the Turkish locale, some routines in OpenSSL fail to recognize some algorithm names as valid, unexpectedly breaking crypto. [Test Plan] This bug is really easy to trigger: sudo locale-gen tr_TR.UTF-8 LANG=C curl https://ubuntu.com/ > /dev/null # This work LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This fails The error is curl: (35) error:0372:digital envelope routines::decode error [Where problems could occur] This patch set is relatively massive, and can cause regressions, as illustrated by the patch #5 which fixes one such regression. Those regressions would likely show up as either libssl crashes, in case of uninitialized objects, or as algorithm selection failures if somehow the case comparison is buggy. [Other Info] The fix has already been released upstream as part of their 3.0.3 release. [Original report] I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUS DESCRIPTION cc-eal yes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+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 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
Here's the debdiff for kinetic, which is the whole 3.0.3 upstream release. You'll find a build for it in my PPA: https://launchpad.net/~schopin/+archive/ubuntu/test- ppa/+sourcepub/13495883/+listing-archive-extra (just pop the extra changelog entry) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: In Progress Status in openssl source package in Jammy: In Progress Status in openssl source package in Kinetic: In Progress Bug description: [Impact] Due to the case comparison differences in the Turkish locale, some routines in OpenSSL fail to recognize some algorithm names as valid, unexpectedly breaking crypto. [Test Plan] This bug is really easy to trigger: sudo locale-gen tr_TR.UTF-8 LANG=C curl https://ubuntu.com/ > /dev/null # This work LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This fails The error is curl: (35) error:0372:digital envelope routines::decode error [Where problems could occur] This patch set is relatively massive, and can cause regressions, as illustrated by the patch #5 which fixes one such regression. Those regressions would likely show up as either libssl crashes, in case of uninitialized objects, or as algorithm selection failures if somehow the case comparison is buggy. [Other Info] The fix has already been released upstream as part of their 3.0.3 release. [Original report] I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUS DESCRIPTION cc-eal yes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
** Description changed: + * Impact + + Connecting to some PEAP wifi doesn't work anymore since the openssl3 + transition + + Details on the issue can be found on + http://lists.infradead.org/pipermail/hostap/2022-May/040511.html + + * Test case + + Try using a PEAP wifi not implementing RFC5746, it should be able to + connect + + * Regression potential + + The change allows to connect to less secure WiFis the same way that wpa + allowed before openssl3, lower security enforcement isn't ideal but + still better than non working hardware. + + + WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: - - mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 + + mtime.conffile..etc.update-manager.release-upgrades: + 2022-02-27T21:07:16.553410 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Committed Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1971112] Re: File picker gets bigger more and more each time!
I see this in the xorg session in the flatpak firefox save downloads dialog, for instance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1971112 Title: File picker gets bigger more and more each time! Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Hello. I've just switched to Ubuntu and ever since day 1 I had this issue that whenever I tried to choose a file the file picker window was way too big and it was getting bigger and bigger each time. I have posted a video on Reddit recording this unusual/unexpected behavior. Here is the reddit post link (with video): https://www.reddit.com/r/Ubuntu/comments/ug97qx/annoying_bug_file_picker_gets_bigger_more_and/ I've also attached the video to this post, in case you don't want to click the link above. Here is my neofetch output: OS: Ubuntu 22.04 LTS x86_64 Kernel: 5.15.0-27-generic Uptime: 13 hours, 13 mins Shell: bash 5.1.16 Resolution: 1440x900, 1920x1080 DE: GNOME 42.0 WM: Mutter WM Theme: Adwaita Theme: Yaru-viridian-dark [GTK2/3] Icons: Yaru-viridian [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-8700K (12) @ 4.700GHz GPU: NVIDIA GeForce GTX 1060 3GB Memory: 5869MiB / 15936MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1971112/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
** Changed in: wpa (Ubuntu) Status: Triaged => Fix Committed ** Changed in: wpa (Ubuntu Jammy) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Committed Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
With the revert, the network-manager ADT tests work again. https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/amd64/n/network-manager/20220505_053118_fb2db@/log.gz ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in network-manager source package in Jammy: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1186376] Re: should support setting of whether or not to include phased updates
** Changed in: software-properties (Ubuntu) Importance: Medium => Wishlist -- 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/1186376 Title: should support setting of whether or not to include phased updates Status in software-properties package in Ubuntu: Triaged Bug description: update-manager is aware of an apt configuration option to either "Always-Include-Phased-Updates" or "Never-Include-Phased-Updates", however there no user interface for creating or changing this setting. I think it makes sense for software-properties (probably in the "Updates" tab) to have the ability to set the option as to whether or not phased updates are always or never included. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1186376/+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 1896772] Re: systemd-resolved configures no Current Scopes on start
Thank you very much, Jamie, for your detailed analysis in #15! I've applied the same fix to isc-dhcp https://launchpad.net/ubuntu/+source/isc-dhcp/4.4.1-2.3ubuntu3 We can consider SRUing this to Jammy and Impish, which are affect too. But it doesn't feel too critical, as systemd-resolved usually wins the race vs NetworkManager/dhclient, as you stated: "but with NetworkManager as the netplan renderer, the dhclient script is called later and the dir is created correctly." I'm marking the systemd component as "Invalid", as the fix is needed in other packages. ** No longer affects: systemd (Ubuntu Jammy) ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: isc-dhcp (Ubuntu) Status: Triaged => Fix Committed ** Also affects: ifupdown (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Impish) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu Impish) ** Changed in: isc-dhcp (Ubuntu Impish) Status: New => Triaged ** Changed in: isc-dhcp (Ubuntu Jammy) Importance: High => Low ** Changed in: isc-dhcp (Ubuntu Impish) Importance: Undecided => Low ** Changed in: ifupdown (Ubuntu Impish) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start Status in ifupdown package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Invalid Status in ifupdown source package in Impish: Triaged Status in isc-dhcp source package in Impish: Triaged Status in ifupdown source package in Jammy: Fix Released Status in isc-dhcp source package in Jammy: Triaged Bug description: Running groovy on the desktop, with the systemd packages that migrated today(/overnight EDT). # Steps to reproduce: 1) `systemctl restart systemd-resolved.service` (This is a minimal reproducer, but I first saw this after an apt upgrade of systemd.) # Expected behaviour: DNS continues to work, status looks like this: Link 2 (enp5s0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.1.1 DNS Servers: 192.168.1.1 DNS Domain: ~. lan # Actual behaviour: DNS is unconfigured: Link 2 (enp5s0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no # Workaround Disconnecting and reconnecting my network connection restored DNS functionality. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: i3 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Sep 23 09:05:42 2020 InstallationDate: Installed on 2019-05-07 (504 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 RebootRequiredPkgs: gnome-shell SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to groovy on 2020-06-22 (92 days ago) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF
[Touch-packages] [Bug 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
Attached is the patch for the Jammy SRU ** Patch added: "openssl_jammy.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+attachment/5586889/+files/openssl_jammy.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: In Progress Status in openssl source package in Jammy: In Progress Status in openssl source package in Kinetic: In Progress Bug description: [Impact] Due to the case comparison differences in the Turkish locale, some routines in OpenSSL fail to recognize some algorithm names as valid, unexpectedly breaking crypto. [Test Plan] This bug is really easy to trigger: sudo locale-gen tr_TR.UTF-8 LANG=C curl https://ubuntu.com/ > /dev/null # This work LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This fails The error is curl: (35) error:0372:digital envelope routines::decode error [Where problems could occur] This patch set is relatively massive, and can cause regressions, as illustrated by the patch #5 which fixes one such regression. Those regressions would likely show up as either libssl crashes, in case of uninitialized objects, or as algorithm selection failures if somehow the case comparison is buggy. [Other Info] The fix has already been released upstream as part of their 3.0.3 release. [Original report] I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUS DESCRIPTION cc-eal yes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+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 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
** Changed in: openssl (Ubuntu Jammy) Status: New => Confirmed ** Changed in: openssl (Ubuntu Jammy) Status: Confirmed => In Progress ** Description changed: - I noticed this when I checked "ua status". It alerted me that I should - check my openssl configuration. + [Impact] + + Due to the case comparison differences in the Turkish locale, some routines in + OpenSSL fail to recognize some algorithm names as valid, unexpectedly breaking + crypto. + + [Test Plan] + + This bug is really easy to trigger: + + sudo locale-gen tr_TR.UTF-8 + LANG=C curl https://ubuntu.com/ > /dev/null # This work + LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This fails + + The error is curl: (35) error:0372:digital envelope routines::decode + error + + [Where problems could occur] + + This patch set is relatively massive, and can cause regressions, as illustrated + by the patch #5 which fixes one such regression. Those regressions would likely + show up as either libssl crashes, in case of uninitialized objects, or as + algorithm selection failures if somehow the case comparison is buggy. + + [Other Info] + + The fix has already been released upstream as part of their 3.0.3 release. + + [Original report] + I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c - ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 - ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 - ca_ES ca_FR ce_RU crh_UA cv_RU - ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB - casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 + ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 + ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 + ca_ES ca_FR ce_RU crh_UA cv_RU + ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB + casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status - SERVICE ENTITLED STATUSDESCRIPTION - cc-ealyes n/a Common Criteria EAL2 Provisioning Packages - cis yes n/a Security compliance and audit tools - esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) - fips yes n/a NIST-certified core packages - fips-updates yes n/a NIST-certified core packages with priority security updates - livepatch yes n/a Canonical Livepatch service + SERVICE ENTITLED STATUS DESCRIPTION + cc-eal yes n/a Common Criteria EAL2 Provisioning Packages + cis yes n/a Security compliance and audit tools + esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) + fips yes n/a NIST-certified core packages + fips-updates yes n/a NIST-certified core packages with priority security updates + livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title:
[Touch-packages] [Bug 1889068] Re: Improve resolved integration
We need to make sure that the resolved hooks use the correct "systemd- resolve" user to setup the statedir permissions inside the hook, see LP: #1896772 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1889068 Title: Improve resolved integration Status in ifupdown package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Fix Released Status in resolvconf package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Insure that ifupdown & dhcp DNS information is always added to resolved. Move the resolved hooks from systemd package to isc-dhcp-client and ifupdown themselves. Figure out how to integrate "eth0" resolver => Manager resolver. Blog / document how to control this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1889068/+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 1971264] Re: Merge bridge-utils from Debian unstable for kinetic
** Changed in: bridge-utils (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1971264 Title: Merge bridge-utils from Debian unstable for kinetic Status in bridge-utils package in Ubuntu: Incomplete Bug description: Upstream: tbd Debian: 1.7-1 Ubuntu: 1.7-1ubuntu3 Debian typically updates bridge-utils every 4 months on average, but it was last updated 21.02 and looks overdue. Check back in on this monthly. Based on Upstream's release history for bridge-utils we should have expected a new upstream update around 2022.03. Presumably it could come any time now. ### New Debian Changes ### bridge-utils (1.7-1) unstable; urgency=medium * New upstream version. Only messages related changes and compilation fixes. * Remove preserve_gcc_flags patch (in upstream now). * Bump standards, no change needed. * Clarify portprio and fix example. * Update upstream url. * Fix NEWS versioning of last entry :-? -- Santiago Garcia Mantinan Wed, 24 Feb 2021 12:34:03 +0100 bridge-utils (1.6-6) unstable; urgency=medium * Fix IPv6 address getting assigned on hotplug devices. Closes: #980752. * Fix waiting so that DAD works again. Closes: #982943. * Move mac setting before brctl addif to ensure mac setting. Closes: #980856. * Update documentation and add examples. Closes: #765098. * Update manpages. Closes: #981253. * Add a note on MTU settings. Closes: #292088. * Hook also on down to recreate the bridge so that multiple stanzas work Ok on ifdown. Closes: #319832. -- Santiago Garcia Mantinan Tue, 16 Feb 2021 13:29:04 +0100 bridge-utils (1.6-5) unstable; urgency=low * Overload bridge_hw to allow do specify an interface as well as the MAC address. Closes: #966244. * Change man page for bridge-utils-interfaces and news fileto document this overloading. -- Santiago Garcia Mantinan Fri, 22 Jan 2021 11:08:47 +0100 bridge-utils (1.6-4) unstable; urgency=low * Add en* to the device regex so that all catches them. Closes: #966319. * Document MAC address changes on news. Closes: #980505. -- Santiago Garcia Mantinan Thu, 21 Jan 2021 10:51:31 +0100 bridge-utils (1.6-3) unstable; urgency=medium * Support VLAN aware setups where we need vlan filtering. Thanks Benedikt Spranger for the patch. Closes: #950879. * Clarify on manual page that stp will get IPv6 lost. Closes: #736336. * Add a 1 second sleep if hw address needs to be changed. Closes: #945466. -- Santiago Garcia Mantinan Thu, 30 Apr 2020 10:06:38 +0200 bridge-utils (1.6-2) unstable; urgency=medium * Bump Standards-Version. * Preserve gcc flags set when building the lib. -- Santiago Garcia Mantinan Mon, 28 Jan 2019 00:25:14 +0100 bridge-utils (1.6-1) unstable; urgency=low * New upstream version. * Change default back to not hotplug. Closes: #892277. * Allow mtu to be set on the bridge by propagating it to the bridged interfaces. Closes: #661711. * Remove kernel headers from the package. -- Santiago Garcia Mantinan Tue, 15 Jan 2019 13:18:33 +0100 bridge-utils (1.5-16) unstable; urgency=medium * Don't set dev globally at bridge-utils.sh. Closes: #873086. -- Santiago Garcia Mantinan Sun, 08 Apr 2018 23:06:30 +0200 bridge-utils (1.5-15) unstable; urgency=medium * Fix substrings on interfaces. Closes: #873087. * Make it lintian clean sticking to 1.0 source format for now. No time to properly comment all the patches right now. -- Santiago Garcia Mantinan Fri, 02 Mar 2018 22:08:20 +0100 bridge-utils (1.5-14) unstable; urgency=low * Fix a problem with some vlan interfaces not being created. -- Santiago Garcia Mantinan Mon, 26 Jun 2017 17:48:37 +0200 bridge-utils (1.5-13) unstable; urgency=low * Fix a hardcoded interface name on bridge-utils.sh. Closes: #854841. -- Santiago Garcia Mantinan Sat, 11 Feb 2017 00:16:45 +0100 bridge-utils (1.5-12) unstable; urgency=medium * Add vlan support so that old setups using vlans as ports don't break. -- Santiago Garcia Mantinan Sun, 22 Jan 2017 00:23:50 +0100 ### Old Ubuntu Delta ### bridge-utils (1.7-1ubuntu3) jammy; urgency=medium * No-change rebuild for ppc64el baseline bump. -- Łukasz 'sil2100' Zemczak Wed, 23 Mar 2022 10:44:35 +0100 bridge-utils (1.7-1ubuntu2) impish; urgency=medium * No-change rebuild to build packages with zstd compression. -- Matthias Klose Thu, 07 Oct 2021 12:09:41 +0200 bridge-utils (1.7-1ubuntu1) impish; urgency=low * Merge from Debian unstable. Remaining changes: - Don't call ifup from bridge-network-interface, instead just call
