chooser trigger detection does not work on RPi

Bug #1870212 reported by Dimitri John Ledkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

# /usr/lib/snapd/snap-bootstrap recovery-chooser-trigger
1970/01/01 00:00:11.047894 cmd_recovery_chooser_trigger.go:80: trigger timeout 10s
1970/01/01 00:00:11.047999 cmd_recovery_chooser_trigger.go:81: marker file /run/snapd-recovery-chooser-triggered
error: cannot find matching devices
# echo $?
1

this is on rpi

Tags: arm64 core20 uc20
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Should I neutralize chooser on arm64 / RPi?

Revision history for this message
Maciej Borzecki (maciek-borzecki) wrote :

Does it block the boot in initramfs?

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

mborzecki> xnox: it's listing /dev/input/* to find ine that generates our trigger event

let me find out, how come that is empty.

Changed in snapd (Ubuntu):
status: New → Incomplete
Changed in snapd (Ubuntu):
status: Incomplete → Confirmed
summary: - chooser fails on RPi
+ chooser trigger detection does not work on RPi
Revision history for this message
Maciej Borzecki (maciek-borzecki) wrote :

I've opened https://github.com/snapcore/snapd/pull/8490 so that recovery trigger detection will no longer fail when no matching input devices are present.

Michael Vogt (mvo)
Changed in snapd (Ubuntu):
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.