wine-bugs July 2024

wine-bugs@winehq.org

1 participants
1151 discussions

[Bug 49420] New: Ableton 10: file dialogs not DPI scaled
by WineHQ Bugzilla 20 Jul '24

20 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=49420 Bug ID: 49420 Summary: Ableton 10: file dialogs not DPI scaled Product: Wine Version: 5.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: io(a)mikelpr.com Distribution: --- the file open/save dialogs are not scaled when running with a different DPI, yet the mouse input is - like if the window were actually scaled. therefore, I can only click the top left halves (width and height) of the file dialogs -- 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 56900] New: Error related to download
by WineHQ Bugzilla 20 Jul '24

20 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56900 Bug ID: 56900 Summary: Error related to download Product: Wine Version: 6.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thatlocalbozo(a)gmail.com Distribution: --- Created attachment 76722 --> https://bugs.winehq.org/attachment.cgi?id=76722 cef_window_renderer.exe is non-functional, non-windows error I was downloading GameLoop Android Emulator and it malfunctioned as so. -- 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 25961] New: Visual C++ 2008 runtime not marked as installed by default
by wine-bugs＠winehq.org 20 Jul '24

20 Jul '24

http://bugs.winehq.org/show_bug.cgi?id=25961 Summary: Visual C++ 2008 runtime not marked as installed by default Product: Wine Version: 1.3.12 Platform: x86 OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: msvcrt AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com The installer for the app I'm looking at now checks for the visual c++ 2008 runtime, and runs D:\\Redistributable\\vcredist_x86_en.exe if it wasn't found. Now, one of these days, Wine's builtin msvcr / msvcp is going to suffice for this and most other apps, at which point Wine might want to set the registry to indicate that vcrun2008 is already installed. This might be in the distant future, depending on how many apps need the other things that come with the runtime package, like mfc and a full msvcp, that wine does not yet provide. So this bug will likely remain open for a long time (if it's not closed for being too far ahead of its time). For the record, this seems to be how the app is checking whether vcrun2008 is installed: 0024:Call msi.MsiQueryProductStateW(0033e2de L"{9A25302D-30C0-39D9-BD6F-21E6EC160475}") ret=0040b9ad 0024:Call advapi32.RegOpenKeyW(80000002,0033d6c2 L"Software\\Microsoft\\Windows\\CurrentVersion\\Installer\\Managed\\S-1-5-4\\Installer\\Products\\D20352A90C039D93DBF6126ECE614057",0033d968) ret=7ef2cd5c 0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=7ef2cd5c 0024:Call advapi32.RegOpenKeyW(80000001,0033d6c2 L"Software\\Microsoft\\Installer\\Products\\D20352A90C039D93DBF6126ECE614057",0033d968) ret=7ef2cd5c 0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=7ef2cd5c 0024:Call advapi32.RegOpenKeyW(80000002,0033d6c2 L"Software\\Classes\\Installer\\Products\\D20352A90C039D93DBF6126ECE614057",0033d968) ret=7ef2cd5c 0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=7ef2cd5c 0024:Call advapi32.RegOpenKeyW(80000002,0033d4ca L"Software\\Microsoft\\Windows\\CurrentVersion\\Installer\\UserData\\S-1-5-4\\Products\\D20352A90C039D93DBF6126ECE614057\\InstallProperties",0033d964) ret=7ef2b600 0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=7ef2b600 0024:Ret msi.MsiQueryProductStateW() retval=ffffffff ret=0040b9ad -- 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 56951] New: psql 16: unrecognized win32 error code: 127 invalid binary: Invalid argument / could not find a "psql.exe" to execute
by WineHQ Bugzilla 19 Jul '24

19 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56951 Bug ID: 56951 Summary: psql 16: unrecognized win32 error code: 127 invalid binary: Invalid argument / could not find a "psql.exe" to execute Product: Wine Version: 9.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: alex(a)willner.ws Distribution: --- **Version:** 9.11 **Steps that will reproduce the problem:** 1. curl -Os https://get.enterprisedb.com/postgresql/postgresql-16.3-2-windows-x64-binar… 2. unzip -q postgresql-16.3-2-windows-x64-binaries.zip 3. wine pgsql/bin/psql.exe --version **What is the expected result:** psql (PostgreSQL) 16.3 **What happens instead:** unrecognized win32 error code: 127invalid binary "Z:\pgsql\bin\psql.exe": Invalid argument psql (PostgreSQL) 16.3 **Possible workaround:** Downgrade to psql 15 *Any additional information:** % curl -Os https://get.enterprisedb.com/postgresql/postgresql-15.7-1-windows-x64-binar… && unzip -q postgresql-15.7-1-windows-x64-binaries.zip && wine pgsql/bin/psql.exe --version psql (PostgreSQL) 15.7 % % curl -Os https://get.enterprisedb.com/postgresql/postgresql-16.3-2-windows-x64-binar… && unzip -q postgresql-16.3-2-windows-x64-binaries.zip && wine cmd Z:\> cd pgsql\bin Z:\pgsql\bin>psql.exe --version unrecognized win32 error code: 127unrecognized win32 error code: 127unrecognized win32 error code: 127unrecognized win32 error code: 127unrecognized win32 error code: 127unrecognized win32 error code: 127unrecognized win32 error code: 127un recognized win32 error code: 127unrecognized win32 error code: 127could not find a "psql.exe" to execute psql (PostgreSQL) 16.3 -- 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

[Bug 55868] New: Horizontal tab character (ASCII 0x09) not rendered in text fields
by WineHQ Bugzilla 19 Jul '24

19 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=55868 Bug ID: 55868 Summary: Horizontal tab character (ASCII 0x09) not rendered in text fields Product: Wine Version: 5.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vojtech.turek(a)hotmail.cz Distribution: --- Created attachment 75394 --> https://bugs.winehq.org/attachment.cgi?id=75394 Wine vs. Windows: the text field contains two horizontal tab characters, none of which are rendered by Wine If a text field contains horizontal tab (ASCII 0x09) characters, these are not rendered. See the attached screenshot from Wine 5.0.3 (left) and the same application running under Windows 10 x64 (right). The field value is "<HT>www.test.org<HT>x" ("<HT>" denotes a single horizontal tab character), yet Wine shows just "www.test.orgx" in the field. However, Wine clearly knows the horizontal tab characters are present, because it shows them in the text field tooltip stating (in English) "Website address<NEW LINE>[<TEXT FIELD VALUE>]". Installing corefonts via winetricks (as recommended in bug #45316) does not lead to any improvement. -- 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 12

[Bug 56986] New: Cursor flickering in Infinity Engine games
by WineHQ Bugzilla 19 Jul '24

19 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56986 Bug ID: 56986 Summary: Cursor flickering in Infinity Engine games Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: accounts.winehq.org(a)vv221.fr Distribution: --- I get cursor flickering with some of the Infinity Engine games, maybe in all of them. csmt is disabled, to prevent performance problems. The games are run in a WINE virtual desktop. The flickering disappear if the games are run in windowed mode, it only happens when in full screen mode. I plan to run extra tests, first to ensure it actually affects all Infinity Engine games, then to check if the flicker still happens with the current development build of WINE, finally to find out when this problem was introduced. I am quite sure this is a regression, as I do not remember this flickering from the last time I played these games (that was probably prior to WINE 9.0). -- 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

[Bug 36692] New: Bad performance when combineng SetEvent / WaitForSingleObject for synchronizing worker threads
by wine-bugs＠winehq.org 19 Jul '24

19 Jul '24

http://bugs.winehq.org/show_bug.cgi?id=36692 Bug ID: 36692 Summary: Bad performance when combineng SetEvent / WaitForSingleObject for synchronizing worker threads Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: milasudril(a)gmail.com In a 2d simulation program, each worker thread has its own pair of events. One event is used to signal master thread that the worker thread is ready. The other is used by the master thread to signal that the worker thread may continue. In Master thread: while(!m_stop) { auto proc_ptr=processors.begin(); while(proc_ptr!=processors.end()) { // Call SetEvent on "start" event object owned by the object pointed // to by proc_ptr proc_ptr->frameNext(); ++proc_ptr; } proc_ptr=processors.begin(); while(proc_ptr!=processors.end()) { // Call WaitForSingleObject on "ready" event object owned by // the object pointed to by proc_ptr proc_ptr->wait(); ++proc_ptr; } ++framecounter; } In worker thread: while(!m_stop) { // Wait for master thread signaling start event (Calls WaitForSingleObject) start.wait(); m_model->process(m_framecounter,m_buffers[0].first ,m_buffers[0].second,m_offset); swap(m_buffers[0],m_buffers[1]); // Signal master thread that we are ready for next frame (Calls SetEvent) ready.set(); } On Wine, the framerate is half of that on Windows 7 on the same machine Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz. Also there seems to be a huge different workload on differnt cores when running under Wine. I realize that SetEvent/WaitForSingleObject are heavy functions on Windows too as they need kernel assistance, so it might be hard to make it perform better. -- 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 29

[Bug 56985] New: how to improve the performance of Wine?
by WineHQ Bugzilla 19 Jul '24

19 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56985 Bug ID: 56985 Summary: how to improve the performance of Wine? Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: csumushu(a)126.com Distribution: --- Created attachment 76816 --> https://bugs.winehq.org/attachment.cgi?id=76816 demo.c I have found that my program runs much slower when using Wine compared to running it directly on Windows. On Windows, it responds quickly, but when running with Wine, there is a delay of three to four seconds. After analyzing the program code, I discovered a loop within which semaphore operations are performed. The time consumption for a single semaphore operation is 10-4 seconds when using Wine, whereas it only takes 10-6 seconds on Windows. I wrote a demo program to test it and indeed confirmed this. Semaphore operations are just one example; some other Windows APIs are also significantly slower when compared to Windows. Is there any way to optimize 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 56987] New: PiTool (pi_server.exe) can't detect Pimax HMD hid/usb devices
by WineHQ Bugzilla 19 Jul '24

19 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56987 Bug ID: 56987 Summary: PiTool (pi_server.exe) can't detect Pimax HMD hid/usb devices Product: Wine Version: 9.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: ivarbug(a)gmail.com Distribution: --- Created attachment 76817 --> https://bugs.winehq.org/attachment.cgi?id=76817 using app's hidapi.dll https://appdb.winehq.org/objectManager.php?sClass=application&iId=19830 The windows application is able to enumerate hid devices but doesn't identify or start talking to it's devices. The app comes with and uses a build of hidapi.dll (version <= 0.9.0 based on it's exports). I followed https://wiki.winehq.org/Winelib_User%27s_Guide#Building_Winelib_DLLs and tried building my own hidapi.dll that uses Linux native hidapi-hidraw. Using this the app does pick up the device, but crashes (probably unrelated to hid) after ~5s in an ungetc call. -- 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 56983] New: UI: Application using ModernWPF crashes, Windows.UI.ViewManagement.UISettings not implemented
by WineHQ Bugzilla 18 Jul '24

18 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56983 Bug ID: 56983 Summary: UI: Application using ModernWPF crashes, Windows.UI.ViewManagement.UISettings not implemented Product: Wine Version: 9.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: madbyte(a)tuta.io Distribution: --- Created attachment 76812 --> https://bugs.winehq.org/attachment.cgi?id=76812 Generated log file using WINEDEBUG=err+all,+debugstr UI library: ModernWPF(https://github.com/Kinnara/ModernWpf) Tried on latest Wine 9.13 devel release. Log is in the 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.

1 3

Jump to page:

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 July 2024