Public bug reported:
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.
** Affects: fprintd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fprintd in Ubuntu.
https://bugs.launchpad.net/bugs/1975660
Title:
Disabling fprintd.service prevents boot
Status in fprintd package in Ubuntu:
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1975660/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
