http://bugs.winehq.org/show_bug.cgi?id=17152
Summary: Blizzard Updater complains about javascript being turned off Product: Wine Version: 1.1.13 Platform: PC-x86-64 URL: http://www.worldofwar OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shdocvw AssignedTo: wine-bugs@winehq.org ReportedBy: adys.wh+winehqdotorg@gmail.com
Created an attachment (id=19021) --> (http://bugs.winehq.org/attachment.cgi?id=19021) Screenshot of behaviour.
When patching World of Warcraft, the Blizzard Updater (at least the old one) complains about Javascript being turned off, instead of showing the patch.html file embedded in the patcher. See screenshot. No interesting terminal output, however testing the patcher is a long process so if a full debug log is needed, just say what to run.
http://bugs.winehq.org/show_bug.cgi?id=17152
Jacek Caban jacek@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jacek@codeweavers.com
--- Comment #1 from Jacek Caban jacek@codeweavers.com 2009-01-27 07:46:35 --- Please attach mshtml debug channel output.
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #2 from Adys adys.wh+winehqdotorg@gmail.com 2009-01-27 08:17:06 --- Created an attachment (id=19024) --> (http://bugs.winehq.org/attachment.cgi?id=19024) WINEDEBUG=+mshtml log
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #3 from Adys adys.wh+winehqdotorg@gmail.com 2009-01-27 08:18:33 --- Small note: after the first 1mb of log or so, the patcher is not running anymore, the launcher is.
http://bugs.winehq.org/show_bug.cgi?id=17152
Cheos cheos@chez-cheos.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cheos@chez-cheos.org
--- Comment #4 from Cheos cheos@chez-cheos.org 2009-02-09 09:42:43 --- I have this behavior too. However, it used to work a while ago (probably a few months to more than a year) but I unfortunately can't tell whether it stopped working after a wine upgrade or after an update of the game.. I didn't bother too much because you don't patch the game very often and you can read release notes from the official website. It's more a minor cosmetic issue imo.
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #5 from Austin English austinenglish@gmail.com 2009-02-09 10:23:28 --- (In reply to comment #4)
I have this behavior too. However, it used to work a while ago (probably a few months to more than a year) but I unfortunately can't tell whether it stopped working after a wine upgrade or after an update of the game.. I didn't bother too much because you don't patch the game very often and you can read release notes from the official website. It's more a minor cosmetic issue imo.
Probably because we started to implement jscript.dll.
Try: $ wget kegel.com/wine/winetricks $ sh winetricks wsh56js
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #6 from Adys adys.wh+winehqdotorg@gmail.com 2009-02-09 12:47:39 --- (In reply to comment #5)
(In reply to comment #4)
I have this behavior too. However, it used to work a while ago (probably a few months to more than a year) but I unfortunately can't tell whether it stopped working after a wine upgrade or after an update of the game.. I didn't bother too much because you don't patch the game very often and you can read release notes from the official website. It's more a minor cosmetic issue imo.
Probably because we started to implement jscript.dll.
Try: $ wget kegel.com/wine/winetricks $ sh winetricks wsh56js
I still get "Please enable Javascript" and no patchnote, however if I change the language, the text appears fine. Only output is fixme:mshtml:DispatchEx_GetNameSpaceParent (0x139e44a0)->(0x33e7d8) fixme:mshtml:DispatchEx_GetNameSpaceParent (0x139e44a0)->(0x33e538)
http://bugs.winehq.org/show_bug.cgi?id=17152
szandor szandor420@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |szandor420@yahoo.com
--- Comment #7 from szandor szandor420@yahoo.com 2009-02-10 11:52:50 --- kill these two processes:
/home/loki/.wine/drive_c/Program Files/World of Warcraft/Wow.exe loki 1735 1664 19 11:53 ? 00:00:32 WoW-3.0.8.9506-to-3.0.9.9551-enUS-downloader.exe loki 1664 1 6 11:52 ? 00:00:13 /home/loki/.wine/drive_c/Program Files/World of Warcraft/Wow.exe
just make sure the only wow process running is:
loki 1753 1 1 11:53 ? 00:00:03 C:\windows\temp\Blizzard Installer Bootstrap - 00004482\Installer.exe --path=C:\Program Files\World of Warcraft\WoW-3.0.8.9506-to-3.0.9.9551-enUS-patch.exe
the patch will continue after that without problems and relaunch wow.
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #8 from szandor szandor420@yahoo.com 2009-02-10 11:55:45 --- (In reply to comment #7)
kill these two processes:
/home/loki/.wine/drive_c/Program Files/World of Warcraft/Wow.exe loki 1735 1664 19 11:53 ? 00:00:32 WoW-3.0.8.9506-to-3.0.9.9551-enUS-downloader.exe loki 1664 1 6 11:52 ? 00:00:13 /home/loki/.wine/drive_c/Program Files/World of Warcraft/Wow.exe
just make sure the only wow process running is:
loki 1753 1 1 11:53 ? 00:00:03 C:\windows\temp\Blizzard Installer Bootstrap - 00004482\Installer.exe --path=C:\Program Files\World of Warcraft\WoW-3.0.8.9506-to-3.0.9.9551-enUS-patch.exe
the patch will continue after that without problems and relaunch wow.
sorry kill these 2 by their process id, i.e. 1735 and 1664:
loki 1735 1664 19 11:53 ? 00:00:32 WoW-3.0.8.9506-to-3.0.9.9551-enUS-downloader.exe loki 1664 1 7 11:52 ? 00:00:12 /home/loki/.wine/drive_c/Program Files/World of Warcraft/Wow.exe
and make sure only 1753 is running. basically, kill the process for any files still open other than the patch.exe.
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #9 from Adys adys.wh+winehqdotorg@gmail.com 2009-02-11 01:43:19 --- (In reply to comment #7)
kill these two processes: ... the patch will continue after that without problems and relaunch wow.
I believe you're mistaken with another bug. This one is unrelated to patching, just to the patchnote itself.
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #10 from Cheos cheos@chez-cheos.org 2009-02-11 10:59:38 ---
Probably because we started to implement jscript.dll.
Try: $ wget kegel.com/wine/winetricks $ sh winetricks wsh56js
I've just patched the game as a new update of the game has been released today (3.0.9). The issue isn't relevant anymore as the updater has been completely revamped (I believe it was shipped with previous update) and this new tool displays release notes correctly for me. Issue solved here.
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #11 from Adys adys.wh+winehqdotorg@gmail.com 2009-02-11 12:11:58 --- (In reply to comment #10)
Probably because we started to implement jscript.dll.
Try: $ wget kegel.com/wine/winetricks $ sh winetricks wsh56js
I've just patched the game as a new update of the game has been released today (3.0.9). The issue isn't relevant anymore as the updater has been completely revamped (I believe it was shipped with previous update) and this new tool displays release notes correctly for me. Issue solved here.
This is irrelevant, the old updater is still available through old patches on older installs.
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #12 from Cheos cheos@chez-cheos.org 2009-02-11 12:20:39 --- (In reply to comment #11)
(In reply to comment #10)
Probably because we started to implement jscript.dll.
Try: $ wget kegel.com/wine/winetricks $ sh winetricks wsh56js
I've just patched the game as a new update of the game has been released today (3.0.9). The issue isn't relevant anymore as the updater has been completely revamped (I believe it was shipped with previous update) and this new tool displays release notes correctly for me. Issue solved here.
This is irrelevant, the old updater is still available through old patches on older installs.
Well I see your point, although I'm not sure how useful old release notes are since you have to do all updates until you have the latest version before you can play the game. Anyway I can confirm I don't have this issue anymore starting from version 3.0.9 :)
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #13 from Adys adys.wh+winehqdotorg@gmail.com 2009-02-11 13:08:08 --- (In reply to comment #12)
Well I see your point, although I'm not sure how useful old release notes are since you have to do all updates until you have the latest version before you can play the game. Anyway I can confirm I don't have this issue anymore starting from version 3.0.9 :)
That doesn't matter. The bug is still there, it may affect other applications. As long as it can be tested, there is no reason to close it.
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #14 from Cheos cheos@chez-cheos.org 2009-02-11 17:08:57 ---
Well I see your point, although I'm not sure how useful old release notes are since you have to do all updates until you have the latest version before you can play the game. Anyway I can confirm I don't have this issue anymore starting from version 3.0.9 :)
That doesn't matter. The bug is still there, it may affect other applications. As long as it can be tested, there is no reason to close it.
I agree.
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #15 from Drew cavedeamon@gmail.com 2009-04-30 22:42:47 --- Created an attachment (id=20849) --> (http://bugs.winehq.org/attachment.cgi?id=20849) Same error in the 3.0.9 installer
http://bugs.winehq.org/show_bug.cgi?id=17152
Roman Skrzypiński romano473@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #16 from Roman Skrzypiński romano473@gmail.com 2009-05-30 07:11:53 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=17152
wanderer@fastmail.fm changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wanderer@fastmail.fm
--- Comment #17 from wanderer@fastmail.fm 2010-01-01 08:53:46 --- This still happens with the Git version of Wine (version wine-1.1.35-364-g9dc584d) as of at least 2009-12-31. Any progress in this area, or is it stalled until further notice?
In the unlikely event that logs or the like would be useful at this point, I can provide them more or less on request, provided that I understand how to generate them (which in most cases I think I do).
http://bugs.winehq.org/show_bug.cgi?id=17152
Devin Cofer ranguvar@archlinux.us changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ranguvar@archlinux.us
--- Comment #18 from Devin Cofer ranguvar@archlinux.us 2010-06-16 23:34:07 --- Confirmed in Wine 1.2-rc3.
I think the most interesting bit is that changing the language (and then changing back if you like) fixes the issue.
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #19 from Jerome Leclanche adys.wh@gmail.com 2010-09-28 03:35:35 CDT --- Can someone retest in wine-1.3.3?
http://bugs.winehq.org/show_bug.cgi?id=17152
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL|http://www.worldofwar |
http://bugs.winehq.org/show_bug.cgi?id=17152
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Installer
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #20 from Jerome Leclanche adys.wh@gmail.com 2011-03-31 01:19:09 CDT --- Had to go back as far as WoW-2.0.0.6080-to-2.0.3.6299-enGB-patch.exe to get it to repro, but it's still an issue in wine-1.3.16 with the new gecko version.
http://bugs.winehq.org/show_bug.cgi?id=17152
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |minor
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #21 from Austin English austinenglish@gmail.com 2013-11-13 16:50:29 CST --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.6 or newer) wine? If so, please attach the terminal output in 1.7.6 (see http://wiki.winehq.org/FAQ#get_log).
http://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #22 from Jerome Leclanche adys.wh@gmail.com 2013-11-15 06:41:51 CST --- (In reply to comment #21)
Don't close. I still have old executables. It's really hard to test but possible. I'll try to do it when I get time.
https://bugs.winehq.org/show_bug.cgi?id=17152
--- Comment #23 from Austin English austinenglish@gmail.com --- (In reply to Jerome Leclanche from comment #22)
(In reply to comment #21)
Don't close. I still have old executables. It's really hard to test but possible. I'll try to do it when I get time.
Ping.
https://bugs.winehq.org/show_bug.cgi?id=17152
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #24 from Jerome Leclanche adys.wh@gmail.com --- (In reply to Austin English from comment #23) Seems to work as far as I can test it...
https://bugs.winehq.org/show_bug.cgi?id=17152
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #25 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.32.
https://bugs.winehq.org/show_bug.cgi?id=17152
Saulius K. saulius2@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |saulius2@gmail.com