Red Hat Bugzilla – Bug 429471
Print job doesn't finish using airport express print server.
Last modified: 2008-01-29 00:14:19 EST
Description of problem:
I have a HP photosmart 7960 connected via usb to an apple airport express. The
airport express advertises the printer over a jet direct port (9100).
When printing the test page it mostly prints out then stops. The printer still
says "printing". Cancelling the print tests and starting a new test page causes
the remaining section of the first job to start printing, followed by the second
It appears as if the last part of the job is never sent or flushed from the
buffer until the next job starts.
The printer works fine when connected directly via usb.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
What does 'lpstat -s' say when the printer is connected via the airport express
I'd like to see the TCP/IP stream between the CUPS client and the print server
when a job is submitted. You can do this by running this command:
tcpdump -s0 -U -w 9100.pcap port 9100
as root before sending the job, and pressing Control-C after the job has
finished printing as much as it's going to. Attach the 9100.pcap file to this
bug report. Thanks.
Created attachment 292406 [details]
tcpdump output of print job
lpstat -s shows the listed device uris with the relevant line being;
device for PhotoSmart_7960: socket://one.home:9100
where one.home is the hostname for my airport express.
See the attachment for the tcpdump output.
Possibly a duplicate of bug #428536.
hplip-2.7.12-4.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update hplip'. You can provide feedback for this update here: http://admin.fedoraproject.org/F8/FEDORA-2008-0820
The update works. The supplied link gives me a 404 error.
hplip-2.7.12-4.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.