[Touch-packages] [Bug 1896251] Please test proposed package

[Steve Langasek]

Hello Mikko, or anyone else affected,

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

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

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

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

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

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

Title:
  rsync --delete-missing-args fails with "error: protocol
  incompatibility"

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Xenial:
  Won't Fix
Status in rsync source package in Bionic:
  Fix Committed
Status in rsync source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Rsync crashes when using --delete-missing-args on a file with a
  missing parent folder.

  Backporting this fix will allow users to delete missing source args
  when some files in the list have missing parent folders without
  interruption.

  This is fixed by patching in an upstream commit that allows files with
  missing parent folders to be handled without aborting.

  [Test Plan]

  # lxc launch images:ubuntu/focal builder
  # lxc exec builder bash
  # apt update
  # apt dist-upgrade
  # apt install -y rsync
  # mkdir -p a/1 b/1; echo "/1/2/3" > list
  # rsync --dry-run --stats -Pav --delete-missing-args --files-from=list a b

  * This should crash with exit code 2 after printing the following:

  building file list ...
   0 files...
  file has vanished: "/root/a/1/2"
  2 files to consider
  ABORTING due to invalid path from sender: 1/2/3
  rsync error: protocol incompatibility (code 2) at generator.c(1278) 
[generator=3.1.3]

  [Where problems could occur]

  Since the remove operation will now continue when files in the list
  have missing parent folders, other errors and warnings with different
  behaviors could arise instead.

  A warning that may arise the most often in these situations is the
  following:

  warning: some files vanished before they could be transferred (code
  24) at main.c(1207) [sender=3.1.3]

  This appears at the end of the above test case with the new code. The
  behavior is expected, but it may cause regressions due to changes in
  the output of certain use cases.

  [Original Description]

  Running

 rsync --delete-missing-args --files-from=...

  fails with error message like

  ABORTING due to invalid path from sender: dir1/dir2/dir3
  rsync error: protocol incompatibility (code 2) at generator.c(1271) 
[generator=3.1.2]

  if the listed directories are trying to delete full subtree of files.

  According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has
  been fixed in version 3.2.2.

  See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334

  Could you update the rsync package or backport the fix?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rsync 3.1.2-2.1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55
  Uname: Linux 5.4.0-47-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep 18 18:27:53 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-01-05 (621 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1896251] Re: rsync --delete-missing-args fails with "error: protocol incompatibility"

[Steve Langasek]

Hello Mikko, or anyone else affected,

Accepted rsync into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/rsync/3.1.3-8ubuntu0.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: rsync (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

** Tags added: verification-needed-bionic

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

Title:
  rsync --delete-missing-args fails with "error: protocol
  incompatibility"

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Xenial:
  Won't Fix
Status in rsync source package in Bionic:
  Fix Committed
Status in rsync source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Rsync crashes when using --delete-missing-args on a file with a
  missing parent folder.

  Backporting this fix will allow users to delete missing source args
  when some files in the list have missing parent folders without
  interruption.

  This is fixed by patching in an upstream commit that allows files with
  missing parent folders to be handled without aborting.

  [Test Plan]

  # lxc launch images:ubuntu/focal builder
  # lxc exec builder bash
  # apt update
  # apt dist-upgrade
  # apt install -y rsync
  # mkdir -p a/1 b/1; echo "/1/2/3" > list
  # rsync --dry-run --stats -Pav --delete-missing-args --files-from=list a b

  * This should crash with exit code 2 after printing the following:

  building file list ...
   0 files...
  file has vanished: "/root/a/1/2"
  2 files to consider
  ABORTING due to invalid path from sender: 1/2/3
  rsync error: protocol incompatibility (code 2) at generator.c(1278) 
[generator=3.1.3]

  [Where problems could occur]

  Since the remove operation will now continue when files in the list
  have missing parent folders, other errors and warnings with different
  behaviors could arise instead.

  A warning that may arise the most often in these situations is the
  following:

  warning: some files vanished before they could be transferred (code
  24) at main.c(1207) [sender=3.1.3]

  This appears at the end of the above test case with the new code. The
  behavior is expected, but it may cause regressions due to changes in
  the output of certain use cases.

  [Original Description]

  Running

 rsync --delete-missing-args --files-from=...

  fails with error message like

  ABORTING due to invalid path from sender: dir1/dir2/dir3
  rsync error: protocol incompatibility (code 2) at generator.c(1271) 
[generator=3.1.2]

  if the listed directories are trying to delete full subtree of files.

  According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has
  been fixed in version 3.2.2.

  See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334

  Could you update the rsync package or backport the fix?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rsync 3.1.2-2.1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55
  Uname: Linux 5.4.0-47-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep 18 18:27:53 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-01-05 (621 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

[Steve Langasek]

Hello Dimitri, or anyone else affected,

Accepted livecd-rootfs into hirsute-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.719.3 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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: livecd-rootfs (Ubuntu Hirsute)
   Status: New => Fix Committed

** Tags added: verification-needed-hirsute

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

Title:
  magic-proxy broke with iptables 1.8.7-1ubuntu2

Status in launchpad-buildd:
  Invalid
Status in iptables package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in iptables source package in Bionic:
  Invalid
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in lxd source package in Bionic:
  Invalid
Status in iptables source package in Focal:
  Invalid
Status in livecd-rootfs source package in Focal:
  Fix Committed
Status in lxd source package in Focal:
  Invalid
Status in iptables source package in Hirsute:
  Invalid
Status in livecd-rootfs source package in Hirsute:
  Fix Committed
Status in lxd source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  The fixes for this bug (including the fixes for LP:#1944906) need to be 
backported to hirsute, focal and bionic) to be able to re-enable  the 
"repo-snapshot-stamp" feature for image builds. That feature is important to 
get consistent image builds (means the same set of packages included in the 
different images) when doing multiple builds (eg. for AWS, Azure and GCE).

  [Test Plan]
  - build a livecd-rootfs image with the changes for every series in a PPA
  - Do build an image with the livecd-rootfs from the PPA and enable the 
repo-snapshot-stamp feature
  - Check that the build did not fail or hang

  [Where problems could occur]
  The codepath that will be changed is only executed in livecd-rootfs if the 
repo-snapshot-stamp feature is enabled. And that feature is currently broken so 
it shouldn't be enabled anywhere.

  [Original description]

  when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic
  proxy stopped working in livecd-rootfs.

  It does very simple thing:

  iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner
  daemon -j REDIRECT --to 8080

  inside hirsute lxd container, with quite high privileges, in a bionic
  VM, running 4.15 kernel.

  With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound
  connectivity the very first http networking command after the above
  call would just hang indefinitely.

  However, if one does this instead:

  iptables -vv -t nat -S
  iptables-legacy -vv -t nat -S
  iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon 
-j REDIRECT --to 8080

  somehow magically everything starts to work fine.

  weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+subscriptions


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

[Touch-packages] [Bug 1949970] Please test proposed package

[Steve Langasek]

Hello Dan, or anyone else affected,

Accepted lightdm into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.30.0-0ubuntu4~20.04.2 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.

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

Title:
  attempt to dlopen nonexistent pam_kwallet.so spams log

Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Bionic:
  New
Status in lightdm source package in Focal:
  Fix Committed
Status in lightdm source package in Hirsute:
  Fix Committed
Status in lightdm source package in Impish:
  Fix Committed
Status in lightdm source package in Jammy:
  New

Bug description:
  [impact]

  lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as
  well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet
  which died around Trusty (https://launchpad.net/ubuntu/+source/pam-
  kwallet) while pam_kwallet5.so comes from kwallet-pam which provides
  only the newer '5' version, not the older unversioned library file.

  This results in repeated spam error messages in the system log
  complaining about failure to load pam_kwallet.so

  [test case]

  install/enable lightdm and check system log at boot for messages like:

  Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so

  [regression potential]

  any regression would likely cause problems during login and/or missing
  or extra log messages during pam authentication.

  [scope]

  this is needed in all releases

  [other info]

  https://github.com/canonical/lightdm/pull/216

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


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

[Touch-packages] [Bug 1949970] Please test proposed package

[Steve Langasek]

Hello Dan, or anyone else affected,

Accepted lightdm into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/lightdm/1.30.0-0ubuntu4.21.04.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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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: lightdm (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  attempt to dlopen nonexistent pam_kwallet.so spams log

Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Bionic:
  New
Status in lightdm source package in Focal:
  Fix Committed
Status in lightdm source package in Hirsute:
  Fix Committed
Status in lightdm source package in Impish:
  Fix Committed
Status in lightdm source package in Jammy:
  New

Bug description:
  [impact]

  lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as
  well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet
  which died around Trusty (https://launchpad.net/ubuntu/+source/pam-
  kwallet) while pam_kwallet5.so comes from kwallet-pam which provides
  only the newer '5' version, not the older unversioned library file.

  This results in repeated spam error messages in the system log
  complaining about failure to load pam_kwallet.so

  [test case]

  install/enable lightdm and check system log at boot for messages like:

  Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so

  [regression potential]

  any regression would likely cause problems during login and/or missing
  or extra log messages during pam authentication.

  [scope]

  this is needed in all releases

  [other info]

  https://github.com/canonical/lightdm/pull/216

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


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

[Touch-packages] [Bug 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log

[Steve Langasek]

Hello Dan, or anyone else affected,

Accepted lightdm into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.30.0-0ubuntu4.21.10.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-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. 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: lightdm (Ubuntu Impish)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-impish

** Changed in: lightdm (Ubuntu Hirsute)
   Status: New => Fix Committed

** Tags added: verification-needed-hirsute

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

Title:
  attempt to dlopen nonexistent pam_kwallet.so spams log

Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Bionic:
  New
Status in lightdm source package in Focal:
  Fix Committed
Status in lightdm source package in Hirsute:
  Fix Committed
Status in lightdm source package in Impish:
  Fix Committed
Status in lightdm source package in Jammy:
  New

Bug description:
  [impact]

  lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as
  well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet
  which died around Trusty (https://launchpad.net/ubuntu/+source/pam-
  kwallet) while pam_kwallet5.so comes from kwallet-pam which provides
  only the newer '5' version, not the older unversioned library file.

  This results in repeated spam error messages in the system log
  complaining about failure to load pam_kwallet.so

  [test case]

  install/enable lightdm and check system log at boot for messages like:

  Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so

  [regression potential]

  any regression would likely cause problems during login and/or missing
  or extra log messages during pam authentication.

  [scope]

  this is needed in all releases

  [other info]

  https://github.com/canonical/lightdm/pull/216

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


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

[Touch-packages] [Bug 1939732] Re: report availability of Ubuntu Advantage ESM services on unattached machines

[Chad Smith]

** Changed in: software-properties (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  report availability of Ubuntu Advantage ESM services on unattached
  machines

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Committed
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Hirsute:
  Fix Committed
Status in software-properties source package in Impish:
  Fix Committed

Bug description:
  [Impact]

    * Error messages emitted to software-properties-gtk console "[Errno 2] No 
such file or directory: '/var/lib/ubuntu-advantage/status.json'" due to 
incorrect expectation that status.json file is written when non-root runs `ua 
status`
    * This logic results in multiple `ua status` calls which each result in a 
network-egress to https://contracts.canonical.com on unattached machines which 
could result in delays in rendering  the GTK dialogs while awaiting a response.

  [Test Case]
  1. Install latest version of software-properties-gtk from -proposed
  cat > setup_proposed.sh 

[Touch-packages] [Bug 1940860] Re: Mellanox NIC interface names change between 5.4 and 5.8

[Javier Diaz Jr]

This also affects the ubuntu-installer when the `d-i base-
installer/kernel/override-image  string linux-generic-hwe-20.04`
flag is added to preseed. The installer loads 5.4 kernel and configure
NICs using the 5.4 naming convention, then once the 5.11 kernel is
loaded and the host reboots the network config fails.

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

Title:
  Mellanox NIC interface names change between 5.4 and 5.8

Status in subiquity:
  New
Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I noticed on a couple of systems that my network interface names
  change when upgrading from the focal LTS (5.4) kernel to the focal HWE
  (both 5.8 & 5.11) kernels. Both systems have Mellanox Connect-X 5
  NICs.

  dannf@bizzy:~$ uname -a
  Linux bizzy 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:10:30 UTC 2021 
aarch64 aarch64 aarch64 GNU/Linux
  dannf@bizzy:~$ ls /sys/class/net
  enp1s0f0  enp1s0f1  enx3e8734bc294f  lo

  dannf@bizzy:~$ uname -a
  Linux bizzy 5.8.0-63-generic #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:44 UTC 
2021 aarch64 aarch64 aarch64 GNU/Linux
  dannf@bizzy:~$ ls /sys/class/net
  enp1s0f0np0  enp1s0f1np1  enx3e8734bc294f  lo

  dannf@bizzy:~$ uname -a
  Linux bizzy 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 15:58:08 UTC 
2021 aarch64 aarch64 aarch64 GNU/Linux
  dannf@bizzy:~$ ls /sys/class/net
  enp1s0f0np0  enp1s0f1np1  enx3e8734bc294f  lo

  I bisected this down to a kernel change:
  # first bad commit: [c6acd629eec754a9679f922d51f90e44c769b80c] net/mlx5e: Add 
support for devlink-port in non-representors mode

  The impact is that your network can fail to come up after
  transitioning from the LTS kernel to the HWE kernel. Now, this isn't a
  huge problem for MAAS installs because MAAS configures netplan to
  always use the same names as were used at commissioning. It does
  impact subiquity based installs however, which do not.

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


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

[Touch-packages] [Bug 1915910] Re: evince does not print

[Rolf Leggewie]

** Tags added: apparmor hirsute

** Summary changed:

- evince does not print
+ evince does not print (apparmor, pxgsettings)

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

Title:
  evince does not print (apparmor, pxgsettings)

Status in evince package in Ubuntu:
  Confirmed
Status in libproxy package in Ubuntu:
  Confirmed

Bug description:
  audit: type=1400 audit(1613557537.646:81): apparmor="DENIED"
  operation="exec" profile="/usr/bin/evince"
  name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500
  comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  It seems that evince has no rights to print if I understand this
  correctly

  Printing the same pdf-file from the same origin/folder works with
  OCULAR

  The error is reproduceable

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


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

[Touch-packages] [Bug 1949266] Re: package openssh-server 1:8.2p1-4ubuntu0.3 failed to install/upgrade: 已安装 openssh-server 软件包 post-installation 脚本 子进程返回错误状态 1

[Robie Basak]

Thank you for your report.

This looks like a local configuration problem, rather than a bug in
Ubuntu. Specifically it looks like you have manually deleted parts of
your openssh installation, so therefore this package can be expected to
be broken.

You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Since we use this bug tracker to track bugs in Ubuntu, rather than 
configuration problems, I'm marking this bug as Invalid. This helps us to focus 
on fixing bugs in Ubuntu.
 
If you believe that this is really a bug, then you may find it helpful to read 
"How to report bugs effectively" 
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you 
would then provide a more complete description of the problem, explain why you 
believe this is a bug in Ubuntu rather than a problem specific to your system, 
and then change the bug status back to New. 


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

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

Title:
  package openssh-server 1:8.2p1-4ubuntu0.3 failed to install/upgrade:
  已安装 openssh-server 软件包 post-installation 脚本 子进程返回错误状态 1

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  rm -r ssh

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: openssh-server 1:8.2p1-4ubuntu0.3
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  AptOrdering:
   ncurses-term:amd64: Install
   openssh-sftp-server:amd64: Install
   openssh-server:amd64: Install
   ssh-import-id:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Oct 31 00:12:11 2021
  ErrorMessage: 已安装 openssh-server 软件包 post-installation 脚本 子进程返回错误状态 1
  InstallationDate: Installed on 2021-10-24 (6 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config: No such file or directory
  SourcePackage: openssh
  Title: package openssh-server 1:8.2p1-4ubuntu0.3 failed to install/upgrade: 
已安装 openssh-server 软件包 post-installation 脚本 子进程返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ssh.moduli: [deleted]

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


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

[Touch-packages] [Bug 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log

[Dan Streetman]

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

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

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

Title:
  attempt to dlopen nonexistent pam_kwallet.so spams log

Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Bionic:
  New
Status in lightdm source package in Focal:
  New
Status in lightdm source package in Hirsute:
  New
Status in lightdm source package in Impish:
  New
Status in lightdm source package in Jammy:
  New

Bug description:
  [impact]

  lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as
  well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet
  which died around Trusty (https://launchpad.net/ubuntu/+source/pam-
  kwallet) while pam_kwallet5.so comes from kwallet-pam which provides
  only the newer '5' version, not the older unversioned library file.

  This results in repeated spam error messages in the system log
  complaining about failure to load pam_kwallet.so

  [test case]

  install/enable lightdm and check system log at boot for messages like:

  Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so

  [regression potential]

  any regression would likely cause problems during login and/or missing
  or extra log messages during pam authentication.

  [scope]

  this is needed in all releases

  [other info]

  https://github.com/canonical/lightdm/pull/216

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


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

[Touch-packages] [Bug 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log

[Dan Streetman]

** Description changed:

  [impact]
  
  lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as
  well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet
  which died around Trusty (https://launchpad.net/ubuntu/+source/pam-
  kwallet) while pam_kwallet5.so comes from kwallet-pam which provides
  only the newer '5' version, not the older unversioned library file.
  
  This results in repeated spam error messages in the system log
  complaining about failure to load pam_kwallet.so
  
  [test case]
  
  install/enable lightdm and check system log at boot for messages like:
  
  Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so
  
  [regression potential]
  
  any regression would likely cause problems during login and/or missing
  or extra log messages during pam authentication.
  
  [scope]
  
  this is needed in all releases
+ 
+ [other info]
+ 
+ https://github.com/canonical/lightdm/pull/216

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

Title:
  attempt to dlopen nonexistent pam_kwallet.so spams log

Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Focal:
  New
Status in lightdm source package in Hirsute:
  New
Status in lightdm source package in Impish:
  New
Status in lightdm source package in Jammy:
  New

Bug description:
  [impact]

  lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as
  well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet
  which died around Trusty (https://launchpad.net/ubuntu/+source/pam-
  kwallet) while pam_kwallet5.so comes from kwallet-pam which provides
  only the newer '5' version, not the older unversioned library file.

  This results in repeated spam error messages in the system log
  complaining about failure to load pam_kwallet.so

  [test case]

  install/enable lightdm and check system log at boot for messages like:

  Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so

  [regression potential]

  any regression would likely cause problems during login and/or missing
  or extra log messages during pam authentication.

  [scope]

  this is needed in all releases

  [other info]

  https://github.com/canonical/lightdm/pull/216

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


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

[Touch-packages] [Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18

[Łukasz Zemczak]

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Lukas Märdian (slyon)

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

Title:
  systemd randomly fails to activate mount units in Ubuntu Core 18

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Jammy:
  New

Bug description:
  Since a month or so, we've been seeing random failures in our snapd
  spread tests where systemd could not start the mount unit associated
  with a snap because of a failed dependency.

  The issue is described in the comments to PR
  https://github.com/snapcore/snapd/pull/10935, but I'll summarize it
  here.

  When starting a snap, snapd creates a mount unit to mount the snap's
  squashfs (the template is
  
https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205).
  The snapd asks systemd to reload the configuration, and starts the
  mount unit.

  The failure we've observed is that sometimes systemd decides to stop
  our mount unit (search for "Unmounting Mount unit for test-snapd-svc-
  flip-flop" in the attached log), and then tries to reactivate it
  again, and at that point it fails.

  When I asked for help, Lukas pointed out that the latest update
  contains a patch that is related to reload handling and mount units:
  
http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz
  (the patch itself is better visible at
  
https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656).
  When looking at the systemd git log, though, I noticed another patch
  that was applied shortly after this one, which also seems related but
  was not backported:
  
https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0

  Since the stopping of our mount unit happens immediately after a
  systemd reload, it actually seems very likely that the inclusion of
  f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what
  causes our woes (though, indeed, the issue is not reliably
  reproducible, so we cannot be sure).

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


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

[Touch-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools

[Dan Watkins]

I would also like to see this change:

* ubuntu-advantage-tools and its dependencies add about 3MB to ubuntu-minimal 
installations (checked by installing ubuntu-minimal's Depends in a Docker 
container with and without u-a-t)
* it installs a systemd timer which runs (to do nothing, as the service it runs 
is disabled without ua-auto-attach.service present)
* it installs MOTD hooks, which run regularly
* it installs an apt hook, which is executed on every update and upgrade, and 
twice on installs

If one is not interested in UA services, these are wasted resources, and
provide an incentive to remove ubuntu-minimal from systems.

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

Title:
  ubuntu-minimal depends on ubuntu-advantage-tools

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  This is counter to #1566183 There is no reason to enforce desktop
  users who manage machine on their own to install ubuntu-advantage-
  tools, especially when this is 'minimal' version.  This should include
  only essential packages to make the OS functional

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-minimal 1.450.2
  ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106
  Uname: Linux 5.4.0-73-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun  4 18:54:56 2021
  InstallationDate: Installed on 2020-01-29 (491 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago)

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


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

[Touch-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  ubuntu-minimal depends on ubuntu-advantage-tools

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  This is counter to #1566183 There is no reason to enforce desktop
  users who manage machine on their own to install ubuntu-advantage-
  tools, especially when this is 'minimal' version.  This should include
  only essential packages to make the OS functional

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-minimal 1.450.2
  ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106
  Uname: Linux 5.4.0-73-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun  4 18:54:56 2021
  InstallationDate: Installed on 2020-01-29 (491 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago)

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


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

[Touch-packages] [Bug 1949970] [NEW] attempt to dlopen nonexistent pam_kwallet.so spams log

[Dan Streetman]

Public bug reported:

[impact]

lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as
well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet
which died around Trusty (https://launchpad.net/ubuntu/+source/pam-
kwallet) while pam_kwallet5.so comes from kwallet-pam which provides
only the newer '5' version, not the older unversioned library file.

This results in repeated spam error messages in the system log
complaining about failure to load pam_kwallet.so

[test case]

install/enable lightdm and check system log at boot for messages like:

Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so

[regression potential]

any regression would likely cause problems during login and/or missing
or extra log messages during pam authentication.

[scope]

this is needed in all releases

** Affects: lightdm (Ubuntu)
 Importance: Low
 Status: New

** Affects: lightdm (Ubuntu Focal)
 Importance: Low
 Status: New

** Affects: lightdm (Ubuntu Hirsute)
 Importance: Low
 Status: New

** Affects: lightdm (Ubuntu Impish)
 Importance: Low
 Status: New

** Affects: lightdm (Ubuntu Jammy)
 Importance: Low
 Status: New

** Also affects: lightdm (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Also affects: lightdm (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

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

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

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

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

Title:
  attempt to dlopen nonexistent pam_kwallet.so spams log

Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Focal:
  New
Status in lightdm source package in Hirsute:
  New
Status in lightdm source package in Impish:
  New
Status in lightdm source package in Jammy:
  New

Bug description:
  [impact]

  lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as
  well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet
  which died around Trusty (https://launchpad.net/ubuntu/+source/pam-
  kwallet) while pam_kwallet5.so comes from kwallet-pam which provides
  only the newer '5' version, not the older unversioned library file.

  This results in repeated spam error messages in the system log
  complaining about failure to load pam_kwallet.so

  [test case]

  install/enable lightdm and check system log at boot for messages like:

  Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so

  [regression potential]

  any regression would likely cause problems during login and/or missing
  or extra log messages during pam authentication.

  [scope]

  this is needed in all releases

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


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

[Touch-packages] [Bug 1946965] Autopkgtest regression report (python3-defaults/3.9.4-1ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted python3-defaults (3.9.4-1ubuntu1) for 
impish have finished running.
The following regressions have been reported in tests triggered by the package:

idseq-bench/0.0~git20200902.8241a9a-1 (ppc64el)
ganeti/3.0.1-2build1 (arm64, ppc64el, amd64)
python-limits/1.5.1-1 (armhf, ppc64el, s390x)
mailman3/3.3.3-1ubuntu1 (armhf)
initramfs-tools/0.140ubuntu6 (amd64)
lintian/2.104.0ubuntu3 (amd64)
ranger/1.9.3-3 (armhf)
limnoria/2021.07.21-2 (amd64)
python-azure-devtools/1.2.0-1 (armhf, arm64, ppc64el, amd64, s390x)
azure-functions-devops-build/0.0.22-5 (armhf, arm64, ppc64el, amd64, s390x)
assimp/5.0.1~ds0-2 (arm64)
reprotest/0.7.16 (amd64)
python-tenacity/6.3.1-1 (ppc64el)
smart-open/1.11.1-3 (armhf, arm64, ppc64el, amd64, s390x)
i3pystatus/3.35+git20191126.5a8eaf4-2 (armhf)
supysonic/0.6.2+ds-3 (armhf, amd64)
adsys/0.7.1 (arm64)
ubuntu-image/1.11+21.04ubuntu2 (amd64)
python-h2/4.0.0-3 (armhf, amd64)
python-transitions/0.8.6-1 (s390x)
ruby-pygments.rb/1.2.1-2 (amd64)
mercurial/5.6.1-4 (armhf, amd64)
python-fakeredis/1.4.5-4 (s390x)
netplan.io/0.103-0ubuntu7 (amd64)
r-cran-irkernel/1.1.1-1 (armhf)
booth/1.0-237-gdd88847-2 (ppc64el)
suricata-update/1.2.1-1 (armhf, arm64, amd64, ppc64el, s390x)
python-crontab/2.5.1-1 (ppc64el)
boost1.74/1.74.0-8ubuntu6 (arm64)
sagetex/3.5+ds-2 (armhf)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/impish/update_excuses.html#python3-defaults

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  python3-defaults: py3versions -i does not list python3.10 when it is
  installed

Status in python3-defaults package in Ubuntu:
  Fix Committed
Status in python3-defaults source package in Impish:
  Won't Fix

Bug description:
  Test case:

  $ sudo apt install python3.9 python3.10
  ...
  $ py3versions -i
  python3.9

  Expected output:

  $ py3versions -i
  python3.10 python3.9

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


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

[Touch-packages] [Bug 1946965] Re: python3-defaults: py3versions -i does not list python3.10 when it is installed

[Matthias Klose]

Removing packages from impish-proposed:
python3-defaults 3.9.4-1ubuntu1 in impish
2to3 3.9.4-1ubuntu1 in impish amd64
2to3 3.9.4-1ubuntu1 in impish arm64
2to3 3.9.4-1ubuntu1 in impish armhf
2to3 3.9.4-1ubuntu1 in impish i386
2to3 3.9.4-1ubuntu1 in impish ppc64el
2to3 3.9.4-1ubuntu1 in impish riscv64
2to3 3.9.4-1ubuntu1 in impish s390x
idle 3.9.4-1ubuntu1 in impish amd64
idle 3.9.4-1ubuntu1 in impish arm64
idle 3.9.4-1ubuntu1 in impish armhf
idle 3.9.4-1ubuntu1 in impish i386
idle 3.9.4-1ubuntu1 in impish ppc64el
idle 3.9.4-1ubuntu1 in impish riscv64
idle 3.9.4-1ubuntu1 in impish s390x
idle3 3.9.4-1ubuntu1 in impish amd64
idle3 3.9.4-1ubuntu1 in impish arm64
idle3 3.9.4-1ubuntu1 in impish armhf
idle3 3.9.4-1ubuntu1 in impish i386
idle3 3.9.4-1ubuntu1 in impish ppc64el
idle3 3.9.4-1ubuntu1 in impish riscv64
idle3 3.9.4-1ubuntu1 in impish s390x
libpython3-all-dbg 3.9.4-1ubuntu1 in impish amd64
libpython3-all-dbg 3.9.4-1ubuntu1 in impish arm64
libpython3-all-dbg 3.9.4-1ubuntu1 in impish armhf
libpython3-all-dbg 3.9.4-1ubuntu1 in impish i386
libpython3-all-dbg 3.9.4-1ubuntu1 in impish ppc64el
libpython3-all-dbg 3.9.4-1ubuntu1 in impish riscv64
libpython3-all-dbg 3.9.4-1ubuntu1 in impish s390x
libpython3-all-dev 3.9.4-1ubuntu1 in impish amd64
libpython3-all-dev 3.9.4-1ubuntu1 in impish arm64
libpython3-all-dev 3.9.4-1ubuntu1 in impish armhf
libpython3-all-dev 3.9.4-1ubuntu1 in impish i386
libpython3-all-dev 3.9.4-1ubuntu1 in impish ppc64el
libpython3-all-dev 3.9.4-1ubuntu1 in impish riscv64
libpython3-all-dev 3.9.4-1ubuntu1 in impish s390x
libpython3-dbg 3.9.4-1ubuntu1 in impish amd64
libpython3-dbg 3.9.4-1ubuntu1 in impish arm64
libpython3-dbg 3.9.4-1ubuntu1 in impish armhf
libpython3-dbg 3.9.4-1ubuntu1 in impish i386
libpython3-dbg 3.9.4-1ubuntu1 in impish ppc64el
libpython3-dbg 3.9.4-1ubuntu1 in impish riscv64
libpython3-dbg 3.9.4-1ubuntu1 in impish s390x
libpython3-dev 3.9.4-1ubuntu1 in impish amd64
libpython3-dev 3.9.4-1ubuntu1 in impish arm64
libpython3-dev 3.9.4-1ubuntu1 in impish armhf
libpython3-dev 3.9.4-1ubuntu1 in impish i386
libpython3-dev 3.9.4-1ubuntu1 in impish ppc64el
libpython3-dev 3.9.4-1ubuntu1 in impish riscv64
libpython3-dev 3.9.4-1ubuntu1 in impish s390x
libpython3-stdlib 3.9.4-1ubuntu1 in impish amd64
libpython3-stdlib 3.9.4-1ubuntu1 in impish arm64
libpython3-stdlib 3.9.4-1ubuntu1 in impish armhf
libpython3-stdlib 3.9.4-1ubuntu1 in impish i386
libpython3-stdlib 3.9.4-1ubuntu1 in impish ppc64el
libpython3-stdlib 3.9.4-1ubuntu1 in impish riscv64
libpython3-stdlib 3.9.4-1ubuntu1 in impish s390x
python3 3.9.4-1ubuntu1 in impish amd64
python3 3.9.4-1ubuntu1 in impish arm64
python3 3.9.4-1ubuntu1 in impish armhf
python3 3.9.4-1ubuntu1 in impish i386
python3 3.9.4-1ubuntu1 in impish ppc64el
python3 3.9.4-1ubuntu1 in impish riscv64
python3 3.9.4-1ubuntu1 in impish s390x
python3-all 3.9.4-1ubuntu1 in impish amd64
python3-all 3.9.4-1ubuntu1 in impish arm64
python3-all 3.9.4-1ubuntu1 in impish armhf
python3-all 3.9.4-1ubuntu1 in impish i386
python3-all 3.9.4-1ubuntu1 in impish ppc64el
python3-all 3.9.4-1ubuntu1 in impish riscv64
python3-all 3.9.4-1ubuntu1 in impish s390x
python3-all-dbg 3.9.4-1ubuntu1 in impish amd64
python3-all-dbg 3.9.4-1ubuntu1 in impish arm64
python3-all-dbg 3.9.4-1ubuntu1 in impish armhf
python3-all-dbg 3.9.4-1ubuntu1 in impish i386
python3-all-dbg 3.9.4-1ubuntu1 in impish ppc64el
python3-all-dbg 3.9.4-1ubuntu1 in impish riscv64
python3-all-dbg 3.9.4-1ubuntu1 in impish s390x
python3-all-dev 3.9.4-1ubuntu1 in impish amd64
python3-all-dev 3.9.4-1ubuntu1 in impish arm64
python3-all-dev 3.9.4-1ubuntu1 in impish armhf
python3-all-dev 3.9.4-1ubuntu1 in impish i386
python3-all-dev 

[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot

[Launchpad Bug Tracker]

This bug was fixed in the package ufw - 0.36.1-3

---
ufw (0.36.1-3) unstable; urgency=medium

  * debian/ufw.service (LP: #1726856, Closes: 990834):
- use Before and Wants on network-pre.target. Per systemd documentation,
  "network-pre.target is a target that may be used to order services
  before any network interface is configured. Its primary purpose is for
  usage with firewall services". Because network-pre.target is a passive
  unit, "services that want to be run before the network is configured
  should place Before=network-pre.target and also set
  Wants=network-pre.target to pull it in"
- remove DefaultDependencies=no so that we pull in default dependencies
  for "basic system initialization". While ufw is meant to come up before
  networking, there is no reason why it shouldn't come up after sysinit.
  This should help make ufw startup more robust on systems that need
  something from sysinit.

 -- Jamie Strandboge   Tue, 02 Nov 2021 13:27:42
+

** Changed in: ufw (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Invalid
Status in ufw package in Ubuntu:
  Fix Released
Status in ufw source package in Xenial:
  Invalid
Status in ufw source package in Bionic:
  Invalid
Status in ufw source package in Cosmic:
  Invalid
Status in ufw source package in Disco:
  Invalid

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

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


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

[Touch-packages] [Bug 1939732] Re: report availability of Ubuntu Advantage ESM services on unattached machines

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.99.15

---
software-properties (0.99.15) jammy; urgency=medium

  * utils: prefer /var/lib/ubuntu-advantage/status.json over ua status
- Handle absent /var/lib/ubuntu-advantage/status.json for non-root
  users (LP: #1939732)
- print unexcepted errors and if _schema_version not equal to 0.1

 -- Chad Smith   Fri, 29 Oct 2021 15:46:58
-0600

** Changed in: software-properties (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  report availability of Ubuntu Advantage ESM services on unattached
  machines

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Hirsute:
  Fix Committed
Status in software-properties source package in Impish:
  Fix Committed

Bug description:
  [Impact]

    * Error messages emitted to software-properties-gtk console "[Errno 2] No 
such file or directory: '/var/lib/ubuntu-advantage/status.json'" due to 
incorrect expectation that status.json file is written when non-root runs `ua 
status`
    * This logic results in multiple `ua status` calls which each result in a 
network-egress to https://contracts.canonical.com on unattached machines which 
could result in delays in rendering  the GTK dialogs while awaiting a response.

  [Test Case]
  1. Install latest version of software-properties-gtk from -proposed
  cat > setup_proposed.sh 

[Touch-packages] [Bug 1948806] Re: [SRU] Enable support for Yoga Cloud Archive

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.99.15

---
software-properties (0.99.15) jammy; urgency=medium

  * utils: prefer /var/lib/ubuntu-advantage/status.json over ua status
- Handle absent /var/lib/ubuntu-advantage/status.json for non-root
  users (LP: #1939732)
- print unexcepted errors and if _schema_version not equal to 0.1

 -- Chad Smith   Fri, 29 Oct 2021 15:46:58
-0600

** Changed in: software-properties (Ubuntu Jammy)
   Status: Triaged => Fix Released

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

Title:
  [SRU] Enable support for Yoga Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Jammy:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:yoga
 cloud-archive:yoga-proposed

  This will also need to be SRU'd back to focal.

  [Impact]
  End users have to manually enable the yoga cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:yoga
  sudo add-apt-repository cloud-archive:yoga-proposed

  [Regression potential]
  Limited - just a data item addition

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


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

[Touch-packages] [Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18

[Lukas Märdian]

Sounds like we cannot have an easy fix by simply applying
04eb582acc203eab0bc5c2cc5e13986f16e09df0 (and its dependencies).

So let's first try to pinpoint if f0831ed2a03fcef582660be1c3b1a9f3e267e656 
really introduced the regression. I've built a new core18 snap with my previous 
work and the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 (and 
dependencies) reverted:
https://people.ubuntu.com/~slyon/uc18/core18_20211105_amd64.snap

Could you please give this another try?

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

Title:
  systemd randomly fails to activate mount units in Ubuntu Core 18

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Jammy:
  New

Bug description:
  Since a month or so, we've been seeing random failures in our snapd
  spread tests where systemd could not start the mount unit associated
  with a snap because of a failed dependency.

  The issue is described in the comments to PR
  https://github.com/snapcore/snapd/pull/10935, but I'll summarize it
  here.

  When starting a snap, snapd creates a mount unit to mount the snap's
  squashfs (the template is
  
https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205).
  The snapd asks systemd to reload the configuration, and starts the
  mount unit.

  The failure we've observed is that sometimes systemd decides to stop
  our mount unit (search for "Unmounting Mount unit for test-snapd-svc-
  flip-flop" in the attached log), and then tries to reactivate it
  again, and at that point it fails.

  When I asked for help, Lukas pointed out that the latest update
  contains a patch that is related to reload handling and mount units:
  
http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz
  (the patch itself is better visible at
  
https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656).
  When looking at the systemd git log, though, I noticed another patch
  that was applied shortly after this one, which also seems related but
  was not backported:
  
https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0

  Since the stopping of our mount unit happens immediately after a
  systemd reload, it actually seems very likely that the inclusion of
  f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what
  causes our woes (though, indeed, the issue is not reliably
  reproducible, so we cannot be sure).

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


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

[Touch-packages] [Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18

[Lukas Märdian]

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

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

Title:
  systemd randomly fails to activate mount units in Ubuntu Core 18

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Jammy:
  New

Bug description:
  Since a month or so, we've been seeing random failures in our snapd
  spread tests where systemd could not start the mount unit associated
  with a snap because of a failed dependency.

  The issue is described in the comments to PR
  https://github.com/snapcore/snapd/pull/10935, but I'll summarize it
  here.

  When starting a snap, snapd creates a mount unit to mount the snap's
  squashfs (the template is
  
https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205).
  The snapd asks systemd to reload the configuration, and starts the
  mount unit.

  The failure we've observed is that sometimes systemd decides to stop
  our mount unit (search for "Unmounting Mount unit for test-snapd-svc-
  flip-flop" in the attached log), and then tries to reactivate it
  again, and at that point it fails.

  When I asked for help, Lukas pointed out that the latest update
  contains a patch that is related to reload handling and mount units:
  
http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz
  (the patch itself is better visible at
  
https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656).
  When looking at the systemd git log, though, I noticed another patch
  that was applied shortly after this one, which also seems related but
  was not backported:
  
https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0

  Since the stopping of our mount unit happens immediately after a
  systemd reload, it actually seems very likely that the inclusion of
  f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what
  causes our woes (though, indeed, the issue is not reliably
  reproducible, so we cannot be sure).

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


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

[Touch-packages] [Bug 1948476] Re: [SRU] Allow target units to fail

[Lukas Märdian]

Thank you Alfonso, I staged this patch for the next Focal SRU:
https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/commit/?h=ubuntu-
focal=fe0cb0bd66baea89d8bbe47cb47d88540f46d470

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

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

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

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

Title:
  [SRU] Allow target units to fail

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

Bug description:
  [Impact]

  A systemd regression in focal made it think that target units cannot
  fail, which produced warnings like:

  emergency.target: Requested dependency OnFailure=reboot.target ignored
  (target units cannot fail).

  So the OnFailure settings are ignored for targets (see
  https://github.com/snapcore/core-initrd/issues/33 for details).
  Upstream fixed the issue in v246:
  
https://github.com/systemd/systemd/commit/94d1ddbd7cd15b1073757eb5ae0645c83f0b414c

  [Test Plan]

  Test on a UC system and check that the above warnings are not shown
  anymore. Check that when a target service type fails, the OnFailure
  setting is used and the mentioned service is run.

  [Where problems could occur]

  Issues might happen if some target has an OnFailure setting that was
  never run in the past because of this bug, and the behavior is not
  really right because it was never tested. However, OnFailure is not
  used that much on 20.04 in target services:

  /lib/systemd $ find . -name \*.target | xargs grep OnFailure
  /lib/systemd $ 
  /etc/systemd $ find . -name \*.target | xargs grep OnFailure
  /etc/systemd $ 

  I've seen it only in emergency.target for UC20.

  [Other Info]
   
  None

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


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

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

[Michel-Ekimia]

apport information

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

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

Title:
  External Jack produce garbled sound with alc293

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  External Jack produce garbled sound

  We tried alc293-dell1 and alc293-dell , but it does not change
  anything

  It seems it was working with some older 5.11 kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.12
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pandora3069 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Nov  5 12:06:01 2021
  InstallationDate: Installed on 2020-10-13 (387 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2020
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NL4x_NL5xLU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NL4x_NL5xLU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pandora3069 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-13 (387 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: pulseaudio 1:13.99.1-1ubuntu3.12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  focal
  Uname: Linux 5.11.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 09/24/2020
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NL4x_NL5xLU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NL4x_NL5xLU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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


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

Re: [Touch-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

[Anuj Upadhyay]

Hi,

I tried setting options snd-hda-
  intel model=alc255-acer, and it worked for me after a reboot.

Let me know if it works for anyone else

On Sat, 22 May, 2021, 13:09 Kreaninw, <1523...@bugs.launchpad.net>
wrote:

> Tried this again on Ubuntu 21.04. There is still no sound out of the
> box.
>
> I then compiled the alsa-topology-conf as suggested here:
> https://gist.github.com/crojewsk/4e6382bfb0dbfaaf60513174211f29cb
> #enabling-the-configuration
> 
>
> And enabled the options snd_intel_dspcfg dsp_driver=2.
>
> But still no luck. I believe that I will have to do the NHLT overriding
> for it to work. However, that's beyond my ability. The page suggested
> that we should ask Intel developers for help to obtain the correct NHLT
> binary.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1789154).
> https://bugs.launchpad.net/bugs/1523100
>
> Title:
>   Alsa not detecting internal microphone [ALC255] (Realtek)
>
> Status in alsa-driver package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
>   Aspire VN7-792G and noticed, that the internal microphone doesn't
>   work. The computer has been released a couple of months ago and it's
>   Intel Skylake -based with a Sunrise Point -based motherboard.
>
>   INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
>   detected. Currently using Ubuntu 16.04 for proper hardware support.
>
>   Alsa reports the audio device to be:
>
>   Card: HDA Intel PCH
>   Chip: Intel Skylake HDMI
>
>   The speakers are working fine, but both alsamixer and pavucontrol
>   (Pulseaudio Volume Control) raport the unplugged external microphone
>   connector as the only sound input.
>
>   I have tried many of the alsa model configurations (options snd-hda-
>   intel model=something) without success, alsa finds only the microphone
>   jack, which works fine when I plug an external microphone in it.
>
>   Here's some info:
>
>   lspci | grep -I audio:
>
>   00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
>   HD Audio (rev 31)
>
>   cat /proc/asound/cards:
>
>   0 [PCH]: HDA-Intel - HDA Intel PCH
>   HDA Intel PCH at 0x8432 irq 128
>
>   And a clip from dmesg | grep snd:
>
>   [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops
> i915_audio_component_bind_ops [i915])
>   [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255:
> line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
>   [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0
> (0x0/0x0/0x0/0x0/0x0)
>   [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1
> (0x21/0x0/0x0/0x0/0x0)
>   [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
>   [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
>   [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
>   [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a
>
>   One problem is that I can't find any model options (options snd-hda-
>   intel model=something) or other parameters for the card's model
>   (ALC255), I suppose this issue is relatively new.
>
>   /Dennis
>   ---
>   ApportVersion: 2.19.2-0ubuntu6
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  dennis 1180 F pulseaudio
>   CurrentDesktop: GNOME
>   DistroRelease: Ubuntu 16.04
>   InstallationDate: Installed on 2015-11-11 (23 days ago)
>   InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20151110)
>   Package: alsa-driver (not installed)
>   ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
>   Tags:  xenial
>   Uname: Linux 4.2.0-19-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 09/25/2015
>   dmi.bios.vendor: Insyde Corp.
>   dmi.bios.version: V1.02
>   dmi.board.asset.tag: No Asset Tag
>   dmi.board.name: Aspire VN7-792G
>   dmi.board.vendor: Acer
>   dmi.board.version: V1.02
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Acer
>   dmi.chassis.version: V1.02
>   dmi.modalias:
> dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
>   dmi.product.name: Aspire VN7-792G
>   dmi.product.version: V1.02
>   dmi.sys.vendor: Acer
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+subscriptions
>

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

Title:
  Alsa not 

[Touch-packages] [Bug 1949958] CurrentDmesg.txt

[Michel-Ekimia]

apport information

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

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

Title:
  External Jack produce garbled sound with alc293

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  External Jack produce garbled sound

  We tried alc293-dell1 and alc293-dell , but it does not change
  anything

  It seems it was working with some older 5.11 kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.12
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pandora3069 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Nov  5 12:06:01 2021
  InstallationDate: Installed on 2020-10-13 (387 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2020
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NL4x_NL5xLU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NL4x_NL5xLU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pandora3069 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-13 (387 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: pulseaudio 1:13.99.1-1ubuntu3.12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  focal
  Uname: Linux 5.11.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 09/24/2020
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NL4x_NL5xLU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NL4x_NL5xLU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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


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

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

[Michel-Ekimia]

apport information

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

** Summary changed:

- External Jack produce garbled sound 
+ External Jack produce garbled sound with alc293

** Description changed:

  External Jack produce garbled sound
+ 
+ We tried alc293-dell1 and alc293-dell , but it does not change anything
+ 
+ It seems it was working with some older 5.11 kernel
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.12
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  pandora3069 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  pandora3069 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Nov  5 12:06:01 2021
  InstallationDate: Installed on 2020-10-13 (387 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2020
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NL4x_NL5xLU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NL4x_NL5xLU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  pandora3069 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  pandora3069 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-13 (387 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: pulseaudio 1:13.99.1-1ubuntu3.12
  PackageArchitecture: amd64
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  focal
  Uname: Linux 5.11.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 09/24/2020
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NL4x_NL5xLU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NL4x_NL5xLU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

Title:
  External Jack produce garbled sound with alc293

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  External Jack produce garbled sound

  We tried alc293-dell1 and alc293-dell , but it does not change
  anything

  It seems it was working with some older 5.11 kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.12
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  

[Touch-packages] [Bug 1949958] [NEW] External Jack produce garbled sound with alc293

[Michel-Ekimia]

Public bug reported:

External Jack produce garbled sound

We tried alc293-dell1 and alc293-dell , but it does not change anything

It seems it was working with some older 5.11 kernel

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.12
ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pandora3069 F pulseaudio
CasperMD5CheckResult: skip
Date: Fri Nov  5 12:06:01 2021
InstallationDate: Installed on 2020-10-13 (387 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2020
dmi.bios.release: 7.4
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.04
dmi.board.asset.tag: Tag 12345
dmi.board.name: NL4x_NL5xLU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.2
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: NL4x_NL5xLU
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pandora3069 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-13 (387 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Package: pulseaudio 1:13.99.1-1ubuntu3.12
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Tags:  focal
Uname: Linux 5.11.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 09/24/2020
dmi.bios.release: 7.4
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.04
dmi.board.asset.tag: Tag 12345
dmi.board.name: NL4x_NL5xLU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.2
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: NL4x_NL5xLU
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

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


** Tags: amd64 apport-bug apport-collected focal

** Tags added: apport-collected

** Description changed:

  External Jack produce garbled sound
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.12
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pandora3069 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Nov  5 12:06:01 2021
  InstallationDate: Installed on 2020-10-13 (387 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2020
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NL4x_NL5xLU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 

[Touch-packages] [Bug 1949958] AlsaInfo.txt

[Michel-Ekimia]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1949958/+attachment/5538406/+files/AlsaInfo.txt

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

Title:
  External Jack produce garbled sound with alc293

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  External Jack produce garbled sound

  We tried alc293-dell1 and alc293-dell , but it does not change
  anything

  It seems it was working with some older 5.11 kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.12
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pandora3069 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Nov  5 12:06:01 2021
  InstallationDate: Installed on 2020-10-13 (387 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2020
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NL4x_NL5xLU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NL4x_NL5xLU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pandora3069 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-13 (387 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: pulseaudio 1:13.99.1-1ubuntu3.12
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  focal
  Uname: Linux 5.11.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 09/24/2020
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NL4x_NL5xLU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: NL4x_NL5xLU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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


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

[Touch-packages] [Bug 1948476] Re: [SRU] Allow target units to fail

[Lukas Märdian]

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

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

Title:
  [SRU] Allow target units to fail

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Focal:
  New

Bug description:
  [Impact]

  A systemd regression in focal made it think that target units cannot
  fail, which produced warnings like:

  emergency.target: Requested dependency OnFailure=reboot.target ignored
  (target units cannot fail).

  So the OnFailure settings are ignored for targets (see
  https://github.com/snapcore/core-initrd/issues/33 for details).
  Upstream fixed the issue in v246:
  
https://github.com/systemd/systemd/commit/94d1ddbd7cd15b1073757eb5ae0645c83f0b414c

  [Test Plan]

  Test on a UC system and check that the above warnings are not shown
  anymore. Check that when a target service type fails, the OnFailure
  setting is used and the mentioned service is run.

  [Where problems could occur]

  Issues might happen if some target has an OnFailure setting that was
  never run in the past because of this bug, and the behavior is not
  really right because it was never tested. However, OnFailure is not
  used that much on 20.04 in target services:

  /lib/systemd $ find . -name \*.target | xargs grep OnFailure
  /lib/systemd $ 
  /etc/systemd $ find . -name \*.target | xargs grep OnFailure
  /etc/systemd $ 

  I've seen it only in emergency.target for UC20.

  [Other Info]
   
  None

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


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

[Touch-packages] [Bug 1945795] Re: krb5: Fail to build against OpenSSL 3.0

[Simon Chopin]

For the record : https://salsa.debian.org/debian/krb5/-/merge_requests/6

I plan on uploading (well, having someone upload) a version of krb5
based off this branch if it hasn't already hit Debian when we start the
transition.

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

Title:
  krb5: Fail to build against OpenSSL 3.0

Status in krb5 package in Ubuntu:
  New

Bug description:
  Hello,

  As part of a rebuild against OpenSSL3, this package failed to build on one or
  several architectures. You can find the details of the rebuild at 

  https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html

  or for the amd64 failed build, directly at

  
https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22098576/+files/buildlog_ubuntu-
  impish-amd64.krb5_1.18.3-6.0~ssl3ppa1.1_BUILDING.txt.gz

  We're planning to transition to OpenSSL 3.0 for the 22.04 release, and 
consider
  this issue as blocking for this transition.

  You can find general migration informations at
  https://www.openssl.org/docs/manmaster/man7/migration_guide.html
  For your tests, you can build against libssl-dev as found in the PPA
  schopin/openssl-3.0.0

  Looking into the upstream master branch, I was able to find the following 
commits
  related to OpenSSL3:

  https://github.com/krb5/krb5/commit/00de1aad7b3647b91017c7009b0bc65cd0c8b2e0
  https://github.com/krb5/krb5/commit/d6bf42279675100e3e4fe7c6e08eef74d49624cb
  https://github.com/krb5/krb5/commit/aa9b4a2a64046afd2fab7cb49c346295874a5fb6

  Perhaps a simple cherry-pick of those would suffice?

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


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

[Touch-packages] [Bug 1949956] [NEW] Debian bug 955135 affects Ubuntu bionic

[4tro]

Public bug reported:

Upstream bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955135

https://github.com/mvo5/unattended-
upgrades/commit/c0773581b636ccb623094abd9554afd17a49c0ce Relevant

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Debian bug 955135 affects Ubuntu bionic

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Upstream bug
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955135

  https://github.com/mvo5/unattended-
  upgrades/commit/c0773581b636ccb623094abd9554afd17a49c0ce Relevant

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


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

[Touch-packages] [Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18

[Michael Vogt]

We created a test PR that uses this core18 snap build in
https://github.com/snapcore/snapd/pull/11015 - we are still running
tests but it seems the error is still there :-(

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

Title:
  systemd randomly fails to activate mount units in Ubuntu Core 18

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Jammy:
  New

Bug description:
  Since a month or so, we've been seeing random failures in our snapd
  spread tests where systemd could not start the mount unit associated
  with a snap because of a failed dependency.

  The issue is described in the comments to PR
  https://github.com/snapcore/snapd/pull/10935, but I'll summarize it
  here.

  When starting a snap, snapd creates a mount unit to mount the snap's
  squashfs (the template is
  
https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205).
  The snapd asks systemd to reload the configuration, and starts the
  mount unit.

  The failure we've observed is that sometimes systemd decides to stop
  our mount unit (search for "Unmounting Mount unit for test-snapd-svc-
  flip-flop" in the attached log), and then tries to reactivate it
  again, and at that point it fails.

  When I asked for help, Lukas pointed out that the latest update
  contains a patch that is related to reload handling and mount units:
  
http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz
  (the patch itself is better visible at
  
https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656).
  When looking at the systemd git log, though, I noticed another patch
  that was applied shortly after this one, which also seems related but
  was not backported:
  
https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0

  Since the stopping of our mount unit happens immediately after a
  systemd reload, it actually seems very likely that the inclusion of
  f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what
  causes our woes (though, indeed, the issue is not reliably
  reproducible, so we cannot be sure).

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


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

[Touch-packages] [Bug 1948698] Re: Update tzdata to version 2021e

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2021e-1ubuntu1

---
tzdata (2021e-1ubuntu1) jammy; urgency=medium

  * Merge from Debian unstable (LP: #1948698). Remaining changes:
- Ship ICU timezone data files which are utilized by php and update them
  to 2021a3.

tzdata (2021e-1) unstable; urgency=medium

  * New upstream version:
- Palestine will fall back 2021-10-29 (not 2021-10-30) at 01:00.

 -- Brian Murray   Mon, 25 Oct 2021 12:12:45 -0700

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

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

Title:
  Update tzdata to version 2021e

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Hirsute:
  Fix Released
Status in tzdata source package in Impish:
  Fix Released

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Asia/Gaza

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Asia/Gaza 2021

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia')); 
print(str(tz.utcoffset(datetime(2021, 9, 26'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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


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

[Touch-packages] [Bug 1934644] Re: gsettings-desktop-schemas 40 breaks workspace nagivation with gnome-shell 38

[Launchpad Bug Tracker]

This bug was fixed in the package gsettings-desktop-schemas -
41.0-2ubuntu1

---
gsettings-desktop-schemas (41.0-2ubuntu1) jammy; urgency=medium

  * Merge with Debian. Remaining changes:
- Add ubuntu_lock-on-suspend.patch
- Drop obsolete Restore-peripheral-display-keys.patch
  * Dropped changes:
- debian/control.in: Drop extra Breaks not needed since 20.04 LTS

gsettings-desktop-schemas (41.0-2) unstable; urgency=medium

  [ Julian Andres Klode ]
  * Break gnome-shell (<< 40) to avoid messing up workspace shortcuts
(LP: #1934644)

gsettings-desktop-schemas (41.0-1) unstable; urgency=medium

  * New upstream release
  * debian/gsettings-desktop-schemas.gsettings-override:
Keep setting panel-main-menu to Alt-F1 for now.
We may drop this override after we finish uploading
GNOME 41 to Unstable. In default GNOME Shell,
Super or Super+S opens the Activities Overview.
Super+A opens the Show Applications view of the Overview.
Other desktops that use this gsettings key should create
their own key since GNOME may remove it in the future
now that it's been marked Deprecated.
  * Bump Standards-Version to 4.6.0

gsettings-desktop-schemas (40.0-2) unstable; urgency=medium

  * Team upload
  * Upload to unstable (transition: #992870)

 -- Jeremy Bicha   Sat, 23 Oct 2021 19:38:37 -0400

** Changed in: gsettings-desktop-schemas (Ubuntu)
   Status: New => Fix Released

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

Title:
  gsettings-desktop-schemas 40 breaks workspace nagivation with gnome-
  shell 38

Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Released

Bug description:
  gsettings-desktop-schemas 40 is supposed to be used with gnome-shell
  40, not 38, and hence has moved the Page_up/Down (and )
  shortcuts for moving between workspaces from vertical to horizontal
  settings, breaking workspace navigation in gnome-shell 38.

  This commit needs to be reverted until gnome-shell 40 lands:

  https://salsa.debian.org/gnome-team/gsettings-desktop-
  schemas/-/commit/a7b057cde57a6509a91fd80b492460a036a04ade

  Once gnome-shell 40 lands, the revert should be reverted and Breaks:
  gnome-shell (<< 40) should be added.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1934644/+subscriptions


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