[Touch-packages] [Bug 1951653] [NEW] can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'

2021-11-19 Thread Steve Langasek
Public bug reported:

I have tried to tell netplan to let my ethernet device be managed by
NetworkManager, so that I can then configure a pppoe connection on top
of this device.

This fails with:

# nmcli c up netplan-wan
Error: Connection activation failed: No suitable device found for this 
connection (device lo not available because device is strictly unmanaged).
#

I don't know why it mentions 'lo' in that message, but the wan interface
is unmanaged (as are all devices on the system, but this one is supposed
to be managed):

# nmcli d status | grep wan
wan   ethernet  unmanaged  -- 
#

After much searching, I've figured out that this comes from
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf:

keyfile]
unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma

Even though I've told netplan to use the NM renderer for this device,
the configuration emitted by netplan is insufficient to override this.

Using the workaround from https://askubuntu.com/questions/71159/network-
manager-says-device-not-managed (sudo touch
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) doesn't
work, but if I set NetworkManager as the toplevel renderer in
/etc/netplan, /run/NetworkManager/conf.d/10-globally-managed-
devices.conf is emitted, which evidently DOES work.  But I only have one
device that I want rendered by NM, so I shouldn't have to declare NM at
the top level of the yaml with a lot of duplication in order to get this
result.

I would argue that the 10-globally-managed-devices.conf should not be
there at all.  But if it is going to be, then netplan needs to
consistently override it whenever there is any use of the NetworkManager
backend.

** Affects: netplan.io (Ubuntu)
 Importance: High
 Status: New

** Affects: network-manager (Ubuntu)
 Importance: High
 Status: New

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

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

Title:
  can't use NM for ethernet device on 20.04 LTS because it is 'strictly
  unmanaged'

Status in netplan.io package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  I have tried to tell netplan to let my ethernet device be managed by
  NetworkManager, so that I can then configure a pppoe connection on top
  of this device.

  This fails with:

  # nmcli c up netplan-wan
  Error: Connection activation failed: No suitable device found for this 
connection (device lo not available because device is strictly unmanaged).
  #

  I don't know why it mentions 'lo' in that message, but the wan
  interface is unmanaged (as are all devices on the system, but this one
  is supposed to be managed):

  # nmcli d status | grep wan
  wan   ethernet  unmanaged  -- 
  #

  After much searching, I've figured out that this comes from
  /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf:

  keyfile]
  unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma

  Even though I've told netplan to use the NM renderer for this device,
  the configuration emitted by netplan is insufficient to override this.

  Using the workaround from
  https://askubuntu.com/questions/71159/network-manager-says-device-not-
  managed (sudo touch /etc/NetworkManager/conf.d/10-globally-managed-
  devices.conf) doesn't work, but if I set NetworkManager as the
  toplevel renderer in /etc/netplan,
  /run/NetworkManager/conf.d/10-globally-managed-devices.conf is
  emitted, which evidently DOES work.  But I only have one device that I
  want rendered by NM, so I shouldn't have to declare NM at the top
  level of the yaml with a lot of duplication in order to get this
  result.

  I would argue that the 10-globally-managed-devices.conf should not be
  there at all.  But if it is going to be, then netplan needs to
  consistently override it whenever there is any use of the
  NetworkManager backend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1951653/+subscriptions


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


[Touch-packages] [Bug 1949205] Re: Prints message that 'Volume group "vgubuntu" not found' when partition encrypted in LUKS

2021-11-18 Thread Steve Langasek
** Summary changed:

- Volume group "vgubuntu" not found when parition encrypted in LUKS
+ Prints message that 'Volume group "vgubuntu" not found' when partition 
encrypted in LUKS

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Prints message that 'Volume group "vgubuntu" not found' when partition
  encrypted in LUKS

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  I wonder whether that is correct LVM starts before LUKS disk decryption. 
Becuase of that the client see the message of non existing vgubuntu.
  Not sure whether that is expected behaviour.

  boot.log attached. And screenshot.

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


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


[Touch-packages] [Bug 1950872] Re: package libpam0g:amd64 1.3.1-5ubuntu4.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Trace/b

2021-11-13 Thread Steve Langasek
> libpam0g:amd64 (--configure):
>  installed libpam0g:amd64 package post-installation script subprocess was 
> killed by signal (Trace/breakpoint trap), core dumped

This is not something that happens during normal operation.  Do you have
some idea why this signal was generated?  Did you also get an apport
notification for the crashed process?

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

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

Title:
  package libpam0g:amd64 1.3.1-5ubuntu4.3 failed to install/upgrade:
  installed libpam0g:amd64 package post-installation script subprocess
  was killed by signal (Trace/breakpoint trap), core dumped

Status in pam package in Ubuntu:
  Incomplete

Bug description:
  just crash

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam0g:amd64 1.3.1-5ubuntu4.3
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Nov 13 18:55:15 2021
  DpkgTerminalLog:
   Preparing to unpack .../libpam0g_1.3.1-5ubuntu4.3_amd64.deb ...
   Unpacking libpam0g:amd64 (1.3.1-5ubuntu4.3) over (1.3.1-5ubuntu4.2) ...
   Setting up libpam0g:amd64 (1.3.1-5ubuntu4.3) ...
   dpkg: error processing package libpam0g:amd64 (--configure):
installed libpam0g:amd64 package post-installation script subprocess was 
killed by signal (Trace/breakpoint trap), core dumped
  DuplicateSignature:
   package:libpam0g:amd64:1.3.1-5ubuntu4.3
   Setting up libpam0g:amd64 (1.3.1-5ubuntu4.3) ...
   dpkg: error processing package libpam0g:amd64 (--configure):
installed libpam0g:amd64 package post-installation script subprocess was 
killed by signal (Trace/breakpoint trap), core dumped
  ErrorMessage: installed libpam0g:amd64 package post-installation script 
subprocess was killed by signal (Trace/breakpoint trap), core dumped
  InstallationDate: Installed on 2021-11-13 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  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
  SourcePackage: pam
  Title: package libpam0g:amd64 1.3.1-5ubuntu4.3 failed to install/upgrade: 
installed libpam0g:amd64 package post-installation script subprocess was killed 
by signal (Trace/breakpoint trap), core dumped
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1921518] Re: OpenSSL "double free" error

2021-11-12 Thread Steve Langasek
How will you test that the change does not regress any wget behavior?

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

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

Title:
  OpenSSL "double free" error

Status in openssl package in Ubuntu:
  Incomplete
Status in wget package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  Incomplete
Status in wget source package in Focal:
  Incomplete

Bug description:
  [Impact]
  openssl config file is being loaded twice, causing engines to be loaded twice 
if specified therein, causing double free errors and other strange behavior.

  [Test plan]
  Run the command of the package being tested in

  gdb  -ex "break CONF_modules_load_file" -ex "run" --args

  and make sure it only breaks one.

  [Where problems could occur]

  wget: This is an upstream change that changes initialization and is in
  use in later releases. Since it mostly removes an unneeded call to the
  load file function, a regression could be a config file being ignored,
  but it seems unlikely given the use in later releases

  [Original bug report]
  "double free" error is seen when using curl utility. Error is from 
libcrypto.so which is part of the OpenSSL package. This happens only when 
OpenSSL is configured to use a dynamic engine.

  OpenSSL version is 1.1.1f

  The issue is not encountered if
  http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead.

  OpenSSL can be configured to use a dynamic engine by editing the
  default openssl config file which is located at '/etc/ssl/openssl.cnf'
  on Ubuntu systems.

  On Bluefield systems, config diff to enable PKA dynamic engine, is as
  below:

  +openssl_conf = conf_section
  +
   # Extra OBJECT IDENTIFIER info:
   #oid_file  = $ENV::HOME/.oid
   oid_section= new_oids

  +[ conf_section ]
  +engines = engine_section
  +
  +[ engine_section ]
  +bf = bf_section
  +
  +[ bf_section ]
  +engine_id=pka
  +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so
  +init=0
  +

  engine_id above refers to dynamic engine name/identifier.
  dynamic_path points to the .so file for the dynamic engine.

  # curl -O https://tpo.pe/pathogen.vim

  double free or corruption (out)

  Aborted (core dumped)

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


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


[Touch-packages] [Bug 1939973] Re: make 4.3-4.1 triggers build failures

2021-11-07 Thread Steve Langasek
Removing block-proposed tag because this is now blocking the unrelated
4.3-4ubuntu2 upload.

** Tags removed: block-proposed

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

Title:
  make 4.3-4.1 triggers build failures

Status in make-dfsg package in Ubuntu:
  Confirmed
Status in make-dfsg source package in Impish:
  Confirmed

Bug description:
  trying to rebuild cross-toolchain-base from
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile/+packages

  triggers a build failure:

  [...]
  START stamp-dir/init-binutils
  tar -x -f  /usr/src/binutils/binutils-2.37.tar.xz
  set -e; cd binutils-2.37 ; cp -a /usr/src/binutils/debian/ . ; if [ -n 
"$(grep -v '^\#' /<>/debian/patches/binutils/series)" ]; then 
QUILT_PATCHES=/<>/debian/patches/binutils quilt --quiltrc 
/dev/null  push -a; fi; rm -rf .pc
  cd binutils-2.37 ; env -i CROSS_ARCHS="amd64 i386 s390x ppc64el arm64 armhf 
armel  powerpc" debian/rules stamps/control
  make: dpkg-architecture: No such file or directory
  make: lsb_release: No such file or directory
  make: lsb_release: No such file or directory
  make: pwd: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  debian/rules:163: *** unexpected source package name: .  Stop.
  make: *** [debian/rules:215: stamp-dir/init-binutils] Error 2
  dpkg-buildpackage.pl: error: debian/rules build subprocess returned exit 
status 2

  
  working around by omitting the -i option to env, or by setting PATH 
explicitly. Reverting to the version in the release pocket lets the c-t-b- 
build succeed.

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


-- 
Mailing list: https://launchpad.net/~touch-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] Please test proposed package

2021-11-05 Thread 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"

2021-11-05 Thread 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

2021-11-05 Thread 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

2021-11-05 Thread 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

2021-11-05 Thread 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

2021-11-05 Thread 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 1948698] Update Released

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

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

Title:
  Update tzdata to version 2021e

Status in tzdata package in Ubuntu:
  In Progress
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 772121] Re: typo in pam_tally manpage

2021-10-26 Thread Steve Langasek
1.4.0-10ubuntu1 has been uploaded to jammy, which fixes this bug, but a
wrong upload option prevents this bug from being autoclosed.

Related changelog entry:

pam (1.4.0-1) unstable; urgency=medium

  * New upstream release.  Closes: #948188.
- Stop using obsoleted selinux headers.  Closes: #956355.
- Continue building pam_cracklib, which is deprecated upstream;
  the replacement, pam_passwdqc, is packaged separately.
- Update symbols file for new symbols.
- Refresh lintian overrides for changes to available pam modules.
  * Drop patches to implement "nullok_secure" option for pam_unix.
Closes: #674857, #936071, LP: #1860826.
  * debian/patches-applied/cve-2010-4708.patch: drop, applied upstream.
  * debian/patches-applied/nullok_secure-compat.patch: Support
nullok_secure as a deprecated alias for nullok.
  * debian/pam-configs/unix: use nullok, not nullok_secure.
  * Drop pam_tally and pam_tally2 modules, which have been deprecated
upstream in favor of pam_faillock.  Closes: #569746, LP: #772121.
  * Add hardening+=bindnow to build options, per lintian.


** Changed in: pam (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  typo in pam_tally manpage

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

Bug description:
  The pam_tally manpage says "filed" where it should say "field".

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


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


[Touch-packages] [Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.

2021-10-22 Thread Steve Langasek
Is there a risk that applying these changes will regress the behavior of
these modems on systems which have NOT applied the firmware updates?
Can the testcase include a check for this?

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

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

Title:
  Support manual firmware upgrading for Foxconn and Quectel modems.

Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  The modem certification requires that different modem firmware is used for 
different network carrier.
  This needs the firmware upgrading capability during the modem certification 
process.

  The modem manufacture vendors (Foxconn and Quectel) provided utilities to do 
modem's firmware upgrading manually.(LP#1943774, LP#1943780)
  These utilities are verified to be working when the recent versions(> v 
1.18.2) of ModemManager are used with.

  To support manual firmware upgrading on the current Focal release which is 
using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2.
  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
  * for Foxconn T99W175
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9
    
**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154

  The firmware upgrading was verified using the patched ModemManager v 1.16.6 
with the following 2 modems:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  4. Using the firmware upgrading application to upgrade the modem’s firmware
  5. Verify if the modem’s firmware upgrading is successful
  6. Reboot
  7. Verify if the upgraded modem firmware is still working

  [Where problems could occur]

  The requested upstream patches are for these 2 specific modems.
  This should not affect existing generic functions and other modems.

  [Other Info]

  The firmware and the upgrading utilities can be downloaded from the following 
link:
  * LP#1943774 for Quectel modems
  * LP#1943780 for Foxconn modems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions


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


[Touch-packages] [Bug 1947475] Re: PAM: pam_chroot.so not accessible after upgrade 21.04 > 21.10

2021-10-18 Thread Steve Langasek
This is a regression in the libpam-chroot package, which is installing
the module to the wrong path, not where libpam looks for it.

libpam-chroot is a separate source package in universe; reassigning.

** Package changed: pam (Ubuntu) => libpam-chroot (Ubuntu)

** Changed in: libpam-chroot (Ubuntu)
   Status: New => Triaged

** Bug watch added: Debian Bug tracker #991113
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991113

** Also affects: libpam-chroot (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991113
   Importance: Unknown
   Status: Unknown

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

Title:
  PAM: pam_chroot.so not accessible after upgrade 21.04 > 21.10

Status in libpam-chroot package in Ubuntu:
  Triaged
Status in libpam-chroot package in Debian:
  Unknown

Bug description:
  After upgrading Ubuntu server (AMD64) from 21.04 to 21.10 the module
  pam_chroot.so cannot be loaded by PAM anymore.

  21.10
  -
  auth.log:
  sshd: PAM unable to dlopen(pam_chroot.so): /lib/security/pam_chroot.so: 
cannot open shared object file: No such file or directory
  sshd: PAM adding faulty module: pam_chroot.so

  # find / -name 'pam_chroot.so'
  /usr/lib/x86_64-linux-gnu/pam_chroot.so

  21.04
  -
  # find / -type f -name 'pam_chroot.so'
  /usr/lib/security/pam_chroot.so

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-release-upgrader-core 1:21.10.8
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  Date: Sat Oct 16 21:02:22 2021
  InstallationDate: Installed on 2020-12-07 (313 days ago)
  InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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


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


[Touch-packages] [Bug 1947429] [NEW] linux-object-* not autoremoved on upgrade

2021-10-15 Thread Steve Langasek
Public bug reported:

After upgrading my kernel, directories are left behind in /lib/modules
for previous kernel because with the kernel packaging layout, not all
binary packages are autoremoved:

$ dpkg -S /lib/modules/5.11.0-34-generic
linux-objects-nvidia-460-5.11.0-34-generic: /lib/modules/5.11.0-34-generic
$ sudo apt autoremove --purge linux-objects-nvidia-460-5.11.0-34-generic
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  linux-objects-nvidia-460-5.11.0-34-generic*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Requesting to save current system state
Successfully saved as "autozsys_sdijbm"
(Reading database ... 362960 files and directories currently installed.)
Purging configuration files for linux-objects-nvidia-460-5.11.0-34-generic (5.11
.0-34.36) ...
dpkg: warning: while removing linux-objects-nvidia-460-5.11.0-34-generic, 
directory '/lib/modules/5.11.0-34-generic' not empty so not removed
ZSys is adding automatic system snapshot to GRUB menu
$

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: apt 2.3.9
ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia zfs zunicode 
zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 15 14:36:40 2021
InstallationDate: Installed on 2019-12-23 (661 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: apt
UpgradeStatus: Upgraded to impish on 2021-10-15 (0 days ago)

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


** Tags: amd64 apport-bug impish

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

Title:
  linux-object-* not autoremoved on upgrade

Status in apt package in Ubuntu:
  New

Bug description:
  After upgrading my kernel, directories are left behind in /lib/modules
  for previous kernel because with the kernel packaging layout, not all
  binary packages are autoremoved:

  $ dpkg -S /lib/modules/5.11.0-34-generic
  linux-objects-nvidia-460-5.11.0-34-generic: /lib/modules/5.11.0-34-generic
  $ sudo apt autoremove --purge linux-objects-nvidia-460-5.11.0-34-generic
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
linux-objects-nvidia-460-5.11.0-34-generic*
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Requesting to save current system state
  Successfully saved as "autozsys_sdijbm"
  (Reading database ... 362960 files and directories currently installed.)
  Purging configuration files for linux-objects-nvidia-460-5.11.0-34-generic 
(5.11
  .0-34.36) ...
  dpkg: warning: while removing linux-objects-nvidia-460-5.11.0-34-generic, 
directory '/lib/modules/5.11.0-34-generic' not empty so not removed
  ZSys is adding automatic system snapshot to GRUB menu
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apt 2.3.9
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia zfs 
zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 15 14:36:40 2021
  InstallationDate: Installed on 2019-12-23 (661 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apt
  UpgradeStatus: Upgraded to impish on 2021-10-15 (0 days ago)

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


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


[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute)

2021-10-15 Thread Steve Langasek
Please provide an SRU template for this bug per
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

** Changed in: libsignon-glib (Ubuntu)
   Status: In Progress => Incomplete

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

Title:
  gir1.2-signon-2.0 needs to declare replace on older releases
  (Groovy2Hirsute)

Status in libsignon-glib package in Ubuntu:
  Incomplete

Bug description:
  gir1.2-signon-1.0 from groovy
  gir1.2-signon-2.0 from hirsute

  above two packages ship the same file /usr/lib/python3/dist-
  packages/gi/overrides/Signon.py without specifying how to resolve the
  conflict.

  Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', 
which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5
  Errors were encountered while processing:
   /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Probably needs a conflicts/replaces dependency added to the newer
  hirsute package.

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


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


[Touch-packages] [Bug 1944741] Re: HiFive Unmatched partitions are named "Unleashed"

2021-10-15