June 2018 - Wine-Bugs - list.winehq.org

[Bug 33350] New: Maxthon 4 fails to start
by wine-bugs＠winehq.org March 2, 2026

March 2, 2026

http://bugs.winehq.org/show_bug.cgi?id=33350 Bug #: 33350 Summary: Maxthon 4 fails to start Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gmazzone0(a)aol.com Classification: Unclassified When I open Maxthon 4, it shows a blonk page with:"Missing: sidebar/index.html Missing: layout:html" and can't be used -- 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 17

[Bug 39844] New: iqfeed.exe does crash after running couple of hours
by wine-bugs＠winehq.org March 2, 2026

March 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=39844 Bug ID: 39844 Summary: iqfeed.exe does crash after running couple of hours Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mozdemir(a)gmail.com Distribution: --- Created attachment 53193 --> https://bugs.winehq.org/attachment.cgi?id=53193 winedbg output Hi, i have windows applications iqfeed.exe. I run it using wine.it does run pretty well but after couple of hours it does crash. All System info is below. I attach the winedbg/back trace file, too. Thanks a lot, musti System information: Wine build: wine-1.6.2 Platform: i386 Host system: Linux Host version: 3.19.0-30-generic -- 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 19368] New: lpfnWndProc can't catch Up/Down/Left/Right and CTRL+ other Button
by wine-bugs＠winehq.org March 1, 2026

March 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=19368 Summary: lpfnWndProc can't catch Up/Down/Left/Right and CTRL+ other Button Product: Wine Version: 1.1.26 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sakaihdt(a)d2.dion.ne.jp Hello I want to use "sakura editor". (a Japanese Open Souce text editor for MS Windows) (http://sakura-editor.sourceforge.net/) But this application is not work well in wine(1.0.1 or 1.1.26 Ubuntu GNU/Linux 9.0.4) - Not work Up/Down/Left/Right button in text area - Not work CTRL+C or CTRL+A and other in text area - Not work Backspace in text area - Not work Function Key in text area normal text button( a-z, 0-9 ) is work well, and Up/Down... is work well in menu . "sakura editor" catch Up/Down/Ctrl event from lpfnWndProc() callback. but wine's lpfnWndProc seem not work when push Up/Down... key. ( I insert log in sakura editor source and check.) I have 2 question. please tell me. (1) Can lpfnWndProc() catch Up/Down/Left/Right CTRL+A,X,C and Function key in Wine ? (2) "lpfnWndProc() can catch Up/Down/Left/Right ..." is WindowsAPI specification? Thank you. -- 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 34134] New: "open file" dialog does not shrink after switching to "use adobe dialog" and back to system dialog
by wine-bugs＠winehq.org March 1, 2026

March 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=34134 Bug #: 34134 Summary: "open file" dialog does not shrink after switching to "use adobe dialog" and back to system dialog Product: Wine Version: 1.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: unxed(a)mail.ru Classification: Unclassified If you press "use adobe dialog" button in "open file" dialog, it grows. If you press "use os dialog" after it, window does not shrink back. -- 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 3

[Bug 33241] New: incorrect display of a combobox in a Clipper application
by wine-bugs＠winehq.org March 1, 2026

March 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=33241 Bug #: 33241 Summary: incorrect display of a combobox in a Clipper application Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ironeman(a)tiscali.it Classification: Unclassified As mentioned in http://forum.winehq.org/viewtopic.php?f=8&t=18198, I am using 16-bit Clipper/xBase programs. When I have a listbox, the field is not correctly initialized, despite the list is ok. Debugging my application, I have found that it is due to a strange memory management. I start by saying that Clipper/xBase uses dynamic scoping, so the value of a variable is the last assigned to it into the stack; a variable can be local or global (prefixed by m->). When using the dialog that has the problem, I use the activation command (Fivewin library): m->mTipoDoc:=.... // assign the global variable m->mTipoDoc activate DIALOG oDlg centered on init (SettaCombo()) function SettaCombo() // initialization code of the dialog ... // use the global variable m->mTipoDoc but, at this point, when using WINE, the variable has lost its content and is empty I solved the problem using a local variable that temporarily holds the value of the global variable: m->mTipoDoc:=.... // assign the global variable m->mTipoDoc local tmpcod:=m->mTipoDoc // to solve the wine bug activate DIALOG oDlg centered on init (SettaCombo(tmpcod)) function SettaCombo(val) m->mTipoDoc:=val // to solve the wine bug ... // use the global variable m->mTipoDoc Evidently the local variable is managed in a different way by WINE and the error has disappered. To test this behaviour, I wrote the attached sample program. Into the zip there is a readme.pdf that explains how it works. Best regards. -- 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 5

[Bug 21127] New: What Colour color picking functionality is not identical to Windows
by wine-bugs＠winehq.org March 1, 2026

March 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=21127 Summary: What Colour color picking functionality is not identical to Windows Product: Wine Version: 1.1.35 Platform: x86 URL: http://www.jumpjet.info/Win2k/05/What_Colour/WhatColou r.zip OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: arethusa26(a)gmail.com With wine-1.1.35-105-gd4a7a9d, when the color picker in the What Colour program is selected, moving the mouse outside the What Colour's client area doesn't result in any color selection changes until the mouse is pressed, causing the application to finally grab the color under the mouse cursor by presumably taking a "screenshot" of the desktop area. On Windows XP, this "screenshotting" behavior happens first, made obvious by a brief, visible change in the screen, and then moving the color picker over the area outside the What Colour client area shows active changes in the color selection, which is only halted when the mouse is pressed. -- 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 8

[Bug 41689] New: Cyberduck crashes at launch
by wine-bugs＠winehq.org Feb. 28, 2026

Feb. 28, 2026

https://bugs.winehq.org/show_bug.cgi?id=41689 Bug ID: 41689 Summary: Cyberduck crashes at launch Product: Wine Version: 1.8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: contact(a)rudloff.pro Distribution: --- Created attachment 56083 --> https://bugs.winehq.org/attachment.cgi?id=56083 Backtrace When I try to run Cyberduck 5.2.3 (https://update.cyberduck.io/windows/Cyberduck-Installer-5.2.3.21496.exe) it crashes. -- 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 23

[Bug 31618] New: Unable to run an old VB5 app
by wine-bugs＠winehq.org Feb. 26, 2026

Feb. 26, 2026

http://bugs.winehq.org/show_bug.cgi?id=31618 Bug #: 31618 Summary: Unable to run an old VB5 app Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ole32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: rhon(a)free.fr Classification: Unclassified Created attachment 41577 --> http://bugs.winehq.org/attachment.cgi?id=41577 First error message I had I'm using wine 1.5.11 on Archlinux, and I try to launch this old game : http://www.cnetfrance.fr/telecharger/waterboy-11006056s.htm?download=1 The problem is that I always get a "Run-time error '13' : Type mismatch" when I try to launch it. I've tried to switch oleaut.dll and ole32.dll to "native" (I used dll copied from an up to date Win XP install), and switch to "Windows 98" mode using winecfg, and then I had the error1 attached. I've installed vb5runtime, vb6run, mfc40 and mfc42 using winetricks, but it didn't help, I now have a window popup with message "System error &H80070078" and console output shows the messages in error2 attached file. -- 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.

3 19

[Bug 39005] New: "http://xml.org/sax/features/namespace-prefixes" default value
by wine-bugs＠winehq.org Feb. 26, 2026

Feb. 26, 2026

https://bugs.winehq.org/show_bug.cgi?id=39005 Bug ID: 39005 Summary: "http://xml.org/sax/features/namespace-prefixes" default value Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: msxml3 Assignee: wine-bugs(a)winehq.org Reporter: ott(a)mirix.org Distribution: --- The specification is ambigous about this feature: "the "http://xml.org/sax/features/namespace-prefixes" feature is set to True. (It is False by default.)" (https://msdn.microsoft.com/en-us/library/ms757829%28v=vs.85%29.aspx) "only if the "http://xml.org/sax/features/namespace-prefixes" feature is set to True. This feature is set to False by default." (https://msdn.microsoft.com/en-us/library/ms762302%28v=vs.85%29.aspx) "The default value is true." (https://msdn.microsoft.com/en-us/library/ms759146%28v=vs.85%29.aspx) "namespace-prefixes | Boolean | True" (https://msdn.microsoft.com/en-us/library/ms762317%28v=vs.85%29.aspx) It should clarified from Microsoft's implementation whether the feature is enabled by default or not. Maybe the "namespace-prefixes" and "http://xml.org/sax/features/namespace-prefixes" are two different features? Perhaps it also makes sense notify Microsoft about the inconsistency. -- 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 2

[Bug 38416] New: Unhandled D3DFORMAT
by wine-bugs＠winehq.org Feb. 26, 2026

Feb. 26, 2026

https://bugs.winehq.org/show_bug.cgi?id=38416 Bug ID: 38416 Summary: Unhandled D3DFORMAT Product: Wine Version: 1.7.40 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru This is the test utility from Microsoft DerectxSDK free distributed Utilities/bin/x86/DXCapsViewer.exe ---- fixme:d3d:wined3d_check_device_format_conversion wined3d 0x134ba0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B10G10R10A2_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d9:wined3dformat_from_d3dformat Unhandled D3DFORMAT 0x54 fixme:d3d9:wined3dformat_from_d3dformat Unhandled D3DFORMAT 0x55 fixme:d3d9:wined3dformat_from_d3dformat Unhandled D3DFORMAT 0x76 fixme:d3d:wined3d_check_device_format_conversion wined3d 0x134ba0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B10G10R10A2_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x134ba0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B5G5R5X1_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x134ba0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B5G5R5A1_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! ---- -- 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.

3 16