[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Steve Langasek]

** Changed in: apt (Ubuntu Focal)
   Status: Fix Released => Fix Committed

-- 
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:
  In Progress
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]
  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 1911858] [NEW] i am not aware what are these errors

[Karan Singh Parmar]

Public bug reported:

cant tell what are these errors releted too...

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Jan 15 12:32:10 2021
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0794]
InstallationDate: Installed on 2017-03-15 (1401 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 15-3568
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=a024a4c4-d7d6-404c-be82-173672511ace ro acpi_rev_override 
alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep 
alx.enable_wol=1 mem_sleep_default=deep drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2017
dmi.bios.release: 1.7
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.07.00
dmi.board.name: 01HYMY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr01.07.00:bd02/15/2017:br1.7:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01HYMY:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 15-3568
dmi.product.sku: 0794
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Wed Jan 13 10:43:27 2021
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.9-2ubuntu1.1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy third-party-packages ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1911858

Title:
  i am not aware what are these errors

Status in xorg package in Ubuntu:
  New

Bug description:
  cant tell what are these errors releted too...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Jan 15 12:32:10 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0794]
  InstallationDate: Installed on 2017-03-15 (1401 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 

[Touch-packages] [Bug 1911857] [NEW] cant tell whats wrong

[Karan Singh Parmar]

Public bug reported:

cant tell whats wrong

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Jan 15 12:30:06 2021
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0794]
InstallationDate: Installed on 2017-03-15 (1401 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 15-3568
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=a024a4c4-d7d6-404c-be82-173672511ace ro acpi_rev_override 
alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep 
alx.enable_wol=1 mem_sleep_default=deep drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2017
dmi.bios.release: 1.7
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.07.00
dmi.board.name: 01HYMY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr01.07.00:bd02/15/2017:br1.7:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01HYMY:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 15-3568
dmi.product.sku: 0794
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Wed Jan 13 10:43:27 2021
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.9-2ubuntu1.1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy third-party-packages ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1911857

Title:
  cant tell whats wrong

Status in xorg package in Ubuntu:
  New

Bug description:
  cant tell whats wrong

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Jan 15 12:30:06 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0794]
  InstallationDate: Installed on 2017-03-15 (1401 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   

[Touch-packages] [Bug 1910576] Re: [MIR] libbpf (dependency of iproute2)

[Christian Ehrhardt ]

Thanks, this seems ready for promotion then

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1910576

Title:
  [MIR] libbpf (dependency of iproute2)

Status in iproute2 package in Ubuntu:
  Invalid
Status in libbpf package in Ubuntu:
  Fix Committed

Bug description:
  [Availability]
  libbpf | 0.1.0-1 | groovy/universe  | source
  libbpf | 0.3-2   | hirsute/universe | source

  [Rationale]
  Libbpf is (or is about to become) a dependency for building iproute2 which 
already is in main. Using BPF is becoming more wide-spread. The library allows 
to load and use eBPF programs from user-space (functionality provided by the 
kernel). It is already maintained in main for Debian 
(https://tracker.debian.org/pkg/libbpf)

  [Security]
  Since the code is taken out of the Linux kernel, this should be treated 
similar to the kernel for security. Research uncovered no records about 
security issues.

  [Quality assurance]
  At this point there are no open bug reports against libbpf (except this one) 
in Ubuntu. Also no open bugs found in Debian. Project is taken from the kernel 
source and claims static analysis via LGTM and Coverty. Also has CI via Travis 
(https://travis-ci.com/github/libbpf/libbpf).
  Right now there are no dep-8 tests. Though potentially it should be possible 
to create those, would this really add additional benefit beyond having 
upstream CI?
  A test build on hirsute was showing no warnings beyond lintian complaining 
about things which would be changed if we had delta (unstable as series for 
example). Otherwise was clean.

  [Dependencies]
  libc6: main
  libelf1: main
  zlib1g: main

  [Standards compliance]
  $ lintian --pedantic libbpf_0.3-2.dsc
  P: libbpf source: no-homepage-field
  P: libbpf source: silent-on-rules-requiring-root

  [Maintenance]
  As this is only taking out code from the kernel into a separate library 
package, the maintenance effort should be minimal. Packaging is done in Debian 
and is synced into Ubuntu (no delta).

  [Background information]
  A discourse about why this is packaged outside the kernel can be found at 
https://lwn.net/Articles/836911/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1910576/+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 1828134] Re: Wifi not working after suspend/resume cycle

[Bug Watch Updater]

** Changed in: network-manager
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1828134

Title:
  Wifi not working after suspend/resume cycle

Status in NetworkManager:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  About 75% of the time for the past few weeks (I don't have a time
  where this started), my wifi is not working after resume from suspend.
  I'm happy to provide more debugging info if needed.

  I have tried an rmmod/modprobe on on the iwlwifi,iwlmvm modules just
  to see after the resume, and didn't re-enable the card.

  The symptoms are, the wlp4so interface is DOWN, I can't bring it up.
  gnome-network-manager widget turning the interface off/on doesn't
  work.  I don't see anything glaring in dmesg.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-generic 5.0.0.14.15
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dpb4587 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  7 18:49:01 2019
  InstallationDate: Installed on 2018-06-18 (323 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-14-generic 
root=UUID=fa64d67d-26bf-4c42-a12f-c45b6ea5117c ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-14-generic N/A
   linux-backports-modules-5.0.0-14-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-03-15 (53 days ago)
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET52W(1.37)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET52W(1.37):bd02/14/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1828134/+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 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic

[Chris Guiver]

Thanks for the update, and attempt to `apport-collect`.  I too was
unsure what package to re-file against, and had forgotten it was against
the meta package when I pasted the apport-collect request.

Ubuntu 20.04.2 release date
(https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule) refers to the ISO
release date. Installed systems will upgrade to it before the scheduled
date (usually a few days, however if the ISO release date is pushed
back/delayed, the installed systems upgrades do not get delayed except
for extraordinary circumstances) as is normal.

The 5.8 kernel has been the -edge option for some time now in focal
repositories, so people using 20.04 that have installed packages that
have dependencies that bring in the latest -edge kernel will have 5.8
already which is expected; any who remained on the the stable kernel
still use 5.4

I suspect the issue is understanding, or you've added additional
packages added to your system (graphics drivers, 3rd party etc) that
have pulled in the -edge kernel option and you off the default stable
kernel path. I hoped to gain more detail from the apport-collect, but
the package name needs correction first, and I don't know what it should
be against (if it's a bug, If there is a bug, I suspect it's only
documentation).

I've assumed you're using Ubuntu 20.04 Desktop, thus the 5.8 kernel is
expected due to announced change; if you're on Ubuntu Server, then this
is more of an issue as that doesn't default to HWE like Desktop does.
The different path now (from 20.04) between Desktop & Server does make
the HWE documents a little harder to write for (both were the same up to
and including 18.04/bionic).

FYI:  Today's Lubuntu 20.04.2 daily (2021-01-14) still has the 5.4
kernel, but it's the only current focal daily I've used today.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1911614

Title:
  Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of
  linux-generic

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Just as the title says, the 20.04 and 20.04.1 images use the HWE
  version of linux-generic resulting in upgrades to the 5.8 series
  kernel. This seems to effect Ubuntu only, or I should say I checked
  the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all
  correctly list linux-generic. Also HWE is not truly complete without
  the accompanying HWE Xstack.

  I checked all the documentation I could find and this was clearly not
  intentional. In fact the manifest for Ubuntu Focal Beta still used
  linux-generic, so this got messed up some time between April 3, 2020
  and April 23, 2020. Here's just one example of the documentation for
  kernel support in Focal LTS:

  https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle

  Installations performed with 20.04 and 20.04.1 media were supposed to
  remain on the 5.4 series kernel throughout Focal's 5 year lifespan as
  had been the case since HWE was introduced. The first step in fixing
  this needs to be stopping fresh installs of Focal using the 20.04 and
  20.04.1 media from immediately upgrading to the 5.8 series kernel.

  It might be a little tricky to revert users from 5.8 to 5.4, but there
  have been reports of breakage, particularly concerning Broadcom wifi
  drivers and some graphics problems. But the graphics problems could
  also be exacerbated by the lack of the matching HWE Xstack? At any
  rate it's a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+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 1904321] Re: does not work as it should " systemctl edit service"

[Launchpad Bug Tracker]

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1904321

Title:
  does not work as it should " systemctl edit service"

Status in systemd package in Ubuntu:
  Expired

Bug description:
  1. `systemctl edit service(elasticsearch)`
  That creates file `/etc/systemd/system/elasticsearch.service.d/override.conf`

  And I've added following section there:

  [Service]
  LimitMEMLOCK=infinity
  LimitNPROC=32768
  LimitNOFILE=25

  
  3. I've executed `systemctl daemon-reload; systemctl stop elasticsearch; 
systemctl start elasticsearch`

  However those parameters were not applied to a newly started service
  and I got an error "memory locking requested for elasticsearch process
  but memory is not locked".

  To workaround I've created a file
  `/etc/systemd/system/elasticsearch.service.d/elasticsearch.conf` with
  the same content and that fixed the problem.

  
  ubuntu 18.04, all updates are installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1904321/+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

[Satyansh Shukla]

** Changed in: apt (Ubuntu Focal)
   Status: Fix Committed => 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/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:
  In Progress
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Committed
Status in apt package in Debian:
  Unknown

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 1910576] Re: [MIR] libbpf (dependency of iproute2)

[Seth Arnold]

Thanks Christian, I think you're right, this probably doesn't need a
security review and being centralized in one place will probably be
easier to maintain.

Thanks

** Changed in: libbpf (Ubuntu)
   Status: New => Fix Committed

** Changed in: libbpf (Ubuntu)
 Assignee: Seth Arnold (seth-arnold) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1910576

Title:
  [MIR] libbpf (dependency of iproute2)

Status in iproute2 package in Ubuntu:
  Invalid
Status in libbpf package in Ubuntu:
  Fix Committed

Bug description:
  [Availability]
  libbpf | 0.1.0-1 | groovy/universe  | source
  libbpf | 0.3-2   | hirsute/universe | source

  [Rationale]
  Libbpf is (or is about to become) a dependency for building iproute2 which 
already is in main. Using BPF is becoming more wide-spread. The library allows 
to load and use eBPF programs from user-space (functionality provided by the 
kernel). It is already maintained in main for Debian 
(https://tracker.debian.org/pkg/libbpf)

  [Security]
  Since the code is taken out of the Linux kernel, this should be treated 
similar to the kernel for security. Research uncovered no records about 
security issues.

  [Quality assurance]
  At this point there are no open bug reports against libbpf (except this one) 
in Ubuntu. Also no open bugs found in Debian. Project is taken from the kernel 
source and claims static analysis via LGTM and Coverty. Also has CI via Travis 
(https://travis-ci.com/github/libbpf/libbpf).
  Right now there are no dep-8 tests. Though potentially it should be possible 
to create those, would this really add additional benefit beyond having 
upstream CI?
  A test build on hirsute was showing no warnings beyond lintian complaining 
about things which would be changed if we had delta (unstable as series for 
example). Otherwise was clean.

  [Dependencies]
  libc6: main
  libelf1: main
  zlib1g: main

  [Standards compliance]
  $ lintian --pedantic libbpf_0.3-2.dsc
  P: libbpf source: no-homepage-field
  P: libbpf source: silent-on-rules-requiring-root

  [Maintenance]
  As this is only taking out code from the kernel into a separate library 
package, the maintenance effort should be minimal. Packaging is done in Debian 
and is synced into Ubuntu (no delta).

  [Background information]
  A discourse about why this is packaged outside the kernel can be found at 
https://lwn.net/Articles/836911/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1910576/+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 1911836] Re: package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Raphael Dumas]

Haha yeah that fixed it. Thanks Seth!

I marked it private because way more info got uploaded than I was
expecting.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1911836

Title:
  package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Possibly related to https://bugs.launchpad.net/ubuntu/+bug/1911835

  These just happened during the same update cycle.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-62-generic 5.4.0-62.70
  ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
  Uname: Linux 5.4.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jan 14 21:19:12 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=b9d6e51c-6ef1-4b05-916a-17aa1a75141c
  InstallationDate: Installed on 2016-07-02 (1657 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 80K9
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-60-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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: grub-pc 2.04-1ubuntu26.7
  SourcePackage: initramfs-tools
  Title: package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to focal on 2020-12-06 (39 days ago)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: Lenovo
  dmi.bios.version: A9CN61WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Edge 15
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Edge 15
  dmi.modalias: 
dmi:bvnLenovo:bvrA9CN61WW:bd07/21/2015:svnLENOVO:pn80K9:pvrLenovoEdge15:rvnLENOVO:rnLenovoEdge15:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoEdge15:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80K9
  dmi.product.sku: LENOVO_MT_80K9_BU_idea_FM_Lenovo Edge 15
  dmi.product.version: Lenovo Edge 15
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1911836/+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 1911836] Re: package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Raphael Dumas]

Haha yeah that fixed it. Thanks Seth!

I marked it private because way more info got uploaded than I was
expecting.

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1911836/+attachment/5453184/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1911836

Title:
  package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Possibly related to https://bugs.launchpad.net/ubuntu/+bug/1911835

  These just happened during the same update cycle.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-62-generic 5.4.0-62.70
  ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
  Uname: Linux 5.4.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jan 14 21:19:12 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=b9d6e51c-6ef1-4b05-916a-17aa1a75141c
  InstallationDate: Installed on 2016-07-02 (1657 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 80K9
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-60-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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: grub-pc 2.04-1ubuntu26.7
  SourcePackage: initramfs-tools
  Title: package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to focal on 2020-12-06 (39 days ago)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: Lenovo
  dmi.bios.version: A9CN61WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Edge 15
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Edge 15
  dmi.modalias: 
dmi:bvnLenovo:bvrA9CN61WW:bd07/21/2015:svnLENOVO:pn80K9:pvrLenovoEdge15:rvnLENOVO:rnLenovoEdge15:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoEdge15:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80K9
  dmi.product.sku: LENOVO_MT_80K9_BU_idea_FM_Lenovo Edge 15
  dmi.product.version: Lenovo Edge 15
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1911836/+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 1911836] Re: package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Seth Arnold]

Hello, I think the core of your problem is this:

Error 24 : Write error : cannot write compressed block

Caused by a full /boot:

/dev/sda2  483946424596 34365  93% /boot


Truncate a few older files in /boot (start a shell via sudo -s, then find files 
with ls -l, then use `> vmlinux-whatever` to truncate files from an old kernel).

Once you've truncated a kernel and symbols file, you probably have
enough disk space free to run:

sudo apt install -f
sudo apt autoremove

Thanks

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1911836

Title:
  package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Possibly related to https://bugs.launchpad.net/ubuntu/+bug/1911835

  These just happened during the same update cycle.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-62-generic 5.4.0-62.70
  ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
  Uname: Linux 5.4.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jan 14 21:19:12 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=b9d6e51c-6ef1-4b05-916a-17aa1a75141c
  InstallationDate: Installed on 2016-07-02 (1657 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 80K9
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-60-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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: grub-pc 2.04-1ubuntu26.7
  SourcePackage: initramfs-tools
  Title: package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to focal on 2020-12-06 (39 days ago)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: Lenovo
  dmi.bios.version: A9CN61WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Edge 15
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Edge 15
  dmi.modalias: 
dmi:bvnLenovo:bvrA9CN61WW:bd07/21/2015:svnLENOVO:pn80K9:pvrLenovoEdge15:rvnLENOVO:rnLenovoEdge15:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoEdge15:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80K9
  dmi.product.sku: LENOVO_MT_80K9_BU_idea_FM_Lenovo Edge 15
  dmi.product.version: Lenovo Edge 15
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1911836/+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 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic

[Chris Guiver]

** Tags added: focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1911614

Title:
  Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of
  linux-generic

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Just as the title says, the 20.04 and 20.04.1 images use the HWE
  version of linux-generic resulting in upgrades to the 5.8 series
  kernel. This seems to effect Ubuntu only, or I should say I checked
  the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all
  correctly list linux-generic. Also HWE is not truly complete without
  the accompanying HWE Xstack.

  I checked all the documentation I could find and this was clearly not
  intentional. In fact the manifest for Ubuntu Focal Beta still used
  linux-generic, so this got messed up some time between April 3, 2020
  and April 23, 2020. Here's just one example of the documentation for
  kernel support in Focal LTS:

  https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle

  Installations performed with 20.04 and 20.04.1 media were supposed to
  remain on the 5.4 series kernel throughout Focal's 5 year lifespan as
  had been the case since HWE was introduced. The first step in fixing
  this needs to be stopping fresh installs of Focal using the 20.04 and
  20.04.1 media from immediately upgrading to the 5.8 series kernel.

  It might be a little tricky to revert users from 5.8 to 5.4, but there
  have been reports of breakage, particularly concerning Broadcom wifi
  drivers and some graphics problems. But the graphics problems could
  also be exacerbated by the lack of the matching HWE Xstack? At any
  rate it's a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+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 1911836] [NEW] package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Raphael Dumas]

*** This bug is a security vulnerability ***

Private security bug reported:

Possibly related to https://bugs.launchpad.net/ubuntu/+bug/1911835

These just happened during the same update cycle.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-62-generic 5.4.0-62.70
ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
Uname: Linux 5.4.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Jan 14 21:19:12 2021
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=b9d6e51c-6ef1-4b05-916a-17aa1a75141c
InstallationDate: Installed on 2016-07-02 (1657 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 80K9
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-60-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
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: grub-pc 2.04-1ubuntu26.7
SourcePackage: initramfs-tools
Title: package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to focal on 2020-12-06 (39 days ago)
dmi.bios.date: 07/21/2015
dmi.bios.vendor: Lenovo
dmi.bios.version: A9CN61WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo Edge 15
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Edge 15
dmi.modalias: 
dmi:bvnLenovo:bvrA9CN61WW:bd07/21/2015:svnLENOVO:pn80K9:pvrLenovoEdge15:rvnLENOVO:rnLenovoEdge15:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoEdge15:
dmi.product.family: IDEAPAD
dmi.product.name: 80K9
dmi.product.sku: LENOVO_MT_80K9_BU_idea_FM_Lenovo Edge 15
dmi.product.version: Lenovo Edge 15
dmi.sys.vendor: LENOVO

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

** Information type changed from Public to Private Security

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1911836

Title:
  package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Possibly related to https://bugs.launchpad.net/ubuntu/+bug/1911835

  These just happened during the same update cycle.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-62-generic 5.4.0-62.70
  ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
  Uname: Linux 5.4.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jan 14 21:19:12 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=b9d6e51c-6ef1-4b05-916a-17aa1a75141c
  InstallationDate: Installed on 2016-07-02 (1657 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 80K9
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-60-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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: grub-pc 2.04-1ubuntu26.7
  SourcePackage: initramfs-tools
  Title: package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to focal on 2020-12-06 (39 days ago)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: Lenovo
  dmi.bios.version: A9CN61WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Edge 15
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Edge 15
  dmi.modalias: 
dmi:bvnLenovo:bvrA9CN61WW:bd07/21/2015:svnLENOVO:pn80K9:pvrLenovoEdge15:rvnLENOVO:rnLenovoEdge15:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoEdge15:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80K9
  dmi.product.sku: LENOVO_MT_80K9_BU_idea_FM_Lenovo Edge 15
  dmi.product.version: 

[Touch-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic

[Erick Brunzell]

Unfortunately apport-collect just says "no additional info collected"
(see pic added). I presume because 'ubuntu-meta' is not an installed
package? I struggled a bit trying to decide what the best way was to
report a bug like this because it's not actually a bug in the kernel
itself, it's just that I believe the 5.8 series kernel should not be
installed without specific user action to do so.

That had been the case in the past. LTS installs using the original iso
or the first point release iso would remain on the original GA (General
Availability) throughout the duration of the 5 year support cycle. In
fact I see the HWE Wiki has been updated to say "The 20.04.2 and newer
point releases will ship with an updated kernel and X stack by default
for the desktop":

https://wiki.ubuntu.com/Kernel/LTSEnablementStack

And 20.04.2 is not due for release until early February. It's worth
mentioning that LTS point releases are frequently delayed by a week or
two if bugs are encountered. Anyway I would expect an installation
performed with 20.04.2 media to include the HWE kernel. You'll also
notice that they do say "kernel and X stack" and as mentioned above the
HWE X stack is not yet even in the repos!

I will probably be testing the 20.04.2 daily build very soon and I'll
then report a bug against 'linux-generic-hwe-20.04' making note that the
accompanying X stack is missing. And yes, this does effect only Ubuntu
Desktop because as mentioned above I checked some of the other flavors
manifests. Only the Ubuntu isos have the HWE version of kinux-generic
installed.

** Attachment added: "Screenshot from 2021-01-14 19-45-49.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+attachment/5453132/+files/Screenshot%20from%202021-01-14%2019-45-49.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1911614

Title:
  Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of
  linux-generic

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Just as the title says, the 20.04 and 20.04.1 images use the HWE
  version of linux-generic resulting in upgrades to the 5.8 series
  kernel. This seems to effect Ubuntu only, or I should say I checked
  the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all
  correctly list linux-generic. Also HWE is not truly complete without
  the accompanying HWE Xstack.

  I checked all the documentation I could find and this was clearly not
  intentional. In fact the manifest for Ubuntu Focal Beta still used
  linux-generic, so this got messed up some time between April 3, 2020
  and April 23, 2020. Here's just one example of the documentation for
  kernel support in Focal LTS:

  https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle

  Installations performed with 20.04 and 20.04.1 media were supposed to
  remain on the 5.4 series kernel throughout Focal's 5 year lifespan as
  had been the case since HWE was introduced. The first step in fixing
  this needs to be stopping fresh installs of Focal using the 20.04 and
  20.04.1 media from immediately upgrading to the 5.8 series kernel.

  It might be a little tricky to revert users from 5.8 to 5.4, but there
  have been reports of breakage, particularly concerning Broadcom wifi
  drivers and some graphics problems. But the graphics problems could
  also be exacerbated by the lack of the matching HWE Xstack? At any
  rate it's a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+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] Autopkgtest regression report (apt/2.0.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.0.4) for focal have finished 
running.
The following regressions have been reported in tests triggered by the package:

gcc-10/10.2.0-5ubuntu1~20.04 (amd64)


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/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:
  In Progress
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]
  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 

[Touch-packages] [Bug 1872200] Autopkgtest regression report (apt/2.0.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.0.4) for focal have finished 
running.
The following regressions have been reported in tests triggered by the package:

gcc-10/10.2.0-5ubuntu1~20.04 (amd64)


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/1872200

Title:
  apt does not accept globs and regexes in some cases

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Users can't use * wildcards anymore in focal, except by accident in apt list.

  For apt list, we now start restricting wildcard syntax to the same
  syntax install now accepts, and at the same time we remove the
  restrictions on which patterns are accepted (which only accepted
  patterns starting in ~ or ?), so !~napt now works, and does not
  accidentally match as a wildcard.

  
  [Test case]

  Test that * wildcards work for both install and list, and test that a
  ? wildcard does not.

  We included autopkgtests for those:

   BEGIN TESTS #

  # * wildcards should still work
  testsuccessequal "Listing...
  automatic1/now 1.0 i386 [installed,local]
  automatic2/now 1.0 i386 [installed,local]" apt list 'automatic*'

  testfailureequal "Reading package lists...
  Building dependency tree...
  Reading state information...
  Note, selecting 'automatic1' for glob 'automatic*'
  Note, selecting 'automatic2' for glob 'automatic*'
  automatic1 is already the newest version (1.0).
  automatic1 set to manually installed.
  automatic2 is already the newest version (1.0).
  automatic2 set to manually installed.
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   broken : Depends: does-not-exist but it is not installable
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution)." apt install -s 'automatic*'

  # other wildcards should fail

  testfailureequal "Listing...
  E: input:0-10: error: Expected pattern
 automatic?
 ^^" apt list 'automatic?'

  testfailureequal "Reading package lists...
  Building dependency tree...
  Reading state information...
  E: Unable to locate package automatic?" apt install -s 'automatic?'

  
   END TESTS #

  Also it might be worth checking that apt list !~napt works. This used
  to produce an empty list, as it was accidentally matched as a wildcard
  and produced no result - now it produces every package whose name does
  not contain "apt".

  
  [Regression potential]
  The changes only affect interactive users, as apt(8) is not stable for 
in-script use, hence they can fix up their command-line if it stops working for 
them (though, really, more should work now).

  No scripts will be broken :)

  [Squashed in changes]
  The SRU also fixes potential build failures by correctly prefxing nullptr_t 
with the std:: namespace, and includes updated Dutch documentation.

  [Original bug report]
  Observed with Ubuntu 20.04 Beta.

  apt remove 'mypackage*' does not remove all installed packages
  starting with “mypackage”.  Instead:

  $ sudo apt remove 'mypackage*'
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  E: Unable to locate package mypackage*

  However:

  $ sudo apt list --installed 'mypackage*'
  Listing... Done
  mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic]
  mypackage1/focal,now 0.3.2-5build1 amd64 [installed]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+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 1876495] Autopkgtest regression report (apt/2.0.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.0.4) for focal have finished 
running.
The following regressions have been reported in tests triggered by the package:

gcc-10/10.2.0-5ubuntu1~20.04 (amd64)


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/1876495

Title:
  bash-completion incorrectly shows source package names for APT

Status in apt package in Ubuntu:
  Fix Released
Status in bash-completion package in Ubuntu:
  Invalid
Status in apt source package in Focal:
  Fix Committed
Status in bash-completion source package in Focal:
  New
Status in apt source package in Groovy:
  Fix Committed
Status in bash-completion source package in Groovy:
  New
Status in apt source package in Hirsute:
  Fix Released
Status in bash-completion source package in Hirsute:
  Invalid

Bug description:
  [Impact]

  Source packages have been included in apt-cache pkgnames, and virtual
  packages have not been included in apt-cache pkgnames --all-names. The
  former leads to completions autocompleting to source package names
  where they only should complete to binaries.

  [Test case]
  An automated test case is included in the test suite

  test-ubuntu-bug-1876495-pkgnames-virtual

  It verifies that pkgnames does not return source package names, and
  that pkgnames --all-names does return source package names and virtual
  package names.

  [Where problems could occur]
  In the pkgnames command only. If there's a bug, it could exclude or include 
packages it should not.

  [Original bug report]
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal, enter one of the commands below

  2a. apt install brisk
  2b. apt source brisk-menu
  2c. apt-get install brisk
  2d. apt-get source brisk-menu
  2e. apt-cache policy brisk

  Expected results:
  * The bash-completion should not lead to package name as there are no binary 
packages named with starting part "brisk" (see 
https://packages.ubuntu.com/search?suite=all=names=brisk )

  Actual results:
  * all commands below get completed to the name of source package - in this 
example named "brisk-menu"
  (see 
https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames).
 This is absolutely unexpected, as user can not really install this package in 
binary form.

  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May  2 20:35:48 2020
  Dependencies:

  InstallationDate: Installed on 2020-04-22 (9 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876495/+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 1911676] Autopkgtest regression report (apt/2.0.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.0.4) for focal have finished 
running.
The following regressions have been reported in tests triggered by the package:

gcc-10/10.2.0-5ubuntu1~20.04 (amd64)


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/1911676

Title:
  Short pattern not terminated by  ~ or !

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  Short patterns like ~nfoo!~nbar or ~nfoo~nbar do not work correctly -
  they are treated as ?name(foo!~nbar) / ?name(foo~nbar) rather than
  ?name(foo)?not(?name(bar)) / ?name(foo)?name(bar)

  [Test Case]
  Unit tests have been added that are run during build and check they are 
parsed correctly

  +   EXPECT_PATTERN_EQ("~napt~nfoo", "?and(?name(apt),?name(foo))");
  +   EXPECT_PATTERN_EQ("~napt!~nfoo", "?and(?name(apt),?not(?name(foo)))");

  [Where problems could occur]
  Really just changing a string constant for this change in a function that 
parses of words, so well, the only problem arising could be that words inside 
patterns are recognized wrongly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1911676/+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 1911812] Re: package libssl1.1:amd64 1.1.1f-1ubuntu2.1 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: openssl (Ubuntu)
   Importance: Undecided => Low

** Changed in: openssl (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1911812

Title:
  package libssl1.1:amd64 1.1.1f-1ubuntu2.1 failed to install/upgrade:
  installed libssl1.1:amd64 package post-installation script subprocess
  returned error exit status 255

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  error at first updating

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libssl1.1:amd64 1.1.1f-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jan 14 18:19:52 2021
  ErrorMessage: installed libssl1.1:amd64 package post-installation script 
subprocess returned error exit status 255
  InstallationDate: Installed on 2021-01-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: openssl
  Title: package libssl1.1:amd64 1.1.1f-1ubuntu2.1 failed to install/upgrade: 
installed libssl1.1:amd64 package post-installation script subprocess returned 
error exit status 255
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1911812/+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 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

[Mauricio Faria de Oliveira]

** Patch added: "lp1908473_librelp_focal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1908473/+attachment/5453106/+files/lp1908473_librelp_focal.debdiff

** Description changed:

  [Impact]
  
  In recent versions of rsyslog and librelp, the imrelp module leaks file
  descriptors due to a bug where it does not correctly close sockets, and
  instead, leaves them in the CLOSE_WAIT state.
  
  This causes rsyslogd on busy servers to eventually hit the limit of
  maximum open files allowed, which locks rsyslogd up until it is
  restarted.
  
  A workaround is to restart rsyslogd every month or so to manually close
  all of the open sockets.
  
  Only users of the imrelp module are affected, and not rsyslog users in
  general.
  
  [Testcase]
  
  Install the rsyslog-relp module like so:
  
  $ sudo apt install rsyslog rsyslog-relp
  
  Next, generate a working directory, and make a config file that loads
  the relp module.
  
  $ sudo mkdir /workdir
  $ cat << EOF >> ./spool.conf
  \$LocalHostName spool
  \$AbortOnUncleanConfig on
  \$PreserveFQDN on
  
  global(
  workDirectory="/workdir"
  maxMessageSize="256k"
  )
  
  main_queue(queue.type="Direct")
  module(load="imrelp")
  input(
  type="imrelp"
  name="imrelp"
  port="601"
  ruleset="spool"
  MaxDataSize="256k"
  )
  
  ruleset(name="spool" queue.type="direct") {
  }
  
  # Just so rsyslog doesn't whine that we do not have outputs
  ruleset(name="noop" queue.type="direct") {
  action(
  type="omfile"
  name="omfile"
  file="/workdir/spool.log"
  )
  }
  EOF
  
  Verify that the config is valid, then start a rsyslog server.
  
  $ sudo rsyslogd -f ./spool.conf -N9
  $ sudo rsyslogd -f ./spool.conf -i /workdir/rsyslogd.pid
  
  Fetch the rsyslogd PID and check for open files.
  
  $ RLOGPID=$(cat /workdir/rsyslogd.pid)
  $ sudo ls -l /proc/$RLOGPID/fd
  total 0
  lr-x-- 1 root root 64 Dec 17 01:22 0 -> /dev/urandom
  lrwx-- 1 root root 64 Dec 17 01:22 1 -> 'socket:[41228]'
  lrwx-- 1 root root 64 Dec 17 01:22 3 -> 'socket:[41222]'
  lrwx-- 1 root root 64 Dec 17 01:22 4 -> 'socket:[41223]'
  lrwx-- 1 root root 64 Dec 17 01:22 7 -> 'anon_inode:[eventpoll]'
  
  We have 3 sockets open by default. Next, use netcat to open 100
  connections:
  
  $ for i in {1..100} ; do nc -z 127.0.0.1 601 ; done
  
  Now check for open file descriptors, and there will be an extra 100 sockets
  in the list:
  
  $ sudo ls -l /proc/$RLOGPID/fd
  
  https://paste.ubuntu.com/p/f6NQVNbZcR/
  
  We can check the state of these sockets with:
  
  $ ss -t
  
  https://paste.ubuntu.com/p/7Ts2FbxJrg/
  
  The listening sockets will be in CLOSE-WAIT, and the netcat sockets will
  be in FIN-WAIT-2.
  
  $ ss -t | grep CLOSE-WAIT | wc -l
  100
  
  If you install the test package available in the following ppa:
  
  https://launchpad.net/~mruffell/+archive/ubuntu/sf299578-test
  
  When you open connections with netcat, these will be closed properly,
  and the file descriptor leak will be fixed.
  
  [Where problems could occur]
  
  If a regression were to occur, it would be limited to users of the
  imrelp module, which is a part of the rsyslogd-relp package, and depends
  on librelp.
  
  rsyslog-relp is not part of a default installation of rsyslog, and is
  opt in by changing a configuration file to enable imrelp.
  
- The changes to rsyslog implement a testcase which exercises the
- problematic code to ensure things are working as expected, and should
- run during autopkgtest time.
+ The changes to rsyslog implement a testcase which exercises the problematic 
code to ensure things are working as expected; this
+ can be enabled manually on build, and has been verified to pass (#7).
  
  [Other]
  
  Upstream bug list:
  
  https://github.com/rsyslog/rsyslog/issues/4350
  https://github.com/rsyslog/rsyslog/issues/4005
  https://github.com/rsyslog/librelp/issues/188
  https://github.com/rsyslog/librelp/pull/193
  
  The following commits fix the problem:
  
  rsyslogd
  
  
  commit baee0bd5420649329793746f0daf87c4f59fe6a6
  Author: Andre lorbach 
  Date:   Thu Apr 9 13:00:35 2020 +0200
  Subject: testbench: Add test for imrelp to check broken session handling.
  Link: 
https://github.com/rsyslog/rsyslog/commit/baee0bd5420649329793746f0daf87c4f59fe6a6
  
  librelp
  ===
  
  commit 7907c9c57f6ed94c8ce5a4e63c3c4e019f71cff0
  Author: Andre lorbach 
  Date:   Mon May 11 14:59:55 2020 +0200
  Subject: fix memory leak on session break.
  Link: 
https://github.com/rsyslog/librelp/commit/7907c9c57f6ed94c8ce5a4e63c3c4e019f71cff0
  
  commit 4a6ad8637c244fd3a1caeb9a93950826f58e956a
  Author: Andre lorbach 
  Date:   Wed Apr 8 15:55:32 2020 +0200
  Subject: replsess: fix double free of sendbuf in some cases.
  Link: 
https://github.com/rsyslog/librelp/commit/4a6ad8637c244fd3a1caeb9a93950826f58e956a
  
  commit 3797944fb62273fa1164acd3104f0894b337c4d0
  Author: Ognyan Kulev 
  

[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

[Mauricio Faria de Oliveira]

** Patch added: "lp1908473_librelp_groovy.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1908473/+attachment/5453105/+files/lp1908473_librelp_groovy.debdiff

-- 
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/1908473

Title:
  rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
  leads to file descriptor leak

Status in librelp package in Ubuntu:
  Fix Released
Status in rsyslog package in Ubuntu:
  Fix Released
Status in librelp source package in Focal:
  In Progress
Status in rsyslog source package in Focal:
  Won't Fix
Status in librelp source package in Groovy:
  In Progress
Status in rsyslog source package in Groovy:
  Fix Released
Status in librelp source package in Hirsute:
  Fix Released
Status in rsyslog source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  In recent versions of rsyslog and librelp, the imrelp module leaks
  file descriptors due to a bug where it does not correctly close
  sockets, and instead, leaves them in the CLOSE_WAIT state.

  This causes rsyslogd on busy servers to eventually hit the limit of
  maximum open files allowed, which locks rsyslogd up until it is
  restarted.

  A workaround is to restart rsyslogd every month or so to manually
  close all of the open sockets.

  Only users of the imrelp module are affected, and not rsyslog users in
  general.

  [Testcase]

  Install the rsyslog-relp module like so:

  $ sudo apt install rsyslog rsyslog-relp

  Next, generate a working directory, and make a config file that loads
  the relp module.

  $ sudo mkdir /workdir
  $ cat << EOF >> ./spool.conf
  \$LocalHostName spool
  \$AbortOnUncleanConfig on
  \$PreserveFQDN on

  global(
  workDirectory="/workdir"
  maxMessageSize="256k"
  )

  main_queue(queue.type="Direct")
  module(load="imrelp")
  input(
  type="imrelp"
  name="imrelp"
  port="601"
  ruleset="spool"
  MaxDataSize="256k"
  )

  ruleset(name="spool" queue.type="direct") {
  }

  # Just so rsyslog doesn't whine that we do not have outputs
  ruleset(name="noop" queue.type="direct") {
  action(
  type="omfile"
  name="omfile"
  file="/workdir/spool.log"
  )
  }
  EOF

  Verify that the config is valid, then start a rsyslog server.

  $ sudo rsyslogd -f ./spool.conf -N9
  $ sudo rsyslogd -f ./spool.conf -i /workdir/rsyslogd.pid

  Fetch the rsyslogd PID and check for open files.

  $ RLOGPID=$(cat /workdir/rsyslogd.pid)
  $ sudo ls -l /proc/$RLOGPID/fd
  total 0
  lr-x-- 1 root root 64 Dec 17 01:22 0 -> /dev/urandom
  lrwx-- 1 root root 64 Dec 17 01:22 1 -> 'socket:[41228]'
  lrwx-- 1 root root 64 Dec 17 01:22 3 -> 'socket:[41222]'
  lrwx-- 1 root root 64 Dec 17 01:22 4 -> 'socket:[41223]'
  lrwx-- 1 root root 64 Dec 17 01:22 7 -> 'anon_inode:[eventpoll]'

  We have 3 sockets open by default. Next, use netcat to open 100
  connections:

  $ for i in {1..100} ; do nc -z 127.0.0.1 601 ; done

  Now check for open file descriptors, and there will be an extra 100 sockets
  in the list:

  $ sudo ls -l /proc/$RLOGPID/fd

  https://paste.ubuntu.com/p/f6NQVNbZcR/

  We can check the state of these sockets with:

  $ ss -t

  https://paste.ubuntu.com/p/7Ts2FbxJrg/

  The listening sockets will be in CLOSE-WAIT, and the netcat sockets
  will be in FIN-WAIT-2.

  $ ss -t | grep CLOSE-WAIT | wc -l
  100

  If you install the test package available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf299578-test

  When you open connections with netcat, these will be closed properly,
  and the file descriptor leak will be fixed.

  [Where problems could occur]

  If a regression were to occur, it would be limited to users of the
  imrelp module, which is a part of the rsyslogd-relp package, and
  depends on librelp.

  rsyslog-relp is not part of a default installation of rsyslog, and is
  opt in by changing a configuration file to enable imrelp.

  The changes to rsyslog implement a testcase which exercises the problematic 
code to ensure things are working as expected; this
  can be enabled manually on build, and has been verified to pass (#7).

  [Other]

  Upstream bug list:

  https://github.com/rsyslog/rsyslog/issues/4350
  https://github.com/rsyslog/rsyslog/issues/4005
  https://github.com/rsyslog/librelp/issues/188
  https://github.com/rsyslog/librelp/pull/193

  The following commits fix the problem:

  rsyslogd
  

  commit baee0bd5420649329793746f0daf87c4f59fe6a6
  Author: Andre lorbach 
  Date:   Thu Apr 9 13:00:35 2020 +0200
  Subject: testbench: Add test for imrelp to check broken session handling.
  Link: 
https://github.com/rsyslog/rsyslog/commit/baee0bd5420649329793746f0daf87c4f59fe6a6

  librelp
  ===

  commit 7907c9c57f6ed94c8ce5a4e63c3c4e019f71cff0
  Author: Andre lorbach 
  Date:   Mon May 11 14:59:55 2020 +0200
  

[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

[Mauricio Faria de Oliveira]

Matthew, thanks for the great work in this bug and patches.

Uploaded to Groovy and Focal w/ trivial changes; attached.

cheers,
Mauricio

...

debdiffs:

I've modified the patch files slightly, as we discussed;
- keep the commit messages;
- use its/patch headers for DEP3, adding Origin: / Bug-Ubuntu:
- added prefix keywords upstream/backport to Origin;, 
  and documented changes done to backport patches 2,3.

upstream:

- no additional changes upstream that further change/fix these patches.

downstream:

- changelog looks good.
- version numbers and upgrade path look good.
- no other current uploads/versions in -proposed
- no block-proposed[-] tag

build:

The packages built successfully on all architectures on
a PPA with -proposed enabled (as on build environments.)

tests:

I've done testing with your steps (thanks!) and the new test introduced in 
patch 2, manually.
Unfortunately it doesn't run at build time as the package --disable-valgrind in 
debian/rules.

> PASS: basic-sessionbreak-vg.sh # --enable-valgrind in d/rules; install
valgrind/libtool; chmod +x

And also we don't have autopkgtests on librelp [1] nor rsyslog [2]
(single reverse dep for librelp0).

So the two tests above seem to be really the only tests for this. 
All good as both have positive results!

...

$ grep Package: debian/control
Package: librelp0
Package: librelp-dev

$ apt rdepends librelp0
librelp0
Reverse Depends:
  Depends: librelp-dev (= 1.5.0-1ubuntu2)
  Depends: rsyslog-relp (>= 1.5.0)
  Depends: rsyslog-relp (>= 1.4.0)

ubuntu@librelp-f:~/librelp-1.5.0$ apt rdepends librelp-dev
librelp-dev
Reverse Depends:

$ apt-cache show rsyslog-relp | grep Source:
Source: rsyslog
Source: rsyslog

[1] https://autopkgtest.ubuntu.com/packages/librelp
[1] https://autopkgtest.ubuntu.com/packages/rsyslog

-- 
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/1908473

Title:
  rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
  leads to file descriptor leak

Status in librelp package in Ubuntu:
  Fix Released
Status in rsyslog package in Ubuntu:
  Fix Released
Status in librelp source package in Focal:
  In Progress
Status in rsyslog source package in Focal:
  Won't Fix
Status in librelp source package in Groovy:
  In Progress
Status in rsyslog source package in Groovy:
  Fix Released
Status in librelp source package in Hirsute:
  Fix Released
Status in rsyslog source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  In recent versions of rsyslog and librelp, the imrelp module leaks
  file descriptors due to a bug where it does not correctly close
  sockets, and instead, leaves them in the CLOSE_WAIT state.

  This causes rsyslogd on busy servers to eventually hit the limit of
  maximum open files allowed, which locks rsyslogd up until it is
  restarted.

  A workaround is to restart rsyslogd every month or so to manually
  close all of the open sockets.

  Only users of the imrelp module are affected, and not rsyslog users in
  general.

  [Testcase]

  Install the rsyslog-relp module like so:

  $ sudo apt install rsyslog rsyslog-relp

  Next, generate a working directory, and make a config file that loads
  the relp module.

  $ sudo mkdir /workdir
  $ cat << EOF >> ./spool.conf
  \$LocalHostName spool
  \$AbortOnUncleanConfig on
  \$PreserveFQDN on

  global(
  workDirectory="/workdir"
  maxMessageSize="256k"
  )

  main_queue(queue.type="Direct")
  module(load="imrelp")
  input(
  type="imrelp"
  name="imrelp"
  port="601"
  ruleset="spool"
  MaxDataSize="256k"
  )

  ruleset(name="spool" queue.type="direct") {
  }

  # Just so rsyslog doesn't whine that we do not have outputs
  ruleset(name="noop" queue.type="direct") {
  action(
  type="omfile"
  name="omfile"
  file="/workdir/spool.log"
  )
  }
  EOF

  Verify that the config is valid, then start a rsyslog server.

  $ sudo rsyslogd -f ./spool.conf -N9
  $ sudo rsyslogd -f ./spool.conf -i /workdir/rsyslogd.pid

  Fetch the rsyslogd PID and check for open files.

  $ RLOGPID=$(cat /workdir/rsyslogd.pid)
  $ sudo ls -l /proc/$RLOGPID/fd
  total 0
  lr-x-- 1 root root 64 Dec 17 01:22 0 -> /dev/urandom
  lrwx-- 1 root root 64 Dec 17 01:22 1 -> 'socket:[41228]'
  lrwx-- 1 root root 64 Dec 17 01:22 3 -> 'socket:[41222]'
  lrwx-- 1 root root 64 Dec 17 01:22 4 -> 'socket:[41223]'
  lrwx-- 1 root root 64 Dec 17 01:22 7 -> 'anon_inode:[eventpoll]'

  We have 3 sockets open by default. Next, use netcat to open 100
  connections:

  $ for i in {1..100} ; do nc -z 127.0.0.1 601 ; done

  Now check for open file descriptors, and there will be an extra 100 sockets
  in the list:

  $ sudo ls -l /proc/$RLOGPID/fd

  https://paste.ubuntu.com/p/f6NQVNbZcR/

  We can check the state of these sockets with:

  $ ss -t

  https://paste.ubuntu.com/p/7Ts2FbxJrg/

  The 

[Touch-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)

[Hadmut Danisch]

Pretty good hint, interesting.

However, the ATEM is definitely able to take audio in on all four HDMI
ports, since it has level indicators and buttons to turn it on and off
(and AFV=Audio follows Video) and adjust the level on all four HDMI
ports.

And I do have a camera with a builtin Mic (GoPro 4) on HDMI 2, which
perfectly takes the Audio from the camera mic.

So there must be some difference in the HDMI signal coming from a camera
(I had a Sony A6300, a Z-Cam e2c, and a GoPro 4 connected, all passing
audio properly to the ATEM) and the HDMI signal coming from a
Linux/Ubuntu notebook.

The cheap chinese LCD screen I used for testing doesn't care about the
difference, it just plays the sound, while the ATEM obviously bothers
about that difference, but, as Uldis figured out, only on Ports 2,3,4.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1910537

Title:
  HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video
  mixer)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is a complicated thing. I have a very specific problem with audio
  output on HDMI.

  I want to use an older notebook with Lubuntu 20.04 as a video source
  for libreoffice slides, videos etc. to feed them over HDMI into a
  Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input.
  Configured on the desktop just like a second screen or beamer.

  Video works well and rock-stable, no problem at all.

  But not audio.

  Although I carefully configured audio with pavucontrol to be directed
  to the HDMI output, the ATEM switcher does not recognize it as an
  audio source (like when connecting a digital camera) and does not
  receive or indicate any audio input.

  Note:

  But when I use the very same computer, same HDMI cable, same video
  with a cheap chinese portable LCD screen with speakers (i.e. pull the
  cable from the ATEM and plug it into the screen) it immediately starts
  playing both video and audio. So there is evidence that the ubuntu
  notebook definitely passes it's sound to HDMI and there's really an
  audio signal on the HDMI.

  I've opened a bug at Blackmagic Design, and got their reply that they
  can't help and have never heard of such a problem before. Their guess
  is that the linux notebook is not setting EDID configuration correctly
  and thus not recognized by the ATEM, while the cheap LCD screen
  propably does not care about EDID and just plays everything, therefore
  a wrong EDID information would not matter.

  Although I have decades of experience with Linux, I am not too
  familiar with details of HDMI and the internals of the X11 driver, so
  I'm not sure where to start debugging, not even, whether this is a
  problem of Xorg/X11 or pulseaudio.


  I've checked this with another notebook with much more recent (intel)
  hardware, which offers dozens of HDMI audio options in the pavucontrol
  selection menu, but same problem: Video works, but the ATEM does not
  recognize it as a audio source.

  
  Blackmagic Design (they're good in Windows and MacOS, but not Linux) 
recommended to use an edid manager, whatever this means.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Jan  7 13:16:26 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0742]
  InstallationDate: Installed on 2020-05-16 (235 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer AO756
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet 
cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
 root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff 
resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7
  SourcePackage: xorg
  

[Touch-packages] [Bug 1871593] Re: User receives prompt on login: "Authentication is required to create a color managed device"

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: colord (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/1871593

Title:
  User receives prompt on login: "Authentication is required to create a
  color managed device"

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  This concerns colord 1.4.4-2 in Ubuntu focal. (xiccd 0.3.0-1 may also
  be relevant.)

  I log into the Xfce desktop environment, and immediately see an
  "Authenticate" window pop up:

  Authentication is required to create a color managed device

  Password for root: 

  Action: org.freedesktop.color-manager.create-device
  Vendor: System Color Manager

  I see this in syslog:

  Apr  8 05:38:30 test-ubuntu64 dbus-daemon[573]: [system]
  Activating via systemd: service name='org.freedesktop.ColorManager'
  unit='colord.service' requested by ':1.35' (uid=1000 pid=1475
  comm="xiccd " label="unconfined")

  This prompt is confusing to ordinary users, and I do not understand
  why it should even be necessary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1871593/+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 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)

[Uldis Kalniņš]

I have same device ATEM Mini Pro ISO and Dell Vostro 3450.
I can confirm, that bug exists and is possible to grab sound from only first 
port.

Actually all ports on ATEM HDMI grabber are NOT same. HDMI1 is using different 
hardware than all others and is accepting sound from my computer.
If I'm using HDMI2,3,4 port - then yes, no sound.

To help debug problem, here is ATEM Mini Pro ISO teardown report with
chip ID's for all ports - https://wphost.spider-e.com/?p=940


And here EDID report with connected HDMI1 and HDMI2:

//HDMI1
sudo get-edid -b 5 | edid-decode
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
Only trying 5 as per your request.
256-byte EDID successfully retrieved from i2c bus 5
Looks like i2c was successful. Have a good day.
edid-decode (hex):

00 ff ff ff ff ff ff 00 23 01 00 00 01 00 00 00 
26 10 01 03 80 47 28 96 0a da ff a3 58 4a a2 29 
17 49 4b 00 00 00 01 01 01 01 01 01 01 01 01 01 
01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c 
45 00 c4 8e 21 00 00 1e 02 3a 80 d0 72 38 2d 40 
58 2c 45 00 c4 8e 21 00 00 1e 00 00 00 fc 00 42 
4d 44 20 48 44 4d 49 0a 20 20 20 20 00 00 00 fd 
00 32 3c 1f 44 08 00 0a 20 20 20 20 20 20 01 f7 

02 03 1f 54 49 85 84 94 93 a0 a1 a2 9f 90 23 09 
04 07 83 01 00 00 68 03 0c 00 10 00 00 1e 00 01 
1d 00 72 51 d0 1e 20 6e 28 55 00 c4 8e 21 00 00 
1e 01 1d 00 bc 52 d0 1e 20 b8 28 55 40 c4 8e 21 
00 00 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f2 



EDID version: 1.3
Manufacturer: HXA Model 0 Serial Number 1
Made in week 38 of 2006
Digital display
Maximum image size: 71 cm x 40 cm
Gamma: 2.50
RGB color display
First detailed timing is preferred timing
Color Characteristics
  Red:   0.6396, 0.3447
  Green: 0.2910, 0.6347
  Blue:  0.1630, 0.0927
  White: 0.2880, 0.2958
Established Timings I & II: none
Standard Timings: none
Detailed mode: Clock 148.500 MHz, 708 mm x 398 mm
   1920 2008 2052 2200 ( 88  44 148)
   1080 1084 1089 1125 (  4   5  36)
   +hsync +vsync
   VertFreq: 60.000 Hz, HorFreq: 67.500 kHz
Detailed mode: Clock 148.500 MHz, 708 mm x 398 mm
   1920 2008 2052 2640 ( 88  44 588)
   1080 1084 1089 1125 (  4   5  36)
   +hsync +vsync
   VertFreq: 50.000 Hz, HorFreq: 56.250 kHz
Display Product Name: BMD HDMI
Display Range Limits
  Monitor ranges (GTF): 50-60 Hz V, 31-68 kHz H, max dotclock 80 MHz
Has 1 extension block
Checksum: 0xf7



CTA-861 Extension Block Revision 3
Basic audio support
Supports YCbCr 4:2:2
4 native detailed modes
27 bytes of CTA data blocks
  Video Data Block
 1920x1080i  60.000 Hz  16:933.750 kHz  74.250 MHz (VIC   5, native)
 1280x72060.000 Hz  16:945.000 kHz  74.250 MHz (VIC   4, native)
 1920x1080i  50.000 Hz  16:928.125 kHz  74.250 MHz (VIC  20, native)
 1280x72050.000 Hz  16:937.500 kHz  74.250 MHz (VIC  19, native)
 1920x1080   24.000 Hz  16:927.000 kHz  74.250 MHz (VIC  32, native)
 1920x1080   25.000 Hz  16:928.125 kHz  74.250 MHz (VIC  33, native)
 1920x1080   30.000 Hz  16:933.750 kHz  74.250 MHz (VIC  34, native)
 1920x1080   50.000 Hz  16:956.250 kHz 148.500 MHz (VIC  31, native)
 1920x1080   60.000 Hz  16:967.500 kHz 148.500 MHz (VIC  16, native)
  Audio Data Block
Linear PCM, max channels 2
  Supported sample rates (kHz): 48
  Supported sample sizes (bits): 24 20 16
  Speaker Allocation Data Block
Speaker map:
  FL/FR - Front Left/Right
  Vendor-Specific Data Block, OUI 0x000c03 (HDMI)
Source physical address 1.0.0.0
Maximum TMDS clock: 150 MHz
Detailed mode: Clock 74.250 MHz, 708 mm x 398 mm
   1280 1390 1430 1650 (110  40 220)
720  725  730  750 (  5   5  20)
   +hsync +vsync
   VertFreq: 60.000 Hz, HorFreq: 45.000 kHz
Detailed mode: Clock 74.250 MHz, 708 mm x 398 mm
   1280 1720 1760 1980 (440  40 220)
720  725  730  750 (  5   5  20)
   +hsync +vsync
   VertFreq: 50.000 Hz, HorFreq: 37.500 kHz
Checksum: 0xf2

//HDMI2
sudo get-edid -b 5 | edid-decode
5
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
Only trying 5 as per your request.
256-byte EDID successfully retrieved from i2c bus 5
Looks like i2c was successful. Have a good day.
edid-decode (hex):

00 ff ff ff ff ff ff 00 23 01 00 00 01 00 00 00 
26 10 01 03 80 47 28 96 0a da ff a3 58 4a a2 29 
17 49 4b 00 00 00 01 01 01 01 01 01 01 01 01 01 
01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c 
45 00 c4 8e 21 00 00 1e 02 3a 80 d0 72 38 2d 40 
58 2c 45 00 c4 8e 21 00 00 1e 00 00 00 fc 00 42 
4d 44 20 48 44 4d 49 0a 20 20 20 20 00 00 00 fd 
00 32 3c 1f 44 08 00 0a 20 20 20 20 20 20 01 f7 

02 03 1f 54 49 85 84 94 93 a0 

[Touch-packages] [Bug 1911812] Re: package libssl1.1:amd64 1.1.1f-1ubuntu2.1 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1911812

Title:
  package libssl1.1:amd64 1.1.1f-1ubuntu2.1 failed to install/upgrade:
  installed libssl1.1:amd64 package post-installation script subprocess
  returned error exit status 255

Status in openssl package in Ubuntu:
  New

Bug description:
  error at first updating

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libssl1.1:amd64 1.1.1f-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jan 14 18:19:52 2021
  ErrorMessage: installed libssl1.1:amd64 package post-installation script 
subprocess returned error exit status 255
  InstallationDate: Installed on 2021-01-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: openssl
  Title: package libssl1.1:amd64 1.1.1f-1ubuntu2.1 failed to install/upgrade: 
installed libssl1.1:amd64 package post-installation script subprocess returned 
error exit status 255
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1911812/+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 1911812] [NEW] package libssl1.1:amd64 1.1.1f-1ubuntu2.1 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit stat

[Mauro Vanzelotti]

Public bug reported:

error at first updating

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libssl1.1:amd64 1.1.1f-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Jan 14 18:19:52 2021
ErrorMessage: installed libssl1.1:amd64 package post-installation script 
subprocess returned error exit status 255
InstallationDate: Installed on 2021-01-14 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.2
SourcePackage: openssl
Title: package libssl1.1:amd64 1.1.1f-1ubuntu2.1 failed to install/upgrade: 
installed libssl1.1:amd64 package post-installation script subprocess returned 
error exit status 255
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openssl (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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1911812

Title:
  package libssl1.1:amd64 1.1.1f-1ubuntu2.1 failed to install/upgrade:
  installed libssl1.1:amd64 package post-installation script subprocess
  returned error exit status 255

Status in openssl package in Ubuntu:
  New

Bug description:
  error at first updating

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libssl1.1:amd64 1.1.1f-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jan 14 18:19:52 2021
  ErrorMessage: installed libssl1.1:amd64 package post-installation script 
subprocess returned error exit status 255
  InstallationDate: Installed on 2021-01-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: openssl
  Title: package libssl1.1:amd64 1.1.1f-1ubuntu2.1 failed to install/upgrade: 
installed libssl1.1:amd64 package post-installation script subprocess returned 
error exit status 255
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1911812/+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 1876495] Autopkgtest regression report (apt/2.1.10ubuntu0.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.1.10ubuntu0.2) for groovy have 
finished running.
The following regressions have been reported in tests triggered by the package:

reprotest/0.7.15 (amd64, arm64, s390x)


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/1876495

Title:
  bash-completion incorrectly shows source package names for APT

Status in apt package in Ubuntu:
  Fix Released
Status in bash-completion package in Ubuntu:
  Invalid
Status in apt source package in Focal:
  Fix Committed
Status in bash-completion source package in Focal:
  New
Status in apt source package in Groovy:
  Fix Committed
Status in bash-completion source package in Groovy:
  New
Status in apt source package in Hirsute:
  Fix Released
Status in bash-completion source package in Hirsute:
  Invalid

Bug description:
  [Impact]

  Source packages have been included in apt-cache pkgnames, and virtual
  packages have not been included in apt-cache pkgnames --all-names. The
  former leads to completions autocompleting to source package names
  where they only should complete to binaries.

  [Test case]
  An automated test case is included in the test suite

  test-ubuntu-bug-1876495-pkgnames-virtual

  It verifies that pkgnames does not return source package names, and
  that pkgnames --all-names does return source package names and virtual
  package names.

  [Where problems could occur]
  In the pkgnames command only. If there's a bug, it could exclude or include 
packages it should not.

  [Original bug report]
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal, enter one of the commands below

  2a. apt install brisk
  2b. apt source brisk-menu
  2c. apt-get install brisk
  2d. apt-get source brisk-menu
  2e. apt-cache policy brisk

  Expected results:
  * The bash-completion should not lead to package name as there are no binary 
packages named with starting part "brisk" (see 
https://packages.ubuntu.com/search?suite=all=names=brisk )

  Actual results:
  * all commands below get completed to the name of source package - in this 
example named "brisk-menu"
  (see 
https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames).
 This is absolutely unexpected, as user can not really install this package in 
binary form.

  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May  2 20:35:48 2020
  Dependencies:

  InstallationDate: Installed on 2020-04-22 (9 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876495/+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] Autopkgtest regression report (apt/2.1.10ubuntu0.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.1.10ubuntu0.2) for groovy have 
finished running.
The following regressions have been reported in tests triggered by the package:

reprotest/0.7.15 (amd64, arm64, s390x)


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/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:
  In Progress
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]
  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 

[Touch-packages] [Bug 1911676] Autopkgtest regression report (apt/2.1.10ubuntu0.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.1.10ubuntu0.2) for groovy have 
finished running.
The following regressions have been reported in tests triggered by the package:

reprotest/0.7.15 (amd64, arm64, s390x)


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/1911676

Title:
  Short pattern not terminated by  ~ or !

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  Short patterns like ~nfoo!~nbar or ~nfoo~nbar do not work correctly -
  they are treated as ?name(foo!~nbar) / ?name(foo~nbar) rather than
  ?name(foo)?not(?name(bar)) / ?name(foo)?name(bar)

  [Test Case]
  Unit tests have been added that are run during build and check they are 
parsed correctly

  +   EXPECT_PATTERN_EQ("~napt~nfoo", "?and(?name(apt),?name(foo))");
  +   EXPECT_PATTERN_EQ("~napt!~nfoo", "?and(?name(apt),?not(?name(foo)))");

  [Where problems could occur]
  Really just changing a string constant for this change in a function that 
parses of words, so well, the only problem arising could be that words inside 
patterns are recognized wrongly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1911676/+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 1911789] Re: package linux-image-5.8.0-38-generic 5.8.0-38.43~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1911789

Title:
  package linux-image-5.8.0-38-generic 5.8.0-38.43~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Upon upgrading the following error has been observed. I am not sure
  what caused this error. So i am attaching the whole list of things
  happened just before the error observed.

  lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  $ sudo apt upgrade

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
linux-headers-5.8.0-38-generic linux-hwe-5.8-headers-5.8.0-38 
linux-image-5.8.0-38-generic linux-modules-5.8.0-38-generic 
linux-modules-extra-5.8.0-38-generic
  The following packages will be upgraded:
linux-generic-hwe-20.04 linux-headers-generic-hwe-20.04 
linux-image-generic-hwe-20.04 linux-libc-dev
  4 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
  Need to get 78.4 MB of archives.
  After this operation, 372 MB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-modules-5.8.0-38-generic amd64 5.8.0-38.43~20.04.1 [15.0 MB]
  Get:2 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-image-5.8.0-38-generic amd64 5.8.0-38.43~20.04.1 [9,500 kB]   
 
  Get:3 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-modules-extra-5.8.0-38-generic amd64 5.8.0-38.43~20.04.1 [40.1 MB]
 
  Get:4 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-generic-hwe-20.04 amd64 5.8.0.38.43~20.04.23 [1,932 B]
 
  Get:5 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-image-generic-hwe-20.04 amd64 5.8.0.38.43~20.04.23 [2,624 B]  
 
  Get:6 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-hwe-5.8-headers-5.8.0-38 all 5.8.0-38.43~20.04.1 [11.3 MB]
 
  Get:7 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-headers-5.8.0-38-generic amd64 5.8.0-38.43~20.04.1 [1,237 kB] 
 
  Get:8 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-headers-generic-hwe-20.04 amd64 5.8.0.38.43~20.04.23 [2,516 B]
 
  Get:9 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-libc-dev amd64 5.4.0-62.70 [1,116 kB] 
 
  Fetched 78.4 MB in 2min 19s (564 kB/s)

   
  Selecting previously unselected package linux-modules-5.8.0-38-generic.
  (Reading database ... 239086 files and directories currently installed.)
  Preparing to unpack 
.../0-linux-modules-5.8.0-38-generic_5.8.0-38.43~20.04.1_amd64.deb ...
  Unpacking linux-modules-5.8.0-38-generic (5.8.0-38.43~20.04.1) ...
  Selecting previously unselected package linux-image-5.8.0-38-generic.
  Preparing to unpack 
.../1-linux-image-5.8.0-38-generic_5.8.0-38.43~20.04.1_amd64.deb ...
  Unpacking linux-image-5.8.0-38-generic (5.8.0-38.43~20.04.1) ...
  Selecting previously unselected package linux-modules-extra-5.8.0-38-generic.
  Preparing to unpack 
.../2-linux-modules-extra-5.8.0-38-generic_5.8.0-38.43~20.04.1_amd64.deb ...
  Unpacking 

[Touch-packages] [Bug 1911802] [NEW] Video glitches playing hardware accelerated video through VAAPI

[Ben64]

Public bug reported:

Same issue as the post here describes:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3681

The video is scaled unevenly in the vertical axis, with a black bar
appearing in the bottom of the video window for a few frames. It happens
seemingly on all videos able to be hardware decoded, upon starting the
video and upon seeking.

The regression happened somewhere between 20.0.8-0ubuntu1~20.04.1 and
20.2.6-0ubuntu0.20.04.1 but apparently has been fixed in mesa 20.3

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: regression-update

** Tags added: regression-update

-- 
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/1911802

Title:
  Video glitches playing hardware accelerated video through VAAPI

Status in mesa package in Ubuntu:
  New

Bug description:
  Same issue as the post here describes:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3681

  The video is scaled unevenly in the vertical axis, with a black bar
  appearing in the bottom of the video window for a few frames. It
  happens seemingly on all videos able to be hardware decoded, upon
  starting the video and upon seeking.

  The regression happened somewhere between 20.0.8-0ubuntu1~20.04.1 and
  20.2.6-0ubuntu0.20.04.1 but apparently has been fixed in mesa 20.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1911802/+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 1848330] Re: Installing auditd sometimes fails in post-inst

[Andreas Hasenack]

I'm going over the DEP8 failures

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
https://bugs.launchpad.net/bugs/1848330

Title:
  Installing auditd sometimes fails in post-inst

Status in audit package in Ubuntu:
  Fix Released
Status in audit source package in Bionic:
  Fix Committed
Status in audit package in Debian:
  New

Bug description:
  [Impact]

  Sometimes, auditd will get stuck when starting up, causing systemd to
  kill it after a while since it (systemd) never got the start
  notification.

  Upstream troubleshooted this to be caused by calling a syslog()
  function inside a signal handler.

  [Test Case]
  There is no reliable test case to reproduce the bug, other than trying the 
fixed packages on an affected system where the hang occurs more frequently.

  Basically:
  sudo systemctl stop auditd
  sudo systemctl start auditd

  should work reliably. Do not run that in a tight loop, however, as
  that will trigger a it's-restarting-too-frequently failure.

  [Where problems could occur]
  - if auditd fails to start, then the first fallback is syslog, and if that is 
not picking up the audit messages, the last resort is the kernel buffer, which 
can fill up. In the case it fills up, audit logs will be lost.

  - it's possible to configure the audit system to panic() the machine
  if audit messages are lost or otherwise not able to be recorded
  (auditctl -f 2; default is 1 which is printk())

  - the update restarts auditd as expected. Misconfiguration on very
  very busy systems could mean that audit logs would be lost during the
  brief moment the service is restarted. If that's the case, this update
  would just be one more way to trigger it, but not be the root cause of
  the problem

  - similarly, as is usual with updates that restart services, it's
  possible than an incorrect configuration for auditd is present, but
  was never loaded before. The restart will load the config, and will
  fail in such a case.

  - this update removes a logging statement that occurs during startup:

  ("dispatcher %d reaped", pid)

  It's unlikely, but possible, that some monitoring software could be
  looking for that message in the logs. It won't be there anymore after
  this update.

  [Other Info]
  The patch is committed upstream and part of the 2.8.5 release, which is 
present in Focal and later.
  The real fix for this bug is just dropping the audit_msg() call in the signal 
handler code. But the original reporter of the bug, who is also who came up 
with the fix (see https://bugzilla.redhat.com/show_bug.cgi?id=1587995#c4) 
stated that with the 3 changes in the patch the startup hang didn't happen to 
him anymore. Since this bug is difficult to reproduce elsewhere (either you 
have it, or you don't), I chose to keep the 3 changes instead of just the 
removal of the audit_msg() call.

  [Original Description]

  This happens sometimes when installing auditd on Ubuntu 18.04.2, most
  installations work successfully, though. Re-running the install also
  fixes the issue, but the failure breaks our automation. The log from
  the failure looks like this:

  # apt install auditd
  ...
  Setting up auditd (1:2.8.2-1ubuntu1) ...
  Created symlink /etc/systemd/system/multi-user.target.wants/auditd.service → 
/lib/systemd/system/auditd.service.
  Job for auditd.service failed because a timeout was exceeded.
  See "systemctl status auditd.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript auditd, action "start" failed.
  ● auditd.service - Security Auditing Service
     Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: enabled)
     Active: failed (Result: timeout) since Tue 2019-09-17 18:43:06 UTC; 11ms 
ago
   Docs: man:auditd(8)
     https://github.com/linux-audit/audit-documentation
    Process: 9702 ExecStart=/sbin/auditd (code=killed, signal=KILL)

  Sep 17 18:40:06 compute-node21 systemd[1]: Starting Security Auditing 
Service...
  Sep 17 18:40:06 compute-node21 auditd[9703]: Started dispatcher: 
/sbin/audispd pid: 9705
  Sep 17 18:40:06 compute-node21 audispd[9705]: No plugins found, exiting
  Sep 17 18:41:36 compute-node21 systemd[1]: auditd.service: Start operation 
timed out. Terminating.
  Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: State 
'stop-sigterm' timed out. Killing.
  Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: Killing process 
9702 (auditd) with signal SIGKILL.
  Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: Killing process 
9703 (auditd) with signal SIGKILL.
  Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: Control process 
exited, code=killed status=9
  Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: Failed with result 
'timeout'.
  Sep 17 18:43:06 compute-node21 systemd[1]: Failed to start Security Auditing 
Service.
  dpkg: error processing package auditd (--configure):

[Touch-packages] [Bug 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8

[Dan Streetman]

The test-cap-list test no longer fails when running the autopkgtest suite with 
5.8 kernel:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20210114_030125_af0b9@/log.gz

that verifies for focal. As mentioned in the description [scope], the
test case fix was backported there to prevent build failures if the lp
build farm ever updates to the 5.8 kernel, but since that situation
isn't trivial to reproduce (and since this is a testcase only fix and is
verified above in focal), i'm using the focal verification to assume
verification of bionic as well. Groovy similarly is hard to verify since
this would require systemd in g to be *built* with older kernel headers
but then tested with newer running kernel, so I'm assuming focal
verification covers groovy as well.

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal verification-needed-groovy
** Tags added: verification-done verification-done-bionic 
verification-done-focal verification-done-groovy

-- 
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/1905044

Title:
  systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [impact]

  autopkgtest failure when running with 5.8 kernel, if systemd is built
  with earlier kernel (e.g. 5.4)

  [test case]

  see autopkgtest results, e.g. links in original description below

  [regression potential]

  as this only fixes a test case, any regression would likely result in
  an incorrectly passing, or incorrectly failing, test.

  [scope]

  this is needed for b/f/g/h.

  this bug was introduced by upstream commit 23cc81e7c22 which first
  added testing for 'invalid' cap numbers, but incorrectly using
  capability_list_length() instead of cap_last_cap(). That commit was
  first included in v236, so this bug does not exist before Bionic.

  this is fixed upstream by commit
  ebc815cd1c647faa934a446ceea91ff4bc9dffa4, which was first included in
  v247, so this is needed for h and earlier.

  Also note that even though the 5.8 kernel is not planned to be
  released for Bionic, this test also runs at build time, and since the
  LP build farm builds inside chroots, if the build farm ever moved up
  to Focal with a 5.8 kernel, the build of systemd for Bionic would
  start failing (since it would still be building using the older kernel
  headers, inside the chroot), so this does need to be fixed in Bionic
  systemd as well.

  [other info]

  there is a non-test bug related to this in bug 1905245

  [original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz

  The failing testcases are:

  - root-unittests

  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, funct
  ion test_capability_set_one(). Aborting.
  FAIL: test-cap-list (code: 134)

  - upstream

  TEST-24-UNIT-TESTS:

  --- test-cap-list begin ---
  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, funct
  ion test_capability_set_one(). Aborting.
  --- test-cap-list end ---

  Both seem to be failing with the same assertion.

  These tests are successful on Focal with linux 5.4, therefore they
  would regress when upgrading the kernel from 5.4 to 5.8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905044/+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 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

[Dan Streetman]

Ok here's my understanding of this:

Most keyboards report a single usb device 'interface' for the keyboard
(some have separate interface(s) for builtin mice or other non-keyboard
stuff). However, your keyboard reports two separate 'interfaces' for
your single keyboard. Unfortunately, both of the interfaces it reports
use the exact same vendor and product id, so there's no way for systemd
to tell which is which, from the bus/vendor/product info.

The setting in the hwdb matches specifically on this bus/vendor/product id info 
(the b0003v045Ep00DB string):
evdev:input:b0003v045Ep00DB*


  

This applies the scancode remapping to *both* of the interfaces that
your keyboard reports. However, only one of the interfaces actually
supports the remapped scancodes, so when systemd attempts to tell the
kernel to map the specific scancode to the assigned keycode, the kernel
rejects it, which results in the warning messages you saw in the logs.

However these warning log messages are only produced for the second
interface which doesn't actually support or provide the scancodes in
question. So, this logged warning is completely harmless and you can
ignore it.

It's possible that we might be able to figure out how to finesse systemd
hwdb config to get around the fact that your hardware keyboard is
essentially broken (because it reports two separate interfaces with
identical vendor/product ids but with different operation and behavior).
However since these logged errors are completely harmless, and any 'fix'
could possibly (accidentally) cause the mapped keys to *not* function, I
don't think it's worth it to bother fixing this.

Therefore I'm going to close this as wontfix, since I believe this is a
hardware problem that does not have any actual impact on the system's
operation, besides logging a harmless warning message.


** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1890186

Title:
  Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103:
  Invalid argument

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel
  5.4.0-42-generic on Dell Latitude E6440.  Upon examining the output of
  journalctl -b, I see this:

  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Show Plymouth Boot Screen being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Forward Password Requests to Plymouth Directory Watch being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Set Up Additional Binary Formats being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
File System Check on Root Device being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Rebuild Hardware Database being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Platform Persistent Storage Archival being skipped.
  Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized
  Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 
524288, num gpu pages 524288
  Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn 
acpi driver for receiving events
  Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to 
call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
  Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to 
call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument

  "Invalid argument" means that something goes wrong there, and I don't know 
what it is.
  On my laptop, event8 seems to be keyboard-related:

  $ sudo cat /proc/bus/input/devices | grep -C 5 event8
  I: Bus=0003 Vendor=045e Product=00db Version=0111
  N: Name="Microsoft Natural® Ergonomic Keyboard 4000"
  P: Phys=usb-:00:14.0-13.1/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9
  U: Uniq=
  H: Handlers=sysrq kbd event8 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff8007ff febeffdff3cf fffe
  B: MSC=10
  B: LED=107

  The issue report
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is
  probably related but marked as a duplicate of a no longer existing
  issue report (#1750855).

  The report
  

[Touch-packages] [Bug 1293267] Re: make_ext4fs results in "can't set android permissions - built without android support"

[Vishniakov Aleksandr]

Holy linux, it's still exists in 2020

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to android-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1293267

Title:
  make_ext4fs results in "can't set android permissions - built without
  android support"

Status in android-tools package in Ubuntu:
  Confirmed

Bug description:
  When trying to use make_ext4fs command(through the mkuserimg script),
  it errors out with "can't set android permissions - built without
  android support", solution was to compile from source and add
  "-Icore/include -DANDROID" parameter, works fine.

  What i ran to reproduce this was "mkuserimg -s /media/carson/img
  sparse-system.img ext4 /tmp 1309M"

  Ubuntu 13.10
  android-tools-fsutils

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1293267/+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 1911456] Re: Can't receive files over bluetooth unless settings dialog is open

[Brian Murray]

** Tags added: focal

** Package changed: ubuntu => bluez (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1911456

Title:
  Can't receive files over bluetooth unless settings dialog is open

Status in bluez package in Ubuntu:
  New

Bug description:
  On 18.04 I could send files from my phone to my laptop at any time.
  On 20.04 I can't get files to be accepted by the laptop over bluetooth. After 
much frustration and experimenting, I figured out that it will work, but only 
if the bluetooth settings dialog is open. If the settings dialog is not open, 
the incoming file is rejected.  If the dialog is closed after the file transfer 
begins, the transfer continues but the file is discarded when the transfer is 
complete.  This is very frustrating.
  I need to be able to send files (mostly photos and videos) from my phone to 
my laptop without having to open the settings dialog on the laptop, just like I 
could before upgrading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1911456/+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 1911456] [NEW] Can't receive files over bluetooth unless settings dialog is open

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

On 18.04 I could send files from my phone to my laptop at any time.
On 20.04 I can't get files to be accepted by the laptop over bluetooth. After 
much frustration and experimenting, I figured out that it will work, but only 
if the bluetooth settings dialog is open. If the settings dialog is not open, 
the incoming file is rejected.  If the dialog is closed after the file transfer 
begins, the transfer continues but the file is discarded when the transfer is 
complete.  This is very frustrating.
I need to be able to send files (mostly photos and videos) from my phone to my 
laptop without having to open the settings dialog on the laptop, just like I 
could before upgrading.

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment focal
-- 
Can't receive files over bluetooth unless settings dialog is open
https://bugs.launchpad.net/bugs/1911456
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bluez 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 1911187] Re: scheduled reboot reboots immediately if dbus or logind is not available

[Ioanna Alifieraki]

** Description changed:

  [IMPACT]
  
  When, for whatever reason, logind or dbus is not available scheduled reboot 
reboots the machine immediately.
  From the sources it seems that this is intended :
  
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
  However, I report this as a bug since this is against the logic of a 
scheduled reboot; if someone schedules a reboot they want the system to reboot 
at the specified time not immediately.
  
  There has been a discussion upstream ( 
https://github.com/systemd/systemd/issues/17575 ) and
  a PR ( https://github.com/systemd/systemd/pull/18010 ).
  
  Upstream community is not willing to accept the patch but debian is.
  I open this bug to to pull the patch into Ubuntu once it lands in debian.
  
  [TEST CASE]
  
  The simpler reproducer is to disable dbus to imitate the real world
  case.
  
  # systemctl stop dbus.service
  # systemctl stop dbus.socket
  # shutdown +1140 -r "REBOOT!"
  Failed to set wall message, ignoring: Failed to activate service 
'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Connection timed out
  Connection to groovy closed by remote host.
  Connection to groovy closed.
  
  [REGRESSION POTENTIAL]
  
- The patch has minimal regression potential since it just takes no action
- ( instead of shutting down ) when bus_call_method fails.
+ This patch changes the behaviour of scheduled reboot in case logind or dbus 
has failed.
+ Originally, if logind is not available (call to logind bus fails 
+ 
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
+ it proceeds with immediate shutdown.
+ This patch changes this behaviour and instead of shutting down it does 
nothing.
+ The actual regression potential is a user asking for a reboot and not getting 
it.
+ Other than that the changes in the code are very small and simple and 
unlikely to break anything.
  
  [OTHER]
  
- Debian bug reports : 
+ Debian bug reports :
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
  
  Upstream issue : https://github.com/systemd/systemd/issues/17575
  PR : https://github.com/systemd/systemd/pull/18010

-- 
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/1911187

Title:
  scheduled reboot reboots immediately if dbus or logind is not
  available

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  [IMPACT]

  When, for whatever reason, logind or dbus is not available scheduled reboot 
reboots the machine immediately.
  From the sources it seems that this is intended :
  
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
  However, I report this as a bug since this is against the logic of a 
scheduled reboot; if someone schedules a reboot they want the system to reboot 
at the specified time not immediately.

  There has been a discussion upstream ( 
https://github.com/systemd/systemd/issues/17575 ) and
  a PR ( https://github.com/systemd/systemd/pull/18010 ).

  Upstream community is not willing to accept the patch but debian is.
  I open this bug to to pull the patch into Ubuntu once it lands in debian.

  [TEST CASE]

  The simpler reproducer is to disable dbus to imitate the real world
  case.

  # systemctl stop dbus.service
  # systemctl stop dbus.socket
  # shutdown +1140 -r "REBOOT!"
  Failed to set wall message, ignoring: Failed to activate service 
'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Connection timed out
  Connection to groovy closed by remote host.
  Connection to groovy closed.

  [REGRESSION POTENTIAL]

  This patch changes the behaviour of scheduled reboot in case logind or dbus 
has failed.
  Originally, if logind is not available (call to logind bus fails 
  
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
  it proceeds with immediate shutdown.
  This patch changes this behaviour and instead of shutting down it does 
nothing.
  The actual regression potential is a user asking for a reboot and not getting 
it.
  Other than that the changes in the code are very small and simple and 
unlikely to break anything.

  [OTHER]

  Debian bug reports :
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042

  Upstream issue : https://github.com/systemd/systemd/issues/17575
  PR : https://github.com/systemd/systemd/pull/18010

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1779767] Re: Default cron PATH does not include /snap/bin

[Iain Lane]

This bug is old but I'm going to un-duplicate it. I don't believe it is
fixed.

I've got a cron script on focal (cron 3.0pl1-136ubuntu1) which is
indirectly running `lxc` from a snap (/snap/bin/lxc).

I found the following in mail though:

/home/ubuntu/autopkgtest/tools/autopkgtest-build-lxd: 139: lxc: not found
/home/ubuntu/autopkgtest/tools/autopkgtest-build-lxd: 1: lxc: not found

crontab(5) mentions the default as being "/usr/bin:/bin", and how it
does NOT come from /etc/environment. What you have to do is set
"PATH=/snap/bin:/usr/bin:/bin" at the top of the crontab file if you
want to be able to use snaps. (You can't do "PATH=/snap/bin:$PATH"...)

pathnames.h has a #define for _PATH_DEFPATH where AFAICS this comes
from. Maybe it's that which we would want to modify to fix this for cron
in Ubuntu.

** This bug is no longer a duplicate of bug 1771858
   /snap/bin not in default PATH for units, snapd should ship 
system-environment-generators to inject /snap/bin into $PATH

** Changed in: cron (Ubuntu)
 Assignee: Dimitri John Ledkov (xnox) => (unassigned)

** Tags removed: rls-ee-incoming
** Tags added: rls-ff-incoming rls-hh-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1779767

Title:
  Default cron PATH does not include /snap/bin

Status in cron package in Ubuntu:
  Confirmed

Bug description:
  I recently changed from a .deb install of LXD to a snap, and was
  surprised that one of my crontab scripts stopped working.

  I see that $PATH in a cron script only contains "/usr/bin:/bin",
  whereas my default shell also includes "/snap/bin".

  It seems to me that for the best user experience with snaps,
  "/snap/bin" should be part of the default $PATH in cron.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cron 3.0pl1-128.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 
kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  2 14:30:06 2018
  InstallationDate: Installed on 2017-12-20 (194 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779767/+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 1911789] [NEW] package linux-image-5.8.0-38-generic 5.8.0-38.43~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Harikrishnan Moovendran]

Public bug reported:

Upon upgrading the following error has been observed. I am not sure what
caused this error. So i am attaching the whole list of things happened
just before the error observed.

lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04

$ sudo apt upgrade

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-headers-5.8.0-38-generic linux-hwe-5.8-headers-5.8.0-38 
linux-image-5.8.0-38-generic linux-modules-5.8.0-38-generic 
linux-modules-extra-5.8.0-38-generic
The following packages will be upgraded:
  linux-generic-hwe-20.04 linux-headers-generic-hwe-20.04 
linux-image-generic-hwe-20.04 linux-libc-dev
4 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 78.4 MB of archives.
After this operation, 372 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-modules-5.8.0-38-generic amd64 5.8.0-38.43~20.04.1 [15.0 MB]
Get:2 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-image-5.8.0-38-generic amd64 5.8.0-38.43~20.04.1 [9,500 kB]   
 
Get:3 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-modules-extra-5.8.0-38-generic amd64 5.8.0-38.43~20.04.1 [40.1 MB]
 
Get:4 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-generic-hwe-20.04 amd64 5.8.0.38.43~20.04.23 [1,932 B]
 
Get:5 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-image-generic-hwe-20.04 amd64 5.8.0.38.43~20.04.23 [2,624 B]  
 
Get:6 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-hwe-5.8-headers-5.8.0-38 all 5.8.0-38.43~20.04.1 [11.3 MB]
 
Get:7 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-headers-5.8.0-38-generic amd64 5.8.0-38.43~20.04.1 [1,237 kB] 
 
Get:8 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-headers-generic-hwe-20.04 amd64 5.8.0.38.43~20.04.23 [2,516 B]
 
Get:9 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-libc-dev 
amd64 5.4.0-62.70 [1,116 kB]
  
Fetched 78.4 MB in 2min 19s (564 kB/s)  

 
Selecting previously unselected package linux-modules-5.8.0-38-generic.
(Reading database ... 239086 files and directories currently installed.)
Preparing to unpack 
.../0-linux-modules-5.8.0-38-generic_5.8.0-38.43~20.04.1_amd64.deb ...
Unpacking linux-modules-5.8.0-38-generic (5.8.0-38.43~20.04.1) ...
Selecting previously unselected package linux-image-5.8.0-38-generic.
Preparing to unpack 
.../1-linux-image-5.8.0-38-generic_5.8.0-38.43~20.04.1_amd64.deb ...
Unpacking linux-image-5.8.0-38-generic (5.8.0-38.43~20.04.1) ...
Selecting previously unselected package linux-modules-extra-5.8.0-38-generic.
Preparing to unpack 
.../2-linux-modules-extra-5.8.0-38-generic_5.8.0-38.43~20.04.1_amd64.deb ...
Unpacking linux-modules-extra-5.8.0-38-generic (5.8.0-38.43~20.04.1) ...
Preparing to unpack 
.../3-linux-generic-hwe-20.04_5.8.0.38.43~20.04.23_amd64.deb ...
Unpacking linux-generic-hwe-20.04 (5.8.0.38.43~20.04.23) over 
(5.8.0.36.40~20.04.21) ...
Preparing to unpack 
.../4-linux-image-generic-hwe-20.04_5.8.0.38.43~20.04.23_amd64.deb ...
Unpacking linux-image-generic-hwe-20.04 (5.8.0.38.43~20.04.23) over 
(5.8.0.36.40~20.04.21) ...
Selecting previously unselected package linux-hwe-5.8-headers-5.8.0-38.
Preparing to unpack 
.../5-linux-hwe-5.8-headers-5.8.0-38_5.8.0-38.43~20.04.1_all.deb ...
Unpacking linux-hwe-5.8-headers-5.8.0-38 (5.8.0-38.43~20.04.1) ...
Selecting previously unselected package linux-headers-5.8.0-38-generic.
Preparing to unpack 
.../6-linux-headers-5.8.0-38-generic_5.8.0-38.43~20.04.1_amd64.deb ...
Unpacking linux-headers-5.8.0-38-generic (5.8.0-38.43~20.04.1) ...
Preparing to unpack 
.../7-linux-headers-generic-hwe-20.04_5.8.0.38.43~20.04.23_amd64.deb ...
Unpacking linux-headers-generic-hwe-20.04 (5.8.0.38.43~20.04.23) over 
(5.8.0.36.40~20.04.21) ...
Preparing to unpack .../8-linux-libc-dev_5.4.0-62.70_amd64.deb ...
Unpacking linux-libc-dev:amd64 (5.4.0-62.70) over (5.4.0-60.67) ...
Setting up linux-modules-5.8.0-38-generic (5.8.0-38.43~20.04.1) ...
Setting up 

[Touch-packages] [Bug 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

[Brian Murray]

** Also affects: bluez (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: bluez (Ubuntu Hirsute)
   Importance: High
 Assignee: Dave Jones (waveform)
   Status: New

** Tags removed: rls-gg-incoming rls-hh-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1905627

Title:
  Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Groovy:
  New
Status in bluez source package in Hirsute:
  New

Bug description:
  Bluetooth stops working after updating to bluez version
  5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization
  timed out". Bluetooth is working again if bluez is reverted to version
  5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt.

  Release:  20.10
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14
  Uname: Linux 5.8.0-1007-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: arm64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 25 16:09:03 2020
  ImageMediaBuild: 20200423.1
  InterestingModules: bnep bluetooth
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  Lsusb:
   Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 
25EE
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 
smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 
vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0 console=tty1 
root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 
elevator=deadline rootwait fixrtc
  SourcePackage: bluez
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago)
  acpidump:
   
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+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 1909612] Re: Closing laptop lid doesn't suspend with external monitor plugged in

[Dan Streetman]

*** This bug is a duplicate of bug 1793918 ***
https://bugs.launchpad.net/bugs/1793918

** This bug has been marked a duplicate of bug 1793918
   Add/reintroduce setting to enable suspend on lid-close with external 
monitors attached

-- 
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/1909612

Title:
  Closing laptop lid doesn't suspend with external monitor plugged in

Status in systemd package in Ubuntu:
  New

Bug description:
  I wish to have my laptop suspend when plugged into my dock with an
  HDMI display added. Instead, the system stays on with the monitor
  becoming the primary display. Suspending manually will work.

  I have tried editing logind.conf and uncommenting
  HandleLidSwitch=suspend and the other related items but to no avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  Uname: Linux 5.10.3-051003-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 29 15:42:42 2020
  InstallationDate: Installed on 2020-07-15 (167 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Swift SF314-42
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.3-051003-generic 
root=UUID=d498d6fe-a45c-4a33-a6d1-b036da243cb3 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd06/08/2020:br1.4:efr1.4:svnAcer:pnSwiftSF314-42:pvrV1.04:rvnRO:rnKona_RN:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  mtime.conffile..etc.systemd.logind.conf: 2020-12-29T14:01:28.524143

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1909612/+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 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

[Dan Streetman]

> /sys/power/image_size represents the required amount of space for the
image

no it doesn't:
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-power

"The kernel's suspend-to-disk code will do its best to ensure the image size
will not exceed this number.  However, if it turns out to be impossible, the
kernel will try to suspend anyway using the smallest image possible."

"Reading from this file will display the current image size limit, which is
set to around 2/5 of available RAM by default."

> /dev/dm-2: is a candidate device.
> /dev/sda2: ignoring device with lower priority
> /sys/power/resume is not configured; attempting to hibernate with path: 
> /dev/dm-2, device: 253:2, offset: 0, priority: -2
> Not enough swap for hibernation, Active(anon)=1134696 kB, size=1003516 kB, 
> used=0 kB, threshold=98%

yeah, this is the problem; the checks in sleep-config.c first look for
the highest-priority swap device that is valid as a target, but doesn't
actually check if it's large enough for all Active(anon) pages until
*after* selecting which swap device to use. Probably need to open an
upstream bug.

-- 
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/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  New

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post 

Re: [Touch-packages] [Bug 1911030] Re: graphical flashes on a raspi 4

[fossfreedom]

Do note.

If I change in /boot/firmware/config.txt the default

dtoverlay=vc4-fkms-v3d

To

dtoverlay=vc4-kms-v3d

Then the graphical issues disappear.  Maybe something to consider?

On Tue, 12 Jan 2021, 02:25 Daniel van Vugt, <1911...@bugs.launchpad.net>
wrote:

> ** Tags added: raspi raspi-gfx
>
> ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
>
> ** Also affects: mesa (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Summary changed:
>
> - graphical flashes on a raspi 4
> + Graphical flashes on a raspi 4
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1911030
>
> Title:
>   Graphical flashes on a raspi 4
>
> Status in mesa package in Ubuntu:
>   New
> Status in xorg-server package in Ubuntu:
>   New
>
> Bug description:
>   Using gnome-shell - activities - see attached video
>
>   Graphics flash - more prominent with more than one app running.
>
>   If you install ubuntu-budgie-desktop and simply move through the menu
>   categories the flashing is even more prominent.
>
>   I'm guessing this is xorg related - but I do note the recent mesa
>   uplift has made things worse
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: xorg 1:7.7+19ubuntu15
>   ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
>   Uname: Linux 5.8.0-1011-raspi aarch64
>   ApportVersion: 2.20.11-0ubuntu55
>   Architecture: arm64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Jan 11 16:49:14 2021
>   DistUpgraded: Fresh install
>   DistroCodename: hirsute
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>
>   ImageMediaBuild: 20201225
>   Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805
> USB 3.0 Host Controller
>   ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0
> snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1
> snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60
> smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0
> vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1
> root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet
> splash
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   acpidump:
>
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.103-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1911030/+subscriptions
>

-- 
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/1911030

Title:
  Graphical flashes on a raspi 4

Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Using gnome-shell - activities - see attached video

  Graphics flash - more prominent with more than one app running.

  If you install ubuntu-budgie-desktop and simply move through the menu
  categories the flashing is even more prominent.

  I'm guessing this is xorg related - but I do note the recent mesa
  uplift has made things worse

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 16:49:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20201225
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-2
  

[Touch-packages] [Bug 1911369] Re: [radeon] Horizontal lines of screen corruption after last update.

[Norm Petroff]

Same problem using the live image 20.10

** Attachment added: "20.10_corruption.png"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1911369/+attachment/5453034/+files/20.10_corruption.png

-- 
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/1911369

Title:
  [radeon] Horizontal lines of screen corruption after last update.

Status in linux package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  A clean install is fine if I don't take updates.  If I do take the
  updates and reboot then I get heavy video corruption.  This just
  started today.

  This is a dual boot system.  The windows system has no issues.
  Appears to be software and not a hardware issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 12 21:18:27 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / 
R9 280] [1002:679a] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO2 [Radeon HD 
7950 Boost] [1002:3000]
  InstallationDate: Installed on 2021-01-13 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP Z420 Workstation
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=e1d90a30-a65a-46c5-bae3-c39bbf1a4e0e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2019
  dmi.bios.release: 3.96
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.96
  dmi.board.name: 1589
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53335X G=D
  dmi.product.name: HP Z420 Workstation
  dmi.product.sku: D8N02UC#ABA
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911369/+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 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

[Matthieu Clemenceau]

** Tags added: fr-1054

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1905627

Title:
  Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth stops working after updating to bluez version
  5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization
  timed out". Bluetooth is working again if bluez is reverted to version
  5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt.

  Release:  20.10
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14
  Uname: Linux 5.8.0-1007-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: arm64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 25 16:09:03 2020
  ImageMediaBuild: 20200423.1
  InterestingModules: bnep bluetooth
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  Lsusb:
   Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 
25EE
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 
smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 
vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0 console=tty1 
root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 
elevator=deadline rootwait fixrtc
  SourcePackage: bluez
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago)
  acpidump:
   
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+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 1910775] Re: netdev does not support the independent flag for vxlan

[Dan Streetman]

I understand the need for the parameter upstream, however backporting
features to existing releases typically needs a bit more justification
than just the fact it's nice to have. Can you explain why you can't just
use the existing method (in focal) for creating a vxlan device?
Specifically, setting VXLAN= in the physical device's .network file.

** Changed in: systemd (Ubuntu)
   Status: New => Incomplete

-- 
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/1910775

Title:
  netdev does not support the independent flag for vxlan

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  systemd.netdev does support the independet option for various types of
  interfaces but not for type vxlan. This options was added in a later
  release of systemd (247) with this PR:
  https://github.com/systemd/systemd/pull/17073.

  Since it is currently not possible to create a interface with type
  vxlan it would be nice the include this change in the current LTS
  release (focal).

  "We also need":
  1) Description: Ubuntu 20.04.1 LTS, Release: 20.04
  2) systemd:
Installed: 245.4-4ubuntu3.3
Candidate: 245.4-4ubuntu3.3
  3) systemd support the flag
  4) it does not support it

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910775/+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 1820866] Re: File dialog extremely slow scanning network mounts

[John Bester]

Ubuntu 20.04 does not have this problem any more. I did a few tests
(even shutting down the server for which I had a share bookmarked). The
various different scenarios I tested all behaved as I would expect.

-- 
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/1820866

Title:
  File dialog extremely slow scanning network mounts

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  From any application where you have a "save as" or "open" option, the
  dialog displays, but it takes forever. I have a i5 with 16GB RAM and 2
  SSD's, so the machine is not slow. However, if I use gedit and click
  open / Other documents it takes 6 to 7 seconds before the file dialog
  is properly displayed. This does not even get better with reuse. I
  opened gedit just now and the first time it took 7 seconds. Then I
  pressed Cancel and repeated the process - it still took more than 6
  seconds before the dialog was properly displayed. Often I would only
  see "Other locations" and then default places (Home, Documents etc)
  and bookmarks (I have about 8 bookmarks of which 2 are network shares)
  are displayed. These items are added one by one - maybe one every half
  second. Often it takes a few seconds before the first location other
  than "Other Locations" is displayed. Even the file panel is not
  immediate at first and you can see how lines are added one by one.
  Take into account that my home folder is on an SSD, so populating a
  file list should be lightning fast. I have looked at the CPU activity,
  but it does not go over about 10% during display of open and close
  dialogs.

  Just be aware that this is not specific to gedit - all applications
  using gnome file dialog has the same problem.

  Please see the attached screen recording.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 19 16:14:16 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['nohotcor...@azuri.free.fr', 
'weather-extens...@xeked.com', 'openweather-extens...@jenslody.de']"
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-12-02 (107 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1820866/+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 1835660] Re: initramfs unpacking failed

[Dimitri John Ledkov]

** Also affects: grub2 (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: grub2 (Ubuntu Hirsute)
   Importance: High
 Assignee: Dimitri John Ledkov (xnox)
   Status: Invalid

** Also affects: initramfs-tools (Ubuntu Hirsute)
   Importance: High
   Status: Invalid

** Also affects: linux (Ubuntu Hirsute)
   Importance: High
   Status: Confirmed

** Also affects: grub2 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: initramfs-tools (Ubuntu Groovy)
   Status: New => Invalid

** Changed in: initramfs-tools (Ubuntu Focal)
   Status: New => Invalid

** Changed in: grub2 (Ubuntu Groovy)
   Status: New => Invalid

** Changed in: grub2 (Ubuntu Focal)
   Status: New => Invalid

** Changed in: linux (Ubuntu Groovy)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Groovy)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Focal)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1835660

Title:
  initramfs unpacking failed

Status in OEM Priority Project:
  New
Status in grub2 package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in grub2 source package in Focal:
  Invalid
Status in initramfs-tools source package in Focal:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in grub2 source package in Groovy:
  Invalid
Status in initramfs-tools source package in Groovy:
  Invalid
Status in linux source package in Groovy:
  Confirmed
Status in grub2 source package in Hirsute:
  Invalid
Status in initramfs-tools source package in Hirsute:
  Invalid
Status in linux source package in Hirsute:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

  [Impact]

   * Decoding failure messages in dmsg with a single lz4 initrd

   * Multiple lz4 compressed initrds cannot be decompressed by kernel,
  when loaded by grub

   * Multiple lz4 compressed initrds cannot be decompressed by kernel,
  when there is padding between them

  [Test Case]

   * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4

   * Create an lz4 compressed initrd with a single test-file in it with
  some content. I.e. echo "second-initrd" > test-file, and then pack
  that with cpio hewc owned by root & lz4 -l.

   * Create a combined padded initrd of stock initrd, pad4, and the
  test-marker initrd created above.

   * Boot above with "break=top" kernel command line.

   * With broken kernels, there should be dmesg error message that
  decoding failed, and one will observe that /test-file does not exist
  in the shell.

   * With fixed kernel, /test-file in the initrd shell should exist, and
  should have the expected content "second-initrd".

   * The alignment and padding in the above test case depends on the
  size of the first initrd => if a given padded initrd does not
  reproduce the problem, try varying the size of the first initrd or
  that of the padding between 0..4.

  
  [Where problems could occur]

   * This changes compatible lz4 decompressor in the kernel, which can
  also be used by other kernel modules such as cryptography, squashfs,
  zram, f2fs, comprssed kernel image, pstore. For example, previously
  rejected files with "bogus" length and extra padding may now be
  accepted, whereas they were previously getting rejected by the
  decompressor.

   * Ideally kernel should switch to the stable lz4 format which has
  better specification of end of stream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1835660] Re: initramfs unpacking failed

[Dimitri John Ledkov]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1835660

Title:
  initramfs unpacking failed

Status in OEM Priority Project:
  New
Status in grub2 package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in grub2 source package in Focal:
  Invalid
Status in initramfs-tools source package in Focal:
  Invalid
Status in linux source package in Focal:
  New
Status in grub2 source package in Groovy:
  Invalid
Status in initramfs-tools source package in Groovy:
  Invalid
Status in linux source package in Groovy:
  Confirmed
Status in grub2 source package in Hirsute:
  Invalid
Status in initramfs-tools source package in Hirsute:
  Invalid
Status in linux source package in Hirsute:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

  [Impact]

   * Decoding failure messages in dmsg with a single lz4 initrd

   * Multiple lz4 compressed initrds cannot be decompressed by kernel,
  when loaded by grub

   * Multiple lz4 compressed initrds cannot be decompressed by kernel,
  when there is padding between them

  [Test Case]

   * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4

   * Create an lz4 compressed initrd with a single test-file in it with
  some content. I.e. echo "second-initrd" > test-file, and then pack
  that with cpio hewc owned by root & lz4 -l.

   * Create a combined padded initrd of stock initrd, pad4, and the
  test-marker initrd created above.

   * Boot above with "break=top" kernel command line.

   * With broken kernels, there should be dmesg error message that
  decoding failed, and one will observe that /test-file does not exist
  in the shell.

   * With fixed kernel, /test-file in the initrd shell should exist, and
  should have the expected content "second-initrd".

   * The alignment and padding in the above test case depends on the
  size of the first initrd => if a given padded initrd does not
  reproduce the problem, try varying the size of the first initrd or
  that of the padding between 0..4.

  
  [Where problems could occur]

   * This changes compatible lz4 decompressor in the kernel, which can
  also be used by other kernel modules such as cryptography, squashfs,
  zram, f2fs, comprssed kernel image, pstore. For example, previously
  rejected files with "bogus" length and extra padding may now be
  accepted, whereas they were previously getting rejected by the
  decompressor.

   * Ideally kernel should switch to the stable lz4 format which has
  better specification of end of stream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Peter]

How to stop receiving this emails?


---
V prípade akýchkoľvek otázok alebo nejasností ma neváhajte kontaktovať.
S pozdravom a úctou / Best regards and respectfully

Peter Onger
Mobil - 00421 904 526 034
Email - ogi2...@gmail.com

-
Zeitgeist - The Movie - Duch doby - český dabing

Zeitgeist - Addendum - Duch doby: Dodatek - český dabing

Zeitgeist - Moving Forward - Duch doby: Stále vpred - slovenský dabing

Americký sen - drsný animovaný film o americké centrální bance - český
dabing 
Váž si svoju planétu - Planet Earth is You by @CarlosChaviraTV


Škola online - KhanAcademy.org 


št 14. 1. 2021 o 14:41 Łukasz Zemczak <1871...@bugs.launchpad.net>
napísal(a):

> 14:32 < juliank> sil2100: everything is straight forward cherry-picked
> from master, which is 2.1.18
>
>
> ** Changed in: apt (Ubuntu)
>Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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:
>   In Progress
> Status in apt source package in Focal:
>   In Progress
> Status in apt source package in Groovy:
>   In Progress
> Status in apt package in Debian:
>   Unknown
>
> 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."
>   

[Touch-packages] [Bug 1876495] Re: bash-completion incorrectly shows source package names for APT

[Łukasz Zemczak]

Hello Norbert, 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.4 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

-- 
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/1876495

Title:
  bash-completion incorrectly shows source package names for APT

Status in apt package in Ubuntu:
  Fix Released
Status in bash-completion package in Ubuntu:
  Invalid
Status in apt source package in Focal:
  Fix Committed
Status in bash-completion source package in Focal:
  New
Status in apt source package in Groovy:
  Fix Committed
Status in bash-completion source package in Groovy:
  New
Status in apt source package in Hirsute:
  Fix Released
Status in bash-completion source package in Hirsute:
  Invalid

Bug description:
  [Impact]

  Source packages have been included in apt-cache pkgnames, and virtual
  packages have not been included in apt-cache pkgnames --all-names. The
  former leads to completions autocompleting to source package names
  where they only should complete to binaries.

  [Test case]
  An automated test case is included in the test suite

  test-ubuntu-bug-1876495-pkgnames-virtual

  It verifies that pkgnames does not return source package names, and
  that pkgnames --all-names does return source package names and virtual
  package names.

  [Where problems could occur]
  In the pkgnames command only. If there's a bug, it could exclude or include 
packages it should not.

  [Original bug report]
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal, enter one of the commands below

  2a. apt install brisk
  2b. apt source brisk-menu
  2c. apt-get install brisk
  2d. apt-get source brisk-menu
  2e. apt-cache policy brisk

  Expected results:
  * The bash-completion should not lead to package name as there are no binary 
packages named with starting part "brisk" (see 
https://packages.ubuntu.com/search?suite=all=names=brisk )

  Actual results:
  * all commands below get completed to the name of source package - in this 
example named "brisk-menu"
  (see 
https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames).
 This is absolutely unexpected, as user can not really install this package in 
binary form.

  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May  2 20:35:48 2020
  Dependencies:

  InstallationDate: Installed on 2020-04-22 (9 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876495/+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 1872200] Re: apt does not accept globs and regexes in some cases

[Łukasz Zemczak]

Hello Torsten, 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.4 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 removed: verification-done verification-done-focal
** 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/1872200

Title:
  apt does not accept globs and regexes in some cases

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Users can't use * wildcards anymore in focal, except by accident in apt list.

  For apt list, we now start restricting wildcard syntax to the same
  syntax install now accepts, and at the same time we remove the
  restrictions on which patterns are accepted (which only accepted
  patterns starting in ~ or ?), so !~napt now works, and does not
  accidentally match as a wildcard.

  
  [Test case]

  Test that * wildcards work for both install and list, and test that a
  ? wildcard does not.

  We included autopkgtests for those:

   BEGIN TESTS #

  # * wildcards should still work
  testsuccessequal "Listing...
  automatic1/now 1.0 i386 [installed,local]
  automatic2/now 1.0 i386 [installed,local]" apt list 'automatic*'

  testfailureequal "Reading package lists...
  Building dependency tree...
  Reading state information...
  Note, selecting 'automatic1' for glob 'automatic*'
  Note, selecting 'automatic2' for glob 'automatic*'
  automatic1 is already the newest version (1.0).
  automatic1 set to manually installed.
  automatic2 is already the newest version (1.0).
  automatic2 set to manually installed.
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   broken : Depends: does-not-exist but it is not installable
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution)." apt install -s 'automatic*'

  # other wildcards should fail

  testfailureequal "Listing...
  E: input:0-10: error: Expected pattern
 automatic?
 ^^" apt list 'automatic?'

  testfailureequal "Reading package lists...
  Building dependency tree...
  Reading state information...
  E: Unable to locate package automatic?" apt install -s 'automatic?'

  
   END TESTS #

  Also it might be worth checking that apt list !~napt works. This used
  to produce an empty list, as it was accidentally matched as a wildcard
  and produced no result - now it produces every package whose name does
  not contain "apt".

  
  [Regression potential]
  The changes only affect interactive users, as apt(8) is not stable for 
in-script use, hence they can fix up their command-line if it stops working for 
them (though, really, more should work now).

  No scripts will be broken :)

  [Squashed in changes]
  The SRU also fixes potential build failures by correctly prefxing nullptr_t 
with the std:: namespace, and includes updated Dutch documentation.

  [Original bug report]
  Observed with Ubuntu 20.04 Beta.

  apt remove 'mypackage*' does not remove all installed packages
  starting with “mypackage”.  Instead:

  $ sudo apt remove 'mypackage*'
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  E: Unable to locate package mypackage*

  However:

  $ sudo apt list --installed 'mypackage*'
  Listing... Done
  mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic]
  mypackage1/focal,now 0.3.2-5build1 amd64 [installed]

To manage notifications about this bug go to:

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Łukasz Zemczak]

Hello andresgenovez, 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.4 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: In Progress => 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/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:
  In Progress
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]
  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 

[Touch-packages] [Bug 1911676] Re: Short pattern not terminated by ~ or !

[Łukasz Zemczak]

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.4 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

-- 
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/1911676

Title:
  Short pattern not terminated by  ~ or !

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  Short patterns like ~nfoo!~nbar or ~nfoo~nbar do not work correctly -
  they are treated as ?name(foo!~nbar) / ?name(foo~nbar) rather than
  ?name(foo)?not(?name(bar)) / ?name(foo)?name(bar)

  [Test Case]
  Unit tests have been added that are run during build and check they are 
parsed correctly

  +   EXPECT_PATTERN_EQ("~napt~nfoo", "?and(?name(apt),?name(foo))");
  +   EXPECT_PATTERN_EQ("~napt!~nfoo", "?and(?name(apt),?not(?name(foo)))");

  [Where problems could occur]
  Really just changing a string constant for this change in a function that 
parses of words, so well, the only problem arising could be that words inside 
patterns are recognized wrongly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1911676/+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 1876495] Re: bash-completion incorrectly shows source package names for APT

[Łukasz Zemczak]

Hello Norbert, or anyone else affected,

Accepted apt into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.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: apt (Ubuntu Groovy)
   Status: New => 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1876495

Title:
  bash-completion incorrectly shows source package names for APT

Status in apt package in Ubuntu:
  Fix Released
Status in bash-completion package in Ubuntu:
  Invalid
Status in apt source package in Focal:
  New
Status in bash-completion source package in Focal:
  New
Status in apt source package in Groovy:
  Fix Committed
Status in bash-completion source package in Groovy:
  New
Status in apt source package in Hirsute:
  Fix Released
Status in bash-completion source package in Hirsute:
  Invalid

Bug description:
  [Impact]

  Source packages have been included in apt-cache pkgnames, and virtual
  packages have not been included in apt-cache pkgnames --all-names. The
  former leads to completions autocompleting to source package names
  where they only should complete to binaries.

  [Test case]
  An automated test case is included in the test suite

  test-ubuntu-bug-1876495-pkgnames-virtual

  It verifies that pkgnames does not return source package names, and
  that pkgnames --all-names does return source package names and virtual
  package names.

  [Where problems could occur]
  In the pkgnames command only. If there's a bug, it could exclude or include 
packages it should not.

  [Original bug report]
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal, enter one of the commands below

  2a. apt install brisk
  2b. apt source brisk-menu
  2c. apt-get install brisk
  2d. apt-get source brisk-menu
  2e. apt-cache policy brisk

  Expected results:
  * The bash-completion should not lead to package name as there are no binary 
packages named with starting part "brisk" (see 
https://packages.ubuntu.com/search?suite=all=names=brisk )

  Actual results:
  * all commands below get completed to the name of source package - in this 
example named "brisk-menu"
  (see 
https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames).
 This is absolutely unexpected, as user can not really install this package in 
binary form.

  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May  2 20:35:48 2020
  Dependencies:

  InstallationDate: Installed on 2020-04-22 (9 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876495/+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

[Łukasz Zemczak]

Hello andresgenovez, or anyone else affected,

Accepted apt into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.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: apt (Ubuntu Groovy)
   Status: In Progress => Fix Committed

-- 
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:
  In Progress
Status in apt source package in Focal:
  In Progress
Status in apt source package in Groovy:
  Fix Committed
Status in apt package in Debian:
  Unknown

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 

[Touch-packages] [Bug 1911676] Re: Short pattern not terminated by ~ or !

[Łukasz Zemczak]

Hello Julian, or anyone else affected,

Accepted apt into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.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: apt (Ubuntu Groovy)
   Status: New => 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1911676

Title:
  Short pattern not terminated by  ~ or !

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  New
Status in apt source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  Short patterns like ~nfoo!~nbar or ~nfoo~nbar do not work correctly -
  they are treated as ?name(foo!~nbar) / ?name(foo~nbar) rather than
  ?name(foo)?not(?name(bar)) / ?name(foo)?name(bar)

  [Test Case]
  Unit tests have been added that are run during build and check they are 
parsed correctly

  +   EXPECT_PATTERN_EQ("~napt~nfoo", "?and(?name(apt),?name(foo))");
  +   EXPECT_PATTERN_EQ("~napt!~nfoo", "?and(?name(apt),?not(?name(foo)))");

  [Where problems could occur]
  Really just changing a string constant for this change in a function that 
parses of words, so well, the only problem arising could be that words inside 
patterns are recognized wrongly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1911676/+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 1894606] Re: [SRU] Add profile-set for HP Thunderbolt Dock

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1894606

Title:
  [SRU] Add profile-set for HP Thunderbolt Dock

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  HP Thunderbolt Dock has a USB audio device provides headset connector 
functionality. The Dock can also attach an optional USB audio module. Since 
they are both USB audio device, the input/output names are the same and it 
confuses user.

  [Fix]
  Add PulseAudio profile-sets for each USB device with different monikers.

  The merge request is already approved by maintainer, will be merged after 
14.0 release:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/353

  [Test]
  With profile-set applied, two different USB audio device on HP TBT Dock have 
distinctive names.

  [Regression Potential]
  Currently I can't think of any regression risk, as this SRU only adds new 
profile-sets and description translation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894606/+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

[Łukasz Zemczak]

14:32 < juliank> sil2100: everything is straight forward cherry-picked
from master, which is 2.1.18


** Changed in: apt (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  In Progress
Status in apt source package in Focal:
  In Progress
Status in apt source package in Groovy:
  In Progress
Status in apt package in Debian:
  Unknown

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: 

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Julian Andres Klode]

** Changed in: apt (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  In Progress
Status in apt source package in Focal:
  In Progress
Status in apt source package in Groovy:
  In Progress
Status in apt package in Debian:
  Unknown

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 1911676] Re: Short pattern not terminated by ~ or !

[Łukasz Zemczak]

14:25 < sil2100> juliank: does the hirsute 2.1.18 include the fix for the short 
pattern termination?
14:25 < sil2100> (talking about apt)
14:26 < juliank> sil2100: yeah, that was in 2.1.13 already :)


** Changed in: apt (Ubuntu)
   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/1911676

Title:
  Short pattern not terminated by  ~ or !

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  New
Status in apt source package in Groovy:
  New

Bug description:
  [Impact]

  Short patterns like ~nfoo!~nbar or ~nfoo~nbar do not work correctly -
  they are treated as ?name(foo!~nbar) / ?name(foo~nbar) rather than
  ?name(foo)?not(?name(bar)) / ?name(foo)?name(bar)

  [Test Case]
  Unit tests have been added that are run during build and check they are 
parsed correctly

  +   EXPECT_PATTERN_EQ("~napt~nfoo", "?and(?name(apt),?name(foo))");
  +   EXPECT_PATTERN_EQ("~napt!~nfoo", "?and(?name(apt),?not(?name(foo)))");

  [Where problems could occur]
  Really just changing a string constant for this change in a function that 
parses of words, so well, the only problem arising could be that words inside 
patterns are recognized wrongly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1911676/+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 1901926] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones

[Marcus Aurelius]

FYI my problem seems to be solved after a bunch of updates to several
alsa packages a few weeks ago.

-- 
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/1901926

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  There is no sound at all from the headphones (p3 out). Speakers work
  fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sartojr2255 F pulseaudio
   /dev/snd/controlC0:  sartojr2255 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 28 13:48:59 2020
  InstallationDate: Installed on 2020-01-14 (287 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: HDA NVidia - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sartojr2255 F pulseaudio
   /dev/snd/controlC0:  sartojr2255 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago)
  dmi.bios.date: 11/04/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P03REZ.041.191104.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P03REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+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 1876495] Re: bash-completion incorrectly shows source package names for APT

[Julian Andres Klode]

** Description changed:

+ [Impact]
+ 
+ Source packages have been included in apt-cache pkgnames, and virtual
+ packages have not been included in apt-cache pkgnames --all-names. The
+ former leads to completions autocompleting to source package names where
+ they only should complete to binaries.
+ 
+ [Test case]
+ An automated test case is included in the test suite 
+ 
+ test-ubuntu-bug-1876495-pkgnames-virtual
+ 
+ It verifies that pkgnames does not return source package names, and that
+ pkgnames --all-names does return source package names and virtual
+ package names.
+ 
+ [Where problems could occur]
+ In the pkgnames command only. If there's a bug, it could exclude or include 
packages it should not.
+ 
+ [Original bug report]
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal, enter one of the commands below
  
  2a. apt install brisk
  2b. apt source brisk-menu
  2c. apt-get install brisk
  2d. apt-get source brisk-menu
- 2e. apt-cache policy brisk 
+ 2e. apt-cache policy brisk
  
  Expected results:
  * The bash-completion should not lead to package name as there are no binary 
packages named with starting part "brisk" (see 
https://packages.ubuntu.com/search?suite=all=names=brisk )
  
  Actual results:
  * all commands below get completed to the name of source package - in this 
example named "brisk-menu"
  (see 
https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames).
 This is absolutely unexpected, as user can not really install this package in 
binary form.
  
  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May  2 20:35:48 2020
  Dependencies:
-  
+ 
  InstallationDate: Installed on 2020-04-22 (9 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  [Impact]
  
  Source packages have been included in apt-cache pkgnames, and virtual
  packages have not been included in apt-cache pkgnames --all-names. The
  former leads to completions autocompleting to source package names where
  they only should complete to binaries.
  
  [Test case]
- An automated test case is included in the test suite 
+ An automated test case is included in the test suite
  
  test-ubuntu-bug-1876495-pkgnames-virtual
  
  It verifies that pkgnames does not return source package names, and that
  pkgnames --all-names does return source package names and virtual
  package names.
  
  [Where problems could occur]
  In the pkgnames command only. If there's a bug, it could exclude or include 
packages it should not.
  
  [Original bug report]
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal, enter one of the commands below
  
  2a. apt install brisk
  2b. apt source brisk-menu
  2c. apt-get install brisk
  2d. apt-get source brisk-menu
  2e. apt-cache policy brisk
  
  Expected results:
  * The bash-completion should not lead to package name as there are no binary 
packages named with starting part "brisk" (see 
https://packages.ubuntu.com/search?suite=all=names=brisk )
  
  Actual results:
  * all commands below get completed to the name of source package - in this 
example named "brisk-menu"
  (see 
https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames).
 This is absolutely unexpected, as user can not really install this package in 
binary form.
  
  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May  2 20:35:48 2020
  Dependencies:
  
  InstallationDate: Installed on 2020-04-22 (9 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
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/1876495

Title:
  bash-completion incorrectly shows source package names for APT

Status in apt package in Ubuntu:
  Fix Released
Status in bash-completion package in Ubuntu:
  Invalid
Status in apt source package in Focal:
  New
Status in 

[Touch-packages] [Bug 1911676] [NEW] Short pattern not terminated by ~ or !

[Julian Andres Klode]

Public bug reported:

[Impact]

Short patterns like ~nfoo!~nbar or ~nfoo~nbar do not work correctly -
they are treated as ?name(foo!~nbar) / ?name(foo~nbar) rather than
?name(foo)?not(?name(bar)) / ?name(foo)?name(bar)

[Test Case]
Unit tests have been added that are run during build and check they are parsed 
correctly

+   EXPECT_PATTERN_EQ("~napt~nfoo", "?and(?name(apt),?name(foo))");
+   EXPECT_PATTERN_EQ("~napt!~nfoo", "?and(?name(apt),?not(?name(foo)))");

[Where problems could occur]
Really just changing a string constant for this change in a function that 
parses of words, so well, the only problem arising could be that words inside 
patterns are recognized wrongly.

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: apt (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: apt (Ubuntu Groovy)
 Importance: Undecided
 Status: New

** Also affects: apt (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: apt (Ubuntu Groovy)
   Importance: Undecided
   Status: New

-- 
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/1911676

Title:
  Short pattern not terminated by  ~ or !

Status in apt package in Ubuntu:
  New
Status in apt source package in Focal:
  New
Status in apt source package in Groovy:
  New

Bug description:
  [Impact]

  Short patterns like ~nfoo!~nbar or ~nfoo~nbar do not work correctly -
  they are treated as ?name(foo!~nbar) / ?name(foo~nbar) rather than
  ?name(foo)?not(?name(bar)) / ?name(foo)?name(bar)

  [Test Case]
  Unit tests have been added that are run during build and check they are 
parsed correctly

  +   EXPECT_PATTERN_EQ("~napt~nfoo", "?and(?name(apt),?name(foo))");
  +   EXPECT_PATTERN_EQ("~napt!~nfoo", "?and(?name(apt),?not(?name(foo)))");

  [Where problems could occur]
  Really just changing a string constant for this change in a function that 
parses of words, so well, the only problem arising could be that words inside 
patterns are recognized wrongly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1911676/+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 1848330] Autopkgtest regression report (audit/1:2.8.2-1ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted audit (1:2.8.2-1ubuntu1.1) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

openssh/1:7.6p1-4ubuntu0.3 (arm64, armhf, amd64, i386, ppc64el)
linux/4.15.0-132.136 (i386)
libvirt/4.0.0-1ubuntu8.17 (amd64, i386)
glibc/2.27-3ubuntu1.4 (amd64)
linux-raspi-5.4/5.4.0-1026.29~18.04.1 (armhf)
linux-hwe-5.4/5.4.0-62.70~18.04.1 (armhf)
linux-hwe-5.0/5.0.0-63.69 (armhf)


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#audit

[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 audit in Ubuntu.
https://bugs.launchpad.net/bugs/1848330

Title:
  Installing auditd sometimes fails in post-inst

Status in audit package in Ubuntu:
  Fix Released
Status in audit source package in Bionic:
  Fix Committed
Status in audit package in Debian:
  New

Bug description:
  [Impact]

  Sometimes, auditd will get stuck when starting up, causing systemd to
  kill it after a while since it (systemd) never got the start
  notification.

  Upstream troubleshooted this to be caused by calling a syslog()
  function inside a signal handler.

  [Test Case]
  There is no reliable test case to reproduce the bug, other than trying the 
fixed packages on an affected system where the hang occurs more frequently.

  Basically:
  sudo systemctl stop auditd
  sudo systemctl start auditd

  should work reliably. Do not run that in a tight loop, however, as
  that will trigger a it's-restarting-too-frequently failure.

  [Where problems could occur]
  - if auditd fails to start, then the first fallback is syslog, and if that is 
not picking up the audit messages, the last resort is the kernel buffer, which 
can fill up. In the case it fills up, audit logs will be lost.

  - it's possible to configure the audit system to panic() the machine
  if audit messages are lost or otherwise not able to be recorded
  (auditctl -f 2; default is 1 which is printk())

  - the update restarts auditd as expected. Misconfiguration on very
  very busy systems could mean that audit logs would be lost during the
  brief moment the service is restarted. If that's the case, this update
  would just be one more way to trigger it, but not be the root cause of
  the problem

  - similarly, as is usual with updates that restart services, it's
  possible than an incorrect configuration for auditd is present, but
  was never loaded before. The restart will load the config, and will
  fail in such a case.

  - this update removes a logging statement that occurs during startup:

  ("dispatcher %d reaped", pid)

  It's unlikely, but possible, that some monitoring software could be
  looking for that message in the logs. It won't be there anymore after
  this update.

  [Other Info]
  The patch is committed upstream and part of the 2.8.5 release, which is 
present in Focal and later.
  The real fix for this bug is just dropping the audit_msg() call in the signal 
handler code. But the original reporter of the bug, who is also who came up 
with the fix (see https://bugzilla.redhat.com/show_bug.cgi?id=1587995#c4) 
stated that with the 3 changes in the patch the startup hang didn't happen to 
him anymore. Since this bug is difficult to reproduce elsewhere (either you 
have it, or you don't), I chose to keep the 3 changes instead of just the 
removal of the audit_msg() call.

  [Original Description]

  This happens sometimes when installing auditd on Ubuntu 18.04.2, most
  installations work successfully, though. Re-running the install also
  fixes the issue, but the failure breaks our automation. The log from
  the failure looks like this:

  # apt install auditd
  ...
  Setting up auditd (1:2.8.2-1ubuntu1) ...
  Created symlink /etc/systemd/system/multi-user.target.wants/auditd.service → 
/lib/systemd/system/auditd.service.
  Job for auditd.service failed because a timeout was exceeded.
  See "systemctl status auditd.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript auditd, action "start" failed.
  ● auditd.service - Security Auditing Service
     Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: enabled)
     Active: failed (Result: timeout) since Tue 2019-09-17 18:43:06 UTC; 11ms 
ago
   Docs: man:auditd(8)
     https://github.com/linux-audit/audit-documentation
    Process: 9702 ExecStart=/sbin/auditd (code=killed, signal=KILL)

  Sep 17 18:40:06 compute-node21 systemd[1]: Starting Security Auditing 
Service...
  Sep 17 18:40:06 compute-node21 auditd[9703]: Started dispatcher: 
/sbin/audispd pid: 9705
  Sep 17 18:40:06 compute-node21 audispd[9705]: No 

[Touch-packages] [Bug 1910576] Re: [MIR] libbpf (dependency of iproute2)

[Christian Ehrhardt ]

[Summary]
MIR Team Ack to src:libbpf
This does not need a security review IMHO, but as outlined below I'd want
security to quickly ACK on that decision - assigning to Seth (security MIR
Team member) for that.
List of specific binary packages to be promoted to main: libbpf0

Required TODOs:
- None

Recommended TODOs:
- Add build and/or autopkgtest tests to the package to spot issues early

[Duplication]
There is no other package in main providing the same functionality.
Some packages that formerly had libbpf code slowly migrate to this lib.
But that isn't duplication it is the right thing to do.

[Dependencies]
OK:
- no other Dependencies to MIR due to this
- -dev package will be auto-promoted, but all it's deps are ok as well

[Embedded sources and static linking]
- no embedded source present (this is in fact used to un-embed some
  in other pkg)
- no static linking

[Security]
OK:
- history of CVEs does not look concerning
  No issues on the lib yet, but the kernel backend has some (as one would
  expect for such a dynamic interface)
  https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=bpf
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not open a port
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)

Problems:
- does not parse data formats, but no externally controlled ones

I'm unsure if this needs a security review. They are currently rather
busy with those and this package does replace code that was worse in iproute2
(pulling it into main). Since this is driven and in a lot of use by the
bigger kernel community as well as Debian jumping onto this for Buster I think
while I'd appreciate a review we don't strictly need it here as we are
replacing better code.
Also the new iproute needs to go along kernel 5.10 which just appeared in
21.04 so the runway is short.

But I'll want security to do a 5-10 minute read of that reasoning and the code
to agree to that decision. If they do we can go on promoting this immediately.
If security decides that a full review is needed it will go their way as usual.

[Common blockers]
OK:
- does not FTBFS currently
- The package has a team bug subscriber
- no translation present, but none needed for this case (user visible)?
- not a python/go package, no extra constraints to consider int hat regard
- no new python2 dependency

Problems:
- does not have a test suite that runs at build time
- does not have a test suite that runs as autopkgtest
Gladly that is somewhat covered by the upstream travis tests. None of the few
but growing dependencies has higher level tests yet. This isn't a blocker
since this is "just" the lib but certainly a step that would be recommended
to the owning team to add.


[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking is in place
- d/watch is present and looks ok
- Upstream update history is good, but it is yet rather new
- Debian/Ubuntu update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- d/rules is rather clean
- Does not have Built-Using

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as I can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH
- no use of user nobody
- no use of setuid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks


** Changed in: libbpf (Ubuntu)
 Assignee: Christian Ehrhardt  (paelzer) => Seth Arnold (seth-arnold)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1910576

Title:
  [MIR] libbpf (dependency of iproute2)

Status in iproute2 package in Ubuntu:
  Invalid
Status in libbpf package in Ubuntu:
  New

Bug description:
  [Availability]
  libbpf | 0.1.0-1 | groovy/universe  | source
  libbpf | 0.3-2   | hirsute/universe | source

  [Rationale]
  Libbpf is (or is about to become) a dependency for building iproute2 which 
already is in main. Using BPF is becoming more wide-spread. The library allows 
to load and use eBPF programs from user-space (functionality provided by the 
kernel). It is already maintained in main for Debian 
(https://tracker.debian.org/pkg/libbpf)

  [Security]
  Since the code is taken out of the Linux kernel, this should be treated 
similar to the kernel for security. Research uncovered no records about 
security issues.

  [Quality assurance]
  At this point there are no open bug reports against libbpf (except this one) 
in Ubuntu. Also no open bugs found in Debian. Project is taken from the kernel 
source and claims static analysis via LGTM and 

[Touch-packages] [Bug 1911369] Re: [radeon] Horizontal lines of screen corruption after last update.

[Timo Aaltonen]

Please test 20.10 live image, do you have the same corruption there?

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: mesa (Ubuntu)
   Status: New => Incomplete

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
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/1911369

Title:
  [radeon] Horizontal lines of screen corruption after last update.

Status in linux package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  A clean install is fine if I don't take updates.  If I do take the
  updates and reboot then I get heavy video corruption.  This just
  started today.

  This is a dual boot system.  The windows system has no issues.
  Appears to be software and not a hardware issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 12 21:18:27 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / 
R9 280] [1002:679a] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO2 [Radeon HD 
7950 Boost] [1002:3000]
  InstallationDate: Installed on 2021-01-13 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP Z420 Workstation
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=e1d90a30-a65a-46c5-bae3-c39bbf1a4e0e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2019
  dmi.bios.release: 3.96
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.96
  dmi.board.name: 1589
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53335X G=D
  dmi.product.name: HP Z420 Workstation
  dmi.product.sku: D8N02UC#ABA
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911369/+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