September 2021 - Wine-bugs - list.winehq.org

[Bug 39793] New: Starcraft freezes when starting a Direct Cable Connection game
by wine-bugs＠winehq.org 22 Jan '24

22 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=39793 Bug ID: 39793 Summary: Starcraft freezes when starting a Direct Cable Connection game Product: Wine Version: 1.7.46 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- To reproduce: 1. Add yourself to the dialout (Ubuntu) or uucp (Arch) user group. 2. Log out and log back in. 3. In Starcraft, click Multiplayer, Direct Cable Connection, Ok. The problem is that Starcraft attempts to detect which serial port is connected by sending a burst of data on all ports COM1 through COM8. On Linux, COM1 through COM4 default to ttyS0 through ttyS3, but even though the device files exist, rarely do all of them correspond to actual physical devices. So, Starcraft hangs forever waiting for the write to complete successfully. A patchset that fixes this bug is available at https://github.com/alexhenrie/wine/commits/master First reported at https://appdb.winehq.org/objectManager.php?sClass=version&iId=149&iTestingI… -- 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 14

[Bug 48908] New: Dr Brain 3 broken color palette
by WineHQ Bugzilla 21 Jan '24

21 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=48908 Bug ID: 48908 Summary: Dr Brain 3 broken color palette Product: Wine Version: 5.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maxmusterm(a)gmail.com Distribution: --- Created attachment 66865 --> https://bugs.winehq.org/attachment.cgi?id=66865 Example image of dr brain running in xephyr Dr Brain 3 is a 16bit Windows program that requires 8bit colors. So to get it running we have to use one of these methods https://wiki.winehq.org/256_Color_Mode I tried every last one of those methods and every method leads to the same result you can see in the image attached to this bug. No error message is printed out by wine. I encountered this bug a few years ago for the first time, but didn't open a bug report for it, since I thought this could be a problem with the virtual X. However when viewing images in the Xephyr session all colors are displayed correctly. Right now the only way for me to run this game is using dosbox with win3.1 or another form of emulation. -- 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 27668] New: SecuROM 4.X: SpellForce won't recognize original CD during install/play
by wine-bugs＠winehq.org 20 Jan '24

20 Jan '24

http://bugs.winehq.org/show_bug.cgi?id=27668 Summary: SecuROM 4.X: SpellForce won't recognize original CD during install/play Product: Wine Version: 1.3.22 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: frans.kool(a)gmail.com Created an attachment (id=35387) --> (http://bugs.winehq.org/attachment.cgi?id=35387) The basic log while running wine on a copied installation of Spellforce While trying to install Spellforce - the Order of the Dawn v1.01 a window pops up notifying "Incompatible system configuration", followed by "Please insert the original Spellforce CD1 into your CD/DVD-drive.". After this, install immediately aborts and thus leaves the game uninstallable. Copying it from a windows installation and running it generates the same error message. Wine produces this fixme which I think is the cause: fixme:ntdll:server_ioctl_file Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) I ran Protection ID v0.6.4.0 July and it detects SecuROM 4.88.00 This is why I did not add my comment to bug #21448, since that one is clearly about SecuROM 5.x. I added the log as attachement, please let me know if I can run additional DEBUG logs for more information. -- 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 15

[Bug 34658] New: Bioshock 2 runs out of GL memory quickly
by wine-bugs＠winehq.org 20 Jan '24

20 Jan '24

http://bugs.winehq.org/show_bug.cgi?id=34658 Bug #: 34658 Summary: Bioshock 2 runs out of GL memory quickly Product: Wine Version: 1.7.3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: descent1(a)gmx.net Classification: Unclassified Created attachment 46195 --> http://bugs.winehq.org/attachment.cgi?id=46195 Console output Note: This is about the new Bioshock 2 version on Steam (1.5.0.019) which has GFWL and SecuROM officially removed - no cracks have been used! When playing single player in Bioshock 2 on highest settings, the game runs out of memory with this message: "err:d3d:resource_init Failed to allocate system memory." I'm sure that I got this message as well a lot of times, but for some reason, the message is now different: "err:d3d_surface:surface_allocate_surface >>>>>>>>>>>>>>>>> GL_OUT_OF_MEMORY" I've set my video RAM amount in the registry to 1024 MB which is correct for my GPU. If i decrease it to e.g. 768 MB, the game crashes a lot sooner. See console output attached. I tried those wine versions: 1.5.12, 1.6, 1.7.3 Tested on openSUSE 12.2 x86 NVidia GeForce GTX 460 (1024 MB RAM) using driver version 319.49 -- 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 34

[Bug 28863] New: SecuROM 8.xx: games require activation on each start
by wine-bugs＠winehq.org 20 Jan '24

20 Jan '24

http://bugs.winehq.org/show_bug.cgi?id=28863 Bug #: 28863 Summary: SecuROM 8.xx: games require activation on each start Product: Wine Version: 1.3.31 Platform: x86 OS/Version: Linux Status: NEW Keywords: obfuscation Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Classification: Unclassified Created attachment 37073 --> http://bugs.winehq.org/attachment.cgi?id=37073 7zipped +relay,+tid,+file,+reg log (uncompressed 118 MB) Two of my games obtained via Gamersgate digital distribution service are damned with Securom 8.03.xxxx protection (online activation). The games are Tomb Raider: Legend GTA San Andreas After installation the Securom activation dialog kicked in, requesting the serial number. Activation was successful and the games started fine. Much to my surprise, next time I launched these games, Securom required a new activation. This happens on each game start (I didn't alter the wineprefix where the games are installed in any way). I installed one of the games in Win XP SP3 (running under Vbox): Securom works there, requiring activation only on the first launch. Here I'm attaching a +relay,+tid,+file,+reg debug log, hopefully someone will find some clues in it. The log was created by getting through the activation process (the game wasn't started at the end of activation). I'm totally dumb at reading such logs but here's what I found: 1. Securom tries to open certain files under 'C:\users\<username>\Application Data\DSS\Product Activation\ User Data\<very long sequence\' The files named dss_v8_01.dat and dss_v8_01.bak. These files as well as the whole directory structure are missing in both Wine and Windows so this can't be the problem. 2. The corresponding Securom registry entry is located under HKCU/Software/DSS. This contains several subkeys, most of them contain binary data, but one of them (Meta Data\Information) contains strange things. Although this subkey can be exported via Wine regedit, it cannot be re-imported correctly. Here is an excerpt what this sub key contains (obtained via Process Monitor under Windows): Type: REG_SZ, Length: 2,600, Data: <?xml version="1.0"?> <UserData> <ExeResource> <Path>C:\Program Files\Rockstar Games\GTA San Andreas\gta_sa.exe</Path> </ExeResource> <CPA>e358d8ee7c711c17f463b620e750df01e896d4e1bdfc0e37d2357859698229f6e896d4e1bdfc0e37cdb6c31028aa1089</CPA> <OfflineInformation> <LASTACCESSDATE>000fb756</LASTACCESSDATE> <INSTALLDATE>000fb756</INSTALLDATE> <COUNTER>00000000</COUNTER> <FIRSTTIME>00000001</FIRSTTIME> <PERIODIC>00000000</PERIODIC> <PERIODICDAYS>00000000</PERIODICDAYS> </OfflineInformation> <ProductActivation> ... Maybe something goes wrong when creating/reading this key under Wine thus Securom considers it invalid? Fedora 15 x86 gcc version 4.6.1 20110908 (Red Hat 4.6.1-9) (GCC) -- 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 36

[Bug 45926] New: Windows Sysinternals ProcessExplorer v12-16+ crashes due to missing advapi32.I_QueryTagInformation () stub
by wine-bugs＠winehq.org 20 Jan '24

20 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=45926 Bug ID: 45926 Summary: Windows Sysinternals ProcessExplorer v12-16+ crashes due to missing advapi32.I_QueryTagInformation() stub Product: Wine Version: 3.17 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. --- snip --- $ WINEDEBUG=+seh,+relay wine ./procexp64.exe >>log.txt 2>&1 ... 002d:Call KERNEL32.LoadLibraryW(1400d20a8 L"advapi32.dll") ret=140080b4a 002d:Ret KERNEL32.LoadLibraryW() retval=7f4d2a1a0000 ret=140080b4a 002d:Call KERNEL32.GetProcAddress(7f4d2a1a0000,1400ecf08 "I_QueryTagInformation") ret=140080b5a 002d:Ret KERNEL32.GetProcAddress() retval=00000000 ret=140080b5a ... 002d:trace:seh:NtRaiseException code=c0000005 flags=0 addr=(nil) ip=0 tid=002d 002d:trace:seh:NtRaiseException info[0]=0000000000000008 002d:trace:seh:NtRaiseException info[1]=0000000000000000 002d:trace:seh:NtRaiseException rax=0000000000000001 rbx=000000014012c9c8 rcx=0000000000000000 rdx=0000000000000003 002d:trace:seh:NtRaiseException rsi=000000014012c9c0 rdi=000000014012c9d0 rbp=0000000000000000 rsp=000000000023f9b8 002d:trace:seh:NtRaiseException r8=000000000023f9e0 r9=000000014012c9c8 r10=0000000000000000 r11=0000000000000246 002d:trace:seh:NtRaiseException r12=0000000140126560 r13=0000000000000000 r14=000000000000000a r15=0000000140000000 002d:trace:seh:RtlVirtualUnwind type 1 rip 14006377a rsp 23f9c0 002d:trace:seh:dump_unwind_info **** func 63720-637a6 --- snip --- Disassembly at crash site (running under x64dbg): --- snip --- 0000000140063720 | mov qword ptr ss:[rsp+8],rbx | 0000000140063725 | mov qword ptr ss:[rsp+10],rbp | 000000014006372A | mov qword ptr ss:[rsp+18],rsi | 000000014006372F | push rdi | 0000000140063730 | sub rsp,30 | 0000000140063734 | mov rsi,rcx | 0000000140063737 | mov rcx,qword ptr ds:[rcx] | 000000014006373A | mov rbx,r9 | 000000014006373D | mov rdi,r8 | 0000000140063740 | mov rbp,rdx | 0000000140063743 | test rcx,rcx | 0000000140063746 | je procexp64.14006375B | 0000000140063748 | call qword ptr ds:[1400D0958] | 000000014006374E | mov qword ptr ds:[rbx],0 | 0000000140063755 | mov dword ptr ds:[rdi],0 | 000000014006375B | lea r8,qword ptr ss:[rsp+20] | 0000000140063760 | mov edx,3 | 0000000140063765 | xor ecx,ecx | 0000000140063767 | mov dword ptr ss:[rsp+20],ebp | 000000014006376B | mov qword ptr ss:[rsp+28],0 | 0000000140063774 | call qword ptr ds:[14012CC68] | NULL *boom* 000000014006377A | test eax,eax | 000000014006377C | jne procexp64.140063791 | 000000014006377E | mov rdx,qword ptr ss:[rsp+28] | 0000000140063783 | mov ecx,dword ptr ds:[rdx] | 0000000140063785 | mov dword ptr ds:[rdi],ecx | 0000000140063787 | mov rcx,qword ptr ds:[rdx+8] | 000000014006378B | mov qword ptr ds:[rbx],rcx | 000000014006378E | mov qword ptr ds:[rsi],rdx | 0000000140063791 | mov rbx,qword ptr ss:[rsp+40] | 0000000140063796 | mov rbp,qword ptr ss:[rsp+48] | 000000014006379B | mov rsi,qword ptr ss:[rsp+50] | 00000001400637A0 | add rsp,30 | 00000001400637A4 | pop rdi | 00000001400637A5 | ret | --- snip --- Using the "find references to address" method for 0x14012CC68 one comes across this: --- snip --- 0000000140080B4A | lea rdx,qword ptr ds:[1400ECF08] | "I_QueryTagInformation" 0000000140080B51 | mov rcx,rax | 0000000140080B54 | call qword ptr ds:[1400D0968] | 0000000140080B5A | lea rcx,qword ptr ds:[1400ECF30] | L"wow64cpu" 0000000140080B61 | mov qword ptr ds:[14012CC68],rax | --- snip --- which corresponds to the trace log snippet earlier. At one point Wine might implement service process tags as well for mapping service hosting threads with their owner service. Service tags were introduced with Windows Vista. The tag is contained in the TEB of every thread (sub-process tag) and is used in threads owned by service processes as a way to link them with their owning service name. https://github.com/processhacker/processhacker/blob/master/phlib/svcsup.c#L… --- snip --- PPH_STRING PhGetServiceNameFromTag( _In_ HANDLE ProcessId, _In_ PVOID ServiceTag ) { static PQUERY_TAG_INFORMATION I_QueryTagInformation = NULL; PPH_STRING serviceName = NULL; TAG_INFO_NAME_FROM_TAG nameFromTag; if (!I_QueryTagInformation) { I_QueryTagInformation = PhGetDllProcedureAddress(L"advapi32.dll", "I_QueryTagInformation", 0); if (!I_QueryTagInformation) return NULL; } memset(&nameFromTag, 0, sizeof(TAG_INFO_NAME_FROM_TAG)); nameFromTag.InParams.dwPid = HandleToUlong(ProcessId); nameFromTag.InParams.dwTag = PtrToUlong(ServiceTag); I_QueryTagInformation(NULL, eTagInfoLevelNameFromTag, &nameFromTag); if (nameFromTag.OutParams.pszName) { serviceName = PhCreateString(nameFromTag.OutParams.pszName); LocalFree(nameFromTag.OutParams.pszName); } return serviceName; } --- snip --- https://github.com/processhacker/processhacker/blob/2bb718f36a702fde6cb346e… --- snip --- _Must_inspect_result_ DWORD WINAPI I_QueryTagInformation( _In_opt_ LPCWSTR pszMachineName, _In_ TAG_INFO_LEVEL eInfoLevel, _Inout_ PVOID pTagInfo ); --- snip --- $ sha1sum ProcessExplorer.zip 97d882b15890471ea9942c80997c180fbfcbba26 ProcessExplorer.zip $ du -sh ProcessExplorer.zip 1.9M ProcessExplorer.zip $wine --version wine-3.17-39-gc96eba60e3 Regards -- 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 3

[Bug 31076] New: WinDirStat problem after clicking on file in graphical analysis
by wine-bugs＠winehq.org 20 Jan '24

20 Jan '24

http://bugs.winehq.org/show_bug.cgi?id=31076 Bug #: 31076 Summary: WinDirStat problem after clicking on file in graphical analysis Product: Wine Version: 1.5.7 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: computergeoffrey(a)zoho.com Classification: Unclassified Created attachment 40789 --> http://bugs.winehq.org/attachment.cgi?id=40789 Exception details "WinDirStat encountered an error and must be closen down." after clicking on a file in the graphical output window. Download here: http://windirstat.info/download.html See also attachment. -- 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 34

[Bug 31145] New: WinDirStat right clicking on a directory and selecting properties says "invalid parameter"
by wine-bugs＠winehq.org 20 Jan '24

20 Jan '24

http://bugs.winehq.org/show_bug.cgi?id=31145 Bug #: 31145 Summary: WinDirStat right clicking on a directory and selecting properties says "invalid parameter" Product: Wine Version: 1.5.8 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: computergeoffrey(a)zoho.com Classification: Unclassified After analysis of a directory, right clicking on a directory (doesn't matter which, as long it's in the "scope" of the analysis) and selecting properties shows the error message "invalid parameter". -- 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 22

[Bug 51446] New: VICE X64.exe crashing (from within C64forever from cloanto)
by WineHQ Bugzilla 19 Jan '24

19 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=51446 Bug ID: 51446 Summary: VICE X64.exe crashing (from within C64forever from cloanto) Product: Wine-staging Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: marcok(a)web.de CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 70295 --> https://bugs.winehq.org/attachment.cgi?id=70295 Backtrace hi! >From within c64forever x64.exe is crashing. See attached report -- 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 43102] New: GTA V keyboard issue
by wine-bugs＠winehq.org 19 Jan '24

19 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=43102 Bug ID: 43102 Summary: GTA V keyboard issue Product: Wine Version: 2.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xsellier(a)gmail.com Distribution: Debian Hey folks, Thank you for you amazing work here. I have a bug when I try to play GTA V. This bug is related to the keyboard. *How to reproduce it* 1. Install wine 2.9 with following components: - d3dcompiler_43 - d3dx11 2. Run winecfg and set the windows version to Windows XP 3. Install steam 4. Install GTA V 5. Run GTA V (login to the social club) 6. Once the game has started do the ALT+TAB trick (https://bugs.winehq.org/show_bug.cgi?id=42330#c18) 7. Press any key of the keyboard (it works flawlessly) 8. Select the Story Mode 9. Once in game, press any key from the keyboard. Now the game is freezing for a 2 second and it will work again. This issue is related to the keyboard, because if you are using a controller (xbox for example) it works without any stutter. But press a key of the keyboard and the freeze is coming (sorry for this one). *Observation* - The sound is still playing - Only the rendering is frozen -- 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 51