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

[Bug 41000] New: wineconsole curses backend 64bit: Some uppercase chars broken on Crysis Wars Dedicated Server
by wine-bugs＠winehq.org 19 Aug '20

19 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=41000 Bug ID: 41000 Summary: wineconsole curses backend 64bit: Some uppercase chars broken on Crysis Wars Dedicated Server Product: Wine Version: 1.9.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: main.haarp(a)gmail.com Distribution: --- I am running the Crysis Wars Dedicated Server in wineconsole. The server offers both 32bit and 64bit binaries. Using wineconsole's user backend, both 32 and 64bit work fine. Using the curses backend, 32bit works fine. 64bit however experiences a bug. Some uppercase characters cannot be typed or pasted at all. There is no reaction. wineconsole will display them just fine, but simply will not let them be typed. The affected chars are uppercase versions of these: 2 4 6 0 - f h j k ; [] q r t y o p x c v m , . / (assuming US keyboard layout) -- 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 30193] New: Crysis Wars ded server doesn't resize with wineconsole (curses backend)
by wine-bugs＠winehq.org 19 Aug '20

19 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=30193 Bug #: 30193 Summary: Crysis Wars ded server doesn't resize with wineconsole (curses backend) Product: Wine Version: 1.4-rc6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: liquitsnake(a)gmx.net Classification: Unclassified Created attachment 39410 --> http://bugs.winehq.org/attachment.cgi?id=39410 screen The Crysis Wars dedicated server, when running under wineconsole with the curses backend, does not resize its viewport. It is stuck at the default 80x25, even if the terminal is considerably larger (see attachment). This produces some unexpected output, as some commands expect a larger size but have to be split over 2 lines via \ My terminal and wineconsole interact just fine, as I have verified with cmd. It's just this app that sticks to 80x25 no matter what. On Windows, it would normally spawn a console window with a size of 132x60 (or less if the desktop resolution can't fit that) Could it be that wineconsole first starts at 80x25 and only later resizes to terminal size? In that case, I can imagine that the app polls the size once during startup and sticks to that, thus limiting itself to 80x25. -- 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 11

[Bug 37928] New: Photoshop CS6: Mini-bridge panel does not show directory entries in alphabetical order
by wine-bugs＠winehq.org 19 Aug '20

19 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=37928 Bug ID: 37928 Summary: Photoshop CS6: Mini-bridge panel does not show directory entries in alphabetical order Product: Wine Version: 1.7.34 Hardware: arm OS: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: robert.munteanu(a)gmail.com Distribution: --- Steps to reproduce: 1. Launch Photoshop 2. Click File -> Open in mini bridge 3. Navigate to a folder with multiple subfolders The subfolders are not ordered alphabetically, but in an apparently random manner. They are definitely not ordered by creation date ( I created the situation in my screenshot using a simple "mkdir a b c d e f g h i j k l" . -- 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 43924] New: Alice: Madness Returns cannot sign in to EA
by wine-bugs＠winehq.org 18 Aug '20

18 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=43924 Bug ID: 43924 Summary: Alice: Madness Returns cannot sign in to EA Product: Wine Version: 2.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexchandel(a)gmail.com Distribution: --- Created attachment 59552 --> https://bugs.winehq.org/attachment.cgi?id=59552 wine-2.19 output Before startup, Alice: Madness Returns requires you to sign into an EA account. However, the EA sign-in never succeeds, always returning a sign-in failure. Wine output 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 5

[Bug 43923] New: Alice: Madness Returns immediately crashes with Page Fault
by wine-bugs＠winehq.org 18 Aug '20

18 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=43923 Bug ID: 43923 Summary: Alice: Madness Returns immediately crashes with Page Fault Product: Wine Version: 2.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexchandel(a)gmail.com Distribution: --- Created attachment 59551 --> https://bugs.winehq.org/attachment.cgi?id=59551 backtrace Alice: Madness Returns doesn't run. Installed with Steam, using a serial purchased through Steam. I've played with it a bit trying to get it working, and at best it crashes with a page fault immediately. -- 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 13624] New: Lineage 2 - The Chaotic Throne - Hellbound
by wine-bugs＠winehq.org 16 Aug '20

16 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=13624 Summary: Lineage 2 - The Chaotic Throne - Hellbound Product: Wine Version: 1.0-rc3 Platform: All OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: eryk-rutkowski(a)o2.pl Created an attachment (id=13604) --> (http://bugs.winehq.org/attachment.cgi?id=13604) Log from Terminal Problem is in Lineage 2 Hellbound and regarding npkycrypt - dll file. This dll is not work fine and don't recognize keyboard and i can't log in. There is communicate: "The keyboard security module has failed to load. please exit the game and try again" Sorry for my bad english but i'm from other country ;p -- 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 47106] New: Fallout 4 FAudio [wmav2 @ 0x7f9ad0135d80] prev_block_len_bits 4 out of range
by wine-bugs＠winehq.org 16 Aug '20

16 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=47106 Bug ID: 47106 Summary: Fallout 4 FAudio [wmav2 @ 0x7f9ad0135d80] prev_block_len_bits 4 out of range Product: Wine Version: 4.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: timofeevsv1989(a)gmail.com Distribution: --- Fallout 4 freezing (or sound disappearing) with spam of tons console messages: [wmav2 @ 0x7f9ad0135d80] prev_block_len_bits 4 out of range INFO System-wide FAudio, not winetricks one Something wrong in connection XAudio2->FAudio -- 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 46670] New: Unhandled exception on Blizzard Battle.net
by wine-bugs＠winehq.org 16 Aug '20

16 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=46670 Bug ID: 46670 Summary: Unhandled exception on Blizzard Battle.net Product: Wine-staging Version: 4.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: b1779506(a)trbvn.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- See attachments. -- 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 7

[Bug 44571] New: Unable to build cue sheets with IMGBurn
by wine-bugs＠winehq.org 16 Aug '20

16 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=44571 Bug ID: 44571 Summary: Unable to build cue sheets with IMGBurn Product: Wine-staging Version: 3.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: halo117nachos(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 60538 --> https://bugs.winehq.org/attachment.cgi?id=60538 stderr and stdout Everytime I try to build a cue sheet out of MP3 files with IMGBurn, the program crashes. Building a cue sheet is the first step in burning MP3 (and other audio files) to standard red book audio discs, so if one can't build a cue sheet, one can't burn music. Of course, I made a new wine prefix to test this, and found that it didn't solve the problem at all. :( Here's what happens: If I click the tools menu, and select "Create Cue File... ", and I start manually adding MP3s, first the program hangs, and then it says the following: "Potential Direct Show Error! - No data has been received for 10 seconds file name: C:\blablabla\file.mp3 Decoding Progress: 9,999,999 bytes" It then gives me three options: "Cancel", "Try Again", and "Continue". BTW, that number (9,999,999) seems to very with each MP3 file. It's possible that whatever number it lands on is the end of the file. I also tend to get a more generic error, although this one is harder to reproduce. IDK if this is the same bug or not. The error is: "An error occured in the application There might be an updated version available that fixes the pr [the rest of this line seems to be cut off by some buttons on the right] Please check the website for updates - http://www.imgburn.co [once again, the message is cut off]" There are three buttons on the bottom, and three on the right (the ones on the right are the ones that cut off the text). The ones on the bottom are "send bug report", "save bug report", and "show bug report". The buttons on the right are "Continue application", "Restart application", and "Close application". If I click "Continue application", the program seems to continue working. PS: I've just run IMGBurn from the terminal, and redirected both stdout and stderr to a file, which I've attached to this report. When the aformentioned "generic" error message appeared. I tried to click "Close application", but the program froze, forcing me to kill it. That error happened on the second file. BTW, I'm running Ubuntu 16.04, and I've installed winehq-devel 3.2 from the official repositories. Also, I didn't modify the prefix at all, except to install IMGBurn, and to change the default version of Windows to XP (otherwise IMGBurn doesn't 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.

2 9

[Bug 48410] New: The "Add syscall thunks for 64 bit" patch partly breaks USVFS
by WineHQ Bugzilla 16 Aug '20

16 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=48410 Bug ID: 48410 Summary: The "Add syscall thunks for 64 bit" patch partly breaks USVFS Product: Wine-staging Version: 5.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: qsniyg(a)mail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- This is the patch that breaks USVFS: https://github.com/wine-staging/wine-staging/blob/d36d63ac848dadbc2c8ffc933… (discussion: https://github.com/ModOrganizer2/modorganizer/issues/372) I've only tested 64-bit, so it's possible https://github.com/wine-staging/wine-staging/blob/master/patches/winebuild-… also affects it. Although USVFS works for the most part, loading DLLs fails, because LdrLoadDll (within ntdll) calls NtOpenFile (through open_dll_file), but for some reason, USVFS doesn't recognize that specific NtOpenFile call (even though it hooks other NtOpenFile calls that aren't called from ntdll without issue). I haven't looked through the patch in much detail, but from what I can tell I believe the reason why this patch breaks USVFS is because the calls to NtOpenFile from within ntdll use the direct function address, whereas with the patch, USVFS now hooks a new "wrapper" around the function, instead of the same address that ntdll calls internally. -- 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