http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #13 from 7WCbywQg3N2H@dyweni.com 2011-09-17 22:34:52 CDT --- (In reply to comment #12)
ZW, does the workaround from http://bugs.winehq.org/show_bug.cgi?id=15485#c100 help you?
No, sorry. That workaround does not work. I can trigger the problem by simply firing up a couple of accounts and point & click between them - never once using Alt+TAB.
I'll also say that once the problem is triggered, X must be reset to make it go away. Simply closing all programs (minus Openbox) is not sufficient in making it go away.
Once the problem is initially triggered and all programs closed, the time from launching EVE until seeing it again varies, but it always gets seen again. Somehow, that time reduces itself as I begin to launch more and more accounts.
This is my latest configuration: * CPU - AMD Phenom II X6 1090T (clocked at 3.6 Ghz) * Linux Kernel 2.6.39-gentoo-r3 * X.Org Server 1.10.4 * X Input Protocol 2.0.2 * Nvidia (Binary) Drivers 275.09.07 * OpenBox - 3.4.11.2 * Wine GIT Commit - 3b40c03a8f0e3dcbb236d59125b115b2501086f8 * EVE Online 7.11.292761
I play multiple accounts simultaneously (usually 6, sometimes 8) (not using any kind of multiboxing / key / mouse broadcasting software - just point/click/type/etc in account 1, move to next account, rinse & repeat).
I've noticed the problem goes away by resetting X (ctrl-alt-backspace) and ONLY running EVE/WINE. As soon as I launch Chrome (the web browser) and surf a bit, the problem comes right back. I've seen other applications trigger the problem, but can't think what they are ATM.
I've even tried running WINE using 'nice -n 20', but that doesn't help here.
I run EVE with this series of commands: * export WINEPREFIX=/home/eve/wine$account * cd /home/eve/Installation * winecmd="wine explorer /desktop=EVE$account,$evesize bin/ExeFile.exe" * nice -n 20 $winecmd
I have found a second workaround (but resource hog) for those times when resetting X is not possible (due to open work, etc): * Run EVE using the same commands as above, but within its own TurboVNC server session with the VirtualGL wrapper. This isolates WINE into its own X environment, but still lets me use my primary video card for all the OpenGL rendering stuff. It's a resource hog because now I have two cores being used for each account.
Thanks, Dyweni