wine-bugs June 2023

wine-bugs@winehq.org

1 participants
2653 discussions

[Bug 54135] New: JGlossator v5.0: Hovering textboxes not displaying
by WineHQ Bugzilla 05 Jul '23

05 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=54135 Bug ID: 54135 Summary: JGlossator v5.0: Hovering textboxes not displaying Product: Wine Version: 8.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: metcalsr(a)gmail.com Distribution: --- Created attachment 73666 --> https://bugs.winehq.org/attachment.cgi?id=73666 +mshtml Application features hover-over translations for text in the search box. This is not only an important QoL feature, but often provides alternative translations which aid significantly in understanding the text. These hovering boxes break under 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.

1 11

[Bug 55024] New: Sims 4 Studio window flickering
by WineHQ Bugzilla 05 Jul '23

05 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55024 Bug ID: 55024 Summary: Sims 4 Studio window flickering Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ryu.ketsueki(a)outlook.com Distribution: --- This is something that was happening before for a while now but it was tolerable. Now it's unusable. Sims 4 Studio updated to the (Star) release, as in the 3.2.0.6 and it's actually usable now. The application doesn't freeze when trying to render anything 3D, which was apparently an issue on Sims 4 Studio itself, as even in a virtual machine, it had the exact same error. Could only get around it by a dual boot with Windows. Not anymore. Sims 4 Studio runs relatively well and I can create and modify game packages normally. That was until recently, when the flickering got so much worse. I'll explain what is happening. The window would hang frames for a bit and flicker them instead of completely update to the newest frame. Now it doesn't hang anymore. Instead, the window appears completely black, except when hovering over buttons or menus, when the window flash its content for a split second and goes black again. This is still on top of the flickering of before, so it still hangs frames but still goes black constantly, making the application unusable. Now, to my knowledge, Sims 4 Studio requires .NET 6.0 to launch at all. I had to install it to make it work, even when it was usable. Maybe this is related Mono or .NET itself, I don't know. I did observe a behavior that may be connected to what is going on. When the window is flashing black, the center of the window has a square showing the correct content but it's following the Windows 10/11 spinning wheel, so only this loading wheel shows correctly. The behavior persists even when the wheel is gone -- 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 54240] New: wineserver crash when calling an rpc stub
by WineHQ Bugzilla 05 Jul '23

05 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=54240 Bug ID: 54240 Summary: wineserver crash when calling an rpc stub Product: Wine Version: 8.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: rpc Assignee: wine-bugs(a)winehq.org Reporter: memory.thrasher(a)gmail.com Distribution: --- "M.A.R.S." game would immediately crash when attempting to launch due to a missing (stubbed) function. I implemented the function in the linked merge request. Game submitted to app db, also linked below. https://gitlab.winehq.org/wine/wine/-/merge_requests/1888 https://appdb.winehq.org/objectManager.php?sClass=version&iId=41241&iTestin… With the above patch, the game progresses to a splashscreen before crashing without any helpful errors, likely due to "easy anti-cheat" software. With tracing enabled, I was able to confirm the rpc endpoint generated by my patch was functioning correctly. -- 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 47067] New: Font is too wide in RPGMaker game Hello Charlotte
by wine-bugs＠winehq.org 04 Jul '23

04 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=47067 Bug ID: 47067 Summary: Font is too wide in RPGMaker game Hello Charlotte Product: Wine Version: 4.6 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 64246 --> https://bugs.winehq.org/attachment.cgi?id=64246 Screenshot on Wine The font in the game is too wide, meaning long lines are cut off. Already tried winetricks allfonts, which doesn't help. To reproduce, just download the game, run Game.exe and click Start in the mainmenu. -- 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 53230] New: user32:win - test_activateapp() fails randomly with fvwm
by WineHQ Bugzilla 04 Jul '23

04 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=53230 Bug ID: 53230 Summary: user32:win - test_activateapp() fails randomly with fvwm Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:win - test_activateapp() fails randomly with fvwm. The failures themselves change quite a bit from one run to the next, depending on where in the function the failures start. It looks a bit like a race condition between the test and the window manager. Here is a relatively complete set: win.c:10976: Test failed: Expected foreground window 0, got 01DE007C win.c:10982: Test failed: Expected foreground window 001A013C, got 01DE007C win.c:10992: Test failed: Expected foreground window 001A013C, got 00000000 win.c:10999: Test failed: Expected foreground window 001A013C, got 01DE007C win.c:11001: Test failed: GetActiveWindow() = 00000000 win.c:11001: Test failed: GetFocus() = 00000000 win.c:11003: Test failed: Received WM_ACTIVATEAPP(0), did not expect it. win.c:11011: Test failed: Expected foreground window 001A013C, got 00000000 win.c:11013: Test failed: GetActiveWindow() = 00000000 win.c:11013: Test failed: GetFocus() = 00000000 win.c:11021: Test failed: Received WM_ACTIVATEAPP(1), did not expect it. https://test.winehq.org/data/patterns.html#user32:win The failures don't seem to depend on the locale or bitness. However they only happen in the TestBot VMs which happen to run fvwm (with a specially curated configuration file) and don't happen on my box which runs KDE for instance. -- 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 55158] New: Mouse input is broken at "POSTAL: Brain Damaged"
by WineHQ Bugzilla 03 Jul '23

03 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55158 Bug ID: 55158 Summary: Mouse input is broken at "POSTAL: Brain Damaged" Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dron2065(a)rambler.ru Distribution: --- Created attachment 74723 --> https://bugs.winehq.org/attachment.cgi?id=74723 Output log of application. At game "POSTAL: Brain Damaged" (GOG version) reaction to mouse moving is wrong, looking around with mouse is impossible. Cursor at menu works normally. -- 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 49229] New: Regression Requiem: Rise of the Reaver mouse issue since Release v5.0-rc3
by WineHQ Bugzilla 03 Jul '23

03 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=49229 Bug ID: 49229 Summary: Regression Requiem: Rise of the Reaver mouse issue since Release v5.0-rc3 Product: Wine-staging Version: 5.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ergoschnuffel(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- radeon/amdgpu (same behaviour) X11 on openbox Game: Requiem: Rise of the Reaver (http://www.playrequiem.com/) Use case: windowed multi client (transfer of items, shop open in the background etc.) issues: - need to click once to activate the game window and then it operates normally, before it was a direct click through (activate game window and action in the game) - mouse cursor gets trapped in game window A while moving the mouse to game window B and activating game window B (game window A/B overlapping a bit since monitor resolution). My issues started between Release v5.0-rc2 and Release v5.0-rc3 (update of the raw input patches?) and are still on going. -- 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 45772] New: Neo Manager needs 'pnputil.exe /a'
by wine-bugs＠winehq.org 02 Jul '23

02 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=45772 Bug ID: 45772 Summary: Neo Manager needs 'pnputil.exe /a' Product: Wine Version: 3.15 Hardware: x86 URL: http://support.renlearn.com/techkb/download/NEOManager 3_9_3USPC.zip OS: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: pnpmgr Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Continued from bug 45735. The installer runs `PnPUtil /a C:\Windows\Inf\AsUSBDrv.inf` to install its drivers. This fails since Wine doesn't implement pnputil.exe. Relevant part of wine log: Z:\home\hazel\Downloads\NEOManager3_9_3USPC>PnPUtil /a C:\Windows\Inf\AsUSBDrv.inf Can't recognize 'PnPUtil /a C:\Windows\Inf\AsUSBDrv.inf' as an internal or external command, or batch script. hazel@watership:~/Downloads$ sha1sum NEOManager3_9_3USPC.zip a844ab468a2c2034c0404f7fc655b7746c410d11 NEOManager3_9_3USPC.zip hazel@watership:~/Downloads$ du -sh NEOManager3_9_3USPC 70M NEOManager3_9_3USPC -- 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 28678] New: DirectDraw primary buffer is obscured by transparent window
by wine-bugs＠winehq.org 01 Jul '23

01 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=28678 Bug #: 28678 Summary: DirectDraw primary buffer is obscured by transparent window Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: octavian.voicu(a)gmail.com Classification: Unclassified Created attachment 36852 --> http://bugs.winehq.org/attachment.cgi?id=36852 Screenshot showing the obscured dialog. When trying to exit from the game The Longest Journey (either via menu option or pressing Alt+F4), a dialog box is shown with Yes/No options. The application uses DirectDraw for rendering. The dialog box and mouse cursor are rendered on an offscreen surface (dialog has an image as the background and buttons use a custom implementation afaics), which is then blitted to the primary buffer (happens like this when you force single buffer mode; with double buffering it could be slightly different, but the overall effect is the same). The dialog is a parent of the main application window, uses the standard dialog window class (atom #32270 or 8000 in hex) and has the WS_POPUP and WS_EX_TRANSPARENT window styles. Window receives a WM_ERASEBKGND message, which is handled by the default dialog proc by painting the background in the standard window background color (gray in this case). When primary buffer is blitted to the d3d surface (ddraw_surface_update_frontbuffer which uses OpenGL), the rendering of the dialog is masked by the window boundaries and the gray rectangle remains. Dialog is interactable and you can click the buttons (if you can do that without seeing where the mouse is). The question is: how can we make the primary buffer draw over WS_EX_TRANSPARENT child windows, as it works on native? Removing the WS_EX_TRANSPARENT style from the dialog window (on runtime, using WinSpy++ 1.7) makes native's behavior identical to current wine behavior (only a gray rectangle is visible). -- 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 30

[Bug 45857] New: Incorrect text color (The Longest Journey)
by wine-bugs＠winehq.org 01 Jul '23

01 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=45857 Bug ID: 45857 Summary: Incorrect text color (The Longest Journey) Product: Wine Version: 3.16 Hardware: x86-64 URL: https://games.softpedia.com/get/Games-Demo/The-Longest -Journey-161-Demo.shtml OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jhansonxi(a)gmail.com Distribution: Ubuntu Created attachment 62344 --> https://bugs.winehq.org/attachment.cgi?id=62344 Wine screenshot In-game text is outlined in a magenta color. See attached screenshots. Reproduced with demo 161 and full version (GOG.com) build 142. MD5: 6d7f91e0a19513e859775862b2ac43d8 thelongestjourneydemo_english.exe wine-devel 3.16.0~xenial from winehq.org Xbuntu 16.04.5 x86_64 Nvidia GeFOrce GTX 750 Ti, driver version 384.130 -- 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 4

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 June 2023