http://bugs.winehq.org/show_bug.cgi?id=10094
--- Comment #10 from antonv72@gmail.com 2007-10-23 01:39:11 --- (In reply to comment #9)
From the log: 0009:trace:winspool:OpenPrinterW (L"\\PINUS600\laserjet_2100_raw", 0x33e460, (nil)) 0009:trace:winspool:get_servername_from_name found L"PINUS600" 0009:fixme:winspool:get_opened_printer_entry server L"PINUS600" not supported 0009:trace:winspool:OpenPrinterW returning 0 with 1801 and (nil)
This is the reason for the fixme in the Description: The application is configured to print to "laserjet_2100_raw" on the server "PINUS600". Configure CUPS for this printer or configure the app to use a different printer to avoid this message. (The application does a fallback to the default printer later)
This is _very_ strange. I don't have a queue with that name anymore. It has been removed from CUPS years ago. I grep'ed for my homedir and /etc/cups and only the personal Thunderbird and Firefox configuration (prefs.js) matched. Those files have entries for most of our other obsolete queues/printers as well.
This is beyond the scope of Wine, but if somebody has a clue why these old queues still exist to Wine and others I'd gladly take any advice in order to fix that.
This is the issue, why you can't print now: The update changed the printing - dialog from PrintDlg (win3.x, win9x, NT: supported in wine) to PrintDlgEx (w2k and above: not implemented in wine yet. See bug #4342)
Closing this Dupe
Is there any workaround in order to get these apps to print? For instance can Wine answer PrintDlgEx related calls and offer PrintDlg type of functionality back? Or is it a "sorry, no printing for you at this time" situation?
Thanks for having time to look into this,