wine-bugs February 2021

wine-bugs@winehq.org

1 participants
6835 discussions

[Bug 19713] New: Some serial port communication functions behave differently in Wine and Windows.
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=19713 Summary: Some serial port communication functions behave differently in Wine and Windows. Product: Wine Version: 1.1.27 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: fenixk19(a)mail.ru Created an attachment (id=23025) --> (http://bugs.winehq.org/attachment.cgi?id=23025) Test program This makes test program to hang in Wine, but in MS it is ok. Test program attached. -- 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 43

[Bug 37846] New: Communication broken using FTDI USB Serial Device converter (FT232RL) / Mostly send using CS-51PLUS
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=37846 Bug ID: 37846 Summary: Communication broken using FTDI USB Serial Device converter (FT232RL) / Mostly send using CS-51PLUS Product: Wine Version: 1.7.30 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lgeorgieff(a)gmail.com Distribution: --- Created attachment 50402 --> https://bugs.winehq.org/attachment.cgi?id=50402 WINEDEBUG="+comm" wine .wine/drive_c/Program\ Files\ $x86$/Icom/CS-51PLUS/CS51PLUS.exe log Hi, I am using FTDI USB Serial Device converter to program ham radio. Cable have FT232RL chip and software is CS-51PLUS. Reading from radio is OK but when I try to write (send) configuration to the radio communication is broken after while and I get error message. The same cable and software on the same machine runs without problems on QEMM's virtual windows. -- 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 13296] New: regression problem in upgrade to Ubuntu Hardy/1.0-rc1: Palm Hotsync over serial Segmentation Fault
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=13296 Summary: regression problem in upgrade to Ubuntu Hardy/1.0-rc1: Palm Hotsync over serial Segmentation Fault Product: Wine Version: 1.0-rc1 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jan-winehq(a)h-i-s.nl Created an attachment (id=13150) --> (http://bugs.winehq.org/attachment.cgi?id=13150) Logging output I upgraded to Ubuntu Hardy, and wine 1.0-rc1. Hotsync manager 1.0 for Palm Pilot worked fine before. http://appdb.winehq.org/objectManager.php?sClass=version&iId=10362 Now it crashes half-way synchronising over the serial port, sometimes after a few seconds, sometimes much later in the process. These crashes reproduce well, and yield a segmentation fault without further information $ wine hotsync.exe Segmentation fault $ I do not know if this means that a part of Wine crashes, or just the application. I added logging, where it seems that the problem lies within the call below: 0009:CallTo16(func=111f:072a,ds=1087,118f,7404,0000,0006) ss:sp=1087:ffd0 I am not sure if the problem lies with wine, or that other problems with Ubuntu Hardy may relate to this. It is disappointing that an application that used to work fine, and I came to depend on, is now broken. -- 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 19

[Bug 25083] New: HyperTerminal unable to loop back on COM1 (RS-232)
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=25083 Summary: HyperTerminal unable to loop back on COM1 (RS-232) Product: Wine Version: 1.3.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: graham(a)nerve.org.za On a machine with an on-board RS-232 port at COM1, HyperTerminal (as shipped with Windows XP) is firstly unable to detect the port until changes are made in the WINE registry, thereafter, after attaching a simple loopback adapter (pins 2 and 3 of a DB9F shorted) no characters are echoed to the screen. Obtaining the software: >From a Windows XP installation, copy the files hypertrm.exe and htrn_jis.dll from 'C:\Program Files\Windows NT' and hticons.dll and hypertrm.dll from C:\Windows\System32' into a suitable directory below .wine/drive_c or Download a free 30 day trial of HyperTerminal Private Edition 7.0 from http://www.hilgraeve.com/hyperterminal/ Create a symbolic link for COM1, documented here: http://www.winehq.org/docs/wineusr-guide/misc-things-to-configure ln -s /dev/ttyS0 ~/.wine/dosdevices/com1 At this point, starting HyperTerminal will result in no serial ports being shown. Now, create a registry entry in WINE for the serial port, mentioned in this bug report: http://bugs.winehq.org/show_bug.cgi?id=4282 Add the following lines to .wine/system.reg [Hardware\\Devicemap\\SerialComm] "Serial0"="COM1" Now HyperTerminal can be started, COM1 can be selected and configured, but no characters are echoed to the screen. However, the free terminal program, simply named 'Terminal' and available here: https://sites.google.com/site/terminalbpp/ Does echo characters to the screen. -- 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 23

[Bug 47873] New: kernel32:comm fails randomly
by WineHQ Bugzilla 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=47873 Bug ID: 47873 Summary: kernel32:comm fails randomly Product: Wine Version: 4.17 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:comm fails randomly on multiple Windows versions: comm.c:708: Found Com port COM1. Connected devices may disturb results comm.c:859: Test failed: WaitCommEvent failed with a timeout comm.c:870: recovering after WAIT_TIMEOUT... comm.c:880: Test failed: WaitCommEvent error 0 comm.c:881: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:885: WaitCommEvent for EV_TXEMPTY took 1500 ms (timeout 1500) comm.c:886: Test failed: WaitCommEvent used 1500 ms for waiting https://test.winehq.org/data/tests/kernel32:comm.html These failures are random and have been seen on the following TestBot VM4 configurations: wxppro w2003std w7pro64-32 w1064v1507-32 w1064v1607-32 w1064v1607-64 w1064v1709-64 w1064v1607-64 w1064v1809-32 w1064v1809-32 w1064v1809-64 w1064v1809-2scr-32 w1064v1809-fr-64 w1064v1809-ja-32 w1064v1809-ja-64 So it does not depend on the Windows version, bitness of the test, or locale. However it only happens on QEmu VMs: it never happened on the fg-win7u64 VMware VMs or on the real hardware machines, cw-rx460 and cw2-gtx560. Yet the VMware VMs have two serial COM ports, and, according to dmesg | grep tty, the real hardware machines do have a serial port too. QEmu bug? -- 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 46676] New: Serial port enumeration (get device description) on Mac OS/X 10.9, 10.13
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=46676 Bug ID: 46676 Summary: Serial port enumeration (get device description) on Mac OS/X 10.9, 10.13 Product: Wine Version: 4.0 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: martin(a)hinner.info Created attachment 63628 --> https://bugs.winehq.org/attachment.cgi?id=63628 suspected problematic function Tested on: Mac OS/X 10.9, 10.13 WineBottler (Wine 1.8) works fine; Wine 4.0 (from .pkg) does not work Our application is trying to enumerate serial ports by using setupapi functions. I have not checked where exactly is the problem as debugging on OS/X is a bit difficult for me, however suspected function is attached (it's goal is to get device description). The affected apps are http://obdtester.com/ficom , http://obdtester.com/bimcom , http://obdtester.com/fcom ; I have tried to create symlink in dosdevices (required for WineBottler to get it working), one OS/X 10.13 my link got deleted everytime I ran the app; on OS/X 10.9 link persisted, but not possible to enumerate any serial port(s). I can provide login for download by personal e-mail (not to be disclosed). I have talked about this on wine mailing list a long time ago, it would be super easy if Wine-enabled application can have a way to load system native .so to talk directly to the host system, I have many examples of device drivers that would be super easy to implement. FYI I have already written "winegate.dll.so" which solves this real world problem, but it was rejected for submission to Wine because of "Wine must be 100% transparent" ideology. -- 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 23326] New: Cannot change printer settings, Family Tree 7
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=23326 Summary: Cannot change printer settings, Family Tree 7 Product: Wine Version: 1.2-rc4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jamesl(a)bestweb.net Created an attachment (id=29072) --> (http://bugs.winehq.org/attachment.cgi?id=29072) FTW7 print dialogue, compare Wine to XP Cannot select printer/change print settings with Family Tree Maker 7. Dialogue box comes up, drop-down boxes are working, but radio buttons for switching between "default printer" and an alternate printer are not selectable. Have compared the print dialogue between Wine vs a native install under Windows XP (SP3) and notice some text from the Windows install does not show up under Wine. Also tried the same thing with the "free" version of FTM2005se available at http://past.familytreemaker.com/download/starter.aspx and found it's behavior is the same. So I will describe steps from there, since it would be eaier for someone to get that to test against. STEPS TO RECREATE: 1: Set up wine profile with "WINEPREFIX=/home/jelabarre/wine-apps/ftw2005 winecfg"; set winver to "Windows XP", point the Documents directory under Desktop Integration to my own Documents directory 2: install FTW2005 by running "WINEPREFIX=/home/jelabaWINEPREFIX=/home/jelabarre/wine-apps/ftw2005 wine ./FamilyTreeMaker2005se.exe", accept all defaults. 3: open FTW 2005 from "Wine" menu entry on Gnome menu. Selected "Buy Later" from popup window (does not affect outcome, as same print problem occurrs in a regular retail version of FTM7) 4: create new file, or use existing file (same result either way) 5: select "File | Print Setup", then try to select radio button for either "Default Printer" or "Specific Printer". Neither can be selected 6: try selecting a "specific printer" from drop-down box. Printer can be selected, but radio buttons still not functional. 7: after selecting a printer other than the default (such as print-to-PDF) and then try printing. Output will still go to the Linux default printer, no edits of the print settings will take effect. The "Family Archive Viewer v6.0" at http://familytreemaker.genealogy.com/abtffiv.html and "Family Archive Viewer v11.0" at http://www.genealogy.com/abtffiv.html are other variants that exhibits this behavior. Have attached sample screenshots of Wine vs WinXP versions of the print dialogue. -- 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 30155] New: secdrv.sys from SafeDisc v2.05.030 does not work
by wine-bugs＠winehq.org 23 Jul '23

23 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=30155 Bug #: 30155 Summary: secdrv.sys from SafeDisc v2.05.030 does not work Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl AssignedTo: wine-bugs(a)winehq.org ReportedBy: stefan(a)codeweavers.com Classification: Unclassified Created attachment 39336 --> http://bugs.winehq.org/attachment.cgi?id=39336 service,relay,winedevice,ntoskrnl log SafeDisc 2.05.030 does not work out of the box. The user-visible symptom is that the application exits with exit code 0 without any output. This affects for example the Command and Conquer Red Alert 2 installer, which is safedisc protected for some reason. The problem seems to be related to the specific secdrv.sys version. If I take a secdrv.sys from a newer safedisc version(e.g. 2.40.010 from the RA2 Yuri's revenge expansion) and put it in C:\windows\system32\drivers, the installer works. ProtectId says: Scanning -> D:\Setup\Setup.exe File Type : 32-Bit Exe (Subsystem : Win GUI / 2), Size : 1308863 (013F8BFh) Byte(s) -> File has 733375 (0B30BFh) bytes of appended data starting at offset 08C800h [File Heuristics] -> Flag : 00000000000000000100000000100111 (0x00004027) [!] Safedisc v2.05.030 detected ! [i] Appended data contents.... [.] o: 0x0008C828 / t: <0x00000001> <0x00000000> <0x00000001> / s: 00194947 byte(s) -> ~de7bc4.tmp [.] o: 0x000BC1D2 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00030208 byte(s) -> clcd32.dll [.] o: 0x000C37F9 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00006784 byte(s) -> clcd16.dll [.] o: 0x000C529D / t: <0x00000001> <0x00000000> <0x0000044D> / s: 00067584 byte(s) -> mcp.dll [.] o: 0x000D5AC5 / t: <0x00000001> <0x00000000> <0x00000000> / s: 00327220 byte(s) -> ~df394b.tmp [.] o: 0x00125920 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00034304 byte(s) -> drvmgt.dll [.] o: 0x0012DF47 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00018768 byte(s) -> secdrv.sys [.] o: 0x001328BF / t: <0x00000001> <0x00000000> <0x00000000> / s: 00053248 byte(s) -> ~ef7194.tmp [CompilerDetect] -> Visual C++ 6.0 - Scan Took : 0.640 Second(s) The md5sum of the broken secdrv.sys is XXX. The md5sum of the working 2.40.010 driver is f376a1580204e47f37a721e1cbc5582a. I am attaching a +relay,+service,+winedevice+ntoskrnl log of a failed run of the setup tool. -- 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 32

[Bug 44823] New: Steam doesn' t close on exit. Will continue running in background.
by wine-bugs＠winehq.org 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=44823 Bug ID: 44823 Summary: Steam doesn't close on exit. Will continue running in background. Product: Wine Version: 3.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vblanton(a)gmail.com Distribution: --- Created attachment 60857 --> https://bugs.winehq.org/attachment.cgi?id=60857 Steam system information and version Running the latest Steam client, I find that Steam doesn't actually close entirely after I exit normally with Steam>Exit. I have to open System Monitor and kill all steam and wine related processes. I can't open steam again until I do so, and the Steam.exe and wineserver processes chew 17% of my CPU each in the background until I do so. -- 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 14

[Bug 42360] New: Terragen 4 fails to start
by wine-bugs＠winehq.org 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=42360 Bug ID: 42360 Summary: Terragen 4 fails to start Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: eneeen(a)gmail.com Distribution: --- Created attachment 57137 --> https://bugs.winehq.org/attachment.cgi?id=57137 tgd4_backlog Using Kubuntu 16.10 I've attached backlog. -- 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 41693] New: The Forrest Steam crashes on startup
by wine-bugs＠winehq.org 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=41693 Bug ID: 41693 Summary: The Forrest Steam crashes on startup Product: Wine Version: 1.9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thomthomthom(a)ymail.com Distribution: --- When I click on the "Play" button, the window "TheForest Configuration" appears. I click on "Play!" and the game crashes. Terminal output: thomthomthom@thomthomthom:/usr/src/wine$ wine ~/.wine/drive_c/Program\ Files/Steam/Steam.exe fixme:ver:GetCurrentPackageId (0x32e460 (nil)): stub ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt". thomthomthom@thomthomthom:/usr/src/wine$ fixme:file:SetFileCompletionNotificationModes 0x29c 1 - stub wine: Unhandled exception 0x80000003 in thread 78 at address 0x100aa6d9 (thread 0078), starting debugger... fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETTASKBARPOS, hwnd=(nil)): stub fixme:appbar:SHAppBarMessage unknown msg: 4 fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETSTATE): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=3): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=1): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=0): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=2): stub err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:mfplat:MFStartup (65648, 1): stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:gdi:GdiInitializeLanguagePack stub fixme:ntdll:EtwEventUnregister (deadbeef) stub. err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, (nil) 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 (nil) 0x33f7a8) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, 0x179d48 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 0x179d48 0x33f7a8) returning a dummy value (current locale) fixme:winsock:WSALookupServiceBeginW (0x33f4b8 0x00000ff0 0x33f4f4) Stub! fixme:iphlpapi:NotifyAddrChange (Handle 0x33f638, overlapped 0x17af7c): stub fixme:win:RegisterDeviceNotificationW (hwnd=0x600e0, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterDeviceNotificationW (hwnd=0x600e0, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:EnumDisplayDevicesW ((null),0,0x33f114,0x00000000), stub! fixme:ver:GetCurrentPackageId (0x2f3dfa4 (nil)): stub fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETTASKBARPOS, hwnd=(nil)): stub fixme:appbar:SHAppBarMessage unknown msg: 4 fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETSTATE): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=3): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=1): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=0): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=2): stub fixme:dwmapi:DwmExtendFrameIntoClientArea (0x6014a, 0x33e798) stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETTASKBARPOS, hwnd=(nil)): stub fixme:appbar:SHAppBarMessage unknown msg: 4 fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETSTATE): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=3): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=1): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=0): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=2): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETTASKBARPOS, hwnd=(nil)): stub fixme:appbar:SHAppBarMessage unknown msg: 4 fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETSTATE): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=3): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=1): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=0): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=2): stub fixme:file:SetFileCompletionNotificationModes 0x28c 1 - stub wine: Unhandled exception 0x80000003 in thread f6 at address 0x100aa6d9 (thread 00f6), starting debugger... err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:mfplat:MFStartup (65648, 1): stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:gdi:GdiInitializeLanguagePack stub fixme:ntdll:EtwEventUnregister (deadbeef) stub. err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, (nil) 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 (nil) 0x33f7a8) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, 0x179d40 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 0x179d40 0x33f7a8) returning a dummy value (current locale) fixme:winsock:WSALookupServiceBeginW (0x33f4b8 0x00000ff0 0x33f4f4) Stub! fixme:iphlpapi:NotifyAddrChange (Handle 0x33f638, overlapped 0x17af74): stub fixme:win:RegisterDeviceNotificationW (hwnd=0x30126, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterDeviceNotificationW (hwnd=0x30126, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:EnumDisplayDevicesW ((null),0,0x33f114,0x00000000), stub! fixme:ver:GetCurrentPackageId (0x2f3dfa4 (nil)): stub fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:file:SetFileCompletionNotificationModes 0x28c 1 - stub wine: Unhandled exception 0x80000003 in thread 118 at address 0x100aa6d9 (thread 0118), starting debugger... err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:mfplat:MFStartup (65648, 1): stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:gdi:GdiInitializeLanguagePack stub fixme:ntdll:EtwEventUnregister (deadbeef) stub. err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, (nil) 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 (nil) 0x33f7a8) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, 0x179d48 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 0x179d48 0x33f7a8) returning a dummy value (current locale) fixme:winsock:WSALookupServiceBeginW (0x33f4b8 0x00000ff0 0x33f4f4) Stub! fixme:iphlpapi:NotifyAddrChange (Handle 0x33f638, overlapped 0x17af7c): stub fixme:win:RegisterDeviceNotificationW (hwnd=0x4012a, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterDeviceNotificationW (hwnd=0x4012a, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:EnumDisplayDevicesW ((null),0,0x33f114,0x00000000), stub! fixme:ver:GetCurrentPackageId (0x303dfa4 (nil)): stub fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:file:SetFileCompletionNotificationModes 0x28c 1 - stub wine: Unhandled exception 0x80000003 in thread 13c at address 0x100aa6d9 (thread 013c), starting debugger... err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:mfplat:MFStartup (65648, 1): stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:gdi:GdiInitializeLanguagePack stub fixme:ntdll:EtwEventUnregister (deadbeef) stub. err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, (nil) 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 (nil) 0x33f7a8) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, 0x179d50 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 0x179d50 0x33f7a8) returning a dummy value (current locale) fixme:winsock:WSALookupServiceBeginW (0x33f4b8 0x00000ff0 0x33f4f4) Stub! fixme:iphlpapi:NotifyAddrChange (Handle 0x33f638, overlapped 0x17af84): stub fixme:win:RegisterDeviceNotificationW (hwnd=0x80090, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterDeviceNotificationW (hwnd=0x80090, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:EnumDisplayDevicesW ((null),0,0x33f114,0x00000000), stub! fixme:ver:GetCurrentPackageId (0x2f3dfa4 (nil)): stub fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:dwmapi:DwmExtendFrameIntoClientArea (0x5010e, 0x33e69c) stub fixme:ntdll:EtwEventRegister ({47a9201e-73b0-42ce-9821-7e134361bc6f}, 0x100772c0, 0x100ed0e0, 0x100ed0d8) stub. fixme:ntdll:EtwEventRegister ({58a9201e-73b0-42ce-9821-7e134361bc70}, 0x100772c0, 0x100ed118, 0x100ed110) stub. fixme:ntdll:EtwEventRegister ({3fa9201e-73b0-43fe-9821-7e145359bc6f}, 0x100772c0, 0x100ed0a8, 0x100ed0a0) stub. fixme:ntdll:EtwEventRegister ({1432afee-73b0-42ce-9821-7e134361b433}, 0x100772c0, 0x100ed150, 0x100ed148) stub. fixme:ntdll:EtwEventRegister ({4372afee-73b0-42ce-9821-7e134361b519}, 0x100772c0, 0x100ed188, 0x100ed180) stub. fixme:imm:ImmGetOpenStatus (0x166778): semi-stub fixme:ver:GetCurrentPackageId (0x33f03c (nil)): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:system:SetProcessDPIAware stub! thomthomthom@thomthomthom:/usr/src/wine$ fixme:win:EnumDisplayDevicesW ((null),0,0x33f44c,0x00000000), stub! fixme:win:EnumDisplayDevicesW (L"\\\\.\\DISPLAY1",0,0x33f44c,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),1,0x33f44c,0x00000000), stub! fixme:imm:ImmReleaseContext (0x5012a, 0x206788): stub fixme:win:EnumDisplayDevicesW ((null),0,0x33f644,0x00000000), stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8A8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, 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 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B5G6R5_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B5G5R5A1_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, 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 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8A8_UNORM, dst_format WINED3DFMT_B5G6R5_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM, dst_format WINED3DFMT_B5G6R5_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B10G10R10A2_UNORM, dst_format WINED3DFMT_B5G6R5_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B5G6R5_UNORM, dst_format WINED3DFMT_B5G6R5_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B5G5R5A1_UNORM, dst_format WINED3DFMT_B5G6R5_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B5G5R5X1_UNORM, dst_format WINED3DFMT_B5G6R5_UNORM stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33ef94,0x00000000), stub! fixme:d3d9:wined3dformat_from_d3dformat Unhandled D3DFORMAT 0xffffffff. fixme:d3d9:wined3dformat_from_d3dformat Unhandled D3DFORMAT 0xffffffff. fixme:d3d9:wined3dformat_from_d3dformat Unhandled D3DFORMAT 0xffffffff. fixme:d3d9:wined3dformat_from_d3dformat Unhandled D3DFORMAT 0xffffffff. fixme:d3d9:wined3dformat_from_d3dformat Unhandled D3DFORMAT 0xffffffff. fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT! fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. fixme:win:RegisterDeviceNotificationW (hwnd=0xd00e0, filter=0x33eeb4,flags=0x00000004) returns a fake device notification handle! thomthomthom@thomthomthom:/usr/src/wine$ fixme:system:SystemParametersInfoW Unknown action: 116 fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB! fixme:win:RegisterDeviceNotificationW (hwnd=0x5012a, filter=0x33fb40,flags=0x00000004) returns a fake device notification handle! fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB! fixme:win:RegisterDeviceNotificationW (hwnd=0x5012a, filter=0x33fc18,flags=0x00000004) returns a fake device notification handle! fixme:win:RegisterTouchWindow (0x5012a 00000000): stub thomthomthom@thomthomthom:/usr/src/wine$ fixme:ver:GetCurrentPackageId (0x1c7eea08 (nil)): stub fixme:ver:GetCurrentPackageId (0x2061ea08 (nil)): stub fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x1c7ee994): stub fixme:win:RegisterDeviceNotificationW (hwnd=0x5012a, filter=0x31c3f098,flags=0x00000000) returns a fake device notification handle! fixme:ntdll:EtwRegisterTraceGuidsW (0x6f424d0, 0x6f4d708, {7c830ece-5fb3-417a-a1bd-508f45277356}, 1, 0x33e654, (null), (null), 0x6f4d710): stub fixme:ntdll:EtwRegisterTraceGuidsW register trace class {7c830ece-5fb3-417a-a1bd-508f45277356} fixme:ntdll:EtwRegisterTraceGuidsW (0xba624d0, 0xba6d708, {7c830ece-5fb3-417a-a1bd-508f45277356}, 1, 0x33e654, (null), (null), 0xba6d710): stub fixme:ntdll:EtwRegisterTraceGuidsW register trace class {7c830ece-5fb3-417a-a1bd-508f45277356} fixme:ntdll:EtwRegisterTraceGuidsW (0xbb024d0, 0xbb0d6e8, {7c830ece-5fb3-417a-a1bd-508f45277356}, 1, 0x33e654, (null), (null), 0xbb0d6f0): stub fixme:ntdll:EtwRegisterTraceGuidsW register trace class {7c830ece-5fb3-417a-a1bd-508f45277356} fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp:validate_addr64 Unsupported address fffffffff7550000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff72e0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff70f0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff5240000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff5210000 fixme:dbghelp:validate_addr64 Unsupported address ffffffffeba30000 fixme:dbghelp:validate_addr64 Unsupported address ffffffffe4410000 fixme:dbghelp:validate_addr64 Unsupported address ffffffffef420000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff40e0000 fixme:dbghelp:validate_addr64 Unsupported address ffffffffe9840000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff50d0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff4e30000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff50b0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff5090000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff5040000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff5030000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff44a0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff4430000 fixme:dbghelp:validate_addr64 Unsupported address ffffffffdd260000 err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x43b4ad thomthomthom@thomthomthom:/usr/src/wine$ fixme:file:SetFileCompletionNotificationModes 0x294 1 - stub wine: Unhandled exception 0x80000003 in thread 15d at address 0x100aa6d9 (thread 015d), starting debugger... err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:mfplat:MFStartup (65648, 1): stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:gdi:GdiInitializeLanguagePack stub fixme:ntdll:EtwEventUnregister (deadbeef) stub. err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, (nil) 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 (nil) 0x33f7a8) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, 0x179d58 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 0x179d58 0x33f7a8) returning a dummy value (current locale) fixme:winsock:WSALookupServiceBeginW (0x33f4b8 0x00000ff0 0x33f4f4) Stub! fixme:iphlpapi:NotifyAddrChange (Handle 0x33f638, overlapped 0x17af8c): stub fixme:win:RegisterDeviceNotificationW (hwnd=0xa010e, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterDeviceNotificationW (hwnd=0xa010e, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:EnumDisplayDevicesW ((null),0,0x33f114,0x00000000), stub! fixme:ver:GetCurrentPackageId (0x2f3dfa4 (nil)): stub fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETTASKBARPOS, hwnd=(nil)): stub fixme:appbar:SHAppBarMessage unknown msg: 4 fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETSTATE): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=3): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=1): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=0): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=2): 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.

2 4

[Bug 49772] New: Memory safety issues in widl
by WineHQ Bugzilla 22 Jul '23

22 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=49772 Bug ID: 49772 Summary: Memory safety issues in widl Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: kolan_n(a)mail.ru Distribution: --- I have tried to compile some type libraries missing in MinGW-w64 and Wine and ReactOS SDKs too (more precisely, sapiddk.idl) into headers from the files in Windows SDK (used Windows 10 SDK). MinGW-w64 widl has crashed without producing any output, just left some files with garbled filenames (looks like a zero terminator got missing in a C string). So I have built wine widl. It has also crashed, but at least produced some meaningful output. -- 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 8

[Bug 9378] New: CM: Shock Force 'Could not initialize graphics display'
by wine-bugs＠winehq.org 22 Jul '23

22 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=9378 Summary: CM: Shock Force 'Could not initialize graphics display' Product: Wine Version: 0.9.43. Platform: PC URL: http://www.battlefront.com/products/cmsf/downloads.html OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-directx AssignedTo: wine-bugs(a)winehq.org ReportedBy: mailing_list(a)orange.nl After starting Combat Mission: Shock Force Demo it stops with the message: 'Could not initialize graphics display. REQUIRED 1024x768, 32-bit color'. The terminal output doesn't provide any clues: wine 'CM Shock Force DEMO.exe' ALSA lib conf.c:3939:(snd_config_expand) Unknown parameters 0 ALSA lib control.c:910:(snd_ctl_open_noupdate) Invalid CTL default:0 err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element fixme:wave:ALSA_AddCaptureDevice Add support for DSCapture ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 37

[Bug 18889] New: Live Messenger 2008 fails to load - possible actctx problem
by wine-bugs＠winehq.org 22 Jul '23

22 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=18889 Summary: Live Messenger 2008 fails to load - possible actctx problem Product: Wine Version: 1.1.16 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: andras(a)csevego.net Created an attachment (id=21730) --> (http://bugs.winehq.org/attachment.cgi?id=21730) +actctx,+relay log Starting of installed (on windows) Msn 2009 wil result: err:module:import_dll Library MSVCR80.dll (which is needed by L"Z:\\media\\disk\\Program Files\\Windows Live\\Messenger\\msnmsgr.exe") not found err:module:LdrInitializeThunk Main exe initialization for L"Z:\\media\\disk\\Program Files\\Windows Live\\Messenger\\msnmsgr.exe" failed, status c0000135 Same load failure, when I manually install with wine (from msi packages) MSVCRT 8.0 is installed, as shown attached +actctx,+relay log I suspect here an Activation Context failure. -- 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 106

[Bug 35866] New: AvP 2000 game: some ingame text has red boxes around it
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=35866 Bug ID: 35866 Summary: AvP 2000 game: some ingame text has red boxes around it Product: Wine Version: 1.7.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bob.mt.wya(a)gmail.com Created attachment 47886 --> http://bugs.winehq.org/attachment.cgi?id=47886 In game HUD : red boxes Using the Steam version of Aliens Vs Predator Classic (2000). Some ingame text has red boxes around each individual character. Appears under both recent Nvidia (proprietary) and AMD radeon (kernel) drivers. I didn't even notice this glitch before. But having booted into Windows 7 to double check... The red boxes are not present when the game is run natively under Windows. I don't see anything of significance in the console log when I launch AvP manually (with Steam running in the same 64-bit Wineprefix). Any thoughts if this is low hanging fruit to fix? Thanks Robert -- 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 46221] New: League of Legends 8.23 crash after champion select
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=46221 Bug ID: 46221 Summary: League of Legends 8.23 crash after champion select Product: Wine Version: 3.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lollinos(a)hotmail.com Distribution: --- i think it's the same error about anti-cheat lol had last patches. After Champion select end, game crash with message: "A critical error has occurred and the process must be terminated. Would you liek to create a crash dump to aid the developers in troubleshooting this issue? This may take up to 5 minutes. NOYE: The process may appear unresponsive during this time. [YES] [NO]". Steps: - WINEPREFIX=~/.wine WINEARCH=win32 wine winecfg - WINEPREFIX=~/.wine WINEARCH=win32 wine winetricks --gui, set to true capture mouse, virtual Desktop and Windows version to XP (I've tried with 7-10 too) - wineboot -u, winetricks -q d3dx9 - cd .wine/drive_c/, ln -s ~/path/lol-installer.exe - wine start lol-installer.exe - wine reg add 'HKEY_CURRENT_USER\Software\Wine\DllOverrides' /v 'msvcp140' /t 'REG_SZ' /d 'native,builtin' /f - wine reg add 'HKEY_CURRENT_USER\Software\Wine\DllOverrides' /v 'wininet' /t 'REG_SZ' /d 'builtin,native' /f - wine start 'C:\Riot Games\League of Legends\LeagueClient.exe' I tried a lot of settings, but i cant make it works after champion select. Some way to fix this bug? ii wine-staging 3.21.0~stretch amd64 WINE Is Not An Emulator - runs MS Windows programs ii wine-staging-amd64 3.21.0~stretch amd64 WINE Is Not An Emulator - runs MS Windows programs ii wine-staging-i386:i386 3.21.0~stretch i386 WINE Is Not An Emulator - runs MS Windows programs ii winehq-staging 3.21.0~stretch amd64 WINE Is Not An Emulator - runs MS Windows programs ii winetricks 0.0+20170101-1 all package manager for Wine to install software easily -- 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 35690] New: Steam network hang ups.
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=35690 Bug ID: 35690 Summary: Steam network hang ups. Product: Wine Version: 1.7.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hellsy22(a)gmail.com Created attachment 47657 --> http://bugs.winehq.org/attachment.cgi?id=47657 Installing and using steam Unpredictable hangups while establishing connection for downloading updates, loggining in, downloading games, etc. There are no problems with network for everything except wine/Steam. Win Steam works perfect, all other services - too. -- 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 18

[Bug 45042] New: Steam doesn't uninstall applications, gets stuck saying " deleting %app" until next popup isn't very visible
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=45042 Bug ID: 45042 Summary: Steam doesn't uninstall applications, gets stuck saying "deleting %app" until next popup isn't very visible Product: Wine Version: 3.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: romulasry(a)gmail.com Distribution: --- Created attachment 61171 --> https://bugs.winehq.org/attachment.cgi?id=61171 wine log It is nearly impossible to delete steam applications when you right click then select uninstall. -- 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 41466] New: Steam: Tray icon menu sometimes flickers
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=41466 Bug ID: 41466 Summary: Steam: Tray icon menu sometimes flickers Product: Wine Version: 1.9.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sworddragon2(a)aol.com Distribution: --- Created attachment 55847 --> https://bugs.winehq.org/attachment.cgi?id=55847 Terminal output On starting Steam, making a right click on the tray icon and clicking on "Setings" instead of vanishing most times the tray icon menu gets black and begins to flicker. This behavior disappears as soon as the mouse cursor is moved. In the attachments is the terminal output where this issues happened. -- 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 44529] New: [Steam] Process remaining after exiting
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=44529 Bug ID: 44529 Summary: [Steam] Process remaining after exiting Product: Wine Version: 3.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maxi.cass11(a)gmail.com Distribution: --- Created attachment 60483 --> https://bugs.winehq.org/attachment.cgi?id=60483 wine 3.1 terminal output When I close steam with the tray icon, a steam process is still her and use 14% of the CPU. I have attached the console output when I leave steam, I don't know how can I give more relevant information. -- 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 24614] New: Medieval Total War crashes on startup
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=24614 Summary: Medieval Total War crashes on startup Product: Wine Version: 1.2 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 AssignedTo: wine-bugs(a)winehq.org ReportedBy: th.seltsam(a)gmail.com CC: wine-bugs(a)winehq.org Running the game just shows a black window, no crash dialog, and an infinite console output err:d3dx:assemble-shader Asm reading failed err:d3dx:assemble-shader Asm reading failed err:d3dx:assemble-shader Asm reading failed err:d3dx:assemble-shader Asm reading failed Using d3dx9-36 did not solve the 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 27

[Bug 49371] New: Incorrect output buffer length check in WSAIoctl with SIO_GET_INTERFACE_LIST
by WineHQ Bugzilla 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=49371 Bug ID: 49371 Summary: Incorrect output buffer length check in WSAIoctl with SIO_GET_INTERFACE_LIST Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: j.g.rennison(a)gmail.com Distribution: --- The output buffer length check in the implementation of the SIO_GET_INTERFACE_LIST ioctl in WSAIoctl is not correct. In the event that there are more interfaces than the supplied buffer is sized for, this can result in output data being written beyond the end of the supplied buffer and no error returned. This can cause undefined behaviour such as crashes, etc. With reference to line 4796 in dlls/ws2_32/socket.c https://github.com/wine-mirror/wine/blob/343043153b44fa46a2081fa8a2c171eac7… if ((numInt + 1)*sizeof(INTERFACE_INFO)/sizeof(IP_ADAPTER_INFO) > out_size) should instead be if ((numInt + 1)*sizeof(INTERFACE_INFO) > out_size) This because the output buffer write pointer intArray is of type INTERFACE_INFO*, and numInt is the index relative to the start of the output buffer, not the size returned from GetAdaptersInfo. The bug appears to have been introduced in commit a239e8ed. https://github.com/wine-mirror/wine/commit/a239e8ed27b1c3cde6bc568c3d7b9996… -- 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 45564] New: Kolab E14 Client installation fails with "Copy failed"
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=45564 Bug ID: 45564 Summary: Kolab E14 Client installation fails with "Copy failed" Product: Wine Version: 3.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- Created attachment 61987 --> https://bugs.winehq.org/attachment.cgi?id=61987 Install log with WINEDEBUG=+ntdll,+commctl The installation of the Kolab E14 Client (Groupware based on KDE) fails with "Copy failed" and aborts. The install log including the generation of the Message "Copy failed" is attached. Wine is self-compiled with the patch from bug #45552 created by Fabian Maurer. -- 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 44223] New: FrameMaker 7.2: Console window minimized and not (re) drawn
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=44223 Bug ID: 44223 Summary: FrameMaker 7.2: Console window minimized and not (re)drawn Product: Wine Version: 3.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- When opening a file in FrameMaker 7.2 which has errors (i.e. missing font, missing cross references), a message window ("Framemaker console", text window with its own window manager decoration) is opened and a message box is created. When this happens the message window is drawn with the least possible size (to allow only the window manager icons to appear) and when enlarging it, its content is not drawn (the content pane shows the content of the underlying window). The message windows content is therefor not readable. Sometimes (not always) the dialog box and the message window are only shown in the panel and are not shown at all (which may be a window manager problem, cannot judge). Any hint to give more helpful details is welcome. -- 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 6

[Bug 47328] New: Steam crashes when loading the Store tab ( Assertion Failed: killing unresponsive browser for URL)
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=47328 Bug ID: 47328 Summary: Steam crashes when loading the Store tab (Assertion Failed: killing unresponsive browser for URL) Product: Wine Version: 4.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jeffersoncarpenter2(a)gmail.com Distribution: --- Created attachment 64652 --> https://bugs.winehq.org/attachment.cgi?id=64652 Console output running Steam.exe under wine Steps to reproduce: Install Steam. Run and visit store tab. Expected behavior: Steam loads store tab Actual behavior: Steam hangs for 40 seconds, then crashes. Attached is the console output. Samba is installed, as well as allfonts via winetricks. This should not be a duplicate of 30202 or 29230 since the first is closed as fixed (and I installed allfonts), and the second has a different error in the console output. -- 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 7

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