https://bugs.kde.org/show_bug.cgi?id=488097

--- Comment #2 from Massimiliano L <m.lince...@gmail.com> ---
Thank you for the quick feedback!

(In reply to Mike from comment #1)
> When you select Add Printer, are you prompted to authenticate?

No, I am not prompted for authentication.

> Also, do you
> have the package system-config-printer installed?

I did not, now I have. But it seems to only provide an additional GUI for the
same CUPS backend?

> Can you post the output from the command: `lpinfo -v`  (You may have to
> elevate privileges)

I get the following list:
-----------------
file cups-brf:/
network beh
network ipp
network https
network ipps
network http
direct hp
network socket
network lpd
network smb
direct hpfax
-----------------

With or without sudo (only the order is different).

> Note: The search button on "Manual Config" asks CUPS for printers at the
> host address.  If you know the printer address, you just type it in and
> choose "Continue".  If the address is just a scheme, CUPS returns local
> printers by default, which we should probably ignore as it is bit confusing.

OK, now I better understand how this works. I think part of the confusion
arises from the fact that the "address" for CUPS can either be an individual
networked printer o a CUPS host. The scroll menu with the search result appears
only if something is returned, giving the impression that otherwise the "search
button" is doing nothing. I think right now I can only add printers through
another CUPS server and not directly as network printers, though.

Note: I find a bit confusing to have "select printer" and "continue with
address" above the address field / printer list, instead of below.

> As far as the crashing, this is something unusual.  You can turn on
> debugging for the  printer manager in KDebugSettings.  Search "print" and
> enable Full Debug for kcm and libkcups.  You can than watch the log in a
> terminal with `journalctl --user -f` to help narrow down what is crashing.

I will as soon as I have the time to look again into this! In the meantime (now
that I figured out how this window is supposed to work) I would classify this
as UI/UX improvement rather than a bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to