mailinglists at who-t.net
Tue Mar 20 18:09:53 PDT 2007
On 21/03/2007, at 09:23 , Magnus Vigerlöf wrote:
> Correct me if I'm wrong, but shouldn't the call to xf86DeleteInput
> be regarded
> as a bug in the evdev-driver? As far as I can see, it's only evdev
> that makes
> this call in the preInit-call. (Ok, calcomp does too, but it
> returns NULL in
> that case.)
> It wouldn't solve your problem, but your server wouldn't crash at
I'd rather solve the problem than quickfixing it to stop crashes. I
don't want to change the evdev driver yet, I only started looking at
it yesterday and my knowledge of its internals is fairly limited.
Unless I get some more of the big picture how it works, I'd rather
not touch it.
> What I can see, there should be something written to the log-file
> includes the errno-string (X_INFO only, but maybe it got into the
> log) that
> could give you a hint.
yeah, forgot to include the msg. "Device or resource busy". which
doesn't make much sense, as the same code in master doesn't seem to
have the problem.
Multi-Pointer X Server
More information about the xorg