May 2023 - Wine-Bugs - list.winehq.org

[Bug 54025] New: Quixel Mixer 2022.1.0 Beta installer cannot find the specified path
by WineHQ Bugzilla Jan. 3, 2025

Jan. 3, 2025

https://bugs.winehq.org/show_bug.cgi?id=54025 Bug ID: 54025 Summary: Quixel Mixer 2022.1.0 Beta installer cannot find the specified path Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: igor.hope(a)noostyche.ru Distribution: --- Created attachment 73591 --> https://bugs.winehq.org/attachment.cgi?id=73591 Output as the program runs. Distro: Ubuntu 20.04 x64 Kernel: Linux 6.0.8 CPU: Ryzen 7 1700 GPU: Radeon RX 580 8 Gb Driver: Mesa 22.2.4 (Kisak PPA) Steps to reproduce: - Running the installation file. - In the installation dialog, after confirming the selection of the directory to install, an error is displayed: "The path you entered is invalid". Changing the path to different directories does not solve the problem. - The program cannot be installed. Download link: https://quixel.com/products/mixer -- 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 17

[Bug 17930] New: Cygwin compilation breaks without --disable-16bit
by wine-bugs＠winehq.org Dec. 31, 2024

Dec. 31, 2024

http://bugs.winehq.org/show_bug.cgi?id=17930 Summary: Cygwin compilation breaks without --disable-16bit Product: Wine Version: 1.1.17 Platform: PC OS/Version: Windows XP Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: gdi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dgerard(a)gmail.com http://wiki.winehq.org/WineOnWindows Cygwin compilation previously broke at internettransport.c (bug 16833). However, it now breaks in dispdib.dll16.spec: ccache gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2 -o dispdib.o dispdib.c ../../tools/winebuild/winebuild -w --def -o dispdib.dll16.def --export ./dispdib.dll16.spec ./dispdib.dll16.spec:1: 'pascal' not supported for Win32 make[2]: *** [dispdib.dll16.def] Error 1 make[2]: Leaving directory `/cygdrive/d/wine-git/dlls/dispdib.dll16' make[1]: *** [dispdib.dll16] Error 2 make[1]: Leaving directory `/cygdrive/d/wine-git/dlls' make: *** [dlls] Error 2 Regression testing shows the commit in question as: [86f54f4c8900db155ad9b11fabf644e0c1b644f9] gdi32: Make dispdib.dll into a stand-alone 16-bit module. Later builds break similarly in compobj.dll16.spec: ./compobj.dll16.spec:215: Type 'segptr' not supported for Win32 ./compobj.dll16.spec:216: Type 'segptr' not supported for Win32 ./compobj.dll16.spec:217: Type 'segptr' not supported for Win32 make[2]: *** [compobj.dll16.def] Error 1 make[2]: Leaving directory `/cygdrive/d/cygwine/wine-1.1.17/dlls/compobj.dll16' make[1]: *** [compobj.dll16] Error 2 make[1]: Leaving directory `/cygdrive/d/cygwine/wine-1.1.17/dlls' make: *** [dlls] Error 2 -- 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 4

[Bug 22384] New: DbgHelp doesn't support DWARF-2 on Mac OS X
by wine-bugs＠winehq.org Dec. 30, 2024

Dec. 30, 2024

http://bugs.winehq.org/show_bug.cgi?id=22384 Summary: DbgHelp doesn't support DWARF-2 on Mac OS X Product: Wine Version: 1.1.42 Platform: x86 OS/Version: Mac OS X 10.6 Status: UNCONFIRMED Severity: minor Priority: P2 Component: dbghelp AssignedTo: wine-bugs(a)winehq.org ReportedBy: cdavis(a)mines.edu Mac OS X has long had support for DWARF-2. Unfortunately, the current implementation of DWARF-2 support in DbgHelp is tied to ELF. This means it can't directly be used on Mac OS X, because Mac OS X does not support ELF. I understand that getting things to work on Linux first takes priority over getting them to work on Mac OS, but right now we Mac users are stuck with the inferior stabs format. Plus, I get the feeling we're going to need this for 64-bit support. Also, DWARF happens to be the default format on 10.5 and up. I also understand that the scheme that Apple uses is different from ELF systems. Not only does DWARF-2 stuff get its own segment (__DWARF), but when the binary is built, the DWARF stuff is put into a dSYM companion bundle. On top of that, the dSYM bundle isn't even generated automatically for multi-file builds. This means that: - We have to invoke dsymutil to create the dSYM bundle. - We have to install the dSYM bundle (if present) with each binary. - We have to find the dSYM bundle to get DWARF-2 debug info. I would be more than willing to help with this. (This might have even made a good SoC project. Too late now...) -- 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 10

[Bug 53000] New: Project64: black screen when gliden64 video plugin is used
by WineHQ Bugzilla Dec. 29, 2024

Dec. 29, 2024

https://bugs.winehq.org/show_bug.cgi?id=53000 Bug ID: 53000 Summary: Project64: black screen when gliden64 video plugin is used Product: Wine Version: 7.8 Hardware: x86-64 URL: https://www.pj64-emu.com/public-releases OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian In newer versions of Project64, GlideN64 is the default video plugin. When using this plugin, games only show a black screen. This is easy to reproduce with Project64 3.0.1. Install the application, and run it. On first start, it will ask if you want to use the GlideN64 or Project64 Video plugin. Choose GlideN64, then select a rom, and start. You may need to resume emulation (press f2), but you'll only see a black screen. If you remove 'C:\Program Files\Project64 3.0\Config\Project64.cfg', and rerun, then select 'Project64 Video', and start a game (and resume), video works. I tested Project64 on my windows partition, to make sure this hardware is capable of running gliden64. On windows, gliden64 works. Not much in the terminal: 0110:fixme:imm:ImeSetActiveContext (00711FA8, 1): stub 0110:fixme:imm:ImmReleaseContext (00030042, 00711FA8): stub 0120:fixme:imm:ImeSetActiveContext (00149A68, 0): stub 0120:fixme:imm:ImmReleaseContext (0002007A, 00149A68): stub 0134:fixme:ver:GetCurrentPackageId (033EFEF0 00000000): stub 0110:fixme:accel:NtUserDestroyAcceleratorTable other process handle 0x1 0154:fixme:ver:GetCurrentPackageId (08FDFEF0 00000000): stub wine-7.8 -- 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 48686] New: Soldier of Fortune Platinum Displays Strange Textures
by WineHQ Bugzilla Dec. 29, 2024

Dec. 29, 2024

https://bugs.winehq.org/show_bug.cgi?id=48686 Bug ID: 48686 Summary: Soldier of Fortune Platinum Displays Strange Textures Product: Wine Version: 5.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: publiclewdness(a)tutanota.com Distribution: --- Created attachment 66548 --> https://bugs.winehq.org/attachment.cgi?id=66548 Debugging Log The game will launch and play but several textures in the game are not correct. Character uniforms; cars; objects in game; etc. The strange colors they are change from playthrough to playthrough as well. I am using version 1.07f of the game from GOG. I have tried installing and running the game on a Windows 10 system and the texture issue isn't present there, it looks normal. I ran the SoF.exe file both through terminal and My system: AMD Ryzen 5 2600X | 16GB DDR4-3000 CL15 | MSI RX 580 8GB Gaming X | Mesa 19.3.4 | Manjaro 19.0.1 | Mate 1.24 | Kernel 5.5.6-1-MANJARO Windows System where it worked: AMD FX-9590 | 16GB DDR3-2133 | Radeon R9 270 2GB | Driver 20.1.3 | Windows 10 Pro 1909 -- 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 43836] New: Dev C++ - Program unable to debug the code
by wine-bugs＠winehq.org Dec. 29, 2024

Dec. 29, 2024

https://bugs.winehq.org/show_bug.cgi?id=43836 Bug ID: 43836 Summary: Dev C++ - Program unable to debug the code Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: amitpooniaamit10(a)gmail.com Distribution: --- While trying to run a program on Dev C++ program encounter errors while loading gdb.exe and unable to execute the program -- 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 29267] New: rtf text from wine's richedit shows up with a black background in LibreOffice Writer
by wine-bugs＠winehq.org Dec. 26, 2024

Dec. 26, 2024

http://bugs.winehq.org/show_bug.cgi?id=29267 Bug #: 29267 Summary: rtf text from wine's richedit shows up with a black background in LibreOffice Writer Product: Wine Version: 1.3.34 Platform: x86 OS/Version: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: richedit AssignedTo: wine-bugs(a)winehq.org ReportedBy: madewokherd(a)gmail.com Classification: Unclassified To reproduce: 1. Open Wine's wordpad and LibreOffice Writer. 2. Type some text in wordpad. 3. Copy text to the clipboard. 4. Paste into LibreOffice Writer. Or: 1. Open Wine's wordpad and LibreOffice Writer. 2. Type some text in wordpad. 3. Save from wordpad as a .rtf file. 4. Open the rtf file in LibreOffice Writer. In both cases, the text shows up with a black background in Writer. This does not happen with native riched20. When opening the rtf file with Word 2007, I do not see the black background, so this is somehow related to the interaction between Wine's richedit and LibreOffice, and I can't be sure which is at fault. -- 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 4

[Bug 20350] New: Lightsmark 2008 - benchmark label looks wrong
by wine-bugs＠winehq.org Dec. 26, 2024

Dec. 26, 2024

http://bugs.winehq.org/show_bug.cgi?id=20350 Summary: Lightsmark 2008 - benchmark label looks wrong Product: Wine Version: 1.1.31 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: richedit AssignedTo: wine-bugs(a)winehq.org ReportedBy: zilforever(a)gmail.com Created an attachment (id=24093) --> (http://bugs.winehq.org/attachment.cgi?id=24093) wine GUI looks different (element that display score). First it appear: wrong background (white not gray) and it looks like not editable input. In Windows XP SP 3 its not visble. After benchmark wrong size and color of font. I checked the source and it use richedit20 but im not good at it so maybe my mistake. Ubuntu 9.04 Intel(R) Pentium(R) Dual CPU E2220 @ 2.40GHz CPU flags: 2400MHz MMX SSE SSE2 SSE3 SSSE3 HTT Linux 32bit GCC 4.3.3 Release May 26 2009 Linux 2.6.28-15-generic i686 GeForce 9600 GT PCI Express 180.44 512Mb -- 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 12

[Bug 26302] New: outliner Keynote NF has a several problems
by wine-bugs＠winehq.org Dec. 26, 2024

Dec. 26, 2024

http://bugs.winehq.org/show_bug.cgi?id=26302 Summary: outliner Keynote NF has a several problems Product: Wine Version: 1.3.14 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: richedit AssignedTo: wine-bugs(a)winehq.org ReportedBy: wit9(a)yandex.ru Created an attachment (id=33527) --> (http://bugs.winehq.org/attachment.cgi?id=33527) listing of "fixmes" There is a popular outliner Keynote NF (Mozilla Public License 1.1) (http://code.google.com/p/keynote-nf/downloads/list) It's written in Delphi with using of some additional components, so author has no plans to port it to Linux. Using the Keynote NF with the Wine causes several problems, including 1. error when pasting from the clipboard 2. using lists and other In the terminal appear a lot of "fixme" (see attachment). -- 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 15

[Bug 54028] New: [cause crash - two problem] dwrite function "create_colorglyphenum" returns DWRITE_E_NOCOLOR and causing null pointer crash on 7.12 but not on 7.22
by WineHQ Bugzilla Dec. 26, 2024

Dec. 26, 2024

https://bugs.winehq.org/show_bug.cgi?id=54028 Bug ID: 54028 Summary: [cause crash - two problem] dwrite function "create_colorglyphenum" returns DWRITE_E_NOCOLOR and causing null pointer crash on 7.12 but not on 7.22 Product: Wine Version: 7.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: dwrite Assignee: wine-bugs(a)winehq.org Reporter: 399989567(a)qq.com Distribution: --- (This problem can be reproduced without any account) There are two problems here.I found out that the first problem existed in 7.12 and cause crash, but was fixed in 7.22 (doesn't exist).The second problem exists in 7.22 and cause crash, but not in 7.12. I found that the first problem has been fixed, so I would like to ask which commit was fixed it (because there are many commits, I think the developer of wine may know better and can give the answer at once,if You feel this bothered you, first of all I'm sorry) . The second issue renders the application completely unusable (QQ Music APP can worked in 7.12, but not in 7.22) -------- Question 1: Describe the crash below (note that the font file msyh.ttf needs to be added in the ./wine/fonts directory to trigger the crash) > Let me explain here why the font msyh.ttf is added to the ./wine/fonts directory instead of using the original wine > Because only after adding the font, QQ Music will call this function "create_colorglyphenum", which will cause a crash. If this font is not added, QQ Music will not call this function and use other logic. > Because I don't have the source code of QQ Music, I don't know the logic of calling the function, so it is necessary to add this font file. The font file is added to reproduce the crash, not to change the wine. Here's a description of how the crash happens: Background: In the QQ Music program, this APP want to use the font "Microsoft YaHei" to output the four characters "QQ音乐". The function to call is: dwritetextlayout_Draw -> QQMusic logic -> create_colorglyphenum -> crash The cause of the crash is that in the function "create_colorglyphenum", there is a judgment of "!colorfont". > if (!colorfont) > return DWRITE_E_NOCOLOR; The "Microsoft YaHei" is not colorfont, it will return DWRITE_E_NOCOLOR directly, thus triggering a null pointer crash. But I found that in the current wine7.22, the same return here but no longer triggers the crash, so I would like to ask which commit fixed this problem (the dichotomy method consumes a lot of time, so I want to ask if you know the commit first, if You feel this bothered you, first of all say sorry) In summary,All you have to do is to add the font file, run the exe file I sent with wine7.12 . QQ Music official website link: https://y.qq.com/ (I will attach the corresponding exe installation package in the next reply, the attached exe file is worried that you are inconvenient to download from the official website) crash information: > 01d8:trace:dwrite:dwritefontface2_IsColorFont 03159B38. > wine: Unhandled page fault on read access to 00000000 at address 511406CB (thread 01d8), starting debugger... -------- Question 2: Use the original wine 7.22 without any modification, after installing QQ Music, open the application, the application cannot be displayed (without any UI interface),which makes the entire application unusable, but 7.12 can be displayed UI and text normally. Figure 1 shows how 7.12 can be displayed normally, and Figure 2 shows how 7.22 cannot display 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 9