[Touch-packages] 自动回复: [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files

[lizehao]

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space--or provide an automatic tool for
  removal of old files

Status in initramfs-tools package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

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


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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files

[Raghvendra Giri]

If you are doing manual partitioning keep at least 1gb space for /boot 
partition. 
update for above post

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space--or provide an automatic tool for
  removal of old files

Status in initramfs-tools package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

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


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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files

[Raghvendra Giri]

The solution is listed in ubuntu documentation.

first check space of /boot

>: df -h

>: sudo apt-get autoremove

this should freeup some space and 90% times this will resolve your
issue.

if you have manually installed and still the old files are not purged
follow the link below

https://help.ubuntu.com/community/RemoveOldKernels

this still works for ubunt 22.04  /boot folder issues resolution,
cleaning /boot folder removing older files

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space--or provide an automatic tool for
  removal of old files

Status in initramfs-tools package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

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


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

[Touch-packages] [Bug 2049247] Re: Broken IPv4 support on IPv6-preferring networks (v255)

[Florian Bach]

Upstream has fixed this for v256 and has indicated the fix will be
backported to v255.

https://github.com/systemd/systemd/commit/7dc431839eeeffe6ed65acbe9bfe2a6e89422086

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

Title:
  Broken IPv4 support on IPv6-preferring networks (v255)

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

Bug description:
  I noticed a bug in systemd version 255 which is currently available in
  noble-proposed (255.2-3ubuntu1).

  I have already reported to upstream at
  https://github.com/systemd/systemd/issues/30891 but there's no fix
  available yet as of today.

  I'm still reporting the bug here anyways because this bug can, under
  some conditions, result in the loss of IPv4 network connectivity in a
  completely standard Ubuntu 24.04 installation just by updating to
  systemd 255. I'm hoping that that's okay even though it's a bug caused
  by upstream not by Ubuntu; just because it could have a bad impact if
  this version ends up in 24.04 as it is.

  ---

  In systemd version 255, a feature has been added to "support" the
  IPv6-only DHCP option 108 defined in RFC8925. I'm putting "support" in
  quotation marks because one functionality that this RFC marks as a
  requirement is not implemented in systemd yet.

  To summarize: Option 108 can be sent by a DHCPv4 client to signal to
  the DHCPv4 server: "Hey, if (and only if) your network has proper IPv6
  support and a working NAT64 gateway, I don't really need my own IPv4
  address, I can handle it using 464XLAT and NAT64". The point of that
  option is to be able to run a Dual Stack network, where only clients
  that really need IPv4 (older Linux, Windows, etc.) will receive an
  IPv4 from DHCP, and clients that don't need IPv4 (Android, MacOS,
  Linux with systemd >=255, etc.) won't receive one from DHCP and
  instead set up a 464XLAT for outgoing IPv4 connectivity.

  This new code in systemd is enabled by default (the option
  "IPv6OnlyMode" defaults to "yes"). However, systemd does not actually
  have code to set up a 464XLAT yet (which violates the RFC).

  This means that systemd signals to the DHCPv4 server "Hey, I don't
  need IPv4, I'll just use 464XLAT and NAT64" but then it doesn't
  actually do that. Updating systemd on an Ubuntu 24.04 installation
  (where systemd-networkd is used) will result in the loss of the DHCP-
  assigned IPv4 address, breaking network connectivity for all IPv4-only
  applications.

  ---

  Information on how to reproduce this issue can be found in detail in
  the github bug report linked above, but to summarize:

  1. Have a Dual Stack network that announces a NAT64 through RAs or through 
DNS (or, ideally, both)
  2. Configure your DHCPv4 server to hand out option 108 ("v6-only-preferred")
  3. Connect an Ubuntu machine with systemd < 255.
  4. Notice that IPv4 connectivity is working fine.
  5. Update to systemd = 255.
  6. Notice that there's no IPv4 connectivity anymore and IPv4-only apps break.

  ---

  The proper fix for this issue to make systemd conform to the RFC would
  be to implement a 464XLAT. However that's not an easy task and most
  certainly not something that would end up as a hotfix / patch release.
  A good workaround for this bug would be, in my opinion, to change the
  default value for the "IPv6OnlyMode" to "no" when compiling systemd.

  That way, the RFC-violating code doesn't run by default, and if a user
  does set up a 464XLAT on their machine in some other way (outside of
  systemd) they can just change their config to include
  "IPv6OnlyMode=yes" and it'll be working as intended.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd 255.2-3ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Jan 13 07:05:42 2024
  InstallationDate: Installed on 2024-01-12 (0 days ago)
  InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release amd64 
(20231011)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
  Lsusb-t:
   /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 001: Dev 002, If 0, Class=Human Interface Device, 
Driver=usbhid, 12M
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic 
root=UUID=b5e6aabf-881a-4589-85ae-688f41df0be7 ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to noble on 2024-01-12 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  

[Touch-packages] [Bug 2051540] Re: ufw ftbfs with Python 3.12 as default

[Jamie Strandboge]

fyi, I plan to fix this but probably not til next week. My plan is to
adjst the import to conditionally (or fall back to) import
setuptools.distutil and then adjust the Build-Depends/autopkgtests to
specify python3-setuptools.

I may do something else longer term, but that should get things going
again.

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

Title:
  ufw ftbfs with Python 3.12 as default

Status in ufw:
  Fix Committed
Status in ufw package in Ubuntu:
  Confirmed
Status in ufw package in Debian:
  Fix Released

Bug description:
  ==
  ERROR: test_ufwcommand_parse 
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
  Test UFWCommand.parse()
  --
  Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in 
test_ufwcommand_parse
  self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
  ^
  AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did 
you mean: 'assertEqual'?

  ==
  ERROR: test_ufwcommand_rule_get_command 
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
  Test UFWCommand(Route)Rule.get_command()
  --
  Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in 
test_ufwcommand_rule_get_command
  self.assertEquals(len(errors), 0,
  ^
  AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did 
you mean: 'assertEqual'?

  --
  Ran 24 tests in 7.584s

  FAILED (errors=9)
  test_skeleton
  test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
  Test example dummy test ... ok

  --
  Ran 1 test in 0.000s

  OK

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


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

[Touch-packages] [Bug 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled

[Matthew Ruffell]

Attached is a debdiff that solves this issue on Jammy.

** Patch added: "Debdiff for coreutils on Jammy"
   
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2033892/+attachment/5745181/+files/lp2033892_jammy.debdiff

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

Title:
  ls -l triggers mount of autofs shares when --ghost option is present
  or browse_mode is enabled

Status in coreutils package in Ubuntu:
  Fix Released
Status in coreutils source package in Jammy:
  In Progress
Status in coreutils package in Fedora:
  Fix Released

Bug description:
  Release: 22.04.3 LTS
  coreutils 8.32-4.1ubuntu1

  ls triggers unwanted mounts of autofs filesystems

  cause: coreutils 8.32.4.1ubuntu1 uses statx which not pass the
  AT_NO_AUTOMOUNT flag

  This bug is also known (and fixed) at Redhat
  https://bugzilla.redhat.com/show_bug.cgi?id=2044981

  upstream commits:
  
https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-177-g85c975df2c2
  
https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-178-g92cb8427c53

  fedora commit
  
https://src.fedoraproject.org/rpms/coreutils/c/d736cafa20f13eeb037a3950bdbb4b63dc39b7e3?branch=f35

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


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

[Touch-packages] [Bug 2051540] Re: ufw ftbfs with Python 3.12 as default

[Alex Murray]

Both deb8 tests already declares a Depends on python3-distutils - and we
can see that the current test runs all used the 3.11 based
python3-distutils - do we need a no-change-rebuild of python3-stdlib-
extensions so that it builds against python 3.12?

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

Title:
  ufw ftbfs with Python 3.12 as default

Status in ufw:
  Fix Committed
Status in ufw package in Ubuntu:
  Confirmed
Status in ufw package in Debian:
  Fix Released

Bug description:
  ==
  ERROR: test_ufwcommand_parse 
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
  Test UFWCommand.parse()
  --
  Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in 
test_ufwcommand_parse
  self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
  ^
  AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did 
you mean: 'assertEqual'?

  ==
  ERROR: test_ufwcommand_rule_get_command 
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
  Test UFWCommand(Route)Rule.get_command()
  --
  Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in 
test_ufwcommand_rule_get_command
  self.assertEquals(len(errors), 0,
  ^
  AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did 
you mean: 'assertEqual'?

  --
  Ran 24 tests in 7.584s

  FAILED (errors=9)
  test_skeleton
  test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
  Test example dummy test ... ok

  --
  Ran 1 test in 0.000s

  OK

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


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

[Touch-packages] [Bug 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled

[Matthew Ruffell]

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

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

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

** Changed in: coreutils (Ubuntu Jammy)
 Assignee: (unassigned) => Matthew Ruffell (mruffell)

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

Title:
  ls -l triggers mount of autofs shares when --ghost option is present
  or browse_mode is enabled

Status in coreutils package in Ubuntu:
  Fix Released
Status in coreutils source package in Jammy:
  In Progress
Status in coreutils package in Fedora:
  Fix Released

Bug description:
  Release: 22.04.3 LTS
  coreutils 8.32-4.1ubuntu1

  ls triggers unwanted mounts of autofs filesystems

  cause: coreutils 8.32.4.1ubuntu1 uses statx which not pass the
  AT_NO_AUTOMOUNT flag

  This bug is also known (and fixed) at Redhat
  https://bugzilla.redhat.com/show_bug.cgi?id=2044981

  upstream commits:
  
https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-177-g85c975df2c2
  
https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-178-g92cb8427c53

  fedora commit
  
https://src.fedoraproject.org/rpms/coreutils/c/d736cafa20f13eeb037a3950bdbb4b63dc39b7e3?branch=f35

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


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

[Touch-packages] [Bug 2052669] Re: update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/in

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. From your description it is hard to tell if you
experienced one or multiple bugs. Does running "update-initramfs -u -k
{version}" succeed?

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

Title:
  update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic E:
  /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-
  initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  My bare metal server would not restart. After some research, I found
  out that I get the following error:

  "Kernel Panic - not syncing: VFS: Unable to mount root fs on
  unknown-block(0,0)"

  I started up in a Rescue, and followed the steps in
  https://askubuntu.com/a/41939/36315, to "update-initramfs -u -k
  {version}".

  Then I got the below message:

  update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.

  I found a workaround for it: https://askubuntu.com/a/916283/36315

     "sudo chmod -x /usr/share/initramfs-tools/hooks/fixrtc"

  I did that for every file in usr/share/initramfs-tools/hooks/*

  After that I did

  update-initramfs -u -k all
  update-grub

  I rebooted from Rescue, and then I got the following error:

  "Kernel Panic - not syncing: No working init found. Try passing
  init= option to kernel."

  AFter this, I reinstalled Ubuntu 22.04 on my bare metal server, but
  even after reinstall, I get the "No working init found" error message.

  I have no idea now how to fix this.

  Any help is greatly appreciated!

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


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

[Touch-packages] [Bug 2052669] Re: update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/in

[Imri Paloja]

** Description changed:

- My bare metal server would not restart,
- 
- Found out that I got the following error:
+ My bare metal server would not restart. After some research, I found out
+ that I get the following error:
  
  "Kernel Panic - not syncing: VFS: Unable to mount root fs on
  unknown-block(0,0)"
  
  I started up in a Rescue, and followed the steps in
  https://askubuntu.com/a/41939/36315, to "update-initramfs -u -k
  {version}".
  
  Then I got the below message:
  
  update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.
  
  I found a workaround for it: https://askubuntu.com/a/916283/36315
  
     "sudo chmod -x /usr/share/initramfs-tools/hooks/fixrtc"
  
  I did that for every file in usr/share/initramfs-tools/hooks/*
  
  After that I did
  
  update-initramfs -u -k all
  update-grub
  
  I rebooted from Rescue, and then I got the following error:
  
- "Kernel Panic - not syncing: No working init found. Try passing
+ "Kernel Panic - not syncing: No working init found. Try passing
  init= option to kernel."
  
- I reinstalled Ubuntu 22.04 on this bare metal, but even after reinstall,
- I get the No working init found.
+ AFter this, I reinstalled Ubuntu 22.04 on my bare metal server, but even
+ after reinstall, I get the "No working init found" error message.
+ 
+ I have no idea now how to fix this.
  
  Any help is greatly appreciated!

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

Title:
  update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic E:
  /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-
  initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  My bare metal server would not restart. After some research, I found
  out that I get the following error:

  "Kernel Panic - not syncing: VFS: Unable to mount root fs on
  unknown-block(0,0)"

  I started up in a Rescue, and followed the steps in
  https://askubuntu.com/a/41939/36315, to "update-initramfs -u -k
  {version}".

  Then I got the below message:

  update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.

  I found a workaround for it: https://askubuntu.com/a/916283/36315

     "sudo chmod -x /usr/share/initramfs-tools/hooks/fixrtc"

  I did that for every file in usr/share/initramfs-tools/hooks/*

  After that I did

  update-initramfs -u -k all
  update-grub

  I rebooted from Rescue, and then I got the following error:

  "Kernel Panic - not syncing: No working init found. Try passing
  init= option to kernel."

  AFter this, I reinstalled Ubuntu 22.04 on my bare metal server, but
  even after reinstall, I get the "No working init found" error message.

  I have no idea now how to fix this.

  Any help is greatly appreciated!

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


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

[Touch-packages] [Bug 2052669] [NEW] update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/

[Imri Paloja]

Public bug reported:

My bare metal server would not restart,

Found out that I got the following error:

"Kernel Panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)"

I started up in a Rescue, and followed the steps in
https://askubuntu.com/a/41939/36315, to "update-initramfs -u -k
{version}".

Then I got the below message:

update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic
E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.

I found a workaround for it: https://askubuntu.com/a/916283/36315

   "sudo chmod -x /usr/share/initramfs-tools/hooks/fixrtc"

I did that for every file in usr/share/initramfs-tools/hooks/*

After that I did

update-initramfs -u -k all
update-grub

I rebooted from Rescue, and then I got the following error:

"Kernel Panic - not syncing: No working init found. Try passing
init= option to kernel."

I reinstalled Ubuntu 22.04 on this bare metal, but even after reinstall,
I get the No working init found.

Any help is greatly appreciated!

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

- My bare metal server would not restart, I started up in a Rescue,
- installed update, then I got the below message:
+ My bare metal server would not restart,
+ 
+ Found out that I got the following error:
+ 
+ "Kernel Panic - not syncing: VFS: Unable to mount root fs on
+ unknown-block(0,0)"
+ 
+ 
+ I started up in a Rescue, installed updates, then I got the below message:
  
  update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.
  
  I found a workaround for it: https://askubuntu.com/a/916283/36315
  
-"sudo chmod -x /usr/share/initramfs-tools/hooks/fixrtc"
+    "sudo chmod -x /usr/share/initramfs-tools/hooks/fixrtc"
  
  I did that for every file in usr/share/initramfs-tools/hooks/*
  
  After that I did
  
- update-initramfs -u -k all
- update-grub
- 
+ update-initramfs -u -k all
+ update-grub
  
  I rebooted from Rescue, and I got the following error:
  
- 
- "Kernel Panic - not syncing: No working init found. Try passing init= option 
to kernel."
- 
+ "Kernel Panic - not syncing: No working init found. Try passing init=
+ option to kernel."
  
  I reinstalled Ubuntu 22.04 on this bare metal, but even after reinstall,
  I get the No working init found.
  
  Any help is greatly appreciated!

** Description changed:

  My bare metal server would not restart,
  
  Found out that I got the following error:
  
- "Kernel Panic - not syncing: VFS: Unable to mount root fs on
+ "Kernel Panic - not syncing: VFS: Unable to mount root fs on
  unknown-block(0,0)"
  
+ I started up in a Rescue, and followed the steps in
+ https://askubuntu.com/a/41939/36315, to "update-initramfs -u -k
+ {version}".
  
- I started up in a Rescue, installed updates, then I got the below message:
+ Then I got the below message:
  
  update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.
  
  I found a workaround for it: https://askubuntu.com/a/916283/36315
  
     "sudo chmod -x /usr/share/initramfs-tools/hooks/fixrtc"
  
  I did that for every file in usr/share/initramfs-tools/hooks/*
  
  After that I did
  
  update-initramfs -u -k all
  update-grub
  
- I rebooted from Rescue, and I got the following error:
+ I rebooted from Rescue, and then I got the following error:
  
- "Kernel Panic - not syncing: No working init found. Try passing init=
- option to kernel."
+ "Kernel Panic - not syncing: No working init found. Try passing
+ init= option to kernel."
  
  I reinstalled Ubuntu 22.04 on this bare metal, but even after reinstall,
  I get the No working init found.
  
  Any help is greatly appreciated!

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

Title:
  update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic E:
  /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-
  initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  My bare metal server would not restart,

  Found out that I got the following error:

  "Kernel Panic - not syncing: VFS: Unable to mount root fs on
  unknown-block(0,0)"

  I started up in a Rescue, and followed the steps in
  https://askubuntu.com/a/41939/36315, to "update-initramfs -u -k
  {version}".

  Then I got the below message:

  update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic
  E: 

[Touch-packages] [Bug 2051997] Re: bdebstrap fails to build with python3-defaults 3.12

[Matthias Klose]

** Changed in: python3-defaults (Ubuntu)
   Status: New => Invalid

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

Title:
  bdebstrap fails to build with python3-defaults 3.12

Status in bdebstrap package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  Invalid
Status in bdebstrap package in Debian:
  New

Bug description:
  When building bdebstrap with python3-default 3.12 the following error occurs
  --
  usr/bin/python3.12 -m pylint --rcfile=/<>/tests/pylint.conf -- 
/<>/bdebstrap tests /<>/setup.py
  FAIL
  test_flake8 (tests.test_shellcheck.ShellcheckTestCase.test_flake8)
  Test: Run shellcheck on Shell source code. ... Running following command:
  shellcheck /<>/hooks/disable-units 
/<>/hooks/enable-units
  ok

  ==
  FAIL: test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
  Test: Run pylint on Python source code.
  --
  Traceback (most recent call last):
File "/<>/tests/test_pylint.py", line 74, in test_pylint
  self.fail("\n".join(msgs))
  AssertionError: pylint found issues:
  * Module setup
  /<>/setup.py:26:0: E0401: Unable to import 'distutils.log' 
(import-error)
  /<>/setup.py:27:0: E0401: Unable to import 
'distutils.command.build' (import-error)
  /<>/setup.py:28:0: E0401: Unable to import 
'distutils.command.clean' (import-error)
  /<>/setup.py:57:4: C0116: Missing function or method docstring 
(missing-function-docstring)
  /<>/setup.py:54:0: R0903: Too few public methods (1/2) 
(too-few-public-methods)
  /<>/setup.py:65:4: C0116: Missing function or method docstring 
(missing-function-docstring)
  /<>/setup.py:62:0: R0903: Too few public methods (1/2) 
(too-few-public-methods)

  --

  due to removal of distutils in python 3.12

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


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

[Touch-packages] [Bug 2051990] Re: python3-defaults 3.12 causes aubio to fail to build from source

[Matthias Klose]

** Changed in: python3-defaults (Ubuntu)
   Status: New => Invalid

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

Title:
  python3-defaults 3.12 causes aubio to fail to build from source

Status in aubio package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  Invalid
Status in aubio package in Debian:
  New

Bug description:
  python3 ./waf configure --verbose --destdir=debian/tmp --prefix=/usr 
--enable-fftw3f --libdir=/usr/lib/x86_64-linux-gnu
  /<>/waflib/Utils.py:443: SyntaxWarning: invalid escape sequence 
'\d'
return re.split('\d+$',s)[0]
  /<>/waflib/ConfigSet.py:7: SyntaxWarning: invalid escape 
sequence '\ '
re_imp=re.compile('^(#)*?([^#=]*?)\ =\ (.*?)$',re.M)
  /<>/waflib/ansiterm.py:178: SyntaxWarning: invalid escape 
sequence '\['
ansi_tokens=re.compile('(?:\x1b\[([0-9?;]*)([a-zA-Z])|([^\x1b]+))')
  Traceback (most recent call last):
File "/<>/./waf", line 164, in 
  from waflib import Scripting
File "/<>/waflib/Scripting.py", line 7, in 
  from waflib import 
Utils,Configure,Logs,Options,ConfigSet,Context,Errors,Build,Node
File "/<>/waflib/Configure.py", line 6, in 
  from waflib import ConfigSet,Utils,Options,Logs,Context,Build,Errors
File "/<>/waflib/Options.py", line 6, in 
  from waflib import Logs,Utils,Context,Errors
File "/<>/waflib/Context.py", line 5, in 
  import os,re,imp,sys
  ModuleNotFoundError: No module named 'imp'
  make[1]: *** [debian/rules:45: override_dh_auto_configure] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:22: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  

  Build finished at 2024-02-01T21:23:22Z

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


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

[Touch-packages] [Bug 2052482] Re: Bad packet length 2424479189 Connection corrupted

[Sergio Durigan Junior]

Thank you for taking the time to report a bug and make Ubuntu better.

I tried reproducing the bug locally using an Oracle 8 container and an
Ubuntu container.  Here are the versions of the packages:

Oracle:
# rpm -qa | grep ssh
openssh-server-8.0p1-19.el8_8.x86_64
openssh-8.0p1-19.el8_8.x86_64
openssh-clients-8.0p1-19.el8_8.x86_64
libssh-config-0.9.6-13.el8_9.noarch
libssh-0.9.6-13.el8_9.x86_64

Ubuntu:
# dpkg -l | grep ssh
ii  openssh-client  1:8.9p1-3ubuntu0.6  amd64   
 secure shell (SSH) client, for secure access to remote machines

Everything worked as expected and I was able to ssh into the Oracle
container.

After some research, I found that this specific error you're getting
might be related to CVE-2023-48795 (Terrapin attack).  More
specifically, it has to do with the cipher suites being chosen by the
client/server at the time of the login:

https://superuser.com/questions/1828501/how-to-solve-ssh-connection-corrupted-error
https://unix.stackexchange.com/questions/765347/how-do-you-mitigate-the-terrapin-ssh-attack

Even when I explicitly disable the use of CHACHA20 on the server, I
still can login successfully and I see that another cipher has been
chosen during the key exchange:

...
debug1: kex: algorithm: curve25519-sha256   
 
debug1: kex: host key algorithm: ssh-ed25519
 
debug1: kex: server->client cipher: aes128-ctr MAC: umac-...@openssh.com 
compression: none   
debug1: kex: client->server cipher: aes128-ctr MAC: umac-...@openssh.com 
compression: none
...

This leads me to believe that there might be some local configuration on
your system that's affecting the choice of a suitable cipher.  Another
option would be some bogus configuration on the server side, I think.

Could you please tell us more details about your environment?  Did you
explicitly configure your ssh client to require CHACHA20 when connecting
to this specific server?

I'm going to mark this bug as Incomplete for to reflect the fact that
we're waiting on more details from you.  Please set it back to New when
you provide the requested information.  Thanks.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-48795

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

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

Title:
  Bad packet length 2424479189 Connection corrupted

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  ssh-clent:
  uname -a :5.15.0-48-generic #54-Ubuntu
  ```
  Ubuntu 22.04.3 LTS
  OpenSSH_8.9p1 Ubuntu-3ubuntu0.6, OpenSSL 3.0.2 15 Mar 2022
  ```

  ssh-server:
  ```
  OracleLinux 8.9
  OpenSSH_8.0p1, OpenSSL 1.1.1k  FIPS 25 Mar 2021
  ```

  ```
  userxxx@userxxx-H3C-X7-030s-0274:~$ ssh 192.168.xxx.xxx -vvv
  OpenSSH_8.9p1 Ubuntu-3ubuntu0.6, OpenSSL 3.0.2 15 Mar 2022
  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 *
  debug2: resolve_canonicalize: hostname 192.168.xxx.xxx is address
  debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> 
'/home/userxxx/.ssh/known_hosts'
  debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> 
'/home/userxxx/.ssh/known_hosts2'
  debug3: ssh_connect_direct: entering
  debug1: Connecting to 192.168.xxx.xxx [192.168.xxx.xxx] port 22.
  debug3: set_sock_tos: set socket 3 IP_TOS 0x10
  debug1: Connection established.
  debug1: identity file /home/userxxx/.ssh/id_rsa type 0
  debug1: identity file /home/userxxx/.ssh/id_rsa-cert type -1
  debug1: identity file /home/userxxx/.ssh/id_ecdsa type 2
  debug1: identity file /home/userxxx/.ssh/id_ecdsa-cert type -1
  debug1: identity file /home/userxxx/.ssh/id_ecdsa_sk type -1
  debug1: identity file /home/userxxx/.ssh/id_ecdsa_sk-cert type -1
  debug1: identity file /home/userxxx/.ssh/id_ed25519 type -1
  debug1: identity file /home/userxxx/.ssh/id_ed25519-cert type -1
  debug1: identity file /home/userxxx/.ssh/id_ed25519_sk type -1
  debug1: identity file /home/userxxx/.ssh/id_ed25519_sk-cert type -1
  debug1: identity file /home/userxxx/.ssh/id_xmss type -1
  debug1: identity file /home/userxxx/.ssh/id_xmss-cert type -1
  debug1: identity file /home/userxxx/.ssh/id_dsa type -1
  debug1: identity file /home/userxxx/.ssh/id_dsa-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.6
  debug1: Remote protocol version 2.0, remote software version OpenSSH_8.0
  debug1: compat_banner: match: OpenSSH_8.0 pat OpenSSH* compat 0x0400
  debug2: fd 3 setting O_NONBLOCK
  debug1: Authenticating to 192.168.xxx.xxx:22 as 'userxxx'
  debug3: record_hostkey: found key type ED25519 in file 

[Touch-packages] [Bug 2043579] Re: initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2

[dann frazier]

Yeah - maybe its just the mantic builder image that has the bad
cryptsetup config (/etc/crypttab)?

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

Title:
  initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR:
  Couldn't resolve device /dev/sda2

Status in Auto Package Testing:
  New
Status in cryptsetup package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  The autopkgtest of initramfs-tools fails on armhf on noble:

  ```
  qemu-ata-onlySKIP Test lists explicitly supported architectures, but 
the current architecture armhf isn't listed.
  unit-tests   PASS
  qemu-klibc   FAIL stderr: cryptsetup: ERROR: Couldn't resolve device 
/dev/sda2
  qemu-busybox FAIL stderr: cryptsetup: ERROR: Couldn't resolve device 
/dev/sda2
  qemu-virtio-only FAIL stderr: cryptsetup: ERROR: Couldn't resolve device 
/dev/sda2
  qemu-separate-usrFAIL stderr: cryptsetup: ERROR: Couldn't resolve device 
/dev/sda2
  qemu-panic-shell FAIL stderr: cryptsetup: ERROR: Couldn't resolve device 
/dev/sda2
  qemu-net FAIL stderr: cryptsetup: ERROR: Couldn't resolve device 
/dev/sda2
  qemu-net-dnsmasq FAIL stderr: cryptsetup: ERROR: Couldn't resolve device 
/dev/sda2
  ```

  The /usr/sbin/mkinitramfs call in build_initramfs() has following
  output:

  ```
  cryptsetup: ERROR: Couldn't resolve device /dev/sda2
  cryptsetup: WARNING: Couldn't determine root device
  copying from directory 
/tmp/autopkgtest.g0n4ix/autopkgtest_tmp/initramfs-test.qV8LgntBoK/rootdir
  ```

  The two cryptsetup log lines are printed by /usr/share/initramfs-
  tools/hooks/cryptroot (which comes from cryptsetup-initramfs)

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2043579/+subscriptions


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

[Touch-packages] [Bug 2043579] Re: initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2

[Benjamin Drung]

The autopkgtest of initramfs-tools on armhf on noble started to succeed
again (roughly on 2023-12-26).

** Changed in: initramfs-tools (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR:
  Couldn't resolve device /dev/sda2

Status in Auto Package Testing:
  New
Status in cryptsetup package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  The autopkgtest of initramfs-tools fails on armhf on noble:

  ```
  qemu-ata-onlySKIP Test lists explicitly supported architectures, but 
the current architecture armhf isn't listed.
  unit-tests   PASS
  qemu-klibc   FAIL stderr: cryptsetup: ERROR: Couldn't resolve device 
/dev/sda2
  qemu-busybox FAIL stderr: cryptsetup: ERROR: Couldn't resolve device 
/dev/sda2
  qemu-virtio-only FAIL stderr: cryptsetup: ERROR: Couldn't resolve device 
/dev/sda2
  qemu-separate-usrFAIL stderr: cryptsetup: ERROR: Couldn't resolve device 
/dev/sda2
  qemu-panic-shell FAIL stderr: cryptsetup: ERROR: Couldn't resolve device 
/dev/sda2
  qemu-net FAIL stderr: cryptsetup: ERROR: Couldn't resolve device 
/dev/sda2
  qemu-net-dnsmasq FAIL stderr: cryptsetup: ERROR: Couldn't resolve device 
/dev/sda2
  ```

  The /usr/sbin/mkinitramfs call in build_initramfs() has following
  output:

  ```
  cryptsetup: ERROR: Couldn't resolve device /dev/sda2
  cryptsetup: WARNING: Couldn't determine root device
  copying from directory 
/tmp/autopkgtest.g0n4ix/autopkgtest_tmp/initramfs-test.qV8LgntBoK/rootdir
  ```

  The two cryptsetup log lines are printed by /usr/share/initramfs-
  tools/hooks/cryptroot (which comes from cryptsetup-initramfs)

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2043579/+subscriptions


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

[Touch-packages] [Bug 2046646] Re: package fwupd 1.7.9-1~22.04.3 failed to install/upgrade: installed fwupd package post-installation script subprocess returned error exit status 127

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

/usr/sbin/update-initramfs: 175: awk: Too many levels of symbolic links

It looks like a broken setup of the awk alternative. Can you follow the 
suggestions in
https://askubuntu.com/questions/1459281/error-update-initramfs-175-awk-too-many-levels-of-symbolic-links-when-using
 to solve your issues?

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

Title:
  package fwupd 1.7.9-1~22.04.3 failed to install/upgrade: installed
  fwupd package post-installation script subprocess returned error exit
  status 127

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  i don't know lol

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: fwupd 1.7.9-1~22.04.3
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Dec 17 12:15:28 2023
  DuplicateSignature:
   package:fwupd:1.7.9-1~22.04.3
   Setting up linux-firmware (20220329.git681281e4-0ubuntu3.23) ...
   /usr/sbin/update-initramfs: 175: awk: Too many levels of symbolic links
   dpkg: error processing package linux-firmware (--configure):
installed linux-firmware package post-installation script subprocess 
returned error exit status 127
  ErrorMessage: installed fwupd package post-installation script subprocess 
returned error exit status 127
  InstallationDate: Installed on 2023-12-16 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: fwupd
  Title: package fwupd 1.7.9-1~22.04.3 failed to install/upgrade: installed 
fwupd 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/2046646/+subscriptions


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

[Touch-packages] [Bug 2051709] Re: package linux-image-5.15.0-92-generic 5.15.0-92.102 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Yes, your guess was right. The relevant dpkg terminal
log says:

No space left on device

So adjusting the space was the correct solution. Therefore I am closing
this bug.

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

Title:
  package linux-image-5.15.0-92-generic 5.15.0-92.102 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:
  I feel like this was due to storage available at the time of the
  virtual build. As it hit capacity, it started to throws errors. I have
  since adjusted allotted space to 40GB from the default.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-92-generic 5.15.0-92.102
  ProcVersionSignature: Ubuntu 6.2.0-1019.19~22.04.1-azure 6.2.16
  Uname: Linux 6.2.0-1019-azure x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   linux-modules-extra-5.15.0-92-generic:amd64: Install
   linux-headers-5.15.0-92:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Mon Jan 29 10:07:21 2024
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 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
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1019-azure 
root=UUID=89ee03ba-6808-4977-a4fb-9b10174744f8 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.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-92-generic 5.15.0-92.102 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: 04/06/2022
  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: 6076-2812-1301-1065-6309-1370-01
  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:bd04/06/2022:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1:skuNone:
  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/2051709/+subscriptions


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

[Touch-packages] [Bug 2052646] Re: Errors after upgrading to package linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exite

[Benjamin Drung]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

cat: write error: No space left on device

So generating the initramfs fails because your /boot partition is full.
Please cleanup your boot partition. Feel free to continue to report any
other bugs you may find.


** This bug has been marked a duplicate of bug 798414
   update-initramfs should produce a more helpful error message when there 
isn't enough  free space--or provide an automatic tool for removal of old files

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

Title:
  Errors after upgrading to package linux-image-6.5.0-17-generic
  6.5.0-17.17~22.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:
  New

Bug description:
  See attached debug information.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  7 10:30:45 2024
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2020-04-30 (1377 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: initramfs-tools
  Title: package linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2023-08-08 (182 days ago)

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


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

[Touch-packages] [Bug 2051540] Re: ufw ftbfs with Python 3.12 as default

[Matthias Klose]

better, but still not complete:

1186s autopkgtest [04:54:38]: test root-unittest: [---
1186s Interpreter: python3
1186s 
1186s rm -rf ./build
1186s rm -rf ./staging
1186s rm -rf ./tests/testarea ./tests/unit/tmp
1186s rm -rf ./tmp
1186s rm -rf ./snap-build
1186s rm -rf ./parts ./stage ./prime
1186s rm -f ./locales/mo/*.mo
1186s rm -f ./tests/unit/*.pyc ./tests/*.pyc ./src/*.pyc
1186s rm -rf ./tests/unit/__pycache__ ./tests/__pycache__ ./src/__pycache__
1186s rm -rf ./.coverage
1186s rm -f ./ufw   # unittest symlink
1186s = Functional Tests =
1186s net.ipv4.ip_forward = 0
1186s net.ipv6.conf.default.forwarding = 0
1186s net.ipv6.conf.all.forwarding = 0
1186s 
1186s Performing tests 'root/bugs'
1186s - installing
1187s Traceback (most recent call last):
1187s   File "/tmp/autopkgtest.qdhyuB/build.T34/src/./setup.py", line 28, in 

1187s from distutils.command.install import install as _install
1187s ModuleNotFoundError: No module named 'distutils'


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

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

Title:
  ufw ftbfs with Python 3.12 as default

Status in ufw:
  Fix Committed
Status in ufw package in Ubuntu:
  Confirmed
Status in ufw package in Debian:
  Fix Released

Bug description:
  ==
  ERROR: test_ufwcommand_parse 
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
  Test UFWCommand.parse()
  --
  Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in 
test_ufwcommand_parse
  self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
  ^
  AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did 
you mean: 'assertEqual'?

  ==
  ERROR: test_ufwcommand_rule_get_command 
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
  Test UFWCommand(Route)Rule.get_command()
  --
  Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in 
test_ufwcommand_rule_get_command
  self.assertEquals(len(errors), 0,
  ^
  AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did 
you mean: 'assertEqual'?

  --
  Ran 24 tests in 7.584s

  FAILED (errors=9)
  test_skeleton
  test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
  Test example dummy test ... ok

  --
  Ran 1 test in 0.000s

  OK

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


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

[Touch-packages] [Bug 2048914] Re: System program problem detected at every login Xubuntu Update Notifier

[spicemines]

After testing the latest Noble daily build of Xubuntu (Version
20240207), I did not experience this error. This is the third build I
have tested that did not have this error.

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

Title:
  System program problem detected at every login Xubuntu Update Notifier

Status in update-notifier package in Ubuntu:
  New
Status in whoopsie package in Ubuntu:
  Incomplete

Bug description:
  Every time I log in to my new installation of Xubuntu 24.04 (daily
  ISO) after a reboot, I get an error message that says, "System program
  problem detected." Clicking either Cancel or Report Problem only
  dismisses the pop-up without any further action. This has occurred on
  multiple computers. This began with the first boot after installation
  and occurs at each subsequent reboot upon logging in. Logging out and
  back in does not cause the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: update-notifier 3.192.66
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Jan 10 09:57:25 2024
  ExecutablePath: /usr/bin/update-notifier
  InstallationDate: Installed on 2024-01-10 (0 days ago)
  InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240110)
  ProcEnviron:
   LANG=C.UTF-8
   LANGUAGE=en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: update-notifier
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1991553] Re: can't add a private PPA

[dann frazier]

** Also affects: software-properties (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

Title:
  can't add a private PPA

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

Bug description:
  As per today's discussion in ~is :

  add-apt-repository has a bug when adding a private PPA. Quoting
  ~cjwatson :

  ===
  It asks Launchpad for all your personal archive subscriptions _that have 
tokens_.  But `Person:+archivesubscriptions` also shows subscriptions without 
tokens - the token is generated when you click on Viewt here for the first time.

  Instead, `add-apt-repository` should call `getArchiveSubscriptionURL` (not 
`getArchiveSubscriptionURLs`) for the archive it's interested in.  That 
generates tokens on-demand.  Either it will get an HTTP 401, or it will get a 
URL which it can parse for the username and password.
  ===

  Thanks !

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


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

[Touch-packages] [Bug 2052648] [NEW] After a long work on debugging GDB crashed with segmentation fault

[Ian Ilyasov]

Public bug reported:

I've been debugging PostgreSQL REL_14_STABLE branch authentication code
starting the postgres postmaster, running psql and then connecting to a
new process using `sudo gdb -p `. After a long day of it, I met
this segmentation fault. This message says, that it is definitely a bug
and I should report it, but GDB site says, that probably I should
firstly message it to the distributor, which for my laptop(x86_64) OS
Ubuntu 22.04 is Ubuntu.

```
Fatal signal: Segmentation fault
- Backtrace -
0x556f0077 ???
0x557f2859 ???
0x557f2a22 ???
0x76c4251f ???
./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0x76db1ebc ???
../sysdeps/x86_64/multiarch/strlen-evex.S:77
0x559b1671 ???
0x559b1ba4 ???
0x559b208f ???
0x559b2b89 ???
0x559c1381 ???
0x559c14be ???
0x5585b7f6 ???
0x55a387a8 ???
0x5585ea1e ???
0x5584e171 ???
0x55851308 ???
0x55845b64 ???
0x5586b9d4 ???
0x55ba4815 ???
0x55ba4cf9 ???
0x55a1aaab ???
0x558afa00 ???
0x558b1a16 ???
0x558b204e ???
0x5564815f ???
0x76c29d8f __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
0x76c29e3f __libc_start_main_impl
../csu/libc-start.c:392
0x5564dbf4 ???
0x ???
-

A fatal error internal to GDB has been detected, further
debugging is not possible.  GDB will now terminate.

This is a bug, please report it.  For instructions, see:
.
```

The only way I could reproduce this bug is to reboot and do debug using
gdb all day like I described in the begging of the message.

Sorry, if I provided little info.

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

** Attachment added: "Error message from GDB"
   
https://bugs.launchpad.net/bugs/2052648/+attachment/5745088/+files/gdb-segfault.txt

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

Title:
  After a long work on debugging GDB crashed with segmentation fault

Status in gdb package in Ubuntu:
  New

Bug description:
  I've been debugging PostgreSQL REL_14_STABLE branch authentication
  code starting the postgres postmaster, running psql and then
  connecting to a new process using `sudo gdb -p `. After a long
  day of it, I met this segmentation fault. This message says, that it
  is definitely a bug and I should report it, but GDB site says, that
  probably I should firstly message it to the distributor, which for my
  laptop(x86_64) OS Ubuntu 22.04 is Ubuntu.

  ```
  Fatal signal: Segmentation fault
  - Backtrace -
  0x556f0077 ???
  0x557f2859 ???
  0x557f2a22 ???
  0x76c4251f ???
  ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
  0x76db1ebc ???
  ../sysdeps/x86_64/multiarch/strlen-evex.S:77
  0x559b1671 ???
  0x559b1ba4 ???
  0x559b208f ???
  0x559b2b89 ???
  0x559c1381 ???
  0x559c14be ???
  0x5585b7f6 ???
  0x55a387a8 ???
  0x5585ea1e ???
  0x5584e171 ???
  0x55851308 ???
  0x55845b64 ???
  0x5586b9d4 ???
  0x55ba4815 ???
  0x55ba4cf9 ???
  0x55a1aaab ???
  0x558afa00 ???
  0x558b1a16 ???
  0x558b204e ???
  0x5564815f ???
  0x76c29d8f __libc_start_call_main
  ../sysdeps/nptl/libc_start_call_main.h:58
  0x76c29e3f __libc_start_main_impl
  ../csu/libc-start.c:392
  0x5564dbf4 ???
  0x ???
  -

  A fatal error internal to GDB has been detected, further
  debugging is not possible.  GDB will now terminate.

  This is a bug, please report it.  For instructions, see:
  .
  ```

  The only way I could reproduce this bug is to reboot and do debug
  using gdb all day like I described in the begging of the message.

  Sorry, if I provided little info.

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


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

[Touch-packages] [Bug 2052646] [NEW] Errors after upgrading to package linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exi

[Brad Stancel]

Public bug reported:

See attached debug information.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Feb  7 10:30:45 2024
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2020-04-30 (1377 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.11
SourcePackage: initramfs-tools
Title: package linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to jammy on 2023-08-08 (182 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy third-party-packages

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

Title:
  Errors after upgrading to package linux-image-6.5.0-17-generic
  6.5.0-17.17~22.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:
  New

Bug description:
  See attached debug information.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  7 10:30:45 2024
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2020-04-30 (1377 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: initramfs-tools
  Title: package linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2023-08-08 (182 days ago)

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


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

[Touch-packages] [Bug 2047450] Re: tail emits no output for sysfs files when using large page kernels

[dann frazier]

> I'm retrying these failing autopkgtests with migration-reference/0
since if they fail anyway they shouldn't hold things up.

Oh, is that something I should do in cases like this? Would that
automatically cause SRUs with failing tests to be unblocked?

> In the meantime, could you please also verify that behaviour on 4K
page size hasn't regressed? It looks like this was implied in the Test
Plan but hasn't been verified.

The patch includes a test case, which is shown to pass in the build
logs.

>From 
>https://launchpadlibrarian.net/710103864/buildlog_ubuntu-mantic-arm64.coreutils_9.1-1ubuntu2.23.10.1_BUILDING.txt.gz
> :
  PASS: tests/tail-2/tail-sysfs.sh

>From 
>https://launchpadlibrarian.net/710103862/buildlog_ubuntu-jammy-arm64.coreutils_8.32-4.1ubuntu1.1_BUILDING.txt.gz
> :
  PASS: tests/tail-2/tail-sysfs.sh

I was considering that sufficient for 4K testing because the buildders
run 4K kernels.

But it is trivial to do a manual test, and that would avoid having to
trust that the test case itself didn't have any errors masking a
failure, so:

root@mantic:~# getconf PAGESIZE
4096
root@mantic:~# dpkg -l coreutils
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  coreutils  9.1-1ubuntu2.23.10.1 arm64GNU core utilities
root@mantic:~# tail /sys/kernel/profiling 
0
root@mantic:~# 
exit
ubuntu@bizzy:~$ lxc exec jammy -- /bin/bash
root@jammy:~# getconf PAGESIZE
4096
root@jammy:~# dpkg -l coreutils
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description
+++-==-=--=
ii  coreutils  8.32-4.1ubuntu1.1 arm64GNU core utilities
root@jammy:~# tail /sys/kernel/profiling 
0
root@jammy:~#

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

Title:
  tail emits no output for sysfs files when using large page kernels

Status in coreutils package in Ubuntu:
  Fix Released
Status in coreutils source package in Jammy:
  Fix Committed
Status in coreutils source package in Lunar:
  Won't Fix
Status in coreutils source package in Mantic:
  Fix Committed
Status in coreutils source package in Noble:
  Fix Released

Bug description:
  [Impact]
  Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 
(optional -64k flavors). When booted on 64K kernels, tail emits no output when 
tailing a sysfs file. The difference in behavior can be a source for bugs in 
scripts that use tail, and general user confusion.

  [Test Plan]
  The upstream fix includes a test case that tails the /sys/kernel/profiling 
file, if it exists. That case would fail with an unfixed coreutils package as 
shown below:

  = When booted on a 4K kernel =
  ubuntu@gunyolk:~$ tail /sys/kernel/profiling 
  0

  = When booted on a 64K kernel =
  ubuntu@gunyolk:~$ tail /sys/kernel/profiling 
  ubuntu@gunyolk:~$ 

  Since the upstream test cases are executed at build time, the existing
  tests and this new test will be used  to regression test behavior.
  This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We
  should also do a manual verification on arm64 w/ the 64K kernel since
  that case is not covered by our builders.

  [Where Problems Could Occur]
  The biggest risk for a regression I see is due to the side-effect of the fix 
now allocating a dynamic buffer instead of the stack. An error in logic there 
could cause a crash or a memory leak in scenarios undetected during testing. I 
used valgrind when developing the fix to derisk the memory leak scenario.

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


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

[Touch-packages] [Bug 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs

[OEM Taipei Bot]

linux-oem-22.04d 6.5.0.1013.15 in jammy-updates contains the fix.
https://changelogs.ubuntu.com/changelogs/pool/main/l/linux-
oem-6.5/linux-oem-6.5_6.5.0-1013.14/changelog

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

Title:
  amdgpu: GPU Recovery fails, frequent hangs

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Confirmed
Status in mesa source package in Jammy:
  New
Status in linux source package in Lunar:
  Confirmed
Status in mesa source package in Lunar:
  New

Bug description:
  I've been using 23.04 for a few months, and experienced a total system
  hang occasionally when sharing my screen over Zoom or Google Meet
  (running on Google Chrome).

  At first it hangs and then it periodically flashes like it's trying
  (unsuccessfully) to recover; I've got 3 screens (including the
  laptop's internal one) and each attempt shows something different (at
  first it tries to recover the contents of all 3 screens, then it shows
  only one of them, and then it shows the same content on all 3, but it
  never gets responsive).

  I've recently upgraded to 23.10, hoping a new kernel would help the
  situation. It's only gotten considerably worse now; it hangs sometimes
  just when opening Zoom; it's somehow easier to reproduce with Google
  Chrome. Interestingly, it fails quickly and reliably now when enabling
  my webcam (with special effects). It started hanging badly when using
  Google Maps as well.

  For all these behaviors, I suspect amdgpu is to blame (I'm running on
  Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
  anything interesting.

  Any tips about debugging this further?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-generic 6.5.0.10.12
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Nov 16 02:27:45 2023
  InstallationDate: Installed on 2023-07-02 (137 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv 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:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET75W(1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD000GUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD000GUS
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

  X-HWE-Bug: Bug #2047389

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


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

[Touch-packages] [Bug 2052525] Re: dracut initramfs missing systemd-executor

[Nick Rosbrook]

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

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

Title:
  dracut initramfs missing systemd-executor

Status in dracut package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
  The dracut autopkgtest fails when run against systemd v255.2-3ubuntu2.
  This looks to be the problem:

  
  504s Failed to stat /etc/localtime, ignoring: No such file or 
directory

  504s /etc/localtime doesn't exist yet, watching /etc
  instead.

  504s Failed to open executor binary
  '/usr/lib/systemd/systemd-executor': No such file or directory

  504s Failed to allocate manager object: No such file or
  directory

  504s [!!] Failed to allocate manager object.

  504s Rebooting in 10s...

  514s Rebooting now...

  514s [   12.571123] ACPI: PM: Preparing to enter system sleep state S5
  514s [   12.573098] reboot: Restarting system
  514s [   12.574688] reboot: machine restart
  515s TEST: root filesystem on a ext3 filesystem   [FAILED] 
  515s see 
/tmp/autopkgtest.Vd8poK/autopkgtest_tmp/dracut-test.Fz28KvLkEv/TEST-01-BASIC/test.log
  515s make[1]: Leaving directory 
'/tmp/autopkgtest.Vd8poK/autopkgtest_tmp/dracut-test.Fz28KvLkEv/TEST-01-BASIC'
  515s make[1]: *** [../Makefile.testdir:4: all] Error 1
  515s make: *** [Makefile:4: TEST-01-BASIC] Error 2
  515s make: Leaving directory 
'/tmp/autopkgtest.Vd8poK/autopkgtest_tmp/dracut-test.Fz28KvLkEv'
  515s autopkgtest [03:42:52]: test upstream-dracut-core: 
---]

  I.e., the systemd-executor binary (which is new in systemd v255) is
  not copied into the initramfs. This has already been fixed in upstream
  dracut.

  [1] 
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/amd64/d/dracut/20240203_093708_6cc09@/log.gz
  [2] 
https://github.com/dracutdevs/dracut/commit/bee1c4824a8cd47ce6c01892a548bdc07b1fa678

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


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

[Touch-packages] [Bug 2051990] Re: python3-defaults 3.12 causes aubio to fail to build from source

[Graham Inggs]

This bug was fixed in the package aubio - 0.4.9-4.4
Sponsored for Vladimir Petko (vpa1977)

---
aubio (0.4.9-4.4) unstable; urgency=medium

  * Non-maintainer upload.

  [ Vladimir Petko ]
  * d/p/waflib-py312.patch: cherry-pick waf patch to resolve python 3.12
build failure due to imp module removal. Closes: #1061736.

 -- Matthias Klose   Wed, 07 Feb 2024 00:46:01 +0100

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

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

Title:
  python3-defaults 3.12 causes aubio to fail to build from source

Status in aubio package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  New
Status in aubio package in Debian:
  New

Bug description:
  python3 ./waf configure --verbose --destdir=debian/tmp --prefix=/usr 
--enable-fftw3f --libdir=/usr/lib/x86_64-linux-gnu
  /<>/waflib/Utils.py:443: SyntaxWarning: invalid escape sequence 
'\d'
return re.split('\d+$',s)[0]
  /<>/waflib/ConfigSet.py:7: SyntaxWarning: invalid escape 
sequence '\ '
re_imp=re.compile('^(#)*?([^#=]*?)\ =\ (.*?)$',re.M)
  /<>/waflib/ansiterm.py:178: SyntaxWarning: invalid escape 
sequence '\['
ansi_tokens=re.compile('(?:\x1b\[([0-9?;]*)([a-zA-Z])|([^\x1b]+))')
  Traceback (most recent call last):
File "/<>/./waf", line 164, in 
  from waflib import Scripting
File "/<>/waflib/Scripting.py", line 7, in 
  from waflib import 
Utils,Configure,Logs,Options,ConfigSet,Context,Errors,Build,Node
File "/<>/waflib/Configure.py", line 6, in 
  from waflib import ConfigSet,Utils,Options,Logs,Context,Build,Errors
File "/<>/waflib/Options.py", line 6, in 
  from waflib import Logs,Utils,Context,Errors
File "/<>/waflib/Context.py", line 5, in 
  import os,re,imp,sys
  ModuleNotFoundError: No module named 'imp'
  make[1]: *** [debian/rules:45: override_dh_auto_configure] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:22: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  

  Build finished at 2024-02-01T21:23:22Z

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


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

[Touch-packages] [Bug 2051997] Re: bdebstrap fails to build with python3-defaults 3.12

[Graham Inggs]

This bug was fixed in the package bdebstrap - 0.6.0-1.1
Sponsored for Vladimir Petko (vpa1977)

---
bdebstrap (0.6.0-1.1) unstable; urgency=medium

  * Non-maintainer upload.

  [ Vladimir Petko ]
  * 001-disable-distutils-pylint.patch: disable pylint errors related to
distutils removal in python 3.12 (LP: #2051997).
  * d/t/control: add dpkg-dev dependency to fix missing dpkg-
architecture error in './system-testing bdebstrap' autopktest.

 -- Matthias Klose   Wed, 07 Feb 2024 01:00:50 +0100

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

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

Title:
  bdebstrap fails to build with python3-defaults 3.12

Status in bdebstrap package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  New
Status in bdebstrap package in Debian:
  New

Bug description:
  When building bdebstrap with python3-default 3.12 the following error occurs
  --
  usr/bin/python3.12 -m pylint --rcfile=/<>/tests/pylint.conf -- 
/<>/bdebstrap tests /<>/setup.py
  FAIL
  test_flake8 (tests.test_shellcheck.ShellcheckTestCase.test_flake8)
  Test: Run shellcheck on Shell source code. ... Running following command:
  shellcheck /<>/hooks/disable-units 
/<>/hooks/enable-units
  ok

  ==
  FAIL: test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
  Test: Run pylint on Python source code.
  --
  Traceback (most recent call last):
File "/<>/tests/test_pylint.py", line 74, in test_pylint
  self.fail("\n".join(msgs))
  AssertionError: pylint found issues:
  * Module setup
  /<>/setup.py:26:0: E0401: Unable to import 'distutils.log' 
(import-error)
  /<>/setup.py:27:0: E0401: Unable to import 
'distutils.command.build' (import-error)
  /<>/setup.py:28:0: E0401: Unable to import 
'distutils.command.clean' (import-error)
  /<>/setup.py:57:4: C0116: Missing function or method docstring 
(missing-function-docstring)
  /<>/setup.py:54:0: R0903: Too few public methods (1/2) 
(too-few-public-methods)
  /<>/setup.py:65:4: C0116: Missing function or method docstring 
(missing-function-docstring)
  /<>/setup.py:62:0: R0903: Too few public methods (1/2) 
(too-few-public-methods)

  --

  due to removal of distutils in python 3.12

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


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

[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Scarlett Gately Moore]

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

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

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

** Changed in: marble (Ubuntu)
Milestone: None => ubuntu-24.04-feature-freeze

** Changed in: marble (Ubuntu)
 Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore)

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akregator package in Ubuntu:
  In Progress
Status in angelfish package in Ubuntu:
  In Progress
Status in apparmor package in Ubuntu:
  Confirmed
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  In Progress
Status in devhelp package in Ubuntu:
  Confirmed
Status in digikam package in Ubuntu:
  In Progress
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in falkon package in Ubuntu:
  In Progress
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  In Progress
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  In Progress
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kiwix package in Ubuntu:
  Confirmed
Status in kmail package in Ubuntu:
  In Progress
Status in konqueror package in Ubuntu:
  In Progress
Status in kontact package in Ubuntu:
  In Progress
Status in marble package in Ubuntu:
  In Progress
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Confirmed
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  In Progress

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

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


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

[Touch-packages] [Bug 2052618] [NEW] Missing sftp-server argument -m force_file_perms

[Karmazyn]

Public bug reported:

In Centos, RHEL, ... openssh-server package with sftp-server has an option
-m force_file_perms
Sets explicit file permissions to be applied to newly-created files instead of 
the default or client requested mode. Numeric values include: 777, 755, 750, 
666, 644, 640, etc. Using both -m and -u switches makes the umask (-u) 
effective only for newly created directories and explicit mode (-m) for newly 
created files.

This option is missing in Ubuntu 22.04.3 LTS 
Code patch from Fedora:
https://src.fedoraproject.org/rpms/openssh/raw/f34/f/openssh-6.7p1-sftp-force-permission.patch

SFTP put command is sending source filemask to the remote server as is.
For shared folders there is a risk sender will generate a file, which another 
user can not read.
That's why there is force_file_perms to force filemask on shared sftp accounts 
no matters what filemask had source file on client side.

This feature is welcome to migrate from RHEL to Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: openssh-server 1:8.9p1-3ubuntu0.6
Uname: Linux 5.15.0-200.131.27.1.el9uek.x86_64 x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Feb  7 10:22:50 2024
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
SourcePackage: openssh
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Missing sftp-server argument -m force_file_perms

Status in openssh package in Ubuntu:
  New

Bug description:
  In Centos, RHEL, ... openssh-server package with sftp-server has an option
  -m force_file_perms
  Sets explicit file permissions to be applied to newly-created files instead 
of the default or client requested mode. Numeric values include: 777, 755, 750, 
666, 644, 640, etc. Using both -m and -u switches makes the umask (-u) 
effective only for newly created directories and explicit mode (-m) for newly 
created files.

  This option is missing in Ubuntu 22.04.3 LTS 
  Code patch from Fedora:
  
https://src.fedoraproject.org/rpms/openssh/raw/f34/f/openssh-6.7p1-sftp-force-permission.patch

  SFTP put command is sending source filemask to the remote server as is.
  For shared folders there is a risk sender will generate a file, which another 
user can not read.
  That's why there is force_file_perms to force filemask on shared sftp 
accounts no matters what filemask had source file on client side.

  This feature is welcome to migrate from RHEL to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssh-server 1:8.9p1-3ubuntu0.6
  Uname: Linux 5.15.0-200.131.27.1.el9uek.x86_64 x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  7 10:22:50 2024
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound

[aminesaka]

** Attachment added: "IMG_20240207_111005_968.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051570/+attachment/5745035/+files/IMG_20240207_111005_968.jpg

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

Title:
  [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal]
  Underruns, dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Since the last three weeks' updates, I have encountered several
  challenges with the audio functionality on my system. Primarily, upon
  starting my laptop, the audio often fails to work, displaying "Dummy
  Output." To resolve this, I find myself needing to restart the laptop
  two or three times before the audio becomes functional.

  Even when the audio is working, I've noticed a recurring issue where,
  after playing video or audio for approximately 2-3 minutes, the sound
  starts crackling and buzzing. The intensity of these distortions
  gradually increases, resembling the static interference on a radio
  station with a weak signal. This issue persists even when using 3.5mm
  headphones, requiring the use of a USB headset or Bluetooth headphones
  to enjoy distortion-free audio.

  Furthermore, I have observed that, regardless of the Ubuntu version
  (ranging from 22.04 to 22.04.3), I face difficulties changing the
  microphone output settings when an external audio peripheral, such as
  a USB headset, 3.5mm headphones, or Bluetooth headphones, is
  connected. The OS appears to exclusively utilize the microphone from
  the connected peripheral, making it impossible to switch to the
  laptop's built-in microphone.

  For your reference, here are the specifications of my laptop and the
  Ubuntu version I am currently using:

  Laptop: Dell Vostro 3400
  CPU: 11th Gen Intel i5-1135G7
  GPU: Intel TigerLake-LP GT2 Iris Xe
  Memory: 2490MiB / 19720MiB
  Resolution: 1920x1080
  OS: Ubuntu 22.04.3 LTS x86_64
  Kernel: 6.5.0-14-generic
  DE: GNOME 42.9
  Shell: bash 5.1.16
  Sound Card: Card: HDA Intel PCH, Chip: Cirrus Logic CS8409/CS42L42

  UPDATE 29-01-2024 After the latest Linux kernel update to
  "6.5.0-15-generic."

  Following the update, I observed a significant reduction in crackling
  sound (approximately 80%) after disabling C-states from the BIOS.
  However, this improvement came at the cost of higher CPU temperatures,
  with the fan constantly running.

  Conversely, with C-states enabled, the crackling sound occurs only
  when the fan starts working. Additionally, I am still encountering the
  "Dummy Output" audio issue consistently on a fresh start,
  necessitating a reboot to resolve.

  I want to emphasize that I receive updates from the Tunisia Ubuntu
  server.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  galxy-a10   1437 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 17:50:44 2024
  InstallationDate: Installed on 2024-01-16 (13 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: جانفي 29 17:49:49 galxya10-VR 
whoopsie-upload-all[712]: INFO:root:/var/crash/_usr_bin_pulseaudio.1000.crash 
already marked for upload, skipping
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] 
Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2023
  dmi.bios.release: 1.27
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.27.1
  dmi.board.name: 0GGCMJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.27.1:bd10/03/2023:br1.27:svnDellInc.:pnVostro3400:pvr:rvnDellInc.:rn0GGCMJ:rvrA02:cvnDellInc.:ct10:cvr:sku0A23:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3400
  dmi.product.sku: 0A23
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-01-28T08:52:28.427855

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


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

[Touch-packages] [Bug 2051576] Re: Please merge 1.9.15p5-3 into noble

[Launchpad Bug Tracker]

This bug was fixed in the package sudo - 1.9.15p5-3ubuntu1

---
sudo (1.9.15p5-3ubuntu1) noble; urgency=medium

  * Merge with Debian unstable (LP: #2051576). Remaining changes:
- debian/sudo[-ldap].manpages: install man/man8/sudo_root.8
- debian/sudo[-ldap].init: delete init scripts, as they are no longer
  necessary.
- debian/etc/pam.d/sudo[-i]:
  + Use pam_env to read /etc/environment and /etc/default/locale
environment files. Reading ~/.pam_environment is not permitted due
to security reasons.
- debian/etc/sudoers:
  + also grant admin group sudo access
  + include /snap/bin in the secure_path
- debian/tests/control: 03-getroot-ldap
  + allow removal of 'sudo' in autopkgtest (SUDO_FORCE_REMOVE=yes)
- debian/tests/04-getroot-sssd:
  + Check if the slapd daemon is ready before proceeding.
In some situations, the next command (ldapmodify) runs before
the service is ready. See LP#2026888

sudo (1.9.15p5-3) unstable; urgency=medium

  * add --with-devel configure option.
Thanks to Bastien Roucariès (Closes: #1061272)

sudo (1.9.15p5-2) unstable; urgency=medium

  * switch Build-Depends from systemd to systemd-dev
Thanks to Michael Biebl (Closes: #1060511)
  * set Multi-Arch: foreign on sudo and sudo-ldap.
Thanks to Andreas Rottmann (Closes: #1060445)
  * add debian/copyright clause for source_sudo.py.
Oops.

sudo (1.9.15p5-1) unstable; urgency=medium

  * new upstream version 1.9.15p5
* This is supposed to properly malloc on hurd.
  Thanks to Martin-Éric Racine (Closes: #1057833)
  * add durch debconf translation.
Thanks to Frans Spiesschaert (Closes: #1059567)

sudo (1.9.15p4-2) unstable; urgency=medium

  * upload to unstable
  * use pkg-config to place systemd units.
Thanks to Chris Hofstaedtler (Closes: #1059063)
  * Add french debconf translation.
Thanks to bubu (Closes: #1058939)
  * fix typo in NEWS.Debian.
Thanks to Vincent Danjean (Closes: #1058925)
  * add persian debconf translation.
Thanks to Danial Behzadi
  * add spanish debconf translation.
Thanks to Camaleón (Closes: #1059460)

sudo (1.9.15p4-1) experimental; urgency=medium

  * new upstream version 1.9.15p4
  * add de.po template translation.
Thanks to Christoph Brinkhaus (Closes: #1058762)
  * Enable AppArmor (MR 15, manually apṕlied)
Thanks to Will Shand
  * remove legacy debian/rules.predh7

sudo (1.9.15p3-1) unstable; urgency=medium

  * new upstream version 1.9.15p3

sudo (1.9.15p2-2) unstable; urgency=medium

  * upload to unstable

sudo (1.9.15p2-1) experimental; urgency=medium

  * the #DENOG15 release
  * New upstream version 1.9.15p2
  * mark sudo-ldap as deprecated.

 -- Danilo Egea Gondolfo   Mon, 29
Jan 2024 17:09:56 +

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

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

Title:
  Please merge 1.9.15p5-3 into noble

Status in sudo package in Ubuntu:
  Fix Released

Bug description:
  tracking bug

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


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

[Touch-packages] [Bug 2052505] Re: Can't install openssl/libssl3 debug package

[Alexander Köpke]

Retested today, now it is working again

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

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

Title:
  Can't install openssl/libssl3 debug package

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  I'm building an application in docker, using
  `mcr.microsoft.com/dotnet/runtime:7.0-jammy`
  (https://github.com/dotnet/dotnet-
  docker/blob/main/src/runtime/7.0/jammy/amd64/Dockerfile) image, that
  is using `amd64/buildpack-deps:jammy-curl`(https://github.com/docker-
  library/buildpack-
  
deps/blob/93d6db0797f91ab674535553b7e0e762941a02d0/ubuntu/jammy/curl/Dockerfile)
  as base image.

  In my docker file I added ubuntu debug repositories and install debug
  packages:

  ```bash
  apt-get install -y software-properties-common
  echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse
  deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted 
universe multiverse | \
  deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted 
universe multiverse" | \
  tee -a /etc/apt/sources.list.d/ddebs.list
  apt install ubuntu-dbgsym-keyring
  apt-get update -y
  apt-get install -y --no-install-recommends libc6-dbg libssl3-dbgsym 
openssl-dbgsym libicu70-dbgsym libstdc++6-dbgsym 
  ```
  Yesterday I tried and the build isn'T running anymore with the error message:

  ```output
  1.884 Some packages could not be installed. This may mean that you have
  1.884 requested an impossible situation or if you are using the unstable
  1.884 distribution that some required packages have not yet been created
  1.884 or been moved out of Incoming.
  1.884 The following information may help to resolve the situation:
  1.884 
  1.887 The following packages have unmet dependencies:
  2.072  libssl3-dbgsym : Depends: libssl3 (= 3.0.2-0ubuntu1.13) but 
3.0.2-0ubuntu1.14 is to be installed
  2.075  openssl-dbgsym : Depends: openssl (= 3.0.2-0ubuntu1.13) but 
3.0.2-0ubuntu1.14 is to be installed
  2.080 E: Unable to correct problems, you have held broken packages.
  ```

  It looks like the debug symbol oackage for libssl3 and openssl should
  be updated. I waited 24h for mirror sync, but error still persist.

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


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

[Touch-packages] [Bug 2047450] Re: tail emits no output for sysfs files when using large page kernels

[Robie Basak]

I'm retrying these failing autopkgtests with migration-reference/0 since
if they fail anyway they shouldn't hold things up.

In the meantime, could you please also verify that behaviour on 4K page
size hasn't regressed? It looks like this was implied in the Test Plan
but hasn't been verified. Thanks!

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

Title:
  tail emits no output for sysfs files when using large page kernels

Status in coreutils package in Ubuntu:
  Fix Released
Status in coreutils source package in Jammy:
  Fix Committed
Status in coreutils source package in Lunar:
  Won't Fix
Status in coreutils source package in Mantic:
  Fix Committed
Status in coreutils source package in Noble:
  Fix Released

Bug description:
  [Impact]
  Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 
(optional -64k flavors). When booted on 64K kernels, tail emits no output when 
tailing a sysfs file. The difference in behavior can be a source for bugs in 
scripts that use tail, and general user confusion.

  [Test Plan]
  The upstream fix includes a test case that tails the /sys/kernel/profiling 
file, if it exists. That case would fail with an unfixed coreutils package as 
shown below:

  = When booted on a 4K kernel =
  ubuntu@gunyolk:~$ tail /sys/kernel/profiling 
  0

  = When booted on a 64K kernel =
  ubuntu@gunyolk:~$ tail /sys/kernel/profiling 
  ubuntu@gunyolk:~$ 

  Since the upstream test cases are executed at build time, the existing
  tests and this new test will be used  to regression test behavior.
  This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We
  should also do a manual verification on arm64 w/ the 64K kernel since
  that case is not covered by our builders.

  [Where Problems Could Occur]
  The biggest risk for a regression I see is due to the side-effect of the fix 
now allocating a dynamic buffer instead of the stack. An error in logic there 
could cause a crash or a memory leak in scenarios undetected during testing. I 
used valgrind when developing the fix to derisk the memory leak scenario.

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


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

[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Scarlett Gately Moore]

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

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

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

** Changed in: kmail (Ubuntu)
Milestone: None => ubuntu-24.04-feature-freeze

** Changed in: kmail (Ubuntu)
 Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore)

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akregator package in Ubuntu:
  In Progress
Status in angelfish package in Ubuntu:
  In Progress
Status in apparmor package in Ubuntu:
  Confirmed
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  In Progress
Status in devhelp package in Ubuntu:
  Confirmed
Status in digikam package in Ubuntu:
  In Progress
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in falkon package in Ubuntu:
  In Progress
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  In Progress
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  In Progress
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kiwix package in Ubuntu:
  Confirmed
Status in kmail package in Ubuntu:
  In Progress
Status in konqueror package in Ubuntu:
  In Progress
Status in kontact package in Ubuntu:
  In Progress
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Confirmed
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  In Progress

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

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


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

[Touch-packages] [Bug 2052535] Re: Blocked by pycountry autopkgtest

[Skia]

This bug isn't necessary, if an admin sees it, please delete :-)

** Changed in: iso-codes (Ubuntu)
   Status: New => Invalid

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

Title:
  Blocked by pycountry autopkgtest

Status in iso-codes package in Ubuntu:
  Invalid

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/pycountry/+bug/2052318
  currently prevents iso-codes to migrate from 4.15.0-1 to 4.16.0-1

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


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