When adding a 'Discovered network printer' within the 'Add a New Printer' dialog, the connection drop-down box ( to choose which printer to add - see dropdown in snapshot1.png attached ) only shows the URI , which isn't particularly human friendly. Ideally the drop-down would show the display name of the printer ( as the CUPS web interface does - see snapshot2.png attached ). Reproducible: Always Steps to Reproduce: 1. Open System Settings 2. Select 'Printers' 3. Select 'Add Printer' 4. Select an item under the 'Discovered Network Printers' sub-item in the multi-select box on the left side of the window. Actual Results: Dropdown on right contains list of URIs, which are not easily understable as to which URI relates to which printer Expected Results: Dropdown on right contains list of printer names For context; I'm the author of a program called 'CUPS Cloud Print' ( https://github.com/simoncadman/CUPS-Cloud-Print ) and am looking to improve the user experience when adding cloud printers under KDE, fixing this issue should do this. Thanks
Created attachment 87070 [details] Screenshot showing dropdown within KDE with URIs
Created attachment 87071 [details] Screenshot showing same functionality within CUPS web interface, but showing display names of printers instead of URIs
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Can you try this in Plasma6?
We believe that Plasma6 resolves this issue. Can you try with Plasma6 and report back?
Yes seems to be fixed, thanks!