https://bugs.winehq.org/show_bug.cgi?id=47837
Bug ID: 47837 Summary: Intrusive graphics glitches .NET app - Logos Bible Software Product: Wine Version: 4.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: johnpgoodman@gmail.com Distribution: ---
It appears as if parts of the graphics buffer that are no longer needed get drawn back onto the screen quite a lot. You start viewing a different book. Suddenly you are looking at the previous one. Then it comes back.
WINEPREFIX=/home/john/wine-logos64/ WINEDEBUG=+wgl wine64 c:'/users/john/Local Settings/Application Data/Logos/Logos.exe' LC_ALL=C &>wine.log
Attached is a log file after running with the above command. I wonder if it is to do with graphics drivers and config? Perhaps someone knowledgable can suggest a workaround or config that will fix this? It makes the app very hard to use.
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #1 from m0rvj johnpgoodman@gmail.com --- Created attachment 65343 --> https://bugs.winehq.org/attachment.cgi?id=65343 Log from wine output with glitching - no crash
Due to large log size it is the result of 'uniq wine.log wine2.log' The two lines that repeated the many thousand times were: 0095:trace:wgl:glGetStringi (7939, 59) - last number increments 009c:trace:wgl:glxdrv_wglGetPixelFormat 0x190047 -> 1
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #2 from m0rvj johnpgoodman@gmail.com --- Turning off window decorations in winecfg seems to affect black box graphical glitches but not the buffer glitches.
https://bugs.winehq.org/show_bug.cgi?id=47837
Don Pobanz dpobanz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dpobanz@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=47837
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download CC| |xerox.xerox2000x@gmail.com Severity|major |normal
--- Comment #3 from Louis Lenders xerox.xerox2000x@gmail.com --- Hi
Personally I have not seen glitches while testing the program, but maybe one needs to have different books for it (to open and see glitsches)?????? Might be driver issue (???).
Does running with LIBGL_ALWAYS_SOFTWARE=1 change anything for you?
https://bugs.winehq.org/show_bug.cgi?id=47837
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |dotnet URL| |https://downloads.logoscdn. | |com/LBS8/Installer/8.7.0.00 | |39/Logos-x86.msi
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #4 from m0rvj johnpgoodman@gmail.com --- Tried with LIBGL_ALWAYS_SOFTWARE=1 and it was worse... I'm on a macbook pro late 2011 running kubuntu 19.04 with wine 4.17 and integrated graphics only. I'm so grateful for help with this. N.b. it is possible to build quite a collection of free books just from the store at logos.com and selecting price low to high. They also do a free book of the month.
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #5 from m0rvj johnpgoodman@gmail.com --- I wonder if you mind sharing what graphics card / window manager you are running with?
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #6 from Louis Lenders xerox.xerox2000x@gmail.com --- (In reply to m0rvj from comment #5)
I wonder if you mind sharing what graphics card / window manager you are running with?
02:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1) Desktop: LXDE Session: lightdm-xsession
Maybe worth a try for testing:
In the past for simple wpf-apps i remember one could disable d3d9, but that crashes Logos, a no go.
However from https://docs.microsoft.com/en-us/dotnet/framework/wpf/graphics-multimedia/gr...
I checked setting key HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DisableHWAcceleration to 1 seems to disable d3d9 (no d3d9 fixme`s in console output anymore) , maybe it helps (maybe it doesn`t) but might help to pinpoint where the troubles come from.
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #7 from m0rvj johnpgoodman@gmail.com --- Avalon.graphics isn't in my registry, is that to do with your graphics card?
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #8 from m0rvj johnpgoodman@gmail.com --- Should I be installing direct x or something?
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #9 from Louis Lenders xerox.xerox2000x@gmail.com --- (In reply to m0rvj from comment #8)
Should I be installing direct x or something?
No, just create the key HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DisableHWAcceleration and set it to 1
Regards
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #10 from m0rvj johnpgoodman@gmail.com --- enable DDR=GDI with winetricks Seems to be a complete fix. I was able to enable window decorations again too.
https://bugs.winehq.org/show_bug.cgi?id=47837
Rik Shaw rikshaw76@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rikshaw76@gmail.com
--- Comment #11 from Rik Shaw rikshaw76@gmail.com --- (In reply to m0rvj from comment #10)
enable DDR=GDI with winetricks Seems to be a complete fix. I was able to enable window decorations again too.
Same here: winetricks ddr=gdi solves all the "flashing", "buffering" problems and the interface works well now. Thanks for finding the fix.
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #12 from m0rvj johnpgoodman@gmail.com --- Even with drr=gdi these glitches are back from wine 5.1 onwards. This seems to be a quite big regression for us. 5.3 staging has working video which is a bit of a crown jewel for us so I want to try and pin down the regression. If we can we are on the way to gold.
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #13 from Louis Lenders xerox.xerox2000x@gmail.com --- (In reply to m0rvj from comment #12)
Even with drr=gdi these glitches are back from wine 5.1 onwards. This seems to be a quite big regression for us. 5.3
Hi m0rv, My guess is the "regression" is caused by commit: https://www.winehq.org/pipermail/wine-cvs/2020-January/141298.html
So winetricks is really at fault here i think; it should set the key HKEY_CURRENT_USER\Software\Wine\Direct3D\renderer instead of HKEY_CURRENT_USER\Software\Wine\Direct3D\DirectDrawRenderer
Could you try if renaming the key from "DirectDrawRenderer" to "renderer" brings back the previous behaviour?
That being said, two further notes:
1. I`ve never seen these glitches while testing Logos. Does this happen for all users or only for a few ones? As I already said in previous comment, I`m guessing it`s related to graphics card/driver issue
2. I`ve noticed that setting the aforementioned key (or disabling hardware acceleration via key https://docs.microsoft.com/en-us/dotnet/framework/wpf/graphics-multimedia/gr...) makes the videos _NOT_ play (!). They only play for me with "normal" settings (so no regkey set). But maybe some other settings might work around this again, don`t know, enough issues to keep us busy testing ;)
Regards
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #14 from Rik Shaw rikshaw76@gmail.com --- @Louis thank you for the tip on fixing the graphical glitches, setting name to "renderer" as you suggest solves the problem.
BTW they often show up as a "clear window" when Logos is trying to sync (in the "preparing your library" dialog you can see the "spinner" but the surrounding box is clear). Also, if you open the Logos Settings, when moving around your mouse pointer it will "glitch" and show the window behind it, then move the mouse more and it will show the settings window, etc. It is "hit and miss" to recreate :-( Note I am on Intel 5th gen graphics (not sure about John)
About videos playing, I am now using WINE 5.3 (well, a bit customized as I package it as /opt/wasta-wine) but they still don't seem to work? Maybe I need better guidance from John on actually testing them playing. I used the library search to set the type to "media collection" and found "Basics of Biblical Hebrew Video Lectures". Then when I select one, it says "We couldn't access the media you're trying to play. Please verify that you are not working offline. For more help troubleshooting this issue please visit our support page." Is this maybe an online only video? Please advise on how I can test playing a video.
https://bugs.winehq.org/show_bug.cgi?id=47837
Frank franksauer@cox.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |franksauer@cox.net
--- Comment #15 from Frank franksauer@cox.net --- @Rik - if you applied the fix that @Louis mentioned, he did state it breaks the video play. Also it appears I have the same issue with the graphical glitch you mention for the box that appears for the syncing sequence. My box however is all black except the spinner.
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #16 from m0rvj johnpgoodman@gmail.com --- (In reply to Louis Lenders from comment #13)
(In reply to m0rvj from comment #12)
Even with drr=gdi these glitches are back from wine 5.1 onwards. This seems to be a quite big regression for us. 5.3
Hi m0rv, My guess is the "regression" is caused by commit: https://www.winehq.org/pipermail/wine-cvs/2020-January/141298.html
So winetricks is really at fault here i think; it should set the key HKEY_CURRENT_USER\Software\Wine\Direct3D\renderer instead of HKEY_CURRENT_USER\Software\Wine\Direct3D\DirectDrawRenderer
Could you try if renaming the key from "DirectDrawRenderer" to "renderer" brings back the previous behaviour?
That being said, two further notes:
- I`ve never seen these glitches while testing Logos. Does this happen for
all users or only for a few ones? As I already said in previous comment, I`m guessing it`s related to graphics card/driver issue
- I`ve noticed that setting the aforementioned key (or disabling hardware
acceleration via key https://docs.microsoft.com/en-us/dotnet/framework/wpf/graphics-multimedia/ graphics-rendering-registry-settings) makes the videos _NOT_ play (!). They only play for me with "normal" settings (so no regkey set). But maybe some other settings might work around this again, don`t know, enough issues to keep us busy testing ;)
Regards
Once again thanks Louis, I've been too tied up to work on this for a few months. The reg key change works for me. Do you understand why it works? Does it mean we have a problem with intel drivers? Will it only apply to old intel chipsets? In which case maybe I should be upgrading... don't want to though;)
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #17 from m0rvj johnpgoodman@gmail.com --- In the mean time I've submitted the issue to winetricks on github. Hopefully that will get updated.
https://bugs.winehq.org/show_bug.cgi?id=47837
Nick nick.andrewes@phonecoop.coop changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nick.andrewes@phonecoop.coo | |p
--- Comment #18 from Nick nick.andrewes@phonecoop.coop --- Just spotted this:
I can confirm two kinds of graphic glitches:
(a) strange, mainly black patterns, at the login screen on first installation (b) Logos often has a virtually completely black window, with icons etc being revealed on mouseover - possibly also when they are updated (e.g. spinner, as stated)
I am currently not using any ddr=gdi or renderer or any other kind of fix.
$lspci 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2)
I am using Debian Bullseye, Wine Staging 5.11, 64 bit, win10, dotnet48
Oh, and I don't think my video works: it appears to try to open the media in a browser, but doesn't succeed. If I remember correctly, it used to work in the browser, but I can't be sure of this.
This would imply that video not working is independent of the ddr=gdi / renderer issue.
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #19 from Nick nick.andrewes@phonecoop.coop --- Created attachment 67560 --> https://bugs.winehq.org/attachment.cgi?id=67560 Picture of graphics glitches
Here's a picture showing the bits that are revealed on mouseover.
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #20 from Nick nick.andrewes@phonecoop.coop --- Created attachment 67561 --> https://bugs.winehq.org/attachment.cgi?id=67561 More glitches!
And another.
I'm happy to try changing some settings. e.g. the renderer fix. But it's interesting that the glitches appear without the fixes.
https://bugs.winehq.org/show_bug.cgi?id=47837
m0rvj johnpgoodman@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED
--- Comment #21 from m0rvj johnpgoodman@gmail.com --- This is now fixed in winetricks... https://github.com/Winetricks/winetricks/issues/1542
https://bugs.winehq.org/show_bug.cgi?id=47837
--- Comment #22 from m0rvj johnpgoodman@gmail.com --- Final note for simplicity. If anyone is seeing these graphical glitches please run winetricks drr=gdi or tick that box in the winetricks gui.
https://bugs.winehq.org/show_bug.cgi?id=47837
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Intrusive graphics glitches |Logos 8 Bible Software |.NET app - Logos Bible |(.Net 4.7.2 app) has |Software |graphics glitches CC| |focht@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
https://bugs.winehq.org/show_bug.cgi?id=47837
m0rvj johnpgoodman@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTOURBUG |--- Status|RESOLVED |UNCONFIRMED
--- Comment #23 from m0rvj johnpgoodman@gmail.com --- I'm updating the status, running with proton experimental and gl there are no graphical glitches and 3d acceleration seems to work. Presumably there is a patch which may find its way into wine? I will try to identify it if I can.
-
WineHQ Bugzilla