Your message dated Mon, 29 Dec 2008 09:16:09 +0100
with message-id <[email protected]>
and subject line Closing old bug without feedback
has caused the Debian Bug report #322505,
regarding /usr/bin/smbspool: smbspool to Windows XP results in hung printer job
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
322505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322505
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: smbclient
Version: 3.0.14a-6
Severity: normal
File: /usr/bin/smbspool
Here is the situation. I have a HP OfficeJet 5510v all-in-one printer
connected to a Windows XP Home box. I have a Linux box running Debian
Unstable, and I would like to print to the 5510v via SAMBA. I
discussed the situation with people on a HP linuxprinting.org mailing
list (included below), and they suggested I try running smbspool
directly with these instructions.
gs -dFIXEDMEDIA -q -dBATCH -dQUIET -dNOPAUSE -sDEVICE=ijs -sIjsServer=hpijs
-dIjsUseOutputFD -sOutputFile=spoolfile -dDEVICEWIDTHPOINTS=595
-dDEVICEHEIGHTPOINTS=842 -r600 -sDeviceManufacturer="HEWLETT-PACKARD"
-sDeviceModel="officejet 5500" -sIjsParams="Quality=1 ColorMode=2 MediaType=0
PenSet=1" /usr/share/cups/data/testprint.ps
export DEVICE_URI=smb://MSHOME/XPCOMP/hpoffice
smbspool 1 1 1 1 1 spoolfile
When I print the CUPS test page manually by running gs and then
smbspool. The printer starts responding. It sounds like the head is
moving back and forth like it normally does before the printer starts
printing. Then, it just sits there indefinitely. The Copy button light
flashes on and off. The LCD panel says "Printing...", but nothing
actually prints. FYI, during the test the XP box is essentially idle.
If I look at the print queue on the XP box, it has a job whose status is
"Printing". I end up having to cancel the job and reboot the XP box to
get it to give up trying to print this document.
The same file I printed with smbspool will print perfectly if I
connect the printer directly via USB to my Linux box.
I was able to print to predecessor (a different HP inkjet printer) to
the OfficeJet 5510v that was connected to this same XP box. Programs
on the XP box are able to print correctly.
Do you have any suggestions?
Tom
********************
Here is a dialog I had with people on the linuxprinting.org list for
HP printers.
I tried your suggestion. Executing smbspool by hand (as you suggested
below) causes the same behavior and printing via CUPS. Should I start
talking with the samba people?
I also verified the correctness of spoolfile by trying
"cat spoolfile > /dev/usb/lp0" after connecting the printer to the Linux
box via a long USB cable.
Tom
On Wed, 2005-08-10 at 13:51 +0100, Hin-Tak Leung wrote:
> You can break down the problem into two pieces:
> (1) cups<-> samba
> (2) samba<->XP
>
> I am not too familiar with how the first part works, but the 2nd part is
> easier to verify. Run the 2nd part without the first, like this:
>
> (1) you need to generate the spool data by hand using ghostscript and hpijs,
> (all in one line - check the <options> and the DeviceModel string from
> hpijs's website or docs)
>
> gs -dFIXEDMEDIA -q -dBATCH -dQUIET -dNOPAUSE -sDEVICE=ijs -sIjsServer=hpijs
> -dIjsUseOutputFD -sOutputFile=spoolfile
> -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842
> -r600 -sIjsParams=<options>
> -sDeviceManufacturer="HEWLETT-PACKARD" -sDeviceModel="hp officehet 5510"
> inputfile.ps
>
> (2) once you have the spool data, you can run the cups samba backend directly
> like this (set the DEVICE_URI parameter is the same as yours - smbspool needs
> 5 parameters before the spoolfile but they are not important so you could
> just put 1 there - this sends the spoolfile over using the Device_URI string).
>
> export DEVICE_URI=smb://<account>:<password>@<machine>/<queue>
> smbspool 1 1 1 1 1 spoolfile
>
> Read the documentation of smbspool, etc for extras.
>
> Tom Epperly wrote:
> > Here is the situation. I have a HP OfficeJet 5510v all-in-one printer
> > connected to a Windows XP Home box. I have a Linux box running Debian
> > Unstable, and I would like to print to the 5510v via SAMBA.
> >
> > I configured CUPS to print to the 5510v via SAMBA using
> > http://localhost:631/. I selected "HP OfficeJet 5500 Foomatic/hpijs
> > (recommended)" for the type of printer. The device URI is
> > Device URI: smb://MYHOME/FOOCOMP/hpoffice
> >
> > When I print the CUPS test page via the CUPS WWW page. The printer
> > starts responding. It sounds like the head is moving back and forth like
> > it normally does before the printer starts printing. Then, it just sits
> > there indefinitely. The Copy button light flashes on and off. The LCD
> > panel says "Printing...", but nothing actually prints. FYI, during the
> > test the XP box is essentially idle.
> >
> > If I look at the print queue on the XP box, it has a job whose status is
> > "Printing". I end up having to cancel the job and reboot the XP box to
> > get it to give up trying to print this document.
> >
> > For curiosity sake, I tried running a USB cable from the Debian box
> > directly to the printer (temporarily disconnecting it from the XP box).
> > I tried configuring CUPS to use the printer via USB, and lo and behold,
> > the printer works perfectly.
> >
> > Configuring with CUPS via USB:
> > USB Printer #1
> > HP OfficeJet 550 Foomatic/hpijs (recommended) (en)
> > Device URI: usb:/dev/usb/lp0
> >
> > This seems to suggest that something is going from in the SAMBA
> > transmission of the document data.
> >
> > Do you have any suggestions about how I can track down the root cause of
> > the problems I am seeing?
> >
> > Thanks,
> >
> > Tom
> >
> > Here are the Debian version numbers for some of the related packages.
> >
> > ii cupsys 1.1.23-11 Common UNIX Printing System(tm) -
> > server
> > ii foomatic-db 20050720-1 linuxprinting.org printer support -
> > database
> > ii foomatic-db-en 3.0.2-20050720 linuxprinting.org printer support -
> > programs
> > ii foomatic-db-gi 4.2.7-10 linuxprinting.org printer support -
> > database
> > un foomatic-db-gu <none> (no description available)
> > ii foomatic-db-hp 1.5-20050705-1 linuxprinting.org printer support -
> > database
> > ii foomatic-filte 3.0.2-20050720 linuxprinting.org printer support -
> > filters
> > ii foomatic-filte 20050720-1 linuxprinting.org printer support -
> > prebuilt
> >
>
>
> ___________________________________________________________
> To help you stay safe and secure online, we've developed the all new Yahoo!
> Security Centre. http://uk.security.yahoo.com
_______________________________________________
Hp-list mailing list
[email protected]
http://www.linuxprinting.org/cgi-bin/mailman/listinfo/hp-list
-- System Information:
Debian Release: testing/unstable
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.2
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) (ignored: LC_ALL set to
en_US)
Versions of packages smbclient depends on:
ii libc6 2.3.5-3 GNU C Library: Shared libraries an
ii libcomerr2 1.38-1.1 common error description library
ii libkrb53 1.3.6-4 MIT Kerberos runtime libraries
ii libldap2 2.1.30-11 OpenLDAP libraries
ii libncurses5 5.4-9 Shared libraries for terminal hand
ii libpopt0 1.7-5 lib for parsing cmdline parameters
ii libreadline5 5.0-10 GNU readline and history libraries
ii samba-common 3.0.14a-6 Samba common files used by both th
smbclient recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
As announced a few weeks ago...
--
signature.asc
Description: Digital signature
--- End Message ---
