http://bugs.winehq.org/show_bug.cgi?id=20646
Summary: Window jerking under awesome Product: Wine Version: 1.1.17 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: harry@unheit.net
When using the awesome window manager, Wine windows behave strange (see below). I didn't get an answer on the awesome mailing list, but someone sent me a mail in private, stating that he had the same problem with Photoshop.
Here's the mail I sent to the awesome mailing list with the description of the problem:
Hi,
I use Lotus Notes in WINE and the windows behave quite strange. Now this might be a WINE problem, but I wanted to ask here if someone has experienced smth. similar with other applications or if someone has ideas about what the reason might be.
At first the window is positioned correctly. But on focus change (either focus-in or focus-out) or if any control in the window is clicked, the window moves 2 pixels to the right and to the bottom. From now on, on each focus change the window jerks once very quickly: it moves to its original position and then back to the 2 pixel off position. Sometimes, but not always, this also happens when clicking controls.
Or it moves further right and down in 2 pixel steps each time the focus is changed or a control clicked.
Whether it jerks or keeps moving is quite erratic.
If the window is set to floating it still does the initial move on the first click/focus change after the window has been moved with the mouse, but no further jerking/moving occurs on subsequent clicks/focus changes.
The window can be moved back to the original position by switching tags or between layouts.
Cheers, harry
http://bugs.winehq.org/show_bug.cgi?id=20646
Alexander Scott-Johns alexander.scott.johns+winebug@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alexander.scott.johns+wineb | |ug@googlemail.com
--- Comment #1 from Alexander Scott-Johns alexander.scott.johns+winebug@googlemail.com 2009-11-10 16:24:08 --- (In reply to comment #0)
When using the awesome window manager, Wine windows behave strange (see below). I didn't get an answer on the awesome mailing list, but someone sent me a mail in private, stating that he had the same problem with Photoshop.
This is probably a bug in awesome (Wine demands a lot from window managers). Try unsetting the "Allow the window manager to control the windows" option in winecfg.
http://bugs.winehq.org/show_bug.cgi?id=20646
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #2 from Vitaliy Margolen vitaliy@kievinfo.com 2009-11-10 20:33:47 --- This reminds me of the same bug on Mac OS/X. Which is/was it's window manager bug. So as this one.
http://bugs.winehq.org/show_bug.cgi?id=20646
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Vitaliy Margolen vitaliy@kievinfo.com 2009-11-10 20:34:30 --- Closing - not a Wine bug.
http://bugs.winehq.org/show_bug.cgi?id=20646
--- Comment #4 from harry harry@unheit.net 2009-11-12 06:47:08 --- Any information about what the problem was exactly on MacOS X? That would help the awesome developers.
http://bugs.winehq.org/show_bug.cgi?id=20646
--- Comment #5 from Vitaliy Margolen vitaliy@kievinfo.com 2009-11-12 08:30:13 ---
Any information about what the problem was exactly on MacOS X?
All Wine windows were moving up & left one pixel each time you click a button.
http://bugs.winehq.org/show_bug.cgi?id=20646
--- Comment #6 from Austin English austinenglish@gmail.com 2009-11-12 11:40:03 --- FWIW, there are a ton of testcases under dlls/user32/tests. Ideally, they should all work under a proper WM.
http://bugs.winehq.org/show_bug.cgi?id=20646
--- Comment #7 from Dmitry Timoshkov dmitry@codeweavers.com 2009-11-16 12:20:34 --- Probably a similar WM problem as reported in the bug 12431.