October 2025 - Wine-bugs - list.winehq.org

[Bug 58041] New: PlayOnline Viewer: Black screen when running via winewayland.
by WineHQ Bugzilla 28 Nov '25

28 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=58041 Bug ID: 58041 Summary: PlayOnline Viewer: Black screen when running via winewayland. Product: Wine Version: 10.4 Hardware: x86-64 URL: https://web.archive.org/web/20210810150839/http://www. playonline.com/ff11eu/download/media/install_win.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: chiitoo(a)gentoo.org Distribution: Gentoo Running PlayOnline Viewer via Wayland by setting DISPLAY="" in an LXQt/Wayfire session results into a completely black window. The application still works, just no content can be seen. Final Fantasy XI Online, which PlayOnline Viewer is used to launch, seems to work OK so far, when navigated to blindly. Did not spot anything different in the default terminal output yet. Running via XWayland works as expected, though that also means a black screen in displays other than the primary screen, or rather the content just isn't updated in the other screens. Without XWayland, the result is the same regardless of the display. Thank you! -- 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 6

[Bug 54927] New: grepwinNP3 (part of Notepad3) crashes inside uxtheme
by WineHQ Bugzilla 28 Nov '25

28 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=54927 Bug ID: 54927 Summary: grepwinNP3 (part of Notepad3) crashes inside uxtheme Product: Wine Version: 8.7 Hardware: x86-64 URL: https://github.com/rizonesoft/Notepad3/releases/downlo ad/RELEASE_6.23.203.2/Notepad3_6.23.203.2_x64_Setup.ex e OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: uxtheme Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- This is a kind of "grep with GUI": Unhandled exception: page fault on read access to 0x0000000000000004 in 64-bit code (0x0000006d5089f5). =>0 0x0000006d5089f5 DrawThemeTextEx+0x45(hTheme=000000000025CA20, hdc=0000000001410094, iPartId=0x2, iStateId=0, pszText=L"Regex search", iCharCount=0xffffffff, flags=0x2450, rect=00000000001FC400, options=0000000000000000) [/home/louis/sda2/wine64-build/../wine/dlls/uxtheme/draw.c:1790] in uxtheme (0x000000001fc400) Apparently crashes in next line because "options" pointer is NULL: if (options->dwFlags & ~(DTT_TEXTCOLOR | DTT_FONTPROP)) FIXME("unsupported flags 0x%08lx\n", options->dwFlags); -- 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 41034] New: TomTom MyDrive Connect needs implementation of KERNEL32.dll.SetVolumeMountPointW and others
by wine-bugs＠winehq.org 28 Nov '25

28 Nov '25

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 58719] New: Wagotabi crashes on wine-10.15.
by WineHQ Bugzilla 28 Nov '25

28 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58719 Bug ID: 58719 Summary: Wagotabi crashes on wine-10.15. Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- Created attachment 79320 --> http://bugs.winehq.org/attachment.cgi?id=79320 Console log The game Wagotabi (Steam AppID: 2701720. Uses Unity Engine) doesn't work under wine-10.15. Attempting to start the game in a clean prefix results in the game crashing with a black screen instantly on start up. Installing DXVK into the wine prefix gets the game to show it's company logos, but it then runs into https://bugs.winehq.org/show_bug.cgi?id=49028. Attempting to use -force-vulkan or -force-glcore Unity cmdline args results in the common UnityPlayer error: InitializeEngineGraphics failed. So the game lacks support for any alternative renderers. A demo is available on steam for anyone wanting to try this. Strangely, the game's store page claims it's Steam Deck Verified. So I guess proton is compatible, but I've only tested Wine, so I can't vouch for that claim. Console log attached. -- 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 58831] New: the commit：win32u: Don't store the window OpenGL drawables on the DCs. Causing software deadlock
by WineHQ Bugzilla 28 Nov '25

28 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58831 Bug ID: 58831 Summary: the commit：win32u: Don't store the window OpenGL drawables on the DCs. Causing software deadlock Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: 1685899837(a)qq.com Distribution: --- I used wine10.15 to run Hypermesh 2023. Before this commit：win32u: Don't store the window OpenGL drawables on the DCs.（https://gitlab.winehq.org/wine/wine/-/commit/c3f3ef24e8d1ebe49e8073e8e… I clicked on 'create session' and selected 'HyperView'. It was running normally, but after merging this commit, there was an issue： 01a0:err:sync:RtlpWaitForCriticalSection section 00007F4A4ACC5570 "?" wait timed out in thread 01a0, blocked by 0134, retrying (60 sec). -- 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 24

[Bug 57486] New: The Last Stand: Aftermath: Loads infinitely
by WineHQ Bugzilla 28 Nov '25

28 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=57486 Bug ID: 57486 Summary: The Last Stand: Aftermath: Loads infinitely Product: Wine Version: unspecified Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Alexander88207(a)Protonmail.com Hello, the game The Last Stand Aftermath loads infinitely when i want to enter the game from the menu. Tested with: Wine 9.22 The game is available at: GOG: https://www.gog.com/en/game/the_last_stand_aftermath Steam: https://store.steampowered.com/app/1266840/The_Last_Stand_Aftermath/ Thank you in advance! -- 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 58800] New: tlReader 10.1.0.2004 toolbar has broken rendering
by WineHQ Bugzilla 28 Nov '25

28 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58800 Bug ID: 58800 Summary: tlReader 10.1.0.2004 toolbar has broken rendering Product: Wine Version: unspecified Hardware: x86-64 URL: https://web.archive.org/web/20251013233829/https://tsh wanedje.com/builds/2004/tlReader_10.1.0.2004.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: arethusa26(a)gmail.com CC: zzhang(a)codeweavers.com Regression SHA1: 541d9be5ecda1bc0c8fce22f1318bf5d72572327 Distribution: --- Created attachment 79445 --> http://bugs.winehq.org/attachment.cgi?id=79445 Broken toolbar rendering With the latest master (wine-10.16-212-g6124fea1dde), when loading the Manx-English dictionary (available from https://tshwanedje.com/downloads/files/Manx_English_Phil_Kelly_Dec2014.zip) the toolbar at the top of the tlReader application appears to have some rendering defects. Specifically, the background color of the toolbar has a darker color, and there is a stray horizontal line that is visible and appears to intersect the tops of the toolbar icons. Additionally, hovering the cursor over the icons results in a blue box that is drawn around a hovered icon but is not cleared when the cursor leaves the icon. With wine-10.16, the rendering of the toolbar seems to be more correct. The background color apparently resembles the color on Windows 10, no stray horizontal line is visible on the toolbar, and hovering over the toolbar icons with the cursor results in a blue box being drawn around a hovered icon that is cleared when the cursor leaves the icon. These behaviors are consistent with what is seen on Windows 10. Regression testing identified commit 541d9be5ecda1bc0c8fce22f1318bf5d72572327, which implemented the final modifications needed for comctl32 separation, as the change that introduced the broken toolbar rendering. However, it's not clear if the toolbar rendering issue is a new introduced problem or if it was previously hidden and now exposed with the comctl32 separation. -- 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 11

[Bug 58442] New: x11 fullscreen retries mwm hints causing chaos
by WineHQ Bugzilla 27 Nov '25

27 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58442 Bug ID: 58442 Summary: x11 fullscreen retries mwm hints causing chaos Product: Wine Version: 10.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zlice(a)crtdrift.us Distribution: --- Created attachment 78893 --> http://bugs.winehq.org/attachment.cgi?id=78893 fix-fullscreen-toggle somewhere after 10.8 e072358059abe8446e4ac9e89d2e0618629edf5f changed behavior to keep trying to update window hints, even if they are non-changes(no-op) https://gitlab.winehq.org/wine/wine/-/merge_requests/8079 on openbox, alt-tabbing watch_dogs will randomly toggle decor, then fullscreen (i think this is a openbox bug or at least behavior) but at some point alt-tab will go to nothing focused, then another alt-tab will focus the game. so if you have 2 windows, it takes 3 alt-tabs to go between them. on fluxbox/my-fork multi-alt-tabbing the fullscreen window will go between expected fullscreen and using the decor size of the frame and then resize the 'not fullscreen' watch_dogs window inside, leaving with an empty border where the titlebar and borders would be. (even with telling properties to not change in the wm itself, wine tries to keep changing settings and this happens) jwm is kind of fubar no matter what jwm and fluxbox both still require QS_POSTMESSAGE fix to get past the splashscreen : see https://bugs.winehq.org/show_bug.cgi?id=57954 not sure what the reason was behind the above change but it causes hints to be repeatedly changed, which incorrectly detects 'fullscreen' by ... dlls/win32u/window.c : apply_window_pos() calls dlls/win32u/sysparams.c : is_window_rect_full_screen() checks rects sizes to determine fullscreen (then calls x11drv) user_driver->pWindowPosChanged() which finally calls wm_net and wmw hint updates fullscreen is incorrect because a minimized window does not keep its size/monitor i assume. then the 'no-op' change retries and somewhere things get set to random states, like wanting titlebars and decor again. patch attached that lets it work on fluxbox and openbox, however, not sure that is complete, as it crosses over with many other bugs since late 9.x thinking the openbox issue may be related to a bug with c67bfdbeba1860c891e53c64379f5e86d8e8b664 -- 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 6

[Bug 50418] New: ArcGIS Pro fails to launch with wine-mono
by WineHQ Bugzilla 27 Nov '25

27 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=50418 Bug ID: 50418 Summary: ArcGIS Pro fails to launch with wine-mono Product: Wine Version: 6.0-rc4 Hardware: x86-64 URL: http://data.wvgis.wvu.edu/SecureFTP/securedownload/arc /ArcGIS%20Pro/ArcGISPro_22_163783.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Unhandled Exception: System.InvalidProgramException: Invalid IL code in ActiproSoftware.Windows.Controls.Ribbon.UI.RibbonMeasurements:set_BackstageTabWidth (double): IL_0002: stsfld 0x04000137 at ArcGIS.Desktop.Framework.FrameworkApplication..ctor () [0x00169] in <a27482abd44f4054a15c91c81cd4a531>:0 at ArcGIS.Desktop.Core.ProApp..ctor () [0x00012] in <5f84b0450bdb4a808e04ab6ef46dd283>:0 at <Module>.main (System.String[] args) [0x00000] in <bb19de946d75458385874ec2b780dbb5>:0 I haven't tried debugging yet. -- 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 1

[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 27 Nov '25

27 Nov '25

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