http://bugs.winehq.org/show_bug.cgi?id=30608
Bug #: 30608 Summary: MK Arcade Kollection: Cannot launch game. Mouse inresponsive in Windowed Mode. Product: Wine Version: 1.5.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: linards.liepins@gmail.com Classification: Unclassified
Created attachment 40060 --> http://bugs.winehq.org/attachment.cgi?id=40060 Error log with console output.
After finally fixed the DirectX error message issue by performing this:
sudo yum install xorg-x11-drv-catalyst-libs.i686
, I am not unable to launch game anyway ... the Wine window is shown, the mouse is hidden and nothing happens ...
Attaching console log. Hopefully from that ton of fixme people could suggest fix or try to debug ...
http://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #1 from Linards linards.liepins@gmail.com 2012-05-06 04:28:38 CDT --- Possible fix: http://forum.winehq.org/viewtopic.php?p=74260&sid=a8066b27cbc0b41a0c3769...
http://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #2 from Linards linards.liepins@gmail.com 2012-05-06 04:37:24 CDT --- Nop, did not help, though attaching new error log. :) Hope it helps...
http://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #3 from Linards linards.liepins@gmail.com 2012-05-06 04:38:38 CDT --- Created attachment 40061 --> http://bugs.winehq.org/attachment.cgi?id=40061 Error log with GLSL disabled.
http://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #4 from Linards linards.liepins@gmail.com 2012-05-13 04:05:35 CDT --- It might be AMD driver bug.
http://wine.1045685.n5.nabble.com/Re-Halo-Combat-Evolved-with-black-text-and...
http://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #5 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.18 or newer) wine?
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #6 from Linards linards.liepins@gmail.com --- Still unable to launch game on wine 1.7.40.
At least now I get some debub information ( copied here because it s enough short to read w/o scrolling ):
[linards@KOMPIIC ~]$ wine '/home/linards/.wine/drive_c/Program Files (x86)/WB Games/Mortal Kombat Arcade Kollection/BINARIES/WIN32/MKHDGame.exe' fixme:d3d:wined3d_dxtn_init Wine cannot find the txc_dxtn library, DXTn software support unavailable. Connection to "Provider=sqloledb;Data Source=production-db;Initial Catalog=EngineTaskPerf;Trusted_Connection=Yes;Connection Timeout=2" or "10.1.10.83" failed fixme:gameux:GameExplorerImpl_VerifyAccess (0x14e1a0, L"C:\Program Files (x86)\WB Games\Mortal Kombat Arcade Kollection\BINARIES\WIN32\MKHDGame.exe", 0x254f2b0) fixme:d3d:swapchain_init Add OpenGL context recreation support to context_validate_onscreen_formats fixme:d3d:swapchain_init Add OpenGL context recreation support to context_validate_onscreen_formats fixme:nvapi:unimplemented_stub function 0xbe7692ec is unimplemented! fixme:nvapi:unimplemented_stub function 0x6c2d048c is unimplemented! fixme:d3d:getColorBits Unsupported format WINED3DFMT_R16G16B16A16_FLOAT. FUdpLink::BindPort: Socket was not created fixme:msvcrt:MSVCRT__set_abort_behavior _WRITE_CALL_REPORTFAULT unhandled fixme:msvcrt:__clean_type_info_names_internal (0x2f51230) stub fixme:msvcrt:__clean_type_info_names_internal (0x28d61ac) stub fixme:msvcrt:__clean_type_info_names_internal (0x2786018) stub fixme:msvcrt:__clean_type_info_names_internal (0x27eb168) stub fixme:msvcrt:__clean_type_info_names_internal (0x2796018) stub fixme:msvcrt:__clean_type_info_names_internal (0x277a630) stub
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #7 from Nikolay Sivov bunglehead@gmail.com --- (In reply to Linards from comment #6)
Still unable to launch game on wine 1.7.40.
fixme:d3d:wined3d_dxtn_init Wine cannot find the txc_dxtn library, DXTn software support unavailable.
There's no such thing in wine. Are you using custom patches?
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #8 from Linards linards.liepins@gmail.com --- (In reply to Nikolay Sivov from comment #7)
(In reply to Linards from comment #6)
Still unable to launch game on wine 1.7.40.
fixme:d3d:wined3d_dxtn_init Wine cannot find the txc_dxtn library, DXTn software support unavailable.
There's no such thing in wine. Are you using custom patches?
No:
[linards@KOMPIIC ~]$ wine --version wine-1.7.40 (Staging) [linards@KOMPIIC ~]$ cat /etc/*-release Fedora release 21 (Twenty One) NAME=Fedora VERSION="21 (Twenty One)" ID=fedora VERSION_ID=21 PRETTY_NAME="Fedora 21 (Twenty One)" ANSI_COLOR="0;34" CPE_NAME="cpe:/o:fedoraproject:fedora:21" HOME_URL="https://fedoraproject.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Fedora" REDHAT_BUGZILLA_PRODUCT_VERSION=21 REDHAT_SUPPORT_PRODUCT="Fedora" REDHAT_SUPPORT_PRODUCT_VERSION=21 Fedora release 21 (Twenty One) Fedora release 21 (Twenty One) [linards@KOMPIIC ~]$ yum info wine Loaded plugins: langpacks fedora/21/x86_64/metalink | 24 kB 00:00 fedora-cdrtools | 2.9 kB 00:00 google-chrome | 951 B 00:00 rpmfusion-free | 1.2 kB 00:00 rpmfusion-free-updates | 2.7 kB 00:00 rpmfusion-nonfree | 1.2 kB 00:00 rpmfusion-nonfree-updates | 2.7 kB 00:00 updates/21/x86_64/metalink | 19 kB 00:00 updates | 3.4 kB 00:00 http://fedora.mirrors.telekom.ro/pub/fedora/linux/updates/21/x86_64/repodata...: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror. updates | 4.9 kB 00:00 (1/3): fedora-cdrtools/21/x86_64/primary_db | 4.9 kB 00:00 (2/3): updates/21/x86_64/group_gz | 230 kB 00:00 (3/3): updates/21/x86_64/primary_db | 7.7 MB 00:07 (1/5): google-chrome/primary | 1.9 kB 00:00 (2/5): rpmfusion-free-updates/21/x86_64/primary_db | 220 kB 00:00 (3/5): rpmfusion-nonfree-updates/21/x86_64/primary_db | 104 kB 00:01 (4/5): updates/21/x86_64/updateinfo | 1.2 MB 00:02 (5/5): updates/21/x86_64/pkgtags | 1.5 MB 00:02 google-chrome 3/3 rpmfusion-free 470/470 rpmfusion-nonfree 178/178 Installed Packages Name : wine Arch : x86_64 Version : 1.7.40 Release : 1.fc21 Size : 0.0 Repo : installed
From repo : updates
Summary : A compatibility layer for windows applications URL : http://www.winehq.org/ License : LGPLv2+ Description : Wine as a compatibility layer for UNIX to run Windows : applications. This package includes a program loader, which allows : unmodified Windows 3.x/9x/NT binaries to run on x86 and x86_64 : Unixes. Wine can use native system .dll files if they are : available. : : In Fedora wine is a meta-package which will install everything : needed for wine to work smoothly. Smaller setups can be achieved : by installing some of the wine-* sub packages.
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #9 from Nikolay Sivov bunglehead@gmail.com --- (In reply to Linards from comment #8)
(In reply to Nikolay Sivov from comment #7)
(In reply to Linards from comment #6)
Still unable to launch game on wine 1.7.40.
fixme:d3d:wined3d_dxtn_init Wine cannot find the txc_dxtn library, DXTn software support unavailable.
There's no such thing in wine. Are you using custom patches?
No:
[linards@KOMPIIC ~]$ wine --version wine-1.7.40 (Staging)
That means yes. Fedora apparently decided to build from staging repo, which means that you should to retest with plain wine first and report bugs here using plain wine.
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #10 from Linards linards.liepins@gmail.com --- Is it possible to easily switch to 'plain' wine w/o re-installing wine packages? It would take way too much time in my case...
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #11 from Austin English austinenglish@gmail.com --- (In reply to Linards from comment #10)
Is it possible to easily switch to 'plain' wine w/o re-installing wine packages? It would take way too much time in my case...
Ask Fedora's packagers, but you'll likely need to compile from source.
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #12 from Linards linards.liepins@gmail.com --- (In reply to Austin English from comment #11)
(In reply to Linards from comment #10)
Is it possible to easily switch to 'plain' wine w/o re-installing wine packages? It would take way too much time in my case...
Ask Fedora's packagers, but you'll likely need to compile from source.
I was afraid you will give this answer. So, I, as end user, have been pushed to corner just because: 1) Fedora ripped off normal way to support Wine and give fully legit reports ( even though I do not understand fully why patched wine ( with patches, accessible in github / winehq attachments and therefore fully transparent and reversable ) is not valid ) about Wine; 2) WineHQ Devs are not capable of supporting patched wine codebase.
This shocks my to the roots. Don't know which should be punched to face ... Fedora packagers or Wine packagers ... Cant imagine how much feedback winehq looses by allowing such b***s**t to happen. I even cant remember any (kind of) warning that I will not be qualified to submmit bug reports after using Staging package(s). :(
Ok, I guess this automatically goes to INVALID WONTFIX? :(
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #13 from Linards linards.liepins@gmail.com --- (In reply to Austin English from comment #11)
(In reply to Linards from comment #10)
Is it possible to easily switch to 'plain' wine w/o re-installing wine packages? It would take way too much time in my case...
Ask Fedora's packagers, but you'll likely need to compile from source.
P.S. Not offence, mate. I do not intend to so criticize WineHQ work. You are doing outstanding and valuable work! ;)
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #14 from Nikolay Sivov bunglehead@gmail.com --- (In reply to Linards from comment #12)
(In reply to Austin English from comment #11)
(In reply to Linards from comment #10)
Is it possible to easily switch to 'plain' wine w/o re-installing wine packages? It would take way too much time in my case...
Ask Fedora's packagers, but you'll likely need to compile from source.
I was afraid you will give this answer. So, I, as end user, have been pushed to corner just because:
- Fedora ripped off normal way to support Wine and give fully legit reports
( even though I do not understand fully why patched wine ( with patches, accessible in github / winehq attachments and therefore fully transparent and reversable ) is not valid ) about Wine;
Basically wine-staging is winehq codebase plus hundreds of patches. And yes, it was Fedora maintainer decision to use it instead of vanilla wine.
- WineHQ Devs are not capable of supporting patched wine codebase.
Winehq has no control over wine-staging.
This shocks my to the roots. Don't know which should be punched to face ... Fedora packagers or Wine packagers ... Cant imagine how much feedback winehq looses by allowing such b***s**t to happen. I even cant remember any (kind of) warning that I will not be qualified to submmit bug reports after using Staging package(s). :(
There's only distro packagers, as winehq itself doesn't provide builds, only source code.
Ok, I guess this automatically goes to INVALID WONTFIX? :(
You could try to report this problem to wine-staging bugzilla first, look it up.
https://bugs.winehq.org/show_bug.cgi?id=30608
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #15 from Linards linards.liepins@gmail.com --- (In reply to Nikolay Sivov from comment #14)
(In reply to Linards from comment #12)
(In reply to Austin English from comment #11)
(In reply to Linards from comment #10)
Is it possible to easily switch to 'plain' wine w/o re-installing wine packages? It would take way too much time in my case...
Ask Fedora's packagers, but you'll likely need to compile from source.
I was afraid you will give this answer. So, I, as end user, have been pushed to corner just because:
- Fedora ripped off normal way to support Wine and give fully legit reports
( even though I do not understand fully why patched wine ( with patches, accessible in github / winehq attachments and therefore fully transparent and reversable ) is not valid ) about Wine;
Basically wine-staging is winehq codebase plus hundreds of patches. And yes, it was Fedora maintainer decision to use it instead of vanilla wine.
- WineHQ Devs are not capable of supporting patched wine codebase.
Winehq has no control over wine-staging.
This shocks my to the roots. Don't know which should be punched to face ... Fedora packagers or Wine packagers ... Cant imagine how much feedback winehq looses by allowing such b***s**t to happen. I even cant remember any (kind of) warning that I will not be qualified to submmit bug reports after using Staging package(s). :(
There's only distro packagers, as winehq itself doesn't provide builds, only source code.
Ok, I guess this automatically goes to INVALID WONTFIX? :(
You could try to report this problem to wine-staging bugzilla first, look it up.
I see.
Thank you for explanation(s), Nikolay.
Cheers.
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #16 from Linards linards.liepins@gmail.com --- Is it possible to export to wine-staging bugzilla this bug or I have manually copy text into it?
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #17 from Linards linards.liepins@gmail.com --- Bug migrated to wine-staging bugzilla: https://bugs.wine-staging.com/show_bug.cgi?id=373
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #18 from Linards linards.liepins@gmail.com --- Created attachment 51854 --> https://bugs.winehq.org/attachment.cgi?id=51854 Game Built-in Launch.log
Further investigation reveals the attached log and the information in the link http://forums.steampowered.com/forums/showthread.php?t=2519777, stating:
"I've found the temporary solution.
The error was caused by incomplete Unicode support. The game seems to use some weird characters on filename which are not supported by non-English code system.
To solve this,
Set 'Current language for non-Unicode programs' to 'English'
You can find it on Windows Control Panel. Control Panel > Region and Language > Administrative.
You need to reboot the computer after changing the option.
Cheers!"
https://bugs.winehq.org/show_bug.cgi?id=30608
Linards linards.liepins@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |19417
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #19 from Linards linards.liepins@gmail.com --- After research, found on https://bugs.wine-staging.com/show_bug.cgi?id=373#c10, game depends on:
- .NET 3.5, which depends on 32-bit WINEPREFIX.
https://bugs.winehq.org/show_bug.cgi?id=30608
Linards linards.liepins@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on|19417 |
https://bugs.winehq.org/show_bug.cgi?id=30608
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #40060|application/octet-stream |text/plain mime type| |
https://bugs.winehq.org/show_bug.cgi?id=30608
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #40061|0 |1 is obsolete| | Attachment #40061|application/octet-stream |text/plain mime type| |
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #20 from Ken Sharp imwellcushtymelike@gmail.com --- So you're saying that the game needs Dotnet 3.5, and the lack of it, in fact, causes this error? There's nothing in the logs to suggest that. In fact there's nothing clear about this bug report at all.
I think that this should be closed invalid until a valid bug report can be built.
https://bugs.winehq.org/show_bug.cgi?id=30608
--- Comment #21 from Linards linards.liepins@gmail.com --- (In reply to Ken Sharp from comment #20)
So you're saying that the game needs Dotnet 3.5, and the lack of it, in fact, causes this error? There's nothing in the logs to suggest that. In fact there's nothing clear about this bug report at all.
I think that this should be closed invalid until a valid bug report can be built.
Yes, that is my assumption. A fully agree that built-in logs and winedbg (by default) do not provide anything obvious ( like unimplemented function or missing feature level ). Anyways, if you feel it is right way - I have no problem with that. Of course, for full clarity Dan should take a look on wine-staging ticket as he is maintainer of UDK software...
https://bugs.winehq.org/show_bug.cgi?id=30608
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #22 from Austin English austinenglish@gmail.com --- (In reply to Linards from comment #21)
(In reply to Ken Sharp from comment #20)
So you're saying that the game needs Dotnet 3.5, and the lack of it, in fact, causes this error? There's nothing in the logs to suggest that. In fact there's nothing clear about this bug report at all.
I think that this should be closed invalid until a valid bug report can be built.
Yes, that is my assumption. A fully agree that built-in logs and winedbg (by default) do not provide anything obvious ( like unimplemented function or missing feature level ). Anyways, if you feel it is right way - I have no problem with that. Of course, for full clarity Dan should take a look on wine-staging ticket as he is maintainer of UDK software...
Invalid.
https://bugs.winehq.org/show_bug.cgi?id=30608
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #23 from Bruno Jesus 00cpxxx@gmail.com --- Closing invalid bugs.