On Sat, 29 Sep 2018 10:14:33 +0200 Tobias Frost wrote:
> Regarding the reported issue, at the BSP in Chemnitz, helmut looked at
> his (stretch) installation and also saw the duplicated lines.
> I've also debootstraped an sid chroot, systemd-nspawn'ed it and could
> also see duplicated log lines.
Hallo Jörg,
during the BTS I came accross your bug report.
I'm sorry that you have problems with lirc, but I also see the
maintainer trying to help you solving the problem. However, the
questions he asked are clearly targeting to triage the bugs, and
I cannot say that the snappy remarks in your
severity 872749 grave
thanks
Hi,
first sorry for my late anwser.
Am Donnerstag, den 07.09.2017, 22:10 +0200 schrieb Alec Leamas:
>
> On 04/09/17 16:21, Jörg Frings-Fürst wrote:
>
> >
> > All messages logged twice:
> >
> > [quote]
> > Sep 4 05:22:48 merkur lircd[2247]: lircd-0.10.0[2247]:
On 04/09/17 16:21, Jörg Frings-Fürst wrote:
All messages logged twice:
[quote]
Sep 4 05:22:48 merkur lircd[2247]: lircd-0.10.0[2247]: Warning: config file
/etc/lirc/lircd.conf contains no valid remote control definition
Sep 4 05:22:48 merkur lircd[2247]: lircd-0.10.0[2247]: Notice:
tags 872749 - moreinfo
thanks
Hi,
Am Donnerstag, den 31.08.2017, 19:24 +0200 schrieb Alec Leamas:
> Hi!
>
>
> On 31/08/17 18:56, Jörg Frings-Fürst wrote:
>
> > I think you should fix the error times instead of thinking about
> > whether the title does not fit.
>
> As explained earlier, the
Hi!
On 31/08/17 18:56, Jörg Frings-Fürst wrote:
I think you should fix the error times instead of thinking about
whether the title does not fit.
As explained earlier, the fix is not simple from a packaging
perspective. Still, users could easily either disable lircd.socket or
just remove
Hi Alec,
Am Mittwoch, den 30.08.2017, 09:38 +0200 schrieb Alec Leamas:
> Hi!
>
> On 29/08/17 22:03, Jörg Frings-Fürst wrote:
> > Hi Alec,
> > > As a starter, what happens if you use journalctl to inspect the logs?
> > > Still same error? We need to establish the difference between your
> > >
Hi!
On 29/08/17 22:03, Jörg Frings-Fürst wrote:
Hi Alec,
As a starter, what happens if you use journalctl to inspect the logs?
Still same error? We need to establish the difference between your
setup and those I use...
Its the same (log all twice):
Aug 29 05:41:28 merkur lircd[4494]:
Hi Alec,
Am Montag, den 21.08.2017, 16:59 +0200 schrieb Alec Leamas:
>
> On 21/08/17 16:50, Jörg Frings-Fürst wrote:
> > Am Montag, den 21.08.2017, 09:32 +0200 schrieb Alec Leamas:
> > > On 21/08/17 09:04, Jörg Frings-Fürst wrote:
> > > > > > Aug 20 20:38:21 merkur lircd[2361]:
On 21/08/17 16:50, Jörg Frings-Fürst wrote:
Am Montag, den 21.08.2017, 09:32 +0200 schrieb Alec Leamas:
On 21/08/17 09:04, Jörg Frings-Fürst wrote:
Aug 20 20:38:21 merkur lircd[2361]: lircd-0.9.4c[2361]: Error: Cannot glob
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
Aug 20 20:38:21 merkur
Am Montag, den 21.08.2017, 09:32 +0200 schrieb Alec Leamas:
>
> On 21/08/17 09:04, Jörg Frings-Fürst wrote:
> >
> > > > Aug 20 20:38:21 merkur lircd[2361]: lircd-0.9.4c[2361]: Error: Cannot
> > > > glob
> > > > /sys/class/rc/rc0/input[0-9]*/event[0-9]*
> > > > Aug 20 20:38:21 merkur
On 21/08/17 09:04, Jörg Frings-Fürst wrote:
Aug 20 20:38:21 merkur lircd[2361]: lircd-0.9.4c[2361]: Error: Cannot glob
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
Aug 20 20:38:21 merkur lircd-0.9.4c[2361]: Error: Cannot glob
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
I cannot reproduce this,
Hi Alec,
Am Sonntag, den 20.08.2017, 21:44 +0200 schrieb Alec Leamas:
>
[...]
> > Aug 20 20:38:21 merkur lircd[2361]: lircd-0.9.4c[2361]: Error: Cannot glob
> > /sys/class/rc/rc0/input[0-9]*/event[0-9]*
> > Aug 20 20:38:21 merkur lircd-0.9.4c[2361]: Error: Cannot glob
> >
On 20/08/17 20:48, Jörg Frings-Fürst wrote:
Package: lirc
Version: 0.9.4c-9
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
every message if lircd logged twince:
Aug 20 20:38:21 merkur lircd[2361]: lircd-0.9.4c[2361]: Error: Cannot glob
14 matches
Mail list logo
