Public bug reported:
I have a HP OfficeJet 9022e network printer which worked flawlessly
until recently. Today I found out that I am no longer able to print on
it from both my Xubuntu PCs. I removed the printer and I tried to add it
again but this also did not work. Regardless of the way I tried adding
it (GUI / command line / CUPS web interface), the printer either could
not be added or could not be printed to. During further research I
narrowed the problem down :
Entering this command:
driverless
...produces the following correct output:
ipp://BonjourHPOfficeJetPro9022e._ipp._tcp.local/
However, subsequently entering this command:
avahi-resolve -n ipp://BonjourHPOfficeJetPro9022e._ipp._tcp.local/
...produces this error:
Failed to resolve host name
'ipp://BonjourHPOfficeJetPro9022e._ipp._tcp.local/': DNS failure:
NXDOMAIN
Manually adding the printer by its IP address (currently 192.168.69.245)
worked flawlessly.
Scanning from the printer using simple-scan still worked flawlessly, as
it did before. In simple-scan, the printer shows as "ESCL
BonjourHPOfficeJetPro9022e".
What I did between the time the printer worked flawlessly and today:
* I updated both my PCs to the latest XUbuntu LTS version (20.04.1)
* I updated, factory reset and reconfigured my home router (Turris Omnia).
However, the IP address range is the same as before (192.168.69.xxx) and the IP
address of the printer is still assigned dynamically, the same way as it was
before (when the printer worked)
SOLUTION: After several hours I found the following solution of the
problem:
In the /etc/nsswitch.conf file, I had to change the line beginning with
"hosts: files" to this:
hosts: files mymachines mdns4_minimal [NOTFOUND=return] resolve
[!UNAVAIL=return] dns mdns4 myhostname
This line originally looked like this:
hosts: files mdns4_minimal [NOTFOUND=return] dns
Then, I had to create the (non-existent) file /etc/mdns.allow with these
2 lines:
.local.
.local
Then I restarted the avahi-daemon service and printing works flawlessly
again.
Note that until today, I had no idea that /etc/nsswitch.conf file exists
and that avahi-daemon service somehow relates to printing. I have no
idea why this solution works and whether it's the best solution, but it
was the first workable solution I found after 4 hours of Googling.
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959850
Title:
Network printer suddenly stopped working, cannot be accessed using
zeroconf anymore
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1959850/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
