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

[Bug 48877] New: [regression] Melodyne crashes when using the Pitch tool
by WineHQ Bugzilla Jan. 3, 2025

Jan. 3, 2025

https://bugs.winehq.org/show_bug.cgi?id=48877 Bug ID: 48877 Summary: [regression] Melodyne crashes when using the Pitch tool Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: marcan(a)marcansoft.com Distribution: --- Created attachment 66814 --> https://bugs.winehq.org/attachment.cgi?id=66814 Partial fix Tested on git master. Regression was introduced by commit 9bc6f004ce, but that commit is not the root cause. The assertion `assert( obj->numRects <= nb_points / 2 );` would fail, but the code actually crashes earlier due to memory corruption as obj->rects overflows. In the normal case of nb_points == 0, ET->ymin..ymax are 2147483647..-2147483648, which makes the code iterate over zero scanlines as ymax < ymin. However, in the crash case, ymin..ymax are -2147483648..378 (note the negative ymin), so it tries to iterate over two billion scanlines and adds rects to the obj until it crashes. This happens because create_polypolygon_region gets passed an insane polygon with a -2147483648,-2147483648 vertex. The actual bug is in GdipWidenPath, which produces NaN float points, which get converted to that insane int after rounding. And this happens because Melodyne is passing in a degenerate path with the first two points at the same position (added debugging trace to dump the path points): format: "index: [type] X, Y" 00df:err:gdiplus:GdipWidenPath 0: [0] 4.000000, 4.000946 00df:err:gdiplus:GdipWidenPath 1: [1] 4.000000, 4.000946 00df:err:gdiplus:GdipWidenPath 2: [3] 4.000000, 4.000946 00df:err:gdiplus:GdipWidenPath 3: [3] 4.000000, 4.000000 00df:err:gdiplus:GdipWidenPath 4: [3] 4.000000, 4.000000 The code goes GdipWidenPath -> widen_open_figure -> widen_cap, where the segment length is computed as 0 and it ends up dividing by zero. I'm not sure what Windows does here. add_bevel_point handles the special case by just placing a point coincident with the path, ignoring the pen width. The attached patch generalizes that to widen_cap as a whole. It fixes the Melodyne crash for me, but I'm not sure if it's the correct behavior, and degenerate segments will probably cause problems in other code paths (e.g. add_anchor seems to have the same bug). Maybe a better solution would be to just remove coincident points from the path before widening (being careful of cases where the path ends up with one point after this). Someone with more experience with the GDI code should look at this, and perhaps test it on Windows to see how it behaves. -- 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 13

[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 36788] New: Wine doesn't show anything with Photodex slideshow
by wine-bugs＠winehq.org Dec. 26, 2024

Dec. 26, 2024

http://bugs.winehq.org/show_bug.cgi?id=36788 Bug ID: 36788 Summary: Wine doesn't show anything with Photodex slideshow Product: Wine Version: 1.7.20 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: ostash(a)ostash.kiev.ua CC: julliard(a)winehq.org Regression SHA1: ea07c310ecfee6b301e7af8413760eb446e6f184 I have one exe file which seems to be Photodex generated slideshow application. It used to word perfectly with Wine in 2010-2012, but when I tried to run it recently I got no output on screen. Sound plays fine, and it looks like application window is created (it is present on taskbar), but there is no window, no borders, no title, no output. Well this slideshow runs fullscreen, but anyway no output. I've managed to bisect this problem to: ea07c310ecfee6b301e7af8413760eb446e6f184 is the first bad commit commit ea07c310ecfee6b301e7af8413760eb446e6f184 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue Sep 4 13:34:15 2012 +0200 winex11: Create the whole window at window creation time. :040000 040000 62dd63d6f45078b96e4305d60fe8d1b7386b1bc0 c02b6dc1c8940fc75d22753888c3fba415848f38 M dlls Unfortunately code changed too much from that time, so git revert patch can't be applied. -- 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 29