October 2020 - Wine-Bugs - list.winehq.org

[Bug 43513] Ys VI: The Ark of Napishtim - videos are not playing

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=43513 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #5 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- (In reply to Beta Version from comment #4) > Still occur in 5.18 Could you please attach a +amstream,+quartz,+strmbase,+gstreamer log? -- 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.

Oct. 29, 2020

[Bug 50077] .NET 3.5SP1 installer depends on PEB->Reserved[1] / AtlThunkSListPtr32 being 0 or 1

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=50077 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish(a)gmail.com -- 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.

Oct. 29, 2020

[Bug 50078] New: Trying to run UFOS (1997), it crashes

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=50078 Bug ID: 50078 Summary: Trying to run UFOS (1997), it crashes Product: Wine Version: 5.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: elias_0000_0000(a)yahoo.com Distribution: --- Created attachment 68534 --> https://bugs.winehq.org/attachment.cgi?id=68534 backtrace Trying to run UFOS (1997), it crashes. The game it was found on Abandonware. -- 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.

Oct. 29, 2020

[Bug 45121] Steam uses high CPU while idle

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=45121 --- Comment #11 from andy <andy86(a)fastwebnet.it> --- I think it's not a duplicate. In bug 41304 was the process of the game to be using 100% of the cpu, in this bug is steamwebserver.exe and wineserver.exe to be using about 50%-60% of the cpu both summed. -- 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.

Oct. 29, 2020

[Bug 44061] Destiny 2 crashes on launch

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=44061 --- Comment #23 from Ker noa <blue-t(a)web.de> --- 4 crashs later the line was found again in the logfile, with a different tid. Steam is currently not running as i still need to solve a build issue with 32bit wine -- 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.

Oct. 29, 2020

[Bug 44061] Destiny 2 crashes on launch

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=44061 --- Comment #22 from David Torok <dt(a)zeroitlab.com> --- (In reply to Ker noa from comment #21) > How do you define "same crash" , which numbers and lines need to match to > say 2 runs are "the same"? The game dialog after the crash says each time > that game content could not be read and i should run the repair method in > steam. > diffing the logs shows a few blocks of messages moving around between > different runs. I define "the same crash" as having this line 0108:trace:seh:dispatch_exception code=c0000096 flags=0 addr=00000001403A13F3 ip=403a13f3 tid=0108 and then the exception handling spiraling out of control. (which you can see from all the repeated lines starting from there) Do you have windows steam installed in your wine prefix? ( You may want to have that running. ) -- 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.

Oct. 29, 2020

[Bug 44061] Destiny 2 crashes on launch

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=44061 --- Comment #21 from Ker noa <blue-t(a)web.de> --- How do you define "same crash" , which numbers and lines need to match to say 2 runs are "the same"? The game dialog after the crash says each time that game content could not be read and i should run the repair method in steam. diffing the logs shows a few blocks of messages moving around between different runs. -- 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.

Oct. 29, 2020

[Bug 44061] Destiny 2 crashes on launch

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=44061 --- Comment #20 from David Torok <dt(a)zeroitlab.com> --- (In reply to Ker noa from comment #19) > Created attachment 68533 [details] > ExtendedCrashLog Thanks. Based on that, it's not obvious to me what the issue is on your side. I think the first indication of anything being wrong is this (line 20894): 0108:trace:seh:handle_syscall_fault code=c0000005 flags=0 addr=0x7fbee62ca7fd ip=7fbee62ca7fd tid=0108 0108:trace:seh:handle_syscall_fault info[0]=0000000000000000 0108:trace:seh:handle_syscall_fault info[1]=000000000b301003 0108:trace:seh:handle_syscall_fault rax=000000000b301003 rbx=000000000ae3d520 rcx=000000000ae3d270 rdx=000000000b30006c 0108:trace:seh:handle_syscall_fault rsi=0000000000000f98 rdi=000000000b30006c rbp=000000000ae3d4d0 rsp=000000000ae3d240 0108:trace:seh:handle_syscall_fault r8=000000000b300000 r9=0000000000001000 r10=00007fbee62ed730 r11=00000000000000f9 0108:trace:seh:handle_syscall_fault r12=000000000ae3d520 r13=000000000b300000 r14=000000000b300004 r15=0000000000000000 0108:trace:seh:handle_syscall_fault returning to handler This exception - 0108:trace:seh:dispatch_exception code=c0000096 flags=0 addr=00000001403A13F3 ip=403a13f3 tid=0108 is intended, part of anti debug in Destiny however seems like wine has some issues unwinding it and faults later on (line 21225): 0108:trace:seh:dispatch_exception code=c0000005 flags=0 addr=0000000000000D68 ip=d68 tid=0108 0108:trace:seh:dispatch_exception info[0]=0000000000000008 0108:trace:seh:dispatch_exception info[1]=0000000000000d68 0108:trace:seh:dispatch_exception rax=00000000000000af rbx=000000007bc6c930 rcx=000000000ae3f380 rdx=000000000ae3d250 0108:trace:seh:dispatch_exception rsi=000000000ae3f5b0 rdi=00000000ffb80000 rbp=000000000ae3d250 rsp=000000000ae3dfd8 0108:trace:seh:dispatch_exception r8=000000000ae3e8e0 r9=000000000ae3e070 r10=000000000000000a r11=0000000000000000 0108:trace:seh:dispatch_exception r12=000000000ae3f380 r13=000000000ae3e070 r14=000000007bc7b5d8 r15=0000000000000001 For reference, I think I'm using a build very similar to yours, 5.20 staging with the patch I attached. Interestingly, which anti debug code path is chosen is random. Do you get the same crash if you try let's say 10 times? -- 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.

Oct. 29, 2020

[Bug 49788] mountmgr is no longer detecting SCSI devices

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49788 --- Comment #2 from Esme Povirk <madewokherd(a)gmail.com> --- Correction, the code was added to do this, but it's only called from libhal code so it might as well not be there. -- 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.

Oct. 29, 2020

[Bug 49788] mountmgr is no longer detecting SCSI devices

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49788 --- Comment #1 from Esme Povirk <madewokherd(a)gmail.com> --- It seems like the drives are detected, there simply wasn't any code added to mountmgr to populate that registry key. -- 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.

Oct. 29, 2020