Public bug reported:
Summary
=======
After upgrading to Kubuntu 24.04, my Epson ET-2750 network printer
became unreliable when configured automatically via DNS-SD/mDNS (.local
hostname).
The printer is discovered correctly, but print jobs often remain queued
because the hostname cannot be resolved. Configuring the printer
manually using its fixed IPv4 address completely solves the problem.
System
======
Distribution:
Kubuntu 24.04 LTS
Printer:
Epson ET-2750 (WiFi)
The printer has a fixed DHCP lease in the FRITZ!Box router.
Problem
=======
The printer was originally added automatically via KDE's printer
configuration.
CUPS configured the printer with:
ipps://EPSON639DA7.local:631/ipp/print
Printing worked for a long time but recently became unreliable.
Typical symptoms:
- Print jobs remain in the queue.
- Sometimes they print immediately after rebooting the computer.
- Sometimes they never print.
- CUPS reports:
"The printer 'EPSON639DA7.local' could not be located."
Investigation
=============
The printer itself is fully reachable:
ping 192.168.178.39
works without packet loss.
Direct IPP communication also works correctly:
ipptool -tv ipp://192.168.178.39/ipp/print get-printer-
attributes.test
returns:
Get printer attributes using get-printer-attributes [PASS]
Therefore IPP communication with the printer is working correctly.
The interesting part is the DNS-SD/mDNS behaviour.
Service discovery works:
avahi-browse -at
shows:
EPSON ET-2750 Series
Internet Printer
Secure Internet Printer
PDL Printer
Scanner
...
However resolving the discovered service fails:
avahi-browse -rt _ipps._tcp
returns:
Error resolving service 'EPSON ET-2750 Series':
Timeout reached
The hostname itself cannot be resolved either:
avahi-resolve-host-name EPSON639DA7.local
returns:
Timeout reached
and
ping EPSON639DA7.local
returns:
Name or service not known
while
lpinfo -v
still reports:
dnssd://EPSON%20ET-2750%20Series._ipp._tcp.local/?uuid=...
Workaround
==========
Deleting the automatically created printer and creating a new printer
manually using
ipp://192.168.178.39/ipp/print
(with the Epson ESC/P-R driver)
completely solves the problem.
Printing is now immediate and reliable.
Additional information
======================
During the investigation the following was observed:
- cups.service is running normally.
- avahi-daemon is running normally.
- The printer is discovered via avahi-browse.
- Service resolution times out.
- Direct IPP communication by IPv4 address works correctly.
This suggests that the issue is related to DNS-SD/mDNS service
resolution rather than IPP printing itself.
I am not sure whether the problem belongs to avahi, cups, systemd-
resolved or an interoperability issue with the printer firmware, but I
hope these observations help identifying the correct component.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: avahi-daemon 0.8-13ubuntu6.2
ProcVersionSignature: Ubuntu 6.8.0-134.134-generic 6.8.12
Uname: Linux 6.8.0-134-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Jul 12 11:44:52 2026
InstallationDate: Installed on 2024-12-26 (563 days ago)
InstallationMedia: Kubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827)
SourcePackage: avahi
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: avahi (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2160445
Title:
avahi-browse discovers IPP printer but resolve always times out
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/2160445/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
