Bug 156567
| Summary: | cups printing to Lexmark N4000e via IPP fails with PCL XL error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Trevor Cordes <trevor> | ||||
| Component: | cups | Assignee: | Tim Waugh <twaugh> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3 | CC: | mattdm | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-02-08 03:59:14 UTC | Type: | --- | ||||
| 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
Trevor Cordes
2005-05-01 21:57:12 UTC
Darn, why does bugzilla sometimes not wrap the description text? Sorry about that folks. Thanks for your report. I'll need some more information from you: 1. Please could you attach the output of 'printconf-tui --Xexport'? This contains the configuration for the printer (as long as you used system-config-printer to set up the queue). 2. I'd like to see all of the TCP traffic between the CUPS print server and the N4000e print server, while that particular job is being spooled. You can use this command (as root) to obtain that: tcpdump -s 0 -U -w traffic.pcap host 192.168.1.1 with 192.168.1.1 replaced by the IP address or hostname of the N4000e print server. 1. I did not use system-config-printer to set up the queue. I'm an old school kind of guy. 2. It may be a while before I can get the tcpdump as the box is about 100km away and I need to be present to see if the PCL XL error occurs. It also might be tough to reproduce the error on demand. I got really lucky the other day when I was reliably able to make a certain report error out -- normally it's much more intermittent. I suppose there's a 50% chance the bug is in the N4000e and not linux, but at least this entry will help anyone else that runs into this. My guess is the traffic to the N4000e will look normal -- but we'll see. I'll report back once I have the tcpdump. Please attach the PPD for the queue (/etc/cups/ppd/queuename.ppd). Also: if you can get a reliable reproducer, please set up a queue to print to a file using that PPD, so we can see what *ought* to get sent. Then we can something to compare the TCP traffic to. There are no files in /etc/cups/ppd. I think this is because it's a "raw" queue? I'm fairly new to cups and don't have all the concepts figured out yet. How would I set it up to print to a file? Ah, yes, it is a raw queue then. Unfortunately I think there is a bug in CUPS regarding printing to a file on a raw queue. :-/ OK, I'll still do the tcpdump stuff next time I am there and report back (might be a few weeks). Hi again, I finally was out onsite and was able to test again, this time with tcpdump running. Unfortunately, I didn't figure out till later that I needed -i eth1 on tcpdump. I did make the bug occur once, but that was before the -i so I didn't capture it. I had a hard time reproducing the bug as I couldn't remember the exact sequence of events to make their custom app cause the bug. I am waiting now for better instructions on their app and will test again next time. However, I did see some weird behaviour that is probably related. In one function in their app, you can print schedules and if I print one that's big, it always failed in a strange way. The printer LED would flash like it was going to print, then the power LED would flash then the printing LED once more then nothing -- no print, no error, no LEDs. If I then send a smaller schedule, it prints fine. All this is using IPP. If I switch to socket: then it all works 100% ok. It would appear that the bug is print job size dependent, or maybe per page size. Above a certain size and it prints nothing. I have a funny feeling hitting the bug at a certain threshold causes the PCL XL page to print. I just need to find out how to do it again. Attachment will follow. Created attachment 117732 [details]
tcpdump text output of all traffic to print server
This tcpdump is of tons of tests I did trying to make the bug occur. Many of
the prints around the 03:5x mark (I think?) were ones that hit the new "didn't
print anything" version of the bug. I know it's a lot of output. Next time
when I can better reproduce the PCL XL bug I'll take a snapshot of just that.
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you! Fedora Core 3 is not maintained anymore. Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the current Fedora release, please reopen this bug and assign it to the corresponding Fedora version. |