On 2/19/19 12:45 PM, Howard Howell wrote:
addendum. Just checked. Printer is now working??? Don't know
what did
that unless it was cleaning the journalctl files. Is that in a closed
volume under F28? I had plenty of diskspace, more than 300GiB.
Only if you have /var on a separate partition and that would only affect
printing if it got full and couldn't create the spool files. But since
the log was still recording, that seems unlikely.
Should I close this now, or is there something I should check to see
what mucked it up in the first place?
Probably not possible to find out. Maybe running system-config-printer
poked cups in some different way. Hopefully it keeps working.