wine-bugs August 2023

wine-bugs@winehq.org

1 participants
2748 discussions

[Bug 55374] New: user32:msg - test_swp_paint_region_on_show() sometimes gets a NULLREGION on Windows 7
by WineHQ Bugzilla 09 Aug '23

09 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55374 Bug ID: 55374 Summary: user32:msg - test_swp_paint_region_on_show() sometimes gets a NULLREGION on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:msg - test_swp_paint_region_on_show() sometimes gets a NULLREGION on Windows 7: msg.c:9471: Test failed: GetRgnBox (on parent) returned 1 msg.c:9475: Test failed: parent update region: got (0,0)-(0,0), expected (10,10)-(100,100) msg.c:9508: Test failed: GetRgnBox (on parent) returned 1 msg.c:9512: Test failed: parent update region: got (0,0)-(0,0), expected (20,20)-(120,120) See https://test.winehq.org/data/patterns.html#user32:msg The oldest known failure happened on 2023-06-22 and it has happened a bit over once per week since, always on a w7u test configuration: * 2023-06-22 win7_newtb-w7u-2qxl * 2023-06-23 win7_newtb-w7u * 2023-06-26 win7_newtb-w7u-2qxl * 2023-07-13 win7_newtb-w7u-2qxl_1 * 2023-07-14 win7_newtb-w7u-de * 2023-07-14 win7_newtb-w7u-de * 2023-07-19 win7_newtb-w7u-es * 2023-07-19 win7_newtb-w7u-es -- 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 12427] New: win16 test suite: printdlg test fails
by wine-bugs＠winehq.org 09 Aug '23

09 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=12427 Summary: win16 test suite: printdlg test fails Product: Wine Version: CVS/GIT Platform: PC URL: http://win16test.googlecode.com OS/Version: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=11966) --> (http://bugs.winehq.org/attachment.cgi?id=11966) Backtrace in git +++ This bug was initially created as a clone of Bug #9850 +++ The code can be downloaded from http://win16test.googlecode.com with svn, and is quite easy to run; see http://win16test.googlecode.com/svn/trunk/src/README for instructions. The printdlg test crashes in current git. Attached is the backtrace in current git. -- 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 55423] New: dinput:device8 - test_mouse_keyboard() sometimes gets access denied on Windows 10
by WineHQ Bugzilla 09 Aug '23

09 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55423 Bug ID: 55423 Summary: dinput:device8 - test_mouse_keyboard() sometimes gets access denied on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinput:device8 - test_mouse_keyboard() sometimes gets access denied on Windows 10: device8.c:695: Test failed: IDirectInputDevice8_Acquire failed: 0x80070005 device8.c:698: Test failed: IDirectInputDevice8_Acquire failed: 0x80070005 device8.c:703: Test failed: GetRegisteredRawInputDevices returned 1, raw_devices_count: 3 device8.c:705: Test failed: Unexpected raw device flags: 0 device8.c:707: Test failed: Unexpected raw device flags: 0 See https://test.winehq.org/data/patterns.html#dinput:device8 Where 0x80070005 == E_ACCESSDENIED This failure mode has been jumping around: * From 2023-01-06 to 2023-03-20 this was happening exclusively on w7u, with one exception, w10pro64-ru-64 on 2023-01-13 (all with "raw_devices_count: 3"). * Then from 2023-03-21 to 2023-05-16 it happened exclusively on various debian11-win32 locales, but with "raw_devices_count: 1". * And since 2023-05-30 it has been happening exclusively on w1064v1507 and w10pro64v2004 (both in 32 and 64-bit) with 12 instances so far, all with "raw_devices_count: 3". See also bug 54558 about other access denied errors in dinput:device8. -- 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 1

[Bug 55413] New: ddraw:ddraw1 sometimes fails and crashes on w1064v1507 and w1046v2004
by WineHQ Bugzilla 09 Aug '23

09 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55413 Bug ID: 55413 Summary: ddraw:ddraw1 sometimes fails and crashes on w1064v1507 and w1046v2004 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ddraw:ddraw1 sometimes fails on w1064v1507 and w1046v2004: ddraw1.c:2495: Test failed: Expected message 0x46, but didn't receive it. ddraw1.c:2618: Test failed: Failed to set foreground window. ddraw1.c:2626: Test failed: Failed to set foreground window. ddraw1.c:2652: Test failed: Expected window style 0x14cf0000, got 0x4cf0000. ddraw1.c:2655: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2662: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2671: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2680: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2683: Test failed: Failed to set foreground window. ddraw1.c:2690: Test failed: Expected window style 0x14cf0000, got 0x4cf0000. ddraw1.c:2693: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2706: Test failed: Failed to set foreground window. ddraw1.c:2731: Test failed: Failed to set foreground window. ddraw1.c:2746: Test failed: Failed to set foreground window. ddraw1.c:2755: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2775: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2778: Test failed: Failed to set foreground window. ddraw1.c:2781: Test failed: Expected window style 0x34cf0000, got 0x14cf0000. ddraw1.c:2784: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:3129: Test failed: Failed to set foreground window. ddraw1.c:3130: Test failed: Expected message 0x6, but didn't receive it. ddraw1.c:3135: Test failed: Got unexpected screen size 800x600. ddraw1.c:867: Test failed: Got unexpected wparam 0 for message 0x1c, expected 0x1. ddraw1.c:3141: Test failed: Expected message 0x5, but didn't receive it. ddraw1.c:3144: Test failed: Expected (0,0)-(640,480), got (-32000,-32000)-(-31840,-31972). ddraw1.c:3148: Test failed: Got unexpected screen size 1024x768. ddraw1.c:3161: Test failed: Expected message 0x46, but didn't receive it. [...] ddraw1.c:3609: Test failed: Expected (0,0)-(640,480), got (-8,-8)-(648,448). ddraw1.c:4338: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:4350: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:4362: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:4384: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:8051: Test failed: Failed to set foreground window. ddraw1.c:8053: Test failed: Got unexpected hr 0. ddraw1.c:8055: Test failed: Got unexpected hr 0. ddraw1.c:8057: Test failed: Got unexpected hr 0. ddraw1.c:8059: Test failed: Got unexpected hr 0. ddraw1.c:8069: Test failed: Got unexpected hr 0. ddraw1.c:8071: Test failed: Got unexpected hr 0. ddraw1.c:8073: Test failed: Got unexpected hr 0. ddraw1.c:8077: Test failed: Failed to set foreground window. ddraw1.c:8079: Test failed: Got unexpected hr 0. ddraw1.c:8081: Test failed: Got unexpected hr 0. ddraw1.c:8087: Test failed: Got unexpected hr 0. ddraw1.c:8135: Test failed: Failed to set foreground window. ddraw1.c:8147: Test failed: Failed to set foreground window. ddraw1.c:13670: Test failed: WM_KILLFOCUS was not received. ddraw1.c:13706: Test failed: Got unexpected hr 0x887600e1. ddraw1.c:13709: Test failed: Got unexpected hr 0x887600ff. 0a60:ddraw1: unhandled exception c0000005 at 00007FF6FFAE2567 See https://test.winehq.org/data/patterns.html#ddraw:ddraw1 Where 0x46 == WM_WINDOWPOSCHANGING and the test window does not seem to be visible: expected: 0x14cf0000 == WS_VISIBLE | 0x04cf0000 This failure happens irregularly and only on w1064v1507 and w1046v2004 so far: * 2022-12-14 win1507_newtb-w1064v1507-64 * 2022-12-15 win1507_newtb-w1064v1507-64 * 2023-01-31 win1507_newtb-w1064v1507-64 * 2023-02-16 win1507_newtb-w1064v1507-64 * 2023-06-07 win1507_newtb-w1064v1507-64 * 2023-06-09 win1507_newtb-w1064v1507-32 * 2023-07-13 win1507_newtb-w1064v1507-64 * 2023-07-27 win2004_newtb-w10pro64v2004-64 -- 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 55388] New: d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd
by WineHQ Bugzilla 09 Aug '23

09 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55388 Bug ID: 55388 Summary: d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd: visual.c:19496: Test failed: Failed to draw, hr 0x80004005. visual.c:19792: Test failed: Got unexpected color 0x0000ff00. See https://test.winehq.org/data/patterns.html#d3d9:visual These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they do not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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 53423] New: Baldur's gate 3 need allocation callbacks for winevulkan
by WineHQ Bugzilla 08 Aug '23

08 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=53423 Bug ID: 53423 Summary: Baldur's gate 3 need allocation callbacks for winevulkan Product: Wine Version: 7.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winevulkan Assignee: wine-bugs(a)winehq.org Reporter: charles2000wang(a)gmail.com Distribution: --- Baldur's gate 3 crashes on startup when using the vulkan renderer. These are the error messages in terminal 0140:fixme:vulkan:wine_vkCreateWin32SurfaceKHR Support for allocation callbacks not implemented yet 0140:fixme:vulkan:__wine_create_vk_device_with_callback Support for allocation callbacks not implemented yet It seems that winevulkan does not have allocation callbacks. -- 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 51122] New: 5.0.3 vs 6.x - slow performance in graphics
by WineHQ Bugzilla 08 Aug '23

08 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=51122 Bug ID: 51122 Summary: 5.0.3 vs 6.x - slow performance in graphics Product: Wine Version: 6.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mondane.woodworker(a)gmail.com Distribution: --- When I use 6.x, even 'winecfg' starts like a slideshow. This doesn't happen with 5.0.3 . No application can be ran like this. Using: * Wine 6.0 - 6.7 * Ubuntu Unity 20.04.1 ( https://ubuntuunity.org/ ) * Laptop: Dell Precision 7550 * Graphics: NVIDIA TU117GLM [Quadro T2000 Mobile / Max-Q] ** Using nvidia-driver-460 -- 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 55419] New: dxgi:dxgi - test_video_memory_budget_notification() is sometimes missing an event in Wine
by WineHQ Bugzilla 08 Aug '23

08 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55419 Bug ID: 55419 Summary: dxgi:dxgi - test_video_memory_budget_notification() is sometimes missing an event in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- dxgi:dxgi - test_video_memory_budget_notification() is sometimes missing an event in Wine: dxgi.c:7876: Test failed: Expected event fired. See https://test.winehq.org/data/patterns.html#dxgi:dxgi The first known instance goes back to 2023-01-26 and it has been happening a bit over twice per month since, mostly on the debiant VM but also on the GitLab CI environment and fg-deb64 (my desktop). -- 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 55418] New: quartz:vmr9 - test_surface_allocator_notify_refcount() sometimes crashes on w11pro64_nv
by WineHQ Bugzilla 08 Aug '23

08 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55418 Bug ID: 55418 Summary: quartz:vmr9 - test_surface_allocator_notify_refcount() sometimes crashes on w11pro64_nv Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com quartz:vmr9 - test_surface_allocator_notify_refcount() sometimes crashes on w11pro64_nv: vmr9.c:3475: this is the last test seen before the exception 1828:vmr9: unhandled exception c0000005 at 000000000049805A See https://test.winehq.org/data/patterns.html#quartz:vmr9 This is crash happened only twice so far and both times on w11pro64_nv, the TestBot's Windows 11 Nvidia RTX 3050 VM: * 2023-08-04 w11pro64-nv-64 * 2023-03-03 w11pro64-nv-64 -- 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 1

[Bug 55396] New: advapi32:registry breaks test_registerOIDFunction() in crypt32:oid on w8adm
by WineHQ Bugzilla 07 Aug '23

07 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55396 Bug ID: 55396 Summary: advapi32:registry breaks test_registerOIDFunction() in crypt32:oid on w8adm Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:registry breaks test_registerOIDFunction() in crypt32:oid on w8adm: oid.c:297: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:303: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:305: Test failed: Could not delete bogus key oid.c:314: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:321: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:325: Test failed: Could not delete CryptDllEncodeObject key oid.c:336: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:340: Test failed: Could not delete CryptDllEncodeObject key oid.c:343: Test failed: Could not delete 'EncodingType 3' key oid.c:377: Test failed: Expected ERROR_FILE_EXISTS, got 00000000 oid.c:382: Test failed: Expected ERROR_FILE_EXISTS, got 00000000 oid.c:390: Test failed: Expected key to exist, RegOpenKeyA failed: 2 oid.c:412: Test failed: CryptUnregisterDefaultOIDFunction failed: 00000002 oid.c:416: Test failed: CryptUnregisterDefaultOIDFunction failed: 00000002 oid.c:430: Test failed: CryptUnregisterDefaultOIDFunction failed See https://test.winehq.org/data/patterns.html#crypt32:oid More precisely these failures only happen if running advapi32:registry before crypt32:oid. Furthermore the failures started on 2023-07-27 which is when the w8 VM's memory was increased to 4GB, and older WineTest builds still produce the failures. So the 2023-07-27 VM change is the cause of these failures but it's not clear why. -- 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 657] Many games and applications need 'mfc42.dll' ('winetricks -q mfc42' is a workaround)
by WineHQ Bugzilla 07 Aug '23

07 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=657 Bartosz <gang65(a)poczta.onet.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gang65(a)poczta.onet.pl -- 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 0

[Bug 55412] New: Super Bubsy crashes before the intro
by WineHQ Bugzilla 06 Aug '23

06 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55412 Bug ID: 55412 Summary: Super Bubsy crashes before the intro Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: spzakulec(a)gmail.com Distribution: --- Created attachment 74972 --> https://bugs.winehq.org/attachment.cgi?id=74972 wine console output and backtrace from crash When I try to install & run Super Bubsy as specified in the AppDB page: https://appdb.winehq.org/objectManager.php?sClass=version&iId=19820 the game crashes right away. Per the AppDB instructions (reproduced below), I've tried to install the game and run it with the videomemorysize=512M winetricks verb. WINEPREFIX="$HOME/SuperBubsy" WINEARCH=win32 wine wineboot WINEPREFIX="$HOME/SuperBubsy" winecfg ---> set Windows 95, do not allow to decorate windows, emulate desktop WINEPREFIX="$HOME/SuperBubsy" winetricks videomemorysize=512 Install the game and to run it: WINEPREFIX="$HOME/SuperBubsy" wine $HOME/SuperBubsy/drive_c/SUPER\ BUBSY/Bubsy.exe I'm on KDE Neon 5.27, using Wine 8.13. -- 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 0

[Bug 54825] New: Visual Studio C++ Build Tools fails to install with 'Could not find Windows Runtime type'
by WineHQ Bugzilla 06 Aug '23

06 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54825 Bug ID: 54825 Summary: Visual Studio C++ Build Tools fails to install with 'Could not find Windows Runtime type' Product: Wine-staging Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lupino8211(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 74328 --> https://bugs.winehq.org/attachment.cgi?id=74328 full_install.log I'm trying to install MSVC toolchain in wine in docker, but didn't succeed. I'm installing tools in following order: - dotnet48 - winecfg /v win10 - Visual Studio C++ Build Tools Installation ends in the following error (from logs which can be found in wine user's Temp directory): [025c:000a][2023-04-13T20:48:57] Error 0x80131522: Rethrowing the exception from the engine: Could not find Windows Runtime type 'Windows.Networking.Connectivity.NetworkCostType'. but how I can inspect, these DLL's exist in the following paths: /root/.wine/drive_c/windows/system32/windows.networking.connectivity /root/.wine/drive_c/windows/syswow64/windows.networking.connectivity and should contain mentioned type. How to reproduce: Download vs_BulidTools.exe from https://download.visualstudio.microsoft.com/download/pr/d24d0627-f1e2-4a69-… Install it via: wine cmd /c start /wait vs_BuildTools.exe \--quiet --add "Microsoft.VisualStudio.Workload.VCTools;includeRecommended" --add "Microsoft.VisualStudio.Workload.MSBuildTools;includeRecommended" --add "Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools;includeRecommended" --add "Microsoft.VisualStudio.Component.VC.Tools.x86.x64;includeRecommended" -- 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 1

[Bug 25100] New: the program don't start...
by wine-bugs＠winehq.org 06 Aug '23

06 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=25100 Summary: the program don't start... Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: salvatore91salvatore(a)yahoo.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 3

[Bug 55406] New: mIRC hangs on receiving a new PM
by WineHQ Bugzilla 06 Aug '23

06 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55406 Bug ID: 55406 Summary: mIRC hangs on receiving a new PM Product: Wine Version: 8.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kooldioxide(a)gmail.com Distribution: --- This problem started once I upgraded mIRC to version 7.74. When someone sends me a PM and this causes mIRC to open a new window, mIRC hangs entirely, and the process keeps using a lot of CPU according to htop. Only thing I can do at that point is kill the process. The problem doesn't occur if I already have a query window open with the person sending me a message. An easy way to reproduce this is to connect to an IRC server, then from the status window: /msg <my_own_nick> hello That will open a query window to yourself which triggers this behaviour as well. This problem occurs on two different Linux installations I tried, one with Wine 8.12 and one with Wine 8.0.2. -- 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 1

[Bug 32900] New: The Bat 5.2.2 - keyboard keys stick
by wine-bugs＠winehq.org 05 Aug '23

05 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=32900 Bug #: 32900 Summary: The Bat 5.2.2 - keyboard keys stick Product: Wine Version: 1.1.22 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sprog(a)online.ru Classification: Unclassified It happens rarely and may be related to RU keyboard layout. You press Cntr-N a new message form is created but pressing letters on a keyboard won't work as expected. If fact it's like you're constantly holding right CTL key. You press right CTL again and the bug disappears.... The same happens happens with ALT key too. The probles was in Wine versions starting from 1.4.1 Unfortunately I can't give you the conditions how to reproduce the bug. This report is more like "think about what could go wrong". If you can advise how to trace this problem - I'll do it. The Bat all so has problems with ole32. From to time the Connection Center causes OLE32 error. The conditions are unkown. It happens once if 2-3 days. After that the connection center works but the status bar is showing OLE32 error... -- 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 7

[Bug 55393] New: The process which started "The Bat!" is still running after the app ist quieted
by WineHQ Bugzilla 05 Aug '23

05 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55393 Bug ID: 55393 Summary: The process which started "The Bat!" is still running after the app ist quieted Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mywine(a)schiermeier-it.de Distribution: --- Created attachment 74957 --> https://bugs.winehq.org/attachment.cgi?id=74957 Part of "ps faux" command Setting: "The Bat!" is installed by its installer and "GnuPG" is also installed with its installer. "The Bat!" is starting normally and the encrypting is working. A mail was created, encrypted, or signed and sent. Now "The Bat!" is quieted by its menu entry. The GUI disappears. Now "(h)top" or "ps" shows still some processes running and can only be quieted with "kill": ---ps faux--- USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND (...) joerg 3281 3.4 0.0 19668 19144 ? Ss 00:59 0:08 /opt/wine-devel/bin/wineserver joerg 3285 0.0 0.0 2380696 16724 ? Ssl 00:59 0:00 C:\windows\system32\services.exe joerg 3288 0.1 0.0 2055360 15552 ? Ssl 00:59 0:00 C:\windows\system32\winedevice.exe joerg 3297 0.8 0.0 2297900 38264 ? Ssl 00:59 0:02 C:\windows\system32\winedevice.exe joerg 3306 0.1 0.0 2142560 29912 ? Ssl 00:59 0:00 C:\windows\system32\plugplay.exe joerg 3314 0.0 0.0 1919060 9596 ? Ssl 00:59 0:00 C:\windows\system32\svchost.exe -k LocalServiceNetworkRestricted joerg 3325 0.1 0.1 2169640 86012 ? Sl 00:59 0:00 C:\windows\system32\explorer.exe /desktop joerg 3330 0.0 0.0 2247080 14336 ? Ssl 00:59 0:00 C:\windows\system32\rpcss.exe joerg 3618 0.4 0.0 2704816 30700 ? Ss 01:00 0:00 z:\opt\winprog\GnuPG\bin\gpg-agent.exe --homedir c:\users\username\appdata\roaming\gnupg-tb --use-standard-socket --daemon ---///--- See also the attached log file. Internally the GnuPG is started from The Bat! via the command line. For another purpose (and wine bug) I wrote a little wrapper to log the commands which The Bat!s hands over to GnuPGs exe-file (gpg.exe). -- 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 49845] New: Sacred Gold: very bad performance (low fps) when zoomed out
by WineHQ Bugzilla 03 Aug '23

03 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=49845 Bug ID: 49845 Summary: Sacred Gold: very bad performance (low fps) when zoomed out Product: Wine Version: 5.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: phaidros(a)gmx.at Distribution: --- Sacred 1 Gold provides 3 zoom levels: Very close, middle and zoomed out. I guess most people really only use the zoomed out setting, the other two show such a small portion of the world that i don't know how anybody could enjoy the experience. Unfortunately the zoomed out setting gives very bad performance, around 20fps on a Ryzen 2700X @ 3.7GHz. Using the middle zoom setting fps go up to about 30-35fps and the very close zoom setting gives 55-60fps. I don't really understand what's going on, I think this is a very old game and a 8-core 3.7GHz CPU should have no problem whatsoever to run it. The 20fps i'm getting make the game really unenjoyable to the extent where i would rather boot windows to play it (where i'm getting 60fps at all zoom levels). I tried with and without CSMT, fixing the process to a single CPU core etc. Unfortunately no luck. It is really strange that the game would run at almost 60fps when zoomed in and then take such a massive performance hit when zooming out. -- 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 53956] New: Sacred Underworld crashes after launching
by WineHQ Bugzilla 03 Aug '23

03 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=53956 Bug ID: 53956 Summary: Sacred Underworld crashes after launching Product: Wine Version: 7.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Alexandr42suv(a)mail.ru Distribution: --- Created attachment 73536 --> https://bugs.winehq.org/attachment.cgi?id=73536 automatically generated backtrace When I was trying to run Sacred Underworld 2.28, I got an error message and game crashes. Other games or windows programs works well CPU: Intel Core i3-4005u GPU: Intel HD Graphics 4400 -- 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 14

[Bug 54124] New: Sacred Underworld black screen hanging
by WineHQ Bugzilla 03 Aug '23

03 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54124 Bug ID: 54124 Summary: Sacred Underworld black screen hanging Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: VladimirVSC(a)yandex.ru Distribution: --- Created attachment 73656 --> https://bugs.winehq.org/attachment.cgi?id=73656 Sacred Underworld crash report When starting the game, the black screen appears which hangs until you press Escape or anything else. Then "Application is not responding" message appears and the game crashes to desktop. The same for stable 7.0.1 and 8.0-rc1. -- 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 1

[Bug 39236] New: shell32:shlfileop fails if privileges not high enough
by wine-bugs＠winehq.org 03 Aug '23

03 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=39236 Bug ID: 39236 Summary: shell32:shlfileop fails if privileges not high enough Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- If the user cannot write to the root of the c: drive the test fails with the following errors: shlfileop.c:2497: Test failed: The file does not exist shlfileop.c:2499: Test failed: File is not removed, ErrorCode: 1026 shlfileop.c:94: Test failed: Failure to open file shlfileop.c:2505: Test failed: The file does not exist shlfileop.c:2507: Test failed: File is not removed, ErrorCode: 1026 In particular one can notice this bug on the following WineTest box: fg-win2000-rusr: Windows 2000 with a Restricted user account The test should try to write its Unicode file in the temporary directory. The test regression was introduced by this commit: commit 1fc0cb75eebeb011a1f620fb96f32245d886916c Author: Nigel Liang <ncliang(a)gmail.com> Date: Fri Jun 8 14:25:24 2007 -0700 shell32: Conformance tests for unicode filenames and fix a bug for file deletion. -- 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

[Bug 55395] New: dinput:force_feedback - test_device_managed_effect() sometimes fails on w8
by WineHQ Bugzilla 03 Aug '23

03 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55395 Bug ID: 55395 Summary: dinput:force_feedback - test_device_managed_effect() sometimes fails on w8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinput:force_feedback - test_device_managed_effect() sometimes fails on w8: driver_bus.c:290: Test failed: id 1: force_feedback.c:4180 got spurious packet driver_bus.c:1098: Test failed: id 1: force_feedback.c:4180 expect[0]: got 0xb000f, expected 0 driver_bus.c:1099: Test failed: id 1: force_feedback.c:4180 expect[0]: got id 6 driver_bus.c:1100: Test failed: id 1: force_feedback.c:4180 expect[0]: got len 2 See https://test.winehq.org/data/patterns.html#dinput:force_feedback These failures are specific to the 32-bit Windows 8 TestBot VM, w8, and they happened 5 times over the past 8 months: * 2022-12-09 win81_newtb-w8 * 2023-01-31 win81_newtb-w8 * 2023-05-05 win81_newtb-w8 * 2023-05-26 win81_newtb-w8 * 2023-07-27 win81_newtb-w8 -- 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 1

[Bug 55298] New: gdi32:font fails the MS Shell Dlg tests in the Arabic, Japanese and Chinese locales in Wine
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55298 Bug ID: 55298 Summary: gdi32:font fails the MS Shell Dlg tests in the Arabic, Japanese and Chinese locales in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- gdi32:font fails the MS Shell Dlg tests in the Arabic, Japanese and Chinese locales in Wine: test_nonexistent_font() font.c:4181: Test failed: MS Shell Dlg should be enumerated font.c:4183: Test failed: MS Shell Dlg should be enumerated font.c:4192: Test failed: expected MS Shell Dlg, got Arial font.c:4205: Test failed: expected MS Shell Dlg, got Arial font.c:4181: Test failed: MS Shell Dlg should be enumerated font.c:4183: Test failed: MS Shell Dlg should be enumerated font.c:4192: Test failed: expected MS Shell Dlg, got Arial font.c:4205: Test failed: expected MS Shell Dlg, got Arial font.c:4181: Test failed: MS Shell Dlg should be enumerated font.c:4183: Test failed: MS Shell Dlg should be enumerated font.c:4192: Test failed: expected MS Shell Dlg, got Arial font.c:4205: Test failed: expected MS Shell Dlg, got Arial font.c:4181: Test failed: MS Shell Dlg should be enumerated font.c:4183: Test failed: MS Shell Dlg should be enumerated font.c:4192: Test failed: expected MS Shell Dlg, got Arial font.c:4205: Test failed: expected MS Shell Dlg, got Arial font.c:4181: Test failed: MS Shell Dlg should be enumerated font.c:4183: Test failed: MS Shell Dlg should be enumerated font.c:4192: Test failed: expected MS Shell Dlg, got Arial font.c:4205: Test failed: expected MS Shell Dlg, got Arial test_EnumFonts_subst() font.c:5507: Test failed: MS Shell Dlg should be enumerated font.c:5509: Test failed: MS Shell Dlg should be enumerated as a TrueType font font.c:5529: Test failed: MS Shell Dlg should be enumerated font.c:5530: Test failed: MS Shell Dlg should be enumerated See https://test.winehq.org/data/patterns.html#gdi32:font This happens on both the TestBot's Debian11 and Testing VMs. -- 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 1

[Bug 55339] New: d3d9:visual - add_dirty_rect_test() fails on w11pro64_nv
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55339 Bug ID: 55339 Summary: d3d9:visual - add_dirty_rect_test() fails on w11pro64_nv Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - add_dirty_rect_test() fails on w11pro64_nv: visual.c:19792: Test failed: Got unexpected color 0x00adbeef. See https://test.winehq.org/data/patterns.html#d3d9:visual This failure goes back to at least 2022-11-23, is systematic and specific to w11pro64_nv, the TestBot's only NVidia test configuration. -- 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 55392] New: d3d9:visual - test_color_clamping() fails on w11pro64-amd
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55392 Bug ID: 55392 Summary: d3d9:visual - test_color_clamping() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - test_color_clamping() fails on w11pro64-amd: visual.c:24213: Test failed: Got unexpected color 0x00000000, case 1. See https://test.winehq.org/data/patterns.html#d3d9:visual This failure is systematic and only happens on w11pro64-amd (AMD RX 6600). In particular it does not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor does it happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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 1

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