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

[Bug 43437] New: Zanzarah game opens a black fullscreen window and then crashes ( needs full implementation of EnumDisplayDevicesW function and implementation of an unhandled pixel format in wined3d_colour_from_ddraw_colour function )
by wine-bugs＠winehq.org 09 Apr '21

09 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=43437 Bug ID: 43437 Summary: Zanzarah game opens a black fullscreen window and then crashes (needs full implementation of EnumDisplayDevicesW function and implementation of an unhandled pixel format in wined3d_colour_from_ddraw_colour function) Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: alehiphopdj2(a)hotmail.com Distribution: --- Created attachment 58801 --> https://bugs.winehq.org/attachment.cgi?id=58801 Log from console in Wine 2.13 This is an update of the Zanzarah bug 17233: https://bugs.winehq.org/show_bug.cgi?id=17233 because i ran Zanzarah on the last version of Wine, 2.13 and i get only a few messages on console (looks Wine developpers fixed lot of them). This is what i get (looks like the game writes to the console "starting zanzarah....hello world" first): starting zanzarah....hello worldfixme:win:EnumDisplayDevicesW ((null),0,0x33f174,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33eaa4,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33f4b4,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33eca4,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33f484,0x00000000), stub! fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. So this game requires these two things to execute: - EnumDisplayDevicesW function (dlls/user32/misc.c) full implementation to work. Lot of games use this function (so they also fail). - Implementation of an unhandled pixel format in wined3d_colour_from_ddraw_colour function (dlls/ddraw/utils.c) I need to paste the log here because i am commenting it, but i am also attaching the log in a file. -- 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.

2 7

[Bug 27528] New: Half Life Software Rendering completely wrong
by wine-bugs＠winehq.org 09 Apr '21

09 Apr '21

http://bugs.winehq.org/show_bug.cgi?id=27528 Summary: Half Life Software Rendering completely wrong Product: Wine Version: 1.3.22 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: michael(a)araneidae.co.uk The Software mode rendering of Half Life (the original 1998 game) is completely wrong: the colours are messed up (purple, mostly) and the selected screen size is squashed into half the selected width. Although noone in their right mind would run Half Life in software mode, this bug must expose problems in the Half Life rendering engine that must affect other games of this and earlier vintage. -- 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.

2 16

[Bug 32641] New: Breath of Fire IV: Crash on starting the game
by wine-bugs＠winehq.org 09 Apr '21

09 Apr '21

http://bugs.winehq.org/show_bug.cgi?id=32641 Bug #: 32641 Summary: Breath of Fire IV: Crash on starting the game Product: Wine Version: 1.5.20 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sworddragon2(a)aol.com Classification: Unclassified Created attachment 43068 --> http://bugs.winehq.org/attachment.cgi?id=43068 Output of Wine On starting the game it crashes with an error window that the application has encountered a serious problem. In the attachments is a log with the console output. -- 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.

2 20

[Bug 37996] New: Wine mono does not support https connection
by wine-bugs＠winehq.org 09 Apr '21

09 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=37996 Bug ID: 37996 Summary: Wine mono does not support https connection Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fracting(a)gmail.com Distribution: --- Created attachment 50628 --> https://bugs.winehq.org/attachment.cgi?id=50628 Test https connection Simple C# program like Client.DownloadFile("https://chocolatey.org/api/v2/", "index2.html"); doesn't work at all, see source code and logs. Workaround by `winetricks -q dotnet40` -- 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.

2 19

[Bug 39156] New: magicka 2 doesn't start
by wine-bugs＠winehq.org 09 Apr '21

09 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=39156 Bug ID: 39156 Summary: magicka 2 doesn't start Product: Wine Version: 1.7.47 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: scrimekiler(a)yahoo.fr Distribution: --- Created attachment 52185 --> https://bugs.winehq.org/attachment.cgi?id=52185 +loaddll Hi, I have added Magicka 2 as new app on wine app db, it should come soon. The game doesn't start at all and I'm trying to figure out why.I run it in a 32 bits clean prefix. disabling d3d10 and d3d11 removes the error output about d3d.Adding vcrun2005 using winetricks removes the error about msvcrt (I've added this specific version because +loaddll shows it's trying to load msvcr80) Anyway, even after this the game still doesn't start.I've also tried to add the component for magicka 1 with winetricks in case it uses some common components without success (dotnet35 xna31 xinput) I've added the +loaddll log as attachement, but here is the default wine output : fixme:winediag:start_process Wine Staging 1.7.47 is a testing version containing experimental patches. fixme:winediag:start_process Please report bugs at http://bugs.wine-staging.com (instead of winehq.org) fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} fixme:console:AttachConsole stub ffffffff fixme:ver:GetCurrentPackageId (0x33fa38 (nil)): stub fixme:d3d11:D3D11CreateDevice adapter 0x13d6d0, driver_type D3D_DRIVER_TYPE_UNKNOWN, swrast (nil), flags 0, feature_levels 0x33f6e4, levels 0x6, sdk_version 7, device (nil), feature_level 0x33f6e0, context (nil) stub! err:ole:CoCreateInstance apartment not initialised fixme:msvcrt:__clean_type_info_names_internal (0x64085a64) stub -- 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.

2 6

[Bug 43896] New: Elex renders most parts as big white glowing area
by wine-bugs＠winehq.org 08 Apr '21

08 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=43896 Bug ID: 43896 Summary: Elex renders most parts as big white glowing area Product: Wine-staging Version: 2.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: holzminister(a)t-online.de CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59514 --> https://bugs.winehq.org/attachment.cgi?id=59514 Terminal log, compressed; uncompressed size is 43 MB When I start up Elex(GOG version) most parts ingame are kind of glowing white/yellow/green and are overshadowing the game graphics(see screenshots). I can move ingame and collect things from the ground, but with the rendering bug it is more or less unplayable. -- 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.

2 17

[Bug 43969] New: openGL SwapBuffers with NULL context
by wine-bugs＠winehq.org 08 Apr '21

08 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=43969 Bug ID: 43969 Summary: openGL SwapBuffers with NULL context Product: Wine Version: 2.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: jp-dev(a)inbox.ru Distribution: --- A fragment of openGL code works under Windows and crashes under wine staging 2.19 at glxdrv_wglSwapBuffers. This code can be found under the VSTGUI project (see https://git.io/vFCwl) The problem in wine is triggered because the library makes a null context current before the invocation of swapBuffers. As strange as it may be, Windows is able to render in this condition. wglMakeCurrent (deviceContext, 0); SwapBuffers (deviceContext); When I pass a context instead of 0, wine works as well. This reveals a pair of problems. First, there is a null pointer dereference in wgl_SwapBuffers. ctx->hdc is an invalid access because of the null context (I have added the `&& ctx` check). if (escape.gl_drawable && ctx) ExtEscape( ctx->hdc, X11DRV_ESCAPE, sizeof(escape), (LPSTR)&escape, 0, NULL ); This change allows the program to run without crash, but the result is no rendering. My test configuration on Windows was 8.1 with the vmware GL passthrough driver. -- 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.

2 8

[Bug 17735] New: andrew rudson's drum machine: makes wine segfault upon start
by wine-bugs＠winehq.org 08 Apr '21

08 Apr '21

http://bugs.winehq.org/show_bug.cgi?id=17735 Summary: andrew rudson's drum machine: makes wine segfault upon start Product: Wine Version: 1.1.17 Platform: PC URL: http://andrewrudson.com/drummachine/main.php OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: timonator(a)perpetuum-immobile.de When starting up Drum Machine (see URL for download link; this bug report is for drum machine version "1.36 beta") Wine crashes with a Segfault like this: zsh: segmentation fault wine DrumMachine.exe I can briefly see a window pop up and immediately close again. -- 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.

2 18

[Bug 44391] New: Star Trek Online: Hang when clicking "Engage"
by wine-bugs＠winehq.org 08 Apr '21

08 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=44391 Bug ID: 44391 Summary: Star Trek Online: Hang when clicking "Engage" Product: Wine Version: 3.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mbt(a)fortifiedtechsystems.com Distribution: --- Updated to Wine 3.0 and decided to try STO to see if it would work. The upside is that it works better than it did when I tried it last time, but it still doesn't work. It patches (slowly, but it does finish), but when clicking the "Engage" button after the patch has done, the program blocks, never to be heard from again. Now, the debug output in total is too large to even really attach as a compressed archive of files, so I'm going to defer to waiting for a detailed request for information. However, what I _do_ know is that the program is blocking on a read of a pipe file descriptor that is apparently not ready. The pipe is created during program startup: pipe2([7, 8], O_CLOEXEC) = 0 And then (MUCH, MUCH LATER), when I click on the Engage button: write(3, "\v\1\0\0\0\0\0\0\0\0\0\0\234\1\0\0D\244\254E\0\0\0\0D\244\254E\0\0\0\0"..., 64) = 64 read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, [HUP INT USR1 USR2 ALRM CHLD IO], [], 8) = 0 writev(3, [{iov_base="\32\0\0\0000\0\0\0\0\0\0\0\2\0\0\0\330\3162\0\0\0\0\0\377\377\377\377\377\377\377\177"..., iov_len=64}, {iov_base="\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., iov_len=40}, {iov_base="\1\0\0\0\340\1\0\0", iov_len=8}], 3) = 112 read(5, "\3\1\0\0\0\0\0\0\377\377\377\377\377\377\377\177\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 read(7, It will sit for _forever_ that way. (At that point, it is still the socket from earlier; I actually worked backwards from the fd number in /proc/$PID/fd/7 in order to figure out where it was instantiated in the log file.) The only way out of it is to kill the process, which then wraps out the log as thus: read(7, <unfinished ...>) = ? +++ killed by SIGKILL +++ At that point, of course, the program ends and Wine shuts back down. Retrial does the same time, and it does not appear to matter what version of Windows WINE is set to report. I would _love_ to report more information. But I need to be told what to gather to turn this into a _really_ useful bug report. STO is just about the only thing I boot up Windows for... it'd sure be nice to be rid of that requirement! Thanks, and keep up the good work. -- 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.

2 5

[Bug 44545] New: LOTRO: crash on startup with D3D11 graphics
by wine-bugs＠winehq.org 08 Apr '21

08 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=44545 Bug ID: 44545 Summary: LOTRO: crash on startup with D3D11 graphics Product: Wine Version: 3.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: a34ypool3voiz(a)t-online.de Distribution: --- Created attachment 60506 --> https://bugs.winehq.org/attachment.cgi?id=60506 log after trying to enter game with D3D11 graphics While The Lord of the Rings Online (LOTRO) runs fine in Wine (target OS: Win7) with the GraphicsCore=OpenGL or GraphicsCore=D3D9 selected in .wine/drive_c/users/USERNAME/My Documents/The Lord Of The Rings Online/UserPreferences.ini, it does not work with D3D11 (or D3D10 but that is a different topic). - select Win7 as target OS in WINE - install the game from https://www.lotro.com/en/game/download and create an account - once game is installed and fully patched, click the 'v' down arrow button in the launcher, click options, and make sure "use legacy client" is checked to avoid incompatibility with the ingame store browser (this does not affect the graphics options available!) - quit the launcher - edit UserPreferences.ini and - after installation and fully patching close the launcher, edit the above UserPreferences.ini and set GraphicsCore=D3D11 . - start the launcher with "wine TurbineLauncher.exe" from the install folder - log in, select a world and start => the launcher closes, but the game engine immediately crashes without opening a window with the attached console errors -- 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.

2 5