If I try to upload printer drivers on the server via a Windows client, I get errors on several files ("can't copy"). E. g. "SN0HGC.DL_"
It seems that the file should be copied to the wrong directory:
[2010/05/20 19:44:03, 5] smbd/filename.c:564(unix_convert)
New file SN0HGC.DLL
[2010/05/20 19:44:03, 8] lib/util.c:1683(is_in_path)
[2010/05/20 19:44:03, 8] lib/util.c:1707(is_in_path)
is_in_path: match not found
[2010/05/20 19:44:03, 3] smbd/vfs.c:865(check_reduced_name)
reduce_name [W32X86/SN0HGC.DLL] [/shares/Printer]
[2010/05/20 19:44:03, 10] smbd/vfs.c:937(check_reduced_name)
reduce_name realpath [W32X86/SN0HGC.DLL] -> [/shares/Printer/W32X86/SN0HGC.DLL]
[2010/05/20 19:44:03, 3] smbd/vfs.c:974(check_reduced_name)
reduce_name: W32X86/SN0HGC.DLL reduced to /shares/Printer/W32X86/SN0HGC.DLL
[2010/05/20 19:44:03, 3] smbd/trans2.c:4050(call_trans2qfilepathinfo)
call_trans2qfilepathinfo: SMB_VFS_STAT of W32X86/SN0HGC.DLL failed (No such file or directory)
[2010/05/20 19:44:03, 3] smbd/error.c:153(reply_unix_error)
unix_error_packet: error string = No such file or directory
[2010/05/20 19:44:03, 3] smbd/error.c:60(error_packet_set)
error packet at smbd/trans2.c(4051) cmd=50 (SMBtrans2) NT_STATUS_OBJECT_NAME_NOT_FOUND
I tried uploading Sharp MX 2600n PS v.0909a driver.
Created attachment 5724 [details]
Level 10 debug log of the failed copy process
This bug is fixed in 3.5.4 (haven't tested 3.4.x any more).
Bug isn't fixed. I have the same problem in 3.5.6 on Debian Squeeze.
If I try to upload a driver over a Win2003 or WinXP Box, I always get a "access denied". Looking where it tries to store the files, they are put in W32X86 directly, not in W32X86/3 as described here.
If you need a complete log, i'll try to deliver it, also if you need smb.conf and/or cupsd.conf.
You are right. It still exists. I can confirm on 3.5.6 too.
I currently use 3.5.19 and updated printer drivers during the last 5 weeks (so 3.5.18 should be fine, too). And here I don't had any problems uploading drivers from XP and Win7.
I can successfully upload a driver for a new printer with 3.6.13. So it seems fixed in at least in the 3.6 tree (don't have 3.5 any more).
Im closing this bug report, as it works since 3.6.13