wine-bugs February 2019

wine-bugs@winehq.org

1 participants
7691 discussions

[Bug 42595] New: Overcooked: Pink screen on startup
by wine-bugs＠winehq.org 17 Jan '22

17 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=42595 Bug ID: 42595 Summary: Overcooked: Pink screen on startup Product: Wine Version: 2.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fritz-stuhr(a)web.de Distribution: --- Created attachment 57531 --> https://bugs.winehq.org/attachment.cgi?id=57531 Output of glxinfo When launching the game Overcooked, the screen is completely pink but sound is playing, so the game probably loads fine. According to https://is.gd/fZDr0Y and https://is.gd/u0fAGt it works out of the box with wine 2.2 staging, but not for me. My guess is it depends on the graphics stack but they didn't mention theirs. The appended logs are from a wine 2.2 staging install on Lubuntu 16.04 32bit. Clean wine prefix with no settings changed. I tested on a different machine with another Intel card, I tested on 1.9.11, on 2.2 (without staging) and probably some more versions. I also tested with native DirectX 9. Same pink screen every time. I can gladly provide more logs and I can compile and test patches. -- 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 40610] New: Nota Bene crashed when I closed it.
by wine-bugs＠winehq.org 16 Jan '22

16 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=40610 Bug ID: 40610 Summary: Nota Bene crashed when I closed it. Product: Wine Version: unspecified Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lucypick(a)uchicago.edu Created attachment 54466 --> https://bugs.winehq.org/attachment.cgi?id=54466 Backtrace of error I don't know my hardware or my version of Wine, but it is probably recent since it was installed for the first time on April 28, 2016. I got an error message while I was trying to close the program. Right before I closed it, I was trying to open a new blank 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 5

[Bug 26992] New: Windows Live FolderShare 14.x needs advapi32.RegisterTraceGuidsW() impl (or at least semi-stub)
by wine-bugs＠winehq.org 16 Jan '22

16 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=26992 Summary: Windows Live FolderShare 14.x needs advapi32.RegisterTraceGuidsW() impl (or at least semi-stub) Product: Wine Version: 1.3.19 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: advapi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, Windows Live FolderShare 14.0.1383.0530 crashes on startup due to RegisterTraceGuidsW() being a stub. --- snip --- $ wine ./FolderShare.exe fixme:heap:HeapSetInformation (nil) 1 (nil) 0 11:27:22.265 core.cpp:1112!initPaths (NORMAL): got application exec location: C:\Program Files\Windows Live\FolderShare 11:27:22.269 configfile.cpp:176!readConfigFile (CRITICAL): unable to open config file: C:\users\focht\Local Settings\Application Data\FolderShare\settings\global.ini, err: 2 11:27:22.269 core.cpp:1464!loadGlobalSettings (ERROR): Error reading config file 'C:\users\focht\Local Settings\Application Data\FolderShare\settings\global.ini',readConfigFile returned 0, fileSize is -1 Opened log: C:\users\focht\Local Settings\Application Data\FolderShare\logs\%COMPUTERNAME%.dev=0.2011-05-01.1127.8-1.log fixme:advapi:RegisterTraceGuidsW (0x4bdb18, (nil), {fde002b2-8125-44b2-b3ca-a6f8549c91bf}, 3, 0x32f11c, (null), (null), 0x500340,) wine: Unhandled exception 0x80000003 at address 0x4b691d (thread 0009), starting debugger... --- snip --- Logfile: --- snip --- 11:28:54.762 global.cpp:175!InitLogger (DETAIL): InitLogger called. outputMask: 2, serverType: 3, maxMegaBytes: 5 11:28:54.763 etw.cpp:193!Etw::RegisterTracing (CRITICAL): FAILED: assert(result == NO_ERROR) --- snip --- Trace log: --- snip --- 0027:Call advapi32.RegisterTraceGuidsW(004bdb18,00000000,004e74d0,00000003,0032f11c,00000000,00000000,00500340) ret=004bdc54 0027:fixme:advapi:RegisterTraceGuidsW (0x4bdb18, (nil), {fde002b2-8125-44b2-b3ca-a6f8549c91bf}, 3, 0x32f11c, (null), (null), 0x500340,) 0027:Ret advapi32.RegisterTraceGuidsW() retval=00000078 ret=004bdc54 ... 0027:trace:seh:raise_exception code=80000003 flags=0 addr=0x4b691d ip=004b691e tid=0027 0027:trace:seh:raise_exception eax=00000000 ebx=ffffffff ecx=338ba91e edx=004fee04 esi=0043ed68 edi=00443dd4 0027:trace:seh:raise_exception ebp=0032f0f8 esp=0032f0f4 cs=0073 ds=007b es=007b fs=0033 gs=003b flags=00000202 0027:trace:seh:call_vectored_handlers calling handler at 0x68ca76fe code=80000003 flags=0 0027:trace:seh:call_vectored_handlers handler at 0x68ca76fe returned 0 0027:trace:seh:call_stack_handlers calling handler at 0x452d10 code=80000003 flags=0 0027:Call KERNEL32.GetLastError() ret=00452823 0027:Ret KERNEL32.GetLastError() retval=00000000 ret=00452823 0027:Call KERNEL32.UnhandledExceptionFilter(0032ebec) ret=00451cec wine: Unhandled exception 0x80000003 at address 0x4b691d (thread 0027), starting debugger... --- snip --- --- snip dlls/advapi32/eventlog.c --- ULONG WINAPI RegisterTraceGuidsW( WMIDPREQUEST RequestAddress, PVOID RequestContext, LPCGUID ControlGuid, ULONG GuidCount, PTRACE_GUID_REGISTRATION TraceGuidReg, LPCWSTR MofImagePath, LPCWSTR MofResourceName, PTRACEHANDLE RegistrationHandle ) { FIXME("(%p, %p, %s, %u, %p, %s, %s, %p,)\n", RequestAddress, RequestContext, debugstr_guid(ControlGuid), GuidCount, TraceGuidReg, debugstr_w(MofImagePath), debugstr_w(MofResourceName), RegistrationHandle); return ERROR_CALL_NOT_IMPLEMENTED; } --- snip dlls/advapi32/eventlog.c --- Regards -- 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 6

[Bug 15220] New: fails to run PeachTree Accounting 8.0 fails with timezone error
by wine-bugs＠winehq.org 16 Jan '22

16 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=15220 Summary: fails to run PeachTree Accounting 8.0 fails with timezone error Product: Wine Version: 1.0.0 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: cjc(a)CosmosEng.com Created an attachment (id=15975) --> (http://bugs.winehq.org/attachment.cgi?id=15975) WINEDEBUG=+relay .wine/drive_c/Peachw/peachw.exe &>wine-pt.out Error message on failure to load: > cjc@Home:~$ .wine/drive_c/Peachw/peachw.exe > fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for bias 480, std (d/m/y): 2/11/2008, dlt (d/m/y): 9/03/2008 > fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for bias 480, std (d/m/y): 2/11/2008, dlt (d/m/y): 9/03/2008 Other info: wine v 1.0 Ubuntu 8.04 LTS gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7) peachtree accounting 8.0 -- 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 10

[Bug 34340] New: Mingw gdb hangs
by wine-bugs＠winehq.org 16 Jan '22

16 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=34340 Bug #: 34340 Summary: Mingw gdb hangs Product: Wine Version: 1.7.0 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: ralf.habacker(a)freenet.de Classification: Unclassified Running gdb 7.6 hangs on all commands. A workaround i found out is to run gdb in wineconsole e.g. wineconsole --backend=curses gdb ... -- 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 13

[Bug 27368] New: IDriver.exe crahses during installation of Peachtree Complete Accounting 2004
by wine-bugs＠winehq.org 16 Jan '22

16 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=27368 Summary: IDriver.exe crahses during installation of Peachtree Complete Accounting 2004 Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: loader AssignedTo: wine-bugs(a)winehq.org ReportedBy: m_almazan(a)yahoo.com "The program IDriver.exe has encountered a serious problem and needs to close." Problem message: 1628 Failed to complete installation -- 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 9

[Bug 33555] New: Peachtree Quantum 2010 Accountant Edition post-install COM inproc server registration hangs on PEB lock (process exit)
by wine-bugs＠winehq.org 16 Jan '22

16 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=33555 Bug #: 33555 Summary: Peachtree Quantum 2010 Accountant Edition post-install COM inproc server registration hangs on PEB lock (process exit) Product: Wine Version: 1.5.29 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello folks, while investigating bug 18935 I noticed a problem in COM inproc server registration during post-install of "Peachtree Quantum 2010 Accountant Edition". The COM inproc server in question is a mixed mode assembly (.NET 2.0). --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/Sage Software/Peachtree $ file PAWLegacy.dll PAWLegacy.dll: PE32 executable (DLL) (GUI) Intel 80386 Mono/.Net assembly, for MS Windows $ wine regsvr32 "C:\\PROG~FBU\\SAGE~XMD\\PEAC~IU0\\PAWLegacy.dll" ... 000a:Starting process L"C:\\windows\\system32\\regsvr32.exe" (entryproc=0x7effcfd4) ... 000a:Call KERNEL32.LoadLibraryExA(0011515d "C:\\PROG~FBU\\SAGE~XMD\\PEAC~IU0\\PAWLegacy.dll",00000000,00000008) ret=7effc7f2 ... 000a:Ret PE DLL (proc=0x109ed6aa,module=0x10000000 L"PAWLegacy.dll",reason=PROCESS_ATTACH,res=(nil)) retval=1 000a:Ret KERNEL32.LoadLibraryExA() retval=10000000 ret=7effc7f2 000a:Call KERNEL32.GetProcAddress(10000000,7effd24e "DllRegisterServer") ret=7effc844 000a:Ret KERNEL32.GetProcAddress() retval=00e04f39 ret=7effc844 000a:CALL PAWLegacy.DllRegisterServer(<unknown, check return>) ret=7effc8e1 ... Successfully registered DLL C:\PROG~FBU\SAGE~XMD\PEAC~IU0\PAWLegacy.dll 000a:Call KERNEL32.FreeLibrary(10000000) ret=7effc945 000a:Ret KERNEL32.FreeLibrary() retval=00000001 ret=7effc945 000a:Call ole32.OleUninitialize() ret=7effcfc3 ... 000a:Ret ole32.OleUninitialize() retval=00000000 ret=7effcfc3 000a:Call KERNEL32.ExitProcess(00000000) ret=7effd062 000a:Call PE DLL (proc=0xf60c66d0,module=0xf60c0000 L"comcat.dll",reason=PROCESS_DETACH,res=0x1) 000a:Ret PE DLL (proc=0xf60c66d0,module=0xf60c0000 L"comcat.dll",reason=PROCESS_DETACH,res=0x1) retval=1 000a:Call PE DLL (proc=0x7907e547,module=0x79060000 L"mscorjit.dll",reason=PROCESS_DETACH,res=0x1) ... 000a:Ret PE DLL (proc=0x6f11db,module=0x6d0000 L"pscore3.dll",reason=PROCESS_DETACH,res=0x1) retval=1 000a:Call PE DLL (proc=0xf69ff77c,module=0xf69f0000 L"mpr.dll",reason=PROCESS_DETACH,res=0x1) 000a:Ret PE DLL (proc=0xf69ff77c,module=0xf69f0000 L"mpr.dll",reason=PROCESS_DETACH,res=0x1) retval=1 000a:Call PE DLL (proc=0x19082444,module=0x19000000 L"Pchlib32.dll",reason=PROCESS_DETACH,res=0x1) 000a:CALL mfc90.1241(190bd408,00000000) ret=19060e1c 000a:Call msvcrt.memset(786dbb50,00000000,00001800) ret=78610ded 000a:Ret msvcrt.memset() retval=786dbb50 ret=78610ded 000a:RET mfc90.1241() retval=786dbb50 ret=19060e1c 000a:Call KERNEL32.DeleteAtom(0000c000) ret=19060f51 000a:Ret KERNEL32.DeleteAtom() retval=00000000 ret=19060f51 000a:Call KERNEL32.DeleteAtom(0000c001) ret=19060f5f 000a:Ret KERNEL32.DeleteAtom() retval=00000000 ret=19060f5f 000a:Call msvcrt.free(001c38b8) ret=1903e047 000a:Call ntdll.RtlFreeHeap(00110000,00000000,001c38b8) ret=f7377f2b 000a:Ret ntdll.RtlFreeHeap() retval=00000001 ret=f7377f2b 000a:Ret msvcrt.free() retval=00000001 ret=1903e047 000a:Call ole32.CoUninitialize() ret=19060f90 000a:Call KERNEL32.SetEvent(0000021c) ret=7ecb64f0 0026:Ret KERNEL32.WaitForMultipleObjects() retval=00000001 ret=7ecb5b8f 0026:Call KERNEL32.CloseHandle(00000220) ret=7ecb5baa 000a:Ret KERNEL32.SetEvent() retval=00000001 ret=7ecb64f0 000a:Call KERNEL32.WaitForSingleObject(00000224,ffffffff) ret=7ecb6509 0026:Ret KERNEL32.CloseHandle() retval=00000001 ret=7ecb5baa 0026:Call KERNEL32.CloseHandle(00000234) ret=7ecb61b0 0026:Ret KERNEL32.CloseHandle() retval=00000001 ret=7ecb61b0 001a:Ret KERNEL32.WaitForSingleObjectEx() retval=00000102 ret=79e77fd1 001a:Call KERNEL32.GetLastError() ret=79e74ab4 001a:Ret KERNEL32.GetLastError() retval=00000000 ret=79e74ab4 001a:Call KERNEL32.GetLastError() ret=79e74ade 001a:Ret KERNEL32.GetLastError() retval=00000000 ret=79e74ade 001a:Call KERNEL32.WaitForMultipleObjects(00000002,7a381bb8,00000000,ffffffff) ret=79f8d98a 000e:err:ntdll:RtlpWaitForCriticalSection section 0x7bcd0dc0 "/home/focht/projects/wine/wine-git/dlls/ntdll/rtl.c: peb_lock" wait timed out in thread 000e, blocked by 000a, retrying (60 sec) 0026:err:ntdll:RtlpWaitForCriticalSection section 0x7bcd0dc0 "/home/focht/projects/wine/wine-git/dlls/ntdll/rtl.c: peb_lock" wait timed out in thread 0026, blocked by 000a, retrying (60 sec --- snip --- The additional threads are .NET CLR/COM remoting helper threads. I remembered some recent changes in that area, specifically process exit behaviour (PEB lock). http://source.winehq.org/git/wine.git/commitdiff/77f222505cdb392f2880932671… ("kernel32: Hold PEB lock during process exit.") Indeed, reverting that commit lets regsvr32 successfully exit. Regards -- 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 9

[Bug 18935] New: Peachtree First Accounting 2010 install fails because it can't find AVManagerUnified.dll
by wine-bugs＠winehq.org 16 Jan '22

16 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=18935 Summary: Peachtree First Accounting 2010 install fails because it can't find AVManagerUnified.dll Product: Wine Version: 1.1.23 Platform: PC URL: http://www.peachtree.com/productsServices/tryPeachtree / OS/Version: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com The installer aborts with the error Error Number: 0x80040702 Description: Failed to load DLL: SASLib Setup will now terminate. SASLib.dll and its dependency AVManagerUnified.dll are located in c:\windows\temp\{*}\ SASLib.dll fails to load because it can't find AVManagerUnified.dll. Is Wine supposed to search the directory containing a DLL for things that DLL depends on? -- 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 10

[Bug 27385] New: Peachtree First Accounting 2012 install fails because USER32.DLL GetListBoxInfo not found
by wine-bugs＠winehq.org 16 Jan '22

16 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=27385 Summary: Peachtree First Accounting 2012 install fails because USER32.DLL GetListBoxInfo not found Product: Wine Version: 1.3.21 Platform: x86-64 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: frederic.delanoy(a)gmail.com Installation aborts due to (popup) error stating that "The procedure GetListBoxInfo could not be located in the DLL USER32.dll" -- 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 46304] New: Fog handling seems to be off in Prince of Persia
by wine-bugs＠winehq.org 16 Jan '22

16 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=46304 Bug ID: 46304 Summary: Fog handling seems to be off in Prince of Persia Product: Wine Version: 3.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gw.fossdev(a)gmail.com Distribution: --- Created attachment 63028 --> https://bugs.winehq.org/attachment.cgi?id=63028 apitrace dump of frame that contains shader: Hello, I came across this by trying out Prince of Persia with virgl ad a driver and comparing it to the host. Initially I thought it was a virgl bug, but it seems to be proper wine where things go wrong: Here are my findings: When I run "wine PrinceOfPersia.exe" on the host (r600) the game is playable but when run with the virgl driver there is not contrast in the images. However, a apitrace created with virgl as driver and replayed on host also renders wrong, where a apitrace recorded on the host and run via virgl renders correctly (only op-side down, because virgl doesn't support GL_ARB_clip_control, but disabling this extension when recording the apitrace makes it possible to get exactly the same output like when run on the r600 host. The difference between the two runs in the apitrace is that when run on r600 I get a vertex shader that does: R6.w = (R6.w * vs_c[20].z); R6.w = (vs_c[20].z + -R6.w); vs_out[11].x = (vs_c[16].y + -R6.w); vs_out[10].xyzw = (R8.xyzw); setup_vs_output(vs_out); The same shader created via virgl does: R6.w = (vs_c[16].y + -R6.w); vs_out[11].x = (R6.w * vs_c[20].z); vs_out[10].xyzw = (R8.xyzw); setup_vs_output(vs_out); ffp_varying_fogcoord = gl_Position.z; gl_Position.y = gl_Position.y * pos_fixup.y; The value ffp_varying_fogcoord is not assigned a value with the r600 version. However, the following fragment shader uses this value in both cases: float fog = (ffp_fog.end - ffp_varying_fogcoord) * ffp_fog.scale; ps_out[0].xyz = mix(ffp_fog.color.xyz, ps_out[0].xyz, clamp(fog, 0.0, 1.0)); In the r600 version ffp_fog.end=0 and ffp_fog.scale=-1, and I assume that this results in clamp(fog, 0.0, 1.0) returning 1.0, and in the scene the fog effect seems to be generated differently. In the virgl version the values are ffp_fog.end=1 and ffp_fog.scale=1, and I can only assume that gl_Position too large so that clamp(fog, 0.0, 1.0) returns very small values (or even 0) and the scene gets rendered in the fog colour overlayed by some post processing effects. I have not yet investigated why wine creates different code path for the two drivers, I guess that it depends on some extension(s) that may or may not be available. The initial but report for virglrenderer can be found here: https://gitlab.freedesktop.org/virgl/virglrenderer/issues/62 -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs February 2019