http://bugs.winehq.org/show_bug.cgi?id=25941
Summary: printing on OS/X fails cont... Product: Wine Version: 1.3.12 Platform: x86-64 OS/Version: Mac OS X 10.6 Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: daniel.price@monash.edu
This is to reopen the bug: http://bugs.winehq.org/show_bug.cgi?id=17354
I have a fresh install of MacPorts WINE-DEVEL 1.3.12, but printing *still* does not work on OS/X (I am running Snow Leopard 10.6.6). I checked to confirm that the macports package was configured with cups, as per the last entry on the bug above. However, still no printers are found by wine, so I don't think this is a macports problem (perhaps cups was disabled because it didn't work in the first place?).
I have followed most other things in that thread, e.g. changing the cups configuration to create the /etc/printcap file, but this didn't seem to fix anything (I deleted and recreated my .wine directory just to be sure the wine config had updated).
I made some progress following the steps at: http://www.witch.westfalen.de/Wine-HOWTO/wineprintconfig.html -- that is, I could get at least the print dialog box functioning (otherwise is greyed out, and get messages "no printer is installed" such as those discussed in the bug report above) by manually entering the register entries using regedit. However, I could not get it to work, with errors such as:
err:winspool:WINSPOOL_GetDriverInfoFromReg Can't find driver L"PS Driver" in registry err:winspool:WINSPOOL_GetDriverInfoFromReg Can't find driver L"PS Driver" in registry err:commdlg:PRINTDLG_ChangePrinterW GetPrinterDriverA failed for L"Wine Postscript Driver", fix your config! fixme:commdlg:PRINTDLG_UpdatePrintDlgW No lpdm ptr? fixme:commdlg:PRINTDLG_WMCommandW Update printdlg was not successful!
... and my feeling from reading the thread for bug 17354 was that it should not be that complicated.
Sorry I can't be more helpful than that, but I thought it would be worth re-flagging the issue as it does not seem to have been resolved by the fix to the Macports Portfile.
Cheers,
Daniel