← Back to team overview

mythbuntu-bugs team mailing list archive

  1. mythbuntu-bugs team
  2. Mailing list archive
  3. Message #10939

[Bug 1768291] [NEW] lirc is flooding the syslog with two lines each second

  Thread Previous • Date Previous • • Thread Next 
Public bug reported:

Hello,

in the syslog every second two lines are written:

May  1 18:05:19 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:19 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:20 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:20 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:21 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:21 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:22 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:22 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:23 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:23 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:24 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:24 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:25 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:25 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:26 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:26 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:27 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:27 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:28 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
May  1 18:05:28 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*

This is not only annoying as it makes it difficult to use the syslog for
checking the system, but also it writes too much data into the log (18MB
each day). Also it keeps the hard disc awaken what is bad for standby.

Kubuntu 18.04
ii  liblirc-client0:amd64 0.10.0-2     amd64        infra-red remote control support - client library
ii  liblirc0:amd64        0.10.0-2     amd64        Infra-red remote control support - Run-time libraries
ii  lirc                  0.10.0-2     amd64        Infra-red remote control support - daemons and utils

I do not have infrared remote control hardware. But I cannot purge the
packages as other packages I want to keep would be removed as well.
Deactivating the services in systemd does not help (or I am doing
something wrong?)

Greetings
Gert

** Affects: lirc (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1768291

Title:
  lirc is flooding the syslog with two lines each second

Status in lirc package in Ubuntu:
  New

Bug description:
  Hello,

  in the syslog every second two lines are written:

  May  1 18:05:19 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:19 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:20 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:20 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:21 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:21 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:22 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:22 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:23 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:23 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:24 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:24 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:25 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:25 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:26 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:26 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:27 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:27 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:28 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
  May  1 18:05:28 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*

  This is not only annoying as it makes it difficult to use the syslog
  for checking the system, but also it writes too much data into the log
  (18MB each day). Also it keeps the hard disc awaken what is bad for
  standby.

  Kubuntu 18.04
  ii  liblirc-client0:amd64 0.10.0-2     amd64        infra-red remote control support - client library
  ii  liblirc0:amd64        0.10.0-2     amd64        Infra-red remote control support - Run-time libraries
  ii  lirc                  0.10.0-2     amd64        Infra-red remote control support - daemons and utils

  I do not have infrared remote control hardware. But I cannot purge the
  packages as other packages I want to keep would be removed as well.
  Deactivating the services in systemd does not help (or I am doing
  something wrong?)

  Greetings
  Gert

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1768291/+subscriptions

Follow ups

  Thread Previous • Date Previous • • Thread Next