wine-bugs April 2022

wine-bugs@winehq.org

1 participants
3452 discussions

[Bug 43347] New: valgrind shows an unintialized read in dlls/iphlpapi/ tests/iphlpapi.c
by wine-bugs＠winehq.org 22 Jun '22

22 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=43347 Bug ID: 43347 Summary: valgrind shows an unintialized read in dlls/iphlpapi/tests/iphlpapi.c Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: iphlpapi Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Gentoo ../../../tools/runtest -q -P wine -T ../../.. -M iphlpapi.dll -p iphlpapi_test.exe.so iphlpapi && touch iphlpapi.ok ==10952== Syscall param ioctl(SIOCGIFINDEX) points to uninitialised byte(s) ==10952== at 0x4338F79: ioctl (syscall-template.S:84) ==10952== by 0x435916D: if_nametoindex (if_index.c:47) ==10952== by 0x4B25E43: getInterfaceIndexByName (ifenum.c:143) ==10952== by 0x4B2EC7E: IPHLP_if_nametoindex (iphlpapi_main.c:3233) ==10952== by 0x488198E: test_interface_identifier_conversion (iphlpapi.c:1958) ==10952== by 0x48831AB: func_iphlpapi (iphlpapi.c:2230) ==10952== by 0x4884014: run_test (test.h:603) ==10952== by 0x4884465: main (test.h:687) ==10952== Address 0x4b0f8c0 is on thread 1's stack ==10952== in frame #1, created by if_nametoindex (if_index.c:35) ==10952== Uninitialised value was created by a stack allocation ==10952== at 0x4359141: if_nametoindex (if_index.c:41) ==10952== -- 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 1

[Bug 44337] New: d3d9/tests/device.ok fails on Nvidia (Nouveau drivers) in test_occlusion_query()
by wine-bugs＠winehq.org 21 Jun '22

21 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=44337 Bug ID: 44337 Summary: d3d9/tests/device.ok fails on Nvidia (Nouveau drivers) in test_occlusion_query() Product: Wine Version: 3.0-rc5 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- with the following lines: device.c:5915: Test failed: Got unexpected hr 0x1. device.c:5919: Test failed: Got unexpected hr 0x1. device.c:5920: Test failed: Got unexpected query result 0xffffffffffffffff. It would be nice to fix this as this is currently the only D3D test failure on the cw2 test machine. -- 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 48820] New: user32:win "unexpected 0x7fff message" Japanese Windows 10 failures
by WineHQ Bugzilla 21 Jun '22

21 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=48820 Bug ID: 48820 Summary: user32:win "unexpected 0x7fff message" Japanese Windows 10 failures Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: major Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The TestBot's w1064v1809-zh_CN configuration runs the tests on Windows 10 1809 in a Chinese locale. This test configuration gets unique failures in user32:win: win.c:3852: Test failed: hwnd 007404D2 message 7fff win.c:3858: Test failed: message 7fff available win.c:3931: Test failed: hwnd 007404D2/0054050A message 7fff win.c:3934: Test failed: hwnd 007404D2/0054050A message 7fff Note how these messages are very similar to the IME messages in bug 48819. However 0x7fff is a totally unknown message: all I can say about it is that it's WM_APP-1. So maybe it's another IME system. Maybe not? See: https://test.winehq.org/data/tests/user32:win.html However note that quite often WineTest fails to submit its results to test.winehq.org, typically because it times out. So you can more easily find the latest failure by looking for the "32 bit WineTest: base VMs" jobs on the TestBot. Finally, three of these messages include the window handles which means they are "always new". Because of this the TestBot will mistakenly attribute the failure to any user32 patch submitted to wine-devel, which should cause them to be rejected. So I bumped the priority on this bug. -- 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 35765] New: gdi32:font / richedit:editor / msvcrt:locale / msvcrt:string fails on newtb-w7u
by wine-bugs＠winehq.org 21 Jun '22

21 Jun '22

http://bugs.winehq.org/show_bug.cgi?id=35765 Bug ID: 35765 Summary: gdi32:font / richedit:editor / msvcrt:locale / msvcrt:string fails on newtb-w7u Product: Wine Version: 1.7.14 Hardware: x86 OS: Linux Status: NEW Keywords: source, testcase Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fracting(a)gmail.com CC: fgouget(a)codeweavers.com http://test.winehq.org/data/770213e16c6918728f69ea33545fafabd59dbc8e/win7_n… It seems these tests are all related to locales, and they fail much more on this machine than other machine. SystemDefaultLCID 411 UserDefaultLCID 409 ThreadLocale 411 UserDefaultUILanguage 411 ThreadUILanguage 411 It doesn't happen frequently that we have a vm with different UserDefaultLCID and SystemDefaultLCID. I'm not very sure if we want to support such a case, it maybe useful in real world for some body. (I personally don't care too much lol) François, is there any chance to try: 1. set all LCIDs to 0x409 (Simplified Chinese) 2. set all LCIDs to 0x411 (Japanese) Then reboot the vm, then resubmit the tests, to see if there is any improvement? Thanks for your great work! Everyone wants your patch/work :) -- 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 23

[Bug 32083] New: Diablo III: Missing logo on startup
by wine-bugs＠winehq.org 20 Jun '22

20 Jun '22

http://bugs.winehq.org/show_bug.cgi?id=32083 Bug #: 32083 Summary: Diablo III: Missing logo on startup Product: Wine Version: 1.5.16 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sworddragon2(a)aol.com Classification: Unclassified On starting Diablo III the logo before the game starts is transparent. If I'm going with the mouse over it the cursor will be hidden. -- 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 34

[Bug 35213] New: Kane & Lynch: Dead Men demo needs native d3dx9_31
by wine-bugs＠winehq.org 20 Jun '22

20 Jun '22

http://bugs.winehq.org/show_bug.cgi?id=35213 Bug ID: 35213 Summary: Kane & Lynch: Dead Men demo needs native d3dx9_31 Product: Wine Version: 1.7.9 Hardware: x86 URL: http://www.gamefront.com/files/9394790/Kane___Lynch__D ead_Men_Demo OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: wine-bugs(a)winehq.org Classification: Unclassified First d3dx9_36 should be installed. Demo crashes with fixme:d3dx:D3DXCreateEffectEx (0x20f000, 0x1e71cb58, 45008, (nil), (nil), (nil), 0x10900, 0x1685a8, 0x1a99cf4, 0x1a99cec): semi-stub after the same issue as for bug 35137, but this time should be d3dx9_31. -- 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 15

[Bug 51158] New: advapi32:lsa fails in French on Windows 2004
by WineHQ Bugzilla 20 Jun '22

20 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=51158 Bug ID: 51158 Summary: advapi32:lsa fails in French on Windows 2004 Product: Wine Version: 6.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- advapi32:lsa fails in French on Windows 2004 because the name of the 'Everyone' group does not seem to be translated anymore: lsa.c:407: Test failed: expected L"Tout le monde", got L"Everyone" That's a bit surprising. Maybe the Windows translation was slightly out of date? * This should be checked on Windows 2009 but we don't have a test configuration for it. * The test also has a translation for German but we don't have a test configuration for German. There should really be one so we can validate the test. Once the results for German and Windows 2009 are known the test can be updated. -- 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 48108] New: kernel32:comm - QEmu's serial baud rate emulation is broken
by WineHQ Bugzilla 20 Jun '22

20 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=48108 Bug ID: 48108 Summary: kernel32:comm - QEmu's serial baud rate emulation is broken Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- kernel32:comm got a failure when running on Wine on the TestBot VM: comm.c:932: Test failed: OutQueue should not be empty This happens in test_waittxempty(): // Open the serial device hcom = test_OpenComm(TRUE); // Here it is already set to 150 bps because that's how a // previous test left it ... // Write 17 bytes in overlaped mode. // At 150 bauds this should take at least 900 ms res = WriteFile(hcom, tbuf, sizeof(tbuf), &bytes, &ovl_write); // Leaving us plenty of time to get to ClearCommError(hcom, &errors, &stat); ... // And here we expect the serial device to still have data to send. // But because QEmu sends the data at > 400 kbps this often fails ok(stat.cbOutQue != 0, "OutQueue should not be empty\n"); That QEmu does not enforce the set baud rate can also be verified from the command line: # stty -F /dev/ttyS0 speed 9600 baud; line = 0; -brkint -imaxbel # dd if=/dev/zero of=/dev/ttyS0 bs=1 count=10000 10000+0 records in 10000+0 records out 10000 bytes (10 kB, 9.8 KiB) copied, 0.224432 s, 44.6 kB/s # stty -F /dev/ttyS0 300 # stty -F /dev/ttyS0 speed 300 baud; line = 0; -brkint -imaxbel # dd if=/dev/zero of=/dev/ttyS0 bs=1 count=10000 10000+0 records in 10000+0 records out 10000 bytes (10 kB, 9.8 KiB) copied, 0.679127 s, 14.7 kB/s Back to the kernel32:comm failure: * It did not happen for a long time and started happening on the debian10 VM on 2019-10-03. That corresponds to the time I added the winetest user to the dialout group, thus giving it access to /dev/ttyS0. * The same issue happens in the Windows VMs, but the ok() call has a broken() clause which hides the issue there. So: 1. The bug needs to be reported to QEmu. 2. See why speeds below 9600 bps are not allowed. 3. We may want a better check for this issue: directly check that the baud rate is respected. This would allow us to skip tests that depend on the baud rate and ditch the broken() clause. 4. If the above does not work out the serial device should be removed from the Wine QEmu 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 3

[Bug 52804] New: Crash when save settings in KaiNote
by WineHQ Bugzilla 20 Jun '22

20 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=52804 Bug ID: 52804 Summary: Crash when save settings in KaiNote 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: matiasmoviegg(a)gmail.com Distribution: --- Created attachment 72181 --> https://bugs.winehq.org/attachment.cgi?id=72181 backtrace Problem with KaiNote Link for stable https://github.com/bjakja/Kainote/releases Link for Beta (log from this version) https://drive.google.com/uc?id=1ECqsrLo5d1jPoz-FKvJrS0279YeTKrmS&export=dow… Go to File->Settings Click OK Click on random place in program Program Crash Testing on virtual machine with Xubuntu 21.10 (adding "LIBGL_ALWAYS_SOFTWARE=1") and Laptop (i5-2520m) with Linux Mint 20.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 2

[Bug 37557] New: SketchUp 2015 doesn't start
by wine-bugs＠winehq.org 18 Jun '22

18 Jun '22

https://bugs.winehq.org/show_bug.cgi?id=37557 Bug ID: 37557 Summary: SketchUp 2015 doesn't start Product: Wine Version: 1.7.30 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: richedit Assignee: wine-bugs(a)winehq.org Reporter: gilson.oliveira.junior(a)gmail.com Distribution: --- Hi All, I've installed the last version of SketchUp in Wine 1.7.30 in my Ubuntu and when I double click the application, the mouse changes the cursor to "working" and then it's set again as normal cursor and Nothing Happens. Via command I get the message below: wine "C:\Program Files (x86)\SketchUp\SketchUp 2015\SketchUp.exe" err:module:import_dll Library mfc100u.dll (which is needed by L"C:\\Program Files (x86)\\SketchUp\\SketchUp 2015\\SketchUp.exe") not found err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files (x86)\\SketchUp\\SketchUp 2015\\SketchUp.exe" failed, status c0000135 Does anybody knows what I can do? I'm a beginner user of Wine and Ubuntu. Thanks in advanced for your help. Regards, Gilson -- 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

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 April 2022