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

[Bug 44784] New: Lingvo x6 portable does not start
by wine-bugs＠winehq.org April 29, 2020

April 29, 2020

https://bugs.winehq.org/show_bug.cgi?id=44784 Bug ID: 44784 Summary: Lingvo x6 portable does not start Product: Wine Version: 3.4 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maksim.andronenkov(a)rovaniemi.uz Created attachment 60812 --> https://bugs.winehq.org/attachment.cgi?id=60812 logs Recently installed wine 3.4 on MacOS High Sierra and tried to run Lingvo X6 portable www.lingvo.ru but did not happen. Logs are attached. -- 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 41564] New: Google Nik Collection: Top menu bar gone and cursor gone
by wine-bugs＠winehq.org April 29, 2020

April 29, 2020

https://bugs.winehq.org/show_bug.cgi?id=41564 Bug ID: 41564 Summary: Google Nik Collection: Top menu bar gone and cursor gone Product: Wine-staging Version: 1.9.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dan.Tableau(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Hello, I just want to report that using wine 1.9.21 (staging) with the Google Nik Collection creates the following issues: Top menu bar gone, cursor gone (while inside the window). After switching to winehq-devel, as suggest in the IRC (Thanks, slackner), the problem was gone. Both times the version used was: 1.9.21 Let me know if more info is needed. Thank for doing all this and keeping it up and 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.

2 5

[Bug 48462] New: "Listen to RawKey* events in the desktop thread" patch makes keyboard unreliable in EverQuest
by WineHQ Bugzilla April 29, 2020

April 29, 2020

https://bugs.winehq.org/show_bug.cgi?id=48462 Bug ID: 48462 Summary: "Listen to RawKey* events in the desktop thread" patch makes keyboard unreliable in EverQuest Product: Wine-staging Version: 5.0-rc5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dvufhr.nznqarjf(a)noclue.notk.org CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Regression SHA1: 8218a789558bf074bd26a9adf3bbf05bdb9cb88e Distribution: Fedora Upgrading from 4.21 to 5.0-rc3 on fedora caused unreliability issues for keyboard in EverQuest (EQ below): - windowed EQ window sometimes (!) taking input when not focused, even when hidden in another workspace - modifier keys (shift, alt, ctrl) sometimes working, sometimes not.. For example right shift seemed to work well exactly once immediately after defocusing/refocusing the window, but not after that, while the left shift key worked a bit better for some reason. I couldn't figure out why or what he hell is happening. Well, anyway, game input goes pretty bonkers and the game is much more difficult to play. I know EQ makes heavy use of raw inputs itself, it reprocesses all keys not as input letters but as key presses and this leads to some weird input sometimes (e.g. typing fast enough with a bit of graphical lag will queue input letters, but pressing shift then will affect letters currently being processed in the backlog, this is pretty interesting and probably not wine's fault); but this patch takes it to a whole new level. I bisected the staging tree down to this patch: patches/user32-rawinput-keyboard/0004-winex11.drv-Listen-to-RawKey-events-in-the-desktop-t.patch introduced in staging commit 8218a789 ("Updated rawinput patchsets") Happy to test things if required, or report somewhere else if that helps. Thanks! -- Dominique Martinet | Asmadeus -- 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 25

[Bug 47408] New: Katamari Damacy: AppData\Local mismatch causes Steam Cloud to be ignored
by wine-bugs＠winehq.org April 29, 2020

April 29, 2020

https://bugs.winehq.org/show_bug.cgi?id=47408 Bug ID: 47408 Summary: Katamari Damacy: AppData\Local mismatch causes Steam Cloud to be ignored Product: Wine Version: 4.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: devilj(a)outlook.pt Distribution: --- Hi, This game seems to have hardcoded the directories for the AppData\Local and AppData\LocalLow folders, and that means the game isn't syncing with Steam Cloud, because Steam is a good program and knows where to store the files correctly and this game doesn't. Specifically, Steam saves in the right directory ("%LocalAppData%" -> "%USERPROFILE%\Local Settings\Application Data\"), and the game is looking for "%USERPROFILE%\AppData\Local\"; thus, Steam can't see the files that the game writes and vice-versa. Note that the game loads and saves correctly; it just does it in the wrong directory. There is also the issue of LocalLow being missing entirely. Now, obviously, this bug sits entirely with the game; but there seems to be more reports about games missing these specific folders (see bug #45713). And this bug is very easily fixable, too, by creating symlinks. That said, the AppData directories are standard since Windows Vista, and Wine is using the very old, XP-style Application Data structure. I propose that we create symlinks from AppData\Local and AppData\Romaing pointing to the correct directories, and create AppData\LocalLow on prefix creation. Hopefully that would be simple to do, and it'd fix every bug of this kind. -- 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 40403] New: WARCRAFT III NO VIDEO
by wine-bugs＠winehq.org April 29, 2020

April 29, 2020

https://bugs.winehq.org/show_bug.cgi?id=40403 Bug ID: 40403 Summary: WARCRAFT III NO VIDEO Product: Wine Version: 1.9.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: legluondunet(a)free.fr Distribution: --- Hello, I just installed Warcraft III and tested it with wine 1.9.7, the videos are not played, just skipped. I joined you the wine log. The videos played well with Wine 1.7.12, is it a regression? -- 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 27325] New: after install wine delete program files...
by wine-bugs＠winehq.org April 29, 2020

April 29, 2020

http://bugs.winehq.org/show_bug.cgi?id=27325 Summary: after install wine delete program files... Product: Wine Version: 1.3.21 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gymka(a)mail.ru Application finereader 10 professional, http://finereader.abbyy.com/ OS: archlinux i install finereader 10 professional, not everything works ok, but for that there is workaround; after install i start application and all program files dissapears... with wine 1.3.19 everything worked ok, problems only with 1.3.20 and 1.3.21 -- 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 25

[Bug 48602] New: Kindle for PC installer 1.26.55076 crashes on execution
by WineHQ Bugzilla April 29, 2020

April 29, 2020

https://bugs.winehq.org/show_bug.cgi?id=48602 Bug ID: 48602 Summary: Kindle for PC installer 1.26.55076 crashes on execution Product: Wine Version: 5.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bug.reporter(a)mail.sheugh.com Distribution: --- Created attachment 66439 --> https://bugs.winehq.org/attachment.cgi?id=66439 Text output from ./KindleForPC-installer-1.26.55076.exe This is a new Wine installation, and this is the first application I tried to run. I am going to add some things just in case it is relevant. It is desired to install the latest Kindle for Windows version following generally the advice set out here: https://ajreissig.com/kindle-linux-read-kindle-books-linux-system/ Option 3 of the guidance "Conversion" was followed. An additional complication is that Kindle offers books sourced from both www.amazon.com and from www.amazon.co.uk, hence for at least the initial installation, www.amazon.com will be used. The first attempt, with the most recent download from Amazon, failed. The version before build 38420 from filehippo appeared to function correctly, but timed out when I attempted to register the application. I later found that Amazon had emailed a one-time code to me to allow completion of the registration. Although Q4Wine is installed, for test purposes, the commandline will be used to execute the attempted re-installation of the latest Kindle Application. cd ~/.wine/drive_c/Program\ Files/ ./KindleForPC-installer-1.26.55076.exe chmod to make the file executable The execution fails after opening a window offering the choice of a cancel or opening the wine debug. There are some warning messages. Wine offered to install wine mono and that seemed to complete ok. Wine then offered to install gecko Clicking Ok produced a bunch of fixme messages. The execution appears to have hung. I will have a look at the things Wine complained about and attempt a reinstall. sha1sum ./KindleForPC-installer-1.26.55076.exe d3407d11d8fcd2f146516b5fd96fa2fcaf73ffcb ./KindleForPC-installer-1.26.55076.exe -- 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 44076] New: LA NOIRESteam Version crash at startup
by wine-bugs＠winehq.org April 29, 2020

April 29, 2020

https://bugs.winehq.org/show_bug.cgi?id=44076 Bug ID: 44076 Summary: LA NOIRESteam Version crash at startup Product: Wine Version: 2.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: legluondunet(a)free.fr Distribution: --- Created attachment 59792 --> https://bugs.winehq.org/attachment.cgi?id=59792 LA NOIRE Wine 2.21-staging terminal log Hello, I installed LA NOIRE Steam version, it crashed at start. I joined you terminal log and backtrace. nota: I installed Dotnet 3.5, directx9 and vcredist. -- 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 12

[Bug 32336] New: finereader 11 trial version install fails and rollbacks
by wine-bugs＠winehq.org April 29, 2020

April 29, 2020

http://bugs.winehq.org/show_bug.cgi?id=32336 Bug #: 32336 Summary: finereader 11 trial version install fails and rollbacks Product: Wine Version: 1.5.18 Platform: x86 OS/Version: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com Classification: Unclassified Created attachment 42679 --> http://bugs.winehq.org/attachment.cgi?id=42679 Log: install ABBYY FineReader 11 We have a similar bug for ABBYY finereader 10: Bug 27325 However, +msi console log is different between ABBYY finereader 10 and ABBYY finereader 11, I'm not sure if this bug is a duplication. 1. Download trial version from http://download.abbyy.cn/dist/fr11/ABBYY_FineReader_11_Chinese.exe 2. run the outer installer, it will extract and run the inner installer $ wine ABBYY_FineReader_11_Chinese.exe 3. click "安装 ABBYY FineReader 11" of the inner installer 4. the install wizard will ask you to install MSXML6, either install it or skip it. 5. run the real ABBYY FineReader installer There is something wrong and the installation will be rollback. Here is a workaround: 1. run the outer installer and extract the inner installer 2. run the inner installer with DISABLEROLLBACK=1 $ msiexec /I ABBYY\ FineReader\ 11.msi TRANSFORMS="C:\Temp\ABBYY FineReader 11\2052.mst" /Liwrmo\!vepacu "C:\users\fracting\Temp\ABBYY FineReader 11.log" LAUNCH_FROM_SETUP=1 DISABLEROLLBACK=1 -- 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 46545] New: WINEPREFIX doesn't work when ends with "windows"
by wine-bugs＠winehq.org April 29, 2020

April 29, 2020

https://bugs.winehq.org/show_bug.cgi?id=46545 Bug ID: 46545 Summary: WINEPREFIX doesn't work when ends with "windows" Product: Wine Version: 4.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: paleozogt(a)gmail.com Distribution: --- Created attachment 63407 --> https://bugs.winehq.org/attachment.cgi?id=63407 wine default prefix Setting WINEPREFIX to something that ends with "windows" (e.g., $HOME/windows) causes wineboot to create a broken wine instance. In particular, C:\ won't exist, for example: > ~ wine cmd /C dir 'C:\' > Volume in drive C has no label. > Volume Serial Number is 0000-0000 > > Directory of C: > > File not found. whereas with the default prefix C:\ is fine: > ~ wine cmd /C dir 'C:\' > Volume in drive C has no label. > Volume Serial Number is 0000-0000 > > Directory of C: > > 1/28/2019 11:31 AM <DIR> Program Files > 1/28/2019 11:31 AM <DIR> Program Files (x86) > 1/28/2019 11:31 AM <DIR> ProgramData > 1/28/2019 11:31 AM <DIR> users > 1/28/2019 11:31 AM <DIR> windows > 0 files 0 bytes > 5 directories 90,299,498,496 bytes free Setting WINEPREFIX to other values seems to work fine (e.g., $HOME/win). Why is "windows" special? Are there any other special values that WINEPREFIX shouldn't use? See the attached console log for more details. -- 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