[Touch-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
** Description changed: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Just for tracking now. [Impact] [Fix] [Test Case] - [Regression Risk] + [Where problems could occur] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in ALSA Libraries: New Status in alsa-lib package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-lib source package in Hirsute: New Bug description: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Just for tracking now. [Impact] [Fix] [Test Case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-lib/+bug/1921452/+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 1920987] Re: IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ]; iso 3
Oh, that's so sweet... when I read this endless memoir about codes of conduct and the importance of democratic institutions, written in English. I think only of the Overton window system, and I only remember that after a very hard war, seeing that the British Empire would fall, Truman introduced the Soviet deterrent system, which is projected to this day, and I see it not as a deterrent system, but as a knife in the back... this is the whole importance of passing through a thousand words and gigabytes of code to justify simple things. While they will fool you with their rules, at the same time they will create lawlessness themselves, for this they write their rules. I remember how the USSR was destroyed, how the Crimea was removed from the USSR, I remember these hordes of Uzbeks with signs on their necks "our Crimea". I see what is happening now around the Crimean peninsula, these claims, attacks and sanctions... in order to change the opinion of the Crimeans. And believe me, I still behave more than correctly when I write all this. After all, if you were left in your infancy just in the woods, you would be the default animal. You wouldn't be able to read or write until you were taught to do so. In another case, if you are placed in an information vacuum and raised in total Russophobia (which includes racism, fascism and nazism), you will already turn into a completely different animal. But the point will be the same. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iso-codes in Ubuntu. https://bugs.launchpad.net/bugs/1920987 Title: IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ]; iso 3166-2 has no RU subdivisions for Crimea Status in iso-codes package in Ubuntu: New Status in tzdata package in Ubuntu: Opinion Bug description: Europe/Simferopol, Crimea is RUSSIA ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: tzdata 2021a-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CurrentDesktop: MATE Date: Tue Mar 23 21:44:56 2021 InstallationDate: Installed on 2021-03-21 (1 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) PackageArchitecture: all SourcePackage: tzdata UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/1920987/+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 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
This is the debdiff for hirsute, thanks. ** Patch added: "alsa-lib_1.2.4-1.1build1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1921452/+attachment/5481031/+files/alsa-lib_1.2.4-1.1build1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in ALSA Libraries: New Status in alsa-lib package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-lib source package in Hirsute: New Bug description: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Just for tracking now. [Impact] [Fix] [Test Case] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-lib/+bug/1921452/+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 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
** Changed in: alsa-lib (Ubuntu Hirsute) Assignee: (unassigned) => Shengyao Xue (xueshengyao) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in ALSA Libraries: New Status in alsa-lib package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-lib source package in Hirsute: New Bug description: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Just for tracking now. [Impact] [Fix] [Test Case] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-lib/+bug/1921452/+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 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
** Also affects: alsa-lib (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: alsa-lib (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: alsa-lib (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in ALSA Libraries: New Status in alsa-lib package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-lib source package in Hirsute: New Bug description: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Just for tracking now. [Impact] [Fix] [Test Case] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-lib/+bug/1921452/+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 1921452] [NEW] [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
Public bug reported: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Just for tracking now. [Impact] [Fix] [Test Case] [Regression Risk] ** Affects: alsa-lib Importance: Undecided Status: New ** Affects: alsa-lib (Ubuntu) Importance: Undecided Assignee: Shengyao Xue (xueshengyao) Status: New ** Affects: alsa-lib (Ubuntu Focal) Importance: Undecided Status: New ** Affects: alsa-lib (Ubuntu Groovy) Importance: Undecided Status: New ** Affects: alsa-lib (Ubuntu Hirsute) Importance: Undecided Assignee: Shengyao Xue (xueshengyao) Status: New ** Also affects: alsa-lib Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in ALSA Libraries: New Status in alsa-lib package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-lib source package in Hirsute: New Bug description: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Just for tracking now. [Impact] [Fix] [Test Case] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-lib/+bug/1921452/+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 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)
** Changed in: mutter (Ubuntu) Status: Fix Committed => In Progress -- 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/1896171 Title: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver) Status in Mutter: Unknown Status in mesa package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Bug description: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver). Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1896171/+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 1693900] Re: apt-get update should return exit code != 0 on error
** Changed in: apt (Debian) Status: Unknown => Fix Released -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt package in Debian: Fix Released Bug description: [Impact] There is no way for scripts to run apt update and be sure that it was entirely successful. We introduce a new flag, --error-on=any that makes apt update also error out on transient errors. [Test plan] We have included a test in the test-suite in test-apt-update-failure-propagation that ensures that warnings become errors. [Where problems could occur] If there's an issue some warnings for transient errors could become errors, or worse I suppose it's possible but unlikely for errors to be reported as warnings... Since the new behavior is behind a flag, regression potential for existing scripts is low if there is no bug. [Original bug report] When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1723585] Re: need help
What is the problem you were reporting? Is it still happening? ** 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/1723585 Title: need help Status in Ubuntu: Incomplete Bug description: Thank you ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Oct 14 16:28:41 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed nvidia-375, 375.66, 4.10.0-37-generic, x86_64: installed nvidia-375, 375.66, 4.4.0-97-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1720] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940MX] [1043:1720] InstallationDate: Installed on 2017-10-11 (2 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: ASUSTeK COMPUTER INC. ZN270IE ProcEnviron: LANGUAGE=en_SG:en PATH=(custom, no user) LANG=en_SG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed root=UUID=1649139e-3af4-4708-9088-0a8173c9727b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0401 dmi.board.asset.tag: Default string dmi.board.name: ZN270IE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd02/24/2017:svnASUSTeKCOMPUTERINC.:pnZN270IE:pvr0401:rvnASUSTeKCOMPUTERINC.:rnZN270IE:rvrRev1.xx:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.name: ZN270IE dmi.product.version: 0401 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 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: Sat Oct 14 15:54:30 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1723585/+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 1724505] Re: a
Please explain what the problem is or was. ** 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/1724505 Title: a Status in Ubuntu: Incomplete Bug description: a ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Oct 18 11:21:30 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-35-generic, x86_64: installed bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed nvidia-375, 375.66, 4.10.0-35-generic, x86_64: installed nvidia-375, 375.66, 4.10.0-37-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:820d] Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:820d] InstallationDate: Installed on 2017-09-28 (19 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c87 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook ProcEnviron: LANGUAGE=it_IT TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed root=UUID=704cd37e-ef78-4fb2-9d03-602b1fe1e1e4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.38 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 820D dmi.board.vendor: HP dmi.board.version: 82.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.38:bd05/24/2017:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820D:rvr82.34:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 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: Wed Oct 18 11:17:13 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1724505/+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 1725385] Re: one
What is the problem you are reporting? Does it still happen? ** 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/1725385 Title: one Status in Ubuntu: Incomplete Bug description: no further information ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic i686 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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: Fri Oct 20 18:21:34 2017 DistUpgraded: 2017-10-13 20:50:46,659 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.4.0-31-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-97-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-98-generic, i686: installed ndiswrapper, 1.60, 4.4.0-97-generic, i686: installed ndiswrapper, 1.60, 4.4.0-98-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470] [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: Dell RV620/M82 [Mobility Radeon HD 3450/3470] [1028:0254] InstallationDate: Installed on 2017-10-13 (7 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) MachineType: Dell Inc. Studio 1535 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=18271d74-75ec-4847-a14e-5541b0a44390 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-10-13 (6 days ago) XorgLogOld: dmi.bios.date: 07/02/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0F700C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd07/02/2008:svnDellInc.:pnStudio1535:pvr:rvnDellInc.:rn0F700C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Studio 1535 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1725385/+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 1735945] Re: Brightness control not working
Are you still experiencing this bug in newer Ubuntu releases? ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (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/1735945 Title: Brightness control not working Status in linux package in Ubuntu: Incomplete Bug description: Brightness control not working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 2 17:53:21 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] InstallationDate: Installed on 2017-11-30 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20211 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed root=UUID=101a39ce-07bc-4b02-87e9-77428c23bae1 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN45WW(V1.18) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad P400 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN45WW(V1.18):bd05/10/2013:svnLENOVO:pn20211:pvrLenovoIdeaPadP400Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadP400Touch: dmi.product.name: 20211 dmi.product.version: Lenovo IdeaPad P400 Touch dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 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: Sat Dec 2 16:42:49 2017 xserver.configfile: default xserver.errors: intel(0): Unrecognised backlight control interface 'ideapad' xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8254 vendor AUO xserver.version: 2:1.19.3-1ubuntu1~16.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1735945/+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 1739510] Re: ill install you signature
Please explain in more detail what kind of problem you are experiencing, and if it is still happening. ** Changed in: xorg (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/1739510 Title: ill install you signature Status in xorg package in Ubuntu: Incomplete Bug description: hope you can help me. i cant affort another computer and spain is acting violence ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 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 Dec 21 01:27:15 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:81ed] InstallationDate: Installed on 2017-12-19 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:651b Microdia Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 276d:1160 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic.efi.signed root=UUID=d6ad60b5-3719-45b3-8b42-1bb91b324af7 ro nopat vesafb.invalid=1 plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81ED dmi.board.vendor: HP dmi.board.version: 62.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/20/2017:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81ED:rvr62.39:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP 250 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 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 Dec 21 00:06:27 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1739510/+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 1740379] Re: vlc et rhymtbox
Sorry for the lateness, but is this bug still occurring? ** Package changed: xorg (Ubuntu) => vlc (Ubuntu) ** Changed in: vlc (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/1740379 Title: vlc et rhymtbox Status in vlc package in Ubuntu: Incomplete Bug description: ces programme refuse de s'ouvrir ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Dec 28 10:30:20 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-103-generic, x86_64: installed bbswitch, 0.8, 4.4.0-104-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF116 [GeForce GTS 450 Rev. 2] [10de:1245] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF116 [GeForce GTS 450 Rev. 2] [10de:0939] InstallationDate: Installed on 2017-10-06 (82 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ECS A880GM-AD3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic root=UUID=b7fa625d-3fd0-4d1d-99d6-d3637b092b50 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.name: A880GM-AD3 dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd06/11/2010:svnECS:pnA880GM-AD3:pvr1.0:rvnECS:rnA880GM-AD3:rvr1.0:cvnECS:ct3:cvr: dmi.product.name: A880GM-AD3 dmi.product.version: 1.0 dmi.sys.vendor: ECS version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Dec 28 10:25:38 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Wired Keyboard 400 KEYBOARD, id 8 inputLogitech USB Receiver MOUSE, id 9 inputLogitech USB Receiver KEYBOARD, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1740379/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Tags removed: verification-needed -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Fix Released Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for
[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error
Fixed in Ubuntu Hirsute. --- apt (2.1.16) unstable; urgency=medium [ Faidon Liambotis ] * Various fixes to http and connect method - basehttp: also consider Access when a Server's URI - connect: convert a C-style string to std::string - connect: use ServiceNameOrPort, not Port, as the cache key [ Julian Andres Klode ] * patterns: Add dependency patterns ?depends, ?conflicts, etc. Note that the -broken- variants are not implemented yet. * Rewrite of the kernel autoremoval code: - Determine autoremovable kernels at run-time (LP: #1615381), this fixes the issue where apt could consider a running kernel autoremovable - Automatically remove unused kernels on apt {full,dist}-upgrade. This helps ensuring that we don't run out of /boot space. - Only keep up to 3 (not 4) kernels. Ubuntu boot partitions were sized for 3 kernels, not 4. * Bump codenames to bullseye/hirsute and adjust -security codename for bullseye (Closes: #969932) * Ignore failures from immediate configuration. This does not change the actual installation ordering - we never passed the return code to the caller and installation went underway anyway if it could be ordered at a later stage, this just removes spurious after-the-fact errors. (Closes: #973305, #188161, #211075, #649588) (LP: #1871268) * Add support for Phased-Update-Percentage, previously used only by update-manager. * Implement update --error-on=any so that scripts can reliably check for transient failures as well. (Closes: #594813) [ Demi M. Obenour ] * test/integration/framework: Be compatible with Bash [ Vangelis Skarmoutsos ] * Greek program translation update -- Julian Andres Klode Fri, 08 Jan 2021 21:49:15 +0100 ** Bug watch removed: Debian Bug tracker #776152 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776152 -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt package in Debian: Unknown Bug description: [Impact] There is no way for scripts to run apt update and be sure that it was entirely successful. We introduce a new flag, --error-on=any that makes apt update also error out on transient errors. [Test plan] We have included a test in the test-suite in test-apt-update-failure-propagation that ensures that warnings become errors. [Where problems could occur] If there's an issue some warnings for transient errors could become errors, or worse I suppose it's possible but unlikely for errors to be reported as warnings... Since the new behavior is behind a flag, regression potential for existing scripts is low if there is no bug. [Original bug report] When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1742695] Re: apt-get update silently fails fetching security updates
*** This bug is a duplicate of bug 1693900 *** https://bugs.launchpad.net/bugs/1693900 ** Also affects: apt (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776152 Importance: Unknown Status: Unknown ** No longer affects: apt (Debian) -- 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/1742695 Title: apt-get update silently fails fetching security updates Status in apt package in Ubuntu: Triaged Bug description: On Ubuntu Xenial, apt-get fails silently when security update server cannot be reached. This state could be detected by scanning the apt- get output afterwards. But manually adding workarounds to each apt-get invocation in production automation is prone to error, thus leaving machines without security updates. Expected behaviour (e.g.): * 0 - all OK * 1 - temporary failure (e.g. network) * 2 - permanent failure Test: * Change your update server IP in /etc/hosts to something unreachable * Run apt-get update (might take a while) * Check exit status $ lsb_release -r -d Description:Ubuntu 16.04.3 LTS Release:16.04 rfiedler@n3ahit1403:~$ ii apt 1.2.24 amd64commandline package manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742695/+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 626144] Re: aptdaemon doesn't respond to network errors correctly
*** This bug is a duplicate of bug 1693900 *** https://bugs.launchpad.net/bugs/1693900 ** This bug is no longer a duplicate of bug 451366 404 from the archive is not handled well ** This bug has been marked a duplicate of bug 1693900 apt-get update should return exit code != 0 on error ** Package changed: debian => apt (Ubuntu) ** Changed in: apt (Ubuntu) Importance: Unknown => Undecided ** Changed in: apt (Ubuntu) Remote watch: Debian Bug tracker #594813 => None ** Bug watch removed: Debian Bug tracker #594813 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594813 -- 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/626144 Title: aptdaemon doesn't respond to network errors correctly Status in Aptdaemon: New Status in apt package in Ubuntu: New Bug description: (A script is attached to demonstrate the behavior) 1) Go to NetworkManager and disconnect from your network 2) Run the script attached What happens - The update starts, continues for a few seconds and then finishes with the state "exit-sucess" What should happen - The update starts, fails and raises an error because it can't connect to the internet. 1) Make sure you are connected to the Internet 2) Run the script attached 3) After a few seconds, go to NetworkManager and disconnect yourself from the internet What happens - The update starts and just hangs What should happen - The update starts and then fails (raising an error) because it can no longer connect to the internet. Such behavior is essential for applications like software-updater and the way it works at the moment seems counter-intuitive. To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/626144/+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 1693900] Re: apt-get update should return exit code != 0 on error
** Bug watch removed: github.com/moby/moby/issues #23910 https://github.com/moby/moby/issues/23910 ** Bug watch removed: github.com/moby/libnetwork/issues #1654 https://github.com/moby/libnetwork/issues/1654 ** Changed in: apt (Ubuntu Xenial) Importance: Undecided => Wishlist ** Changed in: apt (Ubuntu Bionic) Importance: Undecided => Wishlist ** Changed in: apt (Ubuntu Focal) Importance: Undecided => Wishlist ** Changed in: apt (Ubuntu Groovy) Importance: Undecided => Wishlist -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt package in Debian: Unknown Bug description: [Impact] There is no way for scripts to run apt update and be sure that it was entirely successful. We introduce a new flag, --error-on=any that makes apt update also error out on transient errors. [Test plan] We have included a test in the test-suite in test-apt-update-failure-propagation that ensures that warnings become errors. [Where problems could occur] If there's an issue some warnings for transient errors could become errors, or worse I suppose it's possible but unlikely for errors to be reported as warnings... Since the new behavior is behind a flag, regression potential for existing scripts is low if there is no bug. [Original bug report] When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 451366] Re: 404 from the archive is not handled well
*** This bug is a duplicate of bug 1693900 *** https://bugs.launchpad.net/bugs/1693900 ** Package changed: aptdaemon (Debian) => apt (Ubuntu) ** Changed in: apt (Ubuntu) Importance: Unknown => Undecided ** Changed in: apt (Ubuntu) Status: Fix Released => New ** Changed in: apt (Ubuntu) Remote watch: Debian Bug tracker #594813 => None ** Bug watch removed: Debian Bug tracker #594813 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594813 ** This bug has been marked a duplicate of bug 1693900 apt-get update should return exit code != 0 on error -- 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/451366 Title: 404 from the archive is not handled well Status in Aptdaemon: In Progress Status in apt package in Ubuntu: New Status in aptdaemon package in Ubuntu: Triaged Status in software-center package in Ubuntu: Triaged Bug description: Binary package hint: software-center When trying to install Pingus from the Ubuntu Software Center It downloads to 50% and then gives the following error message: Failed to download package files Check your internet connection. Details Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/b/boost1.38/libboost-signals1.38.0_1.38.0-6ubuntu5_i386.deb 404 Not Found [IP: 91.189.88.31 80] My internet is working and I have downloaded and installed other software succesfully from the software center. ProblemType: Bug Architecture: i386 Date: Wed Oct 14 08:20:35 2009 DistroRelease: Ubuntu 9.10 Package: software-center 0.4.6 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.39-generic SourcePackage: software-center Tags: ubuntu-unr Uname: Linux 2.6.31-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/451366/+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 1693900] Re: apt-get update should return exit code != 0 on error
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu Xenial) Status: New => Confirmed -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt package in Debian: Unknown Bug description: [Impact] There is no way for scripts to run apt update and be sure that it was entirely successful. We introduce a new flag, --error-on=any that makes apt update also error out on transient errors. [Test plan] We have included a test in the test-suite in test-apt-update-failure-propagation that ensures that warnings become errors. [Where problems could occur] If there's an issue some warnings for transient errors could become errors, or worse I suppose it's possible but unlikely for errors to be reported as warnings... Since the new behavior is behind a flag, regression potential for existing scripts is low if there is no bug. [Original bug report] When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1693900] Re: apt-get update should return exit code != 0 on error
** Bug watch added: Debian Bug tracker #594813 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594813 ** Also affects: apt (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594813 Importance: Unknown Status: Unknown ** Description changed: [Impact] There is no way for scripts to run apt update and be sure that it was entirely successful. - We introduce a new flag, --error-mode=any that makes apt update also - error out on transient errors. + We introduce a new flag, --error-on=any that makes apt update also error + out on transient errors. [Test plan] We have included a test in the test-suite in test-apt-update-failure-propagation that ensures that warnings become errors. [Where problems could occur] If there's an issue some warnings for transient errors could become errors, or worse I suppose it's possible but unlikely for errors to be reported as warnings... Since the new behavior is behind a flag, regression potential for existing scripts is low if there is no bug. [Original bug report] When running 'apt-get update' (e.g. on a container install post-install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt package in Debian: Unknown Bug description: [Impact] There is no way for scripts to run apt update and be sure that it was entirely successful. We introduce a new flag, --error-on=any that makes apt update also error out on transient errors. [Test plan] We have included a test in the test-suite in test-apt-update-failure-propagation that ensures that warnings become errors. [Where problems could occur] If there's an issue some warnings for transient errors could become errors, or worse I suppose it's possible but unlikely for errors to be reported as warnings... Since the new behavior is behind a flag, regression potential for existing scripts is low if there is no bug. [Original bug report] When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 626144] [NEW] aptdaemon doesn't respond to network errors correctly
You have been subscribed to a public bug: (A script is attached to demonstrate the behavior) 1) Go to NetworkManager and disconnect from your network 2) Run the script attached What happens - The update starts, continues for a few seconds and then finishes with the state "exit-sucess" What should happen - The update starts, fails and raises an error because it can't connect to the internet. 1) Make sure you are connected to the Internet 2) Run the script attached 3) After a few seconds, go to NetworkManager and disconnect yourself from the internet What happens - The update starts and just hangs What should happen - The update starts and then fails (raising an error) because it can no longer connect to the internet. Such behavior is essential for applications like software-updater and the way it works at the moment seems counter-intuitive. ** Affects: aptdaemon Importance: Undecided Status: New ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- aptdaemon doesn't respond to network errors correctly https://bugs.launchpad.net/bugs/626144 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt 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 451366] [NEW] 404 from the archive is not handled well
You have been subscribed to a public bug: Binary package hint: software-center When trying to install Pingus from the Ubuntu Software Center It downloads to 50% and then gives the following error message: Failed to download package files Check your internet connection. Details Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/b/boost1.38/libboost-signals1.38.0_1.38.0-6ubuntu5_i386.deb 404 Not Found [IP: 91.189.88.31 80] My internet is working and I have downloaded and installed other software succesfully from the software center. ProblemType: Bug Architecture: i386 Date: Wed Oct 14 08:20:35 2009 DistroRelease: Ubuntu 9.10 Package: software-center 0.4.6 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.39-generic SourcePackage: software-center Tags: ubuntu-unr Uname: Linux 2.6.31-12-generic i686 ** Affects: aptdaemon Importance: Medium Status: In Progress ** Affects: aptdaemon (Ubuntu) Importance: Medium Status: Triaged ** Affects: software-center (Ubuntu) Importance: Medium Status: Triaged ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug client-server i386 ubuntu-unr -- 404 from the archive is not handled well https://bugs.launchpad.net/bugs/451366 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt 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 1921385] Re: Xorg freeze
Thanks for the bug report. I can see some recurring crashes in your 'i915' kernel graphics driver so will move this bug to the kernel. Also, Ubuntu 16.04 is 5 years old and not supported as well as newer releases. We encourage you to install Ubuntu 20.04.2.0 instead: https://ubuntu.com/download/desktop ** Summary changed: - Xorg freeze + Crashes in i915 on Intel GM965 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1921385 Title: Crashes in i915 on Intel GM965 Status in linux package in Ubuntu: New Bug description: The boot program is very slow. An error dialog pops up simply stating there is a problem with the system. If I open the details a long long list of data is shown, way above my technical knowledge. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-140.144~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-140-generic i686 NonfreeKernelModules: wl .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 CurrentDesktop: Unity Date: Thu Mar 25 08:22:18 2021 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-139-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-140-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Inspiron 1525 [1028:022f] Subsystem: Dell Inspiron 1525 [1028:022f] InstallationDate: Installed on 2021-03-17 (7 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: Dell Inc. Inspiron 1525 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-140-generic root=UUID=b85df775-5de2-47b0-843b-d2f8b1f71d5e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921385/+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 1911036] Re: GDK/GTK app crash in XFCE when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_f
Now in hirsute-proposed: gtk+3.0 (3.24.25-1ubuntu3) hirsute; urgency=medium * d/p/x11-dnd-Ignore-XErrors-from-the-COW.patch: - Ignore XErrors from the COW (LP: #1911036) * d/p/cssshadowvalue-Apply-device-scale-to-the-offset-when.patch: - Apply device scale to the offset when blurring text (LP: #1919404) -- Daniel van Vugt Thu, 25 Mar 2021 16:17:15 +0100 -- 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/1911036 Title: GDK/GTK app crash in XFCE when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_find_window) Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk4 package in Ubuntu: Fix Committed Bug description: For many months now, whenever any mouse drag is attempted in an application using the gtk tool kit, the application immediately crashes. I've noticed this at least in Firefox and thunar. It also occurs when displaying these applications from a Virtualbox machine or from another server running something other than Ubuntu. The VM was running CentOS 8 and the remote server was running Mageia. Both Firefox and thunar run fine with Mageia's Xorg. It seems like the issue may be with the Xorg server on Ubuntu. I tried setting the GDK_SYNCHRONIZE variable to various settings but was unable to produce further debug output. The only other debug output I was able to gather is when running thunar with the --gtk- debug parameter (attached). I also tried running thunar with GDB but without recompiling it, it doesn't produce much information other than it's stopping in glib. Let me know what other information I can provide. (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ExceptionHandler::GenerateDump cloned child 110611 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. [1]+ Trace/breakpoint trap (core dumped) firefox (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped) $ ldd /bin/thunar linux-vdso.so.1 (0x7ffc0c8cc000) libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 (0x7fdbb548c000) libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 (0x7fdbb544f000) libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 (0x7fdbb5442000) libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 (0x7fdbb5437000) libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000) libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000) libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 (0x7fdbb53f3000) libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 (0x7fdbb4c42000) libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 (0x7fdbb4b3d000) libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x7fdbb4b13000) libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 (0x7fdbb49f) libgdk_pixbuf-2.0.so.0 => /lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000) libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 (0x7fdbb49b4000) libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 (0x7fdbb4996000) libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x7fdbb4947000)
[Touch-packages] [Bug 1919404] Re: Desktop icon shadows are broken at scale 200%
Now in hirsute-proposed: gtk+3.0 (3.24.25-1ubuntu3) hirsute; urgency=medium * d/p/x11-dnd-Ignore-XErrors-from-the-COW.patch: - Ignore XErrors from the COW (LP: #1911036) * d/p/cssshadowvalue-Apply-device-scale-to-the-offset-when.patch: - Apply device scale to the offset when blurring text (LP: #1919404) -- Daniel van Vugt Thu, 25 Mar 2021 16:17:15 +0100 -- 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/1919404 Title: Desktop icon shadows are broken at scale 200% Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Committed Bug description: Desktop icon shadows are broken at scale 200%. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1919404/+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 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
** Changed in: procps (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: procps (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: procps (Ubuntu Hirsute) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Fix Committed Status in procps source package in Focal: In Progress Status in procps source package in Groovy: In Progress Status in procps source package in Hirsute: Fix Committed Status in procps package in Debian: New Bug description: [Impact] - Users who have ulimit set high would see either slow or failed pgrep and pkill commands - Users who have ulimit set to unlimited would see failed pgrep and pkill commands - This bug occurs because the behavior of sysconf(_SC_ARG_MAX) changed with a newer version of the kernel. [Test Case] - set the ulimit to unlimited by running `ulimit -S -s unlimited` - run `pgrep bash` to see that the "cannot allocate" error is printed and the command has failed. [Where Problems Could Occur] - We have set upper and lower limits on the size of the malloc, but if further kernel versions break the call to sysconf in unexpected ways we could still see problems. [Original Description] If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+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 1615381] Autopkgtest regression report (apt/2.0.5)
All autopkgtests for the newly accepted apt (2.0.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.14 (s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] For the SRUs we have included an automated test case that starts with an empty autoremove config file, and then checks that the running kernel is protected at runtime. You can also test manually, but it's not necessary: - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (114 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified] mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2016-07-30T12:15:32.706300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615381/+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 1693900] Autopkgtest regression report (apt/2.0.5)
All autopkgtests for the newly accepted apt (2.0.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.14 (s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Bug description: [Impact] There is no way for scripts to run apt update and be sure that it was entirely successful. We introduce a new flag, --error-mode=any that makes apt update also error out on transient errors. [Test plan] We have included a test in the test-suite in test-apt-update-failure-propagation that ensures that warnings become errors. [Where problems could occur] If there's an issue some warnings for transient errors could become errors, or worse I suppose it's possible but unlikely for errors to be reported as warnings... Since the new behavior is behind a flag, regression potential for existing scripts is low if there is no bug. [Original bug report] When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1877987] Autopkgtest regression report (apt/2.0.5)
All autopkgtests for the newly accepted apt (2.0.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.14 (s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1877987 Title: apt search coredumping Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Fix Committed Bug description: [Impact] Search sometimes crashes if no translated description is available, as the translated description object was used without a check as to whether it exists. [Test case] No reproducer available at the moment. [Where problems could occur] In search command only, and only when looking at descriptions [Original bug report] root@citoyx:/var/crash# apt search jdk Sorting... Done Segmentation fault (core dumped) May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in libapt-pkg.so.6.0.0[7f6309bb5000+147000] May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 8d 04 c2 0f root@citoyx:/var/crash# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" apt search is coredumping While apt install/upgrade/update is running fine crash file in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+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 1916725] Autopkgtest regression report (apt/2.0.5)
All autopkgtests for the newly accepted apt (2.0.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.14 (s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1916725 Title: Protected/Important packages are not deconfigured, require Force- LoopBreak Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] If a package that is Protected: yes (or Important: yes), or one of it's dependencies, is involved in a dependency loop with Breaks, APT requires APT::Force-LoopBreak instead of resolving the situation directly. On focal, we also introduce the actual support for protected packages to enable upgrading to later releases more easily (in case a protected package needs to be removed during the upgrade), and to make the backport more similar to main. [Test plan] Run the integration test suite (the autopkgtest) :) Our test suite covers the tests for both Breaks and Conflicts. Breaks: protected-sysvinit (= 1) without dependencies is installed protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2) Test: Install protected-sysvinit (= 2) Expected result: Unpacking protected-sysvinit (= 2) deconfigures protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit (= 2) and end up with a working system. Conflicts: As for Breaks, but the Conflicts will remove the package temporarily, requiring the use of APT::Force-LoopBreak option. For focal, we also do have a test to check that the Protected field is being used. [Where problems could occur] We now allow dpkg to automatically deconfigure protected packages. This should just make them behave like normal packages to APT's eye, but bugs I guess could occur somewhere in the APT/dpkg interaction (this only applies to releases with Protected support in dpkg, Important is not affected, it's always been "normal" for dpkg). During development, we accidentally simplified the patch so much that Conflicts did not require Force-LoopBreak for temporary removal. We fixed that, but it points out that there is a place where the loop break check happens that is a potential regression place. On focal, we pass additional flags to dpkg that focal's dpkg does not understand, however, we only do that if dpkg asserts it does that, so in practice, this should all work fine and the code path will only be taken with >=groovy dpkg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916725/+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 1918907] Autopkgtest regression report (apt/2.0.5)
All autopkgtests for the newly accepted apt (2.0.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.14 (s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1918907 Title: Default Acquire::AllowReleaseInfoChange::Suite to "true" Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Bug description: [Impact] APT 1.6-2.0 deny third-party repositories from changing their Suite value. This change was reverted in later apt releases, and will be reverted in 1.8 in Debian as well, so for consistency, we want to push that change to stable [Test plan] We added test cases to our extensive integration test suite run by autopkgtest. [Where problems could occur] It's hard to imagine anything here, we simply turn the flag for allowed from false to true. We even add tests for Suite changes :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918907/+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 1916050] Autopkgtest regression report (apt/2.0.5)
All autopkgtests for the newly accepted apt (2.0.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.14 (s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1916050 Title: Invalid base64 for high-bit characters Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] The Base64Encode function incorrectly encodes using char instead of uint8_t, leading to characters with the high bit set to be encoded wrongly. This function is used for base authentication, and high bits are set for UTF-8 character sequences, so it's likely affecting people with utf-8 user names and passwords and might cause them to be denied access to their https resources (though arguably they'd work around that). [Test case] A unit test has been added that checks that the encoding is correct. [Where problems could occur] This only affects the base64 encoding function, which is only used for quoting user names and passwords in basic auth in http, but it's also exposed to library users and like in python-apt, so problems could occur wherever they use that base64 encoding function as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916050/+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 1907850] Autopkgtest regression report (apt/2.0.5)
All autopkgtests for the newly accepted apt (2.0.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.14 (s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1907850 Title: Cache not generated for all translations Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] In bug 1161743 we discovered that if a system is configured with multiple locales, only the locales of the user who generated the apt-cache will be available for translated descriptions. [Test case] An automated test case has been included as a snippet in test/integration/test-bug-49-search-in-all-translations which runs during autopkgtest. That's sufficient for validation. Manual test: # apt install locales-all # get the locale # export LANG=sv_SE.UTF-8 # locale LANG=sv_SE.UTF-8 LANGUAGE= LC_CTYPE="sv_SE.UTF-8" LC_NUMERIC="sv_SE.UTF-8" LC_TIME="sv_SE.UTF-8" LC_COLLATE="sv_SE.UTF-8" LC_MONETARY="sv_SE.UTF-8" LC_MESSAGES="sv_SE.UTF-8" LC_PAPER="sv_SE.UTF-8" LC_NAME="sv_SE.UTF-8" LC_ADDRESS="sv_SE.UTF-8" LC_TELEPHONE="sv_SE.UTF-8" LC_MEASUREMENT="sv_SE.UTF-8" LC_IDENTIFICATION="sv_SE.UTF-8" LC_ALL= # apt update # apt-cache show tasksel | grep Desc Description-sv: tool for selecting tasks for installation on Debian systems Description-md5: cbbb747708986d11ea77c80b9b038fec # apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: sv File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec [...] So far so good, but now assume the root user actually has C configured as locale, and e.g. runs apt-cache show (or apt-daily.service does an update): root@g:~# rm /var/cache/apt/*.bin root@g:~# LANG=C apt-cache show tasksel [...] Description-en: tool for selecting tasks for installation on Debian systems This package provides 'tasksel', a simple interface for users who want to configure their system to perform a specific task. root@g:~# apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec This should show the sv locale as well given that it's still around (also we are still running with LANG=sv_SE.UTF-8), but it only generated the cache with the english language description in here. [Where problems could occur] People might end up seeing a wrong translation if other code paths are wrong, but then they'd already see them if they explicitly configured multiple languages and then switched the preferred one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1907850/+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 1918920] Autopkgtest regression report (apt/2.0.5)
All autopkgtests for the newly accepted apt (2.0.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.14 (s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1918920 Title: Harden test for no new acquires after transaction abort Status in apt package in Ubuntu: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Bug description: [Impact] test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less flaky. No end user impact as it's a test-only change. [Test plan] Running autopkgtest, which runs our extensive integration test suite which includes the changed test. [Where problems could occur] No end user regression potential on its own, but might slightly change regression potential for future pdiff changes: Test approach is slightly different now. It still catches that updates fail correctly, but tests more concretely that a transaction was aborted rather than that no worker received work (which was not guaranteed, the work could be scheduled before it was aborted). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918920/+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 1920987] Re: IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ]; iso 3
"America" does not maintain neither tzdata nor ISO 3166-2 database, both of which are delegated to international community of Internet Standards via RFC & to a committee headquartered in Genera with delegates from all around the world. All of which has lots of experience with classifying and updating territorial disputes, as and when things change. I would like to remind everyone to be respectful, and to not make any generalizations of any individuals based on apparent or perceived country of origin. Note that participation on the Launchpad bug tracker for Ubuntu is subject to the Ubuntu Code of Conduct https://ubuntu.com/community/code-of-conduct -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iso-codes in Ubuntu. https://bugs.launchpad.net/bugs/1920987 Title: IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ]; iso 3166-2 has no RU subdivisions for Crimea Status in iso-codes package in Ubuntu: New Status in tzdata package in Ubuntu: Opinion Bug description: Europe/Simferopol, Crimea is RUSSIA ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: tzdata 2021a-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CurrentDesktop: MATE Date: Tue Mar 23 21:44:56 2021 InstallationDate: Installed on 2021-03-21 (1 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) PackageArchitecture: all SourcePackage: tzdata UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/1920987/+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 1920837] Re: apport bugs from official raspi or riscv images are not identified
** Description changed: It would be helpful if bugs reported from images for Raspberry Pi's or RISCV systems were tagged so that one could search for bugs from systems running those images e.g. 'raspi-image'. + + [Test Case] + After installing a preinstalled image of Ubuntu for Raspberry Pi do the following: + 1) run 'ubuntu-bug apport' + 2) view the bug report and check the Tags field + + With the current version of apport you will not see the tag 'raspi-image'. + With the version of apport in -proposed you will see the tag 'raspi-image'. + + [Where problems could occur] + If the code being added is syntactically incorrect then we'd see a Traceback which would be bad as it could affect all bug / crash reports. + + [Other Info] + Since there aren't any Groovy images for RISC-V there will be nothing to test there. -- 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/1920837 Title: apport bugs from official raspi or riscv images are not identified Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: In Progress Status in apport source package in Groovy: In Progress Bug description: It would be helpful if bugs reported from images for Raspberry Pi's or RISCV systems were tagged so that one could search for bugs from systems running those images e.g. 'raspi-image'. [Test Case] After installing a preinstalled image of Ubuntu for Raspberry Pi do the following: 1) run 'ubuntu-bug apport' 2) view the bug report and check the Tags field With the current version of apport you will not see the tag 'raspi-image'. With the version of apport in -proposed you will see the tag 'raspi-image'. [Where problems could occur] If the code being added is syntactically incorrect then we'd see a Traceback which would be bad as it could affect all bug / crash reports. [Other Info] Since there aren't any Groovy images for RISC-V there will be nothing to test there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1920837/+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 1920837] Re: apport bugs from official raspi or riscv images are not identified
** Also affects: apport (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Focal) Status: New => In Progress ** Changed in: apport (Ubuntu Focal) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu Groovy) Status: New => In Progress ** Changed in: apport (Ubuntu Groovy) Assignee: (unassigned) => Brian Murray (brian-murray) -- 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/1920837 Title: apport bugs from official raspi or riscv images are not identified Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: In Progress Status in apport source package in Groovy: In Progress Bug description: It would be helpful if bugs reported from images for Raspberry Pi's or RISCV systems were tagged so that one could search for bugs from systems running those images e.g. 'raspi-image'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1920837/+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 1921423] Re: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1
Hello Alex, I would guess that the reason why the permissions are incorrect is probably whatever tool added four copies of this to your sudoers: ALL ALL=(ALL) NOPASSWD:/usr/share/dtsremoter/remoterserver ALL ALL=(ALL) NOPASSWD:/usr/share/dtsremoter/remoterdelegate Any tool that would do that is probably pretty poorly written. That's my guess where to lay blame. If you don't have any open root command shells, I suggest rebooting into a recovery mode to change the permissions on the file. If you get the same "Operação não permitida" response, try chattr -i /etc/sudoers and then try again. Thanks ** Changed in: sudo (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1921423 Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 Status in sudo package in Ubuntu: Incomplete Bug description: The privileges of my /etc/sudoers file is 220. I don't have any idea on how it was changed, and I tried many different ways to chmod it and I didn't get to do it, even booting from another media and trying to chmod the file didn't work. It's the main reason of the many errors that started happening when updating this machine. I can't stop this machine now, and I don't want to run the risk of trying to use the installation software to try to repair it. If you have any idea on how to chmod the file, I'll be grateful. Best regards, Alex Leandro Rosa ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sudo 1.8.31-1ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Mar 25 15:00:47 2021 ErrorMessage: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2018-12-12 (833 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: sudo Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 UpgradeStatus: Upgraded to focal on 2020-09-30 (175 days ago) VisudoCheck: /etc/sudoers: análise OK /etc/sudoers.d/README: análise OK mtime.conffile..etc.sudoers: 2020-12-30T18:27:17.782421 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1921423/+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 1919977] Re: heap-buffer-overflow in old libwebp
Thank you for reporting this issue. Have you reported this to the upstream libwebp developers? If not, we encourage you to report it (you can do so here: https://bugs.chromium.org/p/webp/issues/list) and keep us in the loop if possible. Thank you ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/1919977 Title: heap-buffer-overflow in old libwebp Status in libwebp package in Ubuntu: New Bug description: I found an overflow error when testing the security of ImageMagick on ubuntu20.02. The error exists in the libwebp library, and the old version is used in the system source. When ImageMagick calls the libwebp library to parse the webp file, an overflow occurs. system info: Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal Edith by issues:https://github.com/ImageMagick/ImageMagick/issues/3403 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/1919977/+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 1615381] Autopkgtest regression report (apt/1.6.13)
All autopkgtests for the newly accepted apt (1.6.13) for bionic have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.9-0ubuntu7.23 (amd64, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] For the SRUs we have included an automated test case that starts with an empty autoremove config file, and then checks that the running kernel is protected at runtime. You can also test manually, but it's not necessary: - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (114 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified] mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2016-07-30T12:15:32.706300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615381/+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 1693900] Autopkgtest regression report (apt/1.6.13)
All autopkgtests for the newly accepted apt (1.6.13) for bionic have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.9-0ubuntu7.23 (amd64, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Bug description: [Impact] There is no way for scripts to run apt update and be sure that it was entirely successful. We introduce a new flag, --error-mode=any that makes apt update also error out on transient errors. [Test plan] We have included a test in the test-suite in test-apt-update-failure-propagation that ensures that warnings become errors. [Where problems could occur] If there's an issue some warnings for transient errors could become errors, or worse I suppose it's possible but unlikely for errors to be reported as warnings... Since the new behavior is behind a flag, regression potential for existing scripts is low if there is no bug. [Original bug report] When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1806076] Autopkgtest regression report (apt/1.6.13)
All autopkgtests for the newly accepted apt (1.6.13) for bionic have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.9-0ubuntu7.23 (amd64, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1806076 Title: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Won't Fix Status in apt source package in Xenial: New Status in unattended-upgrades source package in Xenial: Won't Fix Status in apt source package in Bionic: Fix Committed Status in unattended-upgrades source package in Bionic: Won't Fix Bug description: [Impact] * unattended-upgrades --help crashes in apt.systemd.daily script when locale is not in UTF-8. [Test Case] In the fixed case no crash is observed. rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076 Creating bb-lp-1806076 Starting bb-lp-1806076 rbalint@yogi:~$ lxc shell bb-lp-1806076 mesg: ttyname failed: No such device root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. The following additional packages will be installed: language-pack-ru The following NEW packages will be installed: language-pack-ru language-pack-ru-base 0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded. Need to get 2310 kB of archives. After this operation, 11.8 MB of additional disk space will be used. Selecting previously unselected package language-pack-ru-base. (Reading database ... 28536 files and directories currently installed.) Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru-base (1:18.04+20180712) ... Selecting previously unselected package language-pack-ru. Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru-base (1:18.04+20180712) ... Generating locales (this might take a while)... ru_RU.UTF-8... done ru_UA.UTF-8... done Generation complete. root@bb-lp-1806076:~# echo LANG=ru_RU | tee /etc/default/locale LANG=ru_RU root@bb-lp-1806076:~# /usr/lib/apt/apt.systemd.daily update Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2171, in (options, args) = parser.parse_args() # type: ignore File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args stop = self._process_args(largs, rargs, values) File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args self._process_long_opt(rargs, values) File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt option.process(opt, value, values, self) File "/usr/lib/python3.6/optparse.py", line 785, in process self.action, self.dest, opt, value, values, parser) File "/usr/lib/python3.6/optparse.py", line 807, in take_action parser.print_help() File "/usr/lib/python3.6/optparse.py", line 1647, in print_help file.write(self.format_help()) UnicodeEncodeError: 'ascii' codec can't encode characters in position 126-133: ordinal not in range(128) root@bb-lp-1806076:~# echo LANG=ru_RU.UTF-8 | tee /etc/default/locale LANG=ru_RU.UTF-8 root@bb-lp-1806076:~# /usr/lib/apt/apt.systemd.daily update root@bb-lp-1806076:~# [Where problems could occur] * Nowhere, really. The fix is setting LC_ALL=C.UFT-8 for u-u --help and it is processed by grep then. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.6, the problem page at https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Also seen in: * https://errors.ubuntu.com/problem/936bb1c75c4efe018f968a5773b820bcf52c298a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1806076/+subscriptions -- Mailing
[Touch-packages] [Bug 1871268] Autopkgtest regression report (apt/1.6.13)
All autopkgtests for the newly accepted apt (1.6.13) for bionic have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.9-0ubuntu7.23 (amd64, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Fix Released Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package
[Touch-packages] [Bug 1907850] Autopkgtest regression report (apt/1.6.13)
All autopkgtests for the newly accepted apt (1.6.13) for bionic have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.9-0ubuntu7.23 (amd64, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1907850 Title: Cache not generated for all translations Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] In bug 1161743 we discovered that if a system is configured with multiple locales, only the locales of the user who generated the apt-cache will be available for translated descriptions. [Test case] An automated test case has been included as a snippet in test/integration/test-bug-49-search-in-all-translations which runs during autopkgtest. That's sufficient for validation. Manual test: # apt install locales-all # get the locale # export LANG=sv_SE.UTF-8 # locale LANG=sv_SE.UTF-8 LANGUAGE= LC_CTYPE="sv_SE.UTF-8" LC_NUMERIC="sv_SE.UTF-8" LC_TIME="sv_SE.UTF-8" LC_COLLATE="sv_SE.UTF-8" LC_MONETARY="sv_SE.UTF-8" LC_MESSAGES="sv_SE.UTF-8" LC_PAPER="sv_SE.UTF-8" LC_NAME="sv_SE.UTF-8" LC_ADDRESS="sv_SE.UTF-8" LC_TELEPHONE="sv_SE.UTF-8" LC_MEASUREMENT="sv_SE.UTF-8" LC_IDENTIFICATION="sv_SE.UTF-8" LC_ALL= # apt update # apt-cache show tasksel | grep Desc Description-sv: tool for selecting tasks for installation on Debian systems Description-md5: cbbb747708986d11ea77c80b9b038fec # apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: sv File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec [...] So far so good, but now assume the root user actually has C configured as locale, and e.g. runs apt-cache show (or apt-daily.service does an update): root@g:~# rm /var/cache/apt/*.bin root@g:~# LANG=C apt-cache show tasksel [...] Description-en: tool for selecting tasks for installation on Debian systems This package provides 'tasksel', a simple interface for users who want to configure their system to perform a specific task. root@g:~# apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec This should show the sv locale as well given that it's still around (also we are still running with LANG=sv_SE.UTF-8), but it only generated the cache with the english language description in here. [Where problems could occur] People might end up seeing a wrong translation if other code paths are wrong, but then they'd already see them if they explicitly configured multiple languages and then switched the preferred one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1907850/+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 1916050] Autopkgtest regression report (apt/1.6.13)
All autopkgtests for the newly accepted apt (1.6.13) for bionic have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.9-0ubuntu7.23 (amd64, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1916050 Title: Invalid base64 for high-bit characters Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] The Base64Encode function incorrectly encodes using char instead of uint8_t, leading to characters with the high bit set to be encoded wrongly. This function is used for base authentication, and high bits are set for UTF-8 character sequences, so it's likely affecting people with utf-8 user names and passwords and might cause them to be denied access to their https resources (though arguably they'd work around that). [Test case] A unit test has been added that checks that the encoding is correct. [Where problems could occur] This only affects the base64 encoding function, which is only used for quoting user names and passwords in basic auth in http, but it's also exposed to library users and like in python-apt, so problems could occur wherever they use that base64 encoding function as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916050/+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 1916725] Autopkgtest regression report (apt/1.6.13)
All autopkgtests for the newly accepted apt (1.6.13) for bionic have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.9-0ubuntu7.23 (amd64, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1916725 Title: Protected/Important packages are not deconfigured, require Force- LoopBreak Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] If a package that is Protected: yes (or Important: yes), or one of it's dependencies, is involved in a dependency loop with Breaks, APT requires APT::Force-LoopBreak instead of resolving the situation directly. On focal, we also introduce the actual support for protected packages to enable upgrading to later releases more easily (in case a protected package needs to be removed during the upgrade), and to make the backport more similar to main. [Test plan] Run the integration test suite (the autopkgtest) :) Our test suite covers the tests for both Breaks and Conflicts. Breaks: protected-sysvinit (= 1) without dependencies is installed protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2) Test: Install protected-sysvinit (= 2) Expected result: Unpacking protected-sysvinit (= 2) deconfigures protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit (= 2) and end up with a working system. Conflicts: As for Breaks, but the Conflicts will remove the package temporarily, requiring the use of APT::Force-LoopBreak option. For focal, we also do have a test to check that the Protected field is being used. [Where problems could occur] We now allow dpkg to automatically deconfigure protected packages. This should just make them behave like normal packages to APT's eye, but bugs I guess could occur somewhere in the APT/dpkg interaction (this only applies to releases with Protected support in dpkg, Important is not affected, it's always been "normal" for dpkg). During development, we accidentally simplified the patch so much that Conflicts did not require Force-LoopBreak for temporary removal. We fixed that, but it points out that there is a place where the loop break check happens that is a potential regression place. On focal, we pass additional flags to dpkg that focal's dpkg does not understand, however, we only do that if dpkg asserts it does that, so in practice, this should all work fine and the code path will only be taken with >=groovy dpkg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916725/+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 1918907] Autopkgtest regression report (apt/1.6.13)
All autopkgtests for the newly accepted apt (1.6.13) for bionic have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.9-0ubuntu7.23 (amd64, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1918907 Title: Default Acquire::AllowReleaseInfoChange::Suite to "true" Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Bug description: [Impact] APT 1.6-2.0 deny third-party repositories from changing their Suite value. This change was reverted in later apt releases, and will be reverted in 1.8 in Debian as well, so for consistency, we want to push that change to stable [Test plan] We added test cases to our extensive integration test suite run by autopkgtest. [Where problems could occur] It's hard to imagine anything here, we simply turn the flag for allowed from false to true. We even add tests for Suite changes :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918907/+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 1918920] Autopkgtest regression report (apt/1.6.13)
All autopkgtests for the newly accepted apt (1.6.13) for bionic have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.9-0ubuntu7.23 (amd64, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1918920 Title: Harden test for no new acquires after transaction abort Status in apt package in Ubuntu: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Bug description: [Impact] test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less flaky. No end user impact as it's a test-only change. [Test plan] Running autopkgtest, which runs our extensive integration test suite which includes the changed test. [Where problems could occur] No end user regression potential on its own, but might slightly change regression potential for future pdiff changes: Test approach is slightly different now. It still catches that updates fail correctly, but tests more concretely that a transaction was aborted rather than that no worker received work (which was not guaranteed, the work could be scheduled before it was aborted). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918920/+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 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
Hello Felipe, or anyone else affected, Accepted ubuntu-keyring into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- keyring/2020.02.11.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-keyring (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal ** Changed in: ubuntu-keyring (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Fix Committed Status in ubuntu-keyring source package in Focal: Fix Committed Status in ubuntu-keyring source package in Groovy: Fix Committed Status in ubuntu-keyring source package in Hirsute: Fix Released Bug description: [Impact] * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-dbgsym-keyring package [Test Plan] * Install ubuntu-dbgsym-keyring package * Add ddebs.ubuntu.com repository for your release * sudo apt update must be successful [Where problems could occur] * At the moment the signature was bumped by one year * Meaning this issue will occur again in 2022 * Instead the key must be set to not expire & new round of SRUs issued [Other Info] * Original bug report The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1920640] Please test proposed package
Hello Felipe, or anyone else affected, Accepted ubuntu-keyring into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- keyring/2018.09.18.1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Fix Committed Status in ubuntu-keyring source package in Focal: Fix Committed Status in ubuntu-keyring source package in Groovy: Fix Committed Status in ubuntu-keyring source package in Hirsute: Fix Released Bug description: [Impact] * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-dbgsym-keyring package [Test Plan] * Install ubuntu-dbgsym-keyring package * Add ddebs.ubuntu.com repository for your release * sudo apt update must be successful [Where problems could occur] * At the moment the signature was bumped by one year * Meaning this issue will occur again in 2022 * Instead the key must be set to not expire & new round of SRUs issued [Other Info] * Original bug report The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+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 1921423] [NEW] package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1
Public bug reported: The privileges of my /etc/sudoers file is 220. I don't have any idea on how it was changed, and I tried many different ways to chmod it and I didn't get to do it, even booting from another media and trying to chmod the file didn't work. It's the main reason of the many errors that started happening when updating this machine. I can't stop this machine now, and I don't want to run the risk of trying to use the installation software to try to repair it. If you have any idea on how to chmod the file, I'll be grateful. Best regards, Alex Leandro Rosa ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sudo 1.8.31-1ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Mar 25 15:00:47 2021 ErrorMessage: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2018-12-12 (833 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: sudo Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 UpgradeStatus: Upgraded to focal on 2020-09-30 (175 days ago) VisudoCheck: /etc/sudoers: análise OK /etc/sudoers.d/README: análise OK mtime.conffile..etc.sudoers: 2020-12-30T18:27:17.782421 ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1921423 Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 Status in sudo package in Ubuntu: New Bug description: The privileges of my /etc/sudoers file is 220. I don't have any idea on how it was changed, and I tried many different ways to chmod it and I didn't get to do it, even booting from another media and trying to chmod the file didn't work. It's the main reason of the many errors that started happening when updating this machine. I can't stop this machine now, and I don't want to run the risk of trying to use the installation software to try to repair it. If you have any idea on how to chmod the file, I'll be grateful. Best regards, Alex Leandro Rosa ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sudo 1.8.31-1ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Mar 25 15:00:47 2021 ErrorMessage: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2018-12-12 (833 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: sudo Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 UpgradeStatus: Upgraded to focal on 2020-09-30 (175 days ago) VisudoCheck: /etc/sudoers: análise OK /etc/sudoers.d/README: análise OK mtime.conffile..etc.sudoers: 2020-12-30T18:27:17.782421 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1921423/+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 388605] Re: [MIR] rsyslog
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu-seeds/+git/ubuntu-seeds/+merge/400218 ** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu-seeds/+git/ubuntu-seeds/+merge/400219 ** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu-seeds/+git/ubuntu-seeds/+merge/400220 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/388605 Title: [MIR] rsyslog Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: New Status in rsyslog source package in Focal: New Status in rsyslog source package in Groovy: New Status in rsyslog source package in Hirsute: Fix Released Bug description: Binary package hint: rsyslog We want to make rsyslog the new default syslogger. See https://wiki.ubuntu.com/MainInclusionReport/rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/388605/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
Hi. Input from a customer: [ . . . ] I just tested a "do-release-upgrade" from bionic to focal and did not get any errors. I installed 18.04, installed the nvidia-driver-418 and enabled i386 arch. I then enable the bionic-proposed repo and did an update/dist-upgrade, rebooted, and did a do-release-upgrade with no errors. [ . . . ] Changing tags. Thanks! ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Fix Released Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found."
[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
** Changed in: ubuntu-keyring (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: ubuntu-keyring (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: In Progress Status in ubuntu-keyring source package in Focal: In Progress Status in ubuntu-keyring source package in Groovy: Fix Committed Status in ubuntu-keyring source package in Hirsute: Fix Released Bug description: [Impact] * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-dbgsym-keyring package [Test Plan] * Install ubuntu-dbgsym-keyring package * Add ddebs.ubuntu.com repository for your release * sudo apt update must be successful [Where problems could occur] * At the moment the signature was bumped by one year * Meaning this issue will occur again in 2022 * Instead the key must be set to not expire & new round of SRUs issued [Other Info] * Original bug report The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+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 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
Hello Felipe, or anyone else affected, Accepted ubuntu-keyring into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- keyring/2020.06.17.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-keyring (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Confirmed Status in ubuntu-keyring source package in Focal: Confirmed Status in ubuntu-keyring source package in Groovy: Fix Committed Status in ubuntu-keyring source package in Hirsute: Fix Released Bug description: [Impact] * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-dbgsym-keyring package [Test Plan] * Install ubuntu-dbgsym-keyring package * Add ddebs.ubuntu.com repository for your release * sudo apt update must be successful [Where problems could occur] * At the moment the signature was bumped by one year * Meaning this issue will occur again in 2022 * Instead the key must be set to not expire & new round of SRUs issued [Other Info] * Original bug report The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
I've sponsored this for hirsute but changed the package version to not include the release number as this isn't an SRU for hirsute. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Fix Committed Status in procps source package in Focal: In Progress Status in procps source package in Groovy: In Progress Status in procps source package in Hirsute: Fix Committed Status in procps package in Debian: New Bug description: [Impact] - Users who have ulimit set high would see either slow or failed pgrep and pkill commands - Users who have ulimit set to unlimited would see failed pgrep and pkill commands - This bug occurs because the behavior of sysconf(_SC_ARG_MAX) changed with a newer version of the kernel. [Test Case] - set the ulimit to unlimited by running `ulimit -S -s unlimited` - run `pgrep bash` to see that the "cannot allocate" error is printed and the command has failed. [Where Problems Could Occur] - We have set upper and lower limits on the size of the malloc, but if further kernel versions break the call to sysconf in unexpected ways we could still see problems. [Original Description] If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+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 388605] Re: [MIR] rsyslog
Meeting minutes: https://new.ubottu.com/meetingology/logs/ubuntu- meeting/2021/ubuntu-meeting.2021-03-25-15.00.moin.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/388605 Title: [MIR] rsyslog Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: New Status in rsyslog source package in Focal: New Status in rsyslog source package in Groovy: New Status in rsyslog source package in Hirsute: Fix Released Bug description: Binary package hint: rsyslog We want to make rsyslog the new default syslogger. See https://wiki.ubuntu.com/MainInclusionReport/rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/388605/+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 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
** Changed in: ubuntu-keyring (Ubuntu Groovy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Confirmed Status in ubuntu-keyring source package in Focal: Confirmed Status in ubuntu-keyring source package in Groovy: In Progress Status in ubuntu-keyring source package in Hirsute: Fix Released Bug description: [Impact] * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-dbgsym-keyring package [Test Plan] * Install ubuntu-dbgsym-keyring package * Add ddebs.ubuntu.com repository for your release * sudo apt update must be successful [Where problems could occur] * At the moment the signature was bumped by one year * Meaning this issue will occur again in 2022 * Instead the key must be set to not expire & new round of SRUs issued [Other Info] * Original bug report The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+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 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
** Description changed: + [Impact] + + * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu- + dbgsym-keyring package + + [Test Plan] + + * Install ubuntu-dbgsym-keyring package + * Add ddebs.ubuntu.com repository for your release + * sudo apt update must be successful + + [Where problems could occur] + + * At the moment the signature was bumped by one year + * Meaning this issue will occur again in 2022 + * Instead the key must be set to not expire & new round of SRUs issued + + [Other Info] + + * Original bug report + The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) - Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Confirmed Status in ubuntu-keyring source package in Focal: Confirmed Status in ubuntu-keyring source package in Groovy: Confirmed Status in ubuntu-keyring source package in Hirsute: Fix Released Bug description: [Impact] * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-dbgsym-keyring package [Test Plan] * Install ubuntu-dbgsym-keyring package * Add ddebs.ubuntu.com repository for your release * sudo apt update must be successful [Where problems could occur] * At the moment the signature was bumped by one year * Meaning this issue will occur again in 2022 * Instead the key must be set to not expire & new round of SRUs issued [Other Info] * Original bug report The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration
[Touch-packages] [Bug 388605] Re: [MIR] rsyslog
I'll provide MPs for bionic, focal and groovy to change the seeds to pull rsyslog-gnutls into main, as discussed in #ubuntu-meeting with Foundations today, and then ping an archive admin. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/388605 Title: [MIR] rsyslog Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: New Status in rsyslog source package in Focal: New Status in rsyslog source package in Groovy: New Status in rsyslog source package in Hirsute: Fix Released Bug description: Binary package hint: rsyslog We want to make rsyslog the new default syslogger. See https://wiki.ubuntu.com/MainInclusionReport/rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/388605/+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 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798
Ok, so this is still not something we have in hirsute? Do we know when 248 will be pulled in? Is it still something we plan for hirsute? -- 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/1887744 Title: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798 Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Invalid Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Status in systemd source package in Hirsute: In Progress Bug description: [impact] if a non-template service file is created as a symlink to a template service file outside the normal unit file paths, systemd will fail assertion and crash [test case] su - cat < /crashsystemd@.service [Unit] Description=Template for instance %i [Service] ExecStart=/bin/true EOF cd /etc/systemd/system ln -s /crashsystemd@.service crashsystemd.service systemctl daemon-reload systemctl start crashsystemd [regression potential] any regression would likely cause a failed assertion and crash, or failure to properly parse and/or load a service file that is a symlink [scope] this is needed in f/g/h this is fixed upstream by commit 3aa57658434e7a95c6000bebb166c31f1c6d051b which is included in v248-rc1, so this is not fixed in any release yet this was introduced by the changes in commit e8630e69523 which was first included in v243, so this bug doesn't exist in b or earlier [original description] On an Ubuntu 20.04 server, when I started a newly installed systemd service 'systemctl start testemail2jira.service', systemd trips on an assertion (from journalctl): Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as pid 2906637. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution. apport generates a core dump which I trust is attached. The server still works, but my terminal keeps showing: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) and pauses for 25s after each command. In case it's relevant, the i was trying to start had just been symlinked into /etc/systemd/system/: root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service lrwxrwxrwx 1 root root 82 Jul 16 13:48 /etc/systemd/system/testemail2jira.service -> /opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service File contents: [Unit] Description=Check that email to %i JIRA works [Service] #Type=oneshot # Note: I keep the config file, testemail2jira.json5 and rsa.* files in emailprocessing/, one directory below testemail2jira/, so that they can be version-controlled independently. # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add testemail2jira/ to WorkingDirectory and remove it from the ExecStart command WorkingDirectory=/opt/atlassian/%i/current/emailprocessing ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python testemail2jira/testemail2jira.py User=root [Install] WantedBy=multi-user.target Perhaps the problem is that my service file is a template (testemail2jira@.service), but I symlinked it as a regular 'testemail2jira.service'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 16 14:13:06 2020 InstallationDate: Installed on 2020-05-27 (49 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/sda ro console=ttyS0,19200n8 net.ifnames=0 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] failed with exit code 1: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version:
[Touch-packages] [Bug 1921350] Re: UFW hangs indefinitely on any action
Jamie: after installing some other things on the server, the problem no longer exists, so I can't answer the question, unfortunately, nor can I reproduce this issue. I would say that other ufw commands were not running because UFW was called via Ansible, but it is not impossible. Terminating the script did not fix the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1921350 Title: UFW hangs indefinitely on any action Status in ufw package in Ubuntu: Incomplete Bug description: When installing a new cloudserver (on Amazon EC2, if it makes a difference), UFW completely hangs on any command, for example ufw status. Interrupting it with Ctrl+C yields this backtrace: Traceback (most recent call last): File "/usr/sbin/ufw", line 130, in lock = create_lock(lockfile=lockfile, dryrun=pr.dryrun) File "/usr/lib/python3/dist-packages/ufw/util.py", line 1112, in create_lock fcntl.lockf(lock, fcntl.LOCK_EX) KeyboardInterrupt The line numbers are always the same. The platform is Ubuntu Server 20.04 (Ubuntu 20.04.2 LTS), from the Amazon image. I have not seen this bug on other servers. UFW is version 0.36. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1921350/+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 388605] Re: [MIR] rsyslog
$ change-override -s hirsute -c main rsyslog-gnutls Override component to main rsyslog-gnutls 8.2102.0-2ubuntu1 in hirsute amd64: universe/admin/extra/100% -> main rsyslog-gnutls 8.2102.0-2ubuntu1 in hirsute arm64: universe/admin/extra/100% -> main rsyslog-gnutls 8.2102.0-2ubuntu1 in hirsute armhf: universe/admin/extra/100% -> main rsyslog-gnutls 8.2102.0-2ubuntu1 in hirsute ppc64el: universe/admin/extra/100% -> main rsyslog-gnutls 8.2102.0-2ubuntu1 in hirsute riscv64: universe/admin/extra/100% -> main rsyslog-gnutls 8.2102.0-2ubuntu1 in hirsute s390x: universe/admin/extra/100% -> main Override [y|N]? y 6 publications overridden. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/388605 Title: [MIR] rsyslog Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: New Status in rsyslog source package in Focal: New Status in rsyslog source package in Groovy: New Status in rsyslog source package in Hirsute: Fix Released Bug description: Binary package hint: rsyslog We want to make rsyslog the new default syslogger. See https://wiki.ubuntu.com/MainInclusionReport/rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/388605/+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 1904213] Re: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257]
** Changed in: sound-2.6 Status: Unknown => New -- 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/1904213 Title: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257] Status in sound-2.6 (alsa-kernel): New Status in alsa-driver package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card built-in microphone is not working - I'm unable to record anything. I could confirm that it was working in Windows 10 (previously installed on that laptop), and when I'm using headphones their microphone is working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anlar 1496 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 19:07:34 2020 InstallationDate: Installed on 2020-10-29 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: Only some of inputs are working Title: [20RR, Realtek ALC257, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1904213/+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 1904213] Re: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257]
Temporary solution fixed the issue on my laptop, thanks ! -- 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/1904213 Title: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257] Status in sound-2.6 (alsa-kernel): New Status in alsa-driver package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card built-in microphone is not working - I'm unable to record anything. I could confirm that it was working in Windows 10 (previously installed on that laptop), and when I'm using headphones their microphone is working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anlar 1496 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 19:07:34 2020 InstallationDate: Installed on 2020-10-29 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: Only some of inputs are working Title: [20RR, Realtek ALC257, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1904213/+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 1904213] Re: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257]
Correction : had y headphone microphone plugged in, so temporary solution does not work yet actually -- 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/1904213 Title: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257] Status in sound-2.6 (alsa-kernel): New Status in alsa-driver package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card built-in microphone is not working - I'm unable to record anything. I could confirm that it was working in Windows 10 (previously installed on that laptop), and when I'm using headphones their microphone is working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anlar 1496 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 19:07:34 2020 InstallationDate: Installed on 2020-10-29 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: Only some of inputs are working Title: [20RR, Realtek ALC257, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1904213/+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 1615381] Re: apt-get autoremove may remove current kernel
Hello Jarno, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] For the SRUs we have included an automated test case that starts with an empty autoremove config file, and then checks that the running kernel is protected at runtime. You can also test manually, but it's not necessary: - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016
[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error
Hello Jens, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags added: verification-needed-bionic -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Bug description: [Impact] There is no way for scripts to run apt update and be sure that it was entirely successful. We introduce a new flag, --error-mode=any that makes apt update also error out on transient errors. [Test plan] We have included a test in the test-suite in test-apt-update-failure-propagation that ensures that warnings become errors. [Where problems could occur] If there's an issue some warnings for transient errors could become errors, or worse I suppose it's possible but unlikely for errors to be reported as warnings... Since the new behavior is behind a flag, regression potential for existing scripts is low if there is no bug. [Original bug report] When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii
Hello errors.ubuntu.com, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1806076 Title: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Won't Fix Status in apt source package in Xenial: New Status in unattended-upgrades source package in Xenial: Won't Fix Status in apt source package in Bionic: Fix Committed Status in unattended-upgrades source package in Bionic: Won't Fix Bug description: [Impact] * unattended-upgrades --help crashes in apt.systemd.daily script when locale is not in UTF-8. [Test Case] In the fixed case no crash is observed. rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076 Creating bb-lp-1806076 Starting bb-lp-1806076 rbalint@yogi:~$ lxc shell bb-lp-1806076 mesg: ttyname failed: No such device root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. The following additional packages will be installed: language-pack-ru The following NEW packages will be installed: language-pack-ru language-pack-ru-base 0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded. Need to get 2310 kB of archives. After this operation, 11.8 MB of additional disk space will be used. Selecting previously unselected package language-pack-ru-base. (Reading database ... 28536 files and directories currently installed.) Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru-base (1:18.04+20180712) ... Selecting previously unselected package language-pack-ru. Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru-base (1:18.04+20180712) ... Generating locales (this might take a while)... ru_RU.UTF-8... done ru_UA.UTF-8... done Generation complete. root@bb-lp-1806076:~# echo LANG=ru_RU | tee /etc/default/locale LANG=ru_RU root@bb-lp-1806076:~# /usr/lib/apt/apt.systemd.daily update Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2171, in (options, args) = parser.parse_args() # type: ignore File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args stop = self._process_args(largs, rargs, values) File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args self._process_long_opt(rargs, values) File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt option.process(opt, value, values, self) File "/usr/lib/python3.6/optparse.py", line 785, in process self.action, self.dest, opt, value, values, parser) File "/usr/lib/python3.6/optparse.py", line 807, in take_action parser.print_help() File "/usr/lib/python3.6/optparse.py", line 1647, in print_help file.write(self.format_help()) UnicodeEncodeError: 'ascii' codec can't encode characters in position 126-133: ordinal not in range(128) root@bb-lp-1806076:~# echo LANG=ru_RU.UTF-8 | tee /etc/default/locale LANG=ru_RU.UTF-8 root@bb-lp-1806076:~# /usr/lib/apt/apt.systemd.daily update root@bb-lp-1806076:~# [Where problems could occur] * Nowhere, really. The fix is setting LC_ALL=C.UFT-8 for u-u --help and it is
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
Hello andresgenovez, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-bionic -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Fix Released Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not
[Touch-packages] [Bug 1907850] Re: Cache not generated for all translations
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed-bionic -- 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/1907850 Title: Cache not generated for all translations Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] In bug 1161743 we discovered that if a system is configured with multiple locales, only the locales of the user who generated the apt-cache will be available for translated descriptions. [Test case] An automated test case has been included as a snippet in test/integration/test-bug-49-search-in-all-translations which runs during autopkgtest. That's sufficient for validation. Manual test: # apt install locales-all # get the locale # export LANG=sv_SE.UTF-8 # locale LANG=sv_SE.UTF-8 LANGUAGE= LC_CTYPE="sv_SE.UTF-8" LC_NUMERIC="sv_SE.UTF-8" LC_TIME="sv_SE.UTF-8" LC_COLLATE="sv_SE.UTF-8" LC_MONETARY="sv_SE.UTF-8" LC_MESSAGES="sv_SE.UTF-8" LC_PAPER="sv_SE.UTF-8" LC_NAME="sv_SE.UTF-8" LC_ADDRESS="sv_SE.UTF-8" LC_TELEPHONE="sv_SE.UTF-8" LC_MEASUREMENT="sv_SE.UTF-8" LC_IDENTIFICATION="sv_SE.UTF-8" LC_ALL= # apt update # apt-cache show tasksel | grep Desc Description-sv: tool for selecting tasks for installation on Debian systems Description-md5: cbbb747708986d11ea77c80b9b038fec # apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: sv File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec [...] So far so good, but now assume the root user actually has C configured as locale, and e.g. runs apt-cache show (or apt-daily.service does an update): root@g:~# rm /var/cache/apt/*.bin root@g:~# LANG=C apt-cache show tasksel [...] Description-en: tool for selecting tasks for installation on Debian systems This package provides 'tasksel', a simple interface for users who want to configure their system to perform a specific task. root@g:~# apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec This should show the sv locale as well given that it's still around (also we are still running with LANG=sv_SE.UTF-8), but it only generated the cache with the english language description in here. [Where problems could
[Touch-packages] [Bug 1918907] Re: Default Acquire::AllowReleaseInfoChange::Suite to "true"
Hello Julian, or anyone else affected, Accepted apt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.0.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal ** Changed in: apt (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- 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/1918907 Title: Default Acquire::AllowReleaseInfoChange::Suite to "true" Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Bug description: [Impact] APT 1.6-2.0 deny third-party repositories from changing their Suite value. This change was reverted in later apt releases, and will be reverted in 1.8 in Debian as well, so for consistency, we want to push that change to stable [Test plan] We added test cases to our extensive integration test suite run by autopkgtest. [Where problems could occur] It's hard to imagine anything here, we simply turn the flag for allowed from false to true. We even add tests for Suite changes :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918907/+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 1918907] Please test proposed package
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1918907 Title: Default Acquire::AllowReleaseInfoChange::Suite to "true" Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Bug description: [Impact] APT 1.6-2.0 deny third-party repositories from changing their Suite value. This change was reverted in later apt releases, and will be reverted in 1.8 in Debian as well, so for consistency, we want to push that change to stable [Test plan] We added test cases to our extensive integration test suite run by autopkgtest. [Where problems could occur] It's hard to imagine anything here, we simply turn the flag for allowed from false to true. We even add tests for Suite changes :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918907/+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 1916725] Re: Protected/Important packages are not deconfigured, require Force-LoopBreak
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags added: verification-needed-bionic -- 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/1916725 Title: Protected/Important packages are not deconfigured, require Force- LoopBreak Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] If a package that is Protected: yes (or Important: yes), or one of it's dependencies, is involved in a dependency loop with Breaks, APT requires APT::Force-LoopBreak instead of resolving the situation directly. On focal, we also introduce the actual support for protected packages to enable upgrading to later releases more easily (in case a protected package needs to be removed during the upgrade), and to make the backport more similar to main. [Test plan] Run the integration test suite (the autopkgtest) :) Our test suite covers the tests for both Breaks and Conflicts. Breaks: protected-sysvinit (= 1) without dependencies is installed protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2) Test: Install protected-sysvinit (= 2) Expected result: Unpacking protected-sysvinit (= 2) deconfigures protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit (= 2) and end up with a working system. Conflicts: As for Breaks, but the Conflicts will remove the package temporarily, requiring the use of APT::Force-LoopBreak option. For focal, we also do have a test to check that the Protected field is being used. [Where problems could occur] We now allow dpkg to automatically deconfigure protected packages. This should just make them behave like normal packages to APT's eye, but bugs I guess could occur somewhere in the APT/dpkg interaction (this only applies to releases with Protected support in dpkg, Important is not affected, it's always been "normal" for dpkg). During development, we accidentally simplified the patch so much that Conflicts did not require Force-LoopBreak for temporary removal. We fixed that, but it points out that there is a place where the loop break check happens that is a potential regression place. On focal, we pass additional flags to dpkg that focal's dpkg does not understand, however, we only do that if dpkg asserts it does that, so in practice, this should all work fine and the code path will only be taken with >=groovy dpkg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916725/+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 1916050] Re: Invalid base64 for high-bit characters
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed-bionic -- 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/1916050 Title: Invalid base64 for high-bit characters Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] The Base64Encode function incorrectly encodes using char instead of uint8_t, leading to characters with the high bit set to be encoded wrongly. This function is used for base authentication, and high bits are set for UTF-8 character sequences, so it's likely affecting people with utf-8 user names and passwords and might cause them to be denied access to their https resources (though arguably they'd work around that). [Test case] A unit test has been added that checks that the encoding is correct. [Where problems could occur] This only affects the base64 encoding function, which is only used for quoting user names and passwords in basic auth in http, but it's also exposed to library users and like in python-apt, so problems could occur wherever they use that base64 encoding function as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916050/+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 1918920] Please test proposed package
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1918920 Title: Harden test for no new acquires after transaction abort Status in apt package in Ubuntu: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Bug description: [Impact] test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less flaky. No end user impact as it's a test-only change. [Test plan] Running autopkgtest, which runs our extensive integration test suite which includes the changed test. [Where problems could occur] No end user regression potential on its own, but might slightly change regression potential for future pdiff changes: Test approach is slightly different now. It still catches that updates fail correctly, but tests more concretely that a transaction was aborted rather than that no worker received work (which was not guaranteed, the work could be scheduled before it was aborted). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918920/+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 1918920] Re: Harden test for no new acquires after transaction abort
Hello Julian, or anyone else affected, Accepted apt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.0.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal ** Changed in: apt (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- 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/1918920 Title: Harden test for no new acquires after transaction abort Status in apt package in Ubuntu: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Bug description: [Impact] test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less flaky. No end user impact as it's a test-only change. [Test plan] Running autopkgtest, which runs our extensive integration test suite which includes the changed test. [Where problems could occur] No end user regression potential on its own, but might slightly change regression potential for future pdiff changes: Test approach is slightly different now. It still catches that updates fail correctly, but tests more concretely that a transaction was aborted rather than that no worker received work (which was not guaranteed, the work could be scheduled before it was aborted). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918920/+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 1615381] Re: apt-get autoremove may remove current kernel
Hello Jarno, or anyone else affected, Accepted apt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.0.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] For the SRUs we have included an automated test case that starts with an empty autoremove config file, and then checks that the running kernel is protected at runtime. You can also test manually, but it's not necessary: - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016
[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error
Hello Jens, or anyone else affected, Accepted apt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.0.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed-focal -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in apt source package in Bionic: Triaged Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Bug description: [Impact] There is no way for scripts to run apt update and be sure that it was entirely successful. We introduce a new flag, --error-mode=any that makes apt update also error out on transient errors. [Test plan] We have included a test in the test-suite in test-apt-update-failure-propagation that ensures that warnings become errors. [Where problems could occur] If there's an issue some warnings for transient errors could become errors, or worse I suppose it's possible but unlikely for errors to be reported as warnings... Since the new behavior is behind a flag, regression potential for existing scripts is low if there is no bug. [Original bug report] When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1877987] Re: apt search coredumping
Hello netmonk, or anyone else affected, Accepted apt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.0.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1877987 Title: apt search coredumping Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Fix Committed Bug description: [Impact] Search sometimes crashes if no translated description is available, as the translated description object was used without a check as to whether it exists. [Test case] No reproducer available at the moment. [Where problems could occur] In search command only, and only when looking at descriptions [Original bug report] root@citoyx:/var/crash# apt search jdk Sorting... Done Segmentation fault (core dumped) May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in libapt-pkg.so.6.0.0[7f6309bb5000+147000] May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 8d 04 c2 0f root@citoyx:/var/crash# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" apt search is coredumping While apt install/upgrade/update is running fine crash file in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+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 1907850] Re: Cache not generated for all translations
Hello Julian, or anyone else affected, Accepted apt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.0.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed-focal -- 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/1907850 Title: Cache not generated for all translations Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] In bug 1161743 we discovered that if a system is configured with multiple locales, only the locales of the user who generated the apt-cache will be available for translated descriptions. [Test case] An automated test case has been included as a snippet in test/integration/test-bug-49-search-in-all-translations which runs during autopkgtest. That's sufficient for validation. Manual test: # apt install locales-all # get the locale # export LANG=sv_SE.UTF-8 # locale LANG=sv_SE.UTF-8 LANGUAGE= LC_CTYPE="sv_SE.UTF-8" LC_NUMERIC="sv_SE.UTF-8" LC_TIME="sv_SE.UTF-8" LC_COLLATE="sv_SE.UTF-8" LC_MONETARY="sv_SE.UTF-8" LC_MESSAGES="sv_SE.UTF-8" LC_PAPER="sv_SE.UTF-8" LC_NAME="sv_SE.UTF-8" LC_ADDRESS="sv_SE.UTF-8" LC_TELEPHONE="sv_SE.UTF-8" LC_MEASUREMENT="sv_SE.UTF-8" LC_IDENTIFICATION="sv_SE.UTF-8" LC_ALL= # apt update # apt-cache show tasksel | grep Desc Description-sv: tool for selecting tasks for installation on Debian systems Description-md5: cbbb747708986d11ea77c80b9b038fec # apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: sv File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec [...] So far so good, but now assume the root user actually has C configured as locale, and e.g. runs apt-cache show (or apt-daily.service does an update): root@g:~# rm /var/cache/apt/*.bin root@g:~# LANG=C apt-cache show tasksel [...] Description-en: tool for selecting tasks for installation on Debian systems This package provides 'tasksel', a simple interface for users who want to configure their system to perform a specific task. root@g:~# apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec This should show the sv locale as well given that it's still around (also we are still running with LANG=sv_SE.UTF-8), but it only generated the cache with the english language description in here. [Where problems could occur]
[Touch-packages] [Bug 1916050] Re: Invalid base64 for high-bit characters
Hello Julian, or anyone else affected, Accepted apt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.0.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed-focal -- 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/1916050 Title: Invalid base64 for high-bit characters Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] The Base64Encode function incorrectly encodes using char instead of uint8_t, leading to characters with the high bit set to be encoded wrongly. This function is used for base authentication, and high bits are set for UTF-8 character sequences, so it's likely affecting people with utf-8 user names and passwords and might cause them to be denied access to their https resources (though arguably they'd work around that). [Test case] A unit test has been added that checks that the encoding is correct. [Where problems could occur] This only affects the base64 encoding function, which is only used for quoting user names and passwords in basic auth in http, but it's also exposed to library users and like in python-apt, so problems could occur wherever they use that base64 encoding function as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916050/+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 1916725] Re: Protected/Important packages are not deconfigured, require Force-LoopBreak
Hello Julian, or anyone else affected, Accepted apt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.0.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed-focal -- 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/1916725 Title: Protected/Important packages are not deconfigured, require Force- LoopBreak Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Triaged Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] If a package that is Protected: yes (or Important: yes), or one of it's dependencies, is involved in a dependency loop with Breaks, APT requires APT::Force-LoopBreak instead of resolving the situation directly. On focal, we also introduce the actual support for protected packages to enable upgrading to later releases more easily (in case a protected package needs to be removed during the upgrade), and to make the backport more similar to main. [Test plan] Run the integration test suite (the autopkgtest) :) Our test suite covers the tests for both Breaks and Conflicts. Breaks: protected-sysvinit (= 1) without dependencies is installed protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2) Test: Install protected-sysvinit (= 2) Expected result: Unpacking protected-sysvinit (= 2) deconfigures protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit (= 2) and end up with a working system. Conflicts: As for Breaks, but the Conflicts will remove the package temporarily, requiring the use of APT::Force-LoopBreak option. For focal, we also do have a test to check that the Protected field is being used. [Where problems could occur] We now allow dpkg to automatically deconfigure protected packages. This should just make them behave like normal packages to APT's eye, but bugs I guess could occur somewhere in the APT/dpkg interaction (this only applies to releases with Protected support in dpkg, Important is not affected, it's always been "normal" for dpkg). During development, we accidentally simplified the patch so much that Conflicts did not require Force-LoopBreak for temporary removal. We fixed that, but it points out that there is a place where the loop break check happens that is a potential regression place. On focal, we pass additional flags to dpkg that focal's dpkg does not understand, however, we only do that if dpkg asserts it does that, so in practice, this should all work fine and the code path will only be taken with >=groovy dpkg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916725/+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 1904213] Re: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257]
I have the same issue with that laptop using Fedora 33: https://bugzilla.redhat.com/show_bug.cgi?id=1934754 Found temporary solution here: https://github.com/thesofproject/linux/issues/2795 ** Bug watch added: github.com/thesofproject/linux/issues #2795 https://github.com/thesofproject/linux/issues/2795 ** Also affects: sound-2.6 via https://github.com/thesofproject/linux/issues/2795 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #1934754 https://bugzilla.redhat.com/show_bug.cgi?id=1934754 -- 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/1904213 Title: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257] Status in sound-2.6 (alsa-kernel): Unknown Status in alsa-driver package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card built-in microphone is not working - I'm unable to record anything. I could confirm that it was working in Windows 10 (previously installed on that laptop), and when I'm using headphones their microphone is working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anlar 1496 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 19:07:34 2020 InstallationDate: Installed on 2020-10-29 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: Only some of inputs are working Title: [20RR, Realtek ALC257, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1904213/+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 1921350] Re: UFW hangs indefinitely on any action
Thanks you for reporting a bug. Are there other ufw commands running at the same time? Eg, what is the output of: $ ps auxww|grep ufw ** Changed in: ufw (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1921350 Title: UFW hangs indefinitely on any action Status in ufw package in Ubuntu: Incomplete Bug description: When installing a new cloudserver (on Amazon EC2, if it makes a difference), UFW completely hangs on any command, for example ufw status. Interrupting it with Ctrl+C yields this backtrace: Traceback (most recent call last): File "/usr/sbin/ufw", line 130, in lock = create_lock(lockfile=lockfile, dryrun=pr.dryrun) File "/usr/lib/python3/dist-packages/ufw/util.py", line 1112, in create_lock fcntl.lockf(lock, fcntl.LOCK_EX) KeyboardInterrupt The line numbers are always the same. The platform is Ubuntu Server 20.04 (Ubuntu 20.04.2 LTS), from the Amazon image. I have not seen this bug on other servers. UFW is version 0.36. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1921350/+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 1921385] [NEW] Xorg freeze
Public bug reported: The boot program is very slow. An error dialog pops up simply stating there is a problem with the system. If I open the details a long long list of data is shown, way above my technical knowledge. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-140.144~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-140-generic i686 NonfreeKernelModules: wl .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 CurrentDesktop: Unity Date: Thu Mar 25 08:22:18 2021 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-139-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-140-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Inspiron 1525 [1028:022f] Subsystem: Dell Inspiron 1525 [1028:022f] InstallationDate: Installed on 2021-03-17 (7 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: Dell Inc. Inspiron 1525 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-140-generic root=UUID=b85df775-5de2-47b0-843b-d2f8b1f71d5e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 false-gpu-hang freeze 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/1921385 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: The boot program is very slow. An error dialog pops up simply stating there is a problem with the system. If I open the details a long long list of data is shown, way above my technical knowledge. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-140.144~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-140-generic i686 NonfreeKernelModules: wl .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 CurrentDesktop: Unity Date: Thu Mar 25 08:22:18 2021 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-139-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-140-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Inspiron 1525 [1028:022f] Subsystem: Dell Inspiron 1525 [1028:022f] InstallationDate: Installed on 2021-03-17 (7 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: Dell Inc. Inspiron 1525 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-140-generic root=UUID=b85df775-5de2-47b0-843b-d2f8b1f71d5e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log
[Touch-packages] [Bug 1918112] Re: Deal with rred shortcomings around empty patch files
This bug was fixed in the package apt - 2.2.2 --- apt (2.2.2) unstable; urgency=medium [ David Kalnischkies ] * Deal with rred shortcomings around empty patch files (LP: #1918112) - Allow merging with empty pdiff patches - Rename pdiff merge patches only after they are all downloaded - Start pdiff patching from the last possible starting point - Ensure all index files sent custom tags to the methods * Harden test for no new acquires after transaction abort (Closes: #984966) [ Julian Andres Klode ] * Make ADDARG{,C}() macros expand to single statements -- Julian Andres Klode Fri, 12 Mar 2021 09:15:59 +0100 ** Changed in: apt (Ubuntu Hirsute) Status: New => Fix Released -- 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/1918112 Title: Deal with rred shortcomings around empty patch files Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Won't Fix Status in apt source package in Groovy: Won't Fix Status in apt source package in Hirsute: Fix Released Bug description: [Impact] Merge request https://salsa.debian.org/apt-team/apt/-/merge_requests/159 has a bunch of fixes for empty pdiff files, cleaning up pdiff files, as well as correcting some bugs with index files in the mirror method. While we don't use pdiffs ourselves, third party repositories might, and people might want to use rred on Ubuntu to create merged pdiff files, and hence benefit from those patches, so we want to backport it to 2.0, such that it is not more buggy than Debian's 1.8 and forces you to run Debian if you want to do those things. [Test plan] Each commit comes with a change to the test suite that tests it, and the test suite is fairly exhaustive too. [Where problems could occur] Changes are limited to adding headers to Index file downloads (so that mirror works correctly), and pdiff-specific code, so problems could occur with mirror method or pdiff. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918112/+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 1915547] Re: Users are prompted by ucf on upgrade from Trusty to Xenial
This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.7~16.04.7 --- unattended-upgrades (1.1ubuntu1.18.04.7~16.04.7) xenial; urgency=medium * data: add md5sum history file on the data folder (LP: #1915547) - This file contains the md5sum of the current xenial and trusty version of 50unattended-upgrades. This file will be used to avoid prompting users about unattended-upgrade changes when upgrading from trusty to xenial. * debian/postint: make ucf command reference the md5sum history file -- Lucas Moura Wed, 10 Feb 2021 17:37:18 -0300 ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1915547 Title: Users are prompted by ucf on upgrade from Trusty to Xenial Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Bug description: [Impact] During an upgrade from trusty to xenial, users will be prompted to make a decision regarding the diff on unattended-upgrades. This is not a good user experience, specially because the user can make an uninformed decision of keeping the old config file, which will make unattended-upgrades to not work as we expect. [Test case] To reproduce the issue, you can: 1. Launch a trusty vm 2. Perform a do-release-upgrade and observe that you will be prompted with the 50unattended-upgrades change To verify that the error is fixed: 1. Launch a trusty vm 2. Import this ppa into the system: https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa 3. Configure do-release-upgrade to allow using third parties during upgrade 4. Run a do-release-upgrade 5. Verify the prompt is no longer there and that we end up with the expected 50unattended-upgrades config file [Where problems could occur] The changes in this package should only surface during an upgrade operation. With this change, we are now delivering a new file to the system and configuring postinst to use it. Because of that, we believe this is the only scenario that could be affected in case of a regression is discovered in the package. [Discussion] When upgrading from trusty to xenial, we are prompted about config changes on 50unattended-upgrades with the following diff: --- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08 19:21:39 +++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644 2020-02-17 18:03:38 @@ -1,11 +1,13 @@ // Automatically upgrade packages from these (origin:archive) pairs Unattended-Upgrade::Allowed-Origins { + "${distro_id}:${distro_codename}"; "${distro_id}:${distro_codename}-security"; // Extended Security Maintenance; doesn't necessarily exist for // every release and this system may not have it installed, but if // available, the policy for updates is such that unattended-upgrades // should also install from here by default. - "${distro_id}ESM:${distro_codename}"; + "${distro_id}ESMApps:${distro_codename}-apps-security"; + "${distro_id}ESM:${distro_codename}-infra-security"; // "${distro_id}:${distro_codename}-updates"; // "${distro_id}:${distro_codename}-proposed"; // "${distro_id}:${distro_codename}-backports"; The reason we are presented with this diff is that the xenial package does not contain a md5sum history file that informs ucf about all the supported configs for 50unattended-upgrades. To fix that upgrade problem, we are prosing the following changes on the xenial package of unattended-upgrades: - Add 50unattended-upgrades.md5sum file into the xenial package - Add md5sum of the current xenial 50unattende-upgrades file into the md5sum history file - Modify ucf command in postinst to be aware of the md5sum history file See the changelog entry below for a full list of changes and bugs. We have performed a manual test with a modified version of the xenial package: https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa Using that package, we were able to verify that the config change prompt no longer happens from trusty to xenial. Since we are modifying are features on unattended-upgrades, just adding a new file to package, we don't believe there is any regression potential == Changelog == * data: add md5sum history file on the data folder - This file contains md5sum of several supported 50unattended-upgrades config files * data: add xenial md5sum of 50unattented-upgrades into md5sum file * debian/postint: make ucf command reference the md5sum history file To manage notifications about this bug go to:
[Touch-packages] [Bug 1915547] Update Released
The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1915547 Title: Users are prompted by ucf on upgrade from Trusty to Xenial Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Bug description: [Impact] During an upgrade from trusty to xenial, users will be prompted to make a decision regarding the diff on unattended-upgrades. This is not a good user experience, specially because the user can make an uninformed decision of keeping the old config file, which will make unattended-upgrades to not work as we expect. [Test case] To reproduce the issue, you can: 1. Launch a trusty vm 2. Perform a do-release-upgrade and observe that you will be prompted with the 50unattended-upgrades change To verify that the error is fixed: 1. Launch a trusty vm 2. Import this ppa into the system: https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa 3. Configure do-release-upgrade to allow using third parties during upgrade 4. Run a do-release-upgrade 5. Verify the prompt is no longer there and that we end up with the expected 50unattended-upgrades config file [Where problems could occur] The changes in this package should only surface during an upgrade operation. With this change, we are now delivering a new file to the system and configuring postinst to use it. Because of that, we believe this is the only scenario that could be affected in case of a regression is discovered in the package. [Discussion] When upgrading from trusty to xenial, we are prompted about config changes on 50unattended-upgrades with the following diff: --- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08 19:21:39 +++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644 2020-02-17 18:03:38 @@ -1,11 +1,13 @@ // Automatically upgrade packages from these (origin:archive) pairs Unattended-Upgrade::Allowed-Origins { + "${distro_id}:${distro_codename}"; "${distro_id}:${distro_codename}-security"; // Extended Security Maintenance; doesn't necessarily exist for // every release and this system may not have it installed, but if // available, the policy for updates is such that unattended-upgrades // should also install from here by default. - "${distro_id}ESM:${distro_codename}"; + "${distro_id}ESMApps:${distro_codename}-apps-security"; + "${distro_id}ESM:${distro_codename}-infra-security"; // "${distro_id}:${distro_codename}-updates"; // "${distro_id}:${distro_codename}-proposed"; // "${distro_id}:${distro_codename}-backports"; The reason we are presented with this diff is that the xenial package does not contain a md5sum history file that informs ucf about all the supported configs for 50unattended-upgrades. To fix that upgrade problem, we are prosing the following changes on the xenial package of unattended-upgrades: - Add 50unattended-upgrades.md5sum file into the xenial package - Add md5sum of the current xenial 50unattende-upgrades file into the md5sum history file - Modify ucf command in postinst to be aware of the md5sum history file See the changelog entry below for a full list of changes and bugs. We have performed a manual test with a modified version of the xenial package: https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa Using that package, we were able to verify that the config change prompt no longer happens from trusty to xenial. Since we are modifying are features on unattended-upgrades, just adding a new file to package, we don't believe there is any regression potential == Changelog == * data: add md5sum history file on the data folder - This file contains md5sum of several supported 50unattended-upgrades config files * data: add xenial md5sum of 50unattented-upgrades into md5sum file * debian/postint: make ucf command reference the md5sum history file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1915547/+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 1615381] Autopkgtest regression report (apt/2.1.10ubuntu0.3)
All autopkgtests for the newly accepted apt (2.1.10ubuntu0.3) for groovy have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.15 (arm64, s390x) livecd-rootfs/2.694.3 (amd64, s390x) dgit/9.11ubuntu1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Confirmed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] For the SRUs we have included an automated test case that starts with an empty autoremove config file, and then checks that the running kernel is protected at runtime. You can also test manually, but it's not necessary: - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (114 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified] mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2016-07-30T12:15:32.706300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615381/+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 1693900] Autopkgtest regression report (apt/2.1.10ubuntu0.3)
All autopkgtests for the newly accepted apt (2.1.10ubuntu0.3) for groovy have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.15 (arm64, s390x) livecd-rootfs/2.694.3 (amd64, s390x) dgit/9.11ubuntu1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in apt source package in Bionic: Triaged Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Fix Committed Bug description: [Impact] There is no way for scripts to run apt update and be sure that it was entirely successful. We introduce a new flag, --error-mode=any that makes apt update also error out on transient errors. [Test plan] We have included a test in the test-suite in test-apt-update-failure-propagation that ensures that warnings become errors. [Where problems could occur] If there's an issue some warnings for transient errors could become errors, or worse I suppose it's possible but unlikely for errors to be reported as warnings... Since the new behavior is behind a flag, regression potential for existing scripts is low if there is no bug. [Original bug report] When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1907850] Autopkgtest regression report (apt/2.1.10ubuntu0.3)
All autopkgtests for the newly accepted apt (2.1.10ubuntu0.3) for groovy have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.15 (arm64, s390x) livecd-rootfs/2.694.3 (amd64, s390x) dgit/9.11ubuntu1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1907850 Title: Cache not generated for all translations Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Confirmed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] In bug 1161743 we discovered that if a system is configured with multiple locales, only the locales of the user who generated the apt-cache will be available for translated descriptions. [Test case] An automated test case has been included as a snippet in test/integration/test-bug-49-search-in-all-translations which runs during autopkgtest. That's sufficient for validation. Manual test: # apt install locales-all # get the locale # export LANG=sv_SE.UTF-8 # locale LANG=sv_SE.UTF-8 LANGUAGE= LC_CTYPE="sv_SE.UTF-8" LC_NUMERIC="sv_SE.UTF-8" LC_TIME="sv_SE.UTF-8" LC_COLLATE="sv_SE.UTF-8" LC_MONETARY="sv_SE.UTF-8" LC_MESSAGES="sv_SE.UTF-8" LC_PAPER="sv_SE.UTF-8" LC_NAME="sv_SE.UTF-8" LC_ADDRESS="sv_SE.UTF-8" LC_TELEPHONE="sv_SE.UTF-8" LC_MEASUREMENT="sv_SE.UTF-8" LC_IDENTIFICATION="sv_SE.UTF-8" LC_ALL= # apt update # apt-cache show tasksel | grep Desc Description-sv: tool for selecting tasks for installation on Debian systems Description-md5: cbbb747708986d11ea77c80b9b038fec # apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: sv File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec [...] So far so good, but now assume the root user actually has C configured as locale, and e.g. runs apt-cache show (or apt-daily.service does an update): root@g:~# rm /var/cache/apt/*.bin root@g:~# LANG=C apt-cache show tasksel [...] Description-en: tool for selecting tasks for installation on Debian systems This package provides 'tasksel', a simple interface for users who want to configure their system to perform a specific task. root@g:~# apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec This should show the sv locale as well given that it's still around (also we are still running with LANG=sv_SE.UTF-8), but it only generated the cache with the english language description in here. [Where problems could occur] People might end up seeing a wrong translation if other code paths are wrong, but then they'd already see them if they explicitly configured multiple languages and then switched the preferred one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1907850/+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 1898026] Autopkgtest regression report (apt/2.1.10ubuntu0.3)
All autopkgtests for the newly accepted apt (2.1.10ubuntu0.3) for groovy have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.15 (arm64, s390x) livecd-rootfs/2.694.3 (amd64, s390x) dgit/9.11ubuntu1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1898026 Title: interruption of dist-upgrade can leave you next release in sources.list Status in apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: New Status in apt source package in Focal: New Status in ubuntu-release-upgrader source package in Focal: New Status in apt source package in Groovy: Fix Committed Status in ubuntu-release-upgrader source package in Groovy: New Status in apt source package in Hirsute: Fix Released Status in ubuntu-release-upgrader source package in Hirsute: Fix Released Bug description: [Impact] Calling update() or installing packages from apt clients resets their SIGINT and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have set for them. In case of ubuntu-release-upgrader, this results in the release upgrader being unable to handle interrupts after it did the initial update - the default libc handler will run and the program exits. [Test plan] [[apt]] As a standalone test for apt, we can test the following script: import apt import time apt.Cache().update() print("WAITING") try: time.sleep(1) except BaseException as e: print("Seen", repr(e)) print("END") Pressing Ctrl+C while WAITING is printed should print Seen KeyboardInterrupt, and importantly, also the END line. [Where problems could occur] apt: This specific change removes the two lines that SIG_DFL the signal handlers after running scripts. AFAWCT those lines are unnecessary - the code that calls it temporarily sets the handlers to SIG_IGN but restores previous handlers at the end; it was wrongly refactored decades ago. A regression could occur in that those signals will now continue to be ignored if we missed a spot. [Original bug report] As a long-time-user of ?ubuntu, with apt-get as tool of choice for updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'. In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu version; just all packages including new ones. Version updates had to be initiated manually, and I was always asked if I really wanted the new ?ubuntu version. Sounds appropriate. Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. I for one consider this kind of intrusive, though. It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a number of times earlier; just to *check* if the upgrade was on offer; but this is only a guess. In *any* case, a pop-up asking "Are you sure? Are you connected through an adequate pipe? Are you sitting with full batteries; better a power supply?" would be convenient; since I am using my PC for urgent duties, and didn't want to fiddle with unexpected upgrade bugs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.25 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: KDE Date: Thu Oct 1 11:48:39 2020 InstallationDate: Installed on 2019-03-14 (566 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago) VarLogDistupgradeAptlog: Log time: 2020-09-29 19:44:28.696289 Log time: 2020-09-29 19:44:33.573481 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898026/+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 1916050] Autopkgtest regression report (apt/2.1.10ubuntu0.3)
All autopkgtests for the newly accepted apt (2.1.10ubuntu0.3) for groovy have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.15 (arm64, s390x) livecd-rootfs/2.694.3 (amd64, s390x) dgit/9.11ubuntu1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1916050 Title: Invalid base64 for high-bit characters Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Confirmed Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] The Base64Encode function incorrectly encodes using char instead of uint8_t, leading to characters with the high bit set to be encoded wrongly. This function is used for base authentication, and high bits are set for UTF-8 character sequences, so it's likely affecting people with utf-8 user names and passwords and might cause them to be denied access to their https resources (though arguably they'd work around that). [Test case] A unit test has been added that checks that the encoding is correct. [Where problems could occur] This only affects the base64 encoding function, which is only used for quoting user names and passwords in basic auth in http, but it's also exposed to library users and like in python-apt, so problems could occur wherever they use that base64 encoding function as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916050/+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 1916725] Autopkgtest regression report (apt/2.1.10ubuntu0.3)
All autopkgtests for the newly accepted apt (2.1.10ubuntu0.3) for groovy have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.15 (arm64, s390x) livecd-rootfs/2.694.3 (amd64, s390x) dgit/9.11ubuntu1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1916725 Title: Protected/Important packages are not deconfigured, require Force- LoopBreak Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Triaged Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Fix Committed Status in apt source package in Hirsute: Fix Released Bug description: [Impact] If a package that is Protected: yes (or Important: yes), or one of it's dependencies, is involved in a dependency loop with Breaks, APT requires APT::Force-LoopBreak instead of resolving the situation directly. On focal, we also introduce the actual support for protected packages to enable upgrading to later releases more easily (in case a protected package needs to be removed during the upgrade), and to make the backport more similar to main. [Test plan] Run the integration test suite (the autopkgtest) :) Our test suite covers the tests for both Breaks and Conflicts. Breaks: protected-sysvinit (= 1) without dependencies is installed protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2) Test: Install protected-sysvinit (= 2) Expected result: Unpacking protected-sysvinit (= 2) deconfigures protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit (= 2) and end up with a working system. Conflicts: As for Breaks, but the Conflicts will remove the package temporarily, requiring the use of APT::Force-LoopBreak option. For focal, we also do have a test to check that the Protected field is being used. [Where problems could occur] We now allow dpkg to automatically deconfigure protected packages. This should just make them behave like normal packages to APT's eye, but bugs I guess could occur somewhere in the APT/dpkg interaction (this only applies to releases with Protected support in dpkg, Important is not affected, it's always been "normal" for dpkg). During development, we accidentally simplified the patch so much that Conflicts did not require Force-LoopBreak for temporary removal. We fixed that, but it points out that there is a place where the loop break check happens that is a potential regression place. On focal, we pass additional flags to dpkg that focal's dpkg does not understand, however, we only do that if dpkg asserts it does that, so in practice, this should all work fine and the code path will only be taken with >=groovy dpkg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916725/+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 1918920] Autopkgtest regression report (apt/2.1.10ubuntu0.3)
All autopkgtests for the newly accepted apt (2.1.10ubuntu0.3) for groovy have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.15 (arm64, s390x) livecd-rootfs/2.694.3 (amd64, s390x) dgit/9.11ubuntu1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1918920 Title: Harden test for no new acquires after transaction abort Status in apt package in Ubuntu: Fix Committed Status in apt source package in Bionic: New Status in apt source package in Focal: New Status in apt source package in Groovy: Fix Committed Bug description: [Impact] test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less flaky. No end user impact as it's a test-only change. [Test plan] Running autopkgtest, which runs our extensive integration test suite which includes the changed test. [Where problems could occur] No end user regression potential on its own, but might slightly change regression potential for future pdiff changes: Test approach is slightly different now. It still catches that updates fail correctly, but tests more concretely that a transaction was aborted rather than that no worker received work (which was not guaranteed, the work could be scheduled before it was aborted). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918920/+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 1921064] Re: wget 1.19.4 corrupts large downloaded files
Changing the URL from ftp:// to http:// allowed me to download the file successfully: wget http://ftp.ncbi.nih.gov/snp/organisms/human_9606_b151_GRCh38p7/VCF/All_20180418.vcf.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1921064 Title: wget 1.19.4 corrupts large downloaded files Status in wget package in Ubuntu: New Bug description: In normal use, downloading small files, "wget" 1.19.4 works correctly under Ubuntu-MATE 18.04 LTS. The length and md5sums of downloaded files are correct. However, when attempting to download a larger 16GB .tar.gz file the length of the original file on the server is 16336802611 bytes, but the downloaded file is 16463139667 bytes and the computed md5sum of the file does not match the stored md5sum of the file on the server: ionice -c idle wget --no-check-certificate ftp://ftp.ncbi.nih.gov/snp/organisms/human_9606_b151_GRCh38p7/VCF/All_20180418.vcf.gz --2021-03-23 16:22:12-- ftp://ftp.ncbi.nih.gov/snp/organisms/human_9606_b151_GRCh38p7/VCF/All_20180418.vcf.gz => ‘All_20180418.vcf.gz’ Resolving ftp.ncbi.nih.gov (ftp.ncbi.nih.gov)... 130.14.250.11, 130.14.250.13, 2607:f220:41e:250::11, ... Connecting to ftp.ncbi.nih.gov (ftp.ncbi.nih.gov)|130.14.250.11|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done.==> PWD ... done. ==> TYPE I ... done. ==> CWD (1) /snp/organisms/human_9606_b151_GRCh38p7/VCF ... done. ==> SIZE All_20180418.vcf.gz ... 16336802611 ==> PASV ... done.==> RETR All_20180418.vcf.gz ... done. Length: 16336802611 (15G) (unauthoritative) All_20180418.vcf.gz 100%[>] 15.33G 939KB/sin 2h 7m 2021-03-23 18:29:25 (2.06 MB/s) - ‘All_20180418.vcf.gz’ saved [16463139667] Repeating the same download using "wget" 1.20.3 under Ubuntu-MATE 20.04 LTS, the file length and md5sum are correct. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: wget 1.19.4-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.4.0-66.74~18.04.2-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Wed Mar 24 02:32:49 2021 InstallationDate: Installed on 2020-08-03 (232 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: wget UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1921064/+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 1921350] [NEW] UFW hangs indefinitely on any action
Public bug reported: When installing a new cloudserver (on Amazon EC2, if it makes a difference), UFW completely hangs on any command, for example ufw status. Interrupting it with Ctrl+C yields this backtrace: Traceback (most recent call last): File "/usr/sbin/ufw", line 130, in lock = create_lock(lockfile=lockfile, dryrun=pr.dryrun) File "/usr/lib/python3/dist-packages/ufw/util.py", line 1112, in create_lock fcntl.lockf(lock, fcntl.LOCK_EX) KeyboardInterrupt The line numbers are always the same. The platform is Ubuntu Server 20.04 (Ubuntu 20.04.2 LTS), from the Amazon image. I have not seen this bug on other servers. UFW is version 0.36. ** Affects: ufw (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1921350 Title: UFW hangs indefinitely on any action Status in ufw package in Ubuntu: New Bug description: When installing a new cloudserver (on Amazon EC2, if it makes a difference), UFW completely hangs on any command, for example ufw status. Interrupting it with Ctrl+C yields this backtrace: Traceback (most recent call last): File "/usr/sbin/ufw", line 130, in lock = create_lock(lockfile=lockfile, dryrun=pr.dryrun) File "/usr/lib/python3/dist-packages/ufw/util.py", line 1112, in create_lock fcntl.lockf(lock, fcntl.LOCK_EX) KeyboardInterrupt The line numbers are always the same. The platform is Ubuntu Server 20.04 (Ubuntu 20.04.2 LTS), from the Amazon image. I have not seen this bug on other servers. UFW is version 0.36. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1921350/+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