running gnome-screensaver prevents War§sow from accessing mouse

[hangy]

Problem:
After an upgrade of Ubuntu from Edgy Eft to Feisty Fawn, mouse doesn't work in War§ow any more.

Steps to reproduce:
1. Upgrade to Ubuntu Feisty Fawn.
2. cd /tmp/ ; wget http://ftp.club-internet.fr/pub/games/nofrag/warsow/warsow_0.21_linux.tar.gz ; tar xfz warsow_0.21_linux.tar.gz ; cd warsow ; ./warsow
3. See that you cannot move the mouse at all. However, mouse-wheel and -buttons may work.

Notes:
- My mouse does work in a downloaded version of OpenArena. Despite that, I guess it has to do with Ubuntu, because downloading the latest development source of War§ow and compiling it doesn't help at all.
- in_dgamouse 0/1 does not change anything.
- I successfully built a debian package of War§ow 0.21 with the sources from svn.debian.org and installed the packages, but that didn't help either.

uname -a:
Linux sodium 2.6.20-8-generic #2 SMP Tue Feb 13 01:14:41 UTC 2007 x86_64 GNU/Linux

[hangy (hangy)]

A similar problem was described in the War§ow forums today[1], however I don't think that player uses Ubuntu, because of the gnome version reported. After all, the only visible similarity at this moment is that he uses some up-to-date programs and the same mouse as I do.

[1] http://www.warsow.net/forum/viewtopic.php?id=12563

[detto (detto-o)]

I have the exact same problem. Am using Frugalware 0.6rc1 here. (http://frugalware.org) They have at this very moment GNOME 2.17.91. On same machine warsow and mouse just work in all other WM's and/or DE's. Just NOT in GNOME. In previous version(s) it worked (2.16.x)
Also got the same mouse as hangy: "MX510" connected to USB port.
Self-compiled metacity without composite feature didn't work either. I don't really know where the problem is or to search for.

ADD: Today starting warsow in GNOME 2.17.91 the mouse worked! About ~30 seconds, then suddenly the cursor stopped to respond and same story as before.

[hangy (hangy)]

> ADD: Today starting warsow in GNOME 2.17.91 the mouse worked! About ~30 seconds, then suddenly the cursor stopped to respond and same story as before.

Weird stuff ... I changed my X.org conf to evdev started War§ow and my mouse worked ... well - when I closed it and started it again after some minutes, mouse was gone again. :( Looks like GNOME's the candidate for this ...

[hangy (hangy)]

I can confirm detto's statement that this problem is related to gnome in some way.
Simply using xfce4 instead of gnome makes my mouse work in War§ow.

Because of that, I'm re-assigning this to the ubuntu-gnome team.

[Sebastien Bacher (seb128)]

Thank you for your bug. If you log to a failsafe session, truc wasom does it work? Then can you run gnome-settings-daemon and not if that breaks the mouse?

[hangy (hangy)]

Hello Sebastien,

Firstly, I'd like to say sorry for re-assigning the bug all the time, it was just what I thought might be the best candidate to fix it.

As the GNOME failsafe session starts gnome-session-deamon, I started a Xterm failsafe session. Then, playing War§ow for a minute or so, no problem with the mouse occured. After starting gnome-settings-daemon, I could play for about 30 seconds (like described above) and then the mouse stopped moving. (Mousewheel still works.)
Looks like you know the problem/found the right candidate.

Best regards,
-hangy

[Christoph Rauch (christoph-rauch)]

I suspected this had something to do with the fact that beagle uses all my CPU if I refrain from mouse moving for too long. If I move my mouse beagle stops instantaneous. Somehow beagle must get notified of mouse movements. I suspected that control of the mouse is not given off to newly launched applications.

So I killed several processes until I got the culprit.

It's gnome-screensaver. If I kill it mouse works again in Warsow. If I start it again, mouse isn't working anymore. Pretty obvious I think. :)

In retrospect it's obvious that gnome-screensaver should stop beagle from beagling as it has to look for mouse movement anyway. So I'm pretty sure this is a bug. :)

[Christoph Rauch (christoph-rauch)]

I correct me. After looking at src/gs-watcher-x11.c I think beagle looks for the mouse and key-events itself. Suspected some d-bus trickery.

So is this a problem in gnome-screensaver after all? Or is it a problem in x11?

[Christoph Rauch (christoph-rauch)]

setting it to confirmed.

[Sebastien Bacher (seb128)]

duplicate from bug #84662, a fixed version has been uploaded now