Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Paused" state not persisted #286

Closed
andreaskem opened this issue Aug 31, 2023 · 1 comment
Closed

"Paused" state not persisted #286

andreaskem opened this issue Aug 31, 2023 · 1 comment
Assignees
Labels
bug Something isn't working priority-low
Milestone

Comments

@andreaskem
Copy link

Describe the bug
This bug was encountered using lprint but I was sent here to report the actual issue:
When pausing a printer (or its associated queue), its state is not persisted across service restarts.

To Reproduce

$ lprint pause -d lpne3
$ lprint status -d lpne3
Running, stopped since Thu, 31 Aug 2023 05:47:00 GMTpaused.
$ sudo systemctl restart lprint
$ lprint status -d lpne3
Running, idle since Thu, 31 Aug 2023 05:48:29 GMT.

Expected behavior
A paused printer should not be restarted by a reboot or service restart. For example, a printer might suddenly start printing many jobs after a system reboot.

System Information:

  • OS: Linux (Arch Linux)
  • pappl 1.3.2
  • cups 2.4.6
  • lprint 1.2.0

Additional context
Pausing a printer does not seem to have an effect on /etc/lprint.conf, where I assume its state should be persisted.

@michaelrsweet michaelrsweet self-assigned this Aug 31, 2023
@michaelrsweet michaelrsweet added bug Something isn't working priority-low labels Aug 31, 2023
@michaelrsweet michaelrsweet added this to the v1.4 milestone Aug 31, 2023
@michaelrsweet
Copy link
Owner

[master caca78c] When multiple queues are supported, preserve the paused state of each printer (Issue #286)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-low
Projects
None yet
Development

No branches or pull requests

2 participants