USB serial devices not available in /dev/serial/by-id/ after upgrade

[Christopher Conroy]

it looks like systemd-udevd is crashing with the following error:

-- Boot a74cfdb7e237433f9321d32ebe70e086 --
Oct 23 13:28:50 Himari systemd-udevd[931]: /usr/lib/udev/rules.d/90-pi-bluetooth.rules:14 Invalid value "/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if cmp -s $ALIASES/uart0 $ALIASES/serial0; then echo 0;elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then echo 1; else exit 1; fi'" for PROGRAM (char 58: invalid substitution type), ignoring, but please fix it.
Oct 23 13:28:50 Himari systemd-udevd[931]: /usr/lib/udev/rules.d/90-pi-bluetooth.rules:27 Invalid value "/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if [ -e /dev/ttyAMA0 ]; then exit 1; elif cmp -s $ALIASES/uart0 $ALIASES/serial0; then echo 0;elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then echo 1; else exit 1; fi'" for PROGRAM (char 97: invalid substitution type), ignoring, but please fix it.
Oct 23 13:28:50 Himari systemd-udevd[931]: /usr/lib/udev/rules.d/90-pi-bluetooth.rules:38 Invalid value "/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if cmp -s $ALIASES/uart1 $ALIASES/serial0; then echo 0; elif cmp -s $ALIASES/uart1 $ALIASES/serial1; then echo 1; else exit 1; fi '" for PROGRAM (char 58: invalid substitution type), ignoring, but please fix it.

I'm not sure if this is related, or a red herring.

this is on a raspberry pi 4b 2GB that was recently upgraded from 21.04 to 21.10

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: udev 248.3-1ubuntu8
ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14
Uname: Linux 5.13.0-1008-raspi aarch64
ApportVersion: 2.20.11-0ubuntu70
Architecture: arm64
CasperMD5CheckResult: unknown
CustomUdevRuleFiles: 70-snap.snapd.rules 70-snap.mjpg-streamer.rules
Date: Sat Oct 23 13:31:46 2021
ImageMediaBuild: 20210421.1
Lspci-vt: -[0000:00]---00.0-[01]----00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller
Lsusb:
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1d50:614e OpenMoko, Inc. lpc1769
 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcEnviron:
 SHELL=/bin/bash
 LANG=C.UTF-8
 TERM=xterm
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:7C:E6:E5 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
SourcePackage: systemd
UpgradeStatus: Upgraded to impish on 2021-10-17 (6 days ago)
acpidump:

[Christopher Conroy (cbc02009)]

just to clarify, before the upgrade I had /dev/ttyACM0 and a corresponding entry in /dev/serial/by-id/ for it.

I've verified that a fresh image of 20.04 LTS with the same device attached does not exhibit the same issue, and the device shows up as expected.

[Dan Streetman (ddstreet)]

> /usr/lib/udev/rules.d/90-pi-bluetooth.rules:14 Invalid value ...

rules provided by pi-bluetooth package, not systemd.

[Christopher Conroy (cbc02009)]

Sorry, turns out this is most likely a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947723 and the messages from the pi-bluetooth package are unrelated.