Bug 7263 - Unable to print using Samba 3.5.1 and cups-1.1.23-40.46 on SLES10
Unable to print using Samba 3.5.1 and cups-1.1.23-40.46 on SLES10
Product: Samba 3.5
Classification: Unclassified
Component: Printing
Other Linux
: P3 normal
: ---
Assigned To: Karolin Seeger
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2010-03-18 09:35 UTC by Carlos Eduardo Pedroza Santiviago
Modified: 2010-05-05 03:07 UTC (History)
2 users (show)

See Also:

smb.conf server configuration (2.70 KB, application/octet-stream)
2010-03-18 09:39 UTC, Carlos Eduardo Pedroza Santiviago
no flags Details
Fix cups encryption setting (878 bytes, patch)
2010-05-04 10:30 UTC, Luca Olivetti
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos Eduardo Pedroza Santiviago 2010-03-18 09:35:21 UTC
Also after upgrading to 3.5.1, using cups-1.1.23-40.46, we're unable to printer.

Samba logs reports:
[2010/03/18 11:27:49.776325,  0] printing/print_cups.c:108(cups_connect)
  Unable to connect to CUPS server localhost:631 - Success

And CUPS reports:

E [18/Mar/2010:11:31:58 -0300] Bad request line "��" from localhost!

Looks like they're not speaking the same language.
Comment 1 Carlos Eduardo Pedroza Santiviago 2010-03-18 09:39:39 UTC
Created attachment 5509 [details]
smb.conf server configuration
Comment 2 Carlos Eduardo Pedroza Santiviago 2010-03-18 09:43:36 UTC
Ways to reproduce:

1. Get a SLES10 Box with CUPS installed.
2. Upgrade samba to 3.5.1 from openSUSE repo.
3. Create a printer on CUPS
4. Install that printer on the client via SMB and try to print
Comment 3 Luca Olivetti 2010-05-04 10:30:46 UTC
Created attachment 5682 [details]
Fix cups encryption setting

I had the same problem and it's due to the fact that samba doesn't respect the "cups encryption" setting since lp_cups_encrypt changes the value: if you set "cups encryption=no", the first call will change it to HTTP_ENCRYPT_NEVER, since that is 1 (i.e. true), the next call will change it to HTTP_ENCRYPT_ALWAYS and after that it'll remain set as HTTP_ENCRYPT_ALWAYS.
This patch fixes this problem.
Comment 4 Björn Jacke 2010-05-04 11:18:14 UTC
looks good, thank you VERY much for finding that Luca!
Comment 5 Jeremy Allison 2010-05-04 17:11:12 UTC
+1 from me on this patch. Pushed to master. Re-assigning to Karolin for inclusion in 3.5.x.

Comment 6 Karolin Seeger 2010-05-05 03:07:24 UTC
Pushed to v3-5-test.
Closing out bug report.

Thanks a lot!