Bug 1062484
| Summary: | Fedora 20 fails to print to wireless Canon printer. Hangs in processing state | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paul Lambert <eb30750> | ||||||||||||||||||||||||
| Component: | cups | Assignee: | Tim Waugh <twaugh> | ||||||||||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||
| Version: | 20 | CC: | eb30750, jpopelka, twaugh | ||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||
| Hardware: | athlon | ||||||||||||||||||||||||||
| OS: | Linux | ||||||||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||
| Last Closed: | 2014-08-11 10:06:42 UTC | Type: | Bug | ||||||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||
|
Description
Paul Lambert
2014-02-07 03:11:30 UTC
Please follow the instructions here: https://fedoraproject.org/wiki/How_to_debug_printing_problems#Printing_troubleshooter If this tool doesn't find the problem, you will end up with a troubleshoot.txt file you can attach to this bug report using the 'Add an attachment' link further up this page. Created attachment 860523 [details]
system-config-printer
Created attachment 860524 [details]
lpinfo output
When launching system-config-printer the app finds the wireless printer and displays it by name. However, when initiating troubleshooting and enabling debugging the app just hangs like a print job does. See the screenshot attachment. the output of lpinfo is in the text file attachment. No printer is found by name by this command. The outputs from the command /usr/lib/cups/backend/snmp 192.168.1.67 I did go through the manual steps to clear the cups error log and restart the cups server. Created attachment 860541 [details]
troubleshoot.txt
Created attachment 860543 [details]
screenshot after cancelling system-config-printer
I reran system-config-printer and once it started to hang I clicked cancel. This produced the attached screenshot that stated there is no obvious solution. I was alos able to click save and gather the troubleshoot.txt file contents that is attached.
Could you attach /var/log/cups/error_log please? Created attachment 860556 [details]
errorlog file
The original cups error_log file was over 7.5 GB. I reduced the size by cutting out thousands of reoccurring "select_timout" errors. I capture the first and last 3000 lines of the original file.
OK. There were no jobs there so unfortunately it hasn't captured what we need to see.
Please do this:
1. Show me which version you're using: rpm -q cups
2. Become root: su -
3. As root, stop CUPS:
systemctl stop cups.path cups.socket cups.service
4. Still as root, clear out the error_log file:
>/var/log/cups/error_log
5. Still root, start CUPS:
systemctl start cups.service cups.socket cups.path
6. Make sure we have debugging on:
cupsctl --debug-logging
7. Now, try printing as before, but please describe how you are doing it: e.g. printing from Firefox, something else? What sequence of actions do you use to do this?
8. Notice what you see: tell me how you know it is not working. Is there an error message? Does the application still respond to interaction? Does the printer flash any lights? etc
9. When everything has finished doing what it's going to do, turn off debugging:
cupsctl --no-debug-logging
10. Finally, attach /var/log/cups/error_log
Created attachment 860779 [details]
error log
cups version
cups-1.7.0-9.fc20.x86_64
from desktop folder double click PDF file that launches Document Viewer. Access the settings menu and select print. Print dialog says printing. Nothing happens on the printer. Go to system menu and open Tools. Then open printing. 1 active job. See screen capture. The bottom banner comes up with error and states the printer might not be connected. I click on show jobs and then cancel the print job. Error_log file is attached.
I stand by my first premise that between cups and the device driver they are not making a connection to the network wireless printer.
Created attachment 860780 [details]
screenshot of active print job
The printer is refusing connections: D [07/Feb/2014:18:57:46 -0500] [Job 34] Connecting to 192.168.1.66:515 for printer L1 I [07/Feb/2014:18:57:46 -0500] [Job 34] Connecting to printer. D [07/Feb/2014:18:57:46 -0500] [Job 34] Connection error: Connection refused W [07/Feb/2014:18:57:46 -0500] [Job 34] The printer is in use. Created attachment 861401 [details]
printer config
In reviewing the error I noticed that the IP address was not correct. At one time it was but the printer now uses 192.168.1.67. I ran system-config-printer and opened properties and corrected the IP address. Then I printed a text page and it worked like a champ.
When using wireless printers Fedora needs to find the default printer by name and and then acquire the correct IP address. (though I could probably fix the IP address on the printer). The dynamic solution is to always look up the IP address for a configured printer when performing wireless printing, or for any wireless device for that matter.
How did you configure the queue? What actions did you take when doing that? Created attachment 861425 [details]
printer properties
Does this screen capture provide the information you are looking for?
Not really. It says that perhaps you used system-config-printer to configure it, but I'm not sure what you did next. Crucially: did you tell it the IP address of the printer, or the hostname of the printer, when configuring it? If you told it the IP address, there's really not much that could have been done to prevent this situation. If you told it the hostname, we need to investigate how that information got lost. I simply clicked the "print test page" button and then the page printed. This printer worked previously so the configuration was already stored with only the IP address being incorrect. It is also the default printer. No, the queue was not there at installation. Try this: delete the queue altogether. What do you do next when you want to print to the printer? Created attachment 861553 [details]
cups error log
Created attachment 861557 [details]
error_log
I deleted the printer and planned to re-add it while capturing the error logs for you. I have done that and re-added the printer using system-config-printer and cups.(with different names) and now neither will print. The errors appear different than when the IP address was incorrect. I can ping the printer but when using the interactive configurator it will not find the printer. Only when I force the the URI to be lpd://192/.168.1.67/L1 as in the screenshot previously uploaded.
this bug has been resolved after installing recent CUPS updates. Please close Thanks for re-testing. |