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

[Bug 40333] New: atmlib link broken
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=40333 Bug ID: 40333 Summary: atmlib link broken Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sacviper(a)gmail.com Distribution: --- I am trying to install atmlib using winetricks but link is broken to Microsoft download -- 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 34987] New: Next Car Game tech demo graphics corruption
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=34987 Bug #: 34987 Summary: Next Car Game tech demo graphics corruption Product: Wine Version: 1.7.7 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: andrey.goosev(a)gmail.com Classification: Unclassified Created attachment 46623 --> http://bugs.winehq.org/attachment.cgi?id=46623 screenshot It's how gameplay looks on GT 540M with driver 331.20 -- 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 30086] New: Heavy slow down X with Qt
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=30086 Bug #: 30086 Summary: Heavy slow down X with Qt Product: Wine Version: 1.4-rc6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: alpha_one_x86(a)first-world.info Classification: Unclassified Hello, when I compil Qt or Qt program with wine, X use ~15% of my cpu, and have like 1s with normal activie 1s where all freeze (mouse, X at 100%, ...) No problem with other application like game, or 2D application. To reproduct it: Install the Qt SDK. Compil a big application (in my case http://files.first-world.info/ultracopier/0.3.0.3/ultracopier-src-0.3.0.3.t…) and see the cpu, move the mouse, ... it's easy to see, all freeze at fixed interval. I'm with the open source drivers for my ati radeon. 1 year ago I problem don't exists. -- 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 33319] New: Diabo 3 Freeze after 1-3 Minutes (Menu after login and ingame)
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=33319 Bug #: 33319 Summary: Diabo 3 Freeze after 1-3 Minutes (Menu after login and ingame) Product: Wine Version: 1.5.26 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: bastik(a)gmx.de Classification: Unclassified Created attachment 44070 --> http://bugs.winehq.org/attachment.cgi?id=44070 Diablo console output with the given Diablo start command. Diablo 3 Freeze within 1-3 minutes after successfull login. Hardware: Notebook running Ubuntu 12.10 with wine 1.5.26 Tested Catalyst versions 12.6 / 13.1 / 13.3 beta All requirements and tips according to the Diablo 3 guide are done. (http://appdb.winehq.org/objectManager.php?sClass=version&iId=25953) CPU: Intel C2D T9300 Graphic: AMD HD4850 WINEDEBUG="-all,err+all,warn+all,fixme+all,+tid,+loaddll" WINEPREFIX=~/.local/share/wineprefixes/Diablo3 force_s3tc_enable=true WINEARCH=win32 setarch i386 -3 -L -B wine ~/Games/Diablo3/Diablo\ III.exe -launch -opengl (see attachement for output of this) The error is locking the whole XServer (Unity3D and Unity2D tested) interface. Keyboard is not responding, it is not possible to switch to another Terminal. The mouse courser is movable but will not respond to clicks. In Diablo 3 windowed mode the courser does not change when moving from the game window to the desktop. The game sound continous playing. The only way to restore the Xserver session is to remotely kill the Diablo 3 process with an SSH tunnel. I tried a lot of things to get it working, but without success. - I disabled sound - I worked around with wine registry keys (Direct3D settings) tried ervery possibile setting. Is there a possibilty to debug a running wine process after it is freezed? I tested a bit with winedbg but without success. Please advice me what to do, I don't have any ideas left, trying a few weeks to get it running. -- 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 38863] New: Space Rangers 2 shows only black screen with nouveau
by wine-bugs＠winehq.org 20 Nov '18

20 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=38863 Bug ID: 38863 Summary: Space Rangers 2 shows only black screen with nouveau Product: Wine Version: 1.7.46 Hardware: x86 URL: http://www.fileplanet.com/162972/160000/fileinfo/Space -Rangers-2:-Rise-of-the-Dominators-Demo OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Distribution: --- Created attachment 51791 --> https://bugs.winehq.org/attachment.cgi?id=51791 terminal output Upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=91171 Originally I reported the bug in Mesa bugtracker because the game runs properly on my system with Nvidia binary drivers 340.76. Discussing the issue with Ilia Mirkin on irc he expressed his doubts that the problem might be in Wine as well. Would any of the devs here mind taking a look at this bug and tell me where the problem is? Problem: the game shows only black screen after starting so that only audio can be heard. If I set ddr=gdi then the game displays properly. Trace file (uncompressed 335 MB): https://drive.google.com/open?id=0B-tTbLKBl-tOX1c0T1VqRjR2MEU Replaying the trace with nouveau the problem is reproducible.If I replay the trace with the '--sb' (single-buffer) switch (glretrace --sb rangers2.trace) then it renders correctly. Our discussion on irc (relevant part from 10:29): http://people.freedesktop.org/~cbrill/dri-log/?channel=nouveau&highlight_na… wine-1.7.46-193-g8b566b1 Fedora 22 32-bit VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] (rev a2) Mesa from git Xorg 1.17.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 5

[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 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