I'm attaching a one-liner patch that calls `udevadm trigger` from the system service file instead, which is the same that the friendly-recovery upstart job does as well.
Note that there were 2 errors in the service file:
1) ExecStartPre=-/bin/udevadm settle
The path there is wrong, because udevadm is in /sbin. The attached patch solves this as well as the font issue, in one line.
2) ExecStartPre=-/bin/sh -e 'while systemctl list-jobs | grep -v friendly-recovery | grep -q running; do sleep 0.2; done'
The author there meant "sh -c", to run the command, instead of "sh -e". This is a separate issue. But since it's in the same .service file, maybe we can SRU both issues with one upload.
I suggest that this line is removed completely because it just hangs if "sh -c" is used.
I'm attaching a one-liner patch that calls `udevadm trigger` from the system service file instead, which is the same that the friendly-recovery upstart job does as well.
Note that there were 2 errors in the service file: -/bin/udevadm settle
1) ExecStartPre=
The path there is wrong, because udevadm is in /sbin. The attached patch solves this as well as the font issue, in one line.
2) ExecStartPre= -/bin/sh -e 'while systemctl list-jobs | grep -v friendly-recovery | grep -q running; do sleep 0.2; done'
The author there meant "sh -c", to run the command, instead of "sh -e". This is a separate issue. But since it's in the same .service file, maybe we can SRU both issues with one upload.
I suggest that this line is removed completely because it just hangs if "sh -c" is used.