The Samba-Bugzilla – Bug 144
Win ME Printing is completely broken
Last modified: 2005-02-07 07:57:32 UTC
No print queue is available in local printer, details, add port, browse.
Even with spoolss disabled and printing to a raw CUPS port, error bomb prevents
all printing. This is borked badly!
[2003/06/01 22:55:30, 3] smbd/ipc.c:reply_trans(512)
trans <\PIPE\LANMAN> data=0 params=50 setup=0
[2003/06/01 22:55:30, 3] smbd/ipc.c:named_pipe(326)
named pipe command on <LANMAN> name
[2003/06/01 22:55:30, 3] smbd/lanman.c:api_reply(3485)
Got API command 70 of form <zWrLh> <B13BWWWzzzzzWN>
[2003/06/01 22:55:30, 3] smbd/lanman.c:api_reply(3489)
[2003/06/01 22:55:30, 3] smbd/lanman.c:api_DosPrintQGetInfo(740)
api_DosPrintQGetInfo uLevel=2 name=RAW
[2003/06/01 22:55:30, 3] printing/printing.c:print_cache_expired(1723)
print cache expired for queue raw (last_qscan_time = 1054529719, time now =
1054529730, qcachetime = 10
[2003/06/01 22:55:30, 0] tdb/tdbutil.c:tdb_log(724)
tdb(/var/lib/samba/printing/raw.tdb): rec_free_read bad magic 0xc at offset=22048
[2003/06/01 22:55:30, 3] printing/print_generic.c:print_run_command(83)
Running the command `lpq -P'raw'' gave 0
[2003/06/01 22:55:30, 3] printing/printing.c:print_queue_update(1013)
0 jobs in queue for raw
[2003/06/01 22:55:30, 3] smbd/lanman.c:api_TooSmall(3380)
Supplied buffer too small in API command
[2003/06/01 22:55:32, 3] smbd/process.c:process_smb(882)
Transaction 188 of length 39
Created attachment 18 [details]
Example of Error Dialog on attempt to print to \\frodo\raw
Created attachment 19 [details]
Note Browsing for printers is broken
/var/lib/samba/printing/raw.tdb is corrupted. Stop smbd;
Remove the file; and try again.
I should have mentioned that I had already tried removal of the printing/*.tdb
This did not solve anything. The message follows deletion and re-try.
works flawlessly for me here. Using Samba_3_0
cvs from 2003-06-03. Can you mail me a full
level 10 debug log privately?
I deleted all my tdb files and printing files, set samba up again, now
everything works fine.
Bug report withdrawn - INVALID
Can not reproduce this problem now.
originally reported against 3.0aph24. Bugzilla spring cleaning.
Removing old alpha versions.