date:20200616

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

** Changed in: glib-networking (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Failed to load module: /usr/lib/x86_64-linux-
  gnu/gio/modules/libgiognutls.so

Status in glib-networking package in Ubuntu:
  Expired

Bug description:
  distro: xubuntu 18

  I'm trying to set up a google drive account on my pc and when I run
  the command "env XDG_CURRENT_DESKTOP=GNOME gnome-control-center" the
  following error occurs but opens the settings. When clicking on online
  accounts and trying to configure a google account, the error "TLS /
  SSL support not available; install glib-networking" occurs. I have
  glib-networking installed.

  pc:~$ env XDG_CURRENT_DESKTOP=GNOME gnome-control-center

  (gnome-control-center:13525): Clutter-WARNING **: 16:14:16.359: Whoever 
translated default:LTR did so wrongly.
  /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: symbol 
gnutls_pkcs11_privkey_init, version GNUTLS_3_4 not defined in file 
libgnutls.so.30 with link time reference
  Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
  /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: symbol 
gnutls_pkcs11_privkey_init, version GNUTLS_3_4 not defined in file 
libgnutls.so.30 with link time reference
  Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: glib-networking 2.55.90-1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Feb 23 08:03:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-13 (101 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: glib-networking
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1876882] Re: Backport packages for 18.04.5 HWE stack

This bug was fixed in the package xserver-xorg-video-ati-hwe-18.04 -
1:19.1.0-1~18.04.1

---
xserver-xorg-video-ati-hwe-18.04 (1:19.1.0-1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.5 HWE stack update. (LP: #1876882)

 -- Timo Aaltonen   Thu, 21 May 2020 10:17:02 +0300

** Changed in: llvm-toolchain-10 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Invalid
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-10 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

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

-- 
Mailing list: https://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 1876882] Re: Backport packages for 18.04.5 HWE stack

This bug was fixed in the package llvm-toolchain-10 -
1:10.0.0-4ubuntu1~18.04.1

---
llvm-toolchain-10 (1:10.0.0-4ubuntu1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.5 HWE stack update. (LP: #1876882)

 -- Timo Aaltonen   Fri, 15 May 2020 13:05:47 +0300

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Invalid
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-10 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

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

-- 
Mailing list: https://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 1876882] Re: Backport packages for 18.04.5 HWE stack

This bug was fixed in the package xserver-xorg-video-amdgpu-hwe-18.04 -
19.1.0-1~18.04.1

---
xserver-xorg-video-amdgpu-hwe-18.04 (19.1.0-1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.5 HWE stack update. (LP: #1876882)

 -- Timo Aaltonen   Thu, 21 May 2020 10:16:59 +0300

** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Invalid
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-10 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

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

-- 
Mailing list: https://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 1876882] Re: Backport packages for 18.04.5 HWE stack

This bug was fixed in the package xorg-server-hwe-18.04 -
2:1.20.8-2ubuntu2.1~18.04.1

---
xorg-server-hwe-18.04 (2:1.20.8-2ubuntu2.1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.5 HWE stack update. (LP: #1876882)
  * control: Relax debhelper requirement.
  * control: Relax libepoxy-dev requirement, we don't need
EGL_MESA_query_driver on bionic.
  * rules: xdmx-tools isn't packaged, so don't try to skip it.

 -- Timo Aaltonen   Thu, 14 May 2020 22:05:06 +0300

** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Invalid
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-10 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

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

-- 
Mailing list: https://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 1876882] Re: Backport packages for 18.04.5 HWE stack

This bug was fixed in the package libdrm - 2.4.101-2~18.04.1

---
libdrm (2.4.101-2~18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.5 HWE stack update. (LP: #1876882)
  * control: Relax debhelper requirement.

 -- Timo Aaltonen   Mon, 11 May 2020 15:47:23 +0300

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

** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Invalid
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-10 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

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

-- 
Mailing list: https://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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Good. That discussion appears to be held above my head, so I'm going to
keep quiet there. All I can say is that I was able to reproduce the
issue in groovy.

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Thanks. Further comments on that topic are on that page.

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

** Bug watch removed: gitlab.gnome.org/GNOME/mutter/-/issues #948
   https://gitlab.gnome.org/GNOME/mutter/-/issues/948

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://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

2020-06-16 Thread Alex Hung

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

-- 
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:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  dump_acpi_tables.py generates log files that is similar as the output
  from "acpidump" in acpica-tools. The output can be past to other
  utilities in acpica-tools and / or 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 1882034] Re: cannot start X session with NIS account

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

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

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

Title:
  cannot start X session with NIS account

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When login with a NIS account, X does not start, or more precisely it
  starts and exits immediately.

  Only errors in logs is:
   (EE) systemd-logind: failed to get session: PID 4335 does not belong to any 
known session

  X11/gdm login works fine with local accounts.

  SSH/terminal console login with NIS accounts works fine.

  /etc/X11/Xwrapper.config:
allowed_users=anybody

  I've seen several reports of such problems under other versions (eg
  19.10), but no working solutions was found. It seems that the problem
  is the same with lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  4 08:59:25 2020
  InstallationDate: Installed on 2019-11-26 (190 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)

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

-- 
Mailing list: https://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 1883779] Re: Hub-connected mouse doesn't work until suspend

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

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

Title:
  Hub-connected mouse doesn't work until suspend

Status in linux package in Ubuntu:
  New

Bug description:
  I'm using a USB hub with 4 inputs, one of them is my mouse.

  The mouse doesn't react when I boot the computer into Linux, even if I
  re-plug it into the same or another slot in the hub. It works in
  Windows. It works when connected to a computer USB port.

  The mouse starts working through the hub after I suspend the computer
  then wake it up.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 21:57:02 2020
  DistUpgraded: 2020-04-26 18:49:17,342 DEBUG found components: {'focal': 
{'main', 'universe', 'multiverse', 'restricted'}, 'focal-updates': {'main', 
'universe', 'multiverse', 'restricted'}, 'focal-security': {'main', 'universe', 
'multiverse', 'restricted'}}
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   88x2bu, 1.1, 5.4.0-33-generic, x86_64: installed
   88x2bu, 1.1, 5.4.0-37-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1080] [1462:3362]
  InstallationDate: Installed on 2018-01-05 (893 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=8acf1b56-9cb9-4afa-82c6-7f17663120be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-04-26 (51 days ago)
  dmi.bios.date: 04/29/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z97 MARK 2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0801:bd04/29/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ97MARK2:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

https://gitlab.gnome.org/GNOME/mutter/-/issues/948

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #948
   https://gitlab.gnome.org/GNOME/mutter/-/issues/948

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

I'm not aware of any regression. What is the bug ID for that?

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1883718] Re: zoom in/out problem

Sorry I accidentally deleted one of the attachments. Please add it back
in if you can.

But it looks like the same video you provided earlier this week so
that's Chromium, not Xorg.

** Tags removed: patch

** Patch removed: "Bug "
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883718/+attachment/5384414/+files/VID-20200615-WA0004.mp4

** Package changed: xorg (Ubuntu) => chromium-browser (Ubuntu)

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

Title:
  zoom in/out problem

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://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 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content

This bug was fixed in the package apport - 2.20.11-0ubuntu27.3

---
apport (2.20.11-0ubuntu27.3) focal; urgency=medium

  * apport_python_hook.py: if python apt modules are not built for the python
version then do capture the crash. (LP: #1774843)
  * apport/report.py: If the user is not a part of any system groups then
set UserGroups to 'N/A'. (LP: #1427600)

 -- Brian Murray   Mon, 01 Jun 2020 09:44:37 -0700

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

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

Title:
  apport-unpack: ValueError: ['UserGroups'] has no binary content

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Focal:
  Fix Released
Status in apport source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  apport-unpack crashes when trying to unpack a crash

  [Test Case]
  On a system running 20.04 LTS:
  1) create an additional user who is only a member of their own group e.g.
  bdmurray@clean-focal-amd64:~$ id crashy
  uid=1001(crashy) gid=1001(crashy) groups=1001(crashy)
  2) Launch a process as that user
  3) kill -11 that process
  4) Confirm there is a crash file in /var/crash for that process
  5) Run apport-unpack on that .crash file

  With the version of apport from -proposed you will not get another
  crash file when unpacking the crash file.

  [Regression Potential]
  We are just setting UserGroups to 'N/A' as opposed to having it be completely 
empty so there isn't any chance for regression.

  When running apport-unpack to get at a core dump

  laney@raleigh> sudo apport-unpack 
_usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz
  [sudo] password for laney:
  Traceback (most recent call last):
    File "/usr/bin/apport-unpack", line 73, in 
  pr.extract_keys(f, bin_keys, dir)
    File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in 
extract_keys
  [item for item, element in b64_block.items() if element is False])
  ValueError: ['UserGroups'] has no binary content
  laney@raleigh> apport-cli --version
  2.16.2

  It's not terrible, because most files are unpacked (those which sort
  before UserGroups, I guess).

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: apport 2.16.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportLog:

  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 10:09:26 2015
  InstallationDate: Installed on 2012-10-07 (876 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)

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

-- 
Mailing list: https://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 1774843] Re: apport python exception for python versions which python-apt is not built on

This bug was fixed in the package apport - 2.20.11-0ubuntu27.3

---
apport (2.20.11-0ubuntu27.3) focal; urgency=medium

  * apport_python_hook.py: if python apt modules are not built for the python
version then do capture the crash. (LP: #1774843)
  * apport/report.py: If the user is not a part of any system groups then
set UserGroups to 'N/A'. (LP: #1427600)

 -- Brian Murray   Mon, 01 Jun 2020 09:44:37 -0700

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

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

Title:
  apport python exception for python versions which python-apt is not
  built on

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in python3.7 package in Ubuntu:
  Invalid
Status in python3.8 package in Ubuntu:
  Invalid
Status in apport source package in Bionic:
  Fix Released
Status in python3.7 source package in Bionic:
  Won't Fix
Status in python3.8 source package in Bionic:
  Won't Fix
Status in apport source package in Eoan:
  Fix Released
Status in python3.7 source package in Eoan:
  Won't Fix
Status in python3.8 source package in Eoan:
  Won't Fix
Status in apport source package in Focal:
  Fix Released
Status in python3.7 source package in Focal:
  Invalid
Status in python3.8 source package in Focal:
  Invalid

Bug description:
  [Impact]
  apport's python crash handler runs for every installed version of python e.g. 
on Ubuntu 18.04 LTS it will run for crashes with python3.6 or python3.7 as an 
interpreter. However, python apt modules are only available for the the 
supported version of python so the crash handler generates an exception which 
is annoying.

  [Test Case for 18.04]
  1) Install the non-default version of python3 e.g. python3.7 on Ubuntu 18.04 
LTS.
  2) Run 'python3.7 -c 'print hello' and observe a Traceback re apt_pkg not 
being found.

  With the version of python3-apport from -proposed you'll not receive
  the Traceback from step # 2.

  [Test Case for 20.04]
  1) Install python3.7 and python3.8 on an Ubuntu 19.10 system
  2) Upgrade from 19.10 to 20.04 LTS and keep python3.7 installed
  3) Run 'python3.7 -c 'print hello' and observe a Traceback re apt_pkg not 
being found.

  With the version of python3-apport from -proposed you'll not receive
  the Traceback from step # 2

  [Regression Potential]
  Its possible the crash handler change is incorrect so it should be confirmed 
that we still get python crashes about the system version of python. One way to 
do this is to run 'apport-cli coreutils < /dev/null'.

  [Original Description]
  it seems apport installs an exception hook whenever running python3.
  This hook is apparently installed for python3.7 too.
  This exception handler has a dependency on apt_pkg, which is a binary that is 
not compatible with python3.7 it seems (you can't import it, see below)

  As a result, whenever I run a python3.7 script and run into an exception 
(which happens often when writing code), I get an additional exception in the 
exception handler + a copy of the original exception, so three stacktraces in 
total.
  A solution would be to only install the exception hook for the system python  
i.e. python3.6

  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  apport: 2.20.9-0ubuntu7
  python-apt: 1.6.0
  python3.7: 3.7.0~b3-1

  Demo with a trivial error:
  $ python3 -c 'print hello'
    File "", line 1
  print hello
    ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  $ python3.7 -c 'print hello'
    File "", line 1
  print hello
    ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  Error in sys.excepthook:
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
  from apport.fileutils import likely_packaged, get_recent_crashes
    File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

  from apport.report import Report
    File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
  import apport.fileutils
    File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in 

  from apport.packaging_impl import impl as packaging
    File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in 

  import apt
    File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in 
  import apt_pkg
  ModuleNotFoundError: No module named 'apt_pkg'

  Original exception was:
    File "", line 1
  print hello
    ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  Python 3.6.5 (default, Apr  1 2018, 05:46:30)
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more

[Touch-packages] [Bug 1427600] Update Released

2020-06-16 Thread Chris Halse Rogers

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

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

Title:
  apport-unpack: ValueError: ['UserGroups'] has no binary content

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Focal:
  Fix Released
Status in apport source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  apport-unpack crashes when trying to unpack a crash

  [Test Case]
  On a system running 20.04 LTS:
  1) create an additional user who is only a member of their own group e.g.
  bdmurray@clean-focal-amd64:~$ id crashy
  uid=1001(crashy) gid=1001(crashy) groups=1001(crashy)
  2) Launch a process as that user
  3) kill -11 that process
  4) Confirm there is a crash file in /var/crash for that process
  5) Run apport-unpack on that .crash file

  With the version of apport from -proposed you will not get another
  crash file when unpacking the crash file.

  [Regression Potential]
  We are just setting UserGroups to 'N/A' as opposed to having it be completely 
empty so there isn't any chance for regression.

  When running apport-unpack to get at a core dump

  laney@raleigh> sudo apport-unpack 
_usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz
  [sudo] password for laney:
  Traceback (most recent call last):
    File "/usr/bin/apport-unpack", line 73, in 
  pr.extract_keys(f, bin_keys, dir)
    File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in 
extract_keys
  [item for item, element in b64_block.items() if element is False])
  ValueError: ['UserGroups'] has no binary content
  laney@raleigh> apport-cli --version
  2.16.2

  It's not terrible, because most files are unpacked (those which sort
  before UserGroups, I guess).

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: apport 2.16.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportLog:

  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 10:09:26 2015
  InstallationDate: Installed on 2012-10-07 (876 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)

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

-- 
Mailing list: https://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 1876882] Update Released

2020-06-16 Thread Chris Halse Rogers

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

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Invalid
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-10 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-10: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

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

-- 
Mailing list: https://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 1881659] Re: Dell Inspirion 5391: headphones work only if I manually switch source port every time and no different volume levels for speaker and headphones

2020-06-16 Thread Hui Wang

For the issue of the default input device, we are working on it.
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/295

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

Title:
  Dell Inspirion 5391: headphones work only if I manually switch source
  port every time and no different volume levels for speaker and
  headphones

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a laptop Dell Inspirion 5391 that was shipped with Ubuntu
  18.04, and it doesn't have such problems. But I have manually
  installed Xubuntu 20.04 LTS (firstly because I need full disk
  encryption with LUKS). And I have two problems the with sound system:

  1) If I plug headphones, there is no sound. Sound becomes only if I
  manually switch source port to "Headset Mono microphone" from
  "Headphones stereo microphone" in pavucontrol or with the command:

  pacmd set-source-port 4  "[In] Headset"

  or with ALSA:

  amixer set 'Input Source' 'Headset Mic'

  I have a workaround with /etc/acpi/events, but it is not seamless (I
  have an one second delay when I plug the headphones).

  2) There is no separate volume levels for speaker and headphone in
  pulseaudio.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tenikeev   3385 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Jun  1 23:13:38 2020
  InstallationDate: Installed on 2020-05-28 (4 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 07DM2C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd11/21/2019:svnDellInc.:pnInspiron5391:pvr:rvnDellInc.:rn07DM2C:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5391
  dmi.product.sku: 096E
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-05-31T22:56:28.472784

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

-- 
Mailing list: https://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 1883798] [NEW] package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different

2020-06-16 Thread spyam

Public bug reported:

not install file !!! packettracer

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libjpeg-turbo8 2.0.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
AptOrdering:
 libjpeg-turbo8:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jun 17 03:37:01 2020
DpkgTerminalLog:
 Preparing to unpack .../libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb ...
 Unpacking libjpeg-turbo8:amd64 (2.0.3-0ubuntu1.20.04.1) over (2.0.3-0ubuntu1) 
...
 [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb 
(--unpack):
  trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
InstallationDate: Installed on 2020-06-16 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: libjpeg-turbo
Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which 
is different from other instances of package libjpeg-turbo8:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libjpeg-turbo (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade:
  trying to overwrite shared '/usr/share/doc/libjpeg-
  turbo8/changelog.Debian.gz', which is different from other instances
  of package libjpeg-turbo8:amd64

Status in libjpeg-turbo package in Ubuntu:
  New

Bug description:
  not install file !!! packettracer

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libjpeg-turbo8 2.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  AptOrdering:
   libjpeg-turbo8:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jun 17 03:37:01 2020
  DpkgTerminalLog:
   Preparing to unpack .../libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb ...
   Unpacking libjpeg-turbo8:amd64 (2.0.3-0ubuntu1.20.04.1) over 
(2.0.3-0ubuntu1) ...
   [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
  InstallationDate: Installed on 2020-06-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', 
which is different from other instances of package libjpeg-turbo8:amd64
  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/1883798/+subscriptions

-- 
Mailing list: https://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

2020-06-16 Thread Dan Streetman

I think this is fixed by upstream commit
eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c

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

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

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

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

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

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

Title:
  systemd-networkd crashes with invalid pointer

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

Bug 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 to VPC cidrs via 
inside gateway in

[Touch-packages] [Bug 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify

Hello Adriaan, or anyone else affected,

Accepted openssh into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:8.2p1-4ubuntu0.1 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  Port parameter sshd_config is 22 AND whatever you specify

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Focal:
  Fix Committed
Status in openssh package in Debian:
  Fix Released

Bug description:
  [Impact]

   * The "Port" option in sshd_config is accumulative, but due to a bug re-
 adds the default when an include is encountered. Therefore we have these 
 cases
 a) Port 722
Listens on 722 (correct)
 b) Port 722
Port 
Listens on 722 &  (correct)
 c) Port 722
include /path/to/otherconfig
Listens on 722 & 22 (applied defaults as if Port was unset)

   * Of the above (c) is a bug, not documented that way and can lead to open 
 ports not expected and not wanted.

  [Test Case]

  * Test if defaults are applied even if option is specified

  Rename sshd_config to something_else and replace sshd_config with two
  lines to include the original config (now called something_else) and
  set the Port to 7722:

  systemctl stop ssh
  mv /etc/ssh/sshd_config /etc/ssh/something_else
  cat > /etc/ssh/sshd_config

[Touch-packages] [Bug 1881659] Re: Dell Inspirion 5391: headphones work only if I manually switch source port every time and no different volume levels for speaker and headphones

2020-06-16 Thread tim474

Yes. Headphones work with this version of Pulseaudio. Thank you. But
there is still a problem with volume level. If I plug and unplug
headphones, Speaker volume level drops to level of headphones, then I
can't separate set up volume level for headphones and speaker. But there
is no this problem with OEM version of Ubuntu.

And another problem. If I plug headphones with mic, set external mic as
input device (in pavucontrol), unplug and plug again, the default source
device is still internal mic. I want to set up automatic switching to
external mic if I plug it. As in previous case, there is not such
problem in OEM ubuntu.

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

Title:
Dell Inspirion 5391: headphones work only if I manually switch source
port every time and no different volume levels for speaker and
headphones

Status in pulseaudio package in Ubuntu:
New

Bug description:
I have a laptop Dell Inspirion 5391 that was shipped with Ubuntu
18.04, and it doesn't have such problems. But I have manually
installed Xubuntu 20.04 LTS (firstly because I need full disk
encryption with LUKS). And I have two problems the with sound system:

1) If I plug headphones, there is no sound. Sound becomes only if I
manually switch source port to "Headset Mono microphone" from
"Headphones stereo microphone" in pavucontrol or with the command:

pacmd set-source-port 4 "[In] Headset"

or with ALSA:

amixer set 'Input Source' 'Headset Mic'

I have a workaround with /etc/acpi/events, but it is not seamless (I
have an one second delay when I plug the headphones).

2) There is no separate volume levels for speaker and headphone in
pulseaudio.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tenikeev 3385 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Mon Jun 1 23:13:38 2020
InstallationDate: Installed on 2020-05-28 (4 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 07DM2C
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.3.0:bd11/21/2019:svnDellInc.:pnInspiron5391:pvr:rvnDellInc.:rn07DM2C:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5391
dmi.product.sku: 096E
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2020-05-31T22:56:28.472784

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

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

[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-06-16 Thread Wesley Batista Santos

The comment #65 was what worked for me.

https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1840725/comments/65


My OS installation is Kubuntu 18.04.

Additional and more detailed info about my laptop:

```
$ uname -a
Linux ioku 5.3.0-59-generic #53~18.04.1-Ubuntu SMP Thu Jun 4 14:58:26 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux


$ sudo dmidecode -t system
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 3.1.1 present.

Handle 0x0012, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 20QDCTO1WW
Version: ThinkPad X1 Carbon 7th
Serial Number: PF1E44X3
UUID: 06E257CC-238A-11B2-A85C-ECF7951B56CA
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
Family: ThinkPad X1 Carbon 7th

Handle 0x0027, DMI type 12, 5 bytes
System Configuration Options

Handle 0x0037, DMI type 15, 31 bytes
System Event Log
Area Length: 1586 bytes
Header Start Offset: 0x
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: General-purpose non-volatile data functions
Access Address: 0x00F0
Status: Valid, Not Full
Change Token: 0x0062
Header Format: Type 1
Supported Log Type Descriptors: 4
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: PCI system error
Data Format 2: None
Descriptor 3: System reconfigured
Data Format 3: None
Descriptor 4: Log area reset/cleared
Data Format 4: None


$ arecord -l
 List of CAPTURE Hardware Devices 
card 0: sofsklhdacard [sof-skl_hda_card], device 0: HDA Analog (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsklhdacard [sof-skl_hda_card], device 1: HDA Digital (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsklhdacard [sof-skl_hda_card], device 6: DMIC32 (*) []
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: sofsklhdacard [sof-skl_hda_card], device 7: DMIC16 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

```

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Touch-packages] [Bug 1883781] [NEW] [X570 AORUS ULTRA, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Underruns, dropouts or crackling sound

2020-06-16 Thread Rim

Public bug reported:

I have continuous noise / constant "shooting" instead of the audio and
video. I guess it appeared after the latest Ubuntu update. I cannot
watch any video, hear any sound in any program, only glitches,
shattering noise, and video freezing.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  airim  1808 F pulseaudio
 /dev/snd/controlC0:  airim  1808 F pulseaudio
 /dev/snd/pcmC1D0p:   airim  1808 F...m pulseaudio
 /dev/snd/timer:  airim  1808 f pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 16 23:09:41 2020
InstallationDate: Installed on 2020-01-08 (160 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: GP102 HDMI Audio Controller - HDA NVidia
Symptom_Jack: Digital Out, HDMI
Symptom_PulseAudioLog: июн 16 23:06:40 airim dbus-daemon[1055]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.31' (uid=124 pid=1242 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [X570 AORUS ULTRA, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Underruns, 
dropouts or crackling sound
UpgradeStatus: Upgraded to focal on 2020-04-25 (52 days ago)
dmi.bios.date: 12/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F11
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS ULTRA
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X570 AORUS ULTRA
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug focal

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

Title:
  [X570 AORUS ULTRA, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI]
  Underruns, dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have continuous noise / constant "shooting" instead of the audio and
  video. I guess it appeared after the latest Ubuntu update. I cannot
  watch any video, hear any sound in any program, only glitches,
  shattering noise, and video freezing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  airim  1808 F pulseaudio
   /dev/snd/controlC0:  airim  1808 F pulseaudio
   /dev/snd/pcmC1D0p:   airim  1808 F...m pulseaudio
   /dev/snd/timer:  airim  1808 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 23:09:41 2020
  InstallationDate: Installed on 2020-01-08 (160 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GP102 HDMI Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulseAudioLog: июн 16 23:06:40 airim dbus-daemon[1055]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.31' (uid=124 pid=1242 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [X570 AORUS ULTRA, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] 
Underruns, dropouts or crackling sound
  UpgradeStatus: Upgraded to focal on 2020-04-25 (52 days ago)
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor:

[Touch-packages] [Bug 1883779] [NEW] Hub-connected mouse doesn't work until suspend

2020-06-16 Thread Wojciech Kaliciński

Public bug reported:

I'm using a USB hub with 4 inputs, one of them is my mouse.

The mouse doesn't react when I boot the computer into Linux, even if I
re-plug it into the same or another slot in the hub. It works in
Windows. It works when connected to a computer USB port.

The mouse starts working through the hub after I suspend the computer
then wake it up.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 16 21:57:02 2020
DistUpgraded: 2020-04-26 18:49:17,342 DEBUG found components: {'focal': 
{'main', 'universe', 'multiverse', 'restricted'}, 'focal-updates': {'main', 
'universe', 'multiverse', 'restricted'}, 'focal-security': {'main', 'universe', 
'multiverse', 'restricted'}}
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 88x2bu, 1.1, 5.4.0-33-generic, x86_64: installed
 88x2bu, 1.1, 5.4.0-37-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-37-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] 
[1462:3362]
InstallationDate: Installed on 2018-01-05 (893 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: ASUS All Series
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=8acf1b56-9cb9-4afa-82c6-7f17663120be ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-04-26 (51 days ago)
dmi.bios.date: 04/29/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH Z97 MARK 2
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0801:bd04/29/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ97MARK2:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Hub-connected mouse doesn't work until suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm using a USB hub with 4 inputs, one of them is my mouse.

  The mouse doesn't react when I boot the computer into Linux, even if I
  re-plug it into the same or another slot in the hub. It works in
  Windows. It works when connected to a computer USB port.

  The mouse starts working through the hub after I suspend the computer
  then wake it up.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend

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

2020-06-16 Thread John Nielsen

I've gathered several core dumps now but the stacktraces are identical.
The logged reason for dumping core is "free(): invalid pointer".

I wonder if there is a race condition with whatever networkd itself is
doing when it reconfigures the interface (which it seems to do more
aggressively for DHCP renewals than it used to) and what my scripts in
/etc/networkd-dispatcher/configured.d and /etc/networkd-
dispatcher/configuring.d are doing. Assuming the
"routing_policy_rule_free" function is equivalent to "ip rule delete
..." there could be a conflict with my "configuring.d" script in
particular. The "configured.d" script adds some extra routing policy
rules and the "configuring.d" script deletes them so they aren't
duplicated every time the network is configured.

** Changed in: systemd (Ubuntu)
   Status: Incomplete => 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/1881972

Title:
  systemd-networkd crashes with invalid pointer

Status in systemd package in Ubuntu:
  New

Bug 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

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

2020-06-16 Thread John Nielsen

# coredumpctl gdb 28819
   PID: 28819 (systemd-network)
   UID: 100 (systemd-network)
   GID: 102 (systemd-network)
Signal: 6 (ABRT)
 Timestamp: Tue 2020-06-16 19:36:22 UTC (16min ago)
  Command Line: /lib/systemd/systemd-networkd
Executable: /lib/systemd/systemd-networkd
 Control Group: /system.slice/systemd-networkd.service
  Unit: systemd-networkd.service
 Slice: system.slice
   Boot ID: 578e8b2c2e1a43afbd27211be1a4f531
Machine ID: ec267b3475883f9edb99f554607bb456
  Hostname: ip-10-0-4-251
   Storage: 
/var/lib/systemd/coredump/core.systemd-network.100.578e8b2c2e1a43afbd27211be1a4f531.28819.159233618200.lz4
   Message: Process 28819 (systemd-network) of user 100 dumped core.

Stack trace of thread 28819:
#0  0x7f740d023e97 raise (libc.so.6)
#1  0x7f740d025801 abort (libc.so.6)
#2  0x7f740d06e897 n/a (libc.so.6)
#3  0x7f740d07590a n/a (libc.so.6)
#4  0x7f740d07ce1c cfree (libc.so.6)
#5  0x55fa5c16276b routing_policy_rule_free 
(systemd-networkd)
#6  0x55fa5c1f69e2 manager_rtnl_process_rule 
(systemd-networkd)
#7  0x55fa5c1731d6 process_match (systemd-networkd)
#8  0x55fa5c173413 io_callback (systemd-networkd)
#9  0x55fa5c178350 source_dispatch (systemd-networkd)
#10 0x55fa5c1785ea sd_event_dispatch (systemd-networkd)
#11 0x55fa5c178779 sd_event_run (systemd-networkd)
#12 0x55fa5c1789bb sd_event_loop (systemd-networkd)
#13 0x55fa5c1413a6 main (systemd-networkd)
#14 0x7f740d006b97 __libc_start_main (libc.so.6)
#15 0x55fa5c141a8a _start (systemd-networkd)


** Attachment added: "core dump file"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1881972/+attachment/5384495/+files/core.systemd-network.100.578e8b2c2e1a43afbd27211be1a4f531.28819.159233618200.lz4

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

Title:
  systemd-networkd crashes with invalid pointer

Status in systemd package in Ubuntu:
  Incomplete

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

[Touch-packages] [Bug 1883082] Re: Crash when using Package-Whitelist-Strict

2020-06-16 Thread Balint Reczey

@panfaust I've already fixed it up and the second version still needs extra 
annotation. 
https://github.com/mvo5/unattended-upgrades/pull/277

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

Title:
  Crash when using Package-Whitelist-Strict

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades source package in Focal:
  New

Bug description:
  Hi,

  I'm trying to use unattended-upgrades only with a few packages from a
  list; to do that I tried this simple /etc/apt/apt.conf.d/51local-ua
  file:

  root@focal-ua:~# cat /etc/apt/apt.conf.d/51local-ua   

   
  Unattended-Upgrade::Package-Whitelist-Strict "true";  

   
  Unattended-Upgrade::Package-Whitelist {
  "firefox";
  "bash";
  "openssh-server";
  }

  When running unattended-upgrades in dry run mode I get this crash:

  root@focal-ua:~# unattended-upgrade --debug --dry-run
  Running on the development release
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, 
o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security, 
o=UbuntuESM,a=focal-security
  Initial blacklist: 
  Initial whitelist (strict): firefox bash openssh-server
  Marking not allowed  
with -32768 pin
  Marking not allowed  
with -32768 pin
  Marking not allowed  
with -32768 pin
  Marking not allowed  
with -32768 pin
  Marking not allowed  with -32768 pin
  Marking not allowed  
with -32768 pin
  Marking not allowed  with -32768 pin
  Marking not allowed  
with -32768 pin
  Marking not allowed  with -32768 pin
  Marking not allowed  
with -32768 pin
  An error occurred: '>' not supported between instances of 'apt_pkg.Version' 
and 'int'
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1983, in main
  res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2124, in run
  cache = UnattendedUpgradesCache(rootdir=rootdir)
File "/usr/bin/unattended-upgrade", line 171, in __init__
  apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__
  self.open(progress)
File "/usr/bin/unattended-upgrade", line 330, in open
  self.apply_pinning(self.pinning_from_config())
File "/usr/bin/unattended-upgrade", line 302, in pinning_from_config
  and policy.get_candidate_ver(pkg) > -1:  # type: ignore   

   
  TypeError: '>' not supported between instances of 'apt_pkg.Version' and 'int' 

   
  Extracting content from 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2020-06-11 
09:38:25
  
  Traceback (most recent call last):

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

   
  sys.exit(main(options))   

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

   
  res = run(options, rootdir, mem_log, logfile_dpkg,

   
File "/usr/bin/unattended-upgrade", line 2124, in run   

   
  cache = UnattendedUpgradesCache(rootdir=rootdir)  

   
File "/usr/bin/unattended-upgrade", line 171, in __init__   

   
  apt.Cache.__init__(self, rootdir=rootdir)

[Touch-packages] [Bug 1883338] Re: unattended-upgrades blocks apt

2020-06-16 Thread Balint Reczey

The dpkg frontend starting earlier takes the lock until it is finished.

20.04's unattended-upgrades is much faster, BTW.

Unattended-upgrades gracefully stops when it gets the TERM signal, thus
it can be asked to quit, but I think it is not needed in 20.04 because
u-u became fast enough in typical cases.

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

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

Title:
  unattended-upgrades blocks apt

Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  Version: Ubuntu 18.04 and all prior versions that include unattended-
  upgrades

  Buggy behavior:

  I boot a laptop that has been off for a while with the intent to install 
linux updates.
  I type apt-get update; apt full-upgrade  and it fails, finding that 
unattended upgrades is running in the background for an extended period of 
time, but not actually running dpkg at all, just holding the lock, preventing 
me from running updates.

  
  Expected behavior:

  apt full-upgrade, the graphical update manager, and related commands
  should either

  1) Immediately (and silently?) abort whatever unattended-upgrades is
  doing and proceed with running updates in the foreground

  2) Display progress of updates currently running in the background,
  waiting for them to finish, and then proceed with running additional
  updates in the foreground

  Note that it may be necessary to implement both behaviors, depending
  if unattended-upgrades is just spinning or if it has actually started
  running upgrades.

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

-- 
Mailing list: https://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 1015819] Re: sb_sasl_generic_pkt_length: received illegal packet length when using Active Directory and ldapsearch and sasl with ssl or tls

2020-06-16 Thread Sergio Durigan Junior

** Changed in: cyrus-sasl2 (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  sb_sasl_generic_pkt_length: received illegal packet length when using
  Active Directory and ldapsearch and sasl with ssl or tls

Status in Cyrus-sasl2:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 source package in Bionic:
  Triaged
Status in cyrus-sasl2 source package in Cosmic:
  Won't Fix

Bug description:
  [Status]

  Awaiting upstream fix.

  [Workaround]

  Unknown.

  [Description]

  Not sure if this is a problem with openldap or cyrus-sasl2 at this
  point.

  Using sasl binding only works with ldapsearch when not using ssl or
  tls.  If either ssl or tls is used I see this ouput from -d 1 from
  ldapsearch:

  sb_sasl_generic_pkt_length: received illegal packet length of 813957120 bytes
  sasl_generic_read: want=16, got=16
    :  00 7e 02 01 00 78 84 00  00 00 5d 0a 01 02 04 00   .~...x].
  sb_sasl_cyrus_decode: failed to decode packet: generic failure
  sb_sasl_generic_read: failed to decode packet
  ldap_read: want=8 error=Input/output error

  # numResponses: 0
  ldap_result: Can't contact LDAP server (-1)
  tls_write: want=165 error=Connection reset by peer
  tls_write: want=165 error=Bad file descriptor

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/1015819/+subscriptions

-- 
Mailing list: https://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 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke

Hello Claire, or anyone else affected,

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

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

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

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

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

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

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

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

Title:
  BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi
  broke

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

Bug description:
  [Impact]

   * A driver supports FT (IEEE 802.11r-2008 or fast BSS transition (FT),
 also called fast roaming) if it either supports SME or the
 NL80211_CMD_UPDATE_FT_IES command. When selecting AKM suites,
 wpa_supplicant currently doesn't take into account whether or not either
 of those conditions are met. This can cause association failures, e.g.,
 when an AP supports both WPA-EAP and FT-EAP but the driver doesn't
 support FT (wpa_supplicant will decide to do FT-EAP since it is unaware
 the driver doesn't support it).

   * This is known to affect users at least users with popular chip-sets,
 such as BCM20703A1 or BCM4350 (notably present in the popular XPS 13/15
 laptops).

   * The upload fixes the bug by allowing an FT suite to be selected only
 when the driver also supports FT.

  [Test Case]

   * requires affected hardware and wpa_supplicant built with CONFIG_IEEE80211R
 and connecting to an AP supporting WPA-EAP and FT-EAP

  [Regression Potential]

   * a driver not advertising correctly its support for SME or the
 NL80211_CMD_UPDATE_FT_IES command via the drv_flags would be prevented from
 using FT but would still be able to connect to APs

  [Other Info]

   * Upstream fix: 
https://w1.fi/cgit/hostap/commit/?id=23dc196fde951b3d508f367a603cddffbd053490
   * Initial report: https://bugs.archlinux.org/task/63397
  ---

  Upgraded to 20.04 and the wifi broke.  It was working fine on 18.04.  Tried a 
variety of things with apw but nada.  /var/log attached
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1438 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-07-09 (329 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. XPS 15 9550
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550
  dmi.product.sku: 06E4
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf

Hello Laurent, or anyone else affected,

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

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

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

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

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

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

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

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

Title:
  wpasupplicant: unknown keys in no-mac-addr-change.conf

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Focal:
  Fix Committed
Status in wpa package in Debian:
  New

Bug description:
  * Impact
  wpa ships an invalid network-manager configuration that triggers warnings

  * Test case
  $ journalctl | grep no-mac-addr-change
  should not have errors listed

  * Regression potential
  the change removes configurations which are not needed (since they set the 
value to the same one as the default) and in the wrong section, it shouldn't 
have any visible impact

  

  Hi,

  NetworkManager warns that no-mac-addr-change.conf contains unknown
  configuration directives:

  # journalctl | grep no-mac-addr-change
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 
20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 
10-globally-managed-devices.conf, default-wifi-powersave-on.conf)
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'wifi.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: wpasupplicant 2:2.6-21ubuntu3
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 27 13:15:27 2019
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1879087] Re: dbus errors, frequent roaming and unstable connectivity

Hello Thomas, or anyone else affected,

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

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

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

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

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

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

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

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

Title:
  dbus errors, frequent roaming and unstable connectivity

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

Bug description:
  * Impact
  extra roaming events are been generated

  * Test case
  check the output of `journalctl -lu wpa_supplicant`, it shouldn't have those 
warnings
  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  the roaming events should not be too frequent

  * Regression potential
  check that wifi connection keep working correctly

  --

  When using this version of wpa_supplicant with my company
  WPA2-Enterprise wireless setup, I'm experiencing far too frequent
  roaming events (even when not moving around) accompanied by hiccups in
  connectivity. I also see these messages in the wpa_supplicant log:

  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property RoamTime in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property SessionLength in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  Having done a little research, at least the dbus errors seem to be
  fixed by this commit upstream:

  
https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756

  So I built a version of wpa_supplicant including this particular patch
  and installed on my machine. Apart from solving the dbus errors
  completely, it seems to have had a positive impact on the frequent
  roaming and unstable connectivity as well (I've run for a day with no
  burst of roaming events at all, where they used to happen every few
  minutes most of the time.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wpasupplicant 2:2.9-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat May 16 16:47:27 2020
  InstallationDate: Installed on 2020-05-12 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1881278] Re: Ship 2018 Archive key in xenial's ubuntu-keyring

This bug was fixed in the package ubuntu-keyring - 2012.05.19.1

---
ubuntu-keyring (2012.05.19.1) xenial; urgency=medium

  * Add 4096R/991BC93C Ubuntu Archive Automatic Signing Key (2018)
 to ubuntu-archive-keyring. LP: #1881278

 -- Dimitri John Ledkov   Fri, 29 May 2020 12:58:19
+0100

** Changed in: ubuntu-keyring (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Ship 2018 Archive key in xenial's ubuntu-keyring

Status in ubuntu-keyring package in Ubuntu:
  Invalid
Status in ubuntu-keyring source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Xenial systems will not be able to debootstrap Groovy archives when
  it finally switches to be signed by single 2018 key. To have support
  for xenial to operate against Groovy+ archives it needs access to 2018
  archive key. Ship it.

  [Test Case]

   * Start xenial chroot or lxd container.
   * Observe that 4 keys are trusted - the original 2004 archive & cdimage, 
2012 archive & cdimage

  # apt-key list --fingerprint
  /etc/apt/trusted.gpg
  
  pub   1024D/437D05B5 2004-09-12
Key fingerprint = 6302 39CC 130E 1A7F D81A  27B1 4097 6EAF 437D 05B5
  uid  Ubuntu Archive Automatic Signing Key 

  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
Key fingerprint = 790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid  Ubuntu Archive Automatic Signing Key (2012) 


  pub   4096R/EFE21092 2012-05-11
Key fingerprint = 8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
  uid  Ubuntu CD Image Automatic Signing Key (2012) 


  pub   1024D/FBB75451 2004-12-30
Key fingerprint = C598 6B4F 1257 FFA8 6632  CBA7 4618 1433 FBB7 5451
  uid  Ubuntu CD Image Automatic Signing Key 


* Install the new ubuntu-keyring package
* Observe that 5 keys are now trusted, including the 2018 archive key

  # apt-key list --fingerprint
  /etc/apt/trusted.gpg
  
  pub   1024D/437D05B5 2004-09-12
Key fingerprint = 6302 39CC 130E 1A7F D81A  27B1 4097 6EAF 437D 05B5
  uid  Ubuntu Archive Automatic Signing Key 

  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
Key fingerprint = 790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid  Ubuntu Archive Automatic Signing Key (2012) 


  pub   4096R/EFE21092 2012-05-11
Key fingerprint = 8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
  uid  Ubuntu CD Image Automatic Signing Key (2012) 


  pub   1024D/FBB75451 2004-12-30
Key fingerprint = C598 6B4F 1257 FFA8 6632  CBA7 4618 1433 FBB7 5451
  uid  Ubuntu CD Image Automatic Signing Key 


  pub   4096R/991BC93C 2018-09-17
Key fingerprint = F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
  uid  Ubuntu Archive Automatic Signing Key (2018) 


* Dist upgrade to bionic
* Observe that only 3 keys are trusted the 2012 cdimage + 2018 key, 
and that none of them are in /etc/apt/trusted.gpg but are key snippets in 
/etc/apt/trusted.gpg.d/

  # apt-key list
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg
  --
  pub   rsa4096 2012-05-11 [SC]
790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2012) 


  /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg
  --
  pub   rsa4096 2012-05-11 [SC]
8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
  uid   [ unknown] Ubuntu CD Image Automatic Signing Key (2012) 


  /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
  --
  pub   rsa4096 2018-09-17 [SC]
F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2018) 


  
  [Regression Potential] 

   * Adding additional new trust key can trigger support request (aka
  why are you adding this key on xenial). The reason to add this key on
  xenial, is for xenial to allow securely debootstrap and operate on
  Groovy+ repositories which are about to drop 2012 key signatures.

  [Other Info]
   
   * Bionic switched from shipping keys in /etc/apt/trusted.gpg keyring, to 
individual snippets. Thus xenial's upload that adds the future key to 
/etc/apt/trusted.gpg should also remove it, during upgrade to bionic. To ensure 
that the systems upgraded from xenial to bionic, look the same as those that 
are fresh bionic installations.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1881278] Update Released

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

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

Title:
  Ship 2018 Archive key in xenial's ubuntu-keyring

Status in ubuntu-keyring package in Ubuntu:
  Invalid
Status in ubuntu-keyring source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Xenial systems will not be able to debootstrap Groovy archives when
  it finally switches to be signed by single 2018 key. To have support
  for xenial to operate against Groovy+ archives it needs access to 2018
  archive key. Ship it.

  [Test Case]

   * Start xenial chroot or lxd container.
   * Observe that 4 keys are trusted - the original 2004 archive & cdimage, 
2012 archive & cdimage

  # apt-key list --fingerprint
  /etc/apt/trusted.gpg
  
  pub   1024D/437D05B5 2004-09-12
Key fingerprint = 6302 39CC 130E 1A7F D81A  27B1 4097 6EAF 437D 05B5
  uid  Ubuntu Archive Automatic Signing Key 

  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
Key fingerprint = 790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid  Ubuntu Archive Automatic Signing Key (2012) 


  pub   4096R/EFE21092 2012-05-11
Key fingerprint = 8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
  uid  Ubuntu CD Image Automatic Signing Key (2012) 


  pub   1024D/FBB75451 2004-12-30
Key fingerprint = C598 6B4F 1257 FFA8 6632  CBA7 4618 1433 FBB7 5451
  uid  Ubuntu CD Image Automatic Signing Key 


* Install the new ubuntu-keyring package
* Observe that 5 keys are now trusted, including the 2018 archive key

  # apt-key list --fingerprint
  /etc/apt/trusted.gpg
  
  pub   1024D/437D05B5 2004-09-12
Key fingerprint = 6302 39CC 130E 1A7F D81A  27B1 4097 6EAF 437D 05B5
  uid  Ubuntu Archive Automatic Signing Key 

  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
Key fingerprint = 790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid  Ubuntu Archive Automatic Signing Key (2012) 


  pub   4096R/EFE21092 2012-05-11
Key fingerprint = 8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
  uid  Ubuntu CD Image Automatic Signing Key (2012) 


  pub   1024D/FBB75451 2004-12-30
Key fingerprint = C598 6B4F 1257 FFA8 6632  CBA7 4618 1433 FBB7 5451
  uid  Ubuntu CD Image Automatic Signing Key 


  pub   4096R/991BC93C 2018-09-17
Key fingerprint = F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
  uid  Ubuntu Archive Automatic Signing Key (2018) 


* Dist upgrade to bionic
* Observe that only 3 keys are trusted the 2012 cdimage + 2018 key, 
and that none of them are in /etc/apt/trusted.gpg but are key snippets in 
/etc/apt/trusted.gpg.d/

  # apt-key list
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg
  --
  pub   rsa4096 2012-05-11 [SC]
790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2012) 


  /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg
  --
  pub   rsa4096 2012-05-11 [SC]
8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
  uid   [ unknown] Ubuntu CD Image Automatic Signing Key (2012) 


  /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
  --
  pub   rsa4096 2018-09-17 [SC]
F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2018) 


  
  [Regression Potential] 

   * Adding additional new trust key can trigger support request (aka
  why are you adding this key on xenial). The reason to add this key on
  xenial, is for xenial to allow securely debootstrap and operate on
  Groovy+ repositories which are about to drop 2012 key signatures.

  [Other Info]
   
   * Bionic switched from shipping keys in /etc/apt/trusted.gpg keyring, to 
individual snippets. Thus xenial's upload that adds the future key to 
/etc/apt/trusted.gpg should also remove it, during upgrade to bionic. To ensure 
that the systems upgraded from xenial to bionic, look the same as those that 
are fresh bionic installations.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

This bug was fixed in the package accountsservice -
0.6.55-0ubuntu12~20.04.1

---
accountsservice (0.6.55-0ubuntu12~20.04.1) focal; urgency=medium

  * Backport from groovy to focal.

accountsservice (0.6.55-0ubuntu12) groovy; urgency=medium

  * Cherry-pick from unstable.
  * Add patch to not crash in the library when the daemon goes away
(Closes: #948228) (LP: #1843982)

 -- Iain Lane   Tue, 05 May 2020 17:05:26 +0100

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

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Fix Released
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  [ Description ]

  When accountsservice's daemon is restarted - particularly when there
  is a user configured for auto login - it can cause code using its
  library to crash. This is bad because gnome-shell is one of those
  users which crashes.

  [ QA ]

  Configure a user for automatic login in gnome-shell.

  Update to this SRU, and then *restart your system*. The crash is in
  the library part, and so you will still see it if programs loaded the
  buggy version. Restarting is the easiest way to make sure you're not
  on it.

  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.

  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.

  ---

  Test that fast user switching still works properly.

  ---

  Take a look at the error reports listed below and hopefully see them
  not occurring (barring the usual noise) with the SRU.

  [ Regression potential ]

  We think this is safe - it tells clients that the daemon is away when
  it quits, and is back when it comes back. They should get appropriate
  signals to indicate this. Nevertheless, these signals are sent when
  they weren't before now, so that could cause problems. Watch out for
  errors creeping up with this SRU.

  We wondered upstream whether some more protections might be needed.
  I'm thinking that those should be *additional* safety rails around
  this fix, but it could actually be that more is needed and this fix
  isn't complete.

  [ Original report ]

  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://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 1843982] Update Released

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

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Fix Released
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  [ Description ]

  When accountsservice's daemon is restarted - particularly when there
  is a user configured for auto login - it can cause code using its
  library to crash. This is bad because gnome-shell is one of those
  users which crashes.

  [ QA ]

  Configure a user for automatic login in gnome-shell.

  Update to this SRU, and then *restart your system*. The crash is in
  the library part, and so you will still see it if programs loaded the
  buggy version. Restarting is the easiest way to make sure you're not
  on it.

  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.

  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.

  ---

  Test that fast user switching still works properly.

  ---

  Take a look at the error reports listed below and hopefully see them
  not occurring (barring the usual noise) with the SRU.

  [ Regression potential ]

  We think this is safe - it tells clients that the daemon is away when
  it quits, and is back when it comes back. They should get appropriate
  signals to indicate this. Nevertheless, these signals are sent when
  they weren't before now, so that could cause problems. Watch out for
  errors creeping up with this SRU.

  We wondered upstream whether some more protections might be needed.
  I'm thinking that those should be *additional* safety rails around
  this fix, but it could actually be that more is needed and this fix
  isn't complete.

  [ Original report ]

  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://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 1883718] Re: zoom in/out problem

2020-06-16 Thread 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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1883718

Title:
  zoom in/out problem

Status in xorg package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://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 1869981] Re: Printer notification every day at midnight

2020-06-16 Thread Till Kamppeter

I have already found a solution for this and applied it upstream
(1.27.5, already in Grrovy).

The problem is that near midnight, for the log rotate cups-browsed is
stopped and restarted. Stopping cups-browsed makes the cups-browsed-
generated print queues getting removed and when re-starting cups-browsed
afterwards they are generated again. This causes the notifications.

My approach is to let cups-browsed not remove the queues on shut-down,
on re-start cups-browsed connects to these queues again (as I have
designed cups-browsed to cope with crashes) and so no queue-creation
happens.

Zdenek Dohnal from Red Hat suggests modifying gnome-settings-daemon to
identify queues coming from cups-browsed and not notifying then. See

https://github.com/OpenPrinting/cups-filters/issues/241

Marking as fixed as my approach has made it into Groovy already.

** Bug watch added: github.com/OpenPrinting/cups-filters/issues #241
   https://github.com/OpenPrinting/cups-filters/issues/241

** Changed in: cups (Ubuntu)
   Status: Triaged => Fix Released

** Package changed: cups (Ubuntu) => cups-filters (Ubuntu)

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

Title:
  Printer notification every day at midnight

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1883723] Re: Some official repositories changed compression method from gzip to lz4 leading to checksum errors during apt-get update

2020-06-16 Thread Julian Andres Klode

You have enabled storing indexes in compressed form, which is a non-
default setting that does not work very well. In early days, this used
to store files in the form the server offered them, but this was changed
to recompress to lz4 in order to improve the run time performance of
apt.

Unfortunately, we are going to need a way to reproduce the issue,
otherwise we can't do much about it. There are likely various bugs in
various places of the downloading process that lead to it using files in
the wrong states.

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

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

Title:
  Some official repositories changed compression method from gzip to lz4
  leading to checksum errors during apt-get update

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  This includes bionic-security repositories:

  Reading package lists... Done
  E: Failed to fetch 
store:/var/lib/apt/lists/partial/pl.archive.ubuntu.com_ubuntu_dists_bionic-security_Contents-i386.gz
  Hash Sum mismatch
     Hashes of expected file:
  - Filesize:821731759 [weak]
  - SHA256:03b7fe601ba17908a5bfc628c8eb8309cd682f88ea5c2ed8139a4d46bb02df09
  - SHA1:5b0ca78303b67f3e1e78c828ac10474f4acf8c10 [weak]
  - MD5Sum:fa890ae0f75a803fa744ce126739bfa6 [weak]
     Hashes of received file:
  - SHA256:9cd965c8d4f68b92cfc20484aabf19899b53718f810dc316f7983c4b194108dd
  - SHA1:7c27b4efd7c3ca176b3e7ed85dec5d865a8928b8 [weak]
  - MD5Sum:c1a1a8baef4d45ce444962b981a

  Failed files:
  nusch@xps13:/etc/apt$ sudo ls -l /var/lib/apt/lists/partial/ | grep FAILED
  lrwxrwxrwx 1 root root   87 cze 16 16:52 
pl.archive.ubuntu.com_ubuntu_dists_bionic-proposed_Contents-i386.gz.FAILED -> 
/var/lib/apt/lists/pl.archive.ubuntu.com_ubuntu_dists_bionic-proposed_Contents-i386.lz4
  lrwxrwxrwx 1 root root   87 cze 16 16:52 
pl.archive.ubuntu.com_ubuntu_dists_bionic-security_Contents-i386.gz.FAILED -> 
/var/lib/apt/lists/pl.archive.ubuntu.com_ubuntu_dists_bionic-security_Contents-i386.lz4

  Not sure from where this issue comes - manual browsing of repository
  discovers only .gz file while downloaded copy have lz4 extension.
  After manual downloading .gz one and uncompromising diff command
  confirms both produce the same file.  Apt-get clean and deleting cache
  doesn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.12ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-107.108-generic 4.15.18
  Uname: Linux 4.15.0-107-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 16:49:31 2020
  InstallationDate: Installed on 2015-05-08 (1866 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2018-08-26 (659 days ago)

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

-- 
Mailing list: https://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 1883723] Re: Some official repositories changed compression method from gzip to lz4 leading to checksum errors during apt-get update

2020-06-16 Thread Seth Arnold

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

Title:
  Some official repositories changed compression method from gzip to lz4
  leading to checksum errors during apt-get update

Status in apt package in Ubuntu:
  New

Bug description:
  This includes bionic-security repositories:

  Reading package lists... Done
  E: Failed to fetch 
store:/var/lib/apt/lists/partial/pl.archive.ubuntu.com_ubuntu_dists_bionic-security_Contents-i386.gz
  Hash Sum mismatch
     Hashes of expected file:
  - Filesize:821731759 [weak]
  - SHA256:03b7fe601ba17908a5bfc628c8eb8309cd682f88ea5c2ed8139a4d46bb02df09
  - SHA1:5b0ca78303b67f3e1e78c828ac10474f4acf8c10 [weak]
  - MD5Sum:fa890ae0f75a803fa744ce126739bfa6 [weak]
     Hashes of received file:
  - SHA256:9cd965c8d4f68b92cfc20484aabf19899b53718f810dc316f7983c4b194108dd
  - SHA1:7c27b4efd7c3ca176b3e7ed85dec5d865a8928b8 [weak]
  - MD5Sum:c1a1a8baef4d45ce444962b981a

  Failed files:
  nusch@xps13:/etc/apt$ sudo ls -l /var/lib/apt/lists/partial/ | grep FAILED
  lrwxrwxrwx 1 root root   87 cze 16 16:52 
pl.archive.ubuntu.com_ubuntu_dists_bionic-proposed_Contents-i386.gz.FAILED -> 
/var/lib/apt/lists/pl.archive.ubuntu.com_ubuntu_dists_bionic-proposed_Contents-i386.lz4
  lrwxrwxrwx 1 root root   87 cze 16 16:52 
pl.archive.ubuntu.com_ubuntu_dists_bionic-security_Contents-i386.gz.FAILED -> 
/var/lib/apt/lists/pl.archive.ubuntu.com_ubuntu_dists_bionic-security_Contents-i386.lz4

  Not sure from where this issue comes - manual browsing of repository
  discovers only .gz file while downloaded copy have lz4 extension.
  After manual downloading .gz one and uncompromising diff command
  confirms both produce the same file.  Apt-get clean and deleting cache
  doesn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.12ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-107.108-generic 4.15.18
  Uname: Linux 4.15.0-107-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 16:49:31 2020
  InstallationDate: Installed on 2015-05-08 (1866 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2018-08-26 (659 days ago)

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

-- 
Mailing list: https://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 1883412] Re: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve

2020-06-16 Thread Stephen Warren

The system has resolvconf 1.82 installed. /etc/resolv.conf claims that
it's generated by resolvconf, at least after I switched the system to
netplan, and I'm pretty sure it did before to. I also have ifupdown
0.8.35ubuntu1 installed.

A thought on deprecation: A deprecated package is simply something that
isn't suitable for new use. If the package still exists, it must still
work correctly; known non-working software shouldn't be shipped. At the
point that's no longer possible, it can be removed (hopefully with an
automated transition plan in do-release-upgrade).

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

Title:
  20.04: DNS servers from /etc/network/interfaces not honored by
  systemd-resolve

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I have a server that uses /etc/network/interfaces to configure static
  IP info, including DNS, via /etc/network/interfaces. This worked fine
  in 16.04 and 18.04. However, when I updated to 20.04 this no longer
  works; I have to run "systemd-resolve --set-dns=192.168.63.1
  --interface=enp3s0" to fix it after every boot.

  My /etc/network/interfaces is:

  
  # Loopback
  auto lo
  iface lo inet loopback

  # enp3s0: LAN (Motherboard)
  auto enp3s0
  iface enp3s0 inet static
  address 192.168.63.2
  netmask 255.255.255.0
  network 192.168.63.0
  broadcast 192.168.63.255
  gateway 192.168.63.1
  dns-nameservers 192.168.63.1

  iface enp3s0 inet6 static
  address 2001:470:bb52:63::2/64
  netmask 64

  # WiFi USB
  # FIXME: Probably will get renamed on boot
  #allow-hotplug ethFlashAirWifi
  #iface ethFlashAirWifi inet manual
  

  "systemd-resolve --status" outputs the following beforr I run the WAR
  command given above:

  
  Global
 LLMNR setting: no  
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  
DNSSEC NTA: 10.in-addr.arpa 
16.172.in-addr.arpa 
168.192.in-addr.arpa
17.172.in-addr.arpa 
18.172.in-addr.arpa 
19.172.in-addr.arpa 
20.172.in-addr.arpa 
21.172.in-addr.arpa 
22.172.in-addr.arpa 
23.172.in-addr.arpa 
24.172.in-addr.arpa 
25.172.in-addr.arpa 
26.172.in-addr.arpa 
27.172.in-addr.arpa 
28.172.in-addr.arpa 
29.172.in-addr.arpa 
30.172.in-addr.arpa 
31.172.in-addr.arpa 
corp
d.f.ip6.arpa
home
internal
intranet
lan 
local   
private 
test

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jun 14 01:58:10 2020
  InstallationDate: Installed on 2016-04-12 (1524 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic 
root=/dev/mapper/severn_vg2016-lv_root ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago)
  dmi.bios.date: 06/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.40
  dmi.board.name: 890GX

[Touch-packages] [Bug 1869981] Re: Printer notification every day at midnight

IRC discussion extract

 seb128 see /etc/logrotate.d/cups-daemon postrotate "invoke-rc.d 
--quiet cups restart > /dev/null"; and cups-browsed.service has Requires: 
cups.service so it will restart, too
usually it's so the daemon closes the old logfile and opens the new one, but a 
full restart does seem excessive

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

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  Triaged

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1883718] Re: zoom in/out problem

I've been going through this problem since I left Windows and came to Ubuntu 
Linux. My computer is not running smoothly. There are all kinds of problems. I 
can't think of anything to do. I'm very worried that you are not solving the 
problem properly.
#2 & #3 please I request you to watch the video and fix this problem because I 
have been going through this problem for a long time and I can't find any 
solution to this problem. No one can fix all the problems of system 
software.When I scroll an application after opening the computer, sometimes it 
is not working, then it is working in zoom in zoom out, for this I am not able 
to do any work well, sometimes the system automatically opens one new tab after 
another.

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

Title:
  zoom in/out problem

Status in xorg package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://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 1883718] Re: zoom in/out problem

** Attachment added: "Bug  2"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883718/+attachment/5384418/+files/VID-20200615-WA0005.mp4

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

Title:
  zoom in/out problem

Status in xorg package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://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 1883718] Re: zoom in/out problem

** Attachment added: "Bug "
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883718/+attachment/5384414/+files/VID-20200615-WA0004.mp4

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

Title:
  zoom in/out problem

Status in xorg package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://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 1869981] Re: Printer notification every day at midnight

Till, could you have a look to that? It has been mentioned on bug
#1882462 as well, from the log there

'Jun 12 00:00:01 hero systemd[1]: Starting Rotate log files...
Jun 12 00:00:01 hero systemd[1]: Starting Daily man-db regeneration...
Jun 12 00:00:01 hero systemd[1]: Stopping Make remote CUPS printers available 
locally...
Jun 12 00:00:01 hero systemd[1]: cups-browsed.service: Succeeded.
Jun 12 00:00:01 hero systemd[1]: Stopped Make remote CUPS printers available 
locally.
Jun 12 00:00:01 hero systemd[1]: Stopping CUPS Scheduler...
Jun 12 00:00:01 hero systemd[1]: cups.service: Succeeded.
Jun 12 00:00:01 hero systemd[1]: Stopped CUPS Scheduler.
Jun 12 00:00:01 hero systemd[1]: cups.path: Succeeded.
...
'

Could you try to see why cups services restart there? Does it has to do
with the log rotation?

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

** Changed in: cups (Ubuntu)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  Triaged

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1883412] Re: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve

2020-06-16 Thread Dan Streetman

Generally, ifupdown is no longer recommended (or supported).  It's
recommended to move to netplan, or at least to directly configuring
networkd or network-manager.

For your specific issue, it's been a while since I looked at ifupdown, but from 
an old bug comment:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628552/comments/9

I think ifupdown static configuration of dns does not work with systemd-
resolved; you must have resolvconf installed for that to work (since
resolvconf installs the ifupdown hook, while resolved ignores ifupdown
completely).  Maybe your system upgrade removed the resolvconf package?


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

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

Title:
  20.04: DNS servers from /etc/network/interfaces not honored by
  systemd-resolve

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I have a server that uses /etc/network/interfaces to configure static
  IP info, including DNS, via /etc/network/interfaces. This worked fine
  in 16.04 and 18.04. However, when I updated to 20.04 this no longer
  works; I have to run "systemd-resolve --set-dns=192.168.63.1
  --interface=enp3s0" to fix it after every boot.

  My /etc/network/interfaces is:

  
  # Loopback
  auto lo
  iface lo inet loopback

  # enp3s0: LAN (Motherboard)
  auto enp3s0
  iface enp3s0 inet static
  address 192.168.63.2
  netmask 255.255.255.0
  network 192.168.63.0
  broadcast 192.168.63.255
  gateway 192.168.63.1
  dns-nameservers 192.168.63.1

  iface enp3s0 inet6 static
  address 2001:470:bb52:63::2/64
  netmask 64

  # WiFi USB
  # FIXME: Probably will get renamed on boot
  #allow-hotplug ethFlashAirWifi
  #iface ethFlashAirWifi inet manual
  

  "systemd-resolve --status" outputs the following beforr I run the WAR
  command given above:

  
  Global
 LLMNR setting: no  
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  
DNSSEC NTA: 10.in-addr.arpa 
16.172.in-addr.arpa 
168.192.in-addr.arpa
17.172.in-addr.arpa 
18.172.in-addr.arpa 
19.172.in-addr.arpa 
20.172.in-addr.arpa 
21.172.in-addr.arpa 
22.172.in-addr.arpa 
23.172.in-addr.arpa 
24.172.in-addr.arpa 
25.172.in-addr.arpa 
26.172.in-addr.arpa 
27.172.in-addr.arpa 
28.172.in-addr.arpa 
29.172.in-addr.arpa 
30.172.in-addr.arpa 
31.172.in-addr.arpa 
corp
d.f.ip6.arpa
home
internal
intranet
lan 
local   
private 
test

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jun 14 01:58:10 2020
  InstallationDate: Installed on 2016-04-12 (1524 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic 
root=/dev/mapper/severn_vg2016-lv_root ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago)

[Touch-packages] [Bug 1883718] [NEW] zoom in/out problem

Public bug reported:

zoom in/out problem ,mouse scroll not work ,i seen all type of
application same problem like chromium,fireffox,files all software same
kind of problem ,please solve it .also send a video .

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-59-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 16 19:58:59 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F23
dmi.board.asset.tag: Default string
dmi.board.name: A320M-S2H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: A320M-S2H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
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 N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic resolution ubuntu

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

Title:
  zoom in/out problem

Status in xorg package in Ubuntu:
  New

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte

[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

2020-06-16 Thread Philippe

#6 Chris quote:
4. Go to "System" -> "Administration" -> "Users and Groups".
5. Change password from "Asked on logon" to "Not asked on logon".
6. Lock your machine.
7. Press "Switch User".
8. Observe no password is required to unlock as the current user.

I confirm this issue on Ubuntu Mate 20.04.0 in a virtual machine. I can
reproduce it each times.

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

Title:
  Lock screen can be bypassed when auto-login is enabled.

Status in Ubuntu MATE:
  Confirmed
Status in lightdm package in Ubuntu:
  Fix Committed
Status in mate-session-manager package in Ubuntu:
  Confirmed

Bug description:
  16.04 LTS
  =

  Hi,

  My machine is set up with full-disk encryption, so it requires a
  password when I boot it up. Because of this I thought I would enable
  auto-login to avoid having to enter two passwords at boot.

  When I leave my computer for short periods of time, I lock it. I
  thought this was working fine for a long time, but I've discovered the
  lock screen is actually easily bypassable when auto-login is enabled.
  All one has to do is click "Switch User" on the lock screen, then
  press "Unlock" and the computer unlocks without prompting for a
  password.

  Perhaps this is just me being an idiot, but I thought this was secure
  until now. It seems like either unlocking should always require a
  password (otherwise what's the point of locking in the first place) or
  it should be made totally obvious that unlocking doesn't actually
  require a password (i.e. removing the password box from the lock
  screen when auto-login is enabled).

  Thanks,
  Chris

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

-- 
Mailing list: https://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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

@Daniel: The regression caused by the mutter MR I mentioned in comment
#21 is bad for ibus-hangul users (Korean input). Any chance you can take
a look at it?

Besides fixing that ibus-hangul issue, doing so would make it possible
to stop setting GTK_IM_MODULE=ibus on GNOME desktops, which is something
I believe would be desirable for other reasons but this bug.

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Tagging rls-gg-notfixing after having it discussed in our meeting, while
it's a bug and should be fixed it only has one report and it's mostly a
cosmectic problem so we don't believe it deserves special tracking

Do you have a special ibus configuration?

Could you try if it happens with a new user account on the same machine?

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1876693] Re: [SRU] New stable release 1.64.1

2020-06-16 Thread Iain Lane

Retried those tests, they are green now. Also tested per the description
and it was good.

** 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 gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/1876693

Title:
  [SRU] New stable release 1.64.1

Status in gobject-introspection package in Ubuntu:
  Fix Released
Status in gobject-introspection source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of gobject-
  introspection.

  Changes:

  1.64.1 - 2020-04-05
  ---

  * Replace calls to deprecated xml.etree.cElementTree removed in Python 3.9 
:mr:`202` (:user:`Stephen Gallagher `)
  * gimarshallingtests: Use g_assert_cmpfloat_with_epsilon. Fixes tests on some 
architectures :mr:`200` (:user:`Iain Lane `)

  [ QA ]

  GNOME has a micro release exception that covers this package.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  So we don't need to verify the fixes explicitly.

  Do this:

- Install the update, smoke test some of the reverse depends (apt rdepends 
libgirepository-1.0-1 and more importantly the indirect rdepends via python3-gi)
- Run "reverse-depends -b src:gobject-introspection" and test rebuild a few 
of them

  [ Regression potential ]

  g-i being broken will break pretty much the whole desktop, but you'd
  know that quite fast.

  The .py changes, if they're wrong or bad, could break the build of r
  -build-deps.

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

-- 
Mailing list: https://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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

** Changed in: rtkit (Ubuntu Focal)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-riscv package in Ubuntu:
  Invalid
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-kvm source package in Focal:
  Fix Released
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-riscv source package in Focal:
  Fix Released
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

  Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
  lowlatency kernel since we expected most RT users to use that kernel.
  However we are getting RT regressions with the generic kernel. Digging
  deeper into this option, it seems to be pretty specialized and to
  require quite a bit of workload-specific configuration/tuning to be
  useful, so it doesn't really seem to make sense for a general-purpose
  kernel.

  Fix: Turn this option back off.

  Test Case: See comment #4.

  Regression Potential: This was turned on to support some docker
  functionality, so this functionality will no longer be available.
  We've had this option off for all releases prior to focal, so this
  seems acceptable.

  ---

  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

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

-- 
Mailing list: https://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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

** Tags removed: rls-gg-incoming
** Tags added: rls-gg-notfixing

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1883690] Re: ubuntu-bug - where and how?

2020-06-16 Thread Olaf Zaplinski

apport is not installed, I just installed id. Looks like it is not part
of a default server installation. I will try it in the next bug found.
Thank you!

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

Title:
  ubuntu-bug - where and how?

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  # cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04.4 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.4 LTS"

  
  The manual says, I shall use ubuntu-bug to report a bug, but:

  # ubuntu-bug
  -bash: ubuntu-bug: command not found

  # apt install ubuntu-bug
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  E: Unable to locate package ubuntu-bug

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

-- 
Mailing list: https://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 1883688] Re: ntp not starting at boot

2020-06-16 Thread Olaf Zaplinski

I had no idea that ntp is depreceated.

** Changed in: ntp (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  ntp not starting at boot

Status in ntp package in Ubuntu:
  Invalid

Bug description:
  # cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04.4 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.4 LTS"

  Package: ntp
  Status: install ok installed
  Priority: optional
  Section: net
  Installed-Size: 1906
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 1:4.2.8p10+dfsg-5ubuntu7.1

  I noticed that ntpd is not running when I log in the first time after
  booting. Starting it manually works just fine.

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

-- 
Mailing list: https://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 1870260] Re: initramfs unpacking failed: Decoding failed", message appears on boot up.

2020-06-16 Thread cpg100

"If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to 
COMPRESS=gzip
then the error is fixing."

Just changed it on a fresh install of 20.04 and the problem is still
happening.

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  OS : Ubuntu 20.04(20200401)

  Problem: "initramfs unpacking failed: Decoding failed", message
  appears on boot up

  solution: 
If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to 
COMPRESS=gzip 
  then the error is fixing .

  Expected solution:
  This but in there from a long time I have seen this from 
Ubuntu 18.04,19.04,19.10
  now in 20.04 So please fix it or change it from lz4 to gzip.
  an early reply is highly appreciated 
  Thank you .
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tamal  1451 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD 
Camera
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15-da0xxx
  Package: ubuntu-meta
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=29f895bf-ab7b-4df8-8e9a-c277376a2685 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84A6
  dmi.board.vendor: HP
  dmi.board.version: 80.43
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd11/29/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-da0xxx
  dmi.product.sku: 5AY34PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Interesting. That speaks for two possible ways to fix the issue:

1. Fix it in the IBus source somehow.

2. Stop setting GTK_IM_MODULE also on Xorg (we already don't set it on Wayland)
   in case of a GNOME desktop, which would be a change to the im-config package.

Doing 2. may come with other issues for IM users, though. GNOME's
integration of IBus may not be mature enough to rely on it 100%. The
regression caused by
 is one
example of the latter.

So the issue is a bit complex. Adding the rls-gg-incoming tag to call
the desktop team's attention to it.

** Tags added: rls-gg-incoming

** Also affects: im-config (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1883670] Re: Disable IEC958 on HP Thunderbolt Dock

2020-06-16 Thread Ubuntu Foundations Team Bug Bot

The attachment "alsa-lib_1.2.2-2.3.debdiff" 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 alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1883670

Title:
  Disable IEC958 on HP Thunderbolt Dock

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  New
Status in alsa-lib source package in Focal:
  New
Status in alsa-lib source package in Groovy:
  New

Bug description:
  [Impact]
  On HP Thunderbolt Dock, unusable SPDIF can be selected as output from 
PulseAudio.

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

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

  [Regression Potential]
  Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected.

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

-- 
Mailing list: https://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 1882034] Re: cannot start X session with NIS account

the issue seems to be a systemd on

 (EE) systemd-logind: failed to get session: PID 4335 does not belong to
any known session

** Package changed: gdm3 (Ubuntu) => systemd (Ubuntu)

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

Title:
  cannot start X session with NIS account

Status in systemd package in Ubuntu:
  New

Bug description:
  When login with a NIS account, X does not start, or more precisely it
  starts and exits immediately.

  Only errors in logs is:
   (EE) systemd-logind: failed to get session: PID 4335 does not belong to any 
known session

  X11/gdm login works fine with local accounts.

  SSH/terminal console login with NIS accounts works fine.

  /etc/X11/Xwrapper.config:
allowed_users=anybody

  I've seen several reports of such problems under other versions (eg
  19.10), but no working solutions was found. It seems that the problem
  is the same with lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  4 08:59:25 2020
  InstallationDate: Installed on 2019-11-26 (190 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)

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

-- 
Mailing list: https://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 1883688] Re: ntp not starting at boot

2020-06-16 Thread Jouni Mettala

According to https://ubuntu.com/server/docs/network-ntp
Since Ubuntu 16.04 timedatectl / timesyncd (which are part of systemd) replace 
most of ntpdate / ntp.

Please set this bug to invalid or describe why this is a bug for you.

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

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

Title:
  ntp not starting at boot

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  # cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04.4 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.4 LTS"

  Package: ntp
  Status: install ok installed
  Priority: optional
  Section: net
  Installed-Size: 1906
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 1:4.2.8p10+dfsg-5ubuntu7.1

  I noticed that ntpd is not running when I log in the first time after
  booting. Starting it manually works just fine.

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

-- 
Mailing list: https://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 1882034] [NEW] cannot start X session with NIS account

You have been subscribed to a public bug:

When login with a NIS account, X does not start, or more precisely it
starts and exits immediately.

Only errors in logs is:
 (EE) systemd-logind: failed to get session: PID 4335 does not belong to any 
known session

X11/gdm login works fine with local accounts.

SSH/terminal console login with NIS accounts works fine.

/etc/X11/Xwrapper.config:
  allowed_users=anybody

I've seen several reports of such problems under other versions (eg
19.10), but no working solutions was found. It seems that the problem is
the same with lightdm.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun  4 08:59:25 2020
InstallationDate: Installed on 2019-11-26 (190 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)

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


** Tags: amd64 apport-bug focal
-- 
cannot start X session with NIS account
https://bugs.launchpad.net/bugs/1882034
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1883690] Re: ubuntu-bug - where and how?

2020-06-16 Thread Paul White

Further to the above, does apport-bug work?

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

Title:
  ubuntu-bug - where and how?

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  # cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04.4 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.4 LTS"

  
  The manual says, I shall use ubuntu-bug to report a bug, but:

  # ubuntu-bug
  -bash: ubuntu-bug: command not found

  # apt install ubuntu-bug
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  E: Unable to locate package ubuntu-bug

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

-- 
Mailing list: https://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 1883690] Re: ubuntu-bug - where and how?

2020-06-16 Thread Paul White

ubuntu-bug is a symlink to apport-bug which is part of the apport
package. The package and hence both commands should be installed by
default. Do you have the apport package installed?

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

** Tags added: bionic

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

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

Title:
  ubuntu-bug - where and how?

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  # cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04.4 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.4 LTS"

  
  The manual says, I shall use ubuntu-bug to report a bug, but:

  # ubuntu-bug
  -bash: ubuntu-bug: command not found

  # apt install ubuntu-bug
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  E: Unable to locate package ubuntu-bug

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

-- 
Mailing list: https://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 1850804] Re: Tab completion warnings with ubuntu-bug

2020-06-16 Thread Maksim S

ubuntu-bug actually greps output of ls
I have an alias for ls: ls -la
I can see output like this:
grep: /usr/share/apport/symptoms/-rw-r--r--: No such file or directory
grep: /usr/share/apport/symptoms/1: No such file or directory
grep: /usr/share/apport/symptoms/root: No such file or directory
grep: /usr/share/apport/symptoms/root: No such file or directory

I may be wrong but I think at the very least ubuntu-bug should call /usr/bin/ls 
and not just ls
Depending on user preferences, ubuntu-bug may even execute random software!

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

Title:
  Tab completion warnings with ubuntu-bug

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When running ubuntu-bug on the command line, and tab completing the
  package name, the following warnings are printed:

  /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
  grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:54:43 2019
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

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

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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-06-16 Thread Arnold

Same thing here. In my case, the computer keeps booting into emergency mode, 
with output like in #5, and some additional ACPI errors.
I changed COMPRESS to gzip as described in #47, but not back to lz4.
Now the computer keeps booting into emergency mode with the message "/dev/sda2 
clean" (which is my root partition). No more ACPI errors are reported.
However, in emergency mode, I need to do "mount -a" each time and then "exit", 
otherwise it will return to emergency mode after FS check. The booting is quite 
slow, though.

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

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

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

  ---

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

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

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

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

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

[Touch-packages] [Bug 1883690] [NEW] ubuntu-bug - where and how?

You have been subscribed to a public bug:

# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.4 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.4 LTS"


The manual says, I shall use ubuntu-bug to report a bug, but:

# ubuntu-bug
-bash: ubuntu-bug: command not found

# apt install ubuntu-bug
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ubuntu-bug

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

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

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

[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug

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

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

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

Title:
  Tab completion warnings with ubuntu-bug

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When running ubuntu-bug on the command line, and tab completing the
  package name, the following warnings are printed:

  /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
  grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:54:43 2019
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

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

-- 
Mailing list: https://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 1883534] Re: Screen flickering

2020-06-16 Thread Jeremy Lapierre

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

Dear Mr Daniel Van Vugt,

Choosing 'ubuntu on Wayland' in logging screen fixed the flickerings,
thanks a lot !

Best,
Jeremy

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

Title:
  Screen flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  To whom it may concern,

  As stated I have screen flickerings (see lightning like flickering on photo 
attached for portrait screen, for horizontal screen I also have screen 
flickering on the upper part but hard to catch in a photo) on freshly installed 
Ubuntu 20.04 LTS.
  I have tried this:

  https://askubuntu.com/questions/1231441/ubuntu-screen-flickering

  and this:

  https://learnubuntumate.weebly.com/screen-tearing-on-intel-
  graphics.html

  without success. I have also seen some other people mentioning screen
  flickering on ubuntu 20.04 here:

  
https://www.reddit.com/r/Ubuntu/comments/fvk536/anyone_else_noticing_window_flickering_on_ubuntu/

  without solution.

  I also know that it is very unlikely hardware problem because my screens were 
displaying well on archlinux. I think my graphic card info are already included 
in the report but just in case: Intel Corporation UHD Graphics 630. Might be 
intel driver problems ?
  Could you help me on this please ?

  Best regards,
  Jeremy

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 15:05:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694]
  InstallationDate: Installed on 2020-06-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046a:0023 Cherry GmbH Keyboard
   Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 9: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 9: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 10: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=81cee77a-b529-4dac-9834-dc6d5ab2dc16 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0615
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0615:bd04/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1883694] [NEW] [SRU] New upstream release 2.64.3

2020-06-16 Thread Iain Lane

Public bug reported:

[ Description ]

Take this new upstrem stable release.

+glib2.0 (2.64.3-1~ubuntu20.04.1) UNRELEASED; urgency=medium
+
+  * No-change backport from unstable / groovy to focal.
+
+ -- Iain Lane   Tue, 16 Jun 2020 11:53:34 +0100
+
+glib2.0 (2.64.3-1) unstable; urgency=medium
+
+  * Team upload
+
+  [ Laurent Bigonville ]
+  * Drop the libgio-fam package, and install the fam GIO plugin in
+libglib2.0-0 on Hurd ports. See: #885011 (Closes: #875915)
+  * Stop building the libgio-fam package on kFreeBSD ports.
+It is no longer necessary now that gkqueuefilemonitor is available.
+
+  [ Simon McVittie ]
+  * Clarify changelog entry regarding Hurd and kFreeBSD
+  * New upstream stable release
+
+ -- Simon McVittie   Fri, 29 May 2020 20:24:33 +0100

The gio-fam related changes do not affect Ubuntu, as they are for
hurd/kfreebsd only.

Upstream NEWS diff:

* Stability improvements for various unit tests

* Bugs fixed:
 - #1954 gdbus-server-auth intermittent failure
 - #2094 Deprecation warnings when compiling with 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_28 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_28
 - !1470 Backport !1440 -Wformat-nonliteral fixes to glib-2-64
 - !1471 Backport !1448 memory monitor test dependency fixes to glib-2-64
 - !1473 CI: Switch to new Windows runners (2.64)
 - !1478 Backport !1477 D-Bus keyring handling fixes to glib-2-64
 - !1483 Backport !1481 “array: fix corrupt state of GPtrArray after 
g_ptr_array_extend_and_steal()” to glib-2-64
 - !1484 Backport !1480 “CI: Make sure we use meson 0.49.2 in MSYS2” to 
glib-2-64
 - !1486 Backport !1472 “gthread: ignore deprecated declarations in static 
inline functions” to glib-2-64
 - !1495 Backport !1493 “meson: Remove stray ], in O_DIRECTORY check” to 
glib-2-64
 - !1501 Backport !1439 “Fix stpcpy() detection“ to glib-2-64

* Translation updates:
 - Chinese (Taiwan)
 - German

[ QA ]

Upstream release, so QA already performed by maintainers

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

This upload will trigger many autopkgtests that we expect to not be
regressed by this upload.

[ Regression potential ]

Various fixes in multiple places so multiple apps could be affected.
Pretty much all parts of GNOME use GLib, so test anything in the desktop
that you can.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: Fix Released

** Affects: glib2.0 (Ubuntu Focal)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

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

** Changed in: glib2.0 (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

** Also affects: glib2.0 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Focal)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  [SRU] New upstream release 2.64.3

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  In Progress

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  +glib2.0 (2.64.3-1~ubuntu20.04.1) UNRELEASED; urgency=medium
  +
  +  * No-change backport from unstable / groovy to focal.
  +
  + -- Iain Lane   Tue, 16 Jun 2020 11:53:34 +0100
  +
  +glib2.0 (2.64.3-1) unstable; urgency=medium
  +
  +  * Team upload
  +
  +  [ Laurent Bigonville ]
  +  * Drop the libgio-fam package, and install the fam GIO plugin in
  +libglib2.0-0 on Hurd ports. See: #885011 (Closes: #875915)
  +  * Stop building the libgio-fam package on kFreeBSD ports.
  +It is no longer necessary now that gkqueuefilemonitor is available.
  +
  +  [ Simon McVittie ]
  +  * Clarify changelog entry regarding Hurd and kFreeBSD
  +  * New upstream stable release
  +
  + -- Simon McVittie   Fri, 29 May 2020 20:24:33 +0100

  The gio-fam related changes do not affect Ubuntu, as they are for
  hurd/kfreebsd only.

  Upstream NEWS diff:

  * Stability improvements for various unit tests

  * Bugs fixed:
   - #1954 gdbus-server-auth intermittent failure
   - #2094 Deprecation warnings when compiling with 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_28 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_28
   - !1470 Backport !1440 -Wformat-nonliteral fixes to glib-2-64
   - !1471 Backport !1448 memory monitor test dependency fixes to glib-2-64
   - !1473 CI: Switch to new Windows runners (2.64)
   - !1478 Backport !1477 D-Bus keyring handling fixes to glib-2-64
   - !1483 Backport !1481 “array: fix corrupt state of GPtrArray after 
g_ptr_array_extend_and_steal()” to glib-2-64
   - !1484 Backport !1480 “CI: Make sure we use meson 0.49.2 in MSYS2” to 
glib-2-64
   - !1486 Backport !1472 “gthread: ignore deprecated declarations

[Touch-packages] [Bug 1883688] [NEW] ntp not starting at boot

2020-06-16 Thread Olaf Zaplinski

Public bug reported:

# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.4 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.4 LTS"

Package: ntp
Status: install ok installed
Priority: optional
Section: net
Installed-Size: 1906
Maintainer: Ubuntu Developers 
Architecture: amd64
Version: 1:4.2.8p10+dfsg-5ubuntu7.1

I noticed that ntpd is not running when I log in the first time after
booting. Starting it manually works just fine.

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

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

Title:
  ntp not starting at boot

Status in ntp package in Ubuntu:
  New

Bug description:
  # cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04.4 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.4 LTS"

  Package: ntp
  Status: install ok installed
  Priority: optional
  Section: net
  Installed-Size: 1906
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 1:4.2.8p10+dfsg-5ubuntu7.1

  I noticed that ntpd is not running when I log in the first time after
  booting. Starting it manually works just fine.

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

-- 
Mailing list: https://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 1883670] Re: Disable IEC958 on HP Thunderbolt Dock

2020-06-16 Thread Kai-Heng Feng

debdiff for Focal

** Patch added: "alsa-lib_1.2.2-2.1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1883670/+attachment/5384335/+files/alsa-lib_1.2.2-2.1ubuntu1.debdiff

** Tags added: oem-priority originate-from-1880102 stella

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

Title:
  Disable IEC958 on HP Thunderbolt Dock

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  New
Status in alsa-lib source package in Focal:
  New
Status in alsa-lib source package in Groovy:
  New

Bug description:
  [Impact]
  On HP Thunderbolt Dock, unusable SPDIF can be selected as output from 
PulseAudio.

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

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

  [Regression Potential]
  Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected.

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

-- 
Mailing list: https://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 1883670] Re: Disable IEC958 on HP Thunderbolt Dock

2020-06-16 Thread Kai-Heng Feng

debdiff for Groovy

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

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

** Patch added: "alsa-lib_1.2.2-2.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1883670/+attachment/5384334/+files/alsa-lib_1.2.2-2.3.debdiff

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

Title:
  Disable IEC958 on HP Thunderbolt Dock

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  New
Status in alsa-lib source package in Focal:
  New
Status in alsa-lib source package in Groovy:
  New

Bug description:
  [Impact]
  On HP Thunderbolt Dock, unusable SPDIF can be selected as output from 
PulseAudio.

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

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

  [Regression Potential]
  Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected.

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

-- 
Mailing list: https://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 1883673] Re: no sound after resume

2020-06-16 Thread Paul White

Reverting to "New" awaiting confirmation by another "affected" user.

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

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

Title:
  no sound after resume

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi!

  After a suspend/resume cycle with HDMI plugged in, it seems that
  pulseaudio doesn't recognize anymore the internal analog device
  (speakers/headphones) and I hear no sound. Before suspend I see two
  audio sinks through "pacmd list-sinks" (internal analog and HDMI), and
  after resume I only get HDMI audio. Still, audio only ever comes out
  of the internal device.

  A "killall pulseaudio" solves this for me (i.e., I get audio from the
  internal device).

  This looks a bit similar to the old bug #202089, but I don't know if
  it's the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  della  1195 F pulseaudio
   /dev/snd/controlC1:  della  1195 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 10:50:50 2020
  InstallationDate: Installed on 2020-03-12 (95 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-27 (50 days ago)
  dmi.bios.date: 09/19/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX505DD.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX505DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX505DD.308:bd09/19/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DD_TUF505DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming
  dmi.product.name: TUF Gaming FX505DD_TUF505DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://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 1883673] Re: no sound after resume

2020-06-16 Thread Matteo Dell'Amico

Outputs of pacmd list-sinks before and after suspend:

=== before
==

2 sink(s) available.
  * index: 0
name: 
driver: 
flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: IDLE
suspend cause: (none)
priority: 9030
volume: front-left: 52739 /  80% / -5,66 dB,   front-right: 52739 /  
80% / -5,66 dB
balance 0,00
base volume: 65536 / 100% / 0,00 dB
volume steps: 65537
muted: no
current latency: 301,48 ms
max request: 64 KiB
max rewind: 64 KiB
monitor source: 0
sample spec: s16le ch 2 44100 Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 0
configured latency: 371,52 ms; range is 0,50 .. 371,52 ms
card: 0 
module: 7
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "HDMI 0"
alsa.id = "HDMI 0"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "3"
alsa.card = "0"
alsa.card_name = "HDA NVidia"
alsa.long_card_name = "HDA NVidia at 0xf708 irq 73"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:01:00.1"
sysfs.path = 
"/devices/pci:00/:00:01.1/:01:00.1/sound/card0"
device.bus = "pci"
device.vendor.id = "10de"
device.vendor.name = "NVIDIA Corporation"
device.product.id = "0fb9"
device.product.name = "GP107GL High Definition Audio Controller"
device.string = "hdmi:0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "32768"
device.access_mode = "mmap+timer"
device.profile.name = "hdmi-stereo"
device.profile.description = "Digital Stereo (HDMI)"
device.description = "GP107GL High Definition Audio Controller 
Digital Stereo (HDMI)"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency 
offset 0 usec, available: yes)
properties:
device.icon_name = "video-display"
device.product.name = "U28E590
 "
active port: 
index: 1
name: 
driver: 
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
state: IDLE
suspend cause: (none)
priority: 9039
volume: front-left: 21819 /  33% / -28,66 dB,   front-right: 21819 /  
33% / -28,66 dB
balance 0,00
base volume: 65536 / 100% / 0,00 dB
volume steps: 65537
muted: no
current latency: 101,09 ms
max request: 17 KiB
max rewind: 17 KiB
monitor source: 1
sample spec: s16le ch 2 44100 Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 0
fixed latency: 100,14 ms
card: 1 
module: 8
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC233 Analog"
alsa.id = "ALC233 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "1"
alsa.card_name = "HD-Audio Generic"
alsa.long_card_name = "HD-Audio Generic at 0xf758 irq 75"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:05:00.6"
sysfs.path = 
"/devices/pci:00/:00:08.1/:05:00.6/sound/card1"
device.bus = "pci"
device.vendor.id = "1022"
device.vendor.name = "Advanced Micro Devices, Inc. [AMD]"
device.product.id = "15e3"
device.product.name = "Family 17h (Models 10h-1fh) HD Audio 
Controller"
device.string = "front:1"
device.buffering.buffer_size = "17664"
device.buffering.fragment_size = "2944"
device.access_mode = "mmap"
device.profile.name = "analog-stereo"
device.profile.description = "Stereo analogico"
device.description = "Family 17h (Models

[Touch-packages] [Bug 1883673] Re: no sound after resume

2020-06-16 Thread Balint Harmath

If this still affects you the Fix wasn't enough. Passed on to further
examination.

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

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

Title:
  no sound after resume

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After a suspend/resume cycle with HDMI plugged in, it seems that
  pulseaudio doesn't recognize anymore the internal analog device
  (speakers/headphones) and I hear no sound. Before suspend I see two
  audio sinks through "pacmd list-sinks" (internal analog and HDMI), and
  after resume I only get HDMI audio. Still, audio only ever comes out
  of the internal device.

  A "killall pulseaudio" solves this for me (i.e., I get audio from the
  internal device).

  This looks a bit similar to the old bug #202089, but I don't know if
  it's the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  della  1195 F pulseaudio
   /dev/snd/controlC1:  della  1195 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 10:50:50 2020
  InstallationDate: Installed on 2020-03-12 (95 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-27 (50 days ago)
  dmi.bios.date: 09/19/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX505DD.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX505DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX505DD.308:bd09/19/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DD_TUF505DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming
  dmi.product.name: TUF Gaming FX505DD_TUF505DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://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 1883673] [NEW] no sound after resume

2020-06-16 Thread Matteo Dell'Amico

Public bug reported:

Hi!

After a suspend/resume cycle with HDMI plugged in, it seems that
pulseaudio doesn't recognize anymore the internal analog device
(speakers/headphones) and I hear no sound. Before suspend I see two
audio sinks through "pacmd list-sinks" (internal analog and HDMI), and
after resume I only get HDMI audio. Still, audio only ever comes out of
the internal device.

A "killall pulseaudio" solves this for me (i.e., I get audio from the
internal device).

This looks a bit similar to the old bug #202089, but I don't know if
it's the same.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  della  1195 F pulseaudio
 /dev/snd/controlC1:  della  1195 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 16 10:50:50 2020
InstallationDate: Installed on 2020-03-12 (95 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to focal on 2020-04-27 (50 days ago)
dmi.bios.date: 09/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FX505DD.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX505DD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX505DD.308:bd09/19/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DD_TUF505DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: TUF Gaming
dmi.product.name: TUF Gaming FX505DD_TUF505DD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug focal

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

Title:
  no sound after resume

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After a suspend/resume cycle with HDMI plugged in, it seems that
  pulseaudio doesn't recognize anymore the internal analog device
  (speakers/headphones) and I hear no sound. Before suspend I see two
  audio sinks through "pacmd list-sinks" (internal analog and HDMI), and
  after resume I only get HDMI audio. Still, audio only ever comes out
  of the internal device.

  A "killall pulseaudio" solves this for me (i.e., I get audio from the
  internal device).

  This looks a bit similar to the old bug #202089, but I don't know if
  it's the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  della  1195 F pulseaudio
   /dev/snd/controlC1:  della  1195 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 10:50:50 2020
  InstallationDate: Installed on 2020-03-12 (95 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-27 (50 days ago)
  dmi.bios.date: 09/19/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX505DD.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX505DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX505DD.308:bd09/19/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DD_TUF505DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming
  dmi.product.name: TUF Gaming FX505DD_TUF505DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://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 1883670] [NEW] Disable IEC958 on HP Thunderbolt Dock

2020-06-16 Thread Kai-Heng Feng

Public bug reported:

[Impact]
On HP Thunderbolt Dock, unusable SPDIF can be selected as output from 
PulseAudio.

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

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

[Regression Potential]
Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected.

** Affects: alsa-lib (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Disable IEC958 on HP Thunderbolt Dock

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  [Impact]
  On HP Thunderbolt Dock, unusable SPDIF can be selected as output from 
PulseAudio.

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

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

  [Regression Potential]
  Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected.

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

-- 
Mailing list: https://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 1883668] [NEW] package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127

2020-06-16 Thread Siddharth Tumre

Public bug reported:

Unable to install packages.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-37-generic 5.4.0-37.41
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  siddharth   1331 F pulseaudio
 /dev/snd/pcmC0D0p:   siddharth   1331 F...m pulseaudio
CasperMD5CheckResult: skip
Date: Tue Jun 16 14:09:34 2020
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 127
InstallationDate: Installed on 2020-06-16 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. Vostro 5568
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=46acec17-85ed-475a-8256-f52656c9f9da ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26
SourcePackage: initramfs-tools
Title: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 127
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/04/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.0
dmi.board.name: 0DYWTM
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd12/04/2019:svnDellInc.:pnVostro5568:pvr:rvnDellInc.:rn0DYWTM:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 5568
dmi.product.sku: 0786
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package focal

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Unable to install packages.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-37-generic 5.4.0-37.41
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  siddharth   1331 F pulseaudio
   /dev/snd/pcmC0D0p:   siddharth   1331 F...m pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue Jun 16 14:09:34 2020
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 127
  InstallationDate: Installed on 2020-06-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Vostro 5568
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=46acec17-85ed-475a-8256-f52656c9f9da ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  SourcePackage: initramfs-tools
  Title: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0DYWTM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd12/04/2019:svnDellInc.:pnVostro5568:pvr:rvnDellInc.:rn0DYWTM:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5568
  dmi.product.sku: 0786
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1883665] Re: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

2020-06-16 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed
  lvm2 package post-installation script subprocess returned error exit
  status 1

Status in lvm2 package in Ubuntu:
  New

Bug description:
  I upgraded my system from 18.04 to 20.04, everything seemed to work fine for 
a day or two.  This morning I booted into a very old version of my desktop with 
most of my applications and files missing.  I found that LVM somehow 
failed/uninstalled, since my home partition is on LVM, it had the latter effect.
  Upon trying to install LVM, I got this error, however, LMV is running and I 
have my desktop and files back.  Just concerned that this might happen again.

  lvm2:
Installed: 2.03.07-1ubuntu1
Candidate: 2.03.07-1ubuntu1
Version table:
   *** 2.03.07-1ubuntu1 500
  500 http://za.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  AptOrdering:
   lvm2:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun 16 09:53:38 2020
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2015-10-26 (1695 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: lvm2
  Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-06-13 (3 days ago)

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

-- 
Mailing list: https://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 1883665] [NEW] package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

2020-06-16 Thread wistle

Public bug reported:

I upgraded my system from 18.04 to 20.04, everything seemed to work fine for a 
day or two.  This morning I booted into a very old version of my desktop with 
most of my applications and files missing.  I found that LVM somehow 
failed/uninstalled, since my home partition is on LVM, it had the latter effect.
Upon trying to install LVM, I got this error, however, LMV is running and I 
have my desktop and files back.  Just concerned that this might happen again.

lvm2:
  Installed: 2.03.07-1ubuntu1
  Candidate: 2.03.07-1ubuntu1
  Version table:
 *** 2.03.07-1ubuntu1 500
500 http://za.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lvm2 2.03.07-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
AptOrdering:
 lvm2:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jun 16 09:53:38 2020
ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2015-10-26 (1695 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: lvm2
Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-06-13 (3 days ago)

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


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed
  lvm2 package post-installation script subprocess returned error exit
  status 1

Status in lvm2 package in Ubuntu:
  New

Bug description:
  I upgraded my system from 18.04 to 20.04, everything seemed to work fine for 
a day or two.  This morning I booted into a very old version of my desktop with 
most of my applications and files missing.  I found that LVM somehow 
failed/uninstalled, since my home partition is on LVM, it had the latter effect.
  Upon trying to install LVM, I got this error, however, LMV is running and I 
have my desktop and files back.  Just concerned that this might happen again.

  lvm2:
Installed: 2.03.07-1ubuntu1
Candidate: 2.03.07-1ubuntu1
Version table:
   *** 2.03.07-1ubuntu1 500
  500 http://za.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  AptOrdering:
   lvm2:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun 16 09:53:38 2020
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2015-10-26 (1695 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: lvm2
  Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-06-13 (3 days ago)

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

-- 
Mailing list: https://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 1817955] Re: Getting new "DN is out of the realm subtree" error on adding principal

2020-06-16 Thread lincvz

Is the fix released in Trustu ESM repository ? I don't see it.

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

Title:
  Getting new "DN is out of the realm subtree" error on adding principal

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Trusty:
  Triaged

Bug description:
  Recently applied security update to 14.04.5 LTS kerberos (1.12+dfsg-
  2ubuntu5.4), and started getting errors when adding new principals to
  LDAP.

  Obfuscated example:

  kadmin.local -q "ank -x
  dn=\"uid=testuser,ou=People,dc=example,dc=com\" -pw \"dummypass\"
  testuser"

  now gives:
  Authenticating as principal root/ad...@test.example.com with password.
  NOTICE: no policy specified for testu...@test.example.com; assigning "default"
  add_principal: DN is out of the realm subtree while creating 
"testu...@test.example.com".

  
  This worked up through 1.12+dfsg-2ubuntu5.3, and I think it now fails due to 
changes in src/plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in response to 
CVE-2018-5729 or CVE-2018-5730.

  I'm going to attempt a downgrade to 1.12+dfsg-2ubuntu5.3 to check.

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

-- 
Mailing list: https://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 1881699] Re: No analog output