You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During system shutdown, CUPS logs the following error:
Unable to communicate with avahi-daemon: An unexpected D-Bus error occured
Shortly after that, cupsd calls avahi_client_free() with a NULL DNSSDClient pointer and immediately terminates with SIGABRT.
According to the systemd journal, "Avahi mDNS/DNS-SD Stack" is stopped before "CUPS Scheduler". My guess is that DNSSDClient is freed and set to NULL by dnssdClientCallback() following the termination of the Avahi daemon.
A simple solution would be to check if DNSSDClient is NULL before calling avahi_client_free() in dnssdStop(). Either a (DNSSDClient != NULL) or (avahi_running == 1) condition should suffice.
I'm using Arch Linux on x86_64 with the following software:
cups 2.0.1
systemd 218
avahi 0.6.31
The text was updated successfully, but these errors were encountered:
Version: 2.0.1
CUPS.org User: foutrelis
During system shutdown, CUPS logs the following error:
Shortly after that, cupsd calls avahi_client_free() with a NULL DNSSDClient pointer and immediately terminates with SIGABRT.
According to the systemd journal, "Avahi mDNS/DNS-SD Stack" is stopped before "CUPS Scheduler". My guess is that DNSSDClient is freed and set to NULL by dnssdClientCallback() following the termination of the Avahi daemon.
A simple solution would be to check if DNSSDClient is NULL before calling avahi_client_free() in dnssdStop(). Either a (DNSSDClient != NULL) or (avahi_running == 1) condition should suffice.
I'm using Arch Linux on x86_64 with the following software:
The text was updated successfully, but these errors were encountered: