from:"dave"

** Description changed:

+ [ Impact ]
+ 
+ Pi 5 owners with the D0 stepping will find the noble (24.04) desktop
+ doesn't work at all, including login. While oracular desktop users have
+ a sufficiently up to date mesa, all snaps relying on noble's mesa
+ (firefox, thunderbird, and the snap-store -- all seeded and thus
+ "essential" applications) do not work either on the D0 stepping.
+ 
+ [ Test Plan ]
+ 
+ Given the patches proposed only affect the v3d driver, which is only
+ used on the Pi 4 and Pi 5 hardware, the test plan can reasonably be
+ restricted to boards of this type.
+ 
+ * Flash a 24.04.1 Pi desktop image to a fresh card
+ * Boot card on a D0-stepping Pi 5 (e.g. 2GB board)
+ * Verify that mesa fails to even display the initial setup
+ * Shutdown
+ * Boot card on a pre-D0-stepping board
+ * Run through initial setup
+ * Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed)
+ * Upgrade mesa to proposed version
+ * Reboot
+ * Ensure login and desktop works properly on the pre-D0 board
+ * Test applications; ignore snapped applications until the mesa content snap 
is updated -- test deb-packaged applications, including video players
+ * Shutdown
+ 
+ For all Pi 4 and Pi 5 boards including a D0-stepping board (e.g. Pi 5
+ 2GB), using the upgraded card:
+ 
+ * Boot card on board
+ * Ensure login and desktop works properly on the D0 board
+ * Test applications; ignore snapped applications until the mesa content snap 
is updated -- test deb-packaged applications, including video players
+ 
+ [ Regression Potential ]
+ 
+ Given the changes are restricted to the v3d driver, which itself is only
+ used on the Pi 4 and Pi 5 boards (no other hardware uses this chipset),
+ we can be reasonably confident that only Pi boards are likely to be
+ affected. The test plan above should cover operation on all pre and
+ post-D0 boards, to ensure we do not regress existing operation of the
+ desktop.
+ 
+ [ Original Description ]
+ 
  The Raspberry Pi 5 2GB model now uses the D0 stepping of the 2712 SoC.
  Unfortunately, this is only supported from Mesa 24.2.0 (see
  https://docs.mesa3d.org/relnotes/24.2.0.html -- search for 2712D0). The
  result is corrupted or blank output for the current Ubuntu 24.04.1 Pi
  desktop (using Mesa 24.0.9). The forthcoming oracular desktop does work
  as far as login goes, but snapped applications are still relying on an
  older mesa, thus the software center, firefox, and thunderbird all fail
  to operate.
  
  Although the D0 is only on the 2GB model *currently*, it is anticipated
  to become common to the entire Pi 5 line up going forward, and will be
  present on the forthcoming CM5.
  
  Could we investigate either bumping mesa in noble, and the corresponding
  content snap, or finding the minimal patch-set necessary to support the
  D0 stepping and back-porting that?

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

Title:
  [SRU] Mesa bump to 24.2 required for Pi 2712D0 stepping

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Noble:
  Confirmed

Bug description:
  [ Impact ]

  Pi 5 owners with the D0 stepping will find the noble (24.04) desktop
  doesn't work at all, including login. While oracular desktop users
  have a sufficiently up to date mesa, all snaps relying on noble's mesa
  (firefox, thunderbird, and the snap-store -- all seeded and thus
  "essential" applications) do not work either on the D0 stepping.

  [ Test Plan ]

  Given the patches proposed only affect the v3d driver, which is only
  used on the Pi 4 and Pi 5 hardware, the test plan can reasonably be
  restricted to boards of this type.

  * Flash a 24.04.1 Pi desktop image to a fresh card
  * Boot card on a D0-stepping Pi 5 (e.g. 2GB board)
  * Verify that mesa fails to even display the initial setup
  * Shutdown
  * Boot card on a pre-D0-stepping board
  * Run through initial setup
  * Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed)
  * Upgrade mesa to proposed version
  * Reboot
  * Ensure login and desktop works properly on the pre-D0 board
  * Test applications; ignore snapped applications until the mesa content snap 
is updated -- test deb-packaged applications, including video players
  * Shutdown

  For all Pi 4 and Pi 5 boards including a D0-stepping board (e.g. Pi 5
  2GB), using the upgraded card:

  * Boot card on board
  * Ensure login and desktop works properly on the D0 board
  * Test applications; ignore snapped applications until the mesa content snap 
is updated -- test deb-packaged applications, including video players

  [ Regression Potential ]

  Given the changes are restricted to the v3d driver, which itself is
  only used on the Pi 4 and Pi 5 boards (no other hardware uses this
  chipset), we can be reasonably confident that only Pi boards are
  likely to be affected. The test plan above should co

[Touch-packages] [Bug 2082072] Re: [SRU] Mesa bump to 24.2 required for Pi 2712D0 stepping

** Summary changed:

- Mesa bump to 24.2 required for Pi 2712D0 stepping
+ [SRU] Mesa bump to 24.2 required for Pi 2712D0 stepping

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

Title:
  [SRU] Mesa bump to 24.2 required for Pi 2712D0 stepping

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Noble:
  Confirmed

Bug description:
  The Raspberry Pi 5 2GB model now uses the D0 stepping of the 2712 SoC.
  Unfortunately, this is only supported from Mesa 24.2.0 (see
  https://docs.mesa3d.org/relnotes/24.2.0.html -- search for 2712D0).
  The result is corrupted or blank output for the current Ubuntu 24.04.1
  Pi desktop (using Mesa 24.0.9). The forthcoming oracular desktop does
  work as far as login goes, but snapped applications are still relying
  on an older mesa, thus the software center, firefox, and thunderbird
  all fail to operate.

  Although the D0 is only on the 2GB model *currently*, it is
  anticipated to become common to the entire Pi 5 line up going forward,
  and will be present on the forthcoming CM5.

  Could we investigate either bumping mesa in noble, and the
  corresponding content snap, or finding the minimal patch-set necessary
  to support the D0 stepping and back-porting that?

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


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

[Touch-packages] [Bug 2082072] Re: Mesa bump to 24.2 required for Pi 2712D0 stepping

I'm informed the three commits that require backporting for D0 support
are:

b545e78f12b v3dv: support 2712D0
 
1fc846dce39 v3d: support 2712D0 
 
7b807c3e948 broadcom/cle: fix up shader record for V3D 7.1.10 / 2712D0

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

Title:
  Mesa bump to 24.2 required for Pi 2712D0 stepping

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Noble:
  Confirmed

Bug description:
  The Raspberry Pi 5 2GB model now uses the D0 stepping of the 2712 SoC.
  Unfortunately, this is only supported from Mesa 24.2.0 (see
  https://docs.mesa3d.org/relnotes/24.2.0.html -- search for 2712D0).
  The result is corrupted or blank output for the current Ubuntu 24.04.1
  Pi desktop (using Mesa 24.0.9). The forthcoming oracular desktop does
  work as far as login goes, but snapped applications are still relying
  on an older mesa, thus the software center, firefox, and thunderbird
  all fail to operate.

  Although the D0 is only on the 2GB model *currently*, it is
  anticipated to become common to the entire Pi 5 line up going forward,
  and will be present on the forthcoming CM5.

  Could we investigate either bumping mesa in noble, and the
  corresponding content snap, or finding the minimal patch-set necessary
  to support the D0 stepping and back-porting that?

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


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

[Touch-packages] [Bug 2082072] Re: Mesa bump to 24.2 required for Pi 2712D0 stepping

My uneducated guess is that this is the source of the incompatibility:

/* 2712D0 (V3D 7.1.10) has included draw index and base vertex,
 * shuffling all the fields in the packet. Since the versioning
 * framework doesn't handle revision numbers, the XML has a
 * different shader state record packet including the new fields
 * and we decide at run time which packet we need to emit.

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

Title:
  Mesa bump to 24.2 required for Pi 2712D0 stepping

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Noble:
  Confirmed

Bug description:
  The Raspberry Pi 5 2GB model now uses the D0 stepping of the 2712 SoC.
  Unfortunately, this is only supported from Mesa 24.2.0 (see
  https://docs.mesa3d.org/relnotes/24.2.0.html -- search for 2712D0).
  The result is corrupted or blank output for the current Ubuntu 24.04.1
  Pi desktop (using Mesa 24.0.9). The forthcoming oracular desktop does
  work as far as login goes, but snapped applications are still relying
  on an older mesa, thus the software center, firefox, and thunderbird
  all fail to operate.

  Although the D0 is only on the 2GB model *currently*, it is
  anticipated to become common to the entire Pi 5 line up going forward,
  and will be present on the forthcoming CM5.

  Could we investigate either bumping mesa in noble, and the
  corresponding content snap, or finding the minimal patch-set necessary
  to support the D0 stepping and back-porting that?

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


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

[Touch-packages] [Bug 2082072] Re: Mesa bump to 24.2 required for Pi 2712D0 stepping

Related mesa bug:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29189

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

Title:
  Mesa bump to 24.2 required for Pi 2712D0 stepping

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Noble:
  Confirmed

Bug description:
  The Raspberry Pi 5 2GB model now uses the D0 stepping of the 2712 SoC.
  Unfortunately, this is only supported from Mesa 24.2.0 (see
  https://docs.mesa3d.org/relnotes/24.2.0.html -- search for 2712D0).
  The result is corrupted or blank output for the current Ubuntu 24.04.1
  Pi desktop (using Mesa 24.0.9). The forthcoming oracular desktop does
  work as far as login goes, but snapped applications are still relying
  on an older mesa, thus the software center, firefox, and thunderbird
  all fail to operate.

  Although the D0 is only on the 2GB model *currently*, it is
  anticipated to become common to the entire Pi 5 line up going forward,
  and will be present on the forthcoming CM5.

  Could we investigate either bumping mesa in noble, and the
  corresponding content snap, or finding the minimal patch-set necessary
  to support the D0 stepping and back-porting that?

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


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

[Touch-packages] [Bug 2082072] [NEW] Mesa bump to 24.2 required for Pi 2712D0 stepping

Public bug reported:

The Raspberry Pi 5 2GB model now uses the D0 stepping of the 2712 SoC.
Unfortunately, this is only supported from Mesa 24.2.0 (see
https://docs.mesa3d.org/relnotes/24.2.0.html -- search for 2712D0). The
result is corrupted or blank output for the current Ubuntu 24.04.1 Pi
desktop (using Mesa 24.0.9). The forthcoming oracular desktop does work
as far as login goes, but snapped applications are still relying on an
older mesa, thus the software center, firefox, and thunderbird all fail
to operate.

Although the D0 is only on the 2GB model *currently*, it is anticipated
to become common to the entire Pi 5 line up going forward, and will be
present on the forthcoming CM5.

Could we investigate either bumping mesa in noble, and the corresponding
content snap, or finding the minimal patch-set necessary to support the
D0 stepping and back-porting that?

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: mesa (Ubuntu Noble)
 Importance: Undecided
 Status: Confirmed

** Also affects: mesa (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Mesa bump to 24.2 required for Pi 2712D0 stepping

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Noble:
  Confirmed

Bug description:
  The Raspberry Pi 5 2GB model now uses the D0 stepping of the 2712 SoC.
  Unfortunately, this is only supported from Mesa 24.2.0 (see
  https://docs.mesa3d.org/relnotes/24.2.0.html -- search for 2712D0).
  The result is corrupted or blank output for the current Ubuntu 24.04.1
  Pi desktop (using Mesa 24.0.9). The forthcoming oracular desktop does
  work as far as login goes, but snapped applications are still relying
  on an older mesa, thus the software center, firefox, and thunderbird
  all fail to operate.

  Although the D0 is only on the 2GB model *currently*, it is
  anticipated to become common to the entire Pi 5 line up going forward,
  and will be present on the forthcoming CM5.

  Could we investigate either bumping mesa in noble, and the
  corresponding content snap, or finding the minimal patch-set necessary
  to support the D0 stepping and back-porting that?

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


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

[Touch-packages] [Bug 2081238] Re: colors inverted on qxl graphics on lubuntu installer only with qxl graphics on vm.

2024-09-25 Thread Dave Jones

Well, not exactly duplicate given that's targetting the snap-store-
desktop package specifically, but the symptom sounds identical, and I
wonder if it's the mesa package underlying both these things (given that
snap-store-desktop is packaged as a snap and is thus using the snap
version of mesa which typically lags the debs).

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

Title:
  colors inverted on qxl graphics on lubuntu installer only with qxl
  graphics on vm.

Status in mesa package in Ubuntu:
  New

Bug description:
  To reproduce download a lubuntu iso and then launch the installer and
  the installer prompt appears orange instead of the blue. If try a vm
  with virtio graphics this does not happen. My host system also 24.10
  also does not color inverted. The blue elements of the installer for
  having something selected also appear orange. The lubuntu installer
  prompt also appears orange when launched with qxl graphics on lubuntu-
  installer prompt.

  xserver-xorg-video-qxl:
Installed: 0.1.6-1build1
Candidate: 0.1.6-1build1
Version table:
   *** 0.1.6-1build1 500
  500 http://archive.ubuntu.com/ubuntu oracular/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:Ubuntu Oracular Oriole (development branch)
  Release:24.10

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: xserver-xorg-video-qxl 0.1.6-1build1
  ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7
  Uname: Linux 6.11.0-7-generic x86_64
  ApportVersion: 2.30.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.502
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Fri Sep 20 00:22:14 2024
  DistUpgraded: Fresh install
  DistroCodename: oracular
  DistroVariant: ubuntu
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  LiveMediaBuild: Lubuntu 24.10 "Oracular Oriole" - Beta amd64 (20240918)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Lsusb-t:
   /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 001: Dev 002, If 0, Class=Human Interface Device, 
Driver=usbhid, 480M
   /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 5000M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
  SourcePackage: xserver-xorg-video-qxl
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.3-debian-1.16.3-2
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-9.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.3-debian-1.16.3-2:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-9.0:cvnQEMU:ct1:cvrpc-q35-9.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-9.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.122-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.13-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-3ubuntu1

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


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

[Touch-packages] [Bug 2081238] Re: colors inverted on qxl graphics on lubuntu installer only with qxl graphics on vm.

2024-09-25 Thread Dave Jones

Possible duplicate of LP: #2076919 ?

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

Title:
  colors inverted on qxl graphics on lubuntu installer only with qxl
  graphics on vm.

Status in mesa package in Ubuntu:
  New

Bug description:
  To reproduce download a lubuntu iso and then launch the installer and
  the installer prompt appears orange instead of the blue. If try a vm
  with virtio graphics this does not happen. My host system also 24.10
  also does not color inverted. The blue elements of the installer for
  having something selected also appear orange. The lubuntu installer
  prompt also appears orange when launched with qxl graphics on lubuntu-
  installer prompt.

  xserver-xorg-video-qxl:
Installed: 0.1.6-1build1
Candidate: 0.1.6-1build1
Version table:
   *** 0.1.6-1build1 500
  500 http://archive.ubuntu.com/ubuntu oracular/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:Ubuntu Oracular Oriole (development branch)
  Release:24.10

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: xserver-xorg-video-qxl 0.1.6-1build1
  ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7
  Uname: Linux 6.11.0-7-generic x86_64
  ApportVersion: 2.30.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.502
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Fri Sep 20 00:22:14 2024
  DistUpgraded: Fresh install
  DistroCodename: oracular
  DistroVariant: ubuntu
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  LiveMediaBuild: Lubuntu 24.10 "Oracular Oriole" - Beta amd64 (20240918)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Lsusb-t:
   /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 001: Dev 002, If 0, Class=Human Interface Device, 
Driver=usbhid, 480M
   /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 5000M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
  SourcePackage: xserver-xorg-video-qxl
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.3-debian-1.16.3-2
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-9.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.3-debian-1.16.3-2:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-9.0:cvnQEMU:ct1:cvrpc-q35-9.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-9.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.122-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.13-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-3ubuntu1

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


-- 
Mailing list: https://launchpad.net/~touch-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

2024-09-20 Thread Dave Jones

** Description changed:

  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
+   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).
+ 
+ Additional note: the desktop login sound on oracular *is* working; it's
+ just the oem-config sound that isn't.

-- 
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:
  Confirmed
Status in libcanberra source package in Noble:
  Confirmed
Status in libcanberra source package in Oracular:
  Confirmed

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).

  Additional note: the desktop login sound on oracular *is* working;
  it's just the oem-config sound that isn't.

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 2081052] [NEW] audio

2024-09-18 Thread Dave Andrew

Public bug reported:

i get sound through speakers for about 30 seconds and then sound cuts
off.sound through a headset is ok

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pulseaudio 1:16.1+dfsg1-2ubuntu10
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:dave   1388 F pipewire
 /dev/snd/controlC0:  dave   1396 F wireplumber
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Sep 18 11:23:05 2024
InstallationDate: Installed on 2020-02-07 (1685 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: RM Education RM
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to noble on 2024-09-18 (0 days ago)
dmi.bios.date: 04/20/2011
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 202
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: RM MOBILE ONE 310
dmi.board.vendor: RM Education
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: RM Education
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr202:bd04/20/2011:br4.6:svnRMEducation:pnRM:pvr1.0:rvnRMEducation:rnRMMOBILEONE310:rvr1.0:cvnRMEducation:ct10:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: PEGA Family
dmi.product.name: RM
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: RM Education
mtime.conffile..etc.init.d.apport: 2024-07-22T15:59:07

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


** Tags: amd64 apport-bug noble

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

Title:
  audio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  i get sound through speakers for about 30 seconds and then sound cuts
  off.sound through a headset is ok

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu10
  ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
  Uname: Linux 6.8.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:dave   1388 F pipewire
   /dev/snd/controlC0:  dave   1396 F wireplumber
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Sep 18 11:23:05 2024
  InstallationDate: Installed on 2020-02-07 (1685 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: RM Education RM
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to noble on 2024-09-18 (0 days ago)
  dmi.bios.date: 04/20/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 202
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RM MOBILE ONE 310
  dmi.board.vendor: RM Education
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: RM Education
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr202:bd04/20/2011:br4.6:svnRMEducation:pnRM:pvr1.0:rvnRMEducation:rnRMMOBILEONE310:rvr1.0:cvnRMEducation:ct10:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: RM
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: RM Education
  mtime.conffile..etc.init.d.apport: 2024-07-22T15:59:07

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


-- 
Mailing list: https://launchpad.net/~touch-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: [SRU] py3clean fails when using alternate character set

2024-09-02 Thread 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

Re: [Touch-packages] [Bug 2003027] Re: fq_codel qdisc compiled but not enabled on 22.10

2024-08-30 Thread Dave Taht

h, it stopped being enabled by systemd? (it used to be
>   enabled there via a sysctl), and thus 22.10 (I tried both ubuntu
>   server and ubuntu studio) doesn't have it on. I rather *immediately*
>   noticed this huge regression (I run my ethernet at 100Mbit, and thus
>   immediately saw 400+ms latency) - and I hope it can be fixed in the
>   next release?
>
>   it can also be made the default via compiling it into the kernel as a
>   kernel default.
>
>   Aggh! death to fifos!
>
>   root@localhost:~# sysctl -a | grep qdisc
>   net.core.default_qdisc = pfifo_fast
>
>   disc pfifo_fast 0: dev eth0 parent :1 bands 3 priomap 1 2 2 2 1 2 0 0 1
> 1 1 1 1 1 1 1
>Sent 5250 bytes 53 pkt (dropped 0, overlimits 0 requeues 0)
>backlog 0b 0p requeues 0
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/2003027/+subscriptions
>
>

-- 
Artists/Musician Campout Aug 9-11
https://www.eventbrite.com/e/healing-arts-event-tickets-928910826287
Dave Täht CSO, LibreQos

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

Title:
  fq_codel qdisc compiled but not enabled on 22.10

Status in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  Fix Released
Status in The Noble Numbat:
  Confirmed
Status in procps source package in Noble:
  Fix Committed
Status in The Oracular Oriole:
  Fix Released
Status in procps source package in Oracular:
  Fix Released

Bug description:
  [ Impact ]
  Starting with Ubuntu 22.10, the default qdisc regressed to pfifo_fast. This 
is due to a change we merged from Debian, removing systemd's 
/usr/lib/50-default.conf file. pfifo_fast does not prevent bufferbloat issues, 
severely degrading networking performance on Ubuntu systems.

  [ Test Plan ]
  On an Ubuntu VM, check that net.core.default_qdisc is set to 'fq_codel'. `tc 
qdisc show` should also confirm fq_codel is being used.

  halves@noble-vm:~$ sysctl net.core.default_qdisc
  net.core.default_qdisc = fq_codel

  halves@noble-vm:~$ tc qdisc show
  qdisc noqueue 0: dev lo root refcnt 2
  qdisc mq 0: dev enp5s0 root
  qdisc fq_codel 0: dev enp5s0 parent :1 limit 10240p flows 1024 quantum 1514 
target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64

  [ Where Problems Could Occur ]
  Users relying on the default pfifo_fast qdisc could see different networking 
behavior. Although fq_codel should be an across-the-board improvement over 
pfifo_fast, we could monitor network latency stats and throughput to make sure 
no weird regressions arise from the qdisc scheduler.

  [ Other Info ]
  Instead of adding a sysctl.conf file, Debian has decided to change their 
default kernel configs to use fq_codel. This has the disadvantage of being 
"hidden" from end users, instead of being a queryable setting in e.g. 
/etc/sysctl.d/, and all kernel documentation still refers to pfifo_fast as 
being the default.

  Systemd's /usr/lib/50-default.conf file includes a lot of other
  settings that are either overruled elsewhere (e.g. from procps) or are
  entirely missing from our stable releases. Introducing a diff from
  Debian to ship this file only for the net.core.default_qdisc changes
  seems excessive, so having a dedicated place under procps where other
  similar toggles are already present seems like the more appropriate
  solution.

  --
  [ Original Description ]
  fq_codel has been the default in ubuntu since #1436945

  It is also now the default in debian. Somewhere between 22.04 and
  22.10 though, it stopped being enabled by systemd? (it used to be
  enabled there via a sysctl), and thus 22.10 (I tried both ubuntu
  server and ubuntu studio) doesn't have it on. I rather *immediately*
  noticed this huge regression (I run my ethernet at 100Mbit, and thus
  immediately saw 400+ms latency) - and I hope it can be fixed in the
  next release?

  it can also be made the default via compiling it into the kernel as a
  kernel default.

  Aggh! death to fifos!

  root@localhost:~# sysctl -a | grep qdisc
  net.core.default_qdisc = pfifo_fast

  disc pfifo_fast 0: dev eth0 parent :1 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 
1 1 1 1
   Sent 5250 bytes 53 pkt (dropped 0, overlimits 0 requeues 0)
   backlog 0b 0p requeues 0

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


-- 
Mailing list: https://launchpad.net/~touch-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: [SRU] py3clean fails when using alternate character set

2024-08-12 Thread 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

2024-08-08 Thread 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

2024-08-08 Thread 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

Re: [Touch-packages] [Bug 2003027] Re: fq_codel qdisc compiled but not enabled on 22.10

2024-08-07 Thread Dave Taht

Thank yall for addressing this!

On Wed, Aug 7, 2024, 12:50 PM Nick Rosbrook <2003...@bugs.launchpad.net>
wrote:

> ** Changed in: procps (Ubuntu Oracular)
>Status: In Progress => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2003027
>
> Title:
>   fq_codel qdisc compiled but not enabled on 22.10
>
> Status in Ubuntu:
>   In Progress
> Status in procps package in Ubuntu:
>   Fix Committed
> Status in The Noble Numbat:
>   Confirmed
> Status in procps source package in Noble:
>   Confirmed
> Status in The Oracular Oriole:
>   In Progress
> Status in procps source package in Oracular:
>   Fix Committed
>
> Bug description:
>   [ Impact ]
>   Starting with Ubuntu 22.10, the default qdisc regressed to pfifo_fast.
> This is due to a change we merged from Debian, removing systemd's
> /usr/lib/50-default.conf file. pfifo_fast does not prevent bufferbloat
> issues, severely degrading networking performance on Ubuntu systems.
>
>   [ Test Plan ]
>   On an Ubuntu VM, check that net.core.default_qdisc is set to 'fq_codel'.
> `tc qdisc show` should also confirm fq_codel is being used.
>
>   halves@noble-vm:~$ sysctl net.core.default_qdisc
>   net.core.default_qdisc = fq_codel
>
>   halves@noble-vm:~$ tc qdisc show
>   qdisc noqueue 0: dev lo root refcnt 2
>   qdisc mq 0: dev enp5s0 root
>   qdisc fq_codel 0: dev enp5s0 parent :1 limit 10240p flows 1024 quantum
> 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
>
>   [ Where Problems Could Occur ]
>   Users relying on the default pfifo_fast qdisc could see different
> networking behavior.
>
>   [ Other Info ]
>   Instead of adding a sysctl.conf file, Debian has decided to change their
> default kernel configs to use fq_codel. This has the disadvantage of being
> "hidden" from end users, instead of being a queryable setting in e.g.
> /etc/sysctl.d/, and all kernel documentation still refers to pfifo_fast as
> being the default.
>
>   Systemd's /usr/lib/50-default.conf file includes a lot of other
>   settings that are either overruled elsewhere (e.g. from procps) or are
>   entirely missing from our stable releases. Introducing a diff from
>   Debian to ship this file only for the net.core.default_qdisc changes
>   seems excessive, so having a dedicated place under procps where other
>   similar toggles are already present seems like the more appropriate
>   solution.
>
>   --
>   [ Original Description ]
>   fq_codel has been the default in ubuntu since #1436945
>
>   It is also now the default in debian. Somewhere between 22.04 and
>   22.10 though, it stopped being enabled by systemd? (it used to be
>   enabled there via a sysctl), and thus 22.10 (I tried both ubuntu
>   server and ubuntu studio) doesn't have it on. I rather *immediately*
>   noticed this huge regression (I run my ethernet at 100Mbit, and thus
>   immediately saw 400+ms latency) - and I hope it can be fixed in the
>   next release?
>
>   it can also be made the default via compiling it into the kernel as a
>   kernel default.
>
>   Aggh! death to fifos!
>
>   root@localhost:~# sysctl -a | grep qdisc
>   net.core.default_qdisc = pfifo_fast
>
>   disc pfifo_fast 0: dev eth0 parent :1 bands 3 priomap 1 2 2 2 1 2 0 0 1
> 1 1 1 1 1 1 1
>Sent 5250 bytes 53 pkt (dropped 0, overlimits 0 requeues 0)
>backlog 0b 0p requeues 0
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/2003027/+subscriptions
>
>

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

Title:
  fq_codel qdisc compiled but not enabled on 22.10

Status in Ubuntu:
  In Progress
Status in procps package in Ubuntu:
  Fix Committed
Status in The Noble Numbat:
  Confirmed
Status in procps source package in Noble:
  Confirmed
Status in The Oracular Oriole:
  In Progress
Status in procps source package in Oracular:
  Fix Committed

Bug description:
  [ Impact ]
  Starting with Ubuntu 22.10, the default qdisc regressed to pfifo_fast. This 
is due to a change we merged from Debian, removing systemd's 
/usr/lib/50-default.conf file. pfifo_fast does not prevent bufferbloat issues, 
severely degrading networking performance on Ubuntu systems.

  [ Test Plan ]
  On an Ubuntu VM, check that net.core.default_qdisc is set to 'fq_codel'. `tc 
qdisc show` should also confirm fq_codel is being used.

  halves@noble-vm:~$ sysctl net.core.default_qdisc
  net.core.default_qdisc = fq_codel

  halves@noble-vm:~$ tc qdisc show
  qdisc noqueue 0: dev lo root refcnt 2
  qdisc mq 0: dev enp5s0 root
  qdisc fq_codel 0: dev enp5s0 parent :1 limit 10240p flows 1024 quantum 1514 
target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64

  [ Where Problems Could Occur ]
  Users relying on the default pfifo_fast qdisc could see different networking 
behavior.

  [ Other Info ]
  Ins

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

2024-08-07 Thread 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

2024-08-07 Thread 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

2024-08-07 Thread 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: py3clean fails when using alternate character set

2024-08-05 Thread 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

2024-08-05 Thread 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

2024-08-05 Thread 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 2062667] Re: Fails on (and should be removed from) raspi desktop

2024-04-24 Thread 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 2062414] Re: busybox 1.36.1 FTBFS with current kernel headers on noble

2024-04-23 Thread 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 2062564] Re: [FFe] Seed pemmican

2024-04-19 Thread 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

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 2062414] Re: busybox 1.36.1 FTBFS with current kernel headers on noble

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

** 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] [NEW] busybox 1.36.1 FTBFS with current kernel headers on noble

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 1097467] Re: bash does not fulfill --rcfile option properly

2024-04-16 Thread 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 2060730] Re: totem cannot install codecs via packagekit

2024-04-12 Thread 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

2024-04-11 Thread 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 2060693] Re: No welcome/login sound on Ubuntu desktop

2024-04-11 Thread 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 1942260] Re: compress firmware in /lib/firmware

2024-04-10 Thread 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 2060730] Re: totem cannot install codecs via packagekit

2024-04-09 Thread 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 2037015] Re: Screen corruption of slides during install on Raspberry Pi 4

2024-04-09 Thread 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 2060693] [NEW] No login sound on Ubuntu desktop

2024-04-09 Thread 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 2057927] Re: lxd vga console throws "Operation not permitted" error

2024-03-29 Thread 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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

2024-03-26 Thread 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 2055351] Re: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

2024-03-06 Thread Dave Zielinski

This looks like it's the same issue as this:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2004532

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date

[Touch-packages] [Bug 2054683] Re: Please merge lvm2 2.03.16-3 from Debian unstable.

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 2054683] [NEW] Please merge lvm2 2.03.16-3 from Debian unstable.

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.

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.

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 2054517] Re: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions

2024-02-21 Thread 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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

2024-01-25 Thread Dave Jones

Tested on mantic install, and as Robie suggested, performed binary
debdiff against old versions to ensure only change was the version
number. Marking verification done.

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

-- 
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:
  Fix Released
Status in ubuntu-settings source package in Mantic:
  Fix Committed

Bug description:
  [SRU Justification]

  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).

  [Test case]
  No testing is planned beyond any autopkgtests which may be none (the package 
itself doesn't have any).  This should not be released to -updates on its own, 
but should be staged in -proposed so any future SRUs needed don't fail to copy 
due to out-of-date packages.

  [Where problems may occur]
  It is unlikely but possible that the removal of the raspi binary package from 
this source package will have inadvertently modified the contents of the other 
remaining binary packages.

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 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

2024-01-24 Thread Dave Jones

** Summary changed:

- liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
+ [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

-- 
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:
  [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Fix Committed
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Confirmed
Status in lxc source package in Noble:
  Fix Committed

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

[Touch-packages] [Bug 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

2024-01-24 Thread Dave Jones

Noble's now in proposed and looks to have built successfully so I'll
mark that Fix Committed. I'm just uploading the mantic and jammy SRUs
(the jammy one took a little longer as the fix is slightly different
there; appears the build system changed between jammy and mantic).

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

-- 
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:
  Fix Committed
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Confirmed
Status in lxc source package in Noble:
  Fix Committed

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

[Touch-packages] [Bug 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

2024-01-22 Thread Dave Jones

Okay, good enough for me -- I'll sponsor my aforementioned branch for
noble and have a look at the mantic and jammy SRUs tomorrow, assuming
everything builds happily in noble.

-- 
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
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Confirmed
Status in lxc source package in Noble:
  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

[Touch-packages] [Bug 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

2024-01-22 Thread Dave Jones

I had a little time to look over this again in my patch-pilot shift. I
agree it's almost certainly best to just get LXC_DEVEL set correctly
quickly. Andreas' suggested branch is a good start, but I agree with the
critique that the DEP-8 test should be checking the installed headers
rather than the built source. Due to this, it's probably also best if
the test is named something other than "build". Also, I agree it
shouldn't be marked "superficial".

I've pushed a few commits on top of Andreas' to another clone here,
which also fixes a build-failure on noble (lib/systemd instead of
usr/lib/systemd in d/lxc-utils.install):

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

I've tested the DEP-8 passes with the branch, and crucially that it
fails when the LXC_DEVEL fix is reverted (which it does). If this looks
sane to someone else, I'm happy to sponsor this into noble (and start
SRU proceedings for mantic and jammy).

-- 
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
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Confirmed
Status in lxc source package in Noble:
  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

[Touch-packages] [Bug 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

2023-12-11 Thread 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

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

2023-11-16 Thread 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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

2023-11-15 Thread 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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot

2023-11-15 Thread 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 1097467] Re: bash does not fulfill --rcfile option properly

2023-11-14 Thread 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`:

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

> 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

2023-11-14 Thread 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

2023-11-14 Thread 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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

2023-11-09 Thread 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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

2023-11-07 Thread 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

2023-11-06 Thread 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 1951586] Re: Need option to specify wifi regulatory domain

2023-10-31 Thread 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 2037642] Re: [FFe] Raspberry Pi 5 support

2023-10-13 Thread 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 2038964] Re: raspi ethernet rename is racy

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 2038964] Re: raspi ethernet rename is racy

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

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

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

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

** 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] [NEW] raspi ethernet rename is racy

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 2037642] Re: [FFe] Raspberry Pi 5 support