[Touch-packages] [Bug 2054517] Re: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions

[Dave Jones]

This may be a duplicate of LP: #2037015 -- we saw this on mantic first,
then noble, in the oem-config process (the first-time setup wizard).
Previously it *didn't* affect jammy, but I'm currently running through
the ISO tests for the jammy .4 release and it's cropped up there now as
well.

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

Title:
  webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions

Status in mesa package in Ubuntu:
  New
Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions. Assuming
  it doesn't crash first.

  You first see the corruption in the initial setup wizard on first boot
  of noble-preinstalled-desktop-arm64+raspi.img.xz but the same
  corruption is then visible in the Help app on Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libwebkit2gtk-4.1-0 2.43.3-1
  ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3
  Uname: Linux 6.5.0-1005-raspi aarch64
  ApportVersion: 2.27.0-0ubuntu7
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Wed Feb 21 14:38:56 2024
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: webkit2gtk
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054517/+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 2054683] Re: Please merge lvm2 2.03.16-3 from Debian unstable.

[Dave Jones]

Attaching patch against Debian unstable. For ease of review, relevant
commits and tags have been pushed to the following repository:

https://code.launchpad.net/~waveform/ubuntu/+source/lvm2/+git/lvm2

Specifically:

* logical/2.03.16-2ubuntu1 represents our split-out delta on
  top of old/debian (2.03.16-2)
* logical/2.03.16-3ubuntu1 represents our rebased delta on
  top of new/debian (2.03.16-3)
* merge/2.03.16-3ubuntu1 adds changelog and maintainer
  changes on top of logical/2.03.16-3ubuntu1

Hence, the following command may produce output useful to the purposes
of review:

git range-diff --creation-factor=100
old/debian..logical/2.03.16-2ubuntu1
new/debian..logical/2.03.16-3ubuntu1


** Patch added: "1-2054683.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683/+attachment/5748479/+files/1-2054683.debdiff

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

Title:
  Please merge lvm2 2.03.16-3 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-3 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683/+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 2054683] [NEW] Please merge lvm2 2.03.16-3 from Debian unstable.

[Dave Jones]

Public bug reported:

Please merge lvm2 2.03.16-3 from Debian unstable.

Updated changelog and diff against Debian unstable to be attached below.

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

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

Title:
  Please merge lvm2 2.03.16-3 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-3 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683/+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 2054683] Re: Please merge lvm2 2.03.16-3 from Debian unstable.

[Dave Jones]

Test builds may be found in ppa:waveform/lvm2
(https://launchpad.net/~waveform/+archive/ubuntu/lvm2)

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/lvm2/+git/lvm2/+merge/461016

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

Title:
  Please merge lvm2 2.03.16-3 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-3 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683/+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 2054683] Re: Please merge lvm2 2.03.16-3 from Debian unstable.

[Dave Jones]

Created MP as suggested by Bryce on the last merge (LP: #2020464)

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

Title:
  Please merge lvm2 2.03.16-3 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-3 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

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


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

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

[Dave Jones]

> If you have a bunch of unmanaged interfaces, then you should use a
> drop-in configuration to pass the --any flag to
> systemd-networkd-wait-online:
> 
> cat > /etc/systemd/system/systemd-networkd-wait-online.service.d/any.conf << 
> EOF
> [Service]
> ExecStart=
> ExecStart=/lib/systemd/systemd-networkd-wait-online --any
> EOF
> 
> This makes it so that systemd-networkd-wait-online will return success once 
> at least one interface becomes configured.

Unfortunately this doesn't appear to work. I've tried this on the
current noble dailies (which also suffer the 2 minute boot delay on
the server images due to this issue). The default netplan config is
simply:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
optional: true

This displays the issue, even with --any presumably because wlan0 is
unmanaged so networkctl reports the online state is "unknown" (even
when eth0 is happily configured and routable).

I attempting making wlan0 "managed" but optional. This requires a
mandatory access point to be defined to conform to the YAML schema, so
I added a fake one (I should open a separate issue for this because I
shouldn't have to make up access points just to mark an interface
optional):

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
optional: true
wifis:
  wlan0:
dhcp4: true
optional: true
access-points:
  foo:
password: foobarbaz

Unfortunately this also displays the issue. This time wlan0 is
managed, but "configuring" and the online state is still "unknown". So
far as I can tell, the --any option doesn't match the behaviour
claimed in the man-page (i.e. "exits with success when at least one
interface becomes online").

> There is no workaround for this with the stock netplan config on
> raspberry pi, which trips this bug. But you can customize
> /etc/netplan/ on your system to mark your expected/required network
> interfaces as "optional: false" (which is the default if
> unspecified); AIUI that would avoid this issue with
> systemd-networkd.

This *does* work ... assuming the Pi actually has a network interface.
If the Pi is networkless, it's unfortunately doomed to the 2 minute
delay still. And obviously I don't want to make eth0 mandatory by
default in the images (which would break the 3A+ and Zero 2W, which
lack eth0 entirely).

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

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

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Fix Released

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SR

[Touch-packages] [Bug 2057927] Re: lxd vga console throws "Operation not permitted" error

[Dave Jones]

I see a basically identical message (and dmesg apparmor output) with
"lxc profile edit default":

  unshare: write failed /proc/self/uid_map: Operation not permitted

And the dmesg entry:

  [  194.625507] audit: type=1400 audit(1711709095.424:293):
apparmor="DENIED" operation="capable" class="cap"
profile="unprivileged_userns" pid=6885 comm="unshare" capability=21
capname="sys_admin"

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

Title:
  lxd vga console throws "Operation not permitted" error

Status in apparmor package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Confirmed

Bug description:
  Since I upgraded to Noble the lxd vga console doesn't work anymore. I
  am using the lxd latest/stable snap (5.20-f3dd836). When trying to
  attach a vga console to an lxd vm I get:

  unshare: write failed /proc/self/uid_map: Operation not permitted

  It seems to be related to apparmor, I can see a matching DENIAL
  message in dmesg:

  [ 4735.233989] audit: type=1400 audit(1710419600.517:300):
  apparmor="DENIED" operation="capable" class="cap"
  profile="unprivileged_userns" pid=13157 comm="unshare" capability=21
  capname="sys_admin"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057927/+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 2060693] [NEW] No login sound on Ubuntu desktop

[Dave Jones]

Public bug reported:

Under the Ubuntu desktop for Raspberry Pi, for several recent releases,
the startup sound from the Yaru sound theme has failed to play both at
the initial setup (from oem-config, where it used to play just before
language selection), and at the greeter.

This worked in Jammy (22.04), but on at least mantic (23.10) and the
forthcoming noble (24.04) (and possibly earlier), this has failed. It's
not due to a crash in canberra-gtk-play (used to play the sound). The
only hint that something has failed appears in the oem-config.log:

  Failed to play sound: Not available

Unfortunately there's nothing else in the log that hints at why
canberra-gtk-play is failing.

There are several similar bug report, but I doubt they are related given
their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a very
different sound stack and predates the preinstalled desktop images).

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

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

Title:
  No login sound on Ubuntu desktop

Status in libcanberra package in Ubuntu:
  New

Bug description:
  Under the Ubuntu desktop for Raspberry Pi, for several recent
  releases, the startup sound from the Yaru sound theme has failed to
  play both at the initial setup (from oem-config, where it used to play
  just before language selection), and at the greeter.

  This worked in Jammy (22.04), but on at least mantic (23.10) and the
  forthcoming noble (24.04) (and possibly earlier), this has failed.
  It's not due to a crash in canberra-gtk-play (used to play the sound).
  The only hint that something has failed appears in the oem-config.log:

Failed to play sound: Not available

  Unfortunately there's nothing else in the log that hints at why
  canberra-gtk-play is failing.

  There are several similar bug report, but I doubt they are related
  given their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a
  very different sound stack and predates the preinstalled desktop
  images).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/2060693/+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 2037015] Re: Screen corruption of slides during install on Raspberry Pi 4

[Dave Jones]

There's an intriguingly different style of corruption in the noble
images on the Pi 5. It's still just on the installer's slides, but it's
more ... "chunky"? I'll attach a photo...

** Attachment added: "slide-corruption-2.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2037015/+attachment/5762908/+files/slide-corruption-2.jpg

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

Title:
  Screen corruption of slides during install on Raspberry Pi 4

Status in mesa package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  During the initial configuration of the Ubuntu Desktop for Raspberry
  Pi (the oem-config process, derived from ubiquity), on the Mantic beta
  images, after the various pages of information have been filled out
  and the process moves onto configuration, the "slide deck" that is
  usually displayed during the process appeared corrupted as if a
  horizontal stride were incorrectly set somewhere.

  I'm attached a photo of the screen (as, while I could take a
  screenshot during the process, it evidently wasn't saved somewhere
  persistent).

  I originally thought this might be a regression of LP: #1924251 as the
  corruption in the window looks very similar (incorrect horizontal
  stride causing "banding"), but I tested the embedded browser (via the
  help system) after completing setup and it worked perfectly so that's
  *probably* unrelated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037015/+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 2060730] Re: totem cannot install codecs via packagekit

[Dave Jones]

Adding affects packagekit as I've no idea if this is totem's fault or
packagekit's.

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

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

Title:
  totem cannot install codecs via packagekit

Status in packagekit package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit. This is strange
  given that packagekit is installed, provides packagekit.service, which
  declares that it provides that name over DBus. Specifically, the
  following is output by totem:

  ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC 
decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, 
base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
  ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main 
Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main 
(H.264 (Main Profile) decoder)
  ** Message: 21:13:39.414: PackageKit: xid = 0
  ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
  ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
  ** Message: 21:13:39.414: PackageKit: ignoring field named level
  ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
  ** Message: 21:13:39.414: PackageKit: ignoring field named profile
  ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
  ** Message: 21:13:39.414: PackageKit: structure: 
gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
  ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main 
Profile) decoder
  ** Message: 21:13:39.414: PackageKit: ignoring field named level
  ** Message: 21:13:39.414: PackageKit: ignoring field named profile
  ** Message: 21:13:39.414: PackageKit: structure: 
gstreamer1(decoder-video/x-h264)()(64bit)
  ** Message: 21:13:39.434: PackageKit: Did not install codec: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.PackageKit was not provided by any .service files
  ** Message: 21:13:39.441: No installation candidate for missing plugins 
found.

  The packagekit.service is defined as:

  $ systemctl cat packagekit.service
  # /usr/lib/systemd/system/packagekit.service
  [Unit]
  Description=PackageKit Daemon
  # PK doesn't know how to do anything on ostree-managed systems;
  # currently the design is to have dedicated daemons like
  # eos-updater and rpm-ostree, and gnome-software talks to those.
  ConditionPathExists=!/run/ostree-booted
  Wants=network-online.target
  
  [Service]
  Type=dbus
  BusName=org.freedesktop.PackageKit
  User=root
  ExecStart=/usr/libexec/packagekitd

  And just to demonstrate packagekit is actually running:

  $ systemctl status packagekit.service
  ● packagekit.service - PackageKit Daemon
   Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static)
   Active: active (running) since Tue 2024-04-09 21:11:35 BST; 2min 23s 
ago
 Main PID: 1565 (packagekitd)
Tasks: 4 (limit: 3864)
   Memory: 6.2M (peak: 6.7M)
  CPU: 180ms
   CGroup: /system.slice/packagekit.service
   └─1565 /usr/libexec/packagekitd
  
  Apr 09 21:11:34 fozzie systemd[1]: Starting packagekit.service - 
PackageKit Daemon...
  Apr 09 21:11:34 fozzie PackageKit[1565]: daemon start
  Apr 09 21:11:35 fozzie systemd[1]: Started packagekit.service - 
PackageKit Daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2060730/+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 1942260] Re: compress firmware in /lib/firmware

[Dave Jones]

This was fixed with version 11 of linux-firmware-raspi in noble; I don't
see a great deal of point in expending the effort to backport this to
mantic, however, so I'll set that to invalid.

** Changed in: linux-firmware-raspi (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: linux-firmware-raspi (Ubuntu Mantic)
   Status: Confirmed => Won't Fix

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

Title:
  compress firmware in /lib/firmware

Status in firmware-sof package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware-raspi package in Ubuntu:
  Fix Released
Status in firmware-sof source package in Mantic:
  Fix Released
Status in initramfs-tools source package in Mantic:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware-raspi source package in Mantic:
  Won't Fix

Bug description:
  -- initramfs-tools

  [Impact]

   * linux supports xz compressed linux-firmware which saves disk space.
  In focal, initramfs-tools only knows how to included uncompressed
  firmware files (even when kernel supports loading compressed ones).
  Newer releases of linux-firmware may use compressed firmware files
  only, in such cases it would be nice for focal's initramfs-tools to
  support compressed firmware files in case of partial or incomplete
  upgrades (i.e. linux-firmware force installed or upgraded, without
  newer initramfs-tools). The proposed changes to initramfs-tools are
  backwards and forwards compatible, they prefer to include uncompressed
  firmware files; and if missing, include compressed firmware files in
  their uncompressed form. Thus maintaining compatibility with any
  kernels, irrespective of compressed/uncompressed firmware inputs.

  [Test Plan]

   * Compress all files shipped by linux-firmware with xz

   * Rebuild initrd

   * Check that all the same firmware files are still included in the
  initramfs, in their uncompressed form as before

  [Where problems could occur]

   * This SRU is precautionary to prevent accidental installation of
  compressed linux-firmware from generating incorrect initramfs. It
  should be noted that whilst initramfs-tools would create a compatible
  initramfs with any kernels, pre-v5.3 kernels do not support xz
  compressed firmware files at runtime. Mixing this new initramfs with
  compressed firmwares and pre 5.3 kernels may lead to expectations of
  supporting compressed firmware files with them only working at initrd
  stage and not at runtime.

  [Other Info]
  Original bug report

  Some facts:
   - The linux kernel has supported loading xz compressed firmware since 5.3
   - The size of /lib/firmware in impish is ~650Mb (and growing)
   - The compressed size of firmware could be ~230Mb

  It would be nice to install compressed firmware to save space.

  Here are the plans from the Fedora project:
  https://fedoraproject.org/wiki/Changes/CompressKernelFirmware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1942260/+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 2060693] Re: No welcome/login sound on Ubuntu desktop

[Dave Jones]

** Summary changed:

- No login sound on Ubuntu desktop
+ No welcome/login sound on Ubuntu desktop

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

Title:
  No welcome/login sound on Ubuntu desktop

Status in libcanberra package in Ubuntu:
  New

Bug description:
  Under the Ubuntu desktop for Raspberry Pi, for several recent
  releases, the startup sound from the Yaru sound theme has failed to
  play both at the initial setup (from oem-config, where it used to play
  just before language selection), and at the greeter.

  This worked in Jammy (22.04), but on at least mantic (23.10) and the
  forthcoming noble (24.04) (and possibly earlier), this has failed.
  It's not due to a crash in canberra-gtk-play (used to play the sound).
  The only hint that something has failed appears in the oem-config.log:

Failed to play sound: Not available

  Unfortunately there's nothing else in the log that hints at why
  canberra-gtk-play is failing.

  There are several similar bug report, but I doubt they are related
  given their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a
  very different sound stack and predates the preinstalled desktop
  images).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/2060693/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Dave Jones]

Bah, looks like this upload got accidentally dropped by the subsequent
merge for noble. I'll rebase and re-proposed it when I've got some
time...

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

** Changed in: bash (Ubuntu)
 Assignee: Dan Bungert (dbungert) => Dave Jones (waveform)

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  New
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

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

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 2060730] Re: totem cannot install codecs via packagekit

[Dave Jones]

Sorry, I should give a bit more context on this issue to clarify things.
The test for this issue comes from the ISO tests for the Ubuntu Desktop
for Raspberry Pi images. The test intends to check whether a fresh
install can play a video "out of the box". The video used in the test is
https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4
which is downloaded and opened normally.

The video deliberately uses a codec that isn't seeded and installed by
default (but is a commonly used format) in the expectation that totem
will guide the user through installing the necessary bits (which it used
to back in groovy, but doesn't since -- incidentally the reason this
wasn't noticed in jammy is because it failed to even open the video at
that point, but that's now been fixed).

Seeding gstreamer1.0-packagekit is probably fine (the whole of
gstreamer's in main). Seeding gnome-software is likely not (given we're
using snap-store for software delivery currently). Is app-center
intended to fill that gap in future?

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

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  Triaged
Status in packagekit package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit. This is strange
  given that packagekit is installed, provides packagekit.service, which
  declares that it provides that name over DBus. Specifically, the
  following is output by totem:

  ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC 
decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, 
base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
  ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main 
Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main 
(H.264 (Main Profile) decoder)
  ** Message: 21:13:39.414: PackageKit: xid = 0
  ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
  ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
  ** Message: 21:13:39.414: PackageKit: ignoring field named level
  ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
  ** Message: 21:13:39.414: PackageKit: ignoring field named profile
  ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
  ** Message: 21:13:39.414: PackageKit: structure: 
gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
  ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main 
Profile) decoder
  ** Message: 21:13:39.414: PackageKit: ignoring field named level
  ** Message: 21:13:39.414: PackageKit: ignoring field named profile
  ** Message: 21:13:39.414: PackageKit: structure: 
gstreamer1(decoder-video/x-h264)()(64bit)
  ** Message: 21:13:39.434: PackageKit: Did not install codec: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.PackageKit was not provided by any .service files
  ** Message: 21:13:39.441: No installation candidate for missing plugins 
found.

  The packagekit.service is defined as:

  $ systemctl cat packagekit.service
  # /usr/lib/systemd/system/packagekit.service
  [Unit]
  Description=PackageKit Daemon
  # PK doesn't know how to do anything on ostree-managed systems;
  # currently the design is to have dedicated daemons like
  # eos-updater and rpm-ostree, and gnome-software talks to those.
  ConditionPathExists=!/run/ostree-booted
  Wants=network-online.target
  
  [Service]
  Type=dbus
  BusName=org.freedesktop.PackageKit
  User=root
  ExecStart=/usr/libexec/packagekitd

  And just to demonstrate packagekit is actually running:

  $ systemctl status packagekit.service
  ● packagekit.service - PackageKit Daemon
   Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static)
   Active: active (running) since Tue 2024-04-09 21:11:35 BST; 2min 23s 
ago
 Main PID: 1565 (packagekitd)
Tasks: 4 (limit: 3864)
   Memory: 6.2M (peak: 6.7M)
  CPU: 180ms
   CGroup: /system.slice/packagekit.service
   └─1565 /usr/libexec/packagekitd
  
  Apr 09 21:11:34 fozzie systemd[1]: Starting packagekit.service - 
PackageKit Daemon...
  Apr 09 21:11:34 fozzie PackageKit[1565]: daemon start
  Apr 09 21:11:35 fozzie systemd[1]: Started packagekit.service - 
PackageKit Daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions


-- 
Mailing lis

[Touch-packages] [Bug 1097467] Re: bash does not fulfill --rcfile option properly

[Dave Jones]

Attaching new debdiff based on the current noble version.

** Patch added: "1097467-3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5766422/+files/1097467-3.debdiff

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  New
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

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

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 2062414] [NEW] busybox 1.36.1 FTBFS with current kernel headers on noble

[Dave Jones]

Public bug reported:

The networking/tc.c unit in busybox relies upon the CBQ (class based
queue) UAPI in the kernel. Unfortunately this was removed in [1]. At
present, there is no upstream patch (or even bug report that I can
find), and this close to the release patching the kernel to resolve
things is not going to happen. Will attach a patch re-instating the
defines from the removed headers.

[1]: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble/commit/?id=33241dca486264193ed68167c8eeae1fb197f3df

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


** Tags: rls-nn-incoming update-excuse

** Tags added: rls-nn-incoming

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

Title:
  busybox 1.36.1 FTBFS with current kernel headers on noble

Status in busybox package in Ubuntu:
  New

Bug description:
  The networking/tc.c unit in busybox relies upon the CBQ (class based
  queue) UAPI in the kernel. Unfortunately this was removed in [1]. At
  present, there is no upstream patch (or even bug report that I can
  find), and this close to the release patching the kernel to resolve
  things is not going to happen. Will attach a patch re-instating the
  defines from the removed headers.

  [1]: https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/noble/commit/?id=33241dca486264193ed68167c8eeae1fb197f3df

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+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 2062414] Re: busybox 1.36.1 FTBFS with current kernel headers on noble

[Dave Jones]

** Patch added: "1-2062414.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+attachment/5767655/+files/1-2062414.debdiff

** Tags added: update-excuse

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

Title:
  busybox 1.36.1 FTBFS with current kernel headers on noble

Status in busybox package in Ubuntu:
  New

Bug description:
  The networking/tc.c unit in busybox relies upon the CBQ (class based
  queue) UAPI in the kernel. Unfortunately this was removed in [1]. At
  present, there is no upstream patch (or even bug report that I can
  find), and this close to the release patching the kernel to resolve
  things is not going to happen. Will attach a patch re-instating the
  defines from the removed headers.

  [1]: https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/noble/commit/?id=33241dca486264193ed68167c8eeae1fb197f3df

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+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 2062414] Re: busybox 1.36.1 FTBFS with current kernel headers on noble

[Dave Jones]

Revised patch with upstream bug links

** Patch added: "2-2062414.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+attachment/5767659/+files/2-2062414.debdiff

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

Title:
  busybox 1.36.1 FTBFS with current kernel headers on noble

Status in busybox package in Ubuntu:
  New

Bug description:
  The networking/tc.c unit in busybox relies upon the CBQ (class based
  queue) UAPI in the kernel. Unfortunately this was removed in [1]. At
  present, there is no upstream patch (or even bug report that I can
  find), and this close to the release patching the kernel to resolve
  things is not going to happen. Will attach a patch re-instating the
  defines from the removed headers.

  [1]: https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/noble/commit/?id=33241dca486264193ed68167c8eeae1fb197f3df

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+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 2062414] Re: busybox 1.36.1 FTBFS with current kernel headers on noble

[Dave Jones]

Build reference:
https://launchpad.net/ubuntu/+source/busybox/1:1.36.1-6ubuntu2/+build/28036868

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

Title:
  busybox 1.36.1 FTBFS with current kernel headers on noble

Status in busybox package in Ubuntu:
  New

Bug description:
  The networking/tc.c unit in busybox relies upon the CBQ (class based
  queue) UAPI in the kernel. Unfortunately this was removed in [1]. At
  present, there is no upstream patch (or even bug report that I can
  find), and this close to the release patching the kernel to resolve
  things is not going to happen. Will attach a patch re-instating the
  defines from the removed headers.

  [1]: https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/noble/commit/?id=33241dca486264193ed68167c8eeae1fb197f3df

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+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 2062564] Re: [FFe] Seed pemmican

[Dave Jones]

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/463674

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

Title:
  [FFe] Seed pemmican

Status in pemmican package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  [ Impact ]

  Add pemmican to raspi server and desktop images in order that Pi 5
  users can be notified if/when overcurrent or undervolt events occur
  (potentially resulting in brownout, data-corruption, and all manner of
  other symptoms typically caused as a result of undervolt).

  [ Test Plan ]

  On all supported models of Pi:
  * Boot the image with pemmican installed
  * Ensure boot proceeds normally with package installed and that no warnings 
appear

  On the Pi 5 specifically:
  * Boot the image normally
  * Ensure boot proceeds normally with package installed and that no warnings 
appear
  * Using bench power-supply to back-feed the Pi, lower voltage until brownout 
occurs
  * Reboot and ensure undervolt warning is shown
  * Shutdown and boot with PSU that cannot negotiate 5A
  * Ensure deficient PSU warning is shown

  On the Pi 5 desktop image specifically:
  * Boot desktop image
  * Attach USB load tester and raise current draw until USB ports fail
  * Ensure overcurrent warning is displayed

  [ Regression Potential ]

  Quite low given all the tests noted above have already been performed
  on all supported models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2062564/+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 2062414] Re: busybox 1.36.1 FTBFS with current kernel headers on noble

[Dave Jones]

** Bug watch added: Busybox Bugzilla #16042
   https://bugs.busybox.net/show_bug.cgi?id=16042

** Also affects: busybox via
   https://bugs.busybox.net/show_bug.cgi?id=16042
   Importance: Unknown
   Status: Unknown

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

Title:
  busybox 1.36.1 FTBFS with current kernel headers on noble

Status in BusyBox:
  Unknown
Status in busybox package in Ubuntu:
  Fix Released

Bug description:
  The networking/tc.c unit in busybox relies upon the CBQ (class based
  queue) UAPI in the kernel. Unfortunately this was removed in [1]. At
  present, there is no upstream patch (or even bug report that I can
  find), and this close to the release patching the kernel to resolve
  things is not going to happen. Will attach a patch re-instating the
  defines from the removed headers.

  [1]: https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/noble/commit/?id=33241dca486264193ed68167c8eeae1fb197f3df

To manage notifications about this bug go to:
https://bugs.launchpad.net/busybox/+bug/2062414/+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 2062667] Re: Fails on (and should be removed from) raspi desktop

[Dave Jones]

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

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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

[Dave Jones]

I'll take a shot at responding to @seb128's questions:

Why is this a rls issue in the LTS?
===

Prior to jammy, the crda database was in userland, and the crda package
provided a means (via editing /etc/default/crda) to persist the wireless
region across reboots. From jammy onwards, the regulatory database is
now baked into the kernel, and the crda package is gone (from Debian
upstream and from Ubuntu). There is now no mechanism to set the wifi
regulatory region that will persist across reboots on either server or
desktop (iw reg set is transitory).

It appears (see comments 16 thru 19 above) that under *some*
circumstances, with some APs that wpa-supplicant does correctly
determine the wifi region, and sets it automatically (though the user
has no way of knowing this other than digging through wpa-supplicant's
logs). However, I'm not convinced this is terribly reliable -- it's
apparently never worked for me at home or at various friends houses, and
only once worked when I travelled to Germany for a sprint.

There is currently (in jammy onwards) one hacky way of ensuring the
region is set on each reboot (from comment 12 above): set
"cfg80211.ieee80211_regdom" on the kernel command line. Obviously this
isn't terribly user friendly!

That covers the deficiency, which is new to jammy, but why is setting
the regulatory region particularly important? In the 2.4GHz band [1],
there's a "world" region which covers the vast majority of the available
bands (1 thru 11). So for older wifi hardware, defaulting to the "world"
region doesn't result in *much* limitation (though it does mean European
users can't use bands 12 or 13, and Japanese users don't get their
wonderfully separate band 14).

However, the 5GHz band [2] is a considerably different story. For
starters, there's a great deal more variation in which channels are
available in which regions. Moreover, certain channels have specific
limitations in certain regions. Some require radar detection or
mitigation mechanisms to ensure that 5GHz capable wifi devices don't
interfere with certain radar applications [3]. Others require that
certain channels are strictly for indoor use only. Leaving one's wifi
device in the "world/unset" state for 5GHz typically results in a more
limited experience than it does for 2.4GHz devices [4].

Then, of course, there's the legal aspect. I'm not qualified to comment
on the relevant regulations around the globe but the section "Helping
compliance by allowing to change regulatory domains" under [5] contains
some interesting notes on the fact that wifi devices have both a
"programmed" regulatory domain and a "selected" region (the latter is
affected by crda) which can only *enhance* restrictions. That said, this
is likely important from a legal perspective for those travelling with
wifi capable equipment between countries with differing regulatory
requirements.

[1]: 
https://en.wikipedia.org/wiki/List_of_WLAN_channels#2.4_GHz_(802.11b/g/n/ax)
[2]: 
https://en.wikipedia.org/wiki/List_of_WLAN_channels#5_GHz_(802.11a/h/j/n/ac/ax)
[3]: https://en.wikipedia.org/wiki/Dynamic_frequency_selection
[4]: 
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1851129/comments/1
[5]: 
https://wireless.wiki.kernel.org/en/developers/Regulatory/CRDA#helping_compliance_by_allowing_to_change_regulatory_domains


What's the intended priority?
=

Given this relates to legal requirements in many jurisdictions (again,
I'm not qualified to comment on these specifically, but I don't think
there's any argument that legal restrictions are at least present),
would suggest this should be a reasonably high priority. The counter-
point would be: it would appear there's been *never* been a graphical
interface for setting this and (I presume?) no jurisdiction has ever
complained about this.

However, the fact that the 5GHz experience (which is becoming more and
more common) is, in certain jurisdictions, significantly affected by
lacking this setting (because without setting the regulatory region,
users in such regions can't access a large number of channels) would
also suggest a reasonably high priority to me.


What's the impact?
==

Hopefully covered in the prior sections.


What do we expect to be changed?


At a bare minimum some mechanism for persisting a selected wifi
regulatory domain is required, both on server images (via netplan) and
desktop images (via network manager). During boot, some mechanism should
restore the wifi regulatory domain from this persistent location.

There's some nuance here over whether an AP's broadcast region (if any)
should take precedence over the persistent setting, and when exactly the
restoration of the setting should occur (i.e. particularly in the server
case, whether wifi should only be enabled strictly *after* restoration
of this setting). There's probably more questions around this setting
I'm not th

[Touch-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain

[Dave Jones]

>> it's apparently never worked for me at home or at various friends
>> houses, and only once worked when I travelled to Germany for a
>> sprint.

> is that having a visible impact for users? like was your computer
> not able to connect to some access point?

Personally, I've never encountered issues with WiFi on a Pi. However,
firstly it's worth noting the vast majority of pis around my house are
connected via ethernet and, secondly that my broadband connection
typically hovers around 60-80Mbps, so the 54Mbps max bandwidth of
802.11g is "fast enough" that anything more wouldn't be noticed
anyway.

Notably, this also means I *don't* use bonded 5GHz channels in my home
setup. The reason I mention this is that, over the last few years
there's been a slow (but steady) drum-beat of complaints about WiFi on
the Pi when using Ubuntu [1][2][3][4] (some of those are comments from
the same bug, but it seems to be one that people land on when googling
this for Ubuntu). 

[1]: 
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1851129/comments/1
[2]: 
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1862760/comments/11
[3]: 
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1862760/comments/29
[4]: https://bugs.launchpad.net/netplan/+bug/1908951

> if that's the consequence of the issue it is a bit surprising that
> we got no user report of the type of 'my laptop isn't able to
> connect to my AP anymore since the upgrade to the new LTS' no? or is
> the issue somehow specific to raspi devices?

The complaint usually isn't "I can't connect to my AP anymore". It's
usually "my WiFi connection is slow" (which is obviously a much harder
problem to debug and address) but this does appear to be a problem
specific to the Pi.

Mostly though, this comes up on IRC, and it's a safe bet that the
person involved has a 5GHz setup, sometimes with bonded channels.
Obviously bonded channel setups require more (typically adjacent)
channels and this makes them particularly susceptible to poor
performance when the region code hasn't been set (and the channels, or
channel mitigations are limited). With pure 5GHz APs (no 2.4GHz
channels at all) we've also had reports of no connectivity.

One other (anecdotal) observation is that despite RaspiOS having a
considerably larger installed base of Ubuntu on the Pi, WiFi issues
rarely crop up there. Notably, RaspiOS prompts for a wifi regulatory
region in its first time setup. There are several other differences,
but under the covers we're using the same firmware, and wpa-supplicant
is ultimately in charge of the WiFi connection on both OS'.

Given 5GHz setups are only likely to become more common in future
(802.11ac, which the Pi 3+ and 4 are compatible with, is notably 5GHz
only [5]) my suspicion is this will only become more important in the
coming years.

[5]: https://en.wikipedia.org/wiki/IEEE_802.11ac-2013

-- 
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:
  New
Status in netplan.io package in Ubuntu:
  Triaged
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:
  Triaged
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 1951586] Re: Need option to specify wifi regulatory domain

[Dave Jones]

> It could be maybe added to NetworkManager, if somebody sends a
> patch. But it's not actually clear to me that this is really
> NetworkManager's task. Maybe it is, but what are the arguments for
> that?

I could be glib, and say "because the kernel says so [1]". However, I
suspect that's not a great reason :)

[1]:
https://wireless.wiki.kernel.org/en/developers/Regulatory/CRDA#using_network_manager_to_change_regulatory_domains

A more complete argument would be: it appears that, where possible,
wifi region selection is handled automatically by interpreting
information from the AP's beacon. However, that appears to be sparsely
implemented (at best) and in the (extremely common) event that an AP
*doesn't* advertise its region, it's up to the user to manage this
themselves (where/when needed; as noted above, in 2.4GHz setups this
usually doesn't matter that much).

All the underlying pieces are in place for the user to do so. Nothing
is lacking in wpa-supplicant regarding this (iwd does lack a direct
option for the wifi region but it appears "use ieee80211_regdom or iw
to override the automatic selection" is the answer there), so it's
"simply" a matter of exposing this configuration via their preferred
UI.

Command line users already have the tools to do this (iw), although
they notably lack a persistence mechanism for now. But GUI users have
... nothing. No means of querying, adjusting, or persisting this
setting.

Why NetworkManager?

This setting could arguably go under "Language and Region". It is
quite literally a region setting after all. And I'm still of the
opinion that, at least initially, it should be set from the region
selection during first-time setup.

But consider the debugging scenario: I've travelled from the UK to
Germany and, in the place I'm working, I'm having trouble with wifi
connectivity or performance. What settings do I look at first? The
wifi settings, almost certainly. If I were to see that my wifi region
was "unset" or "UK" I'd likely adjust that to "DE" and see if that
fixes things.

To me at least, it does seem to make sense for this to go under the
wifi settings (which are presumably the purview of NetworkManager?).

-- 
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:
  New
Status in NetworkManager:
  Unknown
Status in netplan.io package in Ubuntu:
  Triaged
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:
  Triaged
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 1951586] Re: Need option to specify wifi regulatory domain

[Dave Jones]

Sure -- I'll try not to drown them in verbiage :)

-- 
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:
  New
Status in NetworkManager:
  Unknown
Status in netplan.io package in Ubuntu:
  Triaged
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:
  Triaged
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 1977764] Re: kernel modules "zstd" and "z3fold" missing.

[Dave Jones]

Doh -- that one's my fault; included it in the kernel command line and
completely forgot to include a patch in ubuntu-raspi-settings to add it
to the set of modules for initramfs-tools to include in the initrd.

The workaround for now:

$ sudo -i
# echo zstd >> /etc/initramfs-tools/modules
# echo z3fold >> /etc/initramfs-tools/modules
# update-initramfs -u

I'll try and get this added to ubuntu-raspi-settings shortly.

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

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

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

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

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

** Changed in: initramfs-tools (Ubuntu Kinetic)
 Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: initramfs-tools (Ubuntu Jammy)
 Assignee: (unassigned) => Dave Jones (waveform)

** Also affects: ubuntu-settings (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: initramfs-tools (Ubuntu)

** No longer affects: initramfs-tools (Ubuntu Kinetic)

** No longer affects: initramfs-tools (Ubuntu Jammy)

** Changed in: ubuntu-settings (Ubuntu Jammy)
     Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: ubuntu-settings (Ubuntu Kinetic)
 Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  kernel modules "zstd" and "z3fold" missing.

Status in linux-raspi package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New
Status in linux-raspi source package in Jammy:
  New
Status in ubuntu-settings source package in Jammy:
  New
Status in linux-raspi source package in Kinetic:
  New
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  The modules "zstd" and "z3fold" are missing despite being configured
  for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot
  display that state they do not exist and so instead use compressor
  "lzo" and pool "zbud".

  Ubuntu version is 22.04 LTS flashed from the official image.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8
  ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30
  Uname: Linux 5.15.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  6 17:29:00 2022
  ImageMediaBuild: 20220419
  SourcePackage: linux-raspi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1977764/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.

[Dave Jones]

Oh, now I remember why this one was more complicated: it's for the pi
*desktop specifically*. Can't add this to ubuntu-raspi-settings directly
as that'll pull in zstd, z3fold, and all the zswap stuff on the server
images too, which increases the memory burden on the minimal Zero 2 and
3A+ platforms.

So (for my own notes): this requires the creation of a new ubuntu-raspi-
settings-desktop package (src:ubuntu-settings) and the addition of that
package to the desktop-raspi seed in the ubuntu seed repo.

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

Title:
  kernel modules "zstd" and "z3fold" missing.

Status in linux-raspi package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New
Status in linux-raspi source package in Jammy:
  New
Status in ubuntu-settings source package in Jammy:
  New
Status in linux-raspi source package in Kinetic:
  New
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  The modules "zstd" and "z3fold" are missing despite being configured
  for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot
  display that state they do not exist and so instead use compressor
  "lzo" and pool "zbud".

  Ubuntu version is 22.04 LTS flashed from the official image.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8
  ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30
  Uname: Linux 5.15.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  6 17:29:00 2022
  ImageMediaBuild: 20220419
  SourcePackage: linux-raspi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1977764/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot

[Dave Jones]

@seb128 tested with pipewire on kinetic with a Pi 4B and it correctly
selects the HDMI out by default both on initial setup and after a few
reboots. So, looks like this could be "invalid" on kinetic, at least for
the Raspberry Pi case. Would be useful to double-check that on PC
hardware too, obviously.

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

Title:
  switch-on-connect mistakes startup for USB hotplug, so seemingly
  ignores the old default device on reboot

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in ubuntu-settings package in Ubuntu:
  New
Status in pulseaudio source package in Kinetic:
  Triaged
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Only difference is that it does not reset to HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.

  In short:
  1. Boot system
  2. "Analogue Output - RODE NT-USB" is selected by default. I want to use 
"Line Out - Built-in Audio", which I choose.
  3. Reboot.
  4 Output device is now back to "Analogue Output - RODE NT-USB".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcus 1604 F pulseaudio
   /dev/snd/controlC0:  marcus 1604 F pulseaudio
   /dev/snd/controlC1:  marcus 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1814302] Re: Quasselcore apparmor profile issue in lxd container.

[Dave Jones]

Looks like this is back in jammy (and beyond); the sync from Debian
dropped the patch to d/usr.bin.quasselcore for lxd.

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

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

** Also affects: apparmor (Ubuntu Kinetic)
   Importance: Undecided
   Status: Invalid

** Also affects: quassel (Ubuntu Kinetic)
   Importance: Medium
 Assignee: Dan Streetman (ddstreet)
   Status: Fix Released

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

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

** Changed in: quassel (Ubuntu Kinetic)
 Assignee: Dan Streetman (ddstreet) => Dave Jones (waveform)

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

** Changed in: quassel (Ubuntu Jammy)
 Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  Quasselcore apparmor profile issue in lxd container.

Status in AppArmor:
  Invalid
Status in apparmor package in Ubuntu:
  Invalid
Status in quassel package in Ubuntu:
  Confirmed
Status in apparmor source package in Bionic:
  Invalid
Status in quassel source package in Bionic:
  Fix Released
Status in apparmor source package in Focal:
  Invalid
Status in quassel source package in Focal:
  Fix Released
Status in apparmor source package in Groovy:
  Invalid
Status in quassel source package in Groovy:
  Fix Released
Status in apparmor source package in Jammy:
  Invalid
Status in quassel source package in Jammy:
  Confirmed
Status in apparmor source package in Kinetic:
  Invalid
Status in quassel source package in Kinetic:
  Confirmed

Bug description:
  [impact]

  quasselcore cannot start inside lxd container

  [test case]

  create lxd container, install quassel-core, check quasselcore service:

  $ systemctl status quasselcore
  ● quasselcore.service - distributed IRC client using a central core component
   Loaded: loaded (/lib/systemd/system/quasselcore.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: signal) since Tue 2020-06-30 18:32:40 UTC; 4s ago
 Docs: man:quasselcore(1)
  Process: 3853 ExecStart=/usr/bin/quasselcore --configdir=${DATADIR} 
--logfile=${LOGFILE} --loglevel=${LOGLEVEL} --port=${PORT} --listen=${LISTEN} 
(code=killed, signal=SEGV)
 Main PID: 3853 (code=killed, signal=SEGV)

  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Scheduled 
restart job, restart counter is at 7.
  Jun 30 18:32:40 lp1814302-f systemd[1]: Stopped distributed IRC client using 
a central core component.
  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Start request 
repeated too quickly.
  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Failed with 
result 'signal'.
  Jun 30 18:32:40 lp1814302-f systemd[1]: Failed to start distributed IRC 
client using a central core component.

  
  Also, the binary will segfault when run directly due to apparmor denials:

  $ /usr/bin/quasselcore 
  Segmentation fault

  [760149.590802] audit: type=1400 audit(1593542073.962:1058):
  apparmor="DENIED" operation="file_mmap" namespace="root//lxd-
  lp1814302-f_" profile="/usr/bin/quasselcore"
  name="/usr/bin/quasselcore" pid=2006430 comm="quasselcore"
  requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100

  [regression potential]

  this expands the apparmor profile, so any regression would likely
  involve problems while starting due to apparmor.

  [scope]

  this is needed for b/f/g.

  this is also needed for e, but that is EOL in weeks and this is not
  important enough to bother there.

  [original description]

  
  Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04 
container. Everything up todate via apt.

  Install quassel-core. Service will not start.

  Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.

  I then added "/usr/bin/quasselcore rm," to
  "/etc/apparmor.d/usr.bin.quasselcore".

  Set "aa-enforce /usr/bin/quasselcore". Restarted main host.

  Quasselcore service now starts and I can connect to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1814302/+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 1814302] Re: Quasselcore apparmor profile issue in lxd container.

[Dave Jones]

** Patch added: "1-1814301-kinetic.debdiff"
   
https://bugs.launchpad.net/ubuntu/jammy/+source/quassel/+bug/1814302/+attachment/5596890/+files/1-1814301-kinetic.debdiff

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

Title:
  Quasselcore apparmor profile issue in lxd container.

Status in AppArmor:
  Invalid
Status in apparmor package in Ubuntu:
  Invalid
Status in quassel package in Ubuntu:
  Confirmed
Status in apparmor source package in Bionic:
  Invalid
Status in quassel source package in Bionic:
  Fix Released
Status in apparmor source package in Focal:
  Invalid
Status in quassel source package in Focal:
  Fix Released
Status in apparmor source package in Groovy:
  Invalid
Status in quassel source package in Groovy:
  Fix Released
Status in apparmor source package in Jammy:
  Invalid
Status in quassel source package in Jammy:
  Confirmed
Status in apparmor source package in Kinetic:
  Invalid
Status in quassel source package in Kinetic:
  Confirmed

Bug description:
  [impact]

  quasselcore cannot start inside lxd container

  [test case]

  create lxd container, install quassel-core, check quasselcore service:

  $ systemctl status quasselcore
  ● quasselcore.service - distributed IRC client using a central core component
   Loaded: loaded (/lib/systemd/system/quasselcore.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: signal) since Tue 2020-06-30 18:32:40 UTC; 4s ago
 Docs: man:quasselcore(1)
  Process: 3853 ExecStart=/usr/bin/quasselcore --configdir=${DATADIR} 
--logfile=${LOGFILE} --loglevel=${LOGLEVEL} --port=${PORT} --listen=${LISTEN} 
(code=killed, signal=SEGV)
 Main PID: 3853 (code=killed, signal=SEGV)

  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Scheduled 
restart job, restart counter is at 7.
  Jun 30 18:32:40 lp1814302-f systemd[1]: Stopped distributed IRC client using 
a central core component.
  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Start request 
repeated too quickly.
  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Failed with 
result 'signal'.
  Jun 30 18:32:40 lp1814302-f systemd[1]: Failed to start distributed IRC 
client using a central core component.

  
  Also, the binary will segfault when run directly due to apparmor denials:

  $ /usr/bin/quasselcore 
  Segmentation fault

  [760149.590802] audit: type=1400 audit(1593542073.962:1058):
  apparmor="DENIED" operation="file_mmap" namespace="root//lxd-
  lp1814302-f_" profile="/usr/bin/quasselcore"
  name="/usr/bin/quasselcore" pid=2006430 comm="quasselcore"
  requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100

  [regression potential]

  this expands the apparmor profile, so any regression would likely
  involve problems while starting due to apparmor.

  [scope]

  this is needed for b/f/g.

  this is also needed for e, but that is EOL in weeks and this is not
  important enough to bother there.

  [original description]

  
  Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04 
container. Everything up todate via apt.

  Install quassel-core. Service will not start.

  Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.

  I then added "/usr/bin/quasselcore rm," to
  "/etc/apparmor.d/usr.bin.quasselcore".

  Set "aa-enforce /usr/bin/quasselcore". Restarted main host.

  Quasselcore service now starts and I can connect to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1814302/+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 1814302] Re: Quasselcore apparmor profile issue in lxd container.

[Dave Jones]

** Patch added: "1-1814301-jammy.debdiff"
   
https://bugs.launchpad.net/ubuntu/jammy/+source/quassel/+bug/1814302/+attachment/5597063/+files/1-1814301-jammy.debdiff

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

Title:
  Quasselcore apparmor profile issue in lxd container.

Status in AppArmor:
  Invalid
Status in apparmor package in Ubuntu:
  Invalid
Status in quassel package in Ubuntu:
  Confirmed
Status in apparmor source package in Bionic:
  Invalid
Status in quassel source package in Bionic:
  Fix Released
Status in apparmor source package in Focal:
  Invalid
Status in quassel source package in Focal:
  Fix Released
Status in apparmor source package in Groovy:
  Invalid
Status in quassel source package in Groovy:
  Fix Released
Status in apparmor source package in Jammy:
  Invalid
Status in quassel source package in Jammy:
  Confirmed
Status in apparmor source package in Kinetic:
  Invalid
Status in quassel source package in Kinetic:
  Confirmed

Bug description:
  [impact]

  quasselcore cannot start inside lxd container

  [test case]

  create lxd container, install quassel-core, check quasselcore service:

  $ systemctl status quasselcore
  ● quasselcore.service - distributed IRC client using a central core component
   Loaded: loaded (/lib/systemd/system/quasselcore.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: signal) since Tue 2020-06-30 18:32:40 UTC; 4s ago
 Docs: man:quasselcore(1)
  Process: 3853 ExecStart=/usr/bin/quasselcore --configdir=${DATADIR} 
--logfile=${LOGFILE} --loglevel=${LOGLEVEL} --port=${PORT} --listen=${LISTEN} 
(code=killed, signal=SEGV)
 Main PID: 3853 (code=killed, signal=SEGV)

  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Scheduled 
restart job, restart counter is at 7.
  Jun 30 18:32:40 lp1814302-f systemd[1]: Stopped distributed IRC client using 
a central core component.
  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Start request 
repeated too quickly.
  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Failed with 
result 'signal'.
  Jun 30 18:32:40 lp1814302-f systemd[1]: Failed to start distributed IRC 
client using a central core component.

  
  Also, the binary will segfault when run directly due to apparmor denials:

  $ /usr/bin/quasselcore 
  Segmentation fault

  [760149.590802] audit: type=1400 audit(1593542073.962:1058):
  apparmor="DENIED" operation="file_mmap" namespace="root//lxd-
  lp1814302-f_" profile="/usr/bin/quasselcore"
  name="/usr/bin/quasselcore" pid=2006430 comm="quasselcore"
  requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100

  [regression potential]

  this expands the apparmor profile, so any regression would likely
  involve problems while starting due to apparmor.

  [scope]

  this is needed for b/f/g.

  this is also needed for e, but that is EOL in weeks and this is not
  important enough to bother there.

  [original description]

  
  Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04 
container. Everything up todate via apt.

  Install quassel-core. Service will not start.

  Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.

  I then added "/usr/bin/quasselcore rm," to
  "/etc/apparmor.d/usr.bin.quasselcore".

  Set "aa-enforce /usr/bin/quasselcore". Restarted main host.

  Quasselcore service now starts and I can connect to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1814302/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.

[Dave Jones]

** Also affects: ubuntu-seeds
   Importance: Undecided
   Status: New

** Changed in: ubuntu-seeds
 Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  kernel modules "zstd" and "z3fold" missing.

Status in Ubuntu Seeds:
  New
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-settings package in Ubuntu:
  New
Status in linux-raspi source package in Jammy:
  Invalid
Status in ubuntu-settings source package in Jammy:
  New
Status in linux-raspi source package in Kinetic:
  Invalid
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  The modules "zstd" and "z3fold" are missing despite being configured
  for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot
  display that state they do not exist and so instead use compressor
  "lzo" and pool "zbud".

  Ubuntu version is 22.04 LTS flashed from the official image.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8
  ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30
  Uname: Linux 5.15.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  6 17:29:00 2022
  ImageMediaBuild: 20220419
  SourcePackage: linux-raspi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.

[Dave Jones]

Attaching debdiff for ubuntu-settings. This adds the ubuntu-raspi-
settings-desktop binary package which includes the necessary initramfs-
tools configuration to include the missing modules. In addition to this,
I'll file a merge proposal for the necessary seed to include this
package in the Ubuntu Pi desktop image(s).

** Patch added: "1-1977764.debdiff"
   
https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+attachment/5604370/+files/1-1977764.debdiff

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

Title:
  kernel modules "zstd" and "z3fold" missing.

Status in Ubuntu Seeds:
  New
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-settings package in Ubuntu:
  New
Status in linux-raspi source package in Jammy:
  Invalid
Status in ubuntu-settings source package in Jammy:
  New
Status in linux-raspi source package in Kinetic:
  Invalid
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  The modules "zstd" and "z3fold" are missing despite being configured
  for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot
  display that state they do not exist and so instead use compressor
  "lzo" and pool "zbud".

  Ubuntu version is 22.04 LTS flashed from the official image.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8
  ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30
  Uname: Linux 5.15.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  6 17:29:00 2022
  ImageMediaBuild: 20220419
  SourcePackage: linux-raspi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.

[Dave Jones]

To sponsors: let me know if the ubuntu-raspi-settings-desktop name is
not desirable; I'm happy to adjust this to (for example) ubuntu-desktop-
raspi-settings but it'll need adjusting in both this debdiff, and in the
MP for the corresponding seed.

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

Title:
  kernel modules "zstd" and "z3fold" missing.

Status in Ubuntu Seeds:
  New
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-settings package in Ubuntu:
  New
Status in linux-raspi source package in Jammy:
  Invalid
Status in ubuntu-settings source package in Jammy:
  New
Status in linux-raspi source package in Kinetic:
  Invalid
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  The modules "zstd" and "z3fold" are missing despite being configured
  for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot
  display that state they do not exist and so instead use compressor
  "lzo" and pool "zbud".

  Ubuntu version is 22.04 LTS flashed from the official image.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8
  ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30
  Uname: Linux 5.15.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  6 17:29:00 2022
  ImageMediaBuild: 20220419
  SourcePackage: linux-raspi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

[Dave Jones]

** Description changed:

- On the hirsute Pi desktop, under a wayland session with the "full" KMS
- overlay enabled, and "kms-modifiers" present in the
- org.gnome.mutter/experimental-features, the body of a window containing
- an HTML renderer (e.g. help text or a login page) displays corruption.
+ On the jammy Pi desktop, under a wayland session, the body of a window
+ containing an HTML renderer (e.g. help text or a login page) displays
+ corruption.
  
  These reproduction cases may not be entirely reliable given that *some*
  pages appear to render correctly, but I'll include a couple in the hopes
  of making it reliably reproducible:
  
  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link
  
  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.
  
  Another reproduction case:
  
  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me
  
  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).
  
  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in the
  body of the window; the window decorations are unaffected. I'll attach a
  screenshot of the corrupted help window to illustrate.

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  On the jammy Pi desktop, under a wayland session, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions


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

[Touch-packages] [Bug 1955084] Re: systemd unit leaves a process running for the system lifetime but it only does anything at shutdown

[Dave Jones]

As requested, here's what I managed to dig up on possible alternatives
to running unattended-upgrades-shutdown persistently:

There appear to be several methods by which systemd can be told to run
something at or near shutdown, but one has to be exceptionally careful
in the selection to cover all edge cases.

Some possibilities can be trivially discarded. For instance, the
systemd-shutdown (8) logic runs too late, potentially after the root
file-system has been remounted read-only.

Other possibilities have extremely subtle side-effects. For example, one
tempting possibility is to reverse the current logic of the
unattended-upgrades.service, which currently looks like this:

  [Service]
  ExecStart=/usr/share/unattended-upgrades/unattended-upgrade-shutdown 
--wait-for-signal
  KillMode=process
  TimeoutStopSec=1800

And instead use a "fake" service that systemd pretends is running, then
activate the shutdown script when systemd goes to stop the service, like
so:

  [Service]
  ExecStart=/bin/true
  RemainAfterExit=yes
  ExecStop=/usr/share/unattended-upgrades/unattended-upgrade-shutdown
  KillMode=process
  TimeoutStopSec=1800

Note the lack of --wait-for-signal (because we want the script to run
immediately when systemd goes to "stop" the fake service).

However, tempting though this possibility is, LP: #1778219 (and associated
commits, particularly [4]) describes why this doesn't work in practice. If a
package upgrade is occurring during shutdown, and that package attempts to
start or restart a systemd service, the attempt will hang. This is particularly
an issue with the "InstallOnShutdown" behaviour (not the default) which expects
to fully complete the upgrade before shutdown (as opposed to the default
behaviour which attempts to stop the upgrade after the next transaction
completes).

Side note: The KillMode setting appears to be an attempt to prevent systemd
from killing a subordinate apt process in the event it deems
unattended-upgrades to have timed out. This seems … risky to me. The timeout
duration is, so far as I can tell, picked fairly arbitrarily and what happens 
in the
event that unattended-upgrades times out, but leaves subordinate apt/dpkg
processes lying around is unclear (does systemd wait for them indefinitely,
does it kill them after another timeout, does it shutdown/reset the machine
with them still running?). There's some more context in LP: #1690980 regard
this.

Ultimately, the solution appears to have been having a persistent process
(u-u-shutdown) watch for the logind PrepareForShutdown event which occurs well
before systemd actually starts the shutdown. Unfortunately (as far as I've been
able to tell?) this requires an active process to watch for it.

The following bugs contain a great deal of detail and further context to this
issue:

* LP: #1778219 -- u-u hanging on shutdown
* LP: #1654600 -- u-u hanging when /var is separate file-system
* LP: #1618900 -- u-u failing to upgrade kernels due to missing mount (+others)
* LP: #1690980 -- context regarding u-u's shutdown inhibit, and killmode

There are also some useful test cases found in these bugs that should be used
in ensuring certain scenarios aren't broken. The following PRs and GitHub
issues are also well worth a read, especially #148:

[1]: https://github.com/mvo5/unattended-upgrades/pull/64
[2]: https://github.com/mvo5/unattended-upgrades/pull/148
[3]: https://github.com/mvo5/unattended-upgrades/issues/176
[4]: 
https://github.com/mvo5/unattended-upgrades/commit/3734e06d03c5146dc307b3996ea11c8b398a55c1

Balint's comment ([5]) in LP: #1778219 also offered an intriguing (partial?)
solution: maintscripts should not be calling systemctl themselves, but
deb-systemd-invoke (lintian already checks for this), and deb-systemd-invoke
should be enhanced to detect when it is operating during shutdown, and refuse
to start/restart services (only stopping them). It appears there was an
intention to fix this but it got lost somewhere along the way.

[5]: https://bugs.launchpad.net/ubuntu/+source/unattended-
upgrades/+bug/1778219/comments/6

** Bug watch added: github.com/mvo5/unattended-upgrades/issues #176
   https://github.com/mvo5/unattended-upgrades/issues/176

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

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

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

Bug description:
  The /lib/systemd/system/unattended-upgrades.service unit leaves a
  process, /usr/share/unattended-upgrades/unattended-upgrade-shutdown
  --wait-for-signal, running from system start until shutdown.  This
  increases the minimum memory footprint of every host, VM, or container
  where unattended-upgrades is installed.  The motivation for having

[Touch-packages] [Bug 1987340] [NEW] Please merge lvm2 2.03.16-1 from Debian unstable.

[Dave Jones]

Public bug reported:

Please merge lvm2 2.03.16-1 from Debian unstable.

Updated changelog and diff against Debian unstable to be attached below.

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

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

Title:
  Please merge lvm2 2.03.16-1 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-1 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+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 1987340] Re: Please merge lvm2 2.03.16-1 from Debian unstable.

[Dave Jones]

Attaching patch against Debian unstable. For ease of review, relevant commits
and tags have been pushed to the following repository:

https://code.launchpad.net/~waveform/ubuntu/+source/lvm2/+git/lvm2

Specifically:

* logical/2.03.11-2.1ubuntu4 represents our split-out delta on top of 
old/debian (2.03.11-2)
* logical/2.03.16-1ubuntu1 represents our rebased delta on top of new/debian 
(2.03.16-1)
* merge/2.03.16-1ubuntu1 just adds changelog and maintainer changes on top of 
logical/2.03.16-1ubuntu1

Hence, the following command may produce output useful to the purposes
of review:

git range-diff old/debian..logical/2.03.11-2.1ubuntu4
new/debian..logical/2.03.16-1ubuntu1


** Patch added: "1-1987340.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+attachment/5610882/+files/1-1987340.debdiff

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

Title:
  Please merge lvm2 2.03.16-1 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-1 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+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 1987340] Re: Please merge lvm2 2.03.16-1 from Debian unstable.

[Dave Jones]

** Tags added: fr-2621

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

Title:
  Please merge lvm2 2.03.16-1 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-1 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+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 1987340] Re: Please merge lvm2 2.03.16-1 from Debian unstable.

[Dave Jones]

Test builds are available from ppa:waveform/lvm2 at the following URL:

https://launchpad.net/~waveform/+archive/ubuntu/lvm2

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

Title:
  Please merge lvm2 2.03.16-1 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-1 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+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 1987340] Re: Please merge lvm2 2.03.16-1 from Debian unstable.

[Dave Jones]

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

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

Title:
  Please merge lvm2 2.03.16-1 from Debian unstable.

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Please merge lvm2 2.03.16-1 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+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 1959211] Re: Please merge dbus 1.14.0-2 from Debian unstable.

[Dave Jones]

** Summary changed:

- Please merge dbus 1.12.20-3 from Debian unstable
+ Please merge dbus 1.14.0-2 from Debian unstable.

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

Title:
  Please merge dbus 1.14.0-2 from Debian unstable.

Status in dbus package in Ubuntu:
  New

Bug description:
  NOTE: Resetting to new; do NOT merge (the current state of the merge
  would also produce LP: #1962036 -- will update this merge once that is
  fixed)

  
  = Original Description =

  Please merge dbus 1.12.20-3 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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 1959211] Re: Please merge dbus 1.14.0-2 from Debian unstable.

[Dave Jones]

Attaching patch against Debian unstable. For ease of review, relevant commits
and tags have been pushed to the following repository:

https://code.launchpad.net/~waveform/ubuntu/+source/dbus/+git/dbus

Specifically:

* logical/1.12.20-2ubuntu4 represents our split-out delta on top of old/debian 
(1.12.20-2)
* logical/1.14.0-2ubuntu1 represents our rebased delta on top of new/debian 
(1.14.0-2)
* merge/1.14.0-2ubuntu1 just adds changelog and maintainer changes on top of 
logical/1.14.0-2ubuntu1

Hence, the following command may produce output useful to the purposes
of review:

git range-diff old/debian..logical/1.12.20-2ubuntu4
new/debian..logical/1.14.0-2ubuntu1

** Description changed:

- NOTE: Resetting to new; do NOT merge (the current state of the merge
- would also produce LP: #1962036 -- will update this merge once that is
- fixed)
- 
- 
- = Original Description =
- 
- Please merge dbus 1.12.20-3 from Debian unstable.
+ Please merge dbus 1.14.0-2 from Debian unstable.
  
  Updated changelog and diff against Debian unstable to be attached below.

** Patch added: "2-1959211.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+attachment/5611005/+files/2-1959211.debdiff

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

Title:
  Please merge dbus 1.14.0-2 from Debian unstable.

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Please merge dbus 1.14.0-2 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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 1959211] Re: Please merge dbus 1.14.0-2 from Debian unstable.

[Dave Jones]

Test builds will be available in ppa:waveform/dbus at the following URL:

https://launchpad.net/~waveform/+archive/ubuntu/dbus

** Tags added: fr-2624

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

Title:
  Please merge dbus 1.14.0-2 from Debian unstable.

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Please merge dbus 1.14.0-2 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Dave Jones]

** Summary changed:

- bash does not fulfill --bashrc option properly
+ bash does not fulfill --rcfile option properly

** Description changed:

  I am starting a bash shell using
  
- $ bash --noprofile --bashrc my-custom-bash-rc-file
+ $ bash --noprofile --rcfile my-custom-bash-rc-file
  
  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:
  
-   --rcfile file
-   Execute commands from file instead of the system wide 
initialization file /etc/bash.bashrc and the standard personal initial‐
-   ization file ~/.bashrc if the shell is interactive (see 
INVOCATION below). 
+   --rcfile file
+   Execute commands from file instead of the system wide 
initialization file /etc/bash.bashrc and the standard personal initial‐
+   ization file ~/.bashrc if the shell is interactive (see 
INVOCATION below).
  
  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.
  
  To see/reproduce/diagnose this, on Ubuntu I believe one can just invoke
  bash like this (as the regular user):
  
  $ touch testrc
- $ env -i bash --noprofile --rcfile testrc 
+ $ env -i bash --noprofile --rcfile testrc
  
  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the invoked
  shell, which in turn triggers the error. The error message is:
  
  > To run a command as administrator (user "root"), use "sudo ".
- > See "man sudo_root" for details. 
+ > See "man sudo_root" for details.
  
  Another way to see this -- without the "env -i" -- is to add  a command
  to /etc/bash.bashrc, such as
  
  echo HELLO THERE
  
  To trigger the bug(?), one can then just do
  
  $ touch testrc
- $ bash --noprofile --bashrc testrc
+ $ bash --noprofile --rcfile testrc
  
  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string
  
  HELLO THERE
  
  is printed.

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

Title:
  bash does not fulfill --rcfile option properly

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

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

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Dave Jones]

This has apparently been an issue for some considerable time. I've just
now run into it while delving into a failure in pexpect's test-suite
(during work on LP: #1987420), which apparently assumes that using
--rcfile will suppress both the user *and* the system's bashrc (as the
man-page documents).

However, I'm not entirely convinced this is a bug in bash, so much as
its man-page. Reading the original code (shell.c in bash) its intent is
fairly clear: execute the system-wide bashrc in all interactive shells,
but permit the user's bashrc to be overridden by --rcfile.

It's worth noting that the original (upstream, not Debian) man-page
makes no mention of the system-wide bashrc because it's an option that's
not activated by default. The Debian packaging enables the system-wide
bashrc (SYS_BASHRC in d/p/deb-bash-config.diff) and then patches the
man-page to mention it (d/p/man-bashrc.diff). In other words, I suspect
this is a documentation bug rather than a behavioural bug (i.e. the man-
page is wrong, not the behaviour).

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

Title:
  bash does not fulfill --rcfile option properly

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

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

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+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 1987340] Re: Please merge lvm2 2.03.16-1 from Debian unstable.

[Dave Jones]

I'm afraid the removal of colons in LP: entries of the changelog is a
deliberate tactic by maintainers to prevent launchpad from inadvertently
marking things closed when it shouldn't (theoretically, this shouldn't
happen if things are targetted correctly to the relevant releases, but
this isn't always the case).

On the subject of basing the branch on salsa, I'm not sure how that
could work given I'd need to be working with a repo containing two
remotes, one the git-ubuntu import (needed to do the initial split
because the delta isn't necessarily a monolithic commit; it can consist
of several ubuntu versions), and the second from salsa. But the latter's
main/master branch cannot match the git-ubuntu import's commit as the
commits in the former are generated from the packaging archive.

It would be possible to cherry-pick the rebased delta onto a chosen
salsa commit, but that wouldn't affect the output of range-diff, so I'm
not seeing how it would improve the ability to review the merge?

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

Title:
  Please merge lvm2 2.03.16-1 from Debian unstable.

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Please merge lvm2 2.03.16-1 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Dave Jones]

Hmm, on the other hand --norc does indeed suppress both user and system-
wide bashrc files. So, the man-page is correct in that instance, and
apparently the intent of bash is to allow the system-wide bashrc file to
be suppressed in certain circumstances. Which sways me back toward the
notion that the bug is in bash's --rcfile behaviour ...

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

Title:
  bash does not fulfill --rcfile option properly

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

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

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Dave Jones]

I'm unsure what the "correct" solution is here; could be that bash's
behaviour is wrong, or it could be that the documentation is wrong.
Rather than decide, I'm taking the cowards way out and attaching patches
for both solutions, leaving it to the maintainer to decide which is
appropriate :)

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

Title:
  bash does not fulfill --rcfile option properly

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

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

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Dave Jones]

** Patch added: "bash-is-wrong.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5611100/+files/bash-is-wrong.debdiff

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

Title:
  bash does not fulfill --rcfile option properly

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

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

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Dave Jones]

** Patch added: "manpage-is-wrong.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5611101/+files/manpage-is-wrong.debdiff

** Tags added: rls-kk-incoming

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

Title:
  bash does not fulfill --rcfile option properly

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

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

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+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 1959211] Re: Please merge dbus 1.14.0-2 from Debian unstable.

[Dave Jones]

> I'll upload it using git-ubuntu style, too, so it will be easier to do
the next merge.

I must get Robie to remind me what I need to stuff in the .changes file
to make that automatic (I vaguely recall him mentioning there were some
extra tags that could/should be placed there).

> Using a "ubuntu/bionic" gbp branch, is probably as useless as using a
"debian/unstable" branch in Ubuntu's development release. I wonder if we
could/should drop that part of the delta on the next occasion.

Yes -- during the merge I initially dropped that change, but then
reverted it because it made the range-diff a little noisier for no
particularly good reason. Still, I do agree it's basically pointless and
should be dropped.

> This seems to be generally useful. Would you mind sending this patch
to Debian, so we can eventually drop it from our delta?

Will do.

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

Title:
  Please merge dbus 1.14.0-2 from Debian unstable.

Status in dbus package in Ubuntu:
  In Progress

Bug description:
  Please merge dbus 1.14.0-2 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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 1959211] Re: Please merge dbus 1.14.0-2 from Debian unstable.

[Dave Jones]

It appears dbus is stuck in kinetic-proposed due to failures in
dependency resolution on i386; there are two new arch-indep packages in
the merged package which the dbus package depends on, but they lack
Multi-Arch tags in d/control.

I'm attaching (yet another :) debdiff which adds M-A: foreign to these
packages which should permit the resolver to use these packages when
attempting to install dbus:i386.

@slyon could you sponsor this change into -proposed? Hopefully things
will migrate this time (and many thanks to @jawn-smith for the
recollection of Multi-Arch when dealing with i386 things!)

** Patch added: "3-1959211.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+attachment/5612541/+files/3-1959211.debdiff

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

Title:
  Please merge dbus 1.14.0-2 from Debian unstable.

Status in dbus package in Ubuntu:
  In Progress

Bug description:
  Please merge dbus 1.14.0-2 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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 1988418] [NEW] Please merge initramfs-tools 0.142 from Debian unstable.

[Dave Jones]

Public bug reported:

Please merge initramfs-tools 0.142 from Debian unstable.

Updated changelog and diff against Debian unstable to be attached below.

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

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

Title:
  Please merge initramfs-tools 0.142 from Debian unstable.

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Please merge initramfs-tools 0.142 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1988418/+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 1988418] Re: Please merge initramfs-tools 0.142 from Debian unstable.

[Dave Jones]

Attaching patch against Debian unstable. For ease of review, relevant commits
and tags have been pushed to the following repository:

https://code.launchpad.net/~waveform/ubuntu/+source/initramfs-
tools/+git/initramfs-tools

Specifically:

* logical/0.140ubuntu17 represents our split-out delta on top of old/debian 
(0.140)
* logical/0.142ubuntu1 represents our rebased delta on top of new/debian (0.142)
* merge/0.142ubuntu1 adds changelog and maintainer changes, and one post-merge 
change on top of logical/0.142ubuntu1

Hence, the following command may produce output useful to the purposes
of review:

git range-diff old/debian..logical/0.140ubuntu17
new/debian..logical/0.142ubuntu1


** Patch added: "1-1988418.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1988418/+attachment/5612987/+files/1-1988418.debdiff

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

Title:
  Please merge initramfs-tools 0.142 from Debian unstable.

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Please merge initramfs-tools 0.142 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1988418/+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 1988418] Re: Please merge initramfs-tools 0.142 from Debian unstable.

[Dave Jones]

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

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

Title:
  Please merge initramfs-tools 0.142 from Debian unstable.

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Please merge initramfs-tools 0.142 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1988418/+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 1988418] Re: Please merge initramfs-tools 0.142 from Debian unstable.

[Dave Jones]

I would caution that there are some substantial changes in this merge.
Specifically:

* upstream has now moved to zstd by default (as in Ubuntu) resulting in
several bits of the delta changing

* upstream re-wrote a fair amount of logic around the "ip=" init
parameter; this is an area we already had a substantial delta which also
needed re-writing as a result

* upstream also added configuration for the compression level of the
initramfs which required our delta to change

Please do not attempt to review the debdiff; at nearly 300KB it would be
pointless. The git range-diff is far more informative, but may need a
larger --creation-factor to make the most of it (100 is a reasonable
choice).

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

Title:
  Please merge initramfs-tools 0.142 from Debian unstable.

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Please merge initramfs-tools 0.142 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1988418/+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 1988418] Re: Please merge initramfs-tools 0.142 from Debian unstable.

[Dave Jones]

Test packages are building in ppa:waveform/initramfs-tools at:

https://launchpad.net/~waveform/+archive/ubuntu/initramfs-tools

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

Title:
  Please merge initramfs-tools 0.142 from Debian unstable.

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Please merge initramfs-tools 0.142 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1988418/+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 2075337] Re: py3clean fails when using alternate character set

[Dave Jones]

Having spent some time digging into this (at the request of the SRU
team), I'll summarise my findings:

Firstly, the analysis is correct: py3clean is ultimately the issue;
packages that both use py3clean and have diversions are affected
(diversions are the only circumstances that produce localised output in
dpkg-query -L).

Secondly, the proposed fix upstream is also fine, though personally I'd
also like to see the stdout decode use errors='replace' (there's no good
reason to fail here in the event of dodgy UTF-8 in a translation, for
instance). I'll attach debdiffs for noble and oracular to illustrate my
intent.

Thirdly, the proposed workaround for affected packages: using Breaks on
python3-minimal with a version strictly less than the fixed version also
appears to be sufficient (in all the cases I've tested this causes
python3-minimal to be at least unpacked prior to the prerm script of the
affected package being executed).

So, if the fix for python3-minimal can be uploaded, it simply remains to
determine which packages are affected. This is where things get tricky.

Benjamin's efforts are much appreciated here, and will likely be
decisive in light of the following: determining which packages use
py3clean is relatively simple (pretty much anything that installs a
python module). Determining which packages have diversions turns out to
be extremely difficult.

It's not enough to detect if a package *itself* uses dpkg-divert. Take
the cloud-init case where this was first detected: the postinst calls
dpkg-divert but only to *remove* an old diversion. The diversion that
actually affects this package comes from usr-merge (because cloud-init
still has files under the unmerged paths for various reasons). In
essence, any package (foo) can cause a diversion in another package
(bar) without the affected package (bar) showing any sign of this in
either its source or its binary artefacts. Further, the diversion may or
may not affect the package (bar) as the source of the diversion (foo)
may be optional to install.

Hence, there are two approaches. The thorough, but likely impractical,
approach would be to apply the "Breaks" fix to all packages using
py3clean: i.e. all packages that install python modules. Then there's
(Benjamin's) empirical approach: attempt to install everything from the
former set and see what fails. As noted above, this cannot guarantee
correctness as we cannot be certain that all packages that may divert
files in our target package are installed, but in practice it's probably
(hopefully!) "good enough" given the rarity of diversions and avoids
updates to (presumably) several thousand packages.

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

Title:
  py3clean fails when using alternate character set

Status in dh-python package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New

Bug description:
  We noticed this in bug 2060769 but think it is a separate issue.

  dh_python3 is putting a py3clean invocation into package prerm
  maintainer scripts. When that runs, it explodes if the system
  character set is for example ISO-8859-1.

  This appears to affect every package for which dh_python3 has inserted
  a call to py3clean into the package prerm.

  python3-minimal 3.12.3-0ubuntu1

  In this reproducer, cloud-init is at 24.1.3-0ubuntu3.3.

  Steps to reproduce:

  $ lxc launch ubuntu:noble rbasak-pro-l8n
  $ lxc shell rbasak-pro-l8n
  # locale-gen fr_FR
  Generating locales (this might take a while)...
fr_FR.ISO-8859-1... done
  Generation complete.
  # update-locale LANG=fr_FR
  # exit
  # adjust terminal to ISO-8859-1
  $ lxc shell rbasak-pro-l8n
  # apt update && apt install --reinstall cloud-init

  Expected results: success

  Actual results:

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances... Fait
  Lecture des informations d'état... Fait
  0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 5 non 
mis à jour.
  Il est nécessaire de prendre 598 ko dans les archives.
  Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
  Réception de :1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 
cloud-init all 24.1.3-0ubuntu3.3 [598 kB]
  598 ko réceptionnés en 1s (926 ko/s)
  Préconfiguration des paquets...
  (Lecture de la base de données... 34406 fichiers et répertoires déjà 
installés.)
  Préparation du dépaquetage de .../cloud-init_24.1.3-0ubuntu3.3_all.deb ...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   ^^

[Touch-packages] [Bug 2075337] Re: py3clean fails when using alternate character set

[Dave Jones]

Attaching debdiff for proposed changes to python3-minimal in oracular

** Patch added: "oracular.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337/+attachment/5802638/+files/oracular.debdiff

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

Title:
  py3clean fails when using alternate character set

Status in dh-python package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New

Bug description:
  We noticed this in bug 2060769 but think it is a separate issue.

  dh_python3 is putting a py3clean invocation into package prerm
  maintainer scripts. When that runs, it explodes if the system
  character set is for example ISO-8859-1.

  This appears to affect every package for which dh_python3 has inserted
  a call to py3clean into the package prerm.

  python3-minimal 3.12.3-0ubuntu1

  In this reproducer, cloud-init is at 24.1.3-0ubuntu3.3.

  Steps to reproduce:

  $ lxc launch ubuntu:noble rbasak-pro-l8n
  $ lxc shell rbasak-pro-l8n
  # locale-gen fr_FR
  Generating locales (this might take a while)...
fr_FR.ISO-8859-1... done
  Generation complete.
  # update-locale LANG=fr_FR
  # exit
  # adjust terminal to ISO-8859-1
  $ lxc shell rbasak-pro-l8n
  # apt update && apt install --reinstall cloud-init

  Expected results: success

  Actual results:

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances... Fait
  Lecture des informations d'état... Fait
  0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 5 non 
mis à jour.
  Il est nécessaire de prendre 598 ko dans les archives.
  Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
  Réception de :1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 
cloud-init all 24.1.3-0ubuntu3.3 [598 kB]
  598 ko réceptionnés en 1s (926 ko/s)
  Préconfiguration des paquets...
  (Lecture de la base de données... 34406 fichiers et répertoires déjà 
installés.)
  Préparation du dépaquetage de .../cloud-init_24.1.3-0ubuntu3.3_all.deb ...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: avertissement: le sous-processus ancien paquet cloud-init script 
pre-removal a renvoyé un état de sortie d'erreur 1
  dpkg: tentative d'exécution du script du nouveau paquet à la place...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb (--unpack) :
   le sous-processus nouveau cloud-init paquet pre-removal script a renvoyé un 
état de sortie d'erreur 1
  dmesg: read kernel buffer failed: Operation not permitted
   Traceback (most 
recent call last):
File "/usr/bin/py3compile", line 323, in 
  main()
File "/usr/bin/py3compile", line 302, in main
  compile(files, versions,
File "/usr/bin/py3compile", line 185, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/py3compile", line 128, in filter_files
  for fpath in files:
File "/usr/share/python3/debpython/files.py", line 71, in filter_public
  for fn in files:
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: erreur lors du nettoyage:
   le sous-processus paquet cloud-init script post-installation installé a 
renvoyé un état de sortie d'erreur 1
  Des erreurs ont été rencontrées pendant l'exécution :
   /var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2075337/+subscriptions


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

[Touch-packages] [Bug 2075337] Re: py3clean fails when using alternate character set

[Dave Jones]

Attaching debdiff for proposed changes to python3-minimal in noble

** Patch added: "noble.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337/+attachment/5802639/+files/noble.debdiff

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

Title:
  py3clean fails when using alternate character set

Status in dh-python package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New

Bug description:
  We noticed this in bug 2060769 but think it is a separate issue.

  dh_python3 is putting a py3clean invocation into package prerm
  maintainer scripts. When that runs, it explodes if the system
  character set is for example ISO-8859-1.

  This appears to affect every package for which dh_python3 has inserted
  a call to py3clean into the package prerm.

  python3-minimal 3.12.3-0ubuntu1

  In this reproducer, cloud-init is at 24.1.3-0ubuntu3.3.

  Steps to reproduce:

  $ lxc launch ubuntu:noble rbasak-pro-l8n
  $ lxc shell rbasak-pro-l8n
  # locale-gen fr_FR
  Generating locales (this might take a while)...
fr_FR.ISO-8859-1... done
  Generation complete.
  # update-locale LANG=fr_FR
  # exit
  # adjust terminal to ISO-8859-1
  $ lxc shell rbasak-pro-l8n
  # apt update && apt install --reinstall cloud-init

  Expected results: success

  Actual results:

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances... Fait
  Lecture des informations d'état... Fait
  0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 5 non 
mis à jour.
  Il est nécessaire de prendre 598 ko dans les archives.
  Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
  Réception de :1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 
cloud-init all 24.1.3-0ubuntu3.3 [598 kB]
  598 ko réceptionnés en 1s (926 ko/s)
  Préconfiguration des paquets...
  (Lecture de la base de données... 34406 fichiers et répertoires déjà 
installés.)
  Préparation du dépaquetage de .../cloud-init_24.1.3-0ubuntu3.3_all.deb ...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: avertissement: le sous-processus ancien paquet cloud-init script 
pre-removal a renvoyé un état de sortie d'erreur 1
  dpkg: tentative d'exécution du script du nouveau paquet à la place...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb (--unpack) :
   le sous-processus nouveau cloud-init paquet pre-removal script a renvoyé un 
état de sortie d'erreur 1
  dmesg: read kernel buffer failed: Operation not permitted
   Traceback (most 
recent call last):
File "/usr/bin/py3compile", line 323, in 
  main()
File "/usr/bin/py3compile", line 302, in main
  compile(files, versions,
File "/usr/bin/py3compile", line 185, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/py3compile", line 128, in filter_files
  for fpath in files:
File "/usr/share/python3/debpython/files.py", line 71, in filter_public
  for fn in files:
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: erreur lors du nettoyage:
   le sous-processus paquet cloud-init script post-installation installé a 
renvoyé un état de sortie d'erreur 1
  Des erreurs ont été rencontrées pendant l'exécution :
   /var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2075337/+subscriptions


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

[Touch-packages] [Bug 2075337] Re: py3clean fails when using alternate character set

[Dave Jones]

** Patch added: "lp2075337-jammy.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337/+attachment/5803631/+files/lp2075337-jammy.debdiff

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

Title:
  py3clean fails when using alternate character set

Status in dh-python package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in dh-python source package in Jammy:
  New
Status in python3-defaults source package in Jammy:
  New
Status in dh-python source package in Noble:
  New
Status in python3-defaults source package in Noble:
  New

Bug description:
  We noticed this in bug 2060769 but think it is a separate issue.

  dh_python3 is putting a py3clean invocation into package prerm
  maintainer scripts. When that runs, it explodes if the system
  character set is for example ISO-8859-1.

  This appears to affect every package for which dh_python3 has inserted
  a call to py3clean into the package prerm.

  python3-minimal 3.12.3-0ubuntu1

  In this reproducer, cloud-init is at 24.1.3-0ubuntu3.3.

  Steps to reproduce:

  $ lxc launch ubuntu:noble rbasak-pro-l8n
  $ lxc shell rbasak-pro-l8n
  # locale-gen fr_FR
  Generating locales (this might take a while)...
fr_FR.ISO-8859-1... done
  Generation complete.
  # update-locale LANG=fr_FR
  # exit
  # adjust terminal to ISO-8859-1
  $ lxc shell rbasak-pro-l8n
  # apt update && apt install --reinstall cloud-init

  Expected results: success

  Actual results:

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances... Fait
  Lecture des informations d'état... Fait
  0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 5 non 
mis à jour.
  Il est nécessaire de prendre 598 ko dans les archives.
  Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
  Réception de :1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 
cloud-init all 24.1.3-0ubuntu3.3 [598 kB]
  598 ko réceptionnés en 1s (926 ko/s)
  Préconfiguration des paquets...
  (Lecture de la base de données... 34406 fichiers et répertoires déjà 
installés.)
  Préparation du dépaquetage de .../cloud-init_24.1.3-0ubuntu3.3_all.deb ...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: avertissement: le sous-processus ancien paquet cloud-init script 
pre-removal a renvoyé un état de sortie d'erreur 1
  dpkg: tentative d'exécution du script du nouveau paquet à la place...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb (--unpack) :
   le sous-processus nouveau cloud-init paquet pre-removal script a renvoyé un 
état de sortie d'erreur 1
  dmesg: read kernel buffer failed: Operation not permitted
   Traceback (most 
recent call last):
File "/usr/bin/py3compile", line 323, in 
  main()
File "/usr/bin/py3compile", line 302, in main
  compile(files, versions,
File "/usr/bin/py3compile", line 185, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/py3compile", line 128, in filter_files
  for fpath in files:
File "/usr/share/python3/debpython/files.py", line 71, in filter_public
  for fn in files:
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: erreur lors du nettoyage:
   le sous-processus paquet cloud-init script post-installation installé a 
renvoyé un état de sortie d'erreur 1
  Des erreurs ont été rencontrées pendant l'exécution :
   /var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
http

[Touch-packages] [Bug 2075337] Re: py3clean fails when using alternate character set

[Dave Jones]

** Patch added: "lp2075337-noble.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337/+attachment/5803632/+files/lp2075337-noble.debdiff

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

Title:
  py3clean fails when using alternate character set

Status in dh-python package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in dh-python source package in Jammy:
  New
Status in python3-defaults source package in Jammy:
  New
Status in dh-python source package in Noble:
  New
Status in python3-defaults source package in Noble:
  New

Bug description:
  We noticed this in bug 2060769 but think it is a separate issue.

  dh_python3 is putting a py3clean invocation into package prerm
  maintainer scripts. When that runs, it explodes if the system
  character set is for example ISO-8859-1.

  This appears to affect every package for which dh_python3 has inserted
  a call to py3clean into the package prerm.

  python3-minimal 3.12.3-0ubuntu1

  In this reproducer, cloud-init is at 24.1.3-0ubuntu3.3.

  Steps to reproduce:

  $ lxc launch ubuntu:noble rbasak-pro-l8n
  $ lxc shell rbasak-pro-l8n
  # locale-gen fr_FR
  Generating locales (this might take a while)...
fr_FR.ISO-8859-1... done
  Generation complete.
  # update-locale LANG=fr_FR
  # exit
  # adjust terminal to ISO-8859-1
  $ lxc shell rbasak-pro-l8n
  # apt update && apt install --reinstall cloud-init

  Expected results: success

  Actual results:

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances... Fait
  Lecture des informations d'état... Fait
  0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 5 non 
mis à jour.
  Il est nécessaire de prendre 598 ko dans les archives.
  Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
  Réception de :1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 
cloud-init all 24.1.3-0ubuntu3.3 [598 kB]
  598 ko réceptionnés en 1s (926 ko/s)
  Préconfiguration des paquets...
  (Lecture de la base de données... 34406 fichiers et répertoires déjà 
installés.)
  Préparation du dépaquetage de .../cloud-init_24.1.3-0ubuntu3.3_all.deb ...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: avertissement: le sous-processus ancien paquet cloud-init script 
pre-removal a renvoyé un état de sortie d'erreur 1
  dpkg: tentative d'exécution du script du nouveau paquet à la place...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb (--unpack) :
   le sous-processus nouveau cloud-init paquet pre-removal script a renvoyé un 
état de sortie d'erreur 1
  dmesg: read kernel buffer failed: Operation not permitted
   Traceback (most 
recent call last):
File "/usr/bin/py3compile", line 323, in 
  main()
File "/usr/bin/py3compile", line 302, in main
  compile(files, versions,
File "/usr/bin/py3compile", line 185, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/py3compile", line 128, in filter_files
  for fpath in files:
File "/usr/share/python3/debpython/files.py", line 71, in filter_public
  for fn in files:
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: erreur lors du nettoyage:
   le sous-processus paquet cloud-init script post-installation installé a 
renvoyé un état de sortie d'erreur 1
  Des erreurs ont été rencontrées pendant l'exécution :
   /var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
http

[Touch-packages] [Bug 2075337] Re: py3clean fails when using alternate character set

[Dave Jones]

Attaching debdiffs for sponsorship in noble and jammy.

For the purposes of review, the jammy diff does include one additional
change to avoid using shell=True on the invocation of dpkg -L. This can
be excised if necessary, but I really didn't want to leave something
that ultimately runs as root doing string interpolation and then calling
something via the shell, when I don't have to!

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

Title:
  py3clean fails when using alternate character set

Status in dh-python package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in dh-python source package in Jammy:
  New
Status in python3-defaults source package in Jammy:
  New
Status in dh-python source package in Noble:
  New
Status in python3-defaults source package in Noble:
  New

Bug description:
  We noticed this in bug 2060769 but think it is a separate issue.

  dh_python3 is putting a py3clean invocation into package prerm
  maintainer scripts. When that runs, it explodes if the system
  character set is for example ISO-8859-1.

  This appears to affect every package for which dh_python3 has inserted
  a call to py3clean into the package prerm.

  python3-minimal 3.12.3-0ubuntu1

  In this reproducer, cloud-init is at 24.1.3-0ubuntu3.3.

  Steps to reproduce:

  $ lxc launch ubuntu:noble rbasak-pro-l8n
  $ lxc shell rbasak-pro-l8n
  # locale-gen fr_FR
  Generating locales (this might take a while)...
fr_FR.ISO-8859-1... done
  Generation complete.
  # update-locale LANG=fr_FR
  # exit
  # adjust terminal to ISO-8859-1
  $ lxc shell rbasak-pro-l8n
  # apt update && apt install --reinstall cloud-init

  Expected results: success

  Actual results:

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances... Fait
  Lecture des informations d'état... Fait
  0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 5 non 
mis à jour.
  Il est nécessaire de prendre 598 ko dans les archives.
  Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
  Réception de :1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 
cloud-init all 24.1.3-0ubuntu3.3 [598 kB]
  598 ko réceptionnés en 1s (926 ko/s)
  Préconfiguration des paquets...
  (Lecture de la base de données... 34406 fichiers et répertoires déjà 
installés.)
  Préparation du dépaquetage de .../cloud-init_24.1.3-0ubuntu3.3_all.deb ...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: avertissement: le sous-processus ancien paquet cloud-init script 
pre-removal a renvoyé un état de sortie d'erreur 1
  dpkg: tentative d'exécution du script du nouveau paquet à la place...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb (--unpack) :
   le sous-processus nouveau cloud-init paquet pre-removal script a renvoyé un 
état de sortie d'erreur 1
  dmesg: read kernel buffer failed: Operation not permitted
   Traceback (most 
recent call last):
File "/usr/bin/py3compile", line 323, in 
  main()
File "/usr/bin/py3compile", line 302, in main
  compile(files, versions,
File "/usr/bin/py3compile", line 185, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/py3compile", line 128, in filter_files
  for fpath in files:
File "/usr/share/python3/debpython/files.py", line 71, in filter_public
  for fn in files:
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: erreur lors du nettoyage:
   le sous-processus paquet cloud-init script post-installation installé a 
renvoyé un état de sortie d'erreur 1
  Des erre

[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set

[Dave Jones]

** Summary changed:

- py3clean fails when using alternate character set
+ [SRU] py3clean fails when using alternate character set

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

Title:
  [SRU] py3clean fails when using alternate character set

Status in cloud-init package in Ubuntu:
  New
Status in dh-python package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in ubuntu-advantage-tools package in Ubuntu:
  New
Status in cloud-init source package in Jammy:
  Invalid
Status in dh-python source package in Jammy:
  New
Status in python3-defaults source package in Jammy:
  New
Status in ubuntu-advantage-tools source package in Jammy:
  Invalid
Status in cloud-init source package in Noble:
  New
Status in dh-python source package in Noble:
  New
Status in python3-defaults source package in Noble:
  New
Status in ubuntu-advantage-tools source package in Noble:
  New

Bug description:
  We noticed this in bug 2060769 but think it is a separate issue.

  dh_python3 is putting a py3clean invocation into package prerm
  maintainer scripts. When that runs, it explodes if the system
  character set is for example ISO-8859-1.

  This appears to affect every package for which dh_python3 has inserted
  a call to py3clean into the package prerm.

  python3-minimal 3.12.3-0ubuntu1

  In this reproducer, cloud-init is at 24.1.3-0ubuntu3.3.

  Steps to reproduce:

  $ lxc launch ubuntu:noble rbasak-pro-l8n
  $ lxc shell rbasak-pro-l8n
  # locale-gen fr_FR
  Generating locales (this might take a while)...
fr_FR.ISO-8859-1... done
  Generation complete.
  # update-locale LANG=fr_FR
  # exit
  # adjust terminal to ISO-8859-1
  $ lxc shell rbasak-pro-l8n
  # apt update && apt install --reinstall cloud-init

  Expected results: success

  Actual results:

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances... Fait
  Lecture des informations d'état... Fait
  0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 5 non 
mis à jour.
  Il est nécessaire de prendre 598 ko dans les archives.
  Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
  Réception de :1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 
cloud-init all 24.1.3-0ubuntu3.3 [598 kB]
  598 ko réceptionnés en 1s (926 ko/s)
  Préconfiguration des paquets...
  (Lecture de la base de données... 34406 fichiers et répertoires déjà 
installés.)
  Préparation du dépaquetage de .../cloud-init_24.1.3-0ubuntu3.3_all.deb ...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: avertissement: le sous-processus ancien paquet cloud-init script 
pre-removal a renvoyé un état de sortie d'erreur 1
  dpkg: tentative d'exécution du script du nouveau paquet à la place...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb (--unpack) :
   le sous-processus nouveau cloud-init paquet pre-removal script a renvoyé un 
état de sortie d'erreur 1
  dmesg: read kernel buffer failed: Operation not permitted
   Traceback (most 
recent call last):
File "/usr/bin/py3compile", line 323, in 
  main()
File "/usr/bin/py3compile", line 302, in main
  compile(files, versions,
File "/usr/bin/py3compile", line 185, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/py3compile", line 128, in filter_files
  for fpath in files:
File "/usr/share/python3/debpython/files.py", line 71, in filter_public
  for fn in files:
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: erreur lors du nettoyage:
   le sous-processus paquet cl

[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set

[Dave Jones]

Marking dh_python as invalid; it was added originally on the theory that
we may have needed to patch the prerm fallback but this has thankfully
turned out to be unnecessary.

** Description changed:

+ [ Impact ]
+ 
+ With the current version of python3-defaults in jammy and noble,
+ packages which utilize py3compile and py3clean in their maintscripts
+ (which is more or less any package which includes Python modules), and
+ which also are affected by diversions installed by dpkg-divert, will
+ fail to install/upgrade/remove on systems with non-UTF-8 locales, which
+ include non-ASCII characters in their localized dpkg -L messages (and
+ which therefore produce output that is not valid UTF-8).
+ 
+ As this has the potential to break apt upgrade, the impact is quite
+ severe (especially if this occurs during a dist-upgrade). However, the
+ scope is probably *fairly* limited given this only affects systems with
+ non-UTF-8 locales (something that has not been the default for many
+ years), and which produce non-ASCII output (e.g. French characters with
+ diacriticals) in their localized messages for dpkg -L.
+ 
+ [ Rectification Plan ]
+ 
+ Firstly, python3-defaults must be patched in oracular, noble, and jammy.
+ doko has uploaded the fix upstream and synced this to oracular. Benjamin
+ has sponsored the noble and jammy SRUs.
+ 
+ Next, affected packages must be patched to include a "Breaks" line on
+ earlier versions of python3-minimal (the python3-defaults binary package
+ containing py3clean and py3compile).
+ 
+ Packages which install Python modules are easily selected, but those
+ affected by diversions are (computationally) impossible to select (see
+ comment 18 for details). Thus, determining the set of affected packages
+ was non-trivial, but Benjamin has kindly produced such a list by
+ empirical means (see comment 24). These will be added to the ticket as
+ they are uploaded.
+ 
+ [ Test Plan ]
+ 
+ Where $series is jammy or noble as appropriate, and $package is the name
+ of the affected package being SRU'd:
+ 
+ $ lxc launch ubuntu:$series py3clean-test
+ $ lxc shell py3clean-test
+ # locale-gen fr_FR
+ Generating locales (this might take a while)...
+   fr_FR.ISO-8859-1... done
+ Generation complete.
+ # update-locale LANG=fr_FR
+ # exit
+ # adjust terminal to ISO-8859-1
+ $ lxc shell py3clean-test
+ # apt update && apt install --reinstall $package
+ 
+ With the current version of python3-defaults in jammy and noble this
+ should fail at the final apt install --reinstall step. With the proposed
+ version, it should succeed.
+ 
+ [ What Could Go Wrong? ]
+ 
+ The potential for regression is low since the python3-defaults changes
+ are minimal and have been reasonably tested, and the only change to
+ affected packages is the addition of a Breaks clause (i.e. the content
+ of the packages are unaffected, just the meta-data).
+ 
+ The major cause for concern is that we are not 100% certain that the
+ Breaks addition is sufficient to fix this. The Debian policy manual is
+ ambiguous as to whether Breaks implies that the fixed package must be
+ unpacked *before* the prerm maintscript of the package it breaks is
+ executed; the policy manual mentions this must happen before the
+ "unpack" phase, but prerm scripts run *before* the unpack phase.
+ However, in all experiments run so far, this did indeed resolve the
+ problem.
+ 
+ Still, as an extra hedge against failure here, we intend that the
+ python3-defaults SRU is released ASAP, and that we then delay a week to
+ allow it to propagate before releasing SRUs for the affected packages.
+ 
+ [ Original Description ]
+ 
  We noticed this in bug 2060769 but think it is a separate issue.
  
  dh_python3 is putting a py3clean invocation into package prerm
  maintainer scripts. When that runs, it explodes if the system character
  set is for example ISO-8859-1.
  
  This appears to affect every package for which dh_python3 has inserted a
  call to py3clean into the package prerm.
  
  python3-minimal 3.12.3-0ubuntu1
  
  In this reproducer, cloud-init is at 24.1.3-0ubuntu3.3.
  
  Steps to reproduce:
  
  $ lxc launch ubuntu:noble rbasak-pro-l8n
  $ lxc shell rbasak-pro-l8n
  # locale-gen fr_FR
  Generating locales (this might take a while)...
-   fr_FR.ISO-8859-1... done
+   fr_FR.ISO-8859-1... done
  Generation complete.
  # update-locale LANG=fr_FR
  # exit
  # adjust terminal to ISO-8859-1
  $ lxc shell rbasak-pro-l8n
  # apt update && apt install --reinstall cloud-init
  
  Expected results: success
  
  Actual results:
  
  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances... Fait
- Lecture des informations d'état... Fait
+ Lecture des informations d'état... Fait
  0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 5 non 
mis à jour.
  Il est nécessaire de prendre 598 ko dans les archives.
  Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
  Réception de :1 http://arc

[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set

[Dave Jones]

** Tags added: foundations-todo

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

Title:
  [SRU] py3clean fails when using alternate character set

Status in cloud-init package in Ubuntu:
  New
Status in dh-python package in Ubuntu:
  Invalid
Status in python3-defaults package in Ubuntu:
  Confirmed
Status in ubuntu-advantage-tools package in Ubuntu:
  New
Status in cloud-init source package in Jammy:
  Invalid
Status in dh-python source package in Jammy:
  Invalid
Status in python3-defaults source package in Jammy:
  Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
  Invalid
Status in cloud-init source package in Noble:
  Fix Committed
Status in dh-python source package in Noble:
  Invalid
Status in python3-defaults source package in Noble:
  Fix Committed
Status in ubuntu-advantage-tools source package in Noble:
  New

Bug description:
  [ Impact ]

  With the current version of python3-defaults in jammy and noble,
  packages which utilize py3compile and py3clean in their maintscripts
  (which is more or less any package which includes Python modules), and
  which also are affected by diversions installed by dpkg-divert, will
  fail to install/upgrade/remove on systems with non-UTF-8 locales,
  which include non-ASCII characters in their localized dpkg -L messages
  (and which therefore produce output that is not valid UTF-8).

  As this has the potential to break apt upgrade, the impact is quite
  severe (especially if this occurs during a dist-upgrade). However, the
  scope is probably *fairly* limited given this only affects systems
  with non-UTF-8 locales (something that has not been the default for
  many years), and which produce non-ASCII output (e.g. French
  characters with diacriticals) in their localized messages for dpkg -L.

  [ Rectification Plan ]

  Firstly, python3-defaults must be patched in oracular, noble, and
  jammy. doko has uploaded the fix upstream and synced this to oracular.
  Benjamin has sponsored the noble and jammy SRUs.

  Next, affected packages must be patched to include a "Breaks" line on
  earlier versions of python3-minimal (the python3-defaults binary
  package containing py3clean and py3compile).

  Packages which install Python modules are easily selected, but those
  affected by diversions are (computationally) impossible to select (see
  comment 18 for details). Thus, determining the set of affected
  packages was non-trivial, but Benjamin has kindly produced such a list
  by empirical means (see comment 24). These will be added to the ticket
  as they are uploaded.

  [ Known affected packages ]

  ```
  $ for section in main restricted universe multiverse; do echo "noble 
$section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM 
package_affected WHERE section = '$section' and install_affected = 1 AND 
(remove_affected = 1 OR remove_affected ISNULL) ORDER BY package;"; echo; done
  noble main:
  cloud-init|cloud-init
  nvme-stas|nvme-stas
  python3-rtslib-fb|python-rtslib-fb
  targetcli-fb|targetcli-fb
  ubiquity|ubiquity
  ubiquity-frontend-debconf|ubiquity
  ubiquity-frontend-gtk|ubiquity
  ubuntu-drivers-common|ubuntu-drivers-common
  ubuntu-pro-client|ubuntu-advantage-tools
  walinuxagent|walinuxagent

  noble restricted:

  noble universe:
  a2d|a2d
  apertium-apy|apertium-apy
  blueman|blueman
  borgmatic|borgmatic
  condor|condor
  cpupower-gui|cpupower-gui
  debomatic|debomatic
  dell-recovery|dell-recovery
  deluge-web|deluge
  depthcharge-tools|depthcharge-tools
  dhcpy6d|dhcpy6d
  dkimpy-milter|dkimpy-milter
  fenrir|fenrir
  galileo|galileo
  glances|glances
  graphite-carbon|graphite-carbon
  grokmirror|grokmirror
  guerillabackup|guerillabackup
  ionit|ionit
  jupyterhub|jupyterhub
  liquidctl|liquidctl
  localslackirc|localslackirc
  logdata-anomaly-miner|logdata-anomaly-miner
  lomiri|lomiri
  mailman3|mailman3
  mailman3-full|mailman3
  matrix-sydent|matrix-sydent
  mom|mom
  mopidy|mopidy
  mpd-sima|mpd-sima
  nordugrid-arc-arex|nordugrid-arc
  notus-scanner|notus-scanner
  nrpe-ng|nrpe-ng
  onionprobe|onionprobe
  openscap-daemon|openscap-daemon
  ospd-openvas|ospd-openvas
  pagekite|pagekite
  pagure|pagure
  pagure-ev-server|pagure
  pagure-milters|pagure
  pglistener|pglistener
  policyd-rate-limit|policyd-rate-limit
  postfix-mta-sts-resolver|postfix-mta-sts-resolver
  powa-collector|powa-collector
  prelude-correlator|prelude-correlator
  prometheus-pgbouncer-exporter|prometheus-pgbouncer-exporter
  prometheus-xmpp-alerts|prometheus-xmpp-alerts
  pyroman|pyroman
  python3-autopilot|autopilot
  python3-btchip|btchip-python
  python3-pyro5|pyro5
  qweborf|weborf
  razercfg|razercfg
  sgt-launcher|sgt-launcher
  sms4you|sms4you
  supervisor|supervisor
  syncplay-server|syncplay
  timekpr-next|timekpr-next
  twms|twms
  ubiquity-frontend-kde|ubiquity
  vanguards|vanguards
  vault

[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set

[Dave Jones]

@mfo re: comment 91 on nordugrid: I've re-uploaded with the (horrible :)
spacing restored. The Breaks being against nordugrid-arc-arex and
nothing else is indeed deliberate and correct. The bug only affects
those binary packages which 1) contain python modules (which this
package does) and 2) are affected by diversions (which this package is).
The python3-nordugrid package satisfies the first condition, but isn't
affected by diversions so it isn't affected. What may be confusing is
that it isn't the only package to contain python modules in the suite.

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

Title:
  [SRU] py3clean fails when using alternate character set

Status in cloud-init package in Ubuntu:
  New
Status in dh-python package in Ubuntu:
  Invalid
Status in logdata-anomaly-miner package in Ubuntu:
  Invalid
Status in lomiri package in Ubuntu:
  Invalid
Status in mailman3 package in Ubuntu:
  Invalid
Status in matrix-sydent package in Ubuntu:
  Invalid
Status in mom package in Ubuntu:
  Invalid
Status in mopidy package in Ubuntu:
  Invalid
Status in mpd-sima package in Ubuntu:
  Invalid
Status in nordugrid-arc package in Ubuntu:
  Invalid
Status in notus-scanner package in Ubuntu:
  Invalid
Status in nrpe-ng package in Ubuntu:
  Invalid
Status in onionprobe package in Ubuntu:
  Invalid
Status in openscap-daemon package in Ubuntu:
  Invalid
Status in ospd-openvas package in Ubuntu:
  Invalid
Status in pagekite package in Ubuntu:
  Invalid
Status in pagure package in Ubuntu:
  Invalid
Status in pglistener package in Ubuntu:
  Invalid
Status in policyd-rate-limit package in Ubuntu:
  Invalid
Status in postfix-mta-sts-resolver package in Ubuntu:
  Invalid
Status in powa-collector package in Ubuntu:
  Invalid
Status in prelude-correlator package in Ubuntu:
  Invalid
Status in prometheus-pgbouncer-exporter package in Ubuntu:
  Invalid
Status in prometheus-xmpp-alerts package in Ubuntu:
  Invalid
Status in pyro5 package in Ubuntu:
  Invalid
Status in pyroman package in Ubuntu:
  Invalid
Status in python3-defaults package in Ubuntu:
  Fix Released
Status in r4d package in Ubuntu:
  Invalid
Status in razercfg package in Ubuntu:
  Invalid
Status in sgt-launcher package in Ubuntu:
  Fix Released
Status in sms4you package in Ubuntu:
  Invalid
Status in supervisor package in Ubuntu:
  Invalid
Status in syncplay package in Ubuntu:
  Invalid
Status in timekpr-next package in Ubuntu:
  Fix Released
Status in twms package in Ubuntu:
  Invalid
Status in ubuntu-advantage-tools package in Ubuntu:
  New
Status in vanguards package in Ubuntu:
  Incomplete
Status in vaultlocker package in Ubuntu:
  Invalid
Status in virtualbox package in Ubuntu:
  Invalid
Status in voctomix-outcasts package in Ubuntu:
  Invalid
Status in weborf package in Ubuntu:
  Invalid
Status in xdiagnose package in Ubuntu:
  Fix Released
Status in cloud-init source package in Jammy:
  Invalid
Status in dh-python source package in Jammy:
  Invalid
Status in logdata-anomaly-miner source package in Jammy:
  Invalid
Status in lomiri source package in Jammy:
  Invalid
Status in mailman3 source package in Jammy:
  Invalid
Status in matrix-sydent source package in Jammy:
  Invalid
Status in mom source package in Jammy:
  Invalid
Status in mopidy source package in Jammy:
  Invalid
Status in mpd-sima source package in Jammy:
  Invalid
Status in nordugrid-arc source package in Jammy:
  Invalid
Status in notus-scanner source package in Jammy:
  Invalid
Status in nrpe-ng source package in Jammy:
  Invalid
Status in onionprobe source package in Jammy:
  Invalid
Status in openscap-daemon source package in Jammy:
  Invalid
Status in ospd-openvas source package in Jammy:
  Invalid
Status in pagekite source package in Jammy:
  Invalid
Status in pagure source package in Jammy:
  Invalid
Status in pglistener source package in Jammy:
  Invalid
Status in policyd-rate-limit source package in Jammy:
  Invalid
Status in postfix-mta-sts-resolver source package in Jammy:
  Invalid
Status in powa-collector source package in Jammy:
  Invalid
Status in prelude-correlator source package in Jammy:
  Invalid
Status in prometheus-pgbouncer-exporter source package in Jammy:
  Invalid
Status in prometheus-xmpp-alerts source package in Jammy:
  Invalid
Status in pyro5 source package in Jammy:
  Invalid
Status in pyroman source package in Jammy:
  Invalid
Status in python3-defaults source package in Jammy:
  Fix Released
Status in r4d source package in Jammy:
  Invalid
Status in razercfg source package in Jammy:
  Invalid
Status in sgt-launcher source package in Jammy:
  New
Status in sms4you source package in Jammy:
  Invalid
Status in supervisor source package in Jammy:
  Invalid
Status in syncplay source package in Jammy:
  Invalid
Status in timekpr-next source package in Jammy:
  Invalid
Status in twms source package in Jammy:
  Invalid
Status in ub

[Touch-packages] [Bug 1999258] [NEW] Please merge dbus 1.14.4-1 from Debian unstable.

[Dave Jones]

Public bug reported:

Please merge dbus 1.14.4-1 from Debian unstable.

Updated changelog and diff against Debian unstable to be attached below.

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

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

Title:
  Please merge dbus 1.14.4-1 from Debian unstable.

Status in dbus package in Ubuntu:
  New

Bug description:
  Please merge dbus 1.14.4-1 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1999258/+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 1999258] Re: Please merge dbus 1.14.4-1 from Debian unstable.

[Dave Jones]

Attaching patch against Debian unstable. For ease of review, relevant commits
and tags have been pushed to the following repository:

https://code.launchpad.net/~waveform/ubuntu/+source/dbus/+git/dbus

Specifically:

* logical/1.14.0-2ubuntu3 represents our split-out delta on top of old/debian 
(1.14.0-2)
* logical/1.14.4-1ubuntu1 represents our rebased delta on top of new/debian 
(1.14.4-1)
* merge/1.14.4-1ubuntu1 just adds changelog and maintainer changes on top of 
logical/1.14.4-1ubuntu1

Hence, the following command may produce output useful to the purposes
of review:

git range-diff old/debian..logical/1.14.0-2ubuntu3
new/debian..logical/1.14.4-1ubuntu1

Test packages are building in ppa:waveform/dbus
(https://launchpad.net/~waveform/+archive/ubuntu/dbus)

** Patch added: "1-1999258.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1999258/+attachment/5635632/+files/1-1999258.debdiff

** Tags added: fr-3127

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

Title:
  Please merge dbus 1.14.4-1 from Debian unstable.

Status in dbus package in Ubuntu:
  New

Bug description:
  Please merge dbus 1.14.4-1 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1999258/+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 2001568] [NEW] unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

[Dave Jones]

Public bug reported:

u-u is currently failing autopkgtest on arm64. It does not look like
this is a new failure (2.8ubuntu1 appears to have had exactly the same
failure) but it's due to the kernel-patterns test assuming that kernel
flavors cannot be a suffix of each other. This is true under Debian, and
under several architectures on Ubuntu, but the arm64 architecture on
Ubuntu has -generic and -generic-64k flavors which cause the test to
fail.

The attached debdiff corrects the test for this case.

One may wonder why the test currently passes under armhf, which has
-generic and -generic-lpae flavors (I certainly did!). It turns out this
is only because Ubuntu autopkgtest runs armhf in a container so the
kernel release reported by "uname -r" (used in the test) does not
meaningfully match anything in the apt cache.

Given this, the attached debdiff also restricts the kernel-patterns test
to isolation-machine as the test assumes a meaningful link between the
running kernel and the packages in the archive which is only true in a
VM or on the bare metal.

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

** Patch added: "uu-arm64-kernels.patch"
   
https://bugs.launchpad.net/bugs/2001568/+attachment/5639008/+files/uu-arm64-kernels.patch

** Patch removed: "uu-arm64-kernels.patch"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2001568/+attachment/5639008/+files/uu-arm64-kernels.patch

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

Title:
  unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  u-u is currently failing autopkgtest on arm64. It does not look like
  this is a new failure (2.8ubuntu1 appears to have had exactly the same
  failure) but it's due to the kernel-patterns test assuming that kernel
  flavors cannot be a suffix of each other. This is true under Debian,
  and under several architectures on Ubuntu, but the arm64 architecture
  on Ubuntu has -generic and -generic-64k flavors which cause the test
  to fail.

  The attached debdiff corrects the test for this case.

  One may wonder why the test currently passes under armhf, which has
  -generic and -generic-lpae flavors (I certainly did!). It turns out
  this is only because Ubuntu autopkgtest runs armhf in a container so
  the kernel release reported by "uname -r" (used in the test) does not
  meaningfully match anything in the apt cache.

  Given this, the attached debdiff also restricts the kernel-patterns
  test to isolation-machine as the test assumes a meaningful link
  between the running kernel and the packages in the archive which is
  only true in a VM or on the bare metal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2001568/+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 2001568] Re: unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

[Dave Jones]

** Patch added: "uu-arm64-kernels.patch"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2001568/+attachment/5639009/+files/uu-arm64-kernels.patch

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

Title:
  unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  u-u is currently failing autopkgtest on arm64. It does not look like
  this is a new failure (2.8ubuntu1 appears to have had exactly the same
  failure) but it's due to the kernel-patterns test assuming that kernel
  flavors cannot be a suffix of each other. This is true under Debian,
  and under several architectures on Ubuntu, but the arm64 architecture
  on Ubuntu has -generic and -generic-64k flavors which cause the test
  to fail.

  The attached debdiff corrects the test for this case.

  One may wonder why the test currently passes under armhf, which has
  -generic and -generic-lpae flavors (I certainly did!). It turns out
  this is only because Ubuntu autopkgtest runs armhf in a container so
  the kernel release reported by "uname -r" (used in the test) does not
  meaningfully match anything in the apt cache.

  Given this, the attached debdiff also restricts the kernel-patterns
  test to isolation-machine as the test assumes a meaningful link
  between the running kernel and the packages in the archive which is
  only true in a VM or on the bare metal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2001568/+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 2002318] [NEW] Please merge lsb 11.5 from Debian unstable.

[Dave Jones]

Public bug reported:

Please merge lsb 11.5 from Debian unstable.

Updated changelog and diff against Debian unstable to be attached below.

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

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

Title:
  Please merge lsb 11.5 from Debian unstable.

Status in lsb package in Ubuntu:
  New

Bug description:
  Please merge lsb 11.5 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/2002318/+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 2002318] Re: Please merge lsb 11.5 from Debian unstable.

[Dave Jones]

Attaching patch against Debian unstable. For ease of review, relevant
commits and tags have been pushed to the following repository:

https://code.launchpad.net/~waveform/ubuntu/+source/lsb/+git/lsb

Specifically:

* logical/11.2ubuntu1 represents our split-out delta on
  top of old/debian (11.2)
* logical/11.5ubuntu1 represents our rebased delta on
  top of new/debian (11.5)
* merge/11.5ubuntu1 adds changelog and maintainer
  changes on top of logical/11.5ubuntu1, and then a pile of fixes to
  tidy up all the lintian warnings and patch various historically
  broken pieces.

Hence, the following commands may produce output useful to the purposes
of review. The first compares the rebased delta against the old delta:

git range-diff --creation-factor=100 old/debian..logical/11.2ubuntu1
new/debian..logical/11.5ubuntu1

The second shows the additional fixes added to the rebased delta to fix
the lintian warnings and historically broken functionality:

git show logical/11.5ubuntu1..merge/11.5ubuntu1

I should additionally note that the historical breakage mentioned above
includes the fact that certain aspects of lsbinstall have not worked
for roughly 17 years (save_lsbinstall_info in initdutils.py has had the
wrong argument order to cPickle.dump / pickle.dump for its entire
history).

We should try and determine if anything in this package is really still
used (if it ever was) and follow Debian in expunging it if not because
at this point the entire package is pretty much a delta. Incidentally,
this is why I've also taken the liberty of replacing "Debian" with
"Ubuntu" in the d/control descriptions as it seems unfair to be
referencing Debian when the package is now empty upstream. 

** Patch added: "1-2002318.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/2002318/+attachment/5640743/+files/1-2002318.debdiff

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

Title:
  Please merge lsb 11.5 from Debian unstable.

Status in lsb package in Ubuntu:
  New

Bug description:
  Please merge lsb 11.5 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/2002318/+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 2004430] [NEW] Migrate raspberry pi image hacks from livecd-rootfs

[Dave Jones]

Public bug reported:

There are currently several "hacks" in livecd-rootfs that introduce
unpackaged files and/or services. In particular, everything in
https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live-
build/ubuntu/hooks/099-ubuntu-image-customization.chroot dealing with
the fstab and the swapfile needs to go. The new ubuntu-image based
process for generating images won't be using these; anything to do with
the fstab needs to go in the image-definition yaml, and the swapfile
services ought to be owned by the ubuntu-raspi-settings-desktop package
anyway.

** Affects: livecd-rootfs (Ubuntu)
 Importance: Undecided
 Assignee: Dave Jones (waveform)
 Status: New

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Assignee: Dave Jones (waveform)
 Status: New

** Also affects: livecd-rootfs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: ubuntu-settings (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  Migrate raspberry pi image hacks from livecd-rootfs

Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  There are currently several "hacks" in livecd-rootfs that introduce
  unpackaged files and/or services. In particular, everything in
  https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live-
  build/ubuntu/hooks/099-ubuntu-image-customization.chroot dealing with
  the fstab and the swapfile needs to go. The new ubuntu-image based
  process for generating images won't be using these; anything to do
  with the fstab needs to go in the image-definition yaml, and the
  swapfile services ought to be owned by the ubuntu-raspi-settings-
  desktop package anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2004430/+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 2004430] Re: Migrate raspberry pi image hacks from livecd-rootfs

[Dave Jones]

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/436647

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/livecd-rootfs/+git/livecd-rootfs/+merge/436648

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

Title:
  Migrate raspberry pi image hacks from livecd-rootfs

Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  There are currently several "hacks" in livecd-rootfs that introduce
  unpackaged files and/or services. In particular, everything in
  https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live-
  build/ubuntu/hooks/099-ubuntu-image-customization.chroot dealing with
  the fstab and the swapfile needs to go. The new ubuntu-image based
  process for generating images won't be using these; anything to do
  with the fstab needs to go in the image-definition yaml, and the
  swapfile services ought to be owned by the ubuntu-raspi-settings-
  desktop package anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2004430/+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 2004430] Re: Migrate raspberry pi image hacks from livecd-rootfs

[Dave Jones]

** Changed in: livecd-rootfs (Ubuntu)
Milestone: None => ubuntu-23.04

** Changed in: ubuntu-settings (Ubuntu)
Milestone: None => ubuntu-23.04

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

Title:
  Migrate raspberry pi image hacks from livecd-rootfs

Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  There are currently several "hacks" in livecd-rootfs that introduce
  unpackaged files and/or services. In particular, everything in
  https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live-
  build/ubuntu/hooks/099-ubuntu-image-customization.chroot dealing with
  the fstab and the swapfile needs to go. The new ubuntu-image based
  process for generating images won't be using these; anything to do
  with the fstab needs to go in the image-definition yaml, and the
  swapfile services ought to be owned by the ubuntu-raspi-settings-
  desktop package anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2004430/+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 2001568] Re: unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

[Dave Jones]

It looks like Debian independently fixed the running_escape_regexp line
in January (in 2.9.1+nmu3 [1]). The d/t/control fix isn't *strictly*
necessary to fix this and is more a matter of fixing semantics -- but
I'll try and forward that change if I can figure out where to submit a
PR (doesn't appear u-u is in salsa, and the GH Vcs-Git repo is way
behind where it's meant to be).

[1]: https://tracker.debian.org/news/1405664/accepted-unattended-
upgrades-291nmu3-source-into-unstable/

** Changed in: unattended-upgrades (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  u-u is currently failing autopkgtest on arm64. It does not look like
  this is a new failure (2.8ubuntu1 appears to have had exactly the same
  failure) but it's due to the kernel-patterns test assuming that kernel
  flavors cannot be a suffix of each other. This is true under Debian,
  and under several architectures on Ubuntu, but the arm64 architecture
  on Ubuntu has -generic and -generic-64k flavors which cause the test
  to fail.

  The attached debdiff corrects the test for this case.

  One may wonder why the test currently passes under armhf, which has
  -generic and -generic-lpae flavors (I certainly did!). It turns out
  this is only because Ubuntu autopkgtest runs armhf in a container so
  the kernel release reported by "uname -r" (used in the test) does not
  meaningfully match anything in the apt cache.

  Given this, the attached debdiff also restricts the kernel-patterns
  test to isolation-machine as the test assumes a meaningful link
  between the running kernel and the packages in the archive which is
  only true in a VM or on the bare metal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2001568/+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 2013080] [NEW] On rpi desktop images, grow root leaving slack for LUKS

[Dave Jones]

Public bug reported:

To aid in user-implemented FDE we wish to leave 16MB of the file-system
unexpanded during first boot. The growth of the partition is unaffected,
but rather than relying on systemd's growfs facility in fstab, we should
use a service that runs a simple script to handle calculating the resize
in early boot.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Assignee: Dave Jones (waveform)
 Status: New

** Changed in: ubuntu-settings (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: ubuntu-settings (Ubuntu)
Milestone: None => ubuntu-23.04

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

Title:
  On rpi desktop images, grow root leaving slack for LUKS

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  To aid in user-implemented FDE we wish to leave 16MB of the file-
  system unexpanded during first boot. The growth of the partition is
  unaffected, but rather than relying on systemd's growfs facility in
  fstab, we should use a service that runs a simple script to handle
  calculating the resize in early boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2013080/+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 2013080] Re: On rpi desktop images, grow root leaving slack for LUKS

[Dave Jones]

This should only be merged once LP: #2004430 as it builds upon those
commits.

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/439835

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/livecd-rootfs/+git/livecd-rootfs/+merge/439842

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

Title:
  On rpi desktop images, grow root leaving slack for LUKS

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  To aid in user-implemented FDE we wish to leave 16MB of the file-
  system unexpanded during first boot. The growth of the partition is
  unaffected, but rather than relying on systemd's growfs facility in
  fstab, we should use a service that runs a simple script to handle
  calculating the resize in early boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2013080/+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 2038964] [NEW] raspi ethernet rename is racy

[Dave Jones]

Public bug reported:

The renaming of the ethernet interface (controlled by 10-raspi-eth0.link
in ubuntu-raspi-settings) turns out to be racy. Specifically, in the
final mantic server images (but not the desktop images), under armhf or
arm64, on the Raspberry Pi 3B+ (but not any other supported board,
including the 3B), the interface renames several times during boot. By
the end, the interface is left in the enxMACMACMAC state and the netplan
configuration fails to apply.

Will attach kern.log from an affected platform, and another from an
unaffected platform.

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


** Tags: raspi-image

** Tags added: raspi-image

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy

[Dave Jones]

** Attachment added: "kern.log from affected 3B+"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708341/+files/affected.log

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy

[Dave Jones]

** Attachment added: "kern.log from unaffected 2B (rev 1.2)"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708342/+files/unaffected.log

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy

[Dave Jones]

** Changed in: ubuntu-settings (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy

[Dave Jones]

There does seem to be something unusual going on with the lan78xx re-
initializing (or restarting?) part way through the boot sequence,
causing another round of renaming to kick off (and then everything
fails). Bizarre.

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy

[Dave Jones]

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/453340

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy

[Dave Jones]

Figured out a work-around: ensure the matching state of the rename rule
matches the end-state of the rename rule so the networkd state machine
stops flopping between the two rules. Linked the MP with the required
change; will tag ubuntu-release to see if it's not too late for a re-
spin.

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2037642] Re: [FFe] Raspberry Pi 5 support

[Dave Jones]

** Changed in: ubuntu-release-notes
   Status: In Progress => Fix Released

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

Title:
  [FFe] Raspberry Pi 5 support

Status in Release Notes for Ubuntu:
  Fix Released
Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Invalid
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+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

[Dave Jones]

Is this fixed in noble now? No. Is this due to be fixed; I've not heard
anything, but happy to be corrected if this is on a roadmap somewhere?

-- 
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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

[Dave Jones]

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/455178

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Mantic:
  New

Bug description:
  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

[Dave Jones]

Thanks for the quick review! Could someone set up a "mantic" branch on
the lp:~ubuntu-desktop/ubuntu/+source/ubuntu-settings repository so I
can propose a merge to fix mantic too? (basically the same commit with a
lower version number)

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Mantic:
  New

Bug description:
  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

[Dave Jones]

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/455407

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Mantic:
  New

Bug description:
  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Dave Jones]

It appears this has come up before, and was discussed upstream. [1] and
[2] cover discussion of whether --rcfile should ignore the system-wide
bashrc (SYS_BASHRC hereafter), with the conclusion from upstream that it
should not. [3] is an attempt by someone to fix this upstream by
modifying bash's behaviour, which is rejected by the upstream
developers. [4] and [5] are the upstream Debian bugs (which I'll link
this bug to).

At any rate, upstream bash devs have made their position quite clear:
the Debian-patched documentation is wrong, and the behaviour of bash is
as expected. So, the solution to this bug is to fix the documentation.
I'll propose an updated patch here and see if we can't put this decade-
old bug to bed!

I'll also try and rebase the noble patch upstream for Debian (there's
already a patch there, but it's predictably ancient).

[1]: https://lists.gnu.org/archive/html/bug-bash/2018-01/msg3.html

[2]: https://lists.gnu.org/archive/html/bug-bash/2009-05/msg00031.html

[3]: https://savannah.gnu.org/support/index.php?107950

[4]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516152

[5]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343673

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

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

** Also affects: gnubash via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516152
   Importance: Unknown
   Status: Unknown

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  Unknown
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

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

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Dave Jones]

** Patch added: "1097467-1.debdiff"
   
https://bugs.launchpad.net/gnubash/+bug/1097467/+attachment/5719274/+files/1097467-1.debdiff

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  Unknown
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

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

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Dave Jones]

Doh, I always forget something...

** Patch added: "1097467-2.debdiff"
   
https://bugs.launchpad.net/gnubash/+bug/1097467/+attachment/5719318/+files/1097467-2.debdiff

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  New
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

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

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot

[Dave Jones]

** Changed in: pulseaudio (Ubuntu)
 Assignee: Dave Jones (waveform) => (unassigned)

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

Title:
  switch-on-connect mistakes startup for USB hotplug, so seemingly
  ignores the old default device on reboot

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in ubuntu-settings package in Ubuntu:
  Invalid
Status in pulseaudio source package in Jammy:
  Confirmed
Status in ubuntu-settings source package in Jammy:
  Invalid
Status in pulseaudio source package in Kinetic:
  Won't Fix
Status in ubuntu-settings source package in Kinetic:
  Invalid

Bug description:
  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Only difference is that it does not reset to HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.

  In short:
  1. Boot system
  2. "Analogue Output - RODE NT-USB" is selected by default. I want to use 
"Line Out - Built-in Audio", which I choose.
  3. Reboot.
  4 Output device is now back to "Analogue Output - RODE NT-USB".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcus 1604 F pulseaudio
   /dev/snd/controlC0:  marcus 1604 F pulseaudio
   /dev/snd/controlC1:  marcus 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

[Dave Jones]

This has been fixed for a couple of releases now (since lunar I
believe), and if I recall correctly the issue was indeed the wpe backend
mentioned in comment 17. That would suggest this should be "invalid" for
gtk and yelp, and "fix released" for webkit2gtk.

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in webkit2gtk package in Ubuntu:
  Incomplete
Status in yelp package in Ubuntu:
  Incomplete

Bug description:
  On the jammy Pi desktop, under a wayland session, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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

[Dave Jones]

Setting network-manager back to confirmed as I think the case is made
that this is an issue, despite upstream having reservations about
whether network-manager is quite the right place for this particular
setting. Also setting netplan.io in jammy to fix released as 0.105 was
back-ported there quite a while ago now and the current (22.04.3) image
should support setting this at first-boot. Setting kinetic to won't fix
(as it's EOL).

** Changed in: network-manager (Ubuntu Kinetic)
   Status: Incomplete => Won't Fix

** Changed in: network-manager (Ubuntu Jammy)
   Status: Incomplete => Confirmed

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: netplan.io (Ubuntu Jammy)
   Status: Triaged => Fix Released

** Changed in: netplan
 Assignee: Lukas Märdian (slyon) => (unassigned)

** Also affects: network-manager (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

** Also affects: network-manager (Ubuntu Noble)
   Importance: Low
   Status: Confirmed

** Also affects: netplan.io (Ubuntu Noble)
   Importance: Medium
   Status: Fix Released

** Also affects: network-manager (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

** Changed in: netplan.io (Ubuntu Lunar)
   Status: New => Fix Released

** Changed in: netplan.io (Ubuntu Mantic)
   Status: New => Fix Released

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

** Changed in: network-manager (Ubuntu Lunar)
   Status: New => Confirmed

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

** Changed in: network-manager (Ubuntu Mantic)
   Status: New => Confirmed

-- 
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:
  Confirmed
Status in netplan.io source package in Jammy:
  Fix Released
Status in network-manager source package in Jammy:
  Confirmed
Status in netplan.io source package in Kinetic:
  Fix Released
Status in network-manager source package in Kinetic:
  Won't Fix
Status in netplan.io source package in Lunar:
  Fix Released
Status in network-manager source package in Lunar:
  Confirmed
Status in netplan.io source package in Mantic:
  Fix Released
Status in network-manager source package in Mantic:
  Confirmed
Status in netplan.io source package in Noble:
  Fix Released
Status in network-manager source package in Noble:
  Confirmed

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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

[Dave Jones]

Thanks very much for the updated debdiff. There's a lot of changes here
to look at and unfortunately I've run out of time looking through it all
during my patch-pilot shift, but here's what I've got so far:

The major thing that I think needs correction is that this patch is
built on top of ubuntu/noble-devel by importing the upstream 5.0.3, but
what Stéphane suggested in comment 14 was to take the Debian upstream
(currently 5.0.3-2) and build on top of that. In this case, the commits
in the repo would be based on debian/sid rather than ubuntu/noble-devel.
This would ensure we incorporate the changes Debian has placed on top of
lxc, as well as our own (and means in future we can follow the git-
ubuntu merge process for this package).

The proposed changes also include package renames (which will be
necessary if we're basing off the upstream Debian version). As far as I
can tell they look sane but I haven't dug deep into this bit yet (it's
something I always need to read the policy guides and manuals for!).

The requested autopkgtest to ensure LXC_DEVEL==0 is present, and looks
good.

I have to dash to an appointment now, but I'll try and add some more
notes later this evening.

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

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

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