Xnest: ghost mouse

Bug #84662 reported by Laurent Bigonville
34
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNOME Screensaver
Fix Released
Medium
X.Org X server
Invalid
Undecided
Unassigned
gnome-screensaver (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Hi,

In feisty, when using Xnets, the mouse pointer is not always updated. This causes the clicks to occurs in an other place that the pointer is.

For example try this:

Xnest -ac :20&
DISPLAY=:20 xeyes&

The eyes don't follow the pointer

Revision history for this message
William Lachance (wrlach) wrote :

Speculated that this might have something to do with the fact that I was using the proprietary nvidia driver. Nope: switching back to the nv driver had no effect.

Revision history for this message
William Lachance (wrlach) wrote :

Did some tracing and I'm pretty sure this is an upstream problem.
Those interested can follow the exciting saga here:

https://bugs.freedesktop.org/show_bug.cgi?id=10096

Changed in xorg-server:
status: Unknown → Confirmed
Revision history for this message
William Lachance (wrlach) wrote :

Beh, after a whole bunch of tracing I determined there was no problem in xorg. The problem is actually in gnome-screensaver. Filed another bug, created a (tentative) patch. See here:

http://bugzilla.gnome.org/show_bug.cgi?id=412486

Revision history for this message
William Lachance (wrlach) wrote :

Changing product.

Changed in xorg-server:
status: Unknown → Unconfirmed
Revision history for this message
Jonh Wendell (wendell) wrote :

William,
Was the problem solved with your patch? Have you tested it?

Revision history for this message
Jonh Wendell (wendell) wrote :

I have tried this patch and it works fine. Xnest is working as expected.
Thanks, William.

Just for learning debian package process, i've made a new ubuntu version of this package, i'll attach a debdiff.

Changed in xorg-server:
status: Unconfirmed → Rejected
Changed in gnome-screensaver:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Changed in gnome-screensaver:
status: Unknown → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for the patch Jonh, I've uploaded the fixed version:

 gnome-screensaver (2.17.8-0ubuntu2) feisty; urgency=low
 .
   * debian/patches/02_ghost_mouse.patch:
     - Make gnome-screensaver not watch for mouse motion events from windows
       which haven't registered for such events (LP: #84662)
       Thanks to William Lachance for the patch

Changed in gnome-screensaver:
status: Confirmed → Fix Released
Revision history for this message
Erkki Seppälä (flux-inside) wrote :

I am seeing the same issue (Xnested xeyes appears to update only when the pointer crosses the Xnest's window edges) with Ubuntu 8.10. However, killing gnome-screensaver (2.24.0-0ubuntu2) didn't remove the problem, which I imagined should have helped, if it is to blame. Perhaps it should've been terminated in a way other than plain kill?

I am running the NVidia proprietary drivers, but as the bug is cunningly similar to this one which had didn't involve NVidia, I'm thinking that's not the case here either. I also verified the bug from another Ubuntu 8.10 user. (unknown setup)

I tried running xev -id $winid_of_Xnest, and received no output when moving the pointer across the Xnest window.

Could there be another process interested in my pointer movements? I'm running the following X clients: applet.py audacious bluetooth-applet evolution-alarm-notify evolution-exchange-storage firefox gnome-netstatus-applet gnome-panel gnome-power-manager gnome-settings-daemon mixer_applet2 mrxvt nautilus nm-applet notification-daemon rep rxvt seahorse-agent tracker-applet trashapplet update-notifier x-session-manager xemacs xterm.

Btw, the actual issue I originally have is not getting the mouse pointer move in Warsow :-), but bugs on that were marked to be duplicate of this.

Changed in gnome-screensaver:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.