[PATCH] libinput-seat: Don't regard no input devices as failure

Peter Hutterer peter.hutterer at who-t.net
Sun Jan 4 14:28:45 PST 2015


On Tue, Dec 30, 2014 at 05:19:45PM +0000, Daniel Stone wrote:
> Hi,
> 
> On 29 December 2014 at 00:03, Peter Hutterer <peter.hutterer at who-t.net>
> wrote:
> 
> > On Sun, Dec 28, 2014 at 11:25:16PM +0100, Sjoerd Simons wrote:
> > > The reason for not having any input devices could actually be that there
> > > are no input devices attached, imagine that. Mention that cause in the
> > > warning and no longer return an error.
> > >
> > > This fixes starting weston on boards with no input devices attached.
> > >
> > > Signed-off-by: Sjoerd Simons <sjoerd.simons at collabora.co.uk>
> >
> > Reviewed-by: Peter Hutterer <peter.hutterer at who-t.net>
> >
> > though I'd use "available" over "attached" which is less ambiguous in
> > a multi-seat scenario.
> >
> 
> It'd be nice to distinguish between 'devices are available but could not be
> opened', and no devices whatsoever. In either case, we made Xorg require an
> option (AllowEmptyInput) to start with no devices, and I guess it could be
> nice to do the same for weston-launch.

fwiw, AEI was removed in the server because 99% of the people who used it
got it from some outdated Ubuntu forum/wiki, didn't know what it did and
then filed bugs because it did what it was supposed to do...
But aside from that, I think it'd be useful for Weston to have a toggle for
this.

Cheers,
   Peter


More information about the wayland-devel mailing list