Comment 1 for bug 1893491

I suspect this was down to one of the newer revisions of the Pi board (the rev 1.4 4B?) appearing during the cycle.

This was fixed at some point during the Groovy release though, firstly by adding the explicit "rev 1.4" entry, and later by adding the "Raspberry Pi *" wildcard entry (in 3.100ubuntu3). I'll set this to "Fix Released" but if you're still having the issue, please do set it back to "New" and I'll dig into it.