Hello,
In adding systemd unit support to the qcontrol package (#781886) I
needed to add a udev rule (60-qcontrol.rules):
KERNELS==gpio-keys, SUBSYSTEMS==platform, DRIVERS==gpio-keys,
TAG+=systemd
In order to tag /dev/input/by-path/platform-gpio-keys-event for systemd,
so that the
On Sun, 2015-05-10 at 15:39 +0200, Michael Biebl wrote:
Am 10.05.2015 um 15:37 schrieb Michael Biebl:
Am 10.05.2015 um 14:46 schrieb Ian Campbell:
Hello,
In adding systemd unit support to the qcontrol package (#781886) I
needed to add a udev rule (60-qcontrol.rules):
KERNELS
On Sun, 2015-05-10 at 15:37 +0200, Michael Biebl wrote:
Am 10.05.2015 um 14:46 schrieb Ian Campbell:
Hello,
In adding systemd unit support to the qcontrol package (#781886) I
needed to add a udev rule (60-qcontrol.rules):
KERNELS==gpio-keys, SUBSYSTEMS==platform, DRIVERS==gpio
On Thu, 2015-04-16 at 10:28 +0200, reportbug wrote:
On Wed, Apr 15, 2015 at 19:19:24 +0100, Ian Campbell wrote:
@reportbug (sorry I don't seem to know your real name), could you try
adding a call to udev settle to the qcontrold initscript, in the start
case right before the daemon
On Thu, 2015-04-16 at 11:28 +0200, reportbug wrote:
On Thu, Apr 16, 2015 at 10:21:06 +0100, Ian Campbell wrote:
BTW, when this fails the system still booted and you could login and fix
it, i.e. it didn't stall the boot or anything, is that right? If that is
the case a release note might
Control: reopen -1
Control: found -1 215-5+b1
On Sun, 14 Sep 2014 17:20:47 +0200 Michael Biebl bi...@debian.org wrote:
I'm going to close this bug for now. If you still encounter any issues
and you have additional information, please let us know, so we can
reopen the bug report.
I'm seeing
