"Richard Fish" <[EMAIL PROTECTED]> writes:

> On 9/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> DEVICE_URI=smb://reader:[EMAIL PROTECTED]/chub-print)
>
> And *now* see the problem.
>
> There should absolutely positively *not* be a ')' at the end of this
> line.  You need to fix printers.conf to remove this.  Sigh...so much
> work for such a silly little problem.

Richard, I'm sorry it seems I've really wasted lots of your time here.
However I don't think this is the only problem.  I really hope there
is not some other moronic user miconfig...

It's really a kick in the pants that my very first post on this thread
Showed  that stupid typo... I never would have seen it I guess, if you
had not.  But it was there in my very first post... looking back it
appears glaringly right their in my posted `printers.conf'.

It seems bad to me that something in cups error output did not point
to that misconstrued URL.  In fact, going further... I see literally
thousands of lines appear in error_log (in debug mode) that are not
error lines at all.   Then the actual error lines are nearly useless
in tracking down a problem.

I'm still unable to print (EVEN WITH THAT CURSED URL FIXED).

It may be too much to expect you to still hang in there with this
problem so please tell me you've had enough if that is the case.

If you are still willing... (and I cannot guarantee there is not some
other horribly stupid user error) what can I post that will help diagnose
this inability to print?  

I've posted below error_log excerpt, /tmp file content.
smbclient connection to chub-print (at the very end)

Why doesn't cups debug output give us some better diagnostic
information?

Can you see some other really stupid typo or something else in this
output?

Actual error lines from /var/log/cups/error_log:
[... skipped Four more of these Connect messages above]

  E [16/Sep/2006:20:48:26 -0500] [Job 51] Unable to connect to CIFS
  host, will retry in 60 seconds...

  E [16/Sep/2006:20:49:26 -0500] [Job 51] Unable to connect to CIFS host
  after (tried 3 times)

  E [16/Sep/2006:20:49:26 -0500] PID 10109
  (/usr/libexec/cups/backend/smb) stopped with status 1!

  E [16/Sep/2006:20:49:27 -0500] PID 10108
 (/usr/libexec/cups/filter/foomatic-rip) stopped with status 9!


After this attempt chub-print gets turned off as revealed by lpq:
 # lpq
  chub-print is not ready
  Rank    Owner   Job     File(s)                         Total Size
  1st     reader  51      file                            2048 bytes

Turning printer off on error is not in my printers.conf (remvoed by
me)

The /tmp file from this print attempt:

  
/usr/libexec/cups/backend/smb:50:reader:file:1:job-uuid=urn:uuid:e3a19e12-d965-3164-57e1-f3f92cea54ec::
  IPP_PORT=631
  TMPDIR=/var/spool/cups/tmp
  CUPS_FONTPATH=/usr/share/cups/fonts
  CUPS_DOCROOT=/usr/share/cups/docs
  USER=root
  CUPS_SERVERROOT=/etc/cups
  SOFTWARE=CUPS/1.2.3
  CUPS_CACHEDIR=/var/cache/cups
  DEVICE_URI=smb://reader:[EMAIL PROTECTED]/chub-print
  PATH=/usr/libexec/cups/filter:/usr/bin:/usr/sbin:/bin:/usr/bin
  CUPS_REQUESTROOT=/var/spool/cups
  PWD=/
  [EMAIL PROTECTED]
  PPD=/etc/cups/ppd/chub-print.ppd
  LANG=en_US
  CUPS_ENCRYPTION=IfRequested
  SHLVL=1
  CUPS_DATADIR=/usr/share/cups
  PRINTER=chub-print
  FINAL_CONTENT_TYPE=printer/chub-print
  RIP_MAX_CACHE=8m
  CONTENT_TYPE=text/plain
  CUPS_SERVER=localhost
  CHARSET=utf-8
  CUPS_STATEDIR=/var/run/cups
  CUPS_SERVERBIN=/usr/libexec/cups
  _=/usr/bin/env
  WARNING: The "printer admin" option is deprecated
  added interface ip=192.168.0.4 bcast=192.168.0.255 nmask=255.255.255.0
  cli_start_connection: failed to connect to CUPS<20> (0.0.0.0)
  cli_start_connection: failed to connect to CUPS<20> (0.0.0.0)
  [... snipped 7 more identicle lines]

Note that smbclient can connect as user reader to chub-print with no
problem. 
  smbclient //chub/chub-print -Ureader
  WARNING: The "printer admin" option is deprecated
  Password: XXXXXX <enter>
  Domain=[CHUB] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
  smb: \>

-- 
gentoo-user@gentoo.org mailing list

Reply via email to