Hi I am using a USB device from a PAM module (fingerprint sensor), and we are seeing the USB device stay attached to the wrong head when session mobility is enabled, and the screen is locked, then tried to be unlocked on different sunray heads.
Here is the scenario: Head 1 (H1): - login, remove card Head 2 (H2): - insert card, screen saver runs (note: process is created on H2) - use usb device (works fine), but don't login (bad password for example) - remove card H1: - insert card, screen is locked - usb device works but its the one plugged into H2!!!! So, the problem it seems is that the initial xscreensaver process is created on H2 (and the environment variables in that process cause the USB driver to pick the device attached to H2). When I move the desktop session back to head-1 and try and unlock the screen, The question is why? There seem to be 2 possibilities: 1) The USB driver is stateful and keeps handles to device on H2 2) The process (xscreensaver) has environment variables set when it is created (on H2) that are never refreshed when the desktop is moved back to H1, and the USB driver (which is driven by the stale environment variables) re-attaches to the old head H2. -- This message posted from opensolaris.org
