Printer settings stuck on loading drivers database

[Luca Ciavatta]

1) Description: Ubuntu Artful Aardvark (development branch)
   Release: 17.10
2) ubuntu-settings:
   Installed: 17.10.17
   Candidate: 17.10.17
3) The printer configuration goes fine and I can print
4) Printer settings stuck on loading drivers database and finally no drivers list available. Only 'cancel' button active.

Note: I'm trying to configure a Brother HL-2030 connected to Network through a FritzBox 7940 router. The printer works fine both on Fedora and macOS X systems. I opened 'System Settings', then select 'Devices' > 'Printers' > 'Add a Printer'. I entered the router address and the window shows me correctly a 'JetDirect-Printer' on 192.168.178.1. I selected the printer and pressed the 'Add' button, a window 'Select Printer Driver' appears and stuck with 'Loading drivers database...'. After about 2 minutes, stopped loading and remains blank. No drivers selection is available and I can only push the 'Cancel' button.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[pumpkinbeer (d....)]

Still happening on 18.04 - slight difference - I can't get past the "Select Printer Driver" screen while "Loading drivers database..." and the swirling busy icon are up, so I don't have the printer at all.

[Pasqual Troncone (pasqualtroncone)]

Still happening on 20.04.

It get stuck while looking for drivers from database for my EPSON WF-2630.

[Sebastien Bacher (seb128)]

Thank you for your bug report, could you take a screenshot of the dialog showing the issue and add a 'journalctl -b 0' log from the session after getting the bug?

[123vier (flowrist)]

Seems to be an issue with apparmor. Here is my output of 'journalctl -b 0':

Mai 19 10:35:46 termy dbus-daemon[1076]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.1031' (uid=1000 pid=226173 comm="/usr/bin/python3 /us>
Mai 19 10:35:46 termy dbus-daemon[1076]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism'
Mai 19 10:35:46 termy audit[213753]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=213753 comm="cupsd" requested_mask="r>
Mai 19 10:35:46 termy audit[213753]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=213753 comm="cupsd" requested_mask="r>
Mai 19 10:35:46 termy audit[213753]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=213753 comm="cupsd" requested_mask="r>
Mai 19 10:35:46 termy audit[213753]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=213753 comm="cupsd" requested_mask="r>
Mai 19 10:35:46 termy audit[213753]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=213753 comm="cupsd" requested_mask="r>
Mai 19 10:35:46 termy kernel: audit: type=1400 audit(1589877346.366:10344): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=21>
Mai 19 10:35:46 termy kernel: audit: type=1400 audit(1589877346.366:10345): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=21>
Mai 19 10:35:46 termy kernel: audit: type=1400 audit(1589877346.366:10346): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=21>
Mai 19 10:35:46 termy kernel: audit: type=1400 audit(1589877346.366:10347): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=21>
Mai 19 10:35:46 termy kernel: audit: type=1400 audit(1589877346.366:10348): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=21>
Mai 19 10:35:46 termy kernel: usblp2: removed
Mai 19 10:35:46 termy kernel: usblp 1-1.1.2:1.0: usblp2: USB Bidirectional printer dev 14 if 0 alt 0 proto 2 vid 0x04F9 pid 0x018C
Mai 19 10:35:46 termy dbus-daemon[1745]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/Notifications" interface="org.gtk.Notifications" member="AddNoti>

I don't see how not being able to add a printer is of 'Low' importance though.

[Till Kamppeter (till-kamppeter)]

Seems that some of the general AppArmor rules needs to get updated.

Access to /proc/sys/kernel/random/boot_id seems to be needed now.

[Jamie Strandboge (jdstrand)]

@Till, the boot_id issue is being tracked here: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.