August 2014 - Wine-Bugs - list.winehq.org

[Bug 37018] Viber : Crash when trying to make a video call. New Wine installation only with new Viber

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=37018 --- Comment #1 from Austin English <austinenglish(a)gmail.com> --- Please retest in 1.7.23. Does this program have a demo/download 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.

Aug. 1, 2014

[Bug 33802] Starcraft II: some textures are missing

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=33802 hanska2(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hanska2(a)luukku.com --- Comment #7 from hanska2(a)luukku.com --- Any update on 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.

Aug. 1, 2014

[Bug 36713] Watch_Dogs requires ws2_32.inet_pton

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=36713 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian(a)fds-team.de --- Comment #7 from Sebastian Lackner <sebastian(a)fds-team.de> --- try this one: https://github.com/compholio/wine-compholio/blob/master/patches/ws2_32-inet… This one also includes proper error handling. -- 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.

Aug. 1, 2014

[Bug 37018] New: Viber : Crash when trying to make a video call. New Wine installation only with new Viber

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=37018 Bug ID: 37018 Summary: Viber : Crash when trying to make a video call. New Wine installation only with new Viber Product: Wine Version: 1.4.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hsh.manbw(a)gmail.com Created attachment 49186 --> http://bugs.winehq.org/attachment.cgi?id=49186 Crash log I have just installed Wine from the Program administration menu. After this I installed Viber for Windows as I have only a 32 bit system. My PC is an ACER ONE model KAV60 Writing Viber message is working fine. / Henning -- 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.

Aug. 1, 2014

[Bug 37017] KEY_WOW64_32KEY doesn't work properly after opening HKLM\Software key.

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=37017 Sagawa <sagawa.aki+winebugs(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.

Aug. 1, 2014

[Bug 37017] New: KEY_WOW64_32KEY doesn't work properly after opening HKLM\Software key.

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=37017 Bug ID: 37017 Summary: KEY_WOW64_32KEY doesn't work properly after opening HKLM\Software key. Product: Wine Version: 1.7.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: sagawa.aki+winebugs(a)gmail.com Created attachment 49185 --> https://bugs.winehq.org/attachment.cgi?id=49185 proof of concept I noticed that following scenario doesn't work properly on 64-bit executable. Step 1. Open or create HKEY_LOCAL_MACHINE\\Software with KEY_WOW64_32KEY. e.g. RegOpenKeyEx( HKEY_LOCAL_MACHINE, "Software", 0, KEY_WOW64_32KEY | KEY_ALL_ACCESS, &key). Step 2. Open or create a subkey of the above key with KEY_WOW64_32KEY. e.g. RegOpenKeyEx( key, "Wine\\Winetest", 0, KEY_WOW64_32KEY | KEY_ALL_ACCESS, &subkey) Step 3. Get the value of the key. Expected behavior is obtaining 32-bit view value in step 3. But, currently wine returns 64-bit view value then. Opening directly, i.e. RegOpenKeyEx(HKLM, "Software\Wine\Winetest", 0, KEY_WOW64_32KEY...), works as expected. I wrote proof of concepts for 1.7.23. See the attachment for details. I'm working on this 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.

Aug. 1, 2014

[Bug 11436] Pepakura viewer: err:wgl:X11DRV_wglShareLists Could not share display lists, context already created !

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=11436 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gyebro69(a)gmail.com --- Comment #19 from Béla Gyebrószki <gyebro69(a)gmail.com> --- I tested Pepakura Viewer v3.05a in wine-1.7.23-33-gc654b7b. The application starts with an error message: 'Error: invalid operation' and terminal shows: >fixme:dib:dibdrv_wglShareLists not supported yet Despite of the error message, the app is started and the 2 demo objects can be opened without issues. The hackish patch from comment #17 didn't make it any better, the error message remained on startup. On the other hand, the patch in comment #17 fixes bug #25420 and bug #25419 for me. In addition there's a bug when you run Blender 2.7.x under Wine where some fonts are unreadable (http://forum.winehq.org/viewtopic.php?f=8&t=23200) The patch fixes this problem too. Could a Wine developer review this patch in case it would be acceptable? setup_pepakura_viewer305a_en.exe md5sum: b8287756e36c1aa790aab787fa8cf583 -- 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.

Aug. 1, 2014

[Bug 37010] DYMO Stamps "Unable to connect to postage transaction server" with wine-mono

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=37010 --- Comment #4 from Vincent Povirk <madewokherd(a)gmail.com> --- Well, ideally we should pull the trusted roots from the Windows API somehow. -- 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.

Aug. 1, 2014

[Bug 37010] DYMO Stamps "Unable to connect to postage transaction server" with wine-mono

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=37010 --- Comment #3 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to Vincent Povirk from comment #2) > [0000002A:] EXCEPTION handling: > System.Security.Cryptography.CryptographicException: Store Root doesn't > exists. > > That doesn't seem right. I found this webpage, it looks useful: "By default Mono trusts no one" http://www.mono-project.com/FAQ%3a_Security#Secure_Socket_Layer_.28SSL.29_.… -- 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.

Aug. 1, 2014

[Bug 37010] DYMO Stamps "Unable to connect to postage transaction server" with wine-mono

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=37010 --- Comment #2 from Vincent Povirk <madewokherd(a)gmail.com> --- [0000002A:] EXCEPTION handling: System.Security.Cryptography.CryptographicException: Store Root doesn't exists. That doesn't seem right. -- 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.

Aug. 1, 2014