Question

1

Disabling fprintd.service prevents boot; How to restore boot?

rated 0 times [ 1] [ 0] / answers: 1 / hits: 513 / 1 Year ago, sun, april 23, 2023, 6:18:18

I've discovered that disabling fprintd.service prevents Ubuntu Desktop 22.04 from booting.

Specifically, a number of [DEPEND] dependency failures scroll rapidly past the screen in tty1, too fast to read but that appear to be mount units failing for want of a dependency, and the boot process stops with

[  OK  ] Reached Target Printer Support

This is in a multiboot setting, so I booted to another Ubuntu partition and deleted the symlink masking the service, at least, but the same boot hang exists.

I also tried to chroot into the partition while booted to stick, to enable the service but the command failed by reason of being in a chroot environment.

The question is, how can one get this machine to boot?

EDIT: The bug report is here.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

losbu

Add To Favorites

Follow

Total Points: 71

Total Questions: 124

Total Answers: 106

Location: Honduras

Member since Sat, Jul 24, 2021

3 Years ago

losbu questions

1 Ctrl +; no longer works after updating to Ubuntu 22.04

Mon, Jan 31, 22, 21:41, 2 Years ago

1 Unable to install CUDA on Ubuntu 22.04 WSL2

Tue, Nov 22, 22, 01:27, 1 Year ago

1 ffmpeg library libfdk-aac.so.1 absence ubuntu 22.04

Wed, Jan 25, 23, 00:28, 1 Year ago

1 4k resolution for Ubuntu 18.04

Wed, May 11, 22, 08:41, 2 Years ago

1 Why are some older versions of packages not found

Thu, May 5, 22, 09:50, 2 Years ago

View All

answered 1 Year ago ravturtl · Accepted Answer

I, frankly, don't think the reason for the system not booting is disabling or even masking fprintd.service, it doesn't have that sort of influence ... most likely something else you did.

Anyway, to re-enable it or any systemd service for the matter, please see below.

One way

systemd.mask=ServiceName.service and systemd.wants=ServiceName.service are two Kernel Command Line Arguments that can be used to respectively disable and enable systemd services during boot (runtime). These can be added as Kernel Boot Parameters to GRUB during boot.

In your case, it's good that you managed to delete the symlink masking the service file so now you can temporarily enable the service during the next boot by adding systemd.wants=fprintd.service kernel boot parameter from the GRUB menu.

Another way

Boot to recovery mode.

Drop to root shell.

Mount your root file system as read and write like so:
```
mount -o remount,rw /
```

Unmask the service like so:
```
systemctl unmask fprintd.service
```

Enable the service like so:
```
systemctl enable fprintd.service
```

Reboot your system.