Re: Recommended way to manually add an undiscovered IPP printer in CUPS 3.x

Abdelrahman,

This functionality has not yet been implemented - it is part of the cups-local project (not libcups).


> On Aug 7, 2026, at 3:14 PM, AbdElRahman Khalifa <[email protected]> wrote:
> 
> Michael, Till,
> 
> I tried to reproduce the proposed per-user profile behavior for an IPP
> printer that is not discoverable through DNS-SD, but I cannot get the
> profile entries to be recognized.
> 
> I tested the proposed directives:
> 
> ```text
> Server ipp://HOST:PORT/ipp/system
> ServerName HOST:PORT
> Printer ipp://HOST:PORT/ipp/print
> ```
> 
> My environment is:
> 
> ```text
> libcups3: 3.0.3 installed under /usr/local
> also i have libcups2: 2.4.7
> cups-locald: not installed
> ```
> 
> For the test printer I used:
> 
> ```text
> ippeveprinter -p 9200 -r off
> ```
> 
> So it does not advertise itself through DNS-SD at all. Direct
> `Get-Printer-Attributes` requests work and return the printer
> correctly.
> 
> I tested both per-user profile locations:
> 
> ```text
> ~/.config/cups/profiles/
> ~/.cups/profiles/
> ```
> 
> However, `strace` shows that libcups3 never scans or opens either
> profiles directory, and `cupsEnumDests()` doesn't shows the printer.
> 
> So currently I cannot reproduce the intended flow:
> 
> ```text
> profile file
>    |
>    v
> cupslocald/libcups reads it
>    |
>    v
> cupsEnumDests()
>    |
>    v
> printer appears
> ```
> 
> Is `cups-locald` currently required for profiles to work?
> 
> And if so, is profile support expected to work with the current
> `cups-local` tree, or is that part still not implemented/released?
> 
> I mainly want to make sure I am testing the intended CUPS 3.x setup
> correctly before deciding how the COSMIC side should handle manually
> entered/undiscovered printers.
> 
> Thanks,
> Abdelrahman
> 

________________________
Michael Sweet