Bug 8834

Summary:	X makes lack of a pointing device a fatal error is broken in N ways.
Product:	xorg	Reporter:	Jim Gettys <jg>
Component:	Server/Input/Core	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	high	CC:	daniel, dberkholz, jg
Version:	unspecified
Hardware:	All
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:
Bug Blocks:	6666

Description Jim Gettys 2006-10-30 11:47:43 UTC

1) this is clearly wrong, as Xkb can allow you to move the core pointer in other
ways without a mouse.

2) with hot-plug input devices, it is perfectly reasonable for the number to be
zero at various times (particulary on startup).

3) The damn log file ends up filling a log based file systems with junk files,
as the X server cycles again, and again, and again.

There is a meta question as to whether a display manager should keep trying or not.

One might argue this could be deferred to 7.3, but please make sure it gets
moved to 7.3's release tracker bug.

Comment 1 Daniel Stone 2006-10-30 13:30:25 UTC

this has already been fixed in input-hotplug, where we use a virtual core
keyboard and pointer.  you can't just allow things to go ahead without one,
because of the number of unconditional dereferences of inputInfo.pointer.

Comment 2 Jim Gettys 2006-10-30 13:32:46 UTC

When was this fixed?

I ask, as we're running pretty recent bits on the OLPC system....

Comment 3 Daniel Stone 2006-10-30 13:58:36 UTC

try nuking the checkCoreInputDevices call in hw/xfree86/common/xf86Config.c,
maybe?  i know for sure that it works in kdrive, because half the time i keep
forgetting '-mouse tslib' ...

Comment 4 Daniel Stone 2006-10-30 14:04:44 UTC

also, half the time, my grammar is always poor.

Comment 5 Daniel Stone 2006-11-01 17:36:50 UTC

fixed in ba9f5138fc32a7a7b97bcf941bc92751b7c6c2c0 -- put Option
"AllowEmptyInput" in server flags

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.