[Ubuntu Wiki] Update of "DebuggingPrintingProblems" by vorlon

Ubuntu Wiki noreply at ubuntu.com
Tue Jul 3 19:33:48 UTC 2018


Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "DebuggingPrintingProblems" page has been changed by vorlon:
http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=100&rev2=101

Comment:
there is no supported release of Ubuntu that lacks the cupsctl command. cull dead documentation.

   1. In Oneiric or newer with Unity desktop click the gear icon at the upper right (the one also used to log out) and in the menu showing up then, click "Printer" (or, in some versions, "Printers"). Or go to "System Settings" in the launcher and click on "Printing". The printer setup tool system-config-printer will open. Select "Server Settings" in the list on the left or in newer versions with the printers showing as icons choose "Server" in the main menu and then "Settings". Note that the main menu will be in the bar at the top of the screen if Oneiric (or newer) with Unity is used. There it only appears if you move the mouse into the top bar. Then check the checkbox "Save debugging information for troubleshooting" and click "Apply".
   2. In all Ubuntu flavors (also Kubuntu and server editions) you can run <<BR>> {{{$ cupsctl LogLevel=debug}}} <<BR>> to activate debug logging.
   3. In Karmic and later (CUPS 1.4.x) there is an automatic debug logging only for failed print jobs. So if you problem was a failed print job, the error_log can already contain the desired information. Unfortunately, only 200 debug message lines get logged per failed job. Run the command <<BR>> {{{$ cupsctl LogDebugHistory=999999}}} <<BR>> for practically unlimited logging of failed jobs.
-  4. In older versions of all flavors, where there is not yet a "cupsctl" command, edit the file {{{/etc/cups/cupsd.conf}}}, find the line '''Log``Level ...''' and change it to '''Log``Level debug''', save the file. Then restart CUPS: <<BR>> {{{$ sudo service cups restart}}}
-  5. Clear the queue from any stuck jobs by deleting the jobs in the job viewer or running the "{{{cancel -a}}}" command.
+  4. Clear the queue from any stuck jobs by deleting the jobs in the job viewer or running the "{{{cancel -a}}}" command.
-  6. Try to print something. Wait until the job disappears from the queue or turns into "Stopped" state, independent whether something gets out of the printer. If the job never reaches "Stopped" state after the printer not showing any reaction for a longer time you also can go on to the next step.
+  5. Try to print something. Wait until the job disappears from the queue or turns into "Stopped" state, independent whether something gets out of the printer. If the job never reaches "Stopped" state after the printer not showing any reaction for a longer time you also can go on to the next step.
-  7. Scan or photograph the printout if it is not correct and attach the images to the bug report.
+  6. Scan or photograph the printout if it is not correct and attach the images to the bug report.
-  8. Add {{{/var/log/cups/error_log}}} as an attachment to the bug report. Note that the file is not accessible for normal users. From Jaunty on you can access it from the account of the first user set up (in general users in the "adm" group). Otherwise you need to access it as root. To view the file run <<BR>> {{{$ sudo less /var/log/cups/error_log}}} <<BR>> and to copy it for attaching to a bug report run <<BR>> {{{$ sudo cp /var/log/cups/error_log ~}}} <<BR>> {{{$ sudo chmod 777 ~/error_log}}}
+  7. Add {{{/var/log/cups/error_log}}} as an attachment to the bug report. Note that the file is not accessible for normal users. From Jaunty on you can access it from the account of the first user set up (in general users in the "adm" group). Otherwise you need to access it as root. To view the file run <<BR>> {{{$ sudo less /var/log/cups/error_log}}} <<BR>> and to copy it for attaching to a bug report run <<BR>> {{{$ sudo cp /var/log/cups/error_log ~}}} <<BR>> {{{$ sudo chmod 777 ~/error_log}}}
  
  = Troubleshooting Wizard =
  



More information about the Ubuntu-bugsquad mailing list