cupsaddsmb cannot find cups printers

[Markus Durzinsky]

Thanks, I could solve the problem now.

> > Everytime when samba is started, I get the following lines in log/cups/access_log:
> >
> > xi - - [11/Jan/2008:18:19:35 -0100] "POST / HTTP/1.1" 200 134 CUPS-Get-Printers client-error-bad-request
> > xi - - [11/Jan/2008:18:19:35 -0100] "POST / HTTP/1.1" 200 134 CUPS-Get-Classes client-error-bad-request
> > xi - - [11/Jan/2008:18:19:35 -0100] "POST / HTTP/1.1" 200 134 CUPS-Get-Printers client-error-bad-request
> > xi - - [11/Jan/2008:18:19:35 -0100] "POST / HTTP/1.1" 200 134 CUPS-Get-Classes client-error-bad-request
> >
> > and those in log/cups/error_log:
> >
> > E [11/Jan/2008:18:19:35 -0100] Unsupported character set "iso-8859-1"!
> > E [11/Jan/2008:18:19:35 -0100] Unsupported character set "iso-8859-1"!
> > E [11/Jan/2008:18:19:35 -0100] Unsupported character set "iso-8859-1"!
> > E [11/Jan/2008:18:19:35 -0100] Unsupported character set "iso-8859-1"!
>
> I cannot say anything regarding the cupsaddsmb stuff - we have switched over
> to an inf file based printer installation on Windows boxes a couple of months ago.
>
> But as for the bad character set: you need to configure your samba tu use UTF-8 as
> the unix character set because starting with 1.3.x, CUPS only accepts IPP requests
> which specify utf-8 as the character set.
>
> Helge

There is an environment variable LC_CTYPE on my system set to iso_8859_1, which I suppose samba is using in cupsLangDefault() and for all cupsDoRequest(...) calls.  Setting it to UTF-8 (just for starting the smbd) lets samba communicate with cups successfully.

localhost - - [14/Jan/2008:14:59:12 -0100] "POST / HTTP/1.1" 200 129 CUPS-Get-Printers successful-ok
localhost - - [14/Jan/2008:14:59:12 -0100] "POST / HTTP/1.1" 200 129 CUPS-Get-Classes successful-ok

And the cupsaddsmb is also working fine.