Bug 3606 - Fiery X3e driver halt MS applications
Fiery X3e driver halt MS applications
Product: Samba 3.0
Classification: Unclassified
Component: Printing
Other Windows 2000
: P3 normal
: none
Assigned To: Gerald (Jerry) Carter
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2006-03-14 10:03 UTC by Joanna Chan
Modified: 2006-03-16 16:46 UTC (History)
0 users

See Also:

driverInstllWarn (57.38 KB, application/x-zip-compressed)
2006-03-14 10:05 UTC, Joanna Chan
no flags Details
driverInstalled (55.95 KB, application/x-zip-compressed)
2006-03-14 10:06 UTC, Joanna Chan
no flags Details
samba logs (27.66 KB, application/x-zip-compressed)
2006-03-14 15:02 UTC, Joanna Chan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joanna Chan 2006-03-14 10:03:47 UTC
Using CUPS 1.1.17 to create a print queue for printer IKON BusinessPro 500c.
The driver for the printer is supplied by the vendor (see attachment 1 [details]).

Installed the driver to the print$ share as normal.  Got the warning about XP compatiablity (see attachment 2 [details]).  Clicked 'Continue' on the warning.  The driver was installed successfully (see attachment 3 [details]).

Add the printer to a client machine using the APW, set that printer as the default.  Then, open the Word application and do 'File -> Print'.  Nothing was returned for more than 5 minutes.  Need to 'End Process' on that application.  The same thing happened on Excel.

Note that the driver comes with a EFI Job Monitor that run on the Windows client and start automatically.  Not sure if this is causing any problem
Comment 1 Joanna Chan 2006-03-14 10:05:46 UTC
Created attachment 1795 [details]
Comment 2 Joanna Chan 2006-03-14 10:06:21 UTC
Created attachment 1796 [details]
Comment 3 Joanna Chan 2006-03-14 10:50:42 UTC
Cannot attached the driver so please use this link to get that:

Attachment 1 [details] becomes the warning message and Attachement 2 is the driver installed success screen
Comment 4 Joanna Chan 2006-03-14 15:02:19 UTC
Created attachment 1797 [details]
samba logs

Contains the debug level 10 samba log when right-click on the print queue from a windows client machine mapped to the Printer & Faxes folder.
Comment 5 Gerald (Jerry) Carter 2006-03-16 07:37:03 UTC
trying to reproduce locally
Comment 6 Gerald (Jerry) Carter 2006-03-16 16:46:14 UTC
I believe this is the same buggy driver family that doesn't 
NULL terminate certain printer data and just happens to work 
against Windows since the server zero's the additional 
memory.  I can reproduce the same 'properties not sticking
bug against Samba' while the same operation works against 
a remote Windows 2000 server.

It would take a while to track.  The only way I found it before 
was with help from Konica printer driver engineers.  You could 
probably get the information you needed to convince the relevant
parties by simply comparing the enumerated printer data from 
Samba and Windows.

My advice is to see if you can find a newer version of the 
driver.  I know their engineers had a new version and that was
probably a year ago.  There's not much we can do about this
from Samba's perspective.