September 2016 - Wine-Bugs - list.winehq.org

[Bug 35698] New: Nuance PDF Create! 5 installer (part of OmniPage 17) reports 'Error code: 154 - Get ServerPolicy failed' (IGroupPolicyObject, CLSID {ea502722-a23d-11d1-a7d3-0000f87571e3})
by wine-bugs＠winehq.org March 4, 2019

March 4, 2019

https://bugs.winehq.org/show_bug.cgi?id=35698 Bug ID: 35698 Summary: Nuance PDF Create! 5 installer (part of OmniPage 17) reports 'Error code: 154 - Get ServerPolicy failed' (IGroupPolicyObject, CLSID {ea502722-a23d-11d1-a7d3-0000f87571e3}) Product: Wine Version: 1.7.13 Hardware: x86 OS: Linux Status: NEW Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, as the summary says. The failure seems non-critical and the message box can be dismissed. The sub-installer can be separately run for testing: --- snip --- $ pwd /mnt/iso/PDFCreate5/System32/PDFCreate $ WINEDEBUG=+tid,+seh,+relay,+ole,+variant wine ./setup.exe >> ~/Downloads/log2.txt 2>&1 ... 003f:Call ole32.CoCreateInstance(00b2e33c,00000000,00000001,00b2e324,00b2e334) ret=008d881a 003f:trace:ole:CoCreateInstance (rclsid={ea502722-a23d-11d1-a7d3-0000f87571e3}, pUnkOuter=(nil), dwClsContext=00000001, riid={ea502723-a23d-11d1-a7d3-0000f87571e3}, ppv=0xb2e334) 003f:trace:ole:CoGetClassObject CLSID: {ea502722-a23d-11d1-a7d3-0000f87571e3},IID: {00000001-0000-0000-c000-000000000046} 003f:Call KERNEL32.FindActCtxSectionGuid(00000001,00000000,00000004,00b2e33c,00b2e11c) ret=7eac14e4 003f:Ret KERNEL32.FindActCtxSectionGuid() retval=00000000 ret=7eac14e4 003f:Call ntdll.RtlInitUnicodeString(00b2e030,00b2e082 L"CLSID\\{EA502722-A23D-11D1-A7D3-0000F87571E3}") ret=7eabb537 003f:Ret ntdll.RtlInitUnicodeString() retval=00b2e030 ret=7eabb537 003f:Call ntdll.NtOpenKey(00b2e07c,00020019,00b2e038) ret=7eabb553 003f:Ret ntdll.NtOpenKey() retval=c0000034 ret=7eabb553 003f:Call ntdll.RtlNtStatusToDosError(c0000034) ret=7eabb55e 003f:Ret ntdll.RtlNtStatusToDosError() retval=00000002 ret=7eabb55e 003f:err:ole:CoGetClassObject class {ea502722-a23d-11d1-a7d3-0000f87571e3} not registered 003f:err:ole:CoGetClassObject no class object {ea502722-a23d-11d1-a7d3-0000f87571e3} could be created for context 0x1 003f:Ret ole32.CoCreateInstance() retval=80040154 ret=008d881a 003f:Call user32.MessageBoxA(00000000,00b2e1e8 "CoCreateInstance \n Error code: 154",00901348 "Get ServerPolicy failed",00000000) ret=008d8eee --- snip --- MSDN: http://msdn.microsoft.com/en-us/library/aa374235%28v=VS.85%29.aspx Here is a blog entry which talks about it, with some code example: http://magicmao.wordpress.com/2011/08/05/changing-group-policy-by-c-coding/ $ wine --version wine-1.7.13-118-g0eb6265 Regards -- 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 4

[Bug 40273] New: Call from 0x7b83d9b2 to unimplemented function windowscodecs.dll.WICCreateBitmapFromSection
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=40273 Bug ID: 40273 Summary: Call from 0x7b83d9b2 to unimplemented function windowscodecs.dll.WICCreateBitmapFromSection Product: Wine Version: 1.9.5 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: windowscodecs Assignee: wine-bugs(a)winehq.org Reporter: xerox_xerox2000(a)yahoo.co.uk Distribution: --- a user reported problems with this app https://paprikaapp.com/windows/ on the forum. After winetricks dotnet45 corefonts and working around https://bugs.winehq.org/show_bug.cgi?id=15670 by adding registrykey like wine-staging does** the app crashes with Call from 0x7b83d9b2 to unimplemented function windowscodecs.dll.WICCreateBitmapFromSection When i use native windowscodecs it also crashes with: Unhandled Exception: System.NotSupportedException: No imaging component suitable to complete this operation was found. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x88982F50 **: (see https://github.com/wine-compholio/wine-staging/blob/master/patches/wine.inf…) -- 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 19

[Bug 39011] New: Sierra Chart hangs when drawing polygon fill line type: gdi32.Polygon()
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=39011 Bug ID: 39011 Summary: Sierra Chart hangs when drawing polygon fill line type: gdi32.Polygon() Product: Wine Version: 1.7.48 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: spam(a)brettcave.net Distribution: --- Created attachment 51965 --> https://bugs.winehq.org/attachment.cgi?id=51965 v1.7.44 WINEDEBUG log segment with THREAD_DETACH errors Sierra Chart is a stock market, forex, and other market price graphing program. They use C/C++ and avoid java and .net. Normally it runs well under wine, but there is a long term issue that they've known about: Drawing chart lines with a polygon fill (Fill Top, Fill Bottom in the program) will hang wine for a minute or 2 but works fine under regular windows. This hanging will release and then hang again shortly after making the chart unusable. I'm using ubuntu 14.04 LTS with wine 1.7.44 from the ppa archive. I've also compiled 1.7.48 32bit using the lxc instructions. I was able to get the X11 socket running inside lxc after some work. Sierra Chart runs at full speed with it. My hardware for testing is a laptop, dual core 2.2ghz AMD K10e, Mobile Radeon HD 4250 using generic linux drivers, and 8g RAM. Sierra Chart isn't known to directly bang video hardware, so chip and driver shouldn't be an issue. This laptop can play 1080i mpeg2 off my DVR faster than normal, so it is capable enough to handle a chart. Both were tested with cleanly created wine prefixes. Sierra Chart is 32bit compiled and normally works fine with wine. I've been able to reproduce the bug by using the polygon fill line type and by scrolling the chart back and forth. If I change the line type to something plain, the freezing problem doesn't happen. The bug is harder to reproduce with debugging activated. It's probably allowing extra time for whatever is causing the hang to finish before it hangs. *** file: wine_SC_THREAD_DETACH.wine1.7.44.log.txt I've attached a small log file segment from ubuntu version 1.7.44: WINEDEBUG=+timestamp,+relay,+seh,+tid,+message,+msgbox,+dll,+loaddll It starts out with the gdi32 draw commands, has the freezing section in the middle, and then continues with the gdi32 draw commands. The problem is from time stamp 1306647.286 to 1306718.051. It's about 71 seconds total. There are a bunch of THREAD_DETACH entries in the log. Sierra Chart support says that graph drawing is not multi threaded and that they don't know what that is. The only other threads are when downloading real time price data updates and loading chart price data from disk. Note: the next 1.7.48 versions were run from inside the 32bit lxc build environment. One thing I noticed when testing with 1.7.48 is that my memory usage bar applet was jumping around a lot during a freeze. I didn't get exact figures but the range was over 3g. That's huge for a 32bit program. I wasn't watching for the first log. *** file: wine_SC_ConsoleLog_wine1.7.48.log.txt This is the regular shell console log. *** file: wine_SC_wine1.7.48.log.txt I've attached a second small log file segment from compiled version 1.7.48: WINEDEBUG=+timestamp,+relay,+seh,+tid,+message,+msgbox,+dll,+loaddll It starts out with the gdi32 draw commands, has a very small freezing section in the middle, and then continues with the regular gdi32 draw commands. The problem is from time stamp 1485052.556 to 1485124.153. It's about 71 seconds total. In this log I didn't see the THREAD_DETACH entries. It was small and clean with no errors reported. I don't know what to make of the difference between the 2 logs. I can see that there's a problem, but I don't have enough programming and debugging skills to understand what is going on. If this looks like a programming error in Sierra Chart, please give me something I can tell them that they won't brush off. ------------- Download Instructions. Download page: http://www.sierrachart.com/index.php?page=doc/SCInstallerList.php The page will list multiple versions ranging from current to past. The file to get is: SierraChartSetupNoCLR.exe The file date in the list: 2015/7/31 The "NoCLR" (No Common Language Runtime) doesn't use poorly supported windows functions and is wine friendly. This is the version Sierra Chart support normally recommends. sha1sum: 4454a0ef2e3a2bb525098ea5620f8d4bb23edb2a SierraChartSetupNoCLR.exe In a week or so, this current version will "probably" be named: 1280SierraChartSetupNoCLR.exe Help / About shows version number 1280. ------------ Account Setup Instructions. Sierra Chart has a free demo account for testing. Their install is almost entirely self contained to a directory and won't scatter files everywhere. Instructions are here: http://www.sierrachart.com/index.php?page=doc/setup.php Step 1: Download program. Since Sierra Chart support isn't going to do anything with this bug, the current version will very likely have it since this is an old bug of unknown age. If not using this link, use the download link above. Step 2: "Create Your Account" to get a free demo account. I recommend something alone the lines of "Wine Debug". They will know what that is. A support ticket will need to be opened to activate the account. They're very easy going with programmers. Just mention that you're someone from the wine debug team. If y'all want more than the 15 day trial, request it there. They will usually activate the account the same day. Support Link: http://www.sierrachart.com/index.php?page=doc/support.html#SCAccounts This is Section #2, instructions in the yellow box with the link. In the future if the trial account expires, open another support ticket, mention that you're with the wine debug team and need to run some more tests. They'll usually reactivate the account the same day. So long as you're actively programming or debugging and not using their product to trade for free, Sierra Chart support is very laid back about continuing accounts. Ignore the rest of the Sierra Chart account steps web page and follow my steps below to reproduce the bug once the demo account is activated. -------------- Steps to reproduce the bug. #create a new prefix WINEPREFIX=/home/user1/.wine3 winecfg Applications / Windows Version: Windows 7 #earlier tests have shown different windows versions don't matter. No library overrides. Turned off Graphics: Allow the window manager to decorate the windows. Sierra Chart has alert sounds, but they are irrelevant for the bug reproduction. "OK" to exit out of winecfg. #install Sierra Chart WINEPREFIX=/home/user1/.wine3 wine SierraChartSetupNoCLR.exe Accept defaults options and locations in the installer. Run when finished. Note: I recommend to run Sierra Chart in normal / non-debug mode the first time as the freezing bug is easier to reproduce. Enter user name and password. When the main window comes up, press "No" at the Data and Trade Service prompt to use demo mode defaults. Hit "Close Log" on "Message Log" to get it out of the way. Menu: File / Find Symbol Expand "Forex". I prefer to select "GBPUSD" as the symbol since it has good volume and is easily recognized. Hit the "Open Intraday Chart" button. Hit the "Close" button to get rid of the find screen. A full screen chart will open and download price data for a minute. Click once in the middle of the chart to select it. Press the keyboard down arrow 11 times. At the very bottom right corner will be a tiny green box with a number in it. Every time the down arrow gets hit, it will decrement and the chart will show more bars per screen. The bar should read "1". If it is red, hit the "End" key on the keyboard. Color doesn't matter much for this reproduction, though. Note: If the hanging problem below gets to be too severe to do anything, only press the down arrow several times to not compress the chart view as much. Maybe go down to "5" instead of "1". Quick side note before the hanging bug gets triggered: Menu: Help / About will show the build number / version number for verification. The latest installer file usually won't have a version number in the name. Menu: Analysis / Studies Hit "Add Custom Study" button at the bottom. Double click to expand "User Contributed Studies". Scroll down to "RSI Bands". Select it and hit "Add". It will show up on the right panel list. This study won't cause the bug alone. It is used to put an extra load on the graph. Hit "Add Custom Study" button again. Scroll down a little to "RSI w/Trend". Select it and hit "Add". It will show up on the right panel list. This study has the polygon fill that will trigger the freezing bug. Note for Bug Settings: Something to point out to come back to later... Select "RSI w/Trend" and hit the "Settings" button. Hit the "Subgraphs" tab at the top. At the top middle will be a "Draw Style" column. This is how the study line types are drawn on the graph. The bug versions will have "Trans. Fill Top" for "Fast MA" and "Trans. Fill Bottom" for "Medium MA". Selecting these two entries and changing them with the "Draw Style" drop down box to "Line" then "Solid" and "1" will allow them to not trigger the bug (but do that later). Changing the two entires to "Fill Top" and "Fill Bottom" will still trigger the bug regardless of transparency settings. For now, don't change the settings for the bug reproduction, but come back to this afterwards. Hit "Cancel" to get out of the settings screen. Hit "OK" on the "Chart Studies" window to get back to the main chart. New lines will be drawn on the screen from the two added studies. The graph "should" come back immediately, but sometimes it will trigger the hanging bug. Click on another virtual desktop and come back or click on a window below Sierra Chart to bring it forwards and then go back to Sierra Chart. If the screen doesn't redraw within a second or two, then the bug was triggered. It will take a minute or two for Sierra Chart to come back. Note that the CPU will be maxed out and RAM usage will be jumping around. To save these settings so far, Menu: File / Save All. Enter a brief chart book name for a file name at the bottom (like "test1"). Afterwards the chart book can be quickly reloaded by that name in the recent files list on the right side of the File menu. This will allow for skipping the "Menu: Analysis / Studies" steps on next program reload. ...That is if the hanging bug isn't triggered again... and again... and again... In wine debug mode, the hanging bug "usually won't" be triggered yet. To manually trigger the hanging bug, use the mouse to grab the horizontal scroll bar at the bottom of the screen and drag it back and forth. This will scroll the chart back and forth causing a lot of redraws. If Sierra Chart stops responding, click on another virtual desktop and come back or click on a window below Sierra Chart to bring it forwards and then go back to Sierra Chart. If the screen doesn't redraw within a second or two, then the bug was triggered. It will take a minute or two for Sierra Chart to come back. Note that the CPU will be maxed out and RAM usage will be jumping around. With the wine debug mode log it is hard to see where the bug was triggered. I use the "+timestamp" option and a stop watch/timer app to note the hang and resume times so they can be matched up later in the debug log. When dragging the chart horizontal scroll bar, they will be surrounted by gdi32 draw commands. In future tests, the Sierra Chart process may have to be killed. To restart it, I go into the drive_c/SierraChart folder and run SierraChart.exe. Sierra Chart will remember your login name and password. When the authentication window pops up, just leave it for a couple seconds and it will go away and the main chart will pop up. Now that the hanging bug has been experienced, the line type can be changed from the Note instructions above to see the comparison with a plain line. -- 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 7

[Bug 40706] New: FolderMerger cmd not valued, xcopy problem in batch
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=40706 Bug ID: 40706 Summary: FolderMerger cmd not valued, xcopy problem in batch Product: Wine Version: 1.7.35 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: peterlongx1988(a)gmail.com Distribution: --- Created attachment 54591 --> https://bugs.winehq.org/attachment.cgi?id=54591 File Merger I try to use this little software http://2xdsoft.de.tl/FolderMerger.htm but is problematic to use with Wine because cmd.exe is not valued when I press Merge Now! Is possibile to create a .bat file indipendently also, but when I try to running it cmd.exe return me this error Merging folders... (1/6) Invalid parameter 'K' - use x copy ? for help Is 'C:\PATH\filename.zip' a filename or directory on the target? (F - File, D - Directory) This happens not because parameter is invalid. Example of command in .bat not valued correctly @echo off cls echo Merging folders ... (1/6) XCOPY "C:\users\psiraja\Desktop\test\test1\test3\Folder Merger v1.6.zip" "C:\users\psiraja\Desktop\estrazione\Folder Merger v1.6.zip*" /C /K /Y /H cls echo Merging folders ... (2/6) XCOPY "C:\users\psiraja\Desktop\test\test2\test1\test2\Folder Merger v1.5.zip" "C:\users\psiraja\Desktop\estrazione\Folder Merger v1.5 (dup. 2).zip*" /C /K /Y /H cls echo. echo Done! echo. ping -n 2 localhost >nul start "" "C:\users\psiraja\Desktop\estrazione" exit Have you got any idea to bypass this problem? -- 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 41404] New: WPS Office 10.1.0.5775 unhandled exception on installation
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=41404 Bug ID: 41404 Summary: WPS Office 10.1.0.5775 unhandled exception on installation Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 2460acc(a)gmail.com Distribution: --- Created attachment 55759 --> https://bugs.winehq.org/attachment.cgi?id=55759 Backtrace file for error When trying to install WPS Office in Wine 1.8 (installation file wps_office_free_10.1.0.5775_en.exe), I get a serious error. Backtrace is attatched. -- 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 41039] New: can't run virtualbox.exe
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=41039 Bug ID: 41039 Summary: can't run virtualbox.exe Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: 1934337507a(a)gmail.com CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 55214 --> https://bugs.winehq.org/attachment.cgi?id=55214 ss 无法运行virtualbox.exe，提示有严重错误 wine '/home/xiejinggang/.wine/drive_c/Program Files/Oracle/VirtualBox/VirtualBox.exe' wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe" err:wineboot:ProcessRunKeys Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2) fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:advapi:RegisterEventSourceW ((null),L"QPCore"): stub fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x00000000,(nil),0x0001,0x00000000,0x72e764,(nil)): stub fixme:advapi:DeregisterEventSource (0xcafe4242) stub fixme:ntoskrnl:KeInitializeEvent stub: 0x5532ac 0 0 fixme:ntoskrnl:KeInitializeEvent stub: 0x5532bc 0 0 fixme:ntoskrnl:KeInitializeEvent stub: 0x555410 1 0 fixme:ntoskrnl:KeEnterCriticalRegion : stub fixme:ntoskrnl:KeLeaveCriticalRegion : stub fixme:ntoskrnl:MmGetSystemRoutineAddress L"PsGetCurrentProcessWin32Process" not found fixme:ntoskrnl:MmGetSystemRoutineAddress L"PsGetCurrentThreadWin32Thread" not found fixme:ntoskrnl:KeGetCurrentIrql stub! fixme:ntoskrnl:KeGetCurrentIrql stub! fixme:ntoskrnl:KeGetCurrentIrql stub! fixme:ntoskrnl:KeEnterCriticalRegion : stub fixme:ntoskrnl:KeLeaveCriticalRegion : stub fixme:ntoskrnl:MmGetSystemRoutineAddress L"ObRegisterCallbacks" not found fixme:ntoskrnl:MmGetSystemRoutineAddress L"ObUnRegisterCallbacks" not found fixme:ntoskrnl:PsSetCreateProcessNotifyRoutine stub: 0x54f7ce 0 fixme:ntoskrnl:PsSetCreateThreadNotifyRoutine stub: 0x54f8b8 fixme:ntoskrnl:PsSetLoadImageNotifyRoutine (0x54f8f6) stub fixme:ntoskrnl:CmRegisterCallback (0x54f934 (nil) 0x5553f8): stub fixme:ntoskrnl:KeEnterCriticalRegion : stub fixme:ntoskrnl:KeLeaveCriticalRegion : stub fixme:ntoskrnl:KeGetCurrentIrql stub! fixme:ntoskrnl:PsSetCreateProcessNotifyRoutine stub: 0x54f7ce 1 fixme:ntoskrnl:PsRemoveCreateThreadNotifyRoutine stub: 0x54f8b8 fixme:ntoskrnl:PsRemoveLoadImageNotifyRoutine stub: 0x54f8f6 fixme:ntoskrnl:KeEnterCriticalRegion : stub fixme:ntoskrnl:KeLeaveCriticalRegion : stub fixme:ntoskrnl:KeGetCurrentIrql stub! fixme:ntoskrnl:KeGetCurrentIrql stub! fixme:ntoskrnl:KeDelayExecutionThread (0, 0, 0x53e664): stub fixme:ntoskrnl:KeGetCurrentIrql stub! fixme:ntoskrnl:KeDelayExecutionThread (0, 0, 0x53e664): stub fixme:ntoskrnl:__regs_ExAcquireFastMutex 0x555404: stub fixme:ntoskrnl:__regs_ExReleaseFastMutex 0x555404: stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f6c8 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f4c8 1 C) semi-stub fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:wtsapi:WTSFreeMemory Stub (nil) wine: Call from 0x7b43bc2c to unimplemented function ntoskrnl.exe.FsRtlIsNameInExpression, aborting wine: Unimplemented function ntoskrnl.exe.FsRtlIsNameInExpression called at address 0x7b43bc2c (thread 0041), starting debugger... wine: Unhandled page fault on write access to 0x00545000 at address 0x7bc5474d (thread 0049), starting debugger... wine: Unhandled page fault on write access to 0x00544000 at address 0x7bc5474d (thread 0051), starting debugger... fixme:ntdll:EtwRegisterTraceGuidsW (0x2382c8d0, 0x23842738, {36c38d96-a693-4a22-b4b7-81510d39f547}, 1, 0x33fa04, (null), (null), 0x23842768): stub fixme:ntdll:EtwRegisterTraceGuidsW register trace class {6e5e5cbc-8acf-4fa6-98e4-0c63a075323b} fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0) fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x75da58 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x75daf8 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x75d8c8 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x75dab8 1 C) semi-stub err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded. err:winediag:nulldrv_CreateWindow The explorer process failed to start. fixme:ntdll:NtQueryInformationProcess (process=0xf0) Unimplemented information class: ProcessSessionInformation fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:msg:ChangeWindowMessageFilter 4a 00000001 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:ntdll:NtLockFile I/O completion on lock not implemented yet wine: Unhandled page fault on read access to 0x0000000f at address 0x41629a (thread 0009), starting debugger... fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:iphlpapi:NotifyAddrChange (Handle 0x18de9e4, overlapped 0x18de9c4): stub fixme:iphlpapi:CancelIPChangeNotify (overlapped 0x18de9c4): stub fixme:process:WTSGetActiveConsoleSessionId stub fixme:wtsapi:WTSQueryUserToken 1 0x82df80 fixme:wtsapi:WTSQueryUserToken 1 0x82df88 fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevation, ...) semi-stub fixme:advapi:EventRegister {dc55d4d9-138d-441a-80cb-77aec617e3f7}, 0x10089e00, 0x10100678, 0x10100670 fixme:advapi:EventUnregister deadbeef: stub fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b290 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b298 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b23c fixme:wtsapi:WTSQueryUserToken 1 0x82b244 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b290 fixme:wtsapi:WTSQueryUserToken 1 0x82b298 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b23c fixme:wtsapi:WTSQueryUserToken 1 0x82b244 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b290 fixme:wtsapi:WTSQueryUserToken 1 0x82b298 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b230 fixme:wtsapi:WTSQueryUserToken 1 0x82b238 err:rpc:I_RpcGetBuffer no binding fixme:crypt:CryptProtectMemory (0x143ac8 112 00000001): stub fixme:crypt:CryptUnprotectMemory (0x10ac1c0 112 00000001): stub fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82dcfc fixme:wtsapi:WTSQueryUserToken 1 0x82dd04 fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b118 fixme:wtsapi:WTSQueryUserToken 1 0x82b120 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b214 fixme:wtsapi:WTSQueryUserToken 1 0x82b21c fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b1c8 fixme:wtsapi:WTSQueryUserToken 1 0x82b1d0 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b134 fixme:wtsapi:WTSQueryUserToken 1 0x82b13c fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b17c fixme:wtsapi:WTSQueryUserToken 1 0x82b184 fixme:wtsapi:WTSQueryUserToken 1 0x82b268 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b1e0 fixme:wtsapi:WTSQueryUserToken 1 0x82b1e8 fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 Unhandled exception: page fault on read access to 0x0000000f in 32-bit code (0x0041629a). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:0041629a ESP:0033e9c4 EBP:0033e9d4 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000004 EBX:00473c80 ECX:00000050 EDX:000000f5 ESI:004a03d0 EDI:00473c80 Stack dump: 0x0033e9c4: 004a03d8 00000270 000000f5 000000f5 0x0033e9d4: 0033f624 00416760 00473c80 00000000 0x0033e9e4: 00409590 7ffdf000 7b636000 00000000 0x0033e9f4: 00000000 00000000 00000000 00000000 0x0033ea04: 00000000 00000000 00000000 00000000 0x0033ea14: 00000000 00000000 00000000 00000000 Backtrace: =>0 0x0041629a in virtualbox (+0x1629a) (0x0033e9d4) 1 0x00416760 in virtualbox (+0x1675f) (0x0033f624) 2 0x004095b0 in virtualbox (+0x95af) (0x0033fe40) 3 0x7b45f81c call_process_entry+0xb() in kernel32 (0x0033fe58) 4 0x7b46084a start_process+0x59(peb=<couldn't compute location>) [/home/xiejinggang/闊充箰/wine-1.9.15/dlls/kernel32/process.c:1108] in kernel32 (0x0033fe88) 5 0x7bc80760 call_thread_func_wrapper+0xb() in ntdll (0x0033fea8) 6 0x7bc8371d call_thread_func+0xfc(entry=0x7b4607f0, arg=0x7ffdf000, frame=0x33ffc8) [/home/xiejinggang/闊充箰/wine-1.9.15/dlls/ntdll/signal_i386.c:2759] in ntdll (0x0033ffa8) 7 0x7bc8073e call_thread_entry_point+0x11() in ntdll (0x0033ffc8) 8 0x7bc52d17 start_process+0x16(kernel_start=0x7b4607f0) [/home/xiejinggang/闊充箰/wine-1.9.15/dlls/ntdll/loader.c:3038] in ntdll (0x0033ffe8) 9 0xb7583b8d wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000) 10 0xb7583cf0 wine_switch_to_stack+0x1f(func=0x7bc52d00, arg=0x7b4607f0, stack=0x340000) [/home/xiejinggang/闊充箰/wine-1.9.15/libs/wine/port.c:77] in libwine.so.1 (0xbf929cb8) 11 0x7bc58ce9 LdrInitializeThunk+0x228(kernel_start=<couldn't compute location>, unknown2=<couldn't compute location>, unknown3=<couldn't compute location>, unknown4=<couldn't compute location>) [/home/xiejinggang/闊充箰/wine-1.9.15/dlls/ntdll/loader.c:3094] in ntdll (0xbf929cf8) 12 0x7b46697a __wine_kernel_init+0xa69() [/home/xiejinggang/闊充箰/wine-1.9.15/dlls/kernel32/process.c:1302] in kernel32 (0xbf92ae68) 13 0x7bc59bc3 __wine_process_init+0x152() [/home/xiejinggang/闊充箰/wine-1.9.15/dlls/ntdll/loader.c:3303] in ntdll (0xbf92aed8) 14 0xb7581d47 wine_init+0x2c6(argc=0x2, argv=0xbf92b434, error="", error_size=0x400) [/home/xiejinggang/闊充箰/wine-1.9.15/libs/wine/loader.c:956] in libwine.so.1 (0xbf92af38) 15 0x7c000ac2 main+0x81(argc=<is not available>, argv=<is not available>) [/home/xiejinggang/闊充箰/wine-1.9.15/loader/main.c:254] in <wine-loader> (0xbf92b388) 16 0xb738e72e __libc_start_main+0xdd() in libc.so.6 (0x00000000) 0x0041629a: movb 0x0000000f,%al Modules: Module Address Debug info Name (17 modules) PE 400000- 4f0000 Export virtualbox ELF 7b400000-7b7e0000 Dwarf kernel32<elf> \-PE 7b410000-7b7e0000 \ kernel32 ELF 7bc00000-7bcf5000 Dwarf ntdll<elf> \-PE 7bc10000-7bcf5000 \ ntdll ELF 7c000000-7c004000 Dwarf <wine-loader> ELF 7ef51000-7ef5f000 Deferred libnss_files.so.2 ELF 7ef5f000-7ef6c000 Deferred libnss_nis.so.2 ELF 7ef6c000-7ef87000 Deferred libnsl.so.1 ELF 7ef87000-7efd4000 Deferred libm.so.6 ELF b7371000-b7376000 Deferred libdl.so.2 ELF b7376000-b7531000 Dwarf libc.so.6 ELF b7532000-b754f000 Deferred libpthread.so.0 ELF b7571000-b757b000 Deferred libnss_compat.so.2 ELF b757b000-b7732000 Dwarf libwine.so.1 ELF b7734000-b7758000 Deferred ld-linux.so.2 ELF b775a000-b775b000 Deferred [vdso].so Threads: process tid prio (all id:s are in hex) 00000008 (D) C:\Program Files\Oracle\VirtualBox\VirtualBox.exe 00000009 0 <== 0000000e services.exe 00000057 0 00000056 0 00000037 0 0000002b 0 00000024 0 0000001c 0 00000017 0 00000016 0 00000014 0 00000010 0 0000000f 0 00000012 winedevice.exe 00000019 0 00000018 0 00000013 0 0000001a plugplay.exe 0000001f 0 0000001e 0 0000001b 0 00000020 QQProtect.exe 00000066 0 00000065 0 00000064 0 00000063 -1 0000005f 0 0000005e 0 0000005d 0 00000028 0 00000027 0 00000026 0 00000021 0 00000029 winedevice.exe 0000002e 0 0000002d 0 0000002a 0 0000002f QQPMSRV.exe 0000003b 0 00000039 0 00000036 0 00000030 0 00000031 explorer.exe 00000035 0 00000034 0 00000033 0 00000032 0 00000052 svchost.exe 0000005c 0 0000005b 0 00000059 0 00000058 0 00000053 0 System information: Wine build: wine-1.9.15 Platform: i386 Version: Windows XP Host system: Linux Host version: 4.2.0-42-generic fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:msvcrt:__clean_type_info_names_internal (0x1005f874) stub fixme:msvcrt:__clean_type_info_names_internal (0x237207a0) stub fixme:advapi:UnregisterTraceGuids deadbeef: stub fixme:msvcrt:__clean_type_info_names_internal (0x238426f0) stub fixme:wtsapi:WTSQueryUserToken 1 0x82d418 fixme:wtsapi:WTSQueryUserToken 1 0x82d440 fixme:wtsapi:WTSQueryUserToken 1 0x82d8e4 fixme:wtsapi:WTSQueryUserToken 1 0x82d8ec fixme:advapi:RegisterEventSourceW ((null),L"QPCore"): stub fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x00000000,(nil),0x0001,0x00000000,0x72e780,(nil)): stub fixme:advapi:DeregisterEventSource (0xcafe4242) 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.

1 9

[Bug 40828] New: Switching resolution in desktop mode makes task bar redraw on top of full screen game
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=40828 Bug ID: 40828 Summary: Switching resolution in desktop mode makes task bar redraw on top of full screen game Product: Wine Version: 1.9.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- I got this issue with Aliens versus Predator Classic 2000 on Steam. Preamble : The game uses 800x600 screen size to render cinematic and the main menu. The gameplay uses whatever screen resolution is set in the game video options menu. It switches between those two resolutions when starting or abandoning a level or when showing an in-game cinematic. The Wine virtual desktop mode is set to the native screen resolution that is the same resolution used for gameplay. When the game does not run, the Steam window and the task bar are visible and working properly. Steam puts an icon in the notification tray of the task bar. Issue : When the game is launched it switches the desktop to 800x600 to show the intro cinematic. The task bar is visible and covers the bottom of the full-screen game. The cinematics are letter-boxed and the menu has nothing of importance on those few bottom pixels so it's not that much a problem. When starting a level, the game switches to the native screen resolution, but the task bar still covers the bottom of the screen. The game can be played as the task bar does not hide much but it contrasts with the game and should be hidden by the full-screen app anyway. Workaround : The game grabs the mouse, so it is by default not possible to click on the window button on the task bar to refresh the game window, but activating the Steam game overlay frees the mouse cursor, and allow to click on the window button on the task bar. Clicking on that button twice makes the game window redraw over the task bar. The Steam overlay can then be closed and the game can be played with the task bar hidden. However, starting/abandoning a level or viewing a cinematic makes the game switch resolution and the task bar come back. -- 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 45

[Bug 40433] New: Fifa 11 EU demo fails to install when run from custom DVD
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=40433 Bug ID: 40433 Summary: Fifa 11 EU demo fails to install when run from custom DVD Product: Wine Version: 1.7.29 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: wylda(a)volny.cz Distribution: --- "Fifa 11 EU Demo" fails to install from DVD created by myself under wine-1.9.7-118-gaaddf13. This demo is distributed as zip file. I took to content of the ZIP and created the ISO by MagicISO. As a volume label i chose "fifa2011_eu_demo". When i copy content of the DVD back to some folder on HDD, then the installation succeeded. This could be interpreted as invalid bug report, but this DVD, created by me, works under Win8.1. Installer pops-up at the end "Please insert the disc: FIFA 11 Demo". Console: "err:msi:msi_view_get_row Error fetching data for 1" This is a regression caused by wine-1.7.28-130-g5cb10c9: commit 5cb10c96b26d07b7d0aabe3b8e337c7ce144b8af Author: Hans Leidekker <hans(a)codeweavers.com> Date: Wed Oct 15 15:30:23 2014 +0200 msi: Don't skip the media check for the first volume. Some installers require the first volume to be reinserted. This commit fixed bug 20444. This commit was also indicated as a regression in bug 38401. There he did reverse, i.e. real DVD copied and created ISO which finally worked. IMHO he interpreted it as invalid by mistake. -- 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 31

[Bug 38066] New: Memento Mori (Numen: Contest of Heroes): mouse buttons don't work (needs native dinput8)
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=38066 Bug ID: 38066 Summary: Memento Mori (Numen: Contest of Heroes): mouse buttons don't work (needs native dinput8) Product: Wine Version: 1.7.36 Hardware: x86 URL: http://www.4players.de/4players.php/download_info/Down loads/Download/50673/Memento_Mori/Deutsche_Demo.html OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Distribution: --- Created attachment 50710 --> https://bugs.winehq.org/attachment.cgi?id=50710 terminal output Keyboard is working in the game because I can skip the intro videos by pressing <Esc> and I can move the mouse pointer when the menu appears. Mouse buttons however are not registered thus I can't select a menu option. 'winetricks dinput8' is a workaround. I know of another game from the same publisher that also needs native dinput8 otherwise mouse buttons don't work: Numen: Contest of Heroes. To test the demo you need to install native d3dx9_36 and Windows Media Player 9 or 10. wine-1.7.36-28-ga679cae Fedora 21 XOrg 1.16.3 XFCE 4.10 Memento_Mori_DEMO_setup_GERMAN.exe md5sum: 8eda283807d43ad2a058c397efde7725 -- 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 7

[Bug 35320] New: wine crash in MSVCRT__mbstowcs_l regarding locale, & other minor locale related problems
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

http://bugs.winehq.org/show_bug.cgi?id=35320 Bug ID: 35320 Summary: wine crash in MSVCRT__mbstowcs_l regarding locale, & other minor locale related problems Product: Wine Version: 1.7.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: htl10(a)users.sourceforge.net Classification: Unclassified Created attachment 47106 --> http://bugs.winehq.org/attachment.cgi?id=47106 The file needed to cause the crash. from r project (http://www.r-project.org/) http://cran.ma.imperial.ac.uk/bin/windows/base/R-2.15.3-win.exe After installing, running: ./wine ~/.wine/drive_c/Program\ Files/R/R-2.15.3/bin/R.exe Then, at the R console prompt, type (having put the attached file at /tmp/1.R): Sys.setlocale("LC_CTYPE", "Chinese") source('z:/tmp/1.R', encoding='UTF8') wine immediately crashes with: -------------------------------------- wine: Unhandled page fault on read access to 0x00000000 at address 0x7eda29af (thread 0030), starting debugger... ... Backtrace: =>0 0x7eda29af MSVCRT__mbstowcs_l+0x5f(wcstr=<couldn't compute location>, mbstr=<couldn't compute location>, count=<couldn't compute location>, locale=<couldn't compute location>) [/home/Nobak-Hin-Tak/tmp-git/wine/dlls/msvcrt/mbcs.c:2140] in msvcrt (0x0440a168) 1 0x7eda2b06 MSVCRT_mbstowcs+0x35(wcstr="as a &Metafile CTRL+W", mbstr=0x0(nil), count=0x64) [/home/Nobak-Hin-Tak/tmp-git/wine/dlls/msvcrt/mbcs.c:2161] in msvcrt (0x0440a198) 2 0x6355b525 in rgraphapp (+0x1b524) (0x00030046) 0x7eda29af MSVCRT__mbstowcs_l+0x5f [/home/Nobak-Hin-Tak/tmp-git/wine/dlls/msvcrt/mbcs.c:2140] in msvcrt: movzbl 0x0(%eax),%eax 2140 if(mbstr[size] == '\0') ... ---------------------------------------- I assume this info in the backtrace should be enough to address the crash. FYI, the slightly unusual procedure is because under R under Vista in an English locale doesn't like to plot graphs with non-latin annotations/texts. The above procedure when used under Vista on British English windows would result in R displaying an almost empty plot with a chinese title. Native R on linux does not need the setlocale part to plot utf8-based texts. Also R on Vista accepts 'Sys.setlocale("LC_CTYPE", "Chinese_China.950")'. I only realized that trying to set traditional chinese [950] in a simplified chinese region [china] is wrong when it is rejected on linux; but R on Vista accepts this. ------------ Warning message: In Sys.setlocale("LC_CTYPE", "Chinese_China.950") : OS reports request to set locale to "Chinese_China.950" cannot be honored ------------ When R is running on Vista, it reports the locale as "English_United Kingdom.1252". But under Linux (in en_GB.utf8 locale), R warns of ----------- During startup - Warning messages: 1: Setting LC_TIME=en_GB.utf8 failed 2: Setting LC_MONETARY=en_GB.utf8 failed ----------- So three locale related issue: - a crash in msvcrt - R under Vista accepts "Chinese_China.950" but R under wine does not. - there are locale-related warning messages from R on start up when running under wine. -- 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 13