[Touch-packages] [Bug 1959015] Re: Switch to new HTTPS-capable domains for PPAs

2022-01-27 Thread Brian Murray
** Tags removed: rls-jj-incoming

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

Title:
  Switch to new HTTPS-capable domains for PPAs

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Jammy:
  New

Bug description:
  As described in bug 1473091, PPAs are now being served from new
  domains that aren't under launchpad.net and so can safely serve HTTPS
  without risk of compromising Launchpad session cookies.  The old
  domains will keep working indefinitely, but nevertheless it would be
  good if we could arrange for add-apt-repository to use the new domains
  as of 22.04.

  The changes are:

   * http://ppa.launchpad.net/ → https://ppa.launchpadcontent.net/ (or http:// 
works too, but we should prefer https://)
   * https://private-ppa.launchpad.net/ → 
https://private-ppa.launchpadcontent.net/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1959015/+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 1955084] Re: systemd unit leaves a process running for the system lifetime but it only does anything at shutdown

2022-01-27 Thread Brian Murray
** Tags added: fr-2007

** Tags removed: rls-jj-incoming

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

Title:
  systemd unit leaves a process running for the system lifetime but it
  only does anything at shutdown

Status in unattended-upgrades package in Ubuntu:
  New
Status in unattended-upgrades source package in Jammy:
  New

Bug description:
  The /lib/systemd/system/unattended-upgrades.service unit leaves a
  process, /usr/share/unattended-upgrades/unattended-upgrade-shutdown
  --wait-for-signal, running from system start until shutdown.  This
  increases the minimum memory footprint of every host, VM, or container
  where unattended-upgrades is installed.  The motivation for having
  this systemd unit is clear in terms of the practicalities of
  implementing what this unit needs to do, but we should try to find
  some way to achieve this which does not rely on increasing the low
  water mark of system memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1955084/+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 1959015] Re: Switch to new HTTPS-capable domains for PPAs

2022-01-27 Thread Brian Murray
** Also affects: software-properties (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: software-properties (Ubuntu Jammy)
   Importance: Undecided => Medium

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

Title:
  Switch to new HTTPS-capable domains for PPAs

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Jammy:
  New

Bug description:
  As described in bug 1473091, PPAs are now being served from new
  domains that aren't under launchpad.net and so can safely serve HTTPS
  without risk of compromising Launchpad session cookies.  The old
  domains will keep working indefinitely, but nevertheless it would be
  good if we could arrange for add-apt-repository to use the new domains
  as of 22.04.

  The changes are:

   * http://ppa.launchpad.net/ → https://ppa.launchpadcontent.net/ (or http:// 
works too, but we should prefer https://)
   * https://private-ppa.launchpad.net/ → 
https://private-ppa.launchpadcontent.net/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1959015/+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 1955084] Re: systemd unit leaves a process running for the system lifetime but it only does anything at shutdown

2022-01-27 Thread Brian Murray
** Also affects: unattended-upgrades (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: unattended-upgrades (Ubuntu Jammy)
   Importance: Undecided => High

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

Title:
  systemd unit leaves a process running for the system lifetime but it
  only does anything at shutdown

Status in unattended-upgrades package in Ubuntu:
  New
Status in unattended-upgrades source package in Jammy:
  New

Bug description:
  The /lib/systemd/system/unattended-upgrades.service unit leaves a
  process, /usr/share/unattended-upgrades/unattended-upgrade-shutdown
  --wait-for-signal, running from system start until shutdown.  This
  increases the minimum memory footprint of every host, VM, or container
  where unattended-upgrades is installed.  The motivation for having
  this systemd unit is clear in terms of the practicalities of
  implementing what this unit needs to do, but we should try to find
  some way to achieve this which does not rely on increasing the low
  water mark of system memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1955084/+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 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders

2022-01-27 Thread Brian Murray
** Also affects: binutils (Ubuntu Jammy)
   Importance: Critical
   Status: New

** Also affects: xen (Ubuntu Jammy)
   Importance: Undecided
   Status: Invalid

** Tags removed: rls-jj-incoming

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

Title:
  Jammy builds of xen segfault, but only on launchpad x86 builders

Status in binutils:
  Confirmed
Status in launchpad-buildd:
  New
Status in binutils package in Ubuntu:
  New
Status in xen package in Ubuntu:
  Invalid
Status in binutils source package in Jammy:
  New
Status in xen source package in Jammy:
  Invalid
Status in binutils package in Debian:
  New

Bug description:
  FTBFS in Jammy on LP infra:
  
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
  
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
  Related PPA:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages

  Summary:
  - Build reliably fails on LP
  - Build in local sbuild works reliably on my Laptop
  - Build in local VM (sizing like LP builders) works (other crashes but works)
  - Build on AMD server (chip more similar to LP) works reliably

  Failing step:

  On Launchpad build infrastructure it breaks on ld:
  $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 
--image-base=0x82d04000 --stack=0,0 --heap=0,0 
--section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 
--minor-image-version=16 --major-os-version=2 --minor-os-version=0 
--major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp 
--build-id=sha1 -T efi.lds -N prelink.o  
/<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o 
/<>/xen/.xen.efi.0x82d04000.0 && :
  Segmentation fault (core dumped

  ---

  Steps to recreate (result depends on platform)

  # you can grab the package from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/4760/+packages

  sudo vim /etc/apt/sources.list
  sudo apt update
  sudo apt dist-upgrade -y
  sudo apt build-dep xen
  sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts 
apport-retrace
  sudo mkdir /mnt/build
  sudo chmod go+w /mnt/build
  cd  /mnt/build
  # copy in things from host
  scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc 
xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 
ubuntu@:/mnt/build
  dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0
  cd xen_4.16.0
  dpkg-buildpackage -i -us -uc -b

  ---

  In a jammy VM 4cpu/8G I get some avx2 crashes but the build works:

  Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 
7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000]
  Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 
1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 
00  fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66

  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
  (gdb) bt
  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  #1  0x7fa98d63c2d0 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #2  0x7fa98d6021e8 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #3  0x7fa98d602509 in coff_write_alien_symbol () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #4  0x7fa98d6033bd in _bfd_coff_final_link () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #5  0x562bdaaae3bf in ?? ()
  #6  0x7fa98d2e8fd0 in __libc_start_call_main 
(main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, 
argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58
  #7  0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, 
argc=8, argv=0x7ffc797f2968, init=, fini=, 
rtld_fini=, 
  stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409
  #8  0x562bdaaad515 in ?? ()

  ^^ that is a different crash than on th LP builders
  ! And despite those crashes the build does appear to work oO?!

  The same crashes I see on my local sbuild runs, the full set of one build is
  Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 
ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in 
libc.so.6[7f566e74+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 
ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in 
libc.so.6[7fbba2571000+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 
ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in 
libc.so.6[7fe368044000+194000]
  Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 
ip 

[Touch-packages] [Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

2022-01-27 Thread Brian Murray
** Also affects: initramfs-tools (Ubuntu Jammy)
   Importance: Critical
   Status: Confirmed

** Tags removed: rls-jj-incoming

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

Title:
  Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Jammy:
  Confirmed

Bug description:
  [Bug description]

  On a jammy installation, which was upgraded from focal, after a full-
  upgrade and a reboot,

  I enter the LUKS password to decrypt the disk. Then I get the
  following error:

  libgcc_s.so.1 must be installed for pthread_exit to work

  After the error is shown, the system asks for the password again
  (which never works, always throwing the same error).

  [Root cause]

  I was able to decrypt the disk with the same password by booting from
  a live usb. Which allowed further investigation.

  The error shown in the LUKS password prompt menu comes from
  https://github.com/bminor/glibc/blob/glibc-2.34/nptl/pthread_exit.c#L31-L32, 
which indeed shows that pthread_exit fails when libgcc_s.so.1 is missing.

  From
  
https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/hook-functions?h=import/0.140ubuntu10#n260,
  we noticed that libgcc_s.so.1 is only copied if

  1) copy_exec is called for a binary directly linked to libgcc_s.so.1, or
  2) copy_exec is called for a binary linked to libpthread

  The cryptsetup initramfs hook, calls copy_exec for /sbin/cryptsetup,
  which is linked to libargon2.so.1, which is linked to libpthread.so.0.
  This covers case (2) above. As a consequence, libgcc_s.so.1 is copied
  to the initrd image and the error reported here is not seen.

  However, since glibc 2.34, libpthread is shipped within glibc, and the
  binaries are no longer linked to libpthread.so.0. As a consequence, an
  argon2 package built with glibc 2.32 will no longer be linked to
  libpthread.so.0 and libgcc_s.so.1 will no longer be copied to the
  initrd image. Triggering the reported error.

  This can be verified in these two argon2 builds, from the same
  sources, but with different glibc versions:

  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build21.04.0/+build/21066610
  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build22/+build/22255217

  Still lvm2 is a seeded package, which Recommends thin-provisioning-
  tools. thin-provisioning-tools ships a initramfs hook that calls
  copy_exec for /usr/sbin/pdata_tools, which is directly linked to
  libgcc_s.so.1. This covers the case (1) above and should suffice to
  ensure the boot process works properly.

  Since thin-provisioning-tools is just a recommends for lvm2, it could
  be removed from the system (and indeed, for some reason, was not
  present in my focal=>jammy installation). In this case, a new kernel
  installation should trigger the reported error.

  [Reproducer]

  - Install jammy with a LUKS encrypted disk
  - remove thin-provisioning-tools
  - perform a full-upgrade (make sure the kernel was upgraded or run 
update-initramfs manually)
  - reboot and verify you can no longer get past the decrypt password prompt 
screen

  [Workaround]

  A workaround for anyone affected would be to install thin-
  provisioning-tools and run update-initramfs.

  [Impact]

  Users upgrading from focal to jammy will eventually be locked out of
  their systems in case they are using LUKS encryption.

  [Additional information]

  While this issue is similar to
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861757,
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254, and
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950551,
  This is a different bug, with a different root cause.

  Thanks to sergiodj for the pairing session on the root cause analysis.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958594/+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 1958904] Re: autopkgtest is failing on jammy with "no space left on device"

2022-01-26 Thread Brian Murray
Given that this is just a test fix I've tagged the bug block-proposed so
that if the new package only contains this change it won't be pushed to
-updates.

** Tags added: block-proposed-focal block-proposed-impish

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

Title:
  autopkgtest is failing on jammy with "no space left on device"

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Invalid
Status in initramfs-tools source package in Focal:
  In Progress
Status in initramfs-tools source package in Impish:
  In Progress

Bug description:
  [Impact]
  In debian/tests/prep-image we create an image file of 1GB, but recent 
jammy/focal cloud images are (barely) bigger than that, for example the current 
one uncompressed is 1001MB...

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz

  Maybe we should consider to create image files of 2GB or even bigger,
  considering that we are only going to allocate the space that is
  actually needed, because we create the file using truncate.

  [Test Plan]
  Run autotestpkg tests from initramfs-tools package. The "net" test is the one 
that depends on the image created by 'prep-image'. The testcase should complete 
successfully without the temporary image running out of space.

  [Where problems could occur]
  The creation of a larger image for the tests could fail if the filesystem of 
the test system is low on disk space. However, as mentioned before, as the 
image file is created using 'truncate', only the necessary space needed to 
uncompress the cloudimg will be used on the filesystem. Apart from that, we 
assume that 2GB of free space should be available on every test system used for 
Ubuntu autopkgtest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+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 1934552] Re: Graphical glitches on Radeon RX 6700 XT

2022-01-26 Thread Brian Murray
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  Graphical glitches on Radeon RX 6700 XT

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Hirsute:
  Won't Fix

Bug description:
  Ubuntu 21.04, mesa 21.0.1-2 amd64

  Upstream MR:
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9568

  Graphical glitches can be seen occasionally on screen with the RX 6700
  XT graphics card.

  This is fixed upstream with the above merged MR, so please backport
  it...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934552/+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 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange

2022-01-26 Thread Brian Murray
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: openssh (Ubuntu Hirsute)
   Status: Triaged => Won't Fix

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

Title:
  monitor_read: unpermitted request 48 on server while attempting GSSAPI
  key exchange

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Focal:
  Triaged
Status in openssh source package in Hirsute:
  Won't Fix

Bug description:
  I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and
  server) with the option "GSSAPIKeyExchange=yes", and this causes the
  connection to fail. The server has GSSAPI (Kerberos authentication)
  enabled, but is is only used for non-root users (root uses SSH keys).

  Client command:

  ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex
  root@server -v -p  -o GSSAPIKeyExchange=yes

  Client log:

  OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f  31 Mar 2020
  debug1: Reading configuration data /home/user/.ssh/config
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
  debug1: /etc/ssh/ssh_config line 21: Applying options for *
  debug1: Connecting to compute-test [130.75.80.46] port .
  debug1: Connection established.
  debug1: identity file /home/rother/.ssh/id_rsa type 0
  debug1: identity file /home/rother/.ssh/id_rsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_dsa type -1
  debug1: identity file /home/rother/.ssh/id_dsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1
  debug1: identity file /home/rother/.ssh/id_ed25519 type -1
  debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1
  debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1
  debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1
  debug1: identity file /home/rother/.ssh/id_xmss type -1
  debug1: identity file /home/rother/.ssh/id_xmss-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2
  debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 
Ubuntu-4ubuntu0.2
  debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400
  debug1: Authenticating to server: as 'root'
  debug1: Offering GSSAPI proposal: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q==
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: Doing group exchange
  debug1: Calling gss_init_sec_context
  debug1: Delegating credentials
  debug1: Received GSSAPI_COMPLETE
  debug1: Calling gss_init_sec_context
  debug1: Delegating credentials
  debug1: Rekey has happened - updating saved versions
  debug1: rekey out after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: rekey in after 134217728 blocks
  debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA 
SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent
  debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA 
SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent
  debug1: Will attempt key: /home/user/.ssh/id_dsa 
  debug1: Will attempt key: /home/user/.ssh/id_ecdsa 
  debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk 
  debug1: Will attempt key: /home/user/.ssh/id_ed25519 
  debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk 
  debug1: Will attempt key: /home/user/.ssh/id_xmss 
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
server-sig-algs=
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
  debug1: Next authentication method: gssapi-with-mic
  debug1: Delegating credentials
  debug1: Delegating credentials
  debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
  debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
  debug1: Next authentication method: gssapi-keyex
  Connection closed by 1.2.3.4 port 

  Server log:

  debug1: sshd version OpenSSH_8.2, OpenSSL 1.1.1f  31 Mar 2020
  debug1: 

[Touch-packages] [Bug 1938058] Re: systemd-time-wait-sync.service should be part of systemd-timesyncd package

2022-01-26 Thread Brian Murray
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  systemd-time-wait-sync.service should be part of systemd-timesyncd
  package

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Focal:
  New
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  New

Bug description:
  [impact]

  systemd-time-wait-sync service never completes when systemd-timesyncd
  package is not installed

  [test case]

  remove the systemd-timesyncd package and enable the systemd-time-wait-
  sync service, and reboot. Check status of the service to see it's
  stuck in 'activating' state, e.g.:

  ubuntu@lp1937238-f:~$ sudo systemctl status systemd-time-wait-sync.service
  ● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized
   Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; 
enabled; vendor preset: enabled)
   Active: activating (start) since Fri 2021-07-23 15:32:12 UTC; 19s ago

  [regression potential]

  TBD

  [scope]

  this is needed in f and later

  the systemd-timesyncd package was split out from the main systemd
  package starting in focal, so this problem exists in f and later

  the service doesn't exist in b, so this is not needed there

  [other info]

  originally noticed in bug 1937238, but create this new bug in case
  that bug was actually a separate problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938058/+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 1522675] Re: Warning messages about unsandboxed downloads

2022-01-26 Thread Brian Murray
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: synaptic (Ubuntu Hirsute)
   Status: Triaged => Won't Fix

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Fix Released
Status in aptitude source package in Xenial:
  Confirmed
Status in synaptic source package in Xenial:
  Confirmed
Status in update-notifier source package in Xenial:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released
Status in aptitude source package in Hirsute:
  Fix Released
Status in synaptic source package in Hirsute:
  Won't Fix
Status in update-notifier source package in Hirsute:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in aptitude package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  READ ME FIRST
  =
  This is only a regression on a cosmetic level. Previous versions of apt did 
not have any sandboxing whatsoever, so this means apt reverted back to that old 
behavior.

  update-notifier SRU
  ---
  [Impact]
  Cosmetic. Warnings when installing packages using update-notifier downloading 
stuff

  [Test case]

  Install flashplugin-installer with apt and check that the output does
  not contain a message like this:

  W: Can't drop privileges for downloading as file '...' couldn't be
  accessed by user '_apt'

  [Regression Potential]

  It just chowns /var/lib/update-notifier/package-data-
  downloads/partial/ to _apt:root, there should not be any regression.

  Original report
  ---

  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2022-01-26 Thread Brian Murray
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Incomplete
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Incomplete
Status in gnome-shell source package in Impish:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 

[Touch-packages] [Bug 1881207] Re: systemd-networkd brings eno1 up and down repeatedly

2022-01-26 Thread Brian Murray
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: systemd (Ubuntu Hirsute)
   Status: In Progress => Won't Fix

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

Title:
  systemd-networkd brings eno1 up and down repeatedly

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  Won't Fix
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  In Progress

Bug description:
  [impact]

  a system using dhcp for an interface where (1) the interface 'resets'
  itself during mtu setting (meaning it briefly drops carrier during mtu
  change), and (2) the dhcp server provides a non-standard (i.e. other
  than 1500) mtu, will continually loop changing mtu between 1500 and
  the dhcp-privded mtu.

  [test case]

  The e1000e nic is one such nic where the driver briefly drops carrier
  when changing the mtu, so this can be reproduced by creating a VM and
  setting the interface to the 'e1000e' emulated hardware. Then
  configure a dhcp server to provide dhcp service to the VM, and set the
  mtu to e.g. 9000 (anything other than the default 1500).

  When the VM runs dhcp, it will loop with:

  Feb 22 15:18:58 lp1881207-upstream systemd-networkd[992]: ens8: Gained carrier
  Feb 22 15:18:58 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv4 
address 1.2.3.133/24 via 1.2.3.1
  Feb 22 15:18:59 lp1881207-upstream systemd-networkd[992]: ens8: Lost carrier
  Feb 22 15:18:59 lp1881207-upstream systemd-networkd[992]: ens8: DHCP lease 
lost
  Feb 22 15:18:59 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv6 lease 
lost
  Feb 22 15:19:01 lp1881207-upstream systemd-networkd[992]: ens8: Gained carrier
  Feb 22 15:19:01 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv4 
address 1.2.3.133/24 via 1.2.3.1
  Feb 22 15:19:02 lp1881207-upstream systemd-networkd[992]: ens8: Lost carrier
  Feb 22 15:19:02 lp1881207-upstream systemd-networkd[992]: ens8: DHCP lease 
lost
  Feb 22 15:19:02 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv6 lease 
lost
  Feb 22 15:19:04 lp1881207-upstream systemd-networkd[992]: ens8: Gained carrier
  Feb 22 15:19:04 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv4 
address 1.2.3.133/24 via 1.2.3.1
  Feb 22 15:19:05 lp1881207-upstream systemd-networkd[992]: ens8: Lost carrier
  Feb 22 15:19:05 lp1881207-upstream systemd-networkd[992]: ens8: DHCP lease 
lost
  Feb 22 15:19:05 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv6 lease 
lost

  [regression potential]

  any regression would likely involve an issue with dhcpv4 service;
  possibly not setting the mtu correctly, or possibly not completing
  dhcpv4 at all.

  [scope]

  this is not fixed upstream yet, so (once fixed upstream) it will be
  needed for b/f/g/h

  [original description]

  Running on a NUC (BOXNUC8i7BEH3).

  After updating the `systemd` package past `237-3ubuntu10.32`, I see
  the onboard NIC link being taken down / up repeatedly, as shown below
  (dates are from my original notes, but the issue remains the same
  today).

  The NIC fails to remain up, and all networking is out of action.

  Running `systemctl stop systemd-netword` stops this and leaves the NIC in an 
unknown state.
  Subsequently running `ifconfig eno1 up && dhclient eno1` allows networking to 
continue basic operation, albeit without systemd's oversight.

  My original solution was to downgrade both the `libsystemd0` and
  `systemd` packages to `237-3ubuntu10.28`.

  After attempting an `apt update && apt upgrade` again today, exactly
  the same thing is happening with `237-3ubuntu10.41`.

  Good versions:
  - 237-3ubuntu10.28
  - 237-3ubuntu10.32 (currently in use, and held)

  Bad versions:
  - 237-3ubuntu10.33
  - 237-3ubuntu10.38
  - 237-3ubuntu10.41

  dmesg:

  [  360.711367] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  360.714370] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  360.726189] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  361.733073] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  361.744146] e1000e :00:1f.6: Interrupt Throttle Rate on
  [  366.760198] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  366.763375] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  366.776060] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  367.781718] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  367.792796] e1000e :00:1f.6: Interrupt Throttle Rate on
  [  372.808660] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  

[Touch-packages] [Bug 1917677] Re: ubuntu: ucf tracking of valid known md5sums should be limited to only those md5sums that affect a given distro release

2022-01-26 Thread Brian Murray
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: unattended-upgrades (Ubuntu Hirsute)
   Status: New => Won't Fix

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

Title:
  ubuntu: ucf tracking of valid known md5sums   should be limited to
  only those md5sums that affect a given distro release

Status in unattended-upgrades package in Ubuntu:
  New
Status in unattended-upgrades source package in Bionic:
  New
Status in unattended-upgrades source package in Focal:
  New
Status in unattended-upgrades source package in Groovy:
  New
Status in unattended-upgrades source package in Hirsute:
  Won't Fix

Bug description:
  Currently the project tracks all valid md5sums of permutations of
  50unattended-upgrades.conf in a single md5sum file that contains every
  md5sum of every historic version of all unique distros:

   50unattended-upgrades.Debian
   50unattended-upgrades.Devuan
   50unattended-upgrades.Raspbian
   50unattended-upgrades.Ubuntu

  Ultimately ucf for a given packaging release should only track the
  applicable md5sums which are expected to be seen on that particular
  distribution and release.

  For example:
 On Ubuntu Bionic: valid md5sums should be limited to the md5sum of the 
most recent Ubuntu Xenial 50unattended-upgrades.conf and the md5sums of 
previous Ubuntu Bionic releases to allow Xenial->Bionic and Bionic->Bionic 
upgrades without prompt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1917677/+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 1923485] Re: unable to reconize Asgard NVME with short serial

2022-01-26 Thread Brian Murray
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  unable to reconize Asgard NVME with short serial

Status in curtin:
  New
Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Focal:
  New
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  New

Bug description:
  check this:
  
https://discourse.maas.io/t/unable-to-deploy-valueerror-failed-to-find-storage-volume-id-nvme0n1/4442/4

  Maybe the line os.listdir should be changed with os.walk to discover all 
child directories?
  Or maybe this is just a BUG of MAAS?

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1923485/+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 1928733] Re: Starting systemd Network Service fails with "Invalid argument"

2022-01-26 Thread Brian Murray
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: systemd (Ubuntu Hirsute)
   Status: Triaged => Won't Fix

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

Title:
  Starting systemd Network Service fails with "Invalid argument"

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in systemd source package in Focal:
  Triaged
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Triaged

Bug description:
  This server has a new install of Ubuntu 18.04 server. Sometimes
  (around 50% of the time) when it boots systemd-networkd.service
  initially fails to start with an error as below. It then tries again
  and succeeds, however other services which depend on systemd-networkd
  have already failed on the dependency by then.

  From the output of "journalctl -u systemd-networkd":

  -- Reboot --
  May 17 19:44:28 server1 systemd[1]: Starting Network Service...
  May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed to 
set up mount namespacing: Invalid argument
  May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed at 
step NAMESPACE spawning /lib/systemd/systemd-networkd: Invalid argument
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Main process 
exited, code=exited, status=226/NAMESPACE
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Failed with 
result 'exit-code'.
  May 17 19:44:30 server1 systemd[1]: Failed to start Network Service.
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Service has no 
hold-off time, scheduling restart.
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Scheduled 
restart job, restart counter is at 1.
  May 17 19:44:30 server1 systemd[1]: Stopped Network Service.
  May 17 19:44:30 server1 systemd[1]: Starting Network Service...
  May 17 19:44:30 server1 systemd-networkd[2321]: Enumeration completed
  May 17 19:44:30 server1 systemd[1]: Started Network Service.
  May 17 19:44:30 server1 systemd-networkd[2321]: eno2: IPv6 successfully 
enabled
  May 17 19:44:30 server1 systemd-networkd[2321]: eno1: Link is not managed by 
us
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not 
managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not 
managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: eno1: IPv6 successfully 
enabled
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not 
managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not 
managed by us
  May 17 19:44:31 server1 systemd-networkd[2321]: eno2: Link UP
  May 17 19:44:31 server1 systemd-networkd[2321]: eno1: Link UP
  May 17 19:44:34 server1 systemd-networkd[2321]: eno2: Gained carrier
  May 17 19:44:34 server1 systemd-networkd[2321]: eno1: Gained carrier
  May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Gained IPv6LL
  May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Configured
  May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Gained IPv6LL
  May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Configured

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.46
  ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18
  Uname: Linux 4.15.0-142-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  Date: Mon May 17 19:53:11 2021
  InstallationDate: Installed on 2021-03-18 (60 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R440
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic 
root=/dev/mapper/vg1-lv_root ro processor.max_cstate=1 intel_idle.max_cstate=0 
transparent_hugepage=never
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.9.3
  dmi.board.name: 04JN2K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.9.3:bd09/23/2020:svnDellInc.:pnPowerEdgeR440:pvr:rvnDellInc.:rn04JN2K:rvrA06:cvnDellInc.:ct23:cvr:
  

[Touch-packages] [Bug 1958806] Re: Fails to include libgcc, resulting in cryptsetup failures

2022-01-26 Thread Brian Murray
*** This bug is a duplicate of bug 1958594 ***
https://bugs.launchpad.net/bugs/1958594

** This bug has been marked a duplicate of bug 1958594
   Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

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

Title:
  Fails to include libgcc, resulting in cryptsetup failures

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I recently rebooted my laptop, and couldn't unlock my (cryptsetup-
  managed) root filesystem; after entering my passphrase, the plymouth
  prompt would always say “unable to unlock /dev/nvme0n1p3_crypt”.

  Dropping to text mode, I can see that cryptsetup is failing with a message 
like:
  "libgcc_s: missing library, needed for pthread_exit”.

  Indeed, in the recovery console cryptsetup will immediately crash with
  that message.

  I note that initramfs-tools already has some logic for detecting when
  libgcc_s is needed but isn't in DT_NEEDED, but this seems to have gone
  out of date.

  Adding an initramfs hook to manually add libgcc_s to the initramfs
  results in a bootable system again.

  I don't reboot this laptop often, so I unfortunately can't narrow down
  *when* this started failing better than “sometime in the last 2
  months”.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu10
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 24 12:08:34 2022
  InstallationDate: Installed on 2021-06-26 (211 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to jammy on 2021-10-28 (87 days ago)

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


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


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

2022-01-26 Thread Brian Murray
** Tags added: connection-refused

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

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

Status in apport package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in apport source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released

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


  top

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

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



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

[Touch-packages] [Bug 1958690] Re: initramfs-tools/0.136ubuntu6.6 ADT test failure with linux/5.4.0-97.110 (No space left on device)

2022-01-25 Thread Brian Murray
*** This bug is a duplicate of bug 1958904 ***
https://bugs.launchpad.net/bugs/1958904

** This bug has been marked a duplicate of bug 1958904
   autopkgtest is failing on jammy with "no space left on device"

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

Title:
  initramfs-tools/0.136ubuntu6.6 ADT test failure with
  linux/5.4.0-97.110 (No space left on device)

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This is a scripted bug report about ADT failures while running
  initramfs-tools tests for linux/5.4.0-97.110 on focal. Whether this is
  caused by the dep8 tests of the tested source or the kernel has yet to
  be determined.'

  Failing with "No space left on device"

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/i/initramfs-tools/20220120_163952_3eaab@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958690/+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 1958904] Re: autopkgtest is failing on jammy with "no space left on device"

2022-01-25 Thread Brian Murray
It looks like this also needs fixing in Focal see bug 1958690, which
I've marked as a duplicate of this.

** Also affects: initramfs-tools (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: initramfs-tools (Ubuntu Focal)
   Status: New => Triaged

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

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

Title:
  autopkgtest is failing on jammy with "no space left on device"

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Focal:
  Triaged

Bug description:
  In debian/tests/prep-image we create an image file of 1GB, but recent
  jammy cloud images are (barely) bigger than that, for example the
  current one uncompressed is 1001MB...

  Maybe we should consider to create image files of 2GB or even bigger,
  considering that we are only going to allocate the space that is
  actually needed, because we create the file using truncate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+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 1958312] Re: Livepatch not working on Ubuntu 22.04 LTS

2022-01-25 Thread Brian Murray
Do you have the canonical-livepatch snap installed?

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Livepatch not working on Ubuntu 22.04 LTS

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  No such file or directory error when I'll try to use livepatch on a
  22.04 device with dev updates enabled.

  It turns off automatically

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1958312/+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 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

2022-01-25 Thread Brian Murray
** Changed in: initramfs-tools (Ubuntu)
Milestone: None => ubuntu-22.02

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

Title:
  Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  [Bug description]

  On a jammy installation, which was upgraded from focal, after a full-
  upgrade and a reboot,

  I enter the LUKS password to decrypt the disk. Then I get the
  following error:

  libgcc_s.so.1 must be installed for pthread_exit to work

  After the error is shown, the system asks for the password again
  (which never works, always throwing the same error).

  [Root cause]

  I was able to decrypt the disk with the same password by booting from
  a live usb. Which allowed further investigation.

  The error shown in the LUKS password prompt menu comes from
  https://github.com/bminor/glibc/blob/glibc-2.34/nptl/pthread_exit.c#L31-L32, 
which indeed shows that pthread_exit fails when libgcc_s.so.1 is missing.

  From
  
https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/hook-functions?h=import/0.140ubuntu10#n260,
  we noticed that libgcc_s.so.1 is only copied if

  1) copy_exec is called for a binary directly linked to libgcc_s.so.1, or
  2) copy_exec is called for a binary linked to libpthread

  The cryptsetup initramfs hook, calls copy_exec for /sbin/cryptsetup,
  which is linked to libargon2.so.1, which is linked to libpthread.so.0.
  This covers case (2) above. As a consequence, libgcc_s.so.1 is copied
  to the initrd image and the error reported here is not seen.

  However, since glibc 2.34, libpthread is shipped within glibc, and the
  binaries are no longer linked to libpthread.so.0. As a consequence, an
  argon2 package built with glibc 2.32 will no longer be linked to
  libpthread.so.0 and libgcc_s.so.1 will no longer be copied to the
  initrd image. Triggering the reported error.

  This can be verified in these two argon2 builds, from the same
  sources, but with different glibc versions:

  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build21.04.0/+build/21066610
  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build22/+build/22255217

  Still lvm2 is a seeded package, which Recommends thin-provisioning-
  tools. thin-provisioning-tools ships a initramfs hook that calls
  copy_exec for /usr/sbin/pdata_tools, which is directly linked to
  libgcc_s.so.1. This covers the case (1) above and should suffice to
  ensure the boot process works properly.

  Since thin-provisioning-tools is just a recommends for lvm2, it could
  be removed from the system (and indeed, for some reason, was not
  present in my focal=>jammy installation). In this case, a new kernel
  installation should trigger the reported error.

  [Reproducer]

  - Install jammy with a LUKS encrypted disk
  - remove thin-provisioning-tools
  - perform a full-upgrade (make sure the kernel was upgraded or run 
update-initramfs manually)
  - reboot and verify you can no longer get past the decrypt password prompt 
screen

  [Workaround]

  A workaround for anyone affected would be to install thin-
  provisioning-tools and run update-initramfs.

  [Impact]

  Users upgrading from focal to jammy will eventually be locked out of
  their systems in case they are using LUKS encryption.

  [Additional information]

  While this issue is similar to
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861757,
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254, and
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950551,
  This is a different bug, with a different root cause.

  Thanks to sergiodj for the pairing session on the root cause analysis.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958594/+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 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders

2022-01-24 Thread Brian Murray
** Tags added: rls-jj-incoming

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

Title:
  Jammy builds of xen segfault, but only on launchpad x86 builders

Status in launchpad-buildd:
  New
Status in binutils package in Ubuntu:
  New
Status in xen package in Ubuntu:
  Invalid

Bug description:
  FTBFS in Jammy on LP infra:
  
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
  
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
  Related PPA:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages

  Summary:
  - Build reliably fails on LP
  - Build in local sbuild works reliably on my Laptop
  - Build in local VM (sizing like LP builders) works (other crashes but works)
  - Build on AMD server (chip more similar to LP) works reliably

  Failing step:

  On Launchpad build infrastructure it breaks on ld:
  $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 
--image-base=0x82d04000 --stack=0,0 --heap=0,0 
--section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 
--minor-image-version=16 --major-os-version=2 --minor-os-version=0 
--major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp 
--build-id=sha1 -T efi.lds -N prelink.o  
/<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o 
/<>/xen/.xen.efi.0x82d04000.0 && :
  Segmentation fault (core dumped

  ---

  Steps to recreate (result depends on platform)

  # you can grab the package from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/4760/+packages

  sudo vim /etc/apt/sources.list
  sudo apt update
  sudo apt dist-upgrade -y
  sudo apt build-dep xen
  sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts 
apport-retrace
  sudo mkdir /mnt/build
  sudo chmod go+w /mnt/build
  cd  /mnt/build
  # copy in things from host
  scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc 
xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 
ubuntu@:/mnt/build
  dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0
  cd xen_4.16.0
  dpkg-buildpackage -i -us -uc -b

  ---

  In a jammy VM 4cpu/8G I get some avx2 crashes but the build works:

  Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 
7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000]
  Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 
1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 
00  fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66

  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
  (gdb) bt
  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  #1  0x7fa98d63c2d0 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #2  0x7fa98d6021e8 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #3  0x7fa98d602509 in coff_write_alien_symbol () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #4  0x7fa98d6033bd in _bfd_coff_final_link () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #5  0x562bdaaae3bf in ?? ()
  #6  0x7fa98d2e8fd0 in __libc_start_call_main 
(main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, 
argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58
  #7  0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, 
argc=8, argv=0x7ffc797f2968, init=, fini=, 
rtld_fini=, 
  stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409
  #8  0x562bdaaad515 in ?? ()

  ^^ that is a different crash than on th LP builders
  ! And despite those crashes the build does appear to work oO?!

  The same crashes I see on my local sbuild runs, the full set of one build is
  Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 
ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in 
libc.so.6[7f566e74+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 
ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in 
libc.so.6[7fbba2571000+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 
ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in 
libc.so.6[7fe368044000+194000]
  Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 
ip 7f241f455f3d sp 7ffd05c2e7c8 error 4 in 
libc.so.6[7f241f2e2000+194000]
  Jan 19 07:44:57 Keschdeichel kernel: x86_64-linux-gn[4171794]: segfault at 0 
ip 7fcbe1f2bf3d sp 7fff62005aa8 error 4 in 
libc.so.6[7fcbe1db8000+194000]
  Jan 19 07:44:57 Keschdeichel kernel: x86_64-linux-gn[4172028]: segfault at 0 
ip 7f601dfa3f3d sp 

[Touch-packages] [Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy

2022-01-24 Thread Brian Murray
** Tags added: rls-jj-incoming

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

Title:
  python3-yaml and python3-six are not co-installable with python-is-
  python2 in jammy

Status in pyyaml package in Ubuntu:
  In Progress
Status in six package in Ubuntu:
  New

Bug description:
  The packages python3-yaml and python-is-python2 are not co-installable
  in jammy and I believe they should be.  This currently prevents me
  from upgrading one of my machines from focal to jammy.

  Further analysis with the help of Stefano Rivera revealed that what-
  is-python no longer produces a python-is-python2 package and the
  changelog hints at that being intentional.  Jammy still has a python2
  package, though.

  python3-yaml in jammy breaks on python (<2.7.18).  The python-is-
  python2 package in focal is version 2.7.17-4 and in impish it is
  2.7.18-9 and thus will be forcefully removed when going to jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+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 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland

2022-01-20 Thread Brian Murray
** Tags added: fr-1989

** Also affects: apport (Ubuntu Jammy)
   Importance: Medium
   Status: Confirmed

** Also affects: x11-utils (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Tags removed: rls-jj-incoming

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

** Also affects: x11-utils (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

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

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

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

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

Title:
  ubuntu-bug -w (using xprop) doesn't work under wayland

Status in apport package in Ubuntu:
  Triaged
Status in x11-utils package in Ubuntu:
  New
Status in apport source package in Impish:
  Triaged
Status in x11-utils source package in Impish:
  New
Status in apport source package in Jammy:
  Triaged
Status in x11-utils source package in Jammy:
  New

Bug description:
  I want to report a Bug about the application Studio Controls.

  As I did it already quite a few times, I run "ubuntu-bug -w", get a
  message that I can select the window of the app I want to report a bug
  about after closing this message.

  I close the message with a click on the appropriate button.

  I click on the window of the application "Studio Controls" that I want
  to report a bug about.

  Nothing happens.

  I wait for a few minutes. Still nothing happens.

  In the console where I started ubuntu-bug -w I see the following
  message:

  (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed


  What I expect:

  Usaully when I use this procedure, after a relatively short while a
  new message window pops up asking me if the bug should be reported and
  showing me the data that is sent to Launchpad.

  I tried other applications, too, same effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apport 2.20.11-0ubuntu71
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  1 20:01:23 2021
  InstallationDate: Installed on 2020-04-12 (597 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+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 1958284] Re: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec

2022-01-20 Thread Brian Murray
** Tags added: fr-1987

** Tags removed: fr-1987 rls-ff-incoming

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

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

Title:
  shutdown hangs at "Waiting for process: ..." for 90s, ignoring
  DefaultTimeoutStopSec

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

Bug description:
  With systemd v245 as shipped with 20.04, the shutdown sequence does
  not use the value of `DefaultTimeoutStopSec` to wait for remaining
  processes, it instead uses the compiled in default of 90s.

  This is most visible with services that use `KillMode=process`
  (docker, k8s, k3s, etc...), especially if the remaining processes do
  not handle `SIGTERM` or choose to ignore it.

  For example:
  ```
  [ OK ] Finished Reboot.
  [ OK ] Reached target Reboot.
  [ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim, 
containerd-shim, containerd-shim, fluent-bit

  --- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower
  value ---

  ```

  The bug has been fixed upstream here:
  https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22

  Marc was kind enough to package the patch for 20.04 so I could test it
  
(https://launchpad.net/~mdeslaur/+archive/ubuntu/testing/+sourcepub/13210617/+listing-
  archive-extra) and with that package, I can confirm that it indeed
  fixes the issue.

  Here's a few github issues I stumbled upon while trying to debug this,
  along with a short writeup of the workaround I ended up using:

  - https://github.com/moby/moby/issues/41831
  - https://github.com/k3s-io/k3s/issues/2400
  - https://github.com/systemd/systemd/issues/16991
  - https://raby.sh/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html

  Of course, it would be much better if all the processes would properly
  handle `SIGTERM`, but having a way to enforce a maximum wait time at
  shutdown is a decent workaround.

  Given that the patch is relatively simple, would it be possible to add
  it the package for 20.04?

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1958284/+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 1952947] Re: ubuntu-bug -w doesn't work under wayland

2022-01-19 Thread Brian Murray
** Also affects: x11-utils (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- ubuntu-bug -w doesn't work under wayland
+ ubuntu-bug -w (using xprop) doesn't work under wayland

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

Title:
  ubuntu-bug -w (using xprop) doesn't work under wayland

Status in apport package in Ubuntu:
  Confirmed
Status in x11-utils package in Ubuntu:
  New

Bug description:
  I want to report a Bug about the application Studio Controls.

  As I did it already quite a few times, I run "ubuntu-bug -w", get a
  message that I can select the window of the app I want to report a bug
  about after closing this message.

  I close the message with a click on the appropriate button.

  I click on the window of the application "Studio Controls" that I want
  to report a bug about.

  Nothing happens.

  I wait for a few minutes. Still nothing happens.

  In the console where I started ubuntu-bug -w I see the following
  message:

  (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed


  What I expect:

  Usaully when I use this procedure, after a relatively short while a
  new message window pops up asking me if the bug should be reported and
  showing me the data that is sent to Launchpad.

  I tried other applications, too, same effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apport 2.20.11-0ubuntu71
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  1 20:01:23 2021
  InstallationDate: Installed on 2020-04-12 (597 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+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 1952947] Re: ubuntu-bug -w doesn't work under wayland

2022-01-19 Thread Brian Murray
Manually testing xwininfo and xprop it seems that neither of them work
under Wayland. The cursor never changes shape and clicking on a window
does nothing.

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

Title:
  ubuntu-bug -w doesn't work under wayland

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I want to report a Bug about the application Studio Controls.

  As I did it already quite a few times, I run "ubuntu-bug -w", get a
  message that I can select the window of the app I want to report a bug
  about after closing this message.

  I close the message with a click on the appropriate button.

  I click on the window of the application "Studio Controls" that I want
  to report a bug about.

  Nothing happens.

  I wait for a few minutes. Still nothing happens.

  In the console where I started ubuntu-bug -w I see the following
  message:

  (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed


  What I expect:

  Usaully when I use this procedure, after a relatively short while a
  new message window pops up asking me if the bug should be reported and
  showing me the data that is sent to Launchpad.

  I tried other applications, too, same effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apport 2.20.11-0ubuntu71
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  1 20:01:23 2021
  InstallationDate: Installed on 2020-04-12 (597 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+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 1817946] Re: package linux-image-4.15.0-45-generic 4.15.0-45.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-01-18 Thread Brian Murray
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update a package on your system due to a lack of free space on
your system.  Please resolve this situation manually and try the update
again.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

** Tags added: no-free-space

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

Title:
  package linux-image-4.15.0-45-generic 4.15.0-45.48 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  package linus-image-4.15.0-45-generic 4.15.0-45.48 failed to
  install/upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1176 F pulseaudio
namirasalm   1548 F pulseaudio
   /dev/snd/controlC0:  gdm1176 F pulseaudio
namirasalm   1548 F pulseaudio
  Date: Tue Feb 26 00:16:03 2019
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=49e290fc-e6be-4c95-9a10-3f1c79417eab
  InstallationDate: Installed on 2018-10-23 (127 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80XU
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=54d2d971-1eed-45d6-a46f-e5ba244f02ea ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.6
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-45-generic 4.15.0-45.48 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5PCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55731WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-14AST
  dmi.modalias: 
dmi:bvnLENOVO:bvr5PCN24WW:bd10/29/2018:svnLENOVO:pn80XU:pvrLenovoideapad320-14AST:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55731WIN:cvnLENOVO:ct10:cvrLenovoideapad320-14AST:
  dmi.product.family: ideapad 320-14AST
  dmi.product.name: 80XU
  dmi.product.version: Lenovo ideapad 320-14AST
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1817946/+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 1858631] Re: package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-01-18 Thread Brian Murray
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update the kernel on your system due to a lack of free space
in your boot partition.  Please resolve this situation manually and try
the update again.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

** Tags added: no-boot-space

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

Title:
  package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  cannot boot after upgrade 
  now using previous kernel (4.4.0-91)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  erbe01 1836 F pulseaudio
gdm2094 F pulseaudio
   /dev/snd/controlC1:  erbe01 1836 F pulseaudio
gdm2094 F pulseaudio
  Date: Tue Jan  7 15:09:54 2020
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=/dev/mapper/EC--WEB01--vg-swap_1
  MachineType: Dell Inc. Vostro 3650
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic 
root=/dev/mapper/EC--WEB01--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.23
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.2.4
  dmi.board.name: 0VGHXY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.2.4:bd06/17/2016:svnDellInc.:pnVostro3650:pvrX00:rvnDellInc.:rn0VGHXY:rvrA01:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Vostro 3650
  dmi.product.version: X00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1858631/+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 1948575] Re: package linux-firmware 1.187.19 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

2022-01-18 Thread Brian Murray
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update a package on your system due to a lack of free space on
your system.  Please resolve this situation manually and try the update
again.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

** Tags added: no-free-space

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

Title:
  package linux-firmware 1.187.19 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  verly long and old maintained authentication keys in trusted software
  repository of ubuntu software updater.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.19
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arun   1871 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Oct 24 15:12:21 2021
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-09-08 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 80T7
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic 
root=UUID=99f31926-b2b0-4b03-a8ba-a15f3b4a9fcd ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.19 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 1GCN15WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: 00RD15IPG076
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15IBR
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnLENOVO:bvr1GCN15WW:bd04/07/2016:br1.15:efr1.15:svnLENOVO:pn80T7:pvrLenovoideapad110-15IBR:skuLENOVO_MT_80T7_BU_idea_FM_Lenovoideapad110-15IBR:rvnLENOVO:rn00RD15IPG076:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad110-15IBR:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80T7
  dmi.product.sku: LENOVO_MT_80T7_BU_idea_FM_Lenovo ideapad 110-15IBR
  dmi.product.version: Lenovo ideapad 110-15IBR
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1948575/+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 1879449] Re: package linux-image-5.4.0-31-generic 5.4.0-31.35 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-01-18 Thread Brian Murray
I wonder if our installation process is creating /boot partitions that
are too small for kernel upgrades. Could you provide some information
about how you installed Ubuntu? Did you use the desktop or server
installer? Did you use the guided installation process or something
else?  Thanks in advance!

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package linux-image-5.4.0-31-generic 5.4.0-31.35 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  I got a warning message that partition /boot does not have enough disk
  space while I was updating the system using apt update / apt upgrade.
  Then the update failed and I got an error message as shown in the
  attached screenshot.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmedelhosseiny   2397 F pulseaudio
  CRDA:
   global
   country EG: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (N/A, 20), (N/A)
(5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS
  CasperMD5CheckResult: skip
  Date: Tue May 19 09:08:03 2020
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2020-04-27 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Latitude E5570
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=59a72f08-8b23-4827-a49c-b82fb036be27 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  SourcePackage: initramfs-tools
  Title: package linux-image-5.4.0-31-generic 5.4.0-31.35 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/07/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.6
  dmi.board.name: 0GF89W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.6:bd02/07/2017:svnDellInc.:pnLatitudeE5570:pvr:rvnDellInc.:rn0GF89W:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E5570
  dmi.product.sku: 06DF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879449/+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 1898482] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-01-18 Thread Brian Murray
Could you please run 'apport-collect 1898482' in a terminal? This will
gather log files related to your upgrade which will be helpful in
determining what went wrong.

** Package changed: initramfs-tools (Ubuntu) => ubuntu-release-upgrader
(Ubuntu)

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: New => Incomplete

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

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete

Bug description:
  do-release-upgrade said it would need 1.5G free diskspace, used 1.7G
  and the disk was then full.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
  Uname: Linux 4.15.0-118-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Oct  4 20:45:27 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-10-04 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898482/+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 1938056] Re: failed on install from USB boot install media

2022-01-18 Thread Brian Murray
Updating the kernel on a live media isn't supported.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  failed on install from USB boot install media

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  error message after install

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jul 26 08:23:41 2021
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1938056/+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 1942119] Re: package linux-image-5.11.0-33-generic 5.11.0-33.35 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-01-18 Thread Brian Murray
I'm curious about how you installed Ubuntu as there may be an issue with
the installation process creating too small of a /boot partition. What
version of Ubuntu did you first install and how did you setup the
partition of your disk? Did you allow the installer to set it up? Thanks
in advance.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  package linux-image-5.11.0-33-generic 5.11.0-33.35 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  out of space on boot

  ProblemType: Package
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-33-generic 5.11.0-33.35
  ProcVersionSignature: Ubuntu 5.11.0-26.28-generic 5.11.22
  Uname: Linux 5.11.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  AptOrdering:
   linux-image-5.11.0-34-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ed 3762 F pulseaudio
   /dev/snd/controlC0:  ed 3762 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Mon Aug 30 12:49:06 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=d2593ab0-191d-4408-97ee-05d6ed8ca557
  InstallationDate: Installed on 2018-06-24 (1163 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-26-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: initramfs-tools
  Title: package linux-image-5.11.0-33-generic 5.11.0-33.35 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.00
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.00:bd07/13/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942119/+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 1829397] Re: package linux-image-4.4.0-148-generic 4.4.0-148.174 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-01-18 Thread Brian Murray
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update a package on your system due to a lack of free space on
your system.  Please resolve this situation manually and try the update
again.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

** Tags added: no-free-space

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

Title:
  package linux-image-4.4.0-148-generic 4.4.0-148.174 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Server reported error - package linux-image-4.4.0-148-generic
  4.4.0-148.174 failed to install/upgrade: run-parts:
  /etc/kernel/postinst.d/initramfs-tools exited with return code 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-148-generic 4.4.0-148.174
  ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
  Uname: Linux 4.4.0-146-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu May 16 06:22:57 2019
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2016-09-21 (967 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-148-generic 4.4.0-148.174 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829397/+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 1824617] Re: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2022-01-18 Thread Brian Murray
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update the kernel on your system due to a lack of free space
in your boot partition.  Please resolve this situation manually and try
the update again.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

** Tags added: no-boot-space

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

Title:
  package linux-firmware 1.157.21 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  when I switched on computer a propmt occured and thats it

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.21
  ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   initramfs-tools: Configure
   linux-firmware: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Apr 13 13:47:51 2019
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-01-13 (454 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1824617/+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 1884082] Re: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-01-18 Thread Brian Murray
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update a package on your system due to a lack of free space on
your system.  Please resolve this situation manually and try the update
again.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

** Tags added: no-free-space

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

Title:
  package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Popped up just like dat. Had boot problems just befo dat du 2 2 less
  space. Keep up da gud work. Peace!

  Ps: sry fo ma dumb langauge.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-37-generic 5.4.0-37.41
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cellardoor   1500 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Jun 17 12:16:57 2020
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2020-05-28 (20 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 004: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
   |__ Port 2: Dev 4, If 0, Class=Human Interface Device, 
Driver=usbhid, 1.5M
  MachineType: LENOVO 4243W4K
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=2115cb1b-ab29-42d1-8560-2ded1bfc06c3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  SourcePackage: initramfs-tools
  Title: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET65WW (1.45 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4243W4K
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET65WW(1.45):bd05/14/2015:svnLENOVO:pn4243W4K:pvrThinkPadT520:rvnLENOVO:rn4243W4K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T520
  dmi.product.name: 4243W4K
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1884082/+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 1879421] Re: update-initramfs doesn't consider free space in /var/tmp

2022-01-18 Thread Brian Murray
** Summary changed:

- package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed 
initramfs-tools package post-installation script subprocess returned error exit 
status 1
+ update-initramfs doesn't consider free space in /var/tmp

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

Title:
  update-initramfs doesn't consider free space in /var/tmp

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Low disk space in /var/tmp mount causes post-installation script to
  fail. It should probably detect it.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: initramfs-tools 0.133ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-1023.25-raspi2 5.3.18
  Uname: Linux 5.3.0-1023-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: arm64
  Date: Tue May 19 00:23:34 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to eoan on 2020-05-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879421/+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 1845836] Re: package linux-image-4.4.0-164-generic 4.4.0-164.192 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-01-18 Thread Brian Murray
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update the kernel on your system due to a lack of free space
in your boot partition.  Please resolve this situation manually and try
the update again.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

** Tags added: no-boot-space

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

Title:
  package linux-image-4.4.0-164-generic 4.4.0-164.192 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  no

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-164-generic 4.4.0-164.192
  Uname: Linux 4.8.0-040800-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Fri Sep 27 18:57:03 2019
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-07-05 (451 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.29ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-164-generic 4.4.0-164.192 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1845836/+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 1892143] Re: package linux-image-4.4.0-189-generic 4.4.0-189.219 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-01-18 Thread Brian Murray
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update the kernel on your system due to a lack of free space
in your boot partition.  Please resolve this situation manually and try
the update again.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

** Tags added: no-boot-space

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

Title:
  package linux-image-4.4.0-189-generic 4.4.0-189.219 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  it is not upgrading

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-189-generic 4.4.0-189.219
  ProcVersionSignature: Ubuntu 4.4.0-187.217-generic 4.4.230
  Uname: Linux 4.4.0-187-generic i686
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pawan  1835 F pulseaudio
  Date: Wed Aug 19 13:27:54 2020
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=8fa258f5-01b1-490e-a55d-4abf285935f3
  InstallationDate: Installed on 2015-12-13 (1710 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: Dell Inc. Inspiron 3252
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-187-generic 
root=UUID=28a6ff81-c9aa-4f94-af2c-1ce175675fd6 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.27
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-189-generic 4.4.0-189.219 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2020-07-30 (19 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.6
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.6:bd12/07/2015:svnDellInc.:pnInspiron3252:pvr2.3.6:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.3.6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1892143/+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 1955797] Re: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.

2022-01-18 Thread Brian Murray
Hello Jerry, or anyone else affected,

Accepted network-manager into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.22.10-1ubuntu2.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-
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: network-manager (Ubuntu Focal)
   Status: New => Fix Committed

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

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

Title:
  [SRU] network-manager can’t modify MTU automatically based on what
  ModemManager exposes for WWAN modems.

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Some 4G/5G mobile networks(for ex., AT) requires a specific MTU
  setting, this setting will be exposed by the ModemManager for network-
  manger to configure the MTU of the modem network interface .

  The current modem-manager v1.22.10-1ubuntu2.2  in focal can’t pass
  AT’s modem system certification.

  [Fix]

  This upstream patch can resolve this bug:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631

  [Test Plan]

  1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an
  AT SIM card in US

  2. Enable 4G modem and connect to AT apn

  $ sudo mmcli -i 0 --pin=
  $ sudo mmcli --modem 0 --enable
  $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome"
  $ sudo nmcli radio wwan on
  $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn 
emome
  $ sudo nmcli connection up id mymodem

  3. Check if the MTU got from the following results are the same:

  $ sudo mmcli --bearer 5 | mtu
  $ ifconfig mhi_mbim0 | grep mtu

  * Expected result:
  Both MTUs are the same value 1430
  * Actual tested result:
  Different values (one is 1430 , another is 1500)

  [Where problems could occur]

  Very low.
  This is a simple fix: network-manager gets the MTU from the ModemManager then 
sets the MTU of the modem interface.

  [Other info]

  1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+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 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else

2022-01-18 Thread Brian Murray
Hello Stefano, or anyone else affected,

Accepted gtk+3.0 into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.30-1ubuntu1.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: gtk+3.0 (Ubuntu Impish)
   Status: New => Fix Committed

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

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

Title:
  Copy from Firefox Wayland fails to be pasted anywhere else

Status in GTK+:
  Unknown
Status in firefox package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Impish:
  Fix Committed

Bug description:
  * Impact

  The clipboard copies from GTK based software sometime stop working
  under wayland

  * Test Case

  - in a wayland session try to copy text between software, from firefox
  to gedit for example, it should work in a consistent manner

  alternative testcase inspired from the gitlab ticket
  - install wl-clipboard
  - use evince to open a pdf
  - select and copy some content
  - on a cmdline do 
  $ wl-paste -t TEXT
  - try to paste then in another software, gedit for example

  the copied text should be pasted

  
  * Regression potential

  The changes are in the wayland selection source so the impact should
  only be for wayland users and limited to clipboard interactions

  
  --

  
  Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on 
Wayland native

  Version   84.0.2
  Build ID  20210105180113

  Window Protocol   wayland
  Desktop Environment   gnome

  DESCRIPTION OF THE PROBLEM:

  If I copy text from a web page and try to paste it into another
  Firefox page, the text is pasted correctly.

  If I copy text from a web page and try to paste it in [gedit,
  libreoffice, thunderbird, terminal, slack (electron)] nothing happens.
  The Gnome Clipboard extension stays empty when content is copied from
  Firefox Wayland.

  Pasting *from* another app *to* Firefox works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1913775/+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 1956831] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-01-17 Thread Brian Murray
It looks like the last time we updated /boot partition sizing used by
the install was with the Artful (17.10) release of Ubuntu, so your
install was well before this and likely has small /boot partition. Given
that we can't do anything about the already installed system I'm going
to close this as Invalid. Thanks for getting back to us!

** Changed in: initramfs-tools (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Happened during do-release-upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
  Uname: Linux 4.15.0-166-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jan  8 18:54:36 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-10-04 (2288 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2022-01-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1956831/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts

2022-01-17 Thread Brian Murray
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

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

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Incomplete
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in gdb source package in Focal:
  Fix Committed
Status in glibc source package in Focal:
  Fix Committed
Status in gdb source package in Groovy:
  Won't Fix
Status in glibc source package in Groovy:
  Won't Fix
Status in gdb source package in Hirsute:
  Won't Fix
Status in glibc source package in Hirsute:
  Won't Fix
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Released

Bug description:
  [Impact]

  * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is
  not installed.

  [Test Plan]

  * Check that ld.so is not stripped on armhf:
  $  /lib/*/ld-2.31.so
  libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, 
EABI5 version 1 (SYSV), dynamically linked, 
BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not 
stripped

  * Check that ld.so is stripped on amd64:

  $ file /lib/x86_64-linux-gnu/ld-2.31.so
  /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, 
version 1 (SYSV), dynamically linked, 
BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped

  [Where problems could occur]

  * The fix is not stripping ld.so on armhf. Not stripping it comes with
  a notable increase in file size and it may be performance critical
  109K stripped vs 1.3M unstripped. Accidentally ld.so could be left
  unstripped on other architectures, but the test plan covers checking
  that, at least on amd64. Other than those not stripping ld.so should
  not cause any issue.

  [Original Bug Text]

  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1927192/+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 1958060] Re: bash returns wrong variable value/call more proccesses?

2022-01-17 Thread Brian Murray
Trusty is no longer a supported release of Ubuntu. Have you tested this
with a supported release of Ubuntu? If so what version of bash were you
using?

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

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

Title:
  bash returns wrong variable value/call more proccesses?

Status in bash package in Ubuntu:
  Incomplete

Bug description:
  Simple function gives different results when interpretator set in first 
string of script
  CHECKPROC()
  {
  i=$(ps aux | grep -c $0)
  ps aux | grep -c $0
  echo variable is $i
  sleep 10
  }
  CHECKPROC

  Expected
  In any conditions it will return same values, then will increments when other 
copies of script  will be found in proccesses list.

  Happened.
  We set interpretator with #!/bin/bash or #!/bin/sh in first string of script 
and runs multiple copies of script from one terminal with & after scriptname. 
It's returns "1" and "variable is 1" always.
  Without interpretator setup, when string #!/bin/bash or #!/bin/sh deleted.
  Run multiple copies scriptname.sh&
  On every iteration it returns right first value and "variable is $value+1"

  $scriptname.sh&
  2
  variable is 3
  $scriptname.sh&
  3
  variable is 4
  ...and so on.

  Without counting in first case it returns only string with grep, in
  second case -- one more string with different PID and script name when
  called from i=$(...) or i=`...`

  
  Ubuntu 14.04 x32, bash 4.3.11(1)-release
  Same results from other man on
  GNU bash, version 5.1.16(1)-release (aarch64-apple-darwin21.1.0)
  GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)

  
  lsb_release -rd
  Description:  Ubuntu 14.04.6 LTS
  Release:  14.04

  apt-cache policy bash
  bash:
Установлен: 4.3-7ubuntu1.7
Кандидат:   4.3-7ubuntu1.7
Таблица версий:
   4.3-7ubuntu1.8+esm1 0
 -32768 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main i386 
Packages
   *** 4.3-7ubuntu1.7 0
  500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
  100 /var/lib/dpkg/status
   4.3-6ubuntu1 0
  500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1958060/+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 1938229] Re: ubuntu-bug -w crashes

2022-01-14 Thread Brian Murray
*** This bug is a duplicate of bug 1952947 ***
https://bugs.launchpad.net/bugs/1952947

** This bug has been marked a duplicate of bug 1952947
   ubuntu-bug -w doesn't work under wayland

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

Title:
  ubuntu-bug -w crashes

Status in apport package in Ubuntu:
  New

Bug description:
  When running ubuntu-bug -w i get the dialog that tells me to select
  the window to report a bug about, but after clicking this window, in
  the terminal where I started ubuntu-bug -w, i only get:

  
  (apport-gtk:26977): Gdk-CRITICAL **: 00:11:09.451: 
gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 
'GDK_IS_WAYLAND_WINDOW (window)' failed
  Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 597, in 
  app.run_argv()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 745, in run_argv
  _('xprop failed to determine process ID of the window') + '\n\n' + err)
  TypeError: can only concatenate str (not "bytes") to str

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: apport 2.20.11-0ubuntu65.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-lowlatency 5.11.22
  Uname: Linux 5.11.0-25-lowlatency x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 28 00:12:06 2021
  InstallationDate: Installed on 2020-04-12 (470 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to hirsute on 2021-07-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1938229/+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 1951647] Re: package nvidia-kernel-common-470 470.82.00-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-kernel-common-470 package post-installation script subprocess

2022-01-14 Thread Brian Murray
I noticed that your boot partition is full. Could you provide the output
of "ls -l /boot"? Additionally, how did you install Ubuntu?

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  package nvidia-kernel-common-470 470.82.00-0ubuntu0.20.04.1 failed to
  install/upgrade: installed nvidia-kernel-common-470 package post-
  installation script subprocess returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  potentially due to full ZFS boot Partition

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-common-470 470.82.00-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Nov 16 22:35:00 2021
  ErrorMessage: installed nvidia-kernel-common-470 package post-installation 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2021-04-12 (221 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  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: initramfs-tools
  Title: package nvidia-kernel-common-470 470.82.00-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-kernel-common-470 package post-installation 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1951647/+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 1952713] Re: package linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-01-14 Thread Brian Murray
I noticed that your boot partition is full. Could you provide the output
of "ls -l /boot"? Additionally, how did you install Ubuntu?

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  After update I received "report problem" dialog with info:
  package linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Nov 30 06:12:46 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-09-01 (89 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: initramfs-tools
  Title: package linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1952713/+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 1953171] Re: package linux-image-5.13.0-1011-raspi 5.13.0-1011.13 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-01-14 Thread Brian Murray
>From DpkgTerminalLog.txt:

Processing triggers for initramfs-tools (0.140ubuntu6) ... 
update-initramfs: Generating /boot/initrd.img-5.11.0-1023-raspi
Killed
E: mkinitramfs failure zstd -q -19 -T0 137 
update-initramfs: failed for /boot/initrd.img-5.11.0-1023-raspi with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
Processing triggers for dbus (1.12.20-2ubuntu2) ... 
Processing triggers for linux-image-5.13.0-1011-raspi (5.13.0-1011.13) ... 
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.13.0-1011-raspi
Killed
E: mkinitramfs failure zstd -q -19 -T0 137 
update-initramfs: failed for /boot/initrd.img-5.13.0-1011-raspi with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.13.0-1011-raspi (--configure):
 installed linux-image-5.13.0-1011-raspi package post-installation script 
subprocess returned error exit status 1


** Tags added: raspi

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

Title:
  package linux-image-5.13.0-1011-raspi 5.13.0-1011.13 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  While upgrading my Raspberry Pi 3 running 21.04 to 21.10, the upgrade
  failed

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-1011-raspi 5.13.0-1011.13
  ProcVersionSignature: Ubuntu 5.11.0-1023.25-raspi 5.11.22
  Uname: Linux 5.11.0-1023-raspi aarch64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Fri Dec  3 03:19:32 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.13.0-1011-raspi 5.13.0-1011.13 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to impish on 2021-12-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1953171/+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 1953722] Re: package linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

2022-01-14 Thread Brian Murray
*** This bug is a duplicate of bug 1953721 ***
https://bugs.launchpad.net/bugs/1953721

** This bug has been marked a duplicate of bug 1953721
   package linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to 
install/upgrade: проблемы зависимостей — оставляем не настроенным

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

Title:
  package linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to
  install/upgrade: проблемы зависимостей — оставляем не настроенным

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  -(

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-generic-hwe-20.04 5.11.0.41.45~20.04.19
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  AptOrdering:
   linux-headers-5.8.0-59-generic:amd64: Remove
   linux-hwe-5.8-headers-5.8.0-59:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Dec  9 10:42:13 2021
  ErrorMessage: проблемы зависимостей — оставляем не настроенным
  InstallationDate: Installed on 2020-07-09 (517 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details:
   Error: command ['readlink', '-f', "ERROR: ld.so: object 'libesets_pac.so' 
from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): 
ignored.\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object 
'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open 
shared object file): ignored.
   , Error: [Errno 2] Нет такого файла или каталога: 'Error: command 
[\'readlink\', \'-f\', "ERROR: ld.so: object \'libesets_pac.so\' from 
/etc/ld.so.preload cannot be preloaded (cannot open shared object file): 
ignored.\\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object 
\'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open 
shared object file): ignored.\n', unpackaged
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to 
install/upgrade: проблемы зависимостей — оставляем не настроенным
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1953722/+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 1955068] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 12

2022-01-14 Thread Brian Murray
>From DpkgTerminalLog.txt:

Processing triggers for initramfs-tools (0.136ubuntu6.6) ... 
/usr/sbin/update-initramfs: 202: awk: Too many levels of symbolic links
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 127

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

Title:
  package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 127

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting...
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Dec 16 06:15:30 2021
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 127
  InstallationDate: Installed on 2021-12-05 (11 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  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: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1955068/+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 1955562] Re: package linux-image-5.11.0-43-generic 5.11.0-43.47~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-01-14 Thread Brian Murray
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update a package on your system due to a lack of free space on
your system.  Please resolve this situation manually and try the update
again.

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

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

** Tags added: no-free-space

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

Title:
  package linux-image-5.11.0-43-generic 5.11.0-43.47~20.04.2 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Suddenly this error creeps in out of no where.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-43-generic 5.11.0-43.47~20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Dec 17 06:38:11 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-12-03 (17 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: initramfs-tools
  Title: package linux-image-5.11.0-43-generic 5.11.0-43.47~20.04.2 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1955562/+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 1956523] Re: package linux-image-5.11.0-44-generic 5.11.0-44.48~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-01-14 Thread Brian Murray
I noticed that your boot partition is full. Could you provide the output
of "ls -l /boot"? Additionally, how did you install Ubuntu?

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  package linux-image-5.11.0-44-generic 5.11.0-44.48~20.04.2 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  I'm running low on /boot and have always to "sudo apt autoremove"
  beforehand ... this time it created this error even with cleaning.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-44-generic 5.11.0-44.48~20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jan  5 21:21:08 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-09-27 (100 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: initramfs-tools
  Title: package linux-image-5.11.0-44-generic 5.11.0-44.48~20.04.2 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1956523/+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 1956404] Re: package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

2022-01-14 Thread Brian Murray
You seem to have run out of space on your disk. This is something you'll
need to resolve before package operations will succeed.

Setting up linux-firmware (1.187.24) ... 
update-initramfs: Generating /boot/initrd.img-5.11.0-43-generic
cp: error writing '/var/tmp/mkinitramfs_rPuC22//usr/lib/systemd/systemd-udevd': 
No space left on device
E: /usr/share/initramfs-tools/hooks/udev failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.11.0-43-generic with 1.
dpkg: error processing package linux-firmware (--configure):
 installed linux-firmware package post-installation script subprocess returned 
error exit status 1


** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  package linux-firmware 1.187.24 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  na

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.24
  ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Tue Jan  4 19:46:50 2022
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PackageArchitecture: all
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-43-generic 
root=PARTUUID=3e5a9664-db4e-4d98-b48a-7cc19a4e843b ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.24 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2021
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 1609-2687-7949-1311-7755-6991-40
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.1
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.1:bd05/05/2021:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:skuNone:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.1
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1956404/+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 1956831] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-01-14 Thread Brian Murray
I noticed that your boot partition is full. Could you provide the output
of "ls -l /boot"? Additionally, how did you install Ubuntu?

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  Happened during do-release-upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
  Uname: Linux 4.15.0-166-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jan  8 18:54:36 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-10-04 (2288 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2022-01-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1956831/+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 1956835] Re: package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

2022-01-14 Thread Brian Murray
I noticed that your boot partition is full. Could you provide the output
of "ls -l /boot"? Additionally, how did you install Ubuntu?

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  package linux-firmware 1.187.24 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  After updating the system, rebooted and this error appeared.
  Fixed a problem related to /boot/grub/grubenv - "Error in environment" and 
grub-common.service
  by providing absolute path to grub-editenv.  /boot/grub/grubenv was full of 
0x0, rather than 0x2323 as it has now.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.24
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   3520 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sat Jan  8 17:37:06 2022
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-11-12 (422 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP EliteBook 8470p
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_x1by5v@/vmlinuz-5.11.0-44-generic 
root=ZFS=rpool/ROOT/ubuntu_x1by5v ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.24 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2018
  dmi.bios.release: 15.113
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.71
  dmi.board.name: 179B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.38
  dmi.chassis.asset.tag: CNU3109W10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 66.56
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.71:bd04/12/2018:br15.113:efr66.56:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1102:skuC3Q91UC#ABU:rvnHewlett-Packard:rn179B:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8470p
  dmi.product.sku: C3Q91UC#ABU
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1956835/+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 1956957] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-01-14 Thread Brian Murray
I noticed that your boot partition is full. Could you provide the output
of "ls -l /boot"? Additionally, how did you install Ubuntu?

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  3 weeks after installing 20.04.3

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jan 10 13:03:11 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-12-22 (19 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1956957/+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 1956647] Re: CUPS TAKE LONG TIME TO PRINT (CTRL+P)

2022-01-14 Thread Brian Murray
** Package changed: ubuntu-release-upgrader (Ubuntu) => cups (Ubuntu)

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

Title:
  CUPS TAKE LONG TIME TO PRINT (CTRL+P)

Status in cups package in Ubuntu:
  New

Bug description:
  CUPS TAKE LONG TIME TO PRINT IN UBUNTU UBUNTU 20.04.3 BUT IN UBUNTU
  20.04.1 IS NORMAL. IN LIBRE TAKE A 5-7 SECOND TO SHOW THE PRINT
  WINDOW, IN WPS IS TAKE 7-10 SECOND TO POPUP PRINT WINDOW

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36 [origin: unknown]
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  7 10:02:15 2022
  InstallationDate: Installed on 2021-09-22 (106 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2021-09-22T12:06:48.046711

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1956647/+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 1953521] Re: fixrtc produces extraneous (confusing) output

2022-01-13 Thread Brian Murray
Somebody uploaded this and neglected to unsubscribe the sponsors team,
I'm doing that now.

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

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

Title:
  fixrtc produces extraneous (confusing) output

Status in initramfs-tools package in Ubuntu:
  Fix Committed

Bug description:
  The premount script for fixrtc produces a couple of lines of
  extraneous (and slightly confusing) output. While this is irrelevant
  for most platforms, on the pi images (which use fixrtc owing to the
  lack of an RTC on the board), it means that "ext4" and "Thu Jan  1
  00:00:10 UTC 1970" are the first console output on every boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1953521/+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 989961] Re: Provide a gmake symlink

2022-01-13 Thread Brian Murray
It isn't easy to extract the debdiff from your PPA currently as make-
dfsg has a new version available and the current diff produced by your
PPA only has debian/changelog changes. Could you please attach a new
debdiff to this bug report and subscribe the Ubuntu Sponsors team after
that is done? Thanks in advance.

** Changed in: make-dfsg (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Provide a gmake symlink

Status in make-dfsg package in Ubuntu:
  Incomplete

Bug description:
  Some, albeit older or proprietary software, expects a gmake symlink
  for gnu make.  Can this be provided?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/989961/+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 1867204] Re: /usr/share/apport/whoopsie-upload-all:FileNotFoundError:/usr/share/apport/whoopsie-upload-all@170:collect_info:process_report

2022-01-13 Thread Brian Murray
** Changed in: apport (Ubuntu)
   Importance: Undecided => High

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:FileNotFoundError:/usr/share/apport/whoopsie-upload-
  all@170:collect_info:process_report

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu19, the problem page at 
https://errors.ubuntu.com/problem/7a3912ff155870bdb23500abfa48a21a6cb07171 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1867204/+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 1939616] Re: u-r-u should leave a breadcrumb indicating a dist-upgrade is in progress

2022-01-13 Thread Brian Murray
** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: update-notifier (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  u-r-u should leave a breadcrumb indicating a dist-upgrade is in
  progress

Status in apport package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in apport source package in Impish:
  New
Status in ubuntu-release-upgrader source package in Impish:
  New
Status in update-notifier source package in Impish:
  New

Bug description:
  Looking at the source code of ubuntu-release-upgrader it looks like an
  environment variable, RELEASE_UPGRADE_IN_PROGRESS, is set when an
  upgrade is being performed. However, it would be better if there was
  an indication that other programs, e.g. apport, could use to tell
  whether or not a release upgrade was in progress.

  This came up as we saw some crash reports in the error tracker that
  didn't make sense and a possible explanation is that a release upgrade
  was in progress.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1939616/+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 574287] Re: tasksel: forcefully removes packages when tasks overlap

2022-01-13 Thread Brian Murray
** Tags added: rls-jj-incoming

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

Title:
  tasksel: forcefully removes packages when tasks overlap

Status in apt package in Ubuntu:
  Invalid
Status in tasksel package in Ubuntu:
  Confirmed
Status in tasksel package in Debian:
  Fix Released

Bug description:
  TEST CASE

  1. Boot Lucid LiveCD

  2. run "sudo tasksel" and select "virtual machine host"

  3. run "sudo tasksel" and deselect "virtual machine host"

  4. watch how tasksel uninstalls your system

  OBSERVATIONS

  What seems to happen is that apt vengefully removes ALL of the items
  associated with one task, including several base dependencies of other
  tasks (e.g. ubuntu-desktop)

  One illustrative example is the openssh-server task:
  This one includes the packages openssh-server, tcpd and libwrap0.
  From a normal ubuntu-desktop (e.g. ~liveCD) both tcpd and libwrap0 are 
already installed, and the task-install pulls in only openssh-server.
  However when the task is removed, all these three packages (openssh-server, 
tcpd and libwrap0) are forcefully removed.
  Since libwrap0 is a core dependency of gnome, a large part of gnome will be 
removed alongside the removal of the task.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/574287/+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 1957816] Re: Wayland dual monitor 60Hz: High pitch audio

2022-01-13 Thread Brian Murray
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Wayland dual monitor 60Hz: High pitch audio

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a desktop computer with a 60Hz 4K display connected through Display 
Port. The display is a ThinkVision X1 with built in audio. With the Display 
Port cable I am then able to output sound from the monitor and this works 
without any issues.
  I have now added a 4K Samsung television through HDMI to the same GPU, which 
also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only 
do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear 
however, that when it is set to 60Hz in Wayland, the animation on the 
television is much more smooth. 

  The problem is that whenever I set the television to 60Hz, the playback of 
any sound is both high pitched and faster than normal. If I play a video in 
YouTube, the video appears to playback about twice as fast as normal and and 
very high pitched sound (everyone sounds like chipmunks). This is the case on 
the entire system (also when playing the video or any other sounds on the X1 
display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz 
again does everything play and sound normal again. 
  It is only the playback of media that is doubled in speed. Everything else 
(animations, mouse, etc.) is still behaving as normal.

  If I change audio output to the ThinkVision X1 (or something else) at
  60Hz while also being connected to the television at 60Hz, the audio
  stays high pitched and sped up.

  If I unplug the main display, ThinkVision X1, then the playback of
  media on the television becomes normal.

  I have tried with different +100 USD HDMI cables, that are all rated
  as HDMI 2.0 and the behavior stays the same.

  My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the
  behavior was the same.

  I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI).

  As mentioned I cannot test it in Xorg, but that is only because it
  does not allow me to set the refresh rate to 60Hz.

  I am uncertain whether this is related to MESA, Pulseaudio or maybe
  Mutter/Wayland?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1957816/+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 1903567] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@447:parse_arguments:print_usage:_print_message

2022-01-12 Thread Brian Murray
** Changed in: apport (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@447:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Xenial:
  Won't Fix
Status in apport source package in Bionic:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.1-0ubuntu2.26, the problem page at 
https://errors.ubuntu.com/problem/c39b4b2ced24aa71d85b0995a56bd3813a39 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1903567/+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 1867204] Re: /usr/share/apport/whoopsie-upload-all:FileNotFoundError:/usr/share/apport/whoopsie-upload-all@170:collect_info:process_report

2022-01-12 Thread Brian Murray
A more recent version of this bucket can be found here and here:

https://errors.ubuntu.com/problem/3adc63930455e99063ec1f77bf461d975492e9b4
https://errors.ubuntu.com/problem/6e66a508ca49b0dc586b3db41a71401cc660271f

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:FileNotFoundError:/usr/share/apport/whoopsie-upload-
  all@170:collect_info:process_report

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu19, the problem page at 
https://errors.ubuntu.com/problem/7a3912ff155870bdb23500abfa48a21a6cb07171 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1867204/+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 1947800] Re: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:r

2022-01-12 Thread Brian Murray
** Changed in: apport (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: apport (Ubuntu Impish)
   Importance: Undecided => High

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:zlib.error:/usr/share/apport/whoopsie-upload-
  
all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Impish:
  Confirmed
Status in apport source package in Jammy:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu70, the problem page at 
https://errors.ubuntu.com/problem/7120f8aebdf09e9dca39196d035eec234071e800 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1947800/+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 1952591] Re: Please merge kmod 29-1 (main) from Debian unstable (main)

2022-01-12 Thread Brian Murray
I uploaded this after modifying the changelog to reference this bug
number.

 $ dput kmod_29-1ubuntu1_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg: /tmp/pkgs/jammy/kmod/kmod_29-1ubuntu1_source.changes: Valid signature from 
1E918B66765B3E31
Checking signature on .dsc
gpg: /tmp/pkgs/jammy/kmod/kmod_29-1ubuntu1.dsc: Valid signature from 
1E918B66765B3E31
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading kmod_29-1ubuntu1.dsc: done.
  Uploading kmod_29.orig.tar.xz: done.
  Uploading kmod_29-1ubuntu1.debian.tar.xz: done.  
  Uploading kmod_29-1ubuntu1_source.buildinfo: done.
  Uploading kmod_29-1ubuntu1_source.changes: done.
Successfully uploaded packages.


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

** Changed in: kmod (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Tags added: fr-1857

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

Title:
  Please merge kmod 29-1 (main) from Debian unstable (main)

Status in kmod package in Ubuntu:
  In Progress

Bug description:
* Merge from Debian unstable. Remaining changes:
   
  - Enable testsuite during build.  
   
  - Build with zstd compression enabled.
   
  - Install ubuntu-specific depmod.d and modprobe.d contents.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1952591/+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 1951519] Re: ubiquity 20.04.15.17 fails to build (test_timezone)

2022-01-12 Thread Brian Murray
The package built fine so I'm setting this to verification done.

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

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

Title:
  ubiquity 20.04.15.17 fails to build (test_timezone)

Status in tzdata package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Invalid
Status in ubiquity source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Invalid
Status in ubiquity source package in Jammy:
  Fix Released

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  When trying to build ubiquity from source,

  sudo apt update
  sudo apt -y dist-upgrade
  sudo apt-get build-dep ubiquity
  sudo apt install -y fakeroot
  apt source ubiquity
  cd ubiquity-*
  dpkg-buildpackage -us -uc
  [...]
  test_has_battery (test_upower.UPowerTests) ... ok
  test_check_hostname (test_usersetup.UserSetupTests) ... ok
  test_check_username (test_usersetup.UserSetupTests) ... ok
  test_default_username (test_usersetup.UserSetupTests) ... ok
  test_default_username_strips_invalid_characters 
(test_usersetup.UserSetupTests) ... ok
  test_hostname_check (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_bogus_dns (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_exists (test_usersetup.UserSetupTests) ... ok
  test_unicode (test_usersetup.UserSetupTests) ... ok

  ==
  FAIL: test_city_entry (test_timezone.TimezoneTests)
  --
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
  return func(*args, **keywargs)
    File "/home/ark/ubiquity-20.04.15.17/tests/test_timezone.py", line 58, in 
test_city_entry
  self.assertEqual(set(results), set(expected))
  AssertionError: Items in the first set but not the second:
  ('Eastern', 'Bahamas')
  Items in the second set but not the first:
  ('Eastern', 'Canada')

  --
  Ran 89 tests in 19.319s

  FAILED (failures=1)
  xauth/Xrdb output:
  make: *** [debian/rules:228: tests] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

  It keeps failing regardless of release.

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

2022-01-11 Thread Brian Murray
The verification of the Stable Release Update for lightdm 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 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:
  Fix Released
Status in lightdm source package in Bionic:
  New
Status in lightdm source package in Focal:
  Fix Released
Status in lightdm source package in Hirsute:
  Fix Committed
Status in lightdm source package in Impish:
  Fix Released
Status in lightdm source package in Jammy:
  Fix Released

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 1956412] Re: crash reports don't go to proper dev team

2022-01-10 Thread Brian Murray
There are frequently modifications made to Ubuntu packages which
upstream developers are not aware of or the Ubuntu version of a package
can be one or more versions behind the latest upstream version. For
these reasons the crash reports first come to Ubuntu and ideally are
then forwarded to the upstream developers. I say ideally as we don't
have the manpower to test and forward every bug report to the upstream
developers.

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

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

Title:
  crash reports don't go to proper dev team

Status in apport package in Ubuntu:
  Won't Fix

Bug description:
  i'm on 21.10.  i was reporting a crash to a gnome dev team and they informed 
me that the crash report dialog that submits coredumps, etc. never makes it to 
the actual responsible party.
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/80#note_1346891

  you need a process that forwards these to the proper team

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1956412/+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 1951519] Re: ubiquity 20.04.15.17 fails to build (test_timezone)

2022-01-10 Thread Brian Murray
** Changed in: ubiquity (Ubuntu Focal)
Milestone: None => ubuntu-20.04.4

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

Title:
  ubiquity 20.04.15.17 fails to build (test_timezone)

Status in tzdata package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Invalid
Status in ubiquity source package in Focal:
  In Progress
Status in tzdata source package in Jammy:
  Invalid
Status in ubiquity source package in Jammy:
  Fix Released

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  When trying to build ubiquity from source,

  sudo apt update
  sudo apt -y dist-upgrade
  sudo apt-get build-dep ubiquity
  sudo apt install -y fakeroot
  apt source ubiquity
  cd ubiquity-*
  dpkg-buildpackage -us -uc
  [...]
  test_has_battery (test_upower.UPowerTests) ... ok
  test_check_hostname (test_usersetup.UserSetupTests) ... ok
  test_check_username (test_usersetup.UserSetupTests) ... ok
  test_default_username (test_usersetup.UserSetupTests) ... ok
  test_default_username_strips_invalid_characters 
(test_usersetup.UserSetupTests) ... ok
  test_hostname_check (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_bogus_dns (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_exists (test_usersetup.UserSetupTests) ... ok
  test_unicode (test_usersetup.UserSetupTests) ... ok

  ==
  FAIL: test_city_entry (test_timezone.TimezoneTests)
  --
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
  return func(*args, **keywargs)
    File "/home/ark/ubiquity-20.04.15.17/tests/test_timezone.py", line 58, in 
test_city_entry
  self.assertEqual(set(results), set(expected))
  AssertionError: Items in the first set but not the second:
  ('Eastern', 'Bahamas')
  Items in the second set but not the first:
  ('Eastern', 'Canada')

  --
  Ran 89 tests in 19.319s

  FAILED (failures=1)
  xauth/Xrdb output:
  make: *** [debian/rules:228: tests] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

  It keeps failing regardless of release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1951519/+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 1956350] Re: xdg-desktop-portal-gnome missing in Jammy ISO

2022-01-07 Thread Brian Murray
** Changed in: ubuntu-meta (Ubuntu)
Milestone: None => ubuntu-22.04-feature-freeze

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

Title:
  xdg-desktop-portal-gnome missing in Jammy ISO

Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Jammy ISO contains xdg-desktop-portal-gtk but xdg-desktop-portal-gnome 
is missing.
  xdg-desktop-portal-gnome is needed for GIMP Color picker and Flameshot on 
Wayland.
  see https://gitlab.gnome.org/GNOME/gimp/-/issues/1074
  apt show xdg-desktop-portal-gnome says:
  Non-GNOME GTK-based desktop environments should normally use
   xdg-desktop-portal-gtk or their own portal implementation instead of
   this one.
  and Ubuntu 22.04 is a GNOME desktop, so xdg-desktop-portal-gnome should be 
included in the ISO image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1956350/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts

2022-01-07 Thread Brian Murray
The gdb autopkgtest test failures listed in comment #24 are actually not
regressions as the test result is "neutral" and they quit early due to
not having machine-level isolation.

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

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Incomplete
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in gdb source package in Focal:
  Fix Committed
Status in glibc source package in Focal:
  Fix Committed
Status in gdb source package in Groovy:
  Won't Fix
Status in glibc source package in Groovy:
  Won't Fix
Status in gdb source package in Hirsute:
  Won't Fix
Status in glibc source package in Hirsute:
  Won't Fix
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Released

Bug description:
  [Impact]

  * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is
  not installed.

  [Test Plan]

  * Check that ld.so is not stripped on armhf:
  $  /lib/*/ld-2.31.so
  libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, 
EABI5 version 1 (SYSV), dynamically linked, 
BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not 
stripped

  * Check that ld.so is stripped on amd64:

  $ file /lib/x86_64-linux-gnu/ld-2.31.so
  /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, 
version 1 (SYSV), dynamically linked, 
BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped

  [Where problems could occur]

  * The fix is not stripping ld.so on armhf. Not stripping it comes with
  a notable increase in file size and it may be performance critical
  109K stripped vs 1.3M unstripped. Accidentally ld.so could be left
  unstripped on other architectures, but the test plan covers checking
  that, at least on amd64. Other than those not stripping ld.so should
  not cause any issue.

  [Original Bug Text]

  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1927192/+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 1951519] Re: ubiquity 20.04.15.17 fails to build (test_timezone)

2022-01-07 Thread Brian Murray
ubiquity (22.04.3) jammy; urgency=medium

  * tests/test_timezone.py:
- update for changes in the new tzdata

 -- Sebastien Bacher   Tue, 23 Nov 2021 23:37:23
+0100


** Changed in: ubiquity (Ubuntu Jammy)
   Status: Invalid => 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/1951519

Title:
  ubiquity 20.04.15.17 fails to build (test_timezone)

Status in tzdata package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Invalid
Status in ubiquity source package in Focal:
  In Progress
Status in tzdata source package in Jammy:
  Invalid
Status in ubiquity source package in Jammy:
  Fix Released

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  When trying to build ubiquity from source,

  sudo apt update
  sudo apt -y dist-upgrade
  sudo apt-get build-dep ubiquity
  sudo apt install -y fakeroot
  apt source ubiquity
  cd ubiquity-*
  dpkg-buildpackage -us -uc
  [...]
  test_has_battery (test_upower.UPowerTests) ... ok
  test_check_hostname (test_usersetup.UserSetupTests) ... ok
  test_check_username (test_usersetup.UserSetupTests) ... ok
  test_default_username (test_usersetup.UserSetupTests) ... ok
  test_default_username_strips_invalid_characters 
(test_usersetup.UserSetupTests) ... ok
  test_hostname_check (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_bogus_dns (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_exists (test_usersetup.UserSetupTests) ... ok
  test_unicode (test_usersetup.UserSetupTests) ... ok

  ==
  FAIL: test_city_entry (test_timezone.TimezoneTests)
  --
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
  return func(*args, **keywargs)
    File "/home/ark/ubiquity-20.04.15.17/tests/test_timezone.py", line 58, in 
test_city_entry
  self.assertEqual(set(results), set(expected))
  AssertionError: Items in the first set but not the second:
  ('Eastern', 'Bahamas')
  Items in the second set but not the first:
  ('Eastern', 'Canada')

  --
  Ran 89 tests in 19.319s

  FAILED (failures=1)
  xauth/Xrdb output:
  make: *** [debian/rules:228: tests] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

  It keeps failing regardless of release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1951519/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593

2022-01-06 Thread Brian Murray
On Thu, Jan 06, 2022 at 05:24:57PM -, Paulo Flabiano Smorigo wrote:
> Thanks! I didn't add the LP number because it was in the previous
> changelog entry. It seems that it needs to be in the latest one in order
> to identify it correctly.

I think you could work around this by using the -v argument to debuild
which will create a source.changes file with different contents e.g.

debuild ... -v5.15.2+dfsg-12

--
Brian Murray

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Focal:
  Fix Released
Status in qtbase-opensource-src source package in Impish:
  Fix Released

Bug description:
  [Impact]

  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th.

  [Test Plan]

  1. Install libqt5svg5-dev, qtbase5-dev and their dependencies.
  2. Build the attached project with the system's version of Qt:
 /usr/lib/qt5/bin/qmake test-2021-38593.pro && make
  3. Start the resulting binary and pass the path to the included input file as 
first parameter:
 ./test-2021-38593 ./input.svg
 The binary should return immediately and without error messages. If it 
doesn't, you might be affected.

  [Where problems could occur]

  The fix tries to skip drawing dashes that would be invisible anyway.
  So a potential problem may that it skips too much. In fact, this has
  already happened, and upstream had to adjust the fix.

  [Other Info]

  The patch is a combination of the following upstream commits:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c

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

2022-01-06 Thread Brian Murray
The verification of the Stable Release Update for openssh 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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1952421

Title:
  Issue on sshd finds correct private key for a certificate when using
  ssh-agent

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Focal:
  Fix Released
Status in openssh source package in Hirsute:
  Fix Released
Status in openssh source package in Impish:
  Fix Released

Bug description:
  Reported as https://bugzilla.mindrot.org/show_bug.cgi?id=3254 upstream

  [Impact]

   * HostCertificate and HostKeyAgent are not working together in sshd due 
 to a mismatched certificate's public key and private key. The function `  
`sshkey_equal_public()`` incorrectly compares the certificate's public 
key with a private key, never finding a match. The impact is that sshd 
cannot use said certificate *even though* its private key is indeed in 
ssh-agent.

  * What it should do is compare the certificate's public key with a
  public key in `sensitive_data`.

  * Having this SRU-ed is a direct ask from one of the major cloud partners. 
They are currently using a customised version of the package to work 
around this issue, and we would like them to use a package directly from 
our own archive.

   * Looping through sensitive_data.host_pubkeys[j] *instead* of 
 sensitive_data.host_keys[j] fixes the issue

  [https://github.com/openssh/openssh-portable/blob/V_8_4/sshd.c#L1936]

  /* Find matching private key */
   for (j = 0; j < options.num_host_key_files; j++) {
    if (sshkey_equal_public(key,
     sensitive_data.host_keys[j])) {
     sensitive_data.host_certificates[j] = key;
  break;
     }
   }

  vs.

  /* Find matching private key */
   for (j = 0; j < options.num_host_key_files; j++) {
    if (sshkey_equal_public(key,
     sensitive_data.host_pubkeys[j])) {
     sensitive_data.host_certificates[j] = key;
  break;
     }
   }
   

  [Test Plan]

   * Due to the empirical nature of this bug, the test is quite straight 
 forward. *Without* the fix, one cannot use certificates to authenticate 
 successfully (e.g. ``sshd -c /path/to/certificate.pem``)
 whereas with the fix (assuming the certificate matches a host key) you 
 can create a channel.
 
  [Where problems could occur]

   * This has already been fixed both upstream and in Jammy without issue. 
 However, if a regression where to happen it would probably be in one of 
 two ways:
   
   * A dependency/reverse-dependency issue stemming from the version 
 bump that will happen if this fix is ported. We mitigate this risk 
 by testing for these exact types of regression, 
 and by selecting carefully what to label this new version.
 
   * Accidentally breaking a set up that was made to work around this 
 bug in the first place. The risk of this is lower, as the most 
 likely fix is the one being implemented here anyway.  Though
 to mitigate this more we can describe exactly what is happening 
 with the fix in the changelog.

  
  This affects every version of openssh back until Focal, at least.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1952421/+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 1951519] Re: ubiquity 20.04.15.17 fails to build (test_timezone)

2022-01-06 Thread Brian Murray
The tzdata update included a change to the Bahamas which has them
following the US East Coast time zone for DST information.

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

** Changed in: ubiquity (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: ubiquity (Ubuntu Focal)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  ubiquity 20.04.15.17 fails to build (test_timezone)

Status in tzdata package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Invalid
Status in tzdata source package in Focal:
  Invalid
Status in ubiquity source package in Focal:
  In Progress
Status in tzdata source package in Jammy:
  Invalid
Status in ubiquity source package in Jammy:
  Invalid

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  When trying to build ubiquity from source,

  sudo apt update
  sudo apt -y dist-upgrade
  sudo apt-get build-dep ubiquity
  sudo apt install -y fakeroot
  apt source ubiquity
  cd ubiquity-*
  dpkg-buildpackage -us -uc
  [...]
  test_has_battery (test_upower.UPowerTests) ... ok
  test_check_hostname (test_usersetup.UserSetupTests) ... ok
  test_check_username (test_usersetup.UserSetupTests) ... ok
  test_default_username (test_usersetup.UserSetupTests) ... ok
  test_default_username_strips_invalid_characters 
(test_usersetup.UserSetupTests) ... ok
  test_hostname_check (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_bogus_dns (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_exists (test_usersetup.UserSetupTests) ... ok
  test_unicode (test_usersetup.UserSetupTests) ... ok

  ==
  FAIL: test_city_entry (test_timezone.TimezoneTests)
  --
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
  return func(*args, **keywargs)
    File "/home/ark/ubiquity-20.04.15.17/tests/test_timezone.py", line 58, in 
test_city_entry
  self.assertEqual(set(results), set(expected))
  AssertionError: Items in the first set but not the second:
  ('Eastern', 'Bahamas')
  Items in the second set but not the first:
  ('Eastern', 'Canada')

  --
  Ran 89 tests in 19.319s

  FAILED (failures=1)
  xauth/Xrdb output:
  make: *** [debian/rules:228: tests] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

  It keeps failing regardless of release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1951519/+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 1951519] Re: ubiquity 20.04.15.17 fails to build (test_timezone)

2022-01-06 Thread Brian Murray
** Changed in: tzdata (Ubuntu Jammy)
   Status: New => Invalid

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

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

Title:
  ubiquity 20.04.15.17 fails to build (test_timezone)

Status in tzdata package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Invalid
Status in tzdata source package in Focal:
  Confirmed
Status in ubiquity source package in Focal:
  Confirmed
Status in tzdata source package in Jammy:
  Invalid
Status in ubiquity source package in Jammy:
  Invalid

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  When trying to build ubiquity from source,

  sudo apt update
  sudo apt -y dist-upgrade
  sudo apt-get build-dep ubiquity
  sudo apt install -y fakeroot
  apt source ubiquity
  cd ubiquity-*
  dpkg-buildpackage -us -uc
  [...]
  test_has_battery (test_upower.UPowerTests) ... ok
  test_check_hostname (test_usersetup.UserSetupTests) ... ok
  test_check_username (test_usersetup.UserSetupTests) ... ok
  test_default_username (test_usersetup.UserSetupTests) ... ok
  test_default_username_strips_invalid_characters 
(test_usersetup.UserSetupTests) ... ok
  test_hostname_check (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_bogus_dns (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_exists (test_usersetup.UserSetupTests) ... ok
  test_unicode (test_usersetup.UserSetupTests) ... ok

  ==
  FAIL: test_city_entry (test_timezone.TimezoneTests)
  --
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
  return func(*args, **keywargs)
    File "/home/ark/ubiquity-20.04.15.17/tests/test_timezone.py", line 58, in 
test_city_entry
  self.assertEqual(set(results), set(expected))
  AssertionError: Items in the first set but not the second:
  ('Eastern', 'Bahamas')
  Items in the second set but not the first:
  ('Eastern', 'Canada')

  --
  Ran 89 tests in 19.319s

  FAILED (failures=1)
  xauth/Xrdb output:
  make: *** [debian/rules:228: tests] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

  It keeps failing regardless of release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1951519/+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 1951519] Re: ubiquity 20.04.15.17 fails to build (test_timezone)

2022-01-06 Thread Brian Murray
** Tags removed: rls-ff-incoming rls-jj-incoming

** Changed in: tzdata (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: tzdata (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: ubiquity (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: ubiquity (Ubuntu Jammy)
   Importance: Undecided => High

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

Title:
  ubiquity 20.04.15.17 fails to build (test_timezone)

Status in tzdata package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in tzdata source package in Focal:
  Confirmed
Status in ubiquity source package in Focal:
  Confirmed
Status in tzdata source package in Jammy:
  New
Status in ubiquity source package in Jammy:
  New

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  When trying to build ubiquity from source,

  sudo apt update
  sudo apt -y dist-upgrade
  sudo apt-get build-dep ubiquity
  sudo apt install -y fakeroot
  apt source ubiquity
  cd ubiquity-*
  dpkg-buildpackage -us -uc
  [...]
  test_has_battery (test_upower.UPowerTests) ... ok
  test_check_hostname (test_usersetup.UserSetupTests) ... ok
  test_check_username (test_usersetup.UserSetupTests) ... ok
  test_default_username (test_usersetup.UserSetupTests) ... ok
  test_default_username_strips_invalid_characters 
(test_usersetup.UserSetupTests) ... ok
  test_hostname_check (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_bogus_dns (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_exists (test_usersetup.UserSetupTests) ... ok
  test_unicode (test_usersetup.UserSetupTests) ... ok

  ==
  FAIL: test_city_entry (test_timezone.TimezoneTests)
  --
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
  return func(*args, **keywargs)
    File "/home/ark/ubiquity-20.04.15.17/tests/test_timezone.py", line 58, in 
test_city_entry
  self.assertEqual(set(results), set(expected))
  AssertionError: Items in the first set but not the second:
  ('Eastern', 'Bahamas')
  Items in the second set but not the first:
  ('Eastern', 'Canada')

  --
  Ran 89 tests in 19.319s

  FAILED (failures=1)
  xauth/Xrdb output:
  make: *** [debian/rules:228: tests] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

  It keeps failing regardless of release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1951519/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593

2022-01-06 Thread Brian Murray
I'm manually setting the bug tasks to Fix Released as this bug wasn't
referenced in the changelog entry.

** Changed in: qtbase-opensource-src (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: qtbase-opensource-src (Ubuntu Impish)
   Status: Fix Committed => Fix Released

** Tags removed: block-proposed-focal block-proposed-impish

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Focal:
  Fix Released
Status in qtbase-opensource-src source package in Impish:
  Fix Released

Bug description:
  [Impact]

  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th.

  [Test Plan]

  1. Install libqt5svg5-dev, qtbase5-dev and their dependencies.
  2. Build the attached project with the system's version of Qt:
 /usr/lib/qt5/bin/qmake test-2021-38593.pro && make
  3. Start the resulting binary and pass the path to the included input file as 
first parameter:
 ./test-2021-38593 ./input.svg
 The binary should return immediately and without error messages. If it 
doesn't, you might be affected.

  [Where problems could occur]

  The fix tries to skip drawing dashes that would be invisible anyway.
  So a potential problem may that it skips too much. In fact, this has
  already happened, and upstream had to adjust the fix.

  [Other Info]

  The patch is a combination of the following upstream commits:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1952947] Re: ubuntu-bug -w doesn't work under wayland

2022-01-06 Thread Brian Murray
** Changed in: apport (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  ubuntu-bug -w doesn't work under wayland

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I want to report a Bug about the application Studio Controls.

  As I did it already quite a few times, I run "ubuntu-bug -w", get a
  message that I can select the window of the app I want to report a bug
  about after closing this message.

  I close the message with a click on the appropriate button.

  I click on the window of the application "Studio Controls" that I want
  to report a bug about.

  Nothing happens.

  I wait for a few minutes. Still nothing happens.

  In the console where I started ubuntu-bug -w I see the following
  message:

  (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed


  What I expect:

  Usaully when I use this procedure, after a relatively short while a
  new message window pops up asking me if the bug should be reported and
  showing me the data that is sent to Launchpad.

  I tried other applications, too, same effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apport 2.20.11-0ubuntu71
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  1 20:01:23 2021
  InstallationDate: Installed on 2020-04-12 (597 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+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 1956415] Re: wiki pages about filing bug reports have out of date info

2022-01-05 Thread Brian Murray
*** This bug is a duplicate of bug 1952947 ***
https://bugs.launchpad.net/bugs/1952947

As Chris has demonstrated this does work in some situations however now
when wayland is being used and there is another apport bug report about
that. I'll make this a duplicate of the wayland bug.

** This bug has been marked a duplicate of bug 1952947
   ubuntu-bug -w doesn't work under wayland

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

Title:
  wiki pages about filing bug reports have out of date info

Status in apport package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/Bugs/FindRightPackage and
  https://help.ubuntu.com/community/ReportingBugs

  both say that you can find the right package for a bug in a window'ed app 
using 
  ubuntu-bug -w

  the former also says you can:
  Launch System -> Preferences -> Main Menu.
  Select the item for the application. (For example, System -> Preferences -> 
Display.)
  Click "Properties" button.
  Write down the "Command" value. 

  or
  xprop WM_CLASS

  none of those work for me in 21.10.

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

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

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

Title:
  restarting systemd-logind loses all existing sessions

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

Bug description:
  [impact]

  restarting the systemd-logind service loses all existing sessions

  [test case]

  ubuntu@test-f:~$ loginctl list-sessions
  SESSION  UID USER   SEAT TTY
     3789 1000 ubuntu  pts/0

  1 sessions listed.
  ubuntu@test-f:~$ journalctl -b -u systemd-logind
  -- Logs begin at Thu 2021-09-23 11:11:57 UTC, end at Thu 2021-09-23 11:22:55 
UTC. --
  Sep 23 11:22:51 test-f systemd[1]: Starting Login Service...
  Sep 23 11:22:51 test-f systemd-logind[198]: New seat seat0.
  Sep 23 11:22:51 test-f systemd[1]: Started Login Service.
  Sep 23 11:22:52 test-f systemd-logind[198]: New session 3789 of user ubuntu.
  ubuntu@test-f:~$ sudo systemctl restart systemd-logind
  ubuntu@test-f:~$ journalctl -b -u systemd-logind
  -- Logs begin at Thu 2021-09-23 11:11:57 UTC, end at Thu 2021-09-23 11:23:07 
UTC. --
  Sep 23 11:22:51 test-f systemd[1]: Starting Login Service...
  Sep 23 11:22:51 test-f systemd-logind[198]: New seat seat0.
  Sep 23 11:22:51 test-f systemd[1]: Started Login Service.
  Sep 23 11:22:52 test-f systemd-logind[198]: New session 3789 of user ubuntu.
  Sep 23 11:23:07 test-f systemd[1]: Stopping Login Service...
  Sep 23 11:23:07 test-f systemd[1]: systemd-logind.service: Succeeded.
  Sep 23 11:23:07 test-f systemd[1]: Stopped Login Service.
  Sep 23 11:23:07 test-f systemd[1]: Starting Login Service...
  Sep 23 11:23:07 test-f systemd-logind[469]: Failed to add user by file name 
1000, ignoring: Invalid argument
  Sep 23 11:23:07 test-f systemd-logind[469]: User enumeration failed: Invalid 
argument
  Sep 23 11:23:07 test-f systemd-logind[469]: User of session 3789 not known.
  Sep 23 11:23:07 test-f systemd-logind[469]: Session enumeration failed: No 
such file or directory
  Sep 23 11:23:07 test-f systemd-logind[469]: New seat seat0.
  Sep 23 11:23:07 test-f systemd[1]: Started Login Service.
  ubuntu@test-f:~$ loginctl list-sessions
  No sessions.

  [regression potential]

  any regression would likely occur during a systemd-logind restart,
  likely causing a loss of current login sessions.

  [scope]

  this is needed only in f

  this is fixed upstream by commit
  ac4e03d45bcf4ad2e570cabdb218e9bac003cc80 which is included in v246, so
  this is fixed in h and later already.

  in b, the function used to parse the /run/systemd/users/* files allows
  either usernames or uids, so this bug does not exist there

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

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

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

Title:
  [SRU] Allow target units to fail

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

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

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

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

Title:
  timedatectl set-timezone fails on UC16

Status in Snappy:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  SRU
  ===

  [Impact]

   * The bug prevents timedated from recognizing and correctly set the
  system's timezone when running Ubuntu Core 16, 18 and 20.

   * This causes by timedated fails to take Ubuntu Core's /etc/writable
  redirection into account.

   * The recognizing part is fixed by making the code take writable
  redirection into account.

   * The set part is fixed by making the code link to the absolute path
  instead of a relative one.

   * Currently core snaps worked around the set part by providing a
  wrapper script which re-create /etc/writable/localtime afterward.
  However this does not cover DBus users.

  [Test Plan]

   * On classics systems: ensure the proposed systemd package is installed.
     On Ubuntu Core systems: build a new core snap including proposed package, 
and install it. Replaces timedatectl with timedatectl.real to test skipping the 
wrapper.

  (Note that one can simulate core snap's /etc/writable redirection by
  running this image creation hook [1] on the system.)

  [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
  core/hooks/08-etc-writable.chroot?h=ubuntu/focal

   * On freshly boot system: query the timezone using `timedatectl`. The
  timezone should corresponds to `readlink -f /etc/localtime` and does
  not show `n/a`.

   * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`.
  `readlink -f /etc/localtime` should points to an existing file.

   * Run `sudo systemctl restart systemd-timedated.service`. Then, query
  the timezone again: `timedatectl`. It should show the previously set
  timezone and not `n/a`.

   * Run `sudo systemctl status systemd-timedated.service`. This should
  show no sign of timedated crashing.

  [Where problems could occur]

   * It's possible that the redirection handling code will be sub-par
  and causes crash. However, it's not likely because the similar pieces
  of code is in the previous patch since Ubuntu 16.04.

   * If it does: the patched `get_timezone()` function is used in 2
  places: the networkd's DHCP server [3] and the timedated itself.

     - Networkd is used primarily on servers where NetworkManage is
  absent. It's possible that this patch causes the user to loss access
  to the server due to networkd crash when setting up network
  interfaces, and requires physical access to fix. However, the code
  path is executed when DHCP is enabled only. I think it's not common
  for users to have networkd's DHCP server enabled: the feature seems to
  gear towards desktop users wanting to share internet connection, and
  in those cases they're more likely to use NetworkManager.

     - The timedated itself is likely used by the programs that involves
  in time-related functions. If a crash occur, in the worst case users
  won't be able to set time or timezone via timedated. However, users
  should still be able to e.g. set time using `date` or set timezone
  using /etc/localtime (assuming online guides still consider systems
  without systemd). Timedated is DBus-activated, and thus a crash should
  be self-healing.

   * The set part would also affects the clasic systems. However, I
  believe nothing else actually rely on /etc/localtime being a relative
  path, otherwise the /etc/writable redirection would causes even more
  problem, and would have been reported.

  [3] Yes, I'm surprised that there's a DHCP server inside systemd
  codebase.

  [Other Info]

   * This is also useful for UBports's Ubuntu Touch. We continue using
  system-image system where the rootfs is read-only, and thus is
  affected by this bug similarly to Ubuntu Core. I've tested the Focal
  version of the package on our (currently in development) Focal Ubuntu
  Touch image, and the fix works.

  

  [Original bug description]

  On a system running UC16, the file /etc/localtime is a link that
  points to /etc/writable/localtime.

  On a freshly 

[Touch-packages] [Bug 1943561] Update Released

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

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

Title:
  Add ACCEL_LOCATION=base property for 6 Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  This hwdb update is to avoid unwanted screen rotation when tilting the
  laptop.

  This is the update to the previously rolled back SRU LP: #1938259

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install 
this package and ensure the kernel is updated to the latest.
   * Screen should be correct side up in login screen and desktop.
   * Tilt the laptop and the screen should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * Only models with the same Dell SKU would be affected.

  [scope]

  this is needed for all releases

  this is being added to upstream by
  https://github.com/systemd/systemd/pull/20314 and
  https://github.com/systemd/systemd/pull/20661

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943561/+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 1952599] Update Released

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

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

Title:
  virt: Support detection for ARM64 Hyper-V guests (fixed upstream)

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

Bug description:
  [Impact]

   * The detection of Microsoft Hyper-V VMs is done by cpuid currently,
  however there is no cpuid on ARM64. And since ARM64 is now a supported
  architecture for Microsoft Hyper-V guests[0], then introduce a more
  generic way to detect whether a guest is running as a Hyper-V guest: check 
  if /sys/class/dmi/id/product_version starts with "Hyper-V".

   * This bug has already been fixed upstream[1][2]

  [Test Plan]

   * While changes have been made in the kernel for ARM64 on Hyper-V,
  there is no way to start an ARM64 VM on Hyper-V at the moment. Thus we
  just want to make sure no regression is introduced.

   * start an Hyper-V amd64 VM and make sure "systemd-detect-virt" still
  return MSFT (should still rely on cpuid here)

  [Where problems could occur]

   * The main risk is for the system to detect Hyper-V virt erroneously.
  An issue was reported upstream after the first commit was merged[3].
  For this reason, systemd is now looking for "Hyper-V" (in
  /sys/class/dmi/id/product_version) and not "Microsoft" (in
  /sys/class/dmi/id/bios_vendor)

   * This change might also break virt detection on hyper-v AMD64.
  That's why we need testing. However, AMD64 virt detection should still
  rely on cpuid instead of DMI as cpuid takes priority over DMI.

  [0] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7aff79e297ee1aa0126924921fd87a4ae59d2467
  [1] https://github.com/systemd/systemd/pull/20998/files
  [2] https://github.com/systemd/systemd/pull/21475/files
  [3] https://github.com/systemd/systemd/issues/21468

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

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

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

Title:
  Add Dell Privacy Mic Mute Key mapping for another Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952733/+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 1952735] Update Released

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

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

Title:
  Add Microphone mute key mapping for Dell machine

Status in OEM Priority Project:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Dell machine add new microphone mute key on keyboard, add this key mapping 
to make it work.
  [Test Plan]

   * Use a Dell machine, which has this microphone mute key, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952735/+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 1955717] Re: BUG: unsupported FP instruction in kernel mode FPEXC == 0x40000700 at the end of a btrfs balance to RAID1

2022-01-04 Thread Brian Murray
** Package changed: apport (Ubuntu) => linux (Ubuntu)

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

Title:
  BUG: unsupported FP instruction in kernel mode FPEXC == 0x4700 at
  the end of a btrfs balance to RAID1

Status in linux package in Ubuntu:
  New

Bug description:
  Hello there,

  on my Raspberry Pi 4 I needed to convert a volume to RAID1, so I added
  a disk and launched btrfs balance:

  #> sudo btrfs balance start -dconvert=raid1 -mconvert=raid1
  /mnt/mountpoint

  The volume was 5 Tb worth of data, and after a couple of days the
  process looked terminated correctly, in "sudo btrfs filesystem show"
  everything looked ok:

  Label: 'mountpoint'  uuid: 15d2c29b-dc20-48a9-910d-e1af8948ed08
   Total devices 2 FS bytes used 4.38TiB
   devid1 size 5.45TiB used 5.16TiB path /dev/mapper/dev-sdb1
   devid2 size 8.65TiB used 5.16TiB path /dev/mapper/dev-sda3

  The total size is less than the single devices size because during the
  process I managed to free up 1 Tb of data. Anyway, I looked at the
  screen containing the balance command and it actually terminated with
  a segfault, and dmesg was reporting this:

  [ven dic 24 13:04:06 2021] BTRFS info (device dm-5): relocating block group 
2177892352 flags data
  [ven dic 24 13:04:43 2021] BTRFS info (device dm-5): found 462 extents, 
stage: move data extents
  [ven dic 24 13:04:44 2021] BTRFS info (device dm-5): found 462 extents, 
stage: update data pointers
  [ven dic 24 13:04:44 2021] BTRFS info (device dm-5): relocating block group 
1104150528 flags data
  [ven dic 24 13:05:22 2021] BTRFS info (device dm-5): found 2625 extents, 
stage: move data extents
  [ven dic 24 13:05:23 2021] BTRFS info (device dm-5): found 2625 extents, 
stage: update data pointers
  [ven dic 24 13:05:24 2021] BTRFS info (device dm-5): relocating block group 
30408704 flags metadata|dup
  [ven dic 24 13:05:56 2021] BTRFS info (device dm-5): found 2412 extents, 
stage: move data extents
  [ven dic 24 13:06:00 2021] BTRFS info (device dm-5): relocating block group 
22020096 flags system|dup
  [ven dic 24 13:06:01 2021] BTRFS info (device dm-5): balance: ended with 
status: 0
  [ven dic 24 13:06:01 2021] BUG: unsupported FP instruction in kernel mode
  [ven dic 24 13:06:01 2021] FPEXC == 0x4700
  [ven dic 24 13:06:01 2021] Internal error: Oops - undefined instruction: 0 
[#1] SMP ARM
  [ven dic 24 13:06:01 2021] Modules linked in: rpcsec_gss_krb5 veth cdc_acm 
aes_arm_bs crypto_simd cryptd dm_crypt dm_mod fuse xt_nat xt_tcpudp 
xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype 
iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
br_netfilter bridge stp llc overlay sg sch_fq_codel nfsd ip_tables x_tables 
ipv6 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq raid1 raid0 
linear md_mod hid_logitech_hidpp joydev hid_logitech_dj brcmfmac brcmutil vc4 
sha256_generic v3d cec gpu_sched drm_kms_helper cfg80211 bcm2835_codec(C) 
raspberrypi_hwmon rfkill bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_mmal_vchiq(C) 
v4l2_mem2mem videobuf2_vmalloc videobuf2_dma_contig videobuf2_memops drm 
videobuf2_v4l2 videobuf2_common vc_sm_cma(C) videodev snd_bcm2835(C) mc 
drm_panel_orientation_quirks snd_soc_core rpivid_mem snd_compress 
snd_pcm_dmaengine snd_pcm snd_timer snd syscopyarea sysfillrect
  [ven dic 24 13:06:01 2021]  sysimgblt fb_sys_fops backlight uio_pdrv_genirq 
nvmem_rmem uio [last unloaded: cdc_acm]
  [ven dic 24 13:06:01 2021] CPU: 3 PID: 9141 Comm: btrfs Tainted: G C  
  5.10.63-v7l+ #1459
  [ven dic 24 13:06:01 2021] Hardware name: BCM2711
  [ven dic 24 13:06:01 2021] PC is at vfp_reload_hw+0x30/0x44
  [ven dic 24 13:06:01 2021] LR is at __und_usr_fault_32+0x0/0x8
  [ven dic 24 13:06:01 2021] pc : []lr : []psr: 
a0070013
  [ven dic 24 13:06:01 2021] sp : ca0adfb0  ip : ca0adf30  fp : 0003
  [ven dic 24 13:06:01 2021] r10: ca0ac1f8  r9 : c0201024  r8 : c1205048
  [ven dic 24 13:06:01 2021] r7 : 0001  r6 :   r5 : c0288068  r4 : 
c88f60f8
  [ven dic 24 13:06:01 2021] r3 : c135607c  r2 : b6cfeb8c  r1 : ae24b2ce  r0 : 
f421070d
  [ven dic 24 13:06:01 2021] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA 
ARM  Segment user
  [ven dic 24 13:06:01 2021] Control: 30c5383d  Table: 0335dd80  DAC: 
  [ven dic 24 13:06:01 2021] Process btrfs (pid: 9141, stack limit = 0x7d756e7e)
  [ven dic 24 13:06:01 2021] Stack: (0xca0adfb0 to 0xca0ae000)
  [ven dic 24 13:06:01 2021] dfa0: 00ad81d2 
00491e87 0008 002c
  [ven dic 24 13:06:01 2021] dfc0: 0008 b6d95d28 00491e8f   
00491e87 b6cef66d b6d95e4c
  [ven dic 24 13:06:01 2021] dfe0: 00ad81d2 be903718 b6cfa6d5 b6cfeb8c 80070010 
  
  [ven dic 24 

[Touch-packages] [Bug 1955965] Re: 21.10 cannot enter desktop after blacklist nouveau driver

2022-01-04 Thread Brian Murray
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  21.10 cannot enter desktop after blacklist nouveau driver

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 21.10 can NOT enter desktop after:
  1) install Nvidia 470
  2) blacklist nouveau driver

  --

  why blacklist nouveau?

  External HDMI monitor render 0.5 frames/second when turn off built-in
  monitor. Render normally if both build-in and external HDMI monitor
  are on.

  Blacklisting nouveau fix `0.5 frames/s` problem in Ubuntu 21.04, but
  cannot enter desktop in Ubuntu 21.10

  ---

  why not use Ubuntu 21.04 ?

  Ubuntu 21.04 render incorrectly, for example, if:
  1) built-in monitor: scale=125%, resolution=4000x2000
  2) external monitor: scale=100%, resulution=2000x1000

  Ubuntu 21.10 render correctly.

  ---
  $ lspci
  00:00.0 Host bridge: Intel Corporation Device 9b44 (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 05)
  01:00.0 VGA compatible controller: NVIDIA Corporation Device 1f99 (rev a1)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02)
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1955965/+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 1956115] Re: ubuntu-advantage-tools ' MOTD is incompatible with Ubuntu Legal's MOTD opt-out directions.

2022-01-04 Thread Brian Murray
Its not clear to me what exactly the bug you are reporting is about. The
file '/etc/default/motd-news-config' is provided by the package motd-
news-config which in turn is part of the cloud-image, server, and
ubuntu-server-raspi packages.  If that package is not installed then the
file will not exist and you should not see the motd-news message. The
opt out directions to which you have linked say the following "The motd-
news portion is highlighted in green, the other pieces of the MOTD are
informational only and do not reach out to the internet for any
information". Could you please elaborate on what you want this bug to be
about?

** Tags removed: rls-jj-incoming

** Changed in: base-files (Ubuntu)
   Status: New => Incomplete

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  ubuntu-advantage-tools ' MOTD is incompatible with Ubuntu Legal's MOTD
  opt-out directions.

Status in base-files package in Ubuntu:
  Incomplete
Status in ubuntu-advantage-tools package in Ubuntu:
  Incomplete

Bug description:
  https://ubuntu.com/legal/motd

  This file does not exist in Jammy 22.04.

  This wouldn't be a problem if it was actually removable without having
  to build custom metapackages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1956115/+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 1956115] Re: ubuntu-advantage-tools ' MOTD is incompatible with Ubuntu Legal's MOTD opt-out directions.

2022-01-04 Thread Brian Murray
** Package changed: ubuntu-meta (Ubuntu) => base-files (Ubuntu)

** Tags added: rls-jj-incoming

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

Title:
  ubuntu-advantage-tools ' MOTD is incompatible with Ubuntu Legal's MOTD
  opt-out directions.

Status in base-files package in Ubuntu:
  New
Status in ubuntu-advantage-tools package in Ubuntu:
  New

Bug description:
  https://ubuntu.com/legal/motd

  This file does not exist in Jammy 22.04.

  This wouldn't be a problem if it was actually removable without having
  to build custom metapackages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1956115/+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 1952947] Re: ubuntu-bug -w doesn't work under wayland

2021-12-17 Thread Brian Murray
bdmurray@clean-impish-amd64:~$ ubuntu-bug -w
^CTraceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 597, in 
app.run_argv()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 734, in run_argv
(out, err) = xprop.communicate()
  File "/usr/lib/python3.9/subprocess.py", line 1134, in communicate
stdout, stderr = self._communicate(input, endtime, timeout)
  File "/usr/lib/python3.9/subprocess.py", line 1979, in _communicate
ready = selector.select(timeout)
  File "/usr/lib/python3.9/selectors.py", line 416, in select
fd_event_list = self._selector.poll(timeout)
KeyboardInterrupt

The problem is likely with the xprop.communicate() call.

** Summary changed:

- nothing happens when trying to report a bug with -w after chosing the window
+ ubuntu-bug -w doesn't work under wayland

** Tags added: rls-jj-incoming

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

Title:
  ubuntu-bug -w doesn't work under wayland

Status in apport package in Ubuntu:
  New

Bug description:
  I want to report a Bug about the application Studio Controls.

  As I did it already quite a few times, I run "ubuntu-bug -w", get a
  message that I can select the window of the app I want to report a bug
  about after closing this message.

  I close the message with a click on the appropriate button.

  I click on the window of the application "Studio Controls" that I want
  to report a bug about.

  Nothing happens.

  I wait for a few minutes. Still nothing happens.

  In the console where I started ubuntu-bug -w I see the following
  message:

  (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed


  What I expect:

  Usaully when I use this procedure, after a relatively short while a
  new message window pops up asking me if the bug should be reported and
  showing me the data that is sent to Launchpad.

  I tried other applications, too, same effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apport 2.20.11-0ubuntu71
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  1 20:01:23 2021
  InstallationDate: Installed on 2020-04-12 (597 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+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 1954320] Re: Add privacy screen modules to the initrd

2021-12-16 Thread Brian Murray
** Also affects: initramfs-tools (Ubuntu Jammy)
   Importance: High
   Status: Confirmed

** Tags removed: rls-jj-incoming

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

Title:
  Add privacy screen modules to the initrd

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Jammy:
  Confirmed

Bug description:
  Starting with kernel 5.17 the kernel supports the builtin privacy
  screens built into the LCD panel of some new laptop models.

  This means that the drm drivers will now return -EPROBE_DEFER from
  their probe() method on models with a builtin privacy screen when the
  privacy screen provider driver has not been loaded yet.

  To avoid any regressions Ubuntu should modify its initrd generation
  tool to include privacy screen provider drivers in the initrd (at
  least on systems with a privacy screen), before 5.17 kernels start
  showing up in the Ubuntu repos.

  If this change is not made, then users using a graphical bootsplash
  (plymouth) will get an extra boot-delay of up to 8 seconds
  (DeviceTimeout in plymouthd.defaults) before plymouth will show and
  when using disk-encryption where the LUKS password is requested from
  the initrd, the system may fallback to text-mode after these 8
  seconds.

  I've written a patch with the necessary changes for dracut, which
  might be useful as an example for how to deal with this, see:
  https://github.com/dracutdevs/dracut/pull/1666

  ATM the only kms driver using privacy screens is the i915 driver and
  the only provider is the thinkpad_acpi driver. But both are likely to
  change (and change soon!), so the detection really should be made
  dynamic as has been done in the dracut patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1954320/+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 1954320] Re: Add privacy screen modules to the initrd

2021-12-16 Thread Brian Murray
** Tags added: fr-1938

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

Title:
  Add privacy screen modules to the initrd

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Starting with kernel 5.17 the kernel supports the builtin privacy
  screens built into the LCD panel of some new laptop models.

  This means that the drm drivers will now return -EPROBE_DEFER from
  their probe() method on models with a builtin privacy screen when the
  privacy screen provider driver has not been loaded yet.

  To avoid any regressions Ubuntu should modify its initrd generation
  tool to include privacy screen provider drivers in the initrd (at
  least on systems with a privacy screen), before 5.17 kernels start
  showing up in the Ubuntu repos.

  If this change is not made, then users using a graphical bootsplash
  (plymouth) will get an extra boot-delay of up to 8 seconds
  (DeviceTimeout in plymouthd.defaults) before plymouth will show and
  when using disk-encryption where the LUKS password is requested from
  the initrd, the system may fallback to text-mode after these 8
  seconds.

  I've written a patch with the necessary changes for dracut, which
  might be useful as an example for how to deal with this, see:
  https://github.com/dracutdevs/dracut/pull/1666

  ATM the only kms driver using privacy screens is the i915 driver and
  the only provider is the thinkpad_acpi driver. But both are likely to
  change (and change soon!), so the detection really should be made
  dynamic as has been done in the dracut patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1954320/+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 1953301] Re: Segfault on AArch64 caused by OpenSSL affecting numerous packages

2021-12-16 Thread Brian Murray
** Tags removed: rls-ff-incoming

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

Title:
  Segfault on AArch64 caused by OpenSSL affecting numerous packages

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  OpenSSL causes crashes when reaching to some URLs on AArch64 platform,
  affecting Ubuntu, but not Fedora for instance.

  Initially reported in https://mediasoup.discourse.group/t/mediasoup-
  worker-default-make-failed/3647/12, more details and reproductions in
  https://github.com/mesonbuild/meson/issues/9690

  Affects curl, wget, python and probably everything else.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1953301/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts

2021-12-15 Thread Brian Murray
The version of gdb in focal-proposed built fine with the tests enabled
and the timeouts in the buildlog were not an issue.

[  3:25PM 11723 ]  [ bdmurray@impulse:/tmp ]
 $ cat buildlog_ubuntu-focal-armhf.gdb_9.2-0ubuntu1\~20.04.1_BUILDING.txt | 
fgrep '(timeout)'|wc -l9

I don't know what doko's plans are for the upload in the focal-proposed
so won't comment on the block-proposed question.

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

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Incomplete
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in gdb source package in Focal:
  Fix Committed
Status in glibc source package in Focal:
  Fix Committed
Status in gdb source package in Groovy:
  Won't Fix
Status in glibc source package in Groovy:
  Won't Fix
Status in gdb source package in Hirsute:
  Won't Fix
Status in glibc source package in Hirsute:
  Won't Fix
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Released

Bug description:
  [Impact]

  * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is
  not installed.

  [Test Plan]

  * Check that ld.so is not stripped on armhf:
  $  /lib/*/ld-2.31.so
  libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, 
EABI5 version 1 (SYSV), dynamically linked, 
BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not 
stripped

  * Check that ld.so is stripped on amd64:

  $ file /lib/x86_64-linux-gnu/ld-2.31.so
  /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, 
version 1 (SYSV), dynamically linked, 
BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped

  [Where problems could occur]

  * The fix is not stripping ld.so on armhf. Not stripping it comes with
  a notable increase in file size and it may be performance critical
  109K stripped vs 1.3M unstripped. Accidentally ld.so could be left
  unstripped on other architectures, but the test plan covers checking
  that, at least on amd64. Other than those not stripping ld.so should
  not cause any issue.

  [Original Bug Text]

  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1927192/+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


  1   2   3   4   5   6   7   8   9   10   >