July 2022 - Wine-bugs - list.winehq.org

[Bug 53333] New: Schneider Electric ClearSCADA 2017 R2 not starting
by WineHQ Bugzilla 11 Jul '22

11 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53333 Bug ID: 53333 Summary: Schneider Electric ClearSCADA 2017 R2 not starting Product: Wine Version: 7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pherklotz(a)pch-edv.com Distribution: --- Created attachment 72719 --> https://bugs.winehq.org/attachment.cgi?id=72719 Error log produced by wine upon crash I installed Schneider Electric ClearSCADA 2017 R2. Installation seemed to run through without major issues (including prerequisites like several Microsoft Visual C runtime packages). The application installs a server icon which is used to start / stop a server process, check server status and configuring the server. Right-clicking on the server icon brings up an error message and apparently a crash. The server never really seems to start. -- 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 0

[Bug 34235] New: SimPark requires 256 bit colors
by wine-bugs＠winehq.org 11 Jul '22

11 Jul '22

http://bugs.winehq.org/show_bug.cgi?id=34235 Bug #: 34235 Summary: SimPark requires 256 bit colors Product: Wine Version: 1.7.0 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: roland(a)mxchange.org Classification: Unclassified Created attachment 45552 --> http://bugs.winehq.org/attachment.cgi?id=45552 warn+all logfile The mentioned game wants 256 bit colors and doesn't start. I don't know which module is to look in so I have chosen "unknown". Attached is a warn+all log as the default one doesn't output anything (which is somewhere good work!). The game is a Windows 3.1x game, switching wine's Windows version to 3.1 doesn't help (and I known it won't, just to mention it). :-) -- 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 53332] New: Locomotion: Cannot start game without virtual desktop
by WineHQ Bugzilla 11 Jul '22

11 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53332 Bug ID: 53332 Summary: Locomotion: Cannot start game without virtual desktop Product: Wine Version: 7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: odecif(a)gmail.com Distribution: --- Created attachment 72717 --> https://bugs.winehq.org/attachment.cgi?id=72717 default console containing exception. When starting the game (Loco.exe) it changes the screen resolution to 800x600 and then crashes with an unhandled exception. This does not happen if you use a virtual desktop (tested with 800x600 and 1920x1080 and both worked fine). Tested in clean 64-bit prefix without overrides nor winetricks. -- 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 0

[Bug 45918] New: Not run Mass Effect 3
by wine-bugs＠winehq.org 09 Jul '22

09 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=45918 Bug ID: 45918 Summary: Not run Mass Effect 3 Product: Wine Version: 3.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Bigkreck(a)gmail.com Distribution: --- Created attachment 62443 --> https://bugs.winehq.org/attachment.cgi?id=62443 When you start the game, it gives an error, a dump in the attachment I con not run Mass Effect 3 - ver. 1.05 in wine 3.17 When you start the game, it gives an error, a dump in the attachment -- 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 4

[Bug 43030] New: LINE: Window border stays on top of other windows
by wine-bugs＠winehq.org 08 Jul '22

08 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=43030 Bug ID: 43030 Summary: LINE: Window border stays on top of other windows Product: Wine Version: 2.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kristopher(a)posteo.net Distribution: --- Created attachment 58181 --> https://bugs.winehq.org/attachment.cgi?id=58181 Screenshot of the behavior This is using the windows version of LINE from here: https://scdn.line-apps.com/client/win/new/LineInst.exe (App homepage: https://line.me/) The app seems to have a black border that follows the main window around. You can see it if you move the window around as the border stays in place, and only moves after the window finishes moving. This border stays on top of all other windows. This behaviour occurs in every window manager or DE that I have tried, so I do not think it's window manager related. I'm currently on wine-staging, but this has happened with multiple versions of 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.

2 43

[Bug 14072] New: Wine Crashes with a Stack dump
by wine-bugs＠winehq.org 08 Jul '22

08 Jul '22

http://bugs.winehq.org/show_bug.cgi?id=14072 Summary: Wine Crashes with a Stack dump Product: Wine Version: 1.0.0 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: celticht32(a)aol.com CC: celticht32(a)aol.com Wine crashes when running EverQuest2.exe : First chance exception: page fault on read access to 0x016c6580 in 32-bit code (0x00a33e9f). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:00a33e9f ESP:7eb619a4 EBP:7eb619e8 EFLAGS:00010216( - 00 -RIAP1) EAX:00000000 EBX:7bc86ae0 ECX:0000000a EDX:00000001 ESI:016c6548 EDI:00000000 Stack dump: 0x7eb619a4: 016c6550 016c6548 7bc86ae0 016eece0 0x7eb619b4: 016eece0 016eedec 00000001 7eb619e8 0x7eb619c4: 6021a9c9 7bc86ae0 ffffffff 7eb61a28 0x7eb619d4: 00817520 00a33daf 7eb61a18 00d05a44 0x7eb619e4: 00000000 7eb61a28 0081bba3 00ba7a29 0x7eb619f4: 015907a0 00ba7a95 016c6548 00ba7a29 Backtrace: =>1 0x00a33e9f in everquest2 (+0x633e9f) (0x7eb619e8) 2 0x0081bba3 in everquest2 (+0x41bba3) (0x7eb61a28) 3 0x7bc687ee call_thread_entry_point+0xe() in ntdll (0x7eb61a38) 4 0x7bc68e82 call_thread_func+0x42(rtl_func=<register EDI not in topmost frame>, arg=<register ESI not in topmost frame>) [/work/Downloads/wine-1.0/dlls/ntdll/thread.c:386] in ntdll (0x7eb61ad8) 5 0x7bc69093 in ntdll (+0x59093) (0x7eb623c8) 6 0x6013b45b (0x7eb624b8) 0x00a33e9f: cmpb $0x0,0x38(%esi) -- 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 53326] New: Wizard101 launcher images won't load
by WineHQ Bugzilla 08 Jul '22

08 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53326 Bug ID: 53326 Summary: Wizard101 launcher images won't load Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: doyoulikecake484(a)gmail.com Distribution: --- Created attachment 72708 --> https://bugs.winehq.org/attachment.cgi?id=72708 Program error details When opening the Wizard101 launcher, the graphics that're supposed to show game updates and stuff fails to load. Using Debian 11 if that's important -- 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 53325] New: Uru - Ages Beyond Myst: Installer crashes due to corefonts missing
by WineHQ Bugzilla 08 Jul '22

08 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53325 Bug ID: 53325 Summary: Uru - Ages Beyond Myst: Installer crashes due to corefonts missing Product: Wine Version: 7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: odecif(a)gmail.com Distribution: --- Created attachment 72706 --> https://bugs.winehq.org/attachment.cgi?id=72706 Crash handler Steps to reproduce: 1. Insert CD into drive 2. Open wineconsole in new prefix 3. Navigate to the disc and execute setup.exe 4. In the GUI, click install 5. Wait for the initial progress bar to finish 6. Notice the unhandled exception error popup If one installs winetricks corefonts, the exception doesn't rise. Tested in 64-bit prefix RTX 3070, proprietary drivers i9-10900K Kernel 5.10.126 Manjaro 23.1 -- 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 1

[Bug 53323] New: Wireshark doesn't update list of packets during capture
by WineHQ Bugzilla 07 Jul '22

07 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53323 Bug ID: 53323 Summary: Wireshark doesn't update list of packets during capture Product: Wine Version: 7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rpisl(a)seznam.cz Distribution: --- This is a continuation of bug 53104. Now Wireshark starts capturing packets successfully but the packets aren't shown on the list. Either "Update list of packets in real-time" option must be deselected or Ctrl+R must be pressed after capture is stopped to update the list. This bug is not very interesting as Wireshark is also native for Linux, but my unqualified guess would be that this a file/pipe handling problem in Wine. "setcap cap_net_raw,cap_net_admin=eip wine64-preloader" is needed to give Wine permissions to capture packets. -- 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 53314] New: ptrace attach timeout freezes processes to stopped state
by WineHQ Bugzilla 07 Jul '22

07 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53314 Bug ID: 53314 Summary: ptrace attach timeout freezes processes to stopped state Product: Wine Version: 7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: superemppu+winehq(a)live.fi Distribution: --- Created attachment 72691 --> https://bugs.winehq.org/attachment.cgi?id=72691 patch remove timeout When wineserver wants to attach ptrace to a process, ptrace() is first called with PTRACE_ATTACH and then wineserver waits on waitpid() until the process has received a SIGSTOP. This is correct behavior and described on ptrace manpage. https://linux.die.net/man/2/ptrace However, there is a timeout: If the SIGSTOP hasn't reached the process in 3 seconds, wineserver will give up on the PTRACE_ATTACH and immediately do a PTRACE_DETACH. According to the manpage, PTRACE_DETACH takes effect only when the process is already stopped, so that PTRACE_DETACH does nothing. When eventually the SIGSTOP reaches the process, it will be stopped forever and wineserver thinks that the ptrace session is already over. This bug only occurs when receiving a SIGSTOP takes over 3 seconds for a process. On most setups that never happens, but on slow running fuse filesystems the kernel may be in uninterruptible disk sleep for over 3 seconds. In our setup this happens consistently when the process runs on fuse-overlayfs on top of a slow NFS, and it probably happens on sshfs too. As a result, games such as Subnautica and Arma Cold War Assault freeze to stopped state. How can we fix this? Method 1: Just remove the timeout entirely (patch attached). The only case where that timeout matters is if the kernel is doing something important, in which case we should probably wait, or a kernel thread is stuck, in which case we have bigger problems. The fact that this bug has been in Wine for 20 years and not reported proves that the timeout is not triggered much. Disadvantages: If a kernel thread of one wine process is stuck, wineserver will also be stuck for other wine processes even if their kernel threads are fine. Method 2: If we want to keep the timeout, we should not do PTRACE_DETACH immediately, but rather set a flag that PTRACE_ATTACH failed. When the SIGSTOP eventually comes, a SIGCHLD will be sent to wineserver and we can do the PTRACE_DETACH in the SIGCHLD handler if the flag was set. Disadvantages: We need an arbitrary timeout. 3 seconds is not enough for slow fuse filesystems. If the timeout is triggered, processes may still crash because they could not use whatever windows API wineserver was emulating with ptrace. -- 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 1