We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 644 - SDL unable to detect pointer with Xorg option "CorePointer"
Summary: SDL unable to detect pointer with Xorg option "CorePointer"
Status: RESOLVED FIXED
Alias: None
Product: SDL
Classification: Unclassified
Component: events (show other bugs)
Version: HG 2.0
Hardware: x86 Linux
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-25 13:03 UTC by Donny Viszneki
Modified: 2009-01-04 23:33 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Donny Viszneki 2008-11-25 13:03:12 UTC
Running Xorg on Debian Etch with SDL trunk revision 4123

If pointer device has the CorePointer option explicitly enabled in Xorg configuration, SDL test "testmmousetablet" is unable to detect the device.

My mouse currently works fine under SDL 1.2.7 and 1.2.8 releases, but when I enable "CorePointer" the multi-mouse code in SDL doesn't find my mouse, it would seem, when it asks Xorg to list all pointer devices. When the only pointer device is explicitly given the "CorePointer" option, here is the output of "testmmousetablet":

====

donny@teamspace:~/SDL$ LD_LIBRARY_PATH=/opt/local/lib ~/SDL/test/testmmousetablet
Initing...
0 pointing devices found

====

When I enable four pointer devices in my Xorg configuration, if any of them has the CorePointer attribute, it becomes invisible to the "testmmousetablet" test SDL trunk revision 4123. In this situation, moving the pointer around the test window works fine when using any of the other three pointers, but no events are registered when using the pointer with the "CorePointer" option explicitly enabled.

Here is what the xorg.conf man page from Debian Etch has to say about this option:

====

Option "CorePointer"

When this is set, the input device  is  installed  as  the  core (primary)  pointer  device.   There  must  be  exactly  one core pointer.  If this option is not set here, or in the ServerLayout section,  or  from  the  -pointer  command line option, then the first input device that is capable  of  being  used  as  a  core pointer  will  be  selected as the core pointer.  This option is implicitly set when the obsolete Pointer section is used.

====

The man page would suggest that in my current Xorg configuration -- four pointer devices specified, none with "CorePointer" option explicitly enabled -- that one of my pointers would be implicitly given the "CorePointer" option. For this reason I suspect the bug may be in Xorg, but I don't know a great deal about it.

FWIW, three of my pointer devices are notional divisions of my WACOM graphire 4 USB tablet, and the other is a Microsoft USB intellimouse. I believe that an explicit CorePointer option is present in almost every automatically generated X configuration file, so this may be a very common problem. Can anyone else reproduce this issue?
Comment 1 Donny Viszneki 2009-01-02 12:19:21 UTC
I believe this bug has been solved by SVN rev 4294