[Touch-packages] [Bug 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gnome-shell (Ubuntu)
   Status: Opinion => In Progress

** Changed in: gnome-shell (Ubuntu)
Milestone: None => ubuntu-22.10

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

Title:
  Screen freeze before the login screen on VirtualBox (if the third
  party software option was selected)

Status in gnome-shell package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in libxcb package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  1. Install *without* the third-party option.

  2. sudo apt install ubuntu-restricted-extras

  3. sudo apt remove gstreamer1.0-vaapi

  
  [ Original Description ]

  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   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/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988488/+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 1586538] Re: certutils from libnss3-tools - man page contradicts Mozilla's

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1277637.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-06-02T19:00:13+00:00 Gareth Williams wrote:

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/49.0.2623.112 Safari/537.36

Steps to reproduce:

The section of the man page for certutil's trustargs is outdated as
discussed at https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1586538


Actual results:

The trustargs section of the man page in the nss source files correlates
with the on-line version at https://developer.mozilla.org/en-
US/docs/Mozilla/Projects/NSS/Tools/certutil (last modified Sept 2014):

p - Valid peer
P - Trusted peer (implies p)
c - Valid CA
T - Trusted CA to issue client certificates (implies c)
C - Trusted CA to issue server certificates (SSL only)
  (implies c)
u - Certificate can be used for authentication or signing
w - Send warning (use with other attributes to include a warning when the 
certificate is used in that context)


Expected results:

The trustargs section of the man page in the nss source files should
correlate with the later on-line version at
https://developer.mozilla.org/en-
US/docs/Mozilla/Projects/NSS/tools/NSS_Tools_certutil (last modified
Sept 2015):

pprohibited (explicitly distrusted)
PTrusted peer
cValid CA
TTrusted CA to issue client certificates (implies c)
CTrusted CA to issue server certificates (SSL only)
  (implies c)
uCertificate can be used for authentication or signing
wSend warning (use with other attributes to include a warning when the 
certificate is used in that context)

The difference being the lowercase 'p' option.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1586538/comments/7


** Changed in: nss
   Importance: Medium => Unknown

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

Title:
  certutils from libnss3-tools - man page contradicts Mozilla's

Status in NSS:
  New
Status in nss package in Ubuntu:
  Triaged

Bug description:
  Description of certuitls here:
  
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/tools/NSS_Tools_certutil#Options_and_Arguments

  contradicts the man page here:
  http://manpages.ubuntu.com/manpages/wily/man1/certutil.1.html

  In the former "-t p" is "prohibited (explicitly distrusted)".  In the
  latter, it's "Valid peer".

  I'm listing it as a security vuln, because someone could do mistakenly
  do the wrong thing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nss/+bug/1586538/+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 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)

[Daniel van Vugt]

If I modify gstreamer-vaapi to ignore X11 on Wayland, then it freezes in
Wayland instead !?

#0  0x7f5ec1d10ec4 in __GI___poll (fds=0x7fff30df9e50, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f5ec14c3e0c in wl_display_dispatch_queue ()
   from /lib/x86_64-linux-gnu/libwayland-client.so.0
#2  0x7f5ec14c4f1f in wl_display_roundtrip_queue ()
   from /lib/x86_64-linux-gnu/libwayland-client.so.0
#3  0x7f5ec1a4253b in gst_vaapi_display_wayland_setup (
display=)
at ../gst-libs/gst/vaapi/gstvaapidisplay_wayland.c:190
#4  0x7f5ec1a0dec8 in gst_vaapi_display_create (data=0x0, 
init_type=GST_VAAPI_DISPLAY_INIT_FROM_DISPLAY_NAME, display=0x562df9389100)
at ../gst-libs/gst/vaapi/gstvaapidisplay.c:958
#5  gst_vaapi_display_config (display=0x562df9389100, 
init_type=GST_VAAPI_DISPLAY_INIT_FROM_DISPLAY_NAME, init_value=0x0)
at ../gst-libs/gst/vaapi/gstvaapidisplay.c:1265
#6  0x7f5ec19d3317 in gst_vaapi_create_display (
display_name=, display_type=)
at ../gst/vaapi/gstvaapipluginutil.c:110
#7  gst_vaapi_create_test_display () at ../gst/vaapi/gstvaapipluginutil.c:929
#8  gst_vaapi_create_test_display () at ../gst/vaapi/gstvaapipluginutil.c:915
#9  plugin_init (plugin=0x562df9373190) at ../gst/vaapi/gstvaapi.c:191

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

Title:
  Screen freeze before the login screen on VirtualBox (if the third
  party software option was selected)

Status in gnome-shell package in Ubuntu:
  Opinion
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in libxcb package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  1. Install *without* the third-party option.

  2. sudo apt install ubuntu-restricted-extras

  3. sudo apt remove gstreamer1.0-vaapi

  
  [ Original Description ]

  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   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/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988488/+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 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)

[Daniel van Vugt]

** Changed in: gstreamer-vaapi (Ubuntu)
Milestone: None => ubuntu-22.10

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

Title:
  Screen freeze before the login screen on VirtualBox (if the third
  party software option was selected)

Status in gnome-shell package in Ubuntu:
  Opinion
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in libxcb package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  1. Install *without* the third-party option.

  2. sudo apt install ubuntu-restricted-extras

  3. sudo apt remove gstreamer1.0-vaapi

  
  [ Original Description ]

  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   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/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988488/+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 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

[Benjamin Gilbert]

** Patch added: "Updated debdiff with dep3 headers added"
   
https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1988796/+attachment/5623244/+files/2-0.38.4-0ubuntu2.debdiff

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

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  New

Bug description:
  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
   to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1988796/+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 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

[Benjamin Gilbert]

[ Impact ]

OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering backend,
always with CAIRO_OPERATOR_SATURATE and sometimes with subpixel
positioning (when reading certain file formats), and Cairo in turn
invokes this code.  As a result, some slides incorrectly render with
large blank spaces and with some pixels rendered on top of other pixels.
This effectively makes OpenSlide unusable for several of the file
formats it supports.  No workaround is believed possible within the
OpenSlide codebase.

[ Test Plan ]

Compile and run the pixman.c test program uploaded to this bug.  It
should report "OK".

[ Where problems could occur ]

Problems would show up as incorrect pixel output from software that
renders via Cairo or pixman.

[ Other Info ]

While I'm not a pixman expert, it appears that the change should only
affect the broken code path, and it seems unlikely that anything else
depends on the incorrect math fixed by this patch.  This bug hasn't
previously been reported in Ubuntu, which may imply that this code path
is not exercised by other packages in the distro.

The affected source file has had no further commits upstream since this
patch was applied in April 2019, and some basic commit grepping didn't
turn up any followup fixes elsewhere in the tree.

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

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  New

Bug description:
  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
   to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1988796/+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 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)

[Daniel van Vugt]

** Changed in: gstreamer-vaapi (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gstreamer-vaapi (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Screen freeze before the login screen on VirtualBox (if the third
  party software option was selected)

Status in gnome-shell package in Ubuntu:
  Opinion
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in libxcb package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  1. Install *without* the third-party option.

  2. sudo apt install ubuntu-restricted-extras

  3. sudo apt remove gstreamer1.0-vaapi

  
  [ Original Description ]

  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   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/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988488/+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 1992105] Re: missing httpform plugin for saslauthd

[Amit]

This works great, thanks!

I did notice that the package version is 2.1.27 while the latest version
is 2.1.28.  It's not material to us, but I just thought I'd mention it
in case the build process needs to change for that separately.

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

Title:
  missing httpform plugin for saslauthd

Status in cyrus-sasl2 package in Ubuntu:
  In Progress
Status in cyrus-sasl2 source package in Jammy:
  In Progress
Status in cyrus-sasl2 source package in Kinetic:
  In Progress

Bug description:
  Hi, we noticed missing httpform plugin for saslauthd.  We are
  migrating from Centos.

  == On Centos (Notice the httpform at the end)

  /usr/sbin/saslauthd -v
  saslauthd 2.1.26
  authentication mechanisms: getpwent kerberos5 pam rimap shadow ldap httpform

  
  == On Ubuntu jammy
  /usr/sbin/saslauthd -v
  saslauthd 2.1.27
  authentication mechanisms: sasldb getpwent kerberos5 pam rimap shadow ldap

  
  == Potential fix

  add the "--enable-httpform" flag to the sasl2-bin package build

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: sasl2-bin 2.1.27+dfsg2-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Thu Oct  6 14:54:13 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: cyrus-sasl2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1992105/+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 1854314] Re: Legacy directory /var/run in /lib/systemd/system/dbus.socket

[Bug Watch Updater]

** Changed in: dbus
   Status: New => Fix Released

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

Title:
  Legacy directory /var/run in /lib/systemd/system/dbus.socket

Status in D-Bus:
  Fix Released
Status in dbus package in Ubuntu:
  Fix Committed
Status in dbus package in Debian:
  Fix Released

Bug description:
  dbus/focal-proposed,now 1.12.16-2ubuntu1 amd64

  Re(o)curring after each new upgrade of dbus, for quite some time and
  still...

  $ dmesg|grep accordingly
  systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a 
path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket 
→ /run/dbus/system_bus_socket; please update the unit file accordingly.

  Originally:
  $cat /lib/systemd/system/dbus.socket
  [Unit]
  Description=D-Bus System Message Bus Socket

  [Socket]
  ListenStream=/var/run/dbus/system_bus_socket

  After change:
  $cat /lib/systemd/system/dbus.socket
  [Unit]
  Description=D-Bus System Message Bus Socket

  [Socket]
  ListenStream=/run/dbus/system_bus_socket

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1854314/+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 1992497] Re: 22.04 LTS: alsa-library + PulseAudio won't detect my USB sound card

[Eric Richards]

Alsa-lib + Pulseaudio.  Library version 1.2.6.1

** Package changed: ubuntu => alsa-lib (Ubuntu)

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

Title:
  22.04 LTS: alsa-library + PulseAudio won't detect my USB sound card

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  ALSA+Pulseaudio have always been difficult with USB Sound.  In order
  to make it work under the best of circumstances, one would have to
  edit

  /etc/modprobe.d/alsa-base.conf

  And comment out any line that said

  options snd-usb-audio index=-2

  Without commenting that out, PulseAudio cannot detect the card.

  Now, Ubuntu 22.04 LTS worked for a while with that change.  Until
  Roughly the last week of September, 2022.  A normal update got pushed
  which disabled my sound card.

  Alsa-lib version: 1.2.6.1

  In /var/log/syslog:

  Oct 02 14:33:56 patchwork alsactl[1000]: alsa-lib
  main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:1 use
  case configuration -2

  After two weeks of effort, and attempts to roll back to an earlier
  version of 22.04 LTS, I scrubbed the root partition and reverted to
  20.04 LTS which works right.

  Samples of output from my exercise can be found here:

  https://ubuntuforums.org/showthread.php?t=2479484

  Again, Xubuntu 22.04 LTS worked (after the alsa-base.conf edit) fine,
  Until the end of September update.

  The above thread on ubuntuforums.org has samples of lsusb, syslog,
  output from various ALSA utilities and PulseAudio utilities, brands
  and models of USB sound DACs tried, alsa-version output, and so on.

  If you need me to, I can build a throwaway system to get you any
  further information you want, but I'd rather not scrub a fully
  configured root partition *again* to go through this effort.

  linuxquestions.org showed that a search on "failed to open hw:1 use
  case configuration" or subsets of that phrase will show this bug.

  The tip of the ALSA development chain release notes for a while back
  shows no effort put forward to fixing this problem.  What works is
  Alsa-lib version 1.2.2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1992497/+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 1992497] [NEW] 22.04 LTS: alsa-library + PulseAudio won't detect my USB sound card

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

ALSA+Pulseaudio have always been difficult with USB Sound.  In order to
make it work under the best of circumstances, one would have to edit

/etc/modprobe.d/alsa-base.conf

And comment out any line that said

options snd-usb-audio index=-2

Without commenting that out, PulseAudio cannot detect the card.

Now, Ubuntu 22.04 LTS worked for a while with that change.  Until
Roughly the last week of September, 2022.  A normal update got pushed
which disabled my sound card.

Alsa-lib version: 1.2.6.1

In /var/log/syslog:

Oct 02 14:33:56 patchwork alsactl[1000]: alsa-lib
main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:1 use
case configuration -2

After two weeks of effort, and attempts to roll back to an earlier
version of 22.04 LTS, I scrubbed the root partition and reverted to
20.04 LTS which works right.

Samples of output from my exercise can be found here:

https://ubuntuforums.org/showthread.php?t=2479484

Again, Xubuntu 22.04 LTS worked (after the alsa-base.conf edit) fine,
Until the end of September update.

The above thread on ubuntuforums.org has samples of lsusb, syslog,
output from various ALSA utilities and PulseAudio utilities, brands and
models of USB sound DACs tried, alsa-version output, and so on.

If you need me to, I can build a throwaway system to get you any further
information you want, but I'd rather not scrub a fully configured root
partition *again* to go through this effort.

linuxquestions.org showed that a search on "failed to open hw:1 use case
configuration" or subsets of that phrase will show this bug.

The tip of the ALSA development chain release notes for a while back
shows no effort put forward to fixing this problem.  What works is Alsa-
lib version 1.2.2.

** Affects: alsa-lib (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
22.04 LTS: alsa-library + PulseAudio won't detect my USB sound card
https://bugs.launchpad.net/bugs/1992497
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-lib in Ubuntu.

-- 
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 1992105] Re: missing httpform plugin for saslauthd

[Lena Voytek]

Thanks for the help! I've created a ppa that enables httpform and
confirmed that it showed up when running saslauthd -v. It's located
here: https://launchpad.net/~lvoytek/+archive/ubuntu/cyrus-
sasl2-saslauthd-add-httpform

If you'd like to install and test, you can run:

sudo add-apt-repository ppa:lvoytek/cyrus-sasl2-saslauthd-add-httpform
sudo apt update
sudo apt upgrade

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

Title:
  missing httpform plugin for saslauthd

Status in cyrus-sasl2 package in Ubuntu:
  In Progress
Status in cyrus-sasl2 source package in Jammy:
  In Progress
Status in cyrus-sasl2 source package in Kinetic:
  In Progress

Bug description:
  Hi, we noticed missing httpform plugin for saslauthd.  We are
  migrating from Centos.

  == On Centos (Notice the httpform at the end)

  /usr/sbin/saslauthd -v
  saslauthd 2.1.26
  authentication mechanisms: getpwent kerberos5 pam rimap shadow ldap httpform

  
  == On Ubuntu jammy
  /usr/sbin/saslauthd -v
  saslauthd 2.1.27
  authentication mechanisms: sasldb getpwent kerberos5 pam rimap shadow ldap

  
  == Potential fix

  add the "--enable-httpform" flag to the sasl2-bin package build

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: sasl2-bin 2.1.27+dfsg2-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Thu Oct  6 14:54:13 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: cyrus-sasl2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1992105/+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 1990743] Re: resolvconf install fails upgrading from Jammy to Kinetic

[Jonathan Kamens]

Given your description, I don't think the upgrade left resolvconf
installed. I think I can my ansible playbook after running the upgrade
and it reinstalled resolvconf which had been uninstalled by the upgrade.
I guess if resolvconf can't be removed yet because of the reverse-
dependencies, then there's nothing more to be done here. :shrug:

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

Title:
  resolvconf install fails upgrading from Jammy to Kinetic

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  Setting up resolvconf (1.91ubuntu1) ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
   installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  $ ls -l /etc/resolvconf/resolv.conf.d/original 
  lrwxrwxrwx 1 root root 39 Jan  2  2019 /etc/resolvconf/resolv.conf.d/original 
-> ../run/systemd/resolve/stub-resolv.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: resolvconf 1.91ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 18:48:31 2022
  InstallationDate: Installed on 2019-01-02 (1361 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified]
  modified.conffile..etc.resolvconf.update.d.dnscache: [deleted]
  mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1990743/+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 1992519] [NEW] Firefox crashing because libwebp's LTO

[Marcos Alano]

Public bug reported:

Full disclosure: I use Firefox from Mozilla repo, not from Snap because
of lack of support to 1Password.

I tried access one site, Dell's website (but the same with AMD's website), and 
Firefox just crashed and asked to report a bug. If I execute on console I just 
get one line multiple times: 'Exiting due to channel error.'.
I found a bug report for Firefox that has a comment about a folk that get a tip 
to compile libwebp without LTO.

I did the same, and worked! I used `apt source libwebp7` to get the
source and `apt build-dep libwebp` to install the dependencies. Than I
executed `export DEB_BUILD_MAINT_OPTIONS=optimize=-lto` to disable LTO
and compiled from source with `dpkg-buildpackage -rfakeroot -uc -b`. No
changes in the code. Installed all relevant packages and browser started
behaving correctly.

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

** Package changed: firefox (Ubuntu) => libwebp (Ubuntu)

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

Title:
  Firefox crashing because libwebp's LTO

Status in libwebp package in Ubuntu:
  New

Bug description:
  Full disclosure: I use Firefox from Mozilla repo, not from Snap
  because of lack of support to 1Password.

  I tried access one site, Dell's website (but the same with AMD's website), 
and Firefox just crashed and asked to report a bug. If I execute on console I 
just get one line multiple times: 'Exiting due to channel error.'.
  I found a bug report for Firefox that has a comment about a folk that get a 
tip to compile libwebp without LTO.

  I did the same, and worked! I used `apt source libwebp7` to get the
  source and `apt build-dep libwebp` to install the dependencies. Than I
  executed `export DEB_BUILD_MAINT_OPTIONS=optimize=-lto` to disable LTO
  and compiled from source with `dpkg-buildpackage -rfakeroot -uc -b`.
  No changes in the code. Installed all relevant packages and browser
  started behaving correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/1992519/+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 1992519] [NEW] Firefox crashing because libwebp's LTO

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Full disclosure: I use Firefox from Mozilla repo, not from Snap because
of lack of support to 1Password.

I tried access one site, Dell's website (but the same with AMD's website), and 
Firefox just crashed and asked to report a bug. If I execute on console I just 
get one line multiple times: 'Exiting due to channel error.'.
I found a bug report for Firefox that has a comment about a folk that get a tip 
to compile libwebp without LTO.

I did the same, and worked! I used `apt source libwebp7` to get the
source and `apt build-dep libwebp` to install the dependencies. Than I
executed `export DEB_BUILD_MAINT_OPTIONS=optimize=-lto` to disable LTO
and compiled from source with `dpkg-buildpackage -rfakeroot -uc -b`. No
changes in the code. Installed all relevant packages and browser started
behaving correctly.

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

-- 
Firefox crashing because libwebp's LTO
https://bugs.launchpad.net/bugs/1992519
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to libwebp in Ubuntu.

-- 
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 1969976] Autopkgtest regression report (fwupd/1.7.9-1~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted fwupd (1.7.9-1~20.04.1) for focal have 
finished running.
The following regressions have been reported in tests triggered by the package:

fwupd/1.7.9-1~20.04.1 (armhf)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#fwupd

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

Thank you!

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

Title:
  DynamicUser=1 doesn't get along with services that need dbus-daemon

Status in Fwupd:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in systemd:
  New
Status in fwupd package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in fwupd source package in Focal:
  Fix Committed
Status in systemd source package in Focal:
  Won't Fix
Status in fwupd source package in Impish:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix
Status in fwupd source package in Jammy:
  Fix Committed
Status in systemd source package in Jammy:
  Won't Fix

Bug description:
  Updating to systemd 245.4-4ubuntu3.16 has caused a regression in
  Ubuntu 20.04, that fwupd-refresh.service always fails to run.

  This has been root caused down to the changes in
  https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538

  Unfortunately this is an upstream issue introduced by stable systemd.
  https://github.com/systemd/systemd/issues/22737

  The problem also occurs in Ubuntu 22.04 with a newer systemd release.
  As discussed in 
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61
 it's a tradeoff of issues.  So within Ubuntu something probably needs to be 
done about fwupd-refresh.service.

  One proposal is to remove DynamicUser=yes from the systemd unit, but
  this will mean fwupdgmr refresh runs as root.  It's relatively
  sandboxed by other security mechanisms, but still not ideal.  Could we
  repurpose any other service account?  Or alternatively we can make a
  new fwupd service account that this systemd unit uses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug/1969976/+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 1992513] [NEW] apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

[dann frazier]

Public bug reported:

apt/jammy

apt will refuse to install nvidia-driver-470-server if nvidia-driver-450-server 
is installed *and* out of date. I can reproduce this by disabling all but the 
jammy release pocket, installing the old n-d-450-s from there, and then 
enabling updates and trying to install n-v-470-s (where a new
n-d-450-s is available):

# libnvidia-gl-450-server has an update available
root@dannf-apt-jammy:/var/cache# apt install --dry-run libnvidia-gl-470-server 
-o Debug::pkgProblemResolver=yes
Reading package lists... Done
Building dependency tree... Done
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:
 libnvidia-common-450-server : Conflicts: libnvidia-common
 libnvidia-common-470-server : Conflicts: libnvidia-common
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

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

** Summary changed:

- will not install nvidia-driver-470-server if nvidia-driver-450-server is 
installed and out of date
+ aptwill not install nvidia-driver-470-server if nvidia-driver-450-server is 
installed and out of date

** Summary changed:

- aptwill not install nvidia-driver-470-server if nvidia-driver-450-server is 
installed and out of date
+ apt will not install nvidia-driver-470-server if nvidia-driver-450-server is 
installed and out of date

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

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  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:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

[Bug Watch Updater]

** Changed in: rsync
   Status: Unknown => Fix Released

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync:
  Fix Released
Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.
  The bug was fixed upstream in June 2020:  
https://github.com/WayneD/rsync/issues/98

  $ touch foo
  $ rsync --update --info=skip foo foo
  foo is newer<=== THIS IS NOT CORRECT - A file can't be newer 
than itself.

  Obviously a file should not be listed as newer than itself.  Another
  way:

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/rsync/+bug/1965076/+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 1992504] [NEW] Update libsoup to 2.74.3

[Jeremy Bicha]

Public bug reported:

New upstream bugfix release in the stable libsoup 2.74 series

https://gitlab.gnome.org/GNOME/libsoup/-/blob/2.74.3/NEWS

https://gitlab.gnome.org/GNOME/libsoup/-/compare/2.74.2...2.74.3

** Affects: libsoup2.4 (Ubuntu)
 Importance: Low
 Status: In Progress


** Tags: kinetic upgrade-software-version

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

Title:
  Update libsoup to 2.74.3

Status in libsoup2.4 package in Ubuntu:
  In Progress

Bug description:
  New upstream bugfix release in the stable libsoup 2.74 series

  https://gitlab.gnome.org/GNOME/libsoup/-/blob/2.74.3/NEWS

  https://gitlab.gnome.org/GNOME/libsoup/-/compare/2.74.2...2.74.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1992504/+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 1992502] [NEW] evolution data server does not sync google calendar

[tiziano.casavecchia]

Public bug reported:

Evolution data server does not sync google calendar. All applications based on 
evolution data server (evolution, gnome-shell-calendar in top bar, gnome 
calendar, indicator-datetime, cinnamon calendar applet) do not display events 
in calendar.
I've tried other gnome distros in live mode (fedora, debian, opensuse) and all 
work as expected. Tried linuxmint and cinnamon calendar applet does not display 
events.
Furthermore korganizer and Kalendar in kubuntu (based on akonadi) work as 
expected.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evolution-data-server 3.44.4-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: X-Cinnamon
Date: Tue Oct 11 20:52:56 2022
InstallationDate: Installed on 2022-07-17 (86 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: evolution-data-server
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  evolution data server does not sync google calendar

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Evolution data server does not sync google calendar. All applications based 
on evolution data server (evolution, gnome-shell-calendar in top bar, gnome 
calendar, indicator-datetime, cinnamon calendar applet) do not display events 
in calendar.
  I've tried other gnome distros in live mode (fedora, debian, opensuse) and 
all work as expected. Tried linuxmint and cinnamon calendar applet does not 
display events.
  Furthermore korganizer and Kalendar in kubuntu (based on akonadi) work as 
expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution-data-server 3.44.4-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: X-Cinnamon
  Date: Tue Oct 11 20:52:56 2022
  InstallationDate: Installed on 2022-07-17 (86 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: evolution-data-server
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1992502/+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 1992364] Re: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[William Wilson]

This appears to be an issue with a missing `/etc/kernel/cmdline` file.
Did that file somehow get removed from your system?

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

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

Title:
  package initramfs-tools 0.140ubuntu13 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Oct 10 19:26:40 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-10-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992364/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken

[William Wilson]

** Tags added: foundations-triage-discuss

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

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fonts-dejavu package in Ubuntu:
  New

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHKLMNT and the digits 1 and
  4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

[William Wilson]

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

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

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

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

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon

[Łukasz Zemczak]

Hello Mario, or anyone else affected,

Accepted fwupd into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/fwupd/1.7.9-1~20.04.1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: fwupd (Ubuntu Focal)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  DynamicUser=1 doesn't get along with services that need dbus-daemon

Status in Fwupd:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in systemd:
  New
Status in fwupd package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in fwupd source package in Focal:
  Fix Committed
Status in systemd source package in Focal:
  Won't Fix
Status in fwupd source package in Impish:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix
Status in fwupd source package in Jammy:
  Fix Committed
Status in systemd source package in Jammy:
  Won't Fix

Bug description:
  Updating to systemd 245.4-4ubuntu3.16 has caused a regression in
  Ubuntu 20.04, that fwupd-refresh.service always fails to run.

  This has been root caused down to the changes in
  https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538

  Unfortunately this is an upstream issue introduced by stable systemd.
  https://github.com/systemd/systemd/issues/22737

  The problem also occurs in Ubuntu 22.04 with a newer systemd release.
  As discussed in 
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61
 it's a tradeoff of issues.  So within Ubuntu something probably needs to be 
done about fwupd-refresh.service.

  One proposal is to remove DynamicUser=yes from the systemd unit, but
  this will mean fwupdgmr refresh runs as root.  It's relatively
  sandboxed by other security mechanisms, but still not ideal.  Could we
  repurpose any other service account?  Or alternatively we can make a
  new fwupd service account that this systemd unit uses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug/1969976/+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 1978738] Re: systemd-oomd and zram-config services: "Swap is currently not detected; memory pressure usage will be degraded"

[William Wilson]

@Oibaf, this bug is fixed in the Ubuntu package in kinetic.

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

Title:
  systemd-oomd and zram-config services: "Swap is currently not
  detected; memory pressure usage will be degraded"

Status in systemd package in Ubuntu:
  Invalid
Status in zram-config package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  New
Status in zram-config source package in Jammy:
  New

Bug description:
  Problem summary:
  
  I've installed the zram-config package. By default it creates a zram swap 
device with half the physical memory size of the system. For instance, in an 
8GB RAM system:

  # swapon
  NAME   TYPE  SIZE USED PRIO
  /dev/zram0 partition 3,8G   1M5

  #zramctl
  NAME   ALGORITHM DISKSIZE  DATA COMPR TOTAL STREAMS MOUNTPOINT
  /dev/zram0 lzo-rle   3,8G  496K 74,9K  376K   4 [SWAP]

  The problem is that when systemd-oomd.service is started during boot
  it doesn't detect that zram swap device because zram-config.service is
  started later. So when systemd-oomd.service was started the zram
  device didn't exists yet. This is the message shown during boot:

  systemd-oomd[587]: Swap is currently not detected; memory pressure
  usage will be degraded

  If you restart systemd-oomd.service after boot it's correctly started
  because zram-config.service was previously loaded and zram device
  exists. So I think it's just a matter of dependencies during boot
  process; it's necessary to make zram-config.service be started before
  systemd-oomd.service (or to make systemd-oomd.service be restarted
  when zram-config.service is started).

  Aditional info:
  ---
  # lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  # apt-cache policy systemd-oomd
  systemd-oomd:
Instalados: 249.11-0ubuntu3.1
Candidato:  249.11-0ubuntu3.1
Tabla de versión:
   *** 249.11-0ubuntu3.1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   249.11-0ubuntu3 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages

  # apt-cache policy zram-config
  zram-config:
Instalados: 0.7build1
Candidato:  0.7build1
Tabla de versión:
   *** 0.7build1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1978738/+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 1971712] Re: Add support for Intel DG2

[Timo Aaltonen]

but you'll have an oem-6.0 with support built in later

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1898207] Re: package logsave (not installed) failed to install/upgrade: no package named 'logsave' is installed, cannot configure

[William Wilson]

This "Operation not permitted" error looks suspicious. @rubiselprieto
can you check the permissions on your /etc/cron.d directory?

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

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

Title:
  package logsave (not installed) failed to install/upgrade: no package
  named 'logsave' is installed, cannot configure

Status in e2fsprogs package in Ubuntu:
  Incomplete

Bug description:
  updating crashes
  as suggested I did apt-get install -f
  now everything is working fine.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: logsave (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct  2 12:45:08 2020
  DpkgTerminalLog:
   dpkg: error processing package logsave (--configure):
no package named 'logsave' is installed, cannot configure
  ErrorMessage: no package named 'logsave' is installed, cannot configure
  InstallationDate: Installed on 2016-02-08 (1697 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: e2fsprogs
  Title: package logsave (not installed) failed to install/upgrade: no package 
named 'logsave' is installed, cannot configure
  UpgradeStatus: Upgraded to focal on 2020-10-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1898207/+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 1971712] Re: Add support for Intel DG2

[Timo Aaltonen]

not in ubuntu archive

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

[Garagoth]

Hi!

I am having trouble making this work in graceful manner.
Fresh Ubuntu 22.04, systemd 249.11-0ubuntu3.6, netplan 0.104-0ubuntu2.1.
Host has multiple interfaces (6 physical, 2 bonds, 3 vlans on those bonds) and 
multiple (20 to 30) IP addresses on those vlan interfaces.

EVERY time i issue `netplan apply` everything goes down and up again. Even with 
no changes to netplan configuration.
systemd-networkd logs interfaces going down and up again.

Changing anything in netplan config (like adding or removing one of IP
addresses from single interface), doing `netplan generate` &&
`networkctl reload` restarts everything as well.

How I am supposed to simply add or remove IP address to existing interface 
without causing delay of about 5 seconds in network traffic, when all 
interfaces are being restarted?
Am I doing something incorrectly here?

Regards,
Marcin.

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

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in netplan:
  Fix Released
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in keepalived source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Won't Fix
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in keepalived source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth2:
  addresses:
    - 12.13.14.18/29
    - 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
     

[Touch-packages] [Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)

[Paul Wright]

While we're about it, the use of a bash variable named "DNS" for both
the actual server names and the name of the variable in which we're
going to store the server names is confusing.

** Patch added: "Sum of patches I've seen so far plus name change"
   
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+attachment/5623083/+files/syntax-errors.patch

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

Title:
  wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
  /etc/network/if-up.d/resolved: 12: mystatedir: not found)

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Jammy:
  Triaged

Bug description:
  Syslog error:

 nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir:
  not found

  I think it's because of this line:

if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
mystatedir statedir ifindex interface <- this 
is interpreted as a 'mystatedir' command and fails

interface=$IFACE
if [ ! "$interface" ]; then

  
  Perhaps the intention was to 'export mystatedir statedir ...'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+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 1852911] Re: CriticalPowerAction=Suspend should be supported

[Pedro Côrte-Real]

I've been running patched upower for a year and a half now. It has saved
me in a few occasions. By far the most common scenario is that I've
forgotten to plugin and it just suspends and I reconnect it and get
going again. Shutdown is just useless, you still lose your work so might
as well let the power fail completely. Ubuntu should just ship the
patch.

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in Upower:
  New
Status in upower package in Ubuntu:
  Triaged

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1852911/+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 1992454] Re: iptables: segfault when renaming a chain

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  iptables: segfault when renaming a chain

Status in iptables package in Ubuntu:
  In Progress
Status in iptables source package in Bionic:
  In Progress
Status in iptables source package in Focal:
  In Progress
Status in iptables source package in Jammy:
  In Progress
Status in iptables source package in Kinetic:
  In Progress

Bug description:
  This is the description for the upstream fix of this bug[1] :

  This is an odd bug: If the number of chains is right and one renames the
  last one in the list, libiptc dereferences a NULL pointer.

  Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug
  upstream. This bug is to have the fix included in Ubuntu in order to
  avoid such segmentation faults.

  For Jammy and onward, iptables uses the new nft libraries so the
  problem does not appear unless the -legacy commands are used.

  The following code (adapted from the upstream commit to work on Kinetic) may 
be used to reproduce the issue :
  8<
  #!/bin/bash
  #
  # Cover for a bug in libiptc:
  # - the chain 'node-98-tmp' is the last in the list sorted by name
  # - there are 81 chains in total, so three chain index buckets
  # - the last index bucket contains only the 'node-98-tmp' chain
  # => rename temporarily removes it from the bucket, leaving a NULL bucket
  #behind which is dereferenced later when inserting the chain again with 
new
  #name again

  (
echo "*filter"
for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 
node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 
node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 
node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 
node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 
node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 
node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 
node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 
node-92 node-93 node-95 node-98-tmp; do
echo ":$chain - [0:0]"
done
echo "COMMIT"
  ) | $XT_MULTI iptables-legacy-restore
  $XT_MULTI iptables-legacy -E node-98-tmp node-98
  exit $?
  >8

  [1]
  
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+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 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)

[Paul Wright]

If someone's fixing the syntax errors, note there's also
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103 which
(in the initial comment) mentions another problem and its fix.

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

Title:
  wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
  /etc/network/if-up.d/resolved: 12: mystatedir: not found)

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Jammy:
  Triaged

Bug description:
  Syslog error:

 nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir:
  not found

  I think it's because of this line:

if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
mystatedir statedir ifindex interface <- this 
is interpreted as a 'mystatedir' command and fails

interface=$IFACE
if [ ! "$interface" ]; then

  
  Perhaps the intention was to 'export mystatedir statedir ...'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+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 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04

[Paul Wright]

Deleted my incorrect comment about the use of "local", that doesn't
work. https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878
has the correct fix.

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

Title:
  System with DNS server in /etc/network/interfaces has bogus systemd-
  resolved config after  upgrade to 22.04

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
   *** 0.8.36+nmu1ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  After upgrading a server with classic ifupdown configuration after
  reboot the machine had no valid dns servers anymore.

  The problem is that the state file created by ifupdown using
  /etc/network/if-up.d/resolved looks like this:

  root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
  "DNS"="134.102.20.20 134.102.200.14"
  "DOMAINS"="marum.de"

  The script later sources this file and causes the following errors,
  easy to see when you execute this:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This happened to me on three different servers, so this is a serious
  bug and should be fixed before 22.04 upgrades are allowed for
  everybody. Most servers provided by data centers like Hetzner
  (Germany) are configure like that. After a do-release-upgrade you have
  no working DNS anymore, unless you disable systemd-resolved. I don't
  want to use netplan, so changing to this is no option.

  The fix is easy - remove the quotes in the script on the left side
  "$DNS" => $DNS; same for DOMAINS:

  if  [ -n "$NEW_DNS" ]; then
  cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DNS="$NEW_DNS"
  EOF
  if  [ -n "$NEW_DOMAINS" ]; then
  cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DOMAINS="$NEW_DOMAINS"
  EOF
  fi
  fi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+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 1991829] Re: machinectl read-only does not work

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/431363

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

Title:
  machinectl read-only does not work

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Focal:
  New
Status in systemd source package in Jammy:
  New
Status in systemd source package in Kinetic:
  Triaged

Bug description:
  [impact]

  machinectl read-only does not work

  [test case]

  On a system where the systemd machines dir is *not* on a btrfs volume
  (e.g. it's on a normal ext4 fs), create an image 'test' and then:

  $ sudo machinectl image-status test
  test
  Type: directory
  Path: /var/lib/machines/test
  Hostname: ubuntu
OS: Ubuntu 20.04.5 LTS
RO: writable
   Created: Wed 2022-10-05 13:41:15 EDT; 34s ago

  $ sudo machinectl read-only test
  Could not mark image read-only: Access denied

  [regression potential]

  failure marking images ro or rw

  [scope]

  this is needed in all releases that include machinectl

  this is fixed upstream by 137d162c42ed858613afc3d7493d08d4ae6d5c1b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1991829/+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 1992105] Re: missing httpform plugin for saslauthd

[Amit]

Please let me know if I can help test anything out!

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

Title:
  missing httpform plugin for saslauthd

Status in cyrus-sasl2 package in Ubuntu:
  In Progress
Status in cyrus-sasl2 source package in Jammy:
  In Progress
Status in cyrus-sasl2 source package in Kinetic:
  In Progress

Bug description:
  Hi, we noticed missing httpform plugin for saslauthd.  We are
  migrating from Centos.

  == On Centos (Notice the httpform at the end)

  /usr/sbin/saslauthd -v
  saslauthd 2.1.26
  authentication mechanisms: getpwent kerberos5 pam rimap shadow ldap httpform

  
  == On Ubuntu jammy
  /usr/sbin/saslauthd -v
  saslauthd 2.1.27
  authentication mechanisms: sasldb getpwent kerberos5 pam rimap shadow ldap

  
  == Potential fix

  add the "--enable-httpform" flag to the sasl2-bin package build

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: sasl2-bin 2.1.27+dfsg2-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Thu Oct  6 14:54:13 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: cyrus-sasl2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1992105/+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 1992178] Re: autopkgtest: upstream tests that run in qemu hang on ppc64el

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/431363

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

Title:
  autopkgtest: upstream tests that run in qemu hang on ppc64el

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  I believe this started early in the kinetic cycle, cf.
  https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el vs
  https://autopkgtest.ubuntu.com/packages/systemd/jammy/ppc64el.
  Timeouts in the upstream tests have been an issue for a while, but
  kinetic on ppc64el consistently times out with upstream tests that run
  in QEMU.

  Skipping individual tests does not help, because *which* tests time
  out appears to change with each build. For example, in 251.4-1ubuntu4
  the TEST-36-NUMAPOLICY test was consistently the culprit, but now in
  251.4-1ubuntu6 the TEST-14-MACHINE-ID often times out.

  I have not been able to identify a root cause for this, but it seems
  that running tests in QEMU is very fragile on ppc64el, where as the
  tests that run in nspawn are more consistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1992178/+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 1992206] Re: bash: non existent locale crashes bash

[Nick Rosbrook]

This bug is the cause of recent systemd autopkgtest failures,
specifically the TEST-69-SHUTDOWN test:
https://autopkgtest.ubuntu.com/results/autopkgtest-
kinetic/kinetic/amd64/s/systemd/20221003_103148_cc8ac@/log.gz. I
confirmed in a local autopkgtest run that this patch fixes the test.

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

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

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

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

Title:
  bash: non existent locale crashes bash

Status in bash package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Committed
Status in bash package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/1021109:

  Package: libc6
  Version: 2.35-1
  Severity: grave
  Justification: renders package unusable
  X-Debbugs-Cc: kos...@debian.org

  Dear maintainer,

  After upgrading to libc6 2.35-1 (or 2.36-1 in experimental), nonexistent 
locale setting
  starts to crash the system.

  This is dangerous because a remote system might not always have the same 
locale installed.
  An auto update will soft-brick the system unless the sysadmin knows to set 
their LC_ALL=POSIX
  before attempting to ssh.

  Steps to reproduce:

  From a clean installed Debian sid, upgrade to libc6 2.35-1.
  Only install C locale and en_US.UTF-8.

  $ LC_ALL=ja_JP.UTF-8 bash
  bash: warning: setlocale: LC_ALL: cannot change locale (ja_JP.UTF-8)
  Segmentation fault (core dumped)

  $ LC_ALL=ja_JP.UTF-8 gdb bash

  Fatal signal: Segmentation fault
  - Backtrace -
  0x55ed3e1e8dcf ???
  0x55ed3e2df312 ???
  0x55ed3e2df488 ???
  0x7f0b4a39ba9f ???
  0x7f0b4b412204 _rl_init_locale
  0x7f0b4b4122f1 _rl_init_eightbit
  0x7f0b4b3f10f2 rl_initialize
  ... snip ...

  Downgrade to 2.34-8 seems also don't fix the issue, probably some locale
  state was invalidated when upgrading.

  Thanks,
  Kan-Ru

  
  -- System Information:
  Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
  Architecture: amd64 (x86_64)

  Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
  Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

  Versions of packages libc6 depends on:
  ii  libgcc-s1  12.2.0-3

  Versions of packages libc6 recommends:
  ii  libidn2-0  2.3.3-1+b1

  Versions of packages libc6 suggests:
  ii  debconf [debconf-2.0]  1.5.79
  pn  glibc-doc  
  ii  libc-l10n  2.35-1
  pn  libnss-nis 
  pn  libnss-nisplus 
  ii  locales2.35-1

  -- debconf information:
glibc/kernel-too-old:
glibc/restart-failed:
glibc/disable-screensaver:
glibc/upgrade: true
  * libraries/restart-without-asking: false
  * glibc/restart-services: cron
glibc/kernel-not-supported:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1992206/+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 1286910] Re: Lock screen uses last active window's language instead of default keyboard language

[tarik walid]

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

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

Title:
  Lock screen uses last active window's language instead of default
  keyboard language

Status in gdm:
  New
Status in GNOME Screensaver:
  New
Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in Unity:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Lock screen (gnome-screensaver) uses last active window's language
  (keyboard layout) instead of default keyboard language.

  Steps to reproduce this bug:
  1. In the system Text Entry settings:
1a. add two or more languages to the input sources list, e.g. English (as 
first and default) and Russian (as second);
1b. Set hotkeys to switch sources (e.g. Ctrl+Shift or CapsLock).
1c. Select "Allow different sources for each window" radio button.
1d. Select "New windows use the default source" radio button.
  2. Run any application (e.g. gedit) and switch keyboard to second input 
language (Russian).
  3. Lock the screen (Ctrl+Alt+L) or just wait idle time.
  4. See what language set by default for password input in the lock screen.

  Expected: lock screen uses first input language (English) by default.
  What happened instead: lock screen uses last active window's language 
(Russian).

  Ubuntu versions affected: Ubuntu 13.10, Ubuntu 14.04 (daily builds)
  gnome-screensaver versions: 3.6.1-0ubuntu7, 3.6.1-0ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1286910/+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 1992454] Re: iptables: segfault when renaming a chain

[Louis Bouchard]

Hello,

Thanks for picking this up. Reference to the test was added to
debian/test/control & test ran fine as we can see in the logs :

Removing autopkgtest-satdep (0) ... 
 
autopkgtest [17:00:57]: test command18: chmod +x 
./iptables/tests/shell/testcases/chain/0006rename-segfault_0; cd 
iptables/tests/shell; ./run-tests.sh --host
autopkgtest [17:00:57]: test command18: [---

 
I: [OK]  ././testcases/arptables/0001-arptables-save-restore_0
I: [OK]  ././testcases/arptables/0002-arptables-restore-defaults_0
I: [OK]  ././testcases/arptables/0003-arptables-verbose-output_0

I: [OK]  ././testcases/chain/0001duplicate_1 
I: [OK]  ././testcases/chain/0002newchain_0 
 
I: [OK]  ././testcases/chain/0003rename_1   
 
I: [OK]  ././testcases/chain/0006rename-segfault_0

Here is a new debdiff with the added bits.

** Patch added: "iptables_1.8.7-1ubuntu7.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+attachment/5623037/+files/iptables_1.8.7-1ubuntu7.debdiff

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

Title:
  iptables: segfault when renaming a chain

Status in iptables package in Ubuntu:
  In Progress
Status in iptables source package in Bionic:
  In Progress
Status in iptables source package in Focal:
  In Progress
Status in iptables source package in Jammy:
  In Progress
Status in iptables source package in Kinetic:
  In Progress

Bug description:
  This is the description for the upstream fix of this bug[1] :

  This is an odd bug: If the number of chains is right and one renames the
  last one in the list, libiptc dereferences a NULL pointer.

  Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug
  upstream. This bug is to have the fix included in Ubuntu in order to
  avoid such segmentation faults.

  For Jammy and onward, iptables uses the new nft libraries so the
  problem does not appear unless the -legacy commands are used.

  The following code (adapted from the upstream commit to work on Kinetic) may 
be used to reproduce the issue :
  8<
  #!/bin/bash
  #
  # Cover for a bug in libiptc:
  # - the chain 'node-98-tmp' is the last in the list sorted by name
  # - there are 81 chains in total, so three chain index buckets
  # - the last index bucket contains only the 'node-98-tmp' chain
  # => rename temporarily removes it from the bucket, leaving a NULL bucket
  #behind which is dereferenced later when inserting the chain again with 
new
  #name again

  (
echo "*filter"
for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 
node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 
node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 
node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 
node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 
node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 
node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 
node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 
node-92 node-93 node-95 node-98-tmp; do
echo ":$chain - [0:0]"
done
echo "COMMIT"
  ) | $XT_MULTI iptables-legacy-restore
  $XT_MULTI iptables-legacy -E node-98-tmp node-98
  exit $?
  >8

  [1]
  
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+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 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04

[Paul Wright]

The same error also happened in the ifdown script for resolved. Weird.

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

Title:
  System with DNS server in /etc/network/interfaces has bogus systemd-
  resolved config after  upgrade to 22.04

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
   *** 0.8.36+nmu1ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  After upgrading a server with classic ifupdown configuration after
  reboot the machine had no valid dns servers anymore.

  The problem is that the state file created by ifupdown using
  /etc/network/if-up.d/resolved looks like this:

  root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
  "DNS"="134.102.20.20 134.102.200.14"
  "DOMAINS"="marum.de"

  The script later sources this file and causes the following errors,
  easy to see when you execute this:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This happened to me on three different servers, so this is a serious
  bug and should be fixed before 22.04 upgrades are allowed for
  everybody. Most servers provided by data centers like Hetzner
  (Germany) are configure like that. After a do-release-upgrade you have
  no working DNS anymore, unless you disable systemd-resolved. I don't
  want to use netplan, so changing to this is no option.

  The fix is easy - remove the quotes in the script on the left side
  "$DNS" => $DNS; same for DOMAINS:

  if  [ -n "$NEW_DNS" ]; then
  cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DNS="$NEW_DNS"
  EOF
  if  [ -n "$NEW_DOMAINS" ]; then
  cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DOMAINS="$NEW_DOMAINS"
  EOF
  fi
  fi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+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 1992472] [NEW] APT hooks do not respect the -q option

[Renan Rodrigo]

Public bug reported:

ubuntu-advantage-tools recently used an APT Cli hook
(AptCli::Hooks::Upgrade) to add a message to the output. We were asked
in https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
tools/+bug/1992026/comments/9 to honor the -q (-qq, -qqq) option of APT
upgrade, and hide the output.

However, the hook does not expose this option, so there is nothing we
can do from our side.

APT could either treat those messages based on the "quietness" defined
when running the command, or expose the flag somehow so we could
configure our message to respect it.

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

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

Title:
  APT hooks do not respect the -q option

Status in apt package in Ubuntu:
  New

Bug description:
  ubuntu-advantage-tools recently used an APT Cli hook
  (AptCli::Hooks::Upgrade) to add a message to the output. We were asked
  in https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
  tools/+bug/1992026/comments/9 to honor the -q (-qq, -qqq) option of
  APT upgrade, and hide the output.

  However, the hook does not expose this option, so there is nothing we
  can do from our side.

  APT could either treat those messages based on the "quietness" defined
  when running the command, or expose the flag somehow so we could
  configure our message to respect it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992472/+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 1951586] Re: Need option to specify wifi regulatory domain

[Lukas Märdian]

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

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

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  Fix Released
Status in NetworkManager:
  New
Status in netplan.io package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Incomplete
Status in netplan.io source package in Jammy:
  Triaged
Status in network-manager source package in Jammy:
  Incomplete
Status in netplan.io source package in Kinetic:
  Fix Released
Status in network-manager source package in Kinetic:
  Incomplete

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users 
can simply setup Ubuntu Server headless by putting the wifi configuration 
details in cloudinit/netplan's "network-config" on the FAT partition of the SD 
card: 
https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so 
may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 1992105] Re: missing httpform plugin for saslauthd

[Lena Voytek]

Thanks for the info, that is a good justification for adding httpform to
Ubuntu. I'll get started on it.

** Changed in: cyrus-sasl2 (Ubuntu Jammy)
   Status: Confirmed => In Progress

** Changed in: cyrus-sasl2 (Ubuntu Kinetic)
   Status: Confirmed => In Progress

** Changed in: cyrus-sasl2 (Ubuntu Jammy)
 Assignee: (unassigned) => Lena Voytek (lvoytek)

** Changed in: cyrus-sasl2 (Ubuntu Kinetic)
 Assignee: (unassigned) => Lena Voytek (lvoytek)

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

Title:
  missing httpform plugin for saslauthd

Status in cyrus-sasl2 package in Ubuntu:
  In Progress
Status in cyrus-sasl2 source package in Jammy:
  In Progress
Status in cyrus-sasl2 source package in Kinetic:
  In Progress

Bug description:
  Hi, we noticed missing httpform plugin for saslauthd.  We are
  migrating from Centos.

  == On Centos (Notice the httpform at the end)

  /usr/sbin/saslauthd -v
  saslauthd 2.1.26
  authentication mechanisms: getpwent kerberos5 pam rimap shadow ldap httpform

  
  == On Ubuntu jammy
  /usr/sbin/saslauthd -v
  saslauthd 2.1.27
  authentication mechanisms: sasldb getpwent kerberos5 pam rimap shadow ldap

  
  == Potential fix

  add the "--enable-httpform" flag to the sasl2-bin package build

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: sasl2-bin 2.1.27+dfsg2-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Thu Oct  6 14:54:13 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: cyrus-sasl2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1992105/+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 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04

[Paul Wright]

Affecting me too on 22.04. By comparing with isc-dhcp-client's
/etc/dhcp/dhclient-exit-hooks.d/resolved I reckon the missing keyword
for those variable declartions is "local" i.e.

local DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE

and so on.

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

Title:
  System with DNS server in /etc/network/interfaces has bogus systemd-
  resolved config after  upgrade to 22.04

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
   *** 0.8.36+nmu1ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  After upgrading a server with classic ifupdown configuration after
  reboot the machine had no valid dns servers anymore.

  The problem is that the state file created by ifupdown using
  /etc/network/if-up.d/resolved looks like this:

  root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
  "DNS"="134.102.20.20 134.102.200.14"
  "DOMAINS"="marum.de"

  The script later sources this file and causes the following errors,
  easy to see when you execute this:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This happened to me on three different servers, so this is a serious
  bug and should be fixed before 22.04 upgrades are allowed for
  everybody. Most servers provided by data centers like Hetzner
  (Germany) are configure like that. After a do-release-upgrade you have
  no working DNS anymore, unless you disable systemd-resolved. I don't
  want to use netplan, so changing to this is no option.

  The fix is easy - remove the quotes in the script on the left side
  "$DNS" => $DNS; same for DOMAINS:

  if  [ -n "$NEW_DNS" ]; then
  cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DNS="$NEW_DNS"
  EOF
  if  [ -n "$NEW_DOMAINS" ]; then
  cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DOMAINS="$NEW_DOMAINS"
  EOF
  fi
  fi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

[Ian! D. Allen]

** Description changed:

  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.
+ 
+ $ touch foo
+ $ rsync --update --info=skip foo foo
+ foo is newer<=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
+ 
+ Obviously a file should not be listed as newer than itself.  Another
+ way:
  
  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00
  
  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.
+ The bug was fixed upstream in June 2020:  
https://github.com/WayneD/rsync/issues/98
  
  $ touch foo
  $ rsync --update --info=skip foo foo
  foo is newer<=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  
  Obviously a file should not be listed as newer than itself.  Another
  way:
  
  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00
  
  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync:
  Unknown
Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.
  The bug was fixed upstream in June 2020:  
https://github.com/WayneD/rsync/issues/98

  $ touch foo
  $ rsync --update --info=skip foo foo
  foo is newer<=== THIS IS NOT CORRECT - A file c

[Touch-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

[Tim Gardner]

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Confirmed
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscripti

[Touch-packages] [Bug 1992454] Re: iptables: segfault when renaming a chain

[Robie Basak]

Thank you for contributing this fix!

This looks fine; just one comment. Upstream adds a test. But it looks to
me like it won't run because the quilt patch can't handle the executable
bit. Looks like there's a workaround in debian/tests/control for another
case of the same issue. Please could you ensure that dep8 tests are
passing (in "isolation-machine") and running this new test?

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

Title:
  iptables: segfault when renaming a chain

Status in iptables package in Ubuntu:
  In Progress
Status in iptables source package in Bionic:
  In Progress
Status in iptables source package in Focal:
  In Progress
Status in iptables source package in Jammy:
  In Progress
Status in iptables source package in Kinetic:
  In Progress

Bug description:
  This is the description for the upstream fix of this bug[1] :

  This is an odd bug: If the number of chains is right and one renames the
  last one in the list, libiptc dereferences a NULL pointer.

  Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug
  upstream. This bug is to have the fix included in Ubuntu in order to
  avoid such segmentation faults.

  For Jammy and onward, iptables uses the new nft libraries so the
  problem does not appear unless the -legacy commands are used.

  The following code (adapted from the upstream commit to work on Kinetic) may 
be used to reproduce the issue :
  8<
  #!/bin/bash
  #
  # Cover for a bug in libiptc:
  # - the chain 'node-98-tmp' is the last in the list sorted by name
  # - there are 81 chains in total, so three chain index buckets
  # - the last index bucket contains only the 'node-98-tmp' chain
  # => rename temporarily removes it from the bucket, leaving a NULL bucket
  #behind which is dereferenced later when inserting the chain again with 
new
  #name again

  (
echo "*filter"
for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 
node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 
node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 
node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 
node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 
node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 
node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 
node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 
node-92 node-93 node-95 node-98-tmp; do
echo ":$chain - [0:0]"
done
echo "COMMIT"
  ) | $XT_MULTI iptables-legacy-restore
  $XT_MULTI iptables-legacy -E node-98-tmp node-98
  exit $?
  >8

  [1]
  
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+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 1992463] [NEW] Totem can't play video captured with the "Take a Screenshot" tool

[Jonathan Kamens]

Public bug reported:

If I create a 5-second video of my desktop with the "Take a Screenshot"
tool (as an aside, is that tool built into gnome-shell now or something?
I couldn't figure out what executable the app icon corresponds to, i.e.,
I couldn't find the desktop file for it :shrug:) and then open the
resulting webm file which causes it to be opened in the Videos app,
i.e., Totem, the video as shown on the screen is all scrunched up to the
left and in monochrome rather than color. If I play the same video in
mplayer it looks fine. See the attached screenshot which shows a Totem
window and an mplayer window with the same video file open in each.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: libgstreamer1.0-0 1.20.3-1
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 11 09:21:21 2022
InstallationDate: Installed on 2022-09-17 (23 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: gstreamer1.0
UpgradeStatus: Upgraded to kinetic on 2022-10-02 (8 days ago)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic wayland-session

** Attachment added: "Screenshot from 2022-10-11 09-20-54.png"
   
https://bugs.launchpad.net/bugs/1992463/+attachment/5623010/+files/Screenshot%20from%202022-10-11%2009-20-54.png

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

Title:
  Totem can't play video captured with the "Take a Screenshot" tool

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  If I create a 5-second video of my desktop with the "Take a
  Screenshot" tool (as an aside, is that tool built into gnome-shell now
  or something? I couldn't figure out what executable the app icon
  corresponds to, i.e., I couldn't find the desktop file for it :shrug:)
  and then open the resulting webm file which causes it to be opened in
  the Videos app, i.e., Totem, the video as shown on the screen is all
  scrunched up to the left and in monochrome rather than color. If I
  play the same video in mplayer it looks fine. See the attached
  screenshot which shows a Totem window and an mplayer window with the
  same video file open in each.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libgstreamer1.0-0 1.20.3-1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 11 09:21:21 2022
  InstallationDate: Installed on 2022-09-17 (23 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to kinetic on 2022-10-02 (8 days ago)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1992463/+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 1992454] Re: iptables: segfault when renaming a chain

[Louis Bouchard]

Here is the debdiff for upload to Kinetic.

** Patch added: "iptables_1.8.7-1ubuntu7.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+attachment/5622997/+files/iptables_1.8.7-1ubuntu7.debdiff

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

Title:
  iptables: segfault when renaming a chain

Status in iptables package in Ubuntu:
  In Progress
Status in iptables source package in Bionic:
  In Progress
Status in iptables source package in Focal:
  In Progress
Status in iptables source package in Jammy:
  In Progress
Status in iptables source package in Kinetic:
  In Progress

Bug description:
  This is the description for the upstream fix of this bug[1] :

  This is an odd bug: If the number of chains is right and one renames the
  last one in the list, libiptc dereferences a NULL pointer.

  Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug
  upstream. This bug is to have the fix included in Ubuntu in order to
  avoid such segmentation faults.

  For Jammy and onward, iptables uses the new nft libraries so the
  problem does not appear unless the -legacy commands are used.

  The following code (adapted from the upstream commit to work on Kinetic) may 
be used to reproduce the issue :
  8<
  #!/bin/bash
  #
  # Cover for a bug in libiptc:
  # - the chain 'node-98-tmp' is the last in the list sorted by name
  # - there are 81 chains in total, so three chain index buckets
  # - the last index bucket contains only the 'node-98-tmp' chain
  # => rename temporarily removes it from the bucket, leaving a NULL bucket
  #behind which is dereferenced later when inserting the chain again with 
new
  #name again

  (
echo "*filter"
for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 
node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 
node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 
node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 
node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 
node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 
node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 
node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 
node-92 node-93 node-95 node-98-tmp; do
echo ":$chain - [0:0]"
done
echo "COMMIT"
  ) | $XT_MULTI iptables-legacy-restore
  $XT_MULTI iptables-legacy -E node-98-tmp node-98
  exit $?
  >8

  [1]
  
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

[Simon Déziel]

** Also affects: rsync via
   https://github.com/WayneD/rsync/issues/98
   Importance: Unknown
   Status: Unknown

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync:
  Unknown
Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/rsync/+bug/1965076/+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 1969976] Autopkgtest regression report (fwupd/1.7.9-1~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted fwupd (1.7.9-1~22.04.1) for jammy have 
finished running.
The following regressions have been reported in tests triggered by the package:

fwupd/1.7.9-1~22.04.1 (armhf)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#fwupd

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

Thank you!

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

Title:
  DynamicUser=1 doesn't get along with services that need dbus-daemon

Status in Fwupd:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in systemd:
  New
Status in fwupd package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in fwupd source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Won't Fix
Status in fwupd source package in Impish:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix
Status in fwupd source package in Jammy:
  Fix Committed
Status in systemd source package in Jammy:
  Won't Fix

Bug description:
  Updating to systemd 245.4-4ubuntu3.16 has caused a regression in
  Ubuntu 20.04, that fwupd-refresh.service always fails to run.

  This has been root caused down to the changes in
  https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538

  Unfortunately this is an upstream issue introduced by stable systemd.
  https://github.com/systemd/systemd/issues/22737

  The problem also occurs in Ubuntu 22.04 with a newer systemd release.
  As discussed in 
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61
 it's a tradeoff of issues.  So within Ubuntu something probably needs to be 
done about fwupd-refresh.service.

  One proposal is to remove DynamicUser=yes from the systemd unit, but
  this will mean fwupdgmr refresh runs as root.  It's relatively
  sandboxed by other security mechanisms, but still not ideal.  Could we
  repurpose any other service account?  Or alternatively we can make a
  new fwupd service account that this systemd unit uses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug/1969976/+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 1992454] Re: iptables: segfault when renaming a chain

[Louis Bouchard]

** Description changed:

  This is the description for the upstream fix of this bug[1] :
  
  This is an odd bug: If the number of chains is right and one renames the
  last one in the list, libiptc dereferences a NULL pointer.
  
  Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug upstream.
  This bug is to have the fix included in Ubuntu in order to avoid such
  segmentation faults.
  
+ For Jammy and onward, iptables uses the new nft libraries so the problem
+ does not appear unless the -legacy commands are used.
+ 
+ The following code (adapted from the upstream commit to work on Kinetic) may 
be used to reproduce the issue :
+ 8<
+ #!/bin/bash
+ #
+ # Cover for a bug in libiptc:
+ # - the chain 'node-98-tmp' is the last in the list sorted by name
+ # - there are 81 chains in total, so three chain index buckets
+ # - the last index bucket contains only the 'node-98-tmp' chain
+ # => rename temporarily removes it from the bucket, leaving a NULL bucket
+ #behind which is dereferenced later when inserting the chain again with 
new
+ #name again
+ 
+ (
+   echo "*filter"
+   for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 
node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 
node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 
node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 
node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 
node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 
node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 
node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 
node-92 node-93 node-95 node-98-tmp; do
+   echo ":$chain - [0:0]"
+   done
+   echo "COMMIT"
+ ) | $XT_MULTI iptables-legacy-restore
+ $XT_MULTI iptables-legacy -E node-98-tmp node-98
+ exit $?
+ >8
+ 
  [1]
  
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f

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

Title:
  iptables: segfault when renaming a chain

Status in iptables package in Ubuntu:
  In Progress
Status in iptables source package in Bionic:
  In Progress
Status in iptables source package in Focal:
  In Progress
Status in iptables source package in Jammy:
  In Progress
Status in iptables source package in Kinetic:
  In Progress

Bug description:
  This is the description for the upstream fix of this bug[1] :

  This is an odd bug: If the number of chains is right and one renames the
  last one in the list, libiptc dereferences a NULL pointer.

  Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug
  upstream. This bug is to have the fix included in Ubuntu in order to
  avoid such segmentation faults.

  For Jammy and onward, iptables uses the new nft libraries so the
  problem does not appear unless the -legacy commands are used.

  The following code (adapted from the upstream commit to work on Kinetic) may 
be used to reproduce the issue :
  8<
  #!/bin/bash
  #
  # Cover for a bug in libiptc:
  # - the chain 'node-98-tmp' is the last in the list sorted by name
  # - there are 81 chains in total, so three chain index buckets
  # - the last index bucket contains only the 'node-98-tmp' chain
  # => rename temporarily removes it from the bucket, leaving a NULL bucket
  #behind which is dereferenced later when inserting the chain again with 
new
  #name again

  (
echo "*filter"
for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 
node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 
node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 
node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 
node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 
node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 
node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 
node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 
node-92 node-93 node-95 node-98-tmp; do
echo ":$chain - [0:0]"
done
echo "COMMIT"
  ) | $XT_MULTI iptables-legacy-restore
  $XT_MULTI iptables-legacy -E node-98-tmp node-98
  exit $?
  >8

  [1]
  
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f

To manage notifications about this bug go to:
https://bugs.launchpa

[Touch-packages] [Bug 1823985] Re: isc-dhcp-server can't load leases file with apparmor enabled

[Launchpad Bug Tracker]

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

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Confirmed

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

Title:
  isc-dhcp-server can't load leases file with apparmor enabled

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  I can't start isc-dhcp-server with apparmor enabled.

  I set a custom leases file in the dhcpd.conf:
   lease-file-name "/test/var/lib/dhcp/dhcpd.leases";

  and created a custom apparmor profile for that in 
/etc/apparmor.d/local/usr.sbin.dhcpd:
  /test/var/lib/dhcp/dhcpd{,6}.leases* lrw,

  But when I try to start I see the following errors from dhcpd:

  Internet Systems Consortium DHCP Server 4.3.5
  Copyright 2004-2016 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/
  Config file: /etc/dhcp/dhcpd.conf
  Database file: /test/var/lib/dhcp/dhcpd.leases
  PID file: /run/dhcp-server/dhcpd.pid
  Can't open /test/var/lib/dhcp/dhcpd.leases for append.

  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..

  exiting.

  
  And in the messages log I can see errors like this:

  Apr  9 17:07:03.601 myhost dhcpd[27361]: Can't open 
/test/var/lib/dhcp/dhcpd.leases for append.
  Apr  9 17:07:03.601 myhost dhcpd[27361]:
  Apr  9 17:07:03.601 myhost dhcpd[27361]: If you think you have received this 
message due to a bug rather
  Apr  9 17:07:03.601 myhost dhcpd[27361]: than a configuration issue please 
read the section on submitting
  Apr  9 17:07:03.601 myhost dhcpd[27361]: bugs on either our web page at 
www.isc.org or in the README file
  Apr  9 17:07:03.601 myhost dhcpd[27361]: before submitting a bug.  These 
pages explain the proper
  Apr  9 17:07:03.601 myhost dhcpd[27361]: process and the information we find 
helpful for debugging..
  Apr  9 17:07:03.601 myhost dhcpd[27361]:
  Apr  9 17:07:03.601 myhost dhcpd[27361]: exiting.
  Apr  9 17:07:03.603 myhost kernel: audit: type=1400 
audit(1554822423.596:221): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/dhcpd" pid=27361 comm="dhcpd" capability=1  
capname="dac_override"
  Apr  9 17:07:03.603 myhost kernel: audit: type=1400 
audit(1554822423.596:221): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/dhcpd" pid=27361 comm="dhcpd" capability=1  
capname="dac_override"



  After disabling apparmor for dhcpd everything works as expected:

  ln -s /etc/apparmor.d/usr.sbin.dhcpd /etc/apparmor.d/disable/
  apparmor_parser -R /etc/apparmor.d/usr.sbin.dhcpd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1823985/+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 1992454] Re: iptables: segfault when renaming a chain

[Louis Bouchard]

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

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

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

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

** Changed in: iptables (Ubuntu Bionic)
 Assignee: (unassigned) => Louis Bouchard (louis)

** Changed in: iptables (Ubuntu Focal)
 Assignee: (unassigned) => Louis Bouchard (louis)

** Changed in: iptables (Ubuntu Jammy)
 Assignee: (unassigned) => Louis Bouchard (louis)

** Changed in: iptables (Ubuntu Kinetic)
 Assignee: (unassigned) => Louis Bouchard (louis)

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

Title:
  iptables: segfault when renaming a chain

Status in iptables package in Ubuntu:
  In Progress
Status in iptables source package in Bionic:
  In Progress
Status in iptables source package in Focal:
  In Progress
Status in iptables source package in Jammy:
  In Progress
Status in iptables source package in Kinetic:
  In Progress

Bug description:
  This is the description for the upstream fix of this bug[1] :

  This is an odd bug: If the number of chains is right and one renames the
  last one in the list, libiptc dereferences a NULL pointer.

  Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug
  upstream. This bug is to have the fix included in Ubuntu in order to
  avoid such segmentation faults.

  [1]
  
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+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 1992454] [NEW] iptables: segfault when renaming a chain

[Louis Bouchard]

Public bug reported:

This is the description for the upstream fix of this bug[1] :

This is an odd bug: If the number of chains is right and one renames the
last one in the list, libiptc dereferences a NULL pointer.

Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug upstream.
This bug is to have the fix included in Ubuntu in order to avoid such
segmentation faults.

[1]
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f

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

** Affects: iptables (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: iptables (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: iptables (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: iptables (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

** Also affects: iptables (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  iptables: segfault when renaming a chain

Status in iptables package in Ubuntu:
  New
Status in iptables source package in Bionic:
  New
Status in iptables source package in Focal:
  New
Status in iptables source package in Jammy:
  New
Status in iptables source package in Kinetic:
  New

Bug description:
  This is the description for the upstream fix of this bug[1] :

  This is an odd bug: If the number of chains is right and one renames the
  last one in the list, libiptc dereferences a NULL pointer.

  Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug
  upstream. This bug is to have the fix included in Ubuntu in order to
  avoid such segmentation faults.

  [1]
  
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+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 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon

[Łukasz Zemczak]

Hello Mario, or anyone else affected,

Accepted fwupd into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/fwupd/1.7.9-1~22.04.1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: fwupd (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  DynamicUser=1 doesn't get along with services that need dbus-daemon

Status in Fwupd:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in systemd:
  New
Status in fwupd package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in fwupd source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Won't Fix
Status in fwupd source package in Impish:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix
Status in fwupd source package in Jammy:
  Fix Committed
Status in systemd source package in Jammy:
  Won't Fix

Bug description:
  Updating to systemd 245.4-4ubuntu3.16 has caused a regression in
  Ubuntu 20.04, that fwupd-refresh.service always fails to run.

  This has been root caused down to the changes in
  https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538

  Unfortunately this is an upstream issue introduced by stable systemd.
  https://github.com/systemd/systemd/issues/22737

  The problem also occurs in Ubuntu 22.04 with a newer systemd release.
  As discussed in 
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61
 it's a tradeoff of issues.  So within Ubuntu something probably needs to be 
done about fwupd-refresh.service.

  One proposal is to remove DynamicUser=yes from the systemd unit, but
  this will mean fwupdgmr refresh runs as root.  It's relatively
  sandboxed by other security mechanisms, but still not ideal.  Could we
  repurpose any other service account?  Or alternatively we can make a
  new fwupd service account that this systemd unit uses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug/1969976/+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 1971712] Re: Add support for Intel DG2

[Sebastian Heiden]

Are there any plans for providing an i915 DKMS Module with DG2 Support
for oem-5.17?

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1916931] Re: omshell returns inconsistent results or segfaults

[Massimiliano Ballerini]

Updated isc-dhcp-server to 4.4.1 from apt and omshell crashing 100% of
the time with my configuration.

Compiled the isc-dhcp-server 4.4.3 from source and I'm using
omshell-4.4.3 bin with isc-dhcp-server 4.4.1 without problem for 3
months now. Probably just fixed in 4.4.3 or 4.4.1 compile problem.

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

Title:
  omshell returns inconsistent results or segfaults

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  I have just built a Ubuntu 20.04 server and installed isc-dhcp-server
  4.4.1 on it and I am seeing inconsistent returns from omshell. 
  Initially omshell returns data as expected, but when I exit and re-enter 
  omshell connections fail.

  Here is the initial, working, session:

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect
  obj: 
  > new failover-state
  obj: failover-state
  > set name = "dhcp-failover"
  obj: failover-state
  name = "dhcp-failover"
  > open
  obj: failover-state
  name = "dhcp-failover"
  partner-address = c0:9d:e9:76:e9:55:00:00
  partner-port = 00:00:02:07
  local-address = 10:9d:e9:76:e9:55:00:00
  local-port = 00:00:02:07
  max-outstanding-updates = 00:00:00:0a
  mclt = 00:00:01:2c
  load-balance-max-secs = 00:00:00:03
  load-balance-hba =
  
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
  partner-state = 00:00:00:02
  local-state = 00:00:00:02
  partner-stos = 60:36:d0:68
  local-stos = 60:36:8b:3b
  hierarchy = 00:00:00:01
  last-packet-sent = 00:00:00:00
  last-timestamp-received = 00:00:00:00
  skew = 00:00:00:00
  max-response-delay = 00:00:00:3c
  cur-unacked-updates = 00:00:00:00

  Here is what I see when the connect fails.  Well, just hangs really.

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect

  And then I hit ctrl-c to break out and tried again:

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect
  Segmentation fault (core dumped)

  Note, the peer to this server is still running Ubuntu 18.04 with
  isc-dhcp-server 4.3.5.  Running the exact same commands on the peer
  works reliably.  (They are using the same python script to drive
  omshell.)  The DHCP server on the new system appears to be working 
  just fine as reported by omshell on the peer and systemctl.

  I was curious if the problem could be with the mis-matched versions
  of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system
  and get the same results.

  I also tried using a python script with the pypureomapi module to
  try and determine if the problem was in omshell or the server.  I 
  got very similar results when I attempted to get information about
  the failover state of the server.  Interestingly interrogating
  the server about host information seems to work just fine.

  This is a critical bug since I don't see how to fail over a DHCP
  that is running the isc-dhcp-server on 20.04 without being able
  to issue omapi commands.

  I am attaching apport output to this bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+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 1992430] Re: Snap based apps crash after 5.19.0-18->5.19.0-19 kernel upgrade

[Alex Murray]

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

** This bug has been marked a duplicate of bug 1991691
   cannot change mount namespace

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

Title:
  Snap based apps crash after 5.19.0-18->5.19.0-19 kernel upgrade

Status in apparmor package in Ubuntu:
  New

Bug description:
  This occurs on Ubuntu ver. 22.10.
  Here is an example:

  skype 
  update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.skype /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied
  + [ -f /home/user/snap/skype/common/.config/skypeforlinux/settings.json ]
  + export SKYPE_LOGS=/home/user/snap/skype/231/logs
  + [ ! -d /home/user/snap/skype/231/logs ]
  + exec /snap/skype/231/usr/share/skypeforlinux/skypeforlinux

  (skypeforlinux:9439): Gtk-WARNING **: 10:13:12.251: Theme parsing error: 
gtk.css:3536:25: 'font-feature-settings' is not a valid property name
  Gtk-Message: 10:13:12.294: Failed to load module "colorreload-gtk-module"
  Gtk-Message: 10:13:12.295: Failed to load module 
"window-decorations-gtk-module"
  [1011/101312.442717:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Permission 
denied (13)
  Nyomkövetési/töréspont csapda (core készült)

  Google translation: Trace/breakpoint trap (core made)

  Here is an another one:
  teams
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat 
/var/lib/snapd/hostfs/usr/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat 
/usr/local/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.teams /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied

  Loading of the previous kernel fixes the issue this is why I think it
  could be kernel-related or something like that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1992430/+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 1979951] Re: 127.0.0.1/::1 removed from loopback interface if you configure extra IPs on lo (r104 regression/behaviour change)

[Lukas Märdian]

** Changed in: netplan.io (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: netplan.io (Ubuntu Focal)
   Status: New => Invalid

** Changed in: netplan.io (Ubuntu Jammy)
   Status: New => Invalid

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

Title:
  127.0.0.1/::1 removed from loopback interface if you configure extra
  IPs on lo (r104 regression/behaviour change)

Status in netplan.io package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Released
Status in netplan.io source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Users who wish to configure additional addresses on lo may
  inadvertently remove the 127.0.0.1/8 address from the interface. And,
  because this only happens on the second invocation of `netplan apply`,
  it can create confusing breakages for users. Although this is not a
  recommended configuration, it was previously supported and the current
  behavior is a regression.

  [Test Plan]

  * Configure additional addresses on the lo interface. I am testing in
  a LXD container, so I added the following to /etc/netplan/10-lxc.yaml
  under `ethernets:`

  lo:
addresses: ["10.10.10.17/24","10.10.10.19/24"]

  * Apply the config, and then inspect the lo interface's addresses:

   $ netplan apply
   $ ip addr show dev lo

  * Observe that the 127.0.0.1/8 address is still present. Now, run the
  same commands again:

   $ netplan apply
   $ ip addr show dev lo

  * On an affected system, observe that the 127.0.0.1/8 address is now
  gone. On a patched system, the address should still be present.

  [Where problems could occur]

  The patch removes cases where systemd-networkd will drop foreign
  addresses from a managed link. If problems were to occur, it would be
  related to the addresses configured on a managed link.

  [Original Description]

  If you configure the loopback interface using netplan without listing
  the standard loopback addresses (127.0.0.1 / ::1) that are auto-
  configured on boot then they are removed by netplan in r104+ but were
  not in r103.

  Confusingly this only happens the second time "netplan apply" is
  invoked and not the first time.

  There is some argument this is not a valid configuration, however
  - It worked on r103 and broke in the r104 SRU for 20.04 and breaks on upgrade
  - Since it only occurs on the second "netplan apply" it is likely people will 
accidentally create a configuration that on first verification works but breaks 
later
  - Adding addresses to a loopback or dummy interface is a common need
  - There is no dummy interface support in Netplan
  - Removing the loopback IP doesn't immediately cause obvious breakage in an 
SSH session but causes all sorts of hard to diagnose issues with applications

  Thus I consider this a high priority regression because of the
  multiple ways this can break a system at an unexpected/unrelated time
  to when the original change was made.

  As a workaround you can add 127.0.0.1/::1 to the file and this seems
  to generally work and product almost the same configuration with the
  exception that "brd 127.255.255.255" is added to the "ip addr" output
  compared to the auto-created configuration. All of the different
  routing tables seem otherwise the tame.

  = Test Case =
  (1) Add IP configuration for lo to /etc/netplan/lo.yaml

  lo:
    match:
  name: lo
    addresses:
    - 10.10.10.17/24
    - 10.10.10.19/24

  (2) Run "netplan apply" and observe the "ip addr show dev lo" output. 
Expected: 127.0.0.1/::1 are still there.
  (3) Run "netplan apply" a second time and observe the "ip addr show dev lo" 
output. Expected: 127.0.0.1/::1 are now removed.
  (4) Repeat the same test under netplan r103. Expected: 127.0.0.1/::1 are 
still there in both cases.

  = Observations =

  I found this change of behaviour happens only in r104. It is suspected
  but not clear that this is due to the configuraiton diffing behaviour
  introduced in r104. It's not clear to me why it doesn't happen on the
  first "netplan apply".

  I also found a recent upstream systemd commit to prevent networkd removing 
127.0.0.1/::1 which solves this issue on r104 as well. It's possible this is a 
better fix to backport to solve this:
  
https://github.com/systemd/systemd/commit/b69bfa43052586cd6894c32d7d3d447195539ec5

  Reverting to r103 *or* running a newer systemd with that patch
  resolves the issue on 20.04 and 22.04 in my testing.

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


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

[Touch-packages] [Bug 1992430] Re: Snap based apps crash after 5.19.0-18->5.19.0-19 kernel upgrade

[Richard Baka]

** Package changed: ubuntu => apparmor (Ubuntu)

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

Title:
  Snap based apps crash after 5.19.0-18->5.19.0-19 kernel upgrade

Status in apparmor package in Ubuntu:
  New

Bug description:
  This occurs on Ubuntu ver. 22.10.
  Here is an example:

  skype 
  update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.skype /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied
  + [ -f /home/user/snap/skype/common/.config/skypeforlinux/settings.json ]
  + export SKYPE_LOGS=/home/user/snap/skype/231/logs
  + [ ! -d /home/user/snap/skype/231/logs ]
  + exec /snap/skype/231/usr/share/skypeforlinux/skypeforlinux

  (skypeforlinux:9439): Gtk-WARNING **: 10:13:12.251: Theme parsing error: 
gtk.css:3536:25: 'font-feature-settings' is not a valid property name
  Gtk-Message: 10:13:12.294: Failed to load module "colorreload-gtk-module"
  Gtk-Message: 10:13:12.295: Failed to load module 
"window-decorations-gtk-module"
  [1011/101312.442717:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Permission 
denied (13)
  Nyomkövetési/töréspont csapda (core készült)

  Google translation: Trace/breakpoint trap (core made)

  Here is an another one:
  teams
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat 
/var/lib/snapd/hostfs/usr/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat 
/usr/local/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.teams /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied

  Loading of the previous kernel fixes the issue this is why I think it
  could be kernel-related or something like that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1992430/+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 1992306] Re: Default to a2dp ldac_hq codec for bluethooth headset and sound distorted

[Launchpad Bug Tracker]

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

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

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

Title:
  Default to a2dp ldac_hq codec for bluethooth headset and sound
  distorted

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I had some trouble getting my bluetooth headphones to work and I
  believe the culprit is the default codec that pulseaudio chooses. It
  appears to work ok when having no other Bluetooth devices connected,
  but when connecting a bluetooth mouse the audio gets distorted and
  begins to stutter. The offending codec is ldac_hq. I did some
  investigating today and found out you can change the codec in
  pavucontrol. Selecting ldac_sq seems to work without any issue.

  I don't know what the problem with ldac_hq is, maybe bandwidth? Wasn't
  able to find any obvious problems in the logs, even when enabling
  debugging in bluez.

  While investigating this I noticed others having the same issue, and
  it was difficult to find a way to change the codec, so maybe ldac_hq
  shouldn't be chosen as default?

  Headphones: Sony WF-1000XM
  Mouse: Logitech M590
  Computer: 
https://www.asus.com/Laptops/For-Home/Zenbook/Zenbook-S-UX391/techspec/

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 27c6:5201 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
  Bus 001 Device 002: ID 13d3:56b9 IMC Networks USB2.0 HD UVC WebCam
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  description: Bluetooth wireless interface
 product: Bluetooth wireless interface
 vendor: Intel Corp.
 physical id: 8
 bus info: usb@1:8
 version: 0.10
 capabilities: bluetooth usb-2.00
 configuration: driver=btusb maxpower=100mA speed=12Mbit/s

  Ubuntu 22.04.1 LTS
  pulseaudio: 1:15.99.1+dfsg1-1ubuntu1
  bluez: 5.64-0ubuntu1
  pavucontrol: 5.0-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1992306/+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 1992430] [NEW] Snap based apps crash after 5.19.0-18->5.19.0-19 kernel upgrade

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This occurs on Ubuntu ver. 22.10.
Here is an example:

skype 
update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.skype /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied
+ [ -f /home/user/snap/skype/common/.config/skypeforlinux/settings.json ]
+ export SKYPE_LOGS=/home/user/snap/skype/231/logs
+ [ ! -d /home/user/snap/skype/231/logs ]
+ exec /snap/skype/231/usr/share/skypeforlinux/skypeforlinux

(skypeforlinux:9439): Gtk-WARNING **: 10:13:12.251: Theme parsing error: 
gtk.css:3536:25: 'font-feature-settings' is not a valid property name
Gtk-Message: 10:13:12.294: Failed to load module "colorreload-gtk-module"
Gtk-Message: 10:13:12.295: Failed to load module "window-decorations-gtk-module"
[1011/101312.442717:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Permission 
denied (13)
Nyomkövetési/töréspont csapda (core készült)

Google translation: Trace/breakpoint trap (core made)

Here is an another one:
teams
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat 
/var/lib/snapd/hostfs/usr/share/fonts: permission denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat 
/usr/local/share/fonts: permission denied
update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.teams /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied

Loading of the previous kernel fixes the issue this is why I think it
could be kernel-related or something like that.

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


** Tags: bot-comment
-- 
Snap based apps crash after 5.19.0-18->5.19.0-19 kernel upgrade
https://bugs.launchpad.net/bugs/1992430
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apparmor in Ubuntu.

-- 
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 1992306] Re: Default to a2dp ldac_hq codec for bluethooth headset and sound distorted

[jixbo]

I can confirm the issue on Ubuntu 22.04, with an Intel Wi-Fi 6 AX200
wireless card.

I have had the issue for a while with my Sony WH-1000XM3, but just
realised it is a codec issue when connected a Sony SRS-XB41.

All other codecs, SBC and LDAC for various qualities, work fine. The
issue is only with LDAC HQ, which is the one selected by default. The
issue only happens when I have my bluetooth mouse connected.

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

Title:
  Default to a2dp ldac_hq codec for bluethooth headset and sound
  distorted

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I had some trouble getting my bluetooth headphones to work and I
  believe the culprit is the default codec that pulseaudio chooses. It
  appears to work ok when having no other Bluetooth devices connected,
  but when connecting a bluetooth mouse the audio gets distorted and
  begins to stutter. The offending codec is ldac_hq. I did some
  investigating today and found out you can change the codec in
  pavucontrol. Selecting ldac_sq seems to work without any issue.

  I don't know what the problem with ldac_hq is, maybe bandwidth? Wasn't
  able to find any obvious problems in the logs, even when enabling
  debugging in bluez.

  While investigating this I noticed others having the same issue, and
  it was difficult to find a way to change the codec, so maybe ldac_hq
  shouldn't be chosen as default?

  Headphones: Sony WF-1000XM
  Mouse: Logitech M590
  Computer: 
https://www.asus.com/Laptops/For-Home/Zenbook/Zenbook-S-UX391/techspec/

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 27c6:5201 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
  Bus 001 Device 002: ID 13d3:56b9 IMC Networks USB2.0 HD UVC WebCam
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  description: Bluetooth wireless interface
 product: Bluetooth wireless interface
 vendor: Intel Corp.
 physical id: 8
 bus info: usb@1:8
 version: 0.10
 capabilities: bluetooth usb-2.00
 configuration: driver=btusb maxpower=100mA speed=12Mbit/s

  Ubuntu 22.04.1 LTS
  pulseaudio: 1:15.99.1+dfsg1-1ubuntu1
  bluez: 5.64-0ubuntu1
  pavucontrol: 5.0-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1992306/+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 1988270] Re: AppArmor fails to start with Yoga UCA libvirt profile on Focal

[Ponnuvel Palaniyappan]

** Tags added: sts

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

Title:
  AppArmor fails to start with Yoga UCA libvirt profile on Focal

Status in Ubuntu Cloud Archive:
  Confirmed
Status in apparmor package in Ubuntu:
  Invalid
Status in apparmor source package in Focal:
  New

Bug description:
  On a fully patched Ubuntu Focal with Yoga UCA enabled, after
  installation of libvirt-daemon-system, restarting apparmor would fail
  with error:

  Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6335]: Restarting 
AppArmor
  Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6335]: Reloading 
AppArmor profiles
  Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6341]: Skipping 
profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6348]: AppArmor 
parser error for /etc/apparmor.d in /etc/apparmor.d/usr.sbin.libvirtd at line 
29: Invalid capability bpf.
  Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6413]: AppArmor 
parser error for /etc/apparmor.d/usr.sbin.libvirtd in 
/etc/apparmor.d/usr.sbin.libvirtd at line 29: Invalid capability bpf.
  Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6418]: Skipping 
profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6335]: Error: At 
least one profile failed to load
  Aug 31 07:40:52 ubuntu2004.localdomain systemd[1]: apparmor.service: Main 
process exited, code=exited, status=1/FAILURE
  Aug 31 07:40:52 ubuntu2004.localdomain systemd[1]: apparmor.service: Failed 
with result 'exit-code'.
  Aug 31 07:40:52 ubuntu2004.localdomain systemd[1]: Failed to start Load 
AppArmor profiles.

  In addition to bpf, perfmon capability, which is also enabled in
  /etc/apparmor.d/usr.sbin.libvirtd profile, would lead to the same
  error.

  System information:
  root@ubuntu2004:~# uname -a
  Linux ubuntu2004.localdomain 5.4.0-125-generic #141-Ubuntu SMP Wed Aug 10 
13:42:03 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
  root@ubuntu2004:~# dpkg -l libvirt\*
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version 
Architecture Description
  
+++-==-===--=
  ii  libvirt-clients8.0.0-1ubuntu7.1~cloud0 amd64  
  Programs for the libvirt library
  ii  libvirt-daemon 8.0.0-1ubuntu7.1~cloud0 amd64  
  Virtualization daemon
  ii  libvirt-daemon-config-network  8.0.0-1ubuntu7.1~cloud0 all
  Libvirt daemon configuration files (default network)
  ii  libvirt-daemon-config-nwfilter 8.0.0-1ubuntu7.1~cloud0 all
  Libvirt daemon configuration files (default network filters)
  un  libvirt-daemon-driver-lxc 
  (no description available)
  ii  libvirt-daemon-driver-qemu 8.0.0-1ubuntu7.1~cloud0 amd64  
  Virtualization daemon QEMU connection driver
  un  libvirt-daemon-driver-storage-gluster 
  (no description available)
  un  libvirt-daemon-driver-storage-iscsi-direct
  (no description available)
  un  libvirt-daemon-driver-storage-rbd 
  (no description available)
  un  libvirt-daemon-driver-storage-zfs 
  (no description available)
  un  libvirt-daemon-driver-vbox
  (no description available)
  un  libvirt-daemon-driver-xen 
  (no description available)
  ii  libvirt-daemon-system  8.0.0-1ubuntu7.1~cloud0 amd64  
  Libvirt daemon configuration files
  ii  libvirt-daemon-system-systemd  8.0.0-1ubuntu7.1~cloud0 all
  Libvirt daemon configuration files (systemd)
  un  libvirt-daemon-system-sysv
  (no description available)
  un  libvirt-login-shell   
  (no description available)
  un  libvirt-sanlock   
  (no description available)
  ii  libvirt0:amd64 8.0.0-1ubuntu7.1~cloud0 amd64  
  library for interfacing with different virtualization systems
  root@ubuntu2004:~# dpkg -l apparmor\*
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ NameVersion   Architecture Descripti

[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Daniel van Vugt]

Workaround:

You can usually install Ubuntu on a drive in one machine and then move
the drive into another machine.

At least I think that's what I did on the affected machine with 22.04,
which is why I never discovered this bug until 22.10 development
started.

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If 

Re: [Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Peter-and-Crazybear]

When is this going to be fixed and is there a work-around. I have tried 
both updating from 20.04 and direct installation of 22.04 and have found 
this problem preventing me from using 22.04 [it never boots]. I have two 
computers. One is a Dell with nvidia drivers [the perfect target machine 
to show this problem] - and it fails, but I also have a desktop I built 
myself that should not have problems [and obviously some having 
installed 22.04 do NOT have problems, but I do - and can not tell you 
what component is the problem [hardware or software]. Somewhere I read 
that making some spaces larger for the possible 'expansion' to not cause 
problems, but can not find it now with all of the many entries. I have 
spent MONTHS trying to install 22.04without success on either 
machine. I do not think you are correct that it only effects a small 
number of machines. Anyway, for those of us who it does, the problem is 
IMMENSE and total.

On 03/08/2022 10:44, Julian Andres Klode wrote:
> Yes, grub will be fixed eventually, but we are blocked by the security
> update not being out yet. This is not a blocker for enabling upgrades to
> 22.04.1, as it only affects a small number of systems and grub fixes
> itself by using the previous kernel version if the new one fails.
>

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/ris