SUMMARY A problem occurs about the ability of a client to get the printer linked to a different router linked to another router by WDS, The printer is not detected if not via personal activity which allows to install the driver by PPD file and to give the IP address of the printer, if both the client and the printer are linked to the same router the printer is visible and detected and immediately available to be used. The printer is sometimes visible because of unknown causes probably due to some kind of upgrade of cups packages, but I am not sure about this. STEPS TO REPRODUCE 1. link a wifi printer to the router linked by wds to another router 2. try for the lan printer 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
I'm afraid this is out of scope of networkmanager-qt, which is a library for NetworkManager. I think this should be reported to print-manager where someone who understands printers can help you.
*** Bug 407996 has been marked as a duplicate of this bug. ***
It should work via brl2710.ppd driver provided in Ubuntu 20.04.
(In reply to Jan Grulich from comment #1) > I'm afraid this is out of scope of networkmanager-qt, which is a library for > NetworkManager. I think this should be reported to print-manager where > someone who understands printers can help you. this problem deals with drivers and or with the networking stack. Who are the developers involved on this software?
(In reply to Kai Uwe Broulik from comment #2) > *** Bug 407996 has been marked as a duplicate of this bug. *** the issue appears to be fixed though the firewall prevents the wifi printer linked to the secondary router to be detected when it is enabled.
Please report if you can see the printer with avahi-browse -a
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!