On Fri, 2008-11-07 at 11:15 -0500, Todd Denniston wrote: > take a look in /var/log/cups/ at page_log, error_log and access_log and see > if > there is something that make sense there, before starting your new thread. > > If there is no info there, then you may have to (backup first and) edit > /etc/cups/cupsd.conf to set LogLevel to debug instead of info, then `service > restart cups`. (hopefully a restorecon /etc/cups/cupsd.conf will not be > needed) > try a few prints and check the logs again.
It would be much easier to just run the printing troubleshooter, System->Administration->Printing, then Help->Troubleshoot. It automates log capture and can even diagnose some simple problems. If it fails to identify the problem, you can see the diagnostic output including the relevant portions of the log files. If the diagnostic output is too cryptic to understand but you think there is a bug in the software, file a bug report about your problem and attach the troubleshoot.txt file. Tim. */
signature.asc
Description: This is a digitally signed message part
-- fedora-list mailing list [email protected] To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
