[Bug 39985] New: Battle.net fails to start with an error dialog pointing to Qt with wine staging, but not with regular wine
https://bugs.winehq.org/show_bug.cgi?id=39985 Bug ID: 39985 Summary: Battle.net fails to start with an error dialog pointing to Qt with wine staging, but not with regular wine Product: Wine Version: 1.9.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: krafczyk.matthew(a)gmail.com Distribution: --- When starting Battle.net with wine-staging 1.9.1, the program fails to start with an error dialog with the following text: "This application failed to start because it could not find or load the Qt platform plugin "windows". Reinstalling the application may fix this problem." If you then switch to regular wine 1.9.1, the program starts as expected without the error dialog. I'm running Arch, and I've installed Battle.net into a 32-bit prefix with the environment variable WINEARCH=win32 You can download Battle.net from here: http://www.battle.net/download/getInstallerForGame?os=win&locale=enUS&versio... -- 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.
https://bugs.winehq.org/show_bug.cgi?id=39985 Matthew Krafczyk <krafczyk.matthew(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux -- 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.
https://bugs.winehq.org/show_bug.cgi?id=39985 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erich.e.hoover(a)wine-staging | |.com, michael(a)fds-team.de, | |sebastian(a)fds-team.de Component|-unknown |-unknown Product|Wine |Wine-staging --- Comment #1 from Sebastian Lackner <sebastian(a)fds-team.de> --- Moving to wine-staging category since it could be a Staging regression. I'll do some further investigation. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=39985 evilny0 <evilny0(a)moomoocamp.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |evilny0(a)moomoocamp.net --- Comment #2 from evilny0 <evilny0(a)moomoocamp.net> --- I have the same problem in my Diablo prefix. Copying Battle.net.6526 folder from another prefix (my wow install) is solving the issue. A recursive diff between those folders shows no difference. The permissions on files were different so I changed them to be the same, but it did not solve it. I'll continue to investigate... -- 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.
https://bugs.winehq.org/show_bug.cgi?id=39985 --- Comment #3 from evilny0 <evilny0(a)moomoocamp.net> --- Issue lies with qwindows.dll. It's the same file in both folders (compared with md5sum), but when I change it, it just works. The only difference I can see is the date. The working one is from december 2015, the other one is from yesterday. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=39985 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Sebastian Lackner <sebastian(a)fds-team.de> --- This issue should be fixed with: https://github.com/wine-compholio/wine-staging/commit/a560ca2cee4a4b5cadad73... Please retest with current Wine Staging git, or alternatively backport the newly added patch to 1.9.1 . Please note that its either necessary to reinstall Battle.Net, or alternatively to remove user.DOSATTRIB extended file attributes from files located in the Program Files/Battle.net directory (setfattr -x could be used for that). Some more technical details: During the installation process, Battle.Net creates a bunch of temporary files starting with ".". Wine interpreted them as hidden, and since Wine Staging supports proper file attributes, the hidden attribute was also copied when the files were later installed. This confused the code to load Qt because it doesn't take into account hidden files. The same issue would also happen in the development branch except that storing file attributes is not implemented yet. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=39985 --- Comment #5 from Matthew Krafczyk <krafczyk.matthew(a)gmail.com> --- I can report that with the latest wine from git with the latest wine-staging patches from git, that Battle.net now installs without giving me the Qt error. Thanks for working to fix this issue Sebastian! -- 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.
https://bugs.winehq.org/show_bug.cgi?id=39985 --- Comment #6 from evilny0 <evilny0(a)moomoocamp.net> --- Tested it as well, looks good, Battle.net installs fine :). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=39985 hash <HASH.DuOrden(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |HASH.DuOrden(a)gmail.com --- Comment #7 from hash <HASH.DuOrden(a)gmail.com> --- Well I didn't need to recompile/reinstall anything with "wine-1.9.1 (Staging)" just needed "setfattr -x user.DOSATTRIB ./Battle.net.6734/platforms/qwindows.dll" and it works. TY for info! -- 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.
https://bugs.winehq.org/show_bug.cgi?id=39985 Rainer Müller <raimue(a)codingfarm.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |raimue(a)codingfarm.de --- Comment #8 from Rainer Müller <raimue(a)codingfarm.de> --- (In reply to Sebastian Lackner from comment #4)
This issue should be fixed with: https://github.com/wine-compholio/wine-staging/commit/ a560ca2cee4a4b5cadad73e1883bd438e70328ad
Thanks for the detailed information and the patch. Initially I fixed it by removing the extended attribute. Now I backported the fixed patch to my wine-staging 1.8.0 and it works fine. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=39985 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #9 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Fixed Staging 3.14 -- 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.
participants (1)
-
wine-bugs＠winehq.org