Did you print a file at the point the troubleshoot process asked you to? It doesn't record any file being printed. It would be really useful to see that debugging output from printing a file.
If you aren't able to do that using the troubleshooter, just use "cupsctl --debug-logging", then print a file, then attach /var/log/cups/error_log. You can turn off debugging afterwards with "cupsctl --no-debug-logging".
I think that's a kernel version number.
Did you print a file at the point the troubleshoot process asked you to? It doesn't record any file being printed. It would be really useful to see that debugging output from printing a file.
If you aren't able to do that using the troubleshooter, just use "cupsctl --debug-logging", then print a file, then attach /var/log/ cups/error_ log. You can turn off debugging afterwards with "cupsctl --no-debug- logging" .