Hello Paulo, In the PC's I have set up multiseat, I used udev rules to fix the /dev/input/event[0-9]+ names of the keyboards and mice. Have you tried doing this? The error '(EE) PreInit returned NULL for "xxxx"' can be caused by not using the assigned event names or by using symlinks (e.g. /dev/input/by-path/<symlinks>).
--- mike t. ----- Original Message ---- > From: Paulo J. S. Silva <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Sent: Monday, March 24, 2008 21:58:20 > Subject: [Bug 173833] Re: evdev mouse fails on hardy: cannot open input pEvdev > > Mike... I had multiseat working in Gutsy too. But it stopped working in > hardy with the new evdev. > > I have found a solution to mine problem (for a 2 seat configuration at > least): > > 1) I had to add the line > > Option "AutoAddDevices" "no" > > to the first first ServerLayout section. This precludes this server to > grab all devices in advance. Note that this options was not necessary > under feisty, it is only needed in hardy. You may also add > > Option "AutoEnableDevices" "no" > > but it doesn't change anything. > > 2) When the second server kicks in it fails to configure its keyboard > and mouse even though the configuration file looks right to me (the > configuration file is attached). The log shows: > > (**) Option "CoreKeyboard" > (**) Keyboard.1: always reports core events > (EE) Keyboard.1: cannot open input pEvdev > (II) UnloadModule: "evdev" > (EE) PreInit returned NULL for "Keyboard.1" > (**) Option "CorePointer" > (**) Mouse.1: always reports core events > (EE) Mouse.1: cannot open input pEvdev > (II) UnloadModule: "evdev" > (EE) PreInit returned NULL for "Mouse.1" > > So it seems that the first server has some exclusive access to the evdev > device (which shouldn't happen). > > 3) But, as my second server tries to automatically add devices (I > doesn't have the option AutoAddDevices set to no), it can get access to > the second keyboard and mouse. > > 4) The only problem, is that the second keyboard is not being added from > the configuration file, so the system doesn't know the correct options > to handle a ABNT2 (Brazilian) keyboard. I had to edit the > 10-x11-input.fdi file to make hal pass the correct options to the auto- > configuration system. The edited file is attached in the next message > for reference. > > The behavior descried by 2, 3 and 4 above doesn't seem right. I would > expected that the second server should get its keyboard and mouse just > like the first one, including reading the keyboard options from the > xorg.conf file. This looks like a bug in the new evdev to me. Should I > file a bug report? > > > ** Attachment added: "xorg.conf" > http://launchpadlibrarian.net/12839640/xorg.conf > > -- > evdev mouse fails on hardy: cannot open input pEvdev > https://bugs.launchpad.net/bugs/173833 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > -- evdev mouse fails on hardy: cannot open input pEvdev https://bugs.launchpad.net/bugs/173833 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
