![\"Welcome](\"https:\/\/cyberelk.net\/tim\/wp-content\/uploads\/2008\/02\/screenshot-1.png\")
<\/p>\nHere are some screenshots of the new trouble-shooter in system-config-printer. The actual framework is not specific to printing or CUPS at all, but provides a way of stringing together question screens while collecting diagnostic output along the way.<\/p>\n
It starts with a welcome screen:<\/p>\n
<\/p>\n
The assumption is that you are trying to print something to a particular printer, and are having trouble doing so. The list of available printers is shown, and you are asked which one you want to print to.<\/p>\n
![\"Choose](\"https:\/\/cyberelk.net\/tim\/wp-content\/uploads\/2008\/02\/screenshot-2.png\")
<\/p>\n
It can currently diagnose a handful of problems such as, in the case of Stylus_D78 here, the queue being disabled due to the printer being switched off. I hope to add more tests for problems such as this in future.<\/p>\n
![\"Queue](\"https:\/\/cyberelk.net\/tim\/wp-content\/uploads\/2008\/02\/screenshot-3.png\")
<\/p>\n
If the printer we want was listed, but none of the checks for common problems finds anything wrong, the next step is to print a test page. Before we do that, you are asked to turn on debugging. The reasons we ask permission here, rather than just doing it, are: firstly, we may need you to enter the root password for authentication with CUPS and want to give you some warning about why that is; secondly, the CUPS server may restart.<\/p>\n
![\"Debugging\"](\"https:\/\/cyberelk.net\/tim\/wp-content\/uploads\/2008\/02\/screenshot-4.png\")
<\/p>\n
Our “print a test page” screen allows you to cancel the jobs currently in the queue, submit a test page, or print your own document.<\/p>\n
![\"Print](\"https:\/\/cyberelk.net\/tim\/wp-content\/uploads\/2008\/02\/screenshot-5.png\")
<\/p>\n
Going back to the ‘choose printer’ screen, if your printer was not listed then we need to find out more about it.<\/p>\n
![\"Remote](\"https:\/\/cyberelk.net\/tim\/wp-content\/uploads\/2008\/02\/screenshot-6.png\")
<\/p>\n
Again, there are a handful of checks for common problems with the server. Ultimately, if we can’t find anything wrong in particular then the final screen admits defeat, although hopefully in a useful way:<\/p>\n
![\"Admit](\"https:\/\/cyberelk.net\/tim\/wp-content\/uploads\/2008\/02\/screenshot-7.png\")
<\/p>\n
The idea is that this diagnostic output, collected in the previous screens, will be useful for finding out the problem in a bug report or support ticket.<\/p>\n
I want it to be relatively easy to add new question screens and problem checks to this, and it is currently just about useful. There are lots more checks to add.<\/p>\n","protected":false},"excerpt":{"rendered":"
Here are some screenshots of the new trouble-shooter in system-config-printer. The actual framework is not specific to printing or CUPS at all, but provides a way of stringing together question screens while collecting diagnostic output along the way.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[3],"tags":[],"class_list":["post-231","post","type-post","status-publish","format-standard","hentry","category-software"],"yoast_head":"\n