http://bugs.winehq.org/show_bug.cgi?id=12103
--- Comment #3 from Austin English austinenglish@gmail.com 2008-03-19 03:44:28 --- (In reply to comment #2)
Thank you for the quick reply!
What Ctrl+C trick?
In the "Get Newsleecher Running in Ubuntu/Linux" thread on NewsLeecher forums (http://www.newsleecher.com/forum/viewtopic.php?t=13822), there is a post by Sasquatch which reads:
"If you use a terminal to run NL, you can use CTRL+C a few times to speed up the startup. Don't press it too often, sometimes it starts after 3 hits, sometimes it takes up to 7-8 hits."
Does: $ rm -rf ~/.wine $ wine newsleecher_setup.exe $ wine newsleecher.exe
Fix the problem?
Yeah, that would probably do it. But, wouldn't that be like throwing out the baby with the bath water?
Somewhat, but it allows to see if misconfiguration is the problem, or if it is a wine bug. You could do: $ mv ~/.wine ~/.wine.bak $ wine newsleecher_setup.exe $ wine newsleecher.exe
To keep it safe
I had this happen once before with NL 3.8 final release. But, at that time, I had the opportunity to upgrade to a beta release, NL 3.9 Beta 9, which solved the problem.
This is just a theory, but it seems like a window manager might be loading the last "screen position" (upper left x,y coordinate and the windows width and height) when re-initializing NL's main display. Perhaps, when I was pressing Ctrl+C, it caused the main display to load before those values could be properly read into the window manager. So, the window popped up with both width and height values equal to zero. Then, when I closed the program, it stored the zero values back to disk. And it is now trying to load them every time.
I don't know if any of that is true. But, it is a theory.
Using Ctrl+C will have very strange effects, since you are stopping the currently running job. Let the program run as it intends, then file bugs based on that behavior.