[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[tran xuan truong]

** Changed in: glibc (Ubuntu)
   Status: Invalid => Fix Committed

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

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Fix Committed
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images, which are not affected:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+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 1898059] Re: [POSITIVO BGH] Repeated sound constantly, and some cracky noise sometimes

[Daniel van Vugt]

This might be a problem in the kernel driver. Please test a newer kernel
by downloading all of these:

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.13/amd64/linux-
headers-5.8.13-050813-generic_5.8.13-050813.202010011235_amd64.deb

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.13/amd64/linux-
headers-5.8.13-050813_5.8.13-050813.202010011235_all.deb

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.13/amd64/linux-
image-
unsigned-5.8.13-050813-generic_5.8.13-050813.202010011235_amd64.deb

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.13/amd64/linux-
modules-5.8.13-050813-generic_5.8.13-050813.202010011235_amd64.deb

and then install them all together with:

  sudo dpkg -i *.deb

and reboot.


** Summary changed:

- Repeated sound constantly, and some cracky noise sometimes
+ [POSITIVO BGH] Repeated sound constantly, and some cracky noise sometimes

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

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

Title:
  [POSITIVO BGH] Repeated sound constantly, and some cracky noise
  sometimes

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I watch youtube videos or hear music in for example spotify or
  anywhere, usually the sounds of what I am playing is heared twice like
  some kind of echo.

  Also, sometimes there is a cracky sound while hearing. I don't know
  what may cause this and that's why I'm reporting this bug. (Before I
  had Linux Mint and that didn't happen, but I prefer Ubuntu so if
  possible I would like a solution, thank you).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.5
  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.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bata340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  1 11:19:48 2020
  InstallationDate: Installed on 2020-08-12 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio Interno - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   oct 01 09:19:13 BataBGH dbus-daemon[788]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.28' (uid=1000 pid= comm="/usr/bin/pulseaudio 
--daemonize=no --log-target=jo" label="unconfined")
   oct 01 09:19:15 BataBGH dbus-daemon[788]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.34' 
(uid=1000 pid= comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" 
label="unconfined")
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_SpeakerTestPulseStderr: W r i t e   e r r o r :   - 3 2 , B r o k e n 
  p i p e
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [POSITIVO BGH, Realtek ALC269VB, Speaker, Internal] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2011
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 1.04.00.IF.Test01
  dmi.board.name: POSITIVO BGH
  dmi.board.vendor: POSITIVO BGH
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: POSITIVO BGH
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.04.00.IF.Test01:bd08/18/2011:svnPOSITIVOBGH:pnPOSITIVOBGH:pvrNotApplicable:rvnPOSITIVOBGH:rnPOSITIVOBGH:rvrNotApplicable:cvnPOSITIVOBGH:ct9:cvrN/A:
  dmi.product.name: POSITIVO BGH
  dmi.product.sku: 1234567890
  dmi.product.version: Not Applicable
  dmi.sys.vendor: POSITIVO BGH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1898059/+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 1898135] Re: [Samsung NP350V5C] Sound crackles and rewinds for 1 millisecond, periodically

[Daniel van Vugt]

** Summary changed:

- Sound crackles and rewinds for 1 millisecond, periodically
+ [Samsung NP350V5C] Sound crackles and rewinds for 1 millisecond, periodically

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

Title:
  [Samsung NP350V5C] Sound crackles and rewinds for 1 millisecond,
  periodically

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Using Lubuntu, Bug began not too long ago, fine before then, short
  sounds are fine. Discovered bug using YouTube

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1.2
  ProcVersionSignature: Ubuntu 5.3.0-64.58-generic 5.3.18
  Uname: Linux 5.3.0-64-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  admin  1391 F pulseaudio
   /dev/snd/pcmC0D0p:   admin  1391 F...m pulseaudio
  CurrentDesktop: LXQt
  Date: Fri Oct  2 09:46:45 2020
  InstallationDate: Installed on 2019-12-27 (279 days ago)
  InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulseAudioLog: Oct 01 16:00:36 admin-pc dbus-daemon[804]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.41' (uid=1000 pid=1391 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: 
[350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX,
 Realtek ALC269VC, Black Headphone Out, Right] Underruns, dropouts or crackling 
sound
  UpgradeStatus: Upgraded to eoan on 2020-05-17 (137 days ago)
  dmi.bios.date: 06/30/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P04AAL
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP350V5C-S02AU
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04AAL:bd06/30/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX:pvrP04AAL.022.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-S02AU:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: Eureka
  dmi.product.name: 
350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX
  dmi.product.sku: P04AAL.022.CP
  dmi.product.version: P04AAL.022.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1898135/+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 1898073] Re: There is a bug.

[Daniel van Vugt]

We need to know what kind of problem you are experiencing.

If the system has reported a bug then that might have been a crash, so please 
try these steps:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  There is a bug.

Status in Ubuntu:
  Incomplete

Bug description:
  System has reported bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
  Uname: Linux 5.4.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  1 21:19:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0502]
  InstallationDate: Installed on 2020-09-15 (16 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Inspiron N4050
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-49-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 02JCHC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/03/2012:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn02JCHC:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N4050
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102+git2009231830.77687f~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2009301930.8dc892~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.3~git2009301930.8dc892~oibaf~f
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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/+bug/1898073/+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 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

[Launchpad Bug Tracker]

This bug was fixed in the package procps - 2:3.3.16-5ubuntu2

---
procps (2:3.3.16-5ubuntu2) groovy; urgency=medium

  * debian/sysctl.d/10-kernel-hardening.conf:
- Add documentation for DMESG_RESTRICT feature, and allow users to
  disable by uncommenting kernel.dmesg_restrict=0. (LP: #1886112)

 -- Matthew Ruffell   Thu, 23 Jul 2020
16:59:38 +1200

** Changed in: procps (Ubuntu Groovy)
   Status: In Progress => Fix Released

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

Title:
  Enabling DMESG_RESTRICT in Groovy Onward

Status in linux package in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  In Progress
Status in linux source package in Groovy:
  Fix Released
Status in procps source package in Groovy:
  Fix Released
Status in util-linux source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT
  feature by default for Groovy onward, proposed to ubuntu-devel:

  https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html

  The kernel log buffer contains a wealth of sensitive information, such
  as detailed call traces and kernel addresses found in register dumps
  in kernel oops messages.

  Exploit developers and attackers can leverage these information leaks
  to get past KASLR, and they can use the kernel log buffer to get
  instant feedback on their privilege escalation attacks, as failures
  will be shown as further oops messages, which attackers can use to fix
  and tune their programs until they work.

  Currently, if I create a new, unprivileged user on a Focal system,
  they cannot access /var/log/kern.log, /var/log/syslog or see system
  events in journalctl. But yet, they are given free reign to the kernel
  log buffer.

  $ sudo adduser dave
  $ su dave
  $ groups
  dave
  $ cat /var/log/kern.log
  cat: /var/log/kern.log: Permission denied
  $ cat /var/log/syslog
  cat: /var/log/syslog: Permission denied
  $ journalctl
  Hint: You are currently not seeing messages from other users and the system.
    Users in groups 'adm', 'systemd-journal' can see all messages.
    Pass -q to turn off this notice.
  Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target.
  Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms.
  $ dmesg
  [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014)
  (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 
15:46:55
  UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic
  root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro
  ...

  I propose that we restrict access to dmesg to users in group 'adm'
  like so:

  1) Add kernel.dmesg_restrict = 1 to
 /etc/sysctl.d/10-kernel-hardening.conf
  2) Following changes to /bin/dmesg permissions in package 'util-linux'
  - Ownership changes to root:adm
  - Permissions changed to 0750 (-rwxr-x---)
  - Add cap_syslog capability to binary.

  For most users, they will use the initial admin account, which is in
  the 'adm' group already, and will see no impact to these changes. If a
  log scraper type program needs access to dmesg, the user the daemon
  runs as can simply be added to the 'adm' group.

  [Testcase]

  Currently, all users can run /usr/bin/dmesg to view the kernel log
  buffer:

  $ dmesg
  [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014)
  (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 
15:46:55
  UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic
  root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro
  ...

  When the changes are applied, the default admin user will be able to
  view dmesg (since they are in group 'adm'), while new unprivileged
  users will not.

  Test packages are available in the following ppa:
  https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test

  $ whoami
  ubuntu
  $ groups
  ubuntu adm cdrom sudo dip plugdev
  $ dmesg
  [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014)
  (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 
15:46:55
  UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic
  root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro
  ...

  $ sudo adduser dave
  $ su dave
  $ groups
  dave
  $ dmesg
  -bash: /usr/bin/dmesg: Permission denied

  [Regression Potential]

  Some users or log scraper type programs may need to view the kernel
  log buffer, or have access to dmesg. In this case, the underlying
  service user would need to be added to the 'adm' group.

  Users have the ability to disable 

[Touch-packages] [Bug 1898135] Re: Sound crackles and rewinds for 1 millisecond, periodically

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Sound crackles and rewinds for 1 millisecond, periodically

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Using Lubuntu, Bug began not too long ago, fine before then, short
  sounds are fine. Discovered bug using YouTube

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1.2
  ProcVersionSignature: Ubuntu 5.3.0-64.58-generic 5.3.18
  Uname: Linux 5.3.0-64-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  admin  1391 F pulseaudio
   /dev/snd/pcmC0D0p:   admin  1391 F...m pulseaudio
  CurrentDesktop: LXQt
  Date: Fri Oct  2 09:46:45 2020
  InstallationDate: Installed on 2019-12-27 (279 days ago)
  InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulseAudioLog: Oct 01 16:00:36 admin-pc dbus-daemon[804]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.41' (uid=1000 pid=1391 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: 
[350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX,
 Realtek ALC269VC, Black Headphone Out, Right] Underruns, dropouts or crackling 
sound
  UpgradeStatus: Upgraded to eoan on 2020-05-17 (137 days ago)
  dmi.bios.date: 06/30/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P04AAL
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP350V5C-S02AU
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04AAL:bd06/30/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX:pvrP04AAL.022.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-S02AU:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: Eureka
  dmi.product.name: 
350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX
  dmi.product.sku: P04AAL.022.CP
  dmi.product.version: P04AAL.022.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1898135/+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 1898135] [NEW] Sound crackles and rewinds for 1 millisecond, periodically

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Using Lubuntu, Bug began not too long ago, fine before then, short
sounds are fine. Discovered bug using YouTube

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: pulseaudio 1:13.0-1ubuntu1.2
ProcVersionSignature: Ubuntu 5.3.0-64.58-generic 5.3.18
Uname: Linux 5.3.0-64-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  admin  1391 F pulseaudio
 /dev/snd/pcmC0D0p:   admin  1391 F...m pulseaudio
CurrentDesktop: LXQt
Date: Fri Oct  2 09:46:45 2020
InstallationDate: Installed on 2019-12-27 (279 days ago)
InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Right
Symptom_PulseAudioLog: Oct 01 16:00:36 admin-pc dbus-daemon[804]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.41' (uid=1000 pid=1391 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: 
[350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX,
 Realtek ALC269VC, Black Headphone Out, Right] Underruns, dropouts or crackling 
sound
UpgradeStatus: Upgraded to eoan on 2020-05-17 (137 days ago)
dmi.bios.date: 06/30/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P04AAL
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP350V5C-S02AU
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: BOARD REVISION 00
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04AAL:bd06/30/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX:pvrP04AAL.022.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-S02AU:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: Eureka
dmi.product.name: 
350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX
dmi.product.sku: P04AAL.022.CP
dmi.product.version: P04AAL.022.CP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug eoan
-- 
Sound crackles and rewinds for 1 millisecond, periodically
https://bugs.launchpad.net/bugs/1898135
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio in Ubuntu.

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

[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[CryptoJones]

If you don't select "Install Third-Party Drivers" it works fine.

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

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images, which are not affected:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[dgoosens]

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

hi @thiagocmarcello

Sorry to hear that...
The day my headset all of a sudden started working, ie. 2020-09-16, it happened 
right after my dayly sudo apt-get update...

Must have been another package that dealt with it...
As a matter a fact, the linux kernel update took place on 2020-09-01...
Must have been distracted

Here is the list of updates I had that day:

fdisk:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), cryptsetup-bin:amd64 
(2:2.2.2-3ubuntu2, 2:2.2.2-3ubuntu2.2), cry
ptsetup-initramfs:amd64 (2:2.2.2-3ubuntu2, 2:2.2.2-3ubuntu2.2), 
firmware-manager-notify:amd64 (0.1.1~1585248044~20.04~5b047
86, 0.1.1~1599764521~20.04~f6b394a), uuid-runtime:amd64 (2.34-0.1ubuntu9, 
2.34-0.1ubuntu9.1), libfdisk1:amd64 (2.34-0.1ubun
tu9, 2.34-0.1ubuntu9.1), popsicle-gtk:amd64 (1.1.0~1596832906~20.04~903614f, 
1.1.0~1600184897~20.04~c093c67), libmount1:amd
64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), libpop-upgrade-gtk:amd64 
(0.1.0~1598294830~20.04~eb2eb9d, 0.1.0~1600134377~20.04~9
c2a95e), popsicle:amd64 (1.1.0~1596832906~20.04~903614f, 
1.1.0~1600184897~20.04~c093c67), gir1.2-accountsservice-1.0:amd64 
(0.6.55-0ubuntu12~20.04.1pop0, 0.6.55-0ubuntu12pop0~1599854970~20.04~bfe7ef3), 
util-linux:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), libgupnp-1.2-0:amd64 
(1.2.2-1, 1.2.3-0ubuntu0.20.04.1), cryptsetup-run:amd64 (2:2.2.2-3ubuntu2, 
2:2.2.2-3ubuntu2.2), initramfs-tools-bin:amd64 (0.136ubuntu6.2, 
0.136ubuntu6.3), libmount-dev:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), 
mount:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), libblkid1:amd64 
(2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), im-config:amd64 (0.44-1ubuntu1.1, 
0.44-1ubuntu1.2), libuuid1:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), 
libsmartcols1:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), rfkill:amd64 
(2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), uuid-dev:amd64 (2.34-0.1ubuntu9, 
2.34-0.1ubuntu9.1), bsdutils:amd64 (1:2.34-0.1ubuntu9, 1:2.34-0.1ubuntu9.1), 
libgssdp-1.2-0:amd64 (1.2.2-1, 1.2.3-0ubuntu0.20.04.1), 
libfirmware-manager:amd64 (0.1.1~1585248044~20.04~5b04786, 
0.1.1~1599764521~20.04~f6b394a), libcryptsetup12:amd64 (2:2.2.2-3ubuntu2, 
2:2.2.2-3ubuntu2.2), linux-firmware:amd64 
(1.187.1+system76~1597425559~20.04~3cf919d, 
1.190+system76~1599667136~20.04~5b2179a), pop-shell:amd64 
(0.1.0~1599583364~20.04~017c92e, 0.1.0~1600180966~20.04~e5a80ea), 
accountsservice:amd64 (0.6.55-0ubuntu12~20.04.1pop0, 
0.6.55-0ubuntu12pop0~1599854970~20.04~bfe7ef3), pop-upgrade:amd64 
(0.1.0~1598294830~20.04~eb2eb9d, 0.1.0~1600134377~20.04~9c2a95e), 
libblkid-dev:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), cryptsetup:amd64 
(2:2.2.2-3ubuntu2, 2:2.2.2-3ubuntu2.2), firmware-manager-shared:amd64 
(0.1.1~1585248044~20.04~5b04786, 0.1.1~1599764521~20.04~f6b394a), 
initramfs-tools-core:amd64 (0.136ubuntu6.2, 0.136ubuntu6.3), 
initramfs-tools:amd64 (0.136ubuntu6.2, 0.136ubuntu6.3), 
libaccountsservice0:amd64 (0.6.55-0ubuntu12~20.04.1pop0, 
0.6.55-0ubuntu12pop0~1599854970~20.04~bfe7ef3), pop-shell-shortcuts:amd64 
(0.1.0~1599143748~20.04~069276a, 0.1.0~1599845228~20.04~9280535)

(from /var/log/apt/history.log)

Hope someone smarter than me will figure out which package did unlock
the HSP/HFP profile...

dGo

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
 

[Touch-packages] [Bug 1898078] Re: FIPS OpenSSL crashes Python2.7 hashlib when using MD5

[Joy Latten]

** Description changed:

- The fix for #1835135 was not included into the python2.7 update. This
- bug has been opened to include it.
+ The fix for #1835135 was included into a python2.7 ver when python2.7
+ was updated, the fix was not included. It needs to be put pack into the
+ latest version pf python2.7 to prevent FIPS issues when using fips
+ openssl with python's hashlib. This is only a problem in latest
+ python2.7 versions in xenial, bionic, focal, and groovy. python3
+ versions do not have this problem on the above releases.
+ 
+ The fix was a backport of
+ 
https://github.com/python/cpython/pull/1777/commits/5e3e3568d27b99dabe44b8aa6283dc76d70f2dae

** Description changed:

- The fix for #1835135 was included into a python2.7 ver when python2.7
- was updated, the fix was not included. It needs to be put pack into the
- latest version pf python2.7 to prevent FIPS issues when using fips
- openssl with python's hashlib. This is only a problem in latest
- python2.7 versions in xenial, bionic, focal, and groovy. python3
- versions do not have this problem on the above releases.
+ LP #1835135 was fixed in python2.7. However, when python2.7 was updated
+ to current verion, the fix was not included. It needs to be included
+ again into current version of python2.7 to prevent FIPS issues when
+ using fips openssl with python's hashlib. This is only a problem in
+ latest python2.7 versions in xenial, bionic, focal, and groovy. python3
+ versions do not have this problem in these releases.
  
  The fix was a backport of
  
https://github.com/python/cpython/pull/1777/commits/5e3e3568d27b99dabe44b8aa6283dc76d70f2dae

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

Title:
  FIPS OpenSSL crashes Python2.7 hashlib when using MD5

Status in python2.7 package in Ubuntu:
  New
Status in python2.7 source package in Xenial:
  New
Status in python2.7 source package in Bionic:
  New
Status in python2.7 source package in Focal:
  New
Status in python2.7 source package in Groovy:
  New

Bug description:
  LP #1835135 was fixed in python2.7. However, when python2.7 was
  updated to current verion, the fix was not included. It needs to be
  included again into current version of python2.7 to prevent FIPS
  issues when using fips openssl with python's hashlib. This is only a
  problem in latest python2.7 versions in xenial, bionic, focal, and
  groovy. python3 versions do not have this problem in these releases.

  The fix was a backport of
  
https://github.com/python/cpython/pull/1777/commits/5e3e3568d27b99dabe44b8aa6283dc76d70f2dae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1898078/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Dominic Swaine]

Affected by this also.

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1898078] Re: FIPS OpenSSL crashes Python2.7 hashlib when using MD5

[Joy Latten]

** Also affects: python2.7 (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: python2.7 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: python2.7 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: python2.7 (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  FIPS OpenSSL crashes Python2.7 hashlib when using MD5

Status in python2.7 package in Ubuntu:
  New
Status in python2.7 source package in Xenial:
  New
Status in python2.7 source package in Bionic:
  New
Status in python2.7 source package in Focal:
  New
Status in python2.7 source package in Groovy:
  New

Bug description:
  The fix for #1835135 was not included into the python2.7 update. This
  bug has been opened to include it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1898078/+subscriptions

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

[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[Balint Reczey]

It does not seem possible to fix the bug in glibc, please use the daily
installer images at http://www.cdimage.ubuntu.com/focal/daily-
live/current/ until APT gets fixed on the release image.

The daily installer images has the latest libc6 packages already thus
the i386 version can be safely installed even with the current APT.

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

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images, which are not affected:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions

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

[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[Balint Reczey]

** Changed in: glibc (Ubuntu Focal)
 Assignee: Balint Reczey (rbalint) => (unassigned)

** Changed in: glibc (Ubuntu Focal)
   Status: In Progress => Invalid

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

** Description changed:

- Test Case 
+ Please use the latest daily installer images, which are not affected:
+ http://www.cdimage.ubuntu.com/focal/daily-live/current/
+ 
+ [Original Bug Text]
+ 
+ Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation
- 
  
  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
- /plugininstall.py: 
- 
+ /plugininstall.py:
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

** Merge proposal unlinked:
   
https://code.launchpad.net/~rbalint/ubuntu/+source/glibc/+git/glibc/+merge/391704

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

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images, which are not affected:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. 

[Touch-packages] [Bug 1861358] Re: tracker search hangs and never returns results

[gebi]

As this is a regression in 20.04, I'm asking if there is a backport
planned ?

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

Title:
  tracker search hangs and never returns results

Status in tracker package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  the tracker search utility isn't working

  * Test case
  $ tracker search something

  it should return results if there are any matching items

  * regression potential
  it's a build flag change, just check that the tracker search works including 
in the desktop and nautilus

  --

  When I run

  $ tracker search -f Bruni

  I see the following output on console
  -
  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot 
register existing type 'TrackerLanguage'

  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot
  add private field to invalid (non-instantiatable) type ''

  (tracker search:2): GLib-CRITICAL **: 00:31:10.761:
  g_once_init_leave: assertion 'result != 0' failed

  (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: 
g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
  -

  The program hangs and never returns. Sending Control-C brings me back
  to prompt

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.3.0-1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Thu Jan 30 00:31:59 2020
  ExecutablePath: /usr/bin/tracker
  InstallationDate: Installed on 2016-11-05 (1180 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1861358/+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 1891953] Re: CVE-2019-8936

[Launchpad Bug Tracker]

This bug was fixed in the package ntp - 1:4.2.8p10+dfsg-5ubuntu7.3

---
ntp (1:4.2.8p10+dfsg-5ubuntu7.3) bionic-security; urgency=medium

  * SECURITY UPDATE: Null dereference attack in mode 6 packet (LP: #1891953)
- debian/patches/CVE-2019-8936.patch: Guard against operations
  on NULL pointer in ntpd/ntp_control.c.
- CVE-2019-8936

 -- Brian Morton   Mon, 17 Aug 2020 21:58:51 -0400

** Changed in: ntp (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  CVE-2019-8936

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp package in Debian:
  Fix Released

Bug description:
  It was discovered that the fix for CVE-2018-7182 introduced a NULL pointer
  dereference into NTP. An attacker could use this vulnerability to cause a
  denial of service (crash).

  https://people.canonical.com/~ubuntu-
  security/cve/2019/CVE-2019-8936.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1891953/+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 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers

[Dan Streetman]

@anarchetic could you update the description with the SRU template:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

and in particular having a clearly documented reproducer in the [test
case] section will help.

thanks!

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

Title:
  nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to
  focal in containers

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  Fix Released

Bug description:
  
  Recent Linux kernels introduced a number of new syscalls ending in _time64 to 
fix Y2038 problem; it appears recent glibc, including the version in focal, 
test for the existence of these. systemd-nspawn in bionic (237-3ubuntu10.38) 
doesn't know about these so blocks them by default. It seems however glibc 
isn't expecting an EPERM, causing numerous programs to fail.

  In particular, running do-release-upgrade to focal in an nspawn
  container hosted on bionic will break as soon as the new libc has been
  unpacked.

  Solution (tested here) is to cherrypick upstream commit
  
https://github.com/systemd/systemd/commit/6ca677106992321326427c89a40e1c9673a499b2

  A newer libseccomp is also needed but this is already being worked on,
  see bug #1876055.

  It's a pretty trivial fix one the new libseccomp lands, and there is
  precedent for SRU-ing for a similar issue in bug #1840640.

  https://patchwork.kernel.org/patch/10756415/ is apparently the
  upstream kernel patch, which should give a clearer idea of which
  architectures are likely to be affected - I noticed it on armhf.

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[lesbats fabrice]

I have re-install ubuntu 18.10 (USB live) with 'install third-party software 
for graphics and WiFi hardware and additional media formats'
=> ok
I launch the update to 20.04 and ALL is OK now !! 
(nvidia card is recogniezd by system.)

Asus X93S with nvidia Gforce GT 630M

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

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  In Progress

Bug description:
  Test Case 
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  
  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py: 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+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 1895757] Autopkgtest regression report (sudo/1.8.21p2-3ubuntu1.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted sudo (1.8.21p2-3ubuntu1.3) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

openssh/1:7.6p1-4ubuntu0.3 (armhf, arm64, i386, ppc64el, amd64, s390x)
gvfs/1.36.1-0ubuntu1.3.3 (amd64)


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

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

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

Title:
  Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  sudo commands can hang when IO logging is enabled

  [Description]
  When doing cleanup in pty_close(), sudo can leave file descriptors and events
  behind that would later cause poll() to wait on a "dead" pty. This can cause
  sudo to hang when IO logging is enabled, due to the poll() timeouts.

  The issue has been fixed upstream by the commit below:
  - In pty_close() close the slave and remove any events associated 
(4df454310dae)

  $ git describe --contains 4df454310dae96d01d09a05be89dc8c57fd4cef7
  SUDO_1_8_23

  $ rmadison sudo
   sudo | 1.8.16-0ubuntu1 | xenial   | source, ...
   sudo | 1.8.16-0ubuntu1.9   | xenial-security  | source, ...
   sudo | 1.8.16-0ubuntu1.9   | xenial-updates   | source, ...
   sudo | 1.8.21p2-3ubuntu1   | bionic   | source, ...
   sudo | 1.8.21p2-3ubuntu1.2 | bionic-security  | source, ...
   => sudo | 1.8.21p2-3ubuntu1.2 | bionic-updates   | source, ... <
   sudo | 1.8.31-1ubuntu1 | focal| source, ...
   sudo | 1.8.31-1ubuntu1.1   | focal-updates| source, ...
   sudo | 1.9.1-1ubuntu1  | groovy   | source, ...

  Xenial doesn't exhibit this behaviour, so fixes are only needed for Bionic
  (Focal onwards already have the fix by default due to sudo version).

  [Test Case]

  1. Ensure /etc/sudoers contains 'Defaults use_pty'
  2. Execute the following test command:
  $ for i in {1..10}; do sudo -- cat /var/log/syslog; done

  The terminal will hang during syslog output.

  [Regression Potential]
  The fix introduces additional cleaning when closing/flushing pty devices, so 
the
  regression potential should be low. It has been present upstream since
  sudo-1.8.23, so it has seen thorough testing in most Linux distributions
  including Ubuntu.

  A regression could possibly cause issues when switching back out from sudo
  sessions, as the changes only touch the pty_close path, but seems unlikely
  considering the patch has been present in other Ubuntu releases as well.

  --
  An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running a 
command using 'sudo' when 'use_pty' is set in /etc/sudoers.

  Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):

  1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
  2) Ensure that /etc/sudoers has the following line (add this line if not 
present)
  Defaults  use_pty
  3) Execute the following (test 'sudo' command):
  for i in {1..10}; do sudo -- cat /var/log/syslog; done

  The terminal hangs and the following backtrace is obtained:

  (gdb) bt
  #0  0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1, 
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  #1  0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
  #2  sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0) 
at ../../../lib/util/event_poll.c:155
  #3  0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0, 
flags=flags@entry=0) at ../../../lib/util/event.c:617
  #4  0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false) 
at ../../src/exec_pty.c:1537
  #5  0x55d015707b97 in pty_close (cstat=0x7ffd074d6110) at 
../../src/exec_pty.c:697
  #6  exec_pty (details=details@entry=0x55d01591e0e0 , 
cstat=cstat@entry=0x7ffd074d6110) at ../../src/exec_pty.c:1412
  #7  0x55d015701178 in sudo_execute (details=0x55d01591e0e0 
, cstat=0x7ffd074d6110) at ../../src/exec.c:391
  #8  0x55d01570e15b in run_command (details=0x55d01591e0e0 
) at ../../src/sudo.c:968
  #9  0x55d0156ff9a0 in main (argc=, argv=, 
envp=) at ../../src/sudo.c:294

  A similar (most likely the same) bug has been reported here
  https://access.redhat.com/solutions/3404401.

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

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

Re: [Touch-packages] [Bug 1896772] Re: systemd-resolved configures no Current Scopes on start

[Dan Watkins]

On Thu, Oct 01, 2020 at 01:41:46PM -, Dan Watkins wrote:
> > How did resolve/netif get owned by root?
> 
> I don't believe I've ever touched it before, so I'm not sure.  I haven't
> rebooted since that last comment, I'll do that at some point today to
> check if ownership reverts to root.

Ownership is `root` on boot; whatever is responsible for creating this
in /run is presumably to blame?

> If it does, what debugging can I perform to determine what's doing it?

Let me know!

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

Title:
  systemd-resolved configures no Current Scopes on start

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Running groovy on the desktop, with the systemd packages that migrated
  today(/overnight EDT).

  # Steps to reproduce:

  1) `systemctl restart systemd-resolved.service`

  (This is a minimal reproducer, but I first saw this after an apt
  upgrade of systemd.)

  # Expected behaviour:

  DNS continues to work, status looks like this:

  Link 2 (enp5s0)
Current Scopes: DNS
  DefaultRoute setting: yes
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
Current DNS Server: 192.168.1.1
   DNS Servers: 192.168.1.1
DNS Domain: ~.
lan

  # Actual behaviour:

  DNS is unconfigured:

  Link 2 (enp5s0)
Current Scopes: none
  DefaultRoute setting: no
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no

  # Workaround

  Disconnecting and reconnecting my network connection restored DNS
  functionality.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+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 1798369] Re: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock"

[Launchpad Bug Tracker]

** Merge proposal unlinked:
   https://code.launchpad.net/~mfo/ubiquity/+git/ubiquity/+merge/390637

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

Title:
  Reinstall Ubuntu (with preserving existing data) shows error message
  due to "Could not get lock /target/var/cache/apt/archives/lock"

Status in APT:
  New
Status in ubiquity:
  New
Status in apt package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Won't Fix
Status in apt source package in Eoan:
  Invalid
Status in ubiquity source package in Eoan:
  Won't Fix

Bug description:
  When trying to reinstall an existing Ubuntu cosmic installation using
  latest 18.10 desktop images, the install shows an error dialog around
  the end of the installation with an "Error restoring installed
  applications". Looking at the syslog such a traceback can be seen:

  apt_pkg.Error: E:Could not get lock
  /target/var/cache/apt/archives/lock - open (11: Resource temporarily
  unavailable), E:Unable to lock directory
  /target/var/cache/apt/archives/

  After reproducing this on a live session, after chrooting into /target
  indeed any apt-get install operations result in the same lock-file
  error. The whole syslog of the reinstall attached to the bug.

  Test case:
   * Download latest cosmic image
   * Install cosmic on the whole disk (can be on a VM)
   * (optional) Boot into the system and leave a file in the home directory (to 
leave a trace, just in case)
   * Reboot and install cosmic using the first option in ubiquity: Reinstall 
Ubuntu
   * Finish configuration

  The install itself doesn't fail, but around the end of the
  installation process the error dialog appears. System is still
  bootable but left with old packages.

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[Steve Langasek]

Do not touch the state of the tasks on this bug if you are not a
developer.

** Changed in: glibc (Ubuntu)
   Status: Fix Committed => Invalid

** Changed in: glibc (Ubuntu)
 Assignee: elouan (elouan4) => (unassigned)

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

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

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

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

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  In Progress

Bug description:
  Test Case 
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  
  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py: 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions

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

[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[elouan]

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

** Changed in: glibc (Ubuntu)
 Assignee: (unassigned) => elouan (elouan4)

** Changed in: glibc (Ubuntu)
   Status: Confirmed => Fix Committed

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

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

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

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

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Committed
Status in glibc package in Ubuntu:
  Fix Committed
Status in apt source package in Bionic:
  Fix Committed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Committed
Status in glibc source package in Focal:
  In Progress

Bug description:
  Test Case 
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  
  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py: 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+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 1896614] Re: Race condition when starting dbus services

[Dan Streetman]

** Description changed:

  [impact]
  
  In certain scenarios, such as high load environments or when "systemctl
  daemon-reload" runs at the same time a dbus service is starting (e.g.
  systemd-logind), systemd is not able to track properly when the service
  has started, keeping the job 'running' forever.
  
  [test case]
  
  set up a 1-cpu VM with Bionic, and configure the system with a ssh key
- so the user can ssh to localhost. Then run:
+ so the user can ssh to localhost. Then run something like:
  
- ubuntu@lp1896614-b:~$ while timeout 5 ssh localhost true; do echo
- 'reloading'; sudo systemctl restart systemd-logind & sudo systemctl
- daemon-reload; done
+ $ while timeout 5 ssh localhost true; do echo 'reloading'; sudo
+ systemctl restart systemd-logind & sudo systemctl daemon-reload; done
  
- that should exit the while loop after only a few attempts. At that
- point, there should be a running job for systemd-logind, and any logins
- attempted after the bug is reproduced should also hang waiting for the
- systemd-logind job to complete, e.g.:
+ if that doesn't work try:
+ 
+ $ while timeout 5 ssh localhost true; do echo 'reloading'; sudo sh -c
+ 'systemctl restart systemd-logind & systemctl daemon-reload'; done
+ 
+ 
+ once the reproducer exits the while loop, there should be a running job for 
systemd-logind, and any logins attempted after the bug is reproduced should 
also hang waiting for the systemd-logind job to complete, e.g.:
  
  ubuntu@lp1896614-b:~$ systemctl list-jobs
  JOB UNIT   TYPE  STATE
  525 systemd-logind.service start running
  669 session-6.scopestart waiting
  664 session-5.scopestart waiting
  
  3 jobs listed.
  
  [regression potential]
  
  any regression would likely involve services that are Type=dbus failing
  to complete starting. as with any systemd change, regressions could also
  involve assertion failures in systemd which causes it to exit.
  
  [scope]
  
  this is needed only for bionic.
  
  this is fixed upstream with commit
  a5a8776ae5e4244b7f5acb2a1bfbe6e0b4d8a870 which is including starting in
  v243, so it is included already in focal and later.
  
  (per upstream bug) this was introduced by upstream commit
  75152a4d6aedbfd3ee8b2d5782b9edf27407622a which was included starting in
  v237, so this bug is not present in xenial or earlier.
  
  [original description]
  
  In certain scenarios, such as high load environments or when "systemctl
  daemon-reload" runs at the same time a dbus service is starting (e.g.
  systemd-logind), systemd is not able to track properly when the service
  has started, keeping the job 'running' forever.
  
  The issue appears when systemd runs the "AddMatch" dbus method call to
  track the service's "NameOwnerChange" once it has already ran. A working
  instance would look like this:
  
  https://pastebin.ubuntu.com/p/868J6WBRQx/
  
  A failing instance would be:
  
  https://pastebin.ubuntu.com/p/HhJZ4p8dT5/
  
  I've been able to reproduce the issue on Bionic (237-3ubuntu10.42)
  running:
  
  sudo systemctl daemon-reload & sudo systemctl restart systemd-logind

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

Title:
  Race condition when starting dbus services

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress

Bug description:
  [impact]

  In certain scenarios, such as high load environments or when
  "systemctl daemon-reload" runs at the same time a dbus service is
  starting (e.g. systemd-logind), systemd is not able to track properly
  when the service has started, keeping the job 'running' forever.

  [test case]

  set up a 1-cpu VM with Bionic, and configure the system with a ssh key
  so the user can ssh to localhost. Then run something like:

  $ while timeout 5 ssh localhost true; do echo 'reloading'; sudo
  systemctl restart systemd-logind & sudo systemctl daemon-reload; done

  if that doesn't work try:

  $ while timeout 5 ssh localhost true; do echo 'reloading'; sudo sh -c
  'systemctl restart systemd-logind & systemctl daemon-reload'; done

  
  once the reproducer exits the while loop, there should be a running job for 
systemd-logind, and any logins attempted after the bug is reproduced should 
also hang waiting for the systemd-logind job to complete, e.g.:

  ubuntu@lp1896614-b:~$ systemctl list-jobs
  JOB UNIT   TYPE  STATE
  525 systemd-logind.service start running
  669 session-6.scopestart waiting
  664 session-5.scopestart waiting

  3 jobs listed.

  [regression potential]

  any regression would likely involve services that are Type=dbus
  failing to complete starting. as with any systemd change, regressions
  could also involve assertion failures in systemd which causes it to
  exit.

  [scope]

  this is needed 

[Touch-packages] [Bug 1895757] Re: Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

[Łukasz Zemczak]

Hello Alejandro, or anyone else affected,

Accepted sudo into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/sudo/1.8.21p2-3ubuntu1.3 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

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

Title:
  Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  sudo commands can hang when IO logging is enabled

  [Description]
  When doing cleanup in pty_close(), sudo can leave file descriptors and events
  behind that would later cause poll() to wait on a "dead" pty. This can cause
  sudo to hang when IO logging is enabled, due to the poll() timeouts.

  The issue has been fixed upstream by the commit below:
  - In pty_close() close the slave and remove any events associated 
(4df454310dae)

  $ git describe --contains 4df454310dae96d01d09a05be89dc8c57fd4cef7
  SUDO_1_8_23

  $ rmadison sudo
   sudo | 1.8.16-0ubuntu1 | xenial   | source, ...
   sudo | 1.8.16-0ubuntu1.9   | xenial-security  | source, ...
   sudo | 1.8.16-0ubuntu1.9   | xenial-updates   | source, ...
   sudo | 1.8.21p2-3ubuntu1   | bionic   | source, ...
   sudo | 1.8.21p2-3ubuntu1.2 | bionic-security  | source, ...
   => sudo | 1.8.21p2-3ubuntu1.2 | bionic-updates   | source, ... <
   sudo | 1.8.31-1ubuntu1 | focal| source, ...
   sudo | 1.8.31-1ubuntu1.1   | focal-updates| source, ...
   sudo | 1.9.1-1ubuntu1  | groovy   | source, ...

  Xenial doesn't exhibit this behaviour, so fixes are only needed for Bionic
  (Focal onwards already have the fix by default due to sudo version).

  [Test Case]

  1. Ensure /etc/sudoers contains 'Defaults use_pty'
  2. Execute the following test command:
  $ for i in {1..10}; do sudo -- cat /var/log/syslog; done

  The terminal will hang during syslog output.

  [Regression Potential]
  The fix introduces additional cleaning when closing/flushing pty devices, so 
the
  regression potential should be low. It has been present upstream since
  sudo-1.8.23, so it has seen thorough testing in most Linux distributions
  including Ubuntu.

  A regression could possibly cause issues when switching back out from sudo
  sessions, as the changes only touch the pty_close path, but seems unlikely
  considering the patch has been present in other Ubuntu releases as well.

  --
  An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running a 
command using 'sudo' when 'use_pty' is set in /etc/sudoers.

  Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):

  1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
  2) Ensure that /etc/sudoers has the following line (add this line if not 
present)
  Defaults  use_pty
  3) Execute the following (test 'sudo' command):
  for i in {1..10}; do sudo -- cat /var/log/syslog; done

  The terminal hangs and the following backtrace is obtained:

  (gdb) bt
  #0  0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1, 
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  #1  0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
  #2  sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0) 
at ../../../lib/util/event_poll.c:155
  #3  0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0, 
flags=flags@entry=0) at ../../../lib/util/event.c:617
  #4  0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false) 
at ../../src/exec_pty.c:1537
  #5  0x55d015707b97 in pty_close 

[Touch-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card

[Gilbertf]

When I first installed 20.04 I had no problem at all.
I have been having this problem since 5.4.0-47-generic #51

I have to turn off or reboot 2, 3 times to get sound back.

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

Title:
  [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to
  detect card

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  kernel 5.4.0-47-generic #51
  upgraded today to this new kernel
  sound is now totally broken
  kern.org and syslog are filling with those messages every second, in loop, 
with no end to it :

  Sep  8 19:42:34 orion kernel: [  147.398030] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20970500
  Sep  8 19:42:35 orion kernel: [  148.410043] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20a70500
  Sep  8 19:42:36 orion kernel: [  149.413955] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20b70500
  Sep  8 19:42:37 orion kernel: [  150.421890] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x201f0500
  Sep  8 19:42:38 orion kernel: [  151.453799] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:39 orion kernel: [  152.461793] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:41 orion kernel: [  153.473734] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:42 orion kernel: [  154.477653] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:43 orion kernel: [  155.481576] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:44 orion kernel: [  156.489620] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:45 orion kernel: [  157.497553] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:46 orion kernel: [  158.509530] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:47 orion kernel: [  159.513471] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015

  Because of this, machine has become very slow and response time is awful
  Login into the machine, even trying to launch a simple program can take up to 
30 seconds of wait before anything happens.

  Sound was working fine with previous kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1758 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  8 19:42:19 2020
  InstallationDate: Installed on 2020-08-29 (9 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894881/+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 1898078] [NEW] FIPS OpenSSL crashes Python2.7 hashlib when using MD5

[Joy Latten]

Public bug reported:

The fix for #1835135 was not included into the python2.7 update. This
bug has been opened to include it.

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  FIPS OpenSSL crashes Python2.7 hashlib when using MD5

Status in python2.7 package in Ubuntu:
  New

Bug description:
  The fix for #1835135 was not included into the python2.7 update. This
  bug has been opened to include it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1898078/+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 1898074] Re: There is a bug.

[Hans Joachim Desserud]

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

** This bug has been marked a duplicate of bug 1898073
   There is a bug.

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

Title:
  There is a bug.

Status in xorg package in Ubuntu:
  New

Bug description:
  System has reported bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
  Uname: Linux 5.4.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  1 21:19:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0502]
  InstallationDate: Installed on 2020-09-15 (16 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Inspiron N4050
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-49-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 02JCHC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/03/2012:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn02JCHC:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N4050
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102+git2009231830.77687f~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2009301930.8dc892~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.3~git2009301930.8dc892~oibaf~f
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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/1898074/+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 1897744] VerifyHostKeyDNS not working due to missing trust-ad flag

[David]

Hello,

I use PowerDNS master, and Is It bst to use their recurser also or ? AND  IS  
PowerDNS own recuursor faster and better than the other ooption like mysql,  
Postgres  as slaves instead or PowerDNS Recursor, is mysql PostgreSQL quicker 
and better than their recursor ? Tinyds is going out I think. Knot dns is also 
free and made by they who sell the tsjekkia domain registry knot its called 
anyone know if that is a better solution? I need anything BUT BIND9 its the 
worst shit that exist! I need something fast, secure and reliable ad good at 
being in heavy  traffic and which can be used in ISPCONFIG 3.2.. Some said 
po3werdhs and knot could work in that panel, I have spent 1 mont looking for a 
panel that supports pdns or knot but none!
Hule lovewom4c advice.

And how do I get DNSSEC for my dns ? Do I login to ripe and get it from
them or ?

Im gong to run my own nameservers like before.

> 1. okt. 2020 kl. 16:17 skrev Dan Streetman <1897...@bugs.launchpad.net>:
> 
> ** Description changed:
> 
> + [impact]
> + 
> + without trust-ad resolv.conf option, glibc will strip AD from systemd-
> + resolved responses. one thing this will prevent working is ssh/sftp
> + VerifyHostKeyDNS
> + 
> + [test case]
> + 
> + TBD
> + 
> + [regression potential]
> + 
> + TBD
> +  
> + [scope]
> + 
> + this is needed only in focal.
> + 
> + glibc first stripped the AD in version 2.31, so this is not needed in
> + bionic or earlier.
> + 
> + this was added upstream in commit a742f9828ea which was included in
> + v246, so this is fixed already in groovy.
> + 
> + [original description]
> + 
>  Hi,
> 
>  1)
>  Description: Ubuntu 20.04.1 LTS
>  Release: 20.04
> 
>  2)
>  systemd:245.4-4ubuntu3.2
> 
>  3)
>  I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp.
> 
>  4)
>  I still get the security question
>  Matching host key fingerprint found in DNS.
> - Are you sure you want to continue connecting (yes/no/[fingerprint])? 
> + Are you sure you want to continue connecting (yes/no/[fingerprint])?
> 
>  The issue is known and fixed in systemd v246.
>  https://github.com/systemd/systemd/pull/16072
> 
>  Best regards
>  Daniel
> 
> ** Also affects: systemd (Ubuntu Focal)
>   Importance: Undecided
>   Status: New
> 
> ** Changed in: systemd (Ubuntu)
>   Status: New => Fix Released
> 
> -- 
> You received this bug notification because you are subscribed to Focal.
> Matching subscriptions: i...@lie.as
> https://bugs.launchpad.net/bugs/1897744
> 
> Title:
>  VerifyHostKeyDNS not working due to missing trust-ad flag
> 
> Status in systemd package in Ubuntu:
>  Fix Released
> Status in systemd source package in Focal:
>  In Progress
> 
> Bug description:
>  [impact]
> 
>  without trust-ad resolv.conf option, glibc will strip AD from systemd-
>  resolved responses. one thing this will prevent working is ssh/sftp
>  VerifyHostKeyDNS
> 
>  [test case]
> 
>  TBD
> 
>  [regression potential]
> 
>  regressions would likely involve DNS lookup failures, probably if
>  DNSSEC is enabled but possibly even without, and likely when the
>  application requesting the dns lookup processes the response AD.
> 
>  [scope]
> 
>  this is needed only in focal.
> 
>  glibc first stripped the AD in version 2.31, so this is not needed in
>  bionic or earlier.
> 
>  this was added upstream in commit a742f9828ea which was included in
>  v246, so this is fixed already in groovy.
> 
>  [original description]
> 
>  Hi,
> 
>  1)
>  Description: Ubuntu 20.04.1 LTS
>  Release: 20.04
> 
>  2)
>  systemd:245.4-4ubuntu3.2
> 
>  3)
>  I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp.
> 
>  4)
>  I still get the security question
>  Matching host key fingerprint found in DNS.
>  Are you sure you want to continue connecting (yes/no/[fingerprint])?
> 
>  The issue is known and fixed in systemd v246.
>  https://github.com/systemd/systemd/pull/16072
> 
>  Best regards
>  Daniel
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897744/+subscriptions
> 
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=systemd; component=main; 
> status=Fix Released; importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; distroseries=focal; 
> sourcepackage=systemd; component=main; status=In Progress; importance=Medium; 
> assignee=ddstr...@canonical.com;
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: itzonban
> Launchpad-Bug-Reporter: Daniel von Obernitz (itzonban)
> Launchpad-Bug-Modifier: Dan Streetman (ddstreet)
> Launchpad-Message-Rationale: Subscriber (Focal)
> Launchpad-Message-For: liewebagency-deactivatedaccount
> Launchpad-Subscription: i...@lie.as

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1884514] Re: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement

[Frank Heimes]

Many thx for the approval.

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

Title:
  [FFe][20.10 FEAT] zlib/gzip hardware compression enablement

Status in Ubuntu on IBM z Systems:
  Triaged
Status in gzip package in Ubuntu:
  Triaged
Status in zlib package in Ubuntu:
  Triaged

Bug description:
  [Feature Freeze Exception]

  1. Feature:

  The latest s390x hardware comes with a new concept for hardware
  assisted compression/decompression, based on a 'Next Accelerator
  Function unit' (NXU). This is an on-chip concept, a co-processor for
  compression available to all cores on the same chip. It provides
  functions as normal 'problem state' instructions (in other words user
  space instructions that are directly consumable by libraries and
  applications) and supports DEFLATE compliant compression/decompression
  + GZIP CRC/ZLIB Adler.

  To enable this hardware support for zlib and gzip, zlib needs to be compiled 
with CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e".
  The value of 0x7e enables hardware compression for the compression levels 1-6 
(out of 0-9).
  There is a significant business value of having the enablement active by 
default, since tests on a system with 4 IFLs and hardware compression enabled 
this way offered (especially for DEFLATE as best case) a speed up of more than 
40x.

  2. Changes

  Adding CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" attributes/macro
  during build of zlib and gzip.

  3. Regression risk

  The concept is new and comes with IBM z15 and LinuxONE III only and is with 
that specific and limited to s390x.
  Hence a potential regressions of this late addition would be limited to s390x 
and there again with the above changes to zlib (and gzip).
  In case of unforeseen issues with the NXU hardware component, a fallback to 
software is done.
  On top a modified zlib package was build and made available in a PPA for 
further testing.
  This change should have been included earlier, but was blocked by other zlib 
tickets/bugs that needed to be fixed and integrated first (like LP 1893170), 
hence this request for late addition.
  __

  HW Compression need to be enabled with Default-Compression-Level 6.

  Adding following CFLAGS attributes during build of zlib and gzip
  "-DDFLTCC_LEVEL_MASK=0x7e"

  CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" ./configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884514/+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 1898073] [NEW] There is a bug.

[Kumar Pramod Sinha]

Public bug reported:

System has reported bug.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
Uname: Linux 5.4.0-49-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct  1 21:19:19 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0502]
InstallationDate: Installed on 2020-09-15 (16 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Inspiron N4050
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-49-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 02JCHC
dmi.board.vendor: Dell Inc.
dmi.board.version: A08
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/03/2012:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn02JCHC:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron N4050
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102+git2009231830.77687f~oibaf~f
version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2009301930.8dc892~oibaf~f
version.libgl1-mesa-glx: libgl1-mesa-glx 20.3~git2009301930.8dc892~oibaf~f
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

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

Title:
  There is a bug.

Status in xorg package in Ubuntu:
  New

Bug description:
  System has reported bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
  Uname: Linux 5.4.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  1 21:19:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0502]
  InstallationDate: Installed on 2020-09-15 (16 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Inspiron N4050
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-49-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 02JCHC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/03/2012:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn02JCHC:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N4050
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102+git2009231830.77687f~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2009301930.8dc892~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.3~git2009301930.8dc892~oibaf~f
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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 

[Touch-packages] [Bug 1898074] [NEW] There is a bug.

[Kumar Pramod Sinha]

Public bug reported:

System has reported bug.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
Uname: Linux 5.4.0-49-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct  1 21:19:19 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0502]
InstallationDate: Installed on 2020-09-15 (16 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Inspiron N4050
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-49-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 02JCHC
dmi.board.vendor: Dell Inc.
dmi.board.version: A08
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/03/2012:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn02JCHC:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron N4050
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102+git2009231830.77687f~oibaf~f
version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2009301930.8dc892~oibaf~f
version.libgl1-mesa-glx: libgl1-mesa-glx 20.3~git2009301930.8dc892~oibaf~f
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

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

Title:
  There is a bug.

Status in xorg package in Ubuntu:
  New

Bug description:
  System has reported bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
  Uname: Linux 5.4.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  1 21:19:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0502]
  InstallationDate: Installed on 2020-09-15 (16 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Inspiron N4050
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-49-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 02JCHC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/03/2012:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn02JCHC:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N4050
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102+git2009231830.77687f~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2009301930.8dc892~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.3~git2009301930.8dc892~oibaf~f
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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 

[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~rbalint/ubuntu/+source/glibc/+git/glibc/+merge/391704

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

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  In Progress

Bug description:
  Test Case 
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  
  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py: 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+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 1898072] [NEW] no sound

[william backus]

Public bug reported:

no sound issue

4 years using ubuntu 16.04.  weekend 9.26.20 clean install ubuntu
20.04.01. planned 3 days install. day one clone and full ext hd backup
all files. day two clean install, paste files and use clean system. all
mostly works but no sound from prior working setup. day 3 troubleshoot
sound, install new versions of apps from prior working system.

seems no sound is a very common issue. ubuntu/settings/sound not showing
my outup options, being locked to an hdmi ouput was baffling and i
considered restoring my clone except for the 2 days of sucessfully
transferring my files. i am satisfied the system is functional for my
core uses so i will continue to try to work this sound issue.

politely asking for advice from community. no shouting here and i do
appreciate help.

the following is my no sound experience on day 3 of clean install:

ubuntu/settings/audio. only showed hdmi output device, everything else
blank.

online advice to search devices

lspci: found my sound card
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)

tried online advice:
search pci devices
kill alsa, reinstall
kill pulseaudio, reinstall

alsamixer: turned up/on everything, finally speaker feeback for
alsamixer loopback setting so i knew sound was capable of something.

pulseaudio, tried every random setting. finally the setting "analog
surround 4.1 ouput + analog stereo input (unplugged) (unavailable)"
setting worked normally thru my audio jacks.

now pulseaudio does not save these settings thru shutdown.
whaaa? relief! baffled. reluctant to touch anything else because it works...so 
far.

went thru pulseaudio settings files, seems almost all options are
commented out. i pasted these files at end this message.

alsa mixer keeps settings. ubuntu/settings/audio still only shows hdmi
output device, everything else blank.

now i am considering online advice to kill and reset all pulseaudio.

Reset PulseAudio If the system is not playing audio, first try reseting the 
pulseaudio daemon: systemctl --user restart pulseaudio Applications may need to 
be restarted. If this fails then try removing the user configuration files for 
PulseAudio: rm -r ~/.config/pulse Then, kill all instances of PulseAudio: 
pulseaudio -k When PulseAudio starts again (which it should do automatically), 
it will create new configuration files. 
https://support.system76.com/articles/audio/

sound output works if i manually reset pulseaudio after start. i am not
confident to blast away or edit conf or daemon files. i would like
working pulseaudio settings to survive restart and i would prefer
ubuntu/settings/audio reflect actual settings. thanks in advance for
suggestions/comments.

following are existing pulseaudio files:

william@william-Studio-XPS-7100:/etc/pulse$ tree
.
├── client.conf
├── client.conf.d
│   └── 01-enable-autospawn.conf -> /run/pulseaudio-enable-autospawn
├── daemon.conf
├── default.pa
└── system.pa


This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; avoid-resampling = false
; enable-remixing = yes
; remixing-use-all-sink-channels = yes
; remixing-produce-lfe = no
; remixing-consume-lfe = no
; lfe-crossover-freq = 0

; flat-volumes = no

; rescue-streams = yes

; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-memlock = -1
; 

[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[Nguyen Khanh Long]

I got this problem when install Ubuntu too. My laptop have NVIDIA
graphic card and secure boot disabled. The installer see the error but
when I remove and reboot laptop, Ubuntu installed on laptop but missing
NVIDIA XServer Settings. But funny thing that it's appear on my Ubuntu
boot media that using 20.04.1 version but giving no error in last time.
So maybe the NVIDIA package from internet have problem (I'm not
specialize in Linux but still know something about computer). Maybe this
information can help.

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

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  In Progress

Bug description:
  Test Case 
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  
  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py: 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+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 1888726] Re: systemd-udevd regression: some renamed network interfaces stuck in "pending" state

[Brian Murray]

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

** Also affects: netplan.io (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Tags removed: rls-ff-incoming

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

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

Title:
  systemd-udevd regression: some renamed network interfaces stuck in
  "pending" state

Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in netplan.io source package in Focal:
  New
Status in systemd source package in Focal:
  Invalid

Bug description:
  Summary:

  In Ubuntu Server 20.04 LTS and newer, using netplan.io and systemd-
  networkd, in certain network configurations, renamed network
  interfaces get stuck in "pending" state and are not configured
  properly. On boot, system is stuck on "Wait for Network to be
  Configured" for 2 minutes.

  
  How to reproduce:

  1. Configure a machine (for example, a virtual machine) with two Ethernet 
network cards. Make note of MAC addresses of these network cards.
  2. Set up netplan with a single configuration file, contents are in the 
attached "00-static.yaml" file. Replace the MAC addresses to match your setup. 
IP address configuration is omitted and is not necessary to reproduce the bug.
  3. Reboot the system.

  
  Expected outcome:

  1. System boots in a reasonable time
  2. First network interface (wan) is brought up, is not renamed, and is marked 
as configured by networkd
  3. Second network interface (lan) is brought up, renamed, configured for 
MTU=9000, and is marked as configured by networkd
  4. VLAN interface (vlan20) is brought up, renamed, configured for MTU=9000, 
and is marked as configured by networkd

  
  Actual outcome:

  1. System boot is delayed by 2 minutes
  2. First network interface (wan) is configured as expected
  3. Second network interface (lan) is configured as expected
  4. VLAN interface (vlan20) seems to be configured as expected, but is stuck 
in "pending" state according to networkctl list

  
  Test environment:

Hardware:

Virtual machine with the following configuration

* 4 amd64 CPU cores (also tested with a single core)
* 1 GB RAM
* 8 GB disk
* 2 network cards (vmxnet3 in VMware, virtio in Parallels)

Working as expected:

* [1] Ubuntu Server 19.10, kernel 5.3.0-62, netplan.io
  0.99-0ubuntu3~19.10.2, systemd+udev 242-7ubuntu3.11

Broken:

* [2] Ubuntu Server 19.10, kernel 5.3.0-62, netplan.io 
0.99-0ubuntu3~19.10.2, systemd 242-7ubuntu3.11, udev 245.4-4ubuntu3.1
* [3] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 
0.99-0ubuntu3~20.04.2, systemd+udev 245.4-4ubuntu3.1
* [4] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 
0.99-0ubuntu3~20.04.2, systemd+udev vanilla upstream git e9769453
* [5] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 
0.99-0ubuntu3~20.04.2, systemd+udev vanilla upstream git v242
* [6] Ubuntu Server 20.10 daily-live, kernel 5.4.0-26, netplan.io 
0.99-0ubuntu5, systemd+udev 245.6-3ubuntu3

  [2] As noted above, issue was reproduced in 19.10 by upgrading ONLY
  udev and libudev1 to ones shipped in focal-updates.

  [4] It was also reproduced in vanilla upstream systemd, git master
  commit e9769453. Just installed on top of existing systemd using "sudo
  ninja -C build install".

  [5] Interestingly enough, issue also seems to exist in vanilla v242.
  Either that, or the installation didn't replace the packaged systemd
  properly. This may hint at some distribution-specific patch that got
  removed before 20.04.

  This issue was reproduced in VMware ESXi 6.7U3, VMware Fusion 11.5.5
  and Parallels Desktop 15.1.4. This leads me to believe that network
  card drivers or virtualisation engines do not play part in the issue.

  
  Extra observations:

  To make the example configuration (00-static.yaml) not get stuck in
  "pending" state, any one of the following options helps:

  * Remove "set-name" parameter for "lan" interface
  * Remove "mtu" parameter for "lan" interface
  * Remove "wan" interface entirely

  I got some data/logs for each of these scenarios for eoan [1] and
  focal [3], as well as the original broken config, and put them
  together in the attached "parallels.tar.gz".

  
  Note about Apport:

  Attached apport report was generated for test environment [2] above.

  
  Attachments:

  * 00-static.yaml: minimalistic broken netplan configuration example
  * parallels.tar.gz: various logs for eoan [1] and focal [3], as described in 
"Extra observations" above

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: udev 245.4-4ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.9
  Architecture: 

[Touch-packages] [Bug 1884514] Re: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement

[Steve Langasek]

FFe approved.

** Changed in: zlib (Ubuntu)
   Status: New => Triaged

** Changed in: gzip (Ubuntu)
   Status: New => Triaged

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

Title:
  [FFe][20.10 FEAT] zlib/gzip hardware compression enablement

Status in Ubuntu on IBM z Systems:
  Triaged
Status in gzip package in Ubuntu:
  Triaged
Status in zlib package in Ubuntu:
  Triaged

Bug description:
  [Feature Freeze Exception]

  1. Feature:

  The latest s390x hardware comes with a new concept for hardware
  assisted compression/decompression, based on a 'Next Accelerator
  Function unit' (NXU). This is an on-chip concept, a co-processor for
  compression available to all cores on the same chip. It provides
  functions as normal 'problem state' instructions (in other words user
  space instructions that are directly consumable by libraries and
  applications) and supports DEFLATE compliant compression/decompression
  + GZIP CRC/ZLIB Adler.

  To enable this hardware support for zlib and gzip, zlib needs to be compiled 
with CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e".
  The value of 0x7e enables hardware compression for the compression levels 1-6 
(out of 0-9).
  There is a significant business value of having the enablement active by 
default, since tests on a system with 4 IFLs and hardware compression enabled 
this way offered (especially for DEFLATE as best case) a speed up of more than 
40x.

  2. Changes

  Adding CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" attributes/macro
  during build of zlib and gzip.

  3. Regression risk

  The concept is new and comes with IBM z15 and LinuxONE III only and is with 
that specific and limited to s390x.
  Hence a potential regressions of this late addition would be limited to s390x 
and there again with the above changes to zlib (and gzip).
  In case of unforeseen issues with the NXU hardware component, a fallback to 
software is done.
  On top a modified zlib package was build and made available in a PPA for 
further testing.
  This change should have been included earlier, but was blocked by other zlib 
tickets/bugs that needed to be fixed and integrated first (like LP 1893170), 
hence this request for late addition.
  __

  HW Compression need to be enabled with Default-Compression-Level 6.

  Adding following CFLAGS attributes during build of zlib and gzip
  "-DDFLTCC_LEVEL_MASK=0x7e"

  CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" ./configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884514/+subscriptions

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

[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[Brian Murray]

** Tags removed: rls-ff-incoming

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

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  In Progress

Bug description:
  Test Case 
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  
  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py: 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Leendert de Kok]

I can confirm this behavior with by JBL TUNE750TNC.

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Leendert de Kok]

Any information needed about my configuration or some log?

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1897744] Re: VerifyHostKeyDNS not working due to missing trust-ad flag

[Dan Streetman]

** Description changed:

  [impact]
  
  without trust-ad resolv.conf option, glibc will strip AD from systemd-
- resolved responses. one thing this will prevent working is ssh/sftp
+ resolved responses. one thing this will prevent working is ssh
  VerifyHostKeyDNS
  
  [test case]
  
- TBD
+ setup a target system to ssh into, and create a SSHFP DNS record for its
+ public key. on a different source system, setup dns to enable DNSSEC,
+ and attempt to ssh to the target system using the VerifyHostKeyDNS=yes
+ option.
+ 
+ setup of the SSHFP is out of scope for this bug, but e.g.:
+ https://en.wikipedia.org/wiki/SSHFP_record
+ https://tools.ietf.org/html/rfc4255
  
  [regression potential]
  
  regressions would likely involve DNS lookup failures, probably if DNSSEC
  is enabled but possibly even without, and likely when the application
  requesting the dns lookup processes the response AD.
  
  [scope]
  
  this is needed only in focal.
  
  glibc first stripped the AD in version 2.31, so this is not needed in
  bionic or earlier.
  
  this was added upstream in commit a742f9828ea which was included in
  v246, so this is fixed already in groovy.
  
  [original description]
  
  Hi,
  
  1)
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  
  2)
  systemd:245.4-4ubuntu3.2
  
  3)
  I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp.
  
  4)
  I still get the security question
  Matching host key fingerprint found in DNS.
  Are you sure you want to continue connecting (yes/no/[fingerprint])?
  
  The issue is known and fixed in systemd v246.
  https://github.com/systemd/systemd/pull/16072
  
  Best regards
  Daniel

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

Title:
  VerifyHostKeyDNS not working due to missing trust-ad flag

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  without trust-ad resolv.conf option, glibc will strip AD from systemd-
  resolved responses. one thing this will prevent working is ssh
  VerifyHostKeyDNS

  [test case]

  setup a target system to ssh into, and create a SSHFP DNS record for
  its public key. on a different source system, setup dns to enable
  DNSSEC, and attempt to ssh to the target system using the
  VerifyHostKeyDNS=yes option.

  setup of the SSHFP is out of scope for this bug, but e.g.:
  https://en.wikipedia.org/wiki/SSHFP_record
  https://tools.ietf.org/html/rfc4255

  [regression potential]

  regressions would likely involve DNS lookup failures, probably if
  DNSSEC is enabled but possibly even without, and likely when the
  application requesting the dns lookup processes the response AD.

  [scope]

  this is needed only in focal.

  glibc first stripped the AD in version 2.31, so this is not needed in
  bionic or earlier.

  this was added upstream in commit a742f9828ea which was included in
  v246, so this is fixed already in groovy.

  [original description]

  Hi,

  1)
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  2)
  systemd:245.4-4ubuntu3.2

  3)
  I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp.

  4)
  I still get the security question
  Matching host key fingerprint found in DNS.
  Are you sure you want to continue connecting (yes/no/[fingerprint])?

  The issue is known and fixed in systemd v246.
  https://github.com/systemd/systemd/pull/16072

  Best regards
  Daniel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897744/+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 1898059] [NEW] Repeated sound constantly, and some cracky noise sometimes

[Bata340]

Public bug reported:

When I watch youtube videos or hear music in for example spotify or
anywhere, usually the sounds of what I am playing is heared twice like
some kind of echo.

Also, sometimes there is a cracky sound while hearing. I don't know what
may cause this and that's why I'm reporting this bug. (Before I had
Linux Mint and that didn't happen, but I prefer Ubuntu so if possible I
would like a solution, thank you).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.5
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.8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bata340 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct  1 11:19:48 2020
InstallationDate: Installed on 2020-08-12 (49 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Audio Interno - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
 oct 01 09:19:13 BataBGH dbus-daemon[788]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.28' (uid=1000 pid= comm="/usr/bin/pulseaudio 
--daemonize=no --log-target=jo" label="unconfined")
 oct 01 09:19:15 BataBGH dbus-daemon[788]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.34' 
(uid=1000 pid= comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" 
label="unconfined")
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_SpeakerTestPulseStderr: W r i t e   e r r o r :   - 3 2 , B r o k e n   
p i p e
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [POSITIVO BGH, Realtek ALC269VB, Speaker, Internal] Underruns, dropouts 
or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2011
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 1.04.00.IF.Test01
dmi.board.name: POSITIVO BGH
dmi.board.vendor: POSITIVO BGH
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: POSITIVO BGH
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.04.00.IF.Test01:bd08/18/2011:svnPOSITIVOBGH:pnPOSITIVOBGH:pvrNotApplicable:rvnPOSITIVOBGH:rnPOSITIVOBGH:rvrNotApplicable:cvnPOSITIVOBGH:ct9:cvrN/A:
dmi.product.name: POSITIVO BGH
dmi.product.sku: 1234567890
dmi.product.version: Not Applicable
dmi.sys.vendor: POSITIVO BGH

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


** Tags: amd64 apport-bug focal

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

Title:
  Repeated sound constantly, and some cracky noise sometimes

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I watch youtube videos or hear music in for example spotify or
  anywhere, usually the sounds of what I am playing is heared twice like
  some kind of echo.

  Also, sometimes there is a cracky sound while hearing. I don't know
  what may cause this and that's why I'm reporting this bug. (Before I
  had Linux Mint and that didn't happen, but I prefer Ubuntu so if
  possible I would like a solution, thank you).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.5
  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.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bata340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  1 11:19:48 2020
  InstallationDate: Installed on 2020-08-12 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio Interno - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   oct 01 09:19:13 BataBGH dbus-daemon[788]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.28' (uid=1000 pid= comm="/usr/bin/pulseaudio 
--daemonize=no --log-target=jo" label="unconfined")
   oct 01 09:19:15 BataBGH dbus-daemon[788]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.34' 
(uid=1000 pid= comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" 
label="unconfined")
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  

[Touch-packages] [Bug 1897744] Re: VerifyHostKeyDNS not working due to missing trust-ad flag

[Dan Streetman]

** Description changed:

  [impact]
  
  without trust-ad resolv.conf option, glibc will strip AD from systemd-
  resolved responses. one thing this will prevent working is ssh/sftp
  VerifyHostKeyDNS
  
  [test case]
  
  TBD
  
  [regression potential]
  
- TBD
+ regressions would likely involve DNS lookup failures, probably if DNSSEC
+ is enabled but possibly even without, and likely when the application
+ requesting the dns lookup processes the response AD.
  
  [scope]
  
  this is needed only in focal.
  
  glibc first stripped the AD in version 2.31, so this is not needed in
  bionic or earlier.
  
  this was added upstream in commit a742f9828ea which was included in
  v246, so this is fixed already in groovy.
  
  [original description]
  
  Hi,
  
  1)
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  
  2)
  systemd:245.4-4ubuntu3.2
  
  3)
  I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp.
  
  4)
  I still get the security question
  Matching host key fingerprint found in DNS.
  Are you sure you want to continue connecting (yes/no/[fingerprint])?
  
  The issue is known and fixed in systemd v246.
  https://github.com/systemd/systemd/pull/16072
  
  Best regards
  Daniel

** Changed in: systemd (Ubuntu Focal)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Focal)
   Status: New => In Progress

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

Title:
  VerifyHostKeyDNS not working due to missing trust-ad flag

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  without trust-ad resolv.conf option, glibc will strip AD from systemd-
  resolved responses. one thing this will prevent working is ssh/sftp
  VerifyHostKeyDNS

  [test case]

  TBD

  [regression potential]

  regressions would likely involve DNS lookup failures, probably if
  DNSSEC is enabled but possibly even without, and likely when the
  application requesting the dns lookup processes the response AD.

  [scope]

  this is needed only in focal.

  glibc first stripped the AD in version 2.31, so this is not needed in
  bionic or earlier.

  this was added upstream in commit a742f9828ea which was included in
  v246, so this is fixed already in groovy.

  [original description]

  Hi,

  1)
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  2)
  systemd:245.4-4ubuntu3.2

  3)
  I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp.

  4)
  I still get the security question
  Matching host key fingerprint found in DNS.
  Are you sure you want to continue connecting (yes/no/[fingerprint])?

  The issue is known and fixed in systemd v246.
  https://github.com/systemd/systemd/pull/16072

  Best regards
  Daniel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897744/+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 1897744] Re: VerifyHostKeyDNS not working due to missing trust-ad flag

[Dan Streetman]

** Description changed:

+ [impact]
+ 
+ without trust-ad resolv.conf option, glibc will strip AD from systemd-
+ resolved responses. one thing this will prevent working is ssh/sftp
+ VerifyHostKeyDNS
+ 
+ [test case]
+ 
+ TBD
+ 
+ [regression potential]
+ 
+ TBD
+ 
+ [scope]
+ 
+ this is needed only in focal.
+ 
+ glibc first stripped the AD in version 2.31, so this is not needed in
+ bionic or earlier.
+ 
+ this was added upstream in commit a742f9828ea which was included in
+ v246, so this is fixed already in groovy.
+ 
+ [original description]
+ 
  Hi,
  
  1)
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  
  2)
  systemd:245.4-4ubuntu3.2
  
  3)
  I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp.
  
  4)
  I still get the security question
  Matching host key fingerprint found in DNS.
- Are you sure you want to continue connecting (yes/no/[fingerprint])? 
+ Are you sure you want to continue connecting (yes/no/[fingerprint])?
  
  The issue is known and fixed in systemd v246.
  https://github.com/systemd/systemd/pull/16072
  
  Best regards
  Daniel

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

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

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

Title:
  VerifyHostKeyDNS not working due to missing trust-ad flag

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  without trust-ad resolv.conf option, glibc will strip AD from systemd-
  resolved responses. one thing this will prevent working is ssh/sftp
  VerifyHostKeyDNS

  [test case]

  TBD

  [regression potential]

  regressions would likely involve DNS lookup failures, probably if
  DNSSEC is enabled but possibly even without, and likely when the
  application requesting the dns lookup processes the response AD.

  [scope]

  this is needed only in focal.

  glibc first stripped the AD in version 2.31, so this is not needed in
  bionic or earlier.

  this was added upstream in commit a742f9828ea which was included in
  v246, so this is fixed already in groovy.

  [original description]

  Hi,

  1)
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  2)
  systemd:245.4-4ubuntu3.2

  3)
  I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp.

  4)
  I still get the security question
  Matching host key fingerprint found in DNS.
  Are you sure you want to continue connecting (yes/no/[fingerprint])?

  The issue is known and fixed in systemd v246.
  https://github.com/systemd/systemd/pull/16072

  Best regards
  Daniel

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

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

[Touch-packages] [Bug 1896772] Re: systemd-resolved configures no Current Scopes on start

[Dan Watkins]

> How did resolve/netif get owned by root?

I don't believe I've ever touched it before, so I'm not sure.  I haven't
rebooted since that last comment, I'll do that at some point today to
check if ownership reverts to root.

If it does, what debugging can I perform to determine what's doing it?

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

Title:
  systemd-resolved configures no Current Scopes on start

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Running groovy on the desktop, with the systemd packages that migrated
  today(/overnight EDT).

  # Steps to reproduce:

  1) `systemctl restart systemd-resolved.service`

  (This is a minimal reproducer, but I first saw this after an apt
  upgrade of systemd.)

  # Expected behaviour:

  DNS continues to work, status looks like this:

  Link 2 (enp5s0)
Current Scopes: DNS
  DefaultRoute setting: yes
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
Current DNS Server: 192.168.1.1
   DNS Servers: 192.168.1.1
DNS Domain: ~.
lan

  # Actual behaviour:

  DNS is unconfigured:

  Link 2 (enp5s0)
Current Scopes: none
  DefaultRoute setting: no
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no

  # Workaround

  Disconnecting and reconnecting my network connection restored DNS
  functionality.

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

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

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

[Touch-packages] [Bug 1896772] Re: systemd-resolved configures no Current Scopes on start

[Dan Streetman]

How did resolve/netif get owned by root? It's created by systemd-
resolved, which should be running as the systemd-resolve user, as that's
the User= set in its service file

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

Title:
  systemd-resolved configures no Current Scopes on start

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Running groovy on the desktop, with the systemd packages that migrated
  today(/overnight EDT).

  # Steps to reproduce:

  1) `systemctl restart systemd-resolved.service`

  (This is a minimal reproducer, but I first saw this after an apt
  upgrade of systemd.)

  # Expected behaviour:

  DNS continues to work, status looks like this:

  Link 2 (enp5s0)
Current Scopes: DNS
  DefaultRoute setting: yes
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
Current DNS Server: 192.168.1.1
   DNS Servers: 192.168.1.1
DNS Domain: ~.
lan

  # Actual behaviour:

  DNS is unconfigured:

  Link 2 (enp5s0)
Current Scopes: none
  DefaultRoute setting: no
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no

  # Workaround

  Disconnecting and reconnecting my network connection restored DNS
  functionality.

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

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[Balint Reczey]

I'm giving a try to dropping libc6's libcrypt1's dependency and if that
works this will work around the issue in Focal but not in Groovy because
libc6 also depends on libnss-nis and libnss-nisplus there. Ideally the
bug could be fixed in APT in Groovy.

** Changed in: glibc (Ubuntu)
   Status: Fix Committed => Invalid

** Changed in: glibc (Ubuntu Focal)
   Status: Invalid => In Progress

** Changed in: glibc (Ubuntu Focal)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

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

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

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

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

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

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  In Progress

Bug description:
  Test Case 
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  
  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py: 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card

[Federico Gentile]

I have the same machine (Dell XPS 13 9300), came preloaded with Ubuntu
18, then upgraded to 20.04. Running Kernel 5.4.0-48-generic #52.

I have the same problem, only that nothing really helps apart from
restarting until it randomly works ...

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

Title:
  [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to
  detect card

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  kernel 5.4.0-47-generic #51
  upgraded today to this new kernel
  sound is now totally broken
  kern.org and syslog are filling with those messages every second, in loop, 
with no end to it :

  Sep  8 19:42:34 orion kernel: [  147.398030] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20970500
  Sep  8 19:42:35 orion kernel: [  148.410043] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20a70500
  Sep  8 19:42:36 orion kernel: [  149.413955] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20b70500
  Sep  8 19:42:37 orion kernel: [  150.421890] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x201f0500
  Sep  8 19:42:38 orion kernel: [  151.453799] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:39 orion kernel: [  152.461793] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:41 orion kernel: [  153.473734] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:42 orion kernel: [  154.477653] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:43 orion kernel: [  155.481576] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:44 orion kernel: [  156.489620] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:45 orion kernel: [  157.497553] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:46 orion kernel: [  158.509530] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:47 orion kernel: [  159.513471] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015

  Because of this, machine has become very slow and response time is awful
  Login into the machine, even trying to launch a simple program can take up to 
30 seconds of wait before anything happens.

  Sound was working fine with previous kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1758 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  8 19:42:19 2020
  InstallationDate: Installed on 2020-08-29 (9 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894881/+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 1897934] Re: The initial sound level is set to zero (mute)

[Łukasz Zemczak]

How was this in 20.04? Since you mentioned that it's a regression from
18.04 - does this mean we had it like this in focal as well?

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

Title:
  The initial sound level is set to zero (mute)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On boot into the live session - or on first install the sound level is
  muted.

  I have to use GNOME Control Center - Sounds to change to an
  appropriate level.  Once changed the level chosen is correctly
  retained between reboots.

  This appears to be a regression from 18.04 where the sound level was
  set to - I guess - 80% on the live-session/first install

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 30 16:03:08 2020
  LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.release: 15.31
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.22
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897934/+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 1898023] Re: [ThinkPad Helix 2nd] No more sound after upgrade 18.04->20.04

[Daniel van Vugt]

** Summary changed:

- No more sound after upgrade 18.04->20.04
+ [ThinkPad Helix 2nd] No more sound after upgrade 18.04->20.04

** Also affects: alsa-driver (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [ThinkPad Helix 2nd] No more sound after upgrade 18.04->20.04

Status in alsa-driver package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  (title says it in principle:)

  Upgraded from 18.04 to 20.04 yesterday. Now my sound is mum. It is
  kind of visible, but not as speakers in the tablet part of my
  convertible. So when removing the tablet from the dock, there is no
  sound. Shouldn't be a hardware problem, since W10 (dual-boot) plays
  musics.

  (The files are with dock attached, since the tablet on its own has -
  and that's a bug of *buntu - no right click. So the 'USB ' shown
  as audio device is the device in the keyboard dock.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1580 F pulseaudio
   /dev/snd/controlC0:  udippel1580 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Oct  1 11:40:36 2020
  InstallationDate: Installed on 2019-03-14 (566 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898023/+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 1898023] [NEW] No more sound after upgrade 18.04->20.04

[udippel]

Public bug reported:

(title says it in principle:)

Upgraded from 18.04 to 20.04 yesterday. Now my sound is mum. It is kind
of visible, but not as speakers in the tablet part of my convertible. So
when removing the tablet from the dock, there is no sound. Shouldn't be
a hardware problem, since W10 (dual-boot) plays musics.

(The files are with dock attached, since the tablet on its own has - and
that's a bug of *buntu - no right click. So the 'USB ' shown as
audio device is the device in the keyboard dock.)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.6
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  udippel1580 F pulseaudio
 /dev/snd/controlC0:  udippel1580 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu Oct  1 11:40:36 2020
InstallationDate: Installed on 2019-03-14 (566 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
dmi.bios.date: 03/24/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N17ETB2W (2.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CHS1KL00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: BT-56-001476
dmi.chassis.type: 11
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
dmi.product.family: ThinkPad Helix 2nd
dmi.product.name: 20CHS1KL00
dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
dmi.product.version: ThinkPad Helix 2nd
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  No more sound after upgrade 18.04->20.04

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  (title says it in principle:)

  Upgraded from 18.04 to 20.04 yesterday. Now my sound is mum. It is
  kind of visible, but not as speakers in the tablet part of my
  convertible. So when removing the tablet from the dock, there is no
  sound. Shouldn't be a hardware problem, since W10 (dual-boot) plays
  musics.

  (The files are with dock attached, since the tablet on its own has -
  and that's a bug of *buntu - no right click. So the 'USB ' shown
  as audio device is the device in the keyboard dock.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1580 F pulseaudio
   /dev/snd/controlC0:  udippel1580 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Oct  1 11:40:36 2020
  InstallationDate: Installed on 2019-03-14 (566 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1898023/+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 1897858] Re: [UIFe] IBus 1.5.23

[Gunnar Hjalmarsson]

** Changed in: ibus (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  [UIFe] IBus 1.5.23

Status in ibus package in Ubuntu:
  In Progress

Bug description:
  Do we want IBus 1.5.23 in groovy? I built it successfully here:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus

  and it seems to run smoothly. debian/ is from Debian's repo and only
  modified with the patch adjustments necessary to apply to the new
  upstream.

  Upstream's release notes:

  https://github.com/ibus/ibus/releases/tag/1.5.23

  The biggest change is that /usr/share/ibus/component/simple.xml, with
  the XKB keyboard layouts, is significantly larger than before. The UI
  for adding input methods seems to handle it fine. But the additional
  layouts should be seen as a bug fix IMO, in response to the bugs
  mentioned at bug #1835541.

  Otherwise it's mostly bug fixes (and insignificant low risk
  improvements).

  The UIFe request is due to some new translatable strings. I will
  notify the documentation and translation teams if this is approved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1897858/+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 1884514] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2020-10-01 05:08 EDT---
This functionallity will only be exploited on z15. On older HW it will be 
changed to the software implementation.

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

Title:
  [FFe][20.10 FEAT] zlib/gzip hardware compression enablement

Status in Ubuntu on IBM z Systems:
  Triaged
Status in gzip package in Ubuntu:
  New
Status in zlib package in Ubuntu:
  New

Bug description:
  [Feature Freeze Exception]

  1. Feature:

  The latest s390x hardware comes with a new concept for hardware
  assisted compression/decompression, based on a 'Next Accelerator
  Function unit' (NXU). This is an on-chip concept, a co-processor for
  compression available to all cores on the same chip. It provides
  functions as normal 'problem state' instructions (in other words user
  space instructions that are directly consumable by libraries and
  applications) and supports DEFLATE compliant compression/decompression
  + GZIP CRC/ZLIB Adler.

  To enable this hardware support for zlib and gzip, zlib needs to be compiled 
with CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e".
  The value of 0x7e enables hardware compression for the compression levels 1-6 
(out of 0-9).
  There is a significant business value of having the enablement active by 
default, since tests on a system with 4 IFLs and hardware compression enabled 
this way offered (especially for DEFLATE as best case) a speed up of more than 
40x.

  2. Changes

  Adding CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" attributes/macro
  during build of zlib and gzip.

  3. Regression risk

  The concept is new and comes with IBM z15 and LinuxONE III only and is with 
that specific and limited to s390x.
  Hence a potential regressions of this late addition would be limited to s390x 
and there again with the above changes to zlib (and gzip).
  In case of unforeseen issues with the NXU hardware component, a fallback to 
software is done.
  On top a modified zlib package was build and made available in a PPA for 
further testing.
  This change should have been included earlier, but was blocked by other zlib 
tickets/bugs that needed to be fixed and integrated first (like LP 1893170), 
hence this request for late addition.
  __

  HW Compression need to be enabled with Default-Compression-Level 6.

  Adding following CFLAGS attributes during build of zlib and gzip
  "-DDFLTCC_LEVEL_MASK=0x7e"

  CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" ./configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884514/+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 1897858] Re: [UIFe] IBus 1.5.23

[Gunnar Hjalmarsson]

The translation and documentation teams have been notified:

https://lists.ubuntu.com/archives/ubuntu-
translators/2020-October/007700.html

https://lists.ubuntu.com/archives/ubuntu-doc/2020-October/020762.html

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

Title:
  [UIFe] IBus 1.5.23

Status in ibus package in Ubuntu:
  Triaged

Bug description:
  Do we want IBus 1.5.23 in groovy? I built it successfully here:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus

  and it seems to run smoothly. debian/ is from Debian's repo and only
  modified with the patch adjustments necessary to apply to the new
  upstream.

  Upstream's release notes:

  https://github.com/ibus/ibus/releases/tag/1.5.23

  The biggest change is that /usr/share/ibus/component/simple.xml, with
  the XKB keyboard layouts, is significantly larger than before. The UI
  for adding input methods seems to handle it fine. But the additional
  layouts should be seen as a bug fix IMO, in response to the bugs
  mentioned at bug #1835541.

  Otherwise it's mostly bug fixes (and insignificant low risk
  improvements).

  The UIFe request is due to some new translatable strings. I will
  notify the documentation and translation teams if this is approved.

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[ChienDV]

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

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

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

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

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

** Changed in: glibc (Ubuntu)
   Status: Incomplete => Fix Committed

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

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

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

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Committed
Status in glibc package in Ubuntu:
  Fix Committed
Status in apt source package in Bionic:
  Fix Committed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Committed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Test Case 
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  
  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py: 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions

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

[Touch-packages] [Bug 1897858] Re: [UIFe] IBus 1.5.23

[Łukasz Zemczak]

It's late, but seeing that we're not really 'prepared' on many UI fronts
already (like missing the default wallpaper), I think it should be fine.
UIFe approved. Please inform the necessary teams and proceed!

** Changed in: ibus (Ubuntu)
   Status: New => Triaged

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

Title:
  [UIFe] IBus 1.5.23

Status in ibus package in Ubuntu:
  Triaged

Bug description:
  Do we want IBus 1.5.23 in groovy? I built it successfully here:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus

  and it seems to run smoothly. debian/ is from Debian's repo and only
  modified with the patch adjustments necessary to apply to the new
  upstream.

  Upstream's release notes:

  https://github.com/ibus/ibus/releases/tag/1.5.23

  The biggest change is that /usr/share/ibus/component/simple.xml, with
  the XKB keyboard layouts, is significantly larger than before. The UI
  for adding input methods seems to handle it fine. But the additional
  layouts should be seen as a bug fix IMO, in response to the bugs
  mentioned at bug #1835541.

  Otherwise it's mostly bug fixes (and insignificant low risk
  improvements).

  The UIFe request is due to some new translatable strings. I will
  notify the documentation and translation teams if this is approved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1897858/+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 1659719] Re: ssh can't call a binary from a snap without the full path

[Michael Hudson-Doyle]

And verified on xenial:

(client-server-5)mwhudson@anduril:~/src/subiquity$ ssh ubuntu@10.187.142.193 
"sh -c 'dpkg-query -W libpam-modules; type go '"
libpam-modules:amd641.1.8-3.2ubuntu2.1
go: not found
(client-server-5)mwhudson@anduril:~/src/subiquity$ lxc exec lp1659719-xenial -- 
apt install -y libpam-modules/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '1.1.8-3.2ubuntu2.3' (Ubuntu:16.04/xenial-proposed [amd64]) 
for 'libpam-modules'
Selected version '1.1.8-3.2ubuntu2.3' (Ubuntu:16.04/xenial-proposed [amd64]) 
for 'libpam-modules-bin' because of 'libpam-modules'
The following packages were automatically installed and are no longer required:
  libfreetype6 motd-news-config
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  libpam-modules-bin
Recommended packages:
  update-motd
The following packages will be upgraded:
  libpam-modules libpam-modules-bin
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 281 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
libpam-modules-bin amd64 1.1.8-3.2ubuntu2.3 [36.9 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
libpam-modules amd64 1.1.8-3.2ubuntu2.3 [244 kB]
Fetched 281 kB in 2s (123 kB/s) 
Preconfiguring packages ...
(Reading database ... 25804 files and directories currently installed.)
Preparing to unpack .../libpam-modules-bin_1.1.8-3.2ubuntu2.3_amd64.deb ...
Unpacking libpam-modules-bin (1.1.8-3.2ubuntu2.3) over (1.1.8-3.2ubuntu2.1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libpam-modules-bin (1.1.8-3.2ubuntu2.3) ...
(Reading database ... 25804 files and directories currently installed.)
Preparing to unpack .../libpam-modules_1.1.8-3.2ubuntu2.3_amd64.deb ...
Unpacking libpam-modules:amd64 (1.1.8-3.2ubuntu2.3) over (1.1.8-3.2ubuntu2.1) 
...
Processing triggers for man-db (2.7.5-1) ...
Setting up libpam-modules:amd64 (1.1.8-3.2ubuntu2.3) ...
(client-server-5)mwhudson@anduril:~/src/subiquity$ ssh ubuntu@10.187.142.193 
"sh -c 'dpkg-query -W libpam-modules; type go '"
libpam-modules:amd641.1.8-3.2ubuntu2.3
go is /snap/bin/go


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

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

Title:
  ssh can't call a binary from a snap without the full path

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  New
Status in openssh source package in Xenial:
  Won't Fix
Status in pam source package in Xenial:
  Fix Committed
Status in livecd-rootfs source package in Bionic:
  New
Status in openssh source package in Bionic:
  Won't Fix
Status in pam source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Focal:
  New
Status in openssh source package in Focal:
  Won't Fix
Status in pam source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Fix Released
Status in openssh source package in Groovy:
  Confirmed
Status in pam source package in Groovy:
  Fix Released
Status in openssh package in Debian:
  New

Bug description:
  [impact]
  ssh can't call a binary from a snap, it will only work using the full path.

  [test case]
  Create a container. Install the go snap (and make sure golang-go is not 
installed). Run "ssh  go version" and check the binary is found.

  [regression potential]
  It's a pam change an they are always a bit scary but the code follows the 
existing pattern for updating PATH in /etc/environment and has been tested in 
groovy.

  [original description]

  Let's say I have the hello snap installed in 192.168.122.24. Then:

  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
  elopio@192.168.122.24's password:
  bash: hello: command not found
  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
  elopio@192.168.122.24's password:
  Hello, world!

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659719/+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 1666203] Re: pam_tty_audit failed in pam_open_session

[Michael Hudson-Doyle]

Verified the new upload on xenial:

root@xenial-pam-play:~# dpkg -l libpam-modules
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 
ArchitectureDescription
+++--===-===-==
ii  libpam-modules:amd64 1.1.8-3.2ubuntu2.1  
amd64   Pluggable Authentication Modules for PAM
root@xenial-pam-play:~# sudo -u ubuntu bash
sudo: policy plugin failed session initialization
root@xenial-pam-play:~# apt install libpam-modules/xenial-proposed 
libpam-modules-bin/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '1.1.8-3.2ubuntu2.3' (Ubuntu:16.04/xenial-proposed [amd64]) 
for 'libpam-modules'
Selected version '1.1.8-3.2ubuntu2.3' (Ubuntu:16.04/xenial-proposed [amd64]) 
for 'libpam-modules-bin'
Recommended packages:
  update-motd
The following packages will be upgraded:
  libpam-modules libpam-modules-bin
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 281 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
libpam-modules-bin amd64 1.1.8-3.2ubuntu2.3 [36.9 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
libpam-modules amd64 1.1.8-3.2ubuntu2.3 [244 kB]
Fetched 281 kB in 2s (111 kB/s) 
Preconfiguring packages ...
(Reading database ... 47120 files and directories currently installed.)
Preparing to unpack .../libpam-modules-bin_1.1.8-3.2ubuntu2.3_amd64.deb ...
Unpacking libpam-modules-bin (1.1.8-3.2ubuntu2.3) over (1.1.8-3.2ubuntu2.1) ...
Setting up libpam-modules-bin (1.1.8-3.2ubuntu2.3) ...
(Reading database ... 47120 files and directories currently installed.)
Preparing to unpack .../libpam-modules_1.1.8-3.2ubuntu2.3_amd64.deb ...
Unpacking libpam-modules:amd64 (1.1.8-3.2ubuntu2.3) over (1.1.8-3.2ubuntu2.1) 
...
Setting up libpam-modules:amd64 (1.1.8-3.2ubuntu2.3) ...
root@xenial-pam-play:~# sudo -u ubuntu bash
To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.

bash: /root/.bashrc: Permission denied
ubuntu@xenial-pam-play:~$ ls
ls: cannot open directory '.': Permission denied
ubuntu@xenial-pam-play:~$ exit
root@xenial-pam-play:~# aureport --tty -i

TTY Report
===
# date time event auid term sess comm data
===
1. 10/01/20 08:21:14 132 unset ? 4294967295 bash "ls",,<^D>


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

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

Title:
  pam_tty_audit failed in pam_open_session

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Xenial:
  Fix Committed
Status in pam source package in Bionic:
  Fix Released
Status in pam source package in Cosmic:
  Fix Released
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Kernel keystroke auditing via pam_tty_audit.so not working

   * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it 
failed in pam_open_session.
     It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  [Test Case]

  1) Open a shell & escalate to root
  2) Update /etc/pam.d/common-session & 
/etc/pam.d/common-session-noninteractive and add the following line directly 
after the line: "session required pam_unix.so":
  "session required pam_tty_audit.so enable=*"

  3) Start a second new shell session on the box and type a variety of commands
  4) Exit the second shell session to flush the buffer?
  5) In the root shell run "aureport -tty -i". The output should show the 
commands run in the other shell.

  [Regression Potential]

   * Low, we are simply including the missing header file and copy the
  old status as initialization of new. The fix is already found/part of
  Debian and Disco.

  [Pending SRU]

  All regressions found in Bionic and Cosmic looks like long standing
  ADT failure. Nothing has been introduce by this particular SRU.

  [Other Info]

  # Upstream fix:
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  # git describe --contains c5f829931a22c65feffee16570efdae036524bee
  Linux-PAM-1_2_0~75

  # rmadision pam
  =>  pam | 1.1.8-1ubuntu2.2   | trusty-updates   | source
  =>  pam | 1.1.8-3.2ubuntu2   | xenial   |