[Bug 505494] Re: Mouse events fail frequently and unpredictably, requiring kwin restart

[Patrick Dawkins]

** Description changed:

  Binary package hint: kdebase-workspace
  
  There is confusion between a number of related bugs (which didn't show
- up for me in "Do any of the following bugs..."). #478464 seems most
- similar to this but that's dubiously marked as a duplicate of #41301.
+ up for me in "Do any of the following bugs..."). Bug #478464 seems most
+ similar to this but that's dubiously marked as a duplicate of bug
+ #41301.
  
  DESCRIPTION
- It occurs within a few minutes after starting KDE or restarting kwin with "kwin --replace". The mouse cursor continues to move where it should, but clicking either does nothing or affects an unexpected (inactive) window, and gestures such as pushing into the desktop corners also do nothing. It's as if kwin thinks the mouse cursor is frozen somewhere other than where it appears. 
+ It occurs within a few minutes (usually sooner) after starting KDE or restarting kwin with "kwin --replace". The mouse cursor continues to move where it should, but clicking either does nothing or affects an unexpected (inactive) window, and gestures such as pushing into the desktop corners also do nothing. It's as if kwin thinks the mouse cursor is frozen somewhere other than where it appears.
  
  Everything other than mouse events continues to work as expected:
  controlling KDE with keyboard shortcuts shows that applications,
  compositing and desktop effects are all fine.
+ 
+ [Edit: it is NOT as if a phantom window/app is grabbing the mouse
+ events, because as stated above, clicks occasionally still affect a
+ window for a short while, even if it's the wrong window.]
  
  WORKAROUND
  Restart kwin with "kwin --replace".
  
  None of the workarounds mentioned in the discussion for bug #41301 work
  for this, which is why I think it's different.
  
  BACKGROUND
  I'm not running Xinerama or dual screens, I have a USB mouse which works perfectly on my other machine, my Kubuntu 9.10 retains most of its default settings, windows are set to "Click to Focus", and my graphics card is nVidia GeForce 6100 with the nvidia-glx-185 driver.
  
  I run regular apt updates, and first noticed this bug on 8 Jan 2010,
  having run KDE with very few problems for several months. I think the
  automatic updates on 8 Jan were for Firefox and GIMP (upgrades), but
  this bug occurs whether or not Firefox or GIMP are running. I have not
  made any configuration changes recently.
  
  ProblemType: Bug
  Architecture: amd64
  Date: Sun Jan 10 13:44:24 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/kwin
  NonfreeKernelModules: nvidia
  Package: kde-window-manager 4:4.3.2-0ubuntu7.1
  ProcEnviron:
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
-  LANGUAGE=
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
+  LANGUAGE=
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: kdebase-workspace
  Uname: Linux 2.6.31-17-generic x86_64

** Description changed:

  Binary package hint: kdebase-workspace
  
  There is confusion between a number of related bugs (which didn't show
  up for me in "Do any of the following bugs..."). Bug #478464 seems most
  similar to this but that's dubiously marked as a duplicate of bug
  #41301.
  
  DESCRIPTION
  It occurs within a few minutes (usually sooner) after starting KDE or restarting kwin with "kwin --replace". The mouse cursor continues to move where it should, but clicking either does nothing or affects an unexpected (inactive) window, and gestures such as pushing into the desktop corners also do nothing. It's as if kwin thinks the mouse cursor is frozen somewhere other than where it appears.
  
  Everything other than mouse events continues to work as expected:
  controlling KDE with keyboard shortcuts shows that applications,
  compositing and desktop effects are all fine.
  
  [Edit: it is NOT as if a phantom window/app is grabbing the mouse
- events, because as stated above, clicks occasionally still affect a
- window for a short while, even if it's the wrong window.]
+ events, because as stated above, clicks occasionally still affect a real
+ window for a short while, even if it's an inactive one.]
  
  WORKAROUND
  Restart kwin with "kwin --replace".
  
  None of the workarounds mentioned in the discussion for bug #41301 work
  for this, which is why I think it's different.
  
  BACKGROUND
  I'm not running Xinerama or dual screens, I have a USB mouse which works perfectly on my other machine, my Kubuntu 9.10 retains most of its default settings, windows are set to "Click to Focus", and my graphics card is nVidia GeForce 6100 with the nvidia-glx-185 driver.
  
  I run regular apt updates, and first noticed this bug on 8 Jan 2010,
  having run KDE with very few problems for several months. I think the
  automatic updates on 8 Jan were for Firefox and GIMP (upgrades), but
  this bug occurs whether or not Firefox or GIMP are running. I have not
  made any configuration changes recently.
  
  ProblemType: Bug
  Architecture: amd64
  Date: Sun Jan 10 13:44:24 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/kwin
  NonfreeKernelModules: nvidia
  Package: kde-window-manager 4:4.3.2-0ubuntu7.1
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
   LANGUAGE=
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: kdebase-workspace
  Uname: Linux 2.6.31-17-generic x86_64

-- 
Mouse events fail frequently and unpredictably, requiring kwin restart
https://bugs.launchpad.net/bugs/505494
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.