Forum › Forums › Official Releases › antiX-21/22 “Grup Yorum” › [solved] CUPS server error when adding new printer
- This topic has 46 replies, 11 voices, and was last updated Sep 21-5:49 pm by caprea.
-
AuthorPosts
-
January 21, 2022 at 1:32 am #75673
afghanMemberPossibly. But I would be very surprised if this were the case.
You could test by removing all of cups on your antiX install, remove (temporarily) nosystemd from antix.list in apt sources, apt update and install cups from Debian repo.It was just pure speculation on my part; hoping it triggers some ideas from ppl who know far more than I do about the internals of these things. I’ll give it a go over the weekend to see what happens.
Could this be a wifi problem?
Can you connect the printers by ethernet to see if they work without PASSTHRU?
I doubt it’s the wifi. It works fine on my wife’s notebook running Debian Bullseye. I’ve been removing and adding printers without problems on it. It’s just on my notebook that’s running a new install of antiX 21 that showing this problem. I’ll try your lan cable suggestion a try to see what happens; over the weekend.
Thanks for the suggestions.
- This reply was modified 4 years, 8 months ago by afghan.
- This reply was modified 4 years, 8 months ago by afghan.
- This reply was modified 4 years, 8 months ago by afghan.
Beware of people who knows nothing; they are the ones that won't know that they know nothing.
January 22, 2022 at 5:07 am #75770
afghanMemberFinally found the problem! After a sleepless night of troubleshooting and tracing debug messages of system-config-printer. Somehow the base config of antiX 21 allows network printers to be discovered, but when actually adding the printer (i.e. actually polling the discovered printer to configure the appropriate driver ppd) it fails. All it needed was libnss-mdns. This provides the NSS functionality to resolve the printer in the .local domain. It is epecially required for certain printer models that configures driverless ppds on the fly. This may explain why it works for some people (having different printers) and not for me. I started to suspect something along this line when I manually added an old model of Epson ppd and it actually added the printer and printed a test page (more of garbage printing because of driver mismatch).
It worked on the Debian Bullseye system because libnss-mdns was installed.
Now everything works as normal after installing libnss-mdns. Admins should consider having libnss-mdns installed by default for new installs.
I shall call this problem solved! (btw how does one mark this topic as solved so that others reading are aware?)
Beware of people who knows nothing; they are the ones that won't know that they know nothing.
January 22, 2022 at 12:04 pm #75799
anticapitalistaForum AdminThanks for finding the solution.
I’ll make sure future antiX-base versions include libnss-mdns.
Marked post as solved.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
January 22, 2022 at 2:59 pm #75823olsztyn
MemberSomehow the base config of antiX 21 allows network printers to be discovered, but when actually adding the printer (i.e. actually polling the discovered printer to configure the appropriate driver ppd) it fails. All it needed was libnss-mdns. This provides the NSS functionality to resolve the printer in the .local domain. It is epecially required for certain printer models that configures driverless ppds on the fly.
Thank you afghan for this discovery…
Although I did not have any issue with my printers I want my system to be complete in such critical function. I am running antiX 21 runit Full and just checked – libnss-mdns is also missing in antiX Full version, not just Base. So I am adding libnss-mdns to my antiX instances as well.
Thanks and Regards…Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersJanuary 26, 2022 at 9:27 am #76132ModdIt
MemberThanks afghan,
This may mean no mean no more need for USB connection in a couple of stubborn cases.
Also added to full antiX 21 for passing on to users, for all students and school kids printing is critical.June 3, 2022 at 7:11 am #84039
seriousnessMemberI always thought it was one of antiX’ limitations, that I cannot access my network printer via DNS-SD – thanks for figuring that out, afghan!
June 3, 2022 at 7:29 pm #84075greevous
Member… Can anyone try adding a printer on their antiX 21 system and see if you get the error?..
Today I installed a network printer (HP Deskjet 3050, wifi) in antiX 21. system-config-printer requested a username and password, after that the printer appeared in the list as a network printer. No errors. libnss-mdns is not installed.
- This reply was modified 4 years, 3 months ago by greevous.
July 31, 2023 at 12:43 pm #113209
seriousnessMemberToday I found that I am no longer able to print to my brother HL-2250DN via DNS-SD connection.
The cause: avahi-daemon is not running.
When I looked for the init script, I found /etc/init.d/avahi-daemon.dpkg-remove
Obviously support for System-V init was dropped from the package avahi-daemon.
Since the lpd connection works, this is not a big problem, but it would be nice to get avahi-daemon
started on boot again.- This reply was modified 3 years, 1 month ago by seriousness.
September 18, 2023 at 7:42 pm #117137
seriousnessMemberI just noticed two new threads dealing with this problem…
Since the init script was dropped by Debian, it should be provided by antiX.
My workaround was to copy avahi-daemon.dpkg-remove to avahi-daemon .
To get it started on boot, I ran
sudo update-rc.d avahi-daemon defaults- This reply was modified 3 years ago by seriousness.
September 18, 2023 at 7:47 pm #117139
anticapitalistaForum AdminNext set of upgrades will include the dropped by Debian sysVinit script.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
September 20, 2023 at 1:08 pm #117261
capreaModeratorTrying to upgrade avahi-daemon on antiX21 the following errors occured today
The whole libavahi got upgraded to 0.8-9.0antix2 but not avahi-daemon, which is still 0.8-9.0antix1Posting it it was kicked by forum software so I uploaded a file
- This reply was modified 3 years ago by caprea.
Attachments:
September 20, 2023 at 1:22 pm #117267
capreaModeratorOn antiX23 the upgrade of avahi-daemon went through without problems, on antiX21 see above post.
September 20, 2023 at 1:23 pm #117268
anticapitalistaForum Admin@caprea
What if you remove all of avahi and then sudo apt install avahi-daemon
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
September 20, 2023 at 1:38 pm #117271
capreaModeratorRemoving eg libavahi-client3 or libavahi-common3 wants to remove a lot, like antix-goodies,arandr etc
September 20, 2023 at 2:12 pm #117273
anticapitalistaForum AdminIs this better?
sudo apt purge avahi-daemon
sudo apt install avahi-daemonPhilosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
-
AuthorPosts
- You must be logged in to reply to this topic.