public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [OT] print to printer on winxp via cups samba smb
Date: Wed, 13 Sep 2006 21:27:03 -0700	[thread overview]
Message-ID: <7573e9640609132127w4f9d254fq9bbc3a763ddfadf7@mail.gmail.com> (raw)
In-Reply-To: <87y7snqifr.fsf@newsguy.com>

On 9/13/06, reader@newsguy.com <reader@newsguy.com> wrote:
> > Hmm, do you get something similar if you do:
> >
> > DEVICE_URI=smb://reader:XXXXX@chub/chub-print
> > export DEVICE_URI
> > /usr/bin/smbspool 0 reader test 1 0 /etc/fstab
>
> Well, that tried to print something at least.  Somekind of stepping
> problem seems to have prevented a real print.  I got 2 pages. one page
> with the first and second line of fstab.  The second line was indented
> about half a page. Then a blank page.

Ok, that's good.  The staircasing is easily explained/fixed, but not
really important.  Mostly we are just interested in the fact that that
command did connect and try and print.

First, do an "ls -l /usr/libexec/cups/backend/smb"  It should be a
symbolic link pointing to /usr/bin/smbspool.

If it is, then we need to see what the differences are between running
that command directly vs the way cups runs it.  We can use some shell
script trickery to do this:

1. mv /usr/bin/smbspool /usr/bin/smbspool.bin
2. $EDITOR /usr/bin/smbspool
Make a new script that contains:
------
#!/bin/bash
tmpfile=/tmp/smbspool.$$
echo $0:$1:$2:$3:$4:$5:$6:$7 > $tmpfile
env >>$tmpfile

# this part is just a guess..
export DEVICE_URI=$0
/usr/bin/smbspool $1 $2 $3 $4 $5 $6 >>$tmpfile
------

3. chmod 755 /usr/bin/smbspool

Try printing again through cups.  After the failure, you should have
one or more /tmp/smbspool.* files.  Post one of those here, although
you may want to inspect it first and mask out anything that reveals
your password!

-Richard
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-09-14  4:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 16:59 [gentoo-user] [OT] print to printer on winxp via cups samba smb reader
2006-09-13 20:04 ` Mick
2006-09-14  0:37   ` [gentoo-user] " reader
2006-09-13 20:18 ` [gentoo-user] " Richard Fish
2006-09-14  1:10   ` [gentoo-user] " reader
2006-09-14  1:55     ` Richard Fish
     [not found]       ` <87y7snqifr.fsf@newsguy.com>
2006-09-14  4:27         ` Richard Fish [this message]
     [not found]           ` <87ac52k3o1.fsf@newsguy.com>
2006-09-14 13:56             ` reader
2006-09-15  7:40             ` Richard Fish
2006-09-15 13:52               ` reader
2006-09-15 16:55                 ` Richard Fish
2006-09-15 17:56                   ` reader
2006-09-15 23:57                     ` Richard Fish
2006-09-17  2:09                       ` reader
2006-09-17  4:27                         ` Richard Fish
2006-09-17 11:44                           ` reader
2006-09-17 15:21                             ` Richard Fish
2006-09-18 17:12                               ` reader

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7573e9640609132127w4f9d254fq9bbc3a763ddfadf7@mail.gmail.com \
    --to=bigfish@asmallpond.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox