When printing with samba 3.0.6 under solaris 9 on a sun server the jobs are
printed and removed from the job queue as they should when finished, but the
jobs are still shown as documents being printed on the Windows clients. The
samba package was successfully compiled locally with gcc version 3.3.1. The
install was done as an upgrade to a running version of samba.2.2.8a. I would
really have liked somebody to compile a binary 3.0 version that was proven to
work properly under sun solaris.
Are the documents showing as "Spooling" in the windows print monitor ?
Created attachment 630 [details]
workaround parsing bug in print change notify code
do you use netbios aliases and include files to define printers ?
If so, please try tyhis second patch as a temporary workaround.
Created attachment 637 [details]
test case -- disable the backgroup print queue update daemon
In version 3.0.7 containing the proposed patch (id=630) the problem now seems
to have been resolved. However, the configure script gave warnings about not
being able to compile net/if.h, netinet/ip.h and security/pam_modules.h
(because being dependant on sys/socket.h, netinet/in.h and security/pam_appl.h
respectively). I don't know if this has any impact, but to be sure I made a
workaround for this by adding lines like
in the failing include files. This should of course be handled more
appropriately in the samba source suite. When compiling 3.0.6 those warnings
were ignored by me.
(In reply to comment #5)
> In version 3.0.7 containing the proposed patch (id=630) the problem now seems
> to have been resolved.
The problem still occurs on a debian woody (x86) machine with deb packages
version 3.0.7-1 from samba.org installed.
I'm afraid the problem is not fully resolved yet. Suddenly the document lists
again appeared to become not exhausted after jobs were printed. Most probably
this behaviour started when one of the printers failed for a period.
Temporarely resolved by clearing the lists manually and then restating smbd.
The queue update bug is fixed by
(which also fixes bug 1519). Suggest you test 3.0.7 after applying
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.