[Touch-packages] [Bug 1893889] Re: unattended-upgrade of nova-common failure due to conffile prompt

2020-09-15 Thread Trent Lloyd
Right, the systems are running 1.1ubuntu1.18.04.11 - in my original
query to you I was trying to figure out if the patches in .12 or .13
were likely to have caused this specific situation and you weren't sure
hence the bug report with more details.

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => New

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

Title:
  unattended-upgrade of nova-common failure due to conffile prompt

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  unattended-upgrades attempted to upgrade nova from 2:17.0.9-0ubuntu1
  to 2:17.0.10-0ubuntu2.1 (bionic-security), however nova-common
  contains a modified conffile (/etc/nova/nova.conf) which prompts
  during upgrade and leaves apt/dpkg in a permanent error state
  requiring manual intervention. It also prevents other automated apt
  install operations from working while in this state.

  I understand that this conffile prompt is a generally known problem
  and that unattended-upgrades specifically attempts to skip upgrades
  that have such a conffile prompt, however that did not work on this
  case. I am filing this bug to try and identify and resolve the cause
  and this affected multiple systems in an Ubuntu OpenStack deployment.

  rbalint advised that this is very likely a more complex interaction with the 
exact upgrades that were being staged at the time and hence more logs would be 
needed, indeed attempting to reproduce this very simply with a downgrade of 
nova packages to 2:17.0.0-0ubuntu1 results in it being skipped, as expected:
  root@juju-c21ec6-bionic-nova-7:/home/ubuntu# unattended-upgrade
  Package nova-common has conffile prompt and needs to be upgraded manually

  And from the unattended-upgrades log we can see that 179 packages in
  total were scheduled to upgrade together during this run.

  Attaching the following logs files:
  /var/log/unattended-upgrades/*
  /var/log/dpkg*
  dpkg_-l (As at 2020-04-27 16:22, the same time period as the 
unattended-upgrades logs, but the dpkg.log* files were taken later but also 
cover the full time period from before 2019-12-28 and after 2020-04-27).

  The first instance of the failure is in unattended-upgrades.log.4.gz Line 161
  "2019-12-28 06:15:29,837 Packages that will be upgraded: amd64-microcode... 
[truncated, 179 packages total]"

  That relates to the output in unattended-upgrades-dpkg.log.4.gz Line
  791 "Log started: 2019-12-28  06:25:56"

  Which relates to the output of dpkg.log.6.gz Line 392
  "2019-12-28 06:25:56 upgrade nova-compute-kvm:all 2:17.0.9-0ubuntu1 
2:17.0.10-0ubuntu2.1"

  It fails many times after that as anytime you attempt to install a
  package, it attempts to configure nova.conf again and exits with an
  error again. But that is the original failure. But note that various
  package upgrades happened by unattended-upgrades (and possibly other
  sources) in the intervening 4 months and so I guess reproducing the
  situation may require reverse engineering the original package list
  from the dpkg logs. I have not currently attempted to do that with the
  hopes intimate knowledge of the unattended-upgrades code and logs will
  make that process faster.

  A full sosreport from the system is available if more information is
  required that will include other log files, and various other command
  outputs. It is not uploaded initially for privacy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1893889/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

2020-09-15 Thread Kelsey Margarete Skunberg
Seeing similar problems on Xenial and I suspect it's similar to the
problems occurring with Bionic and Focal:
http://autopkgtest.ubuntu.com/packages/s/systemd/xenial/amd64

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% B  0% => P 67%/) 
FFF..FF..F.FF..F
  root-unittests (F 10% S  0% B  0% => P 90%/) 
FFF...F.
arm64
  tests-in-lxd   (F 40% S  0% B  2% => P 57%/) 
F.B...FFF.FF..F..F.FFF.F
  logind (F  2% S  0% B  2% => P 95%/) 
..B...F.
  upstream   (F 22% S  0% B  2% => P 75%/) 
...F.FB.F.F.F..FFF.F
  root-unittests (F 12% S  0% B  2% => P 85%/) 
..B.F...F.FF...F

  (I'm sure LP will make this unreadable, but is is nice in monospace)

  Whatever the root cause is - the success rate of these has reduced so
  much that the (even formerly questionable) practice of retry-until-
  success won't work anymore.

  
  I have run the two tests in a local VM and systemd-fsckd works there while 
tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services".

  We had the discussion in the past, but I think I need to again bring
  up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until
  they are on reasonable success rates.

To manage notifications about this 

[Touch-packages] [Bug 1895761] Re: a menu bug

2020-09-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1889102 ***
https://bugs.launchpad.net/bugs/1889102

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1889102, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock
(Ubuntu)

** This bug has been marked a duplicate of bug 1889102
   [ubuntu-dock] App grid has too many page dots on right

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

Title:
  a menu bug

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  This what I have: duplication of menu-bullets this the right of Menu.
  This what I do:

  - open Applications Menu 
  - open Utility Mini Menu
  - close Utility.
  - get menu-bullets over 15 bullets but in reality I have just 3 menus

  NP: just the bullets not Menu pages.

  Thanks for your time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 16 01:52:25 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
  InstallationDate: Installed on 2020-03-24 (175 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20351
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=dd50ef9b-da29-43a4-b89b-4b65fe9e3229 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN28WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN28WW:bd09/23/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20351
  dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  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/gnome-shell-extension-ubuntu-dock/+bug/1895761/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-09-15 Thread Launchpad Bug Tracker
[Expired for gnome-online-accounts (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  Expired
Status in gnome-online-accounts package in Ubuntu:
  Expired
Status in gnutls28 package in Ubuntu:
  Expired

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-09-15 Thread Launchpad Bug Tracker
[Expired for evolution (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  Expired
Status in gnome-online-accounts package in Ubuntu:
  Expired
Status in gnutls28 package in Ubuntu:
  Expired

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-09-15 Thread Launchpad Bug Tracker
[Expired for gnutls28 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  Expired
Status in gnome-online-accounts package in Ubuntu:
  Expired
Status in gnutls28 package in Ubuntu:
  Expired

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1895761] Re: a menu bug

2020-09-15 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (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/1895761

Title:
  a menu bug

Status in xorg package in Ubuntu:
  New

Bug description:
  This what I have: duplication of menu-bullets this the right of Menu.
  This what I do:

  - open Applications Menu 
  - open Utility Mini Menu
  - close Utility.
  - get menu-bullets over 15 bullets but in reality I have just 3 menus

  NP: just the bullets not Menu pages.

  Thanks for your time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 16 01:52:25 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
  InstallationDate: Installed on 2020-03-24 (175 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20351
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=dd50ef9b-da29-43a4-b89b-4b65fe9e3229 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN28WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN28WW:bd09/23/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20351
  dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  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/1895761/+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 1895761] [NEW] a menu bug

2020-09-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

This what I have: duplication of menu-bullets this the right of Menu.
This what I do:

- open Applications Menu 
- open Utility Mini Menu
- close Utility.
- get menu-bullets over 15 bullets but in reality I have just 3 menus

NP: just the bullets not Menu pages.

Thanks for your time.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 16 01:52:25 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
InstallationDate: Installed on 2020-03-24 (175 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20351
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=dd50ef9b-da29-43a4-b89b-4b65fe9e3229 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/23/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 9ACN28WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lancer 5A2
dmi.board.vendor: LENOVO
dmi.board.version: NANANANANO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G50-70
dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN28WW:bd09/23/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:
dmi.product.family: IDEAPAD
dmi.product.name: 20351
dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70
dmi.product.version: Lenovo G50-70
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
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 ubuntu
-- 
a menu bug
https://bugs.launchpad.net/bugs/1895761
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1895060] Re: [FFe] apparmor 3 upstream release

2020-09-15 Thread Alex Murray
Apologies for posting the description as a comment above...

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

Title:
  [FFe] apparmor 3 upstream release

Status in apparmor package in Ubuntu:
  New

Bug description:
  As per the draft upstream release notes[1]:

  AppArmor 3.0 is a major new release of the AppArmor user space that makes
  an important change to policy development and support. Its focus is
  transitioning policy to the new features ABI and as such other new features
  have been limited.

  Apprmor 3.0 is a bridge release between older AppArmor 2.x policy and the
  newer AppArmor 3 style policy which requires the declaration of a features
  abi. As such AppArmor 3.0 will be a short lived release, and will not
  receive long term support. The following AppArmor 3.1 feature release is
  planned to be a regular release, please take this into account when
  including AppArmor 3.0 into a distro release.

  As such, Ubuntu 20.10 provides a great opportunity to introduce AppArmor3
  to Ubuntu and provide these new capabilities to users and system
  administrators. The short support lifespan of Ubuntu 20.10 ensures that
  there is alignment with the limited support lifetime of AppArmor 3.0 from
  upstream, whilst giving good exposure and opportunity to test and exercise
  the new features in AppArmor 3.x on the road to Ubuntu 22.04. A highlight
  of new features provided by AppArmor 3.0 include:

  - Policy now must declare the feature abi it was developed for if it is to
    use any new features. This ensures that old policy will not become
    incompatible with new kernels that support additional AppArmor features.
  - The use of profile names that are based on pathnames are deprecated.
  - Support for new kernel features (requires appropriate features abi
    tagging in policy)
    - upstream v8 network socket rules
    - xattr attachment conditionals
    - capabilities PERFMON and BPF
  - Improved compiler warnings and semantic checks
  - aa-status rewritten in C (previously was python) with additional features
    - supports use in systems/images where python is not available
    - supports kill, unconfined and mixed profile modes
  - Rewritten aa-notify (previously was perl, now python3)
    - shared backend with other python tools
    - support use of aa.CONFDIR instead of hard coded /etc/apparmor
    - improved message layout
  - Improved support for kernels that support LSM stacking
  - New utility aa-features-abi to extract and work with kernel abi features
  - New utility aa-load to load binary policy without calling the
    apparmor_parser
  - Support for profile modes
    - enforce (default when no mode flag is supplied)
    - kill (experimental)
    - unconfined (experimental)

  The use of the new AppArmor profile feature ABI includes a default
  configuration (for the Ubuntu packaged version of AppArmor proposed in this
  FFE) for the AppArmor features within the 5.4 Linux kernel - this ensures
  that all profiles provided in AppArmor3 for groovy will conform to this
  feature set and that upgrades to the kernel version (say to 5.8) that may
  include newer AppArmor confinement features will not result in additional
  policy denials as a result (since say the existing profile did not specify
  a rule for a new AppArmor feature which is now supported by the upgraded
  kernel). This ensures that there will be no regressions in application
  behaviour as a result of AppArmor kernel feature upgrades.

  TESTING

  This has been extensively tested by the security team - this includes
  following the documented Ubuntu merges test plan[2] for AppArmor and the
  extensive QA Regression Tests[3] for AppArmor as well. This ensures that the
  various applications that make heavy use of AppArmor (LXD, docker, lxc,
  dbus, libvirt, snapd etc) have all been exercised and no regressions have
  been observed. All tests have passed and demonstrated both apparmor and the
  various applications that use it to be working as expected.

  BUILD LOGS

  This is currently uploaded to groovy-proposed, build logs can be found on
  Launchpad at:
  https://launchpad.net/ubuntu/+source/apparmor/3.0.0~beta1-0ubuntu1

  INSTALL LOG

  See attached
  
(https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895060/+attachment/5411197/+files
  /groovy-proposed-apparmor-install.log) for a log showing install of
  the packages from groovy-proposed

  [1] https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.0
  [2] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor
  [3] 
https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py

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

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

[Touch-packages] [Bug 1895060] Re: [FFe] apparmor 3 upstream release

2020-09-15 Thread Alex Murray
As per the draft upstream release notes:

AppArmor 3.0 is a major new release of the AppArmor user space that makes
an important change to policy development and support. Its focus is
transitioning policy to the new features ABI and as such other new features
have been limited.

Apprmor 3.0 is a bridge release between older AppArmor 2.x policy and the
newer AppArmor 3 style policy which requires the declaration of a features
abi. As such AppArmor 3.0 will be a short lived release, and will not
receive long term support. The following AppArmor 3.1 feature release is
planned to be a regular release, please take this into account when
including AppArmor 3.0 into a distro release.

As such, Ubuntu 20.10 provides a great opportunity to introduce AppArmor3
to Ubuntu and provide these new capabilities to users and system
administrators. The short support lifespan of Ubuntu 20.10 ensures that
there is alignment with the limited support lifetime of AppArmor 3.0 from
upstream, whilst giving good exposure and opportunity to test and exercise
the new features in AppArmor 3.x on the road to Ubuntu 22.04. A highlight
of new features provided by AppArmor 3.0 include:

- Policy now must declare the feature abi it was developed for if it is to
  use any new features. This ensures that old policy will not become
  incompatible with new kernels that support additional AppArmor features.
- The use of profile names that are based on pathnames are deprecated.
- Support for new kernel features (requires appropriate features abi
  tagging in policy)
  - upstream v8 network socket rules
  - xattr attachment conditionals
  - capabilities PERFMON and BPF
- Improved compiler warnings and semantic checks
- aa-status rewritten in C (previously was python) with additional features
  - supports use in systems/images where python is not available
  - supports kill, unconfined and mixed profile modes
- Rewritten aa-notify (previously was perl, now python3)
  - shared backend with other python tools
  - support use of aa.CONFDIR instead of hard coded /etc/apparmor
  - improved message layout
- Improved support for kernels that support LSM stacking
- New utility aa-features-abi to extract and work with kernel abi features
- New utility aa-load to load binary policy without calling the
  apparmor_parser
- Support for profile modes
  - enforce (default when no mode flag is supplied)
  - kill (experimental)
  - unconfined (experimental)

The use of the new AppArmor profile feature ABI includes a default
configuration (for the Ubuntu packaged version of AppArmor proposed in this
FFE) for the AppArmor features within the 5.4 Linux kernel - this ensures
that all profiles provided in AppArmor3 for groovy will conform to this
feature set and that upgrades to the kernel version (say to 5.8) that may
include newer AppArmor confinement features will not result in additional
policy denials as a result (since say the existing profile did not specify
a rule for a new AppArmor feature which is now supported by the upgraded
kernel). This ensures that there will be no regressions in application
behaviour as a result of AppArmor kernel feature upgrades.

TESTING

This has been extensively tested by the security team - this includes
following the documented Ubuntu merges test plan for AppArmor and the
extensive QA Regression Tests for AppArmor as well. This ensures that the
various applications that make heavy use of AppArmor (LXD, docker, lxc,
dbus, libvirt, snapd etc) have all been exercised and no regressions have
been observed. All tests have passed and demonstrated both apparmor and the
various applications that use it to be working as expected.

BUILD LOGS

This is currently uploaded to groovy-proposed, build logs can be found on
Launchpad at:
https://launchpad.net/ubuntu/+source/apparmor/3.0.0~beta1-0ubuntu1

INSTALL LOG

See attached for a log showing install of the packages from groovy-
proposed


** Description changed:

- To be filled in
+ As per the draft upstream release notes:
+ 
+ AppArmor 3.0 is a major new release of the AppArmor user space that makes
+ an important change to policy development and support. Its focus is
+ transitioning policy to the new features ABI and as such other new features
+ have been limited.
+ 
+ Apprmor 3.0 is a bridge release between older AppArmor 2.x policy and the
+ newer AppArmor 3 style policy which requires the declaration of a features
+ abi. As such AppArmor 3.0 will be a short lived release, and will not
+ receive long term support. The following AppArmor 3.1 feature release is
+ planned to be a regular release, please take this into account when
+ including AppArmor 3.0 into a distro release.
+ 
+ As such, Ubuntu 20.10 provides a great opportunity to introduce AppArmor3
+ to Ubuntu and provide these new capabilities to users and system
+ administrators. The short support lifespan of Ubuntu 20.10 ensures that
+ there is alignment with the limited support lifetime of AppArmor 3.0 from
+ upstream, whilst 

[Touch-packages] [Bug 1895060] Re: [FFe] apparmor 3 upstream release

2020-09-15 Thread Alex Murray
** Attachment added: "groovy-proposed-apparmor-install.log"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895060/+attachment/5411197/+files/groovy-proposed-apparmor-install.log

** Description changed:

  As per the draft upstream release notes:
  
  AppArmor 3.0 is a major new release of the AppArmor user space that makes
  an important change to policy development and support. Its focus is
  transitioning policy to the new features ABI and as such other new features
  have been limited.
  
  Apprmor 3.0 is a bridge release between older AppArmor 2.x policy and the
  newer AppArmor 3 style policy which requires the declaration of a features
  abi. As such AppArmor 3.0 will be a short lived release, and will not
  receive long term support. The following AppArmor 3.1 feature release is
  planned to be a regular release, please take this into account when
  including AppArmor 3.0 into a distro release.
  
  As such, Ubuntu 20.10 provides a great opportunity to introduce AppArmor3
  to Ubuntu and provide these new capabilities to users and system
  administrators. The short support lifespan of Ubuntu 20.10 ensures that
  there is alignment with the limited support lifetime of AppArmor 3.0 from
  upstream, whilst giving good exposure and opportunity to test and exercise
  the new features in AppArmor 3.x on the road to Ubuntu 22.04. A highlight
  of new features provided by AppArmor 3.0 include:
  
  - Policy now must declare the feature abi it was developed for if it is to
-   use any new features. This ensures that old policy will not become
-   incompatible with new kernels that support additional AppArmor features.
+   use any new features. This ensures that old policy will not become
+   incompatible with new kernels that support additional AppArmor features.
  - The use of profile names that are based on pathnames are deprecated.
  - Support for new kernel features (requires appropriate features abi
-   tagging in policy)
-   - upstream v8 network socket rules
-   - xattr attachment conditionals
-   - capabilities PERFMON and BPF
+   tagging in policy)
+   - upstream v8 network socket rules
+   - xattr attachment conditionals
+   - capabilities PERFMON and BPF
  - Improved compiler warnings and semantic checks
  - aa-status rewritten in C (previously was python) with additional features
-   - supports use in systems/images where python is not available
-   - supports kill, unconfined and mixed profile modes
+   - supports use in systems/images where python is not available
+   - supports kill, unconfined and mixed profile modes
  - Rewritten aa-notify (previously was perl, now python3)
-   - shared backend with other python tools
-   - support use of aa.CONFDIR instead of hard coded /etc/apparmor
-   - improved message layout
+   - shared backend with other python tools
+   - support use of aa.CONFDIR instead of hard coded /etc/apparmor
+   - improved message layout
  - Improved support for kernels that support LSM stacking
  - New utility aa-features-abi to extract and work with kernel abi features
  - New utility aa-load to load binary policy without calling the
-   apparmor_parser
+   apparmor_parser
  - Support for profile modes
-   - enforce (default when no mode flag is supplied)
-   - kill (experimental)
-   - unconfined (experimental)
+   - enforce (default when no mode flag is supplied)
+   - kill (experimental)
+   - unconfined (experimental)
  
  The use of the new AppArmor profile feature ABI includes a default
  configuration (for the Ubuntu packaged version of AppArmor proposed in this
  FFE) for the AppArmor features within the 5.4 Linux kernel - this ensures
  that all profiles provided in AppArmor3 for groovy will conform to this
  feature set and that upgrades to the kernel version (say to 5.8) that may
  include newer AppArmor confinement features will not result in additional
  policy denials as a result (since say the existing profile did not specify
  a rule for a new AppArmor feature which is now supported by the upgraded
  kernel). This ensures that there will be no regressions in application
  behaviour as a result of AppArmor kernel feature upgrades.
  
  TESTING
  
  This has been extensively tested by the security team - this includes
  following the documented Ubuntu merges test plan for AppArmor and the
  extensive QA Regression Tests for AppArmor as well. This ensures that the
  various applications that make heavy use of AppArmor (LXD, docker, lxc,
  dbus, libvirt, snapd etc) have all been exercised and no regressions have
  been observed. All tests have passed and demonstrated both apparmor and the
  various applications that use it to be working as expected.
  
  BUILD LOGS
  
  This is currently uploaded to groovy-proposed, build logs can be found on
  Launchpad at:
  https://launchpad.net/ubuntu/+source/apparmor/3.0.0~beta1-0ubuntu1
  
  INSTALL LOG
  
- See attached for a log showing install of the packages from groovy-
- proposed
+ See attached
+ 

[Touch-packages] [Bug 1895665] Re: PulseAudio automatically switches from HDMI 2 after display sleep

2020-09-15 Thread Daniel van Vugt
Please try editing /etc/pulse/default.pa and comment out all of this:

  ### Should be after module-*-restore but before module-*-detect
  load-module module-switch-on-port-available

  ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794)
  .ifexists module-switch-on-connect.so
  load-module module-switch-on-connect
  .endif

Then reboot.


** 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/1895665

Title:
  PulseAudio automatically switches from HDMI 2 after display sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have an Nvidia based video card that has an HDMI output + a DisplayPort 
output.
  DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output 
is listed as "Digital Stereo (HDMI 2)".

  I prefer to use "Digital Stereo (HDMI 2)".
  But after each display sleep (screen lock for example) audio is switched to 
built in audio

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Sep 15 14:56:58 2020
  InstallationDate: Installed on 2020-06-20 (86 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.name: 0CNDTP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5590
  dmi.product.sku: 08EA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-15 Thread Brian Murray
I actually think this is either a bug with systemd or a change in how it
handles the services which apport-autoreport includes. I've tested this
by changing /usr/lib/systemd/system/apport-autoreport.service so that it
contains the following:

ExecStart=/usr/bin/aplay /usr/share/sounds/sound-icons/canary-long.wav

Then if I touch a .crash file in /var/crash e.g. touch
'/var/crash/canary.crash I ended up hearing the canary sound 5 times
then a pause and then the canary sound multiple times again. On Ubuntu
20.04 the same test case results in the canary sound being heard only
one time.

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

Title:
  systemd 100% cpu usage apport-autoreport.service: Failed with result
  'start-limit-hit'

Status in apport package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in apport source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  New

Bug description:
  after upgrade from Ubuntu 20.04 to 20.10  
  seeing systemd use 100% cpu forever


  top

top - 10:16:19 up 20 min,  1 user,  load average: 3.91, 4.28, 3.39
Tasks: 332 total,   2 running, 330 sleeping,   0 stopped,   0 zombie
%Cpu(s): 18.7 us,  6.4 sy, 11.9 ni, 62.2 id,  0.0 wa,  0.0 hi,  0.8 si, 
 0.0 st
MiB Mem :  15917.6 total,   8553.4 free,   2604.3 used,   4759.9 
buff/cache
MiB Swap:   2048.0 total,   2048.0 free,  0.0 used.  12633.7 avail 
Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND  
  1 root  20   0  177316  12252   8684 R 100.0   0.1  15:01.25 
systemd  
   4636 kush  39  19  633796 176152  16360 S  98.3   1.1  17:51.56 
tracker-miner-f  
820 message+  20   0   10740   6452   4212 S  39.8   0.0   6:19.06 
dbus-daemon  
316 root  19  -1  535916 322896 320824 S  15.3   2.0   3:16.41 
systemd-journal  
844 syslog20   0  221136   5840   3920 S  13.6   0.0   2:14.52 
rsyslogd 
858 root  20   0   83708  74124   7568 S  12.7   0.5   2:06.98 
systemd-logind   
  5 root  20   0   0  0  0 I   3.4   0.0   0:05.01 
kworker/0:0-events   
  35566 kush  20   0 3850088 588344 262192 S   2.5   3.6   0:30.48 
MainThread   
   5626 kush  20   0 5004788 260876  93400 S   1.7   1.6   3:05.19 
gnome-shell  
   7033 kush  20   0  869792  66440  44272 S   1.7   0.4   0:06.05 
gnome-terminal-  
  36790 kush  20   0 2525432 156636  98568 S   1.7   1.0   0:04.99 
Web Content  
957 root  20   0 1556196  45044  24284 S   0.8   0.3   0:02.48 
containerd   
   1038 root  20   0   10460   4412   3300 S   0.8   0.0   0:00.16 
fancontrol   



  
sudo tail -n 100 /var/log/syslog
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
 

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-15 Thread Brian Murray
** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  systemd 100% cpu usage apport-autoreport.service: Failed with result
  'start-limit-hit'

Status in apport package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in apport source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  New

Bug description:
  after upgrade from Ubuntu 20.04 to 20.10  
  seeing systemd use 100% cpu forever


  top

top - 10:16:19 up 20 min,  1 user,  load average: 3.91, 4.28, 3.39
Tasks: 332 total,   2 running, 330 sleeping,   0 stopped,   0 zombie
%Cpu(s): 18.7 us,  6.4 sy, 11.9 ni, 62.2 id,  0.0 wa,  0.0 hi,  0.8 si, 
 0.0 st
MiB Mem :  15917.6 total,   8553.4 free,   2604.3 used,   4759.9 
buff/cache
MiB Swap:   2048.0 total,   2048.0 free,  0.0 used.  12633.7 avail 
Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND  
  1 root  20   0  177316  12252   8684 R 100.0   0.1  15:01.25 
systemd  
   4636 kush  39  19  633796 176152  16360 S  98.3   1.1  17:51.56 
tracker-miner-f  
820 message+  20   0   10740   6452   4212 S  39.8   0.0   6:19.06 
dbus-daemon  
316 root  19  -1  535916 322896 320824 S  15.3   2.0   3:16.41 
systemd-journal  
844 syslog20   0  221136   5840   3920 S  13.6   0.0   2:14.52 
rsyslogd 
858 root  20   0   83708  74124   7568 S  12.7   0.5   2:06.98 
systemd-logind   
  5 root  20   0   0  0  0 I   3.4   0.0   0:05.01 
kworker/0:0-events   
  35566 kush  20   0 3850088 588344 262192 S   2.5   3.6   0:30.48 
MainThread   
   5626 kush  20   0 5004788 260876  93400 S   1.7   1.6   3:05.19 
gnome-shell  
   7033 kush  20   0  869792  66440  44272 S   1.7   0.4   0:06.05 
gnome-terminal-  
  36790 kush  20   0 2525432 156636  98568 S   1.7   1.0   0:04.99 
Web Content  
957 root  20   0 1556196  45044  24284 S   0.8   0.3   0:02.48 
containerd   
   1038 root  20   0   10460   4412   3300 S   0.8   0.0   0:00.16 
fancontrol   



  
sudo tail -n 100 /var/log/syslog
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 

[Touch-packages] [Bug 1895665] Re: PulseAudio automatically switches from HDMI 2 after display sleep

2020-09-15 Thread Hui Wang
I guess your bug is similar to this one:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598

Could you please do a test:

edit the /usr/share/pulseaudio/alsa-mixer/paths/hdmi-output-0.conf and
hdmi-output-1.conf, change the priority in 0.conf to 58 and change the
priority in 1.conf to 59, then reboot and redo the test.

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

Title:
  PulseAudio automatically switches from HDMI 2 after display sleep

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have an Nvidia based video card that has an HDMI output + a DisplayPort 
output.
  DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output 
is listed as "Digital Stereo (HDMI 2)".

  I prefer to use "Digital Stereo (HDMI 2)".
  But after each display sleep (screen lock for example) audio is switched to 
built in audio

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Sep 15 14:56:58 2020
  InstallationDate: Installed on 2020-06-20 (86 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.name: 0CNDTP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5590
  dmi.product.sku: 08EA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-15 Thread Brian Murray
** Tags removed: rls-gg-incoming

** Also affects: apport (Ubuntu Groovy)
   Importance: Undecided
 Assignee: Brian Murray (brian-murray)
   Status: Confirmed

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

Title:
  systemd 100% cpu usage apport-autoreport.service: Failed with result
  'start-limit-hit'

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Groovy:
  Confirmed

Bug description:
  after upgrade from Ubuntu 20.04 to 20.10  
  seeing systemd use 100% cpu forever


  top

top - 10:16:19 up 20 min,  1 user,  load average: 3.91, 4.28, 3.39
Tasks: 332 total,   2 running, 330 sleeping,   0 stopped,   0 zombie
%Cpu(s): 18.7 us,  6.4 sy, 11.9 ni, 62.2 id,  0.0 wa,  0.0 hi,  0.8 si, 
 0.0 st
MiB Mem :  15917.6 total,   8553.4 free,   2604.3 used,   4759.9 
buff/cache
MiB Swap:   2048.0 total,   2048.0 free,  0.0 used.  12633.7 avail 
Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND  
  1 root  20   0  177316  12252   8684 R 100.0   0.1  15:01.25 
systemd  
   4636 kush  39  19  633796 176152  16360 S  98.3   1.1  17:51.56 
tracker-miner-f  
820 message+  20   0   10740   6452   4212 S  39.8   0.0   6:19.06 
dbus-daemon  
316 root  19  -1  535916 322896 320824 S  15.3   2.0   3:16.41 
systemd-journal  
844 syslog20   0  221136   5840   3920 S  13.6   0.0   2:14.52 
rsyslogd 
858 root  20   0   83708  74124   7568 S  12.7   0.5   2:06.98 
systemd-logind   
  5 root  20   0   0  0  0 I   3.4   0.0   0:05.01 
kworker/0:0-events   
  35566 kush  20   0 3850088 588344 262192 S   2.5   3.6   0:30.48 
MainThread   
   5626 kush  20   0 5004788 260876  93400 S   1.7   1.6   3:05.19 
gnome-shell  
   7033 kush  20   0  869792  66440  44272 S   1.7   0.4   0:06.05 
gnome-terminal-  
  36790 kush  20   0 2525432 156636  98568 S   1.7   1.0   0:04.99 
Web Content  
957 root  20   0 1556196  45044  24284 S   0.8   0.3   0:02.48 
containerd   
   1038 root  20   0   10460   4412   3300 S   0.8   0.0   0:00.16 
fancontrol   



  
sudo tail -n 100 /var/log/syslog
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 

[Touch-packages] [Bug 1894369] Re: apport-autoreport.service fails to start in groovy after upgrading from focal

2020-09-15 Thread Brian Murray
** Also affects: apport (Ubuntu Groovy)
   Importance: Undecided
 Assignee: Brian Murray (brian-murray)
   Status: Confirmed

** Tags removed: rls-gg-incoming

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

Title:
  apport-autoreport.service fails to start in groovy after upgrading
  from focal

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Groovy:
  Confirmed

Bug description:
  apport-autoreport.service fails to start with that CPU load increases
  significantly making computer unusable. disabling the service and path
  and stopping both normalizes CPU load as it was supposed to be. for
  test purposes i started apport-autoreport.service and after checking
  its status i get state: degraded and 2 units failed.

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

2020-09-15 Thread Brian Murray
This process which reinstalls your existing applications has been
removed from ubiquity as it was broken and misleading in that it
frequently would not reinstall many of the applications which were
installed on the system. So in the interest of providing a better user
experience, by not creating expectations that would not be met, we have
removed that part of the "Reinstall Ubuntu" option.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 1895757] Re: Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

2020-09-15 Thread Alejandro Santoyo Gonzalez
** Description changed:

  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:
+ 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:
  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.

-- 
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:
  New

Bug description:
  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:
  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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2020-09-15 Thread Alejandro Santoyo Gonzalez
Public bug reported:

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)
Defaultsuse_pty
3) Execute the following:
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.

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

-- 
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:
  New

Bug description:
  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:
  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 : 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

2020-09-15 Thread Brian Murray
** Tags added: rls-ff-incomng

** Tags removed: rls-ff-incomng
** Tags added: rls-ff-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/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

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: amd64
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Thu Jul 23 18:54:58 2020
  InstallationDate: Installed on 2020-07-22 (1 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  

[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-09-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

-- 
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 1886300] Update Released

2020-09-15 Thread Brian Murray
The verification of the Stable Release Update for util-linux has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  rename.ul refuses to rename links that don't resolve (regression)

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux source package in Groovy:
  Fix Released
Status in util-linux package in Debian:
  Fix Released

Bug description:
  [Impact]

  rename.ul refuses to rename links that don't resolve.

  bionic rename.ul renames links whether or not they resolve (util-linux
  2.31.1-0.4ubuntu3.6).

  focal rename.ul refuses to rename links that don't resolve
  (regression) (util-linux 2.34-0.1ubuntu9).

  Eoan is EOL, so removed.

  
  [Test case]

  Commit has good test case. I paste it here

  Before:

$ touch file-found
$ ln -s file-found symlink-1
$ ./rename sym symbolic- symlink-1  # XPASS.
$ echo $?
0

$ ln -s file-not-found symlink-2
$ ./rename sym symbolic- symlink-2  # FAIL! REGRESSION.
rename: symlink-2: not accessible: No such file or directory
$ echo $?
1

$ ./rename sym symbolic- symlink-3  # XFAIL.
rename: symlink-3: not accessible: No such file or directory
$ echo $?
1

$ touch file-found
$ ./rename found existing file-found# XPASS.
$ echo $?
0

$ ./rename found existing file-not-found # XFAIL.
rename: file-not-found: not accessible: No such file or directory
$ echo $?
1

  After:

$ touch file-found
$ ln -s file-found symlink-1
$ ./rename sym symbolic- symlink-1  # XPASS.
$ echo $?
0

$ ln -s file-not-found symlink-2
$ ./rename sym symbolic- symlink-2  # PASS! REGRESSION FIXED.
$ echo $?
0

$ ./rename sym symbolic- symlink-3  # XFAIL.
rename: symlink-3: not accessible: No such file or directory
$ echo $?
1

$ touch file-found
$ ./rename found existing file-found# XPASS.
$ echo $?
0

$ ./rename found existing file-not-found # XFAIL.
rename: file-not-found: not accessible: No such file or directory
$ echo $?
1

  
  [Regression Potential]
  This commit changes code that checking accessibility to file or sym link. 
  If this fails, rename command will not work properly.it could be crashed or 
causes failure of rename. 

  
  [Original Description]

  rename.ul refuses to rename links that don't resolve.

  bionic rename.ul renames links whether or not they resolve (util-linux
  2.31.1-0.4ubuntu3.6).

  focal rename.ul refuses to rename links that don't resolve
  (regression) (util-linux 2.34-0.1ubuntu9).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jul  4 20:38:06 2020
  InstallationDate: Installed on 2020-04-05 (90 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886300/+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 1886300] Re: rename.ul refuses to rename links that don't resolve (regression)

2020-09-15 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.34-0.1ubuntu9.1

---
util-linux (2.34-0.1ubuntu9.1) focal; urgency=medium

  * d/p/rename_fix_regression_for_symlink_with_non-existing_target.patch
- rename: fix regression for symlink with non-existing target
  (LP: #1886300)

 -- Seyeong Kim   Tue, 21 Jul 2020 16:49:28
+0900

** Changed in: util-linux (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  rename.ul refuses to rename links that don't resolve (regression)

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux source package in Groovy:
  Fix Released
Status in util-linux package in Debian:
  Fix Released

Bug description:
  [Impact]

  rename.ul refuses to rename links that don't resolve.

  bionic rename.ul renames links whether or not they resolve (util-linux
  2.31.1-0.4ubuntu3.6).

  focal rename.ul refuses to rename links that don't resolve
  (regression) (util-linux 2.34-0.1ubuntu9).

  Eoan is EOL, so removed.

  
  [Test case]

  Commit has good test case. I paste it here

  Before:

$ touch file-found
$ ln -s file-found symlink-1
$ ./rename sym symbolic- symlink-1  # XPASS.
$ echo $?
0

$ ln -s file-not-found symlink-2
$ ./rename sym symbolic- symlink-2  # FAIL! REGRESSION.
rename: symlink-2: not accessible: No such file or directory
$ echo $?
1

$ ./rename sym symbolic- symlink-3  # XFAIL.
rename: symlink-3: not accessible: No such file or directory
$ echo $?
1

$ touch file-found
$ ./rename found existing file-found# XPASS.
$ echo $?
0

$ ./rename found existing file-not-found # XFAIL.
rename: file-not-found: not accessible: No such file or directory
$ echo $?
1

  After:

$ touch file-found
$ ln -s file-found symlink-1
$ ./rename sym symbolic- symlink-1  # XPASS.
$ echo $?
0

$ ln -s file-not-found symlink-2
$ ./rename sym symbolic- symlink-2  # PASS! REGRESSION FIXED.
$ echo $?
0

$ ./rename sym symbolic- symlink-3  # XFAIL.
rename: symlink-3: not accessible: No such file or directory
$ echo $?
1

$ touch file-found
$ ./rename found existing file-found# XPASS.
$ echo $?
0

$ ./rename found existing file-not-found # XFAIL.
rename: file-not-found: not accessible: No such file or directory
$ echo $?
1

  
  [Regression Potential]
  This commit changes code that checking accessibility to file or sym link. 
  If this fails, rename command will not work properly.it could be crashed or 
causes failure of rename. 

  
  [Original Description]

  rename.ul refuses to rename links that don't resolve.

  bionic rename.ul renames links whether or not they resolve (util-linux
  2.31.1-0.4ubuntu3.6).

  focal rename.ul refuses to rename links that don't resolve
  (regression) (util-linux 2.34-0.1ubuntu9).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jul  4 20:38:06 2020
  InstallationDate: Installed on 2020-04-05 (90 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886300/+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 1267866] Re: usb audio: cannot get ctl value: req = 0x81, wValue = 0x0, wIndex = 0x1400, type = 3

2020-09-15 Thread Ryan Nunes
Just a heads up.. Noticed this post digging into the same exact syptoms
with a schiit hel on arch linux. (5.8.8 kernel). I was able to resolve
the lack of audio by installing and using pulsemixer. Using pulsemixer
if you hit f3 (cards) and set the audio source from off to digital
stereo duplex it should prevent alsa crashing and actually allow the
audio source to work.

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

Title:
  usb audio: cannot get ctl value: req = 0x81, wValue = 0x0, wIndex =
  0x1400, type = 3

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  I typed in terminal:

  alsamixer

  Then I wanted to change the sound card (I have connected an external
  sound card via USB).

  I pressed F6, selected the external sound card and pressed enter.

  alsamixer crashed and outputed:

  cannot load mixer controls: Broken pipe

  My ALSA information is located at http://www.alsa-
  project.org/db/?f=1871c086b58a2965d18cfb38483794788187edfb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1267866/+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 1887210] Re: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer

2020-09-15 Thread Ryan Nunes
Just a heads up.. Noticed this post digging into the same exact syptoms
with a schiit hel on arch linux. (5.8.8 kernel). I was able to resolve
the lack of audio by installing and using pulsemixer. Using pulsemixer
if you hit f3 (cards) and set the audio source from off to digital
stereo duplex it should prevent alsa crashing and actually allow the
audio source to work.

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

Title:
  USB DAC/AMP unselectable from Sound Settings  and crashes alsamixer

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I am experiencing the same issue with the same device described in
  this report comment: https://bugs.launchpad.net/ubuntu/+source/alsa-
  driver/+bug/1267866/comments/26

  The device works as expected with Windows 10 and macOS no drivers
  required. However, the device is not an option from Ubuntu's sound
  settings. It is visible in alsamixer, however, it crashes immediately
  upon selection with 'cannot load mixer controls: Broken pipe'.

  Here's some more debug information. Let me know if there is anymore I
  can provide or feel free to redirect me if there is another place this
  is better reported.

  Device: Schiit Audio Fulla 3 USB DAC/AMP
  Kernel version: 5.4.0-40-generic
  Ubuntu version: 20.04

  Alsa debug output: http://alsa-
  project.org/db/?f=3f494b2155bdde7f5ee0e52240da77468bcb

  `dmesg -w` output upon re-plugging in the device:
  [  895.624302] usb 3-2.3: new high-speed USB device number 8 using xhci_hcd
  [  895.739125] usb 3-2.3: New USB device found, idVendor=30be, 
idProduct=0100, bcdDevice= 1.02
  [  895.739129] usb 3-2.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [  895.739131] usb 3-2.3: Product: I'm Fulla Schiit
  [  895.739133] usb 3-2.3: Manufacturer: Schiit Audio
  [  896.076914] input: Schiit Audio I'm Fulla Schiit as 
/devices/pci:00/:00:07.1/:11:00.3/usb3/3-2/3-2.3/3-2.3:1.3/0003:30BE:0100.0007/input/input20
  [  896.136457] hid-generic 0003:30BE:0100.0007: input,hidraw5: USB HID v1.00 
Device [Schiit Audio I'm Fulla Schiit] on usb-:11:00.3-2.3/input3
  [  896.228480] audit: type=1107 audit(1594446870.681:57): pid=1286 uid=105 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal"  
bus="system" path="/org/freedesktop/NetworkManager" 
interface="org.freedesktop.NetworkManager" member="CheckPermissions" 
name=":1.8" mask="receive" pid=10228 label="snap.spotify.spotify" peer_pid=1287 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'
  [  896.238190] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, 
wIndex = 0x1100, type = 1
  [  896.298659] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, 
wIndex = 0x1100, type = 1
  [  896.427249] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, 
wIndex = 0x1100, type = 1
  [  896.618498] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, 
wIndex = 0x1100, type = 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1887210/+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 1895454] Re: ibus indicator is unreadable, and the dropdown doesn't clarify what option is selected

2020-09-15 Thread Gunnar Hjalmarsson
On 2020-09-15 18:26, php4fan wrote:
> Most icon have bright colors, which seems to suggest that if there is
> an expectation about the background color, it's that it is dark,
> which my current panel background is.

Dark blue is probably not an optimal default.

I would suggest that you file an upstream issue about it:

https://github.com/ibus/ibus/issues/

If you do, please post the URL to it here. We can keep this bug open for
now for tracking purposes.

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

Title:
  ibus indicator is unreadable, and the dropdown doesn't clarify what
  option is selected

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  I don't know exactly what iBus is and what it does, but it has this
  indicator on the bottom-right corner of the screen (whatever that area
  is called) which shows what the currently selected input language is,
  whatever that means. For example, on my system there are two choices
  available: "Spanish - Spanish" and "English - English (US)", and
  therefore the indicator shows either "ES" or "EN" depending on which
  one is selected. Whatever the effect of that is.

  The issue is, this indicator is designed with an idiotic choice of
  colours: a very dark blue text on a very dark gray background, which
  makes it mostly unreadable. I am not color blind nor visually
  impaired, yet both colors are almost undistinguishable to me, and it
  costs me a great effort to tell whether it says "EN" or "ES".

  Additionally, adding to the idiocy, if I click on it to see which one
  is actually selected, a dropdown unfolds where the two options are
  listed, and the currently selected one is not highlighted in any way!!
  It seems that the selected one is always shown first, which, assuming
  it's true, I can only learn by changing the selection back and forth,
  when it could have been as easy as showing the currently selected one
  in bold.

  It looks as if every single possible step had been purposefully taken
  to make this less useful, because even by doing it carelessly and
  without putting any thought into it, it's unlikely that it could turn
  out so ridiculously badly designed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Sun Sep 13 15:38:34 2020
  InstallationDate: Installed on 2013-10-11 (2528 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to focal on 2020-07-12 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1895454/+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 1895294] Re: Fix Raccoon vulnerability (CVE-2020-1968)

2020-09-15 Thread Seth Arnold
Alternatively, you could use one of the recommended TLS configurations
from Mozilla, https://wiki.mozilla.org/Security/Server_Side_TLS which do
not enable the unsafe cryptography suites.

Thanks

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

Title:
  Fix Raccoon vulnerability (CVE-2020-1968)

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Confirmed

Bug description:
  Xenial's current OpenSSL (1.0.2g-1ubuntu4.16) seems to not have been
  patched yet against the Raccoon Attack (CVE-2020-1968):

  - https://www.openssl.org/news/secadv/20200909.txt
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1968
  - https://raccoon-attack.com/

  Ubuntu's CVE tracker still lists this as NEEDED for Xenial:

  - https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-1968.html
  - https://people.canonical.com/~ubuntu-security/cve/pkg/openssl.html

  Other supported Ubuntu releases use versions of OpenSSL that are not
  affected.

  Indeed:

    $ apt-cache policy openssl
    openssl:
  Installed: 1.0.2g-1ubuntu4.16

    $ apt-get changelog openssl | grep CVE-2020-1968 || echo "Not patched"
    Not patched

  What is the status?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1895294/+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 1799928] Re: [20.10 FEAT] openssl: RNG support

2020-09-15 Thread Dimitri John Ledkov
The patch mentioned alone does not apply on 1.1.1f in Ubuntu, it seems
it also needs

9cc834d966ea5afc38fb829bfe498aed4c5d498d
0d011f540400b425aba1c3e59624ad9dbabe83cb
a1ec85c169a8e53e52ab35914ad47b5baea84070
53eb05bdf00d7237e3b12976c2ac38d68206eb13
e6a80cbad28ee748830815634917efe96948f2f3

Will try this set next.

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

Title:
  [20.10 FEAT] openssl: RNG support

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl package in Ubuntu:
  In Progress

Bug description:
  Provide a CPACF based random number generator for openSSL using PRNO-
  SHA-512-DRNG to implement a NIST SP800-90A compliant SHA512 hash based
  deterministic random bit generator (DRBG) seeded true random numbers
  extracted using the PRNO-TRNG instruction.

  Planned with > openssl 1.1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1799928/+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 1895294] Re: Fix Raccoon vulnerability (CVE-2020-1968)

2020-09-15 Thread Nils Toedtmann
> "Please upgrade to bionic or focal?"

Is this an official recommendation from Ubuntu, that users shall migrate
off Xenial now, because of a security issue in a core library?

And there I was, thinking we have until April 2021 ...

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

Title:
  Fix Raccoon vulnerability (CVE-2020-1968)

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Confirmed

Bug description:
  Xenial's current OpenSSL (1.0.2g-1ubuntu4.16) seems to not have been
  patched yet against the Raccoon Attack (CVE-2020-1968):

  - https://www.openssl.org/news/secadv/20200909.txt
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1968
  - https://raccoon-attack.com/

  Ubuntu's CVE tracker still lists this as NEEDED for Xenial:

  - https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-1968.html
  - https://people.canonical.com/~ubuntu-security/cve/pkg/openssl.html

  Other supported Ubuntu releases use versions of OpenSSL that are not
  affected.

  Indeed:

    $ apt-cache policy openssl
    openssl:
  Installed: 1.0.2g-1ubuntu4.16

    $ apt-get changelog openssl | grep CVE-2020-1968 || echo "Not patched"
    Not patched

  What is the status?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1895294/+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 1895708] Re: Openssl should integrate with needrestart better

2020-09-15 Thread Dimitri John Ledkov
** Changed in: openssl (Ubuntu)
   Status: New => Triaged

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

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

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

Title:
  Openssl should integrate with needrestart better

Status in openssl package in Ubuntu:
  Triaged

Bug description:
  [Impact]

   * needrestart is a better solution to track and restart services that use 
openssl
   * when needrestart is available, openssl should not ask about restarting 
services or rebooting the host, as needrestart is a better way to report that.

  [Test Case]

   * Install needrestart
   * Upgrade openssl
   * Observe that openssl debconf questions about restarting services are not 
raised, and requirement to reboot the system is not raised

  [Regression Potential]

   * Needrestart may be installed, but dpkg/apt hooks could have been
  disabled, in such scenarios one may not see any notifications that one
  needs to do something to their system to ensure that openssl using
  applications are restarted to become protected.

  [Other Info]
   
   * glibc, libpam potentially need similar fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1895708/+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 1895708] [NEW] Openssl should integrate with needrestart better

2020-09-15 Thread Dimitri John Ledkov
Public bug reported:

[Impact]

 * needrestart is a better solution to track and restart services that use 
openssl
 * when needrestart is available, openssl should not ask about restarting 
services or rebooting the host, as needrestart is a better way to report that.

[Test Case]

 * Install needrestart
 * Upgrade openssl
 * Observe that openssl debconf questions about restarting services are not 
raised, and requirement to reboot the system is not raised

[Regression Potential]

 * Needrestart may be installed, but dpkg/apt hooks could have been
disabled, in such scenarios one may not see any notifications that one
needs to do something to their system to ensure that openssl using
applications are restarted to become protected.

[Other Info]
 
 * glibc, libpam potentially need similar fixes.

** Affects: openssl (Ubuntu)
 Importance: Wishlist
 Status: Triaged

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

Title:
  Openssl should integrate with needrestart better

Status in openssl package in Ubuntu:
  Triaged

Bug description:
  [Impact]

   * needrestart is a better solution to track and restart services that use 
openssl
   * when needrestart is available, openssl should not ask about restarting 
services or rebooting the host, as needrestart is a better way to report that.

  [Test Case]

   * Install needrestart
   * Upgrade openssl
   * Observe that openssl debconf questions about restarting services are not 
raised, and requirement to reboot the system is not raised

  [Regression Potential]

   * Needrestart may be installed, but dpkg/apt hooks could have been
  disabled, in such scenarios one may not see any notifications that one
  needs to do something to their system to ensure that openssl using
  applications are restarted to become protected.

  [Other Info]
   
   * glibc, libpam potentially need similar fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1895708/+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 1799928] Re: [20.10 FEAT] openssl: RNG support

2020-09-15 Thread Dimitri John Ledkov
** Information type changed from Private to Public

** Changed in: openssl (Ubuntu)
   Status: Incomplete => In Progress

** Changed in: ubuntu-z-systems
   Status: Expired => In Progress

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

Title:
  [20.10 FEAT] openssl: RNG support

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl package in Ubuntu:
  In Progress

Bug description:
  Provide a CPACF based random number generator for openSSL using PRNO-
  SHA-512-DRNG to implement a NIST SP800-90A compliant SHA512 hash based
  deterministic random bit generator (DRBG) seeded true random numbers
  extracted using the PRNO-TRNG instruction.

  Planned with > openssl 1.1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1799928/+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 1888101] Re: 'unsupported protocol' error when using PyMySQL

2020-09-15 Thread Dimitri John Ledkov
If you require using obsolete, deprecated, old protocols, with weak
keys, and broken hash algorithms you can use these instructions to
downgrade security on your systems https://discourse.ubuntu.com/t
/default-to-tls-v1-2-in-all-tls-libraries-in-20-04-lts/12464/8?u=xnox

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

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

Title:
  'unsupported protocol' error when using PyMySQL

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  1)
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2)
  openssl:
Installiert:   1.1.1f-1ubuntu2
Installationskandidat: 1.1.1f-1ubuntu2
Versionstabelle:
   *** 1.1.1f-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) + 4)
  I am trying to connect to my MariaDB with python package "PyMySQL" and SSL 
enabled. On my old installation (Kubuntu 19.10) this worked. With the new 
installation (also new PC: Xubuntu 20.04) I get this error message:

  ssl.SSLError: [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol
  (_ssl.c:1108)

  Here are my installation details:
  Old installation: python 3.7.5, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1c 
28 May 2019
  New installation: python 3.8.2, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1f 
31 Mar 2020

  When I use python with a different SSL version...:
  this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.0m-dev xx XXX 
  this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX 
  this works: python 3.8.2, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX 

  
  It seems, like the one specific version of openSSL (1.1.1f 31 Mar 2020) does 
not work together with PyMySQL.

  Some more details I have posted here:
  
https://stackoverflow.com/questions/62964998/unsupported-protocol-error-when-using-pymysql

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1f-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Jul 18 15:42:27 2020
  InstallationDate: Installed on 2020-07-13 (4 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1888101/+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 1879826] Re: User interface error when executing openssl from a daemon

2020-09-15 Thread Dimitri John Ledkov
** Changed in: openssl (Ubuntu)
   Status: New => In Progress

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

Title:
  User interface error when executing openssl from a daemon

Status in openssl package in Ubuntu:
  In Progress

Bug description:
  When a daemon executes `openssl` using fork()+execl() it get the
  following error:

  User interface error 139953222812992:error:2807206C:UI
  routines:open_console:unknown ttyget errno
  value:../crypto/ui/ui_openssl.c:454:errno=1
  139953222812992:error:2807106B:UI routines:UI_process:processing
  error:../crypto/ui/ui_lib.c:545:while opening session unable to load
  CA private key 139953222812992:error:06065064:digital envelope
  routines:EVP_DecryptFinal_ex:bad decrypt:../crypto/evp/evp_enc.c:588:
  139953222812992:error:0906A065:PEM routines:PEM_do_header:bad
  decrypt:../crypto/pem/pem_lib.c:461:

  The problem has been fixed in upstream openssl: 
https://github.com/openssl/openssl/commit/082394839ea32386abc7ee33aaa9da864287064c
  See the relevant issue here: https://github.com/openssl/openssl/pull/11767

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1f-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 10:51:27 2020
  InstallationDate: Installed on 2020-04-09 (41 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1879826/+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 1876790] Re: cannot connect to the mail server

2020-09-15 Thread Dimitri John Ledkov
Please use https://www.orange.sk/napiste-nam/internetove-sluzby
/vseobecne-informacie-o-internetovych-sluzbach-a-ich-dostupnosti with
your mobile phone number requesting orange to add support for TLSv1.2

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

Title:
  cannot connect to the mail server

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  Hi, 
 After upgrade lubuntu on 20.04 both email clients Trojita and Sylpheed 
cannot connect to the mail server. from the log: 
  creating IMAP4 connection to imap4.orangemail.sk:993 ...
  ** LibSylph-WARNING: SSL_connect() failed with error 1, ret = -1 
(error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol)

  problem with ssl?
  OpenSSL 1.1.1f  31 Mar 2020

  I try:
  openssl s_client -host imap4.orangemail.sk -port 993 -prexit 
  CONNECTED(0003)
  140518603695424:error:1425F102:SSL 
routines:ssl_choose_client_version:unsupported 
protocol:../ssl/statem/statem_lib.c:1941:
  ..

  lsb_release -rd
  Description:Ubuntu 20.04 LTS
  Release:20.04

  By

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1876790/+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 1878519] Re: Unable to use TLSv1.1 to connect to external servers

2020-09-15 Thread Dimitri John Ledkov
Instructions on how to make your system insecure and easy to hack are
here https://discourse.ubuntu.com/t/default-to-tls-v1-2-in-all-tls-
libraries-in-20-04-lts/12464/8?u=xnox

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

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

Title:
  Unable to use TLSv1.1 to connect to external servers

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  I'm on 20.04 LTS (Focal Fossa). (Kubuntu)

  openssl (I'm on 1.1.1f-1ubuntu2) appears to now be set to use a
  minimum of TLSv1.2

  This is despite the fact that the Changelog 
(https://launchpad.net/ubuntu/+source/openssl/+changelog) says:
Revert "Enable system default config to enforce TLS1.2 as a
minimum" & "Increase default security level from 1 to 2".

  As a result of this I can't get fetchmail to connect to an external
  IMPA server I use, which only uses TLSv1.1

  I *can* get:
openssl s_client -state -cipher "DEFAULT:@SECLEVEL=1" -connect ... 
-starttls imap
  to open a connexion, but I can find no way of getting that option into a 
configuration file such that it is used.

  Consequently I cannot use a secure connexion to retrieve my emails.

  All was fine in 19.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1878519/+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 1884147] Re: package libssl1.1 1.1.1f-1ubuntu2 [modified: usr/share/doc/libssl1.1/NEWS.Debian.gz usr/share/doc/libssl1.1/changelog.Debian.gz] failed to install/upgrade: trying to

2020-09-15 Thread Dimitri John Ledkov
a legacy app most likely will not be using libssl1.1 but the older
libssl1.0.0 which is no longer provided in ubuntu.

you need to create a chroot or a VM, or manually enable old series to
download old libssl1.0 which may still be available for i386.

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

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

Title:
  package libssl1.1 1.1.1f-1ubuntu2 [modified:
  usr/share/doc/libssl1.1/NEWS.Debian.gz
  usr/share/doc/libssl1.1/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from
  other instances of package libssl1.1:i386

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  Attempting to install legacy 32 bit version of libssl.so.1.0.0 to
  allow an old app to run.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libssl1.1 1.1.1f-1ubuntu2 [modified: 
usr/share/doc/libssl1.1/NEWS.Debian.gz 
usr/share/doc/libssl1.1/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  AptOrdering:
   libssl1.1:i386: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jun 18 14:37:52 2020
  DpkgTerminalLog:
   Preparing to unpack .../libssl1.1_1.1.1f-1ubuntu2_i386.deb ...
   Unpacking libssl1.1:i386 (1.1.1f-1ubuntu2) over (1.1.1-1ubuntu2.1~18.04.5) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/libssl1.1_1.1.1f-1ubuntu2_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which 
is different from other instances of package libssl1.1:i386
  DuplicateSignature:
   package:libssl1.1:1.1.1f-1ubuntu2 [modified: 
usr/share/doc/libssl1.1/NEWS.Debian.gz 
usr/share/doc/libssl1.1/changelog.Debian.gz]
   Unpacking libssl1.1:i386 (1.1.1f-1ubuntu2) over (1.1.1-1ubuntu2.1~18.04.5) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/libssl1.1_1.1.1f-1ubuntu2_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which 
is different from other instances of package libssl1.1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from other 
instances of package libssl1.1:i386
  InstallationDate: Installed on 2020-02-21 (118 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: openssl
  Title: package libssl1.1 1.1.1f-1ubuntu2 [modified: 
usr/share/doc/libssl1.1/NEWS.Debian.gz 
usr/share/doc/libssl1.1/changelog.Debian.gz] failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is 
different from other instances of package libssl1.1:i386
  UpgradeStatus: Upgraded to focal on 2020-05-09 (40 days ago)

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

2020-09-15 Thread Dimitri John Ledkov
Please attempt to reinstall / upgrade the package again.

I.e. $ sudo dpkg --configure -a

or

$ sudo apt install --reinstall libssl1.1

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

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

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

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  failed to update package

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-1027.32-oem 4.15.18
  Uname: Linux 4.15.0-1027-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Aug 27 14:15:05 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+matira-5-7-r+X58
  ErrorMessage: installed libssl1.1:amd64 package post-installation script 
subprocess returned error exit status 128
  InstallationDate: Installed on 2020-08-06 (21 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.1
  SourcePackage: openssl
  Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.6 failed to 
install/upgrade: installed libssl1.1:amd64 package post-installation script 
subprocess returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1893264/+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 1895454] Re: ibus indicator is unreadable, and the dropdown doesn't clarify what option is selected

2020-09-15 Thread php4fan
The bug is not invalid. It may belong to ibus or to Cinnamon or to
something else.

Are all icons supposed to have transparent backgrounds? If so, that
would mean that both icons and desktop environments should adhere to
strict color guidelines so that icons are always guaranteed to be
legible. Do such guidelines exist? If so, either (a) this icon does not
have an acceptable color, or (b) Cinnamon's panel does not have an
acceptable background color, or (c) the guidelines are not good enough.

If there are no such guidelines, then icons should never have a
completely transparent background without any border. That is, they
should be designed in whatever way that guarantees that they are visible
on any backround.

So, something is wrong somewhere, either in how the icon is designed, or
in how the desktop environment is designed, or in the the framework
where the desktop and the icons live.

That the user can change the icon color is cool but is not a solution.
The icon must be visible out of the box.


So far, iBus icon is the only one I've ever seen that is practically invisible.
Most icon have bright colors, which seems to suggest that if there is an 
expectation about the background color, it's that it is dark, which my current 
panel background is.

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

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

Title:
  ibus indicator is unreadable, and the dropdown doesn't clarify what
  option is selected

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  I don't know exactly what iBus is and what it does, but it has this
  indicator on the bottom-right corner of the screen (whatever that area
  is called) which shows what the currently selected input language is,
  whatever that means. For example, on my system there are two choices
  available: "Spanish - Spanish" and "English - English (US)", and
  therefore the indicator shows either "ES" or "EN" depending on which
  one is selected. Whatever the effect of that is.

  The issue is, this indicator is designed with an idiotic choice of
  colours: a very dark blue text on a very dark gray background, which
  makes it mostly unreadable. I am not color blind nor visually
  impaired, yet both colors are almost undistinguishable to me, and it
  costs me a great effort to tell whether it says "EN" or "ES".

  Additionally, adding to the idiocy, if I click on it to see which one
  is actually selected, a dropdown unfolds where the two options are
  listed, and the currently selected one is not highlighted in any way!!
  It seems that the selected one is always shown first, which, assuming
  it's true, I can only learn by changing the selection back and forth,
  when it could have been as easy as showing the currently selected one
  in bold.

  It looks as if every single possible step had been purposefully taken
  to make this less useful, because even by doing it carelessly and
  without putting any thought into it, it's unlikely that it could turn
  out so ridiculously badly designed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Sun Sep 13 15:38:34 2020
  InstallationDate: Installed on 2013-10-11 (2528 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to focal on 2020-07-12 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1895454/+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 1698388] Update Released

2020-09-15 Thread Brian Murray
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Assertion failure in journal-remote-parse.c

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [impact]

  assertion failure in systemd-journal-remote

  [test case]

  only happens under specific circumstances, which is unclear exactly
  how to reproduce it

  [regression potential]

  any regression would likely result in the failure/crash of systemd-
  journal-remote program while processing data from a remote source.

  [scope]

  this is needed only for x.

  this is fixed by commit 9ba37525d0ef3d144a50ed5fd4710573e92b7ec1 which
  is included upstream starting in v230, so this is already included in
  b and later.

  [original description]

  I am observing the following assertion failure in systemd-journal-
  remote:

  Assertion 'source->filled <= source->size' failed at ../src/journal-
  remote/journal-remote-parse.c:95, function get_line(). Aborting.

  Systemd version:

  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Ubuntu release:

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Package version:

  systemd:
    Installed: 229-4ubuntu13
    Candidate: 229-4ubuntu17

  It looks like this issue has been fixed upstream in v230, specifically
  in commit 9ba37525d0ef3d144a50ed5fd4710573e92b7ec1. Could this
  particular commit be backported?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698388/+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 1698388] Re: Assertion failure in journal-remote-parse.c

2020-09-15 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 229-4ubuntu21.29

---
systemd (229-4ubuntu21.29) xenial; urgency=medium

  [ Dan Streetman ]
  * 
d/p/lp1881312/0001-core-don-t-dispatch-load-queue-when-setting-Slice-fo.patch,
d/p/lp1881312/0002-run-make-slice-work-in-conjunction-with-scope.patch:
- run new scope unit in specified slice (LP: #1881312)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5a778c3cd93e3d684602146f281f315f30778a8
  * d/p/lp1877176-sd-dhcp-client-validate-hostnames-stricter-7308.patch:
- strictly validate hostname sent to dhcp server (LP: #1877176)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a1f1c41dcd860fcba6be42a2153cfe4315ebf17
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=43357bd260a1c3e7b4951d33cbacaebda1d086b3
  * d/p/lp1698388-journal-remote-Ensure-reallocation-of-source-buf-doe.patch:
- Fix assertion failure when journald source->filled < source->size
  (LP: #1698388)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1cc15b88113510227e5a76654e103ef54a8b8f3

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8dc9ef188944349169044d8974a4ffa55c66be9d

 -- Heitor Alves de Siqueira   Tue, 07 Jul 2020
17:28:11 -0400

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

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

Title:
  Assertion failure in journal-remote-parse.c

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [impact]

  assertion failure in systemd-journal-remote

  [test case]

  only happens under specific circumstances, which is unclear exactly
  how to reproduce it

  [regression potential]

  any regression would likely result in the failure/crash of systemd-
  journal-remote program while processing data from a remote source.

  [scope]

  this is needed only for x.

  this is fixed by commit 9ba37525d0ef3d144a50ed5fd4710573e92b7ec1 which
  is included upstream starting in v230, so this is already included in
  b and later.

  [original description]

  I am observing the following assertion failure in systemd-journal-
  remote:

  Assertion 'source->filled <= source->size' failed at ../src/journal-
  remote/journal-remote-parse.c:95, function get_line(). Aborting.

  Systemd version:

  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Ubuntu release:

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Package version:

  systemd:
    Installed: 229-4ubuntu13
    Candidate: 229-4ubuntu17

  It looks like this issue has been fixed upstream in v230, specifically
  in commit 9ba37525d0ef3d144a50ed5fd4710573e92b7ec1. Could this
  particular commit be backported?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698388/+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 1876018] Re: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters

2020-09-15 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 229-4ubuntu21.29

---
systemd (229-4ubuntu21.29) xenial; urgency=medium

  [ Dan Streetman ]
  * 
d/p/lp1881312/0001-core-don-t-dispatch-load-queue-when-setting-Slice-fo.patch,
d/p/lp1881312/0002-run-make-slice-work-in-conjunction-with-scope.patch:
- run new scope unit in specified slice (LP: #1881312)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5a778c3cd93e3d684602146f281f315f30778a8
  * d/p/lp1877176-sd-dhcp-client-validate-hostnames-stricter-7308.patch:
- strictly validate hostname sent to dhcp server (LP: #1877176)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a1f1c41dcd860fcba6be42a2153cfe4315ebf17
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=43357bd260a1c3e7b4951d33cbacaebda1d086b3
  * d/p/lp1698388-journal-remote-Ensure-reallocation-of-source-buf-doe.patch:
- Fix assertion failure when journald source->filled < source->size
  (LP: #1698388)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1cc15b88113510227e5a76654e103ef54a8b8f3

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8dc9ef188944349169044d8974a4ffa55c66be9d

 -- Heitor Alves de Siqueira   Tue, 07 Jul 2020
17:28:11 -0400

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

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

Title:
  40-vm-hotadd.rules attempts to set non-existent sysfs parameters

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

Bug description:
  [impact]

  40-vm-hotadd.rules unconditionally tries onlining memory, which
  results in logged error messages if the memory is already online

  [test case]

  since this rules file restricts operation to only hyper-v or xen
  guests, boot a hyper-v or xen vm guest, and check for logged error
  msgs like:

  Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
  /usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
  ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
  argument

  alternately, to test on a vm guest other than hyper-v or xen,
  comment/remove the 'GOTO="vm_hotadd_end"' line from the rules file and
  reboot.

  [regression potential]

  as this adds a check before attempting to online memory for hyper-v
  and xen vm guests, any regression would likely involve failure to
  correctly online all memory on those guest platforms.

  [scope]

  this rule has been around for a long time, so is needed for x/b/f/g.

  [original description]

  In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
  tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
  resulting in warnings such as:

  Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
  /usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
  ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
  argument

  Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
  removed, or something else. This behavior is present on systems
  upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
  first reboot of the VM.

  udev: 245.4-4ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+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 1877176] Re: 64-char hostname causes dhcp server to reject lease

2020-09-15 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 229-4ubuntu21.29

---
systemd (229-4ubuntu21.29) xenial; urgency=medium

  [ Dan Streetman ]
  * 
d/p/lp1881312/0001-core-don-t-dispatch-load-queue-when-setting-Slice-fo.patch,
d/p/lp1881312/0002-run-make-slice-work-in-conjunction-with-scope.patch:
- run new scope unit in specified slice (LP: #1881312)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5a778c3cd93e3d684602146f281f315f30778a8
  * d/p/lp1877176-sd-dhcp-client-validate-hostnames-stricter-7308.patch:
- strictly validate hostname sent to dhcp server (LP: #1877176)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a1f1c41dcd860fcba6be42a2153cfe4315ebf17
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=43357bd260a1c3e7b4951d33cbacaebda1d086b3
  * d/p/lp1698388-journal-remote-Ensure-reallocation-of-source-buf-doe.patch:
- Fix assertion failure when journald source->filled < source->size
  (LP: #1698388)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1cc15b88113510227e5a76654e103ef54a8b8f3

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8dc9ef188944349169044d8974a4ffa55c66be9d

 -- Heitor Alves de Siqueira   Tue, 07 Jul 2020
17:28:11 -0400

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

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

Title:
  64-char hostname causes dhcp server to reject lease

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [impact]

  a systemd with a 64-character hostname (the maximum hostname length
  for Linux) will cause a dhcp server to reject its dhcp lease due to
  passing the invalid hostname in the dhcp lease request.

  [test case]

  $ cat /etc/systemd/network/10-ens3.network
  [Match]
  Name=ens3

  [Network]
  DHCP=yes

  set hostname to 64-char name, e.g.:

  $ sudo hostnamectl set-hostname
  a123456789b123456789c123456789d123456789e123456789f123456789g123

  restart networkd:

  $ sudo systemctl restart systemd-networkd

  check logs:

  root@a123456789b123456789c123456789d123456789e123456789f123456789g123:~# 
journalctl -b -u systemd-networkd --no-pager | grep 'DHCP error'
  May 06 19:01:30 
a123456789b123456789c123456789d123456789e123456789f123456789g123 
systemd-networkd[737]: ens3: DHCP error: Client failed: Invalid argument

  [regression potential]

  Any regression would likely result in failure configuring/processing
  dhcpv4 server response, or rejection from the dhcpv4 server.

  [scope]

  this is fixed by commit 9740eae694e93b06658ff3b3045b22b591561e7c which
  is included in Bionic and later.  This is needed only for Xenial.

  [other info]

  this is a follow on to bug 1862232, which corrected sd-dhcp-client.c
  to continue networkd dhcp even if the hostname is invalid, however the
  older code in Xenial doesn't correctly detect the invalid hostname, so
  this additional patch is needed.

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

2020-09-15 Thread Brian Murray
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  64-char hostname causes dhcp server to reject lease

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [impact]

  a systemd with a 64-character hostname (the maximum hostname length
  for Linux) will cause a dhcp server to reject its dhcp lease due to
  passing the invalid hostname in the dhcp lease request.

  [test case]

  $ cat /etc/systemd/network/10-ens3.network
  [Match]
  Name=ens3

  [Network]
  DHCP=yes

  set hostname to 64-char name, e.g.:

  $ sudo hostnamectl set-hostname
  a123456789b123456789c123456789d123456789e123456789f123456789g123

  restart networkd:

  $ sudo systemctl restart systemd-networkd

  check logs:

  root@a123456789b123456789c123456789d123456789e123456789f123456789g123:~# 
journalctl -b -u systemd-networkd --no-pager | grep 'DHCP error'
  May 06 19:01:30 
a123456789b123456789c123456789d123456789e123456789f123456789g123 
systemd-networkd[737]: ens3: DHCP error: Client failed: Invalid argument

  [regression potential]

  Any regression would likely result in failure configuring/processing
  dhcpv4 server response, or rejection from the dhcpv4 server.

  [scope]

  this is fixed by commit 9740eae694e93b06658ff3b3045b22b591561e7c which
  is included in Bionic and later.  This is needed only for Xenial.

  [other info]

  this is a follow on to bug 1862232, which corrected sd-dhcp-client.c
  to continue networkd dhcp even if the hostname is invalid, however the
  older code in Xenial doesn't correctly detect the invalid hostname, so
  this additional patch is needed.

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

2020-09-15 Thread Brian Murray
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  systemd-run does not make the new scope unit part of the slice
  specified via the --slice arg

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [impact]

  running 'systemd-run --scope --slice=$SLICE $PROGRAM' does not start
  the program under $SLICE, instead it starts it under system.slice

  [test case]

  root:~# systemd-run --scope --slice=user-1000.slice sleep 1000
  Running scope as unit run-r16d872f1b0894b88a79421a890269e6c.scope.
  ^Z
  [3]+  Stopped systemd-run --scope --slice=user-1000.slice 
sleep 1000
  root:~# bg
  [3]+ systemd-run --scope --slice=user-1000.slice sleep 1000 &
  root:~# systemctl show -p Slice run-r16d872f1b0894b88a79421a890269e6c.scope
  Slice=system.slice

  [regression potential]

  This defers running the manager unit load queue when setting the slice
  for a transient unit, as well as actually passing the slice parameter
  over the bus when using --scope, so any regression would very likely
  involve incorrectly setting the slice for a scope and/or problems when
  processing transient units that specify a slice.

  [scope]

  this is needed only for Xenial.

  this is fixed upstream by
  https://github.com/systemd/systemd/pull/3094
  which is included starting in v230, so is included in Bionic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1881312/+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 1881312] Re: systemd-run does not make the new scope unit part of the slice specified via the --slice arg

2020-09-15 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 229-4ubuntu21.29

---
systemd (229-4ubuntu21.29) xenial; urgency=medium

  [ Dan Streetman ]
  * 
d/p/lp1881312/0001-core-don-t-dispatch-load-queue-when-setting-Slice-fo.patch,
d/p/lp1881312/0002-run-make-slice-work-in-conjunction-with-scope.patch:
- run new scope unit in specified slice (LP: #1881312)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5a778c3cd93e3d684602146f281f315f30778a8
  * d/p/lp1877176-sd-dhcp-client-validate-hostnames-stricter-7308.patch:
- strictly validate hostname sent to dhcp server (LP: #1877176)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a1f1c41dcd860fcba6be42a2153cfe4315ebf17
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=43357bd260a1c3e7b4951d33cbacaebda1d086b3
  * d/p/lp1698388-journal-remote-Ensure-reallocation-of-source-buf-doe.patch:
- Fix assertion failure when journald source->filled < source->size
  (LP: #1698388)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1cc15b88113510227e5a76654e103ef54a8b8f3

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8dc9ef188944349169044d8974a4ffa55c66be9d

 -- Heitor Alves de Siqueira   Tue, 07 Jul 2020
17:28:11 -0400

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

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

Title:
  systemd-run does not make the new scope unit part of the slice
  specified via the --slice arg

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [impact]

  running 'systemd-run --scope --slice=$SLICE $PROGRAM' does not start
  the program under $SLICE, instead it starts it under system.slice

  [test case]

  root:~# systemd-run --scope --slice=user-1000.slice sleep 1000
  Running scope as unit run-r16d872f1b0894b88a79421a890269e6c.scope.
  ^Z
  [3]+  Stopped systemd-run --scope --slice=user-1000.slice 
sleep 1000
  root:~# bg
  [3]+ systemd-run --scope --slice=user-1000.slice sleep 1000 &
  root:~# systemctl show -p Slice run-r16d872f1b0894b88a79421a890269e6c.scope
  Slice=system.slice

  [regression potential]

  This defers running the manager unit load queue when setting the slice
  for a transient unit, as well as actually passing the slice parameter
  over the bus when using --scope, so any regression would very likely
  involve incorrectly setting the slice for a scope and/or problems when
  processing transient units that specify a slice.

  [scope]

  this is needed only for Xenial.

  this is fixed upstream by
  https://github.com/systemd/systemd/pull/3094
  which is included starting in v230, so is included in Bionic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1881312/+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 1876790] Re: cannot connect to the mail server

2020-09-15 Thread Dimitri John Ledkov
Hi,

After inspecting imap4.orangemail.sk host, it appears to only support
TLS1.0 and does not support TLS1.1 or TLS1.2 which have been release
more than 12 years ago and widely adopted. It only supports TLS1.0 which
has been deprecated this year and is no longer supported by default as
it is weak and insecure.

Please contact orangemail.sk requesting for them to support TLSv1.2.

The problem is with them, not Ubuntu. Ubuntu is trying to protect your
communication to be secure.

If you wish to downgrade security and allow broken cryptography you can
use the following documentation to allow connecting to said host in an
insecure manner that is easier to hack https://discourse.ubuntu.com/t
/default-to-tls-v1-2-in-all-tls-libraries-in-20-04-lts/12464/8?u=xnox

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

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

Title:
  cannot connect to the mail server

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  Hi, 
 After upgrade lubuntu on 20.04 both email clients Trojita and Sylpheed 
cannot connect to the mail server. from the log: 
  creating IMAP4 connection to imap4.orangemail.sk:993 ...
  ** LibSylph-WARNING: SSL_connect() failed with error 1, ret = -1 
(error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol)

  problem with ssl?
  OpenSSL 1.1.1f  31 Mar 2020

  I try:
  openssl s_client -host imap4.orangemail.sk -port 993 -prexit 
  CONNECTED(0003)
  140518603695424:error:1425F102:SSL 
routines:ssl_choose_client_version:unsupported 
protocol:../ssl/statem/statem_lib.c:1941:
  ..

  lsb_release -rd
  Description:Ubuntu 20.04 LTS
  Release:20.04

  By

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1876790/+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 1876600] Re: cookie overruns can cause org.freedesktop.systemd1 dbus to hang

2020-09-15 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 229-4ubuntu21.29

---
systemd (229-4ubuntu21.29) xenial; urgency=medium

  [ Dan Streetman ]
  * 
d/p/lp1881312/0001-core-don-t-dispatch-load-queue-when-setting-Slice-fo.patch,
d/p/lp1881312/0002-run-make-slice-work-in-conjunction-with-scope.patch:
- run new scope unit in specified slice (LP: #1881312)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5a778c3cd93e3d684602146f281f315f30778a8
  * d/p/lp1877176-sd-dhcp-client-validate-hostnames-stricter-7308.patch:
- strictly validate hostname sent to dhcp server (LP: #1877176)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a1f1c41dcd860fcba6be42a2153cfe4315ebf17
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=43357bd260a1c3e7b4951d33cbacaebda1d086b3
  * d/p/lp1698388-journal-remote-Ensure-reallocation-of-source-buf-doe.patch:
- Fix assertion failure when journald source->filled < source->size
  (LP: #1698388)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1cc15b88113510227e5a76654e103ef54a8b8f3

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8dc9ef188944349169044d8974a4ffa55c66be9d

 -- Heitor Alves de Siqueira   Tue, 07 Jul 2020
17:28:11 -0400

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

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

Title:
  cookie overruns can cause org.freedesktop.systemd1 dbus to hang

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Long-running services overflow the sd_bus->cookie counter, causing further 
communication with org.freedesktop.systemd1 to stall.

  [Description]
  Systemd dbus messages include a "cookie" value to uniquely identify them in 
their bus context. This value is obtained from the bus header, and incremented 
for each exchanged message in the same bus object. For services that run for 
longer periods of time and keep communicating through dbus, it's possible to 
overflow the cookie value, causing further messages to the 
org.freedesktop.systemd1 dbus to fail. This can lead to these services becoming 
unresponsive, as they get stuck trying to communicate with invalid bus cookie 
values.

  This issue has been fixed upstream by the commit below:
  -  sd-bus: deal with cookie overruns (1f82f5bb4237)

  $ git describe --contains 1f82f5bb4237
  v242-rc1~228

  $ rmadison systemd
   systemd | 229-4ubuntu4 | xenial  | source, ...
   systemd | 229-4ubuntu21.27 | xenial-security | source, ...
   systemd | 229-4ubuntu21.27 | xenial-updates  | source, ...
   systemd | 229-4ubuntu21.28 | xenial-proposed | source, ...
   systemd | 237-3ubuntu10| bionic  | source, ...
   systemd | 237-3ubuntu10.38 | bionic-security | source, ...
   systemd | 237-3ubuntu10.39 | bionic-updates  | source, ...
   systemd | 237-3ubuntu10.40 | bionic-proposed | source, ... <
   systemd | 242-7ubuntu3 | eoan| source, ...

  Releases starting with Eoan already have this fix.

  [Test Case]
  There doesn't seem to be an easy test case for this, as the cookie values 
start at zero and won't overflow until (1<<32). There have been reports from 
users hitting this on Kubernetes clusters continuously running for longer 
periods (~5 months).
  Using GDB, we can construct an artificial test case to test the cookie 
overflow. The test case below performs the following steps:

  1. Create a new system bus object through sd_bus_default_system()
  2. Allocate and append a new method_call message to the bus
  3. Send the message through sd_bus_call()
  4. Handle the response message and free up the message objects

  It's essentially the example code from the
  sd_bus_message_new_method_call() manpage, with minor modifications:
  this is done continuously, to keep incrementing the bus cookie value.
  We step in with GDB when it reaches 0x1, and set its value to
  0xff00 which then causes the test program to fail shortly
  afterwards. An example test run of an impacted system:

  ubuntu@bionic:~$ gcc -Wall test.c -o cookie -lsystemd -g
  ubuntu@bionic:~$ gdb --batch --command=test.gdb --args ./cookie
  Breakpoint 1 at 0xe61: file test.c, line 38.
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  (16s) cookie: 0x0001

[Touch-packages] [Bug 1875781] Re: Unable to verify self signed certificate

2020-09-15 Thread Dimitri John Ledkov
The patch to address this is rather large, and doesn't quite apply
cleanly to 1.1.1f that we currently ship.

Also there is a workaround for this - just generate a better / different
self-signed cert which is identified as such by openssl.

But I do understand that doing that may be very inconvenient as well.

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

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

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

Title:
  Unable to verify self signed certificate

Status in openssl package in Ubuntu:
  Triaged

Bug description:
  See the upstream bug background
  https://github.com/openssl/openssl/issues/1418

  The issue initially was caught in a case when developers works behind
  company firewall and requires install company self signed certificate
  on Ubuntu host in order to access internet via company proxy.

  User may experience unable to access internet services via https
  protocol when even manually installed root trust ca-certificate on
  host machine due to openssl unable to verify some type of self signed
  certificate.

  This is also causing problems for snapcraft developers who work behind
  proxy servers unable to build snap packages.

  There is a fix going into openssl upstream apparently
  https://github.com/openssl/openssl/pull/10587

  Just create a bug here to track this issue in Ubuntu in order to make
  sure we merge upstream fixes ultimately.

  Similar case reported by other users:
  [1] 
https://serverfault.com/questions/966846/cannot-trust-development-https-self-signed-certificate-in-ubuntu-18-04-2-lts
  [2] 
https://stackoverflow.com/questions/55485511/how-to-run-dotnet-dev-certs-https-trust/59702094#59702094

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1875781/+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 1866611] Re: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6

2020-09-15 Thread Dimitri John Ledkov
The status of this bug is invalid, because we will not downgrade default
security level to the one that allows broken crypto to be used by
default. And instructions on how to self-compromise systems are
available and are currently known to work.

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

Title:
  OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  After upgrading openssl on my Focal-install this morning (upgrade
  openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log),
  my OpenVPN tunnel refuses to connect to our corporate VPN (from
  /var/log/syslog):

  corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature 
digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, 
emailAddress=XX
  corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL 
routines:tls_process_server_certificate:certificate verify failed

  I'm told we're running a SHA1-signed CA, which we're guessing has been
  deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog
  for -2ubuntu4 mentions importing some upstream changes, but isn't more
  specific than that:
  https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1
  .1d-2ubuntu4/changelog

  As a work-around, the internet suggests two work-arounds (neither of
  which has worked for me):

  1) Adding the following to /etc/defaults/openssl:

  OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0"

  2) Adding the following to /etc/ssl/openssl.conf:

  CipherString= :@SECLEVEL=1

  I also tried rolling back the package, but the old version doesn't
  seem to be available:

  $ sudo apt install openssl=1.1.1d-2ubuntu3
  ...
  E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found

  
  I am no SSL-expert and would appreciate any pointers to get around this. (Our 
network-dept. does not have the bandwidth to roll over our CA on short notice, 
so I will need some other way to move ahead).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1866611/+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 1866611] Re: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6

2020-09-15 Thread Dimitri John Ledkov
I'm not quite sure about the attempts written in the description of the
bug, as they do not look like correct instructions to downgrade openssl
to Seclevel 0.

If you are looking for instuctions on how to make your systems insecure
and allow using weak keys, broken certificates and obsolete protocol
versions you can use these instructions for OpenSSL and GnuTLS on per-
app or system-wide basis https://discourse.ubuntu.com/t/default-to-
tls-v1-2-in-all-tls-libraries-in-20-04-lts/12464/8?u=xnox

However, I advise you to rotate / upgrade your certificates to use
widely available and accepted hash-algos, key sizes, protocol versions
indead.

I will close this bug as invalid.

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

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

Title:
  OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  After upgrading openssl on my Focal-install this morning (upgrade
  openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log),
  my OpenVPN tunnel refuses to connect to our corporate VPN (from
  /var/log/syslog):

  corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature 
digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, 
emailAddress=XX
  corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL 
routines:tls_process_server_certificate:certificate verify failed

  I'm told we're running a SHA1-signed CA, which we're guessing has been
  deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog
  for -2ubuntu4 mentions importing some upstream changes, but isn't more
  specific than that:
  https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1
  .1d-2ubuntu4/changelog

  As a work-around, the internet suggests two work-arounds (neither of
  which has worked for me):

  1) Adding the following to /etc/defaults/openssl:

  OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0"

  2) Adding the following to /etc/ssl/openssl.conf:

  CipherString= :@SECLEVEL=1

  I also tried rolling back the package, but the old version doesn't
  seem to be available:

  $ sudo apt install openssl=1.1.1d-2ubuntu3
  ...
  E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found

  
  I am no SSL-expert and would appreciate any pointers to get around this. (Our 
network-dept. does not have the bandwidth to roll over our CA on short notice, 
so I will need some other way to move ahead).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1866611/+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 1879980] Update Released

2020-09-15 Thread Brian Murray
The verification of the Stable Release Update for initramfs-tools has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Opinion
Status in cryptsetup source package in Xenial:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in mdadm source package in Xenial:
  Won't Fix
Status in cryptsetup source package in Bionic:
  In Progress
Status in initramfs-tools source package in Bionic:
  In Progress
Status in mdadm source package in Bionic:
  Opinion
Status in cryptsetup source package in Focal:
  In Progress
Status in initramfs-tools source package in Focal:
  Fix Released
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  In Progress
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in mdadm source package in Groovy:
  Opinion
Status in cryptsetup package in Debian:
  New

Bug description:
  [Impact]
  * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu 
is currently unable to decrypt the rootfs if the array gets degraded, like for 
example if one of the array's members gets removed.

  * The problem has 2 main aspects: first, cryptsetup initramfs script
  attempts to decrypt the array only in the local-top boot stage, and in
  case it fails, it gives-up and show user a shell (boot is aborted).

  * Second, mdadm initramfs script that assembles degraded arrays
  executes later on boot, in the local-block stage. So, in a stacked
  setup of encrypted root on top of RAID, if the RAID is degraded,
  cryptsetup fails early in the boot, preventing mdadm to assemble the
  degraded array.

  * The hereby proposed solution has 2 components: first, cryptsetup
  script is modified to allow a gentle failure on local-top stage, then
  it retries for a while (according to a heuristic based on ROOTDELAY
  with minimum of 30 executions) in a later stage (local-block). This
  gives time to other initramfs scripts to run, like mdadm in local-
  block stage. And this is meant to work this way according to
  initramfs-tools documentation (although Ubuntu changed it a bit with
  wait-for-root, hence we stopped looping on local-block, see next
  bullet).

  * Second, initramfs-tools was adjusted - currently, it runs for a
  while the mdadm local-block script, in order to assemble the arrays in
  a non-degraded mode. We extended this approach to also execute
  cryptsetup, in a way that after mdadm ends its execution, we execute
  at least once more time cryptsetup. In an ideal world we should loop
  on local-block as Debian's initramfs (in a way to remove hardcoded
  mdadm/cryptsetup mentions from initramfs-tools code), but this would
  be really a big change, non-SRUable probably. I plan to work that for
  future Ubuntu releases.

  [Test case]
  * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to 
create a RAID1 volume and an encrypted root on top of it.

  * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table
  from one of the RAID members. Reboot and it will fail to mount rootfs
  and continue boot process.

  * If using the initramfs-toos/cryptsetup patches hereby proposed, the
  rootfs can be mounted normally.

  [Regression potential]

  * There are potential for regressions, since this is a change in 2
  boot components. The patches were designed in a way to keep the
  regular case working, it changes the failure case which is not
  currently working anyway.

  * A modification in the behavior of cryptsetup was introduced: right
  now, if we fail the password 3 times (the default maximum attempts),
  the script doesn't "panic" and drop to a shell immediately; instead it
  runs once more (or twice, if mdadm is installed) before failing. This
  is a minor change given the benefit of the being able to mount rootfs
  in a degraded RAID1 scenario.

  * Other potential regressions could show-up as boot problems, but the
  change in initramfs-tools specifically is not invasive, it just may
  delay boot time a bit, given we now run cryptsetup multiple times on
  local-block, with 1 sec delays between executions.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1879987] Update Released

2020-09-15 Thread Brian Murray
The verification of the Stable Release Update for initramfs-tools has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  In Progress
Status in initramfs-tools source package in Bionic:
  In Progress
Status in initramfs-tools source package in Eoan:
  Won't Fix
Status in initramfs-tools source package in Focal:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  * Currently, if users provide the wrong console in kernel command-line
  (like console=ttyS1, when the right one is ttyS0) *and* "quiet"
  parameter is not provided, we may face an infinite loop on initramfs-
  tools, effectively blocking the boot.

  * Details are: the _log_msg() functions is "void" typed, which means it 
returns whatever its last command returns; this function is the basic building 
block for all error/warning messages in initramfs-tools. In case a bad console 
was provided to kernel on command-line, printf (and apparently all 
write()-related functions) returns error, and so this error is carried over in 
_log_msg().
   
  * Happens that checkfs() function has a loop that runs forever in this 
scenario (*if* fsck is not present in initramfs, and obviously if "quiet" is 
not provided in the command-line). The situation is easily reproducible.

  * This SRU proposes a pretty simple fix: return zero on _log_msg(). We
  should definitely not brake the boot due to error log functions.

  
  [Test Case]

  * To reproduce this, one must boot a system (virtual machine is good)
  with the wrong console set on kernel command-line through the
  "console=" parameter *and* not pass the "quiet" parameter.

  * Also, e2fsck tool shouldn't be present in the initrd - for that, the
  6th field of /etc/fstab (fs_passno) should be 0 and initrd must be
  recreated after that. This is the default in Ubuntu, though.

  
  [Regression Potential]

  * The regression potential is small, we're just returning 0 after a
  printf that is executed in error paths, so I don't expect any issues
  from that. But in case something bad happens after this change, I
  expect a more friendly" breakage, like an initramfs panic (drop to a
  shell), not a silent failure or boot-loop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+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 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

2020-09-15 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.136ubuntu6.3

---
initramfs-tools (0.136ubuntu6.3) focal; urgency=medium

  * scripts/functions: Prevent printf error carry over if the wrong
console is set. (LP: #1879987)
  The function _log_msg() is "void" typed, returning whatever its
  last command returns. This function is the basic building block
  for all error/warning messages in initramfs-tools. If a bad console
  is provided to kernel on command-line, printf returns error, and so
  this error is carried over in _log_msg(). Happens that checkfs()
  function has a loop that runs forever in this scenario (*if* fsck
  is not present in initramfs and "quiet" is not passed in the
  command-line). If that happens, boot is stuck and cannot progress.
  The simple fix hereby merged is to return zero on _log_msg().

  * scripts/local: Re-execute cryptroot local-block script. (LP: #1879980)
  Currently, if an encrypted rootfs is configured on top of a MD RAID1
  array and such array gets degraded (like a member is removed/failed),
  initramfs-tools cannot mount the rootfs and the boot fails. We fix
  that issue here by allowing cryptroot script to re-run on local-block
  stage, given that mdadm is able to activate a degraded array in that
  point. There is a cryptsetup counter-part for this fix, but alone the
  initramfs-tools portion is innocuous.

  * d/tests: Add explicit call to partprobe on net test, specially in
prep-image and run-image. (LP: #1893675)

 -- gpicc...@canonical.com (Guilherme G. Piccoli)  Mon, 31 Aug 2020
13:43:29 -0300

** Changed in: initramfs-tools (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Opinion
Status in cryptsetup source package in Xenial:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in mdadm source package in Xenial:
  Won't Fix
Status in cryptsetup source package in Bionic:
  In Progress
Status in initramfs-tools source package in Bionic:
  In Progress
Status in mdadm source package in Bionic:
  Opinion
Status in cryptsetup source package in Focal:
  In Progress
Status in initramfs-tools source package in Focal:
  Fix Released
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  In Progress
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in mdadm source package in Groovy:
  Opinion
Status in cryptsetup package in Debian:
  New

Bug description:
  [Impact]
  * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu 
is currently unable to decrypt the rootfs if the array gets degraded, like for 
example if one of the array's members gets removed.

  * The problem has 2 main aspects: first, cryptsetup initramfs script
  attempts to decrypt the array only in the local-top boot stage, and in
  case it fails, it gives-up and show user a shell (boot is aborted).

  * Second, mdadm initramfs script that assembles degraded arrays
  executes later on boot, in the local-block stage. So, in a stacked
  setup of encrypted root on top of RAID, if the RAID is degraded,
  cryptsetup fails early in the boot, preventing mdadm to assemble the
  degraded array.

  * The hereby proposed solution has 2 components: first, cryptsetup
  script is modified to allow a gentle failure on local-top stage, then
  it retries for a while (according to a heuristic based on ROOTDELAY
  with minimum of 30 executions) in a later stage (local-block). This
  gives time to other initramfs scripts to run, like mdadm in local-
  block stage. And this is meant to work this way according to
  initramfs-tools documentation (although Ubuntu changed it a bit with
  wait-for-root, hence we stopped looping on local-block, see next
  bullet).

  * Second, initramfs-tools was adjusted - currently, it runs for a
  while the mdadm local-block script, in order to assemble the arrays in
  a non-degraded mode. We extended this approach to also execute
  cryptsetup, in a way that after mdadm ends its execution, we execute
  at least once more time cryptsetup. In an ideal world we should loop
  on local-block as Debian's initramfs (in a way to remove hardcoded
  mdadm/cryptsetup mentions from initramfs-tools code), but this would
  be really a big change, non-SRUable probably. I plan to work that for
  future Ubuntu releases.

  [Test case]
  * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to 
create a RAID1 volume and an encrypted root on top of it.

  * Boot the VM, 

[Touch-packages] [Bug 1893675] Update Released

2020-09-15 Thread Brian Murray
The verification of the Stable Release Update for initramfs-tools has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Autopkgtest failure on latest version of initramfs-tools - lack of
  partprobe

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Focal:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  * Currently the initramfs-tools autopkgtest fails for at least AMD64, with 
the following signature:
  "mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device 
/dev/loop0p1 does not exist."

  * The reason for that is the test trying immediately to use that
  partition on the loop device, but kernel may not have a partition re-
  read ioctl issued, so the test may fail as observing a nonexistent
  partition.

  * The fix proposed here is just to manually run "partprobe" before
  using the new to-be-discovered loop partition in the net autopkgtest.

  [Test Case]
  * Run the autopkgtest suite in the initramfs-tools package and observe the 
failure aforementioned.

  [Regression Potential]
  * Extremely low potential, we are just introducing a partition re-read/probe 
operation during autopkgtest phase, in order to keep the partition table of 
loop devices consistent before the test uses it.
  * The only potential issue I see with that is if for some reason we don't 
have partprobe in the autopkgtest environment, but that shouldn't happen since 
parted package is on ubuntu-standard.

  * Notice that this test is not executed in Debian CI given that CI has
  no support for VMs, and this test requires that. [See the
  Rectification below]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+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 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

2020-09-15 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.130ubuntu3.10

---
initramfs-tools (0.130ubuntu3.10) bionic; urgency=medium

  * Cherrypick upstream commit to copy libgcc_s, as a dependency of
libpthread including when there is optimized pthreads installed. LP:
#1880853

 -- Dimitri John Ledkov   Wed, 02 Sep 2020 15:53:41
+0100

** Changed in: initramfs-tools (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  libc6-lse lets update-initramfs fail on AWS m6g instances

Status in cloud-images:
  New
Status in btrfs-progs package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in btrfs-progs source package in Bionic:
  Invalid
Status in glibc source package in Bionic:
  Invalid
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in btrfs-progs source package in Focal:
  Invalid
Status in glibc source package in Focal:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * update-initramfs -u fails on arm64 m6g instances in AWS

  [Test Case]

   * launch m6g instance in AWS
   * install libc6-lse (if not installed)
   * run $ update-initramfs -u
   * It should suceed
   * It should contain pthread, and libgcc_s libraries

  [Regression Potential]

   * Adding one more path to libgcc_s1 resolution. This will still fail
  if something compiles libc6 for _two_ optimisations like
  /lib/$arch/foo/bar/libpthread.

  [Other Info]

   * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in
  the initrd libgcc_s1 must be copied in too. However the logic to find
  matching libgcc_s1 is broken for optimizied builds of libc6 without
  optimized build of libgcc_s1. I think libpthread should link against
  libgcc_s1 to prevent these issues.

   * Original bug report

  With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse
  lets update-initramfs always fail with the following error:

  ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1.

  ## Steps to reproduce (on AWS)

  ### With focal 20200423 AMI

  1. Find the following AMI and launch on m6g instance family

     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423

  2. Run: sudo apt update && sudo apt install libc6-lse
  3. Try: sudo update-initramfs -u

  ### With focal 20200522 AMI

  1. Find the following AMI and launch on m6g instance family

     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522

  2. Try: sudo update-initramfs -u

  ## Note

  - The entire log of the above steps performed on 20200423 AMI is attached.
  - Latest cloud-image AMI 
"ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes 
libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse 
manually.
  - This doesn't reproduce on EC2 a1.* instance family.

  ## Expected behavior

  Does not fail.

  ## Background to find this bug

  As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get
  upgrade pulls newer package that triggers update-initramfs, apt-get
  upgrade always fail on 20200522 AMI.

  the following is an apport report on 20200423 AMI:

  

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed May 27 09:52:16 2020
  Dependencies:
   gcc-10-base 10-20200411-0ubuntu1
   libc6 2.31-0ubuntu9
   libcrypt1 1:4.4.10-10ubuntu4
   libgcc-s1 10-20200411-0ubuntu1
   libidn2-0 2.2.0-2
   libunistring2 0.9.10-2
  DistroRelease: Ubuntu 20.04
  Ec2AMI: ami-061102f51d47b1c24
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-northeast-1c
  Ec2InstanceType: m6g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: libc6-lse 2.31-0ubuntu9
  PackageArchitecture: arm64
  ProcCpuinfoMinimal:
   processor  : 0
   BogoMIPS   : 243.75
   Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
   CPU implementer: 0x41
   CPU architecture: 8
   CPU variant: 0x3
   CPU part   : 0xd0c
   CPU revision   : 1
  ProcEnviron:
   LANG=C.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30
  SourcePackage: glibc
  Tags:  focal ec2-images
  Uname: Linux 5.4.0-1009-aws aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1880853/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

2020-09-15 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.136ubuntu6.3

---
initramfs-tools (0.136ubuntu6.3) focal; urgency=medium

  * scripts/functions: Prevent printf error carry over if the wrong
console is set. (LP: #1879987)
  The function _log_msg() is "void" typed, returning whatever its
  last command returns. This function is the basic building block
  for all error/warning messages in initramfs-tools. If a bad console
  is provided to kernel on command-line, printf returns error, and so
  this error is carried over in _log_msg(). Happens that checkfs()
  function has a loop that runs forever in this scenario (*if* fsck
  is not present in initramfs and "quiet" is not passed in the
  command-line). If that happens, boot is stuck and cannot progress.
  The simple fix hereby merged is to return zero on _log_msg().

  * scripts/local: Re-execute cryptroot local-block script. (LP: #1879980)
  Currently, if an encrypted rootfs is configured on top of a MD RAID1
  array and such array gets degraded (like a member is removed/failed),
  initramfs-tools cannot mount the rootfs and the boot fails. We fix
  that issue here by allowing cryptroot script to re-run on local-block
  stage, given that mdadm is able to activate a degraded array in that
  point. There is a cryptsetup counter-part for this fix, but alone the
  initramfs-tools portion is innocuous.

  * d/tests: Add explicit call to partprobe on net test, specially in
prep-image and run-image. (LP: #1893675)

 -- gpicc...@canonical.com (Guilherme G. Piccoli)  Mon, 31 Aug 2020
13:43:29 -0300

** Changed in: initramfs-tools (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  In Progress
Status in initramfs-tools source package in Bionic:
  In Progress
Status in initramfs-tools source package in Eoan:
  Won't Fix
Status in initramfs-tools source package in Focal:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  * Currently, if users provide the wrong console in kernel command-line
  (like console=ttyS1, when the right one is ttyS0) *and* "quiet"
  parameter is not provided, we may face an infinite loop on initramfs-
  tools, effectively blocking the boot.

  * Details are: the _log_msg() functions is "void" typed, which means it 
returns whatever its last command returns; this function is the basic building 
block for all error/warning messages in initramfs-tools. In case a bad console 
was provided to kernel on command-line, printf (and apparently all 
write()-related functions) returns error, and so this error is carried over in 
_log_msg().
   
  * Happens that checkfs() function has a loop that runs forever in this 
scenario (*if* fsck is not present in initramfs, and obviously if "quiet" is 
not provided in the command-line). The situation is easily reproducible.

  * This SRU proposes a pretty simple fix: return zero on _log_msg(). We
  should definitely not brake the boot due to error log functions.

  
  [Test Case]

  * To reproduce this, one must boot a system (virtual machine is good)
  with the wrong console set on kernel command-line through the
  "console=" parameter *and* not pass the "quiet" parameter.

  * Also, e2fsck tool shouldn't be present in the initrd - for that, the
  6th field of /etc/fstab (fs_passno) should be 0 and initrd must be
  recreated after that. This is the default in Ubuntu, though.

  
  [Regression Potential]

  * The regression potential is small, we're just returning 0 after a
  printf that is executed in error paths, so I don't expect any issues
  from that. But in case something bad happens after this change, I
  expect a more friendly" breakage, like an initramfs panic (drop to a
  shell), not a silent failure or boot-loop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+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 1893675] Re: Autopkgtest failure on latest version of initramfs-tools - lack of partprobe

2020-09-15 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.136ubuntu6.3

---
initramfs-tools (0.136ubuntu6.3) focal; urgency=medium

  * scripts/functions: Prevent printf error carry over if the wrong
console is set. (LP: #1879987)
  The function _log_msg() is "void" typed, returning whatever its
  last command returns. This function is the basic building block
  for all error/warning messages in initramfs-tools. If a bad console
  is provided to kernel on command-line, printf returns error, and so
  this error is carried over in _log_msg(). Happens that checkfs()
  function has a loop that runs forever in this scenario (*if* fsck
  is not present in initramfs and "quiet" is not passed in the
  command-line). If that happens, boot is stuck and cannot progress.
  The simple fix hereby merged is to return zero on _log_msg().

  * scripts/local: Re-execute cryptroot local-block script. (LP: #1879980)
  Currently, if an encrypted rootfs is configured on top of a MD RAID1
  array and such array gets degraded (like a member is removed/failed),
  initramfs-tools cannot mount the rootfs and the boot fails. We fix
  that issue here by allowing cryptroot script to re-run on local-block
  stage, given that mdadm is able to activate a degraded array in that
  point. There is a cryptsetup counter-part for this fix, but alone the
  initramfs-tools portion is innocuous.

  * d/tests: Add explicit call to partprobe on net test, specially in
prep-image and run-image. (LP: #1893675)

 -- gpicc...@canonical.com (Guilherme G. Piccoli)  Mon, 31 Aug 2020
13:43:29 -0300

** Changed in: initramfs-tools (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Autopkgtest failure on latest version of initramfs-tools - lack of
  partprobe

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Focal:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  * Currently the initramfs-tools autopkgtest fails for at least AMD64, with 
the following signature:
  "mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device 
/dev/loop0p1 does not exist."

  * The reason for that is the test trying immediately to use that
  partition on the loop device, but kernel may not have a partition re-
  read ioctl issued, so the test may fail as observing a nonexistent
  partition.

  * The fix proposed here is just to manually run "partprobe" before
  using the new to-be-discovered loop partition in the net autopkgtest.

  [Test Case]
  * Run the autopkgtest suite in the initramfs-tools package and observe the 
failure aforementioned.

  [Regression Potential]
  * Extremely low potential, we are just introducing a partition re-read/probe 
operation during autopkgtest phase, in order to keep the partition table of 
loop devices consistent before the test uses it.
  * The only potential issue I see with that is if for some reason we don't 
have partprobe in the autopkgtest environment, but that shouldn't happen since 
parted package is on ubuntu-standard.

  * Notice that this test is not executed in Debian CI given that CI has
  no support for VMs, and this test requires that. [See the
  Rectification below]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+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 1895640] Re: BlueZ 5.55 release

2020-09-15 Thread Sebastien Bacher
** Changed in: bluez (Ubuntu)
   Status: In Progress => Fix Committed

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

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

Title:
  BlueZ 5.55 release

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.55.tar.xz

  https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.55

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895640/+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 1895294] Re: Fix Raccoon vulnerability (CVE-2020-1968)

2020-09-15 Thread Dimitri John Ledkov
It is true that said vulnerability is not patched in xenial; but also it
is low; and no public patches for it exist.

Please upgrade to bionic or focal? which are unaffected / fixes
released?

** Information type changed from Public to Public Security

** Also affects: openssl (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  Fix Raccoon vulnerability (CVE-2020-1968)

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Confirmed

Bug description:
  Xenial's current OpenSSL (1.0.2g-1ubuntu4.16) seems to not have been
  patched yet against the Raccoon Attack (CVE-2020-1968):

  - https://www.openssl.org/news/secadv/20200909.txt
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1968
  - https://raccoon-attack.com/

  Ubuntu's CVE tracker still lists this as NEEDED for Xenial:

  - https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-1968.html
  - https://people.canonical.com/~ubuntu-security/cve/pkg/openssl.html

  Other supported Ubuntu releases use versions of OpenSSL that are not
  affected.

  Indeed:

    $ apt-cache policy openssl
    openssl:
  Installed: 1.0.2g-1ubuntu4.16

    $ apt-get changelog openssl | grep CVE-2020-1968 || echo "Not patched"
    Not patched

  What is the status?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1895294/+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 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

2020-09-15 Thread Christian Ehrhardt 
** Changed in: pcsc-lite (Ubuntu)
 Assignee: Seth Arnold (seth-arnold) => Christian Ehrhardt  (paelzer)

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

Title:
  [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

Status in ccid package in Ubuntu:
  New
Status in opensc package in Ubuntu:
  Incomplete
Status in pam-pkcs11 package in Ubuntu:
  New
Status in pcsc-lite package in Ubuntu:
  New
Status in pcsc-perl package in Ubuntu:
  Invalid
Status in pcsc-tools package in Ubuntu:
  Invalid

Bug description:
  ==> ccid <==
  [Availability]
  ccid is in universe, and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs for ccid are listed in our database.
  Doesn't appear to bind to a socket.
  No privileged executables, but does have udev rules.
  Probably needs a security review.

  [Quality assurance]
  No test suite.
  Does require odd hardware that we'll probably need to buy.
  I don't see debconf questions.
  ccid is well maintained in Debian by upstream author.
  One open wishlist bug in BTS, harmless.

  One open bug in launchpad, not security, but looks very frustrating
  for the users. The upstream author was engaged but it never reached
  resolution.  https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465

  Has a debian/watch file.
  Quilt packaging.

  P: ccid source: no-dep5-copyright
  P: ccid source: package-uses-experimental-debhelper-compat-version 13

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  ccid provides drivers to interact with usb-connected smart card readers.

  ==> libpam-pkcs11 <==
  [Availability]
  Source package pam-pkcs11 is in universe and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs in our database.
  Doesn't appear to bind to sockets.
  No privileged executables (but is a PAM module).
  As a PAM module this will require a security review.

  [Quality assurance]
  The package does not call pam-auth-update in its postinst #1650366
  Does not ask questions during install.
  One Ubuntu bug claims very poor behaviour if a card isn't plugged in.
  No Debian bugs.
  Occasional updates in Debian by long-term maintainer.
  Does require odd hardware that we'll probably need to buy.
  Does not appear to run tests during build.
  Has scary warnings in the build logs.
  Has a debian/watch file.

  Ancient standards version; other smaller lintian messages, mostly
  documentation problems.

  Quilt packaging.

  [Dependencies]
  Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1
  All are in main.

  [Standards compliance]
  The package does not call pam-auth-update in its postinst #1650366
  Otherwise looks to conform to FHS and Debian policies

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  This PAM module can use CRLs and full-chain verification of certificates.
  It can also do LDAP, AD, and Kerberos username mapping.

  ==> libpcsc-perl <==
  [Availability]
  Source package pcsc-perl is in universe, builds for all architectures,
  plus i386

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  There are no cves for pcsc-perl in our database.
  No privileged executables.
  Doesn't appear to bind to sockets.
  Probably needs a security review.

  [Quality assurance]
  Library package not intended to be used directly.
  No debconf questions.
  No bugs in Debian.
  No bugs in Ubuntu.
  Does require odd hardware that we'll probably need to buy.
  Tests exist, not run during the build; probably can't run during the build.
  Includes debian/watch file.
  A handful of lintian issues
  Quilt packaging.

  [Dependencies]
  libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0.
  All are in main.

  [Standards compliance]
  One oddity, Card.pod is stored in 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/
  Many other perl packages have .pod files in these directory trees so maybe
  it's fine, but it seems funny all the same.

  Otherwise appears to satisfy FHS and Debian policy.

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant 

[Touch-packages] [Bug 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

2020-09-15 Thread Seth Arnold
** Changed in: pcsc-lite (Ubuntu)
   Status: Incomplete => New

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

Title:
  [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

Status in ccid package in Ubuntu:
  New
Status in opensc package in Ubuntu:
  Incomplete
Status in pam-pkcs11 package in Ubuntu:
  New
Status in pcsc-lite package in Ubuntu:
  New
Status in pcsc-perl package in Ubuntu:
  Invalid
Status in pcsc-tools package in Ubuntu:
  Invalid

Bug description:
  ==> ccid <==
  [Availability]
  ccid is in universe, and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs for ccid are listed in our database.
  Doesn't appear to bind to a socket.
  No privileged executables, but does have udev rules.
  Probably needs a security review.

  [Quality assurance]
  No test suite.
  Does require odd hardware that we'll probably need to buy.
  I don't see debconf questions.
  ccid is well maintained in Debian by upstream author.
  One open wishlist bug in BTS, harmless.

  One open bug in launchpad, not security, but looks very frustrating
  for the users. The upstream author was engaged but it never reached
  resolution.  https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465

  Has a debian/watch file.
  Quilt packaging.

  P: ccid source: no-dep5-copyright
  P: ccid source: package-uses-experimental-debhelper-compat-version 13

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  ccid provides drivers to interact with usb-connected smart card readers.

  ==> libpam-pkcs11 <==
  [Availability]
  Source package pam-pkcs11 is in universe and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs in our database.
  Doesn't appear to bind to sockets.
  No privileged executables (but is a PAM module).
  As a PAM module this will require a security review.

  [Quality assurance]
  The package does not call pam-auth-update in its postinst #1650366
  Does not ask questions during install.
  One Ubuntu bug claims very poor behaviour if a card isn't plugged in.
  No Debian bugs.
  Occasional updates in Debian by long-term maintainer.
  Does require odd hardware that we'll probably need to buy.
  Does not appear to run tests during build.
  Has scary warnings in the build logs.
  Has a debian/watch file.

  Ancient standards version; other smaller lintian messages, mostly
  documentation problems.

  Quilt packaging.

  [Dependencies]
  Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1
  All are in main.

  [Standards compliance]
  The package does not call pam-auth-update in its postinst #1650366
  Otherwise looks to conform to FHS and Debian policies

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  This PAM module can use CRLs and full-chain verification of certificates.
  It can also do LDAP, AD, and Kerberos username mapping.

  ==> libpcsc-perl <==
  [Availability]
  Source package pcsc-perl is in universe, builds for all architectures,
  plus i386

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  There are no cves for pcsc-perl in our database.
  No privileged executables.
  Doesn't appear to bind to sockets.
  Probably needs a security review.

  [Quality assurance]
  Library package not intended to be used directly.
  No debconf questions.
  No bugs in Debian.
  No bugs in Ubuntu.
  Does require odd hardware that we'll probably need to buy.
  Tests exist, not run during the build; probably can't run during the build.
  Includes debian/watch file.
  A handful of lintian issues
  Quilt packaging.

  [Dependencies]
  libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0.
  All are in main.

  [Standards compliance]
  One oddity, Card.pod is stored in 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/
  Many other perl packages have .pod files in these directory trees so maybe
  it's fine, but it seems funny all the same.

  Otherwise appears to satisfy FHS and Debian policy.

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  Dependency 

[Touch-packages] [Bug 1895686] Re: blkid always hangs, launched by dpkg --configure -a

2020-09-15 Thread Darxus
** Description changed:

  I noticed last night that package install fails.  Then I noticed
- processes running from an automatic upgrade that ran on September 9th.
+ processes running from an automatic upgrade that ran on September first.
  Whenever I run "dpkg --configure -a", it gets stuck on blkid hanging.
  When I run the same command manually through strace, it seems to get
  hung on opening the floppy drive, which does not exist:
  
  # strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
  b6a3-888f7368c779
  
  ...
  lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  access("/dev/fd0", F_OK)= 0
  stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
  openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or 
directory)
  close(4)= 0
  openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC
  
  This bug was submitted by running ubuntu-bug on one of the hung
  instances of blkid.
  
  https://ubuntuforums.org/showthread.php?t=2450510
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Sep 15 10:18:23 2020
  ExecutablePath: /sbin/blkid
  InstallationDate: Installed on 2016-05-28 (1571 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to focal on 2020-08-20 (25 days ago)

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

Title:
  blkid always hangs, launched by dpkg --configure -a

Status in util-linux package in Ubuntu:
  New

Bug description:
  I noticed last night that package install fails.  Then I noticed
  processes running from an automatic upgrade that ran on September
  first.  Whenever I run "dpkg --configure -a", it gets stuck on blkid
  hanging.  When I run the same command manually through strace, it
  seems to get hung on opening the floppy drive, which does not exist:

  # strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
  b6a3-888f7368c779

  ...
  lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  access("/dev/fd0", F_OK)= 0
  stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
  openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or 
directory)
  close(4)= 0
  openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC

  This bug was submitted by running ubuntu-bug on one of the hung
  instances of blkid.

  https://ubuntuforums.org/showthread.php?t=2450510

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Sep 15 10:18:23 2020
  ExecutablePath: /sbin/blkid
  InstallationDate: Installed on 2016-05-28 (1571 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to focal on 2020-08-20 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1895686/+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 1895686] Re: blkid always hangs, launched by dpkg --configure -a

2020-09-15 Thread Darxus
** Attachment added: "Full output of that strace"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1895686/+attachment/5411074/+files/blkid.log

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

Title:
  blkid always hangs, launched by dpkg --configure -a

Status in util-linux package in Ubuntu:
  New

Bug description:
  I noticed last night that package install fails.  Then I noticed
  processes running from an automatic upgrade that ran on September
  first.  Whenever I run "dpkg --configure -a", it gets stuck on blkid
  hanging.  When I run the same command manually through strace, it
  seems to get hung on opening the floppy drive, which does not exist:

  # strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
  b6a3-888f7368c779

  ...
  lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  access("/dev/fd0", F_OK)= 0
  stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
  openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or 
directory)
  close(4)= 0
  openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC

  This bug was submitted by running ubuntu-bug on one of the hung
  instances of blkid.

  https://ubuntuforums.org/showthread.php?t=2450510

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Sep 15 10:18:23 2020
  ExecutablePath: /sbin/blkid
  InstallationDate: Installed on 2016-05-28 (1571 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to focal on 2020-08-20 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1895686/+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 1895686] [NEW] blkid always hangs, launched by dpkg --configure -a

2020-09-15 Thread Darxus
Public bug reported:

I noticed last night that package install fails.  Then I noticed
processes running from an automatic upgrade that ran on September first.
Whenever I run "dpkg --configure -a", it gets stuck on blkid hanging.
When I run the same command manually through strace, it seems to get
hung on opening the floppy drive, which does not exist:

# strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
b6a3-888f7368c779

...
lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
access("/dev/fd0", F_OK)= 0
stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
close(4)= 0
openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC

This bug was submitted by running ubuntu-bug on one of the hung
instances of blkid.

https://ubuntuforums.org/showthread.php?t=2450510

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: util-linux 2.34-0.1ubuntu9
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Tue Sep 15 10:18:23 2020
ExecutablePath: /sbin/blkid
InstallationDate: Installed on 2016-05-28 (1571 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: util-linux
UpgradeStatus: Upgraded to focal on 2020-08-20 (25 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Description changed:

  I noticed last night that package install fails.  Then I noticed
  processes running from an automatic upgrade that ran on September 9th.
  Whenever I run "dpkg --configure -a", it gets stuck on blkid hanging.
  When I run the same command manually through strace, it seems to get
  hung on opening the floppy drive, which does not exist:
  
  # strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
  b6a3-888f7368c779
  
  ...
  lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  access("/dev/fd0", F_OK)= 0
  stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
  openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or 
directory)
  close(4)= 0
  openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC
  
+ https://ubuntuforums.org/showthread.php?t=2450510
  
- https://ubuntuforums.org/showthread.php?t=2450510
+ This bug was submitted by running ubuntu-bug on one of the hung
+ instances of blkid.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Sep 15 10:18:23 2020
  ExecutablePath: /sbin/blkid
  InstallationDate: Installed on 2016-05-28 (1571 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to focal on 2020-08-20 (25 days ago)

** Description changed:

  I noticed last night that package install fails.  Then I noticed
  processes running from an automatic upgrade that ran on September 9th.
  Whenever I run "dpkg --configure -a", it gets stuck on blkid hanging.
  When I run the same command manually through strace, it seems to get
  hung on opening the floppy drive, which does not exist:
  
  # strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
  b6a3-888f7368c779
  
  ...
  lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  access("/dev/fd0", F_OK)= 0
  stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
  openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
  openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or 
directory)
  close(4)= 0
  openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC
  
- https://ubuntuforums.org/showthread.php?t=2450510
- 
  This bug was submitted by running ubuntu-bug on one of the hung
  instances of blkid.
+ 
+ https://ubuntuforums.org/showthread.php?t=2450510
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Sep 15 10:18:23 

[Touch-packages] [Bug 1881699] Re: No analog output

2020-09-15 Thread Sebastien Bacher
Tagging as notfixing, it seems specific to one configuration and not
qualifying as a rls issue

** Tags removed: rls-gg-incoming
** Tags added: rls-gg-notfixing

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

Title:
  No analog output

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

Bug description:
  After a fresh boot and login, there is no analog output. Only HDMI and 
bluetooth are available.
  It becomes available when I kill pulseaudio with 'pulseaudio -k' but the 
sound indicator only shows 'dummy' output and I cannot control the output from 
the sound settings or the sound indicator.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu36
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  j-lallement  184080 F pulseaudio
   /dev/snd/controlC1:  j-lallement  184080 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  2 06:32:09 2020
  InstallationDate: Installed on 2020-05-31 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0032.2019.1021.1624
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu36
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  j-lallement   3669 F pulseaudio
   /dev/snd/controlC0:  j-lallement   3669 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-05-31 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  MachineType: Intel(R) Client Systems NUC10i7FNH
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  groovy
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/21/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0032.2019.1021.1624
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+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 1895665] [NEW] PulseAudio automatically switches from HDMI 2 after display sleep

2020-09-15 Thread Andrii Puhalevich
Public bug reported:

I have an Nvidia based video card that has an HDMI output + a DisplayPort 
output.
DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output 
is listed as "Digital Stereo (HDMI 2)".

I prefer to use "Digital Stereo (HDMI 2)".
But after each display sleep (screen lock for example) audio is switched to 
built in audio

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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Sep 15 14:56:58 2020
InstallationDate: Installed on 2020-06-20 (86 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.1
dmi.board.name: 0CNDTP
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr:
dmi.product.family: GSeries
dmi.product.name: G5 5590
dmi.product.sku: 08EA
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

** Attachment added: "screenshot_2020-09-15_15-49-17.jpg"
   
https://bugs.launchpad.net/bugs/1895665/+attachment/5411015/+files/screenshot_2020-09-15_15-49-17.jpg

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

Title:
  PulseAudio automatically switches from HDMI 2 after display sleep

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have an Nvidia based video card that has an HDMI output + a DisplayPort 
output.
  DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output 
is listed as "Digital Stereo (HDMI 2)".

  I prefer to use "Digital Stereo (HDMI 2)".
  But after each display sleep (screen lock for example) audio is switched to 
built in audio

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Sep 15 14:56:58 2020
  InstallationDate: Installed on 2020-06-20 (86 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.name: 0CNDTP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5590
  dmi.product.sku: 08EA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1891338] Re: apparmor misconfigured for evince

2020-09-15 Thread Rolf Leggewie
** Summary changed:

- apparmor misconfigured for envice
+ apparmor misconfigured for evince

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

Title:
  apparmor misconfigured for evince

Status in apparmor package in Ubuntu:
  In Progress
Status in evince package in Ubuntu:
  Triaged

Bug description:
  On a fully up to date xubuntu 20-04 system, when i run evince and
  click on a link, it fails to follow that link in my browser. This kind
  of thing happens when you are reading a technical paper and want to
  follow one of the references and click on the doi or url.

  When i click on the link i get a box that i cannot copy from that says:
  Failed to launch preferred application for category "WebBrowser".

  Failed to execute child process "/usr/lib/x86_64-linux-gnu/xfce4/exo-2
  /exo-helper-2"(Permission denied).

  Did I say that it is annoying that i could not copy the text in this
  box!!

  The output of the ldd command you asked for is attached.

  I should also point out that this worked fine under xubuntu 18.04.

  I had originally posted this as an additional comment on
  https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159?comments=all
  but https://launchpad.net/~seb128 said that I should submit this as a
  separate bug because this is likely an apparmor configuration problem
  that is similar to the ancient bug
  https://bugs.launchpad.net/bugs/987578.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1891338/+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 1895664] [NEW] problem in apparmor configuration of evince

2020-09-15 Thread Rolf Leggewie
Public bug reported:

evince 3.28.4-0ubuntu1.2 running on bionic.  I cannot call the vivaldi-
browser by clicking on a link.  Instead an error is shown "Failed to
execute child process “/usr/bin/vivaldi-stable” (Permission denied)".
Some lines from syslog:

Sep 15 14:28:28 work kernel: [46945.893234] audit: type=1400 
audit(1600172908.761:241): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
Sep 15 14:28:29 work kernel: [46946.523153] audit: type=1400 
audit(1600172909.393:242): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
Sep 15 14:28:29 work kernel: [46946.716721] audit: type=1400 
audit(1600172909.585:243): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
Sep 15 14:28:29 work kernel: [46946.748450] audit: type=1400 
audit(1600172909.617:244): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
Sep 15 14:28:53 work kernel: [46970.973331] audit: type=1400 
audit(1600172933.841:256): apparmor="DENIED" operation="exec" 
profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=5390 comm="evince" 
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

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

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


** Tags: bionic

** Also affects: evince (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  problem in apparmor configuration of evince

Status in apparmor package in Ubuntu:
  New
Status in evince package in Ubuntu:
  New

Bug description:
  evince 3.28.4-0ubuntu1.2 running on bionic.  I cannot call the
  vivaldi-browser by clicking on a link.  Instead an error is shown
  "Failed to execute child process “/usr/bin/vivaldi-stable” (Permission
  denied)".  Some lines from syslog:

  Sep 15 14:28:28 work kernel: [46945.893234] audit: type=1400 
audit(1600172908.761:241): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.523153] audit: type=1400 
audit(1600172909.393:242): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.716721] audit: type=1400 
audit(1600172909.585:243): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.748450] audit: type=1400 
audit(1600172909.617:244): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:53 work kernel: [46970.973331] audit: type=1400 
audit(1600172933.841:256): apparmor="DENIED" operation="exec" 
profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=5390 comm="evince" 
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895664/+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 1894838] Re: FFe: update to 2.4.53, fixing crash bugs

2020-09-15 Thread Andreas Hasenack
Thanks for the review laney

I did run the sssd dep8 tests, which exercise openldap, but not a
replication.

So I followed the server guide on setting up replication with TLS
(https://ubuntu.com/server/docs/service-ldap-replication and
https://ubuntu.com/server/docs/service-ldap-with-tls) and confirmed
replication was working. I added data to the provider, and it
immediately appeared on the consumer. Of course, this is a basic test,
and didn't even show the original bug in the current groovy packages,
nor when I updated to 2.4.53 from my ppa, but at least it's not a brown
paper bag release.

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

Title:
  FFe: update to 2.4.53, fixing crash bugs

Status in openldap package in Ubuntu:
  Confirmed

Bug description:
  Groovy has openldap 2.4.51

  Upstream made two quick new releases after that: 2.4.52 and 2.4.53. A
  crash was reported in the mailing list:

  https://lists.openldap.org/hyperkitty/list/openldap-
  techni...@openldap.org/thread/NKOM6DI7RQY6FDLRZGSGYJSGONKIRFEP/

  """
  This segfault is due to a problem with the fix for ITS#9282 that went into 
  the OpenLDAP 2.4.51 and OpenLDAP 2.4.52 releases.  This is fixed in the 
  2.4.53 release (released today).
  """

  Almost all changes in 2.4.52 and 2.4.53 are bug fixes, but a few feathre 
changes/additions slipped through, hence this FFe:
  OpenLDAP 2.4.53 (2020/09/07)
  Added slapd syncrepl additional SYNC logging (ITS#9043)
  Fixed slapd syncrepl segfault on NULL cookie on REFRESH (ITS#9282)
  Fixed slapd syncrepl to use fresh connection on REFRESH fallback 
(ITS#9338)
  Fixed slapo-ppolicy race condition for pwdFailureTime (ITS#9302,ITS#9334)
  Build
  Require OpenSSL 1.0.2 or later (ITS#9323)
  Fixed libldap compilation issue with broken C compilers (ITS#9332)

  OpenLDAP 2.4.52 (2020/08/28)
  Added libldap LDAP_OPT_X_TLS_REQUIRE_SAN option (ITS#9318)
  Added libldap OpenSSL support for multiple EECDH curves (ITS#9054)
  Added slapd OpenSSL support for multiple EECDH curves (ITS#9054)
  Fixed librewrite malloc/free corruption (ITS#9249)
  Fixed libldap hang when using UDP and server down (ITS#9328)
  Fixed slapd syncrepl rare deadlock due to network issues (ITS#9324)
  Fixed slapd syncrepl regression that could trigger an assert (ITS#9329)
  Fixed slapd-mdb index error with collapsed range (ITS#9135)

  I grouped the changes with links to the bug reports:
  Replication fixes:
  Fixed slapd syncrepl segfault on NULL cookie on REFRESH 
(https://bugs.openldap.org/show_bug.cgi?id=9282)
  Fixed slapd syncrepl to use fresh connection on REFRESH fallback 
(https://bugs.openldap.org/show_bug.cgi?id=9338)
  Fixed slapd syncrepl rare deadlock due to network issues 
(https://bugs.openldap.org/show_bug.cgi?id=9324)
  Fixed slapd syncrepl regression that could trigger an assert 
(https://bugs.openldap.org/show_bug.cgi?id=9329)

  Features and other non-fixes changes:
  Added slapd syncrepl additional SYNC logging 
(https://bugs.openldap.org/show_bug.cgi?id=9043)
  Require OpenSSL 1.0.2 or later 
(https://bugs.openldap.org/show_bug.cgi?id=9323)
  Added libldap LDAP_OPT_X_TLS_REQUIRE_SAN option 
(https://bugs.openldap.org/show_bug.cgi?id=9318)
  Added libldap OpenSSL support for multiple EECDH curves 
(https://bugs.openldap.org/show_bug.cgi?id=9054)
  Added slapd OpenSSL support for multiple EECDH curves 
(https://bugs.openldap.org/show_bug.cgi?id=9054)

  Other fixes:
  Fixed slapo-ppolicy race condition for pwdFailureTime 
(https://bugs.openldap.org/show_bug.cgi?id=9302,https://bugs.openldap.org/show_bug.cgi?id=9334)
  Fixed libldap compilation issue with broken C compilers 
(https://bugs.openldap.org/show_bug.cgi?id=9332)
  Fixed librewrite malloc/free corruption 
(https://bugs.openldap.org/show_bug.cgi?id=9249)
  Fixed libldap hang when using UDP and server down 
(https://bugs.openldap.org/show_bug.cgi?id=9328)
  Fixed slapd-mdb index error with collapsed range 
(https://bugs.openldap.org/show_bug.cgi?id=9135)

  
  PPA with a groovy proposed and all arches test build (still ongoing as I 
write this): 
https://launchpad.net/~ahasenack/+archive/ubuntu/openldap-2453/+packages

  I believe a backport of that many fixes is riskier than an update to
  the new upstream version at this point.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1894838/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

2020-09-15 Thread Christian Ehrhardt 
** Branch linked: lp:~paelzer/britney/hints-ubuntu-focal-disable-systemd

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% B  0% => P 67%/) 
FFF..FF..F.FF..F
  root-unittests (F 10% S  0% B  0% => P 90%/) 
FFF...F.
arm64
  tests-in-lxd   (F 40% S  0% B  2% => P 57%/) 
F.B...FFF.FF..F..F.FFF.F
  logind (F  2% S  0% B  2% => P 95%/) 
..B...F.
  upstream   (F 22% S  0% B  2% => P 75%/) 
...F.FB.F.F.F..FFF.F
  root-unittests (F 12% S  0% B  2% => P 85%/) 
..B.F...F.FF...F

  (I'm sure LP will make this unreadable, but is is nice in monospace)

  Whatever the root cause is - the success rate of these has reduced so
  much that the (even formerly questionable) practice of retry-until-
  success won't work anymore.

  
  I have run the two tests in a local VM and systemd-fsckd works there while 
tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services".

  We had the discussion in the past, but I think I need to again bring
  up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until
  they are on reasonable success rates.

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

-- 

[Touch-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected

2020-09-15 Thread Mohammed-Salah OKA
I think this is duplicate with #1840725.

for me the use of a headset allow me to une the microphone.

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

Title:
  [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not
  detected

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I 
have no internal mic detected.
  The GNOME settings sound entry list is empty. Speaker sound is working 
properly.

  When hooking a microphone enabled headphone on the jack plug, the
  headphones mic is then detected, but there is now no sound output on
  the headphone.

  I've been looking for a few similar issues on recent (HP or not)
  laptops and found a few similar issues :

  Bug #1523100
  Bug #1837821

  so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx 
hardware.
  I already tryed quite a few of the workaroubds/fix available here and there 
(e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module 
etc. none with success)

  I'm available to test/provide any additional needed data.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mathieu1719 F pulseaudio
   /dev/snd/controlC0:  mathieu1719 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 14 13:33:14 2019
  InstallationDate: Installed on 2019-12-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Black Mic, Right
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Only some of inputs are working
  Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2019
  dmi.bios.vendor: HP
  dmi.bios.version: R92 Ver. 01.03.04
  dmi.board.name: 860F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 65.23.00
  dmi.chassis.asset.tag: 5CD944676Z
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook 15 G6
  dmi.product.sku: 6VD99AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-09-15 Thread Mohammed-Salah OKA
Have same issue with my "HP ZBook 15 G6" (5CD025HRT7)

when the headset not connected (mic not working)
 List of CAPTURE Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

when the headset connected (work fine)
 List of CAPTURE Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0

uname -a
Linux tawra 5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1699329] Re: every upgrade has errors libssl1.0.0:amd64

2020-09-15 Thread Aldo Hux
** This bug is no longer a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

** Information type changed from Public to Private

** Description changed:

- dpkg: error processing package libssl1.0.0:amd64 (--configure):
-  package libssl1.0.0:amd64 is not ready for configuration
-  cannot configure (current status 'half-installed')
- dpkg: dependency problems prevent configuration of openssl:
-  openssl depends on libssl1.0.0 (>= 1.0.2g); however:
-   Package libssl1.0.0:amd64 is not installed.
- 
- dpkg: error processing package openssl (--configure):
-  dependency problems - leaving unconfigured
- No apport report written because the error message indicates its a followup 
error from a previous failure.
-   dpkg: dependency problems prevent configuration of 
linux-headers-4.8.0-56-generic:
-  linux-headers-4.8.0-56-generic depends on libssl1.0.0 (>= 1.0.0); however:
-   Package libssl1.0.0:amd64 is not installed.
- 
- dpkg: error processing package linux-headers-4.8.0-56-generic (--configure):
-  dependency problems - leaving unconfigured
- dpkg: dependency problems prevent configuration of 
linux-headers-generic-hwe-16.04:
-  linux-headers-generic-hwe-16.04 depends on linux-headers-4.8.0-56-generic; 
however:
-   Package linux-headers-4.8.0-56-generic is not configured yet.
- 
- dpkg: error processing package linux-headers-generic-hwe-16.04 (--configure):
-  dependency problems - leaving unconfigured
- dpkg: dependency problems prevent configuration of linux-generic-hwe-16.04:
-  linux-generic-hwe-16.04 depends on linux-headers-generic-hwe-16.04 (= 
4.8.0.56.27); however:
-   Package linux-headers-generic-hwe-16.04 is not configured yet.
- 
- dpkg: error processing package linux-generic-hwe-16.04 (--configure):
-  dependency probleNo apport report written because the error message 
indicates its a followup error from a previous failure.
- No apport report written because 
MaxReports is reached already
-   No apport report written because MaxReports is 
reached already
- ms - leaving unconfigured
- Errors were encountered while processing:
-  libssl1.0.0:amd64
-  openssl
-  linux-headers-4.8.0-56-generic
-  linux-headers-generic-hwe-16.04
-  linux-generic-hwe-16.04
- E: Sub-process /usr/bin/dpkg returned an error code (1)
- 
- ProblemType: Package
- DistroRelease: Ubuntu 16.04
- Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.8
- ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
- Uname: Linux 4.8.0-54-generic x86_64
- ApportVersion: 2.20.1-0ubuntu2.6
- Architecture: amd64
- Date: Tue Jun 20 16:22:32 2017
- DuplicateSignature:
-  package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.8
-  Setting up libc6-dev:amd64 (2.23-0ubuntu9) ...
-  dpkg: error processing package libssl1.0.0:amd64 (--configure):
-   package libssl1.0.0:amd64 is not ready for configuration
- ErrorMessage: package libssl1.0.0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
- InstallationDate: Installed on 2017-05-31 (20 days ago)
- InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
- RelatedPackageVersions:
-  dpkg 1.18.4ubuntu1.2
-  apt  1.2.20
- SourcePackage: openssl
- Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
package libssl1.0.0:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
- UpgradeStatus: No upgrade log present (probably fresh install)
+ Erase

** Summary changed:

- every upgrade has errors libssl1.0.0:amd64
+ Void

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

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

Title:
  Void

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  Erase

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1699329/+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 1895640] Re: BlueZ 5.55 release

2020-09-15 Thread Daniel van Vugt
** Attachment added: "bluez_5.55.orig.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895640/+attachment/5410977/+files/bluez_5.55.orig.tar.xz

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

Title:
  BlueZ 5.55 release

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.55.tar.xz

  https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.55

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895640/+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 1895640] Re: BlueZ 5.55 release

2020-09-15 Thread Daniel van Vugt
** Attachment added: "bluez_5.55-0ubuntu1.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895640/+attachment/5410978/+files/bluez_5.55-0ubuntu1.debian.tar.xz

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

Title:
  BlueZ 5.55 release

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.55.tar.xz

  https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.55

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895640/+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 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work

2020-09-15 Thread Hui Wang
Please test this kernel: https://people.canonical.com/~hwang4/hstbtn/

to install the testing kernel: sudo dpkg -i linux-image-xxx.deb

reboot and run sudo evtest, then upload the output log of 'sudo evtest'

to uninstall the testing kernel: sudo dpkg -r linux-image- (5.9-rc3)

reboot

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

Title:
  [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control
  buttons don't work

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

Bug description:
  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)

  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why
  does the erroneous behavior of being unable to set volume from my
  earphones happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  4 23:29:52 2020
  InstallationDate: Installed on 2018-09-28 (706 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 02P5YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7570
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+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 1895640] [NEW] BlueZ 5.55 release

2020-09-15 Thread Daniel van Vugt
Public bug reported:

https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.55.tar.xz

https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.55

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Assignee: Daniel van Vugt (vanvugt)
 Status: In Progress


** Tags: groovy

** Description changed:

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.55.tar.xz
+ 
+ https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.55

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

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

Title:
  BlueZ 5.55 release

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.55.tar.xz

  https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.55

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895640/+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 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work

2020-09-15 Thread JasonSome
Would it be helpful if I collected the above requested kernel info too
for my current kernel, or is it contingent on the above mentioned
testing kernel? (an if yes, how would I apply that to a live CD, since I
don't want to interfere with my existing Ubuntu installation with
installing a testing kernel)

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

Title:
  [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control
  buttons don't work

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

Bug description:
  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)

  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why
  does the erroneous behavior of being unable to set volume from my
  earphones happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  4 23:29:52 2020
  InstallationDate: Installed on 2018-09-28 (706 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 02P5YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7570
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+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 1894124] Re: Merge gtk 3.24.22 from Debian

2020-09-15 Thread Sebastien Bacher
Thanks, the fix is in the current version which has been uploaded to the
newest Ubuntu serie

https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.23-1ubuntu1

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Merge gtk 3.24.22 from Debian

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Please merge gtk 3.24.22 from Debian. It supposedly fixes bug #1891761
  and improves frame clock smoothness and fixes frame clock
  monotonicity.

  https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS

  Overview of Changes in GTK+ 3.24.22
  ===

  * GtkTextView:
   - Fix some corner cases of pixelcache invalidation
   - Make select-all work on touch

  * Fix print portal support

  * Adwaita:
   - Tweak title style class
   - Add a public color for text view background

  * Windows:
   - Limit the size of the corner mask cache
   - Use native API for keycode conversion
   - Use GLES on arm64

  * Wayland: Add a way to change the application id (LP: #1891761)

  * Quartz: Add axes to master devices

  * Add --enable-tracker3 option to configure

  * Translation updates:
   Catalan
   German
   Indonesian
   Italian
   Kazakh
   Spanish
   Turkish

  
  Overview of Changes in GTK+ 3.24.21
  ===

  * Wayland:
   - Prevent crashes with offscreen windows
   - Handle disorderly tablet/pad disconnects

  * GtkFileChooser:
   - Translate the type column
   - Add a tracker3 search engine
   - Rate-limit trash monitoring
   - Make get_filter work for native chooser

  * GtkGLArea:
   - Fix a redraw problem

  * GtkScrolledWindow:
   - Fix kinetic scrolling

  * Add a gtk-cursor-aspect-ratio setting

  * GDK:
   - Improve frame clock smoothness
   - Fix frame clock monotonicity

  * OS X:
   - Support Pen / Eraser input
   - Support openfiles in GtkApplication

  * Adwaita:
   - Improve notebook tab legibility

  * Translation updates:
   Basque
   Brazilian Portuguese
   Catalan
   Chinese (Taiwan)
   German
   Indonesian
   Italian
   Japanese
   Kazakh
   Lithuanian
   Polish
   Romanian
   Slovak
   Slovenian
   Swedish
   Ukrainian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1894124/+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 1894737] Re: gtkglarea not working on software renderers

2020-09-15 Thread Sebastien Bacher
Thanks, the fix is in the current version which has been uploaded to the
newest Ubuntu serie

https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.23-1ubuntu1

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  gtkglarea not working on software renderers

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  to reproduce:
  install gtk-3-examples on a system with software rendering, like virtualbox.
  run gtk3-demo --run=glarea
  observe black boxes.
  I fixed it upstream with this commit:
  
https://gitlab.gnome.org/GNOME/gtk/-/commit/69334021a22a79f5fddb30f0872fcf3fc6bc1cf0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1894737/+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 1894838] Re: FFe: update to 2.4.53, fixing crash bugs

2020-09-15 Thread Iain Lane
Agreed that taking the unit which upstream has validated is more
sensible than backporting. Thanks for the detailed report. I think the
only thing which I would like to see in future is you saying that (and
how) you've tested it manually and spotted no regressions.

But go ahead this time.

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

Title:
  FFe: update to 2.4.53, fixing crash bugs

Status in openldap package in Ubuntu:
  Confirmed

Bug description:
  Groovy has openldap 2.4.51

  Upstream made two quick new releases after that: 2.4.52 and 2.4.53. A
  crash was reported in the mailing list:

  https://lists.openldap.org/hyperkitty/list/openldap-
  techni...@openldap.org/thread/NKOM6DI7RQY6FDLRZGSGYJSGONKIRFEP/

  """
  This segfault is due to a problem with the fix for ITS#9282 that went into 
  the OpenLDAP 2.4.51 and OpenLDAP 2.4.52 releases.  This is fixed in the 
  2.4.53 release (released today).
  """

  Almost all changes in 2.4.52 and 2.4.53 are bug fixes, but a few feathre 
changes/additions slipped through, hence this FFe:
  OpenLDAP 2.4.53 (2020/09/07)
  Added slapd syncrepl additional SYNC logging (ITS#9043)
  Fixed slapd syncrepl segfault on NULL cookie on REFRESH (ITS#9282)
  Fixed slapd syncrepl to use fresh connection on REFRESH fallback 
(ITS#9338)
  Fixed slapo-ppolicy race condition for pwdFailureTime (ITS#9302,ITS#9334)
  Build
  Require OpenSSL 1.0.2 or later (ITS#9323)
  Fixed libldap compilation issue with broken C compilers (ITS#9332)

  OpenLDAP 2.4.52 (2020/08/28)
  Added libldap LDAP_OPT_X_TLS_REQUIRE_SAN option (ITS#9318)
  Added libldap OpenSSL support for multiple EECDH curves (ITS#9054)
  Added slapd OpenSSL support for multiple EECDH curves (ITS#9054)
  Fixed librewrite malloc/free corruption (ITS#9249)
  Fixed libldap hang when using UDP and server down (ITS#9328)
  Fixed slapd syncrepl rare deadlock due to network issues (ITS#9324)
  Fixed slapd syncrepl regression that could trigger an assert (ITS#9329)
  Fixed slapd-mdb index error with collapsed range (ITS#9135)

  I grouped the changes with links to the bug reports:
  Replication fixes:
  Fixed slapd syncrepl segfault on NULL cookie on REFRESH 
(https://bugs.openldap.org/show_bug.cgi?id=9282)
  Fixed slapd syncrepl to use fresh connection on REFRESH fallback 
(https://bugs.openldap.org/show_bug.cgi?id=9338)
  Fixed slapd syncrepl rare deadlock due to network issues 
(https://bugs.openldap.org/show_bug.cgi?id=9324)
  Fixed slapd syncrepl regression that could trigger an assert 
(https://bugs.openldap.org/show_bug.cgi?id=9329)

  Features and other non-fixes changes:
  Added slapd syncrepl additional SYNC logging 
(https://bugs.openldap.org/show_bug.cgi?id=9043)
  Require OpenSSL 1.0.2 or later 
(https://bugs.openldap.org/show_bug.cgi?id=9323)
  Added libldap LDAP_OPT_X_TLS_REQUIRE_SAN option 
(https://bugs.openldap.org/show_bug.cgi?id=9318)
  Added libldap OpenSSL support for multiple EECDH curves 
(https://bugs.openldap.org/show_bug.cgi?id=9054)
  Added slapd OpenSSL support for multiple EECDH curves 
(https://bugs.openldap.org/show_bug.cgi?id=9054)

  Other fixes:
  Fixed slapo-ppolicy race condition for pwdFailureTime 
(https://bugs.openldap.org/show_bug.cgi?id=9302,https://bugs.openldap.org/show_bug.cgi?id=9334)
  Fixed libldap compilation issue with broken C compilers 
(https://bugs.openldap.org/show_bug.cgi?id=9332)
  Fixed librewrite malloc/free corruption 
(https://bugs.openldap.org/show_bug.cgi?id=9249)
  Fixed libldap hang when using UDP and server down 
(https://bugs.openldap.org/show_bug.cgi?id=9328)
  Fixed slapd-mdb index error with collapsed range 
(https://bugs.openldap.org/show_bug.cgi?id=9135)

  
  PPA with a groovy proposed and all arches test build (still ongoing as I 
write this): 
https://launchpad.net/~ahasenack/+archive/ubuntu/openldap-2453/+packages

  I believe a backport of that many fixes is riskier than an update to
  the new upstream version at this point.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1894838/+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 1895631] [NEW] systemd at 100% handling apport failures

2020-09-15 Thread Colin Ian King
Public bug reported:

systemd is pegged at 100% after booting Groovy Desktop.

Seems like an apport-report.service issue:

Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.

I removed apport to resolve the issue.

** Affects: systemd (Ubuntu)
 Importance: Medium
 Status: New

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

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

Title:
  systemd at 100% handling apport failures

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd is pegged at 100% after booting Groovy Desktop.

  Seems like an apport-report.service issue:

  Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
  Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
  Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
  Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
  Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request 
repeated too quickly.

  I removed apport to resolve the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895631/+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 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work

2020-09-15 Thread Daniel van Vugt
** Summary changed:

- [Samsung Earphones Tuned by AKG] Volume control buttons don't work
+ [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons 
don't work

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

Title:
  [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control
  buttons don't work

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

Bug description:
  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)

  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why
  does the erroneous behavior of being unable to set volume from my
  earphones happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  4 23:29:52 2020
  InstallationDate: Installed on 2018-09-28 (706 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 02P5YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7570
  dmi.sys.vendor: Dell Inc.

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

2020-09-15 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1894338

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control
  buttons don't work

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

Bug description:
  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)

  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why
  does the erroneous behavior of being unable to set volume from my
  earphones happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  4 23:29:52 2020
  InstallationDate: Installed on 2018-09-28 (706 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 02P5YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7570
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+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 1894338] Re: [Samsung Earphones Tuned by AKG] Volume control buttons don't work

2020-09-15 Thread Hui Wang
This depends on the hardware design first, if the audio jack and the
codec supports it or not.

Then it depends on the kernel driver. With the ubuntu 20.04, the
userspace part is OK to support the headset button, since I already
verified it on the Leonvo x1c7.

I will build a testing kernel, let us see if it could work or not.

thx.


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

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

Title:
  [Samsung Earphones Tuned by AKG] Volume control buttons don't work

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

Bug description:
  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)

  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why
  does the erroneous behavior of being unable to set volume from my
  earphones happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  4 23:29:52 2020
  InstallationDate: Installed on 2018-09-28 (706 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 02P5YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7570
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

2020-09-15 Thread Christian Ehrhardt 
Thanks rbalint for pointing me to the other bug for the s390x fail we see now.
I'll continue there and consider the Groovy portion of this one closed again.

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% B  0% => P 67%/) 
FFF..FF..F.FF..F
  root-unittests (F 10% S  0% B  0% => P 90%/) 
FFF...F.
arm64
  tests-in-lxd   (F 40% S  0% B  2% => P 57%/) 
F.B...FFF.FF..F..F.FFF.F
  logind (F  2% S  0% B  2% => P 95%/) 
..B...F.
  upstream   (F 22% S  0% B  2% => P 75%/) 
...F.FB.F.F.F..FFF.F
  root-unittests (F 12% S  0% B  2% => P 85%/) 
..B.F...F.FF...F

  (I'm sure LP will make this unreadable, but is is nice in monospace)

  Whatever the root cause is - the success rate of these has reduced so
  much that the (even formerly questionable) practice of retry-until-
  success won't work anymore.

  
  I have run the two tests in a local VM and systemd-fsckd works there while 
tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services".

  We had the discussion in the past, but I think I need to again bring
  up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until
  they are on reasonable success rates.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1895576] Re: boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x

2020-09-15 Thread Christian Ehrhardt 
Thanks for this bug Rbalint.
That the new glibc/cryptsetup worked is odd as nothing on the issue indicates 
they are related. There was nothing in the queue - for the sake of some test 
data I have restarted the packages currently blocked on this with all-proposed 
which will pull in e.g. gblibc/cryptsetup.

Let us check in some hours how that worked out ...

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

Title:
  boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x

Status in systemd package in Ubuntu:
  New

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  groovy/groovy/s390x/s/systemd/20200903_184028_2bbdf@/log.gz

  ...
  test_rsyslog (__main__.ServicesTest) ... FAIL
  test_tmp_cleanup (__main__.ServicesTest) ... ok
  test_tmp_mount (__main__.ServicesTest) ... ok
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'

  ==
  FAIL: test_rsyslog (__main__.ServicesTest)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.15TVnz/build.ZVh/real-tree/debian/tests/boot-and-services", 
line 120, in test_rsyslog
  self.assertRegex(log, 'systemd.*Reached target Graphical Interface')
  ...

  Interestingly it does not fail locally on an s390x Focal VM running 
boot-and-services in LXD.
  Kernel:
  Linux juju-d7a408-generic-21 5.4.0-14-generic 

  Also interestingly it is passing with cryptsetup/2:2.3.3-1ubuntu5
  glibc/2.32-0ubuntu2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895576/+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 1894338] Re: [Samsung Earphones Tuned by AKG] Volume control buttons don't work

2020-09-15 Thread Daniel van Vugt
I was wondering if this was a kernel bug...

** Also affects: linux (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/1894338

Title:
  [Samsung Earphones Tuned by AKG] Volume control buttons don't work

Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)

  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why
  does the erroneous behavior of being unable to set volume from my
  earphones happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  4 23:29:52 2020
  InstallationDate: Installed on 2018-09-28 (706 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 02P5YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7570
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+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 1894338] Re: [Samsung Earphones Tuned by AKG] Volume control buttons don't work

2020-09-15 Thread Hui Wang
@JasonSome,

So far, the linux kernel (audio driver) only supports the headset button
on some specific machines like Lenovo X1C7.

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

Title:
  [Samsung Earphones Tuned by AKG] Volume control buttons don't work

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)

  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why
  does the erroneous behavior of being unable to set volume from my
  earphones happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  4 23:29:52 2020
  InstallationDate: Installed on 2018-09-28 (706 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 02P5YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7570
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894338/+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 1894338] Re: [Samsung Earphones Tuned by AKG] Volume control buttons don't work

2020-09-15 Thread Daniel van Vugt
** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => 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/1894338

Title:
  [Samsung Earphones Tuned by AKG] Volume control buttons don't work

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)

  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why
  does the erroneous behavior of being unable to set volume from my
  earphones happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  4 23:29:52 2020
  InstallationDate: Installed on 2018-09-28 (706 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 02P5YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7570
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894338/+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 1660316] Re: apparmor denial of CUPS

2020-09-15 Thread Claudio Kuenzler
Same happens in 18.04 (Linux Mint 19.3). Needed to manually add the
net_admin caps as mentioned by Jamie.

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

Title:
  apparmor denial of CUPS

Status in cups package in Ubuntu:
  Expired

Bug description:
  Printing is enabled when doing sudo aa-complain cupsd

  Here is an extract of /var/log/syslog:

  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929457] audit: type=1400 
audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 
comm="apparmor_parser"
  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929744] audit: type=1400 
audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser"
  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.945422] audit: type=1400 
audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 
comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817070] audit: type=1400 
audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 
comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817342] audit: type=1400 
audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.837254] audit: type=1400 
audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 
comm="apparmor_parser"
  Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: 
downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: 
Error when getting information for file '/home/dag/.glvndcEQzqA': No such file 
or directory
  Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service'
  Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service...
  Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service.
  Jan 30 12:42:26 dag-TS-P500 kernel: [  895.746636] audit: type=1400 
audit(1485776546.086:43): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12  capname="net_admin"
  Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary 
Directories...
  Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary 
Directories.
  Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.OneConf'
  Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.OneConf'
  Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts'
  Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.sso'
  Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.sso'
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 
audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 
comm="apparmor_parser"
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 
audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser"
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 
audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=7024 
comm="apparmor_parser"
  Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940891] audit: type=1400 
audit(1485776757.284:47): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12  capname="net_admin"
  Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940938] audit: type=1400 
audit(1485776757.284:48): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12  capname="net_admin"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: cups 2.2.0-2
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset 

[Touch-packages] [Bug 1894338] Re: [Samsung Earphones Tuned by AKG] Volume control buttons don't work

2020-09-15 Thread JasonSome
Yes, precisely as expected.

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

Title:
  [Samsung Earphones Tuned by AKG] Volume control buttons don't work

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  My earphones are the one coming with Samsung Galaxy S8 (here:
  https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung-
  earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04
  (dual-boot with Windows 10, Secure Boot enabled)

  Trying to set the volume from my earphones' controls doesn't work, no
  modification on the volume, the sound bar on Ubuntu doesn't appear in
  order to indicate volume change. I would like to change the master
  volume, or whatever my common laptop controls do when I up/down the
  volume controls on my earphones, like it happens on Windows 10. Why
  does the erroneous behavior of being unable to set volume from my
  earphones happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.10
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  4 23:29:52 2020
  InstallationDate: Installed on 2018-09-28 (706 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 02P5YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7570
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894338/+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 1314160] Re: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb

2020-09-15 Thread Claudio Kuenzler
Still present in 18.04.

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

Title:
  Apparmor profile violated: cupsd does mknod on
  /var/cache/samba/gencache.tdb

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When I print to my smb printer, I get a dbus notification of the
  following entries in my syslog:

  Apr 29 12:27:15 tinker kernel: [ 3359.467314] type=1400 
audit(1398770835.923:150): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7
  Apr 29 12:27:15 tinker kernel: [ 3359.467453] type=1400 
audit(1398770835.923:151): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7
  Apr 29 12:27:15 tinker kernel: [ 3359.469047] type=1400 
audit(1398770835.923:152): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7

  I get new entries every time I print. I'm running Ubuntu 14.04 with
  cups-daemon 1.7.2-0ubuntu1 on btrfs, fwiw.

  I saw this replicated on http://www.dedoimedo.com/computers/ubuntu-
  trusty-tahr-laptop-ultrabook.html .

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