wine-bugs March 2022

wine-bugs@winehq.org

1 participants
3787 discussions

[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 52384] New: Wine is crashing when opened
by WineHQ Bugzilla 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=52384 Bug ID: 52384 Summary: Wine is crashing when opened Product: Wine Version: 7.0-rc5 Hardware: arm OS: Android Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: raphaelsebastiaovenegaribeiro(a)gmail.com The Android version of Wine is for an older version of Android, so it crashes on current versions of Android, can you fix this? -- 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 51168] New: Wine Android cannot run on Huawei EMUI11
by WineHQ Bugzilla 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=51168 Bug ID: 51168 Summary: Wine Android cannot run on Huawei EMUI11 Product: Wine Version: 6.9 Hardware: aarch64 OS: Android Status: UNCONFIRMED Severity: blocker Priority: P1 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fzh2003(a)yeah.net Created attachment 70036 --> https://bugs.winehq.org/attachment.cgi?id=70036 screenshot My device is Huawei nova 5 Pro (SEA-AL10),EMUI 11.0.0,Android 10,kernel 4.14.116. I installed the latest version of wine(6.9),but I failed to start it. When I opened the application,it showed "Setting up the Windows environment". Then I kept the screen open and waited for half an hour. However,it still showed this message.Clearing cache and reinstalling is of no use.Please solve it. Thanks. -- 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 51138] New: 6.8 ARM Samsung Exynos 9810 Galaxy Note 9 stuck on setting up windows environment dialog / grey screen at android 11.
by WineHQ Bugzilla 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=51138 Bug ID: 51138 Summary: 6.8 ARM Samsung Exynos 9810 Galaxy Note 9 stuck on setting up windows environment dialog / grey screen at android 11. Product: Wine Version: 6.8 Hardware: aarch64 OS: Android Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kcrans43(a)gmail.com I tested this on the Note 10 lite and Galaxy Tab Active 3, but the Note and S9 (Exynos) should behave the same. 6.3 and 6.4 got grey screen, 6.5 up to 6.8 went stuck on setting up windows environment. Sometimes when leaving it in the background and returning to the app, which after it crashes because memory, manually reopening the app; it also makes it to the grey screen, wow. -- 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 51125] New: Wine stuck on setting up on windows environment at startup. Kindle Fire 10 HD.
by WineHQ Bugzilla 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=51125 Bug ID: 51125 Summary: Wine stuck on setting up on windows environment at startup. Kindle Fire 10 HD. Product: Wine Version: 6.8 Hardware: arm OS: Android Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Mario.rossi.ch(a)protonmail.ch Wine stuck on setting up on windows environment at startup. Kindle Fire 10 HD. -- 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 50635] New: wine fails to startup
by WineHQ Bugzilla 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=50635 Bug ID: 50635 Summary: wine fails to startup Product: Wine Version: 6.0-rc3 Hardware: x86-64 OS: Android Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hejazi23(a)yahoo.com Wine screen goes blank and terminates after one or some seconds at first run, it happens after "extracting files" (android-x86 8.1 running on desktop PC) -- 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 50372] New: wine display is abnormal
by WineHQ Bugzilla 20 Oct '22

20 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=50372 Bug ID: 50372 Summary: wine display is abnormal Product: Wine Version: 6.0-rc3 Hardware: arm OS: Android Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 2775266219(a)qq.com Created attachment 68978 --> https://bugs.winehq.org/attachment.cgi?id=68978 screenshot When I run wine on a Huawei tablet equipped with Kirin 990, it does not display most of the screen normally (but it can display a simple message box), and the window can be moved -- 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 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs March 2022