[Bug 35627] New: Moyo Go Studio stones not visible
http://bugs.winehq.org/show_bug.cgi?id=35627 Bug ID: 35627 Summary: Moyo Go Studio stones not visible Product: Wine Version: 1.7.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: krafczyk.matthew(a)gmail.com Created attachment 47576 --> http://bugs.winehq.org/attachment.cgi?id=47576 How the application looks for me The go stones in moyo go studio are not visible. Only their shadows display. I've attached a picture of what the board should look like, and what it looks like for me. I've also attached a log output of me placing a few moves on the board. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=35627 --- Comment #1 from Matthew Krafczyk <krafczyk.matthew(a)gmail.com> --- Created attachment 47577 --> http://bugs.winehq.org/attachment.cgi?id=47577 How the application should 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.
http://bugs.winehq.org/show_bug.cgi?id=35627 --- Comment #2 from Matthew Krafczyk <krafczyk.matthew(a)gmail.com> --- Created attachment 47578 --> http://bugs.winehq.org/attachment.cgi?id=47578 command line log from running the application -- 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=35627 --- Comment #3 from Austin English <austinenglish(a)gmail.com> --- Looking at the website, it looks like a .NET app. Does using native .NET instead of wine-mono help? -- 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=35627 --- Comment #4 from Matthew Krafczyk <krafczyk.matthew(a)gmail.com> --- So, I tried to use mono, but it turns out that none of the binaries are actually mono binaries. Here is the output of if I run the 'file' command on the relavent binaries. After unziping the download contains setup executables: InstallCyberKiwon4d.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed InstallCyberKiwon5d.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed InstallCyberKiwon6d.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed InstallCyberKiwon7d.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed InstallIGS.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed InstallKGS4dvs4d.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed InstallKGS5dvs5d.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed InstallKGS6dvs5d.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed InstallKGS6dvs6d.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed InstallKGS7dvs5-7d.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed InstallKGS8dvs5-8d.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed InstallKGS9dvs5d.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed InstallNNGS.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed InstallTygem.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed Setup.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed After installing, here are all the exectuables in the install directory: ./speexenc.exe: PE32 executable (console) Intel 80386, for MS Windows ./GNU Go/gnugo.exe: PE32 executable (console) Intel 80386, for MS Windows ./CopyPrevious.exe: PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed ./speexdec.exe: PE32 executable (console) Intel 80386, for MS Windows ./Postscript/gswin32c.exe: PE32 executable (console) Intel 80386, for MS Windows ./Uninstall.exe: PE32 executable (GUI) Intel 80386, for MS Windows ./MoyoGo.exe: PE32 executable (GUI) Intel 80386, for MS Windows I contacted the developer and he only put the statement about mono on his website because some person emailed him and told him that he got it to work. However no instructions exist. -- 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=35627 --- Comment #5 from Austin English <austinenglish(a)gmail.com> --- (In reply to Matthew Krafczyk from comment #4)
So, I tried to use mono, but it turns out that none of the binaries are actually mono binaries. Here is the output of if I run the 'file' command on the relavent binaries.
Wine ships its own version of mono that replaces native .Net. The website doesn't indicate what version of .Net it uses, however. Try 'winetricks dotnet20' as a starting point. -- 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=35627 --- Comment #6 from Matthew Krafczyk <krafczyk.matthew(a)gmail.com> --- So, I started a new wineprefix, then I used winetricks to install dotnet20 as you suggested, then I installed the application, but the stones still do not show. I also tried dotnet35, but winetricks fellback to dotnet20. Is there a debug channel I can turn on which might show if an error is occuring? -- 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=35627 --- Comment #7 from Austin English <austinenglish(a)gmail.com> --- (In reply to Matthew Krafczyk from comment #6)
So, I started a new wineprefix, then I used winetricks to install dotnet20 as you suggested, then I installed the application, but the stones still do not show. I also tried dotnet35, but winetricks fellback to dotnet20. Is there a debug channel I can turn on which might show if an error is occuring?
The terminal output itself would be helpful. -- 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=35627 --- Comment #8 from Matthew Krafczyk <krafczyk.matthew(a)gmail.com> --- Created attachment 47584 --> https://bugs.winehq.org/attachment.cgi?id=47584 Log of installation of dotnet20, moyo go studio, and running moyo go studio -- 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=35627 --- Comment #9 from Matthew Krafczyk <krafczyk.matthew(a)gmail.com> --- I already had a command line log from running moyo go studio. But I'll attach another. This one also has a log from installing dotnet20, moyo go, and finally running moyogo itself. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=35627 --- Comment #10 from Matthew Krafczyk <krafczyk.matthew(a)gmail.com> --- So I've been in contact with an openSUSE user who provided a screenshot of this program working for him. He said the default rpms for wine, produced a screen similar to mine, and then installing the rpm for wine-mono made the stones show. I'm not sure whats going wrong for me, but I'm determined to find out. Could this be an issue with graphics drivers? -- 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=35627 --- Comment #11 from Austin English <austinenglish(a)gmail.com> --- (In reply to Matthew Krafczyk from comment #10)
So I've been in contact with an openSUSE user who provided a screenshot of this program working for him. He said the default rpms for wine, produced a screen similar to mine, and then installing the rpm for wine-mono made the stones show.
Presumably your wine package disabled mono, but..see http://wiki.winehq.org/Mono to manually install it: $ wget "http://sourceforge.net/projects/wine/files/Wine%20Mono/4.5.2/wine-mono-4.5.2..." $ msiexec /i wine-mono-4.5.2.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.
http://bugs.winehq.org/show_bug.cgi?id=35627 --- Comment #12 from Matthew Krafczyk <krafczyk.matthew(a)gmail.com> --- So, I've done exactly that for my previous installations. I've checked and the windows/mono/mono-2.0 directory exists in my wine prefix and everything. After talking to the openSUSE guy, it sounds like he just had a distro update and during the update it asked him if he wanted to install mono. Since it worked after the mono (and distro upgrade) installation, he assumed the improvement in the program was linked to mono. Given the results from the file command that I mentioned earlier, is there any reason to believe at this point that the program is using anything mono related? I'm pretty sure at this point that mono has nothing to do with this. In addition, I tried it on another machine, this time a debian installation with a radeon gpu but no luck. I guess this means it isn't graphics driver related. Btw, thanks a lot for your help. -- 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=35627 --- Comment #13 from Austin English <austinenglish(a)gmail.com> --- (In reply to Matthew Krafczyk from comment #12)
So, I've done exactly that for my previous installations. I've checked and the windows/mono/mono-2.0 directory exists in my wine prefix and everything.
After talking to the openSUSE guy, it sounds like he just had a distro update and during the update it asked him if he wanted to install mono. Since it worked after the mono (and distro upgrade) installation, he assumed the improvement in the program was linked to mono.
Given the results from the file command that I mentioned earlier, is there any reason to believe at this point that the program is using anything mono related? I'm pretty sure at this point that mono has nothing to do with this.
WINEDEBUG=mscoree would tell you. Is there a demo of this available? -- 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=35627 --- Comment #14 from Matthew Krafczyk <krafczyk.matthew(a)gmail.com> --- Below is a log of the program with WINEDEBUG=+mscoree. You can see that it's the same. no messages from that channel. The additional entries are clicking around the program in a different way. There isn't a demo that I know of unfortunately.. matthew(a)sibelius: ~/.wine_moyogo/drive_c/Program Files/Moyo Go Studio $ WINEDEBUG=+mscoree wine MoyoGo.exe p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory fixme:shell:FileIconInit (true) fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} fixme:win:EnumDisplayDevicesW ((null),0,0x33e9f8,0x00000000), stub! fixme:ieframe:PersistStreamInit_Load (0x10058850)->(0x1042c2c0) -- 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=35627 Matthew Krafczyk <krafczyk.matthew(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #15 from Matthew Krafczyk <krafczyk.matthew(a)gmail.com> --- So, I've found that this bug is NOT caused by wine. This is most likely due to an incorrect Nvidia graphics driver. I have a hybrid graphics system and was testing this application with the discrete GPU. Upon switching to the intel GPU, the application worked as expected. This bug can be closed. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=35627 Frédéric Delanoy <frederic.delanoy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #16 from Frédéric Delanoy <frederic.delanoy(a)gmail.com> --- Closing -- 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)
-
wine-bugs＠winehq.org