The stack traces attached to this bug report suggest that cups-browsed crashes on shutdown, but if cups-browsed is shut down during a reboot of the machine, the apport message only appears after the machine has completed the reboot and so makes the impression that the crash happened during startup.
I have done a quick test on Focal and for me cups-browsed does not crash. So I need additional information. Please edit the /etc/cups/cups-browsed.conf file, making sure that it contains a line DebugLogging file with no "#" in the beginning. Stop cups-browsed with sudo systemctl stop cups-browsed Wait some minutes. If you get a crash now it is NOT yet covered by the debug logging. Now start cups-browsed with sudo systemctl start cups-browsed wait some minutes, run "lpstat -v" repeatedly and see when no more remote queues get discovered. If it did not crash yet, shut down cups-browsed with sudo systemctl stop cups-browsed Wait some minutes. If it did not crash yet, repeat this procedure until you get a crash. Now take the /var/log/cups/error_log file and attach it to this bug report. DO NOT compress it. ** Changed in: cups-filters (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857815 Title: cups-browsed assert failure: corrupted double-linked list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1857815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs