http://bugs.winehq.org/show_bug.cgi?id=9591
Summary: Print to default laser printer in FoxPro fails and shuts down application Product: Wine Version: unspecified Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: wine-misc AssignedTo: wine-bugs@winehq.org ReportedBy: wb4ubd@yahoo.com
Created an attachment (id=7966) --> (http://bugs.winehq.org/attachment.cgi?id=7966) Backtraces for FoxPro errors
In FoxPro whether running an application or using the "command" level, sending a print command to a default network laser printer results in no print and a shutdown of FoxPro and its application (if used). If CUPS-PDF is used as the default printer, a pdf file is generated and the FoxPro application remains active (does not shutdown).
The backtrace report includes comment lines in brackets for the two scenarios.
I have also observed that while in the "command" level of FoxPro, merely the selection of the laser printer in Print Setup or having the laser printer as default and entering Print Setup will shutdown the application.
http://bugs.winehq.org/show_bug.cgi?id=9591
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com
--- Comment #1 from Dan Kegel dank@kegel.com 2007-09-05 16:14:34 --- Can you reproduce with a Wine that has debug info, so we can see line numbers? Alternately, can you point us to a freely downloadable app that reproduces the problem? (e.g. can you make a trivial foxpro app that immediately tries to print and crashes, with no user interaction?)
http://bugs.winehq.org/show_bug.cgi?id=9591
Detlef Riekenberg wine.dev@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wine.dev@web.de
--- Comment #2 from Detlef Riekenberg wine.dev@web.de 2007-09-05 16:56:17 --- Your wine has no Debug-Informations.
Please use an official Package (or build wine from source with debug-symbols) and attach ~1000 lines from the logfile around the crash:
WINEDEBUG="+commdlg,+winspool,+print,+driver,+loaddll" wine yourapp.exe 2>&1 | tee logfile.txt
(all of the above command in one line)
Thanks
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #3 from Jim wb4ubd@yahoo.com 2007-09-05 18:17:19 --- Created an attachment (id=7968) --> (http://bugs.winehq.org/attachment.cgi?id=7968) FoxPro test print app
This simple app will be compiled as an fxp file the first time it's run in FoxPro. The system would not let me attach the compiled file.
All the app does is turn the printer on, print a simple line of text and turn the printer off. On my system, it will crash FoxPro/wine with my laser printer and photo printer. It will operate properly with CUPS-PDF and FaxPrint under E-fax.
I am using wine version 0.9.44 that is made available through the Ubuntu repositories. I opted to generate the three line FoxPro app because that was a much simpler route than removing the Ubuntu package and recompiling an "official" version.
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #4 from Dan Kegel dank@kegel.com 2007-09-06 08:49:26 --- I assume the .exe attachment was rejected because it was larger than a megabyte. Can you try compressing it with bzip2 and check the size? If that's larger than a megabyte, try compressing instead with rzip (http://rzip.samba.org) and check the size again. Once you get it under a megabyte, try attaching it again.
Or use a service like yousendit.com... thanks!
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #7966 is|0 |1 obsolete| | Attachment #7968 is|0 |1 obsolete| |
--- Comment #5 from Jim wb4ubd@yahoo.com 2007-09-06 10:35:18 --- Created an attachment (id=7974) --> (http://bugs.winehq.org/attachment.cgi?id=7974) Simple FoxPro app to test print function
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #6 from Jim wb4ubd@yahoo.com 2007-09-06 10:39:15 --- I presume that you have a copy of FoxPro to run the app in. I don't have the means (FoxPro tools) to generate a standalone executable. Size wasn't the problem ... both the source and compiled app are less than 1K.
http://bugs.winehq.org/show_bug.cgi?id=9591
Detlef Riekenberg wine.dev@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|minor |normal
--- Comment #7 from Detlef Riekenberg wine.dev@web.de 2007-09-06 16:30:58 --- I do not have FoxPro, so I can't test your demo-application.
I can't find the correct Error-Location without the log from comment #2.
All official packages should include the debug-symbols.
Please tell me the URL, where you get your Package. (Ubuntu version and wine version)
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #8 from Jim wb4ubd@yahoo.com 2007-09-06 17:03:19 --- Sorry you don't have FoxPro to test with. I had forgotten, but I must've set up WineHq in the repository list for the Synaptic Package Manager. The URL listed for the repository site is: http://wine.budgetdedicated.com/apt The installed version listed in the Package Manager is: 0.9.44~winehq0~ubuntu~7.04-1
From the above info, it looks like it should be an official package.
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #9 from Jim wb4ubd@yahoo.com 2007-09-06 17:44:53 --- Created an attachment (id=7978) --> (http://bugs.winehq.org/attachment.cgi?id=7978) Trace data after running WINEDEBUG as requested.
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #10 from Jim wb4ubd@yahoo.com 2007-09-06 17:46:06 --- Detlef ....
I finally got a trace working. I ran the little test program putting both in the same subdirectory and got the attached data. Hope this is what you were looking for.
Jim
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #7974 is|0 |1 obsolete| | Attachment #7978 is|0 |1 obsolete| |
--- Comment #11 from Jim wb4ubd@yahoo.com 2007-09-15 11:50:08 --- Created an attachment (id=8083) --> (http://bugs.winehq.org/attachment.cgi?id=8083) Debug Trace with Wine v0.9.45
Running the test app in FoxPro with Wine v0.9.45, FoxPro did not shutdown in the crash, it only locked up. Test line still does not print with the default network laser printer, but , as before, it does create a pdf file with the virtual printer.
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #8083 is|0 |1 obsolete| |
--- Comment #12 from Jim wb4ubd@yahoo.com 2007-09-29 17:04:37 --- Created an attachment (id=8296) --> (http://bugs.winehq.org/attachment.cgi?id=8296) V0.9.46 backtrace file with Test app
No change with Wine version 0.9.46
http://bugs.winehq.org/show_bug.cgi?id=9591
Detlef Riekenberg wine.dev@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #13 from Detlef Riekenberg wine.dev@web.de 2007-10-14 08:10:23 ---
From your log:
trace:winspool:WINSPOOL_GetStringFromReg L"Port": "LPR:LaserJet" trace:winspool:WINSPOOL_GetStringFromReg L"Printer Driver": "PS Driver" ----------------------------------------------------------------------
You have an old ~/.wine directory where all Printers used "PS Driver". (created before wine-0.9.25, which was released on 10. Nov. 2006).
As a workaround, when you still want to use your old Installation, use "wine regedit.exe" and delete all this key to remove all Printers: "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Printers"
Wine rebuild the new registry-entries, when needed.
(cups-pdf works, because wine created the new style registry-entries, when cups-pdf was detected first.)
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #8296 is|0 |1 obsolete| |
--- Comment #14 from Jim wb4ubd@yahoo.com 2007-10-15 13:56:19 --- Created an attachment (id=8593) --> (http://bugs.winehq.org/attachment.cgi?id=8593) Backtrace file after registry change
I removed the registry entries for the LaserJet and PhotoPrint printers and let wine rebuild the entries. FoxPro doesn't crash when the test application (and the original real application), but there is still no printing to either of the printers. FoxPro comes up with the error "Printer not ready". So we are closer, but still not there.
The only difference between the printers that work and those that do not work are that the non-working printers (LaserJet and PhotoPrint) are network printers and the working printers (FaxPrint and PDF_File) are virtual printers.
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #8593 is|0 |1 obsolete| |
--- Comment #15 from Jim wb4ubd@yahoo.com 2007-10-24 08:21:08 --- Created an attachment (id=8742) --> (http://bugs.winehq.org/attachment.cgi?id=8742) Backtrace after Gutsy upgrade
Now with Ubuntu Gutsy (v7.10) we are back to NO printers working - even the virtual printers. FoxPro displays the "Printer Not ready" error with any attempt to print.
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|FIXED |
--- Comment #16 from Jim wb4ubd@yahoo.com 2007-10-24 08:24:57 --- Wine 0.9.47 v- refer to comments #14 & #15
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #8742 is|0 |1 obsolete| |
--- Comment #17 from Jim wb4ubd@yahoo.com 2007-10-31 08:50:00 --- Created an attachment (id=8890) --> (http://bugs.winehq.org/attachment.cgi?id=8890) Logfile after update to Wine 0.9.48
No change in symptoms with new version of Wine.
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #8890 is|0 |1 obsolete| |
--- Comment #18 from Jim wb4ubd@yahoo.com 2007-11-10 13:49:06 --- Created an attachment (id=9084) --> (http://bugs.winehq.org/attachment.cgi?id=9084) Backtrace after update to Wine 0.9.49
No change from previous version.
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #19 from Jim wb4ubd@yahoo.com 2007-12-02 13:35:40 --- Created an attachment (id=9462) --> (http://bugs.winehq.org/attachment.cgi?id=9462) Backtrace file with v0.9.50
Backtrace after update to Wine 0.9.50
No change from previous versions. All printers not recognized by FoxPro.
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #9084 is|0 |1 obsolete| | Attachment #9462 is|0 |1 obsolete| |
--- Comment #20 from Jim wb4ubd@yahoo.com 2007-12-15 09:47:44 --- Created an attachment (id=9634) --> (http://bugs.winehq.org/attachment.cgi?id=9634) Backtracr file for v0.9.51
All printers continue to not be recognized with FoxPro for Windows running under Wine.
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #9634 is|0 |1 obsolete| |
--- Comment #21 from Jim wb4ubd@yahoo.com 2007-12-29 17:03:06 --- Created an attachment (id=9890) --> (http://bugs.winehq.org/attachment.cgi?id=9890) traces for v0.9.52
Same as before. These submittals seem to be an exercise in futility.
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #9890 is|0 |1 obsolete| |
--- Comment #22 from Jim wb4ubd@yahoo.com 2008-01-12 08:25:47 --- Created an attachment (id=10185) --> (http://bugs.winehq.org/attachment.cgi?id=10185) trace for 0.9.53
doesn't work with 0.9.53 either
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |ABANDONED
--- Comment #23 from Jim wb4ubd@yahoo.com 2008-02-18 17:55:16 --- No printers will work with this application even under Wine v0.9.55. It appears that the difficulty with printer recognition by FoxPro for Windows started with the update to Ubuntu 7.10 - at least network printers and print to pdf worked quite well up to that point. The printers do work with other applications under Wine, but not FPW. Whether Apparmor or CUPS is the culprit in this problem, I don't know. I have tried disabling as well as removing Apparmor, but there was no change - the printers were still not recognized by FPW.
I changed the resolution of the bug to "abandoned" because it appears to me that there is no interest in resolving this bug.
http://bugs.winehq.org/show_bug.cgi?id=9591
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|ABANDONED |
--- Comment #24 from Dan Kegel dank@kegel.com 2008-02-18 18:05:15 --- Nah, it's not abandoned until nobody is left who cares about it.
Two questions: 1) does 'wine notepad' print ok?
2) can you figure out some way to get the compiled test app to us? For instance, maybe if you zip it, it will be small enough to attach.
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #25 from Jim wb4ubd@yahoo.com 2008-02-20 17:56:22 --- Forgot to mention .... it does print okay with wine notepad.
http://bugs.winehq.org/show_bug.cgi?id=9591
Mantas Kriaučiūnas mantas@akl.lt changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mantas@akl.lt
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #26 from Jim wb4ubd@yahoo.com 2008-04-27 21:00:48 --- v0.9.60 under Ubuntu 8.04 - we have totallty regressed to a non-working application in it's entirety. Attempting to execute FoxPro from terminal gives the messages:
preloader: Warning: failed to reserve range 00000000-00010000 preloader: Warning: failed to reserve range 00000000-00010000 winevdm: unable to exec 'C:\FPW26\FOXPROW.EXE': DOS memory range unavailable
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #27 from Dan Kegel dank@kegel.com 2008-04-27 21:32:25 --- You've just run into a known issue with the new kernel, see http://wiki.winehq.org/PreloaderPageZeroProblem for a workaround.
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #28 from Jim wb4ubd@yahoo.com 2008-04-28 07:29:13 --- Thanks, Dan. Works like a champ. Printer problems, however, remain even with this latest release.
http://bugs.winehq.org/show_bug.cgi?id=9591
ben bgitchel@arissolutions.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bgitchel@arissolutions.org
--- Comment #29 from ben bgitchel@arissolutions.org 2008-05-14 12:09:16 ---
(In reply to comment #28
I am having the same printing problem with Foxpro for Windows 2.6a. Current Wine rc 1.
http://bugs.winehq.org/show_bug.cgi?id=9591
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #30 from Lei Zhang thestig@google.com 2008-05-14 12:11:31 --- confirming then.
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #10185|0 |1 is obsolete| |
--- Comment #31 from Jim wb4ubd@yahoo.com 2008-05-31 15:35:14 --- Created an attachment (id=13539) --> (http://bugs.winehq.org/attachment.cgi?id=13539) trace file for wine v1.0-rc3
same lack of print problem with rc3.
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #32 from Jim wb4ubd@yahoo.com 2008-05-31 15:40:19 --- Created an attachment (id=13540) --> (http://bugs.winehq.org/attachment.cgi?id=13540) logfile from trace action
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #33 from Jim wb4ubd@yahoo.com 2008-10-10 08:36:41 --- -Nothing new with v1.1.5 - print function still does not work. Will create amd post revised trace file on request.
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #34 from Jim wb4ubd@yahoo.com 2008-11-22 10:25:51 --- No change with v1.1.9
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #35 from Jim wb4ubd@yahoo.com 2009-01-03 15:48:34 --- Same problem with v 1.1.12 - all printers fail to operate in FoxPro for Windows when operated under wine. Trace file can be provided upon request.
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #13539|0 |1 is obsolete| | Attachment #13540|0 |1 is obsolete| |
--- Comment #36 from Jim wb4ubd@yahoo.com 2009-05-12 16:52:19 --- Created an attachment (id=21060) --> (http://bugs.winehq.org/attachment.cgi?id=21060) Trace for v1.1.21
Wine continues to not allow printing with FoxPro - this latest version 1.1.21 now prevents FoxPro from running in its entirety indicating the "winevdm.exe has encountered a serious problem and needs to close". Okay ......
http://bugs.winehq.org/show_bug.cgi?id=9591
Oliver olischmid@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |olischmid@gmx.net
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #37 from Oliver olischmid@gmx.net 2009-09-05 11:16:56 --- Trace for v1.1.29
The problem printing from a FoxPro application is still present. I ran a debug with +winspool option, but I think this bug might be related to the 16bit application FoxPro. Printing from notepad works.
If I can not resolve this issue, I will have to revert to windows. Please let me know if I can provide you with details on how to resolve this.
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #38 from Oliver olischmid@gmx.net 2009-09-05 11:44:03 --- I found that when running a dump like suggested by Jim, i get the following error when I compare the notepad dump (printing works) with the foxpro dump:
trace:commdlg:PrintDlg16 exit!
Notepad loads the driver correctly:
trace:commdlg:PRINTDLG_WMCommandW OK button was hit trace:commdlg:PrintDlgW No hDevMode yet... Need to create my own trace:winspool:GetDefaultPrinterW L"Generic-text-only-printer,WINEPS.DRV,LPR:Generic-text-only-printer" trace:driver:DRIVER_GetDriverName Found L"WINEPS.DRV" for L"Generic-text-only-printer" trace:loaddll:load_builtin_dll Loaded L"C:\windows\system32\wineps.drv" at 0x7df90000: builtin
FoxPro gives this result:
trace:commdlg:PRINTDLG_WMCommandA OK button was hit trace:winspool:GetDefaultPrinterW L"Generic-text-only-printer,WINEPS.DRV,LPR:Generic-text-only-printer" trace:winspool:GetDefaultPrinterA 0x0000001a/0x00000104:L"Generic-text-only-printer" trace:commdlg:PrintDlg16 exit! (1)
Get back if I have more information.
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #39 from Dan Kegel dank@kegel.com 2009-09-05 13:25:16 --- Maybe somebody should test with a 16 bit notepad and see if that prints ok.
http://bugs.winehq.org/show_bug.cgi?id=9591
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |printing, win16
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #40 from Detlef Riekenberg wine.dev@web.de 2010-09-03 10:11:38 CDT --- Printing with a 16bit notepad works here.
Lots of changes where done in the last year.
Please retest.
http://bugs.winehq.org/show_bug.cgi?id=9591
Jim wb4ubd@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #21060|0 |1 is obsolete| |
--- Comment #41 from Jim wb4ubd@yahoo.com 2010-09-03 14:19:50 CDT --- Created an attachment (id=30533) --> (http://bugs.winehq.org/attachment.cgi?id=30533) Trace for the latest wine version in the Mepis repository
There is no change in the problem. The title of this bug should be "Print to Any Printer in FoxPro fails". Specifically, when any pront function is run whether in an application or at the command line (such as "Set Printer On"), the program rep[orts back an error of "Printer Not Ready". FoxPro Printer Setup appears to be correct (and normal).
I have since given up on using FoxPro in wine and for the past 2-3 years have been using FoxPro ubder WinXP in VirtualBox.
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #42 from Dan Kegel dank@kegel.com 2010-09-03 14:36:23 CDT --- Thanks for trying. What does wine --version say there? If it's lower than wine-1.2, you probably need to update.
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #43 from Jim wb4ubd@yahoo.com 2010-09-03 15:39:47 CDT --- It is version 1.1.38 - I have checked various updates over the past couple of years and there never is any deviation from the symptoms. Lately, I have been using the updates in the repository which is conservative in it's updating. If I have some leisure moments, I may try the latest stable version of wine and possibly even the development version. I'll report back the results when I do.
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #44 from Jim wb4ubd@yahoo.com 2010-09-09 21:10:33 CDT --- A recent update from the Mepis repository installed v1.3.2 - there is no difference - the print problem remains as described in comment 41.
http://bugs.winehq.org/show_bug.cgi?id=9591
butraxz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |butraxz@gmail.com
--- Comment #45 from butraxz@gmail.com 2012-05-17 14:51:22 CDT --- This bug has not been updated for two years. Is this still an issue i current (1.5.4) or newer wine ? You may also close this as abandoned if you feel that that this is issue is no longer relevant to you.
http://bugs.winehq.org/show_bug.cgi?id=9591
--- Comment #46 from Jim wb4ubd@yahoo.com 2012-05-17 15:32:54 CDT --- I have quit running FoxPro in wine and now use it in WinXP in a Virtual Machine.
http://bugs.winehq.org/show_bug.cgi?id=9591
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |ABANDONED
--- Comment #47 from Austin English austinenglish@gmail.com 2012-05-17 16:16:52 CDT --- Marking abandoned then.
http://bugs.winehq.org/show_bug.cgi?id=9591
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #48 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-05-31 07:06:21 CDT --- Closing ABANDONED bugs