samba - Jul 2003 - Mdk 9.1, samba-LDAP 2.2.8a/3.0b3 (LDAP) can't print to z53

I've not been able to get Samba to print to a Lexmark Z53.
If I call it a Z52, the driver uploads (to where, I have no idea so I 
can't check it) but I still can't get anything out of the printer.

On Mon, 28 Jul 2003, Jim C wrote:
> I've not been able to get Samba to print to a Lexmark Z53.
> If I call it a Z52, the driver uploads (to where, I have no idea so I
> can't check it) but I still can't get anything out of the printer.
Jim,

You seem to be going through a big pain barrier!

You have CUPS installed? If so, then why are you doing things the hard
way?

With CUPS the easiest installation is to install the printer in CUPS.
The Z53 is fully supported in SuSE 8.1 and upwards.

Then install only the Adobe postscript drivers for all your clients.
CUPS will do all the conversion needed. You Windows clients do not need to
talk to the printer and you cut loose from that aweful Lexmark driver.

Just a thought! It could save a lot of head banging!

- John T.
-- 
John H Terpstra
Email: jht@samba.org

Nice telling subject, Jim. Exemplary. Kudos :-}
>I've not been able to get Samba to print to a Lexmark 
>Z53. If I call it a Z52, the driver uploads (to 
>where, I have no idea so I  can't check it) but I 
>still can't get anything out of the printer.
If you dig deeper into Kurt Pfeiffle's opus, you may
find out that there is a procedure to be followed to
establisch default settings for a printer upon first
install on a client. You need to be the domain admin
to do it properly.

I hope your problem is as simple as that. But don't
despair if it isn't. you would probably have the same
problem with any other printer.


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

>>>still can't get anything out of the printer.
>>If you dig deeper into Kurt Pfeiffle's opus, you may
>I don't suppose you have a link for this guys stuff?
Ever heard of google? Sorry I missspelled his name,
which is really Preifle, not Pfeiffle, but google is
forgiving. It showed all Mr. Pfeifle's documents on
the web wrongly attributed to Preiffle and then asked: "Did you mean
'Pfeifle cups'?". Here are a
coupla URLs off the top of that heap:
  
http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/VII.cups-help/VII.cups-help.html
     
http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html

Lots of other people discuss each other's printing
problemse here:

   http://www.linuxprinting.org/printer_list.cgi

   http://www.linuxprinting.org/driver_list.cgi

   http://www.linuxprinting.org/driver_list.cgi

and keep samba list open for knottier problems with
authentication etc.

If you can speak or at least read German these URLs
are also valuable:

   http://www.danka.de/printpro/faq.html

   http://www.danka.de/printpro/node6.html

And of course, once you embark on any of these URLs
further URLs open up aplenty.


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

>>PS: Your subject line sucks.
>This better? ;-)
Big way! Hey Jim, now everyone knows exactly what the
thread is about and can contribute freely to your
salvation.


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

>>Jim, you are incorrigible!
>>
>>I told you a hundred times you should change your
>>subject line, because it has technically very little 
>>to do with your problem, but you still keep writing
>>"Re: I've always HATED printing with Samba".
>>
>>As a matter of fact, your problem is psychological
>>rather than technical, as your last letter shows. 
>>For reasons you won't tell us, you DO want samba NOT 
>>to be able to print to your printer. You are wasting 
>>our time.
>>  
>>
>Jeeze. Relax.  Your just reading my mail out of order 
>I think... or perhaps I sent it out of order. <shrug>
>...and some of this was just me being nit picky about
>perspective anyway.
Jeeze, Jim. Relax. I only cussed as long as the 
subject line sucked. I'm in a totally different time 
zone. And I get your mail as paper slips delivered by 
a yacc. Sequentially. That's my firewall.


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

>ROFL! ;-)
>
>OT but here is something you'll probably like. 
>http://www.userfriendly.org/cartoons/archives/03jul/uf005775.gif
kewl. lol. I like userfriendly too. Just no time to
visit it too often.


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

>>It's probably better to first make it to print under
>>3.0b3. It's supposed to be stable and bug-free for
>Right but my setup for it isn't, just yet. ;-)
If you feel more comfortable (i.e. your setup works)
with 2.2.8, sure go for it, but take care of bug #82.


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

>Yup.  Also spotted him on the list anyway.  Got some 
>leads from him but most of them are for 3.0 (which 
>I'll need later).
Don't be confused by "3.0" in the name of the document.
99% perhaps even 100% of the printing related 
information is not version dependent. Version 3.0 is 
better for printing because the resolution of bug #82 
was checked into 3.0 branch and not in 2.2.8 branch 
because they probably don't want to maintain that 
branch so actively now that 3.0 is out. The team is
spread a little too thin. 
>Also check this out:
>
>[root@enigma printers]# pwd
>/var/lib/samba/printers
>[root@enigma printers]# ls -l
>total 3
>drwxrwxr-x 2 root adm    48 Mar 16 06:50 W32ALPHA/
>drwxrwxr-x 2 root adm    48 Mar 16 06:50 W32MIPS/
>drwxrwxr-x 2 root adm    48 Mar 16 06:50 W32PPC/
>drwxrwxr-x 2 root adm    48 Mar 16 06:50 W32X86/
>drwxrwxr-x 2 root adm    48 Mar 16 06:50 WIN40/
>[root@enigma printers]#
>
>According to reasearch, this is where I think the 
>printer drivers are supposed to wind up and 
>apparently they are not even after adding 
>Administrator to the adm group. W32X86 is the most 
>likely target since that is where they are on the XP 
>client.   I'm going to run some more tests on this 
>(after I get some Z's) to be sure.
This is a directory which is created by a template in
samba.spec, not necessarily the directory in which
samba will look for it, which is ruled by an option
to configure command IIRC and is usually "drivers"
directory. I resolved the ambiguity have one name
linked to the other.


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

>Where can I find out more about this Samba bug #82 or how can I 
>check and see if I've the patch? I don't seem to be able to find it 
>useing just the number 82 at 
>   http://evacs.samba.org/cgi-bin/evacs-bugs/
>Am I looking in the right place?
You ain't. The right place to lookit up is this, my very first letter 
to you, which begins with:

   --------- Original Message ---------
   DATE: Sat, 26 Jul 2003 15:40:00
   From: "Dragan Krnic" <dkrnic@lycos.com>
   To: jcllings@tsunamicomm.net
   Cc: samba@lists.samba.org
   
   >Can't you give your subject line a more positive spin
   ....

and ends like this:

   ...
   >I haven't followed your thread but perhaps your problem
   >and solution are described in the following document:
   >
   >   https://bugzilla.samba.org/show_bug.cgi?id=82

Looks like it's never enough to tell you once :-)

> Which doesn't:
> a)Have any attachments
Thanks. The maintainer closed the bug as fixed. I didn't see the need
to supply further information. So I left it at that.

I've just posted attachment #62 to bug #82 containing the patch
diff text I use to incorporate changes in my 2.2.8a.
> b)link to a cvs diff
Huh?
> c)Give any information that would be useful in tracking down the 
> patch (I have looked, the first time you posted this link).
> 
> All my printer driver uploads have worked correctly on our 2.2.8a
> packages, (I did one last week on 9.0/2.2.8a-2mdk).
Which is really interesting. Can you look up the section cited in
my patch file to see whether Mandrake patched it on their own or the 
patch is already in cvs without a link to it in bugzilla?
> So, unless I see an official patch list for 2.2.8a (or there is a 
> new release, maybe also fixing the problem with cups printers not 
> appearing without a restart of smbd) or a transparent way of 
> finding which patches should be applied, I won't rebuild packages 
> for 5 releases.
You're under no obligation to do anything, especially if you don't 
have the problem. Your name just popped up in a thread I shared with 
Jim for some reason and I didn't remove it from later correspondence.

If you don't want this thread to be copied to you, just say so.

Sorry for the inconvenience it might have caused.

Well it really wouldn't be fair to ask Buchan to jump through his 
bungholio over this.  I'ld be pretty ticked off if someone asked me to.
What about turning up the loglevel to10 for a test and then I could do 
something like this:

tail -f /var/log/messages | grep 'INTERNAL ERROR'

Then I try to upload the drivers again and if I see the error, I'll know 
it is time to give up on 2.2.8 and just wait for 3.0
Any reason you can think of why this won't work for detecting the bug in 
question?

Jim C.

>Well it really wouldn't be fair to ask Buchan to jump 
>through his bungholio over this.  I'ld be pretty 
>ticked off if someone asked me to. What about turning 
>up the loglevel to10 for a test and then I could do 
>something like this:
>
>tail -f /var/log/messages | grep 'INTERNAL ERROR'
>
>Then I try to upload the drivers again and if I see 
>the error, I'll know  it is time to give up on 2.2.8 
>and just wait for 3.0 Any reason you can think of why 
>this won't work for detecting the bug in question?
If you read carefully the bug thread #82, that's
pretty much what I did. But once I found what was 
wrong, I also tried to fix it. That's probably why I 
love samba printing and you choose to hate it.

If something like that happens with a WinDoze, once
you've exhausted all the mouse clicks prescribed by
Mr. Ballmer, well, tough luck. With open source, you 
dig deeper and you realize the software has been
written by people like you and me - not perfect, but
perfectionable. Nothing stops you from making it work,
if by chance it's broke. The maintainers have probably 
fixed it in 3.0 in such a way that the sysadmin 
reporting routine doesn't have to be taken out of the 
loop. I thought, what the hell, I'm the only printer 
admin on my system, so why should I want to know that 
I've installed all those printers if I know already. 
But if you want to know exactly that you have 
installed the goddamn z53, there's no way around 
waiting until 3.0 is safe enough for you and buchan. I 
don't know, it's not everyone's beer, but it was fun 
picking up the pieces of the puzzle (different 
components like templates, patch files etc.) to make 
my distro's samba.spec amenable to an rpm build, i.e. 
compile the whole samba suite without an error. You 
learn a lot like that. And you get the job done.


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

>>>b)link to a cvs diff
>> Huh?
>Something like this:
>http://cvs.samba.org/cgi-bin/cvsweb/samba/source/lib/util_unistr.c.diff?r1=1.45.2.27&r2=1.45.2.28&only_with_tag=SAMBA_2_2
>
>Which according to the cvs log:
>http://cvs.samba.org/cgi-bin/cvsweb/samba/source/lib/util_unistr.c.diff?r1=1.45.2.27&r2=1.45.2.28&only_with_tag=SAMBA_2_2
It's twice the same link, Buchan, but I can understand
the message.
>[f]ixes this. But I don't see a patch in cvs to
>source/rpc_server/srv_spoolss_nt.c that relates to 
>this. So is the fix above sufficient?
There are really 2 bugs. One affects the enumdriver
subcommand and is resolved with the patch you quoted. 
The other is burried deeper in the invocation of 
sys_adminlog and affects the adddriver or setdrivers
subcommand, I'm not sure which anymore. Since I 
considered it somehow superfluous, I extended the 
comment /* BEGIN_ADMIN_LOG */ up to the comment
/* END_ADMIN_LOG */ to include the whole switch loop.

The actual maintainer might have fixed the underlying
defect. I just killed what seemed superfluous to me.
>> Which is really interesting. Can you look up the 
>> section cited in my patch file to see whether 
>> Mandrake patched it on their own or the patch is 
>> already in cvs without a link to it in bugzilla?
>No, we didn't have a patch for this (although you can 
>check for yourself in cvs at 
> http://cvs.mandrakesoft.com/cgi-bin/cvsweb.cgi/SPECS/samba
Huh? I never used cvs. I've administered a big 
ClearCase multi-site but I never touched cvs. Sorry.
>>>So, unless I see an official patch list for 2.2.8a 
>>>(or there is a new release, maybe also fixing the 
>>>problem with cups printers not appearing without a 
>>>restart of smbd) or a transparent way of finding 
>>>which patches should be applied, I won't rebuild 
>>>packages for 5 releases.
>> You're under no obligation to do anything, 
>> especially if you don't have the problem. Your name 
>> just popped up in a thread I shared with Jim for 
>> some reason and I didn't remove it from later 
>> correspondence.
>
>Well, I maintain samba/samba3 in Mandrake, 
How do you do, Mr. Milne?
>and a number of people have implied that there are 
>patches for 2.2.8a which should be applied (and I
>would like to see the one for the cups printer list 
>myself) ... but there is no list available of those 
>that should be applied ... so distributors must guess 
>from cvs logs what should be applied (which IMHO
>is not the ideal situation for the samba team if they 
>want their software to work out-the-box on the 
>majority of deployments). And with a potential switch 
>to samba-3.0.0 just before the upcoming 9.2, I would
>prefer not to have to go chasing after patches for 
>2.2.8a (I have enough to test with samba3).
I can sympathize with samba team that they're too busy
following up on 3.betas but at the same time, this 
kind of bug can't be ignored. It's making people 
almost criminally insane. Someone was yelling
"How I HATE samba printing" right in his subject line.

I should have fixed it earlier, since it first didn't
abide by the documentation in 2.2.5, but it was so much
easier to kludge the clients to live with it.


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005