from:"MichaeL."

Ah no it's a bit simpler than that https://github.com/util-linux/util-
linux/issues/2528.

--disable-libmount-mountfd-support looking better tbh.

** Bug watch added: github.com/util-linux/util-linux/issues #2528
   https://github.com/util-linux/util-linux/issues/2528

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

Title:
  mantic images after 20230917 are failing to deploy with failure to
  mount root and kernel filesystems

Status in maas-images:
  New
Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  New
Status in linux source package in Mantic:
  Incomplete
Status in systemd source package in Mantic:
  Confirmed
Status in util-linux source package in Mantic:
  New

Bug description:
  Mantic arm64 deploys started failing on Sept 18th with:

  [   41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root 
and Kernel File Systems...
   Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File 
Systems...
  [   41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug 
All udev Devices...
   Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev 
Devices...
  [   41.964758] systemd[1]: Started systemd-journald.service - Journal Service.
  [[0;32m  OK  [0m] Started [0;1;39msystemd-journald.service[0m - Journal 
Service.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message 
Queue File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace 
File System.
  [[0;32m  OK  [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console 
keyboard layout.
  [[0;32m  OK  [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static 
Device Nodes.
  [[0;32m  OK  [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or 
progress polling.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel 
Module configfs.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel 
Module dm_mod.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel 
Module drm.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel 
Module efi_pstore.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel 
Module fuse.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel 
Module loop.
  [[0;32m  OK  [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load 
Kernel Modules.
  [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and 
Kernel File Systems.
  See 'systemctl status systemd-remount-fs.service' for details.

  After this many other services and cloud-init fails. See the full
  kopter-0918.log. For comparison, a log from the prior day's test is
  also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/2037417/+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 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems

So the cause of this, I am fairly sure, is the new "libmount-mountfd"
support in util-linux which seems to have the consequence that "mount -o
remount $mountpoint" fails for an overlay that references paths no
longer available in the current mount namespace.

You can see the discussion of a similar-but-not-the-same issue here
https://github.com/util-linux/util-linux/issues/1992

I'm trying to come up with a reproducer but I have to head afk now. I'll
file a bug upstream when I get that done.

Maybe we should build util-linux with --disable-libmount-mountfd-support
for now (bit late in the release cycle to be uploading util-linux
though...)


** Bug watch added: github.com/util-linux/util-linux/issues #1992
   https://github.com/util-linux/util-linux/issues/1992

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

Title:
  mantic images after 20230917 are failing to deploy with failure to
  mount root and kernel filesystems

Status in maas-images:
  New
Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  New
Status in linux source package in Mantic:
  Incomplete
Status in systemd source package in Mantic:
  Confirmed
Status in util-linux source package in Mantic:
  New

Bug description:
  Mantic arm64 deploys started failing on Sept 18th with:

  [   41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root 
and Kernel File Systems...
   Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File 
Systems...
  [   41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug 
All udev Devices...
   Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev 
Devices...
  [   41.964758] systemd[1]: Started systemd-journald.service - Journal Service.
  [[0;32m  OK  [0m] Started [0;1;39msystemd-journald.service[0m - Journal 
Service.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message 
Queue File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace 
File System.
  [[0;32m  OK  [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console 
keyboard layout.
  [[0;32m  OK  [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static 
Device Nodes.
  [[0;32m  OK  [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or 
progress polling.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel 
Module configfs.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel 
Module dm_mod.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel 
Module drm.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel 
Module efi_pstore.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel 
Module fuse.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel 
Module loop.
  [[0;32m  OK  [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load 
Kernel Modules.
  [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and 
Kernel File Systems.
  See 'systemctl status systemd-remount-fs.service' for details.

  After this many other services and cloud-init fails. See the full
  kopter-0918.log. For comparison, a log from the prior day's test is
  also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/2037417/+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 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems

** Also affects: util-linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  mantic images after 20230917 are failing to deploy with failure to
  mount root and kernel filesystems

Status in maas-images:
  New
Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  New
Status in linux source package in Mantic:
  Incomplete
Status in systemd source package in Mantic:
  Confirmed
Status in util-linux source package in Mantic:
  New

Bug description:
  Mantic arm64 deploys started failing on Sept 18th with:

  [   41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root 
and Kernel File Systems...
   Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File 
Systems...
  [   41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug 
All udev Devices...
   Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev 
Devices...
  [   41.964758] systemd[1]: Started systemd-journald.service - Journal Service.
  [[0;32m  OK  [0m] Started [0;1;39msystemd-journald.service[0m - Journal 
Service.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message 
Queue File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace 
File System.
  [[0;32m  OK  [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console 
keyboard layout.
  [[0;32m  OK  [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static 
Device Nodes.
  [[0;32m  OK  [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or 
progress polling.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel 
Module configfs.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel 
Module dm_mod.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel 
Module drm.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel 
Module efi_pstore.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel 
Module fuse.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel 
Module loop.
  [[0;32m  OK  [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load 
Kernel Modules.
  [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and 
Kernel File Systems.
  See 'systemctl status systemd-remount-fs.service' for details.

  After this many other services and cloud-init fails. See the full
  kopter-0918.log. For comparison, a log from the prior day's test is
  also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/2037417/+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 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems

** Tags added: foundaitions-todo

** Tags removed: foundaitions-todo
** Tags added: foundations-todo

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

Title:
  mantic images after 20230917 are failing to deploy with failure to
  mount root and kernel filesystems

Status in maas-images:
  New
Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Mantic:
  Incomplete
Status in systemd source package in Mantic:
  Confirmed

Bug description:
  Mantic arm64 deploys started failing on Sept 18th with:

  [   41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root 
and Kernel File Systems...
   Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File 
Systems...
  [   41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug 
All udev Devices...
   Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev 
Devices...
  [   41.964758] systemd[1]: Started systemd-journald.service - Journal Service.
  [[0;32m  OK  [0m] Started [0;1;39msystemd-journald.service[0m - Journal 
Service.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message 
Queue File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace 
File System.
  [[0;32m  OK  [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console 
keyboard layout.
  [[0;32m  OK  [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static 
Device Nodes.
  [[0;32m  OK  [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or 
progress polling.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel 
Module configfs.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel 
Module dm_mod.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel 
Module drm.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel 
Module efi_pstore.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel 
Module fuse.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel 
Module loop.
  [[0;32m  OK  [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load 
Kernel Modules.
  [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and 
Kernel File Systems.
  See 'systemctl status systemd-remount-fs.service' for details.

  After this many other services and cloud-init fails. See the full
  kopter-0918.log. For comparison, a log from the prior day's test is
  also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/2037417/+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 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up

2023-10-02 Thread Michael Hudson-Doyle

https://code.launchpad.net/~mwhudson/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+merge/452586 might be a fix? Not tested at
all.

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

Title:
  Mantic/23.10: PXE boot tries to initialize DHCP before network link is
  up

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I'm not sure whether this is the correct package for this bug, please
  reassign if not.

  I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in
  order to perform an unattended installation. The kernel command line
  looks like that:

  iso/casper/vmlinuz --- ip=dhcp netboot=nfs
  nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s=

  This has worked perfectly before. However, in 23.10, the kernel tries
  to intialize DHCP before a network link is up.

  I can see a few instances of messages like the following:
  dhcpcd-10.0.2 starting
  dev: loaded udev
  no interfaces have a carrier
  exiting due to oneshot
  dhcpcd exited

  Then, the kernel tries to mount NFS, even though neither an IP address nor 
even a link is available:
  connect: Network is unreachable
  NFS over TCP not available from 192.168.1.1

  This is repeated for a while. In between, a message tells that now the link 
is up:
  [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: Rx/Tx

  The NFS messages repeat for a while, until the system gives up and I'm
  dropped into a busybox prompt.

  Executing dhcpcd now correctly gets IP addresses, but I don't know how
  to continue the boot from there.

  The problem occurs on most physical machines that I tried, but not in
  VMs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+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 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up

2023-10-02 Thread Michael Hudson-Doyle

Is the point here that dhcpcd -1 exits immediately if it finds no
devices, even if it has a -t argument?

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

Title:
  Mantic/23.10: PXE boot tries to initialize DHCP before network link is
  up

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I'm not sure whether this is the correct package for this bug, please
  reassign if not.

  I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in
  order to perform an unattended installation. The kernel command line
  looks like that:

  iso/casper/vmlinuz --- ip=dhcp netboot=nfs
  nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s=

  This has worked perfectly before. However, in 23.10, the kernel tries
  to intialize DHCP before a network link is up.

  I can see a few instances of messages like the following:
  dhcpcd-10.0.2 starting
  dev: loaded udev
  no interfaces have a carrier
  exiting due to oneshot
  dhcpcd exited

  Then, the kernel tries to mount NFS, even though neither an IP address nor 
even a link is available:
  connect: Network is unreachable
  NFS over TCP not available from 192.168.1.1

  This is repeated for a while. In between, a message tells that now the link 
is up:
  [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: Rx/Tx

  The NFS messages repeat for a while, until the system gives up and I'm
  dropped into a busybox prompt.

  Executing dhcpcd now correctly gets IP addresses, but I don't know how
  to continue the boot from there.

  The problem occurs on most physical machines that I tried, but not in
  VMs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+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 2037281] Re: Shutdown when triggering daemon-reload eary in boot

2023-09-25 Thread Michael Vogt

** Description changed:

  In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue
  where if a service, started earlier than devices are processed by udev,
  does `systemctl daemon-reload`, the system shuts down. This is due to
  devices for mounted filesystem temporarily taken dead, which pulls most
  units down.
  
  This was fixed by upstream in
  https://github.com/systemd/systemd/pull/23218.
  
  But this was not backported to the versions used by Ubuntu packages for
  focal and jammy. The needed commit from that PR is the one with message
  `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`.
  
  This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed.
  And I suppose it does also for jammy.
  
  I have manually tested the fix with Ubuntu Core 20, and this fixes our
  issue.
  
  We would like this patch to be backported to focal-updates and jammy-
  updates.
  
  Thank you in advance.
+ 
+ 
+ [ Impact ] 
+  * An explanation of the effects of the bug on users and
+  * justification for backporting the fix to the stable release.
+  * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+ 
+ [ Test Plan ]
+  * detailed instructions how to reproduce the bug
+  * these should allow someone who is not familiar with the affected
+package to reproduce the bug and verify that the updated package fixes
+the problem.
+  * if other testing is appropriate to perform before landing this update,
+this should also be described here.
+ 
+ [ Where problems could occur ]
+  * Think about what the upload changes in the software. Imagine the change is
+wrong or breaks something else: how would this show up?
+  * It is assumed that any SRU candidate patch is well-tested before
+upload and has a low overall risk of regression, but it's important
+to make the effort to think about what ''could'' happen in the
+event of a regression.
+  * This must '''never''' be "None" or "Low", or entirely an argument as to why
+your upload is low risk.
+  * This both shows the SRU team that the risks have been considered,
+and provides guidance to testers in regression-testing the SRU.
+ 
+ [ Other Info ]
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance

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

Title:
  Shutdown when triggering daemon-reload eary in boot

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

Bug description:
  In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue
  where if a service, started earlier than devices are processed by
  udev, does `systemctl daemon-reload`, the system shuts down. This is
  due to devices for mounted filesystem temporarily taken dead, which
  pulls most units down.

  This was fixed by upstream in
  https://github.com/systemd/systemd/pull/23218.

  But this was not backported to the versions used by Ubuntu packages
  for focal and jammy. The needed commit from that PR is the one with
  message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`.

  This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing
  needed. And I suppose it does also for jammy.

  I have manually tested the fix with Ubuntu Core 20, and this fixes our
  issue.

  We would like this patch to be backported to focal-updates and jammy-
  updates.

  Thank you in advance.

  
  [ Impact ] 
   * An explanation of the effects of the bug on users and
   * justification for backporting the fix to the stable release.
   * In addition, it is helpful, but not required, to include an
 explanation of how the upload fixes this bug.

  [ Test Plan ]
   * detailed instructions how to reproduce the bug
   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.
   * if other testing is appropriate to perform before landing this update,
 this should also be described here.

  [ Where problems could occur ]
   * Think about what the upload changes in the software. Imagine the change is
 wrong or breaks something else: how would this show up?
   * It is assumed that any SRU candidate patch is well-tested before
 upload and has a low overall risk of regression, but it's important
 to make the effort to think about what ''could'' happen in the
 event of a regression.
   * This must '''never''' be "None" or "Low", or entirely an argument as to why
 your upload is low risk.
   * This both shows the SRU team that the risks have been considered,
 and provides guidance to

[Touch-packages] [Bug 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04

2023-09-24 Thread Michael Hudson-Doyle

This is fixed in the 23.10 dailies. I'm not sure it's really practical
to fix this for the next 22.04 point release, unfortunately.

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

** Changed in: subiquity
   Status: Triaged => Fix Released

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

Title:
  autoinstall ssh:install-server:false is misleading in 22.04

Status in subiquity:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Jammy:
  Confirmed

Bug description:
  With 22.04, openssh-server is baked into the image curtin copies to
  the target.  The ssh:install-server key no longer controls whether
  openssh-server gets installed.  It should be easy enough to have the
  bit of code that installs openssh-server when the key is true also
  remove it when the key is false.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1974483/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

2023-09-20 Thread Michael Biech

Thank you everyone for your speedy work! I have verified
"249.11-0ubuntu3.11" fixes the issue on Jammy for me! Very much
appreciated.

Steps taken:



# 1)
cat

[Touch-packages] [Bug 1593407] Re: Guest session cannot run snaps

** Project changed: snappy => snapd

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

Title:
  Guest session cannot run snaps

Status in Light Display Manager:
  Confirmed
Status in snapd:
  Confirmed
Status in Ubuntu MATE:
  Confirmed
Status in Desktop:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in firefox source package in Xenial:
  Confirmed
Status in lightdm source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed

Bug description:
  I'm using Ubuntu 16.04.

  The guest session cannot execute snaps, because of a permission error.
  The LightDM's guest session AppArmor profile is not allowing access to /snap 
and other needed files and folders.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1593407/+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 1659719] Re: ssh can't call a binary from a snap without the full path

** Project changed: snappy => snapd

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

Title:
  ssh can't call a binary from a snap without the full path

Status in snapd:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  New
Status in openssh source package in Xenial:
  Won't Fix
Status in pam source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  New
Status in openssh source package in Bionic:
  Won't Fix
Status in pam source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Focal:
  New
Status in openssh source package in Focal:
  Won't Fix
Status in pam source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Fix Released
Status in openssh source package in Groovy:
  Won't Fix
Status in pam source package in Groovy:
  Fix Released
Status in openssh package in Debian:
  New

Bug description:
  [impact]
  ssh can't call a binary from a snap, it will only work using the full path.

  [test case]
  Create a container. Install the go snap (and make sure golang-go is not 
installed). Run "ssh  go version" and check the binary is found.

  [regression potential]
  It's a pam change an they are always a bit scary but the code follows the 
existing pattern for updating PATH in /etc/environment and has been tested in 
groovy.

  [original description]

  Let's say I have the hello snap installed in 192.168.122.24. Then:

  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
  elopio@192.168.122.24's password:
  bash: hello: command not found
  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
  elopio@192.168.122.24's password:
  Hello, world!

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1659719/+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 1965328] Re: transient scope could not be started error in bionic lxd container

** Project changed: snappy => snapd

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

Title:
  transient scope could not be started error in bionic lxd container

Status in snapd:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  On my impish development host machine I tend to use lxd containers to
  support snap building and other tasks targeting different releases.
  Today I came to use a bionic container as per usual and found that I
  could not invoke any snap applications. I installed hello-world as the
  most simple test of running a snap app:

  ```
  ubuntu@b:~$ hello-world
  internal error, please report: running "hello-world" failed: transient scope 
could not be started, job /org/freedesktop/systemd1/job/44 finished with result 
failed
  ```

  I made sure the container had up to date packages in it (apt & snaps)
  and rebooted it. But the problem persisted. I then created a second
  container and installed hello-world in it and again the problem was
  reproducible. At the time of producing the following attachments I had
  not attempted to reboot the host.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1965328/+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 1503680] Re: dhclient for eth0 does never exit and retries dhcp foerever

** Project changed: snappy => snapd

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

Title:
  dhclient for eth0 does never exit and retries dhcp foerever

Status in snapd:
  Incomplete
Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  When booting snappy without eth0 connected, dhclient runs forever
  trying to retrieve DHCP every 5 minutes.

  dhclient is run with the -1 parameter which is supposed to try only
  once and exit after trying.

 -1 Try  to  get  a  lease  once.   On failure exit with code 2.  In
DHCPv6 this sets the maximum duration of the initial exchange to
timeout (from dhclient.conf(5) with a default of sixty seconds).

  Though dhclient keeps running / does not exit.

  If dhclient is changed to exit after failure, it must be insured that
  it will be restarted when the network interface gets a physical link.

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


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

[Touch-packages] [Bug 1650688] Re: timedatectl set-timezone fails on UC16

** Project changed: snappy => snapd

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

Title:
  timedatectl set-timezone fails on UC16

Status in snapd:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  SRU
  ===

  [Impact]

   * The bug prevents timedated from recognizing and correctly set the
  system's timezone when running Ubuntu Core 16, 18 and 20.

   * This causes by timedated fails to take Ubuntu Core's /etc/writable
  redirection into account.

   * The recognizing part is fixed by making the code take writable
  redirection into account.

   * The set part is fixed by making the code link to the absolute path
  instead of a relative one.

   * Currently core snaps worked around the set part by providing a
  wrapper script which re-create /etc/writable/localtime afterward.
  However this does not cover DBus users.

  [Test Plan]

   * On classics systems: ensure the proposed systemd package is installed.
     On Ubuntu Core systems: build a new core snap including proposed package, 
and install it. Replaces timedatectl with timedatectl.real to test skipping the 
wrapper.

  (Note that one can simulate core snap's /etc/writable redirection by
  running this image creation hook [1] on the system.)

  [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
  core/hooks/08-etc-writable.chroot?h=ubuntu/focal

   * On freshly boot system: query the timezone using `timedatectl`. The
  timezone should corresponds to `readlink -f /etc/localtime` and does
  not show `n/a`.

   * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`.
  `readlink -f /etc/localtime` should points to an existing file.

   * Run `sudo systemctl restart systemd-timedated.service`. Then, query
  the timezone again: `timedatectl`. It should show the previously set
  timezone and not `n/a`.

   * Run `sudo systemctl status systemd-timedated.service`. This should
  show no sign of timedated crashing.

  [Where problems could occur]

   * It's possible that the redirection handling code will be sub-par
  and causes crash. However, it's not likely because the similar pieces
  of code is in the previous patch since Ubuntu 16.04.

   * If it does: the patched `get_timezone()` function is used in 2
  places: the networkd's DHCP server [3] and the timedated itself.

     - Networkd is used primarily on servers where NetworkManage is
  absent. It's possible that this patch causes the user to loss access
  to the server due to networkd crash when setting up network
  interfaces, and requires physical access to fix. However, the code
  path is executed when DHCP is enabled only. I think it's not common
  for users to have networkd's DHCP server enabled: the feature seems to
  gear towards desktop users wanting to share internet connection, and
  in those cases they're more likely to use NetworkManager.

     - The timedated itself is likely used by the programs that involves
  in time-related functions. If a crash occur, in the worst case users
  won't be able to set time or timezone via timedated. However, users
  should still be able to e.g. set time using `date` or set timezone
  using /etc/localtime (assuming online guides still consider systems
  without systemd). Timedated is DBus-activated, and thus a crash should
  be self-healing.

   * The set part would also affects the clasic systems. However, I
  believe nothing else actually rely on /etc/localtime being a relative
  path, otherwise the /etc/writable redirection would causes even more
  problem, and would have been reported.

  [3] Yes, I'm surprised that there's a DHCP server inside systemd
  codebase.

  [Other Info]

   * This is also useful for UBports's Ubuntu Touch. We continue using
  system-image system where the rootfs is read-only, and thus is
  affected by this bug similarly to Ubuntu Core. I've tested the Focal
  version of the package on our (currently in development) Focal Ubuntu
  Touch image, and the fix works.

  

  [Original bug description]

  On a system running UC16, the file /etc/localtime is a link that
  points to /etc/writable/localtime.

  On a freshly installed system, /etc/writable/localtime is a fully-
  qualified link that points at /usr/share/zoneinfo/UTC.

  If timedatectl is used to set the timezone to something else,
  timedated updates the localtime symbolic link with a relative path to
  the zoneinfo directory, which results in an invalid link.

  $ sudo timedatectl set-timezone America/Detroit

  $ sudo timedatectl
    Local time: Fri 2016-12-16 18:18:49 EST

[Touch-packages] [Bug 1712312] Re: Cannot add secondary group to user

** Project changed: snappy => snapd

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

Title:
  Cannot add secondary group to user

Status in snapd:
  Triaged
Status in shadow package in Ubuntu:
  New

Bug description:
  When I try and add 'docker' group as a secondary group to my user:

  sudo usermod -aG docker $USER
  usermod: /etc/group.2059: Read-only file system
  usermod: cannot lock /etc/group; try again later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1712312/+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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

** Project changed: snappy => snapd

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

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in snapd:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
  fix were SRU'd, will all of these things in the wild cope with this
  sysctl change?

  [Other Info]

   * Original bug report

  Hi there,
  we found a replicable issue that involves the Ubuntu Core networking and 
causes complete loss of connectivity.
  We run a custom board with ubuntu core: the architecure is amrhf.
  We replicated this issue with an official Ubuntu Core image on a Raspberry 
Pi: other platform was been tested.
  It shows that it is a snap core problem which interests networkd: we use the 
default network stack based on networkd + netplan.

  Below steps to replicate the issue.

  1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes).
  2)Boot the board and wait for get an ip from dhcp server
  3)Before the lease expires, set a reservation for a different ip address

  Depending on lease duration before the lease expires( for 10 minute we have 2 
minutes before ), networkd configure the new address in addition to the 
previous one.
  When the lease expire both ip address ( the prevoius and the new one ) 
disappear from the interested network interface.
  Depending on lease duration before the second lease expires ( for 10 minure 
we have 2 minutes before ) networkd configure only the new ip address on the 
network interface and the ping toward an outside host work properly.

  During the test the dhcp server records correctly leases and their
  duration.

  We check directly from console the network interface setting with the
  tool ip, checking continuously the value for ip address and valid_lft
  fields for the interested network interface.

  Please note that if the ip address setting are the

[Touch-packages] [Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

2023-09-18 Thread Michael Biech

I'm also affected by this: I'm on Ubuntu 22.04.3 for Raspberry Pi and
after updating to 249.11-0ubuntu3.10 on boot I get:



Sep 18 19:16:33 pi4-ubuntu systemd[1]: Starting Wait for Network to be 
Configured...
Sep 18 19:19:29 pi4-ubuntu systemd-networkd-wait-online[1319]: Timeout occurred 
while waiting for network connectivity.
Sep 18 19:19:29 pi4-ubuntu systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
Sep 18 19:19:29 pi4-ubuntu systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
Sep 18 19:19:29 pi4-ubuntu systemd[1]: Failed to start Wait for Network to be 
Configured.



Output of networkctl:



IDX LINK TYPE OPERATIONAL SETUP
  1 lo   loopback carrier unmanaged
  2 eth0 etherroutableconfigured

2 links listed.



Running `SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-
online --timeout=5 --any` yields:



Found link 2
Found link 1
eth0: link is ignored
lo: link is ignored
Timeout occurred while waiting for network connectivity.



Which makes no sense, given eth0 is up and running.

I've made no changes to the default network settings and everything
worked up until the update. This also doesn't bother me TOO much, since
after the timeout of about 2 minutes, things continue as usual. Just a
bit annoying and I was honestly wondering whether I was going crazy
before I (luckily) stumbled upon this.

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

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2028180] [NEW] [SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id

2023-07-19 Thread Michael Reed

Public bug reported:

[Impact]

When working with NVMe/TCP host functionality, connecting to NVMe
subsystem through multiple controllers can lead to an invalid device
link created in /dev/disc/by-id/ being created.

Steps to reproduce:
Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04.1-live-server-amd64) on system.
Step 2: Install nvme-cli package, currently installed version is nvme version 
1.16
Step 3: In the os terminal, type any nvme connect-all to connect to NVMe 
subsystems and check the duplicate entries in /dev/disk/by-id/.

This may cause users to choose the wrong link and would not be able to
work with it.

[Fix]

udev-rules: fix nvme symlink creation on namespace changes
https://github.com/systemd/systemd/commit/c5ba7a2a4dd19a2d31b8a9d52d3c4bdde78387f0


[Test Plan]
Connect to NVMe/TCP subsystem using nvme connect-all. This was tested against a 
few Dell Storage systems.

Steps to Reproduce:
1. Use nvme connect-all to connect to an NVMe/TCP subsystems
2. Check /dev/disc/by-id

[ Where problems could occur ]


[ Other Info ]

Expected Behavior:
No duplicate entries of NVMe subsystems should exist.

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

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

Title:
  [SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id

Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

  When working with NVMe/TCP host functionality, connecting to NVMe
  subsystem through multiple controllers can lead to an invalid device
  link created in /dev/disc/by-id/ being created.

  Steps to reproduce:
  Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04.1-live-server-amd64) on system.
  Step 2: Install nvme-cli package, currently installed version is nvme version 
1.16
  Step 3: In the os terminal, type any nvme connect-all to connect to NVMe 
subsystems and check the duplicate entries in /dev/disk/by-id/.

  This may cause users to choose the wrong link and would not be able to
  work with it.

  [Fix]

  udev-rules: fix nvme symlink creation on namespace changes
  
https://github.com/systemd/systemd/commit/c5ba7a2a4dd19a2d31b8a9d52d3c4bdde78387f0

  
  [Test Plan]
  Connect to NVMe/TCP subsystem using nvme connect-all. This was tested against 
a few Dell Storage systems.

  Steps to Reproduce:
  1. Use nvme connect-all to connect to an NVMe/TCP subsystems
  2. Check /dev/disc/by-id

  [ Where problems could occur ]

  
  [ Other Info ]

  Expected Behavior:
  No duplicate entries of NVMe subsystems should exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2028180/+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 1960005] Re: Exceptions crash

2023-06-29 Thread Michael Truog

I bumped into this problem, as described in the issue
https://github.com/CloudI/CloudI/issues/229 .  To avoid it, I used clang
for compilation and both linking with '-rtlib=compiler-rt
-unwindlib=libunwind' and '-unwindlib=libgcc' was able to avoid the
segfault.  I also didn't see the segfault occur when using a Ubuntu
22.04 LTS VM in VirtualBox with (nongnu) libunwind 1.3.2, though the VM
execution only provides slower execution of the C++ throw that leads to
the libunwind segfault (i.e., it may not be able to replicate the
failure due to being slower).

It would be nice if Ubuntu 20.04 updated nongnu libunwind to 1.3.2 or
1.6.2 to avoid causing problems for other people, even if this situation
is unusual.  The issue linked above describes how to replicate the
problem (the execution takes less than 2 minutes to get a segfault).

** Bug watch added: github.com/CloudI/CloudI/issues #229
   https://github.com/CloudI/CloudI/issues/229

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

Title:
  Exceptions crash

Status in google-glog package in Ubuntu:
  Confirmed
Status in libunwind package in Ubuntu:
  Confirmed

Bug description:
  There is a serious bug in libunwind 1.2.1 on
  Ubuntu 20.04 which causes a crash when
  handling exceptions (C++ in my case).

  I have observed libunwind incorrectly
  restoring registers while executing DWARF
  opcodes in .eh_frame. In my case, the restore
  of the register r6 (rbp on x86-64) was
  prematurely commited. In certain complex
  scenarios with optimization enabled,
  gcc emits DWARF instructions which express
  the offsets for save addresses
  of higher-numbered registers against rbp
  (instead of against the canonical frame
  address, as is usual).
  If rbp is prematurely committed,
  higher-numbered registers are
  restored incorrectly, i.e. corrupted.

  I have described the issue in great detail at
  https://gcc.gnu.org/pipermail/gcc-help/2022-February/141189.html

  The current version on Arch (1.6.x) seems
  to have this bug fixed. I don’t known at
  which  point or which bug was it exactly,
  but it would be a really good idea to
  backport this fix.

  In my case, my application had libunwind
  linked in instead of using the builting gcc
  unwinder due to a 3rd party dependency,
  Google glog, used by the Google Ceres
  solver. However, it is only an optional
  dependency, and glog can be built without
  libunwind (it is just the preferred unwinder
  for printing stack dumps in glog).

  I had to rebuild glog without libunwind
  to stop my application from crashing
  (the builtin gcc unwinder works fine).

  Google has a strict policy against using
  C++ exceptions so I’m not surprised that
  they haven’t stumbled upon this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-glog/+bug/1960005/+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 1635382] Re: PrivateNetwork=yes (hostnamed, localed) does not work in lxd

2023-06-23 Thread Michael

This might actually be apparmor on the LXD host denying the container?

Look for messages like:

   2023-06-23T09:53:56.040427+08:00 grook kernel: [772843.931461] audit: 
type=1400 audit(1687485236.036:118): apparmor="DENIED" operation="file_lock" 
profile="lxd-pat_" pid=3334600 comm="(.plocate)" family="unix" 
sock_type="dgram" protocol=0 requested_mask="send"
   2023-06-23T09:53:56.040437+08:00 grook kernel: [772843.931469] audit: 
type=1400 audit(1687485236.036:119): apparmor="DENIED" operation="file_lock" 
profile="lxd-pat_" pid=3334600 comm="(.plocate)" family="unix" 
sock_type="dgram" protocol=0 requested_mask="send"

In my case, plocate-updatedb.service (and systemd-hostnamed.service)
fails to run inside containers when PrivateNetwork is enabled).

See also https://bugs.debian.org/1038315

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

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

Title:
  PrivateNetwork=yes (hostnamed, localed) does not work in lxd

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  $ lxc launch ubuntu-daily:yakkety y-hostname1
  $ sleep 10
  $ lxc exec y-hostname1 -- hostnamectl set-hostname smoser
  
  Could not set property: Connection timed out

  $ lxc exec y-hostname1 -- systemctl status --no-pager -l systemd-hostnamed 
  ● systemd-hostnamed.service - Hostname Service
 Loaded: loaded (/lib/systemd/system/systemd-hostnamed.service; static; 
vendor preset: enabled)
 Active: failed (Result: exit-code) since Thu 2016-10-20 19:19:16 UTC; 1min 
9s ago
   Docs: man:systemd-hostnamed.service(8)
 man:hostname(5)
 man:machine-info(5)
 http://www.freedesktop.org/wiki/Software/systemd/hostnamed
Process: 561 ExecStart=/lib/systemd/systemd-hostnamed (code=exited, 
status=225/NETWORK)
   Main PID: 561 (code=exited, status=225/NETWORK)

  Oct 20 19:19:16 y-hostname1 systemd[1]: Starting Hostname Service...
  Oct 20 19:19:16 y-hostname1 systemd[1]: systemd-hostnamed.service: Main 
process exited, code=exited, status=225/NETWORK
  Oct 20 19:19:16 y-hostname1 systemd[1]: Failed to start Hostname Service.
  Oct 20 19:19:16 y-hostname1 systemd[1]: systemd-hostnamed.service: Unit 
entered failed state.
  Oct 20 19:19:16 y-hostname1 systemd[1]: systemd-hostnamed.service: Failed 
with result 'exit-code'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Thu Oct 20 19:02:29 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635382/+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 1656024] Re: Units using PrivateNetwork=yes don't work inside user namespaces

2023-06-23 Thread Michael

This might be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635382

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

Title:
  Units using PrivateNetwork=yes don't work inside user namespaces

Status in systemd package in Ubuntu:
  Won't Fix
Status in varnish package in Ubuntu:
  New

Bug description:
  lxd host is Ubuntu 17.04 Alpha amd64
  lxd container is ubuntu:16.10

  hostnamectl does not work inside the lxd container:

  $ hostnamectl status
  $ sudo hostnamectl set-hostname server.example.com
  Could not set property: Connection timed out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1656024/+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 2019970] Re: OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

2023-06-22 Thread Michael Baentsch

Thanks very much for this complete answer and apologies for using the
term "bug completeness": I meant "feature stability" (with bugs being on
the arguably negative side of that term -- and this discussion being one
regarding a bug).

Clearly there's more users (valuing stability) than developers (valuing
"progress" -- with known risks).

I personally think the OpenSSL team goes to great lengths to not break
things with new sub-sub-version releases but I can appreciate that not
all projects do the same and you don't want to annoy your users.

Indeed your distribution is one of the first to have integrated OpenSSL3
-- which gave me the ability to integrate quantum safe crypto and thus
make available that capability (in 3.0.2 only for KEMs, in future
releases also for signatures/certificates) to Ubuntu users: So, a big
Thanks to you for having taken that step -- with regard to quantum
security possibly still many, many years before it's a true necessity.

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

Title:
  OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  Full bug report at https://github.com/openssl/openssl/issues/20981

  No upstream impact: OpenSSL 3.0.9-dev does not contain the problem any
  more.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2019970/+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 2019970] Re: OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

2023-06-16 Thread Michael Baentsch

Thanks for this explanation, Seth. Very good to know--from a security
perspective. A bit less satisfying from a functionality perspective,
particularly given the assurance by Matt from the OpenSSL team above.

I do understand though that you're aiming for "bug completeness" to
support those that rely on those bugs. The others then need to work
around them (using other distros or building packages from source).

Please feel free to close this report then.

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

Title:
  OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  Full bug report at https://github.com/openssl/openssl/issues/20981

  No upstream impact: OpenSSL 3.0.9-dev does not contain the problem any
  more.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2019970/+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 2019970] Re: OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

2023-06-15 Thread Michael Baentsch

Fine for me -- I'm working around this (not using Ubuntu for CI any more
and/or using/building less buggy OpenSSL releases for CI).

> if it's time to re-visit that practice of not updating through minor
openssl versions; it's risky to try.

What risks do you see? I find it much more risky _not_ to do it: You'll
retain buggy versions that are possibly also security risks: I'm
counting 24 CVEs that Ubuntu with this policy willingly does not fix --
as an Ubuntu user I wouldn't be happy (see
https://www.openssl.org/news/vulnerabilities-3.0.html)

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

Title:
  OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  Full bug report at https://github.com/openssl/openssl/issues/20981

  No upstream impact: OpenSSL 3.0.9-dev does not contain the problem any
  more.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2019970/+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 589496] Re: bash --rcfile does not behave as documented

2023-06-01 Thread Michael McNeil Forbes

My use case: I want to be able to spawn a clean shell with a customized
development environment (python) from a Makefile  (i.e. `make shell`
runs `bash --init-file .init_file.bash` which does not inherit cruft
from the environment (such as activated conda environments, PATHs etc.)

```
shell:
bash --init-file .init_file.bash
```

This worked fine until I started trying to use this on Debian-based
systems with -DSYS_BASHRC where, sometimes, admins activate a conda
environment for all users by default.

So, no admin access in the typical case.  Now a user can do this by
running `bash --norc` then manually sourcing `.init_file.bash` from that
shell.

How do I achieve this effect from my Makefile?  This is what I would
have expected `bash --norc --init-file .init_file.bash` but that is not
what bash does.  I tend to agree that ignoring `--rcfile` flag behaviour
with `--norc` is the error... but it looks like that is not going to
change.

So what do I do?  That non-admins are "not supposed to be able to bypass
it" seems moot, since they can with `--norc`. Am I missing something?

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

Title:
  bash --rcfile does not behave as documented

Status in bash package in Ubuntu:
  Confirmed
Status in bash package in Debian:
  New

Bug description:
  Binary package hint: bash

  the bash manpage says this about --rcfile

  --rcfile file
  Execute commands from file instead of the system  wide  initial‐
  ization file /etc/bash.bashrc and the standard personal initial‐
  ization file ~/.bashrc if the shell is interactive (see  INVOCA‐
  TION below).

  under INVOCATION it says

  When  an  interactive  shell that is not a login shell is started, bash
  reads and executes commands from  /etc/bash.bashrc  and  ~/.bashrc,  if
  these  files  exist.  This may be inhibited by using the --norc option.
  The --rcfile file option will force bash to read and  execute  commands
  from file instead of /etc/bash.bashrc and ~/.bashrc.

  but when i execute
  $ bash --rcfile somercfilewhichreallydoesexistandisreadableandall
  it will still read /etc/bash/bashrc (can be verified by adding --verbose)

  using lucid with bash 4.1-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/589496/+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 2018401] Re: Backport neon27 to 0.32.5 in Ubuntu 22.04, 0.32.2 has bugs

2023-05-31 Thread Michael Brohl

** Summary changed:

- Backport neon27 to  0.32.5 in Ubunto 22.04, 0.32.2 has bugs
+ Backport neon27 to  0.32.5 in Ubuntu 22.04, 0.32.2 has bugs

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

Title:
  Backport neon27 to  0.32.5 in Ubuntu 22.04, 0.32.2 has bugs

Status in neon27 package in Ubuntu:
  New

Bug description:
  Due to a bug in neon27 it is not possible to mount WebDAV folders with
  davfs.

  See https://github.com/notroj/neon/issues/78 and
  https://github.com/notroj/neon/issues/88

  This is solved in 0.32.5 as available in newer Ubuntu versions.
  Please provide a backport to upgrade neon27 to 0.32.5 in Ubuntu 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2018401/+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 589496] Re: bash --rcfile does not behave as documented

2023-05-28 Thread Michael McNeil Forbes

What is the status of this?  There is a further discussion from Chet
here:

https://www.mail-archive.com/bug-bash@gnu.org/msg20804.html

Why does Debian enable -DSYS_BASHRC?  This question does not seem to be
answered anywhere.

Is there a workaround?  Can someone release an alternate version of bash
for Ubuntu without -DSYS_BASHRC?

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

Title:
  bash --rcfile does not behave as documented

Status in bash package in Ubuntu:
  Confirmed
Status in bash package in Debian:
  New

Bug description:
  Binary package hint: bash

  the bash manpage says this about --rcfile

  --rcfile file
  Execute commands from file instead of the system  wide  initial‐
  ization file /etc/bash.bashrc and the standard personal initial‐
  ization file ~/.bashrc if the shell is interactive (see  INVOCA‐
  TION below).

  under INVOCATION it says

  When  an  interactive  shell that is not a login shell is started, bash
  reads and executes commands from  /etc/bash.bashrc  and  ~/.bashrc,  if
  these  files  exist.  This may be inhibited by using the --norc option.
  The --rcfile file option will force bash to read and  execute  commands
  from file instead of /etc/bash.bashrc and ~/.bashrc.

  but when i execute
  $ bash --rcfile somercfilewhichreallydoesexistandisreadableandall
  it will still read /etc/bash/bashrc (can be verified by adding --verbose)

  using lucid with bash 4.1-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/589496/+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 2019970] Re: OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

2023-05-21 Thread Michael Baentsch

Thanks for trying to reproduce this. A crash can only be triggered with
two providers active. Your command "OPENSSL_MODULES=_build/lib/
OPENSSL_CONF=scripts/o-ca.cnf ./.local/bin/openssl version" is not quite
conclusive: The config file "o-ca.cnf" doesn't look right. Please verify
that your setup confirms two instances of the provider being active. You
can do this with the option "list -providers": This is what must be
displayed (also in the test run) to trigger/showcase the problem:

OPENSSL_MODULES=_build/lib/ OPENSSL_CONF=scripts/openssl-ca.cnf 
LD_LIBRARY_PATH=.local/lib64 ./.local/bin/openssl list -providers
Providers:
  default
name: OpenSSL Default Provider
version: 3.2.0
status: active
  oqsprovider
name: OpenSSL OQS Provider
version: 0.5.0-dev
status: active
  oqsprovider2
name: OpenSSL OQS Provider
version: 0.5.0-dev
status: active

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

Title:
  OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

Status in openssl package in Ubuntu:
  New

Bug description:
  Full bug report at https://github.com/openssl/openssl/issues/20981

  No upstream impact: OpenSSL 3.0.9-dev does not contain the problem any
  more.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2019970/+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 2019970] [NEW] OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

2023-05-17 Thread Michael Baentsch

Public bug reported:

Full bug report at https://github.com/openssl/openssl/issues/20981

No upstream impact: OpenSSL 3.0.9-dev does not contain the problem any
more.

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

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

Title:
  OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

Status in openssl package in Ubuntu:
  New

Bug description:
  Full bug report at https://github.com/openssl/openssl/issues/20981

  No upstream impact: OpenSSL 3.0.9-dev does not contain the problem any
  more.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2019970/+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 2018985] [NEW] package ubuntu-minimal 1.501 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

2023-05-09 Thread Michael Klaeb

Public bug reported:

after restart same crash

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: ubuntu-minimal 1.501
ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6
Uname: Linux 6.2.0-1004-raspi aarch64
ApportVersion: 2.26.1-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: unknown
Date: Tue May  9 11:25:37 2023
ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
ImageMediaBuild: 20221018.1
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.6.0
SourcePackage: ubuntu-meta
Title: package ubuntu-minimal 1.501 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package arm64 arm64-image lunar raspi-image

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

Title:
  package ubuntu-minimal 1.501 failed to install/upgrade:
  Abhängigkeitsprobleme - verbleibt unkonfiguriert

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  after restart same crash

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-minimal 1.501
  ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6
  Uname: Linux 6.2.0-1004-raspi aarch64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Tue May  9 11:25:37 2023
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  ImageMediaBuild: 20221018.1
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: ubuntu-meta
  Title: package ubuntu-minimal 1.501 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2018985/+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 2018984] [NEW] package unattended-upgrades 2.9.1+nmu2ubuntu2 failed to install/upgrade: »installiertes post-installation-Skript des Paketes unattended-upgrades«-Unterprozess gab

2023-05-09 Thread Michael Klaeb

Public bug reported:

Updating the RaspberryPi 400 it crashes with error.
I do not really know the reason.
I will do a retry of the upgrade of the RaspberryPi 400 after a reboot.

I also could not update a Bananapi System with Ubuntu and send a few
days before also Bug Reports.

Best Regards from Germany

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: unattended-upgrades 2.9.1+nmu2ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-1017.24-raspi 5.19.17
Uname: Linux 5.19.0-1017-raspi aarch64
ApportVersion: 2.26.1-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: unknown
Date: Tue May  9 10:47:23 2023
ErrorMessage: »installiertes post-installation-Skript des Paketes 
unattended-upgrades«-Unterprozess gab den Fehlerwert 1 zurück
ImageMediaBuild: 20221018.1
PackageArchitecture: all
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.6.0
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 2.9.1+nmu2ubuntu2 failed to install/upgrade: 
»installiertes post-installation-Skript des Paketes 
unattended-upgrades«-Unterprozess gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "1";
 APT::Periodic::Download-Upgradeable-Packages "0";
 APT::Periodic::AutocleanInterval "0";
 APT::Periodic::Unattended-Upgrade "0";
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2023-03-11T22:07:25.851682

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


** Tags: apport-package arm64 arm64-image lunar raspi-image

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

Title:
  package unattended-upgrades 2.9.1+nmu2ubuntu2 failed to
  install/upgrade: »installiertes post-installation-Skript des Paketes
  unattended-upgrades«-Unterprozess gab den Fehlerwert 1 zurück

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Updating the RaspberryPi 400 it crashes with error.
  I do not really know the reason.
  I will do a retry of the upgrade of the RaspberryPi 400 after a reboot.

  I also could not update a Bananapi System with Ubuntu and send a few
  days before also Bug Reports.

  Best Regards from Germany

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: unattended-upgrades 2.9.1+nmu2ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1017.24-raspi 5.19.17
  Uname: Linux 5.19.0-1017-raspi aarch64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Tue May  9 10:47:23 2023
  ErrorMessage: »installiertes post-installation-Skript des Paketes 
unattended-upgrades«-Unterprozess gab den Fehlerwert 1 zurück
  ImageMediaBuild: 20221018.1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 2.9.1+nmu2ubuntu2 failed to 
install/upgrade: »installiertes post-installation-Skript des Paketes 
unattended-upgrades«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "0";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2023-03-11T22:07:25.851682

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2018984/+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 2018661] [NEW] package libxxf86vm1 1:1.1.4-1build3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2023-05-06 Thread Michael McConnell

Public bug reported:

Attempting to install steam

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libxxf86vm1 1:1.1.4-1build3
ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: pass
CompositorRunning: None
Date: Sat May  6 16:04:28 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics 
Controller [1043:122d]
InstallationDate: Installed on 2023-02-14 (81 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: ASUSTeK COMPUTER INC. X750JA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=/dev/mapper/vgubuntu-root ro recovery nomodeset dis_ucode_ldr
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.6
SourcePackage: libxxf86vm
Title: package libxxf86vm1 1:1.1.4-1build3 failed to install/upgrade: dpkg-deb 
--fsys-tarfile subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2013
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X750JB.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X750JA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX750JB.208:bd08/14/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnX750JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
dmi.product.family: X
dmi.product.name: X750JA
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-package jammy ubuntu

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

Title:
  package libxxf86vm1 1:1.1.4-1build3 failed to install/upgrade: dpkg-
  deb --fsys-tarfile subprocess returned error exit status 2

Status in libxxf86vm package in Ubuntu:
  New

Bug description:
  Attempting to install steam

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libxxf86vm1 1:1.1.4-1build3
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sat May  6 16:04:28 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:122d]
  InstallationDate: Installed on 2023-02-14 (81 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: ASUSTeK COMPUTER INC. X750JA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=/dev/mapper/vgubuntu-root ro recovery nomodeset dis_ucode_ldr
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.6
  SourcePackage: libxxf86vm
  Title: package libxxf86vm1 1:1.1.4-1build3 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JA

[Touch-packages] [Bug 2018401] [NEW] Backport neon27 to 0.32.5 in Ubunto 22.04, 0.32.2 has bugs

2023-05-03 Thread Michael Brohl

Public bug reported:

Due to a bug in neon27 it is not possible to mount WebDAV folders with
davfs.

See https://github.com/notroj/neon/issues/78 and
https://github.com/notroj/neon/issues/88

This is solved in 0.32.5 as available in newer Ubuntu versions.
Please provide a backport to upgrade neon27 to 0.32.5 in Ubuntu 22.04

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

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

Title:
  Backport neon27 to  0.32.5 in Ubunto 22.04, 0.32.2 has bugs

Status in neon27 package in Ubuntu:
  New

Bug description:
  Due to a bug in neon27 it is not possible to mount WebDAV folders with
  davfs.

  See https://github.com/notroj/neon/issues/78 and
  https://github.com/notroj/neon/issues/88

  This is solved in 0.32.5 as available in newer Ubuntu versions.
  Please provide a backport to upgrade neon27 to 0.32.5 in Ubuntu 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2018401/+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 2017317] Re: Ubuntu: upon reboot, forever waiting for encrypted swapfile ...

2023-04-21 Thread Michael Heuberger

I've initially reported this bug there
https://gitlab.com/cryptsetup/cryptsetup/-/issues/811#note_1361818938

But got recommended posting it here instead.

There, Milan Broz added following:

"My guess here is that /etc/crypttab is missing something about
cryptswap device, but we cannot do anything with these problems in the
upstream cryptsetup project (also, Debian/Ubuntu specific cryptsetup
tools are not even maintained upstream."

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

Title:
Ubuntu: upon reboot, forever waiting for encrypted swapfile ...

Status in systemd package in Ubuntu:
New

Bug description:
### Issue description
When restarting my machine, cryptsetup waits forever. Waiting for the
swapfile. Unable to start Ubuntu at all. Error message is:

```
cryptsetup: Waiting for encrypted source device /swapfile...
```

### Steps for reproducing the issue
1. Do a fresh installation of Ubuntu, unencrypted.
2. Later, due to restrictions at work, encrypt Ubuntu POST installation
accordingly to this article:
https://jumpcloud.com/blog/how-to-encrypt-ubuntu-20-04-desktop-post-installation
3. Reboot, all works fine, but ...
4. Later, after a couple of months, install a new Linux kernel and then ...
5. Upon boot cryptsetup gets stuck, waits forever. See attached photo.

### Additional info
I've found a temporary, painful workaround by rebooting in recovery mode and
running this command every time:

```
sudo update-initramfs -u -k all
```

Then I can boot again. But I have to do this every time. Why?

### Debug log

Hard to say but here's the output of this command `journalctl | grep
crypt`, not sure if you can find anything interesting about it:

```
Apr 21 13:48:28 M1 audit[179547]: AVC apparmor="DENIED" operation="getattr"
class="file" info="Failed name lookup - disconnected path" error=-13
profile="/usr/bin/evince-thumbnailer"
name="home/.ecryptfs/michael-heuberger/.Private/ECRYPTFS_FNEK_ENCRYPTED.FWaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0W8LFNkfXu75b-QusjTdAA---/ECRYPTFS_FNEK_ENCRYPTED.FXaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0JjExLlqv3Fk6x4GGYcQdjXda2554lHGsMAmCwjYZWGA-"
pid=179547 comm="evince-thumbnai" requested_mask="r" denied_mask="r"
fsuid=1000 ouid=1000
Apr 21 17:01:49 M1 gdm-password][219451]: pam_ecryptfs: pam_sm_authenticate:
/home/michael-heuberger is already mounted
Apr 21 17:26:59 M1 systemd[1]: Requested transaction contradicts existing
jobs: Transaction for plymouth-quit.service/start is destructive
(dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop'
job queued, but 'start' is included in transaction).
Apr 21 17:26:59 M1 systemd[1]: gdm.service: Failed to enqueue OnFailure= job,
ignoring: Transaction for plymouth-quit.service/start is destructive
(dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop'
job queued, but 'start' is included in transaction).
Apr 21 17:26:59 M1 systemd[3094]: Stopping GnuPG cryptographic agent and
passphrase cache...
Apr 21 17:27:00 M1 systemd[3094]: Stopped GnuPG cryptographic agent and
passphrase cache.
Apr 21 17:27:07 M1 systemd[1]: Stopped target Local Encrypted Volumes.
Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig
[2bda85c181b04823]: Required key not available
Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig
[96c111e5680ecc45]: Required key not available
Apr 21 17:27:09 M1 systemd[1]: Deactivating swap
/dev/disk/by-id/dm-name-cryptswap1...
Apr 21 17:27:09 M1 systemd[1]: dev-disk-by\x2dlabel-cryptswap1.swap:
Deactivated successfully.
Apr 21 17:27:09 M1 systemd[1]: Deactivated swap /dev/disk/by-label/cryptswap1.
```

Do you have any tips, advice please, how to fix this, how can I reboot
my machine without running `update-initramfs` every time? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017317/+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 2017317] [NEW] Ubuntu: upon reboot, forever waiting for encrypted swapfile ...

2023-04-21 Thread Michael Heuberger

Public bug reported:

### Issue description
When restarting my machine, cryptsetup waits forever. Waiting for the swapfile.
Unable to start Ubuntu at all. Error message is:

```
cryptsetup: Waiting for encrypted source device /swapfile...
```

### Additional info
I've found a temporary, painful workaround by rebooting in recovery mode and
running this command every time:

```
sudo update-initramfs -u -k all
```

Then I can boot again. But I have to do this every time. Why?

### Debug log

Hard to say but here's the output of this command `journalctl | grep
crypt`, not sure if you can find anything interesting about it:

```
Apr 21 13:48:28 M1 audit[179547]: AVC apparmor="DENIED" operation="getattr"
class="file" info="Failed name lookup - disconnected path" error=-13
profile="/usr/bin/evince-thumbnailer"
name="home/.ecryptfs/michael-heuberger/.Private/ECRYPTFS_FNEK_ENCRYPTED.FWaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0W8LFNkfXu75b-QusjTdAA---/ECRYPTFS_FNEK_ENCRYPTED.FXaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0JjExLlqv3Fk6x4GGYcQdjXda2554lHGsMAmCwjYZWGA-"
pid=179547 comm="evince-thumbnai" requested_mask="r" denied_mask="r"
fsuid=1000 ouid=1000
Apr 21 17:01:49 M1 gdm-password][219451]: pam_ecryptfs: pam_sm_authenticate:
/home/michael-heuberger is already mounted
Apr 21 17:26:59 M1 systemd[1]: Requested transaction contradicts existing jobs:
Transaction for plymouth-quit.service/start is destructive
(dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop'
job queued, but 'start' is included in transaction).
Apr 21 17:26:59 M1 systemd[1]: gdm.service: Failed to enqueue OnFailure= job,
ignoring: Transaction for plymouth-quit.service/start is destructive
(dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop'
job queued, but 'start' is included in transaction).
Apr 21 17:26:59 M1 systemd[3094]: Stopping GnuPG cryptographic agent and
passphrase cache...
Apr 21 17:27:00 M1 systemd[3094]: Stopped GnuPG cryptographic agent and
passphrase cache.
Apr 21 17:27:07 M1 systemd[1]: Stopped target Local Encrypted Volumes.
Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig
[2bda85c181b04823]: Required key not available
Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig
[96c111e5680ecc45]: Required key not available
Apr 21 17:27:09 M1 systemd[1]: Deactivating swap
/dev/disk/by-id/dm-name-cryptswap1...
Apr 21 17:27:09 M1 systemd[1]: dev-disk-by\x2dlabel-cryptswap1.swap:
Deactivated successfully.
Apr 21 17:27:09 M1 systemd[1]: Deactivated swap /dev/disk/by-label/cryptswap1.
```

Do you have any tips, advice please, how to fix this, how can I reboot
my machine without running `update-initramfs` every time? Thanks!

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

** Attachment added: "Screenshot of error message upon boot"

https://bugs.launchpad.net/bugs/2017317/+attachment/5666561/+files/IMG_2291.jpg

** Bug watch added: gitlab.com/cryptsetup/cryptsetup/-/issues #811
https://gitlab.com/cryptsetup/cryptsetup/-/issues/811

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

Title:
Ubuntu: upon reboot, forever waiting for encrypted swapfile ...

Status in systemd package in Ubuntu:
New

Bug description:
### Issue description
When restarting my machine, cryptsetup waits forever. Waiting for the
swapfile. Unable to start Ubuntu at all. Error message is:

```
cryptsetup: Waiting for encrypted source device /swapfile...
```

### Additional info
I've found a temporary, painful workaround by rebooting in recovery mode and
running this command every time:

```
sudo update-initramfs -u -k all
```

Then I can boot again. But I have to do this every time. Why?

### Debug log

Hard to say but here's the output of this command `journalctl | grep
crypt`, no

[Touch-packages] [Bug 2015134] [NEW] libdmapsharing with 3.0 API is incompatible with libsoup3

2023-04-03 Thread W. Michael Petullo

Public bug reported:

The version of the libdmapsharing API found in the libdmapsharing
packages shipped by Ubuntu is obsolete, and the versions of
libdmapsharing that provide it are incompatible with libsoup3. Since
more applications are requiring libsoup3, and libsoup3 cannot exist with
libsoup2 in the same process, Ubuntu should move to
libdmapsharing-3.9.12+ in its upcoming release. Libdmapsharing-3.9.12+
makes use of libsoup3. The packages that use libdmapsharing include
Rhythmbox and grilo-plugins, and both recently moved to libsoup3:

https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1996
https://gitlab.gnome.org/GNOME/grilo-plugins/-/commit/ae34da2264eab49eceaeeb0d1510b952a65ae030

The 3.9 series of libdmapsharing is available at:

https://www.flyn.org/projects/libdmapsharing/

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

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

Title:
  libdmapsharing with 3.0 API is incompatible with libsoup3

Status in libdmapsharing package in Ubuntu:
  New

Bug description:
  The version of the libdmapsharing API found in the libdmapsharing
  packages shipped by Ubuntu is obsolete, and the versions of
  libdmapsharing that provide it are incompatible with libsoup3. Since
  more applications are requiring libsoup3, and libsoup3 cannot exist
  with libsoup2 in the same process, Ubuntu should move to
  libdmapsharing-3.9.12+ in its upcoming release. Libdmapsharing-3.9.12+
  makes use of libsoup3. The packages that use libdmapsharing include
  Rhythmbox and grilo-plugins, and both recently moved to libsoup3:

  https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1996
  
https://gitlab.gnome.org/GNOME/grilo-plugins/-/commit/ae34da2264eab49eceaeeb0d1510b952a65ae030

  The 3.9 series of libdmapsharing is available at:

  https://www.flyn.org/projects/libdmapsharing/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdmapsharing/+bug/2015134/+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 2012563] Re: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'

2023-03-30 Thread Michael Vogt

This also affects "functionfs" that uses
"uid=2000,gid=2000,no_disconnect=1,rmode=0550,fmode=0660 ".

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

Title:
  unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and
  'nolazytime'

Status in apparmor package in Ubuntu:
  New

Bug description:
  The following mount options are unsupported: 'nofail',
  'nostrictatime', 'lazytime', and 'nolazytime'.

  Other mount options have mappings from options to bitflags in
  `parser/mount.cc`, and the bitflags themselves are defined in
  `parser/mount.h`. Should the aforementioned mount options be included
  as well, or is there a reason why they are excluded? snapd currently
  assumes that they are supported, resulting in an error from the
  apparmor parser when a snap is connected with those options.

  I'd be happy to file a PR to add these mappings if I knew what the new
  bitflags should be defined as, and if/how they should be used
  elsewhere.

  For completeness:
  1) This is a question/bug regarding the source code from the 'ubuntu/devel' 
branch (and presumably other branches), not a particular release.
  2) Same as 1).
  3) I expected the apparmor parser to recognize the 'nofail', 'nostrictatime', 
'laztime', and 'nolazytime' mount options.
  4) The apparmor parser threw an error with message "unsupported mount 
options" (from within `parser/mount.cc`).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012563/+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 2009071] [NEW] [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all

2023-03-02 Thread Michael Black

Public bug reported:

New install of Ubuntu 22.04 has no audio.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mblack 1793 F pulseaudio
 /dev/snd/controlC1:  mblack 1793 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: 
Error executing command as another user: Request dismissed
Date: Thu Mar  2 13:21:20 2023
InstallationDate: Installed on 2023-03-02 (0 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
Symptom_Card: sof-hda-dsp - sof-hda-dsp
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mblack 1793 F pulseaudio
 /dev/snd/controlC1:  mblack 1793 F pulseaudio
  mblack 8091 F alsamixer
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/27/2023
dmi.bios.release: 1.7
dmi.bios.vendor: Razer
dmi.bios.version: 1.07
dmi.board.name: SO690
dmi.board.vendor: Razer
dmi.board.version: 4
dmi.chassis.type: 10
dmi.chassis.vendor: Razer
dmi.ec.firmware.release: 1.3
dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd01/27/2023:br1.7:efr1.3:svnRazer:pnBlade16-RZ09-0483:pvr9.04:rvnRazer:rnSO690:rvr4:cvnRazer:ct10:cvr:skuRZ09-0483SEJ3:
dmi.product.family: 1A583006 Razer Blade
dmi.product.name: Blade 16 - RZ09-0483
dmi.product.sku: RZ09-0483SEJ3
dmi.product.version: 9.04
dmi.sys.vendor: Razer

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2009071

Title:
  [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  New install of Ubuntu 22.04 has no audio.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mblack 1793 F pulseaudio
   /dev/snd/controlC1:  mblack 1793 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: 
Error executing command as another user: Request dismissed
  Date: Thu Mar  2 13:21:20 2023
  InstallationDate: Installed on 2023-03-02 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mblack 1793 F pulseaudio
   /dev/snd/controlC1:  mblack 1793 F pulseaudio
mblack 8091 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: SO690
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd01/27/2023:br1.7:efr1.3:svnRazer:pnBlade16-RZ09-0483:pvr9.04:rvnRazer:rnSO690:rvr4:cvnRazer:ct10:cvr:skuRZ09-0483SEJ3:
  dmi.product.family: 1A583006 Razer Blade
  dmi.product.name: Blade 16 - RZ09-0483
  dmi.product.sku: RZ09-0483SEJ3
  dmi.product.version: 9.04
  dmi.sys.vendor: Razer

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


-- 
Mailing list:

[Touch-packages] [Bug 2006754] Re: hdmi audio not working after suspend to ram

2023-02-18 Thread Michael

So, just to try something, I installed kernel 6.2rc8 from Ubuntu kernel
PPA. And... Problem fixed!!

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

Title:
  hdmi audio not working after suspend to ram

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello

  I installed a new Kubuntu 22.10 system on a Beelink GTR6 (AMD Ryzen 9
  6900HX). Everything is running fine. Except that after a wakeup from a
  suspend to RAM, there is no more Audio coming through the loudspeakers
  in my HDMI monitor, although every widget, audio control etc still say
  that audio is playing. I have not yet found any way to reactivate the
  audio, except of a complete reboot of the system.

  I am not sure, how to debug this. I have tried very many
  recommendations from the net (to restart pipewire, wireplumber,
  disconnect the HDMI device, open amixer, ...), but none worked.

  Thanks

  Michael

  ---

  Betriebssystem: Kubuntu 22.10
  KDE-Plasma-Version: 5.25.5
  KDE-Frameworks-Version: 5.98.0
  Qt-Version: 5.15.6
  Kernel-Version: 5.19.0-31-generic (64-bit)
  Grafik-Plattform: X11
  Prozessoren: 16 × AMD Ryzen 9 6900HX with Radeon Graphics
  Speicher: 28.2 GiB Arbeitsspeicher
  Grafikprozessor: REMBRANDT
  Hersteller: AZW
  Produktname: GTR
  Systemversion: V02

  
  Affected package: No idea, maybe pipewire, wireplumber, but probably a kernel 
driver

  Expected result: HDMI audio should work after wakeup from a suspend-
  to-ram

  
  Some output from pw-cli ls:
  ``` 
id 0, type PipeWire:Interface:Core/3
object.serial = "0"
core.name = "pipewire-0"
id 1, type PipeWire:Interface:Module/3
object.serial = "1"
module.name = "libpipewire-module-rt"
id 2, type PipeWire:Interface:Module/3
object.serial = "2"
module.name = "libpipewire-module-protocol-native"
id 3, type PipeWire:Interface:Module/3
object.serial = "3"
module.name = "libpipewire-module-profiler"
id 4, type PipeWire:Interface:Profiler/3
object.serial = "4"
id 5, type PipeWire:Interface:Module/3
object.serial = "5"
module.name = "libpipewire-module-metadata"
id 6, type PipeWire:Interface:Factory/3
object.serial = "6"
module.id = "5"
factory.name = "metadata"
factory.type.name = "PipeWire:Interface:Metadata"
factory.type.version = "3"
id 7, type PipeWire:Interface:Module/3
object.serial = "7"
module.name = "libpipewire-module-spa-device-factory"
id 8, type PipeWire:Interface:Factory/3
object.serial = "8"
module.id = "7"
factory.name = "spa-device-factory"
factory.type.name = "PipeWire:Interface:Device"
factory.type.version = "3"
id 9, type PipeWire:Interface:Module/3
object.serial = "9"
module.name = "libpipewire-module-spa-node-factory"
id 10, type PipeWire:Interface:Factory/3
object.serial = "10"
module.id = "9"
factory.name = "spa-node-factory"
factory.type.name = "PipeWire:Interface:Node"
factory.type.version = "3"
id 11, type PipeWire:Interface:Module/3
object.serial = "11"
module.name = "libpipewire-module-client-node"
id 12, type PipeWire:Interface:Factory/3
object.serial = "12"
module.id = "11"
factory.name = "client-node"
factory.type.name = "PipeWire:Interface:ClientNode"
factory.type.version = "4"
id 13, type PipeWire:Interface:Module/3
object.serial = "13"
module.name = "libpipewire-module-client-device"
id 14, type PipeWire:Interface:Factory/3
object.serial = "14"
module.id = "13"
factory.name = "client-device"
factory.type.name = "Spa:Pointer:Interface:Device"
factory.type.version = "0"
id 15, type PipeWire:Interface:Module/3
object.serial = "15"
module.name = "libpipewire-modul

[Touch-packages] [Bug 2007004] Re: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected

2023-02-12 Thread Michael P

 2S Mouse 
as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88
-   Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 
0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 
2S] on 20:4e:xx:xx:xx:xx
-   Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S 
Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90
-   Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse 
as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91
-   Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 
0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 
2S] on 20:4e:xx:xx:xx:xx
+   Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from 
de:5d:xx:xx:xx:xx by
+   local choice (Reason: 3=DEAUTH_LEAVING)
+   Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta 
de:5d:xx:xx:xx:xx
+   with macid 0 left
+   Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S 
Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87
+   Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse 
as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88
+   Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 
0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 
2S] on 20:4e:xx:xx:xx:xx
+   Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S 
Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90
+   Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse 
as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91
+   Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 
0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 
2S] on 20:4e:xx:xx:xx:xx
  < I reconnect to Wifi>
-   Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S 
Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93
-   Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse 
as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94
-   Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 
0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 
2S] on 20:4e:xx:xx:xx:xx
-   Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with 
de:5d:xx:xx:xx:xx
-   Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to 
de:5d:xx:xx:xx:xx (try 1/3)
-   Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated
-   Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with 
de:5d:xx:xx:xx:xx (try 1/3)
-   Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from 
de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2)
-   Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta 
de:5d:xx:xx:xx:xx joined with macid 0
-   Feb 11 20:47:19 ithaca kernel: [ 3449.943789] wlo1: associated
-   Feb 11 20:47:19 ithaca kernel: [ 3449.995269] IPv6: 
ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
+   Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S 
Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93
+   Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse 
as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94
+   Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 
0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 
2S] on 20:4e:xx:xx:xx:xx
+   Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with 
de:5d:xx:xx:xx:xx
+   Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to 
de:5d:xx:xx:xx:xx (try 1/3)
+   Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated
+   Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with 
de:5d:xx:xx:xx:xx (try 1/3)
+   Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from 
de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2)
+   Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta 
de:5d:xx:xx:xx:xx joined with macid 0
+   Feb 11 20:47:19 ithaca kernel: [ 3449.943789] wlo1: associated
+   Feb 11 20:47:19 ithaca kernel: [ 3449.995269] IPv6: 
ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
  
  Nothing logged in dmesg
  
  After reconnecting WiFi, everything works OK again.
- 
- I assume bluez is the correct package - please let me know if otherwise,
- of if there is any other info I can provide.
- 
- Thanks,
- 
- Michael

** Summary changed:

- Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected
+ rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi 
disconnected

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

Title:
  rtw88_8821ce: Bluet

[Touch-packages] [Bug 2007004] [NEW] Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected

2023-02-11 Thread Michael P

if otherwise,
of if there is any other info I can provide.

Thanks,

Michael

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

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

Title:
  Bluetooth Mouse goes into connect/disconnect loop when Wifi
  disconnected

Status in bluez package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.01 /  ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse.
  Fully updated via apt.

  Everything worked OK until sometime around early January 2023 (it may
  have started earlier, but I only noticed it the first time I moved to
  a location without WiFi).

  Since then, everything works OK as long as I am connected to WiFi. The
  moment I disconnect from a WiFi network, or disable WiFi altogether,
  the mouse begins to rapidly disconnect/connect in a loop about 3-4
  times a second. If I boot up somewhere where I have no WiFi signal,
  same thing happens.

  If I boot with an older 22.04.01 live USB  - no problem
  If I boot with a recent 22.10 live USB - same problem

root@ithaca:~ # uname -a  
Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 
x86_64 x86_64 x86_64 
GNU/Linux

root@ithaca:~ # inxi -EMN
Machine:
  Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA
v: 1.0 serial: 
  Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX
UEFI: American Megatrends v: E410MA.302 date: 09/11/2020
Network:
  Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
driver: rtw_8821ce
Bluetooth:
  Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb
  Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1

  Output of running bluetoothctl while this happens:

root@ithaca:/var/log # bluetoothctl
Agent registered
  (At this point I disconnect WiFI. Mouse starts acting up immediately, 
responding erratically,
   then about 10 seconds elapse, then the below messages start)
[CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no
[CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
[CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes
[CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no
[CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
[CHG] Device E4:3B:XX:XX:XX:XX Connected: no
[CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
[CHG] Device E4:3B:XX:XX:XX:XX Connected: no
  (This goes on and on about 3 times a second until I reconnect Wifi using 
the touchpad)
[CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
[CHG] Device E4:3B:XX:XX:XX:XX Connected: no
[CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
[CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes
[MX Anywhere 2S]# 
[MX Anywhere 2S]# 

  kern.log messages while this happens:
  < I disconnect from Wifi>
Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from 
de:5d:xx:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta 
de:5d:xx:xx:xx:xx 
with macid 0 left
Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S 
Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87
Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse 
as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88
Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 
0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 
2S] on 20:4e:xx:xx:xx:xx
Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S 
Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90
Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse 
as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91
Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 
0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 
2S] on 20:4e:xx:xx:xx:xx
  < I reconnect to Wifi>
Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S 
Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93
Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse 
as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94
Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 
0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 
2S] on 20:4e:xx:xx:xx:xx
Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with 
de:5d:xx:xx:xx:xx
Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to 
de:5d:xx:xx:xx:xx (try 1/3)
Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated
Feb 11 20:47:19 ithaca kernel: [ 3449.939267]

[Touch-packages] [Bug 1971932] Re: error in rsync protocol data stream

2023-01-11 Thread Michael Knichel

I have confirmed this bug as well.  Here is what I have done:

rsync failed when transferring large files over network with error 12
when using compression (z option).  rsync succeeded when I transferred
large files over USB to external SSD when using compression (z option).
rsync succeeded when transferring large files over network when NOT
using compression (z option).

Hope this offers some assistance in tracking and correcting this bug.

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

Title:
  error in rsync protocol data stream

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  When synchronizing to other systems, rsync exits with "error in rsync
  protocol data stream (code 12)".

  The problem occurs since ubuntu 22.04 LTS with two different
  destination systems not running ubuntu but plain debian. The error did
  not occur under 20.04 LTS.

  Synchronisation runs fine for most other files, but always stops at
  the same (relative large) file. The file itself has also been changed
  on a test basis to make sure the file is not the problem itself.

  Log snippet:
  

  ...
  chunk[46131] len=46120 offset=2127561720 sum1=2f48caf4
  chunk[46132] len=46120 offset=2127607840 sum1=5dfcb4ee
  chunk[46133] len=46120 offset=2127653960 sum1=d1037d81
  chunk[46134] len=8870 offset=2127700080 sum1=6deedc97
  send_files mapped 
/path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX of size 
2135722584
  calling match_sums 
/path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX
  built hash table
  hash search b=46120 len=2135722584
  sum=1e1722dc k=46120
  hash search s->blength=46120 len=2135722584 count=46135
  potential match at 0 i=0 sum=1e1722dc
  match at 0 last_match=0 j=0 len=46120 n=0
  potential match at 46120 i=1 sum=c482d6b6
  match at 46120 last_match=46120 j=1 len=46120 n=0
  potential match at 92240 i=2 sum=b21c7e11
  match at 92240 last_match=92240 j=2 len=46120 n=0
  potential match at 138360 i=3 sum=d066473a
  match at 138360 last_match=138360 j=3 len=46120 n=0
  potential match at 184480 i=4 sum=a32a2984
  match at 184480 last_match=184480 j=4 len=46120 n=0
  potential match at 230600 i=5 sum=39cc049f
  match at 230600 last_match=230600 j=5 len=46120 n=0
  potential match at 276720 i=6 sum=ad3de98a
  match at 276720 last_match=276720 j=6 len=46120 n=0
  potential match at 322840 i=7 sum=83e16fa9
  match at 322840 last_match=322840 j=7 len=46120 n=0
  deflate on token returned 0 (8512 bytes left)
  rsync error: error in rsync protocol data stream (code 12) at token.c(476) 
[sender=3.2.3]
  [sender] _exit_cleanup(code=12, file=token.c, line=476): entered
  [sender] _exit_cleanup(code=12, file=token.c, line=476): about to call 
exit(12)

  Sender system: (rsync 3.2.3-8ubuntu3)
  -

  rsync  version 3.2.3  protocol version 31
  Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others.
  Web site: https://rsync.samba.org/
  Capabilities:
  64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,
  socketpairs, hardlinks, hardlink-specials, symlinks, IPv6, atimes,
  batchfiles, inplace, append, ACLs, xattrs, optional protect-args, iconv,
  symtimes, prealloc, stop-at, no crtimes
  Optimizations:
  SIMD, no asm, openssl-crypto
  Checksum list:
  xxh128 xxh3 xxh64 (xxhash) md5 md4 none
  Compress list:
  zstd lz4 zlibx zlib none

  rsync comes with ABSOLUTELY NO WARRANTY.  This is free software, and you
  are welcome to redistribute it under certain conditions.  See the GNU
  General Public Licence for details.

  Recipient systems: (rsync 3.1.3-6)
  --

  rsync  version 3.1.3  protocol version 31
  Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others.
  Web site: http://rsync.samba.org/
  Capabilities:
  64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,
  socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
  append, ACLs, xattrs, iconv, symtimes, prealloc

  rsync comes with ABSOLUTELY NO WARRANTY.  This is free software, and you
  are welcome to redistribute it under certain conditions.  See the GNU
  General Public Licence for details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1971932/+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 1950906] Re: etc/rc.local should Want or Require network-online.target

2022-12-28 Thread Michael Tokarev

Hmm. Come on please. rc.local should NOT, in any way possible, depend on
network-online *by default*. Enabling that After= directive was a
mistake. Why do you think that any system not connected to the network
but which uses anything in rc.local (like doing any *local* stuff)
should not let the user to login?  Is this a joke or what?  Guys, come
on, this is insane..

I come here after having a painful debugging session with my pc not
letting me in. Because rc.local is waiting for the network which is not
here.

If *your* rc.local modifications (rc.local is empty by default) require
network, by all means, add a *local* config droplet like this. But
never, ever, lock people out of their PCs.

*Shrug*.

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

Title:
  etc/rc.local should Want or Require network-online.target

Status in systemd package in Ubuntu:
  New

Bug description:
  The fix for bug #1451797 introduced /lib/systemd/system/rc-
  local.service.d/debian.conf with the intent that rc.local would always
  run after the network was fully online. However, it only has an After=
  line, without actually pulling in network-online.target. Systemd docs
  say:

  "Units that strictly require a configured network connection should pull in 
network-online.target (via a Wants= type dependency) and order themselves after 
it. ... Note the distinction between this unit and network.target. This unit is 
an active unit (i.e. pulled in by the consumer rather than the
  provider of this functionality) ... Usually, network.target is part of the 
boot of most systems, while network-online.target is not ..."

  TL;DR - need to add "Wants=network-online.target" to
  /lib/systemd/system/rc-local.service.d/debian.conf :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.13
  ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148
  Uname: Linux 5.4.0-90-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Xpra
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sun Nov 14 17:22:54 2021
  InstallationDate: Installed on 2017-01-08 (1771 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
   |__ Port 9: Dev 3, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M
  MachineType: Dell Inc. OptiPlex 3040
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-90-generic 
root=/dev/mapper/lvg2-host ro rootflags=subvol=rootfs rw 
drm.edid_firmware=edid/toguard2.bin video=HDMI-A-1:1024x768@60D
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-09-02 (73 days ago)
  acpidump:
   
  dmi.bios.date: 06/30/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.6
  dmi.board.name: 0TTDMJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.6:bd06/30/2016:svnDellInc.:pnOptiPlex3040:pvr:rvnDellInc.:rn0TTDMJ:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 3040
  dmi.product.sku: 06BB
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.logind.conf: 2019-03-03T09:57:30.814201

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950906/+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 1999104] Re: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort

2022-12-14 Thread Michael Hudson-Doyle

I tweaked the version numbers slightly (ubuntu1 -> ubuntu0.1) and
uploaded.

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

Title:
  arm64: broken c++ exception handler support leads to std::terminate()
  being called and program abort

Status in libunwind package in Ubuntu:
  Fix Released
Status in libunwind source package in Bionic:
  In Progress
Status in libunwind source package in Focal:
  In Progress

Bug description:
  [Impact]

  On architectures other than i386 and amd64, the C++ exception support
  in libunwind appears to be broken, always failing and calling
  std::terminate() which leads to the program aborting.

  (gdb) bt
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
  #1  0xf7c2daac in __GI_abort () at abort.c:79
  #2  0xf7e21868 in __gnu_cxx::__verbose_terminate_handler() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #3  0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6
  #4  0xf7e1f280 in std::terminate() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #5  0xf7e1f5e0 in __cxa_rethrow ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #6  0xf7e21804 in __gnu_cxx::__verbose_terminate_handler() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #7  0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6
  #8  0xf7e1f280 in std::terminate() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #9  0xf7e1f574 in __cxa_throw ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #10 0xf7fb9f50 in function_throws_int () at lib.cpp:9
  #11 0x0d54 in main (argc=1, argv=0xfab8) at main.cpp:9

  Compiling libunwind with --enable-cxx-exceptions enabled leads to
  _Unwind_RaiseException being called during __cxa_throw(), which fails
  to find a handler, and the generic std::terminate() is called instead,
  aborting the program.

  On i386 and amd64 this doesn't seem to be the case, and the libunwind
  handlers seem to be present.

  To fix, we only enable the configure option --enable-cxx-exceptions on
  i386 and amd64 only, in debian/rules. This lets other architectures
  fall back to the symbols provided by libgcc_s, which implementation
  works correctly.

  [Testcase]

  Ali Sadi has provided a reproducer program.

  Start an arm64 instance, for example, a c6g.medium instance on AWS,
  with either Bionic or Focal.

  $ wget 
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635122/+files/libunwind.tar.gz
  $ sudo apt install -y build-essential libunwind-dev
  $ tar xvf libunwind.tar.gz && cd test
  $ make all

  There are two executable, main and main_unwind. main is not linked to
  libunwind, and main_unwind is linked to libunwind.

  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  terminate called after throwing an instance of 'int'
  terminate called recursively
  Aborted (core dumped)

  If you install the test package available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf350246-test

  $ make clean
  $ sudo apt install -y libunwind-dev
  $ make all
  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  int throws lib
  int caught main

  The exception is caught as expected the program does not abort.

  [Where problems could occur]

  For architectures other than i386 and amd64, we are changing from
  libunwind provided exception handlers for __cxa_throw(), and using
  those provided by libgcc_s instead.

  There are a few reverse dependencies for libunwind-dev and libunwind8,
  which need to be considered:

  $ apt rdepends libunwind-dev
  libunwind-dev
  Reverse Depends:
Depends: libunwind-setjmp0-dev (= 1.2.1-9build1)
Depends: libefl-all-dev

  t$ apt rdepends libunwind-dev8
  libunwind8
  Reverse Depends:
Depends: libunwind-dev (= 1.2.1-9build1)
Depends: xvfb
Depends: xnest
Depends: xdmx
Depends: xwayland
Depends: xserver-xorg-core
Depends: xserver-xephyr
Depends: linux-tools-5.4.0-*
Depends: linux-raspi-tools-*
Depends: linux-raspi2-tools-5.4.0-*
Depends: linux-raspi2-5.4-tools-5.4.0-*
Depends: linux-oracle-5.15-tools-5.15.0-*
Depends: linux-lowlatency-hwe-5.15-tools-5.15.0-*
Depends: linux-hwe-5.8-tools-5.8.0-*
Depends: linux-hwe-5.15-tools-5.15.0-*
Depends: linux-gke-tools-5.4.0-*
Depends: linux-gke-5.15-tools-5.15.0-*
Depends: linux-gcp-tools-5.4.0-*
Depends: linux-gcp-5.15-tools-5.15.0-*
Depends: linux-azure-tools-5.4.0-*
Depends: linux-azure-5.15-tools-5.15.0-*
Depends: linux-aws-tools-5.4.0-*
Depends: linux-aws-5.8-tools-5.8.0-*
Depends: linux-aws-5.15-tools-5.15.0-*
Depends: xvfb
Depends: xnest
Depends: xdmx
Depends: trafficserver
Depends: tilix
Depends:

[Touch-packages] [Bug 1986521] Re: ssh client spins if output fd closed

2022-12-12 Thread Michael Rutter

I can confirm that the updated package works in that the real use case
which triggered the original bug (involving a script setting up an ssh
tunnel) no longer does. Sorry for the delay in responding -- things have
been busy, so I have also not tested the updated package much.

I have not updated the verification status as the VM on which I tested
this is not entirely up-to-date and standard. I hope that someone is in
a better position than I to test more thoroughly.

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

Title:
  ssh client spins if output fd closed

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

Bug description:
  [Impact]
  In certain edge cases where the terminal goes away while an ssh process is 
running, ssh can be left consuming 100% CPU.  This increases processing costs 
for cloud users and wastes energy.  While this is an uncommon error, googling 
indicates many people have run into it in several different ways.   It seems 
important to get this fixed in stable releases.

  This is a regression in jammy presumably due to change from select()
  to poll() (see OpennSSH 8.9 Release Announcement [1] ), fixed by
  upstream commit d6556de1db0822c76ba2745cf5c097d9472adf7c "upstream:
  fix poll() spin when a channel's output fd closes..." [2].

  1: https://lwn.net/Articles/885886/
  2. 
https://github.com/openssh/openssh-portable/commit/d6556de1db0822c76ba2745cf5c097d9472adf7c

  [Test Case]
  $ lxc launch ubuntu-daily:jammy ssh-cpu
  $ lxc shell ssh-cpu

  # passwd -d root
  # ssh-keygen -t rsa -N '' -f /root/.ssh/id_rsa

  # cat << EOF >>/etc/ssh/ssh_config
  StrictHostKeyChecking accept-new
  EOF

  # sed -ri 's/^PasswordAuthentication/#PasswordAuthentication/' 
/etc/ssh/sshd_config
  # cat << EOF >>/etc/ssh/sshd_config
  PermitRootLogin yes
  PubkeyAuthentication yes
  PermitEmptyPasswords yes
  PasswordAuthentication yes
  ChallengeResponseAuthentication no
  UsePAM no
  EOF

  # systemctl restart sshd

  # ssh localhost 2> >({exec 1>&2})

  You can shell into the container from a second terminal and use "htop"
  to verify that ssh is using 100% of one of the CPU cores:

  $ lxc shell ssh-cpu
  # htop

  This should show one CPU pegged at 100% due to the 'ssh localhost'
  process

  Next, return to the first terminal, exit out of the sub-ssh session and
  install the fix:

  # logout
  # add-apt-repository -yus ppa:bryce/openssh-sru-lp1986521
  # apt-get full-upgrade -y

  Now repeat the test in the first terminal window, while viewing htop in
  the second terminal:

  # ssh localhost 2> >({exec 1>&2})

  [Where Problems Could Occur]

  While the patch in question is well tested upstream, it has a
  relatively high line count and as such is difficult to assure
  correctness by visual code checking.  However, it's not clear that the
  line count could be significantly reduced without risking loss of
  correctness.  Thus this relies more on testing to assure robustness,
  than on code review.

  The code involves polling behavior, so issues to watch for would more
  likely involve process handling, i.e. problems with socket polling.

  Beyond that, the usual generic issues to watch for - build issues,
  dependency issues during build or on upgrade, and service restarting.

  [Original Report]
  The OpenSSH package 8.9p1 as shipped with U22.04 (8.9p1-3) suffers from the 
bug described at
  https://bugzilla.mindrot.org/show_bug.cgi?id=3411 and 
https://bugzilla.mindrot.org/show_bug.cgi?id=3405

  A command such as "xterm -e 'ssh -f remote.host sleep 60'" will pop up
  an xterm, ask for whatever authentication is needed, close the xterm,
  and leave the ssh client spinning consuming CPU time for 60 seconds
  before it exits. It should leave the ssh client idle for 60 seconds.
  Many uses of ssh to launch graphical applications will be caught by
  this bug.

  This is fixed in OpenSSH 9.0p1 as the first bugfix listed in its
  release notes at https://www.openssh.com/txt/release-9.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1986521/+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 615773] Re: flash-kernel fails to handle raw boot partitons on eMMC

2022-12-08 Thread Michael Opdenacker

Marking as invalid, too old


** Changed in: flash-kernel (Ubuntu)
   Status: Confirmed => 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/615773

Title:
  flash-kernel fails to handle raw boot partitons on eMMC

Status in Release Notes for Ubuntu:
  Invalid
Status in flash-kernel package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in flash-kernel source package in Maverick:
  Won't Fix
Status in initramfs-tools source package in Maverick:
  Invalid
Status in flash-kernel source package in Natty:
  Won't Fix
Status in initramfs-tools source package in Natty:
  Invalid
Status in flash-kernel source package in Oneiric:
  Won't Fix
Status in initramfs-tools source package in Oneiric:
  Won't Fix

Bug description:
  Binary package hint: initramfs-tools

  The postinst trigger calls update-initramfs which fails on "Cannot find mtd 
partition 'Kernel'"
  Configuration: eMMC memory, so no NAND MTD partition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/615773/+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 1998001] Re: Missing tests from libdrm-tests

2022-12-06 Thread Michael Vogt

@Brian Once the archive is frozen this is not entirely trivial anymore
as the command-not-found indexfile is stored in the now frozen archive
mirror.

It seems the easiest way to fix is:
* uploading a higher version in the -updates pocket should fix the problem 
automatically, the database code 
(CommandNotFound/db/creator.py:_parse_single_commands_file()) should discard 
the content of older versions. There are some useful ways to control what 
commands are visible from the pkg, you could use "X-Cnf-Ignore-Commands: 
kms-universal-planes" on the "libdrm-tests" binary package stanza (see 
what-is-python for an example)

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

Title:
  Missing tests from libdrm-tests

Status in command-not-found:
  New
Status in command-not-found package in Ubuntu:
  Confirmed
Status in libdrm package in Ubuntu:
  Invalid

Bug description:
  It is advertised by the OS that kms-universal-planes can be installed
  via libdrm-tests but this is false:

  $ kms-universal-planes
  Command 'kms-universal-planes' not found, but can be installed with:
  sudo apt install libdrm-tests

  $ sudo apt install libdrm-tests
  [sudo] password for stolk: 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following NEW packages will be installed:
libdrm-tests
  0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
  Need to get 47.5 kB of archives.
  After this operation, 193 kB of additional disk space will be used.
  Get:1 http://ca.archive.ubuntu.com/ubuntu kinetic/universe amd64 libdrm-tests 
amd64 2.4.113-2 [47.5 kB]
  Fetched 47.5 kB in 0s (142 kB/s)  
  Selecting previously unselected package libdrm-tests.
  (Reading database ... 308766 files and directories currently installed.)
  Preparing to unpack .../libdrm-tests_2.4.113-2_amd64.deb ...
  Unpacking libdrm-tests (2.4.113-2) ...
  Setting up libdrm-tests (2.4.113-2) ...

  $ kms-universal-planes
  Command 'kms-universal-planes' not found, but can be installed with:
  sudo apt install libdrm-tests

  OS: Ubuntu 22.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/command-not-found/+bug/1998001/+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 1994146] Re: [SRU] apparmor - Focal, Jammy

2022-12-05 Thread Michael Vogt

Fwiw, the code has landed in the upstream git repository in
https://gitlab.com/apparmor/apparmor/-/merge_requests/858

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

Title:
  [SRU] apparmor - Focal, Jammy

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Focal:
  In Progress
Status in apparmor source package in Jammy:
  Incomplete

Bug description:
  [ Impact ]

  This is a SRU proposal for apparmor in Focal and Jammy.
  For focal, we want to SRU fixes for Bug 1964636 which introduces the
  capability upstream patches. We are also fixing Bug 1728130 and
  Bug 1993353 which are introducing full backport of abi from
  apparmor-3.0 and support for POSIX message queue rules, which are both
  a request from Honeywell.

  Note that specifically for message queue rules, we are overriding the
  abi behavior.
  Message queue mediation is not a part of the 2.13 abi we are
  pinning. Honeywell has a kernel that has message queue mediation,
  but their policy does not contain an abi specified, so when we pin the
  abi for a kernel that does not mediate message queue, it will break
  Honeywell's AppArmor policies. So we are making an exception: when abi
  is not specified in the policy, and the policy contain mqueue rules,
  we are enforcing mqueue rules. When the policy does not contain mqueue
  rules, then they are not being enforced. This is so we do not break
  Honeywell policies and we also are not breaking policies that were
  developed when there was no mqueue or abi support.

  For jammy, we are SRUing fixes for Bug 1993353 which adds message
  queue rules support. 

  
  [ Test Plan ]

  This has been extensively tested by using QA Regression Tests[1] for
  AppArmor. All tests have passed and demonstrated AppArmor to be
  working as expected. We are also adding regression tests for message
  queue rules[2] which guarantees it is working as expected.

  [1] 
https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py
  [2] https://gitlab.com/apparmor/apparmor/-/merge_requests/858

  [ Where problems could occur ]

  The message queue rules support could cause issues for AppArmor
  policies that were developed before there was support for mqueues,
  that's why we are also backporting abi support and pinning the abi on
  parser.conf on focal. Jammy already has the abi pinned for a kernel
  that does not have support for mqueue mediation.

  [ Other Info ]

  The patches for both focal and jammy can be found at:
  https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1994146/+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 1966418]

2022-12-03 Thread Michael Catanzaro

Is this still a problem?

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

Title:
  [jammy regression] webkit apps do not display content (yelp, epiphany,
  gnome-online-accounts etc)

Status in Gnome DevHelp:
  Invalid
Status in Mesa:
  Fix Released
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Invalid

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/devhelp/+bug/1966418/+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 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s

2022-11-11 Thread Michael Vogt

** Changed in: snapd
   Status: Fix Committed => Fix Released

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

Title:
  snapd fails to autopkgtest on mksquashfs, which is looking for
  libgcc_s

Status in snapd:
  Fix Released
Status in openssh package in Ubuntu:
  New
Status in squashfs-tools package in Ubuntu:
  New

Bug description:
  During current snapd autopkgtest, a failure can be observed:

  https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/amd64/s/snapd/20210907_175258_5451b@/log.gz

  
  error: cannot pack 
"/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox":
 mksquashfs call failed: 
  -
  libgcc_s.so.1 must be installed for pthread_cancel to work
  Parallel mksquashfs: Using 1 processor
  Creating 4.0 filesystem on 
/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox/test-snapd-sandbox_1.0_all.snap,
 block size 131072.
  -
  error: cannot read snap file: "/var/lib/snapd/snaps/.local-install-136125945"
 is not a snap or snapdir

  
  I traced the underlying call to the following:
  "/snap/snapd/current/lib/x86_64-linux-gnu/ld-2.23.so" "--library-path"
  
"/snap/snapd/current/usr/local/lib:/snap/snapd/current/lib/x86_64-linux-gnu:/snap/snapd/current/usr/lib/x86_64-linux-gnu"
  "/snap/snapd/current/usr/bin/mksquashfs" asdf asdf.squashfs

  (the real call has more arguments, this is a simplified version that
  produces the failure)

  To observe this, one can create a VM based a cloud image from
  https://cloud-images.ubuntu.com/impish/current, then run the above command in
  the resulting environment.
  Doing so will test against snapd v2.51.4 (12883).
  Retesting with edge 2.52+git635.gada2d87 (13323) produces an equivalent 
result.

  Running a more bland `/snap/snapd/current/usr/bin/mksquashfs asdf
  asdf.squashfs` without messing with library paths has mksquashfs behaving as
  expected.  Also, getting a v2.51.3 snapd seems to behave itself.  Updating 
from
  2.51.3 -> 2.51.4 also works.

  One can see a passing mksquashfs by taking libgcc_s.so.1 from hirsute
  and placing it in the library path for the above call.

  In the working scenario, it appears that libgcc_s is being obtained
  from outside of /snap (and also libz).  In the failing scenario, this
  external copy of libgcc_s is not being loaded (per gdb info sharedlibrary),
  but libz still is.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1943077/+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 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04

2022-10-20 Thread Michael Timblin

The comment by @fru1z (#32) worked for me on Ubuntu 22.04 with
GlobalProtect 5.3.1-36. Be sure to comment out the line mentioned in the
instructions. Adding the "Options = UnsafeLegacyRenegotiation" line by
itself did not work for me.

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

Title:
  SSL handshake failed - VPN SSL broken in 22.04

Status in openssl package in Ubuntu:
  Expired

Bug description:
  I'm trying to connect with global protect VPN but fails at login with:

  SSL handshake failed
  Failed to load URL https://...
  QtNetwork Error 6

  Another VPN client does work but the rdp connection to a remote server fails 
with:

  transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session impish
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+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 1993084] Re: libkrb5-dev: dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

I think we're going to need more output that than to help you debug
this.

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

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

Title:
  libkrb5-dev:  dpkg-deb: error: paste subprocess was killed by signal
  (Broken pipe)

Status in krb5 package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04.1 LTS:  sudo apt install libkrb5-dev

  Installation fails with this message:

  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  I had tried to install this package as a dependency of building Wine
  from source:

  configure: libkrb5 32-bit/64-bit development files not found (or too
  old), Kerberos won't be supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1993084/+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 1993008] Re: ftbfs: E: fontconfig: alien-tag fc-cache-used-in-maintainer-script

lintian errors do not count as a build failure. You could file this as a
bug in Debian if you like -- we'll pick up the fix from there in due
course.

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

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

Title:
  ftbfs: E: fontconfig: alien-tag fc-cache-used-in-maintainer-script

Status in fontconfig package in Ubuntu:
  Invalid

Bug description:
  When trying to build from source using

  debuild -us -uc -b

  the result errors out with

  Now running lintian fontconfig_2.13.1-4.4ubuntu1_amd64.changes ...
  E: fontconfig: alien-tag fc-cache-used-in-maintainer-script 
[usr/share/lintian/overrides/fontconfig:1]
  W: libfontconfig-doc: bad-whatis-entry 
[usr/share/man/man3/FcPatternIterNext.3.gz]

  from:
  
https://www.mit.edu/afs.new/sipb/project/debathena/lintian/www/tags/fc-cache-used-in-maintainer-script.html

  "This script apparently runs fc-cache. Updating of the fontconfig cache files 
is now handled automatically by triggers, so running fc-cache from maintainer 
scripts is no longer necessary."

   
  ubuntu: kinetic kudu

  libfontconfig1-dev:
Installed: 2.13.1-4.4ubuntu1
Candidate: 2.13.1-4.4ubuntu1
Version table:
   *** 2.13.1-4.4ubuntu1 500
  500 http://ubuntu.hysing.is/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libfontconfig-dev 2.13.1-4.4ubuntu1
  Uname: Linux 6.0.1-gnulibre x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Oct 14 21:07:42 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to kinetic on 2022-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1993008/+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 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

** Tags added: foundations-triage-discuss

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

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1992979/+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 1992947] Re: gdb fails in Ubuntu-22.04

There is a new version of gdb in jammy-proposed that might help. Can you
try that? (some pointers on how to do this at
https://wiki.ubuntu.com/Testing/EnableProposed)

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

Title:
  gdb fails in Ubuntu-22.04

Status in gdb package in Ubuntu:
  New

Bug description:
  In Jammy 5.15.0-1014 when i try to debug an application with gdb got
  below error,

  Log:
  root@kria:/home/ubuntu/swetha_bins/v2xpfm# gdb threshold
  Could not find platform independent libraries 
  Could not find platform dependent libraries 
  Consider setting $PYTHONHOME to [:]
  Python path configuration:
PYTHONHOME = (not set)
PYTHONPATH = (not set)
program name = '/usr/bin/python'
isolated = 0
environment = 1
user site = 1
import site = 1
sys._base_executable = '/usr/bin/python'
sys.base_prefix = '/usr'
sys.base_exec_prefix = '/usr'
sys.platlibdir = 'lib'
sys.executable = '/usr/bin/python'
sys.prefix = '/usr'
sys.exec_prefix = '/usr'
sys.path = [
  '/usr/lib/python39.zip',
  '/usr/lib/python3.9',
  '/usr/lib/lib-dynload',
]
  Fatal Python error: init_fs_encoding: failed to get the Python codec of the 
filesystem encoding
  Python runtime state: core initialized
  ModuleNotFoundError: No module named 'encodings'

  Current thread 0xa057f020 (most recent call first):
  
  root@kria:/home/ubuntu/swetha_bins/v2xpfm#
  root@kria:/home/ubuntu/swetha_bins/v2xpfm#
  root@kria:/home/ubuntu/swetha_bins/v2xpfm# uname -a
  Linux kria 5.15.0-1014-xilinx-zynqmp #15-Ubuntu SMP Tue Aug 30 07:56:28 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux
  root@kria:/home/ubuntu/swetha_bins/v2xpfm#
  root@kria:/home/ubuntu/swetha_bins/v2xpfm#
  root@kria:/home/ubuntu/swetha_bins/v2xpfm# file threshold
  threshold: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (GNU/Linux), 
dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, 
BuildID[sha1]=ae073c5ee47a3663ef3a06861c5df9bf62147ecd, for GNU/Linux 3.14.0, 
with debug_info, not stripped
  root@kria:/home/ubuntu/swetha_bins/v2xpfm#
  root@kria:/home/ubuntu/swetha_bins/v2xpfm#
  root@kria:/home/ubuntu/swetha_bins/v2xpfm#

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

I think your /boot ran out of space during the upgrade.

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

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

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  it just said it want to report a problem

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Oct 13 07:00:41 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-01-09 (641 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-50-generic 5.15.0-50.56~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992727/+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 1689381] Re: FTBFS cp: cannot stat 'doc/fontconfig-user.html'

fontconfig 2.13.1-4.4ubuntu1 built successfully for me in a kinetic
sbuild so I think this can be closed.

** Changed in: fontconfig (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 fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1689381

Title:
  FTBFS cp: cannot stat 'doc/fontconfig-user.html'

Status in fontconfig package in Ubuntu:
  Fix Released

Bug description:
  while attempting to build with debuild:

  debuild -us -uc -b
  ...
  Adding cdbs dependencies to debian/libfontconfig1-dbg.substvars
  dh_installdirs -plibfontconfig1-dbg \

  dh_installdocs -pfontconfig ./README ./NEWS ./AUTHORS
  cp: cannot stat 'doc/fontconfig-user.html': No such file or directory
  dh_installdocs: cp --reflink=auto -a doc/fontconfig-user.html 
debian/fontconfig/usr/share/doc/fontconfig returned exit code 1
  /usr/share/cdbs/1/rules/debhelper.mk:235: recipe for target 
'binary-install/fontconfig' failed
  make: *** [binary-install/fontconfig] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
2
  debuild: fatal error at line 1116:
  dpkg-buildpackage -rfakeroot -us -uc -b failed
  z@aisha:~/fontconfig/fontconfig-2.11.94/debian$ 

  ubuntu: 17.10 artful
  libfontconfig1-dev:  2.11.94-0ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libfontconfig1-dev (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon May  8 19:23:10 2017
  InstallationDate: Installed on 2016-05-07 (366 days ago)
  InstallationMedia:
   
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to artful on 2017-05-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1689381/+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 1959832] Re: new version available upstream: 11.2

Kinetic has 12.1?

** Changed in: gdb (Ubuntu)
   Status: Fix Committed => Invalid

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

Title:
  new version available upstream: 11.2

Status in gdb package in Ubuntu:
  Invalid

Bug description:
  Release 11.2 of GDB, the GNU Debugger, is now available

  You can download GDB from the GNU FTP server in the directory:

  ftp://ftp.gnu.org/gnu/gdb

  GDB announcement https://www.sourceware.org/gdb/download/ANNOUNCEMENT

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdb 9.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  2 10:39:47 2022
  InstallationDate: Installed on 2017-04-18 (1750 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gdb
  UpgradeStatus: Upgraded to focal on 2020-04-25 (648 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1959832/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

2022-10-16 Thread Michael Hudson-Doyle

I think the issue here is that snaps (with cgroupsv2) require a systemd
user session and some desktop environments do not set this up? It's not
clear to me what needs to change here -- should snapd be more tolerant
of this situation or should the other desktop environments change to set
the necessary environment variables?

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

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

Title:
  Can't run snaps: .slice/session-1.scope is not a snap cgroup

Status in X2Go:
  New
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete
Status in x2goserver package in Ubuntu:
  Confirmed
Status in snapd package in Debian:
  New

Bug description:
  I just upgraded from hirsute to impish using do-release-upgrade. On
  the upgraded system, I can't run either firefox or chromium (both of
  which worked fine under hirsute). Both fail with:

  /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where
  NNN is my uid

  With firefox, I was able to fix the problem with:

  snap remove --purge firefox
  apt purge firefox
  apt install firefox

  Now firefox works. But I tried the same thing substituting chromium-
  browser for firefox, and it didn't help: chromium fails with the same
  error message.

  I guess there must be something left over from the hirsute version of
  snapd that isn't getting noticed or cleared by the impish version?

  Someone suggested this might be related to bug 1850667, but that bug
  is marked fixed as of a couple months ago, and I just did this upgrade
  today. Also, it doesn't mention the error message I'm seeing.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: snapd 2.53+21.10ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov 18 18:12:45 2021
  InstallationDate: Installed on 2020-04-29 (568 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/x2go/+bug/1951491/+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 1269840] Re: ubuntu-bug ubuntu-bug doesn't work

2022-10-16 Thread Michael Hudson-Doyle

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

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

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

Title:
  ubuntu-bug ubuntu-bug doesn't work

Status in apport package in Ubuntu:
  Triaged

Bug description:
  ubuntu-bug doesn't make program lookup when package lookup failed.
  This is inconvenient for users, who don't know about `which` command.
  Is it possible to automate lookup and continue search until something
  matches?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apport 2.12.5-0ubuntu2.2
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  CrashReports:
   640:1000:122:1423125:2014-01-09 20:22:25.104739665 +0300:2014-01-09 
20:22:26.104739665 
+0300:/var/crash/_usr_lib_i386-linux-gnu_bamf_bamfdaemon.1000.crash
   640:1000:122:157297300:2014-01-09 20:56:44.036795854 +0300:2014-01-09 
20:56:45.036795854 +0300:/var/crash/_usr_bin_compiz.1000.crash
   640:0:122:4884804:2014-01-10 13:10:06.891414880 +0300:2014-01-10 
13:10:07.891414880 +0300:/var/crash/_usr_bin_Xorg.0.crash
  Date: Thu Jan 16 18:10:59 2014
  InstallationDate: Installed on 2012-03-12 (675 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (87 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1269840/+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 1992688] Re: firefox deb not installed

2022-10-16 Thread Michael Hudson-Doyle

This just needs to be backported to Jammy now?

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

Title:
  firefox deb not installed

Status in firefox package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in firefox source package in Jammy:
  New
Status in ubuntu-meta source package in Jammy:
  Triaged

Bug description:
  Bug 1964036 leads me to believe that the firefox deb provides some
  important functionality (the firefox favourite icon in the gnome shell
  dock) but there is nothing that would require the deb to be installed
  (it is not seeded nor has an rdep) and the package description
  indicates that it can be safely removed. Is there some important
  functionality that it provides?

  ProblemType: BugDistroRelease: Ubuntu 22.10
  Package: ubuntu-release-upgrader-core 1:22.10.8
  ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 12 11:30:46 2022
  InstallationDate: Installed on 2022-04-27 (167 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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 1993025] Re: systemd-journald crashed with SIGABRT in journal_file_move_to_object()

2022-10-15 Thread Michael De La Rue

this may be an old bug -

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1436168
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1703898

it happened under definite memory pressure - oomkiller had been active.
unfortunately apport doesn't seem to support cut and paste so I can't
easily get more of the data from there.

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

Title:
  systemd-journald crashed with SIGABRT in journal_file_move_to_object()

Status in systemd package in Ubuntu:
  New

Bug description:
  Directly after a resume from suspend on Ubuntu 22.04 LTS I got an
  crash report with the message

  systemd-journald crashed with SIGABRT in journal_file_move_to_object()

  I'm too concerned about the private information included in, for
  example, the coredump, to submit so I'm making this separate bug
  report. I have preserved the bug file in case it turns out to be
  important.

  ProblemType: Crash
  Architecture: amd64
  Date: Sat Oct 15 09:11:42 2022
  DistroRelease: Ubuntu 22.04
  ExecutablePath: /usr/lib/systemd/systemd-journald
  ExecutableTimestamp: 1662749236
  ProcCmdline: /lib/systemd/systemd-journald
  ProcCwd: /
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1993025/+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 1993025] [NEW] systemd-journald crashed with SIGABRT in journal_file_move_to_object()

2022-10-15 Thread Michael De La Rue

Public bug reported:

Directly after a resume from suspend on Ubuntu 22.04 LTS I got an crash
report with the message

systemd-journald crashed with SIGABRT in journal_file_move_to_object()

I'm too concerned about the private information included in, for
example, the coredump, to submit so I'm making this separate bug report.
I have preserved the bug file in case it turns out to be important.

ProblemType: Crash
Architecture: amd64
Date: Sat Oct 15 09:11:42 2022
DistroRelease: Ubuntu 22.04
ExecutablePath: /usr/lib/systemd/systemd-journald
ExecutableTimestamp: 1662749236
ProcCmdline: /lib/systemd/systemd-journald
ProcCwd: /
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)

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

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

Title:
  systemd-journald crashed with SIGABRT in journal_file_move_to_object()

Status in systemd package in Ubuntu:
  New

Bug description:
  Directly after a resume from suspend on Ubuntu 22.04 LTS I got an
  crash report with the message

  systemd-journald crashed with SIGABRT in journal_file_move_to_object()

  I'm too concerned about the private information included in, for
  example, the coredump, to submit so I'm making this separate bug
  report. I have preserved the bug file in case it turns out to be
  important.

  ProblemType: Crash
  Architecture: amd64
  Date: Sat Oct 15 09:11:42 2022
  DistroRelease: Ubuntu 22.04
  ExecutablePath: /usr/lib/systemd/systemd-journald
  ExecutableTimestamp: 1662749236
  ProcCmdline: /lib/systemd/systemd-journald
  ProcCwd: /
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1993025/+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 1990729] Re: gdb crashes when run from VSCode

2022-09-27 Thread Michael Hudson-Doyle

Oh yikes I'm sorry for giving you incomplete advice. These are the
instructions to follow: https://wiki.ubuntu.com/Testing/EnableProposed
-- no building from source required!

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

Title:
  gdb crashes when run from VSCode

Status in gdb package in Ubuntu:
  New

Bug description:
  I had no pre-existing breakpoints in VSCode, then added a breakpoint,
  and used F5 to run the debugger to the one breakpoint.  It crashed
  before it got there.  This is a C++ executable compiled for debugging
  using CMAKE.  I can successfully debug the program using the TUI mode
  of gdb, so I think the problem likes in the vscode interface to gdb.

  /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: 
Assertion `arg->contents != nullptr' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) [answered Y; input not from terminal]
  /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: 
Assertion `arg->contents != nullptr' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) [answered Y; input not from terminal]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdb 12.0.90-0ubuntu1
  ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21
  Uname: Linux 5.14.0-1051-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 11:10:11 2022
  InstallationDate: Installed on 2022-02-15 (221 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gdb
  UpgradeStatus: Upgraded to jammy on 2022-09-06 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1990729/+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 1990729] Re: gdb crashes when run from VSCode

2022-09-26 Thread Michael Hudson-Doyle

Could you try the gdb from proposed? I think it should help.

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

Title:
  gdb crashes when run from VSCode

Status in gdb package in Ubuntu:
  New

Bug description:
  I had no pre-existing breakpoints in VSCode, then added a breakpoint,
  and used F5 to run the debugger to the one breakpoint.  It crashed
  before it got there.  This is a C++ executable compiled for debugging
  using CMAKE.  I can successfully debug the program using the TUI mode
  of gdb, so I think the problem likes in the vscode interface to gdb.

  /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: 
Assertion `arg->contents != nullptr' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) [answered Y; input not from terminal]
  /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: 
Assertion `arg->contents != nullptr' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) [answered Y; input not from terminal]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdb 12.0.90-0ubuntu1
  ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21
  Uname: Linux 5.14.0-1051-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 11:10:11 2022
  InstallationDate: Installed on 2022-02-15 (221 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gdb
  UpgradeStatus: Upgraded to jammy on 2022-09-06 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1990729/+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 1990659] [NEW] Systemd component broken following update

2022-09-23 Thread Michael R

Public bug reported:

Following update to the latest package today (245.4-4ubuntu3.18) on
focal, systemd-resolved and systemd-timesyncd (at least) can't start

Ubuntu 20.04
x86_64
kernel 5.4.0-122-generic

logs:

Sep 23 10:48:53 systemd[1]: Starting Network Name Resolution...
Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed to set up 
mount namespacing: /run/systemd/unit-root/dev: Invalid argument
Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed at step 
NAMESPACE spawning /lib/systemd/systemd-resolved: Invalid argument
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Main process exited, 
code=exited, status=226/NAMESPACE
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result 
'exit-code'.
Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution.
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Scheduled restart job, 
restart counter is at 5.
Sep 23 10:48:53 systemd[1]: Stopped Network Name Resolution.
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Start request repeated 
too quickly.
Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result 
'exit-code'.
Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution.

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

** Description changed:

  Following update to the latest package today (245.4-4ubuntu3.18) on
  focal, systemd-resolved and systemd-timesyncd can't start
  
  Ubuntu 20.04
  x86_64
  kernel 5.4.0-122-generic
  
  logs:
  
  Sep 23 10:48:53 systemd[1]: Starting Network Name Resolution...
  Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed to set up 
mount namespacing: /run/systemd/unit-root/dev: Invalid argument
  Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed at step 
NAMESPACE spawning /lib/systemd/systemd-resolved: Invalid argument
  Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Main process exited, 
code=exited, status=226/NAMESPACE
  Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result 
'exit-code'.
  Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution.
- Sep 23 10:48:53 curie systemd[1]: systemd-resolved.service: Scheduled restart 
job, restart counter is at 5.
+ Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Scheduled restart job, 
restart counter is at 5.
  Sep 23 10:48:53 systemd[1]: Stopped Network Name Resolution.
  Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Start request repeated 
too quickly.
  Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result 
'exit-code'.
  Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution.

** Description changed:

  Following update to the latest package today (245.4-4ubuntu3.18) on
- focal, systemd-resolved and systemd-timesyncd can't start
+ focal, systemd-resolved and systemd-timesyncd (at least) can't start
  
  Ubuntu 20.04
  x86_64
  kernel 5.4.0-122-generic
  
  logs:
  
  Sep 23 10:48:53 systemd[1]: Starting Network Name Resolution...
  Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed to set up 
mount namespacing: /run/systemd/unit-root/dev: Invalid argument
  Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed at step 
NAMESPACE spawning /lib/systemd/systemd-resolved: Invalid argument
  Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Main process exited, 
code=exited, status=226/NAMESPACE
  Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result 
'exit-code'.
  Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution.
  Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Scheduled restart job, 
restart counter is at 5.
  Sep 23 10:48:53 systemd[1]: Stopped Network Name Resolution.
  Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Start request repeated 
too quickly.
  Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result 
'exit-code'.
  Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution.

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

Title:
  Systemd component broken following update

Status in systemd package in Ubuntu:
  New

Bug description:
  Following update to the latest package today (245.4-4ubuntu3.18) on
  focal, systemd-resolved and systemd-timesyncd (at least) can't start

  Ubuntu 20.04
  x86_64
  kernel 5.4.0-122-generic

  logs:

  Sep 23 10:48:53 systemd[1]: Starting Network Name Resolution...
  Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed to set up 
mount namespacing: /run/systemd/unit-root/dev: Invalid argument
  Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed at step 
NAMESPACE spawning /lib/systemd/systemd-resolved: Invalid argument
  Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Main process exited, 
code=exited,

[Touch-packages] [Bug 1990312] Re: Can't change desktop language in Ubuntu 22.04

2022-09-20 Thread Michael Opdenacker

Set the package to "ubuntu-meta" containing "ubuntu-desktop"

** Package changed: ubuntu => ubuntu-meta (Ubuntu)

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

Title:
  Can't change desktop language in Ubuntu 22.04

Status in ubuntu-meta package in Ubuntu:
  Incomplete

Bug description:
  I initially installed Ubuntu 22.04 with the English language.
  Now, I'd like to use the Ubuntu desktop in the German language.
  I believe I've done everything needed. I rebooted of course. The login screen 
is now in German, but my user desktop is still in English, except the calendar 
showing the date.

  See the attached screenshot.

  Here is the output of the "locale" command:

  LANG=de_DE.UTF-8
  LANGUAGE=en
  LC_CTYPE=en_US.UTF-8
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE=en_US.UTF-8
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES=en_US.UTF-8
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  Am I the only one having this issue?
  Thanks in advance
  Michael

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990312/+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 1989973] Re: focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it uninstallable without explicit version

** Tags added: foundations-todo

** Changed in: vim (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it
  uninstallable without explicit version

Status in vim package in Ubuntu:
  New

Bug description:
  In a fresh focal install/container, vim is uninstallable because
  version 2:8.1.2269-1ubuntu5.8 failed to build for vim, but the `all`
  packages did succeed.

  ```
  $ docker run -ti --rm arm32v7/ubuntu:focal bash -c 'apt update && apt install 
vim-tiny'
  WARNING: The requested image's platform (linux/arm/v7) does not match the 
detected host platform (linux/amd64) and no specific platform was requested
  Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB]
  Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB]
  Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB]
  Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB]
  Get:5 http://ports.ubuntu.com/ubuntu-ports focal/main armhf Packages [1227 kB]
  Get:6 http://ports.ubuntu.com/ubuntu-ports focal/universe armhf Packages 
[10.9 MB]
  Get:7 http://ports.ubuntu.com/ubuntu-ports focal/multiverse armhf Packages 
[141 kB]
  Get:8 http://ports.ubuntu.com/ubuntu-ports focal/restricted armhf Packages 
[10.8 kB]
  Get:9 http://ports.ubuntu.com/ubuntu-ports focal-updates/restricted armhf 
Packages [16.9 kB]
  Get:10 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe armhf 
Packages [996 kB]
  Get:11 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse armhf 
Packages [9626 B]
  Get:12 http://ports.ubuntu.com/ubuntu-ports focal-updates/main armhf Packages 
[1400 kB]
  Get:13 http://ports.ubuntu.com/ubuntu-ports focal-backports/universe armhf 
Packages [27.4 kB]
  Get:14 http://ports.ubuntu.com/ubuntu-ports focal-backports/main armhf 
Packages [54.7 kB]
  Get:15 http://ports.ubuntu.com/ubuntu-ports focal-security/main armhf 
Packages [1032 kB]
  Get:16 http://ports.ubuntu.com/ubuntu-ports focal-security/multiverse armhf 
Packages [4730 B]
  Get:17 http://ports.ubuntu.com/ubuntu-ports focal-security/universe armhf 
Packages [698 kB]
  Get:18 http://ports.ubuntu.com/ubuntu-ports focal-security/restricted armhf 
Packages [16.6 kB]
  Fetched 17.2 MB in 8s (2274 kB/s)
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  23 packages can be upgraded. Run 'apt list --upgradable' to see them.
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   vim-tiny : Depends: vim-common (= 2:8.1.2269-1ubuntu5.7) but 
2:8.1.2269-1ubuntu5.8 is to be installed
  E: Unable to correct problems, you have held broken packages.
  ```

  Seems to be due to
  https://launchpad.net/ubuntu/+source/vim/2:8.1.2269-1ubuntu5.8/+build/24478851

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1989973/+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 1989973] Re: focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it uninstallable without explicit version

Argh that shouldn't have happened. I've retried both the builds (it
looks like they failed because of infrastructure issues), hopefully that
will fix it.

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

Title:
  focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it
  uninstallable without explicit version

Status in vim package in Ubuntu:
  New

Bug description:
  In a fresh focal install/container, vim is uninstallable because
  version 2:8.1.2269-1ubuntu5.8 failed to build for vim, but the `all`
  packages did succeed.

  ```
  $ docker run -ti --rm arm32v7/ubuntu:focal bash -c 'apt update && apt install 
vim-tiny'
  WARNING: The requested image's platform (linux/arm/v7) does not match the 
detected host platform (linux/amd64) and no specific platform was requested
  Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB]
  Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB]
  Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB]
  Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB]
  Get:5 http://ports.ubuntu.com/ubuntu-ports focal/main armhf Packages [1227 kB]
  Get:6 http://ports.ubuntu.com/ubuntu-ports focal/universe armhf Packages 
[10.9 MB]
  Get:7 http://ports.ubuntu.com/ubuntu-ports focal/multiverse armhf Packages 
[141 kB]
  Get:8 http://ports.ubuntu.com/ubuntu-ports focal/restricted armhf Packages 
[10.8 kB]
  Get:9 http://ports.ubuntu.com/ubuntu-ports focal-updates/restricted armhf 
Packages [16.9 kB]
  Get:10 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe armhf 
Packages [996 kB]
  Get:11 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse armhf 
Packages [9626 B]
  Get:12 http://ports.ubuntu.com/ubuntu-ports focal-updates/main armhf Packages 
[1400 kB]
  Get:13 http://ports.ubuntu.com/ubuntu-ports focal-backports/universe armhf 
Packages [27.4 kB]
  Get:14 http://ports.ubuntu.com/ubuntu-ports focal-backports/main armhf 
Packages [54.7 kB]
  Get:15 http://ports.ubuntu.com/ubuntu-ports focal-security/main armhf 
Packages [1032 kB]
  Get:16 http://ports.ubuntu.com/ubuntu-ports focal-security/multiverse armhf 
Packages [4730 B]
  Get:17 http://ports.ubuntu.com/ubuntu-ports focal-security/universe armhf 
Packages [698 kB]
  Get:18 http://ports.ubuntu.com/ubuntu-ports focal-security/restricted armhf 
Packages [16.6 kB]
  Fetched 17.2 MB in 8s (2274 kB/s)
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  23 packages can be upgraded. Run 'apt list --upgradable' to see them.
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   vim-tiny : Depends: vim-common (= 2:8.1.2269-1ubuntu5.7) but 
2:8.1.2269-1ubuntu5.8 is to be installed
  E: Unable to correct problems, you have held broken packages.
  ```

  Seems to be due to
  https://launchpad.net/ubuntu/+source/vim/2:8.1.2269-1ubuntu5.8/+build/24478851

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1989973/+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 1989292] Re: package openssh-server 1:8.9p1-3 failed to install/upgrade: »installiertes openssh-server-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zur

It's unclear to me how the comment about the kernel panic and the
openssh upgrade failing are related to me, I'm afraid.

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

Title:
  package openssh-server 1:8.9p1-3 failed to install/upgrade:
  »installiertes openssh-server-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 1 zurück

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  when starting the system it shows the following:
  [ 0.578926]--- [end Kernel panic - not syncing: VFS: Unable to mount root fs 
on unknown-block (0,0) ]---

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: openssh-server 1:8.9p1-3
  ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195
  Uname: Linux 5.4.0-124-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Sep  8 13:40:54 2022
  ErrorMessage: »installiertes openssh-server-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: openssh
  Title: package openssh-server 1:8.9p1-3 failed to install/upgrade: 
»installiertes openssh-server-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to jammy on 2022-09-08 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1989292/+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 1971409] Re: value_copy: Assertion `arg->contents != nullptr' failed.