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

[Bug 25192] New: 'fatal error in gc: collecting from unknown thread' with Mono
by wine-bugs＠winehq.org 29 Sep '18

29 Sep '18

http://bugs.winehq.org/show_bug.cgi?id=25192 Summary: 'fatal error in gc: collecting from unknown thread' with Mono Product: Wine Version: 1.3.7 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sam(a)robots.org.uk Created an attachment (id=31979) --> (http://bugs.winehq.org/attachment.cgi?id=31979) test case script I'm trying to run Wix, a .NET application, on Wine. In order to do this I am using the mono-gtksharp installer from <http://ftp.novell.com/pub/mono/archive/2.8/windows-installer/9/mono-2.8-gtk…>. When building an installer, I get the following error: fatal error in gc Collecting from unknown thread Some digging around reveals that this message comes from Mono's use of the Boehm garbage collector. There is a bug open in their tracker that talks about the error <https://bugzilla.novell.com/show_bug.cgi?id=323578>; they seem to consider it a bug in Wine. I'll attach a shell script that reproduces this from scratch, almost automatically. You just have to download Wix3.msi and drop it in the same directory as test.sh. -- 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.

1 15

[Bug 34522] New: Drakan: Order of the Flame demo crashes before entering the main menu
by wine-bugs＠winehq.org 28 Sep '18

28 Sep '18

http://bugs.winehq.org/show_bug.cgi?id=34522 Bug #: 34522 Summary: Drakan: Order of the Flame demo crashes before entering the main menu Product: Wine Version: 1.7.2 Platform: x86 URL: http://www.fileplanet.com/11604/10000/fileinfo/Drakan- Demo OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dmusic AssignedTo: wine-bugs(a)winehq.org ReportedBy: andrey.goosev(a)gmail.com Classification: Unclassified Created attachment 45962 --> http://bugs.winehq.org/attachment.cgi?id=45962 log+backtrace Crashes after intro movies. -- 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.

1 18

[Bug 27288] New: Facade installation ends prematurely when installing to a directory name with a space
by wine-bugs＠winehq.org 28 Sep '18

28 Sep '18

http://bugs.winehq.org/show_bug.cgi?id=27288 Summary: Facade installation ends prematurely when installing to a directory name with a space Product: Wine Version: 1.3.20 Platform: x86-64 URL: http://www.interactivestory.net/download/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: asb(a)asbradbury.org Created an attachment (id=34897) --> (http://bugs.winehq.org/attachment.cgi?id=34897) console log Tested in self-built wine 1.3.20, git HEAD, and 1.2.3. When installing Facade with the default destination directory (C:\Program Files\Facade) and a fresh WINEPREFIX, the installation ends prematurely. Interestingly, choosing 'C:\Facade' as the destination directory works, as does 'C:\Test\This\Facade', while 'C:\Faceade Space' also fails. (to reproduce, remember to delete the WINEPREFIX in between, or the installer will erroneously report success). See the attached console log. -- 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.

1 18

[Bug 34739] New: manual install of wine gecko gets in the wrong directory in Wow64 wine
by wine-bugs＠winehq.org 28 Sep '18

28 Sep '18

http://bugs.winehq.org/show_bug.cgi?id=34739 Bug #: 34739 Summary: manual install of wine gecko gets in the wrong directory in Wow64 wine Product: Wine-gecko Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-gecko-unknown AssignedTo: jacek(a)codeweavers.com ReportedBy: roland65(a)free.fr Classification: Unclassified When installing the gecko msi package with : msiexec /i wine_gecko-2.21-x86_64.msi on a wine 1.6 WoW64 architecture, then the gecko files are installed in c:\windows\syswow64 directory instead of c:\windows\system32. Thus, 64 bits iexplore doesn't work in this architecture. Note that a manual install of wine_gecko-2.21-x86.msi goes correctly into c:\windows\syswow64. -- 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.

1 9

[Bug 18271] New: MSI creates incompatible msi file in a specific case of create table
by wine-bugs＠winehq.org 28 Sep '18

28 Sep '18

http://bugs.winehq.org/show_bug.cgi?id=18271 Summary: MSI creates incompatible msi file in a specific case of create table Product: Wine Version: 1.1.20 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P5 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: tijnema(a)gmail.com Created an attachment (id=20797) --> (http://bugs.winehq.org/attachment.cgi?id=20797) Test application for this bug (source and binary) I was doing some testing on MSI, and figured that when using only 1 column in a table with only 1 character, wine's msi implementation fails to create a correct msi file. When opening the msi file with orca, orca crashes after selecting the table. Using native dll override for msi.dll, a correct msi file is generated. The query I am using is CREATE TABLE testTable (b INT PRIMARY KEY b) Test application built in VS2008 (source and binary) is attached, it needs vcredist package from microsoft to run. -- 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.

1 17

[Bug 23487] New: Buccaneer: freezes when changing screen resolution
by wine-bugs＠winehq.org 28 Sep '18

28 Sep '18

http://bugs.winehq.org/show_bug.cgi?id=23487 Summary: Buccaneer: freezes when changing screen resolution Product: Wine Version: 1.2-rc6 Platform: x86 URL: http://www.bigdownload.com/games/buccaneer-the-pursuit -of-infamy/pc/buccaneer-the-pursuit-of-infamy-demo/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Created an attachment (id=29315) --> (http://bugs.winehq.org/attachment.cgi?id=29315) standard console log The game Buccaneer: The Pursuit of Infamy (an arcadish Pirates! clone) becomes unresponsive when changing in-game screen resolution. This occurs both in Wine's virtual desktop mode and in fullscreen. If you untick the 'Fullscreen' option in the game (so it runs in windowed mode), the freezing doesn't happen and I can switch resolutions successfully. The game uses the Torque engine, there are D3D9 and OpenGL rendering modes available. However selecting OpenGL rendering from the options menu doesn't have an effect: the game always resets itself to the default D3D9 renderer. You can check out the issue using the demo (122 Mb download size), I added the link to URL. How to reproduce the issue in the demo: 1. Install the demo and start it by T3D.exe. The game will notify you about the latest update, you can install it, the game will restart after updating. 2. Go to 'Help & Options' in the menu, then select 'Settings'. Change the screen resolution (default is 1024x768) and press 'Apply graphic changes' >> the game will hang, although music is playing on, and htop shows the game executable still consumes 50-60 % CPU. Workaround: playing the game in windowed mode. I attached the console output when the game freezes. I added winedebug=-dsound to the command line to suppress the tons of dsound related fixmes in the log. Fedora 13 x86 Wine-1.2-rc6 Nvidia 7600 GT / driver 195.36.31 -- 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.

1 7

[Bug 38742] New: Watch_Dogs fail to run after successful Uplay installation
by wine-bugs＠winehq.org 28 Sep '18

28 Sep '18

https://bugs.winehq.org/show_bug.cgi?id=38742 Bug ID: 38742 Summary: Watch_Dogs fail to run after successful Uplay installation Product: Wine Version: 1.7.44 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tomasz.piotr.kowalczyk(a)gmail.com Distribution: --- I run Ubuntu 14.04 and tried to play Watch_Dogs. My steps: * install PlayOnLinux * create x64 container for WD (latest WINE 1.7.44) * install Uplay from .exe from its website * login and install WD When I click "play" Uplay installs other related packages (don't remember exact names but there were 9 of them) like DirectX, VC2008, VS2010 and .NET Framework, on which it hangs for more than an hour, but after some fiddling (closing and retrying) finally passes. I'm greeted with the error about ntlm_auth which was fixed by installing winbind, but then I get the error: error Disrupt_b64.dll, procedure entry point __crt_debugger_hook could not be loaded in the dynamic link library MSVCR100.dll I read somewhere that this error is caused by something other and it's just a stub so I opened POL logs and found: fixme:heap:RtlSetHeapInformation 0x690000 0 0x23fc90 4 stub fixme:heap:RtlSetHeapInformation 0x7a0000 0 0x23fc90 4 stub fixme:heap:RtlSetHeapInformation 0x8b0000 0 0x23fc90 4 stub fixme:heap:RtlSetHeapInformation 0xad0000 0 0x23fca0 4 stub fixme:heap:RtlSetHeapInformation 0xe00000 0 0x23fc90 4 stub err:module:attach_process_dlls "Disrupt_b64.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files (x86)\\Ubisoft\\Ubisoft Game Launcher\\games\\Watch_Dogs\\bin\\watch_dogs.exe" failed, status c0000142 and a bunch of: fixme:gdiplus:GdipCreateFontFamilyFromName No support for FontCollections yet! I can provide any necessary information, please guide me what should I do in this situation. I tried installing gdiplus package using winetricks but that only created a bunch of other errors (haven't saved those and unfortunately removed them) and I'd like to know the other way before downloading those ~20GiB again. I found error #36713 which seems related (same error message) but as I wrote above I use a "fixed" version 1.7.44 and there wasn't any mention of what went wrong, just that "DLL failed to initialize". -- 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

[Bug 39020] New: aSc TimeTables 2016 (trial): window scrollbar is slow to respond
by wine-bugs＠winehq.org 28 Sep '18

28 Sep '18

https://bugs.winehq.org/show_bug.cgi?id=39020 Bug ID: 39020 Summary: aSc TimeTables 2016 (trial): window scrollbar is slow to respond Product: Wine Version: 1.7.40 Hardware: x86 URL: http://www.asctimetables.com/download/aScTimeTables.ex e OS: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: windowscodecs Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: madewokherd(a)gmail.com Distribution: --- There is a noticeable (1-1.5 sec) lag when scrolling the window content in 'aSc Timetables 2016'. To reproduce the problem in the trial version: 1.install & start the application, select language. 2.in the main menu press the 4th button from the left in the toolbar (<show demo files> if you selected English language). 3. in the selection window on the left use the scrollbar to scroll through the list. You should notice that scrolling is laggy, comes to a halt frequently. In the terminal I have >fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub >fixme:shell:SetCurrentProcessExplicitAppUserModelID L"aSc.TimeTables.AppID": stub >fixme:dwmapi:DwmIsCompositionEnabled 0x33ca30 >fixme:appbar:SHAppBarMessage unknown msg: 4 >fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETSTATE): stub >... >libpng warning: Incorrect sBIT chunk length >fixme:richedit:ME_HandleMessage EM_SETMARGINS: stub >libpng warning: Incorrect sBIT chunk length Even if it's technically not a regression, should be noted that the slow scrolling was introduced by commit f2f5cd831bdda21deef1fca67febe78fb174d582 Author: Vincent Povirk <vincent(a)codeweavers.com> Date: Wed Mar 25 14:42:15 2015 -0500 windowscodecs: Implement PngDecoder_Block_GetReaderByIndex. Reverting the commit on current git, or native gdiplus.dll (comes with the installed application) fixes the problem and the scrollbar is moving smoothly. wine-1.7.48-74-gb3fe96a Fedora 22 / libpng-1.6.16-3.fc22.i686 XOrg 1.17.2 aScTimeTables.exe sha1: 284c69284415b35634a109444ad0d1c08ece63a0 -- 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 28000] New: World War One Gold hangs during the initial loading stage
by wine-bugs＠winehq.org 28 Sep '18

28 Sep '18

http://bugs.winehq.org/show_bug.cgi?id=28000 Summary: World War One Gold hangs during the initial loading stage Product: Wine Version: 1.3.26 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Created an attachment (id=35848) --> (http://bugs.winehq.org/attachment.cgi?id=35848) plain terminal output World War One Gold Edition v1.08l never reaches the main menu after starting: the game always stops at the same point while loading (the progress bar reaches 95-98% when the loading process halts). The game is still using 100% CPU power, the mouse pointer is movable across the screen and music is playing but nothing else happens (I've waited for about 15 minutes just to be sure). The same problem when trying to start the game in Wine-1.0.1, 1.2.3 etc. The game was installed in a clean wineprefix, no native dlls were used. I found out that adding WINEDEBUG=warn+heap to the command line makes it possible to reach the main menu. No additional lines in the terminal appeared when warn+heap was used. -- 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.

1 9

[Bug 41325] New: Actions of MSI installer properties missing or wrong
by wine-bugs＠winehq.org 28 Sep '18

28 Sep '18

https://bugs.winehq.org/show_bug.cgi?id=41325 Bug ID: 41325 Summary: Actions of MSI installer properties missing or wrong Product: Wine Version: 1.9.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: reinhold.hoffmann(a)hotmail.com Distribution: --- The MSI installer offers properties for uninstalling. The properties ARPNOREPAIR ARPNOMODIFY APRNOREMOVE are not considered. The above properties need to result in the following Registry entries: ARPNOREPAIR: NoRepair = 1 ARPNOMODIFY: NoModify = 1 APRNOREMOVE: NoRemove = 1 in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{product key} Those Registry entries are not taken from the installer msi file and are missing. Adding those Registry entries manually in the Registry result in some actions/options of the uninstaller but those actions are not correct. E.g. when NoRepair = 1 is set, the user can still repair the product, or for NoRemove = 1 the product can still be removed etc. A Remove/Repair windows should not show up at all when the according actions is blocked. Please compare with Windows' Control Panel. When corecting this software area I recommend to also fix the System Information of the uninstaller. The System Information should reflect what came in by the msi installer (that from the above Registry key). -- 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 2