April 2024 - Wine-Bugs - list.winehq.org

[Bug 46947] New: Loxone Config works but some text is missing.
by wine-bugs＠winehq.org July 2, 2024

July 2, 2024

https://bugs.winehq.org/show_bug.cgi?id=46947 Bug ID: 46947 Summary: Loxone Config works but some text is missing. Product: Wine Version: 4.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: j.echter(a)gmx.de Distribution: --- Created attachment 64069 --> https://bugs.winehq.org/attachment.cgi?id=64069 screenshot of the problem. Program installs fine and runs, but some text is not visible in some checkboxes. see screenshot download link for the tool: https://www.loxone.com/dede/produkte/loxone-config/ -- 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 11

[Bug 34029] New: QuickBooks SS 2008 R1 hangs on first run
by wine-bugs＠winehq.org July 2, 2024

July 2, 2024

http://bugs.winehq.org/show_bug.cgi?id=34029 Bug #: 34029 Summary: QuickBooks SS 2008 R1 hangs on first run Product: Wine Version: 1.6-rc5 Platform: x86-64 URL: http://download.microsoft.com/download/C/C/0/CC0BD555- 33DD-411E-936B-73AC6F95AE11/IE8-WindowsXP-x86-ENU.exe OS/Version: Linux Status: NEW Keywords: dotnet, download Severity: minor Priority: P2 Component: mscoree AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Classification: Unclassified Created attachment 45221 --> http://bugs.winehq.org/attachment.cgi?id=45221 wine-1.6-rc5 console output QuickBooks SS 2008 R1 hangs on first run following a successful install and working around Bug 34028 with msxml4. Subsequent attempts to run the application becomes less and less useful: I assume the data becomes too corrupt to continue. Workaround is dotnet20. -- 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 9

[Bug 45474] New: Angels of Death ( game ) wont open .net Error
by wine-bugs＠winehq.org July 2, 2024

July 2, 2024

https://bugs.winehq.org/show_bug.cgi?id=45474 Bug ID: 45474 Summary: Angels of Death ( game ) wont open .net Error Product: Wine-staging Version: 3.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xehi(a)yk20.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Unhandled Exception: System.ObjectDisposedException: Cannot access a disposed object. Object name: 'System.Windows.Forms.LinkLabel'. at System.Windows.Forms.Control.CreateHandle () [0x00013] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.LinkLabel.CreateHandle () [0x00000] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Control.CreateGraphics () [0x00008] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Control.Invalidate (System.Drawing.Region region, System.Boolean invalidateChildren) [0x00000] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Control.Invalidate (System.Drawing.Region region) [0x00000] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.Control:Invalidate (System.Drawing.Region) at System.Windows.Forms.LinkLabel+Link.Invalidate () [0x00016] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.LinkLabel+Link.set_Focused (System.Boolean value) [0x00009] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.LinkLabel.Select (System.Boolean directed, System.Boolean forward) [0x00046] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Control.SelectNextControl (System.Windows.Forms.Control ctl, System.Boolean forward, System.Boolean tabStopOnly, System.Boolean nested, System.Boolean wrap) [0x00051] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Form.SetVisibleCore (System.Boolean value) [0x00146] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Control.set_Visible (System.Boolean value) [0x00009] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.Control:set_Visible (bool) at System.Windows.Forms.Application.RunLoop (System.Boolean Modal, System.Windows.Forms.ApplicationContext context) [0x00059] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Application.Run (System.Windows.Forms.ApplicationContext context) [0x00011] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Application.Run (System.Windows.Forms.Form mainForm) [0x00006] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at _1._1._8._9.Program.Main () [0x00013] in <864ef9c5e92d43a4849a7da3a17ce838>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.ObjectDisposedException: Cannot access a disposed object. Object name: 'System.Windows.Forms.LinkLabel'. at System.Windows.Forms.Control.CreateHandle () [0x00013] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.LinkLabel.CreateHandle () [0x00000] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Control.CreateGraphics () [0x00008] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Control.Invalidate (System.Drawing.Region region, System.Boolean invalidateChildren) [0x00000] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Control.Invalidate (System.Drawing.Region region) [0x00000] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.Control:Invalidate (System.Drawing.Region) at System.Windows.Forms.LinkLabel+Link.Invalidate () [0x00016] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.LinkLabel+Link.set_Focused (System.Boolean value) [0x00009] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.LinkLabel.Select (System.Boolean directed, System.Boolean forward) [0x00046] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Control.SelectNextControl (System.Windows.Forms.Control ctl, System.Boolean forward, System.Boolean tabStopOnly, System.Boolean nested, System.Boolean wrap) [0x00051] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Form.SetVisibleCore (System.Boolean value) [0x00146] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Control.set_Visible (System.Boolean value) [0x00009] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.Control:set_Visible (bool) at System.Windows.Forms.Application.RunLoop (System.Boolean Modal, System.Windows.Forms.ApplicationContext context) [0x00059] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Application.Run (System.Windows.Forms.ApplicationContext context) [0x00011] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at System.Windows.Forms.Application.Run (System.Windows.Forms.Form mainForm) [0x00006] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0 at _1._1._8._9.Program.Main () [0x00013] in <864ef9c5e92d43a4849a7da3a17ce838>:0 -- 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 51685] New: In Wine gdiplus:font fails to find "MS Shell Dlg" in Arabic, Japanese and Chinese locales
by WineHQ Bugzilla July 2, 2024

July 2, 2024

https://bugs.winehq.org/show_bug.cgi?id=51685 Bug ID: 51685 Summary: In Wine gdiplus:font fails to find "MS Shell Dlg" in Arabic, Japanese and Chinese locales Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- When running in Wine, gdiplus:font fails in the Arabic, Japanese and Chinese locales: font.c:890: Test failed: Expected 0, got 14 https://test.winehq.org/data/patterns.html#gdiplus:font In all three cases the failure happens because GdipCreateFontFamilyFromName() fails to find an "MS Shell Dlg" font: is_font_installed_proc() is never called and EnumFontFamiliesW(..."MS Shell Dlg"...) returns non-zero. -- 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 54943] New: The gdipdrawstring function uses the wrong width when rendering CJK fonts
by WineHQ Bugzilla July 2, 2024

July 2, 2024

https://bugs.winehq.org/show_bug.cgi?id=54943 Bug ID: 54943 Summary: The gdipdrawstring function uses the wrong width when rendering CJK fonts Product: Wine Version: 8.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: 399989567(a)qq.com Distribution: --- 1. First create a LOGFONT, and make lfwidth=0, and use the font Tahoma 2. Use Font "font(hdc, &lf)" to create the font 3. Use " graphics.DrawString(string, -1, &font, { 1.0f,1.0f,0,0 }, &format, &brush);" to render the string where WCHAR string[] = L "这里有一些错误". You will find the Chinese font is too narrow.If you fail to render, make sure your lfCharSet=134 ps：Don't say there is no Chinese in tahoma so there is a rendering problem, it has nothing to do with this bug I researched the bug and found that it is related to the implementation of gdipdrawstring. The function finally calls GDI32_GdipDrawDriverString, which uses SelectObject to select the font and ExtTextOutW to output the font. So the problem can be well abstracted out, the reason for the problem is in the last selectobject lf.lfwidth=7 (instead of the 0 you set at the beginning) ps:7 is the result of my computer's calculation So we can write a simple demo to reproduce this problem: 1.lf.lfWidth = 0; 2.hUnderline = CreateFontIndirectA(&lf); 3.SelectObject(hdc, hUnderline); 4.ExtTextOutW(hdc, x, y, 0, NULL, string, lstrlenW(string), NULL); 5.lf.lfWidth = 7; 6.hUnderline = CreateFontIndirectA(&lf); 7.SelectObject(hdc, hUnderline); 8.ExtTextOutW(hdc, x, y, 0, NULL, string, lstrlenW(string), NULL); You can find that the strings in 4 are drawn at the correct width, while the strings in 8 are too narrow; I don't know how to fix this bug, as it also affects the calculation of the string width I hope I can get an answer -- 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 25355] New: Time clock SBE 1.2 and 2.2 not working properly on ubuntu 10.04LTS
by wine-bugs＠winehq.org July 2, 2024

July 2, 2024

http://bugs.winehq.org/show_bug.cgi?id=25355 Summary: Time clock SBE 1.2 and 2.2 not working properly on ubuntu 10.04LTS Product: Wine Version: 1.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ryanmore2006(a)yahoo.com.ph Our company used Ubuntu 8.04 install in all computer in all branches. were using Time clock SBE 1.2 for time logging for all our employees. the said software were stable in ubuntu 8.04 LTS wine wine version 1.0. The problem starts when we updated the LINUX OS to Ubuntu 10.04LTS with wine 1.2 install, but something wrong with the some menu can't be seen anymore, we tried to update the time clock sbe form 1.2 to 2.2 but the unfortunately it did not fixed the problem. we also updated the version of wine but still the same. for reference i will attached the screen shot for ubuntu 8.04 and 10.04 Im homping that someone can help me with this problem. -- 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 13

[Bug 54890] New: Ultimate Doom Builder will crash if some dialoge boxes are used
by WineHQ Bugzilla July 2, 2024

July 2, 2024

https://bugs.winehq.org/show_bug.cgi?id=54890 Bug ID: 54890 Summary: Ultimate Doom Builder will crash if some dialoge boxes are used Product: Wine Version: 8.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: beneschork(a)gmail.com Distribution: --- Created attachment 74388 --> https://bugs.winehq.org/attachment.cgi?id=74388 Crash log Whenever I use Ultimate doom Builder, I will often need to change a Thing* ID or a texture. To do this, I have to click on the linedef or thing to open its dialog box. There are fields I use to enter a string for the texture name or and integer for the TID, and whenever I do, wine immediately throws up an error and I have to save the crash log. This bug is replaceable on my machine, I have even changed distros. -- 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 21

[Bug 27294] New: livezilla can't start, complains of missing Verdana font
by wine-bugs＠winehq.org July 2, 2024

July 2, 2024

http://bugs.winehq.org/show_bug.cgi?id=27294 Summary: livezilla can't start, complains of missing Verdana font Product: Wine Version: 1.3.20 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com A user complained that Livezilla wouldn't start, see http://forum.winehq.org/viewtopic.php?t=12202 I was able to reproduce this, plus a possible font-related gdiplus bug: cd $HOME rm -rf ~/.wine sh winetricks corefonts dotnet20 wget http://www.livezilla.net/downloads/pubfiles/LiveZilla_3.3.2.2_Full.exe wine LiveZilla_3.3.2.2_Full.exe cd ~/".wine/drive_c/Program Files/LiveZilla" wine LiveZilla That gets the error Your system misses the font Microsoft Sans Serif Copying micross.ttf from a Windows system into ~/.wine/drive_c/windows/Fonts gets past that. (Dunno if that needs to be added to winetricks, or if one of the existing fonts in 'allfonts' should satisfy it.) The next problem is Your system misses the font Tahoma Doing winetricks tahoma gdiplus gets past that. (Don't know why gdiplus was needed, that's interesting.) The next problem is the user's error, Your system misses the font 'Verdana Regular' Which is funny, because Verdana Regular is already in windows/Fonts, and WINEDEBUG=+font shows trace:font:AddFontToList Loading font file "/home/dank/.wine/dosdevices/c:/windows/Fonts/Verdana.TTF" index 0 trace:font:get_familyname Got localised name L"Verdana" trace:font:AddFontToList fsCsb = 2000019f 00000000/00000287 00000000 00000000 00000000 trace:font:AddFontToList Added font L"Verdana" L"Regular" ... trace:font:AddFontToList Loading font file "/usr/share/fonts/truetype/msttcorefonts/Verdana.ttf" index 0 trace:font:get_familyname Got localised name L"Verdana" trace:font:AddFontToList Already loaded font L"Verdana" L"Regular" original version is 10000, this version is 10000 trace:font:AddFontToList Original font is newer so skipping this one Oddly, at some point, wine forgets about the Regular variant: trace:font:DumpFontList Family: L"Verdana" 000d:Ret advapi32.RegGetValueW() retval=0000trace:font:DumpFontList L"Bold" 2000019f 000d:Call advapi32.RegGetValueW(0000004c,000trace:font:DumpFontList L"Bold Italic" 2000019f Perhaps one of the fonts in /usr/share/fonts is interfering... -- 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 43736] New: PathGradientBrush results in a white shape
by wine-bugs＠winehq.org July 2, 2024

July 2, 2024

https://bugs.winehq.org/show_bug.cgi?id=43736 Bug ID: 43736 Summary: PathGradientBrush results in a white shape Product: Wine Version: 2.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: norike(a)gmail.com Distribution: --- Created attachment 59217 --> https://bugs.winehq.org/attachment.cgi?id=59217 test project with screenshots We develop a charting library and found some gradients are drawn as solid white shapes in Wine for Ubuntu. Reducing the issue to the minimum we found the problem seems to be when drawing a rectangle with a PathGradientBrush. See the screenshots in the attachment. - Windows.png is the result of running the .exe in a Windows 10. - Ubuntu.png is the result of running the .exe in Ubuntu 16.04 using Wine. We got the same result in Wine 1.6 (?), 2.0.2 and 2.17. The attachment also contains the .exe and the project sources (made with Visual Studio 2017). -- 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 5

[Bug 33410] New: QQ International 1.6 displays its window abnormally with a black line across
by wine-bugs＠winehq.org July 2, 2024

July 2, 2024

http://bugs.winehq.org/show_bug.cgi?id=33410 Bug #: 33410 Summary: QQ International 1.6 displays its window abnormally with a black line across Product: Wine Version: 1.5.28 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus AssignedTo: wine-bugs(a)winehq.org ReportedBy: fangendoucg(a)gmail.com Classification: Unclassified Created attachment 44204 --> http://bugs.winehq.org/attachment.cgi?id=44204 screenshot Hi folks, While I install QQ International QQIntl1.61.exe, its first window shows with a threadlet across.See the attachment. Well, winetricks gdiplus can workaround it. It's free to download. $ sha1sum QQIntl1.61.exe 6cd9042f591a7b140e3216df2851c9b7a436be34 QQIntl1.61.exe -- 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 11