Bug 4707 - Printing Failure
Printing Failure
Status: NEW
Product: Samba 3.0
Classification: Unclassified
Component: smbclient
x86 Linux
: P3 major
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2007-06-18 10:30 UTC by Daniel Feiglin
Modified: 2007-06-19 02:38 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Feiglin 2007-06-18 10:30:15 UTC
I got this:

  smbd version 3.0.23d-19.5-1290-SUSE-SL10.2 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2006
[2007/06/18 17:03:22, 0] rpc_parse/parse_spoolss.c:spoolss_io_devmode(790)
  spoolss_io_devmode: I've parsed all I know and there is still stuff left|
[2007/06/18 17:03:22, 0] rpc_parse/parse_spoolss.c:spoolss_io_devmode(792)
  spoolss_io_devmode: available_space = [252], devmode_size = [472]!
[2007/06/18 17:03:22, 0] rpc_parse/parse_spoolss.c:spoolss_io_devmode(793)
  spoolss_io_devmode: please report to samba-technical@samba.org!
[2007/06/18 17:03:22, 0] rpc_server/srv_spoolss.c:api_spoolss_open_printer_ex(76)
  spoolss_io_q_open_printer_ex: unable to unmarshall SPOOL_Q_OPEN_PRINTER_EX.
[2007/06/18 17:03:22, 0] rpc_server/srv_pipe.c:api_rpcTNP(2287)
  api_rpcTNP: spoolss: SPOOLSS_OPENPRINTEREX failed.

Here is some more detailed background: (Extract of email to the openSUSE list)


I have an openSUSE 10.2 "vanilla" installation with Samba set up as a
server for my Windows work group, with all Win 2K clients. The Linux
system is fully patched. I have a parallel port HP printer attached to
the Linux box - which works fine, locally. CUPS operates as expected,
without problems.

When I try to print something from a Win 2K client, say a browser page -
there is a flurry of activity on the net (from the blinking lights on
the hub) - and then, nothing.

If on the client, I open up a command line and do something like this:

print  /d:\\<server_name>\<printer_share_name>   <little_text_file>

<little_text_file> gets printed as expected.

Other things:
1. The smb.conf file is maintained using SWAT, and follows the help
instructions for configuration with CUPS.
2. The CUPS and Samba spool directories have (at least for now) rwx
permissions for all users.
3. A second Win 2K client running as a VMware guest shows precisely the
same behavior.
4. A look at the Samba & CUPS logs suggests that Samba is not passing
stuff to CUPS.

(Attempting to print from Word on either client also produces nothing as
above, but with the additional bonus that Word crashes.)


What I was doing at the time, was printing a web page from Firefox on the Win 2K client. The web page was contrived, having only one line of text.
Comment 1 Jeremy Allison 2007-06-18 18:16:45 UTC
We'll need a debug level 10 to look into this I'm afraid.
Comment 2 Daniel Feiglin 2007-06-19 00:14:19 UTC
(In reply to comment #1)
> We'll need a debug level 10 to look into this I'm afraid.
> Jeremy.

OK. What do I do?

(I'm an ex-programmer turned tech writer, so I don't scare too much from tech stuff.)
Comment 3 Daniel Feiglin 2007-06-19 02:38:10 UTC
I'm reducing severity.

You can print directly from a client via a shared printer on a Linux box via CUPS (using the IPP protocol). I was not ware of this when I submitted the bug.

Since IPP is supported since Win 2K, I wonder if it would not be worth fiddling Samba to just "pass through" print jobs via IPP for CUPS users.