wine-bugs July 2021

wine-bugs@winehq.org

1 participants
5147 discussions

[Bug 48877] New: [regression] Melodyne crashes when using the Pitch tool
by WineHQ Bugzilla 03 Jan '25

03 Jan '25

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 31 Dec '24

31 Dec '24

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 30 Dec '24

30 Dec '24

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 48686] New: Soldier of Fortune Platinum Displays Strange Textures
by WineHQ Bugzilla 29 Dec '24

29 Dec '24

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 29 Dec '24

29 Dec '24

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 51345] New: Regression: Visual Studio 2005 "package load failure"
by WineHQ Bugzilla 29 Dec '24

29 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=51345 Bug ID: 51345 Summary: Regression: Visual Studio 2005 "package load failure" Product: Wine Version: 6.11 Hardware: x86-64 OS: FreeBSD Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: damjan.jov(a)gmail.com winetricks vc2005trial wine cmd "C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat" devenv Some time during 28-31 March 2021, the Visual Studio 2005 trial began giving +/- 10 of these error dialogs on startup, each relating to a different package. This is a rough transcript of one of them: ------------------------ Package Load Failure ------------------------ Package 'Microsoft.VisualStudio.TestTools.TestCaseManagement.QualtyToolsPackage, Microsoft.VisualStudio.QualityTools.TestCaseManagement, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03F5F7f11d50s3a' has failed to load properly { GUID = {AS4DSAES-9ACE-4FOE-ADGF-7AFESSFEFCET) ). Please contact package vendor for assistance. Application restart is recommended, due to possible environment corruption. Would you like to disable loading this package in the future? You may use 'devenv /resetskippkgs' to re-enable package loading. Yes No ------------------------ It is the worst git bisect I've ever done. Apart from the lengthy time needed to test each commit, the regression occurs within a range of 44 commits (bb065801a69..2a8a4cbbe63), the first 43 of which all die on startup, so we can't easily distinguish that bug from this one. I've now had to make a separate branch, "git rebase --onto <that range>" to copy commits from that range there, then "git rebase -i" to reorder them and separate the startup-breaking commits (ntdll/kernel32/kernelbase) from the other commits. Unfortunately, having done so, it appears the startup-breaking commits are also the commits that caused this regression. One or more of these is the culprit: ntdll: Move kernel32 loading into LdrInitializeThunk(). ntdll: Return system dir path for PE mapping bootstrap placeholders. ntdll: Fail to load non-existent dlls, except during prefix bootstrap. ntdll: Also check syswow64 to determine if the prefix was initialized. include: Add more SYSTEM_INFORMATION_CLASS definitions. kernel32: Implement GetSystemCpuSetInformation(). ntdll: Implement NtQuerySystemInformationEx(SystemCpuSetInformation). kernelbase: Don't fall back to dll loading for LOAD_LIBRARY_AS_DATAFILE. ntdll: Set the window title to the image name on the Unix side. ntdll: Remove load_builtin_dll() and get_load_order() from the Unix interface. ntdll: Map the builtin or fake dll from the Wine dirs if it's missing from the prefix. -- 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 15

[Bug 42882] New: rs232 port access no working with ubuntu 17.10 worked fine with previous versions of ubuntu
by wine-bugs＠winehq.org 28 Dec '24

28 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=42882 Bug ID: 42882 Summary: rs232 port access no working with ubuntu 17.10 worked fine with previous versions of ubuntu Product: Wine Version: 2.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: arcadeshopper(a)gmail.com Distribution: --- I am able to connect to the serial port via applications in wine but there is never any data received. I can communicate outside of wine without issue using minicom. I am using a ftdi usb to serial adapter that worked fine in previous versions of ubuntu. I am having this problems with all relases of wine I have tried including the default ubuntu package and 2.4 from the PPA -- 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 26

[Bug 21017] New: Adobe Premiere Pro CS4 won't start
by wine-bugs＠winehq.org 27 Dec '24

27 Dec '24

http://bugs.winehq.org/show_bug.cgi?id=21017 Summary: Adobe Premiere Pro CS4 won't start Product: Wine Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: skerit(a)kipdola.com Created an attachment (id=25215) --> (http://bugs.winehq.org/attachment.cgi?id=25215) Log of Premiere Pro CS4 itself To reproduce this you'll have to install Premiere Pro CS4 using wine 1.1.16 (there's also a patch available for current trunk) I believe this beginning error lies somewhere in msxml and gdiplus. (You can get a lot further in the program using native dll's (like msxml and gdiplus) but then you're not allowed to post bugs for obvious reasons. You can try it out using the same winetricks for Photoshop CS4) -- 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 48

[Bug 51230] New: winecfg: Graphics tab - Per application settings don't work
by WineHQ Bugzilla 26 Dec '24

26 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=51230 Bug ID: 51230 Summary: winecfg: Graphics tab - Per application settings don't work Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jkfloris(a)dds.nl Distribution: --- "Wine can mimic different Windows versions for each application. This tab is linked to the Libraries and Graphics tabs to allow you to change system-wide or per-application settings in those tabs as well." >From this I understand that it should also be possible to also set the DPI or a virtual desktop per application. Unfortunately, this does not work. For example: winecfg Applications tab -> Add application -> "notepad.exe" (select notepad.exe) Graphics tab -> Select "Emulate a virtual desktop" (click "Apply" and "OK") wine notepad.exe Now I expect notepad to run in a virtual desktop. -- 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 29267] New: rtf text from wine's richedit shows up with a black background in LibreOffice Writer
by wine-bugs＠winehq.org 26 Dec '24

26 Dec '24

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

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 July 2021