wine-bugs September 2021

wine-bugs@winehq.org

1 participants
4671 discussions

[Bug 48760] New: ConEmu shows 'GetConsoleProcessList failed' at startup
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=48760 Bug ID: 48760 Summary: ConEmu shows 'GetConsoleProcessList failed' at startup Product: Wine Version: 5.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rpisl(a)seznam.cz Distribution: --- ConEmu shows "ConEmuC64.exe: PID=132: GetConsoleProcessList failed, code=0" at startup due to GetConsoleProcessList being just a stub. Returning zero is an error according to documentation, "because every console has at least one process associated with it". Then ConEmu starts successfully, so this is a minor issue. -- 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 48201] New: unimplemented function KERNEL32.dll.SetCurrentConsoleFontEx
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=48201 Bug ID: 48201 Summary: unimplemented function KERNEL32.dll.SetCurrentConsoleFontEx Product: Wine Version: 4.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: davidmanuel1993(a)hotmail.com Distribution: --- When running a console program, wine crashes with: unimplemented function KERNEL32.dll.SetCurrentConsoleFontEx To reproduce you can compile the following program and try to run it with Wine. I compiled it with MinGW. https://pastebin.com/k5SfvEtp PS: This is a follow up of https://bugs.winehq.org/show_bug.cgi?id=47620 -- 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 51591] New: AFxW: file list panes aren't updated at start-up
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=51591 Bug ID: 51591 Summary: AFxW: file list panes aren't updated at start-up Product: Wine Version: 6.14 Hardware: x86-64 URL: https://web.archive.org/web/20210811070411/http://akt. d.dooo.jp/lzh/afxw32_165.zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: sagawa.aki+winebugs(a)gmail.com Distribution: Ubuntu Created attachment 70441 --> https://bugs.winehq.org/attachment.cgi?id=70441 AFxW window after launching AFxW[1], aka あふｗ in Japanese, is an ultra-low functionality two-pane file manager. After launching AFXW.EXE, it should show file lists in panes as seen in [2]. But, it doesn't on Wine. @momota1999, a reporter on Twitter, tweeted list items would be shown by moving the cursor (with up/down arrow keys) and the issue didn't occur on Wine 4.0 (Debian 4.0-2). I can confirm both of them with AFxW v1.65. Steps to reproduce: 1. unzip afxw32_165.zip 2. LANG=ja_JP.UTF-8 wine AFXW.EXE Expected result: File list panes are updated on start-up without any key inputs. You can see file names, their size and time stamps in the panes. Actual result: File list panes aren't updated on start-up. You can't see anything in the panes. Please refer to the attachment about this situation. [1] http://akt.d.dooo.jp/akt_afxw.html [2] http://akt.d.dooo.jp/afxwss/afxwss_b0.png -- 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

[Bug 51574] New: swscanf_s with %zu fails for valid value
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=51574 Bug ID: 51574 Summary: swscanf_s with %zu fails for valid value Product: Wine Version: 6.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: winebugs(a)63bit.net Distribution: --- Running Microsoft Texconv.exe with parameters specifying height or width returns "Invalid value specified for h (512)". Link to source is here: https://github.com/microsoft/DirectXTex/blob/54ce2c8da97c3508899c31f80bfb1e… Link to binary is here: https://github.com/microsoft/DirectXTex/releases/download/aug2021/texconv.e… Example failing arguments are '-nowic -nologo -y -sepalpha -h 512 -w 512 -aw 256 -keepcoverage 0 -f BC7_UNORM -bc q -o "C:\dyndolod\TexGen_Output\Textures\lod" "C:\dyndolod\TexGen_Output\Textures\lod\bridge01lod.dds"' -- 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 51465] New: EVE Online Launcher Crashes Due to Missing syscalls in Windows Credential Manager
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=51465 Bug ID: 51465 Summary: EVE Online Launcher Crashes Due to Missing syscalls in Windows Credential Manager Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: algebro(a)tuta.io Distribution: --- Created attachment 70306 --> https://bugs.winehq.org/attachment.cgi?id=70306 Crash on authentication As of version 1917874 of the EVE Online launcher, the application crashes when trying to log in. According to the developers, they moved to a new credential management solution (involving https://github.com/frankosterfeld/qtkeychain and the Windows Credential Store), and they said that Wine currently doesn't implement the needed syscalls for this to function. I've attached a stacktrace which looks like it crashes somewhere in cryptopp, but I haven't been able to figure out much by debugging (winedbg doesn't see any of those function addresses as valid, and I haven't been able to map them to functions in a disassembler). Let me know if I can provide any more information that would be helpful. -- 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 56

[Bug 51348] New: uxtheme.SetWindowTheme should use SendMessage to send WM_THEMECHANGED
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=51348 Bug ID: 51348 Summary: uxtheme.SetWindowTheme should use SendMessage to send WM_THEMECHANGED Product: Wine Version: 6.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: uxtheme Assignee: wine-bugs(a)winehq.org Reporter: x1917x(a)gmail.com Distribution: --- Created attachment 70205 --> https://bugs.winehq.org/attachment.cgi?id=70205 Bad behavior The issue affects SourceInsight 4 in particular. SourceInsight has its own built-in theme functionality which doesn't get along well with any non-standard Wine theme. When a non-standard Wine theme is selected, then the main toolbar in SI4 ignores its app theme and always gets drawn with the selected Wine theme. Selecting the default Wine theme fixes the issue - the toolbar is drawn according to the app theme. On Windows it's ok no matter which UI theme is set. Screenshot of the issue is attached. The root cause of the issue is that UXTHEME_broadcast_msg/UXTHEME_broadcast_msg_enumchild in dlls/uxtheme/system.c both use a PostMessage() call to send WM_THEMECHANGED to affected window(s). In SI4 the main toolbar is implemented as a combination of a custom container window (si_Rebar class) and a standard win32 Rebar control (RebarWindow32 class). Immediately after creating the RebarWindow32 window, SI4 does SetWindowTheme(hwndRebar, L" ", L" ") for it. According to MSDN (https://docs.microsoft.com/en-us/windows/win32/api/uxtheme/nf-uxtheme-setwi…) > The theme manager retains the pszSubAppName and the pszSubIdList associations through the lifetime of the window, even if visual styles subsequently change. The window is sent a WM_THEMECHANGED message at the end of a SetWindowTheme call, so that the new visual style can be found and applied. > > When pszSubAppName and pszSubIdList are NULL, the theme manager removes the previously applied associations. You can prevent visual styles from being applied to a specified window by specifying an empty string, (L" "), which does not match any section entries. - this L" ", L" " stuff means that SI4 DOES NOT want for system visual styles being applied to its RebarWindow32 control. However, according to WINEDEBUG logs they were applied to all bg erase, painting etc operations no matter the SetWindowTheme(, L" ", L" ") call. Turns out that RebarWindow32' WndProc receives WM_THEMECHANGED too late, after all stuff including drawing already happened with the system-wide theme being applied. The reason why it was received so late is simple - SetWindowTheme implementation in wine uses PostMessage() instead of SendMessage(). Replacing it with a SendMessage() call allows to fix the bug. I've checked what Windows actually does in SetWindowTheme and found out that it always uses SendMessage to send WM_THEMECHANGED (for any HWND). So. suggested fix: diff --git a/dlls/uxtheme/system.c b/dlls/uxtheme/system.c index a37e532500a..3b6e6d2b6b6 100644 --- a/dlls/uxtheme/system.c +++ b/dlls/uxtheme/system.c @@ -59,7 +59,7 @@ static WCHAR szCurrentSize[64]; static BOOL CALLBACK UXTHEME_broadcast_msg_enumchild (HWND hWnd, LPARAM msg) { - PostMessageW(hWnd, msg, 0, 0); + SendMessageW(hWnd, msg, 0, 0); return TRUE; } @@ -72,7 +72,7 @@ static BOOL CALLBACK UXTHEME_broadcast_msg (HWND hWnd, LPARAM msg) } else { - PostMessageW(hWnd, msg, 0, 0); + SendMessageW(hWnd, msg, 0, 0); EnumChildWindows (hWnd, UXTHEME_broadcast_msg_enumchild, msg); } return TRUE; -- 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 10

[Bug 51728] New: copypasta in pwcache.c:ctox()
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=51728 Bug ID: 51728 Summary: copypasta in pwcache.c:ctox() Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mpr Assignee: wine-bugs(a)winehq.org Reporter: gonzomdx(a)gmail.com Distribution: --- In https://source.winehq.org/git/wine.git/blob/refs/heads/master:/dlls/mpr/pwc… if( ( x >= 'a' ) && ( x <= 'a' ) ) should be changed to if( ( x >= 'a' ) && ( x <= 'f' ) ) -- 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 8

[Bug 51452] New: oleaut32:varformat fails in Wine when the currency sign has two characters or more
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=51452 Bug ID: 51452 Summary: oleaut32:varformat fails in Wine when the currency sign has two characters or more Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- oleaut32:varformat fails in Wine when the currency sign has two characters or more: https://test.winehq.org/data/patterns.html#oleaut32:varformat varformat.c:641: str=L"\062f.\0645.\200f 0.000" varformat.c:643: Test failed: Unexpected hr 0x80020005. In Morocco the currency sign has 5 characters. This is simply not supported by VarParseNumFromStr(). But even the currency sign is only two characters VarParseNumFromStr() fails because it advances a pointer by one character only. For instance with Polish: varformat.c:641: str=L"0,000 z\0142" varformat.c:643: Test failed: Unexpected hr 0x80020005. Note that the w10pro64 TestBot Windows VMs have an incorrect UserDefaultLCID so that these issues are not actually tested (see bug 51451). The w7u VMs are more correct in this regard but only test simple European cases (€). -- 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

[Bug 51435] New: iostream float formatting broken
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=51435 Bug ID: 51435 Summary: iostream float formatting broken Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: winebugz(a)t41t.com Distribution: --- Created attachment 70288 --> https://bugs.winehq.org/attachment.cgi?id=70288 test case solution demonstrating the error On wine-6.12-162-gd10887b8f56 Full solution is in the attachment, but Wine is improperly formatting floats when using printf "%g" or iostreams. A very simple example is: std::cout << 9.999999999999999e-5 << std::endl; It should print "0.0001". It does print "0". Of course, this affects much larger and more complicated programs, too. Tested on Ubuntu 20.04, although I don't think it matters. -- 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 10

[Bug 51382] New: NetEase Cloud Music crashes on zh_CN.UTF-8 locale.
by WineHQ Bugzilla 25 Feb '22

25 Feb '22

https://bugs.winehq.org/show_bug.cgi?id=51382 Bug ID: 51382 Summary: NetEase Cloud Music crashes on zh_CN.UTF-8 locale. Product: Wine Version: 6.11 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: jactry92(a)gmail.com Distribution: --- Created attachment 70237 --> https://bugs.winehq.org/attachment.cgi?id=70237 Registry for adding '宋体' font replacement. This looks like a regression of 93ef83e903354e5d28a9a0b14dd2ff83504f2b0f. Step to reproduce: 1. `export LANG=zh_CN.UTF-8 LANGUAGE=zh_CN.UTF-8 LC_ALL=zh_CN.UTF-8` 2. `winetricks -q fakechinese arial` for installing Chinese font and work around a CEF issue. 3. Add this registry: ``` [HKEY_CURRENT_USER\Software\Wine\Fonts\Replacements] "宋体"="Source Han Sans SC" ``` 4. `wine cloudmusicsetup2.9.1.199099.exe` for installing the application. 5. `cd .wine/drive_c/Program\ Files/Netease/CloudMusic` and `wine cloudmusic.exe` for running the application. Then it will crash when startup. -- 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 6

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 September 2021