March 2018 - Wine-Bugs - list.winehq.org

[Bug 37151] New: Focus Problems with Tera
by wine-bugs＠winehq.org April 2, 2018

April 2, 2018

https://bugs.winehq.org/show_bug.cgi?id=37151 Bug ID: 37151 Summary: Focus Problems with Tera Product: Wine Version: 1.7.24 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: eli(a)orbsky.homelinux.org Hi. Using wine 1.7.24 32bit on x86_64. Wine is configured to: Automatically capture the mouse in full-screen Allow the window manager to decorate the windows Allow the window manager to control the windows I play games in full sreen on a dual screen setup. The screen that I play on is sitting to the right while my other screen is to the left. The game that I play most of the time is Tera online, but I've seen these problems other games as well. 1st Focus Problem ----------------- After starting the game, the launcher pops up and I can login. When I press on the play button; what should happen next is a splash screen pops up, then a warning about not being able to exceed 4GB memory should pop up ontop of the splash screen. I would then dismiss the warning and then the game should pop up in front and I should be able to play. What does happen is that the the splash screen, the warning screen and the game itself are all thrown into the background. I need to alt-tab to the warning screen before I can dismiss it. Then I need to alt-tab to the game window before it appears. The game then starts normally. Now... If I disable "allow the windows manager to control the windows" then the windows pop up as expected, but.... when the game pops up, the mouse does not move. 2nd Focus Problem ----------------- During transition screens the mouse looses focus and I can drag the mouse off the game. This also happens after starting a dialog with an npc and the dialog box of the "conversation" appears. If I click on the game again all is well, but I shouldn't loose the focus. 3rd Focus Problem ----------------- Sometimes, when actually playing I cannot turn to the left (where my secondary monitory is sitting and the game is not. I can continue to turn to the right, but turning left is froozen unless I alt-tab cycle out of and then back into the game and all is well. If there is any additional information that you need from me I will do my best to either provide that info or ask howto provide it. Thanks for any time you might spend looking into the problem. -- 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.

1 10

[Bug 32986] New: Fallout New Vegas: Anti-aliasing doesn't work properly
by wine-bugs＠winehq.org April 2, 2018

April 2, 2018

http://bugs.winehq.org/show_bug.cgi?id=32986 Bug #: 32986 Summary: Fallout New Vegas: Anti-aliasing doesn't work properly Product: Wine Version: 1.5.24 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: joedavison.davison(a)gmail.com Classification: Unclassified Before continuing I should mention Multisampling is enabled in the Wine registry. Anti-aliasing in Fallout: New Vegas doesn't seem to work like it should. Values up to 8 samples (as per the launcher) apply anti-aliasing, but it seems like it's only in fact rendering with 2 samples. Selecting 9 samples or more simply disables anti-aliasing altogether. World details are anti-aliased correctly. Buildings, streetlamps and the like are smoothed like they should be, while objects like grass are not. Furthermore, structures in the distance (like pylons) are not aliased at all and look like pencil scribbles from MS Paint. I've observed this in Wine versions throughout the 1.5.x series. My distro is Arch Linux x86_64. DirectX 9 DLL overrides *are* being used as the Steam installer for New Vegas installs DirectX automatically. I have not yet tested it without overrides. This doesn't occur in Skyrim, a game that uses the same engine as New Vegas. My specs: Nvidia 660Ti 2GB 16GB DDR3 RAM Intel Core i5 3.4GHz @ 4.0GHz -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

1 4

[Bug 38772] New: Incorrect GetLastError error of RemoveDirectoryA and CreateDirectory.
by wine-bugs＠winehq.org March 31, 2018

March 31, 2018

https://bugs.winehq.org/show_bug.cgi?id=38772 Bug ID: 38772 Summary: Incorrect GetLastError error of RemoveDirectoryA and CreateDirectory. Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: christopherwuy(a)gmail.com Distribution: --- Created attachment 51705 --> https://bugs.winehq.org/attachment.cgi?id=51705 patch The following patch has a test which shows that RemoveDirectoryA will set incorrect GetLastError error. For example, using RemoveDirectoryA("D:\\not_exist_file") will lead to ERROR_PATH_NOT_FOUND in windows while ERROR_FILE_NOT_FOUND in Wine. I had tried to write a patch to fix it and it worked. However, it causes a set of tests failed in ntdll. -- 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.

1 3

[Bug 38570] New: user32 set_focus_window send WM_KILLFOCUS message not right.
by wine-bugs＠winehq.org March 31, 2018

March 31, 2018

https://bugs.winehq.org/show_bug.cgi?id=38570 Bug ID: 38570 Summary: user32 set_focus_window send WM_KILLFOCUS message not right. Product: Wine Version: 1.7.42 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: liuchanghui(a)linuxdeepin.com Distribution: --- Created attachment 51465 --> https://bugs.winehq.org/attachment.cgi?id=51465 The running screen in Windows Reproduce: 1, Download the test program from: http://www.imakevideo.com/set_focus_bug.exe 2, wine set_focus_bug.exe 3, Click the compute name button, a layered tool window will pop up to show host name. In Windows the pop up window will keep visible until the user click the mouse in the main dialog window or switch to other program (see the attache png file) . But in Wine the pop up window will be closed immediately when present. -- 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.

1 4

[Bug 17410] New: game 'will rock' not started
by wine-bugs＠winehq.org March 31, 2018

March 31, 2018

http://bugs.winehq.org/show_bug.cgi?id=17410 Summary: game 'will rock' not started Product: WineHQ Apps Database Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: appdb-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kolotvin(a)gmail.com there is one little message: gsVideoinit() failed and blank screen -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

1 21

[Bug 44859] New: TEFS Trader: Crashes after login
by wine-bugs＠winehq.org March 31, 2018

March 31, 2018

https://bugs.winehq.org/show_bug.cgi?id=44859 Bug ID: 44859 Summary: TEFS Trader: Crashes after login Product: Wine Version: 2.21 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: figurastecnicas(a)gmail.com Created attachment 60914 --> https://bugs.winehq.org/attachment.cgi?id=60914 Log file of the TEFS Trader error Hello, i recently installed a newer version of the software TEFS Trader because the company discontinued the old one and approximately 3 seconds after login the software crashes with the message that the software encountered a serious problem and needs to close. It can be a problem with the software or a deficiency in wine. Please find the attachment for more information. Thank you. -- 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.

1 11

[Bug 43241] New: bad performance (low fps) in Grand Theft Auto V
by wine-bugs＠winehq.org March 30, 2018

March 30, 2018

https://bugs.winehq.org/show_bug.cgi?id=43241 Bug ID: 43241 Summary: bad performance (low fps) in Grand Theft Auto V Product: Wine Version: 2.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Created attachment 58548 --> https://bugs.winehq.org/attachment.cgi?id=58548 default log wine-2.11 I get very poor performance in GTA V at lowest settings. The in-game test shows an average of 3 FPS (goes as low as 2 and peak at 6). That's about what I get when actually playing. Enabling or disabling CSMT does not change the frame rate. My specs are: CPU: Intel Core i7-4930K CPU @ 3.40GHz x 12 GPU: GeForce GTX 970/PCIe/SSE2 (4Gb) Driver: NVIDIA Driver 375.66 (current from Debian Jessie repos) Screen: Single monitor 1280x1024 - or 3840x1024 - makes no difference. wine-2.11 patched to workaround bug 43102 and to silence ActivateKeyboardLayout FIXMEs is used. The issue is the same with unpatched Wine. -- 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.

1 7

[Bug 44786] New: Native Instruments crashes: Unimplemented function vcruntime140.dll.__processing_throw
by wine-bugs＠winehq.org March 30, 2018

March 30, 2018

https://bugs.winehq.org/show_bug.cgi?id=44786 Bug ID: 44786 Summary: Native Instruments crashes: Unimplemented function vcruntime140.dll.__processing_throw Product: Wine Version: 3.4 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Hi, Follow up of bug 42446. Steps to reproduce: 1. Use workaround from Stan to get around bug 42446: https://www.winehq.org/pipermail/wine-bugs/2018-March/485972.html 2. Run with native msvcp140 to work around bug 42686 WINEDLLOVERRIDES=msvcp140=n wine Native\ Access.exe 3. The crash can be triggered by putting some garbage in the login fields, and click login Note: I used old version of installer of Native Access i had lying around here, but the program first updates itsself, and seems to get frequent updates so now it runs sha1sum Native\ Access.exe 24a8b8ddbd572cb3f0116f65ae868efbbe5aee40 Native Access.exe -- 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.

1 4

[Bug 39582] New: Battlefield 3 (Origin) tries to verify installation using bcrypt.
by wine-bugs＠winehq.org March 30, 2018

March 30, 2018

https://bugs.winehq.org/show_bug.cgi?id=39582 Bug ID: 39582 Summary: Battlefield 3 (Origin) tries to verify installation using bcrypt. Product: Wine Version: 1.7.54 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)vr-web.de Distribution: Debian Created attachment 52734 --> https://bugs.winehq.org/attachment.cgi?id=52734 bcrypt: Change/implement some functions to succeed for bf3.exe. An attempt to start an Origin installation of Battlefield 3 is followed by this message: Error Your game data is corrupt. Please repair your installation through Origin In the console output there appears this line: fixme:bcrypt:BCryptOpenAlgorithmProvider 0x300de48, L"RSA", (null), 00000000 - stub Attached (quick) hack modifies/adds BCryptOpenAlgorithmProvider, BCryptImportKeyPair, BCryptVerifySignature, BCryptDestroyKey, BCryptCloseAlgorithmProvider, succeeding on every input parameters. With this applied bf3.exe stops complaining about this and continues. -- 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.

1 23

[Bug 43186] New: 1Password 6.5.401 crashes on login with System.TypeInitializationException
by wine-bugs＠winehq.org March 30, 2018

March 30, 2018

https://bugs.winehq.org/show_bug.cgi?id=43186 Bug ID: 43186 Summary: 1Password 6.5.401 crashes on login with System.TypeInitializationException Product: Wine Version: 2.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs(a)winehq.org Reporter: me(a)jackgrigg.com Distribution: --- Created attachment 58459 --> https://bugs.winehq.org/attachment.cgi?id=58459 Stack trace I applied the PBKDF2 patch (https://www.winehq.org/pipermail/wine-patches/2017-June/162842.html) to master (at commit c7f0777fc55229d910461a7a38e21f1e17c8913a), and compiled 32-bit Wine on 64-bit Ubuntu 16.04.2 LTS. With a fresh Wine prefix, I followed the steps in https://bugs.winehq.org/show_bug.cgi?id=43079#c2 (executing the dotnet* winetricks steps by hand because I couldn't get winetricks to cope with wine in the git build directory). Upon logging in, 1Password crashed with the following exception: Unhandled Exception: System.TypeInitializationException: The type initializer for 'AgileBits.OnePassword.WindowsDesktopAuthenticatedAes' threw an exception. ---> System.Runtime.InteropServices.COMException: Message 0x not found in file . (Exception from HRESULT: 0x8007013D) I believe this may be related to the following warning I receive when I run the bcrypt tests (wine32-build$ ../wine-source/tools/runtest -p dlls/bcrypt/tests/bcrypt_test.exe.so): fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"AES" not supported bcrypt.c:839: Test marked todo: AES provider not available fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"AES" not supported bcrypt.c:928: Test marked todo: AES provider not available fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"AES" not supported bcrypt.c:1019: Test marked todo: AES provider not 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.

1 4