Created attachment 819512 [details] cups log files Description of problem: Attempted to install two different printers to FC20 Beta (Fedora-20-Beta-x86_64-DVD.iso) using cups-bjnp to a Canon MP980 MFP, and both LPD and smb to a Samsung ML2540 laser printer shared from a Windows 8.1 system. With the Canon, cups sees the printer and can pull up information from it. When a job is sent to the printer, the printer indicates "Printing from PC", but does not activate the rollers or print heads. With cups logging enabled, no errors are indicated from the cups side. With LPD through Windows to the Samsung laser, cups again gives no indication of any errors, but the Windows Event Log states "The Line Printer Daemon (LPD) service received commands in an invalid format from 192.168.1.15 and refused the print job. This can occur if the Line Printer Remote (LPR) client is incompatible with the Windows LPD service and Request for Comments (RFC) 1179. Try printing using a different LPR client." With Samba through Windows 8.1, the Windows system has been configured to allow anonymous access to the printer and the firewall has been disabled. When the print job is submitted from FC20, the job is received by Windows as indicated in the Printer Status window, and forwarded to the printer connected via USB. The Samsung laser printer spins up and activates the fuser, but draws no paper and spins down. Version-Release number of selected component (if applicable): cups 1.7.0 cups-bjnp 1.2.1 cups-libs 1.7.0 cups-pk-helper 0.2.5 How reproducible: So far, I've only been able to test locally. Steps to Reproduce: 1. Set up Canon printer on network, and Samsung laser printer shared via Windows 8.1 with both LPD service and anonymous smb access allowed. 2. Add the printers through the CUPS web interface at https://localhost:631 using bjnp, LPD, and smb access. 3. Submit a job to the printers. Actual results: Printers indicate they are receiving data, but print jobs are not completed. Expected results: Completed print jobs. Additional info: The Canon printer works in FC19 using the cups-bjnp package, and configured through the web interface as described above.
Thanks for this report. It looks like there are a few things to investigate. For this bug report, let's concentrate on printing to the Canon printer. I've cloned this bug separate for the other issues. Could you please follow the troubleshooting procedure outlined here?: https://fedoraproject.org/wiki/How_to_debug_printing_problems#Printing_troubleshooter
Created attachment 820447 [details] First 500 lines of 30+GB error log system-config-printer went into a race condition, pumping data into the error log.
Created attachment 820450 [details] Last 500 lines of 30+GB error_log
That didn't go too well. The system-config-printer troubleshooter went into a race condition (ABRT bug 1027034) and wouldn't close. My error log was at 30GB before I managed to kill the process - I am attaching the first 500 and last 500 lines of the log. Trying to perform the steps manually according to the Fedora wiki produced zero results - lpinfo -l -v simply listed the configured printers, with no URIs listed. The drivers are less than informative since cups renamed them to printer_name.dpp. I didn't attempt the filter tests yet. One additional note - the system automatically found and attached to a networked HP Laserjet 4014n, and is fully operational with that printer.
Please follow these steps: 1. Stop the cups server: systemctl stop cups.socket cups.path cups.service 2. Clear out the error_log file: >/var/log/cups/error_log 3. Start the cups server again: systemctl start cups.service cups.socket cups.path 4. Enable debugging: cupsctl --debug-logging 5. Now send a print job to the Canon MP980 MFP. 6. Disable debugging: cupsctl --no-debug-logging After those steps, please attach: 1. The PPD for the queue from the /etc/cups/ppd/ directory. 2. The /var/log/cups/error_log file Thanks.
I apologize for dropping the ball on this bug. I no longer have the hardware or software referenced herein, so I cannot provide the needed information. I am closing this bug for lack of required info.