Bug 643 - Problems saving printing preferences to samba hosted server
Problems saving printing preferences to samba hosted server
Product: Samba 3.0
Classification: Unclassified
Component: Printing
All Windows 2000
: P3 normal
: none
Assigned To: Gerald (Jerry) Carter
Depends on:
  Show dependency treegraph
Reported: 2003-10-17 13:41 UTC by Evan Harris
Modified: 2005-11-14 09:28 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Evan Harris 2003-10-17 13:41:28 UTC
After installing the drivers for HP laserjet printers on a samba server via
Win2k client, everything seems to go fine until I go to Properties->Advanced and
try to enable "Enable Advanced Printing Features".  I check it, and it seems to
apply, but next time the properties is opened, it is cleared again.  It appears
to behave the same using a WinXP client.

Without this, I am unable to to use duplexing and other "advanced" features
(even though they are installed in the "Device Settings".

I have followed the instructions for setting valid device modes as described at:
specifically, going to the "Printing Defaults..." screen and changing the page
orientation (with applies between changes as instructed).

I am running under a printer admin account and am doing this from the same
machine I installed the drivers as.

I am happy to provide any additional information in tracking this down.
Comment 1 Gerald (Jerry) Carter 2003-11-04 20:22:22 UTC
The "Enable Advanced Printing Features" checkbox enables 
server side rendering of print jobs.  Samba cannot support
this due to the requirement of running win32 code.  Therefore
that checkbox is always disabled.  

The bug as reported is actually behavior by design.
However, most print drivers still support duplexing
and other similar features when using client side 

Contact me directly if you think you have a bug 
before we reopen this.
Comment 2 Gerald (Jerry) Carter 2003-11-13 19:24:35 UTC
this was a real bug
Comment 3 Gerald (Jerry) Carter 2003-11-13 19:24:48 UTC
This was actually a duplicate of bug 338 and will 
be fixed in 3.0.1pre3.  Sorry for the confusion.
Comment 4 Gerald (Jerry) Carter 2005-08-24 10:18:02 UTC
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.
Comment 5 Gerald (Jerry) Carter 2005-11-14 09:28:22 UTC
database cleanup