[Bug 57510] New: Printers recognised but can't be used - crash in winedvm
https://bugs.winehq.org/show_bug.cgi?id=57510 Bug ID: 57510 Summary: Printers recognised but can't be used - crash in winedvm Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: michael.lager(a)gmx.com Distribution: --- Created attachment 77543 --> https://bugs.winehq.org/attachment.cgi?id=77543 Wine's error report Using MYOB.exe (MYOB 6 from Personal Computer World free CD of October 1998 needing "Windows 3.1 or later on at least a Pentium PC with at least 16Mb of memory") after years of being able to print from within this program, recently having had to freshly install Ubuntu 22.04 and upgrade to 24.04.1, and using Wine 9.0~repack-4build3, repeatedly the pwogram crashed with the erro "winedvm.exe has experienced a serious problem and needs to close", and does so. All system printers are on offer within MYOB 6 but without the usual options and ongoing failure to do any printing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57510 --- Comment #1 from Rafał Mużyło <galtgendo(a)o2.pl> --- Attach full console output from the program (perhaps with 'commdlg' debug channel). Also, state clearly which version of wine was working for you. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57510 --- Comment #2 from Andrew Nguyen <arethusa26(a)gmail.com> --- I couldn't reproduce a crash with wine-10.0-rc1 using the "Test Drive v6.0.5" version of MYOB that I installed from https://archive.org/details/pcwjan98. When I started the app and selected the "Open a Sample Set of Books to Explore M.Y.O.B." button, I tried printing by selecting the File -> Print menu item and pressing the Print button in the "Index to Reports" window. After selecting OK in the "Report Filters" dialog and then OK in the "Print" dialog, the application successfully prints to the default CUPS PDF printer. I was also unable to reproduce a crash with wine-9.0. Can you please provide some instructions on how to replicate the issue? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57510 --- Comment #3 from michael.lager(a)gmx.com --- (In reply to Rafał Mużyło from comment #1)
Attach full console output from the program (perhaps with 'commdlg' debug channel).
Also, state clearly which version of wine was working for you.
Thanks, but I'll need to work through how to get this information to you, which will take appreciable time. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57510 --- Comment #4 from michael.lager(a)gmx.com --- Created attachment 77567 --> https://bugs.winehq.org/attachment.cgi?id=77567 MYOB 6 for comparison Thanks for your help: are we using the same MYOB 6 version as mine is on a PCW CD which is red without pictures and labelled “October issue Volume 21 No 10? I attach the installation files for MYOB 6 from my PCW disk dated October which may help. The files for v6.0.5 are not the same as for MYOB 6 . Anyway, trying to install it failed at “myob.exe” flagging up “winevdm.exe” as not responding some 18% through the installation. Incidentally I think it may not be a Wine issue at all as the same behaviour happens using Virtualbox 7 hosting Windows 7 where nothing prints. I’ve reinstalled almost everything especially CUPS and the printers, which work from my Ubuntu 24.04.1. I don't know where next to look. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57510 --- Comment #5 from Andrew Nguyen <arethusa26(a)gmail.com> --- The hang you observed with the installer is a regression that was reported in bug 57384 and is fixed in wine-10.0-rc2. I could not reproduce the crash you originally reported with your version of MYOB 6, neither with wine-9.0 nor wine-10.0-rc2. Looking at the backtrace that was originally attached, the crash is due to a null pointer dereference of the print dialog internal value PrintStructures->lpDevMode. As far as I can tell, this can only happen if the dialog believes there are printers available, but it is unable for whatever reason to query information about a printer to be selected in the dialog. Are you able to print in other applications under Wine (e.g., the builtin Wine notepad)? If you continue to experience the crash with MYOB 6, it would be helpful if you can attach debug output from Wine (see https://gitlab.winehq.org/wine/wine/-/wikis/FAQ#how-can-i-get-a-debugging-lo...), perhaps starting with WINEDEBUG=+commdlg,+winspool debug channels. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57510 --- Comment #6 from michael.lager(a)gmx.com --- Created attachment 77622 --> https://bugs.winehq.org/attachment.cgi?id=77622 Notepad crash back trace Notepad.exe crashed as soon as I tried to print. Available printers were recognised, but did not respond when selected (even pdf). The work-around may well be to use a laptop with Windows and installing MYOB6 on it, which I have yet to try. The laptop is a dual boot with Ubuntu and Windows 11 but this may prove a dead end. I now have wine-10.0-rc2 where the problem remains with all installed printers. The only common factor between Wine and Virtualbox is the cups system which works otherwise. Or could there be a permissions issue? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57510 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal Version|unspecified |10.0-rc1 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57510 --- Comment #7 from michael.lager(a)gmx.com --- Created attachment 77974 --> https://bugs.winehq.org/attachment.cgi?id=77974 debug report as requested In reply to comment 5: Now on wine 10.0-noble-1. No change in problem. Debug report attached as "wineDEBUG.txt" resulting from "WINEDEBUG=+commdlg,+winspool,+debug,+channels wine .wine/drive_c/MYOB6/MYOB.EXE /home/boss/accounts.dat>>/tmp/wineDEBUG.txt 2>&1". I now realise I should have replace "+channels" with "+all". My user name is "boss", and the data is in "accounts.dat". The screen output from the debugging command was normal except that MYOB reported "abort" as not a MYOB file, It was then restarted and went through normally until again not printing a report. The available printers were found but in the debug report file I noticed towards the end a line reading "01e4:warn:winspool:get_config_module Could not load L"C:\\windows\\system32\\spool\\drivers\\win40\\3\\wineps16.drv". If you are able to suggest what to do I'd be very grateful. Michael -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla