Keyboard stops working after any mouse click

[maaatt]

Here's a rundown of versions, in case any of it is important:

Wine: 1.3.21
Kernel: 2.6.39 (Gentoo r1)
X.Org X server: 1.10.2
Window manager: musca (0.9.24)

I'm using the default xorg.conf settings.

When I run any program in wine (notepad, for example), the keyboard stops working after I click the mouse. I can type to my heart's content as long as I don't use the mouse.

However, the moment I click, I will not be able to type anything again (this includes dialog boxes).

Furthermore, in some programs (usually games: e.g. starcraft), the keyboard won't work at all, even before I click the mouse.

There are no keyboard-related error messages. The only consistent error message is some variation of this -- usually twice or more:

Code: Select all

fixme:event:wait_for_withdrawn_state window 0x30038/1400007 wait timed out

Any ideas? Thanks!
Matt

[maaatt]

I'm using a laptop, by the way, and plugging in a USB keyboard makes no difference at all.

[maaatt]

Also, adding --without-xinput2 has no effect.

[maaatt]

I just noticed that 1.3.21 is a development version of Wine, so I installed 1.2.3 instead (I uninstalled 1.3.21 and deleted ~/.wine/ first). The problem persists exactly as written.

Nobody's yet replied, and I'm wondering if I'm making some totally annoying newbie mistake. If I am, I apologize, and I'd really appreciate it if someone helped correct me on it (or at least pointed me to the appropriate thread or whatever that I overlooked).

Thanks!
Matt

[jjmckenzie]

On Thu, Jun 16, 2011 at 10:12 AM, maaatt <[email protected]> wrote:

I just noticed that 1.3.21 is a development version of Wine, so I installed 1.2.3 instead (I uninstalled 1.3.21 and deleted ~/.wine/ first). The
problem persists exactly as written.

Actually, we recommend doing the exact opposite of what you did. The
'stable' version is there with a list of known applications that work
with it and for people who want to know exactly what does/does not
work. The development version is a continuing effort to increase
functions and to fix known problems (which may introduce additional
problems.)

The reason that no one has replied is that you need to be detailed in
what you are doing. Here is a list of things to do before posting:
1. Look at other posts to see if someone has encountered your
problem. If so, look to see if there is a solution.
2. Look in the Applications Database to see if your program is
listed. If so, look and see if there is a how-to or workaround.
3. Look in the Bugzilla. There are many problems listed and some
have 'patches' and some have 'replace the xxx.dll with native and set
wine so it will use native'.
4. Post what you have done, so far, to solve the problem. Include
any and all use of winetricks or dll substitutions.

In this case it looks like you have a problem outside of Wine. The
mouse should NEVER stop the keyboard driver from dropping the ability
to accept inputs. I'll review this on the forums this evening PDT
time, if I don't end up working three to four hours over my scheduled
time.

[lahmbi5678]

Hi Matt,

I'm quite sure, you didn't do anything wrong. No answer on this list usually means that noone knows an obvious solution for your problem. Wine 1.2.3 is way too old, there have been many improvements since then.

You might try another window manager like KDE or Gnome or even another linux distribution. Maybe some mainstream linux like opensuse works better with your notebook and wine.

[maaatt]

Thanks!

I just got it working; it turns out the problem was the window manager. Musca is a tiling window manager, but it has a stacking mode. If I switch to stacking mode, the issue goes away completely.

Thanks again!
Matt

P.S. I reinstalled 1.3.21