[Bug 38262] New: Warframe Update Fails!
https://bugs.winehq.org/show_bug.cgi?id=38262 Bug ID: 38262 Summary: Warframe Update Fails! Product: Wine Version: 1.7.38 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: levanchelidze(a)gmail.com Distribution: --- Created attachment 51091 --> https://bugs.winehq.org/attachment.cgi?id=51091 terminal output I created a 32-bit wine prefix and installed warframe on But the launcher keeps crashing and shows this massage "update failed" http://i.imgur.com/hFD9t1k.png I will attache terminal output as well -- 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=38262 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, regression Status|UNCONFIRMED |NEW URL| |http://content.warframe.com | |/dl/Warframe.msi CC| |focht(a)gmx.net Component|-unknown |wininet Ever confirmed|0 |1 Regression SHA1| |5436fef80722fe7896aed5e659c | |31fdade4ef5b3 --- Comment #1 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, confirming. This ought to work some time ago, when I was investigating bug 37798 (Wine 1.7.33) Looks like a regression. http://source.winehq.org/git/wine.git/commit/5436fef80722fe7896aed5e659c31fd... That commit can't be cleanly reverted on current head without manual resolution. Revert to working state: --- snip --- $ git reset --hard 5436fe~1 --- snip --- or use 'winetricks -q wininet' as workaround without recompiling. 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.
https://bugs.winehq.org/show_bug.cgi?id=38262 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jacek(a)codeweavers.com, | |sebastian(a)fds-team.de -- 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=38262 --- Comment #2 from Levan <levanchelidze(a)gmail.com> --- (In reply to Anastasius Focht from comment #1)
Hello folks,
confirming.
This ought to work some time ago, when I was investigating bug 37798 (Wine 1.7.33)
Looks like a regression.
http://source.winehq.org/git/wine.git/commit/ 5436fef80722fe7896aed5e659c31fdade4ef5b3
That commit can't be cleanly reverted on current head without manual resolution.
Revert to working state:
--- snip --- $ git reset --hard 5436fe~1 --- snip ---
or use 'winetricks -q wininet' as workaround without recompiling.
Regards
The wininet did the job -- 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=38262 razzylaqui(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |razzylaqui(a)gmail.com --- Comment #3 from razzylaqui(a)gmail.com --- I have wininet installed and still have this problem. Originally I had the "Update of DirectX components failed." message, but I copied values from HKEY_CURRENT_USER\Software\Digital Extremes\Warframe\Launcher and fixed that, but now have the same message that Levan's screenshot had. I've ensured wininet was installed through winetricks and set to native, but no change. -- 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=38262 --- Comment #4 from Levan <levanchelidze(a)gmail.com> --- (In reply to razzylaqui from comment #3)
I have wininet installed and still have this problem. Originally I had the "Update of DirectX components failed." message, but I copied values from HKEY_CURRENT_USER\Software\Digital Extremes\Warframe\Launcher and fixed that, but now have the same message that Levan's screenshot had. I've ensured wininet was installed through winetricks and set to native, but no change.
Have you original installed this game on a clean x32 wine prefix ?? -- 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=38262 --- Comment #5 from razzylaqui(a)gmail.com --- (In reply to Levan from comment #4)
(In reply to razzylaqui from comment #3)
I have wininet installed and still have this problem. Originally I had the "Update of DirectX components failed." message, but I copied values from HKEY_CURRENT_USER\Software\Digital Extremes\Warframe\Launcher and fixed that, but now have the same message that Levan's screenshot had. I've ensured wininet was installed through winetricks and set to native, but no change.
Have you original installed this game on a clean x32 wine prefix ??
Yes, actually I was just running it in a 32-bit prefix earlier and it appeared to be working, but I'll need to wait until tomorrow or sometime when I have faster internet to test on to be sure. -- 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=38262 --- Comment #6 from Levan <levanchelidze(a)gmail.com> --- I should add even though I am able to continue after rebooting warframe even with winiest I get stuck on the launcher http://i.imgur.com/B8okrq3.png -- 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=38262 --- Comment #7 from Levan <levanchelidze(a)gmail.com> --- and before the restarting the warframe I could not log in http://i.imgur.com/vSD1QpK.png -- 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=38262 --- Comment #8 from razzylaqui(a)gmail.com --- I don't have a problem like your first screenshot (I have wininet installed as well) but I have the same login problem. It shows that exact same error and won't ever log in. -- 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=38262 --- Comment #9 from Jacek Caban <jacek(a)codeweavers.com> --- I have problems reproducing the real bug. Most of the time, I get the problem like in comment 6. However, I could once observe the original problem and captured logs. From them, I expect this patch to fix the problem: http://source.winehq.org/patches/data/112091 -- 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=38262 Jacek Caban <jacek(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |049a3ba40153253e40177d05e47 | |cd59b0144c86c Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from Jacek Caban <jacek(a)codeweavers.com> --- Assuming fixed, please reopen if not. -- 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=38262 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #11 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.7.49. -- 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=38262 Fem Marak <alfrescopain24(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alfrescopain24(a)gmail.com --- Comment #12 from Fem Marak <alfrescopain24(a)gmail.com> --- How do you make a clean 32 bit install? -- 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=38262 --- Comment #13 from Levan <levanchelidze(a)gmail.com> --- (In reply to Fem Marak from comment #12)
How do you make a clean 32 bit install?
Well it depends on what distro you are using here is the information on winehq website http://wiki.winehq.org/FAQ#head-8d9263369d4c6d93a7cbacf2415377778c679d32 if you are using ubuntu you might find this hateful http://askubuntu.com/questions/177192/how-do-i-create-a-32-bit-wine-prefix -- 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=38262 --- Comment #14 from Fem Marak <alfrescopain24(a)gmail.com> --- Thanks :) -- 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