OpenPrinting / OpenPrinting/cups-browsed
cups-browsed fails after some suspend/resume cycles
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 49
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
I have to restart the cups-browsed.service pretty often when my printer gets set to inactive after some suspend/resume cycles. I'm not sure if this maybe printer model related (Samsung M2825DW via IPPeverwhere). If have this on my desktop as well when trying to access from laptop using the same OS.
Attaching debug cups-browsed logs where the printer failed trying to print after the 19:59 resume:
cups-browsed_log.before_restart.txt
cups-browsed_log.after_restart.txt
Any idea how to track this down and if this could be an issue in cups-browsed or the printer firmware? Could this also be some issue in cups itself?
This is Arch Linux running cups-browsed 2.0.0-2 (last master commit added) and cups 2.4.8-1.
Contributor guide
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 by comparing the attached cups-browsed logs from before and after restarting the service, focusing on the failed print after the 19:59 resume. Reproduce the suspend/resume cycle on Arch Linux with cups-browsed 2.0.0-2 and cups 2.4.8-1. Done means identifying whether the failure is in cups-browsed, cups, or the printer firmware and documenting a reproducible diagnosis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- arch-linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100