[Bug 51815] New: DocumentProperties broken by last update
https://bugs.winehq.org/show_bug.cgi?id=51815 Bug ID: 51815 Summary: DocumentProperties broken by last update Product: Wine Version: 6.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: spooler Assignee: wine-bugs(a)winehq.org Reporter: incubusrk(a)gmail.com Distribution: --- Last update cause DocumentProperties return -1 for existing printer. GetLastError return 193 For wine 6.17 and lower it's work correct -- 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=51815 --- Comment #1 from Konstantin <incubusrk(a)gmail.com> --- additional error info showed in console 01a4:err:winspool:DocumentPropertiesW Could not load config module for L"PRINTER_NAME" -- 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=51815 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression -- 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=51815 --- Comment #2 from Konstantin <incubusrk(a)gmail.com> --- Created attachment 70700 --> https://bugs.winehq.org/attachment.cgi?id=70700 Test win32 app source wchar_t wname[] = L"PDF"; int modeSize = DocumentPropertiesW(NULL, NULL, wname, NULL, NULL, 0); std::cout << "DocumentPropertiesW: " << modeSize << std::endl; std::cout << "GetLastError: " << GetLastError() << std::endl; -- 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=51815 Jacek Caban <jacek(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jacek(a)codeweavers.com --- Comment #3 from Jacek Caban <jacek(a)codeweavers.com> --- Please attach full +winspool debug output with an application that regressed. Your test case fails for me the same way on Windows and Wine because it depends on a printer named "PDF" be available. If I replace it with an actual printer name, it works. -- 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=51815 Esme Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd(a)gmail.com -- 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=51815 --- Comment #4 from Konstantin <incubusrk(a)gmail.com> --- Created attachment 70708 --> https://bugs.winehq.org/attachment.cgi?id=70708 logs with +winspool for wine-6.15 and wine-6.18 -- 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=51815 --- Comment #5 from Konstantin <incubusrk(a)gmail.com> --- Created attachment 70710 --> https://bugs.winehq.org/attachment.cgi?id=70710 fixed test case change hardcoded printer name to GetDefaultPrinterW -- 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=51815 --- Comment #6 from Esme Povirk <madewokherd(a)gmail.com> --- This came from the wine-mono report here: https://github.com/madewokherd/wine-mono/issues/120 I later found that the wine-mono tests also show this issue. x86_64.MonoTests.System.Drawing.Printing.PageSettingsTest:CloneTest fails, but x86.MonoTests.System.Drawing.Printing.PageSettingsTest:CloneTest succeeds. So it seems this is 64-bit specific somehow. The printer name it tries to use is definitely correct. A winspool log shows an error loading wineps.drv: 010c:warn:winspool:get_config_module Could not load L"C:\\windows\\system32\\spool\\drivers\\w32x86\\3\\wineps.drv" 010c:err:winspool:DocumentPropertiesW Could not load config module for L"Canon_MF731C_733C" So it seems the problem is that it tries to load 32-bit wineps.drv in a 64-bit process. -- 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=51815 Esme Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, source --- Comment #7 from Esme Povirk <madewokherd(a)gmail.com> --- The bug can be even more easily reproduced by running "wine64 notepad". Pressing the "Properties" button on the Print dialog fails, and other information in print-related dialogs aren't filled in. All of this works fine when running the 32-bit version with "wine notepad". -- 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=51815 Esme Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |testcase -- 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=51815 Esme Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |printing, win64 -- 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=51815 Konstantin <incubusrk(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|DocumentProperties broken |DocumentProperties broken |by last update |by last update (x64 only) -- 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=51815 Bernhard Übelacker <bernhardu(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhardu(a)mailbox.org --- Comment #8 from Bernhard Übelacker <bernhardu(a)mailbox.org> --- Created attachment 70734 --> https://bugs.winehq.org/attachment.cgi?id=70734 Return in a 64-bit process the x64 printer driver subdirectory. It looks like the validate_envW function returns currently for 64-bit processes the 32-bit driver subdirectory. This patch is an attempt to change this and seems to be at least for the "wine64 notepad" case an improvement. -- 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=51815 --- Comment #9 from Jacek Caban <jacek(a)codeweavers.com> --- Yes, it looks like we will need something like that. We should probably make it match setupapi: https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/setupapi/dirid.c#l48 -- 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=51815 --- Comment #10 from Esme Povirk <madewokherd(a)gmail.com> --- To match setupapi we're going to have to add a printenv_t for arm and arm64. Unsure if there are any other implications of this. -- 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=51815 --- Comment #11 from Esme Povirk <madewokherd(a)gmail.com> --- More importantly we'll need to know what to put in for envname, which I guess requires looking at the registry of a Windows on ARM system under HKLM\System\CurrentControlSet\control\Print\Environments. -- 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=51815 --- Comment #12 from Esme Povirk <madewokherd(a)gmail.com> --- Based on https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-rprn/e81cbc0... it seems "Windows ARM" is an environment name but that doesn't tell us which one to use for aarch64. -- 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=51815 --- Comment #13 from Esme Povirk <madewokherd(a)gmail.com> --- Well that's interesting. My (amd64) Windows box has a "Windows ARM64" environment in the registry, but not "Windows ARM". And it only has a version 4 driver for that, no version 3. But, version 4 may actually have some differences in the API, so it's probably not a good idea to switch to that until some application needs it. So even though it doesn't match real Windows, I think it makes sense to add a version 3 driver for both "Windows ARM" and "Windows ARM64" environments for now. -- 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=51815 --- Comment #14 from Esme Povirk <madewokherd(a)gmail.com> --- I sent patches: https://www.winehq.org/pipermail/wine-devel/2021-October/198617.html https://www.winehq.org/pipermail/wine-devel/2021-October/198618.html -- 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=51815 Esme Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Fixed by SHA1| |6e14766ad517cd8387c649d9958 | |f376fbcdc808c --- Comment #15 from Esme Povirk <madewokherd(a)gmail.com> --- Should be fixed in 6.20. -- 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=51815 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #16 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 6.21. -- 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