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

[Bug 44697] New: Dark Souls: Prepare to Die Edition 2.0 - Cinematics Audio Drops Intermittently
by wine-bugs＠winehq.org 12 Oct '20

12 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=44697 Bug ID: 44697 Summary: Dark Souls: Prepare to Die Edition 2.0 - Cinematics Audio Drops Intermittently Product: Wine Version: 3.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: escomk3(a)hotmail.com Distribution: --- Created attachment 60707 --> https://bugs.winehq.org/attachment.cgi?id=60707 Terminal Output (+tid) While playing a video, such as the opening cinematics, the audio drops now and then, but keeps in sync just fine. -- 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 49745] New: SHRunControlPanel implementation
by WineHQ Bugzilla 12 Oct '20

12 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49745 Bug ID: 49745 Summary: SHRunControlPanel implementation Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: contact(a)kcsoftwares.com Distribution: --- SHRunControlPanel is currently only a stub. I propose an implementation based on ShellExecuteW : [Shellord.c] BOOL WINAPI SHRunControlPanel (LPCWSTR commandLine, HWND parent) { HINSTANCE hr; TRACE("SHRunControlPanel(%s, %p)n", debugstr_w(commandLine), parent); hr = ShellExecuteW(parent, NULL, commandLine, NULL, NULL, SW_NORMAL); return ((int)hr > 32); } -- 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 7

[Bug 38227] New: wine crashes when running quotetracker
by wine-bugs＠winehq.org 12 Oct '20

12 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=38227 Bug ID: 38227 Summary: wine crashes when running quotetracker Product: Wine Version: 1.7.38 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: rockman6112(a)yahoo.com CC: rockman6112(a)yahoo.com Distribution: --- Created attachment 51029 --> https://bugs.winehq.org/attachment.cgi?id=51029 crash info given by wine 1. the crash is reproducible for both wine 1.7 and 1.6 on ubuntu 14.04. 2. the exact same quotetracker setup ran with wine 1.4 on unbuntu 10.04 for several years without any issues. 3. this bug is timing related in multi-processes(threads): a. if the application has two open windows, no crash is observed. if the application has more than 10 windows openned, it usually will crash within 60 minutes. b. with using +relay, no crash was observered even after more than 100GB debugging data was logged from the command line output. In this case, the application takes more cpu load due to the logging process. 4. no err from the debug logging(class ERR). 5. There is an overhead in the setup to reproduce the bug, especially it needs to get real time stock quote streaming. But I can be a big helper on this: such as turning on a given set of debug parameters, even things like getting instrumented code from the developer and compile/install wine on my system. So please feel free to contact me in the bug fixing process. -- 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 45124] New: Fortnite: crash when loading battle royal lobby
by wine-bugs＠winehq.org 10 Oct '20

10 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=45124 Bug ID: 45124 Summary: Fortnite: crash when loading battle royal lobby Product: Wine Version: 3.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ado92300(a)gmail.com Distribution: --- Created attachment 61306 --> https://bugs.winehq.org/attachment.cgi?id=61306 wine log of launching fortnite As of Fortnite 4.0/for now, battle eye is not required to play fortnite and when run through wine the launcher will set -nobe (no battleeye) and fortnite launches with out this bug https://bugs.winehq.org/show_bug.cgi?id=41670. But once you load the title screen and select battle royal it crashes without a clear error (in wine output). I included the log of wine64 (Wine 3.7 Staging) and the UE4 Log for fortnite the only dll override set is shcore to disabled because the launcher wont load with it note: sometimes i can hear the battle royal intro video but never see it -- 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 32073] New: Some chars are mapped as dead key
by wine-bugs＠winehq.org 10 Oct '20

10 Oct '20

http://bugs.winehq.org/show_bug.cgi?id=32073 Bug #: 32073 Summary: Some chars are mapped as dead key Product: Wine Version: 1.5.16 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: cerebro.alexiel(a)gmail.com Classification: Unclassified When I use TapTouche, a typing training software, it warns me my keyboard is mis-configured and disables automatically some exercices. I installed it in an XP VM, compared with wine and found that exercices using the following chars were not available in wine : é ç à ù â ê û î ô É È Ç À Ù Â Ê Û Î Ô Thanks to +relay and +key,+keyboard, I found that VkKeyScan(0xe7) returns -1 in wine, 0x39 in windows VkKeyScan(0xe8) returns -1 in wine, 0x37 in windows I have a french keyboard and as you may have guessed, the 7 key contains 'è' and '`' while the 9 key contains 'ç' and '^'. For the following, I only focus on the 7 key (keycode 16) as it's the same issue for the 9 key. I played with XkbKeycodeToKeysym(display, 16, 0, [0-4]) and it returns 0xe8 'è' / 0x37 '7' / 0x60 '`' / 0xac6 '⅞'. showing my keyboard is correctly mapped/configured so the issue is on the wine side. I looked at the source code and found the issue was in the loop at http://source.winehq.org/git/wine.git/blob/HEAD:/dlls/winex11.drv/keyboard.… More precisely, line 1728, keycode_to_keysym returns 0xe8 for i=0, XkbTranslateKeySym fails and as 0xe8 > 0x7F (the lastest ascii char), ckey[i] is 0. There is an explicit FIXME but as I don't fully understand it, I prefer filing a bug. If you need any info, testcase or log, just let me know. -- 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 3

[Bug 12443] New: Multi-monitor handling in ddraw/d3d
by wine-bugs＠winehq.org 10 Oct '20

10 Oct '20

http://bugs.winehq.org/show_bug.cgi?id=12443 Summary: Multi-monitor handling in ddraw/d3d Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: thestig(a)google.com In bug 1347, I write: I'm guessing slideshows in Picasa with multi-monitors is affected by this as well. When starting the slideshow, the entire screen gets blanked. After the slideshow ends, the screen that showed the slideshow gets restored, but the secondary screen remains blank until it gets drawn over. Stefan replied: This could as well be a bug with multi-monitor handling in ddraw, as ddraw is pretty ignorant to that. Yes, a bug on d3d multi-monitor handling is a good idea I think. Thus this bug serves as a reminder to look at multi-monitor handling issues in ddraw/d3d. -- 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 14

[Bug 14398] New: X3 Reunion crash on opening comm menu
by wine-bugs＠winehq.org 10 Oct '20

10 Oct '20

http://bugs.winehq.org/show_bug.cgi?id=14398 Summary: X3 Reunion crash on opening comm menu Product: Wine Version: 1.1.0 Platform: PC URL: http://www.egosoft.com/games/x3/info_en.php OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: pablo.bueti(a)gmail.com Created an attachment (id=14712) --> (http://bugs.winehq.org/attachment.cgi?id=14712) The console outuput when game hangs When selecting a ship and pressing C to open comms dialog the game hangs, there are several fixme:amstream lines in console that don't stop showing while games is hang. After pressing Ctrl-c in console I got the output to report the error here (attached). This was tested on openSuSe 10.3, kernel 2.6.22.18-0.2-default and Wine 1.1.0 without modifications. Also videos and sounds aparently in mp3 format don't play. I found that I'm not the only having this problem and seems to be related to amstream.dll. Also tried using native dll but don't help (game crashes and return to console). -- 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 14

[Bug 49790] New: wine (staging) from 5.13 to current 5.16 - qclauncher hangs (on access to a lock file?)
by WineHQ Bugzilla 09 Oct '20

09 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49790 Bug ID: 49790 Summary: wine (staging) from 5.13 to current 5.16 - qclauncher hangs (on access to a lock file?) Product: Wine-staging Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)lam.pl CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Because Bethesda.net Launcher doesn't work in WINE, qclauncher has been a great tool to start Quake Champions in WINE for pure BNL accounts (non-Steam). On Fedora (which uses wine-staging), I can't run qclauncher on any wine (staging) newer than 5.12. To reproduce qclauncher's problem, you don't need the game or Bethesda account. All you need is to: - grab the newest qclauncher.exe - https://github.com/syncore/qclauncher/releases/tag/v1.06 and extract that into a directory - cd <said directory> - touch data.qcl - ./qclauncher.exe Because the configuration file is 0 bytes, it should pop up an error saying "Your data.qcl is from an old version (...) You must restart (...)". That's the expected behavior for this test scenario. At least it was able to open the file, see that it's empty and display a dialog. It will remove the empty data.qcl file and you need to touch (re-create) it before test with a different WINE version. In current wine-staging, the pop-up never appears. Instead, wine apparently hangs completely, doesn't show any window, doesn't react to ^C/^\, but can be killed. My history with this problem: - 5.9 works - 5.10 had the same issue - not sure about 5.11 - 5.12 works - 5.13, 5.14, 5.15, 5.16 (newest at the time of writing) all have the bug Because I found a way to reproduce the hang without qclauncher ever trying to launch the game, I'm now suspecting (actually, pretty convinced) that the hang occurs during access to the data.qcl file. The program creates a file "qcl.lock" and perhaps this locking mechanisms got broken? This should be 100% reproducible without any requirements (other than grabbing qclauncher from github), but please let me know if it somehow isn't. Many thanks in advance! -- 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 9

[Bug 49823] New: Wine-staging 5.17 build fails on older Debian/Ubuntu versions
by WineHQ Bugzilla 09 Oct '20

09 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49823 Bug ID: 49823 Summary: Wine-staging 5.17 build fails on older Debian/Ubuntu versions Product: Wine-staging Version: 5.17 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dimesio(a)earthlink.net CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Building the wine-staging packages failed on Debian 9, Ubuntu 16.04, and Ubuntu 18.04. No problem on newer Debian/Ubuntu versions, Fedora, or the wine-devel packages. [ 846s] unix/file.c: In function 'FILE_CreateSymlink': [ 846s] unix/file.c:6093:48: error: 'RENAME_EXCHANGE' undeclared (first use in this function); did you mean 'SONAME_LIBSANE'? [ 846s] if (!renameat2( -1, tmplink, -1, unix_src, RENAME_EXCHANGE )) [ 846s] ^~~~~~~~~~~~~~~ [ 846s] SONAME_LIBSANE [ 846s] unix/file.c:6093:48: note: each undeclared identifier is reported only once for each function it appears in [ 846s] unix/file.c: In function 'FILE_RemoveSymlink': [ 846s] unix/file.c:6418:49: error: 'RENAME_EXCHANGE' undeclared (first use in this function); did you mean 'SONAME_LIBSANE'? [ 846s] if (!renameat2( -1, tmpfile, -1, unix_name, RENAME_EXCHANGE )) [ 846s] ^~~~~~~~~~~~~~~ [ 846s] SONAME_LIBSANE [ 846s] Makefile:945: recipe for target 'unix/file.o' failed [ 846s] make[2]: *** [unix/file.o] Error 1 [ 846s] make[2]: Leaving directory '/usr/src/packages/BUILD/dlls/ntdll' [ 846s] Makefile:9337: recipe for target 'dlls/ntdll' failed [ 846s] make[1]: *** [dlls/ntdll] Error 2 -- 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 4

[Bug 49645] New: Adobe Photoshop CC 2018 crashes at every "cancel" interaction
by WineHQ Bugzilla 09 Oct '20

09 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49645 Bug ID: 49645 Summary: Adobe Photoshop CC 2018 crashes at every "cancel" interaction Product: Wine-staging Version: 5.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: l4vebs1mx(a)relay.firefox.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 67846 --> https://bugs.winehq.org/attachment.cgi?id=67846 Backtrace Error Log I have been running Adobe Photoshop CC 2018 flawlessly from 5.10 onwards, but since staging 5.12 a usage breaking error appears: Whenever I cancel / close a dialogue by exiting it (via clicking cancel or esc), the bug occurs: Photoshop has presented an error dialogue "Could not complete your request" for every canceled interaction (example: using the crop tool and then using escape to not commiting the action). Since 5.12, this dialogue does not appear, instead the program crashes to Desktop. Any help would be much appreciated... Thank you all! -- 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 5