linuxmint / linuxmint/cinnamon-desktop
Printing fails silently, and "cups-pki-invalid" error is hidden.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 249
- Forks
- 76
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 2
Description
Error in cups log (but not shown as a popup unless I missed it), and the printer tray icon offers no way to solve the issue. It just doesn't print (silent failure).
Here are the full details: https://github.com/OpenPrinting/cups/issues/1072
michaelrsweet from CUPS says it should be handled by the GUI code:
What needs to happen is the desktop software should display this alert with an option for resetting (deleting) the certificate. That is outside the scope of this project. Ordinarily the certificate should not change for a while (default on most printers is 10 years for their self-signed certs).
Disabling the PKI check disables an important security check. . .
-michaelrsweet https://github.com/OpenPrinting/cups/issues/1072#issuecomment-2393434856
@sample What matters is the certificate the printer is currently using. I've noticed that some printers (incorrectly) generate a new self-signed certificate after a firmware update. They can also do this if their hostname changes.
. . .
-michaelrsweet https://github.com/OpenPrinting/cups/issues/1072#issuecomment-2393543651
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked CUPS issue and its cited comments, then inspect how the desktop printer tray handles CUPS errors. Done means displaying the certificate error with an option to reset or delete the certificate, without disabling the PKI check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100