After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 347092 - Screensaver activates when using joystick
Screensaver activates when using joystick
Status: RESOLVED DUPLICATE of bug 444927
Product: gnome-screensaver
Classification: Deprecated
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-10 13:39 UTC by Mathieu Comandon
Modified: 2009-08-21 04:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Mathieu Comandon 2006-07-10 13:39:39 UTC
Please describe the problem:
Whenever I play games using only the joystick (/dev/input/js0) , the screensaver activates, and i have to hit a keyboard key or mouse to stop it. 


Steps to reproduce:
1. Be sure the screensaver is active
2. Play a game using only the joystick (xmame or cedega for me)
3. After some time the screensaver activates


Actual results:
The screensaver interrupts the gaming

Expected results:
Consider joystick input the same as keyboard and mouse so the screensaver doesn't appear.

Does this happen every time?
yes

Other information:
no
Comment 1 Sam Morris 2006-11-18 13:07:41 UTC
I guess this is because X11 knows nothing of joysticks; games access them directly by opening /dev/js0 etc.
Comment 2 Eetu Huisman 2007-12-04 20:59:17 UTC
Is there any hope that this issue could be ever solved?
Comment 3 Alan Swanson 2008-12-19 23:16:11 UTC
If the games are using SDL then the IDLETIME solution with gnome-screensaver 2.25.2 referenced in bug 335149 should apply. Otherwise if not using SDL the games needs to call the XResetScreensaver function for same solution.
Comment 4 William Jon McCann 2009-08-21 04:23:14 UTC

*** This bug has been marked as a duplicate of bug 444927 ***