Bug#797881: QNAP TS-219P II: qcontrol no longer works after upgrading to linux-image-4.1.0-0.bpo.1-kirkwood
On Thu, 2015-12-10 at 07:36 +0000, Ian Campbell wrote:
> On Wed, 2015-12-09 at 16:04 -0800, Martin Michlmayr wrote:
> > * Ian Campbell <ijc@debian.org> [2015-10-04 14:04]:
> > > I suspect this is due to the device path for the input node
> > changing
> > > from /dev/input/by-path/platform-gpio_keys-event to /dev/input/by
> > > -path/platform-gpio-keys-event. With the version of qcontrol in
> > Jessie
> > > it won't even start if it can't find the device, even though it
> can
> > do
> > > many of its core things without it (the node is for button input
> > only).
> > >
> > > This is fixed by qcontrol 0.5.4-4 in testing (both looking for
> old
> > and
> > > new names, as well as not treating failure to find either as a
> > > catastrophe), but for Jessie you can just edit the path in
> > > /etc/qcontrol.conf.
> > >
> > > If that works for you then it might be worth uploading an updated
> > > qcontrol to backports.
> >
> > Ian, were you going to upload qcontrol to backports or did you want
> > someone else to do it?
>
> I wasn't, but now I am. I've left a build going and will (hopefully)
> upload after breakfast.
Done (pending a successful dinstall run).
Cheers,
Ian.
Reply to: