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

[Bug 24576] New: Final Fantasy XIV: Live Client Launch Fails
by wine-bugs＠winehq.org 02 Oct '18

02 Oct '18

http://bugs.winehq.org/show_bug.cgi?id=24576 Summary: Final Fantasy XIV: Live Client Launch Fails Product: Wine Version: 1.2 Platform: x86 URL: http://www.finalfantasyxiv.com OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: senjion(a)gmail.com I was able to get the client installed easily just running the installer through wine, patching was an issue as it seems to have been in Beta, however after the install I copied in an already patched version of the game which allowed me to get past the Version Check and patching process. Now when running ffxivboot.exe the game loads the Login Screen properly. I can enter credentials and it logs in fine and then goes to the Launcher page. On the Launcher Page I can get into Account Management just fine, however if I click on the big red "Play" button nothing happens, it seems like the Launch page just refreshes. After logging in I tried leaving the Launcher page up and just executing ffxivgame.exe however it acts like it is trying to launch and then simply crashes. Wine Configuration has Audio set to OSS instead of ALSA. All graphics in ffxiv config are set to the lowest possible settings. I have tried with both Hardware Mouse enabled and disabled via ffxiv config, and with sound enabled and disabled aswell. If there is any data I can collect to assist in troubleshooting let me know. -- 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 14

[Bug 14601] New: Easter egg of WinRAR do very slow speed of application
by wine-bugs＠winehq.org 01 Oct '18

01 Oct '18

http://bugs.winehq.org/show_bug.cgi?id=14601 Summary: Easter egg of WinRAR do very slow speed of application Product: Wine Version: 1.0.0 Platform: All OS/Version: All Status: UNCONFIRMED Severity: enhancement Priority: P5 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: Zenitur(a)yandex.ru In About window you can see logo (icon) and logo (WinRAR word on the sea). First logo is in 16 colors, this is strange: in Windows this is full-colored. Double clicking do easter egg: it jump to down of window! Double clicking on second logo (big WinRAR word) can do second easter egg, but it make very small speed of application! Double click fix this. -- 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 20

[Bug 31226] New: MathCad 15 installer fails without native dotnet35sp1
by wine-bugs＠winehq.org 29 Sep '18

29 Sep '18

http://bugs.winehq.org/show_bug.cgi?id=31226 Bug #: 31226 Summary: MathCad 15 installer fails without native dotnet35sp1 Product: Wine Version: 1.5.8 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified Tried repeating bug 31201 without native dotnet35sp1. When the installer's progress bar hits about 50%, I get a dialog Fatal error in gc GetThreadContext failed Using ps, I see it's coming from "C:\users\dank\Temp\msi1c95.tmp HandBooks" This is a 24KB .net executable, and running it by hand while that dialog is still up generates another instance of the fatal error. One sees lots of this error message on the web, mostly from Unity3d apps conflicting with antivirus programs. I also recall seeing this before when using Mono in Wine, so it's not specific to this app. See also bug 30914 for another GetThreadContext failure which may be the same problem. -- 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 5

[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