https://bugs.winehq.org/show_bug.cgi?id=37880
Bug ID: 37880 Summary: Don't run Watchtower Library 2014 on ubuntu 14.04LTS wine 1.6.2 Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: ansaf1914@gmail.com Distribution: ---
Created attachment 50449 --> https://bugs.winehq.org/attachment.cgi?id=50449 Don't run Watchtower Library 2014 on ubuntu 14.04LTS wine 1.6.2
Don't run Watchtower Library 2014 on ubuntu 14.04LTS wine 1.6.2
https://bugs.winehq.org/show_bug.cgi?id=37880
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu Summary|Don't run Watchtower |Watchtower Library 2014 |Library 2014 on ubuntu |crashes |14.04LTS wine 1.6.2 |
--- Comment #1 from Austin English austinenglish@gmail.com --- Please retest in 1.7.34.
https://bugs.winehq.org/show_bug.cgi?id=37880
business.kid@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |business.kid@gmail.com
--- Comment #2 from business.kid@gmail.com --- I can confirm this bug. I have Slackware-current as of 09/14, wine-git 20150120 and kernel 3.14.5. It installs fine but crashes out on startup, leaving a lot of stuff hanging in the air..
This thread on the forum: https://forum.winehq.org/viewtopic.php?f=8&t=24050 WINEDEBUG=+all here: https://onedrive.live.com/?cid=9936144096FF2C07&id=9936144096FF2C07!208
I have the 2013 install and the 2014 wtlibrary.exe is the culprit. I swapped the files around 2013 crashed out similarly with the 2014 wtlibrary exe (the main exe) 2014 works after a fashion with the 2013 wtlibrary.exe but doesn't show 2014 :-(.
The only output I captured with any meaningful info is from winedbg, which I'm not at all familiar with, but it's attached. Thius is a quick sit-down. The "Show details" dialogue on a crash is blank "Waiting . . "
https://bugs.winehq.org/show_bug.cgi?id=37880
--- Comment #3 from business.kid@gmail.com --- Created attachment 50544 --> https://bugs.winehq.org/attachment.cgi?id=50544 winedebug output from WT Library 2014
It's a quick and nearly noiseless exit. Further details require a little advice. I will check if I can bend copyright to sort this.
https://bugs.winehq.org/show_bug.cgi?id=37880
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |focht@gmx.net Resolution|--- |FIXED Summary|Watchtower Library 2014 |Watchtower Library 2010 |crashes |crashes on startup
--- Comment #4 from Anastasius Focht focht@gmx.net --- Hello folks,
I can't reproduce any of the issues, neither with Watchtower Library 2010, 2013, 2014.
OP's crash is with Watchtower Library 2010 and using an outdated Wine 1.6.2
--- snip --- 00000033 (D) C:\Program Files\Watchtower\Watchtower Library 2010\E\WTLibrary.exe 00000034 0 <== --- snip ---
Each Watchtower Library version (ISO, installer) has it's own directory to allow multiple Watchtower versions to be installed in same WINEPREFIX.
To work around garbled fonts, use 'winetricks -q corefonts'. No other 'winetricks' recipes are needed.
Additionally have a look at Wine appdb: https://appdb.winehq.org/objectManager.php?sClass=application&iId=1485 (it's regularly rated gold/platinum).
Comment #2 and #3 are likely the result of broken WINEPREFIX/WT installer packages and/or invalid steps.
--- quote --- I swapped the files around --- quote ---
This renders any information/deduction automatically invalid.
--- quote --- winedebug output from WT Library 2014 --- quote ---
Don't use 'winedbg' if you don't know how to debug.
Resolving 'fixed' since OP's problems with Watchtower 2010 could not be reproduced with Wine 1.7.x which is also supported by many test results in Wine Appdb. Watchtower is one of the apps that get regular test reports and have quite a large community compared to other appdb entries.
$ wine --version wine-1.7.34-159-g7b45103
Regards
https://bugs.winehq.org/show_bug.cgi?id=37880
--- Comment #5 from business.kid@gmail.com --- As the author of comments 2, 3 I feel you are being hasty.
I have had this installed in linux since WTL 2007, and every year the wtlibrary.exe is substantially rebuilt. This is the second one not to work straight out of the box. I have it installed beside 2013 library. 2013 works fine - from the shortcut or from the directory. 2014 pukes and falls over.
I am not in the habit of reaching for bug reports unless something cannot be made work. This is the case in this instance. I have a vanilla wine-git (wine --version reports wine-1.7.34-90-g5fa7402) with corefonts installed. Running the shortcut command only gives this env WINEPREFIX="/home/dec/.wine" wine C:\Program\ Files\Watchtower\Watchtower\ Library\ 2014\E\WTLibrary.exe fixme:module:load_library unsupported flag(s) used (flags: 0x00000800) fixme:advapi:RegisterTraceGuidsW (0xac8c72, (nil), {f7b697a3-4db5-4d3b-be71-c4d284e6592f}, 7, 0xe61fec, (null), (null), 0xecfd28): stub wine: Unhandled exception 0x40000015 in thread 9 at address 0x30023:0x005fb454 (thread 0009), starting debugger...
Is that fixed?
https://bugs.winehq.org/show_bug.cgi?id=37880
--- Comment #6 from Anastasius Focht focht@gmx.net --- Hello business.kid,
how about mentioning the not-that-unimportant fact that you changed the default Windows version of the WINEPREFIX to something else?
When reporting issues you *must* state all deviations from standard settings otherwise you lengthen or even waste the time of people investigating.
Your problem has nothing to do with OP's bug report. You jumped the ship, "I can confirm this bug" = "me too" just because there is a crash. A crash can be the result of gazillion things gone wrong. Bug reports should target specific situations (API insufficiencies, incorrect implementation, undocumented behaviour) and are not meant to collect all kinds of crashes with the app -> "one problem per bug".
Back to your problem ... The application is specifically aware of Windows Vista and Windows 7. It tries to use more advanced APIs and even makes distinctions between Vista and Windows 7.
It works perfectly with Wine's default 'Windows XP'.
Nowhere in WineHQ Appdb entries for Watchtower Library is a statement "you must change Windows version to Windows Vista/Windows 7 for better experience". In many cases the opposite would be true: due to Wine insufficiencies in various areas the apps will simply not run and/or exhibit strange behaviour.
The issues with missing/insufficient Vista/Win7 API are already partially covered by existing bugs.
Regards
https://bugs.winehq.org/show_bug.cgi?id=37880
--- Comment #7 from business.kid@gmail.com --- Ah! Windows XP!
I was on vista - How/why I don't know. Thank you kindly. Very grateful for that.
Extremely grateful. G'bye.
https://bugs.winehq.org/show_bug.cgi?id=37880
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.36.
-
wine-bugs＠winehq.org