Disabling fprintd.service prevents boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fprintd (Ubuntu) |
New
|
Low
|
Unassigned |
Bug Description
Disabling fprintd.service prevents boot.
System: Ubuntu Desktop 22.04
Behavior: Rebooting immediately after disabling and masking fprintd.service, fails.
A series of [DEPEND] messages scroll past in tty1 early in the boot process, too quickly to read but that appear to be mount units failing for want of a dependency. Consistently, the last message to appear in tty1 is:
[ OK ] Reached Target Printer Support
Expected behavior: No disruption in boot process from the deletion of an irrelevant service for which no hardware exists.
Unfortunately, no further information is available because the machine resists booting.
- While booted to a separate partition, I deleted the symlink in /etc/systemd/system to /dev/null, but boot failed thereafter in the same way.
- I chrooted into the partition to attempt to re-enable the unit but the command failed by reason of being in a chroot environment.
- The partition's syslog has no entries containing DEPEND, probably because they occurred before rsyslog could receive input from the kernel ring buffer.
tags: | added: community-security |
information type: | Public → Public Security |
Changed in fprintd (Ubuntu): | |
status: | Confirmed → New |
Thank you for your bug report. Could you provide some details on why you disabled the service and how? And yes it's not unexpected that manually disabling system jobs might lead to issues