[Touch-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device

[Hui Wang]

Updated the [Where problems will occur] part.


** Description changed:

  [Impact]
  On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio.
  
  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.
  
  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.
  
  [Where problems will occur]
- This fix limits to the Cmedia Audio only, other devices are unaffected.
+ "Cmedia Audio" is the sound card name of this usb audio dongle, and this 
string is got from usb string descriptor, that is to say the "Cmedia Audio" is 
hard-coded in the firmware of that usb dongle.
+ Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't 
set string descriptor, then the audio driver sets a generic name "USB Audio 
Device" for them, and all dongles I met before don't have SPDIF interface.
+ So If this SRU could introduce regression, it will happen on a Cmedia usb 
audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor 
and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF 
playback device from the gnome-sound-setting. But this regression chance is 
very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in 
the string descriptor and it is very rare a usb audio dongle has SPDIF 
interface. So far we haven't met such a cmedia usb audio dongle.

** Description changed:

  [Impact]
  On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio.
  
  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.
  
  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.
  
  [Where problems will occur]
  "Cmedia Audio" is the sound card name of this usb audio dongle, and this 
string is got from usb string descriptor, that is to say the "Cmedia Audio" is 
hard-coded in the firmware of that usb dongle.
- Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't 
set string descriptor, then the audio driver sets a generic name "USB Audio 
Device" for them, and all dongles I met before don't have SPDIF interface.
+ Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't 
set string descriptor, then the audio driver sets a generic name "USB Audio 
Device" for them, if a dongle has string descriptor, it may have different 
string like "C-Media USB Headphone Set", and all dongles I met before don't 
have SPDIF interface.
  So If this SRU could introduce regression, it will happen on a Cmedia usb 
audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor 
and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF 
playback device from the gnome-sound-setting. But this regression chance is 
very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in 
the string descriptor and it is very rare a usb audio dongle has SPDIF 
interface. So far we haven't met such a cmedia usb audio dongle.

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

Title:
  [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-
  Audio.pcm.iec958_device

Status in OEM Priority Project:
  In Progress
Status in alsa-lib package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  In Progress
Status in alsa-lib source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio.

  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.

  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.

  [Where problems will occur]
  "Cmedia Audio" is the sound card name of this usb audio dongle, and this 
string is got from usb string descriptor, that is to say the "Cmedia Audio" is 
hard-coded in the firmware of that usb dongle.
  Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't 
set string descriptor, then the audio driver sets a generic name "USB Audio 
Device" for them, if a dongle has string descriptor, it may have different 
string like "C-Media USB Headphone Set", and all dongles I met before don't 
have SPDIF interface.
  So If this SRU could introduce regression, it will happen on a Cmedia usb 
audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor 
and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF 
playback device from the gnome-sound-setting. But this regression chance is 
very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in 
the string descriptor and it is very rare a usb audio dongle has SPDIF 
interface. So far we haven't met such a cmedia usb audio dongle.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1404172] Re: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory

[navycat]

This bug is present in Ubuntu 21.04 and 20.10 daily builds.

** Tags removed: apport-bug i386
** Tags added: groovy hirsute

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

Title:
  lightdm: PAM unable to dlopen(pam_kwallet.so):
  /lib/security/pam_kwallet.so: cannot open shared object file: No such
  file or directory

Status in One Hundred Papercuts:
  Confirmed
Status in Light Display Manager:
  Confirmed
Status in systemd:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  auth.log complaints:

  Dec 19 07:24:42 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Dec 19 07:24:42 u32 lightdm: PAM adding faulty module: pam_kwallet.so
  Dec 19 07:24:42 u32 lightdm: pam_unix(lightdm-greeter:session): session 
opened for user lightdm by (uid=0)
  Dec 19 07:24:42 u32 systemd-logind[656]: New session c1 of user lightdm.
  Dec 19 07:24:42 u32 systemd: pam_unix(systemd-user:session): session opened 
for user lightdm by (uid=0)
  Dec 19 07:24:46 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Dec 19 07:24:46 u32 lightdm: PAM adding faulty module: pam_kwallet.so
  Dec 19 07:24:46 u32 lightdm: pam_succeed_if(lightdm:auth): requirement "user 
ingroup nopasswdlogin" not met by user "oem"
  Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm-greeter:session): session 
closed for user lightdm
  Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm:session): session opened for 
user oem by (uid=0)

  
  As per lp:1309535 #18 comment such 'warnings' should be silenced (as they 
scared unawared users about the both needs of pam's gnome/kde)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.13.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-7.8-generic 3.18.0
  Uname: Linux 3.18.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Fri Dec 19 10:47:07 2014
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1404172/+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 1921485] Re: Bosch CERT Advisory: OpenSSL Multiple Vulnerabilities

[Steve Beattie]

This was addressed in https://ubuntu.com/security/notices/USN-4891-1 .

** Information type changed from Private Security to Public Security

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

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

Title:
  Bosch CERT Advisory: OpenSSL Multiple Vulnerabilities

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Description

  Multiple vulnerabilities have been reported in OpenSSL, which can be
  exploited by malicious people to bypass certain security restrictions
  and cause a DoS (Denial of Service).

  1

  An error when validating CA certificates can be exploited to bypass
  certificate validation checks.

  Successful exploitation of the vulnerability #1 requires the
  X509_V_FLAG_X509_STRICT flag to be enabled (not enabled by default)
  and an application to either not set a purpose for certificate
  verification or override the default purpose.

  2

  A NULL-pointer deference error when handling renegotiation ClientHello
  messages can be exploited to crash the OpenSSL TLS server.

  Successful exploitation of the vulnerability #2 requires an OpenSSL
  server with TLSv1.2 and renegotiation enabled (enabled by default).

  The vulnerabilities are reported in versions prior to 1.1.1k.

  Affected Software

  The following software is affected by the described vulnerability.
  Please check the vendor links below to see if exactly your version is
  affected.

  OpenSSL 1.x

  Solution

  Update to version 1.1.1k.

  References

  1. https://www.openssl.org/news/vulnerabilities.html 

  2. https://www.openssl.org/news/secadv/20210325.txt 


  
  Please provide a fix as soon as possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921485/+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 1921690] Re: I dont know

[Steve Beattie]

Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


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

** Information type changed from Private Security to Public

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

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

Title:
  I dont know

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I dont know

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 29 00:50:07 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:3988]
  InstallationDate: Installed on 2021-03-16 (13 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 13d3:5621 IMC Networks EasyCamera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80X6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=fa69165d-92ad-4dfe-9070-67261b9c30f3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2017
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 1YCN21WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-13IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-13IKB
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr1YCN21WW(V1.06):bd04/14/2017:br1.21:efr1.21:svnLENOVO:pn80X6:pvrLenovoYOGA720-13IKB:rvnLENOVO:rnLenovoYOGA720-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80X6
  dmi.product.sku: LENOVO_MT_80X6_BU_idea_FM_Lenovo YOGA 720-13IKB
  dmi.product.version: Lenovo YOGA 720-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1kisak1~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1~kisak1~f
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/xorg/+bug/1921690/+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 1921883] Re: Notification badges for app switcher

[Daniel van Vugt]

Thanks for the bug report.

Please check the issue is still present in newer versions of GNOME. If
so then report it to the developers at https://gitlab.gnome.org/GNOME
/gnome-shell/issues and tell us the new issue ID.

** Package changed: xorg (Ubuntu) => unity (Ubuntu)

** Package changed: unity (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  Notification badges for app switcher

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The Alt+Tab application switcher could benefit from a colored
  notification badge. This *could* be a number with the amount of
  notifications, but honestly, a simple boolean "has / has no badge"
  would suffice already.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-140.144-generic 4.15.18
  Uname: Linux 4.15.0-140-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 30 11:43:33 2021
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [17aa:3801]
  InstallationDate: Installed on 2018-12-20 (830 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 04f2:b579 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80TF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-140-generic 
root=UUID=0f8de3b2-c66e-4eb6-ae0a-f2650fc5b9b5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 1MCN43WW X64
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V110-14IAP
  dmi.modalias: 
dmi:bvnLENOVO:bvr1MCN43WWX64:bd11/27/2017:svnLENOVO:pn80TF:pvrLenovoV110-14IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV110-14IAP:
  dmi.product.family: V110-14IAP
  dmi.product.name: 80TF
  dmi.product.version: Lenovo V110-14IAP
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1921883/+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 1918855] Re: Xorg xserver got signal 6 to abort

[Kai-Chuan Hsieh]

I try memory stress test with my ppa in #4, the issue is still
reproduced.

** Attachment added: "sosreport-u-Inspiron-1918855-2021-03-31-xbkosvf.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5482483/+files/sosreport-u-Inspiron-1918855-2021-03-31-xbkosvf.tar.xz

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

Title:
  Xorg xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  I run checkbox job
  com.canonical.certification::memory/memory_stress_ng on focal, and the
  xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1918855/+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 1918410] Re: isc-dhcp-client denied by apparmor

[John Johansen]

Merge upstream https://gitlab.com/apparmor/apparmor/-/merge_requests/730

it will be part of the next apparmor point releases

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

Title:
  isc-dhcp-client denied by apparmor

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Hi, I get weird errors in the audit log, seeing dhclient is being
  denied reading its comm or the comm of one of its tasks:

  
  [1383307.827378] audit: type=1400 audit(1615367094.054:162): 
apparmor="DENIED" operation="open" profile="/{,usr/}sbin/dhclient" 
name="/proc/1095210/task/1095213/comm" pid=1095210 comm="dhclient" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0

  This might or might not be linked with the fact that I can't get an
  IPv4 on this interface. Note that it happened to other, see this
  comment:

  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1413232/comments/8

  Or even an article recommending disabling apparmor for dhclient(!):
  
https://blog.anthony-jacob.com/perte-dip-v4-sous-ubuntu-20-04-apparmor-et-dhclient/

  
  As I said, I'm not sure this is the root cause of the lack of IPv4 renewal, 
because running it manually *does* succeed in getting an IP. And running it in 
strace shows the EACCES failure:

  [pid 1095210] openat(AT_FDCWD, "/proc/self/task/1095211/comm", O_RDWRstrace: 
Process 1095211 attached
  ) = -1 EACCES (Permission non accordée)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1918410/+subscriptions

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

[Touch-packages] [Bug 1887744] Autopkgtest regression report (systemd/245.4-4ubuntu3.6)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (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/focal/update_excuses.html#systemd

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

Title:
  systemd dumps core on starting service: Assertion 'u->instance' failed
  at src/core/load-fragment.c:4798

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  Invalid
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [impact]

  if a non-template service file is created as a symlink to a template
  service file outside the normal unit file paths, systemd will fail
  assertion and crash

  [test case]

  su -
  cat < /crashsystemd@.service
  [Unit]
  Description=Template for instance %i

  [Service]
  ExecStart=/bin/true
  EOF

  cd /etc/systemd/system
  ln -s /crashsystemd@.service crashsystemd.service
  systemctl daemon-reload
  systemctl start crashsystemd

  [regression potential]

  any regression would likely cause a failed assertion and crash, or
  failure to properly parse and/or load a service file that is a symlink

  [scope]

  this is needed in f/g/h

  this is fixed upstream by commit
  3aa57658434e7a95c6000bebb166c31f1c6d051b which is included in
  v248-rc1, so this is not fixed in any release yet

  this was introduced by the changes in commit e8630e69523 which was
  first included in v243, so this bug doesn't exist in b or earlier

  [original description]

  On an Ubuntu 20.04 server, when I started a newly installed systemd
  service 'systemctl start testemail2jira.service', systemd trips on an
  assertion (from journalctl):

  Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed 
at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting.
  Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as 
pid 2906637.
  Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution.

  apport generates a core dump which I trust is attached.

  The server still works, but my terminal keeps showing:

  Failed to get properties: Failed to activate service
  'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

  and pauses for 25s after each command.

  In case it's relevant, the  i was trying to start had just
  been symlinked into /etc/systemd/system/:

  root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service
  lrwxrwxrwx 1 root root 82 Jul 16 13:48 
/etc/systemd/system/testemail2jira.service -> 
/opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service

  File contents:

  [Unit]
  Description=Check that email to %i JIRA works

  [Service]
  #Type=oneshot
  # Note: I keep the config file, testemail2jira.json5 and rsa.* files in 
emailprocessing/, one directory below testemail2jira/, so that they can be 
version-controlled independently.
  # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add 
testemail2jira/ to WorkingDirectory and remove it from the ExecStart command
  WorkingDirectory=/opt/atlassian/%i/current/emailprocessing
  
ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python
 testemail2jira/testemail2jira.py
  User=root

  [Install]
  WantedBy=multi-user.target

  Perhaps the problem is that my service file is a template
  (testemail2jira@.service), but I symlinked it as a regular
  'testemail2jira.service'.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jul 16 14:13:06 2020
  InstallationDate: Installed on 2020-05-27 (49 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 

[Touch-packages] [Bug 1916485] Autopkgtest regression report (systemd/245.4-4ubuntu3.6)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (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/focal/update_excuses.html#systemd

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

Title:
  test -x fails inside shell scripts in containers

Status in docker.io package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  Opinion
Status in libseccomp package in Ubuntu:
  Fix Committed
Status in runc package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  New
Status in libseccomp source package in Xenial:
  New
Status in runc source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in docker.io source package in Bionic:
  New
Status in libseccomp source package in Bionic:
  New
Status in runc source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in docker.io source package in Focal:
  New
Status in libseccomp source package in Focal:
  New
Status in runc source package in Focal:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in docker.io source package in Groovy:
  New
Status in libseccomp source package in Groovy:
  New
Status in runc source package in Groovy:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Released
Status in docker.io source package in Hirsute:
  New
Status in libseccomp source package in Hirsute:
  Fix Committed
Status in runc source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  (SRU template for systemd)

  [impact]

  bash (and some other shells) builtin test command -x operation fails

  [test case]

  on any affected host system, start nspawn container, e.g.:

  $ sudo apt install systemd-container
  $ wget 
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz
  $ mkdir h
  $ cd h
  $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz
  $ sudo systemd-nspawn

  Then from a bash shell, verify if test -x works:

  root@h:~# ls -l /usr/bin/gpg
  -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg
  root@h:~# test -x /usr/bin/gpg || echo "fail"
  fail

  [regression potential]

  any regression would likely occur during a syscall, most likely
  faccessat2(), or during other syscalls.

  [scope]

  this is needed for b/f

  this is fixed upstream by commit
  bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so
  this is fixed in h

  this was pulled into Debian at version 246.2 in commit
  e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g

  in x, the entire systemd seccomp code is completely different and the
  patch doesn't apply, nor does it appear to be needed, as the problem
  doesn't reproduce in a h container under x.

  [other info]

  this needs fixing in libseccomp as well

  [original description]

  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:

  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#

  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail

  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #

  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  

[Touch-packages] [Bug 1891810] Autopkgtest regression report (systemd/245.4-4ubuntu3.6)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (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/focal/update_excuses.html#systemd

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

Title:
  Backport 2.5.1 to fix missing openat2 syscall, causing problems for
  fuse-overlayfs in nspawn containers

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

Bug description:
  [Impact]

  The version of libseccomp2 in X/B/F/G does not know about the openat2
  syscall. As such applications that use libseccomp cannot specify a
  system-call filter against this system-call and so it cannot be
  mediated.

  [Test Plan]

  This can be tested by simply running scmp_sys_resolver from the
  seccomp binary package and specifying this system-call:

  Existing behaviour:

  $ scmp_sys_resolver openat2
  -1

  Expected behaviour:

  $ scmp_sys_resolver openat2
  437

  (Note this value will be different on other architectures)

  [Where problems could occur]

  In version 2.5.1 of libseccomp which adds this new system-call,
  changes were also made in the way the socket system-call is handled by
  libseccomp on PPC platforms - this resulted in a change in the
  expected behaviour and so this has already been noticed and a fix is
  required for the systemd unit tests as a result
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696

  There was also a similar change for s390x but so far no regressions
  have been observed as a result as systemd already expected that
  behaviour from libseccomp, it was only PPC that was missing.

  In the event that a regression is observed however, we can easily
  either patch the affected package to cope with the new behaviour of
  this updated libseccomp since in each case the change in behaviour
  only affects a few system calls on particular architectures, or we can
  revert this update.

  [Other Info]

   * As usual thorough testing of this update has been performed both
  manually via the QA Regression Testing scripts, and via the
  autopkgtest infrastructure against packages in the Ubuntu Security
  Proposed PPA https://launchpad.net/~ubuntu-security-
  proposed/+archive/ubuntu/ppa/ with results seen
  https://people.canonical.com/~platform/security-britney/current/

  I have attached debdiffs of the prepared updates which are also
  sitting in the Ubuntu Security Proposed PPA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1915887] Autopkgtest regression report (systemd/245.4-4ubuntu3.6)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (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/focal/update_excuses.html#systemd

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

Title:
  systemd spams the syslog about lack of native systemd unit file

Status in apport package in Ubuntu:
  Invalid
Status in fam package in Ubuntu:
  Invalid
Status in freeradius package in Ubuntu:
  Invalid
Status in ipfm package in Ubuntu:
  Invalid
Status in n2n package in Ubuntu:
  Invalid
Status in pfm package in Ubuntu:
  Invalid
Status in shadowsocks package in Ubuntu:
  Invalid
Status in sysfsutils package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Invalid
Status in xl2tpd package in Ubuntu:
  Invalid
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [impact]

  systemd spams journal with log messages

  [test case]

  see journalctl output and search for msgs similar to those listed in
  original description below

  [regression potential]

  any regession would likely result in logs incorrectly not logged when
  detecting a problem such as lack of native unit file, or using
  /var/run.

  [scope]

  this is needed in f/g

  this is fixed upstream with commit https://salsa.debian.org/systemd-
  team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from
  debian, which is included in 247.3-2 and later so this is fixed in
  hirsute already (in -proposed package).

  these log messages aren't present in b or earlier so aren't needed in
  x/b

  [original description]

  systemd in hirsute spams the syslog file several times per second
  about services lacking native systemd unit files.  Two things should
  happen.

  1) a systemd unit file ought to be created
  2) systemd should be slowed down with regards to these messages

  Feb 17 02:02:48 ubuntu-devel kernel: [  289.794825] 
systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:49 ubuntu-devel kernel: [  290.165351] 
systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:49 ubuntu-devel kernel: [  291.111278] 
systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:50 ubuntu-devel kernel: [  291.507164] 
systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.

  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386062] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386321] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386742] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386767] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a 
native systemd unit file. Automatically generating a unit file for 
compatibility. Please update 

[Touch-packages] [Bug 1918696] Autopkgtest regression report (systemd/245.4-4ubuntu3.6)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (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/focal/update_excuses.html#systemd

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

Title:
  libseccomp 2.5.1 will break unit tests on ppc

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

Bug description:
  [impact]

  when libseccomp is upgraded to 2.5.1 on all releases, the systemd
  seccomp unit tests will start failing on ppc, as
  RestrictAddressFamilies= will no longer work on that arch.

  However, the systemd.exec man page has stated that
  RestrictAddressFamiles= doesn't work on ppc since before bionic.

  [test case]

  check systemd autopkgtest on ppc, looking at the
  test_restrict_access_familes unit test

  [regression potential]

  any regression would involve the use of RestrictAddressFamilies=,
  either no longer restricting or incorrectly restricting address
  familes.

  [scope]

  this is needed for b/f/g

  this was fixed upstream by commit
  d5923e38bc0e6cf9d7620ed5f1f8606fe7fe1168 which is included in 247, so
  this is fixed in h already

  This isn't needed in x, because it doesn't include upstream commit
  469830d1426a91e0897c321fdc8ee428f0a750c1 which reworked the code to
  switch from seccomp_rule_add to seccomp_rule_add_exact, so systemd
  could handle lack of arch support itself, instead of allowing the 'not
  exact' seccomp syscall to just ignore the call due to lack of arch
  support.

  [other info]

  libseccomp will be updated to 2.5.1 in the near future so this is
  needed before that update

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

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

[Touch-packages] [Bug 1887744] Autopkgtest regression report (systemd/246.6-1ubuntu1.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.3) for groovy 
have finished running.
The following regressions have been reported in tests triggered by the package:

prometheus/2.20.0+ds-1 (amd64)
asterisk/1:16.12.0~dfsg-1 (amd64)
apt/2.1.10ubuntu0.2 (arm64)
flatpak/1.8.2-1ubuntu0.1 (ppc64el)
udisks2/2.9.1-2ubuntu1 (amd64)
gvfs/1.46.1-1ubuntu1 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/groovy/update_excuses.html#systemd

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

Title:
  systemd dumps core on starting service: Assertion 'u->instance' failed
  at src/core/load-fragment.c:4798

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  Invalid
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [impact]

  if a non-template service file is created as a symlink to a template
  service file outside the normal unit file paths, systemd will fail
  assertion and crash

  [test case]

  su -
  cat < /crashsystemd@.service
  [Unit]
  Description=Template for instance %i

  [Service]
  ExecStart=/bin/true
  EOF

  cd /etc/systemd/system
  ln -s /crashsystemd@.service crashsystemd.service
  systemctl daemon-reload
  systemctl start crashsystemd

  [regression potential]

  any regression would likely cause a failed assertion and crash, or
  failure to properly parse and/or load a service file that is a symlink

  [scope]

  this is needed in f/g/h

  this is fixed upstream by commit
  3aa57658434e7a95c6000bebb166c31f1c6d051b which is included in
  v248-rc1, so this is not fixed in any release yet

  this was introduced by the changes in commit e8630e69523 which was
  first included in v243, so this bug doesn't exist in b or earlier

  [original description]

  On an Ubuntu 20.04 server, when I started a newly installed systemd
  service 'systemctl start testemail2jira.service', systemd trips on an
  assertion (from journalctl):

  Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed 
at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting.
  Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as 
pid 2906637.
  Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution.

  apport generates a core dump which I trust is attached.

  The server still works, but my terminal keeps showing:

  Failed to get properties: Failed to activate service
  'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

  and pauses for 25s after each command.

  In case it's relevant, the  i was trying to start had just
  been symlinked into /etc/systemd/system/:

  root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service
  lrwxrwxrwx 1 root root 82 Jul 16 13:48 
/etc/systemd/system/testemail2jira.service -> 
/opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service

  File contents:

  [Unit]
  Description=Check that email to %i JIRA works

  [Service]
  #Type=oneshot
  # Note: I keep the config file, testemail2jira.json5 and rsa.* files in 
emailprocessing/, one directory below testemail2jira/, so that they can be 
version-controlled independently.
  # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add 
testemail2jira/ to WorkingDirectory and remove it from the ExecStart command
  WorkingDirectory=/opt/atlassian/%i/current/emailprocessing
  
ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python
 testemail2jira/testemail2jira.py
  User=root

  [Install]
  WantedBy=multi-user.target

  Perhaps the problem is that my service file is a template
  (testemail2jira@.service), but I symlinked it as a regular
  'testemail2jira.service'.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jul 16 14:13:06 2020
  InstallationDate: Installed on 2020-05-27 (49 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit 

[Touch-packages] [Bug 1915887] Autopkgtest regression report (systemd/246.6-1ubuntu1.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.3) for groovy 
have finished running.
The following regressions have been reported in tests triggered by the package:

prometheus/2.20.0+ds-1 (amd64)
asterisk/1:16.12.0~dfsg-1 (amd64)
apt/2.1.10ubuntu0.2 (arm64)
flatpak/1.8.2-1ubuntu0.1 (ppc64el)
udisks2/2.9.1-2ubuntu1 (amd64)
gvfs/1.46.1-1ubuntu1 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/groovy/update_excuses.html#systemd

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

Title:
  systemd spams the syslog about lack of native systemd unit file

Status in apport package in Ubuntu:
  Invalid
Status in fam package in Ubuntu:
  Invalid
Status in freeradius package in Ubuntu:
  Invalid
Status in ipfm package in Ubuntu:
  Invalid
Status in n2n package in Ubuntu:
  Invalid
Status in pfm package in Ubuntu:
  Invalid
Status in shadowsocks package in Ubuntu:
  Invalid
Status in sysfsutils package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Invalid
Status in xl2tpd package in Ubuntu:
  Invalid
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [impact]

  systemd spams journal with log messages

  [test case]

  see journalctl output and search for msgs similar to those listed in
  original description below

  [regression potential]

  any regession would likely result in logs incorrectly not logged when
  detecting a problem such as lack of native unit file, or using
  /var/run.

  [scope]

  this is needed in f/g

  this is fixed upstream with commit https://salsa.debian.org/systemd-
  team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from
  debian, which is included in 247.3-2 and later so this is fixed in
  hirsute already (in -proposed package).

  these log messages aren't present in b or earlier so aren't needed in
  x/b

  [original description]

  systemd in hirsute spams the syslog file several times per second
  about services lacking native systemd unit files.  Two things should
  happen.

  1) a systemd unit file ought to be created
  2) systemd should be slowed down with regards to these messages

  Feb 17 02:02:48 ubuntu-devel kernel: [  289.794825] 
systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:49 ubuntu-devel kernel: [  290.165351] 
systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:49 ubuntu-devel kernel: [  291.111278] 
systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:50 ubuntu-devel kernel: [  291.507164] 
systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.

  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386062] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386321] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386742] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386767] 
systemd-sysv-generator[9909]: SysV service 

[Touch-packages] [Bug 1918696] Autopkgtest regression report (systemd/246.6-1ubuntu1.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.3) for groovy 
have finished running.
The following regressions have been reported in tests triggered by the package:

prometheus/2.20.0+ds-1 (amd64)
asterisk/1:16.12.0~dfsg-1 (amd64)
apt/2.1.10ubuntu0.2 (arm64)
flatpak/1.8.2-1ubuntu0.1 (ppc64el)
udisks2/2.9.1-2ubuntu1 (amd64)
gvfs/1.46.1-1ubuntu1 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/groovy/update_excuses.html#systemd

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

Title:
  libseccomp 2.5.1 will break unit tests on ppc

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

Bug description:
  [impact]

  when libseccomp is upgraded to 2.5.1 on all releases, the systemd
  seccomp unit tests will start failing on ppc, as
  RestrictAddressFamilies= will no longer work on that arch.

  However, the systemd.exec man page has stated that
  RestrictAddressFamiles= doesn't work on ppc since before bionic.

  [test case]

  check systemd autopkgtest on ppc, looking at the
  test_restrict_access_familes unit test

  [regression potential]

  any regression would involve the use of RestrictAddressFamilies=,
  either no longer restricting or incorrectly restricting address
  familes.

  [scope]

  this is needed for b/f/g

  this was fixed upstream by commit
  d5923e38bc0e6cf9d7620ed5f1f8606fe7fe1168 which is included in 247, so
  this is fixed in h already

  This isn't needed in x, because it doesn't include upstream commit
  469830d1426a91e0897c321fdc8ee428f0a750c1 which reworked the code to
  switch from seccomp_rule_add to seccomp_rule_add_exact, so systemd
  could handle lack of arch support itself, instead of allowing the 'not
  exact' seccomp syscall to just ignore the call due to lack of arch
  support.

  [other info]

  libseccomp will be updated to 2.5.1 in the near future so this is
  needed before that update

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

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

[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)

[Matthieu Clemenceau]

** Tags added: fr-1216

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

Title:
  EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic
  Signing Key (2016) 

Status in ubuntu-keyring package in Ubuntu:
  Fix Released
Status in ubuntu-keyring source package in Bionic:
  Fix Committed
Status in ubuntu-keyring source package in Focal:
  Fix Committed
Status in ubuntu-keyring source package in Groovy:
  Fix Committed
Status in ubuntu-keyring source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * Cannot update apt metadata from ddebs.ubuntu.com whilst using
  ubuntu-dbgsym-keyring package

  [Test Plan]

   * Install ubuntu-dbgsym-keyring package
   * Add ddebs.ubuntu.com repository for your release
   * sudo apt update must be successful

   * Install ubuntu-dbgsym-keyring package
   * Install and use `apt-key list` and check that there is no expiry on the 
dbgsym key

  I.e. bad output
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg
  -
  pub   rsa4096 2016-03-21 [SC] [expired: 2021-03-20]
F2ED C64D C5AE E1F6 B9C6  21F0 C8CA B659 5FDF F622
  uid   [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key 
(2016) 

  
  Good output has no [date] in the pub line.

  [Where problems could occur]

   * At the moment the signature was bumped by one year
   * Meaning this issue will occur again in 2022
   * Instead the key must be set to not expire & new round of SRUs issued

  [Other Info]

   * Original bug report

  The public key used by the debugging symbols repository
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu-
  dbgsym-keyring expired.

  $ apt policy ubuntu-dbgsym-keyring
  ubuntu-dbgsym-keyring:
    Installed: 2020.02.11.2
    Candidate: 2020.02.11.2
    Version table:
   *** 2020.02.11.2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status
  $ gpg --no-default-keyring --keyring 
/usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg
  -
  pub   rsa4096 2016-03-21 [SC] [expired: 2021-03-20]
    F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622
  uid   [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key 
(2016) 

  Error message on "apt update":

  E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not 
signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ddebs.ubuntu.com bionic Release: The following 
signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive 
Automatic Signing Key (2016) 
  E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following 
signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive 
Automatic Signing Key (2016) 
  E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not 
signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions

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

[Touch-packages] [Bug 388605] Re: [MIR] rsyslog

[Andreas Hasenack]

Actually, Christian didn't explicitly ack the stable releases in that
comment (but he did in the MPs I raised for the seed changes). I'll ask
him tomorrow to flip the statuses.

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

Title:
  [MIR] rsyslog

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  New
Status in rsyslog source package in Focal:
  New
Status in rsyslog source package in Groovy:
  New
Status in rsyslog source package in Hirsute:
  Fix Released

Bug description:
  Binary package hint: rsyslog

  We want to make rsyslog the new default syslogger.

  See https://wiki.ubuntu.com/MainInclusionReport/rsyslog

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

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

[Touch-packages] [Bug 388605] Re: [MIR] rsyslog

[Andreas Hasenack]

Given Christian's comments in comment #6, and the fact that the seed
changes were done, I'm going to mark the tasks for the stable releases
as "fix committed"

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

Title:
  [MIR] rsyslog

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  New
Status in rsyslog source package in Focal:
  New
Status in rsyslog source package in Groovy:
  New
Status in rsyslog source package in Hirsute:
  Fix Released

Bug description:
  Binary package hint: rsyslog

  We want to make rsyslog the new default syslogger.

  See https://wiki.ubuntu.com/MainInclusionReport/rsyslog

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

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

[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)

[Brian Murray]

Setting to verification-done for Focal.

(focal-amd64)root@impulse:/home/bdmurray/source-trees/error-tracker-deployment/trunk#
 apt-get update
...
Reading package lists... Done
W: GPG error: http://ddebs.ubuntu.com focal Release: The following signatures 
were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol A
rchive Automatic Signing Key (2016) 
E: The repository 'http://ddebs.ubuntu.com focal Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.
W: GPG error: http://ddebs.ubuntu.com focal-updates Release: The following 
signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug 
Symbol Archive Automatic Signing Key (2016) 
E: The repository 'http://ddebs.ubuntu.com focal-updates Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.
W: GPG error: http://ddebs.ubuntu.com focal-proposed Release: The following 
signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug
 Symbol Archive Automatic Signing Key (2016) 
E: The repository 'http://ddebs.ubuntu.com focal-proposed Release' is not 
signed.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.  
(focal-amd64)root@impulse:/home/bdmurray/source-trees/error-tracker-deployment/trunk#
 apt-get install ubuntu-dbgsym-keyring
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  ubuntu-dbgsym-keyring
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/6956 B of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 10155 files and directories currently installed.)
Preparing to unpack .../ubuntu-dbgsym-keyring_2020.02.11.4_all.deb ...
Unpacking ubuntu-dbgsym-keyring (2020.02.11.4) over (2020.02.11.2) ...
Setting up ubuntu-dbgsym-keyring (2020.02.11.4) ...
(focal-amd64)root@impulse:/home/bdmurray/source-trees/error-tracker-deployment/trunk#
 apt-get update
...
Get:20 http://ddebs.ubuntu.com focal-proposed/universe amd64 Packages [41.3 kB]
Fetched 5486 kB in 9s (623 kB/s)
Reading package lists... Done


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

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

Title:
  EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic
  Signing Key (2016) 

Status in ubuntu-keyring package in Ubuntu:
  Fix Released
Status in ubuntu-keyring source package in Bionic:
  Fix Committed
Status in ubuntu-keyring source package in Focal:
  Fix Committed
Status in ubuntu-keyring source package in Groovy:
  Fix Committed
Status in ubuntu-keyring source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * Cannot update apt metadata from ddebs.ubuntu.com whilst using
  ubuntu-dbgsym-keyring package

  [Test Plan]

   * Install ubuntu-dbgsym-keyring package
   * Add ddebs.ubuntu.com repository for your release
   * sudo apt update must be successful

   * Install ubuntu-dbgsym-keyring package
   * Install and use `apt-key list` and check that there is no expiry on the 
dbgsym key

  I.e. bad output
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg
  -
  pub   rsa4096 2016-03-21 [SC] [expired: 2021-03-20]
F2ED C64D C5AE E1F6 B9C6  21F0 C8CA B659 5FDF F622
  uid   [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key 
(2016) 

  
  Good output has no [date] in the pub line.

  [Where problems could occur]

   * At the moment the signature was bumped by one year
   * Meaning this issue will occur again in 2022
   * Instead the key must be set to not expire & new round of SRUs issued

  [Other Info]

   * Original bug report

  The public key used by the debugging symbols repository
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu-
  dbgsym-keyring expired.

  $ apt policy ubuntu-dbgsym-keyring
  ubuntu-dbgsym-keyring:
    Installed: 2020.02.11.2
    Candidate: 2020.02.11.2
    Version table:
   *** 2020.02.11.2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status
  $ gpg --no-default-keyring --keyring 
/usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg
  -
  pub   rsa4096 2016-03-21 [SC] [expired: 

[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)

[Brian Murray]

I tested this again in the Ubuntu Error Tracker using ubuntu-dbgsym-
keyring version 2018.09.18.1~18.04.2 and retracing started working
again.

2021-03-30 
19:11:42,253:21370:140207348864832:INFO:root:64b7ba98-918a-11eb-8a05-fa163e7a7275:swift:Processing.
2021-03-30 
19:11:42,389:21370:140207348864832:INFO:root:64b7ba98-918a-11eb-8a05-fa163e7a7275:swift:Decompressing
 to /tmp/tmpWpOfew-swift.64b
7ba98-918a-11eb-8a05-fa163e7a7275.oopsid.core
2021-03-30 
19:11:42,527:21370:140207348864832:INFO:root:64b7ba98-918a-11eb-8a05-fa163e7a7275:swift:Retracing
 64b7ba98-918a-11eb-8a05-fa163e7
a7275:swift with sandbox-dir /srv/daisy.staging.ubuntu.com/devel/cache/Ubuntu 
21.04/cache-bryjaH/sandbox with cache /srv/daisy.staging.ubunt
u.com/devel/cache/Ubuntu 21.04/cache-bryjaH/cache
2021-03-30 
19:11:46,738:21370:140207348864832:INFO:root:64b7ba98-918a-11eb-8a05-fa163e7a7275:swift:Apport's
 return code was 1.
2021-03-30 
19:11:46,738:21370:140207348864832:INFO:root:64b7ba98-918a-11eb-8a05-fa163e7a7275:swift:ERROR:
 W:Download is performed unsandboxe
d as root as file '/srv/daisy.staging.ubuntu.com/devel/cache/Ubuntu 
21.04/cache-bryjaH/cache/Ubuntu 21.04/apt/var/lib/apt/lists/partial/arch
ive.ubuntu.com_ubuntu_dists_hirsute_InRelease' couldn't be accessed by user 
'_apt'. - pkgAcquire::Run (13: Permission denied), W:GPG error: 
http://ddebs.ubuntu.com hirsute Release: The following signatures were invalid: 
EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Autom
atic Signing Key (2016) , E:The repository 
'http://ddebs.ubuntu.com hirsute Release' is not signed., W:Upda
ting from such a repository can't be done securely, and is therefore disabled 
by default., W:See apt-secure(8) manpage for repository creati
on and user configuration details., W:GPG error: http://ddebs.ubuntu.com 
hirsute-updates Release: The following signatures were invalid: EXP
KEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key 
(2016) , E:The repository 'http:/
/ddebs.ubuntu.com hirsute-updates Release' is not signed.
2021-03-30 
19:11:46,738:21370:140207348864832:INFO:root:64b7ba98-918a-11eb-8a05-fa163e7a7275:swift:Will
 retry (64b7ba98-918a-11eb-8a05-fa163
e7a7275) due to a transient error.
2021-03-30 
19:11:46,740:21370:140207348864832:INFO:root:64b7ba98-918a-11eb-8a05-fa163e7a7275:swift:Processing.
2021-03-30 
19:11:46,931:21370:140207348864832:INFO:root:64b7ba98-918a-11eb-8a05-fa163e7a7275:swift:Decompressing
 to /tmp/tmpn7RBHi-swift.64b
7ba98-918a-11eb-8a05-fa163e7a7275.oopsid.core
2021-03-30 
19:11:47,078:21370:140207348864832:INFO:root:64b7ba98-918a-11eb-8a05-fa163e7a7275:swift:Retracing
 64b7ba98-918a-11eb-8a05-fa163e7
a7275:swift with sandbox-dir /srv/daisy.staging.ubuntu.com/devel/cache/Ubuntu 
21.04/cache-bryjaH/sandbox with cache /srv/daisy.staging.ubunt
u.com/devel/cache/Ubuntu 21.04/cache-bryjaH/cache
2021-03-30 
19:12:48,786:21370:140207348864832:INFO:root:64b7ba98-918a-11eb-8a05-fa163e7a7275:swift:Writing
 back to Cassandra
2021-03-30 
19:12:48,888:21370:140207348864832:INFO:root:64b7ba98-918a-11eb-8a05-fa163e7a7275:swift:Successfully
 retraced.


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

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

Title:
  EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic
  Signing Key (2016) 

Status in ubuntu-keyring package in Ubuntu:
  Fix Released
Status in ubuntu-keyring source package in Bionic:
  Fix Committed
Status in ubuntu-keyring source package in Focal:
  Fix Committed
Status in ubuntu-keyring source package in Groovy:
  Fix Committed
Status in ubuntu-keyring source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * Cannot update apt metadata from ddebs.ubuntu.com whilst using
  ubuntu-dbgsym-keyring package

  [Test Plan]

   * Install ubuntu-dbgsym-keyring package
   * Add ddebs.ubuntu.com repository for your release
   * sudo apt update must be successful

   * Install ubuntu-dbgsym-keyring package
   * Install and use `apt-key list` and check that there is no expiry on the 
dbgsym key

  I.e. bad output
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg
  -
  pub   rsa4096 2016-03-21 [SC] [expired: 2021-03-20]
F2ED C64D C5AE E1F6 B9C6  21F0 C8CA B659 5FDF F622
  uid   [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key 
(2016) 

  
  Good output has no [date] in the pub line.

  [Where problems could occur]

   * At the moment the signature was bumped by one year
   * Meaning this issue will occur again in 2022
   * Instead the key must be set to not expire & new round of SRUs issued

  [Other Info]

   * Original bug report

  The public key used by the debugging symbols repository
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu-
  dbgsym-keyring 

[Touch-packages] [Bug 1868780] Re: [virtio] Xubuntu 20.04 - Blank screen after login

[Paul Donohue]

The problem is that Xfwm's built-in compositor and virgl don't play nice
together.

Work-around: Boot the VM with virgl=off (on the video device) or gl=off
(on the display), run xfwm4-tweaks-settings in the VM, select the
"Compositor" tab, and uncheck "Enable display compositing".  Then shut
down the VM and re-enable virgl.

picom works with Xfwm and doesn't seem to have the same issues, so if
you want a compositor, install/use picom instead of using Xfwm's built-
in compositor: https://wiki.archlinux.org/index.php/Picom

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

Title:
  [virtio] Xubuntu 20.04 - Blank screen after login

Status in lightdm package in Ubuntu:
  New

Bug description:
  Both on Xubuntu 20.04 23rd March and 24th March daily build.
  Using Martin Wimpress QuickEMU setup.
  Installation part of xubuntu is working fine.
  But after install and reboot, you get the login box. I type in the password 
for the user and then just get a black screen and mouse cursor, no other error 
boxes or gui.
  Have tested my QuickEMU setup on ubuntu-mate and do not see this issue, only 
on Xubuntu daily builds do I see this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Mar 24 16:40:12 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  InstallationDate: Installed on 2020-03-24 (0 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   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/8p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=4b1c21e9-1325-435b-9ade-04263b901e6d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/lightdm/+bug/1868780/+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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

[Brian Murray]

Hello Dave, or anyone else affected,

Accepted bluez into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.53-0ubuntu3.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
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.

** Tags removed: verification-done
** 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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048

Title:
  [SRU] Bluetooth won't activate on the pi 400

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

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * Enable the -proposed repository for the release (groovy)
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1921939] [NEW] Create Upstream Repo

[Bryan Quigley]

Public bug reported:

I started investigating this due to software-properties in Debian being
listed as under-maintained per https://mako.cc/copyrighteous
/identifying-underproduced-software

AFAICT the source of truth for this package is in the current Ubuntu
packages.  Would it be possible to make a real upstream repo that both
Debian and Ubuntu can eventually pull from?

Today, the Debian package has no updates for a while and I get that many
of the additions are for Livepatch/other ubuntu specific things. If it's
better for software-properties in Debian to just become it's own thing,
that's a path too.

Related debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661908

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Create Upstream Repo

Status in software-properties package in Ubuntu:
  New

Bug description:
  I started investigating this due to software-properties in Debian
  being listed as under-maintained per https://mako.cc/copyrighteous
  /identifying-underproduced-software

  AFAICT the source of truth for this package is in the current Ubuntu
  packages.  Would it be possible to make a real upstream repo that both
  Debian and Ubuntu can eventually pull from?

  Today, the Debian package has no updates for a while and I get that
  many of the additions are for Livepatch/other ubuntu specific things.
  If it's better for software-properties in Debian to just become it's
  own thing, that's a path too.

  Related debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661908

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1921939/+subscriptions

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

[Touch-packages] [Bug 388605] Re: [MIR] rsyslog

[Steve Beattie]

Ack by the Ubuntu Security team to move rsyslog-gnutls to main, both for
hirsute, and for bionic, focal, and groovy. Thanks!

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

Title:
  [MIR] rsyslog

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  New
Status in rsyslog source package in Focal:
  New
Status in rsyslog source package in Groovy:
  New
Status in rsyslog source package in Hirsute:
  Fix Released

Bug description:
  Binary package hint: rsyslog

  We want to make rsyslog the new default syslogger.

  See https://wiki.ubuntu.com/MainInclusionReport/rsyslog

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

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

[Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list

[udippel]

With respect to #12, I am not sufficiently well versed in rolling back to 18_04 
in order to try once again, as much as I would love to do so and help by 
repeating my earlier steps that lead to the upgrade.
Though, it looks like others have been able to simulate the steps.

Thanks a lot for all the efforts!

Uwe

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

Title:
  interruption of dist-upgrade can leave you next release in
  sources.list

Status in apt package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  New
Status in ubuntu-release-upgrader source package in Bionic:
  New
Status in apt source package in Focal:
  New
Status in ubuntu-release-upgrader source package in Focal:
  New
Status in apt source package in Groovy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Groovy:
  New
Status in apt source package in Hirsute:
  Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  Calling update() or installing packages from apt clients resets their SIGINT 
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have 
set for them.

  In case of ubuntu-release-upgrader, this results in the release
  upgrader being unable to handle interrupts after it did the initial
  update - the default libc handler will run and the program exits.

  [Test plan]

  [[apt]]
  As a standalone test for apt, we can test the following script:

  import apt
  import time

  apt.Cache().update()
  print("WAITING")
  try:
  time.sleep(1)
  except BaseException as e:
  print("Seen", repr(e))
  print("END")

  Pressing Ctrl+C while WAITING is printed should print Seen
  KeyboardInterrupt, and importantly, also the END line.

  [Where problems could occur]
  apt: This specific change removes the two lines that SIG_DFL the signal 
handlers after running scripts. AFAWCT those lines are unnecessary - the code 
that calls it temporarily sets the handlers to SIG_IGN but restores previous 
handlers at the end; it was wrongly refactored decades ago. A regression could 
occur in that those signals will now continue to be ignored if we missed a spot.

  [Original bug report]
  As a long-time-user of ?ubuntu, with apt-get as tool of choice for 
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
  In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu 
version; just all packages including new ones. Version updates had to be 
initiated manually, and I was always asked if I really wanted the new ?ubuntu 
version. Sounds appropriate.

  Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. 
I for one consider this kind of intrusive, though.
  It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a 
number of times earlier; just to *check* if the upgrade was on offer; but this 
is only a guess.

  In *any* case, a pop-up asking "Are you sure? Are you connected
  through an adequate pipe? Are you sitting with full batteries; better
  a power supply?" would be convenient; since I am using my PC for
  urgent duties, and didn't want to fiddle with unexpected upgrade bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Thu Oct  1 11:48:39 2020
  InstallationDate: Installed on 2019-03-14 (566 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
  VarLogDistupgradeAptlog:
   Log time: 2020-09-29 19:44:28.696289
   Log time: 2020-09-29 19:44:33.573481

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

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

[Touch-packages] [Bug 1921766] Re: Output device not remembered after connecting/disconnecting another

[Cody Shepherd]

So I did look at those options, but disabling them did not provide the
experience I was looking for, and required me to do as much or more
manual switching of audio devices.

To be clear, I don't want to disable the functionality that these
options provide. I am happy with the audio switching to hotplug devices
(such as my headphones) automatically when they connect, and I'm happy
with the audio switching to new ports as well. This bug is with the
behavior of switching _back_ to the original device when a hotplug
device disconnects. It should remember the original device, or at least
allow me to set a default to switch back to, instead of deciding for
itself.

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

Title:
  Output device not remembered after connecting/disconnecting another

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 20.10 running pulseaudio version 13.99.2 is my daily driver for
  development work. I run it on a Lenovo X1 Carbon 8th Generation
  connected to dual monitors via a Lenovo dock. Both monitors are
  capable of outputting sound via HDMI.

  I use bluetooth headphones frequently with my Ubuntu 20.10 system, but
  I don't leave them on -- I turn them on and off as needed for Zoom
  calls. When I'm not on a call, however, I prefer to use my laptop's
  speakers for audio -- not my monitor speakers.

  Turning the bluetooth headphones on works fine, they connect and
  pulseaudio correctly identifies the new connection and switches to the
  headphones as the audio device.

  However, when I turn the headphones off, pulseaudio always selects an
  HDMI audio device as the sound device to use, not the internal speaker
  device that I was using prior to turning on the headphones. I must
  manually open Sound Settings and select the speaker device every time
  I turn my headphones off.

  My expectation is that the device I was using prior to connecting the
  headphones is remembered and switched back to by default after I
  disconnect my bluetooth headphones.

  I've tried using the pavucontrol app to disable the HDMI audio
  devices, but the hardware device disable settings are not granular
  enough to let me target the HDMI devices independently of the speaker
  device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1921766/+subscriptions

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

[Touch-packages] [Bug 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii

[Balint Reczey]

** Description changed:

  [Impact]
  
-  * unattended-upgrades --help crashes in apt.systemd.daily script when
+  * unattended-upgrades --help crashes in apt.systemd.daily script when
  locale is not in UTF-8.
  
  [Test Case]
  
  In the fixed case no crash is observed.
  
  rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076
  Creating bb-lp-1806076
  Starting bb-lp-1806076
  rbalint@yogi:~$ lxc shell bb-lp-1806076
  mesg: ttyname failed: No such device
  root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base
  The following package was automatically installed and is no longer required:
    libfreetype6
  Use 'apt autoremove' to remove it.
  The following additional packages will be installed:
    language-pack-ru
  The following NEW packages will be installed:
    language-pack-ru language-pack-ru-base
  0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded.
  Need to get 2310 kB of archives.
  After this operation, 11.8 MB of additional disk space will be used.
  Selecting previously unselected package language-pack-ru-base.
  (Reading database ... 28536 files and directories currently installed.)
  Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ...
  Unpacking language-pack-ru-base (1:18.04+20180712) ...
  Selecting previously unselected package language-pack-ru.
  Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ...
  Unpacking language-pack-ru (1:18.04+20180712) ...
  Setting up language-pack-ru (1:18.04+20180712) ...
  Setting up language-pack-ru-base (1:18.04+20180712) ...
  Generating locales (this might take a while)...
    ru_RU.UTF-8... done
    ru_UA.UTF-8... done
  Generation complete.
  
- root@bb-lp-1806076:~# echo LANG=ru_RU | tee /etc/default/locale 
+ root@bb-lp-1806076:~# echo LANG=ru_RU | tee /etc/default/locale
  LANG=ru_RU
  root@bb-lp-1806076:~#
  /usr/lib/apt/apt.systemd.daily update
  Traceback (most recent call last):
-   File "/usr/bin/unattended-upgrade", line 2171, in 
- (options, args) = parser.parse_args()  # type: ignore
-   File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args
- stop = self._process_args(largs, rargs, values)
-   File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args
- self._process_long_opt(rargs, values)
-   File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt
- option.process(opt, value, values, self)
-   File "/usr/lib/python3.6/optparse.py", line 785, in process
- self.action, self.dest, opt, value, values, parser)
-   File "/usr/lib/python3.6/optparse.py", line 807, in take_action
- parser.print_help()
-   File "/usr/lib/python3.6/optparse.py", line 1647, in print_help
- file.write(self.format_help())
+   File "/usr/bin/unattended-upgrade", line 2171, in 
+ (options, args) = parser.parse_args()  # type: ignore
+   File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args
+ stop = self._process_args(largs, rargs, values)
+   File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args
+ self._process_long_opt(rargs, values)
+   File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt
+ option.process(opt, value, values, self)
+   File "/usr/lib/python3.6/optparse.py", line 785, in process
+ self.action, self.dest, opt, value, values, parser)
+   File "/usr/lib/python3.6/optparse.py", line 807, in take_action
+ parser.print_help()
+   File "/usr/lib/python3.6/optparse.py", line 1647, in print_help
+ file.write(self.format_help())
  UnicodeEncodeError: 'ascii' codec can't encode characters in position 
126-133: ordinal not in range(128)
  
- root@bb-lp-1806076:~# echo LANG=ru_RU.UTF-8 | tee /etc/default/locale 
+ root@bb-lp-1806076:~# echo LANG=ru_RU.UTF-8 | tee /etc/default/locale
  LANG=ru_RU.UTF-8
  root@bb-lp-1806076:~# /usr/lib/apt/apt.systemd.daily update
  root@bb-lp-1806076:~#
  
  [Where problems could occur]
  
- * Nowhere, really. The fix is setting LC_ALL=C.UFT-8 for u-u --help and
+ * Nowhere, really. The fix is setting LC_ALL=C.UTF-8 for u-u --help and
  it is processed by grep then.
- 
  
  [Original Bug Text]
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.6, the problem page at 
https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.
  
  Also seen in:
   * https://errors.ubuntu.com/problem/936bb1c75c4efe018f968a5773b820bcf52c298a

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

Title:
  unattended-upgrade --help 

[Touch-packages] [Bug 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii

[Julian Andres Klode]

I installed 1.6.13 and could verify that the regression wrt --help is
fixed. unattended-upgrades still logged a lot of errors because for some
reason gettext returned utf8 despite being on non-UTF-8 locale, but
that's all from the APT side.

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

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

Title:
  unattended-upgrade --help raises UnicodeEncodeError when stdout
  encoding is ascii

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Won't Fix
Status in apt source package in Xenial:
  New
Status in unattended-upgrades source package in Xenial:
  Won't Fix
Status in apt source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

   * unattended-upgrades --help crashes in apt.systemd.daily script when
  locale is not in UTF-8.

  [Test Case]

  In the fixed case no crash is observed.

  rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076
  Creating bb-lp-1806076
  Starting bb-lp-1806076
  rbalint@yogi:~$ lxc shell bb-lp-1806076
  mesg: ttyname failed: No such device
  root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base
  The following package was automatically installed and is no longer required:
    libfreetype6
  Use 'apt autoremove' to remove it.
  The following additional packages will be installed:
    language-pack-ru
  The following NEW packages will be installed:
    language-pack-ru language-pack-ru-base
  0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded.
  Need to get 2310 kB of archives.
  After this operation, 11.8 MB of additional disk space will be used.
  Selecting previously unselected package language-pack-ru-base.
  (Reading database ... 28536 files and directories currently installed.)
  Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ...
  Unpacking language-pack-ru-base (1:18.04+20180712) ...
  Selecting previously unselected package language-pack-ru.
  Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ...
  Unpacking language-pack-ru (1:18.04+20180712) ...
  Setting up language-pack-ru (1:18.04+20180712) ...
  Setting up language-pack-ru-base (1:18.04+20180712) ...
  Generating locales (this might take a while)...
    ru_RU.UTF-8... done
    ru_UA.UTF-8... done
  Generation complete.

  root@bb-lp-1806076:~# echo LANG=ru_RU | tee /etc/default/locale
  LANG=ru_RU
  root@bb-lp-1806076:~#
  /usr/lib/apt/apt.systemd.daily update
  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 2171, in 
  (options, args) = parser.parse_args()  # type: ignore
    File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args
  stop = self._process_args(largs, rargs, values)
    File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args
  self._process_long_opt(rargs, values)
    File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt
  option.process(opt, value, values, self)
    File "/usr/lib/python3.6/optparse.py", line 785, in process
  self.action, self.dest, opt, value, values, parser)
    File "/usr/lib/python3.6/optparse.py", line 807, in take_action
  parser.print_help()
    File "/usr/lib/python3.6/optparse.py", line 1647, in print_help
  file.write(self.format_help())
  UnicodeEncodeError: 'ascii' codec can't encode characters in position 
126-133: ordinal not in range(128)

  root@bb-lp-1806076:~# echo LANG=ru_RU.UTF-8 | tee /etc/default/locale
  LANG=ru_RU.UTF-8
  root@bb-lp-1806076:~# /usr/lib/apt/apt.systemd.daily update
  root@bb-lp-1806076:~#

  [Where problems could occur]

  * Nowhere, really. The fix is setting LC_ALL=C.UTF-8 for u-u --help
  and it is processed by grep then.

  [Original Bug Text]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.6, the problem page at 
https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Also seen in:
   * https://errors.ubuntu.com/problem/936bb1c75c4efe018f968a5773b820bcf52c298a

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

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

[Touch-packages] [Bug 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii

[Julian Andres Klode]

Log:

+ /usr/lib/apt/apt.systemd.daily lock_is_held update



--- Logging error ---   



Traceback (most recent call last):  



  File "/usr/lib/python3.6/logging/__init__.py", line 996, in emit  



stream.write(msg)   



UnicodeEncodeError: 'ascii' codec can't encode characters in position 29-34: 
ordinal not in range(128)   

   
Call stack: 



  File "/usr/bin/unattended-upgrade", line 2193, in 



sys.exit(main(options)) 



  File "/usr/bin/unattended-upgrade", line 1750, in main



" ".join(blacklisted_pkgs)) 



Message: '\u041f\u0430\u043a\u0435\u0442\u044b \u0432 
\u0447\u0451\u0440\u043d\u043e\u043c \u0441\u043f\u0438\u0441\u043a\u0435 
\u0438\u0437\u043d\u0430\u0447\u0430\u043b\u044c\u043d\u043e: %s'   

Arguments: ('',)



--- Logging error ---   



Traceback (most recent call last):  



  File "/usr/lib/python3.6/logging/__init__.py", line 996, in emit  



stream.write(msg)   



UnicodeEncodeError: 'ascii' codec can't encode characters in position 29-39: 
ordinal not in range(128)  

[Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list

[Julian Andres Klode]

I checked do-release-upgrade -d before upgrading apt, and pressing
Ctrl+C at the prompt for conforming changes left hirsute in
sources.list.

I upgraded to apt 2.1.10ubuntu0.3 from proposed, ran it again, and
Ctrl+C now caused the restore code to run:

 Continue [yN]  Details [d]^C
Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree  
Reading state information... Done
=== Command detached from window (Tue Mar 30 15:04:31 2021) ===

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

Title:
  interruption of dist-upgrade can leave you next release in
  sources.list

Status in apt package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  New
Status in ubuntu-release-upgrader source package in Bionic:
  New
Status in apt source package in Focal:
  New
Status in ubuntu-release-upgrader source package in Focal:
  New
Status in apt source package in Groovy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Groovy:
  New
Status in apt source package in Hirsute:
  Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  Calling update() or installing packages from apt clients resets their SIGINT 
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have 
set for them.

  In case of ubuntu-release-upgrader, this results in the release
  upgrader being unable to handle interrupts after it did the initial
  update - the default libc handler will run and the program exits.

  [Test plan]

  [[apt]]
  As a standalone test for apt, we can test the following script:

  import apt
  import time

  apt.Cache().update()
  print("WAITING")
  try:
  time.sleep(1)
  except BaseException as e:
  print("Seen", repr(e))
  print("END")

  Pressing Ctrl+C while WAITING is printed should print Seen
  KeyboardInterrupt, and importantly, also the END line.

  [Where problems could occur]
  apt: This specific change removes the two lines that SIG_DFL the signal 
handlers after running scripts. AFAWCT those lines are unnecessary - the code 
that calls it temporarily sets the handlers to SIG_IGN but restores previous 
handlers at the end; it was wrongly refactored decades ago. A regression could 
occur in that those signals will now continue to be ignored if we missed a spot.

  [Original bug report]
  As a long-time-user of ?ubuntu, with apt-get as tool of choice for 
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
  In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu 
version; just all packages including new ones. Version updates had to be 
initiated manually, and I was always asked if I really wanted the new ?ubuntu 
version. Sounds appropriate.

  Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. 
I for one consider this kind of intrusive, though.
  It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a 
number of times earlier; just to *check* if the upgrade was on offer; but this 
is only a guess.

  In *any* case, a pop-up asking "Are you sure? Are you connected
  through an adequate pipe? Are you sitting with full batteries; better
  a power supply?" would be convenient; since I am using my PC for
  urgent duties, and didn't want to fiddle with unexpected upgrade bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Thu Oct  1 11:48:39 2020
  InstallationDate: Installed on 2019-03-14 (566 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
  VarLogDistupgradeAptlog:
   Log time: 2020-09-29 19:44:28.696289
   Log time: 2020-09-29 19:44:33.573481

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

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

[Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list

[Julian Andres Klode]

The small simple script also worked with the proposed version:

# python3 a.py
WAITING
^CSeen KeyboardInterrupt()
END


** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-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/1898026

Title:
  interruption of dist-upgrade can leave you next release in
  sources.list

Status in apt package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  New
Status in ubuntu-release-upgrader source package in Bionic:
  New
Status in apt source package in Focal:
  New
Status in ubuntu-release-upgrader source package in Focal:
  New
Status in apt source package in Groovy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Groovy:
  New
Status in apt source package in Hirsute:
  Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  Calling update() or installing packages from apt clients resets their SIGINT 
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have 
set for them.

  In case of ubuntu-release-upgrader, this results in the release
  upgrader being unable to handle interrupts after it did the initial
  update - the default libc handler will run and the program exits.

  [Test plan]

  [[apt]]
  As a standalone test for apt, we can test the following script:

  import apt
  import time

  apt.Cache().update()
  print("WAITING")
  try:
  time.sleep(1)
  except BaseException as e:
  print("Seen", repr(e))
  print("END")

  Pressing Ctrl+C while WAITING is printed should print Seen
  KeyboardInterrupt, and importantly, also the END line.

  [Where problems could occur]
  apt: This specific change removes the two lines that SIG_DFL the signal 
handlers after running scripts. AFAWCT those lines are unnecessary - the code 
that calls it temporarily sets the handlers to SIG_IGN but restores previous 
handlers at the end; it was wrongly refactored decades ago. A regression could 
occur in that those signals will now continue to be ignored if we missed a spot.

  [Original bug report]
  As a long-time-user of ?ubuntu, with apt-get as tool of choice for 
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
  In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu 
version; just all packages including new ones. Version updates had to be 
initiated manually, and I was always asked if I really wanted the new ?ubuntu 
version. Sounds appropriate.

  Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. 
I for one consider this kind of intrusive, though.
  It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a 
number of times earlier; just to *check* if the upgrade was on offer; but this 
is only a guess.

  In *any* case, a pop-up asking "Are you sure? Are you connected
  through an adequate pipe? Are you sitting with full batteries; better
  a power supply?" would be convenient; since I am using my PC for
  urgent duties, and didn't want to fiddle with unexpected upgrade bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Thu Oct  1 11:48:39 2020
  InstallationDate: Installed on 2019-03-14 (566 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
  VarLogDistupgradeAptlog:
   Log time: 2020-09-29 19:44:28.696289
   Log time: 2020-09-29 19:44:33.573481

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

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

[Touch-packages] [Bug 1877987] Re: apt search coredumping

[Julian Andres Klode]

Can't exactly verify as we did not get another reproducer, but marking
it as verified anyway

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

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

Title:
  apt search coredumping

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

Bug description:
  [Impact]
  Search sometimes crashes if no translated description is available, as the 
translated description object was used without a check as to whether it exists.

  [Test case]
  No reproducer available at the moment.

  
  [Where problems could occur]
  In search command only, and only when looking at descriptions

  [Original bug report]
  root@citoyx:/var/crash# apt search jdk
  Sorting... Done
  Segmentation fault (core dumped)

  May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 
7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in 
libapt-pkg.so.6.0.0[7f6309bb5000+147000]
  May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 
48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 
08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 
8d 04 c2 0f

  root@citoyx:/var/crash# cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  apt search is coredumping
  While apt install/upgrade/update is running fine

  crash file in attachment.

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

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

[Touch-packages] [Bug 1916725] Re: Protected/Important packages are not deconfigured, require Force-LoopBreak

[Julian Andres Klode]

** Tags removed: verification-donefocal
** Tags added: verification-done-focal

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

Title:
  Protected/Important packages are not deconfigured, require Force-
  LoopBreak

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

Bug description:
  [Impact]
  If a package that is Protected: yes (or Important: yes), or one of it's 
dependencies, is involved in a dependency loop with Breaks, APT requires 
APT::Force-LoopBreak instead of resolving the situation directly.

  On focal, we also introduce the actual support for protected packages
  to enable upgrading to later releases more easily (in case a protected
  package needs to be removed during the upgrade), and to make the
  backport more similar to main.

  [Test plan]
  Run the integration test suite (the autopkgtest) :)

  Our test suite covers the tests for both Breaks and Conflicts.

  Breaks:

  protected-sysvinit (= 1) without dependencies is installed
  protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv
  protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2)

  Test: Install protected-sysvinit (= 2)
  Expected result: Unpacking protected-sysvinit (= 2) deconfigures 
protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit 
(= 2) and end up with a working system.

  Conflicts: As for Breaks, but the Conflicts will remove the package
  temporarily, requiring the use of APT::Force-LoopBreak option.

  For focal, we also do have a test to check that the Protected field is
  being used.

  [Where problems could occur]
  We now allow dpkg to automatically deconfigure protected packages. This 
should just make them behave like normal packages to APT's eye, but bugs I 
guess could occur somewhere in the APT/dpkg interaction (this only applies to 
releases with Protected support in dpkg, Important is not affected, it's always 
been "normal" for dpkg).

  During development, we accidentally simplified the patch so much that
  Conflicts did not require Force-LoopBreak for temporary removal. We
  fixed that, but it points out that there is a place where the loop
  break check happens that is a potential regression place.

  On focal, we pass additional flags to dpkg that focal's dpkg does not
  understand, however, we only do that if dpkg asserts it does that, so
  in practice, this should all work fine and the code path will only be
  taken with >=groovy dpkg.

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

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

[Touch-packages] [Bug 1918907] Re: Default Acquire::AllowReleaseInfoChange::Suite to "true"

[Julian Andres Klode]

Oops, of course apt's test passed, hence verification done :)

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

Title:
  Default Acquire::AllowReleaseInfoChange::Suite to "true"

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

Bug description:
  [Impact]
  APT 1.6-2.0 deny third-party repositories from changing their Suite value. 
This change was reverted in later apt releases, and will be reverted in 1.8 in 
Debian as well, so for consistency, we want to push that change to stable

  [Test plan]
  We added test cases to our extensive integration test suite run by 
autopkgtest.

  [Where problems could occur]
  It's hard to imagine anything here, we simply turn the flag for allowed from 
false to true. We even add tests for Suite changes :)

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

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

[Touch-packages] [Bug 1918907] Re: Default Acquire::AllowReleaseInfoChange::Suite to "true"

[Julian Andres Klode]

apt's tests failed, I believe the regressions are just intermittent
unrelated issues.

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal
** Tags added: verification-done verification-done-bionic 
verification-done-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/1918907

Title:
  Default Acquire::AllowReleaseInfoChange::Suite to "true"

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

Bug description:
  [Impact]
  APT 1.6-2.0 deny third-party repositories from changing their Suite value. 
This change was reverted in later apt releases, and will be reverted in 1.8 in 
Debian as well, so for consistency, we want to push that change to stable

  [Test plan]
  We added test cases to our extensive integration test suite run by 
autopkgtest.

  [Where problems could occur]
  It's hard to imagine anything here, we simply turn the flag for allowed from 
false to true. We even add tests for Suite changes :)

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

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

[Touch-packages] [Bug 1878969] Autopkgtest regression report (systemd/229-4ubuntu21.30)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.30) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

upstart/unknown (armhf)
umockdev/0.8.11-2 (i386)
systemd/229-4ubuntu21.30 (amd64)
linux-aws-hwe/unknown (arm64)
snapd/2.48.3 (i386)
gvfs/1.28.2-1ubuntu1~16.04.3 (amd64)
cloudprint/0.14-5 (ppc64el)
nplan/0.32~16.04.7 (ppc64el, amd64)
cups/2.1.3-4ubuntu0.11 (ppc64el)
apt/1.2.32ubuntu0.2 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#systemd

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

Title:
  time-epoch never changes in SRUs

Status in ubuntu-core-initramfs:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * Systems without hwclock come up with a fixed time epoch which is not 
updated in SRUs
   * Ideally booting with a newer built of systemd should move time epoch to be 
at least when systemd was last built. For example to the value of 
SOURCE_DATE_EPOCH.

  [Test Case]

   * Boot without network NTP or hwclock
   * Observe that the epoch is the same as the time when NEWS entry in the 
systemd source code was last touched.
   * Boot newer update of systemd, observe that the time epoch is at least 2020

  [Regression Potential]

   * Bad epoch, may result in unable to perform TLS connections,
  validated GPG signatures, and snapd assertions. Changing epoch to be
  more recent is desired. Some machines may rely on the fact that
  "bionic" without hwclock always comes up in year 2018. But in practice
  that is incorrect thing to do.

  [Other Info]
   
   * By default

  option('time-epoch', type : 'integer', value : '-1',
 description : 'time epoch for time clients')

  in systemd is set to the modification time of the NEW entry
  time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()

  If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value
  to be compliant with the https://reproducible-
  builds.org/docs/timestamps/ specification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+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 1913763] Autopkgtest regression report (systemd/229-4ubuntu21.30)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.30) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

upstart/unknown (armhf)
umockdev/0.8.11-2 (i386)
systemd/229-4ubuntu21.30 (amd64)
linux-aws-hwe/unknown (arm64)
snapd/2.48.3 (i386)
gvfs/1.28.2-1ubuntu1~16.04.3 (amd64)
cloudprint/0.14-5 (ppc64el)
nplan/0.32~16.04.7 (ppc64el, amd64)
cups/2.1.3-4ubuntu0.11 (ppc64el)
apt/1.2.32ubuntu0.2 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#systemd

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

Title:
  hyperv: unable to distinguish PTP devices

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

Bug description:
  [impact]

  the /dev/ptp0 device for a hyperv instance may not be the correct,
  hyperv-provided, ptp device.

  [test case]

  on some hyperv instance types, particularly those that might contain
  passthrough network card(s) that also provide ptp, the first ptp
  device may not be the correct one to use for ptp, e.g. there may be
  multiple ones:

  $ ls /dev/ptp*
  /dev/ptp0 /dev/ptp1
  $ cat /sys/class/ptp/ptp0/clock_name
  hyperv
  $ cat /sys/class/ptp/ptp1/clock_name
  mlx5_p2p

  the order can change across boots, so a consistent way of addressing
  the hyperv-provided one is needed

  [regression potential]

  any regression would involve failure to properly create the ptp
  symlink, or other failure while udev is processing newly detected ptp
  device(s)

  [scope]

  this is needed in all releases

  this was fixed upstream with the commit
  32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
  any release

  [original description]

  Hyperv provides a PTP device. On system with multiple PTP devices,
  services like Chrony don't have a way to know which one is which.

  We would like to have a udev rule to create a symlink to the hyperv
  clock. This way, services could be configured to always use this clock
  no matter if it is ptp0, ptp1, etc..

  For example:

  ```
  SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1886728] Re: OpenVPN OTP replaces the ordinary password

[Thomas M Steenholdt]

This is still an issue in Ubuntu 21.04 (development, as of March 30,
2021)

It looks like people have been complaining about this for years, and
while some people have tried to fix it, those fixes never made it in.
Surely it must be of some type of urgency to support 2FA one-time
passwords in the primary network management solution in Ubuntu?

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

Title:
  OpenVPN OTP replaces the ordinary password

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  When OpenVPN has One-time password (OTP) enabled, and the user
  connects, a dialog asks the user to enter the One-time password (OTP)
  and press ok. This action replaces the ordinary "long term" password
  with the OTP. This causes annoyance as the next login will fail
  because the password is wrong and the user has to enter both the
  password and the OTP the next time they log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  8 01:07:18 2020
  InstallationDate: Installed on 2020-03-23 (106 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to focal on 2020-05-11 (57 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1886728/+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 1891810] Autopkgtest regression report (libseccomp/2.5.1-1ubuntu1~20.10.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted libseccomp (2.5.1-1ubuntu1~20.10.1) for 
groovy have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/246.6-1ubuntu1.2 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/groovy/update_excuses.html#libseccomp

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

Title:
  Backport 2.5.1 to fix missing openat2 syscall, causing problems for
  fuse-overlayfs in nspawn containers

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

Bug description:
  [Impact]

  The version of libseccomp2 in X/B/F/G does not know about the openat2
  syscall. As such applications that use libseccomp cannot specify a
  system-call filter against this system-call and so it cannot be
  mediated.

  [Test Plan]

  This can be tested by simply running scmp_sys_resolver from the
  seccomp binary package and specifying this system-call:

  Existing behaviour:

  $ scmp_sys_resolver openat2
  -1

  Expected behaviour:

  $ scmp_sys_resolver openat2
  437

  (Note this value will be different on other architectures)

  [Where problems could occur]

  In version 2.5.1 of libseccomp which adds this new system-call,
  changes were also made in the way the socket system-call is handled by
  libseccomp on PPC platforms - this resulted in a change in the
  expected behaviour and so this has already been noticed and a fix is
  required for the systemd unit tests as a result
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696

  There was also a similar change for s390x but so far no regressions
  have been observed as a result as systemd already expected that
  behaviour from libseccomp, it was only PPC that was missing.

  In the event that a regression is observed however, we can easily
  either patch the affected package to cope with the new behaviour of
  this updated libseccomp since in each case the change in behaviour
  only affects a few system calls on particular architectures, or we can
  revert this update.

  [Other Info]

   * As usual thorough testing of this update has been performed both
  manually via the QA Regression Testing scripts, and via the
  autopkgtest infrastructure against packages in the Ubuntu Security
  Proposed PPA https://launchpad.net/~ubuntu-security-
  proposed/+archive/ubuntu/ppa/ with results seen
  https://people.canonical.com/~platform/security-britney/current/

  I have attached debdiffs of the prepared updates which are also
  sitting in the Ubuntu Security Proposed PPA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1891486] Re: vim ftbfs in focal (armhf, ppc64el)

[Lukas Märdian]

I'm marking this WONTFIX as both builds have passed on retry.

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

** Changed in: vim (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  vim ftbfs in focal (armhf, ppc64el)

Status in vim package in Ubuntu:
  Won't Fix
Status in vim source package in Focal:
  Won't Fix

Bug description:
  seen in a focal test rebuild:
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19801040
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19801038

  ---
  Executed:  2257 Tests
   Skipped:31 Tests
FAILED: 1 Tests

  
  Failures: 
From test_debugger.vim:
Found errors in Test_Debugger():
function 
RunTheTest[40]..Test_Debugger[157]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..59
 line 1: Expected 'No breakpoints defined' but got 'cmd: echo Foo()'
function 
RunTheTest[40]..Test_Debugger[185]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..71
 line 1: Expected '19' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[188]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..72
 line 1: Expected 'E161: Breakpoint not found: 2' but got '~\[  occurs 74 
times]'
function 
RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..73
 line 1: Expected 'Entering Debug mode.  Type "cont" to continue.' but got '~\[ 
 occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..74
 line 1: Expected 'function Bazz' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..75
 line 1: Expected 'line 2: let var1 = 3 + a:var' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[199]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..76
 line 1: Expected '  3  func Bazz  line 2' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[199]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..77
 line 1: Expected '  4  expr var3' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..78
 line 1: Expected 'Breakpoint in "Bazz" line 5' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..79
 line 1: Expected 'Oldval = "''another var''"' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..80
 line 1: Expected 'Newval = "''value2''"' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..81
 line 1: Expected 'function Bazz' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..82
 line 1: Expected 'line 5: catch' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[208]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..83
 line 1: Expected 'No breakpoints defined' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..84
 line 1: Expected 'Error detected while processing function Bazz:' but got '~\[ 
 occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..85
 line 1: Expected 'line5:' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..86
 line 1: Expected 'E475: Invalid argument: abcd' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[215]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..87
 line 1: Expected 'E475: Invalid argument: func' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[216]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..88
 line 1: Expected 'E475: Invalid argument: func 2' but got '~\[  occurs 74 
times]'
function 
RunTheTest[40]..Test_Debugger[217]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..89
 line 1: Expected 'E475: Invalid argument: func a()' but got '~\[  occurs 74 
times]'
function 
RunTheTest[40]..Test_Debugger[218]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..90
 line 1: Expected 'E475: Invalid argument: abcd' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[219]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..91
 line 1: Expected 'E475: Invalid 

[Touch-packages] [Bug 1916485] Autopkgtest regression report (systemd/237-3ubuntu10.46)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.46) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.4/5.4.0-71.79~18.04.1 (i386)
polkit-qt-1/unknown (i386)
openssh/1:7.6p1-4ubuntu0.3 (ppc64el, arm64, s390x, i386, amd64, armhf)
systemd/237-3ubuntu10.46 (amd64)
linux-hwe-5.0/5.0.0-65.71 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

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

Title:
  test -x fails inside shell scripts in containers

Status in docker.io package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  Opinion
Status in libseccomp package in Ubuntu:
  Fix Committed
Status in runc package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  New
Status in libseccomp source package in Xenial:
  New
Status in runc source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in docker.io source package in Bionic:
  New
Status in libseccomp source package in Bionic:
  New
Status in runc source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in docker.io source package in Focal:
  New
Status in libseccomp source package in Focal:
  New
Status in runc source package in Focal:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in docker.io source package in Groovy:
  New
Status in libseccomp source package in Groovy:
  New
Status in runc source package in Groovy:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Released
Status in docker.io source package in Hirsute:
  New
Status in libseccomp source package in Hirsute:
  Fix Committed
Status in runc source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  (SRU template for systemd)

  [impact]

  bash (and some other shells) builtin test command -x operation fails

  [test case]

  on any affected host system, start nspawn container, e.g.:

  $ sudo apt install systemd-container
  $ wget 
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz
  $ mkdir h
  $ cd h
  $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz
  $ sudo systemd-nspawn

  Then from a bash shell, verify if test -x works:

  root@h:~# ls -l /usr/bin/gpg
  -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg
  root@h:~# test -x /usr/bin/gpg || echo "fail"
  fail

  [regression potential]

  any regression would likely occur during a syscall, most likely
  faccessat2(), or during other syscalls.

  [scope]

  this is needed for b/f

  this is fixed upstream by commit
  bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so
  this is fixed in h

  this was pulled into Debian at version 246.2 in commit
  e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g

  in x, the entire systemd seccomp code is completely different and the
  patch doesn't apply, nor does it appear to be needed, as the problem
  doesn't reproduce in a h container under x.

  [other info]

  this needs fixing in libseccomp as well

  [original description]

  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:

  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#

  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail

  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #

  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ 

[Touch-packages] [Bug 1891810] Autopkgtest regression report (systemd/237-3ubuntu10.46)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.46) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.4/5.4.0-71.79~18.04.1 (i386)
polkit-qt-1/unknown (i386)
openssh/1:7.6p1-4ubuntu0.3 (ppc64el, arm64, s390x, i386, amd64, armhf)
systemd/237-3ubuntu10.46 (amd64)
linux-hwe-5.0/5.0.0-65.71 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

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

Title:
  Backport 2.5.1 to fix missing openat2 syscall, causing problems for
  fuse-overlayfs in nspawn containers

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

Bug description:
  [Impact]

  The version of libseccomp2 in X/B/F/G does not know about the openat2
  syscall. As such applications that use libseccomp cannot specify a
  system-call filter against this system-call and so it cannot be
  mediated.

  [Test Plan]

  This can be tested by simply running scmp_sys_resolver from the
  seccomp binary package and specifying this system-call:

  Existing behaviour:

  $ scmp_sys_resolver openat2
  -1

  Expected behaviour:

  $ scmp_sys_resolver openat2
  437

  (Note this value will be different on other architectures)

  [Where problems could occur]

  In version 2.5.1 of libseccomp which adds this new system-call,
  changes were also made in the way the socket system-call is handled by
  libseccomp on PPC platforms - this resulted in a change in the
  expected behaviour and so this has already been noticed and a fix is
  required for the systemd unit tests as a result
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696

  There was also a similar change for s390x but so far no regressions
  have been observed as a result as systemd already expected that
  behaviour from libseccomp, it was only PPC that was missing.

  In the event that a regression is observed however, we can easily
  either patch the affected package to cope with the new behaviour of
  this updated libseccomp since in each case the change in behaviour
  only affects a few system calls on particular architectures, or we can
  revert this update.

  [Other Info]

   * As usual thorough testing of this update has been performed both
  manually via the QA Regression Testing scripts, and via the
  autopkgtest infrastructure against packages in the Ubuntu Security
  Proposed PPA https://launchpad.net/~ubuntu-security-
  proposed/+archive/ubuntu/ppa/ with results seen
  https://people.canonical.com/~platform/security-britney/current/

  I have attached debdiffs of the prepared updates which are also
  sitting in the Ubuntu Security Proposed PPA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1918696] Autopkgtest regression report (systemd/237-3ubuntu10.46)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.46) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.4/5.4.0-71.79~18.04.1 (i386)
polkit-qt-1/unknown (i386)
openssh/1:7.6p1-4ubuntu0.3 (ppc64el, arm64, s390x, i386, amd64, armhf)
systemd/237-3ubuntu10.46 (amd64)
linux-hwe-5.0/5.0.0-65.71 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

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

Title:
  libseccomp 2.5.1 will break unit tests on ppc

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

Bug description:
  [impact]

  when libseccomp is upgraded to 2.5.1 on all releases, the systemd
  seccomp unit tests will start failing on ppc, as
  RestrictAddressFamilies= will no longer work on that arch.

  However, the systemd.exec man page has stated that
  RestrictAddressFamiles= doesn't work on ppc since before bionic.

  [test case]

  check systemd autopkgtest on ppc, looking at the
  test_restrict_access_familes unit test

  [regression potential]

  any regression would involve the use of RestrictAddressFamilies=,
  either no longer restricting or incorrectly restricting address
  familes.

  [scope]

  this is needed for b/f/g

  this was fixed upstream by commit
  d5923e38bc0e6cf9d7620ed5f1f8606fe7fe1168 which is included in 247, so
  this is fixed in h already

  This isn't needed in x, because it doesn't include upstream commit
  469830d1426a91e0897c321fdc8ee428f0a750c1 which reworked the code to
  switch from seccomp_rule_add to seccomp_rule_add_exact, so systemd
  could handle lack of arch support itself, instead of allowing the 'not
  exact' seccomp syscall to just ignore the call due to lack of arch
  support.

  [other info]

  libseccomp will be updated to 2.5.1 in the near future so this is
  needed before that update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696/+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 1915502] Re: "systemd --user" fails to start for non-local users

[Launchpad Bug Tracker]

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

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

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

Title:
  "systemd --user" fails to start for non-local users

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-logind fails to start the systemd --user process for non-local
  users on Ubuntu 20.04.  This is a reproducible problem; all our
  systems are displaying the same symptoms.

  The systems are using Kerberos (Active Directory) for authentication,
  and NIS for account meta-data and authorisation (groups)

  A base installation is performed using the server 20.04 ISO image.  No
  additional packages are selected.  Post-install, I run:

  apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd

  I set up the NIS client (supply the default domain name, check ypbind
  is running and ypcat passwd is working)

  I then set up /etc/krb5.conf for kerberos authentication to a domain
  controller, confirm that kinit works and a kerberos ticket is issued.

  I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to
  the end of each.

  /etc/nsswitch.conf is modified to support compat mode, as well as
  systemd:

  passwd: compat systemd
  group:  compat systemd
  shadow: compat

  I can log in remotely via ssh using my NIS account and Kerberos
  credentials.  MY NIS meta-data looks like:

  amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh

  (where UID and GID are replaced with values unique to the
  organisation)

  On login, the following occurs:

  hostname:~> systemctl --user
  Failed to connect to bus: No such file or directory

  I put pam-systemd and systemd-logind into debug mode to get more
  information:

  Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from 
[redact] port 58849 ssh2: RSA SHA256:[redact]
  Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened 
for user amcvey by (uid=0)
  Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call 
sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1 
interface=org.freedesktop.login1.Manager member=CreateSession cookie=2 
reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a
  Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd 
initializing
  Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call 
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40 
reply_cookie=0 signature=s error-name=n/a error-message=n/a
  Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking 
logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user 
desktop= seat= vtnr=0 tty= display= remote=yes remote_user= 
remote_host=10.105.121.110
  Feb 12 09:51:32 myhostname systemd-logind[903]: Got message 
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a 
interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a 
error-message=n/a
  Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session 
limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a 
runtime_max_sec=n/a
  Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call 
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41 
reply_cookie=0 signature=s error-name=n/a error-message=n/a
  Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to 
create session: No such process
  Feb 12 09:51:32 myhostname systemd-logind[903]: Got message 
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a 
interface=n/a member=n/a cookie=14 reply_cookie=41 signature=u error-name=n/a 
error-message=n/a
  Feb 12 09:51:32 myhostname systemd-logind[903]: Unable to connect to 
/run/systemd/userdb/io.systemd.Multiplexer: No such file or directory
  Feb 12 09:51:32 myhostname systemd-logind[903]: n/a: varlink: setting state 
idle-client
  Feb 12 09:51:32 myhostname systemd-logind[903]: 
/run/systemd/userdb/io.systemd.DynamicUser: Sending message: 
{"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"uid":198083,"service":"io.systemd.DynamicUser"}}
  Feb 12 09:51:32 myhostname systemd-logind[903]: 
/run/systemd/userdb/io.systemd.DynamicUser: varlink: changing state idle-client 
→ awaiting-reply
  Feb 12 09:51:32 myhostname systemd-logind[903]: 
/run/systemd/userdb/io.systemd.DynamicUser: New incoming message: 
{"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
  Feb 12 09:51:32 myhostname systemd-logind[903]: 

[Touch-packages] [Bug 1915502] Re: "systemd --user" fails to start for non-local users

[Michael Rutter]

I think I am suffering from the same issue.

I have always run without "UsePAM yes" in sshd_config, but I recently
tried turning it on in order to get XDG_ variables set correctly and
proper systemd sessions for ssh logins.

In 18.04 it worked as expected, but in 20.04 I get

sshd[387766]: pam_systemd(sshd:session): Failed to create session: No
such process

in the logs after turning setting debug on pam_systemd.so

and loginctl does not list the session. I am using NIS, but do not have
the added complication of Kerberos.

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

Title:
  "systemd --user" fails to start for non-local users

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-logind fails to start the systemd --user process for non-local
  users on Ubuntu 20.04.  This is a reproducible problem; all our
  systems are displaying the same symptoms.

  The systems are using Kerberos (Active Directory) for authentication,
  and NIS for account meta-data and authorisation (groups)

  A base installation is performed using the server 20.04 ISO image.  No
  additional packages are selected.  Post-install, I run:

  apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd

  I set up the NIS client (supply the default domain name, check ypbind
  is running and ypcat passwd is working)

  I then set up /etc/krb5.conf for kerberos authentication to a domain
  controller, confirm that kinit works and a kerberos ticket is issued.

  I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to
  the end of each.

  /etc/nsswitch.conf is modified to support compat mode, as well as
  systemd:

  passwd: compat systemd
  group:  compat systemd
  shadow: compat

  I can log in remotely via ssh using my NIS account and Kerberos
  credentials.  MY NIS meta-data looks like:

  amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh

  (where UID and GID are replaced with values unique to the
  organisation)

  On login, the following occurs:

  hostname:~> systemctl --user
  Failed to connect to bus: No such file or directory

  I put pam-systemd and systemd-logind into debug mode to get more
  information:

  Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from 
[redact] port 58849 ssh2: RSA SHA256:[redact]
  Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened 
for user amcvey by (uid=0)
  Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call 
sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1 
interface=org.freedesktop.login1.Manager member=CreateSession cookie=2 
reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a
  Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd 
initializing
  Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call 
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40 
reply_cookie=0 signature=s error-name=n/a error-message=n/a
  Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking 
logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user 
desktop= seat= vtnr=0 tty= display= remote=yes remote_user= 
remote_host=10.105.121.110
  Feb 12 09:51:32 myhostname systemd-logind[903]: Got message 
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a 
interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a 
error-message=n/a
  Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session 
limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a 
runtime_max_sec=n/a
  Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call 
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41 
reply_cookie=0 signature=s error-name=n/a error-message=n/a
  Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to 
create session: No such process
  Feb 12 09:51:32 myhostname systemd-logind[903]: Got message 
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a 
interface=n/a member=n/a cookie=14 reply_cookie=41 signature=u error-name=n/a 
error-message=n/a
  Feb 12 09:51:32 myhostname systemd-logind[903]: Unable to connect to 
/run/systemd/userdb/io.systemd.Multiplexer: No such file or directory
  Feb 12 09:51:32 myhostname systemd-logind[903]: n/a: varlink: setting state 
idle-client
  Feb 12 09:51:32 myhostname systemd-logind[903]: 
/run/systemd/userdb/io.systemd.DynamicUser: Sending message: 
{"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"uid":198083,"service":"io.systemd.DynamicUser"}}
  Feb 12 09:51:32 myhostname 

[Touch-packages] [Bug 1921883] [NEW] Notification badges for app switcher

[Woodrow Shigeru]

Public bug reported:

The Alt+Tab application switcher could benefit from a colored
notification badge. This *could* be a number with the amount of
notifications, but honestly, a simple boolean "has / has no badge" would
suffice already.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-140.144-generic 4.15.18
Uname: Linux 4.15.0-140-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 30 11:43:33 2021
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [17aa:3801]
InstallationDate: Installed on 2018-12-20 (830 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 003: ID 0bda:0821 Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 04f2:b579 Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80TF
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-140-generic 
root=UUID=0f8de3b2-c66e-4eb6-ae0a-f2650fc5b9b5 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 1MCN43WW X64
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo V110-14IAP
dmi.modalias: 
dmi:bvnLENOVO:bvr1MCN43WWX64:bd11/27/2017:svnLENOVO:pn80TF:pvrLenovoV110-14IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV110-14IAP:
dmi.product.family: V110-14IAP
dmi.product.name: 80TF
dmi.product.version: Lenovo V110-14IAP
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu wishlist

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

Title:
  Notification badges for app switcher

Status in xorg package in Ubuntu:
  New

Bug description:
  The Alt+Tab application switcher could benefit from a colored
  notification badge. This *could* be a number with the amount of
  notifications, but honestly, a simple boolean "has / has no badge"
  would suffice already.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-140.144-generic 4.15.18
  Uname: Linux 4.15.0-140-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 30 11:43:33 2021
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [17aa:3801]
  InstallationDate: Installed on 2018-12-20 (830 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 04f2:b579 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80TF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-140-generic 
root=UUID=0f8de3b2-c66e-4eb6-ae0a-f2650fc5b9b5 ro quiet splash 

[Touch-packages] [Bug 1907850] Re: Cache not generated for all translations

[Julian Andres Klode]

autopkgtests for apt have passed, so validation was successful. I'm
confident the autopkgtest failures are unrelated intermittent ones; I've
done some more retries.

** 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1907850

Title:
  Cache not generated for all translations

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  In bug 1161743 we discovered that if a system is configured with multiple 
locales, only the locales of the user who generated the apt-cache will be 
available for translated descriptions.

  [Test case]
  An automated test case has been included as a snippet in  
test/integration/test-bug-49-search-in-all-translations which runs during 
autopkgtest. That's sufficient for validation.

  Manual test:

  # apt install locales-all # get the locale
  # export LANG=sv_SE.UTF-8
  # locale
  LANG=sv_SE.UTF-8
  LANGUAGE=
  LC_CTYPE="sv_SE.UTF-8"
  LC_NUMERIC="sv_SE.UTF-8"
  LC_TIME="sv_SE.UTF-8"
  LC_COLLATE="sv_SE.UTF-8"
  LC_MONETARY="sv_SE.UTF-8"
  LC_MESSAGES="sv_SE.UTF-8"
  LC_PAPER="sv_SE.UTF-8"
  LC_NAME="sv_SE.UTF-8"
  LC_ADDRESS="sv_SE.UTF-8"
  LC_TELEPHONE="sv_SE.UTF-8"
  LC_MEASUREMENT="sv_SE.UTF-8"
  LC_IDENTIFICATION="sv_SE.UTF-8"
  LC_ALL=
  # apt update
  # apt-cache show tasksel | grep Desc
  Description-sv: tool for selecting tasks for installation on Debian systems
  Description-md5: cbbb747708986d11ea77c80b9b038fec
  # apt-cache showpkg tasksel
  Package: tasksel
  Versions:
  3.34ubuntu16 
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages)
   Description Language:
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages
    MD5: cbbb747708986d11ea77c80b9b038fec
   Description Language: sv
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv
    MD5: cbbb747708986d11ea77c80b9b038fec
   Description Language: en
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en
    MD5: cbbb747708986d11ea77c80b9b038fec
  [...]

  So far so good, but now assume the root user actually has C configured
  as locale, and e.g. runs apt-cache show (or apt-daily.service does an
  update):

  root@g:~# rm /var/cache/apt/*.bin
  root@g:~# LANG=C apt-cache  show tasksel
  [...]
  Description-en: tool for selecting tasks for installation on Debian systems
   This package provides 'tasksel', a simple interface for users who
   want to configure their system to perform a specific task.

  root@g:~# apt-cache  showpkg tasksel
  Package: tasksel
  Versions:
  3.34ubuntu16 
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages)
   Description Language:
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages
    MD5: cbbb747708986d11ea77c80b9b038fec
   Description Language: en
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en
    MD5: cbbb747708986d11ea77c80b9b038fec

  This should show the sv locale as well given that it's still around
  (also we are still running with LANG=sv_SE.UTF-8), but it only
  generated the cache with the english language description in here.

  [Where problems could occur]
  People might end up seeing a wrong translation if other code paths are wrong, 
but then they'd already see them if they explicitly configured multiple 
languages and then switched the preferred one.

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

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

[Touch-packages] [Bug 1916050] Re: Invalid base64 for high-bit characters

[Julian Andres Klode]

autopkgtests for apt have passed, so validation was successful. I'm
confident the autopkgtest failures are unrelated intermittent ones; I've
done some more retries.

** 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1916050

Title:
  Invalid base64 for high-bit characters

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  The Base64Encode function incorrectly encodes using char instead of uint8_t, 
leading to characters with the high bit set to be encoded wrongly. This 
function is used for base authentication, and high bits are set for UTF-8 
character sequences, so it's likely affecting people with utf-8 user names and 
passwords and might cause them to be denied access to their https resources 
(though arguably they'd work around that).

  [Test case]
  A unit test has been added that checks that the encoding is correct.

  [Where problems could occur]
  This only affects the base64 encoding function, which is only used for 
quoting user names and passwords in basic auth in http, but it's also exposed 
to library users and like in python-apt, so problems could occur wherever they 
use that base64 encoding function as well.

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

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

[Touch-packages] [Bug 1916725] Re: Protected/Important packages are not deconfigured, require Force-LoopBreak

[Julian Andres Klode]

autopkgtests for apt have passed, so validation was successful. I'm
confident the autopkgtest failures are unrelated intermittent ones; I've
done some more retries.

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

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

Title:
  Protected/Important packages are not deconfigured, require Force-
  LoopBreak

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

Bug description:
  [Impact]
  If a package that is Protected: yes (or Important: yes), or one of it's 
dependencies, is involved in a dependency loop with Breaks, APT requires 
APT::Force-LoopBreak instead of resolving the situation directly.

  On focal, we also introduce the actual support for protected packages
  to enable upgrading to later releases more easily (in case a protected
  package needs to be removed during the upgrade), and to make the
  backport more similar to main.

  [Test plan]
  Run the integration test suite (the autopkgtest) :)

  Our test suite covers the tests for both Breaks and Conflicts.

  Breaks:

  protected-sysvinit (= 1) without dependencies is installed
  protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv
  protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2)

  Test: Install protected-sysvinit (= 2)
  Expected result: Unpacking protected-sysvinit (= 2) deconfigures 
protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit 
(= 2) and end up with a working system.

  Conflicts: As for Breaks, but the Conflicts will remove the package
  temporarily, requiring the use of APT::Force-LoopBreak option.

  For focal, we also do have a test to check that the Protected field is
  being used.

  [Where problems could occur]
  We now allow dpkg to automatically deconfigure protected packages. This 
should just make them behave like normal packages to APT's eye, but bugs I 
guess could occur somewhere in the APT/dpkg interaction (this only applies to 
releases with Protected support in dpkg, Important is not affected, it's always 
been "normal" for dpkg).

  During development, we accidentally simplified the patch so much that
  Conflicts did not require Force-LoopBreak for temporary removal. We
  fixed that, but it points out that there is a place where the loop
  break check happens that is a potential regression place.

  On focal, we pass additional flags to dpkg that focal's dpkg does not
  understand, however, we only do that if dpkg asserts it does that, so
  in practice, this should all work fine and the code path will only be
  taken with >=groovy dpkg.

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

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

[Touch-packages] [Bug 1918920] Re: Harden test for no new acquires after transaction abort

[Julian Andres Klode]

autopkgtests for apt have passed, so validation was successful. I'm
confident the autopkgtest failures are unrelated intermittent ones; I've
done some more retries.

** 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1918920

Title:
  Harden test for no new acquires after transaction abort

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

Bug description:
  [Impact]
  test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less 
flaky. No end user impact as it's a test-only change.

  [Test plan]
  Running autopkgtest, which runs our extensive integration test suite which 
includes the changed test.

  [Where problems could occur]
  No end user regression potential on its own, but might slightly change 
regression potential for future pdiff changes:

  Test approach is slightly different now. It still catches that updates
  fail correctly, but tests more concretely that a transaction was
  aborted rather than that no worker received work (which was not
  guaranteed, the work could be scheduled before it was aborted).

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

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

[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel

[Julian Andres Klode]

The autopkgtests for apt have passed, so testing succeeded. I retried
the failures, I expect them to be unrelated: apport one already happened
with binutils/2.30-21ubuntu1~18.04.5, the i386 retry succeeded; and
reprotest fails in its normal way, a few retries should get it working.

** 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Won't Fix
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  APT will try and fail to remove the currently running kernel, when booted 
into an older kernel that is not protected. May wreak some havoc if mixed with 
other operations to the point that apt goes weird and needs manual fixing up.

  [Test case]
  For the SRUs we have included an automated test case that starts with an 
empty autoremove config file, and then checks that the running kernel is 
protected at runtime.

  You can also test manually, but it's not necessary:

  - Install new kernel
  - Reboot into kernel not listed as protected in 01autoremove-kernels
  - Run autoremove

  [Where problems could occur]
  We may more easily run out of space in /boot. hirsute has new autoremoval 
code that runs completely at runtime; but that seems a bit large to SRU after 
only a few weeks in hirsute. Hence, we should protect the current kernel _in 
addition_ to the other kernels, just like unattended-upgrades and 
update-manager do. This increases the risk of filling up /boot compared to 
older apt versions, but is at the same level as unattended-upgrades and 
update-manager.

  [Original bug report]

  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 21 16:11:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (114 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 
2016-07-30T12:15:32.706300

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

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

[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error

[Julian Andres Klode]

The autopkgtests for apt have passed, so testing succeeded. I retried
the failures, I expect them to be unrelated: apport one already happened
with binutils/2.30-21ubuntu1~18.04.5, the i386 retry succeeded; and
reprotest fails in its normal way, a few retries should get it working.


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

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  There is no way for scripts to run apt update and be sure that it was 
entirely successful.

  We introduce a new flag, --error-on=any that makes apt update also
  error out on transient errors.

  [Test plan]
  We have included a test in the test-suite in 
test-apt-update-failure-propagation that ensures that warnings become errors.

  [Where problems could occur]
  If there's an issue some warnings for transient errors could become errors, 
or worse I suppose it's possible but unlikely for errors to be reported as 
warnings...

  Since the new behavior is behind a flag, regression potential for
  existing scripts is low if there is no bug.

  [Original bug report]

  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
    Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
    Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
    Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

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

Re: [Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Andreas Kostyrka]

@Oscar That was never an issue: A2DP always sounded decent. The problem
with Linux Bluetooth headset support comes when you want decent quality
while listening and recording sound, you know e.g. during video calls.

Am Di., 30. März 2021 um 07:35 Uhr schrieb Oscar Pérez del Campo <
1838...@bugs.launchpad.net>:

> I guess this bug has been solved. As stated in
> https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/776 by
> @rmeissn, from gnome-settings, when the headset is connected, you can
> switch from HSP/HFP to A2DP.
> Once changed this setting my headsed sounds perfectly.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1838151
>
> Title:
>   Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
>   wide band speech support (Bluetooth A2DP codecs).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions
>

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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