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

[Bug 29937] New: File selection dialog view shows Favorites when you click elsewhere
by wine-bugs＠winehq.org April 5, 2026

April 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=29937 Bug #: 29937 Summary: File selection dialog view shows Favorites when you click elsewhere Product: Wine Version: 1.4-rc1 Platform: x86-64 URL: http://www.winuae.net/files/InstallWinUAE2330.exe OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: markk(a)clara.co.uk Classification: Unclassified There is a small issue with file selection dialogs which some programs use. When the dialog opens, it shows the files in some directory in the right pane, and a tree view of the directory hierarchy in the left pane. The tree view shows Favorites and Desktop (which is expanded to show My Computer, My Documents, Trash, /). If you then click on any of the + or - symbols in the tree view, the view in the right pane jumps to Favorites. For example, click the + next to My Computer and the view on the right changes to Favorites (which may be empty). The directory shown in the right pane should probably not change when the user clicks a + or - symbol in the left pane. WinUAE is one program which uses that type of file dialog. To show the problem, download and run the WinUAE installer, check the box to run the program at the end. When the WinUAE Properties window appears, click "Select image file" to open a file selection dialog. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

3 9

[Bug 32079] New: dotted files hasn't displayed
by wine-bugs＠winehq.org April 5, 2026

April 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=32079 Bug #: 32079 Summary: dotted files hasn't displayed Product: Wine Version: 1.5.15 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: icegood1980(a)gmail.com Classification: Unclassified Application: notepad++ (http://notepad-plus-plus.org/) wine config /drivers/ show dot files checked. In explorer under notepad++ dot files hasn't shown. In particular in home directory. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

3 11

[Bug 42340] New: Wrong decorations with KWin (KDE Plasma 5)
by wine-bugs＠winehq.org April 4, 2026

April 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=42340 Bug ID: 42340 Summary: Wrong decorations with KWin (KDE Plasma 5) Product: Wine Version: 2.0-rc6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: ArchLinux Created attachment 57102 --> https://bugs.winehq.org/attachment.cgi?id=57102 Testprogram to show wrong decorations Setting "Allow the window manager to decorate the windows" in winecfg solves the issue. There are two issues: -Minimize box is always shown -Maximize box is only shown when WS_THICKFRAME is also used Testprogram 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.

2 2

[Bug 41247] New: WASAPI exclusive pull mode sound doesn't work, but shared (non-exclusive) does
by wine-bugs＠winehq.org April 3, 2026

April 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=41247 Bug ID: 41247 Summary: WASAPI exclusive pull mode sound doesn't work, but shared (non-exclusive) does Product: Wine Version: 1.9.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: markk(a)clara.co.uk Distribution: --- Wine 1.9.17, Lubuntu 16.04 x86-64. The current beta version of WinUAE (3.4.0 beta 4) uses WASAPI in pull mode. In Wine that works OK in shared (non-exclusive) mode, but exclusive mode does not work, giving console output like this: fixme:alsa:AudioClient_Initialize EXCLUSIVE mode with EVENTCALLBACK WASAPI: Initialize() 8889000A Sorry, can't initialize sound. In contrast, WinUAE 3.3.0 uses WASAPI in push mode, and both exclusive and shared work fine there. To reproduce: - Use winecfg to set Windows version to e.g. Windows 10. - Download and run the WinUAE 3.3.0 installer from http://www.winuae.net/files/InstallWinUAE3300.msi - Rename winuae.exe to winuae330.exe - Download WinUAE 3.4.0 beta 4 from http://www.winuae.net/files/b/winuae_3300b4.7z then unpack to the WinUAE program directory. - Download a program which plays sound, for example http://main.aminet.net/demo/euro/DOC_Demons.lha - Run winuae.exe (version 3.4.0b4): wine winuae.exe -log - When the WinUAE Properties window appears, click Floppy drives in the tree-view on the left side. Then click the "..." button to the right of DF0: and select DOC_Demons.lha - Click Sound in the tree-view on the left. By default the drop-down at the top should say "WASAPI: Default Audio Device", if not select that. - Click Start at the bottom of the window. - Part of the log output should say something like WASAPI: '{0.0.0.00000000}.{176D6B2F-F69E-497A-AE3D-15C5CEE27C79}' WASAPI: Shared Pull CH=2 FREQ=44100 BUF=2048 (4096) - Wait for the demo to load and start, and you should hear sound. - Press F12 to open the settings window. The sound page should be showing. Change the drop-down at the top to "WASAPI EX: Default Audio Device" then click OK at the bottom to continue emulation. There is no sound and this console output: fixme:alsa:AudioClient_Initialize EXCLUSIVE mode with EVENTCALLBACK WASAPI: Initialize() 8889000A Sorry, can't initialize sound. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

3 4

[Bug 24387] New: MS Money 2000: Crashes updating financial informations from the Internet
by wine-bugs＠winehq.org April 3, 2026

April 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=24387 Summary: MS Money 2000: Crashes updating financial informations from the Internet Product: Wine Version: 1.3.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: andrea.vai(a)unipv.it Created an attachment (id=30732) --> (http://bugs.winehq.org/attachment.cgi?id=30732) Terminal output. If I click on "update informations from the internet" in the main page of the application, the applications crashes (Application error window "MSMONEY encountered an error and has must be closed" appears. The only way to close the application is to kill it). Problem was not present in wine 1.1.15, so I performed a regression test and the result is: ---------------------------------------------------------------- c5a6b7b36674e8b7f7dc687b01773b88fa7d7312 is the first bad commit commit c5a6b7b36674e8b7f7dc687b01773b88fa7d7312 Author: Juan Lang <juan.lang(a)gmail.com> Date: Tue Mar 30 10:26:48 2010 -0700 rsaenh: Support setting salt via KP_SALT (resend). :040000 040000 d9a20e02d3637c41baadb3131a23907fb5603fe8 51eea86ad80613f612f64bd44a0517c0b89a4894 M dlls ---------------------------------------------------------------- As far as I can notice, the bad commit is the same involved in bug 23208. Fixing this regression would really bring this app towards complete functionality. -- 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 55

[Bug 42517] New: StarOffice51 Crash on File open
by wine-bugs＠winehq.org April 3, 2026

April 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=42517 Bug ID: 42517 Summary: StarOffice51 Crash on File open Product: Wine Version: 1.8.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gerhard.muellner(a)gm.co.at Distribution: --- the good old Star Office 51 works nearly perfect except it crashes if file open menu is selected (backtrace file in root of zip file) an error "missing font" could occur during start, please ignore. unpack zip and start Office51/soffice.exe wine. a bugfix would be very useful to convert or work with (very)old files ;-) many thanks to all for your good job. -- 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 38874] New: Homesite+ (v5.5): Radiobutton in Find dialog not set properly when using keyboard shortcut (Alt+U)
by wine-bugs＠winehq.org April 3, 2026

April 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=38874 Bug ID: 38874 Summary: Homesite+ (v5.5): Radiobutton in Find dialog not set properly when using keyboard shortcut (Alt+U) Product: Wine Version: 1.7.46 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fooquency(a)gmail.com Distribution: --- Created attachment 51804 --> https://bugs.winehq.org/attachment.cgi?id=51804 Screenshot showing after situation While in the editor window, there is a Find dialog which enables text search within the current file being edited. The Dialog includes a radiobutton pair for setting the direction of search to be either Up (with U underlined) or Down (D). On Mac OSX, pressing Cmd+U to set the radiobutton only selects the label, but does not actually make the radiobutton be checked. However, the original behaviour on Windows does check the radiobutton. Therefore, the radiobutton has then to be made active either by using the mouse, or using the Space key. The attached screenshot shows the state immediately after pressing Cmd+U. As you can see, the label is surrounded but the radiobutton is still on its original value. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

3 6

[Bug 26389] New: Win3.1 Notepad crashes when opening a large file
by wine-bugs＠winehq.org April 3, 2026

April 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=26389 Summary: Win3.1 Notepad crashes when opening a large file Product: Wine Version: 1.2.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: spammis(a)spam.la Created an attachment (id=33605) --> (http://bugs.winehq.org/attachment.cgi?id=33605) DOSBox (left) and Wine (right) This bug applies to the version of Notepad bundled with Windows 3.1. Old versions of Notepad can't open big text files. Instead, Notepad displays a message saying "The file FILENAME is too large for Notepad. Use another editor to edit the file." Wine crashes instead of displaying this message. A giant file can be created in numerous ways. I used a small python script: for i in range(1999999): print i "python script.py > giant.txt" gives a giant file. I tried opening the file using Wine running Notepad and using DOSBox running Windows 3.1 running Notepad. Windows 3.1 is just a normal DOS application, so it runs fine under DOSBox. I'm attaching a PNG file displaying the differences between Wine and DOSBox. In this case, DOSBox is correct while Wine is wrong. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

3 18

[Bug 11446] New: Gangsters: Wrong 2d rendering
by wine-bugs＠winehq.org April 1, 2026

April 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=11446 Summary: Gangsters: Wrong 2d rendering Product: Wine Version: 0.9.51. Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: wielkiegie(a)gmail.com Created an attachment (id=10577) --> (http://bugs.winehq.org/attachment.cgi?id=10577) Wine messages when starting with OpenGL as DDraw renderer OpenGL as DirectDraw driver causes unhandled page fault when playing intro (I tried GDI for testing). When the game starts or after changing menu screen, main menu is completely black. Graphics can be visible only after pushing any button in the menu, but releasing mouse button elsewhere. Buttons doesn't contain any text and colors of whole screen are ugly. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

3 39

[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 March 30, 2026

March 30, 2026

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.

3 25