[Touch-packages] [Bug 1814302] Re: Quasselcore apparmor profile issue in lxd container.

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

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

Title:
  Quasselcore apparmor profile issue in lxd container.

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

Bug description:
  [impact]

  quasselcore cannot start inside lxd container

  [test case]

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

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

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

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

  $ /usr/bin/quasselcore 
  Segmentation fault

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

  [regression potential]

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

  [scope]

  this is needed for b/f/g.

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

  [original description]

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

  Install quassel-core. Service will not start.

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

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

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

  Quasselcore service now starts and I can connect to it.

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


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


[Touch-packages] [Bug 1814302] Re: Quasselcore apparmor profile issue in lxd container.

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

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

Title:
  Quasselcore apparmor profile issue in lxd container.

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

Bug description:
  [impact]

  quasselcore cannot start inside lxd container

  [test case]

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

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

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

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

  $ /usr/bin/quasselcore 
  Segmentation fault

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

  [regression potential]

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

  [scope]

  this is needed for b/f/g.

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

  [original description]

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

  Install quassel-core. Service will not start.

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

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

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

  Quasselcore service now starts and I can connect to it.

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


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


[Touch-packages] [Bug 1814302] Re: Quasselcore apparmor profile issue in lxd container.

2022-06-12 Thread Dave Jones
Looks like this is back in jammy (and beyond); the sync from Debian
dropped the patch to d/usr.bin.quasselcore for lxd.

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

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

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

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

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

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

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

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

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

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

Title:
  Quasselcore apparmor profile issue in lxd container.

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

Bug description:
  [impact]

  quasselcore cannot start inside lxd container

  [test case]

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

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

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

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

  $ /usr/bin/quasselcore 
  Segmentation fault

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

  [regression potential]

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

  [scope]

  this is needed for b/f/g.

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

  [original description]

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

  Install quassel-core. Service will not start.

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

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

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

  Quasselcore service now starts and I can connect to it.

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


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


[Touch-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot

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

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

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

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

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

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

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

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

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


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


[Touch-packages] [Bug 1977764] Re: kernel modules "zstd" and "z3fold" missing.

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

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

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

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

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

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

  Ubuntu version is 22.04 LTS flashed from the official image.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1977764/+subscriptions


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


[Touch-packages] [Bug 1977764] Re: kernel modules "zstd" and "z3fold" missing.

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

The workaround for now:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  Ubuntu version is 22.04 LTS flashed from the official image.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1977764/+subscriptions


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


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

2022-06-01 Thread Dave Jones
Sure -- I'll try not to drown them in verbiage :)

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

Title:
  Need option to specify wifi regulatory domain

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions


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


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

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

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

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

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

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

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

Why NetworkManager?

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

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

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

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

Title:
  Need option to specify wifi regulatory domain

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions


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


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

2022-06-01 Thread Dave Jones
>> it's apparently never worked for me at home or at various friends
>> houses, and only once worked when I travelled to Germany for a
>> sprint.

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

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

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

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

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

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

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

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

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

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

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

Title:
  Need option to specify wifi regulatory domain

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions


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


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

2022-05-31 Thread Dave Jones
I'll take a shot at responding to @seb128's questions:

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

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

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

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

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

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

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

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


What's the intended priority?
=

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

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


What's the impact?
==

Hopefully covered in the prior sections.


What do we expect to be changed?


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

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

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

2022-05-09 Thread Dave Jones
> Should be part of the 'beacon' info.
https://howiwifi.com/2020/07/13/802-11-frame-types-and-formats/ has a
good overview. I discovered this exchange while observing 'on the wire'
with wireshark.

Thanks for the link; lots of useful stuff there!

> > I wondered if perhaps it this only works on some APs?

> That is the impression that I get, the country code info is part of
the management frames transmitted by the AP, could be unsupported, not
configured, or mis-configured.

Okay, to my mind that brings us back to "need option to specify wifi
regulatory domain". It seems the situation with netplan/networkd is
"there's no option", and in NetworkManager is "there's no option, but
*sometimes* it'll magically work anyway" (although you'll need to go
digging in the logs to confirm that :)

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

Title:
  Need option to specify wifi regulatory domain

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions


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


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

2022-05-09 Thread Dave Jones
I'm not entirely convinced NetworkManager is working correctly this
regard? I *was* checking the wifi regulatory domain with "iw reg get"
which consistently shows UNSET both globally and for phy#0 under the
desktop for Pi images:

$ iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
(5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
(5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
(57240 - 63720 @ 2160), (N/A, 0), (N/A)

phy#0
country 99: DFS-UNSET
(2402 - 2482 @ 40), (6, 20), (N/A)
(2474 - 2494 @ 20), (6, 20), (N/A)
(5140 - 5360 @ 160), (6, 20), (N/A)
(5460 - 5860 @ 160), (6, 20), (N/A)

Still, perhaps "iw" doesn't know about changes that wpa_supplicant
makes? On a freshly flashed jammy pi desktop card, I get the following
output when looking for REGDOM in the wpa_supplicant logs:

$ journalctl -u wpa_supplicant -g REGDOM
-- Boot 732bf3d726d543d4985f9e8ded5b5dc3 --
May 09 11:19:54 miss-piggy wpa_supplicant[727]: wlan0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD

The "WORLD" region is presumably consistent with "UNSET" so it doesn't
look like NetworkManager or wpa_supplicant is setting things correctly
there. I wondered if perhaps it this only works on some APs? So here's
the output from my regular development Pi. This also runs the jammy
desktop, but it's not a freshly flashed image -- it's been upgraded thru
every release since hirsute so it's probably a bit crufty -- but it has
travelled with me to various places so it's seen a few different access
points (it spends most of its time on ethernet at home though, so the
lack of lots of REGDOM changes is not too surprising):

-- Boot 3342ed4b84f14e6a8f7b900d240b2c4d --
-- Boot d9087ec569c64e258d9b0a39d5d51c81 --
-- Boot b4c27a9655d747d48fc16329f73ad596 --
-- Boot d431767f6d89494bba39cc9ab9bce969 --
Sep 29 00:09:43 kermit wpa_supplicant[1081]: wlan0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
-- Boot 345a7579a52147aea56af3152178c199 --
Sep 29 09:28:02 kermit wpa_supplicant[1077]: wlan0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
-- Boot 624126fce6cc45abad47cb42b9ac256f --
-- Boot e424d65195804a6eae2f948ee1e4ef38 --
-- Boot 77fb125a0ecc4df985d5317cd536b54a --
-- Boot da38e67821874b3fa66a330acf17f18c --
-- Boot 02be9377913d4886b21988b903d1b4cd --
-- Boot 8a6dc8a10b0f42689056adacb374d269 --
-- Boot 85bbc4cfc473439a899e467a2debb201 --
-- Boot fa07d0686c68401696caf2b3e4c402dd --
Jan 14 15:09:22 kermit wpa_supplicant[87530]: wlan0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
-- Boot 9e7e7bf75790439bbc2e72371a14c8ab --
-- Boot a70d0f3889794224a7bf370998aaf7dd --
-- Boot bd314e15c8f1415eb75c9950129edd5b --
-- Boot c54489d0e45b4318b1b07d88bdaff7ea --
-- Boot 370a4871b0ec43f9a1b58cab78ac875c --
-- Boot 4756c93714f247009f5b93f228925455 --
-- Boot 884e307c2a13455b9fbb913e0a0f0c29 --
-- Boot bad77d689f714ca88d38f498cd8bfa2b --
-- Boot 1cf2c96be69748afa60489603ef8b771 --
-- Boot 09375e4eaaf94141a8cfe904bc303989 --
-- Boot 8fa2bdfb2e6e4ad0abeda9b3a79ac37a --
-- Boot 6c23de48f7a748d995cce77b9a908d3f --
-- Boot 364f760176b54df5b3fcaa5b978f3e70 --
-- Boot ff656412414f4c7880079f7bbf07400a --
-- Boot ebb1115d58724cf9bd544028d01c6e96 --
-- Boot 5c85c03736934ed6a2426544f5f98b88 --
-- Boot 6051d9f10827419996db1bfa376ec562 --
-- Boot 4996ddb853a248268b27e93adff373e1 --
-- Boot 0b7927e93a38434683395e88d202a8e1 --
Feb 14 09:57:26 kermit wpa_supplicant[1030]: wlan0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
-- Boot 08038d28c346496eb7884859c306ca4c --
-- Boot b2c62ed0866d4618ac058670dbaae672 --
Feb 17 01:37:49 kermit wpa_supplicant[1032]: wlan0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
-- Boot 5a2883f8ce074e748e9a94beaf72f123 --
-- Boot ec2157fa46fa48a3ba3445bfa7fe4b1b --
-- Boot e2dbc92b2764473eb8d65a1f7e6df5df --
-- Boot ec2157fa46fa48a3ba3445bfa7fe4b1b --
-- Boot e2dbc92b2764473eb8d65a1f7e6df5df --
-- Boot a8ef52e6c63949cea168ea8c1d06d148 --
Feb 23 10:43:59 kermit wpa_supplicant[1027]: wlan0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
-- Boot 319081b9562a4c20aa1560a4fe998f19 --
-- Boot 4d3841cc1dbb4906a4465dd2122f64a8 --
Feb 26 18:18:07 kermit wpa_supplicant[1048]: wlan0: CTRL-EVENT-REGDOM-CHANGE 
init=USER type=COUNTRY alpha2=DE
-- Boot 8729c7f4e1ae45dcbece9aeceb9b19cb --
-- Boot 8034051089274a34ba65bc96d749a9b7 --
-- Boot 8729c7f4e1ae45dcbece9aeceb9b19cb --
Mar 03 10:07:39 kermit wpa_supplicant[1040]: wlan0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
-- Boot 8034051089274a34ba65bc96d749a9b7 --
Mar 11 11:20:39 kermit wpa_supplicant[1040]: wlan0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
-- Boot dcd973755091479b9be508eaf11667dd --
-- Boot b0c3f4f9a2d64a8a959844ad1773e6c1 --

[Touch-packages] [Bug 1928973] Re: Please merge lvm2 2.03.11-2.1 from Debian unstable

2022-05-06 Thread Dave Jones
** Changed in: lvm2 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Please merge lvm2 2.03.11-2.1 from Debian unstable

Status in lvm2 package in Ubuntu:
  Fix Released

Bug description:
  Please merge lvm2 2.03.11-2.1 from Debian unstable.

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

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


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


[Touch-packages] [Bug 1923672] Re: [FFe] Provide access to GPIO to default user

2022-05-06 Thread Dave Jones
** Changed in: ubuntu-settings (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  [FFe] Provide access to GPIO to default user

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Hirsute:
  Fix Released
Status in ubuntu-settings source package in Impish:
  Won't Fix
Status in ubuntu-settings source package in Jammy:
  Fix Released

Bug description:
  At present, access to the GPIO pins is provided to the dialout group
  by the udev rules from the rpi.gpio-common package. However, rpi.gpio
  is a single GPIO library, and the device(s) it provides access to are
  not specific to it. Moreover, the interface used is deprecated and the
  /dev/gpiochip* interface is now the favoured mechanism for controlling
  the GPIO pins.

  The choice of the dialout group appears reasonable (historically it's
  used to provide access to the serial ports, and indeed the serial
  ports are part of the GPIO header on Raspberry Pi devices), but the
  rules should be extended to cover the modern /dev/gpiochip* devices,
  the related /dev/spidev* and /dev/i2c-* devices, and should be placed
  in a central location (i.e. ubuntu-raspi-settings) rather than in a
  specific GPIO library (like rpi.gpio).

  Related to this is LP: #1923363 which seeks to ensure equal access
  across images (the default user is currently granted "dialout" group
  membership on the pi server images, but not the desktop ones).

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


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


[Touch-packages] [Bug 1972009] Re: Totem fails to find video - kinetic ubuntu raspi pi

2022-05-06 Thread Dave Jones
*** This bug is a duplicate of bug 1969512 ***
https://bugs.launchpad.net/bugs/1969512

Sorry, I think this is a duplicate of 1969512 (marking as such) -- I
have found, in the course of investigating that one that we may either
need to switch the ISO test to use an OGG (or OGV) file instead (or
mandate that gstreamer1.0-libav is installed first) but the bug still
stands (even with that pkg installed, totem's reporting the same
message).

** This bug has been marked a duplicate of bug 1969512
   Totem unable to play video: "The specified movie could not be found"

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

Title:
  Totem fails to find video - kinetic ubuntu raspi pi

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Running test kinetic ubuntu daily - raspi 4 8GB daily ISO

  When attempting to run "totem big_buck_bunny_720p_surround.mp4" as per
  the testcase - received the error - An error occurred - the specified
  movie could not be found.

  No further errors encountered

  
  -- I ran ubuntu-bug totem but see that the package selected is "gstreamer1.0" 
- please correct if need be.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libgstreamer1.0-0 1.20.1-1
  ProcVersionSignature: Ubuntu 5.15.0-1006.6-raspi 5.15.30
  Uname: Linux 5.15.0-1006-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  6 17:07:53 2022
  ImageMediaBuild: 20220506
  LogAlsaMixer:
   Simple mixer control 'Headphone',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined
 Playback channels: Mono
 Limits: Playback -10239 - 400
 Mono: Playback -2000 [77%] [-20.00dB] [on]
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972009/+subscriptions


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


[Touch-packages] [Bug 1915966] Re: Please merge initramfs-tools 0.139 from Debian unstable

2022-05-06 Thread Dave Jones
** Changed in: initramfs-tools (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Please merge initramfs-tools 0.139 from Debian unstable

Status in initramfs-tools package in Ubuntu:
  Fix Released

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

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

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


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

2022-05-06 Thread Dave Jones
@jvonau I just came back to this while trawling through my still-open
bug list and had a look at what happens on the desktop. At least on our
Pi desktop images (using NetworkManager), no wifi regulatory domain gets
set at all (at least on my local network). Just in case it made any
difference, I also tried switching on "location services", but there was
no effect on the regulatory domain.

It appears that the effort to make NetworkManager (or more broadly, the
GNOME desktop) location aware stalled some considerable time ago [1] [2]
[3]

[1]: 
http://linuxwireless.sipsolutions.net/en/developers/GSoC/2009/GeoClue_regulatory/
[2]: 
https://wireless.wiki.kernel.org/en/developers/Regulatory/CRDA#using_network_manager_to_change_regulatory_domains
[3]: 
https://wireless.wiki.kernel.org/en/developers/Regulatory#automatic_country_discovery

Also, I don't see any option to manually set the regulatory domain in
the UI. Now that crda's gone in jammy, and "iw" isn't seeded on the
desktop image (for the Pi at least; is the PC any different?) there's
effectively no way for the user to set the wifi regulatory domain
(something that's fairly important ... legal stuff and all that) "out of
the box" either via the GUI or via the command line.

I've added the info the jammy release notes, and I'm going to add a few
targets here as this clearly needs some work on several fronts,
presumably netplan for servers and NetworkManager for desktops.

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: network-manager (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: netplan.io (Ubuntu Kinetic)
   Importance: Medium
   Status: Triaged

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

Title:
  Need option to specify wifi regulatory domain

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

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 1926906] Re: (Ubuntu 21.04) RPi4 audio is slow and crackling

2022-04-19 Thread Dave Jones
*** This bug is a duplicate of bug 1877194 ***
https://bugs.launchpad.net/bugs/1877194

** This bug is no longer a duplicate of bug 1899962
   Wrong audio output device selected on Raspberry Pi Desktop
** This bug has been marked a duplicate of bug 1877194
   switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the 
old default device on reboot

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

Title:
  (Ubuntu 21.04) RPi4 audio is slow and crackling

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm using a Raspberry Pi 4. After updating from Ubuntu 20.10 to 21.04, I 
noticed audio problems.
  The sound is slow and crackling.

  I'm using the headphone jack and the config.txt option:
  dtparam=audio=on

  If I start a video or audio file in VLC player and select the VLC options:
  Audio:
  Output module: ALSA Audio Output
  Device: bcm2835 Headphones, bcm2835 Headphones Default Audio Device

  Then the playback speed seems to be normal but the "electric" crackling in 
voices remains.
  And system-wide the problem persists, too.

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


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


[Touch-packages] [Bug 1899962] Re: Wrong audio output device selected on Raspberry Pi Desktop

2022-04-19 Thread Dave Jones
*** This bug is a duplicate of bug 1877194 ***
https://bugs.launchpad.net/bugs/1877194

Looks like this fell off my radar, but looking at vanvugt's comment this
is indeed a duplicate of bug 1877194 (and still occurs in Jammy). I'll
mark it as such

** This bug has been marked a duplicate of bug 1877194
   switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the 
old default device on reboot

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

Title:
  Wrong audio output device selected on Raspberry Pi Desktop

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  On each boot, an incorrect audio output device is selected, at least
  when HDMI audio output is in use (still need to test the TV/aux
  output; will update the bug when done).

  Specifically, the settings application lists "Multichannel Output -
  Built-in Audio" as the selected output device. However, for audio to
  play through the connected HDMI device, "Analog Output - Built-in
  Audio" must be selected instead. Unfortunately, this setting will be
  lost on subsequent boots. A workaround is to remove the following
  lines from /etc/pulse/default.pa:

  ### Use hot-plugged devices like Bluetooth or USB automatically (LP: 
#1702794)
  .ifexists module-switch-on-connect.so
  load-module module-switch-on-connect
  .endif

  However, removal of these lines will (as the comment suggests) result
  in hot-plugged USB devices *not* being automatically selected.

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


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

2022-04-19 Thread Dave Jones
Another quick update: in recent days we've gone from "blank white space"
back to "incorrect stride corruption" in all documented cases (embedded
browsers, help windows, MiniBrowser, etc).

I note in the dpkg logs, libglx-mesa0 got updated a few days ago, but
unfortunately I'm unsure exactly when the change occurred so this is
speculation on my part.

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

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

Bug description:
  On the hirsute Pi desktop, under a wayland session with the "full" KMS
  overlay enabled, and "kms-modifiers" present in the
  org.gnome.mutter/experimental-features, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-04-14 Thread Dave Jones
** Changed in: ubuntu-meta (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-image (Ubuntu)
   Status: New => Invalid

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions


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


[Touch-packages] [Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-04-14 Thread Dave Jones
@noahod I've just tried this with the current
https://cdimage.ubuntu.com/ubuntu-server/daily-
preinstalled/current/jammy-preinstalled-server-arm64+raspi.img.xz image
(downloaded today) and with just your growpart config (I didn't try the
resize_rootfs key), the card booted without resizing the rootfs:

  ubuntu@ubuntu:~$ df -h /
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/mmcblk0p2  3.3G  2.2G  964M  70% /

  ubuntu@ubuntu:~$ sudo fdisk -l /dev/mmcblk0
  Disk /dev/mmcblk0: 29.72 GiB, 31914983424 bytes, 62333952 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0xc34fdafd

  Device Boot  Start End Sectors  Size Id Type
  /dev/mmcblk0p1 *  2048  526335  524288  256M  c W95 FAT32 (LBA)
  /dev/mmcblk0p2  526336 7656787 7130452  3.4G 83 Linux

Could you have a go with just the growpart config?

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions


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


[Touch-packages] [Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-04-07 Thread Dave Jones
** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions


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

2022-04-04 Thread Dave Jones
@seb128 interesting, I've just tried this on a fully updated jammy image
on a Pi 400 and /usr/lib/aarch64-linux-gnu/webkit2gtk-4.0/MiniBrowser
starts quite happily; browser window opens and ... nothing but blank
white space within the body of the window. All the controls in the
toolbar are fine and it's definitely able to navigate to pages, and
after a bit of experimentation I'm reasonably convinced it's all
"working correctly" with the one exception that nothing actually shows
up (but the mouse cursor changes shape in all the right places, etc).

@vanvugt: in case it's of any use, MiniBrowser produced the following
console output:

** (MiniBrowser:149058): WARNING **: 21:30:51.512: GDK is not able to create a 
GL context, falling back to glReadPixels (slow!): Unable to create a GL context
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

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

Bug description:
  On the hirsute Pi desktop, under a wayland session with the "full" KMS
  overlay enabled, and "kms-modifiers" present in the
  org.gnome.mutter/experimental-features, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop

2022-04-01 Thread Dave Jones
Attaching debdiff which I believe should prevent the service from being
stopped on upgrade. Test packages are currently building in
ppa:waveform/dbus (https://launchpad.net/~waveform/+archive/ubuntu/dbus)
but I've already built locally and verified that the offending portion
of the preinst maintscript is gone.

Ultimately this is down to a mis-understanding of debhelper's
start/restart options (which are unfortunately named, and in my opinion
insufficiently documented -- something I'll try and post a patch for
upstream):

In Ubuntu (several releases back) we'd altered the dh_installsystemd
options for dbus (in d/rules) to "--no-start" intending the service to
be activated solely via dbus.socket. Unfortunately, just specifying "--
no-start" tells debhelper you don't want the service started, but it
still implies that you wish the service to be *restarted* (if it's
running) during upgrade. You must *additionally* specify "--no-stop-on-
upgrade" (formerly known as "--no-restart-on-upgrade", and not to be
confused with "--no-restart-after-upgrade") if you do not want it
restarted.

Debian have also (more recently) adjusted their dh_installsystemd
options for dbus (for different reasons), so this will also need
patching upstream (I'll try and open a bug for this and associate it
with this one as it's all the same options affected at the end of the
day).

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

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

Title:
  dbus was stopped during today's jammy update, breaking desktop

Status in dbus package in Ubuntu:
  Triaged
Status in dbus source package in Jammy:
  Triaged

Bug description:
  Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
  Had to hard reset.

  Today's jammy upgrade stopped dbus at 19:46:27

  Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
  Bus...

  This should not happen. I don't know which package caused this, but
  presumably dbus should not be stoppable in the first place.


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus 1.12.20-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Feb 23 20:03:41 2022
  InstallationDate: Installed on 2018-03-14 (1442 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1962036] Re: dbus was stopped during today's jammy update, breaking desktop

2022-04-01 Thread Dave Jones
Some additional info:

"dh_installsystemd --no-start" on its own is *not* equivalent to "--no-
start --restart-after-upgrade" as one might imagine ("--restart-after-
upgrade" is *usually* the dh_installsystemd default). Instead "--no-
start" adjusts the restart default to "--no-restart-after-upgrade" (I'm
now *fairly* convinced this is actually a bug). Unfortunately "--no-
restart-after-upgrade" cannot work with "--no-start" because, whilst the
preinst script will always stop the service, the postinst script won't
attempt to start it again because "--no-start" is specified.

Even if dh_installsystemd did try to be more intelligent, I'm not
convinced this combination can ever work in all circumstances: the
postinst maintscript cannot know whether the service was running prior
to the preinst script stopping it because the idempotency requirement
for maintscripts implies that postinst is not necessarily running
immediately after preinst.

In other words, "--no-start --no-restart-after-upgrade" (or "--no-start"
on its own which is equivalent) is a broken combination which does not
(and probably cannot, at least with the current design) work.

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

Title:
  dbus was stopped during today's jammy update, breaking desktop

Status in dbus package in Ubuntu:
  Triaged
Status in dbus source package in Jammy:
  Triaged

Bug description:
  Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
  Had to hard reset.

  Today's jammy upgrade stopped dbus at 19:46:27

  Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
  Bus...

  This should not happen. I don't know which package caused this, but
  presumably dbus should not be stoppable in the first place.


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus 1.12.20-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Feb 23 20:03:41 2022
  InstallationDate: Installed on 2018-03-14 (1442 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1962036] Re: dbus was stopped during today's jammy update, breaking desktop

2022-04-01 Thread Dave Jones
** Changed in: dbus (Ubuntu Jammy)
 Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  dbus was stopped during today's jammy update, breaking desktop

Status in dbus package in Ubuntu:
  Triaged
Status in dbus source package in Jammy:
  Triaged

Bug description:
  Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
  Had to hard reset.

  Today's jammy upgrade stopped dbus at 19:46:27

  Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
  Bus...

  This should not happen. I don't know which package caused this, but
  presumably dbus should not be stoppable in the first place.


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus 1.12.20-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Feb 23 20:03:41 2022
  InstallationDate: Installed on 2018-03-14 (1442 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1959211] Re: Please merge dbus 1.12.20-3 from Debian unstable

2022-04-01 Thread Dave Jones
** Description changed:

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

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

** Description changed:

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

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

Title:
  Please merge dbus 1.12.20-3 from Debian unstable

Status in dbus package in Ubuntu:
  New

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

  
  = Original Description =

  Please merge dbus 1.12.20-3 from Debian unstable.

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

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


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


[Touch-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

2022-03-28 Thread Dave Jones
This still seems to be an issue on the current Ubuntu Pi Jammy images
although it presents in a different manner: instead of an incorrect-
stride corruption, the embedded browser (in the same places: help
windows, or the login entries for online accounts) simply appears blank
white.

However, if the mouse cursor is moved across the blank white content of
the window, the cursor shape changes to indicate text entry fields or
clickable links indicating that the browser is likely operating
correctly but failing to render correctly.

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

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

Bug description:
  On the hirsute Pi desktop, under a wayland session with the "full" KMS
  overlay enabled, and "kms-modifiers" present in the
  org.gnome.mutter/experimental-features, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-03-28 Thread Dave Jones
** Tags added: fr-2147

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions


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


[Touch-packages] [Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-03-21 Thread Dave Jones
Sorry, this slipped off my radar -- I'll get on with the required PRs
today

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions


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


[Touch-packages] [Bug 1899953] Re: Crackling audio on Raspberry Pi Desktop

2022-03-11 Thread Dave Jones
Closing as we're now using "full" KMS on all supported desktops

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

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

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

Title:
  Crackling audio on Raspberry Pi Desktop

Status in PulseAudio:
  Unknown
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Attempting to play audio (e.g. from rhythmbox) on the raspberry pi
  desktop image, results in broken up / crackling audio. The "tsched=0"
  workaround noted in
  
https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling
  successfully avoids the issue.

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


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


[Touch-packages] [Bug 1959054] Re: debhelper restarts services marked --no-restart-on-upgrade

2022-02-28 Thread Dave Jones
** Changed in: debhelper (Ubuntu Jammy)
 Assignee: Dave Jones (waveform) => (unassigned)

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

Title:
  debhelper restarts services marked --no-restart-on-upgrade

Status in debconf package in Ubuntu:
  Fix Released
Status in debhelper package in Ubuntu:
  Fix Released
Status in docker.io package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in debconf source package in Jammy:
  Fix Released
Status in debhelper source package in Jammy:
  Fix Released
Status in docker.io source package in Jammy:
  Fix Released
Status in libvirt source package in Jammy:
  Fix Released
Status in debconf package in Debian:
  New
Status in debhelper package in Debian:
  New

Bug description:
  Debian bug #994204 (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that
  results in the postinst being generated in such a fashion that
  services marked --no-stop-on-upgrade (or its deprecated alias --no-
  restart-on-upgrade), restart anyway.

  Please note: this is nothing to do with the --no-restart-after-upgrade
  flag (which is, somewhat confusingly IMO, unrelated).

  I've confirmed that the flaw appears to be present in the jammy
  version of debhelper (though not impish) and that packages generated
  with it appear to contain the flawed postinst (I first encountered
  this whilst working on the open-iscsi merge), though I haven't yet
  managed to test that the flaw exhibits itself on upgrade (though I'd
  say from the presence of the flaw in the postinst, that it's a
  reasonable inference that it will).

  In dbus (the merge of which I'm currently working on), Debian has
  worked around this but given I've now run into two affected packages
  (open-iscsi and dbus), only one of which has a work-around, I'd much
  rather we got debhelper fixed up and rebuilt affected packages?

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


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


[Touch-packages] [Bug 1961618] Re: Pi server image no longer connects to eth0 after upgrade to jammy

2022-02-21 Thread Dave Jones
** Patch added: "1-1961618.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1961618/+attachment/5562552/+files/1-1961618.debdiff

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Confirmed

** Tags added: raspi-image rls-jj-incoming

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

Title:
  Pi server image no longer connects to eth0 after upgrade to jammy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The eth0 rename fix introduced in 20.10.1, and removed in 22.04.1
  unfortunately causes problems on upgrade from impish to jammy as the
  file (/etc/netplan/10-rpi-ethernet-eth0.yaml) still remains in place,
  and the new netplan version on jammy chokes on the space-separated
  driver filter.

  This results in the entire netplan configuration failing to apply,
  with the result that the network doesn't come up.

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


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


[Touch-packages] [Bug 1961618] Re: Pi server image no longer connects to eth0 after upgrade to jammy

2022-02-21 Thread Dave Jones
Oh, and apparently ubuntu-settings FTBFS with the version of meson in
jammy (0.61.2-1); will add a patch for that too.

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

Title:
  Pi server image no longer connects to eth0 after upgrade to jammy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The eth0 rename fix introduced in 20.10.1, and removed in 22.04.1
  unfortunately causes problems on upgrade from impish to jammy as the
  file (/etc/netplan/10-rpi-ethernet-eth0.yaml) still remains in place,
  and the new netplan version on jammy chokes on the space-separated
  driver filter.

  This results in the entire netplan configuration failing to apply,
  with the result that the network doesn't come up.

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


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


[Touch-packages] [Bug 1961618] [NEW] Pi server image no longer connects to eth0 after upgrade to jammy

2022-02-21 Thread Dave Jones
Public bug reported:

The eth0 rename fix introduced in 20.10.1, and removed in 22.04.1
unfortunately causes problems on upgrade from impish to jammy as the
file (/etc/netplan/10-rpi-ethernet-eth0.yaml) still remains in place,
and the new netplan version on jammy chokes on the space-separated
driver filter.

This results in the entire netplan configuration failing to apply, with
the result that the network doesn't come up.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: raspi-image rls-jj-incoming

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

Title:
  Pi server image no longer connects to eth0 after upgrade to jammy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The eth0 rename fix introduced in 20.10.1, and removed in 22.04.1
  unfortunately causes problems on upgrade from impish to jammy as the
  file (/etc/netplan/10-rpi-ethernet-eth0.yaml) still remains in place,
  and the new netplan version on jammy chokes on the space-separated
  driver filter.

  This results in the entire netplan configuration failing to apply,
  with the result that the network doesn't come up.

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


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


[Touch-packages] [Bug 1959054] Re: debhelper restarts services marked --no-restart-on-upgrade

2022-02-20 Thread Dave Jones
Excellent, happy with that. I'm attaching a debdiff for the debconf
change, and will see if I can rustle up a sponsor on Monday to finally
put all this to bed!

** Patch added: "1-1959054.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1959054/+attachment/5562301/+files/1-1959054.debdiff

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

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

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

Title:
  debhelper restarts services marked --no-restart-on-upgrade

Status in debconf package in Ubuntu:
  Confirmed
Status in debhelper package in Ubuntu:
  Fix Released
Status in docker.io package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Committed
Status in debconf source package in Jammy:
  Confirmed
Status in debhelper source package in Jammy:
  Fix Released
Status in docker.io source package in Jammy:
  Fix Released
Status in libvirt source package in Jammy:
  Fix Committed
Status in debconf package in Debian:
  New
Status in debhelper package in Debian:
  New

Bug description:
  Debian bug #994204 (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that
  results in the postinst being generated in such a fashion that
  services marked --no-stop-on-upgrade (or its deprecated alias --no-
  restart-on-upgrade), restart anyway.

  Please note: this is nothing to do with the --no-restart-after-upgrade
  flag (which is, somewhat confusingly IMO, unrelated).

  I've confirmed that the flaw appears to be present in the jammy
  version of debhelper (though not impish) and that packages generated
  with it appear to contain the flawed postinst (I first encountered
  this whilst working on the open-iscsi merge), though I haven't yet
  managed to test that the flaw exhibits itself on upgrade (though I'd
  say from the presence of the flaw in the postinst, that it's a
  reasonable inference that it will).

  In dbus (the merge of which I'm currently working on), Debian has
  worked around this but given I've now run into two affected packages
  (open-iscsi and dbus), only one of which has a work-around, I'd much
  rather we got debhelper fixed up and rebuilt affected packages?

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


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


[Touch-packages] [Bug 1959211] Re: Please merge dbus 1.12.20-3 from Debian unstable

2022-02-20 Thread Dave Jones
** Changed in: dbus (Ubuntu)
   Status: New => Confirmed

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

Title:
  Please merge dbus 1.12.20-3 from Debian unstable

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Please merge dbus 1.12.20-3 from Debian unstable.

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

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


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


[Touch-packages] [Bug 1959054] Re: debhelper restarts services marked --no-restart-on-upgrade

2022-02-20 Thread Dave Jones
@ahasenack Could you try the debconf version from [1]? I've patched that
with the same fix that I've proposed upstream [2]. I'll add the relevant
debian bug here too. I realize this is *technically* a separate issue,
but it's all so interconnected and related that I'd prefer to keep it
all in one place.

[1]: https://launchpad.net/~waveform/+archive/ubuntu/dh-merge

[2]: https://salsa.debian.org/pkg-debconf/debconf/-/merge_requests/10

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

** Also affects: debconf (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006147
   Importance: Unknown
   Status: Unknown

** Changed in: docker.io (Ubuntu Jammy)
   Status: Confirmed => Fix Released

** Changed in: libvirt (Ubuntu Jammy)
   Status: Triaged => Fix Committed

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

Title:
  debhelper restarts services marked --no-restart-on-upgrade

Status in debconf package in Ubuntu:
  New
Status in debhelper package in Ubuntu:
  Fix Released
Status in docker.io package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Committed
Status in debconf source package in Jammy:
  New
Status in debhelper source package in Jammy:
  Fix Released
Status in docker.io source package in Jammy:
  Fix Released
Status in libvirt source package in Jammy:
  Fix Committed
Status in debconf package in Debian:
  Unknown
Status in debhelper package in Debian:
  New

Bug description:
  Debian bug #994204 (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that
  results in the postinst being generated in such a fashion that
  services marked --no-stop-on-upgrade (or its deprecated alias --no-
  restart-on-upgrade), restart anyway.

  Please note: this is nothing to do with the --no-restart-after-upgrade
  flag (which is, somewhat confusingly IMO, unrelated).

  I've confirmed that the flaw appears to be present in the jammy
  version of debhelper (though not impish) and that packages generated
  with it appear to contain the flawed postinst (I first encountered
  this whilst working on the open-iscsi merge), though I haven't yet
  managed to test that the flaw exhibits itself on upgrade (though I'd
  say from the presence of the flaw in the postinst, that it's a
  reasonable inference that it will).

  In dbus (the merge of which I'm currently working on), Debian has
  worked around this but given I've now run into two affected packages
  (open-iscsi and dbus), only one of which has a work-around, I'd much
  rather we got debhelper fixed up and rebuilt affected packages?

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


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


[Touch-packages] [Bug 1959054] Re: debhelper restarts services marked --no-restart-on-upgrade

2022-02-19 Thread Dave Jones
Many thanks to Andreas for the report, and the logs. I suppose it was
too much to hope that this went through entirely smoothly, and so it has
come to pass! After digging into the logs above, and then dpkg-
reconfigure's code it appears that it does the following (see [1] for
details):

* Run the package's prerm script (if it exists)
* Run the package's config script (ditto)
* Run the package's postinst script (ditto)

This may seem a little odd; why run the prerm script if you don't intend
on removing the package? Presumably because, prior to the change made
above, that's where the "stop services" action went if --no-restart-
after-upgrade was specified in d/rules. However, as discussed above,
that leaves the restart behaviour of a package spread across two
distinct versions in the case of an upgrade (because it's actually the
*old* version's prerm that runs, followed by the *new* versions's
postinst to start them up again). Now, it's the package's preinst script
that handles stopping services.

Therefore, if we were being strict, dpkg-reconfigure ought to run just
the preinst, config, and postinst scripts, avoiding the prerm entirely.
Unfortunately, I suspect that's likely to break anything that relies
upon it running the prerm script, so that's probably not a wise idea.
I'll propose a change upstream to add preinst to the running order,
leaving prerm alone for now, and I'll post a debdiff with a similar
change here.

[1]: https://salsa.debian.org/pkg-debconf/debconf/-/blob/master/dpkg-
reconfigure#L196-198

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

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

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

Title:
  debhelper restarts services marked --no-restart-on-upgrade

Status in debconf package in Ubuntu:
  New
Status in debhelper package in Ubuntu:
  Confirmed
Status in docker.io package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Triaged
Status in debconf source package in Jammy:
  New
Status in debhelper source package in Jammy:
  Confirmed
Status in docker.io source package in Jammy:
  Confirmed
Status in libvirt source package in Jammy:
  Triaged
Status in debhelper package in Debian:
  New

Bug description:
  Debian bug #994204 (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that
  results in the postinst being generated in such a fashion that
  services marked --no-stop-on-upgrade (or its deprecated alias --no-
  restart-on-upgrade), restart anyway.

  Please note: this is nothing to do with the --no-restart-after-upgrade
  flag (which is, somewhat confusingly IMO, unrelated).

  I've confirmed that the flaw appears to be present in the jammy
  version of debhelper (though not impish) and that packages generated
  with it appear to contain the flawed postinst (I first encountered
  this whilst working on the open-iscsi merge), though I haven't yet
  managed to test that the flaw exhibits itself on upgrade (though I'd
  say from the presence of the flaw in the postinst, that it's a
  reasonable inference that it will).

  In dbus (the merge of which I'm currently working on), Debian has
  worked around this but given I've now run into two affected packages
  (open-iscsi and dbus), only one of which has a work-around, I'd much
  rather we got debhelper fixed up and rebuilt affected packages?

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


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


[Touch-packages] [Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-02-18 Thread Dave Jones
@xnox Ah, that makes sense, thanks. I'll propose some seed updates in a
bit.

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions


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


[Touch-packages] [Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-02-18 Thread Dave Jones
Hmmm, I wonder if this is in the seeds, given we *finally* got around to
using the platform seeds to build the impish image (the intention was to
do this in hirsute, and they were ready but for some reason they were
never activated on that release).

Ah ha! Here's the culprit:

https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/platform/tree/raspi-common

Now I wonder why that was added ...

https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/platform/commit/raspi-
common?id=66ab1060453f5cdc8db8af901910282de20411bc

Ohhh. I wonder if this is required to grow the partition on the desktop
images. Those don't use cloud-init at all, instead there's a
"x-systemd.growfs" tag in the fstab, but perhaps this package was
required to operate that? I thought that was systemd-growfs though...
Either way, it seems like something that could be added to the desktop
seed specifically instead of the raspi-common seed.

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

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

** Changed in: cloud-init (Ubuntu)
     Assignee: Dave Jones (waveform) => (unassigned)

** Changed in: cloud-init (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions


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


[Touch-packages] [Bug 1959211] Re: Please merge dbus 1.12.20-3 from Debian unstable

2022-01-27 Thread Dave Jones
Attaching patch against Debian unstable. For ease of review, relevant
commits and tags have been pushed to the following repository:

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

Specifically:

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

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

  git range-diff old/debian..logical/1.12.20-2ubuntu2
new/debian..logical/1.12.20-3ubuntu1


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

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

Title:
  Please merge dbus 1.12.20-3 from Debian unstable

Status in dbus package in Ubuntu:
  New

Bug description:
  Please merge dbus 1.12.20-3 from Debian unstable.

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

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


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


[Touch-packages] [Bug 1959211] [NEW] Please merge dbus 1.12.20-3 from Debian unstable

2022-01-27 Thread Dave Jones
Public bug reported:

Please merge dbus 1.12.20-3 from Debian unstable.

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

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

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

Title:
  Please merge dbus 1.12.20-3 from Debian unstable

Status in dbus package in Ubuntu:
  New

Bug description:
  Please merge dbus 1.12.20-3 from Debian unstable.

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

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


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


[Touch-packages] [Bug 1958415] [NEW] Sync libdatrie 0.2.13-2 from Debian unstable

2022-01-19 Thread Dave Jones
Public bug reported:

Please sync libdatrie 0.2.13-2 (main) from Debian unstable.

Explanation of the Ubuntu delta and why it can be dropped:

  * debian/tests/build: Make build test cross-testable

This change was introduced in libdatrie 0.2.13-1ubuntu1. Upstream
incorporated a variation on this patch in 0.2.13-2; from
https://salsa.debian.org/debian/libdatrie/-/commit/9d0be356dbc5586fc913a27529807c0bd975ec8f:

  * d/tests/build: Make build test cross-testable.
Change adapted from Sebastien Bacher's patch for libthai in bug #983522.
Thanks Julian Andres Klode for first rasing this with initial patch.
(Closes: #982540)

The later 0.2.13-1ubuntu2 and 0.2.13-1ubuntu3 versions were no-change
rebuilds and can be ignored. All Ubuntu deltas are present upstream; no
significant or unwanted changes in Debian packaging.

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

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

Title:
  Sync libdatrie 0.2.13-2 from Debian unstable

Status in libdatrie package in Ubuntu:
  New

Bug description:
  Please sync libdatrie 0.2.13-2 (main) from Debian unstable.

  Explanation of the Ubuntu delta and why it can be dropped:

* debian/tests/build: Make build test cross-testable

  This change was introduced in libdatrie 0.2.13-1ubuntu1. Upstream
  incorporated a variation on this patch in 0.2.13-2; from
  
https://salsa.debian.org/debian/libdatrie/-/commit/9d0be356dbc5586fc913a27529807c0bd975ec8f:

* d/tests/build: Make build test cross-testable.
  Change adapted from Sebastien Bacher's patch for libthai in bug #983522.
  Thanks Julian Andres Klode for first rasing this with initial patch.
  (Closes: #982540)

  The later 0.2.13-1ubuntu2 and 0.2.13-1ubuntu3 versions were no-change
  rebuilds and can be ignored. All Ubuntu deltas are present upstream;
  no significant or unwanted changes in Debian packaging.

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


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


[Touch-packages] [Bug 574287] Re: tasksel: forcefully removes packages when tasks overlap

2022-01-13 Thread Dave Jones
** Tags removed: rls-jj-incoming

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

Title:
  tasksel: forcefully removes packages when tasks overlap

Status in apt package in Ubuntu:
  Invalid
Status in tasksel package in Ubuntu:
  Confirmed
Status in tasksel package in Debian:
  Fix Released

Bug description:
  TEST CASE

  1. Boot Lucid LiveCD

  2. run "sudo tasksel" and select "virtual machine host"

  3. run "sudo tasksel" and deselect "virtual machine host"

  4. watch how tasksel uninstalls your system

  OBSERVATIONS

  What seems to happen is that apt vengefully removes ALL of the items
  associated with one task, including several base dependencies of other
  tasks (e.g. ubuntu-desktop)

  One illustrative example is the openssh-server task:
  This one includes the packages openssh-server, tcpd and libwrap0.
  From a normal ubuntu-desktop (e.g. ~liveCD) both tcpd and libwrap0 are 
already installed, and the task-install pulls in only openssh-server.
  However when the task is removed, all these three packages (openssh-server, 
tcpd and libwrap0) are forcefully removed.
  Since libwrap0 is a core dependency of gnome, a large part of gnome will be 
removed alongside the removal of the task.

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


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


[Touch-packages] [Bug 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd

2021-12-14 Thread Dave Jones
Just to clarify, while gzip may be preferable this shouldn't prevent the
lz4 fix from landing. It's a "good enough" workaround for a bug that
prevents people from running apt-upgrade (which is far more important
than "choice of compression algorithm").

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

Title:
  raspi 64 bit Impish image fails update-initramfs with OOM on zstd

Status in ubuntu-settings package in Ubuntu:
  Confirmed
Status in ubuntu-settings source package in Impish:
  Confirmed
Status in ubuntu-settings source package in Jammy:
  Confirmed

Bug description:
  When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit
  Impish image and nothing new installed to it, update-initramfs fails
  like so:

  Setting up linux-firmware (1.201.1) ...
  update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi
  Killed
   E: mkinitramfs failure 
zstd -q -19 -T0 137

  A simple workaround for now is to switch to the old lz4 default:

  $ sudo apt install lz4
  $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' 
/etc/initramfs-tools/initramfs.conf

  Original Workaround
  ===

  Adding a swap file to the setup allowed 'apt -f install' to run
  successfully.

  How the device was setup
  1) xzcat | dd the sdcard with the impish 64 bit server image
  2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, 
link getty@ttyGS0.service
  ) as suggested in 
https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console
  3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest 
of the 16GB flash, e2fsck, resize2fs
  4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per 
https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html
  5) boot, connect to wireless, ssh in
  6) apt update && apt upgrade
  7) observe above issue

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: linux-firmware 1.201.1
  ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14
  Uname: Linux 5.13.0-1009-raspi aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 19:47 seq
   crw-rw 1 root audio 116, 33 Nov  8 19:47 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.13.0-1009-raspi.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  Date: Mon Nov  8 21:00:59 2021
  Dependencies:

  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  ImageMediaBuild: 20211013
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lspci-vt: -[:00]-
  Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
  PackageArchitecture: all
  PciMultimedia:

  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 
smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 
vc_mem.mem_size=0x2000  dwc_otg.lpm_enable=0 console=ttyS0,115200 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash modules-load=dwc2,g_serial
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-firmware
  StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 
bcm2835_codec vc_sm_cma
  Title: package linux-firmware 1.201.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

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


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


[Touch-packages] [Bug 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd

2021-12-14 Thread Dave Jones
Some further research on this [1] suggests gzip may be a preferable
choice on the smaller platforms (lower memory usage, and better
compression anyway), plus this would alleviate the need for including
lz4 in the images.

I need to do some further analysis of the decompression to see if it is
still suitable there too.

[1] https://github.com/waveform80/compression/

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

Title:
  raspi 64 bit Impish image fails update-initramfs with OOM on zstd

Status in ubuntu-settings package in Ubuntu:
  Confirmed
Status in ubuntu-settings source package in Impish:
  Confirmed
Status in ubuntu-settings source package in Jammy:
  Confirmed

Bug description:
  When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit
  Impish image and nothing new installed to it, update-initramfs fails
  like so:

  Setting up linux-firmware (1.201.1) ...
  update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi
  Killed
   E: mkinitramfs failure 
zstd -q -19 -T0 137

  A simple workaround for now is to switch to the old lz4 default:

  $ sudo apt install lz4
  $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' 
/etc/initramfs-tools/initramfs.conf

  Original Workaround
  ===

  Adding a swap file to the setup allowed 'apt -f install' to run
  successfully.

  How the device was setup
  1) xzcat | dd the sdcard with the impish 64 bit server image
  2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, 
link getty@ttyGS0.service
  ) as suggested in 
https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console
  3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest 
of the 16GB flash, e2fsck, resize2fs
  4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per 
https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html
  5) boot, connect to wireless, ssh in
  6) apt update && apt upgrade
  7) observe above issue

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: linux-firmware 1.201.1
  ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14
  Uname: Linux 5.13.0-1009-raspi aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 19:47 seq
   crw-rw 1 root audio 116, 33 Nov  8 19:47 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.13.0-1009-raspi.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  Date: Mon Nov  8 21:00:59 2021
  Dependencies:

  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  ImageMediaBuild: 20211013
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lspci-vt: -[:00]-
  Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
  PackageArchitecture: all
  PciMultimedia:

  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 
smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 
vc_mem.mem_size=0x2000  dwc_otg.lpm_enable=0 console=ttyS0,115200 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash modules-load=dwc2,g_serial
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-firmware
  StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 
bcm2835_codec vc_sm_cma
  Title: package linux-firmware 1.201.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

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


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


[Touch-packages] [Bug 1954348] [NEW] sed 4.8-1 needs patch disabling non-portable tests

2021-12-09 Thread Dave Jones
Public bug reported:

The sed 4.8-1 package currently in proposed is failing to migrate due to
a failing test on armhf. The patch added in 4.7-1ubuntu1 is still
required to work around this, and the attached debdiff restores this.

The patch has been applied upstream to gnulib
(https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=175e0bc72808d564074c4adcc72aeadb74adfcc6)
but sed upstream has not yet bumped the version of gnulib that it
vendors in (or more precisely has not made a release since bumping its
version of gnulib; 4.8 predates that).

The patch itself simply disables the non-portable tests which is not
exactly ideal, but given it's what upstream's gone with we ought to
follow suit.

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

** Patch added: "sed-migration.debdiff"
   
https://bugs.launchpad.net/bugs/1954348/+attachment/5546537/+files/sed-migration.debdiff

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

Title:
  sed 4.8-1 needs patch disabling non-portable tests

Status in sed package in Ubuntu:
  New

Bug description:
  The sed 4.8-1 package currently in proposed is failing to migrate due
  to a failing test on armhf. The patch added in 4.7-1ubuntu1 is still
  required to work around this, and the attached debdiff restores this.

  The patch has been applied upstream to gnulib
  
(https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=175e0bc72808d564074c4adcc72aeadb74adfcc6)
  but sed upstream has not yet bumped the version of gnulib that it
  vendors in (or more precisely has not made a release since bumping its
  version of gnulib; 4.8 predates that).

  The patch itself simply disables the non-portable tests which is not
  exactly ideal, but given it's what upstream's gone with we ought to
  follow suit.

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


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


[Touch-packages] [Bug 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd

2021-12-07 Thread Dave Jones
** Changed in: ubuntu-settings (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: ubuntu-settings (Ubuntu Impish)
   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/1950214

Title:
  raspi 64 bit Impish image fails update-initramfs with OOM on zstd

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in ubuntu-settings package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Impish:
  New
Status in ubuntu-settings source package in Impish:
  Confirmed
Status in initramfs-tools source package in Jammy:
  Confirmed
Status in ubuntu-settings source package in Jammy:
  Confirmed

Bug description:
  When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit
  Impish image and nothing new installed to it, update-initramfs fails
  like so:

  Setting up linux-firmware (1.201.1) ...
  update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi
  Killed
   E: mkinitramfs failure 
zstd -q -19 -T0 137

  A simple workaround for now is to switch to the old lz4 default:

  $ sudo apt install lz4
  $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' 
/etc/initramfs-tools/initramfs.conf

  Original Workaround
  ===

  Adding a swap file to the setup allowed 'apt -f install' to run
  successfully.

  How the device was setup
  1) xzcat | dd the sdcard with the impish 64 bit server image
  2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, 
link getty@ttyGS0.service
  ) as suggested in 
https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console
  3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest 
of the 16GB flash, e2fsck, resize2fs
  4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per 
https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html
  5) boot, connect to wireless, ssh in
  6) apt update && apt upgrade
  7) observe above issue

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: linux-firmware 1.201.1
  ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14
  Uname: Linux 5.13.0-1009-raspi aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 19:47 seq
   crw-rw 1 root audio 116, 33 Nov  8 19:47 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.13.0-1009-raspi.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  Date: Mon Nov  8 21:00:59 2021
  Dependencies:

  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  ImageMediaBuild: 20211013
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lspci-vt: -[:00]-
  Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
  PackageArchitecture: all
  PciMultimedia:

  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 
smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 
vc_mem.mem_size=0x2000  dwc_otg.lpm_enable=0 console=ttyS0,115200 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash modules-load=dwc2,g_serial
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-firmware
  StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 
bcm2835_codec vc_sm_cma
  Title: package linux-firmware 1.201.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

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


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


[Touch-packages] [Bug 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd

2021-12-07 Thread Dave Jones
The attached debdiff fixes this issue in ubuntu-settings (and restores
the 21.04.3 changes that were previously missing). Packages have been
built and tested in the following PPA:

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

** Patch added: "1-1950214.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1950214/+attachment/5546073/+files/1-1950214.debdiff

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

Title:
  raspi 64 bit Impish image fails update-initramfs with OOM on zstd

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in ubuntu-settings package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Impish:
  New
Status in ubuntu-settings source package in Impish:
  Confirmed
Status in initramfs-tools source package in Jammy:
  Confirmed
Status in ubuntu-settings source package in Jammy:
  Confirmed

Bug description:
  When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit
  Impish image and nothing new installed to it, update-initramfs fails
  like so:

  Setting up linux-firmware (1.201.1) ...
  update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi
  Killed
   E: mkinitramfs failure 
zstd -q -19 -T0 137

  A simple workaround for now is to switch to the old lz4 default:

  $ sudo apt install lz4
  $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' 
/etc/initramfs-tools/initramfs.conf

  Original Workaround
  ===

  Adding a swap file to the setup allowed 'apt -f install' to run
  successfully.

  How the device was setup
  1) xzcat | dd the sdcard with the impish 64 bit server image
  2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, 
link getty@ttyGS0.service
  ) as suggested in 
https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console
  3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest 
of the 16GB flash, e2fsck, resize2fs
  4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per 
https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html
  5) boot, connect to wireless, ssh in
  6) apt update && apt upgrade
  7) observe above issue

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: linux-firmware 1.201.1
  ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14
  Uname: Linux 5.13.0-1009-raspi aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 19:47 seq
   crw-rw 1 root audio 116, 33 Nov  8 19:47 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.13.0-1009-raspi.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  Date: Mon Nov  8 21:00:59 2021
  Dependencies:

  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  ImageMediaBuild: 20211013
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lspci-vt: -[:00]-
  Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
  PackageArchitecture: all
  PciMultimedia:

  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 
smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 
vc_mem.mem_size=0x2000  dwc_otg.lpm_enable=0 console=ttyS0,115200 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash modules-load=dwc2,g_serial
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-firmware
  StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 
bcm2835_codec vc_sm_cma
  Title: package linux-firmware 1.201.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

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


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

[Touch-packages] [Bug 1953521] Re: fixrtc produces extraneous (confusing) output

2021-12-07 Thread Dave Jones
The attached debdiff fixes the issue.

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

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

Title:
  fixrtc produces extraneous (confusing) output

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The premount script for fixrtc produces a couple of lines of
  extraneous (and slightly confusing) output. While this is irrelevant
  for most platforms, on the pi images (which use fixrtc owing to the
  lack of an RTC on the board), it means that "ext4" and "Thu Jan  1
  00:00:10 UTC 1970" are the first console output on every boot.

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


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


[Touch-packages] [Bug 1953521] [NEW] fixrtc produces extraneous (confusing) output

2021-12-07 Thread Dave Jones
Public bug reported:

The premount script for fixrtc produces a couple of lines of extraneous
(and slightly confusing) output. While this is irrelevant for most
platforms, on the pi images (which use fixrtc owing to the lack of an
RTC on the board), it means that "ext4" and "Thu Jan  1 00:00:10 UTC
1970" are the first console output on every boot.

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

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

Title:
  fixrtc produces extraneous (confusing) output

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The premount script for fixrtc produces a couple of lines of
  extraneous (and slightly confusing) output. While this is irrelevant
  for most platforms, on the pi images (which use fixrtc owing to the
  lack of an RTC on the board), it means that "ext4" and "Thu Jan  1
  00:00:10 UTC 1970" are the first console output on every boot.

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


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


[Touch-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+

2021-12-07 Thread Dave Jones
Targetting to Impish and Jammy as apparently ubuntu-settings lost the
21.04.3 changes in 21.10.1 (which was based on 21.04.2).

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

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

** Also affects: ubuntu-meta (Ubuntu Jammy)
   Importance: Undecided
   Status: Fix Released

** Also affects: ubuntu-settings (Ubuntu Jammy)
   Importance: Undecided
   Status: Fix Released

** Changed in: ubuntu-settings (Ubuntu Jammy)
   Status: Fix Released => New

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

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

Title:
  eth0 interface name change fails on Pi 3/3+

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-meta source package in Hirsute:
  Fix Released
Status in ubuntu-settings source package in Hirsute:
  Fix Released
Status in ubuntu-meta source package in Impish:
  Fix Released
Status in ubuntu-settings source package in Impish:
  New
Status in ubuntu-meta source package in Jammy:
  Fix Released
Status in ubuntu-settings source package in Jammy:
  New

Bug description:
  The netplan configuration in ubuntu-raspi-settings (and more widely,
  the network-config in the gadget used on the server images) fails to
  rename the internal ethernet interface on Pi 3B and 3B+ models from
  "en" to "eth0". In the netplan case this is because the
  driver matching logic doesn't handle space-separate driver matches
  (although the underlying networkd system does); in the cloud-init case
  it simply refuses to rename interfaces that aren't matched by full MAC
  address.

  The intended fix is to stop attempting to do this via netplan or
  cloud-init, and simply handle this via a networkd .link file in
  ubuntu-raspi-settings. This will require an update to the relevant
  seeds as this package is currently only pulled into ubuntu-desktop-
  raspi, not ubuntu-server-raspi.

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


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


[Touch-packages] [Bug 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd

2021-12-07 Thread Dave Jones
Adding ubuntu-settings as that's where the override for the raspi will
be added

** Also affects: ubuntu-settings (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-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1950214

Title:
  raspi 64 bit Impish image fails update-initramfs with OOM on zstd

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in ubuntu-settings package in Ubuntu:
  New
Status in initramfs-tools source package in Impish:
  New
Status in ubuntu-settings source package in Impish:
  New
Status in initramfs-tools source package in Jammy:
  Confirmed
Status in ubuntu-settings source package in Jammy:
  New

Bug description:
  When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit
  Impish image and nothing new installed to it, update-initramfs fails
  like so:

  Setting up linux-firmware (1.201.1) ...
  update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi
  Killed
   E: mkinitramfs failure 
zstd -q -19 -T0 137

  A simple workaround for now is to switch to the old lz4 default:

  $ sudo apt install lz4
  $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' 
/etc/initramfs-tools/initramfs.conf

  Original Workaround
  ===

  Adding a swap file to the setup allowed 'apt -f install' to run
  successfully.

  How the device was setup
  1) xzcat | dd the sdcard with the impish 64 bit server image
  2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, 
link getty@ttyGS0.service
  ) as suggested in 
https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console
  3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest 
of the 16GB flash, e2fsck, resize2fs
  4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per 
https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html
  5) boot, connect to wireless, ssh in
  6) apt update && apt upgrade
  7) observe above issue

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: linux-firmware 1.201.1
  ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14
  Uname: Linux 5.13.0-1009-raspi aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 19:47 seq
   crw-rw 1 root audio 116, 33 Nov  8 19:47 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.13.0-1009-raspi.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  Date: Mon Nov  8 21:00:59 2021
  Dependencies:

  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  ImageMediaBuild: 20211013
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lspci-vt: -[:00]-
  Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
  PackageArchitecture: all
  PciMultimedia:

  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 
smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 
vc_mem.mem_size=0x2000  dwc_otg.lpm_enable=0 console=ttyS0,115200 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash modules-load=dwc2,g_serial
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-firmware
  StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 
bcm2835_codec vc_sm_cma
  Title: package linux-firmware 1.201.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

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


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


[Touch-packages] [Bug 1923672] Re: [FFe] Provide access to GPIO to default user

2021-12-07 Thread Dave Jones
Targetting to Impish and Jammy as apparently ubuntu-settings lost the
21.04.3 changes in 21.10.1 (which was based on 21.04.2).

** Also affects: ubuntu-settings (Ubuntu Jammy)
   Importance: Undecided
   Status: Fix Released

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

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

** Changed in: ubuntu-settings (Ubuntu Hirsute)
   Status: New => Fix Released

** Changed in: ubuntu-settings (Ubuntu Jammy)
   Status: Fix Released => New

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

Title:
  [FFe] Provide access to GPIO to default user

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Hirsute:
  Fix Released
Status in ubuntu-settings source package in Impish:
  New
Status in ubuntu-settings source package in Jammy:
  New

Bug description:
  At present, access to the GPIO pins is provided to the dialout group
  by the udev rules from the rpi.gpio-common package. However, rpi.gpio
  is a single GPIO library, and the device(s) it provides access to are
  not specific to it. Moreover, the interface used is deprecated and the
  /dev/gpiochip* interface is now the favoured mechanism for controlling
  the GPIO pins.

  The choice of the dialout group appears reasonable (historically it's
  used to provide access to the serial ports, and indeed the serial
  ports are part of the GPIO header on Raspberry Pi devices), but the
  rules should be extended to cover the modern /dev/gpiochip* devices,
  the related /dev/spidev* and /dev/i2c-* devices, and should be placed
  in a central location (i.e. ubuntu-raspi-settings) rather than in a
  specific GPIO library (like rpi.gpio).

  Related to this is LP: #1923363 which seeks to ensure equal access
  across images (the default user is currently granted "dialout" group
  membership on the pi server images, but not the desktop ones).

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


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


[Touch-packages] [Bug 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd

2021-12-06 Thread Dave Jones
** Also affects: initramfs-tools (Ubuntu Jammy)
   Importance: Undecided
   Status: Confirmed

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

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

Title:
  raspi 64 bit Impish image fails update-initramfs with OOM on zstd

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Impish:
  New
Status in initramfs-tools source package in Jammy:
  Confirmed

Bug description:
  When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit
  Impish image and nothing new installed to it, update-initramfs fails
  like so:

  Setting up linux-firmware (1.201.1) ...
  update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi
  Killed
   E: mkinitramfs failure 
zstd -q -19 -T0 137

  A simple workaround for now is to switch to the old lz4 default:

  $ sudo apt install lz4
  $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' 
/etc/initramfs-tools/initramfs.conf

  Original Workaround
  ===

  Adding a swap file to the setup allowed 'apt -f install' to run
  successfully.

  How the device was setup
  1) xzcat | dd the sdcard with the impish 64 bit server image
  2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, 
link getty@ttyGS0.service
  ) as suggested in 
https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console
  3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest 
of the 16GB flash, e2fsck, resize2fs
  4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per 
https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html
  5) boot, connect to wireless, ssh in
  6) apt update && apt upgrade
  7) observe above issue

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: linux-firmware 1.201.1
  ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14
  Uname: Linux 5.13.0-1009-raspi aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 19:47 seq
   crw-rw 1 root audio 116, 33 Nov  8 19:47 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.13.0-1009-raspi.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  Date: Mon Nov  8 21:00:59 2021
  Dependencies:

  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  ImageMediaBuild: 20211013
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lspci-vt: -[:00]-
  Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
  PackageArchitecture: all
  PciMultimedia:

  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 
smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 
vc_mem.mem_size=0x2000  dwc_otg.lpm_enable=0 console=ttyS0,115200 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash modules-load=dwc2,g_serial
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-firmware
  StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 
bcm2835_codec vc_sm_cma
  Title: package linux-firmware 1.201.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

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


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


[Touch-packages] [Bug 1950985] Re: Please merge netcat-openbsd 1.218-2 from Debian unstable

2021-12-02 Thread Dave Jones
Yes, managed an sbuild of source and binary packages in a jammy chroot
(build log: https://paste.ubuntu.com/p/ySB3mm6xMG/) -- what was the
build failure you encountered?

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

Title:
  Please merge netcat-openbsd 1.218-2 from Debian unstable

Status in netcat-openbsd package in Ubuntu:
  Incomplete

Bug description:
  Please merge netcat-openbsd 1.218-2 from Debian unstable.

  Updated changelog and diff against Debian unstable is attached below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1950985/+subscriptions


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


[Touch-packages] [Bug 1950985] Re: Please merge netcat-openbsd 1.218-2 from Debian unstable

2021-11-15 Thread Dave Jones
netcat-openbsd (1.218-2ubuntu1) jammy; urgency=low

  * Merge from Debian unstable. Remaining changes:
- Move the netcat transitional package here and have it depend on the
  peferred netcat-openbsd implementation of netcat, not
  netcat-traditional.

 -- Dave Jones   Sun, 14 Nov 2021 09:42:30
+


** Patch added: "1-1950985.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1950985/+attachment/5541005/+files/1-1950985.debdiff

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

Title:
  Please merge netcat-openbsd 1.218-2 from Debian unstable

Status in netcat-openbsd package in Ubuntu:
  New

Bug description:
  Please merge netcat-openbsd 1.218-2 from Debian unstable.

  Updated changelog and diff against Debian unstable is attached below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1950985/+subscriptions


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


[Touch-packages] [Bug 1950985] [NEW] Please merge netcat-openbsd 1.218-2 from Debian unstable

2021-11-15 Thread Dave Jones
Public bug reported:

Please merge netcat-openbsd 1.218-2 from Debian unstable.

Updated changelog and diff against Debian unstable is attached below.

** Affects: netcat-openbsd (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Please merge netcat-openbsd 1.218-2 from Debian unstable

Status in netcat-openbsd package in Ubuntu:
  New

Bug description:
  Please merge netcat-openbsd 1.218-2 from Debian unstable.

  Updated changelog and diff against Debian unstable is attached below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1950985/+subscriptions


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


[Touch-packages] [Bug 1950214] Re: raspi 64 bit Impish image can't 'apt upgrade' without adding swap on pi zero 2

2021-11-09 Thread Dave Jones
This is down to initramfs-tools switching to zstd by default, which has
such huge memory requirements that it gets killed by OOM on the Zero 2
(and presumably the 3A+?) which only has 512MB of RAM. The default
should be switched back to lz4, at least on the Pi images.

Note to self: add a test for update-initramfs -u to the ISO tracker for
the Pi server images to ensure it gets tested across the platforms.

** Description changed:

  When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish
  image and nothing new installed to it, update-initramfs fails like so:
  
- Setting up linux-firmware (1.201.1) ...   
   
- update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi   
   
- Killed
   E: mkinitramfs failure 
zstd -q -19 -T0 137 
  
+ Setting up linux-firmware (1.201.1) ...
+ update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi
+ Killed
   E: mkinitramfs failure 
zstd -q -19 -T0 137
+ 
+ A simple workaround for now is to switch to the old lz4 default:
+ 
+ $ sudo apt install lz4
+ $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' 
/etc/initramfs-tools/initramfs.conf
+ 
+ Original Workaround
+ ===
  
  Adding a swap file to the setup allowed 'apt -f install' to run
  successfully.
  
  How the device was setup
  1) xzcat | dd the sdcard with the impish 64 bit server image
  2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, 
link getty@ttyGS0.service
  ) as suggested in 
https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console
  3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest 
of the 16GB flash, e2fsck, resize2fs
  4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per 
https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html
  5) boot, connect to wireless, ssh in
  6) apt update && apt upgrade
  7) observe above issue
  
  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: linux-firmware 1.201.1
  ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14
  Uname: Linux 5.13.0-1009-raspi aarch64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Nov  8 19:47 seq
-  crw-rw 1 root audio 116, 33 Nov  8 19:47 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Nov  8 19:47 seq
+  crw-rw 1 root audio 116, 33 Nov  8 19:47 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.13.0-1009-raspi.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  Date: Mon Nov  8 21:00:59 2021
  Dependencies:
-  
+ 
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  ImageMediaBuild: 20211013
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
-  
+ 
  Lspci-vt: -[:00]-
  Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
  PackageArchitecture: all
  PciMultimedia:
-  
+ 
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 
smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 
vc_mem.mem_size=0x2000  dwc_otg.lpm_enable=0 console=ttyS0,115200 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash modules-load=dwc2,g_serial
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-firmware
  StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 
bcm2835_codec vc_sm_cma
  Title: package linux-firmware 1.201.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

** Summary changed:

- raspi 64 bit Impish image can't 'apt upgrade' without adding swap on pi zero 2
+ raspi 64 bit Impish image fails update-initramfs with OOM on zstd

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

[Touch-packages] [Bug 1950214] Re: raspi 64 bit Impish image can't 'apt upgrade' without adding swap on pi zero 2

2021-11-09 Thread Dave Jones
** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux-firmware (Ubuntu)

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

Title:
  raspi 64 bit Impish image can't 'apt upgrade' without adding swap on
  pi zero 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit
  Impish image and nothing new installed to it, update-initramfs fails
  like so:

  Setting up linux-firmware (1.201.1) ...   
   
  update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi   
   
  Killed
   E: mkinitramfs failure 
zstd -q -19 -T0 137 
  

  Adding a swap file to the setup allowed 'apt -f install' to run
  successfully.

  How the device was setup
  1) xzcat | dd the sdcard with the impish 64 bit server image
  2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, 
link getty@ttyGS0.service
  ) as suggested in 
https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console
  3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest 
of the 16GB flash, e2fsck, resize2fs
  4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per 
https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html
  5) boot, connect to wireless, ssh in
  6) apt update && apt upgrade
  7) observe above issue

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: linux-firmware 1.201.1
  ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14
  Uname: Linux 5.13.0-1009-raspi aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 19:47 seq
   crw-rw 1 root audio 116, 33 Nov  8 19:47 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.13.0-1009-raspi.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  Date: Mon Nov  8 21:00:59 2021
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  ImageMediaBuild: 20211013
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
  PackageArchitecture: all
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 
smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 
vc_mem.mem_size=0x2000  dwc_otg.lpm_enable=0 console=ttyS0,115200 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash modules-load=dwc2,g_serial
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-firmware
  StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 
bcm2835_codec vc_sm_cma
  Title: package linux-firmware 1.201.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

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


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


[Touch-packages] [Bug 1899953] Re: Crackling audio on Raspberry Pi Desktop

2021-10-11 Thread Dave Jones
Worth noting that this issue only appears to occur when the fkms ("fake"
KMS) overlay is in use on the Ubuntu Desktop for Raspberry Pi images.
Under the kms ("full" KMS) overlay, the audio is fine. While kms is
indeed the default overlay, it is likely (due to LP: #1946368 on impish)
that many may be using fkms as a workaround.

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

Title:
  Crackling audio on Raspberry Pi Desktop

Status in PulseAudio:
  Unknown
Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Attempting to play audio (e.g. from rhythmbox) on the raspberry pi
  desktop image, results in broken up / crackling audio. The "tsched=0"
  workaround noted in
  
https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling
  successfully avoids the issue.

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


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


[Touch-packages] [Bug 1928973] Re: Please merge lvm2 2.03.11-2.1 from Debian unstable

2021-05-19 Thread Dave Jones
Attaching patch against Debian unstable. For ease of review, I've also
pushed relevant commits and tags to the following repository:

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

Specifically:

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

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

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

A test package has been built in the following PPA:

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

** Patch added: "1-1928973.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1928973/+attachment/5498796/+files/1-1928973.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/1928973

Title:
  Please merge lvm2 2.03.11-2.1 from Debian unstable

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.11-2.1 from Debian unstable.

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

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

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


[Touch-packages] [Bug 1928973] [NEW] Please merge lvm2 2.03.11-2.1 from Debian unstable

2021-05-19 Thread Dave Jones
Public bug reported:

Please merge lvm2 2.03.11-2.1 from Debian unstable.

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

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

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

Title:
  Please merge lvm2 2.03.11-2.1 from Debian unstable

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.11-2.1 from Debian unstable.

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

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

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


[Touch-packages] [Bug 1927978] [NEW] Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable

2021-05-10 Thread Dave Jones
Public bug reported:

Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable.

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

** Affects: db5.3 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable

Status in db5.3 package in Ubuntu:
  New

Bug description:
  Please merge db5.3 5.3.28+dfsg1-0.8 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/db5.3/+bug/1927978/+subscriptions

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


[Touch-packages] [Bug 1927978] Re: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable

2021-05-10 Thread Dave Jones
Attaching patch against Debian unstable. Test builds available from the
following PPA:

https://launchpad.net/~waveform/+archive/ubuntu/db/+packages

** Patch added: "1-1927978.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1927978/+attachment/5496169/+files/1-1927978.debdiff

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

Title:
  Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable

Status in db5.3 package in Ubuntu:
  New

Bug description:
  Please merge db5.3 5.3.28+dfsg1-0.8 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/db5.3/+bug/1927978/+subscriptions

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


[Touch-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi

2021-04-23 Thread Dave Jones
> Thanks for the details. You did address the part about upstreaming the
change to Debian. How important is that notification in practice? If
feels like we should have bluez preinstall on the raspi images if that's
not the case, and if it's pre-install is that really worth the packaging
overhead to have to carry a delta over Debian?

Just to give a bit of context here, the bluetooth situation on the pi is
somewhat complicated and there's compromises that we make between the
desktop and server images:

The bluetooth module on the Pi is controlled via a UART. Two UARTs are
available on the Pi (there's more on the Pi 4, but it's the same
situation for the bits we're talking about here):

* the PL011 which is full featured (buffers, flow-control, etc.), and

* the mini-UART which is ... not. Furthermore, the mini-UART's baud rate
is tied to the GPU's clock, so if that floats then the mini-UART's baud
rate floats too

On models of Pi with a bluetooth module (everything except the Pi 2, the
CM3/3+ and some models of the CM4), the PL011 is used to talk to the
bluetooth module and by default the mini-UART is disabled. This is the
configuration we use on the desktop images as we make the assumption a
serial console is less important on something which almost certainly has
a monitor, and this configuration permits the GPU clock to float
(important for something relying upon graphical acceleration).

On the server images, we assume that the serial console *is* important,
and so this is enabled by default. We don't *disable* the bluetooth
module, but we don't pre-install the packages for it either. This means
that the PL011 is tied to the bluetooth module by default (but unused),
and the mini-UART to the serial console. Because the mini-UART is in
use, the GPU's clock is locked to the base speed. This is a compromise
because all the alternatives are nastier in some way for some of the
typical use cases:

* If the server image is used without a graphical environment, and
without bluetooth, this is fine (this is the default). The GPU's clock
doesn't really matter in this scenario and the serial console will still
work reliably.

* If the server image is used without a graphical environment, but with
bluetooth, all the user needs to do is install pi-bluetooth and reboot
(personally I don't think the reboot warning is terribly necessary; like
knowing to install pi-bluetooth in the first place, it's fairly
widespread knowledge and tends to be part of first-time setup steps
anyway). This again leaves the GPU's clock locked (but without a
graphical environment that doesn't really matter), the serial console
still works, and bluetooth works.

* If the server image is used with a graphical environment, without
bluetooth, the user needs to either disable the serial console (if they
don't want it, this is a one-line change in the boot configuration), or
alternatively add the line "dtoverlay=disable-bt" to the boot
configuration which disables the bluetooth module entirely, allowing the
serial console to use the "full" PL011 UART. Either option unlocks the
GPU's clock.

* If the server image is used with a graphical environment, with
bluetooth, that's effectively the same as the desktop setup and we
assume that in this scenario the user would disable the serial console
(which means the mini-UART is no longer used and the GPU's clock can
float again); again, a one-line change in the boot configuration.

So the compromise is to ship an image which, with either zero steps or
one step can be moved to one of the scenarios above, with hardware
working acceptably for that scenario. We could default to, for example,
shipping the server image with both serial console *and* bluetooth
enabled, but that complicates moving to a GPU clock unlocked scenario as
it involves either disabling the serial console (easy) or removing
bluetooth (quite a bit harder, especially if the pi-bluetooth package is
now depended on by a meta-package, and also still involves disabling the
hardware module with the dtoverlay).

Anyway, for the above reasons I don't foresee that we're likely to ship
bluetooth enabled server images anytime soon. As to how necessary a
reboot warning is -- I'd consider it "nice to have but by no means
critical" (it's not hardware enablement after all). If we want to keep
the delta minimal, I've no objections.

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

Title:
  Bluez should notify users when they need to reboot to apply changes on
  Raspberry Pi

Status in bluez package in Ubuntu:
  In Progress
Status in bluez package in Debian:
  New

Bug description:
  In the case of upgrading or installing bluez for the first time on
  certain raspberry pi devices, a reboot may be required to apply the
  changes. We should add a check for this scenario in the postinst
  script.

To manage notifications about this bug 

[Touch-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+

2021-04-15 Thread Dave Jones
Attaching debdiff; test builds are available from the following PPA:

https://launchpad.net/~waveform/+archive/ubuntu/ubuntu-
settings/+packages

** Patch added: "1-1922266.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1922266/+attachment/5488517/+files/1-1922266.debdiff

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

Title:
  eth0 interface name change fails on Pi 3/3+

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The netplan configuration in ubuntu-raspi-settings (and more widely,
  the network-config in the gadget used on the server images) fails to
  rename the internal ethernet interface on Pi 3B and 3B+ models from
  "en" to "eth0". In the netplan case this is because the
  driver matching logic doesn't handle space-separate driver matches
  (although the underlying networkd system does); in the cloud-init case
  it simply refuses to rename interfaces that aren't matched by full MAC
  address.

  The intended fix is to stop attempting to do this via netplan or
  cloud-init, and simply handle this via a networkd .link file in
  ubuntu-raspi-settings. This will require an update to the relevant
  seeds as this package is currently only pulled into ubuntu-desktop-
  raspi, not ubuntu-server-raspi.

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

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


[Touch-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+

2021-04-14 Thread Dave Jones
It's still necessary; I've got the changes ready but was holding off as
there's possibly another fix that may need to go into this package too
(LP: #1900904). But it's getting close to release so I'll push it anyway
and deal with the other ticket separately.

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

Title:
  eth0 interface name change fails on Pi 3/3+

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The netplan configuration in ubuntu-raspi-settings (and more widely,
  the network-config in the gadget used on the server images) fails to
  rename the internal ethernet interface on Pi 3B and 3B+ models from
  "en" to "eth0". In the netplan case this is because the
  driver matching logic doesn't handle space-separate driver matches
  (although the underlying networkd system does); in the cloud-init case
  it simply refuses to rename interfaces that aren't matched by full MAC
  address.

  The intended fix is to stop attempting to do this via netplan or
  cloud-init, and simply handle this via a networkd .link file in
  ubuntu-raspi-settings. This will require an update to the relevant
  seeds as this package is currently only pulled into ubuntu-desktop-
  raspi, not ubuntu-server-raspi.

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

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


[Touch-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+

2021-04-13 Thread Dave Jones
Seeds have now been updated:

https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/400932
https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/400933

And the meta package has been updated to incorporate these changes in
1.467

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

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

** Changed in: ubuntu-settings (Ubuntu)
Milestone: None => ubuntu-21.04

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

Title:
  eth0 interface name change fails on Pi 3/3+

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The netplan configuration in ubuntu-raspi-settings (and more widely,
  the network-config in the gadget used on the server images) fails to
  rename the internal ethernet interface on Pi 3B and 3B+ models from
  "en" to "eth0". In the netplan case this is because the
  driver matching logic doesn't handle space-separate driver matches
  (although the underlying networkd system does); in the cloud-init case
  it simply refuses to rename interfaces that aren't matched by full MAC
  address.

  The intended fix is to stop attempting to do this via netplan or
  cloud-init, and simply handle this via a networkd .link file in
  ubuntu-raspi-settings. This will require an update to the relevant
  seeds as this package is currently only pulled into ubuntu-desktop-
  raspi, not ubuntu-server-raspi.

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

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


[Touch-packages] [Bug 1923672] [NEW] [FFe] Provide access to GPIO to default user

2021-04-13 Thread Dave Jones
Public bug reported:

At present, access to the GPIO pins is provided to the dialout group by
the udev rules from the rpi.gpio-common package. However, rpi.gpio is a
single GPIO library, and the device(s) it provides access to are not
specific to it. Moreover, the interface used is deprecated and the
/dev/gpiochip* interface is now the favoured mechanism for controlling
the GPIO pins.

The choice of the dialout group appears reasonable (historically it's
used to provide access to the serial ports, and indeed the serial ports
are part of the GPIO header on Raspberry Pi devices), but the rules
should be extended to cover the modern /dev/gpiochip* devices, the
related /dev/spidev* and /dev/i2c-* devices, and should be placed in a
central location (i.e. ubuntu-raspi-settings) rather than in a specific
GPIO library (like rpi.gpio).

Related to this is LP: #1923363 which seeks to ensure equal access
across images (the default user is currently granted "dialout" group
membership on the pi server images, but not the desktop ones).

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

** Summary changed:

- Provide access to GPIO to default user
+ [FFe] Provide access to GPIO to default user

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

Title:
  [FFe] Provide access to GPIO to default user

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  At present, access to the GPIO pins is provided to the dialout group
  by the udev rules from the rpi.gpio-common package. However, rpi.gpio
  is a single GPIO library, and the device(s) it provides access to are
  not specific to it. Moreover, the interface used is deprecated and the
  /dev/gpiochip* interface is now the favoured mechanism for controlling
  the GPIO pins.

  The choice of the dialout group appears reasonable (historically it's
  used to provide access to the serial ports, and indeed the serial
  ports are part of the GPIO header on Raspberry Pi devices), but the
  rules should be extended to cover the modern /dev/gpiochip* devices,
  the related /dev/spidev* and /dev/i2c-* devices, and should be placed
  in a central location (i.e. ubuntu-raspi-settings) rather than in a
  specific GPIO library (like rpi.gpio).

  Related to this is LP: #1923363 which seeks to ensure equal access
  across images (the default user is currently granted "dialout" group
  membership on the pi server images, but not the desktop ones).

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

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


[Touch-packages] [Bug 1920837] Re: apport bugs from official raspi or riscv images are not identified

2021-04-06 Thread Dave Jones
The most reliable means I know of at the moment for detecting Raspberry
Pi hardware at runtime  is to query the device-tree.

For example, flash-kernel determines the type of board it is running on,
by matching the content of /proc/device-tree/model (e.g. "Raspberry Pi
400 Rev 1.0") against a pre-determined list of strings in its database.
Personally I don't much like matching fixed strings -- new board
revisions frequently come out and then f-k needs patching to add them,
but last cycle I did add the ability to match the "Raspberry Pi *" glob
as an attempt to support new boards even if they come out mid-cycle.
Something similar could be accomplished with some Python like so:

try:
with open('/proc/device-tree/model', 'r', encoding='ascii') as f:
is_a_pi = f.read().startswith('Raspberry Pi ')
except FileNotFoundError:
is_a_pi = False

That seems to work reliably (even on compute modules where the model is
"Raspberry Pi Compute Module 4 Rev 1.0"), but I've no idea if the /proc
/device-tree/model file *always* exists or whether other boards publish
useful information in there.

Another possibility is to look at /proc/device-tree/compatible which I
*think* should always exist assuming a device-tree is in use on the
system. This is a binary file containing a sequence of NUL-terminated
strings, each of which is of the form "vendor,model" and is intended for
kernel driver matching. For example, on the Pi 400 it contains:

raspberrypi,400\0brcm,bcm2711\0

(where \0 is the NUL character). And on a 3B+ contains:

raspberrypi,3-model-b-plus\0brcm,bcm2837\0

My understanding is there's no strict requirement that these strings
appear in any particular order so simple prefix matching is potentially
unreliable. However, it's trivial enough to parse and extract the
"raspberrypi" vendor from this with some Python like:

try:
with open('/proc/device-tree/compatible', 'rb') as f:
is_a_pi = any(vendor == 'raspberrypi'
  for s in f.read().split(b'\0') if s
  for vendor, model in (s.decode('ascii').split(',', 1),))
except FileNotFoundError:
is_a_pi = False

Something similar *should* be reasonably useful with just about any
board that uses a device tree (but obviously PCs don't have device-trees
so we still need the file-not-found check).

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

Title:
  apport bugs from official raspi or riscv images are not identified

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  In Progress
Status in apport source package in Groovy:
  In Progress

Bug description:
  It would be helpful if bugs reported from images for Raspberry Pi's or
  RISCV systems were tagged so that one could search for bugs from
  systems running those images e.g. 'raspi-image'.

  [Test Case]
  After installing a preinstalled image of Ubuntu for Raspberry Pi do the 
following:
  1) run 'ubuntu-bug apport'
  2) view the bug report and check the Tags field

  With the current version of apport you will not see the tag 'raspi-image'.
  With the version of apport in -proposed you will see the tag 'raspi-image'.

  [Where problems could occur]
  If the code being added is syntactically incorrect then we'd see a Traceback 
which would be bad as it could affect all bug / crash reports.

  [Other Info]
  Since there aren't any Groovy images for RISC-V there will be nothing to test 
there.

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

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


[Touch-packages] [Bug 1922266] [NEW] eth0 interface name change fails on Pi 3/3+

2021-04-01 Thread Dave Jones
Public bug reported:

The netplan configuration in ubuntu-raspi-settings (and more widely, the
network-config in the gadget used on the server images) fails to rename
the internal ethernet interface on Pi 3B and 3B+ models from "en" to "eth0". In the netplan case this is because the driver
matching logic doesn't handle space-separate driver matches (although
the underlying networkd system does); in the cloud-init case it simply
refuses to rename interfaces that aren't matched by full MAC address.

The intended fix is to stop attempting to do this via netplan or cloud-
init, and simply handle this via a networkd .link file in ubuntu-raspi-
settings. This will require an update to the relevant seeds as this
package is currently only pulled into ubuntu-desktop-raspi, not ubuntu-
server-raspi.

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

Title:
  eth0 interface name change fails on Pi 3/3+

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The netplan configuration in ubuntu-raspi-settings (and more widely,
  the network-config in the gadget used on the server images) fails to
  rename the internal ethernet interface on Pi 3B and 3B+ models from
  "en" to "eth0". In the netplan case this is because the
  driver matching logic doesn't handle space-separate driver matches
  (although the underlying networkd system does); in the cloud-init case
  it simply refuses to rename interfaces that aren't matched by full MAC
  address.

  The intended fix is to stop attempting to do this via netplan or
  cloud-init, and simply handle this via a networkd .link file in
  ubuntu-raspi-settings. This will require an update to the relevant
  seeds as this package is currently only pulled into ubuntu-desktop-
  raspi, not ubuntu-server-raspi.

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

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


[Touch-packages] [Bug 1915966] Re: Please merge initramfs-tools 0.139 from Debian unstable

2021-03-10 Thread Dave Jones
Attaching revised patch with needs-root added to the new qemu-related
tests (to work around build failure:
https://launchpad.net/ubuntu/+source/initramfs-
tools/0.139ubuntu1/+build/21138158)

** Patch added: "2-1915966.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1915966/+attachment/5475404/+files/2-1915966.debdiff

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

Title:
  Please merge initramfs-tools 0.139 from Debian unstable

Status in initramfs-tools package in Ubuntu:
  Fix Committed

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

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

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

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


[Touch-packages] [Bug 1915966] Re: Please merge initramfs-tools 0.139 from Debian unstable

2021-02-17 Thread Dave Jones
Attaching patch against Debian unstable. For ease of review, I've also
pushed relevant commits and tags to the following repository:

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

Specifically:

* The logical/0.137ubuntu12 tag represents our split-out delta on top of 
old/debian (0.137)
* The merge/0.139ubuntu1 tag represents the rebased delta on top of new/debian 
(0.139)

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

  git range-diff old/debian..logical/0.137ubuntu12
new/debian..merge/0.139ubuntu1

A test package has been built in the following PPA:

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

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

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

Title:
  Please merge initramfs-tools 0.139 from Debian unstable

Status in initramfs-tools package in Ubuntu:
  New

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

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

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

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


[Touch-packages] [Bug 1915966] [NEW] Please merge initramfs-tools 0.139 from Debian unstable

2021-02-17 Thread Dave Jones
Public bug reported:

Please merge initramfs-tools 0.139 from Debian unstable.

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

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

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

Title:
  Please merge initramfs-tools 0.139 from Debian unstable

Status in initramfs-tools package in Ubuntu:
  New

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

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

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

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


[Touch-packages] [Bug 1571506] Re: update-initramfs should include firmware from /lib/firmware/updates

2021-02-08 Thread Dave Jones
** Changed in: initramfs-tools (Ubuntu Hirsute)
 Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  update-initramfs should include firmware from /lib/firmware/updates

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools source package in Focal:
  New
Status in initramfs-tools source package in Groovy:
  New
Status in initramfs-tools source package in Hirsute:
  Triaged

Bug description:
  according to the kernel doc
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/firmware_class/README

  Linux kernel will search firmware from
  "/lib/firmware/updates/" UTS_RELEASE,
  "/lib/firmware/updates",
  "/lib/firmware/" UTS_RELEASE,
  "/lib/firmware"

  But the add module function in initramfs-tools won't search the
  "/lib/firmware/updates".

  This problem applies to all Ubuntu releases.

  Attach patch to fix this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.2
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:24:29 2016
  InstallationDate: Installed on 2014-04-23 (725 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1915005] Re: Please merge findutils 4.8.0 from Debian unstable

2021-02-08 Thread Dave Jones
Attaching patch against Debian unstable.

** Patch added: "1-1915005.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1915005/+attachment/5461235/+files/1-1915005.debdiff

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

Title:
  Please merge findutils 4.8.0 from Debian unstable

Status in findutils package in Ubuntu:
  New

Bug description:
  Please merge findutils 4.8.0-1 from Debian unstable.

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

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

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


[Touch-packages] [Bug 1915005] [NEW] Please merge findutils 4.8.0 from Debian unstable

2021-02-08 Thread Dave Jones
Public bug reported:

Please merge findutils 4.8.0-1 from Debian unstable.

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

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

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

Title:
  Please merge findutils 4.8.0 from Debian unstable

Status in findutils package in Ubuntu:
  New

Bug description:
  Please merge findutils 4.8.0-1 from Debian unstable.

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

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

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


[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

2021-02-02 Thread Dave Jones
There's a version of bluez with the patches that I've submitted upstream
built in the following PPA against the hirsute branch (the patch changes
are pretty minimal; basically amounts to removal of the arbitrary
sleep(1) as during December's tests I couldn't find a single platform
that actually required that, even amongst the Pi's we don't support like
the zero):

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

I'm happy to convert that to a git-ubuntu branch if that's preferable.
Once sponsored, we should consider SRU'ing to focal given that Pi400
support is now being SRU'd there generally.

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Groovy:
  Fix Released
Status in bluez source package in Hirsute:
  Triaged

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * Enable the -proposed repository for the release (groovy)
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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


[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

2020-11-25 Thread Dave Jones
@hujq is there anything unusual about your bluetooth setup? miniuart-bt
overlay or anything like that? I'm unable to replicate the failure here
on a Pi 4 8GB

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Groovy:
  Fix Released
Status in bluez source package in Hirsute:
  Triaged

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * Enable the -proposed repository for the release (groovy)
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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


Re: [Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

2020-11-13 Thread Dave Jones
On Fri, Nov 13, 2020 at 09:37:34AM -, Sebastien Bacher wrote:
>@Matthieu, @Dave, thanks for the comments and details.
>
>I'm not blocking work to land, the 20.10 SRU could be accepted now and I 
>didn't revert in that serie.
>The SRU team tries to ensure the fix is in the new serie so it doesn't get 
>forgotten/regress when next version is out but I think it's pretty clear we 
>are going to sort out the review details, that's not a blocker and SRU team 
>has been happy in the past to let things in with the understand than $newserie 
>is being sorted out

Ah, my apologies - I had mis-interpreted the reversion as applying to 
the SRU. I've no issue with a reversion in hirsute, provided it doesn't 
delay existing users from using their Bluetooth hardware.

>> If upstream say "yes" to the patches, without further discussion: that's
>> great, but there'd presumably still be some delay before another version
>> makes its way down to us, so we'd be applying *some* patch to make it work 
>> in the interim.
>
>Again I'm not asking for the patches to be reviewed or accepted upstream
>before they are uploaded to Ubuntu, I'm just asking for them to be sent
>upstream and the reference to the email/report/merge request to be added
>to the patches. It would probably have been less work to just do it
>rather than type a long explanation here on why we need to distro patch
>in any case (which I never  disagreed with)

I estimate, as I think several others do judging by various comments, 
that the patches in their current state don't stand much chance of 
passing muster upstream, and I have no desire to waste their time with a 
premature submission. At the very least, some justification needs adding 
to the 1 second sleep: either a datasheet reference, which I've so far 
failed to find, or some empirical measurements that it's actually 
required (which I'm in the process of gathering; I've verified *a* delay 
is required but not the minimum, or whether it can be combined with the 
post-load nanosleep), along with evidence it doesn't break any existing 
platforms (I've found a datasheet reference to back that bit up, but 
tests are good too).

Anyway, sorry I mis-interpreted the release your action applied to; I 
look forward to seeing the SRU land.

In the meantime, rest assured a submission will be made upstream as soon 
as I think I've got a faint hope of it passing!

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Hirsute:
  Triaged

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * sudo add-apt-repository ppa:waveform/pi-bluetooth
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly 

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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


Re: [Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

2020-11-12 Thread Dave Jones
On Thu, Nov 12, 2020 at 11:11:23AM -, Sebastien Bacher wrote:
>Sorry but I'm reverting that upload for now until the patches are
>properly upstreamed. We have been bitten too often by unforwarded
>changes that create issues or create maintainance burden over the years
>and we currently don't have the team capacity to deal with extra cost.
>If foundations would like to step up and take over bluez though that's a
>discussion we could have...

My apologies; I omitted to note in the patch that the Pi 400 is a 
certified platform, i.e. we're effectively committed to making it work 
as best we can, which makes the status of whether upstream accept the 
patches or not rather moot:

If upstream say "yes" to the patches, without further discussion: that's 
great, but there'd presumably still be some delay before another version 
makes its way down to us, so we'd be applying *some* patch to make it 
work in the interim.

If upstream say "with these changes" to the patches: again great, but in 
the interim, we'd again be applying *some* patch to make things work on 
a certified platform while working through changes upstream.

If upstream say "not in a month of Sundays" to these patches: we'd be 
left carrying *some* patch, and we'd do it because it's a certified 
platform and we're committed to making it work.

 From our end user's perspective therefore, the application of this 
patch-set, whether via upstream or not, and whether in this form or not, 
is not a matter of "if", but "when". Given we have in our possession a 
patch-set that fixes the problem, I at least don't have a good answer to 
the hypothetical user's obvious follow-up question: "why not now?"

Anyway, onto technical matters:

>I'm not asking for the patches to be merged upstream but at least to be
>sent there for review and have the appropriate tagging, it's easy to
>unblock from your side. Also I would like to see if we can get for a
>better way to probe for the system to be ready rather than relying on a
>random sleep

The following involves a certain amount of educated guessing. I haven't 
dug into this extensively, but I can offer some reasons for why sleep(1) 
is being used (and how this could be refined a bit, but not much):

Consider the bcm43xx_load_firmware routine in hciattach_bcm43xx.c [1] 
which is being called prior to the apparently arbitrarily inserted 
sleep(1) line in the patch. It's a fairly typical firmware load routine 
by all accounts:

1. Calls write() with a command (0x2e 0xfc) to place the device into a 
state where it's read to receive new firmware

2. Calls read_hci_event() to check the device responded "okay!"

3. Calls nanosleep() to wait a short while (50ms) for the device to be 
ready

4. Calls read() and write() repeatedly to write the firmware blob from a 
file to the UART

5. Calls nanosleep() again to wait another short while (200ms) after the 
firmware load

So the existing (pre-patch) firmware load routine already has a 
seemingly arbitrary post-firmware-load delay of 200ms. If we have a look 
at the BCM4334 datasheet [2], p.159 we can see "wait at least 150ms 
after [power on] before initiating SDIO accesses" (SDIO being one of 
several interfaces for this particular module). However, that's just for 
the BCM4334. There's also the BCM4330, BCM4329, and the Cypress 305 (on 
the Pi 400, which uses the BCM43xx interface; Cypress, incidentally, 
acquired Broadcom's wireless business which explains why their chips 
suddenly have Broadcom's interfaces).

The bluez interface *could* presumably check precisely which device it 
was dealing with and adjust its post-firmware-load delay accordingly. Or 
it could simply go with a delay that's "long enough" to cover all the 
supported chipsets, and avoid all that logic (which appears to be what's 
favoured in the original code). Given it's a one-time setup delay, and 
it's likely to occur during boot-up (or system wake-up) when half a 
dozen other things are happening in parallel, it's unlikely the user 
will notice a difference between a 150ms, 200ms, or even 1.2s delay to 
their Bluetooth module becoming available.

Hence one possibility for the sleep(1) delay is that the Cypress 305, 
being a later and more feature-rich device, requires a longer delay. I 
can't confirm that as I can't find the datasheet online; sadly, this 
isn't remotely surprising, but I could reasonably assume that the Pi 
Foundation *do* have access to it and thus the 1 second delay isn't 
*entirely* arbitrary.

In some of the BCM43xx modules it does appear that the UART CTS line is 
asserted to indicate the device is "ready" (e.g. the BCM4330 datasheet 
mentions this under the Bluetooth PMU section). However, one of the 
configurations (not the default, but a supported configuration 
nonetheless) for the Bluetooth module on all Pi models is to be operated 
via the mini-UART instead of the PL011. The mini-UART, as noted 
previously, explicitly lacks any hardware flow-control ([3], 

Re: [Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

2020-11-11 Thread Dave Jones
On Tue, Nov 10, 2020 at 03:12:30PM -, Sebastien Bacher wrote:
>Thanks for the work but it there any work to upstream those changes? I'm
>not happy to carry a sleep(1) hack in our package unless there is a
>strong reason and we are working on a way to replace it by a better
>solution

The changes come from the Pi Foundation originally (though I've tidied 
them up a tiny bit). They're not interested in upstreaming them 
themselves, though they expressed no objections to my attempting to do 
so when I raised the question.

I realize I'll probably have a bit of a battle on my hands with 
something like the patch involving sleep(1), but I would note that the 
sleep(1) hack is in the hciattach_bcm43xx module so it is not something 
that would be applied to every single Bluetooth module, only to those 
compatible with the BCM43xx line.

While 1 second is obviously a suspiciously round number for the delay, I 
would further note that it's immediately after a firmware load over the 
controlling UART and that that UART can (in certain configurations) be 
the Pi's mini-UART which has some (minimal) buffering, but lacks any 
hardware flow control. Finally, these patches were also intended to work 
on the relatively slow, single core Pi Zero.

Obviously we don't support the Zero, and thus it's possible *we* might
be able to either do away with that sleep, or at least reduce the delay 
required, but given this is one-off initialization, and the delay is all 
of 1 second, I'm not convinced it's worth investing the time required to 
figure out the minimum. Also, I would assume in the interests of 
upstreaming the patch, the delay should be as widely applicable as 
possible.

Anyway, I'll upstream what I can and we'll have to carry whatever's left 
over.

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * sudo add-apt-repository ppa:waveform/pi-bluetooth
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly 

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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


[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

2020-11-10 Thread Dave Jones
** Description changed:

+ [Impact]
+ 
+ Without these patches, Bluetooth is inoperable on the recently released
+ Raspberry Pi 400.
+ 
+ [Test Case]
+ 
+ * Boot the Ubuntu Desktop for Pi image on a Pi 400.
+ * Start the Settings application and switch to the Bluetooth tab
+ * Verify that Bluetooth is not enabled and attempting to activate it fails
+ * sudo add-apt-repository ppa:waveform/pi-bluetooth
+ * sudo apt update
+ * sudo apt install bluez
+ * sudo reboot
+ * Start the Settings application and switch to the Bluetooth tab
+ * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly 
+ 
+ [Regression Potential]
+ 
+ Extremely low (on groovy in particular, this has the same version of
+ bluez as hirsute). The only significant risk is to non-Pi platforms or
+ dongles which also use the Broadcom 43xx (or Cypress 305) chips for
+ Bluetooth which might be inadvertently affected by these patches.
+ 
+ [Original Description]
+ 
  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst
  wifi works happily, Bluetooth fails to operate. This doesn't appear to
  be an issue with either the firmware (the latest versions from upstream
  Raspbian have been tried), or the kernel (a known-good raspi kernel has
  been tested under Ubuntu), but with Bluez itself. Specifically, tracing
  the initialization with btmon on Raspbian and Ubuntu, the stack
  consistently fails when attempting to "Set Default PHY" on the latter.
  Curiously, under Ubuntu the adapter also appears to lack a MAC address.

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * sudo add-apt-repository ppa:waveform/pi-bluetooth
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly 

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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


[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

2020-11-10 Thread Dave Jones
** Summary changed:

- Bluetooth won't activate on the pi 400
+ [SRU] Bluetooth won't activate on the pi 400

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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


[Touch-packages] [Bug 1903614] Re: Please merge kbd 2.3.0-3 from Debian unstable

2020-11-09 Thread Dave Jones
Ooops - left a redundant file in the diff; revised patch attached below

** Patch added: "2-2.3.0-3ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1903614/+attachment/5432819/+files/2-2.3.0-3ubuntu1.debdiff

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

Title:
  Please merge kbd 2.3.0-3 from Debian unstable

Status in kbd package in Ubuntu:
  New

Bug description:
  Please merge kbd 2.3.0-3 from Debian unstable.

  Updated changelog and diff against Debian unstable is attached below.
  Test build available from
  https://launchpad.net/~waveform/+archive/ubuntu/kbd/+packages

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

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


[Touch-packages] [Bug 1903614] [NEW] Please merge kbd 2.3.0-3 from Debian unstable

2020-11-09 Thread Dave Jones
Public bug reported:

Please merge kbd 2.3.0-3 from Debian unstable.

Updated changelog and diff against Debian unstable is attached below.
Test build available from
https://launchpad.net/~waveform/+archive/ubuntu/kbd/+packages

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

** Patch added: "1-2.3.0-3ubuntu1.debdiff"
   
https://bugs.launchpad.net/bugs/1903614/+attachment/5432816/+files/1-2.3.0-3ubuntu1.debdiff

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

Title:
  Please merge kbd 2.3.0-3 from Debian unstable

Status in kbd package in Ubuntu:
  New

Bug description:
  Please merge kbd 2.3.0-3 from Debian unstable.

  Updated changelog and diff against Debian unstable is attached below.
  Test build available from
  https://launchpad.net/~waveform/+archive/ubuntu/kbd/+packages

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

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


[Touch-packages] [Bug 789196] Re: resizecons missing

2020-11-09 Thread Dave Jones
This was fixed by the merge from debian back in yakkety

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

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

Title:
  resizecons missing

Status in kbd package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: kbd

  The manual page for resizecons is included in this package but not the
  utility itself.

  dpkg --listfiles kbd | fgrep -i resize
  /usr/share/man/man8/resizecons.8.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: kbd 1.15-1ubuntu5
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  CheckboxSubmission: 1e1a99f31ec2933306456e1f141c45d8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Fri May 27 11:58:37 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: kbd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4

2020-11-06 Thread Dave Jones
@Daniel could you try out the bluez package from the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/pi-bluetooth/+packages ?

Should be as simple as doing:

  sudo add-apt-repository ppa:waveform/pi-bluetooth
  sudo apt update
  sudo apt upgrade

The version in that PPA contains the pi foundation's patches to bluez
which were necessary to enable bluetooth on the pi400 (LP: #1903048),
but they also alter some of the general initialization of the bluetooth
module on all pis (amongst other things). A (slightly tidied up) variant
of this is currently intended for hirsute, to be SRU'd to groovy and
focal, so I'd be interested to hear if it also fixes this issue.

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

Title:
  Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on
  Raspberry Pi 4

Status in bluez package in Ubuntu:
  Incomplete
Status in linux-raspi package in Ubuntu:
  Incomplete
Status in pi-bluetooth package in Ubuntu:
  Confirmed
Status in bluez source package in Groovy:
  Incomplete
Status in linux-raspi source package in Groovy:
  Incomplete
Status in pi-bluetooth source package in Groovy:
  New

Bug description:
  Raspberry pi 4 4Gb ram
  Ubuntu desktop 20.10 64 bit
  After reboot no Bluetooth devices connect, scanning Bluetooth devices works, 
results with same device name (duplicated and with not set up status).
  Sometimes after several reboots it works.
  If I use power off and cycle power then it works fine each time.

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

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


[Touch-packages] [Bug 1903048] Re: Bluetooth won't activate on the pi 400

2020-11-06 Thread Dave Jones
@henry-sprog yup, that looks like the same

Attached a patch to fix this in hirsute; once landed will SRU this to
groovy and earlier.

** Patch added: "lp1903048.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+attachment/5431962/+files/lp1903048.debdiff

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

Title:
  Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  New

Bug description:
  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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


[Touch-packages] [Bug 1903048] [NEW] Bluetooth won't activate on the pi 400

2020-11-05 Thread Dave Jones
Public bug reported:

The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst
wifi works happily, Bluetooth fails to operate. This doesn't appear to
be an issue with either the firmware (the latest versions from upstream
Raspbian have been tried), or the kernel (a known-good raspi kernel has
been tested under Ubuntu), but with Bluez itself. Specifically, tracing
the initialization with btmon on Raspbian and Ubuntu, the stack
consistently fails when attempting to "Set Default PHY" on the latter.
Curiously, under Ubuntu the adapter also appears to lack a MAC address.

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Assignee: Dave Jones (waveform)
 Status: New

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

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

Title:
  Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  New

Bug description:
  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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


[Touch-packages] [Bug 1899953] Re: Crackling audio on Raspberry Pi Desktop

2020-10-21 Thread Dave Jones
Hmm, this looks like someone reported exactly this about a year ago:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/762

Unfortunately it's closed with "approach the driver maintainer".

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #762
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/762

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

Title:
  Crackling audio on Raspberry Pi Desktop

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Attempting to play audio (e.g. from rhythmbox) on the raspberry pi
  desktop image, results in broken up / crackling audio. The "tsched=0"
  workaround noted in
  
https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling
  successfully avoids the issue.

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

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


[Touch-packages] [Bug 1899962] [NEW] Wrong audio output device selected on Raspberry Pi Desktop

2020-10-15 Thread Dave Jones
Public bug reported:

On each boot, an incorrect audio output device is selected, at least
when HDMI audio output is in use (still need to test the TV/aux output;
will update the bug when done).

Specifically, the settings application lists "Multichannel Output -
Built-in Audio" as the selected output device. However, for audio to
play through the connected HDMI device, "Analog Output - Built-in Audio"
must be selected instead. Unfortunately, this setting will be lost on
subsequent boots. A workaround is to remove the following lines from
/etc/pulse/default.pa:

### Use hot-plugged devices like Bluetooth or USB automatically (LP: 
#1702794)
.ifexists module-switch-on-connect.so
load-module module-switch-on-connect
.endif

However, removal of these lines will (as the comment suggests) result in
hot-plugged USB devices *not* being automatically selected.

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

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

Title:
  Wrong audio output device selected on Raspberry Pi Desktop

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On each boot, an incorrect audio output device is selected, at least
  when HDMI audio output is in use (still need to test the TV/aux
  output; will update the bug when done).

  Specifically, the settings application lists "Multichannel Output -
  Built-in Audio" as the selected output device. However, for audio to
  play through the connected HDMI device, "Analog Output - Built-in
  Audio" must be selected instead. Unfortunately, this setting will be
  lost on subsequent boots. A workaround is to remove the following
  lines from /etc/pulse/default.pa:

  ### Use hot-plugged devices like Bluetooth or USB automatically (LP: 
#1702794)
  .ifexists module-switch-on-connect.so
  load-module module-switch-on-connect
  .endif

  However, removal of these lines will (as the comment suggests) result
  in hot-plugged USB devices *not* being automatically selected.

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

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


[Touch-packages] [Bug 1899953] [NEW] Crackling audio on Raspberry Pi Desktop

2020-10-15 Thread Dave Jones
Public bug reported:

Attempting to play audio (e.g. from rhythmbox) on the raspberry pi
desktop image, results in broken up / crackling audio. The "tsched=0"
workaround noted in
https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling
successfully avoids the issue.

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

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

Title:
  Crackling audio on Raspberry Pi Desktop

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Attempting to play audio (e.g. from rhythmbox) on the raspberry pi
  desktop image, results in broken up / crackling audio. The "tsched=0"
  workaround noted in
  
https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling
  successfully avoids the issue.

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

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


[Touch-packages] [Bug 1891316] Re: duplicate "progname" under gcc-10

2020-08-12 Thread Dave Jones
** Description changed:

  Under gcc-10's linker an error occurs wherein "progname" appears to be
  included from multiple locations (as it's defined in version.h rather
  than merely declared).
+ 
+ A trivial patch is available from the following branch:
+ 
+ https://code.launchpad.net/~waveform/ubuntu/+source/kbd/+git/kbd/+ref
+ /fix-duplicate-progname
+ 
+ With test builds in the following PPA:
+ 
+ https://launchpad.net/~waveform/+archive/ubuntu/kbd

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

Title:
  duplicate "progname" under gcc-10

Status in kbd package in Ubuntu:
  New

Bug description:
  Under gcc-10's linker an error occurs wherein "progname" appears to be
  included from multiple locations (as it's defined in version.h rather
  than merely declared).

  A trivial patch is available from the following branch:

  https://code.launchpad.net/~waveform/ubuntu/+source/kbd/+git/kbd/+ref
  /fix-duplicate-progname

  With test builds in the following PPA:

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

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

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


[Touch-packages] [Bug 1891316] [NEW] duplicate "progname" under gcc-10

2020-08-12 Thread Dave Jones
Public bug reported:

Under gcc-10's linker an error occurs wherein "progname" appears to be
included from multiple locations (as it's defined in version.h rather
than merely declared).

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

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

Title:
  duplicate "progname" under gcc-10

Status in kbd package in Ubuntu:
  New

Bug description:
  Under gcc-10's linker an error occurs wherein "progname" appears to be
  included from multiple locations (as it's defined in version.h rather
  than merely declared).

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

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


[Touch-packages] [Bug 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines

2020-06-04 Thread Dave Jones
All regressions now cleared after a re-run (thanks!), and verifications
done.

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

Title:
  [SRU] apt-add-repository adds duplicate commented/disabled source
  lines

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Committed
Status in python-apt source package in Bionic:
  Fix Committed
Status in python-apt source package in Eoan:
  Fix Committed

Bug description:
  Impact
  ==

  Under most circumstances, the impact is minimal (a few extra redundant
  comment lines in apt sources. However, if users are automating source
  removal / addition on a machine (as in comment 11), there is the
  potential to wind up with an excessively large (and thus slow to
  parse) apt sources configuration.

  Test packages for the supported releases are available from the
  following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/python-apt

  Built from the source which can be found in the following branches:

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-xenial

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-bionic

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-eoan

  Test Case
  =

  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the presence of one uncommented "deb" line, and one commented 
"deb-src" line
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the uncommented "deb" line is still there but the commented "deb-src" 
line has now been duplicated
  * sudo add-apt-repository ppa:waveform/python-apt
  * sudo apt upgrade  # update python-apt to fixed version
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note there has been no further duplication of the commented "deb-src" line

  Regression Potential
  

  Minimal; test cases have been added to cover the duplication case, and
  to cover the enabling of sources (which was not covered by existing
  tests, but was part of the code altered to fix the duplication case),
  and insertion of sources at a position (again, not covered by existing
  tests but modified as part of the fix). The test case has been used
  successfully on all targeted releases (xenial, bionic, and eoan).

  Original Description
  

  Trusty Tahr 14.04

  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list
  deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y 
ppa:aims/aims-desktop
  gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created
  gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created
  gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created
  gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb 
http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#

  That deb-src line should have stayed commented out, and not been
  duplicated. (Commented deb lines should of course be uncommented, as
  already fixed per https://bugs.launchpad.net/ubuntu/+source/python-
  apt/+bug/1042916 .)

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

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


[Touch-packages] [Bug 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines

2020-05-28 Thread Dave Jones
Successfully verified fixes on xenial, bionic, and eoan. The autopkgtest
regressions on xenial were due to flaky tests on i386 and armhf; these
have been re-run successfully. The regressions on bionic look like a
transient network failure (would be grateful if someone could attempt a
re-run on those). The same is true of one of the regressions on eoan;
the other *may* be (would be grateful if someone could attempt a re-run
of those too).

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

Title:
  [SRU] apt-add-repository adds duplicate commented/disabled source
  lines

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Committed
Status in python-apt source package in Bionic:
  Fix Committed
Status in python-apt source package in Eoan:
  Fix Committed

Bug description:
  Impact
  ==

  Under most circumstances, the impact is minimal (a few extra redundant
  comment lines in apt sources. However, if users are automating source
  removal / addition on a machine (as in comment 11), there is the
  potential to wind up with an excessively large (and thus slow to
  parse) apt sources configuration.

  Test packages for the supported releases are available from the
  following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/python-apt

  Built from the source which can be found in the following branches:

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-xenial

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-bionic

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-eoan

  Test Case
  =

  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the presence of one uncommented "deb" line, and one commented 
"deb-src" line
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the uncommented "deb" line is still there but the commented "deb-src" 
line has now been duplicated
  * sudo add-apt-repository ppa:waveform/python-apt
  * sudo apt upgrade  # update python-apt to fixed version
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note there has been no further duplication of the commented "deb-src" line

  Regression Potential
  

  Minimal; test cases have been added to cover the duplication case, and
  to cover the enabling of sources (which was not covered by existing
  tests, but was part of the code altered to fix the duplication case),
  and insertion of sources at a position (again, not covered by existing
  tests but modified as part of the fix). The test case has been used
  successfully on all targeted releases (xenial, bionic, and eoan).

  Original Description
  

  Trusty Tahr 14.04

  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list
  deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y 
ppa:aims/aims-desktop
  gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created
  gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created
  gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created
  gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb 
http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#

  That deb-src line should have stayed commented out, and not been
  duplicated. (Commented deb lines should of course be uncommented, as
  already fixed per https://bugs.launchpad.net/ubuntu/+source/python-
  apt/+bug/1042916 .)

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

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


  1   2   >