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

[Bug 45039] New: Mono: System.UnauthorizedAccessException when trying to read from stdin when both stdout and stderr are redirected
by wine-bugs＠winehq.org Dec. 2, 2025

Dec. 2, 2025

https://bugs.winehq.org/show_bug.cgi?id=45039 Bug ID: 45039 Summary: Mono: System.UnauthorizedAccessException when trying to read from stdin when both stdout and stderr are redirected Product: Wine Version: 3.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mk+winehq1803(a)pimpmybyte.de Distribution: --- I wrote a simple C# program that reads a line from stdin and prints it in uppercase (01_shout.cs in [1]). The exe (compiled on Ubuntu with "mcs") is available for download at http://l.proggr.de/?1839m7ier It accepts interactive input when run in cmd.exe on windows 7, even with both stdout and stderr redirected (02_log_win7.txt in [1]). In Ubuntu, it crashes when trying to read the line while stdin is a TTY and both stdout and stderr are redirected (03_log_wine.txt in [1]). Ubuntu 14.04.5 LTS trusty, wine-3.6, Mono JIT compiler version 3.2.8 (Debian 3.2.8+dfsg-4ubuntu1.1) Kernel 3.13.0-142-generic #191-Ubuntu SMP Fri Feb 2 12:14:37 UTC 2018 i686 i686 i686 GNU/Linux [1] https://gist.github.com/mk-pmb/adae211e875ff11274d9b81248d033a3 -- 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 44840] New: Icewind Dale unusably glitchy starting with Wine Version 3.2
by wine-bugs＠winehq.org Dec. 2, 2025

Dec. 2, 2025

https://bugs.winehq.org/show_bug.cgi?id=44840 Bug ID: 44840 Summary: Icewind Dale unusably glitchy starting with Wine Version 3.2 Product: Wine Version: 3.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wodencafe(a)gmail.com Distribution: --- Starting with Wine 3.2 and on, Icewind Dale (2.0.0.11 (GOG)) is having very strange input / glitchy rendering issues. I have attached a video comparison with 3.1 where it works fine. Tested with 3.2, 3.3, and 3.4, and all have the strange input and glitchy problem. There are no additional wine modifications. Please see the video for example of problem, and comparison of when it was working with 3.1 -- 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 21

[Bug 30853] New: Wine doesn’t always handle "right alt" properly
by wine-bugs＠winehq.org Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=30853 Bug #: 30853 Summary: Wine doesn’t always handle "right alt" properly Product: Wine Version: 1.5.5 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: sloonz(a)gmail.com Classification: Unclassified Created attachment 40410 --> http://bugs.winehq.org/attachment.cgi?id=40410 workaround/quick and dirty fix I’m trying to get World of Warcraft working under Wine. However, I have huge trouble with key bindings (I use unusual key bindings : I use the right half of my keyboard, whereas most players use the left half). After investigation, I found 3 bugs (different behaviors between Wine and my Windows installation). The first one is the management of the right "Alt" key (labeled "Alt-Gr" on my keyboard). When I press AltGr+l under Windows with Spy++, I get the followings events : <03637> 0007045A P WM_KEYDOWN nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:0 fRepeat:0 fUp:0 <03638> 0007045A P WM_KEYDOWN nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:1 fRepeat:0 fUp:0 <03639> 0007045A P WM_KEYDOWN nVirtKey:'L' cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:0 fUp:0 <03640> 0007045A P WM_DEADCHAR chCharCode:'002F' (47) cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:0 fUp:0 <03641> 0007045A P WM_KEYUP nVirtKey:'L' cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:1 fUp:1 <03642> 0007045A P WM_SYSKEYUP nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:1 fRepeat:1 fUp:1 <03643> 0007045A P WM_KEYUP nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:0 fRepeat:1 fUp:1 Under Wine 1.5.5 however (WINEDEBUG=+msg), I get those : trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x6007e wp eb lp 760001 [note: wp = VK_OEM_PA2] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp 4c lp c0260001 [note: wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp eb lp c0760001 [note: wp = VK_OEM_PA2] With xev, I get : KeyPress event, serial 93, synthetic NO, window 0x4000001, root 0xbc, subw 0x0, time 5086996, (1585,410), root:(2578,425), state 0x0, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 93, synthetic NO, window 0x4000001, root 0xbc, subw 0x0, time 5087052, (1585,410), root:(2578,425), state 0x80, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False After "setxkbmap us", AltGr is bound to Alt_R under X (checked with xev), and I get this under Wine : trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp a5 lp 21380001 [wp = VK_RMENU] trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp 4c lp 20260001 [wp = 'L'] trace:msg:peek_message got type 6 msg 106 (WM_SYSCHAR) hwnd 0x10046 wp 6c lp 20260001 [wp = 'l'] trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10046 wp 4c lp e0260001 [wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10046 wp a5 lp c1380001 [wp = VK_RMENU] (yes, I have a KEYUP without KEYDOWN) Wich is still not the same as Windows. So I think there is two problems here : - ISO_Level3_Shift is not properly recognized by Wine - "AltGr" doesn't have the same behavior under Wine and Windows FYI, attached patch is a workaround to have the same behavior than Windows. With it, I get this under Wine : trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a2 lp 1d0001 [note: wp = VK_LCONTROL] trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a4 lp 20380001 [note: wp = VK_LMENU] trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp 4c lp 20260001 [note: wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp 4c lp e0260001 trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10062 wp a2 lp e01d0001 trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp a4 lp c0380001 Which is still not the same as Windows : - Windows uses (right) control + menu (with fExtended flag for menu) whereas Wine uses left control + left menu. Not investigated if this is related to TranslateMessage. - AltGr+L is a dead symbol on my keymap. Windows send a DEADCHAR message, wheras Wine send nothing. Note that I had to disable the XFilterEvent test in event.c to have those messages, otherwise nothing is sent to the program (but that’s another story for another bug report) But it suffice for my use case (WoW key bindings with right alt) -- 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 45063] New: win64 / 64-bit .NET 4.0 - c0000005 from ntdll: RtlGetDaclSecurityDescriptor
by wine-bugs＠winehq.org Nov. 28, 2025

Nov. 28, 2025

https://bugs.winehq.org/show_bug.cgi?id=45063 Bug ID: 45063 Summary: win64 / 64-bit .NET 4.0 - c0000005 from ntdll:RtlGetDaclSecurityDescriptor Product: Wine Version: 3.6 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: pembertona(a)gmail.com After fighting for some to get .NET 4.0 running on 64 bit (great progress here after overcoming multiple msi/msiexec/installer issues), I've hit an access violation exception running a very basic 'hello world' 64-bit console app. This is on `portable-winehq-staging-3.6-osx64` - but almost certainly the devel and stable branches as well. 136984.882:0008:0041:Call advapi32.ConvertStringSecurityDescriptorToSecurityDescriptorW(19e1f7f8 L"D:P(A;;GRGW;;;BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)",00000001,19e1f780,19e1f7c8) ret=6447f2c4d3e 136984.884:0008:0041:trace:advapi:ConvertStringSecurityDescriptorToSecurityDescriptorW L"D:P(A;;GRGW;;;BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)", 1, 0x19e1f780, 0x19e1f7c8 136984.884:0008:0041:trace:heap:RtlAllocateHeap (0x10000,70000062,00000062): returning 0xf60b0 136984.885:0008:0041:trace:advapi:ParseStringAclToAcl L"P(A;;GRGW;;;BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)" 136984.885:0008:0041:trace:advapi:ParseStringSidToSid L"BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)", 0x0, 0x19e1f514 136984.885:0008:0041:trace:advapi:ParseStringSidToSid only size requested, returning TRUE with 16 136984.885:0008:0041:trace:advapi:ParseStringSidToSid L"S-1-5-21-0-0-0-1000)", 0x0, 0x19e1f514 136984.885:0008:0041:trace:advapi:ParseStringSidToSid only size requested, returning TRUE with 28 136984.885:0008:0041:trace:heap:RtlFreeHeap (0x10000,70000062,0xf60b0): returning TRUE 136984.886:0008:0041:trace:heap:RtlAllocateHeap (0x10000,7000006a,00000058): returning 0x46340 136984.886:0008:0041:trace:heap:LocalAlloc (flags=0040) returning 0x46340 136984.886:0008:0041:trace:heap:RtlAllocateHeap (0x10000,70000062,00000062): returning 0x46420 136984.886:0008:0041:trace:advapi:ParseStringAclToAcl L"P(A;;GRGW;;;BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)" 136984.886:0008:0041:trace:advapi:ParseStringSidToSid L"BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)", 0x46364, 0x19e1f514 136984.886:0008:0041:trace:advapi:ParseStringSidToSid returning TRUE 136984.886:0008:0041:trace:advapi:ParseStringSidToSid L"S-1-5-21-0-0-0-1000)", 0x4637c, 0x19e1f514 136984.886:0008:0041:trace:advapi:ParseStringSidToSid returning TRUE 136984.887:0008:0041:trace:heap:RtlFreeHeap (0x10000,70000062,0x46420): returning TRUE 136984.887:0008:0041:trace:advapi:ConvertStringSecurityDescriptorToSecurityDescriptorW ret=1 136984.887:0008:0041:Ret advapi32.ConvertStringSecurityDescriptorToSecurityDescriptorW() retval=00000001 ret=6447f2c4d3e 136984.887:0008:0041:Call ntdll.RtlFreeHeap(00010000,00000000,000f5f30) ret=6447f2c4dc8 136984.887:0008:0041:trace:heap:RtlFreeHeap (0x10000,70000062,0xf5f30): returning TRUE 136984.887:0008:0041:Ret ntdll.RtlFreeHeap() retval=00000001 ret=6447f2c4dc8 136984.887:0008:0041:trace:ntdll:RtlGetSaclSecurityDescriptor (0x46340,0x19e1f716,0x19e1f718,0x19e1f715) 136984.887:0008:0041:trace:ntdll:RtlGetDaclSecurityDescriptor (0x46340,0x19e1f717,0x19e1f720,0x19e1f715) 136984.887:0008:0041:trace:heap:RtlAllocateHeap (0x10000,7000006a,0000009c): returning 0x46570 136984.888:0008:0041:trace:heap:RtlFreeHeap (0x10000,70000062,0x46570): returning TRUE 136984.888:0008:0041:trace:seh:NtRaiseException code=c0000005 flags=0 addr=0x6447f1d6f19 ip=6447f1d6f19 tid=0041 136984.888:0008:0041:trace:seh:NtRaiseException info[0]=0000000000000000 136984.888:0008:0041:trace:seh:NtRaiseException info[1]=0000000000000010 136984.888:0008:0041:trace:seh:NtRaiseException rax=0000000000000000 rbx=000006447f27fd30 rcx=0000000019e1fce0 rdx=0000000019e21ad0 136984.888:0008:0041:trace:seh:NtRaiseException rsi=0000000019e1fce0 rdi=0000000000000000 rbp=0000000019e1fe00 rsp=0000000019e1fc20 136984.888:0008:0041:trace:seh:NtRaiseException r8=0000000019e1f298 r9=0000000000000010 r10=0000000019e21b25 r11=ffffffffffffffa9 136984.888:0008:0041:trace:seh:NtRaiseException r12=0000000000000000 r13=0000000000000000 r14=0000000000044860 r15=0000000000000000 136984.888:0008:0041:trace:seh:call_vectored_handlers calling handler at 0x6447f30a954 code=c0000005 flags=0 ... 136984.967:0008:0041:err:eventlog:ReportEventW L"Application: Console64.exe\nFramework Version: v4.0.30319\nDescription: The process was terminated due to an internal error in the .NET Runtime at IP 000006447F1D6F19 (000006447F100000) with exit code 80131506.\n" Possibly related to https://bugs.winehq.org/show_bug.cgi?id=27680? -- 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 22

[Bug 41644] New: Civilization v1.2: crashes on startup
by wine-bugs＠winehq.org Nov. 28, 2025

Nov. 28, 2025

https://bugs.winehq.org/show_bug.cgi?id=41644 Bug ID: 41644 Summary: Civilization v1.2: 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: K_ThaaL(a)bk.ru Distribution: --- Created attachment 56018 --> https://bugs.winehq.org/attachment.cgi?id=56018 trace generated by wine Wine crashes right after the first frame of game intro is shown. Created a new 32bit wine prefix for this game. Tried windows versions XP and 3.1 - behavior is the same in both cases. Using virtual desktop and disallowing window decorations did not help. No other options tried. Ubuntu 16.04 LTS is used with Wine installed from winehq repository. Problem is detected on 1.9.21 and 1.9.22. -- 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 42792] New: SQL Server 2012/2014: Installer requires ChangeServiceConfig2 with SERVICE_CONFIG_SERVICE_SID_INFO support
by wine-bugs＠winehq.org Nov. 28, 2025

Nov. 28, 2025

https://bugs.winehq.org/show_bug.cgi?id=42792 Bug ID: 42792 Summary: SQL Server 2012/2014: Installer requires ChangeServiceConfig2 with SERVICE_CONFIG_SERVICE_SID_INFO support Product: Wine Version: 2.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: pgkos.bugzilla(a)yahoo.com Distribution: ArchLinux Currently, during the installation of SQL Server 2012 or 2014, the setup fails during the configuration of the SqlWriter component, because ChangeServiceConfig2 (svcctl_ChangeServiceConfig2W) does not implement SERVICE_CONFIG_SERVICE_SID_INFO. Relevant part of SqlWriter_Cpu32_1.log: Doing Action: Do_sqlServiceSidType PerfTime Start: Do_sqlServiceSidType : Sun Apr 09 11:15:55 2017 <Func Name='Do_sqlServiceSidType'> SQLWriter Configuring service: Name: SQLWriter SID type: 0x1 Failed: Unable to set the SID type for service SQLWriter to 1. Error code: 124. Error Code: 0x80077377 (29559) Windows Error Text: Source File Name: sqlca\sqlsddlca.cpp Compiler Timestamp: Fri Feb 10 17:29:21 2012 Function Name: ExceptionInSDDL Source Line Number: 65 Error Code: 29559 1: 29559 2: SQLWriter 3: pgkos <Failure Type='Fatal' Error='29559'> <EndFunc Name='LaunchFunction' Return='29559' GetLastError='0'> 1: 29528 2: Setting Service SID Type 3: Installation failed. -- 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 44948] New: fixme:file:CreateSymbolicLinkW() is not implemented
by wine-bugs＠winehq.org Nov. 28, 2025

Nov. 28, 2025

https://bugs.winehq.org/show_bug.cgi?id=44948 Bug ID: 44948 Summary: fixme:file:CreateSymbolicLinkW() is not implemented Product: Wine Version: 3.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: phaidros(a)gmx.at Distribution: --- Spine is a Mod-starter for Gothic which supports easy patching and installation of Mods. It uses CreateSymbolicLinkW() to copy files into the game directory. This function is not implemented 005e:fixme:file:CreateSymbolicLinkW (L"C:/games/Gothic-Spine/system/GothicGame.ini" L"C:/users/gottfried/Application Data/Clockwork Origins/Spine/mods/37/system/GothicGame.ini" 0): stub hence the game cannot be started via Spine, it crashes with an access violation. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 29

[Bug 41034] New: TomTom MyDrive Connect needs implementation of KERNEL32.dll.SetVolumeMountPointW and others
by wine-bugs＠winehq.org Nov. 28, 2025

Nov. 28, 2025

https://bugs.winehq.org/show_bug.cgi?id=41034 Bug ID: 41034 Summary: TomTom MyDrive Connect needs implementation of KERNEL32.dll.SetVolumeMountPointW and others Product: Wine Version: 1.9.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: h.mth(a)web.de Distribution: --- Created attachment 55207 --> https://bugs.winehq.org/attachment.cgi?id=55207 snipped of application log Starting TomTom MyDrive Connect with Wine 1.9.15 its tray icon appears. Though, left-, right- and double-click will not present its context(drop-down) menu. Attached is a snipped of the application log. The application tries to mount a volume at 'E:\', then queries NotifyAddrChange multiple times and finally retries to mount volume again. This goes on endlessly. -- 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 36

[Bug 16882] New: WMI core 1.5 installation hangs (needed for .NET 3.0 installer, WCF part), SECURITY_SERVICE_RID missing from service token group
by wine-bugs＠winehq.org Nov. 27, 2025

Nov. 27, 2025

http://bugs.winehq.org/show_bug.cgi?id=16882 Summary: WMI core 1.5 installation hangs (needed for .NET 3.0 installer, WCF part), SECURITY_SERVICE_RID missing from service token group Product: Wine Version: 1.1.12 Platform: Other URL: http://www.microsoft.com/downloads/details.aspx?familyid =AFE41F46-E213-4CBF-9C5B-FBF236E0E875 OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: advapi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, after getting past bug 16879 one encounters this one. ---- Prerequisite: 1. clean WINEPREFIX 2. sh winetricks -q dotnet20 3. download .NET 3.0 Framework installer from: http://download.microsoft.com /download/4/d/a/4da3a5fa-ee6a-42b8-8bfa-ea5c4a458a7d/dotnetfx3setup.exe (sha1sum: a566bcd2ffffc3842a95adc57f7df3f8cd11577f) 4. export _SFX_CAB_SHUTDOWN_REQUEST=1 (workaround, see bug 9158) 5. wine ./dotnetfx3setup.exe It might take a while until all required packages are downloaded using BITS. Note: If you need to redo steps, backup the directory "dotnetfx304506.30" from "c:\\windows\\temp" to a different location, remove ~/.wine, copy "dotnetfx304506.30" again to "c:\\windows\\temp" to prevent BITS from downloading over and over again. ---- "c:\\windows\\temp\\dd_dotnetfx3error.txt": --- snip --- [01/11/09,12:50:20] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603 [01/11/09,12:50:31] WapUI: [2] DepCheck indicates Windows Communication Foundation is not installed. [01/11/09,12:50:31] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed. --- snip --- "c:\\windows\\temp\\dd_wcf_retMSI597F.txt": --- snip --- 1: C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe /r /x /y /v 2: 1: ERROR: Process returned non-0 value! CMDLINE: C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe /r /x /y /v 2: 1: Failed 2: --- snip --- and "c:\\windows\\temp\\dd_wcf_retCA69A1.txt": --- snip --- === Verbose logging started: 1/11/2009 12:50:17 Calling process: C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe === ServiceModelReg [12:50:18:302]: Warning: Could not detect IIS installation or IIS is disabled, skipping the Web Host Script Mappings component since it depends upon IIS to function properly. If you believe this message is an error, check your IIS installation to make sure it is installed properly. ServiceModelReg [12:50:18:329]: Information: The ServiceModelReg tool will take the following actions: Reinstalling configuration section system.serviceModel to C:\windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config. Reinstalling configuration section system.runtime.serialization to C:\windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config. Reinstalling configuration section system.serviceModel.activation to C:\windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config. Adding configuration entry for BuildProvider: System.ServiceModel.Activation.ServiceBuildProvider, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Reinstalling compilation assembly node to System.Web section group: System.Runtime.Serialization, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL Reinstalling compilation assembly node to System.Web section group: System.IdentityModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitectur... ServiceModelReg [12:50:18:358]: Uninstalling: Machine.config Section Groups and Handlers ServiceModelReg [12:50:18:366]: Warning: Configuration section system.serviceModel does not exist in C:\windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config. ServiceModelReg [12:50:18:369]: Warning: Configuration section system.runtime.serialization does not exist in C:\windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config. ServiceModelReg [12:50:18:373]: Warning: Configuration section system.serviceModel.activation does not exist in C:\windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config. ServiceModelReg [12:50:18:374]: Installing: Machine.config Section Groups and Handlers ServiceModelReg [12:50:18:893]: Uninstalling: System.Web Build Provider ServiceModelReg [12:50:19:095]: Warning: A configuration entry for BuildProvider System.ServiceModel.Activation.ServiceBuildProvider, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 does not exist. ServiceModelReg [12:50:19:096]: Installing: System.Web Build Provider ServiceModelReg [12:50:19:138]: Uninstalling: System.Web Compilation Assemblies ServiceModelReg [12:50:19:153]: Warning: All compilation assembly nodes do not exist in System.Web section group. ServiceModelReg [12:50:19:154]: Installing: System.Web Compilation Assemblies ServiceModelReg [12:50:19:246]: Uninstalling: HTTP Handlers ServiceModelReg [12:50:19:260]: Warning: HttpHandlers node *.svc does not exist in System.Web section group. ServiceModelReg [12:50:19:261]: Installing: HTTP Handlers ServiceModelReg [12:50:19:322]: Uninstalling: HTTP Modules ServiceModelReg [12:50:19:333]: Warning: HttpModules node ServiceModel does not exist in System.Web section group. ServiceModelReg [12:50:19:334]: Installing: HTTP Modules ServiceModelReg [12:50:19:365]: Repairing: WMI Classes ServiceModelReg [12:50:19:396]: Warning: Failure executing "C:\windows\system32\wbem\mofcomp.exe" with parameters ""C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModel.mof"": System.IO.FileNotFoundException: Could not load file or assembly 'C:\windows\system32\wbem\mofcomp.exe' or one of its dependencies. Exception from HRESULT: 0x80070002 File name: 'C:\windows\system32\wbem\mofcomp.exe' at System.ServiceModel.Install.InstallHelper.ExecuteWaitHelper(String program, String parameters) at System.ServiceModel.Install.InstallHelper.ExecuteWait(String program, String parameters, Int32[] allowedExitCodes) at System.ServiceModel.Install.WmiInstallComponent.OnInstall(OutputLevel outputLevel) ServiceModelReg [12:50:19:516]: System.InvalidCastException: Retrieving the COM class factory for component with CLSID {4590F811-1D3A-11D0-891F-00AA004B2E24} failed due to the following error: 80004002. at System.Management.ManagementScope.InitializeGuts(Object o) at System.Management.ManagementScope.Initialize() at System.Management.ManagementScope.Connect() at System.ServiceModel.Install.WmiInstallComponent.get_IsInstalled() at System.ServiceModel.Install.WmiInstallComponent.ApplyNamespaceDacl(OutputLevel outputLevel) at System.ServiceModel.Install.WmiInstallComponent.OnInstall(OutputLevel outputLevel) at System.ServiceModel.Install.WmiInstallComponent.Reinstall(OutputLevel outputLevel) at Microsoft.Tools.ServiceModel.ServiceModelReg.PerformAction(ActionItem actionItem, Nullable`1 confirmUninstall) at Microsoft.Tools.ServiceModel.ServiceModelReg.Run(String[] args) at Microsoft.Tools.ServiceModel.ServiceModelReg.TryRun(String[] args) === Verbose logging stopped: 1/11/2009 12:50:19 === --- snip --- Oh joy ... WMI. Providing fake mofcomp.exe (returning success) is not enough, WCF installer will try *use* WMI hence there needs to be some working infrastructure: --- snip --- ServiceModelReg [19:37:29:832]: Starting tool 'C:\windows\system32\wbem\mofcomp.exe' with parameters '"C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModel.mof"'. ServiceModelReg [19:37:29:895]: ServiceModelReg [19:37:29:896]: ServiceModelReg [19:37:29:897]: Tool 'C:\windows\system32\wbem\mofcomp.exe' with parameters '"C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModel.mof"' exited with code '0'. ServiceModelReg [19:37:29:955]: System.InvalidCastException: Retrieving the COM class factory for component with CLSID {4590F811-1D3A-11D0-891F-00AA004B2E24} failed due to the following error: 80004002. at System.Management.ManagementScope.InitializeGuts(Object o) at System.Management.ManagementScope.Initialize() at System.Management.ManagementScope.Connect() at System.ServiceModel.Install.WmiInstallComponent.get_IsInstalled() at System.ServiceModel.Install.WmiInstallComponent.ApplyNamespaceDacl(OutputLevel outputLevel) at System.ServiceModel.Install.WmiInstallComponent.OnInstall(OutputLevel outputLevel) at System.ServiceModel.Install.WmiInstallComponent.Reinstall(OutputLevel outputLevel) at Microsoft.Tools.ServiceModel.ServiceModelReg.PerformAction(ActionItem actionItem, Nullable`1 confirmUninstall) at Microsoft.Tools.ServiceModel.ServiceModelReg.Run(String[] args) at Microsoft.Tools.ServiceModel.ServiceModelReg.TryRun(String[] args) === Verbose logging stopped: 1/8/2009 19:37:29 === --- snip --- This is a big blocker and getting WMI to work with Wine is imperative for .NET 3.0 and higher. Of course this also useful for older .NET Frameworks Roll-back, prepare clean WINEPREFIX again;-) We need to install native WMI core 1.5 from: http://www.microsoft.com/downloads/details.aspx?familyid=AFE41F46-E213-4CBF… Download wmicore http://download.microsoft.com/download/platformsdk/wmicore/1.5/W9XNT4/EN-US… (sha1sum: f7a36668eb6c82a28393637ffdf0ec6e8adfa6a1) Make sure you set winver to NT 4.0 (don't forget to reset to default) and execute the installer (I already have my own winetricks step for this): --- snip --- wine wmicore.exe --- snip --- The installer will then hang at some point "Configuring repository". With winedbg one can see following processes: --- snip --- Wine-dbg>info process pid threads parent executable (all id:s are in hex) 0000000c 5 0000000a 'services.exe' 0000000f 1 0000000a 'explorer.exe' 0000001b 4 0000000c 'winedevice.exe' 00000025 1 00000000 'wmicore.exe' 00000027 2 00000025 'GLBbab.tmp' 00000022 4 0000000c 'WinMgmt.exe' --- snip --- The problem is "WinMgmt.exe" which ought to be a service but due to Wine insufficiency the service thinks it's a normal process not showing usual service process behaviour as registering control handler and the like. If you do 'wineserver -k' and try to start anything with Wine nothing will happen until wineboot times out... As quickfix, start regedit (wait until wineboot timeout) and set service start type key for "WinMgmt" to manual start, e.g. "2" -> "3". Also a kernel driver (service) that is installed with WMI "smbios" fails to load but this currently harmless. If we look now in "c:\\windows\\system32\\WBEM" we see the whole stuff installed. The logs in "logs" subdirs are not revealing much so we have to increase the log level: --- snip --- [HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM] "Logging"="1" "Logging Directory"="C:\\windows\\system32\\WBEM\\Logs" --- snip --- LogLevel is 0 to turn off logging, a 1 to turn on logging, and a 2 for verbose logging. After that, we manually try to start the service: --- snip --- $ wine net start winmgmt err:winedevice:ServiceMain driver L"smbios" failed to load The Windows Management Instrumentation service is starting. fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),2,2,(nil),32,(nil)) - stub! fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),1,3,(nil),0,(nil)) - stub! fixme:advapi:RegisterEventSourceW (L"",L"WinMgmt"): stub wine: Call from 0x7b844f54 to unimplemented function ole32.dll.CoSwitchCallContext, aborting err:rpc:I_RpcReceive we got fault packet with status 0x80000100 fixme:ole:CoCreateInstance no instance created for interface {00000000-0000-0000-c000-000000000046} of class {8bc3f05e-d86b-11d0-a075-00c04fb68820}, hres is 0xc0000005 --- snip --- This is bug 7187 After fixing this problem, we repeat the whole stuff again to get this in logs: --- snip --- (Sun Jan 11 13:41:41 2009) : Starting WinMgmt, ProcID = 26, CmdLine = , User = focht(Sun Jan 11 13:41:41 2009) : WinMgmt bIsService = 0, return code from function determining if service = 0(Sun Jan 11 13:41:41 2009) : WinMgmt gbRunAsApp = 1(Sun Jan 11 13:41:41 2009) : Starting Initialize, ID = 26(Sun Jan 11 13:41:41 2009) : Registered class factory with flags: 0x15 (Sun Jan 11 13:41:41 2009) : RegOpenKey returned 0x2 while trying to open the transports node. Using default transports!(Sun Jan 11 13:41:41 2009) : Initialize complete(Sun Jan 11 13:41:41 2009) : WindowProc got hWnd=20026, message=24, wParam=0, lParam=33f814(Sun Jan 11 13:41:41 2009) : WindowProc got hWnd=20026, message=81, wParam=0, lParam=33fce8(Sun Jan 11 13:41:41 2009) : WindowProc got hWnd=20026, message=83, wParam=0, lParam=33f974(Sun Jan 11 13:41:41 2009) : WindowProc got hWnd=20026, message=1, wParam=0, lParam=33fce8(Sun Jan 11 13:41:41 2009) : Inside the waiting function --- snip --- "WinMgmt bIsService = 0" is the culprit. The process retrieves token information and checks if process token groups contain "SECURITY_INTERACTIVE_RID" (-> normal process) or "SECURITY_SERVICE_RID" (service process). I think it's actually services.exe that adds the SECURITY_SERVICE_RID sid to the newly created service process (token groups). This requires some infrastructure, including wineserver. I already quick-hacked a path to verify this and it works as expected, letting the service successfully start ;-) 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 24

[Bug 24963] New: Okad2: Unhandled page fault at address 0x00007f8a during startup
by wine-bugs＠winehq.org Nov. 26, 2025

Nov. 26, 2025

http://bugs.winehq.org/show_bug.cgi?id=24963 Summary: Okad2: Unhandled page fault at address 0x00007f8a during startup Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: pandolfo(a)gis.net Created an attachment (id=31617) --> (http://bugs.winehq.org/attachment.cgi?id=31617) a description of the page fault plus an annotated backtrace During program startup, Okad2-xx-pd (xx = version) generates an unhandled page fault when loading an icon. The page fault is caused by CreateFileW as it processes the name of the file from the parameter list. The name pointer is 0x00007f8a, which is an address in an unmapped page. This value is also an index into Windows resources, selecting the hourglass icon. What has happened is that the application was attempting to load the hourglass icon and passed in BOTH the Windows resource index and a flag indicating LOADFROMFILE. Wine attempted to load-from-file and looked for the file name through the "name" parameter (0x00007f8a) generating the page fault. Native Windows appears to give the value of the "name" pointer precedence and determines that the "name" parameter is actually a resource number; hence it does not page fault and runs Okad2 normally. Wine *DOES* check the "name" parameter to see if it is a resource index, but several subroutine calls later it forgets this fact and branches based on the LOADFROMFILE bit. The backtrace has been annotated to provide both a description and source lines involved in the decision. This behavior was found in the latest version of Wine for Debian (.1.42) and in a MacOS X version. -- 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