November 2018 - Wine-bugs - list.winehq.org

[Bug 33341] New: Planetside 2 unplayable after April 3rd game update.
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=33341 Bug #: 33341 Summary: Planetside 2 unplayable after April 3rd game update. Product: Wine Version: 1.5.27 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kisak42(a)gmail.com Classification: Unclassified Created attachment 44104 --> http://bugs.winehq.org/attachment.cgi?id=44104 backtrace of crash The April 3rd, 2013 update of Planetside 2 has caused the game to crash for me. I have a separate 32 bit wineprefix for Planetside 2 with a Windows XP imm32.dll added to it. Before the update, the game was more or less playable, besides the other documented issues of running this game on wine. It now crashes just after selecting a character and clicking the play / log in button. I am running on Gentoo Linux 64 bit with an AMD Bulldozer and nVidia GTX 460 (nvidia-drivers 313.26). I am using Cinnamon 1.6.7 for my DE. Please feel free to request any other relevant information. Attached is a backtrace, which is consistent from one attempt to another. If I am reading it right, the crash is occuring in apexframework_x86. -- 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 12

[Bug 32576] New: Skyrim runs but does not display game
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=32576 Bug #: 32576 Summary: Skyrim runs but does not display game Product: Wine Version: 1.5.20 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: alex_y_xu(a)yahoo.ca Classification: Unclassified Basically, Skyrim starts fine, and I can create a new game fine. Nothing crashes, and the text ("Bethesda... presents... The Elder Scrolls V... SKYRIM") displays fine, but the "background" i.e. game never displays. I am using Wine 1.5.20, Mesa 9.0, xf86-video-ati 7.0.0 (Radeon HD 6850), and linux 3.8.0-rc1+ (101e5c7470eb7f77ae87f966b9155f0dbb5b4698 with 4fc3f1d66b1ef0d7b8dc11f4ff1cc510f78b37d6, 5a505085f043e8380f83610f79642853c051e2f1 reverted). -- 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 16

[Bug 44751] New: In Ex Machina (Hard Truck Apocalypse) wheels are always turned to the left.
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=44751 Bug ID: 44751 Summary: In Ex Machina (Hard Truck Apocalypse) wheels are always turned to the left. Product: Wine Version: 3.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thatguyyoucannottrust(a)gmail.com Distribution: --- Created attachment 60762 --> https://bugs.winehq.org/attachment.cgi?id=60762 Wheels are turned to the left. Game works perfectly (especially compared to Windows 10, where I get 10fps and graphical glitches), but as soon as the gameplay starts, the wheels of the car turn to the left and stay in that position. It's the same on all trucks and I don't know if there's a way to fix it. Same game in Windows has no such 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 6

[Bug 42002] New: Chuckie Egg: The Next Batch v1.2 - Blackscreen on some setups
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=42002 Bug ID: 42002 Summary: Chuckie Egg: The Next Batch v1.2 - Blackscreen on some setups Product: Wine Version: 1.9.24 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de CC: stefan(a)codeweavers.com Regression SHA1: a385c9ea3ead9438f591c3777a6ff6a21abdfc42 Distribution: ArchLinux The games shows a black-screen since on some setups, but only since a certain wine version. Other reported it to work, but not for me. Regression introduced by commit a385c9ea3ead9438f591c3777a6ff6a21abdfc42 Author: Stefan Dösinger <stefan(a)codeweavers.com> Date: Mon Oct 12 22:34:38 2015 +0200 wined3d: Pass a context to surface_load_sysmem. Signed-off-by: Stefan Dösinger <stefan(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Since that commit only ddr=gdi works, ddr=opengl only results in a blackscreen. See also: Bug 41993, fix for a different black-screen issue. Using an R9 285 with mesa 13.0.2 -- 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 12

[Bug 37475] New: SimCity 2013 freezes on start in fullscreen (Failed to open BO for returned DRI2 buffer (1600x900, dri2 back buffer, named 11). This is likely a bug in the X Server that will lead to a crash soon.)
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=37475 Bug ID: 37475 Summary: SimCity 2013 freezes on start in fullscreen (Failed to open BO for returned DRI2 buffer (1600x900, dri2 back buffer, named 11). This is likely a bug in the X Server that will lead to a crash soon.) Product: Wine Version: 1.7.29 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jre.winesim(a)gmail.com Distribution: --- Created attachment 49859 --> https://bugs.winehq.org/attachment.cgi?id=49859 Complete output (WINEDEBUG=fixme+all,err+all). The crash happens in line 3553. Hi, I installed SimCity 2013 in EA's Origin. When I start the game in fullscreen it freezes during the intro. See the complete output (WINEDEBUG=fixme+all,err+all) in the attachment. The crash happens in line 3553. Starting and playing in an emulated virtual desktop works, but gives during the intro more than 3.000.000 lines like this: ~~~~~ err:d3d_surface:surface_invalidate_location Surface 0x10ecfed0 does not have any up to date location. [...] err:d3d_surface:surface_load_location Surface 0x10ed83e8 does not have any up to date location. ~~~~~ I'm really not sure if this is wine's fault or as suggested by the error message the X Server's. I got the same error message ("This is likely a bug in the X Server that will lead to a crash soon.") when watching videos with mpv when toggling fullscreen on and off. At the same time this works with other video players, e.g. mplayer. Hardware: Samsung Serie 9 900X4C-A07 38,1cm (15 Zoll) Ultrabook (Intel Core i7-3517U, 1,9 GHz, 8GB RAM, 256GB SSD, Intel HD 4000). It happens regardless if I have an external monitor plugged in or not. Software: Debian Jessie (testing), 64-bit Linux 3.16-3-amd64 #1 SMP Debian 3.16.5-1 (2014-10-10) x86_64 GNU/Linux xserver-xorg 1:7.7+7 xserver-xorg-core 2:1.16.1-1 xserver-xorg-video-intel 2:2.21.15-2+b2 Origin 9.4.22.2815 See also my test report in the AppDB: https://appdb.winehq.org/objectManager.php?sClass=version&iId=27821&iTestin… I'd be happy to provide any further information. Greets and thanks! jre -- 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 8

[Bug 43057] New: Final Fantasy XIV DX9 Creates an invalid GLSL shader
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=43057 Bug ID: 43057 Summary: Final Fantasy XIV DX9 Creates an invalid GLSL shader Product: Wine Version: 2.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: yitziw(a)gmail.com Distribution: ArchLinux Created attachment 58225 --> https://bugs.winehq.org/attachment.cgi?id=58225 section of debug output The D3DX9-to-OpenGL process appears to create a shader that fails to compile. The responsible error appears to be logged at the final line of the attached debug log, and additionally appeared throughout the original debug output (which was over 2mb in size and could not be uploaded in whole): fixme:d3d_shader:print_glsl_info_log error: Input block `shader_in_out' is not an output of the previous stage This bug results in ugly visuals on the main menu, and causes no visuals to display when in the main game. -- 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 18

[Bug 45451] New: Doom 2016 Freezing and Crashing in background
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=45451 Bug ID: 45451 Summary: Doom 2016 Freezing and Crashing in background Product: Wine Version: 3.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winevulkan Assignee: wine-bugs(a)winehq.org Reporter: linards.liepins(a)gmail.com Distribution: --- Created attachment 61784 --> https://bugs.winehq.org/attachment.cgi?id=61784 winetricks installed module list After I enabled Vulkan via enabling it in kernel cmdline (radeon.cik_support=0 amdgpu.cik_support=1), was able to launch the game. Once all intro cinematics was finished, the game loading bar was showing up, but it stopped at 99%. See following link for similar reports: I tried several options suggested there and none of them appears to be fixing the issue. I have created all possible graphics (& vulkan) related logs about my system and attached in this bug. Also attached game crash log, created by Id Engine. I also attached winetricks installed module list. -- 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 16

[Bug 44005] New: ieproxy registration breaks Internet Explorer 8
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=44005 Bug ID: 44005 Summary: ieproxy registration breaks Internet Explorer 8 Product: Wine Version: 2.20 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: piotr.caban(a)gmail.com Distribution: --- Internet Explorer 8 no longer starts in wine. Steps to reproduce: sh winetricks ie8 wine iexplore This is a regression caused by this commit: commit 448ac0e9c439c5a8095e2e8a150997caebcb32ab Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Thu Aug 10 13:52:31 2017 -0500 ieproxy: Add proxy/stub for IInternetExplorerManager. Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Setting the ieproxy dll to native is not helping because builtin gets registered on prefix update (different installation path). The dll path is different depending on Internet Explorer version. So it kind of makes it impossible to use native. The dll is missing a proxy/stub for C90250F3-4D7D-4991-9B69-A5C5BC1C2AE6 (undocumented). -- 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 16

[Bug 46171] New: Crash when testing for disk drive speed
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=46171 Bug ID: 46171 Summary: Crash when testing for disk drive speed Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rwtmiller13(a)gmail.com Distribution: --- Created attachment 62830 --> https://bugs.winehq.org/attachment.cgi?id=62830 This is the error report I'm always given when Wine "encounters a serious error and needs to close." I was installing a game (Lighthouse: The Dark Being, made in 1996), and I was asked to have it run an analysis of my disk drive to determine if the speed was high enough to run the game. However, as soon as the analysis begins, Wine tells me that it has encountered a serious problem and needs to close. This happens every time I try it. -- 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 2

[Bug 46150] New: Battlefield 3/4/ 1 freeze when key pressed in wine-staging 3.20
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=46150 Bug ID: 46150 Summary: Battlefield 3/4/1 freeze when key pressed in wine-staging 3.20 Product: Wine-staging Version: 3.20 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: llenort(a)aol.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Hello, running wine-staging 3.19, dxvk 0.92, Mesa 18.2, nvidia 415.13 and can run and play all Battlefield version. Update to wine-staging 3.20 and reinstalling dxvk 0.92 all BF Versions freeze when any key is pressed. Hole X Server seems to freeze an has to stop from a terminal window. Downgrade to 3.19 and reinst. dxvk 0.92 everything is running well again ?? Is the old wine key pressed problem returned?! But i use no overlay in Origin. I own also Titanfall 2 and i had no Problems running the game and press any keys. Checked also Doom 2016 (Vulkan) over Steam and even this game runs well with wine-staging 3.20. Looks like only BF Versions listed above has a Problem here? Thank you for all your good work and support! lle -- 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 5