[Bug 48716] New: Logos Bible Software - Printer is recognized but will not print (WPF Related?)
https://bugs.winehq.org/show_bug.cgi?id=48716 Bug ID: 48716 Summary: Logos Bible Software - Printer is recognized but will not print (WPF Related?) Product: Wine Version: 5.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: franksauer(a)cox.net Distribution: --- One of the Engineers from Logos responded to the exact issue here: https://community.logos.com/forums/t/62338.aspx There is no crash when the Print button is clicked - just no response or sending to the printer. I have tried multiple printers and PDF - Notepad in the same Prefix prints without 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=48716 Frank <franksauer(a)cox.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |franksauer(a)cox.net -- 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=48716 Frank <franksauer(a)cox.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu -- 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=48716 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://downloads.logoscdn. | |com/LBS8/Installer/8.7.0.00 | |39/Logos-x86.msi Keywords| |dotnet, download Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC| |xerox.xerox2000x(a)gmail.com --- Comment #1 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Hi, I think I cannot test this properly as I have no printer installed , but according to the console output*** there seems to be some activities on cvs list: https://www.winehq.org/pipermail/wine-cvs/2020-June/145435.html console output Logos while trying to print: 015c:fixme:prntvpt:PTOpenProviderEx L"PDF", 1, 1, 000000000051D930, 000000000ADA26C8: stub So could you retest next week in upcoming wine-5.11 (or update to current git if you compile wine from source) Regards -- 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=48716 --- Comment #2 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- On second thought I think we should just resolve this as fixed, and track next problems in new bugreports In current git I get: unimplemented function prntvpt.dll.PTConvertDevModeToPrintTicket called in 64-bit code I applied pending patch on devel-list https://www.winehq.org/pipermail/wine-devel/2020-June/168008.html Then I get: Call from 0x7b01133e to unimplemented function prntvpt.dll.PTGetPrintCapabilities, aborting -- 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=48716 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Logos Bible Software - |Logos Bible Software - |Printer is recognized but |Printer is recognized but |will not print (WPF |will not print |Related?) |(PTOpenProviderEx is a | |stub) Resolution|--- |FIXED Status|NEW |RESOLVED Fixed by SHA1| |645d909b28b29970af220d5d241 | |ac8b5c5add38e --- Comment #3 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- I resolve this; @Frank: could you open new bugreport for the behaviour of Logos once you`re able to test (with upcominig wine-5.11). (Don`t forget to include console output) Thanks Fixed by 645d909b28b29970af220d5d241ac8b5c5add38e Thanks Dmitry -- 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=48716 --- Comment #4 from Frank <franksauer(a)cox.net> --- Thanks! I will give it a try when the update comes out -- 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=48716 --- Comment #5 from Frank <franksauer(a)cox.net> --- @Louis - is there any way to build a Wine update with your patch? I don't have a lot of experience in building from source. I did build the original Logos Wine setup per the instructions that were listed in the Google Doc John and Rik had setup. I'm willing to give it a try, but would prefer to not have to reinstall everything again. I don't mind waiting for the Wine repos to be updated, but am willing to try building the update if possible. I've only seen the Git instructions on here and that seems to imply needed a new install. -- 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=48716 --- Comment #6 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- (In reply to Frank from comment #5)
@Louis - is there any way to build a Wine update with your patch? I don't have a lot of experience in building from source. I did build the original Logos Wine setup per the instructions that were listed in the Google Doc John and Rik had setup.
I'm willing to give it a try, but would prefer to not have to reinstall everything again.
I don't mind waiting for the Wine repos to be updated, but am willing to try building the update if possible. I've only seen the Git instructions on here and that seems to imply needed a new install.
Hi Frank, I didn't make patches at all, I just tested patches that were made by wine-developer on the wine-devel mailinglist Anyway, those patches are in wine now, so if you test with upcoming wine-5.11 there should be a different behaviour/hopefully some improvement I`d guess, though I`m not sure if printing already works. For further bugs please open new bugreports. About your question of building wine:It`s documented here https://wiki.winehq.org/Building_Wine I don`t know what you mean with "seems to imply needed a new install." but if you build wine yourself, you can run Logos out of the wine-build-tree so you don`t have to reinstall Logos -- 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=48716 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 5.11. -- 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=48716 --- Comment #8 from Frank <franksauer(a)cox.net> --- Created attachment 67496 --> https://bugs.winehq.org/attachment.cgi?id=67496 Issue is Confirmed Fixed Installed 5.11 and printing is now functional - THANK YOU!!! Also attached the image to show that the "Page" module still shows an error - BUT for those who would assume that it means it will not print - it does indeed print without problem with Wine 5.11 -- 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=48716 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1|645d909b28b29970af220d5d241 |9f2512d836cc62204c7ef61b661 |ac8b5c5add38e |a02682ecb34c0 CC| |mstefani(a)winehq.org --- Comment #9 from Michael Stefaniuc <mstefani(a)winehq.org> --- There were no follow up bugs opened as 5.11 worked for the OP. As 9f2512d836cc62204c7ef61b661a02682ecb34c0 implements prntvpt.dll.PTGetPrintCapabilities and gets the application to print I've changed the fixed by to that. No change to the release notes as both 645d909b28b29970af220d5d241ac8b5c5add38e and 9f2512d836cc62204c7ef61b661a02682ecb34c0 were implemented in 5.11. -- 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=48716 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |printing Summary|Logos Bible Software - |Logos 8 Bible Software |Printer is recognized but |(.NET 4.7 app): Printer is |will not print |recognized but will not |(PTOpenProviderEx is a |print (PTOpenProviderEx is |stub) |a stub) CC| |focht(a)gmx.net URL|https://downloads.logoscdn. |https://web.archive.org/web |com/LBS8/Installer/8.7.0.00 |/20210209172851/https://dow |39/Logos-x86.msi |nloads.logoscdn.com/LBS8/In | |staller/8.7.0.0039/Logos-x8 | |6.msi -- 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=48716 --- Comment #10 from Frank <franksauer(a)cox.net> --- Looks like this issue may be back in Logos 9 https://bugs.winehq.org/show_bug.cgi?id=51853 -- 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=48716 --- Comment #11 from Frank <franksauer(a)cox.net> --- Any chance that the patch that allowed this to work for Win7, could be applied in any manner to allow the same issue to be fixed with Win10 set? -- 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