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

[Bug 36094] New: advapi32/security test uses an unitialized variable in test_CreateDirectoryA
by wine-bugs＠winehq.org 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=36094 Bug ID: 36094 Summary: advapi32/security test uses an unitialized variable in test_CreateDirectoryA Product: Wine Version: 1.3.13 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: minor Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==7325== Syscall param writev(vector[...]) points to uninitialised byte(s) ==7325== at 0x4E9528CC: writev (in /usr/lib/libc-2.18.so) ==7325== by 0x7BC7FDBF: send_request (server.c:213) ==7325== by 0x7BC7FF51: wine_server_call (server.c:294) ==7325== by 0x7BC44D67: FILE_CreateFile (file.c:185) ==7325== by 0x7BC44FB8: NtCreateFile (file.c:279) ==7325== by 0x7B860841: CreateDirectoryW (path.c:1531) ==7325== by 0x7B8608F0: CreateDirectoryA (path.c:1555) ==7325== by 0x497D484: test_CreateDirectoryA (security.c:3085) ==7325== by 0x498A469: func_security (security.c:5423) ==7325== by 0x4999ED4: run_test (test.h:584) ==7325== by 0x499A2C3: main (test.h:654) ==7325== Address 0x472dcf8 is 88 bytes inside a block of size 120 alloc'd ==7325== at 0x7BC4C735: notify_alloc (heap.c:255) ==7325== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==7325== by 0x7BC884F6: NTDLL_create_struct_sd (sync.c:118) ==7325== by 0x7BC44C62: FILE_CreateFile (file.c:167) ==7325== by 0x7BC44FB8: NtCreateFile (file.c:279) ==7325== by 0x7B860841: CreateDirectoryW (path.c:1531) ==7325== by 0x7B8608F0: CreateDirectoryA (path.c:1555) ==7325== by 0x497D484: test_CreateDirectoryA (security.c:3085) ==7325== by 0x498A469: func_security (security.c:5423) ==7325== by 0x4999ED4: run_test (test.h:584) ==7325== by 0x499A2C3: main (test.h:654) ==7325== Uninitialised value was created by a client request ==7325== at 0x7BC4C52C: mark_block_uninitialized (heap.c:209) ==7325== by 0x7BC4C697: initialize_block (heap.c:240) ==7325== by 0x7BC50FA3: RtlAllocateHeap (heap.c:1717) ==7325== by 0x497D2A5: test_CreateDirectoryA (security.c:3067) ==7325== by 0x498A469: func_security (security.c:5423) ==7325== by 0x4999ED4: run_test (test.h:584) ==7325== by 0x499A2C3: main (test.h:654) ==7325== -- 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 42462] New: Severe hang in several places in FFXIV
by wine-bugs＠winehq.org 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=42462 Bug ID: 42462 Summary: Severe hang in several places in FFXIV Product: Wine-staging Version: 2.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: spryor(a)redhat.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- After playing FFXIV for a certain amount of time, or in certain locations (I haven't noticed a common shader that seems to trigger this) the game will experience a severe hang. When running perf top to examine what's going on, this line stands out: Overhead Shared Object Symbol 9.22% wined3d-csmt.dll.so [.] 0x0000000000048362 It seems to vary from around 7-15% when not experiencing the issue, to around 50%. The jump in overhead accompanies an almost total lockup of the desktop, if the game manages to recover, it usually accompanies graphical glitches not present before the lockup, and will usually crash not too long after recovery if gameplay proceeds (which I would hazard a guess is due to framebuffer corruption) Variant: Fedora 25, fully updated as of 2/16/2017 Desktop: KDE Processor: i7-7700k GPU: Nvidia GTX 1080 (with proprietary driver 378.13) WINE: wine-2.1-1.fc25.x86_64 (current from the fedora repos as of 2/16/2017) -- 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 30

[Bug 47394] New: Valgrind reports Invalid read of size 4 one frame below call_dll_entry_point
by wine-bugs＠winehq.org 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=47394 Bug ID: 47394 Summary: Valgrind reports Invalid read of size 4 one frame below call_dll_entry_point Product: Wine Version: 4.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: jeffersoncarpenter2(a)gmail.com Distribution: --- Created attachment 64741 --> https://bugs.winehq.org/attachment.cgi?id=64741 Output of valgrind --trace-children=yes wine main.exe Steps to reproduce: * Build wine-4.10 for 32 bits. * Using i686-w64-mingw32-gcc, compile 'int main() { return 0; }' * Disable the wine preloader (chmod -x wine-preloader) * Run with valgrind Valgrind reports an invalid read of size 4 one frame below call_dll_entry_point while loading rpcrt4.dll. Prior to this it (at least, a wine process with the same process id) successfully loads ntdll.dll, KERNEL32.dll, advapi32.dll, msvcrt.dll calling call_dll_entry_point without any issues, as confirmed by inserting the line FIXME("Loading %s %i %p\n", debugstr_w(wm->ldr.BaseDllName.Buffer), getpid(), (void*)entry); above retv = call_dll_entry_point( entry, module, reason, lpReserved ); inside of MODULE_InitDLL. -- 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 1

[Bug 46188] New: Black screen on Android 8
by wine-bugs＠winehq.org 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=46188 Bug ID: 46188 Summary: Black screen on Android 8 Product: Wine Version: 3.21 Hardware: arm OS: Android Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: janisozaur+wine(a)gmail.com Created attachment 62850 --> https://bugs.winehq.org/attachment.cgi?id=62850 wine_3.21_on_android8.1.log Issue similar to bug #44245, when trying out Wine 3.21 on Android 8.1, all I get is a brief flicker of cmd, then the screen turns black. The aforementioned bug seems to have resolved issues for Android 9, but running on Android 8.1 is not really possible due to this. Here's remainder of my previous comment in the other bug: The behaviour has improved a bit, I can now see a brief flicker of cmd, but it's covered with a black screen in just a few frames. Android 8.1.0 OnePlus 5, SnapDragon 835 Wine 3.21 See the recording of the issue: https://gfycat.com/EvergreenInnocentGreatdane (or original recording: https://www.dropbox.com/s/yuaz398nz2wxeq0/wine.mp4?dl=0) I have also added an attachment with the logs collected from logcat from a later start 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 41

[Bug 46041] New: Wine 3.18 shows blank screen on android
by wine-bugs＠winehq.org 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=46041 Bug ID: 46041 Summary: Wine 3.18 shows blank screen on android Product: Wine Version: 3.18 Hardware: arm OS: Android Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexterranova81(a)gmail.com I installed wine 3.17 without issues. After installing 3.18 neither version works. Both versions show a blank screen after unpacking files. I think it's residual files but I dont know their location. -- 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 45342] New: Android: partial english keymap layout is used on a german keyboard
by wine-bugs＠winehq.org 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=45342 Bug ID: 45342 Summary: Android: partial english keymap layout is used on a german keyboard Product: Wine Version: 3.10 Hardware: aarch64 OS: Android Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wine.dev(a)web.de LANG and LC_ALL are set to "de_DE.UTF-8" "z" and "y" on the keyboard give the correct chars in wine, but many other keys on my german keyboard produce in wine the chars from an english keyboard: right of "m": ,.- right of "l": öä right of "p": ü+# right of "0": ß´ (the last char in combination with space) shifted values starting from "1" to the right The keyboard works in all android apps, including termux -- Regards ... ... Detlef -- 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 46752] New: error message
by wine-bugs＠winehq.org 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=46752 Bug ID: 46752 Summary: error message Product: Wine Version: 3.15 Hardware: arm OS: Android Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: drakemcmannis9876(a)gmail.com Created attachment 63754 --> https://bugs.winehq.org/attachment.cgi?id=63754 screenshot of the error my wine app is displaying an error message when running a setup file PLZ FIX THIS ERROR -- 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 46926] New: wine don't start after installation
by wine-bugs＠winehq.org 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=46926 Bug ID: 46926 Summary: wine don't start after installation Product: Wine Version: 4.4 Hardware: arm OS: Android Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: unthend(a)aol.com hello, i installed wine-4.4-arm.apk on my huawei mediapad m3, the installation apparently went well but when i try to launch wine it doesn't start, i also tried previous versions like 4.0 etc but i get the same problem, i may be doing something wrong, can you help me, greetings lino -- 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 47470] New: UI too big
by wine-bugs＠winehq.org 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=47470 Bug ID: 47470 Summary: UI too big Product: Wine Version: 4.12 Hardware: arm OS: Android Status: UNCONFIRMED Severity: normal Priority: P2 Component: browseui Assignee: wine-bugs(a)winehq.org Reporter: christianlawton527(a)gmail.com Created attachment 64844 --> https://bugs.winehq.org/attachment.cgi?id=64844 No "OK" button When I restarted "Wine" on my android phone the ui was too big,and I couldn't launch anything using "run" or "explorer" -- 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 29094] New: d3dx8/device.c, d3dx9/device.c: sometimes fails with "Test failed: Didn't receive MOUSEMOVE"
by wine-bugs＠winehq.org 20 Oct '22

20 Oct '22

http://bugs.winehq.org/show_bug.cgi?id=29094 Bug #: 29094 Summary: d3dx8/device.c, d3dx9/device.c: sometimes fails with "Test failed: Didn't receive MOUSEMOVE" Product: Wine Version: 1.3.31 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified I've seen runs of errors like this on my i7 / ubuntu 11.10 system (nvidia geforce 8500 gt, 270.41.06) device.c:895: Test failed: Didn't receive MOUSEMOVE 2 (100, 100). alarum: fail: exit status 1, command '../../../wine d3d8_test.exe.so device.c ' device.c:3239: Test failed: Didn't receive MOUSEMOVE 5 (125, 125). alarum: fail: exit status 1, command '../../../wine d3d9_test.exe.so device.c ' Examples: http://www.winehq.org/pipermail/wine-tests-results/2011-October/005109.html http://www.winehq.org/pipermail/wine-tests-results/2011-October/005110.html http://www.winehq.org/pipermail/wine-tests-results/2011-October/005111.html http://www.winehq.org/pipermail/wine-tests-results/2011-October/005112.html http://www.winehq.org/pipermail/wine-tests-results/2011-November/005187.html Since the failure seems to happen both in d3d8 and d3d9, it doesn't seem flaky in the usual way. (I should probably start reporting system uptime in the test failure logs.) The uptime at the most recent error was 6 days. FWIW, the first revision this was seen with was 7df024529541128719ed09a7ed69bda0b11beadb but I have no idea if it's a regression. -- 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 12