wine-bugs

wine-bugs@winehq.org

1 participants
158978 discussions

[Bug 55753] New: Fonts on dialog/modal windows are not aliased
by WineHQ Bugzilla 09 Oct '23

09 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55753 Bug ID: 55753 Summary: Fonts on dialog/modal windows are not aliased Product: Wine Version: 8.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: fonts Assignee: wine-bugs(a)winehq.org Reporter: jimmyg521(a)gmail.com Distribution: --- Created attachment 75248 --> https://bugs.winehq.org/attachment.cgi?id=75248 Screenshot of application mp3tag with open dialog box showing unalised fonts I'm on a brand new install of MXLinux v23/Debian Bookworm with the latest stable/dev wine using the Debian Bookworm PPA from WineHQ (now after significant trouble-shooting). **Previous install of MXLinux v21 with it's version of wine-staging did not exhibit this behavior.** Current system/wine information: √ ~ > uname -a Linux HOLLIN 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-2 (2023-07-27) x86_64 GNU/Linux HOLLIN [uname -a] ~ 23-10-08 4:17PM √ ~ > wine --version wine-8.17 MX-Linux System Report: KDE Plasma 5.27.5; Debian 12.2 CPU: 8-Core Intel Core i7-10700 (-MT MCP-) speed/min/max: 990/800/4800 MHz Kernel: 6.1.0-10-amd64 x86_64 Up: 8d 9h 1m Mem: 6843.1/15775.5 MiB (43.4%) Storage: 19.11 TiB (41.5% used) Procs: 476 Client: Unknown Client: mx-welcome inxi: 3.3.06 ==== Problem is not about an application installing or running, it's about the dialog windows that both Wine itself and applications display. For example, I can run the notepad app from a terminal in any wine prefix (default 64-bit or a new 32-bit)and its fonts on menubar and menus look fine. But if, for example, I select from the menubar File > Open, the fonts on the Open dialog window are not aliased. The dialog itself is fully functional, its only the fonts that are unaliased. WineCfg it turns out is a dialog (modal?) window and it opens with unaliased fonts. No change to any of the fonts listed on the WineCfg Desktop Integration Appearance Theme modify this font behavior. I have: 1. Completely uninstalled the MXLinux v23 default wine (using mc to track down every folder and file to delete them); reinstalled from the MXLinux repos - no change 2. Completely uninstalled again and reinstalled using flatpak version from org.winehq.Wine - no change 3. Completely uninstalled again, added the Debian Bookwork PPAs to install from WineHq - no change 4. Installed from the WineHQ PPA Wine-Dev - no change 5. Googled ad nauseam various combinations of words trying to limit search results to this specific issue, but it's a bit hopeless; most everyone is looking for ways to install fonts or make fonts larger, but that all works fine for me; in fact, on the Winecfg tab for Appearance, the slider is at 144 dpi and the font displayed below the slider is, of course, correctly aliased; just not any of the rest of the fonts used on the Winecfg dialog window or any other dialog window 6. I have made sure that any tahoma, etc. font in my Linux system that might cause some kind of font conflict was deleted and reinstalled using winetricks and rebooted my system - no change 7. I have removed nearly every font from my user /.fonts/ folder and restarted - no change 8. I have used winetricks to set the fontsmooting registry keys - no change 9. I have used winetricks to install most of the avialable fonts - no change 10. I have created test 32-bit and 64-bit prefixes using winetricks and Q4wine - no change; dialog/modal dialog fonts remain unaliases 10. I have added specific values to my local linux install's user .fonts.conf file to force Linux system aliasing and hinting hoping, based on a blog post, this might spill over into wine, and restarted - no change Again - this is not about funcationality - it all works, it's only about the font display of dialog windows; primary windows of apps and Wine system apps (regedit, notepad, control, taskmgr) all load and display fonts as expected until I use File | Open, File | Print, etc. (see attached screen of application mp3tag running in a 32-bit prefix). Why is this a problem? On an HDPI monitor, pencil thin unaliased fonts are very difficult to read. It is a real usability issue. Here is an image of what I'm talking about - the application mp3tag (which I've been using for several years in wine on both Kubutu and MXLinx v21) with the File | Options dialog enabled. If you increase view to 200%, you can clearly see that the font of the dialog is not aliased while the menu font and other fonts in the app UI are. -- 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 55757] New: The 32-bit kernel32:debugger gets a debugger inactive failure in the new WoW mode on macOS
by WineHQ Bugzilla 08 Oct '23

08 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55757 Bug ID: 55757 Summary: The 32-bit kernel32:debugger gets a debugger inactive failure in the new WoW mode on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The 32-bit kernel32:debugger gets a debugger inactive failure in the new WoW mode on macOS: debugger.c:205: child: crashing... Unhandled exception: page fault on write access to 0x00000000 in segmented 32-bit code (0107:0044d143). Assertion failed: curr_mode == stm_32bit, file ../wine/dlls/dbghelp/cpu_i386.c, line 278 debugger.c:735: Test failed: exit code = c0000354 See https://test.winehq.org/data/patterns.html#kernel32:debugger Where c0000354 == STATUS_DEBUGGER_INACTIVE The failures are systematic but only happen when running the 32-bit test in a Windows-on-Windows wineprefix on macOS. Looking at the pattern one may also think they started on 2023-10-02 but in fact that's just because before that date the WineTest report had so many other errors that test.winehq.org rejected the report. In fact the test was already failing all the way back to at least 2023-09-07 (there is no earlier data). -- 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 55756] New: The 32-bit ntdll:wow64 crashes in the new WoW mode on macOS
by WineHQ Bugzilla 08 Oct '23

08 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55756 Bug ID: 55756 Summary: The 32-bit ntdll:wow64 crashes in the new WoW mode on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The 32-bit ntdll:wow64 crashes in the new WoW mode on macOS: [... skip failures from bug 55752, bug 55754 and bug 55755...] wow64.c:1773: got init block 000000f0 Unhandled exception: page fault on read access to 0xffffffff in segmented 32-bit code (0107:00dd000e). Assertion failed: curr_mode == stm_32bit, file ../wine/dlls/dbghelp/cpu_i386.c, line 278 ntdll:wow64:0e24 done (-1073740972) in 2s 665B See https://test.winehq.org/data/patterns.html#ntdll:wow64 The failures are systematic but only happen when running the 32-bit test in a Windows-on-Windows wineprefix on macOS. Looking at the pattern one may also think they started on 2023-10-02 but in fact that's just because before that date the WineTest report had so many other errors that test.winehq.org rejected the report. In fact the test was already failing all the way back to at least 2023-09-07 (there is no earlier data). -- 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 55754] New: ntdll:wow64 - The 32-bit test_modules() fails in Wine's new WoW mode
by WineHQ Bugzilla 08 Oct '23

08 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55754 Bug ID: 55754 Summary: ntdll:wow64 - The 32-bit test_modules() fails in Wine's new WoW mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ntdll:wow64 - The 32-bit test_modules() fails in Wine's new WoW mode: wow64.c:1558: Test failed: unknown module 6ffffdce0000 L"win32u.dll" found See https://test.winehq.org/data/patterns.html#ntdll:wow64 In particular one can see this issue on fg-deb64-i386, fgtb-debian11-i386, fgtb-debian12-i386 and rbernon-*-wow64 which all run the 32-bit tests in the new Windows-on-Windows Wine mode. This failure does no happen in the 64-bit test, or when running in a pure 32-bit environment or in the old Windows-on-Windows mode. -- 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 47510] New: Roblox Player or Studio doesnt work on Linux
by wine-bugs＠winehq.org 08 Oct '23

08 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=47510 Bug ID: 47510 Summary: Roblox Player or Studio doesnt work on Linux Product: WineHQ Apps Database Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: adrianpluta4(a)gmail.com Distribution: --- Created attachment 64898 --> https://bugs.winehq.org/attachment.cgi?id=64898 Crash during Installaion of Roblox Roblox Player or Studio doesnt work on Linux Can i run this native??? -- 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 55737] New: black screen on new mini games (free available) eg. Inkobot by soerbgames
by WineHQ Bugzilla 08 Oct '23

08 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55737 Bug ID: 55737 Summary: black screen on new mini games (free available) eg. Inkobot by soerbgames Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: elias_0000_0000(a)yahoo.com Distribution: --- black screen on new mini windows games (free available) eg. Inkobot by soerbgames black screen on new mini games (free available) eg. Inkobot by soerbgames its the second iogame that make this problem. I dont know if programers' fault or wine. wine --version wine-8.0 (Debian 8.0~repack-4) Debian GNU/Linux 12 (bookworm) -- 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 55751] New: wbemprox:query crashes on macOS
by WineHQ Bugzilla 08 Oct '23

08 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55751 Bug ID: 55751 Summary: wbemprox:query crashes on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wbemprox:query crashes on macOS: query.c:1347: Test failed: got 0x80041001 Couldn't get first exception for process 0230 C:\users\runner\Temp\wct\wbemprox_test.exe. No backtrace available [...] wbemprox:query:0230 done (-1073741819) in 7s 10853B See https://test.winehq.org/data/patterns.html#wbemprox:query Where 0x80041001 == WBEM_E_FAILED -1073741819 == STATUS_ACCESS_VIOLATION This crash first happened on 2023-10-06 and only happen on macOS (see Remi's rbernon-macos-* cloud test machines) but in both 32-bit and 64-bit tests. -- 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 55750] New: The 32-bit kernel32:virtual fails on macOS + WoW
by WineHQ Bugzilla 08 Oct '23

08 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55750 Bug ID: 55750 Summary: The 32-bit kernel32:virtual fails on macOS + WoW Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The 32-bit kernel32:virtual fails on macOS + WoW: virtual.c:2292: Test failed: VirtualLock unexpectedly succeeded virtual.c:2294: Test marked todo: wrong error 3735928559 virtual.c:2298: Test succeeded inside todo block: VirtualLock failed 3735928559 [...] virtual.c:2237: exception: 80000001 flags:0 addr:00560BB1 virtual.c:2330: Test failed: memory block contains wrong value, expected 0x101, got 0x1 [...] virtual.c:2237: exception: 80000001 flags:0 addr:005612B5 virtual.c:2444: Test failed: VirtualLock unexpectedly succeeded virtual.c:2446: Test marked todo: wrong error 3735928559 virtual.c:2455: Test succeeded inside todo block: VirtualLock failed 3735928559 [...] virtual.c:2483: exception: c0000005 flags:0 addr:01150000 info[0]:8 info[1]:01150000 virtual.c:2775: Test failed: expected no STATUS_ACCESS_VIOLATION exception, got 1 exceptions [...] See https://test.winehq.org/data/patterns.html#kernel32:virtual The failures are systematic but only happen when running the 32-bit test in a Windows-on-Windows wineprefix on macOS. Looking at the pattern one may also think they started on 2023-10-02 but in fact that's just because before that date the WineTest report had so many other errors that test.winehq.org rejected the report. In fact kernel32:virtual was already failing all the way back to at least 2023-09-07 (there is no earlier data). -- 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 55749] New: comctl32:button - The 64-bit test_button_messages() sometimes fails on macOS
by WineHQ Bugzilla 08 Oct '23

08 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55749 Bug ID: 55749 Summary: comctl32:button - The 64-bit test_button_messages() sometimes fails on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:button - The 64-bit test_button_messages() sometimes fails on macOS: button.c:807: Test failed: SetFocus(hwnd) on a button: the msg 0x0281 should NOT have been sent by DefWindowProc button.c:807: Test failed: SetFocus(hwnd) on a button: the msg 0x0281 was expected in child button.c:807: Test failed: SetFocus(hwnd) on a button: the msg 0x0007 should NOT have been sent by DefWindowProc button.c:807: Test failed: SetFocus(hwnd) on a button: the msg 0x0007 was expected in child button.c:807: Test failed: SetFocus(hwnd) on a button: the msg 0x0111 was expected, but got msg 0x0008 instead button.c:807: Test failed: SetFocus(hwnd) on a button: the msg 0x8000 was expected, but got msg 0x0281 instead button.c:807: Test failed: SetFocus(hwnd) on a button: the msg 0x000f was expected, but got msg 0x0281 instead button.c:807: Test failed: SetFocus(hwnd) on a button: the msg sequence is not complete: expected 0000 - actual 0007 See https://test.winehq.org/data/patterns.html#comctl32:button These failures are specific to the *-win64 test configurations which corresponds to the 64-bit tests. The *-wow64 (32-bit) tests have no failure. The failure rate is about 11%. -- 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 55748] New: The 32-bit atl:atl_ax times out in WoW mode on macOS
by WineHQ Bugzilla 08 Oct '23

08 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55748 Bug ID: 55748 Summary: The 32-bit atl:atl_ax times out in WoW mode on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: atl Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The 32-bit atl:atl_ax times out in WoW mode on macOS: atl:atl_ax start dlls/atl/tests/atl_ax.c atl:atl_ax:0810 done (258) in 120s 0B See https://test.winehq.org/data/patterns.html#atl:atl_ax The failures are systematic but only happen when running the 32-bit test in a Windows-on-Windows wineprefix on macOS. Looking at the pattern one may also think they started on 2023-10-02 but in fact that's just because before that date the WineTest report had so many other errors that test.winehq.org rejected the report. In fact atl:atl_ax was already failing all the way back to at least 2023-09-08 (there is no earlier data). -- 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