wine-bugs September 2022

wine-bugs@winehq.org

1 participants
3517 discussions

[Bug 49936] New: modal dialog box behaves modeless
by WineHQ Bugzilla 13 Jan '24

13 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=49936 Bug ID: 49936 Summary: modal dialog box behaves modeless Product: Wine Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ch.panel(a)free.fr Distribution: --- Creating a modal dialog box in an MDI environment : when this one has for parent an MDI Child window, this behaves like a modeless window (bug because MDI child was expecting an answer) when this one has for parent the Application Frame window (parent of parent... of MDI Child window), this behaves correctly (modal). It's like wine doesn't manage MDI model 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 52966] New: user32:combo - test_listbox_size() fails in Wine in the Japanese locale
by WineHQ Bugzilla 13 Jan '24

13 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=52966 Bug ID: 52966 Summary: user32:combo - test_listbox_size() fails in Wine in the Japanese locale 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:combo - test_listbox_size() fails in Wine in the Japanese locale: combo.c:798: Test marked todo: Test 1, expected list height to be 0, got 14 combo.c:798: Test failed: Test 2, expected list height to be 0, got 15 combo.c:798: Test failed: Test 11, expected list height to be 0, got 15 combo.c:798: Test succeeded inside todo block: Test 15, expected list height to be 54, got 54 https://test.winehq.org/data/patterns.html#user32:combo This is readily reproducible with: (just make sure to have the required locale in locale -a) LANG=ja_JP.UTF-8 ./wine dlls/user32/tests/user32_test.exe combo -- 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 52491] New: SpaceDesk: Error when trying to connect to the server now but it worked in 6.10 and below
by WineHQ Bugzilla 12 Jan '24

12 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=52491 Bug ID: 52491 Summary: SpaceDesk: Error when trying to connect to the server now but it worked in 6.10 and below 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: jota0222(a)hotmail.com Distribution: --- Created attachment 71785 --> https://bugs.winehq.org/attachment.cgi?id=71785 Log Of SpaceDesk Runinng After the release of stable 7.0.0, I noticed that SpaceDesk stoped working and then I tried some older versions versions, none of the listed to register the apps in the WineHQ page worked (6.21 and above), however it worked in all the ones below 6.10. I didn't try with the ones in between, so I don't really know when the bug was introduced exactly. The app doesn't throw exceptions or show error in logs, the log attached is basically the same in both 6.10 and 7.0.0 versions. I also tried with winedbg but if I dissable $BreakOnFirstChance it never stops on any exception and the log finish up being the same as the one attached (at least doesn't looks like it's showing things related to the issue). And if I run it with $BreakOnFirstChance set as 1, it's impossible to reach the moment of in which the error occurs due to al the exceptions in which it stops before to even show the window. This image shows the error: https://paste.pics/FTUXV -- 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 38780] New: AArch64 platforms: register X18 must remain reserved for Wine to run 64-bit ARM Windows applications (Distro aarch64 toolchains need '-ffixed-x18' default, loader/libc/userland)
by wine-bugs＠winehq.org 12 Jan '24

12 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=38780 Bug ID: 38780 Summary: AArch64 platforms: register X18 must remain reserved for Wine to run 64-bit ARM Windows applications (Distro aarch64 toolchains need '-ffixed-x18' default, loader/libc/userland) Product: Wine Version: 1.7.45 Hardware: aarch64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, split off from bug 38719 ("64-bit ARM Windows applications from Windows SDK for Windows 10 crash when accessing TEB/PEB members (AArch64 platform specific register X18 must be reserved for TEB)") Resolution is 'upstream' here, the Wine part is bug 38719 http://infocenter.arm.com/help/topic/com.arm.doc.ihi0055b/IHI0055B_aapcs64.… Chapter 5 "THE BASE PROCEDURE CALL STANDARD" --- quote --- The role of register r18 is platform specific. If a platform ABI has need of a dedicated general purpose register to carry interprocedural state (for example, the thread context) then it should use this register for that purpose. If the platform ABI has no such requirements, then it should use r18 as an additional temporary register. The platform ABI specification must document the usage for this register. Note Software developers creating platform independent code are advised to avoid using r18 if at all possible. Most compilers provide a mechanism to prevent specific registers from being used for general allocation; portable hand-coded assembler should avoid it entirely. It should not be assumed that treating the register as callee saved will be sufficient to satisfy the requirements of the platform. Virtualization code must, of course, treat the register as they would any other resource provided to the virtual machine. --- quote --- Regards -- 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 37

[Bug 47406] New: add support for debug symbols is separate files
by wine-bugs＠winehq.org 12 Jan '24

12 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=47406 Bug ID: 47406 Summary: add support for debug symbols is separate files Product: Wine Version: 4.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- <will be a bit ranty> One on the "installation options" on Gentoo is 'splitdebug'. It allows to keep debug symbols in separate files (and potentially keep them compressed). gdb supports it (AFAICT) seamlessly. While addr2line doesn't seem to supports it, the one from elfutils does. I don't know where Gentoo got the idea, but given gdb and elfutils, it's likely more wide-spread than Gentoo family. So, would you consider adding support for it in winedbg ? -- 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 46777] New: Two Worlds 2 crashing on start [REGRESSION]
by wine-bugs＠winehq.org 12 Jan '24

12 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=46777 Bug ID: 46777 Summary: Two Worlds 2 crashing on start [REGRESSION] Product: Wine Version: 4.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: timofeevsv1989(a)gmail.com Distribution: --- Created attachment 63791 --> https://bugs.winehq.org/attachment.cgi?id=63791 Two Worlds 2 crash. Console out. Two Worlds 2 crashing on start. In older wine (4.0) on load screen. On old wine 1.1.39 everything was OK -- 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 10

[Bug 53319] New: robot battle game extremely slow after wine version 7.11 and above
by WineHQ Bugzilla 12 Jan '24

12 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=53319 Bug ID: 53319 Summary: robot battle game extremely slow after wine version 7.11 and above Product: Wine Version: 7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: evren320(a)hotmail.com Distribution: --- Robot Battle 1.4 game is slow on wine version 7.11 and above. Game works fine with wine 7.10 and below. -- 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 52962] New: dinput:force_feedback breaks ntoskrnl.exe:ntoskrnl on Windows 7
by WineHQ Bugzilla 12 Jan '24

12 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=52962 Bug ID: 52962 Summary: dinput:force_feedback breaks ntoskrnl.exe:ntoskrnl on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinput:force_feedback breaks ntoskrnl.exe:ntoskrnl on Windows 7: ntoskrnl.c:1837: Test failed: Failed to uninstall INF, error 3758096957 https://test.winehq.org/data/patterns.html#ntoskrnl.exe:ntoskrnl This can be tested by running the following on wtbw7u: Program: winetest.exe Arguments: -c -o - -t foo dinput:force_feedback ntoskrnl.exe:ntoskrnl A bisect shows that this failure started with the commit below: commit 2644f6361759caa3631c6ce85a912a1654093da0 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Tue Mar 22 11:41:40 2022 +0100 dinput/tests: Create all HID devices from the Bus driver. Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> (On the plus side a different set of 12 failures got fixed at about the same time, maybe by the same commit.) -- 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 50998] New: Failed to open error Word 2007 (c0000135)
by WineHQ Bugzilla 12 Jan '24

12 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=50998 Bug ID: 50998 Summary: Failed to open error Word 2007 (c0000135) Product: Wine-staging Version: 6.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pierce.adam.randall(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Since 6.5, I'm not able to open Word 2007. I get the following errors when I try to open it in terminal: wine: failed to open "[path redacted]/drive_c/Program Files/Microsoft Office/Office12/WINWORD.exe": c0000135 0094:err:rpc:I_RpcReceive we got fault packet with status 0x1c010003 Not much other than that. I'm using Arch Linux. Kernel 5.11.13. The program works on 6.4, but not 6.5 or 6.6. I also ran into this bug using non-staging version of 6.5. -- 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 49852] New: Performance regression in "msvcrt: Use correct code page in _write when outputing to console."
by WineHQ Bugzilla 12 Jan '24

12 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=49852 Bug ID: 49852 Summary: Performance regression in "msvcrt: Use correct code page in _write when outputing to console." Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: martin(a)martin.st Distribution: --- Created attachment 68190 --> https://bugs.winehq.org/attachment.cgi?id=68190 Test sample Since 081d25d4b989c732d301b786311c034132c8d7a3, "msvcrt: Use correct code page in _write when outputing to console.", a test app (that prints a lot to stdout) had an around 10-20x slowdown. Before, "time wine64 ihateeh-x86_64.exe > /dev/null 2>&1" ran in around 1 second, after that commit it takes 15 seconds. (At some later point, it has regressed further to 25 seconds. The corresponding testcase on aarch64 used to run in 3 seconds, after the commit it takes 60, and with current master takes around 120 seconds.) -- 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

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