May 2023 - Wine-bugs - list.winehq.org

[Bug 47331] New: Steam browser flickering
by wine-bugs＠winehq.org 27 May '25

27 May '25

https://bugs.winehq.org/show_bug.cgi?id=47331 Bug ID: 47331 Summary: Steam browser flickering Product: Wine-staging Version: 4.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: werifGX(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- As referenced on https://github.com/PhoenicisOrg/scripts/issues/994 steam installed using `winetricks 20190310-next` on debian buster using `wine-4.9 (Staging)` which has win7 environment, gameoverlayrenderer dll_override disabled and CSMT enabled result in flickering of steam browser as presented on https://youtu.be/LaR8nQ0Ir2w Suspecting this beeing wine 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.

2 20

[Bug 54948] New: EA app fails after login
by WineHQ Bugzilla 26 May '25

26 May '25

https://bugs.winehq.org/show_bug.cgi?id=54948 Bug ID: 54948 Summary: EA app fails after login Product: Wine Version: 8.8 Hardware: x86-64 URL: https://www.ea.com/ea-app OS: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- d3dcompiler_47 (x64) putted in '../Program Files/Electronic Arts/EA Desktop/EA Desktop' After login the app main window shows for a second and then immediately closes. Disabling d3d12 helps. 0a88:fixme:dxgi:d3d12_swapchain_init Ignoring swap effect 0x4. 0a88:fixme:dxgi:d3d12_swapchain_init Ignoring swapchain flags 0x2. Assertion failed: !status, file ../wine/dlls/winevulkan/loader_thunks.c, line 160 0324:err:seh:call_stack_handlers invalid frame 000000001C07EA48 (000000001C082000-000000001C180000) 0324:err:seh:call_stack_handlers invalid frame 000000001C07C820 (000000001C082000-000000001C180000) 0324:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception. 8.8-34-gd54e7cd51db -- 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 50155] New: Ableton Live: multicore audio processing causes high CPU usage across multiple audio backends
by WineHQ Bugzilla 26 May '25

26 May '25

https://bugs.winehq.org/show_bug.cgi?id=50155 Bug ID: 50155 Summary: Ableton Live: multicore audio processing causes high CPU usage across multiple audio backends Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sirwinstoncat5(a)gmail.com Distribution: Ubuntu When running Ableton Live, if multicore audio processing is enabled, CPU usage will drastically increase, causing unpredictable audio crackles and overall unstable performance. The easiest way to test this is using Ableton Live 9; Live 10 also has the same issue, but multicore audio processing is permanently turned on. - Open an empty Live Set. (By default, this has 4 empty tracks, a reverb effect, and a delay effect: a negligible amount of audio processing.) - In Ableton's preferences, under the CPU tab, disable multicore audio processing. Observe the built-in CPU meter in the upper-right corner; it should sit very low (0-1% on my system). - Enable multicore audio processing. Even with an empty Set, observe that the CPU meter jumps to at least 10-20%. On Windows, idle CPU usage should remain identical between single and multicore modes. - Attempt playback of a nontrivial Set; for example, a few tracks of recorded audio. A Set that plays back fine in single-core mode will exhibit unpredictable audio crackling and rapid spikes in CPU usage when using multicore mode. I have tested this across multiple versions of Ableton (various versions of 9 and 10 both exhibit this issue), multiple audio interfaces from various manufacturers (Behringer X32, NI Audio Kontrol 1, onboard chipset audio, PreSonus FireStudio), and even multiple audio backends (winepulse, wineasio->JACK). The issue seems to be most pronounced when using pulseaudio, but it is present across all audio backends. Most importantly, this issue can be duplicated using wineasio and a JACK server with the dummy backend (aka not connected to any audio interface). I am unsure where to start collecting logs for this. One guess: perhaps there is some sort of delay or sleep occuring while a mutex is being held? This is possibly related to #47458; however, that specifically refers to a test case for PulseAudio, whereas this bug occurs across backends. -- 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 39022] New: Mouse cursor shows the wrong symbol
by wine-bugs＠winehq.org 26 May '25

26 May '25

https://bugs.winehq.org/show_bug.cgi?id=39022 Bug ID: 39022 Summary: Mouse cursor shows the wrong symbol Product: Wine Version: 1.7.44 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sworddragon2(a)aol.com Distribution: --- Starting Steam and going to the menu bar -> Steam and moving the mouse cursor over the entry "Check for Steam Client Updates..." and then stopping the mouse results that the mouse cursor is showing the I symbol (the cursor symbol that for example also appears if moving the mouse cursor over a text area). Moving the mouse shows the normal mouse cursor again but stopping the mouse on the entry again shows the I symbol again. A workaround seems to be to close the menu and reopening it. -- 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 24785] New: Explorer++: tile view doesn't work
by wine-bugs＠winehq.org 25 May '25

25 May '25

http://bugs.winehq.org/show_bug.cgi?id=24785 Summary: Explorer++: tile view doesn't work Product: Wine Version: 1.3.5 Platform: x86-64 URL: http://www.explorerplusplus.com/download OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: RandomAccountName(a)mail.com Created an attachment (id=31335) --> (http://bugs.winehq.org/attachment.cgi?id=31335) Complete terminal output To reproduce, click view -> tiles. Nothing happens, it just looks the same as the default icon view. This looks pretty suspicious: fixme:listview:LISTVIEW_SetView View LV_VIEW_TILE unimplemented I can't test with the native comctl32, though (it crashes the program on startup). -- 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 8

[Bug 19371] New: BCArchive: encoutners unknown toolbar style
by wine-bugs＠winehq.org 25 May '25

25 May '25

http://bugs.winehq.org/show_bug.cgi?id=19371 Summary: BCArchive: encoutners unknown toolbar style Product: Wine Version: 1.1.26 Platform: PC URL: http://www.jetico.com/encryption-bcarchive/ OS/Version: Linux Status: NEW Keywords: download Severity: enhancement Priority: P2 Component: comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com CC: bunglehead(a)gmail.com fixme:toolbar:TOOLBAR_SetExtendedStyle Unknown Toolbar Extended Style 0x00000020. Please report. Native comctl32 'fixes' it. There's not major visual flaw afaict, but the fixme does say to report it ;-). -- 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 52466] New: Toolbar: Wrong size returned by TB_GETMAXSIZE message for toolbars with TBSTYLE_WRAPABLE style
by WineHQ Bugzilla 25 May '25

25 May '25

https://bugs.winehq.org/show_bug.cgi?id=52466 Bug ID: 52466 Summary: Toolbar: Wrong size returned by TB_GETMAXSIZE message for toolbars with TBSTYLE_WRAPABLE style Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: yal(a)csoftcom.com Distribution: --- Under Windows (I've tested Win10/11) TB_GETMAXSIZE always returns size for single row of buttons regardless of wrapped it or not. WINE calculates size for current wrapping. For example: under Win toolbar with initial size (0,0) and 2 buttons (20,20) TB_GETMAXSIZE always returns(40,20), WINE returns (20,40) - 2 rows wrapping. -- 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

[Bug 52465] New: Toolbar: Wrong TB_GETBUTTON message processing, returns (-1) instead of separator width in TBBUTTON structure
by WineHQ Bugzilla 25 May '25

25 May '25

https://bugs.winehq.org/show_bug.cgi?id=52465 Bug ID: 52465 Summary: Toolbar: Wrong TB_GETBUTTON message processing, returns (-1) instead of separator width in TBBUTTON structure Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: yal(a)csoftcom.com Distribution: --- >From MSDN documents about TB_GETBUTTON : If the button is a separator, that is, if fsStyle is set to BTNS_SEP, iBitmap determines the width of the separator, in pixels. So, this code needs to change: /wine/dlls/comctl32/toolbar.c:3373 static LRESULT TOOLBAR_GetButton (const TOOLBAR_INFO *infoPtr, INT nIndex, TBBUTTON *lpTbb) { ---------------------------<cut>------------------------ /*From MSDN documents: If the button is a separator, that is, if fsStyle is set to BTNS_SEP, iBitmap determines the width of the separator, in pixels*/ lpTbb->iBitmap = (btnPtr->fsStyle & BTNS_SEP) ? SEPARATOR_WIDTH : btnPtr->iBitmap; ---------------------------<cut>------------------------ -- 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 49280] New: Possible usage of null pointer line_def in edit.c
by WineHQ Bugzilla 25 May '25

25 May '25

https://bugs.winehq.org/show_bug.cgi?id=49280 Bug ID: 49280 Summary: Possible usage of null pointer line_def in edit.c Product: Wine Version: 5.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal54(a)gmail.com Distribution: --- `line_def` may be null(based on condition on while loop) but is used later `line_def->width` ``` while (line_def && line_idx) { line_def = line_def->next; line_idx--; } w = es->format_rect.right - es->format_rect.left; lw = line_def->width; ``` https://github.com/wine-mirror/wine/blob/f0ad5b5c546d17b281aef13fde996cda08… -- 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 15741] New: Emule: Configuration asistant window is not repainted correctly
by wine-bugs＠winehq.org 25 May '25

25 May '25

http://bugs.winehq.org/show_bug.cgi?id=15741 Summary: Emule: Configuration asistant window is not repainted correctly Product: Wine Version: 1.1.6 Platform: Other URL: http://www.emule-project.net OS/Version: other Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jaimerave(a)gmail.com Created an attachment (id=16836) --> (http://bugs.winehq.org/attachment.cgi?id=16836) Screenshot in WinXP The first time you run eMule, a configuration window will appear and after you pass to the second step, the background of the first window will still remain in the back. Check the screenshots. -- 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 21