[Desktop-packages] [Bug 1843988] Re: python library installed into site-packages instead of into dist-packages

[Alec Leamas]

You are indeed right. Python libraries are not multilib, and should live
in  /usr/lib/python3/site-packages. Will fix, but the process starts at
the Debian side.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1843988

Title:
  python library installed into site-packages instead of into dist-
  packages

Status in lirc package in Ubuntu:
  New

Bug description:
  The lirc package comes with python libraries and it installs the libraries 
into 
 /usr/lib/x86_64-linux-gnu/python3.6/site-packages
  This results in the libraries not being found by system python.

  From what I read in https://wiki.debian.org/Python
  they should instead be installed into 
 /usr/lib/python3/dist-packages

  
  Release:18.04

  Package: lirc
  Version: 0.10.0-2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lirc 0.10.0-2
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 14 12:41:30 2019
  InstallationDate: Installed on 2014-08-28 (1842 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  SourcePackage: lirc
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (395 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1832885] Re: package lirc 0.10.1-5.2 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1

[Alec Leamas]

The core issue here is the dependency in vdr. There is a ticket [1]
about this.

Otherwise, the simple work-around is uninstall the lirc package.

This is an old bug. I see no new reports or comments lately, which seems
to indicate that it is fixed in current release.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012274

** Bug watch added: Debian Bug tracker #1012274
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012274

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1832885

Title:
  package lirc 0.10.1-5.2 failed to install/upgrade: installed lirc
  package post-installation script subprocess returned error exit status
  1

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  I tried to install vdr. lirc comes as a dependency...

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: lirc 0.10.1-5.2
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Fri Jun 14 21:14:27 2019
  ErrorMessage: installed lirc package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2019-05-18 (27 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.6ubuntu1
   apt  1.8.1
  SourcePackage: lirc
  Title: package lirc 0.10.1-5.2 failed to install/upgrade: installed lirc 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1768291] Re: lirc is flooding the syslog with two lines each second

[Alec Leamas]

Filed vdr issue: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1012274

** Bug watch added: Debian Bug tracker #1012274
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012274

-- 
You received this bug notification because you are a member of Desktop
Packages, 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:
  Triaged

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 amd64infra-red remote control 
support - client library
  ii  liblirc0:amd640.10.0-2 amd64Infra-red remote control 
support - Run-time libraries
  ii  lirc  0.10.0-2 amd64Infra-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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1843988] Re: python library installed into site-packages instead of into dist-packages

[Alec Leamas]

Sorry for late reply.

The python module contains binary. architecture-dependent code and can
for that reason not be installed in  /usr/lib/python3/ due to overall
multi-arch requirements.

That said, the official Debian documents I find are not explicit on how
to install these kind of modules. Sending a message to debian-devel in
an attempt to get this sorted out.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1843988

Title:
  python library installed into site-packages instead of into dist-
  packages

Status in lirc package in Ubuntu:
  New

Bug description:
  The lirc package comes with python libraries and it installs the libraries 
into 
 /usr/lib/x86_64-linux-gnu/python3.6/site-packages
  This results in the libraries not being found by system python.

  From what I read in https://wiki.debian.org/Python
  they should instead be installed into 
 /usr/lib/python3/dist-packages

  
  Release:18.04

  Package: lirc
  Version: 0.10.0-2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lirc 0.10.0-2
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 14 12:41:30 2019
  InstallationDate: Installed on 2014-08-28 (1842 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  SourcePackage: lirc
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (395 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1768291] Re: lirc is flooding the syslog with two lines each second

[Alec Leamas]

lirc does not spam the log if correctly configured. The repeated
messages is a actually a feature since it's an easy way to detect status
when configuring and hot-plugging a device.

The basic issue here is if lirc is pulled in as a dependency. It should
not, it's designed to be used by users which actually have the need. The
only rdepends I find in Sid is a Recommends in the vdr package. I'll
file an issue about that. Once this is fixed, no-one will have lirc
installed "by accident" so to speak.

For users which does not use lirc there are two options. One is to
remove the package completely, this should be possible on all
installations since there are no hard rdepends, just a Recommends in the
vdr package.

The other is to disable  lircd.socket and lircd.uinput using systemctl.
This is nothing special, it's standard system service configuration.

Besides the R: lirc in the vdr package I thus still don't see any actual
bug here. What *could* be considered is to add some info to the logged
message about disabling services to get rid of it.

Allowing a unused service to continue to run as root without spamming
the log is wrong for security and performance reasons. Hence, just
writing the log message once is IMHO not a viable alternative.

-- 
You received this bug notification because you are a member of Desktop
Packages, 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:
  Triaged

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 amd64infra-red remote control 
support - client library
  ii  liblirc0:amd640.10.0-2 amd64Infra-red remote control 
support - Run-time libraries
  ii  lirc  0.10.0-2 amd64Infra-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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : 

[Desktop-packages] [Bug 1817441] Re: lirc ITE8713 not working

[Alec Leamas]

[sorry for late walking through bugs]

Have you tried the installation instructions as described in the
upstream docs[1] ?

[1] https://www.lirc.org/html/configuration-guide.html

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1817441

Title:
  lirc ITE8713 not working

Status in lirc package in Ubuntu:
  New

Bug description:
  On Zotac ZBOX NANO AQ01 remote control with in build ir receiver does
  not work.

  $ irw # gives not output at all
  $ mode2 -d /dev/lirc0 # gives output
  $ sudo dpkg-reconfigure lirc # Windows Media Center Transceivers/Remotes 
(all) chosen

  $ sudo systemctl status lirc
  ● lirc.service - LSB: Starts LIRC daemon.
 Loaded: loaded (/etc/init.d/lirc; generated)
 Active: active (running) since Sun 2019-02-24 00:48:21 CET; 17min ago
   Docs: man:systemd-sysv-generator(8)
Process: 6693 ExecStart=/etc/init.d/lirc start (code=exited, 
status=0/SUCCESS)
  Tasks: 1 (limit: 3976)
 CGroup: /system.slice/lirc.service
 └─6706 /usr/sbin/lircd --output=/run/lirc/lircd --device=/dev/lirc0

  Feb 24 00:48:21 keksdose systemd[1]: Starting LSB: Starts LIRC daemon
  Feb 24 00:48:21 keksdose lirc[6693]:  * Loading LIRC modules
  Feb 24 00:48:21 keksdose lirc[6693]:...done.
  Feb 24 00:48:21 keksdose lirc[6693]:  * Starting remote control daemon(s) :
  Feb 24 00:48:21 keksdose lircd-0.9.0[6706]: lircd(default) ready, using 
/run/lirc/lircd
  Feb 24 00:48:21 keksdose lirc[6693]:...done.
  Feb 24 00:48:21 keksdose systemd[1]: Started LSB: Starts LIRC daemon..
  Feb 24 00:48:24 keksdose lircd-0.9.0[6706]: accepted new client on 
/run/lirc/lircd
  Feb 24 00:48:50 keksdose lircd-0.9.0[6706]: removed client

  $ sudo ir-keytable 
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Name: ITE8713 CIR transceiver
Driver: ite-cir, table: rc-rc6-mce
lirc device: /dev/lirc0
Supported protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 
sharp xmp 
Enabled protocols: lirc 
bus: 25, vendor/product: 1283:, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1778569] Re: ir-keytable -c -w /etc/rc_keymaps/file

[Alec Leamas]

Late comment: vlc does not depend on lirc any more, so this should not
happen to new installations.

Work around for existing installations is to either remove the lirc
package or simply disable lircd.socket, lircd.service and lircd-uinput
using systemctl.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1778569

Title:
  ir-keytable -c -w /etc/rc_keymaps/file

Status in lirc package in Ubuntu:
  New

Bug description:
  Subject pretty much says it all. Installing vlc also installs 
liblirc-client0. This hoses up kernel lirc by not allowing some key codes to be 
passed to apps. ir-keytable -t shows it is working fine. Removing 
liblirc-client0 fixes the problem but also removes vlc.
  See mt last post for more details.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04

[Alec Leamas]

https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/comments/16
is a beginning...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1788235

Title:
  lirc broken on 18.04

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Lirc 0.10.0-2 is never configured after installation. Manually running
  "dpkg-reconfigure lirc " also does not do anything. I also noticed
  that /usr/share/lirc/remotes is empty, which is where I had my config
  file for Ubuntu 16.04.

  This was an upgrade install from 16.04.
  Searching the web indicates others have this problem. Some have reverted to 
the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I 
have been unsuccessful so far.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1791409] Re: LIRC not working on Ubuntu 18.04

[Alec Leamas]

Basically, it isn't buggy but requires manual intervention when
updating.

A script called lirc-setup is however broken. It's primary use-case is
fresh installs rather than updates which have no need for it. A
workaround to make it wotk could be found in comment #2.

Some users have had problems with duplicated keys caused by the lirc-
uinput.service running. Stopping the service fixes this (it is not
enabled by default in recent updates).

However, the main problem is users claiming that lirc should work as
before without changes after a fully unattended update. I have done what
I can to describe that this is not the case...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1791409

Title:
  LIRC not working on Ubuntu 18.04

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  It appears that the LIRC 0.10.0-2 package for Ubuntu 18.04 (bionic) is
  not working correctly. The usual configuration menu to select your
  remote does not come up after installing the package.

  Saw some other mentions of this issue as well on the forums:
  https://ubuntuforums.org/showthread.php?t=2396923

  This handy blog post shows a workaround of installing an older version
  (0.9.0) from xenial to get it to work:
  https://twosortoftechguys.wordpress.com/2018/07/24/make-lirc-work-in-
  ubuntu-18-04/

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1791409] Re: LIRC not working on Ubuntu 18.04

[Alec Leamas]

> I suppose it is a bug, as lirc should work after upgrade without
manual reconfiguration.

No it should not, as apparent if you read the comkplete discussion in
this bug or, more on the spot,  bug #1788235.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1791409

Title:
  LIRC not working on Ubuntu 18.04

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  It appears that the LIRC 0.10.0-2 package for Ubuntu 18.04 (bionic) is
  not working correctly. The usual configuration menu to select your
  remote does not come up after installing the package.

  Saw some other mentions of this issue as well on the forums:
  https://ubuntuforums.org/showthread.php?t=2396923

  This handy blog post shows a workaround of installing an older version
  (0.9.0) from xenial to get it to work:
  https://twosortoftechguys.wordpress.com/2018/07/24/make-lirc-work-in-
  ubuntu-18-04/

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1791409] Re: LIRC not working on Ubuntu 18.04

[Alec Leamas]

That said, if someone filed a bug against lirc because lirc-setup is
broken, that bug is certainly valid.  But IMHO, that's a very different
story. And since there is a usable work-around it would probably just be
closed as fixed upstream.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1791409

Title:
  LIRC not working on Ubuntu 18.04

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  It appears that the LIRC 0.10.0-2 package for Ubuntu 18.04 (bionic) is
  not working correctly. The usual configuration menu to select your
  remote does not come up after installing the package.

  Saw some other mentions of this issue as well on the forums:
  https://ubuntuforums.org/showthread.php?t=2396923

  This handy blog post shows a workaround of installing an older version
  (0.9.0) from xenial to get it to work:
  https://twosortoftechguys.wordpress.com/2018/07/24/make-lirc-work-in-
  ubuntu-18-04/

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1791409] Re: LIRC not working on Ubuntu 18.04

[Alec Leamas]

The main issue described in this bug is bogus, as apparent from  bug
#1788235

However, the configuration script lirc-setup *is* indeed broken . This
is fixed in Debian upstream from 0.10.1, but hasn't trickled down.  That
said, users will still need to read README.Debian, and the process to
configure lirc is still very different from what it used to be. Also,
most users updating does not need lirc-setup.

I'm  considering  closing this bug as a duplicate or just invalid.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1791409

Title:
  LIRC not working on Ubuntu 18.04

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  It appears that the LIRC 0.10.0-2 package for Ubuntu 18.04 (bionic) is
  not working correctly. The usual configuration menu to select your
  remote does not come up after installing the package.

  Saw some other mentions of this issue as well on the forums:
  https://ubuntuforums.org/showthread.php?t=2396923

  This handy blog post shows a workaround of installing an older version
  (0.9.0) from xenial to get it to work:
  https://twosortoftechguys.wordpress.com/2018/07/24/make-lirc-work-in-
  ubuntu-18-04/

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04

[Alec Leamas]

> Kodi definitely works with the latest versions of Lirc and the problem i
> is very easy to fix so stop downgrading your systems to an older version of 
> Lirc

Right.

> The problem is Kodi defaults to looking for a Lirc socket at /dev/lircd which 
> doesn’t exist anymore.

Has anyone cared to file a bug against kodi on this?

> 3. Modify the /lib/systemd/system/lircd.service to create a symlink 
> from /dev/lircd to /var/run/lirc/lircd each time the lircd.service or 
> system is restarted:

Please, no. The files in /lib/systemd/system should not be tampered with, they 
are
replaced on package update without mercy. Instead, copy 
/lib/systemd/system/lircd.service
to /etc/systemd/system and modify that copy (it overrides the /lib/systemd one).

Also note that lirc_options.conf supports code: stanzas which are executed as
root before lircd is launched. Linking could be done here instead of patching 
the service
file.

And, finally: the /dev directory is just not aimed for this kind of files, it's 
supposed
to be handled by udev. So, creating links here should be avoided if at all 
possible.

> e.g: sudo systemctl disable lircd-uinput.service

Indeed. Debian upstream by default disables this service in last update. Using 
'systemctl disable --now lircd-uinput.service' is probably the best to both 
stop and disable. 

> What I still cannot get working is the lirc-setup app (which replaces
dpkg-reconfigure lirc)

Also this is fixed in debian upstream. Until it trickles down, the dirty 
work-around is 
something like:


# libdir=/usr/lib/x86_64-linux-gnu/python3.6/site-packages
# cp /usr/share/lirc/python-pkg/config.py $libdir/lirc
# ln -s $libdir/lirc /usr/lib/python3/dist-packages/
# ln -s $libdir/lirc-setup /usr/lib/python3/dist-packages/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1788235

Title:
  lirc broken on 18.04

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Lirc 0.10.0-2 is never configured after installation. Manually running
  "dpkg-reconfigure lirc " also does not do anything. I also noticed
  that /usr/share/lirc/remotes is empty, which is where I had my config
  file for Ubuntu 16.04.

  This was an upgrade install from 16.04.
  Searching the web indicates others have this problem. Some have reverted to 
the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I 
have been unsuccessful so far.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1778569] Re: ir-keytable -c -w /etc/rc_keymaps/file

[Alec Leamas]

To further investigate this issues, a question is if the main lirc
package is installed. If so, the lircd.socket, lircd.service and lircd-
uinput.services should be disabled and stopped. If problem persists,
with or without liblircclient installed, this should be re-assigned to
the kernel

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1778569

Title:
  ir-keytable -c -w /etc/rc_keymaps/file

Status in lirc package in Ubuntu:
  New

Bug description:
  Subject pretty much says it all. Installing vlc also installs 
liblirc-client0. This hoses up kernel lirc by not allowing some key codes to be 
passed to apps. ir-keytable -t shows it is working fine. Removing 
liblirc-client0 fixes the problem but also removes vlc.
  See mt last post for more details.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1791409] Re: LIRC not working on Ubuntu 18.04

[Alec Leamas]

This is fixed in debian upstream. Until this trickles down, the  walk-
around is something like


# libdir=/usr/lib/x86_64-linux-gnu/python3.6/site-packages
# cp /usr/share/lirc/python-pkg/config.py $libdir/lirc
# ln -s $libdir/lirc /usr/lib/python3/dist-packages/
# ln -s $libdir/lirc-setup /usr/lib/python3/dist-packages/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1791409

Title:
  LIRC not working on Ubuntu 18.04

Status in lirc package in Ubuntu:
  New

Bug description:
  It appears that the LIRC 0.10.0-2 package for Ubuntu 18.04 (bionic) is
  not working correctly. The usual configuration menu to select your
  remote does not come up after installing the package.

  Saw some other mentions of this issue as well on the forums:
  https://ubuntuforums.org/showthread.php?t=2396923

  This handy blog post shows a workaround of installing an older version
  (0.9.0) from xenial to get it to work:
  https://twosortoftechguys.wordpress.com/2018/07/24/make-lirc-work-in-
  ubuntu-18-04/

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04

[Alec Leamas]

So, changing status.
@xekon: dpkg-reconfigure doesn't do anything at all...

** Changed in: lirc (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1788235

Title:
  lirc broken on 18.04

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Lirc 0.10.0-2 is never configured after installation. Manually running
  "dpkg-reconfigure lirc " also does not do anything. I also noticed
  that /usr/share/lirc/remotes is empty, which is where I had my config
  file for Ubuntu 16.04.

  This was an upgrade install from 16.04.
  Searching the web indicates others have this problem. Some have reverted to 
the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I 
have been unsuccessful so far.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04

[Alec Leamas]

> @»ekon, @Alec, thanks for your comments, reading those it looks like
you are stating that there is no real bug, just that the changes in the
software and its configuration files confused users that were used to
the old way? E.g nothing that needs to be resolved?

Right, from my point of view this should be closed as not-a-bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1788235

Title:
  lirc broken on 18.04

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  Lirc 0.10.0-2 is never configured after installation. Manually running
  "dpkg-reconfigure lirc " also does not do anything. I also noticed
  that /usr/share/lirc/remotes is empty, which is where I had my config
  file for Ubuntu 16.04.

  This was an upgrade install from 16.04.
  Searching the web indicates others have this problem. Some have reverted to 
the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I 
have been unsuccessful so far.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04

[Alec Leamas]

@seb128: The missing UI refers to the reconfiguration UI which was part
of lirc up to 0.9.0. This reflected even older code containing kernel
modules where lirc was rebuilt from source depending on configuration.
Nowadays lirc is a just a server with configuration files and there is
no need to make anything special at configuration time.

There are new tools available to assist in configuration, but these can
and should be used after installation.

Bottom line seems to be that the expectation was that nothing is
changed. However, it is. The decision to make a breaking change was not
taken lightly, it actually took several years, but eventually it became
necessary.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1788235

Title:
  lirc broken on 18.04

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  Lirc 0.10.0-2 is never configured after installation. Manually running
  "dpkg-reconfigure lirc " also does not do anything. I also noticed
  that /usr/share/lirc/remotes is empty, which is where I had my config
  file for Ubuntu 16.04.

  This was an upgrade install from 16.04.
  Searching the web indicates others have this problem. Some have reverted to 
the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I 
have been unsuccessful so far.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04

[Alec Leamas]

Seems that we agree that the idea that lirc as of 18.04 is "broken" is
plain wrong.

The problem is about making a correct upgrade which involves manual
steps as described in README.Debian (with a notification in the upgrade
message).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1788235

Title:
  lirc broken on 18.04

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  Lirc 0.10.0-2 is never configured after installation. Manually running
  "dpkg-reconfigure lirc " also does not do anything. I also noticed
  that /usr/share/lirc/remotes is empty, which is where I had my config
  file for Ubuntu 16.04.

  This was an upgrade install from 16.04.
  Searching the web indicates others have this problem. Some have reverted to 
the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I 
have been unsuccessful so far.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04

[Alec Leamas]

> Is there more documentation at a website that I could read to learn
more?

The official site is http://lirc.org. Among other things, here is an
updated Configuration Guide.

> I am particularly interested in the info about the raw events from the
socket.

At the same site there is info on the APIs, in particular the Client
API. The problem is that Kodi uses the raw events (documented in
lircd(8)) instead of  using that API. Changing this in a stable
application as Kodi requires some serious thinking  to not break
existing setups -- using the proper client API functionality must
basically be opt-in, I guess. That said, scanning the docs will reveal
the functionality in the API which is missing in the raw socket
interface.

The first step should be to file a bug against Kodi for not using the
API and the corresponding loss of lirc functionality (and, ironically,
added configuration complexity).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1788235

Title:
  lirc broken on 18.04

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  Lirc 0.10.0-2 is never configured after installation. Manually running
  "dpkg-reconfigure lirc " also does not do anything. I also noticed
  that /usr/share/lirc/remotes is empty, which is where I had my config
  file for Ubuntu 16.04.

  This was an upgrade install from 16.04.
  Searching the web indicates others have this problem. Some have reverted to 
the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I 
have been unsuccessful so far.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04

[Alec Leamas]

> While I am sure LIRC has a lot of uses. I would wager 90% of its users
are using kodi.

This might be the truth as seen from the kodi community. However, from
an upstream lirc point of view I cannot really see that the number of
kodi users are dominating in any way.

>  forgot a couple steps, here was all of them:

While these steps worked for you, other users will have other needs.
That said, disabling/stopping lircd-uinput might be a good idea in many
cases.  The last update to lirc has it disabled by default.

> also some discussion here:
https://forum.kodi.tv/showthread.php?tid=324727

That discussion is utterly confused and does not mention the need to
migrate (manual or automatic) the old 0.9.0 setup to the new one. Also,
some users in that thread are using the default driver while other seem
to be using the devinput one. No one seems to be reading the
documentation, but still seems to be able to establish the "fact" that
lirc is broken.

If it was possible to file a bug against the Kodi community overall I
would consider doing that ;)

On top of that Kodi is the one and only application which misuses lirc
by using the raw events from the socket -- this makes lirc seriously
crippled compared to the real stuff. I filed a bug on this long ago, but
at a glance it seems to be lost.

Unless there is more input I will close this as not-a-bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1788235

Title:
  lirc broken on 18.04

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  Lirc 0.10.0-2 is never configured after installation. Manually running
  "dpkg-reconfigure lirc " also does not do anything. I also noticed
  that /usr/share/lirc/remotes is empty, which is where I had my config
  file for Ubuntu 16.04.

  This was an upgrade install from 16.04.
  Searching the web indicates others have this problem. Some have reverted to 
the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I 
have been unsuccessful so far.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04

[Alec Leamas]

Now, considering these reports one cannot IMHO really say that lirc is
'broken'. What could be said is that the upgrade to the new version
requires manual steps, none of which mentioned in this report.

The manual steps are documented in the file
/usr/share/doc/lirc/README.Debian.gz -- this is presented in the upgrade
message for lirc.

>From xekon's note it's clear that the new lirc installation is using the
default setup. It just cannot work as expected. However, the
documentation is pretty clear and there is even a migration script.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1788235

Title:
  lirc broken on 18.04

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  Lirc 0.10.0-2 is never configured after installation. Manually running
  "dpkg-reconfigure lirc " also does not do anything. I also noticed
  that /usr/share/lirc/remotes is empty, which is where I had my config
  file for Ubuntu 16.04.

  This was an upgrade install from 16.04.
  Searching the web indicates others have this problem. Some have reverted to 
the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I 
have been unsuccessful so far.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1685394] Re: hp media center remote not responding

[Alec Leamas]

Glad that it works for you. The question is just how...

As noted in the README, from 0.9.4 all lircd.conf files needs names like
mce.lircd.conf i. e., with a lircd.conf suffix. The default lircd.conf
files only includes files with this suffix. That said, a custom
lircd.conf could of course include anything.

Given the overall situation, this is more like a support request than a
bug, right?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1685394

Title:
  hp media center remote not responding

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  The hp mce remote was working fine with kodi running on Ubuntu 16.10. After 
upgrade to 17.04, 
  the remote does not respond anymore. Loads the driver, dmesg looks ok. I 
managed to get it to respond a couple of times after a reboot by unpluging an 
plugging back in. 
  ir-keytable gives:

  Found /sys/class/rc/rc0/ (/dev/input/event9) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo 
mce_kbd rc-6 sharp xmp 
Enabled protocols: lirc rc-6 
Name: Media Center Ed. eHome Infrared 
bus: 3, vendor/product: 1934:5168, version: 0x0001
Repeat delay = 500 ms, repeat period = 125 ms
  I suspect this is a bug because it happenee just after the upgrade
  any help would be greatly appreciated
  cheers
  Michael

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lirc 0.9.4c-9
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 22 10:28:49 2017
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lirc
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (4 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-18T19:07:44.10
  mtime.conffile..etc.lirc.lircd.conf: 2017-04-18T18:58:35.039496

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1685394] Re: hp media center remote not responding

[Alec Leamas]

Oops... seems that the default lircd.conf only requires .conf suffix,
not lircd.conf. All solved, my bad.


** Changed in: lirc (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1685394

Title:
  hp media center remote not responding

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  The hp mce remote was working fine with kodi running on Ubuntu 16.10. After 
upgrade to 17.04, 
  the remote does not respond anymore. Loads the driver, dmesg looks ok. I 
managed to get it to respond a couple of times after a reboot by unpluging an 
plugging back in. 
  ir-keytable gives:

  Found /sys/class/rc/rc0/ (/dev/input/event9) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo 
mce_kbd rc-6 sharp xmp 
Enabled protocols: lirc rc-6 
Name: Media Center Ed. eHome Infrared 
bus: 3, vendor/product: 1934:5168, version: 0x0001
Repeat delay = 500 ms, repeat period = 125 ms
  I suspect this is a bug because it happenee just after the upgrade
  any help would be greatly appreciated
  cheers
  Michael

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lirc 0.9.4c-9
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 22 10:28:49 2017
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lirc
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (4 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-18T19:07:44.10
  mtime.conffile..etc.lirc.lircd.conf: 2017-04-18T18:58:35.039496

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1685646] Re: 'dpkg-reconfigure lirc' doesn't work as expected.

[Alec Leamas]

The package contains a README.Debian.gz file which explains the changes
done. A reference to this file was displayed when you upgraded lirc, but
perhaps you missed it (such things happens, for sure).

The update 0.9.0 -> 0.9.4 is a breaking update requiriung manual
intervention as described in this file. Have you read it and performed
the manual steps described therein?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1685646

Title:
  'dpkg-reconfigure lirc' doesn't work as expected.

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  The lirc package does not respond predictably to the 'sudo dpkg-
  reconfigure lirc' command. When the command is run, the following
  messages are displayed:

  Warning: Stopping lircd.service, but it can still be activated by:
lircd.socket
  Listing '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/'...
  Compiling 
'/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/baseview.py'...
  Compiling 
'/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/choosers.py'...
  Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/config.py'...
  Compiling 
'/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/database.py'...
  Compiling 
'/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/mvc_control.py'...
  Compiling 
'/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/mvc_model.py'...
  Compiling 
'/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/mvc_view.py'...
  Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/util.py'...

  This is followed by the system abruptly dropping back to shell without
  the configuration screen displayed. No other errors are displayed.
  There is no errors in dmesg.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1685394] Re: hp media center remote not responding

[Alec Leamas]

At a closer look, the configuration seems messy. E. g.,
/etc/lirc/lirc.conf includes a file from /usr/share/lirc/configs, a
directory not present in 0.9.4.

Have you worked through the necessary manual upgrade steps as described
in /usr/share/doc/lirc/README.Debian.gz?

Note that the missing remotes in /usr/share/lirc/configs are available
in the lirc-compat-remotes packages.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1685394

Title:
  hp media center remote not responding

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  The hp mce remote was working fine with kodi running on Ubuntu 16.10. After 
upgrade to 17.04, 
  the remote does not respond anymore. Loads the driver, dmesg looks ok. I 
managed to get it to respond a couple of times after a reboot by unpluging an 
plugging back in. 
  ir-keytable gives:

  Found /sys/class/rc/rc0/ (/dev/input/event9) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo 
mce_kbd rc-6 sharp xmp 
Enabled protocols: lirc rc-6 
Name: Media Center Ed. eHome Infrared 
bus: 3, vendor/product: 1934:5168, version: 0x0001
Repeat delay = 500 ms, repeat period = 125 ms
  I suspect this is a bug because it happenee just after the upgrade
  any help would be greatly appreciated
  cheers
  Michael

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lirc 0.9.4c-9
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 22 10:28:49 2017
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lirc
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (4 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-18T19:07:44.10
  mtime.conffile..etc.lirc.lircd.conf: 2017-04-18T18:58:35.039496

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1685646] Re: 'dpkg-reconfigure lirc' doesn't work as expected.

[Alec Leamas]

Previous versions needed some configuration to basically make a
conditional compilation. Possibly, submitter expects the configuration
menu as of 0.9.0. However, there is no such menu in 0.9.4 - all
configuration is done after installation using regular configuration
files

Given this, my provisionary conclusion is that this should be closed as
not-a-bug unless there is more input.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1685646

Title:
  'dpkg-reconfigure lirc' doesn't work as expected.

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  The lirc package does not respond predictably to the 'sudo dpkg-
  reconfigure lirc' command. When the command is run, the following
  messages are displayed:

  Warning: Stopping lircd.service, but it can still be activated by:
lircd.socket
  Listing '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/'...
  Compiling 
'/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/baseview.py'...
  Compiling 
'/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/choosers.py'...
  Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/config.py'...
  Compiling 
'/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/database.py'...
  Compiling 
'/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/mvc_control.py'...
  Compiling 
'/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/mvc_model.py'...
  Compiling 
'/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/mvc_view.py'...
  Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/util.py'...

  This is followed by the system abruptly dropping back to shell without
  the configuration screen displayed. No other errors are displayed.
  There is no errors in dmesg.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1681838] Re: IR pilot is not working after kernel change from 3.13 to 4.4

[Alec Leamas]

Re-assigning to kernel packagem possiblye the wrong one.,

** Package changed: lirc (Ubuntu) => kernel-package (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1681838

Title:
  IR pilot is not working after kernel change from 3.13 to 4.4

Status in kernel-package package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04
  linux-image-4.4.0-72-generic

  I'm using custom IR receiver with CIR header in my ASRock MoBo.
  This one IR receiver serves 3 devices - HTPC, TV and amplifier.

  Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped 
to work with HTPC.
  mode2 app shows, that IR header is receiving something, but there is 
something wrong.

  Example pulse-pause timings for 3.13 kernel are:
  space 2949
  pulse 39
  space 1157
  pulse 39
  space 1159
  pulse 39
  Example pulse-pause timings for 4.4 kernel are:
  space 16777176
  pulse 1
  space 16777176
  pulse 1
  space 16777176
  pulse 1

  for this same button.

  Maybe I'm not only one which wants still to use lirc_sir
  Please, help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lirc 0.9.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-116-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Tue Apr 11 11:55:14 2017
  SourcePackage: lirc
  UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756
  mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289
  --- 
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dugi  10933 F pulseaudio
   /dev/snd/controlC0:  dugi  10933 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: lirc 0.9.0-0ubuntu5
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic 
root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro 
video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf 
nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: lirc_sir
  Tags:  trusty staging trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 07/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.60
  dmi.board.name: FM2A75 Pro4-M
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386
  mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289
  --- 
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  Package: lirc 0.9.0-0ubuntu5
  PackageArchitecture: amd64
  Tags:  trusty
  Uname: Linux 4.11.0-041100rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1681838/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1685394] Re: hp media center remote not responding

[Alec Leamas]

> I figured out that the lirc device path changed in the new version.

This was actually changed in 0.9.0, upstream release (2011)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1685394

Title:
  hp media center remote not responding

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  The hp mce remote was working fine with kodi running on Ubuntu 16.10. After 
upgrade to 17.04, 
  the remote does not respond anymore. Loads the driver, dmesg looks ok. I 
managed to get it to respond a couple of times after a reboot by unpluging an 
plugging back in. 
  ir-keytable gives:

  Found /sys/class/rc/rc0/ (/dev/input/event9) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo 
mce_kbd rc-6 sharp xmp 
Enabled protocols: lirc rc-6 
Name: Media Center Ed. eHome Infrared 
bus: 3, vendor/product: 1934:5168, version: 0x0001
Repeat delay = 500 ms, repeat period = 125 ms
  I suspect this is a bug because it happenee just after the upgrade
  any help would be greatly appreciated
  cheers
  Michael

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lirc 0.9.4c-9
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 22 10:28:49 2017
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lirc
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (4 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-18T19:07:44.10
  mtime.conffile..etc.lirc.lircd.conf: 2017-04-18T18:58:35.039496

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1685394] Re: hp media center remote not responding

[Alec Leamas]

Are you actually using lirc here i. e., have you configured kodi to use lirc? 
If not, this bug should be assigned to the kernel. The ir-keytable stuff is 
actually part of the kernel...

If you indeed are using lirc, as a starter: what does irw(1) tell you
when pushing a button  or two on the remote?

> If I remove lirc, some of the keys work after a replug of the
receiver.

The keys which work obviously uses the kernel decoding, independent of
lirc

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1685394

Title:
  hp media center remote not responding

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  The hp mce remote was working fine with kodi running on Ubuntu 16.10. After 
upgrade to 17.04, 
  the remote does not respond anymore. Loads the driver, dmesg looks ok. I 
managed to get it to respond a couple of times after a reboot by unpluging an 
plugging back in. 
  ir-keytable gives:

  Found /sys/class/rc/rc0/ (/dev/input/event9) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo 
mce_kbd rc-6 sharp xmp 
Enabled protocols: lirc rc-6 
Name: Media Center Ed. eHome Infrared 
bus: 3, vendor/product: 1934:5168, version: 0x0001
Repeat delay = 500 ms, repeat period = 125 ms
  I suspect this is a bug because it happenee just after the upgrade
  any help would be greatly appreciated
  cheers
  Michael

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lirc 0.9.4c-9
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 22 10:28:49 2017
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lirc
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (4 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-18T19:07:44.10
  mtime.conffile..etc.lirc.lircd.conf: 2017-04-18T18:58:35.039496

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1681838] Re: IR pilot is not working after kernel change from 3.13 to 4.4

[Alec Leamas]

For the sake of order, this bug should be re-assigned to the kernel
package instead of the user-space lirc package.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1681838

Title:
  IR pilot is not working after kernel change from 3.13 to 4.4

Status in linux package in Ubuntu:
  Confirmed
Status in lirc package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04
  linux-image-4.4.0-72-generic

  I'm using custom IR receiver with CIR header in my ASRock MoBo.
  This one IR receiver serves 3 devices - HTPC, TV and amplifier.

  Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped 
to work with HTPC.
  mode2 app shows, that IR header is receiving something, but there is 
something wrong.

  Example pulse-pause timings for 3.13 kernel are:
  space 2949
  pulse 39
  space 1157
  pulse 39
  space 1159
  pulse 39
  Example pulse-pause timings for 4.4 kernel are:
  space 16777176
  pulse 1
  space 16777176
  pulse 1
  space 16777176
  pulse 1

  for this same button.

  Maybe I'm not only one which wants still to use lirc_sir
  Please, help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lirc 0.9.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-116-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Tue Apr 11 11:55:14 2017
  SourcePackage: lirc
  UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756
  mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289
  --- 
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dugi  10933 F pulseaudio
   /dev/snd/controlC0:  dugi  10933 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: lirc 0.9.0-0ubuntu5
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic 
root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro 
video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf 
nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: lirc_sir
  Tags:  trusty staging trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 07/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.60
  dmi.board.name: FM2A75 Pro4-M
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386
  mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289
  --- 
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  Package: lirc 0.9.0-0ubuntu5
  PackageArchitecture: amd64
  Tags:  trusty
  Uname: Linux 4.11.0-041100rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 206495] Re: hvr-1100 is not configured properly

[Alec Leamas]

This bug is 8 years old, The primary culprits hald and hardware.conf are
gone and this bugf shouldI MHO be closed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/206495

Title:
  hvr-1100 is not configured properly

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  Hello, the hardware.conf file that is created for this remote control is not 
right. But the one used for the "Hauppauge Nova-T 500" is fine. 
  The remote control works fine if I configure lirc with the  "Hauppauge Nova-T 
500" remote and if I change the lircd.conf file to 
/usr/share/lirc/remotes/hauppauge/lircd.conf.hauppauge. 
  Thanks

  ubuntu 8.10

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 358817] Re: Add irexec, irxevent, ... to session

[Alec Leamas]

After a second thought I think this is wontfix. Setting up lirc is a
complex task, and enabling a service in the standard session GUI tools
is a small problem compared to other. Also, the 'parse .lircrc'approach
just don't work since applications can store them anywhere. And does so.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/358817

Title:
  Add irexec,irxevent,... to session

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  irexec (from package lirc) and irxevent (from package lirc-x) are
  useful tools that enable lirc users execute programs (irexec) or
  generate keystrokes (irxevent). For these to work, they have to be
  added to the session (go to System - Preferences - Sessions - Startup
  Programs and add "irexec -d" and "irxevent -d", but that is not very
  user-friendly and many people don't seem to get this. If you google
  for irexec, you will see that many people instead try to hack it into
  their /etc/init.d/lirc, which is plain wrong because these tools have
  to run inside the user context.

  I propose that the packages lirc and lirc-x should automatically add
  such tools (I name irexec and irxevent here because these are the ones
  I use, but there could be more) to the sessions of all users.

  A possible drawback: running all these tools when the user has only
  configured some of them inside his lircrc wastes memory. We could
  either make this somehow configurable (but I don't know how), or parse
  /etc/lirc/lircrc and ~/.lircrc for the required programs and only add
  those to the session. /etc/init.d/lirc could reparse the files
  whenever neccessary, so when the user edits his .lircrc and adds e.g.
  irexec, the init script could modify the user's session to run irexec
  too.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 934023] Re: mceusb remote stops working after lucid->precise upgrade

[Alec Leamas]

Setting Incomplete  to let bug expire. Please change if you don't wan
bug to expire-

** Changed in: lirc (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/934023

Title:
  mceusb remote stops working after lucid->precise upgrade

Status in lirc package in Ubuntu:
  Incomplete
Status in mythbuntu-lirc-generator package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  I had a previously functioning mceusb remote with lucid.  After the
  precise upgrade it stopped working.

  It appears that this is caused by button names that changed with the
  upgrade.  The /etc/lirc/lircd.conf sources the lircd.conf included
  with the package so these button names in the lircrc may not be
  consistent.

   If I re-run mythbuntu-lirc-generator after the upgrade, my media
  applications begin working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lirc 0.9.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
  Uname: Linux 3.2.0-16-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  Date: Fri Feb 17 02:10:52 2012
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lirc
  UpgradeStatus: Upgraded to precise on 2012-02-17 (0 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2009-10-13T09:51:29.209483
  mtime.conffile..etc.lirc.lircd.conf: 2009-12-03T21:18:43.198785

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 358817] Re: Add irexec, irxevent, ... to session

[Alec Leamas]

So,I'm not allowed set it to wontfix.  Setting Incomplete, please change
you don't want  this bug to be closed.

** Changed in: lirc (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/358817

Title:
  Add irexec,irxevent,... to session

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  irexec (from package lirc) and irxevent (from package lirc-x) are
  useful tools that enable lirc users execute programs (irexec) or
  generate keystrokes (irxevent). For these to work, they have to be
  added to the session (go to System - Preferences - Sessions - Startup
  Programs and add "irexec -d" and "irxevent -d", but that is not very
  user-friendly and many people don't seem to get this. If you google
  for irexec, you will see that many people instead try to hack it into
  their /etc/init.d/lirc, which is plain wrong because these tools have
  to run inside the user context.

  I propose that the packages lirc and lirc-x should automatically add
  such tools (I name irexec and irxevent here because these are the ones
  I use, but there could be more) to the sessions of all users.

  A possible drawback: running all these tools when the user has only
  configured some of them inside his lircrc wastes memory. We could
  either make this somehow configurable (but I don't know how), or parse
  /etc/lirc/lircrc and ~/.lircrc for the required programs and only add
  those to the session. /etc/init.d/lirc could reparse the files
  whenever neccessary, so when the user edits his .lircrc and adds e.g.
  irexec, the init script could modify the user's session to run irexec
  too.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM

[Alec Leamas]

Now, suspend-resume is about the kernel, the extra modules secion. But
which iof them? Just don't know.

** Package changed: lirc (Ubuntu) => linux-lts-xenial (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/359356

Title:
  USB device attached to different ttyUSB after resume from suspend to
  RAM

Status in linux-lts-xenial package in Ubuntu:
  Confirmed

Bug description:
  Update: As for Xubuntu 11.04 at least, please read comment #13

  OS: 8.10

  USB device is attached to /dev/ttyUSB0 when I plug it in USB port. But
  when I suspend to RAM and resume, it gets attached to /dev/ttyUSB1.
  Consequently, the daemon configured using /dev/ttyUSB0 does not work
  after resume. I would expect the device to be attached to the same
  ttyUSB before and after.

  Details of the device (from output of lsusb -v):

  Bus 003 Device 010: ID 0403:6001 Future Technology Devices International, Ltd 
FT232 USB-Serial (UART) IC
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.00
    bDeviceClass0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 8
    idVendor   0x0403 Future Technology Devices International, Ltd
    idProduct  0x6001 FT232 USB-Serial (UART) IC
    bcdDevice6.00
    iManufacturer   1 FTDI
    iProduct2 FT232R USB UART
    iSerial 3 A5001qxI
    bNumConfigurations  1
    Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   32
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0
  bmAttributes 0xa0
    (Bus Powered)
    Remote Wakeup
  MaxPower   90mA
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber0
    bAlternateSetting   0
    bNumEndpoints   2
    bInterfaceClass   255 Vendor Specific Class
    bInterfaceSubClass255 Vendor Specific Subclass
    bInterfaceProtocol255 Vendor Specific Protocol
    iInterface  2 FT232R USB UART
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes2
    Transfer TypeBulk
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0040  1x 64 bytes
  bInterval   0
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x02  EP 2 OUT
  bmAttributes2
    Transfer TypeBulk
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0040  1x 64 bytes
  bInterval   0
  Device Status: 0x
    (Bus Powered)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/359356/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM

[Alec Leamas]

Re-assigning to kernel - this is teh way to clarify whether it's a bug
or just documented behaviour.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/359356

Title:
  USB device attached to different ttyUSB after resume from suspend to
  RAM

Status in linux-lts-xenial package in Ubuntu:
  Confirmed

Bug description:
  Update: As for Xubuntu 11.04 at least, please read comment #13

  OS: 8.10

  USB device is attached to /dev/ttyUSB0 when I plug it in USB port. But
  when I suspend to RAM and resume, it gets attached to /dev/ttyUSB1.
  Consequently, the daemon configured using /dev/ttyUSB0 does not work
  after resume. I would expect the device to be attached to the same
  ttyUSB before and after.

  Details of the device (from output of lsusb -v):

  Bus 003 Device 010: ID 0403:6001 Future Technology Devices International, Ltd 
FT232 USB-Serial (UART) IC
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.00
    bDeviceClass0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 8
    idVendor   0x0403 Future Technology Devices International, Ltd
    idProduct  0x6001 FT232 USB-Serial (UART) IC
    bcdDevice6.00
    iManufacturer   1 FTDI
    iProduct2 FT232R USB UART
    iSerial 3 A5001qxI
    bNumConfigurations  1
    Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   32
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0
  bmAttributes 0xa0
    (Bus Powered)
    Remote Wakeup
  MaxPower   90mA
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber0
    bAlternateSetting   0
    bNumEndpoints   2
    bInterfaceClass   255 Vendor Specific Class
    bInterfaceSubClass255 Vendor Specific Subclass
    bInterfaceProtocol255 Vendor Specific Protocol
    iInterface  2 FT232R USB UART
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes2
    Transfer TypeBulk
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0040  1x 64 bytes
  bInterval   0
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x02  EP 2 OUT
  bmAttributes2
    Transfer TypeBulk
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0040  1x 64 bytes
  bInterval   0
  Device Status: 0x
    (Bus Powered)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/359356/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 204769] Re: /etc/init.d/lirc requires TRANSMITTER_DEVICE to be set in hardware.conf

[Alec Leamas]

Closing as fixed, since release 0.9.4c does not use sysV scripts or
hardware.conf.

** Changed in: lirc (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/204769

Title:
  /etc/init.d/lirc requires TRANSMITTER_DEVICE to be set in
  hardware.conf

Status in lirc package in Ubuntu:
  Fix Released

Bug description:
  Currently /etc/init.d/lirc requires TRANSMITTER_DEVICE to be set by
  hand (or during debconf) to load the transmitter's daemon.
  Additionally, if a remote is being used in conjunction with a
  transmitter, REMOTE_DEVICE needs to be set as well to have both
  daemons load properly.

  There are two approaches to fix this problem:

  1. Modify debconf for lirc. 
  TRANSMITTER_DEVICE and REMOTE_DEVICE will vary depending on the order in 
which the modules are loaded. Currently the modules are loaded Remote, 
Transmitter (from /etc/init.d/lirc). If this remains the case, REMOTE_DEVICE 
should be /dev/lirc0 (if being used) while TRANSMITTER_DEVICE should be 
/dev/lirc0 (if no remote is being used) or /dev/lirc1 (if a remote is being 
used). 

  2. Modify /etc/init.d/lirc
  The same logic described above can be used to "guess" the values of 
REMOTE_DEVICE and TRANSMITTER_DEVICE if they are not set. This may be the 
easier fix to apply because it only would require some additional bash 
scripting.

  Anybody with a recommendation on "best practices" here? I will gladly
  modify the init script and post a diff if I know it is going to be
  used.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 505705] Re: irexec isn't started automatically on existing installs

[Alec Leamas]

As for the lirc part, the last 0.9.4 release solves this since the lircd
output socket is created at an very early point in the boot sequence.
lircd is started using socket activation when irexec or some otther
client connects to the socket. So, no race is possible.

IMHO, mysql should do the same, and might indeed have so already. Don't
know, closing as fixed.

** Changed in: lirc (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/505705

Title:
  irexec isn't started automatically on existing installs

Status in Mythbuntu:
  Expired
Status in lirc package in Ubuntu:
  Fix Released

Bug description:
  Irexec does not start with the lirc service on 9.10 (Ubuntu+MythTV,
  not Mythbuntu). In my testing, it seems that the following line might
  be the issue.

  (from /etc/init.d/lirc)
  start-stop-daemon --start --quiet --oknodo --exec /usr/bin/irexec -- -d 
/etc/lirc/lircrc < /dev/null

  I've compared my two systems and there doesn't seem to be that big of
  difference (one is Mythbuntu, the other is Ubuntu+MythTV). The
  Mythbuntu system works correctly where the Ubuntu+MythTV does not.

  /etc/lirc/lircrc does not exist on either system.

  If I edit the line to just

  start-stop-daemon --start --quiet --oknodo --exec /usr/bin/irexec --

  Then it does work, but it stays in the terminal and thus is not really
  a viable option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/505705/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 786743] Re: Lack of support for Multiple receivers

[Alec Leamas]

At second thogt this is a mythbuntu issue, re-assigning.

Please note that that from 0.9.4 lirc no longer supports hardware.conf.
In short, each lircd instance is configured as a systemd service. There
is also a ren lirc_options.conf file which defines default values for
command line options. See upstream documentation at http://lirc.org.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/786743

Title:
  Lack of support for Multiple receivers

Status in mythbuntu-common package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: lirc

  The lirc configuration file /etc/lirc/hardware.conf, /etc/init.d/lirc
  and the Mythbuntu Control Center only supports the use of a single
  receiver and a single transmitter. There are valid cases for using
  multiple receivers, for example, the Imon Knob, which only provides
  volume up, volume down and mute depending on the revision of the
  hardware, plus another IR remote. If the configuration files were able
  to support multiple receivers then Mythbuntu Control Center should be
  able to support it too.

  Currently manually editing the lirc configurations files is required
  to get multiple lirc receivers functional.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mythbuntu-common/+bug/786743/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 786743] Re: Lack of support for Multiple receivers

[Alec Leamas]

This do belong to mythbuntu since it's about  the automatic generation
of config files. Still unsure which of the mythbuntu packages, sorry.

** Package changed: lirc (Ubuntu) => mythbuntu-common (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/786743

Title:
  Lack of support for Multiple receivers

Status in mythbuntu-common package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: lirc

  The lirc configuration file /etc/lirc/hardware.conf, /etc/init.d/lirc
  and the Mythbuntu Control Center only supports the use of a single
  receiver and a single transmitter. There are valid cases for using
  multiple receivers, for example, the Imon Knob, which only provides
  volume up, volume down and mute depending on the revision of the
  hardware, plus another IR remote. If the configuration files were able
  to support multiple receivers then Mythbuntu Control Center should be
  able to support it too.

  Currently manually editing the lirc configurations files is required
  to get multiple lirc receivers functional.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mythbuntu-common/+bug/786743/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 517743] Re: Check the TRANSMITTER logic for errors w/ lirc-mceusb

[Alec Leamas]

The last release 0.9.4c dos not support hardware.conf anymore, so this
is bug is obsoleted. Closing as "FixReleased", short of better options.

** Changed in: lirc (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/517743

Title:
  Check the TRANSMITTER logic for errors w/ lirc-mceusb

Status in lirc package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: lirc

   do you know who maintains the lirc packages for ubuntu?
   it's a ~mythbuntu team effort to maintain them, but usually ends up 
being me when i find time
   aha
   can you *please* add some informative text in hardware.conf and/or 
whatever twiddles it to explain to users when they actually need that separate 
TRANSMITTER thing set?
   in what scenario?
   it's generally dynamically built 
   there's a disgustingly huge volume of questions about screwed up 
hardware.conf files, where people are setting up two lircd instances when a 
single one would do -- i.e., when using lirc_mceusb or lirc_zilog
   it's quite possible the logic is building it wrong
   seems a lot of people are hand-editing it too
   well if that's the case, then yeah some comments in there will 
hopefully fix the problem for them

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 334144] Re: [Intrepid AMD64] lirc daemon fails to load at startup

[Alec Leamas]

Anyway, we believe this is fixed in last update lirc-0.9.4c:
  - The udev rule restarting lircd when /dev/lirc0 is created is removed.
  - 0.9.4 sports a much simpler systemd setup, which certainly can have 
problems but not this.


Closing


lirc (0.9.4b-0.1) experimental; urgency=medium

  * Non-maintainer upload.
  * First shot on major upstream updates.
- Re-packaged from scratch based on new dh primitives.
- Thanks for help on debian-mentors!
  * New upstream release 0.9.4
- Release 0.9.1 .. 0.9.3 was never packaged.
- Old 'lirc' service split into separate systemd services:
  lircd.service, lircmd.service and irexec.service.
- Remote definitions moved out of lirc to new project
  lirc-remotes; affects large number of LP issues.
- Builds also on FreeBSD 10.3.
- Fixes "Not updated to last version" (Closes: #777199),
  LP: #1443590.
- Fixes "Default device for mode2 is /dev/lirc" (Closes: #702140).
- Fixes "/var/run/lirc contents disappear..." (Closes: #676343).
- Fixes "lircrcd segfaults" (Closes: #780062).
- Fixes "'/etc/init.d/lirc restart' is broken" (Closes: #782091).
- Fixes "Prompting due to modified conffiles..." (Closes: #655969).
- Fixes "LIRC installs bad udev rule" (Closes: #804397),
  users depending on this rule will need to explicitly start lircd.
- Fixes "lirc init script can create circular symlinks", LP: #698007.
- Fixes "Update Uploaders List (Closes: #762554).
- Fixes "Please switch to libftdi1" (Closes:  #810370).
- Fixes LP: #153457 "iguanaIR support not functional".
- Fixes LP: #460027 "using lirc init script restart function fails
  sometimes".
- Fixes LP: #499588 "lirc udev rule causes unreliable startup".
- Fixes LP: #567519 "lircd(8) mentions non-existent
  /dev/input/uinput".
- Fixes LP: #1029604 "mce remote doesn't work due to out of date
  lircd.conf.devinput".
- Fixes LP: #1312287 "lircd start problem".
  * The built-in irman support is moved to the lirc-drv-irman package.
  * Revised package structure: keep old liblircclient0 (renamed to
liblirc-client0). Adding new packages liblirc0, liblirc-dev and
lirc-doc. Former liblircclient-dev merged into new liblirc-dev.
  * Don't overwrite existing lircd.conf file.
  * Ship sysV scripts from the svn tree [Stefan Lippers-Hollmann]
  * Add handling of obsolete 0.9.0 udev rule restarting lircd
  * Old lircd output socket link /dev/lirc dropped. Use
/var/run/lirc/lircd.
  * Updated copyright
  * Update compiler flags: -Wl,as-needed + hardening
[Stefan Lippers-Hollmann]
  * Avoid negative architecture deps like [!hurd] (Closes: #634807)
[Stefan Lippers-Hollmann]
  * Add patch 0007-tools-remove-configs-symlink.patch + explicit link
to walk around #801719 (dh_python3 shortcomings).
  * Last parts of libirman dependencies removed.
  * Changing Vcs-* headers to point to upstream packaging branch.
  * Fixes existing large number of upgrade bugs.
  * Enhance hardening flags.
  * Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg
therein.
  * Tested (build-wise) on stretch and sid.

 -- Alec Leamas  <leamas.a...@gmail.com>  Thu, 26 May 2016 11:14:25
+0100


** Changed in: lirc (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/334144

Title:
  [Intrepid AMD64] lirc daemon fails to load at startup

Status in lirc package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: lirc

  I use Intrepid AMD64, and it so happens that lirc always fails to load when 
the system boots.
  The weird thing is, that when I use the "sudo /etc/init.d/lirc restart" 
command afterwards, lirc loads properly.

  The nasty side effect is that I always have to reload lirc by hand
  before I can use my media center remote.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 330203] Re: Add Winfast 2000XP ir remote settings to lirc

[Alec Leamas]

The last version of lirc 0.9.4c sort of resolves this problem by not
bundling the remote definitions. From 0.9.2+, the remote definitions
lives at http://sf.net/p/lirc-remotes. Closing bug as fixed.

lirc (0.9.4b-0.1) experimental; urgency=medium

  * Non-maintainer upload.
  * First shot on major upstream updates.
- Re-packaged from scratch based on new dh primitives.
- Thanks for help on debian-mentors!
  * New upstream release 0.9.4
- Release 0.9.1 .. 0.9.3 was never packaged.
- Old 'lirc' service split into separate systemd services:
  lircd.service, lircmd.service and irexec.service.
- Remote definitions moved out of lirc to new project
  lirc-remotes; affects large number of LP issues.
- Builds also on FreeBSD 10.3.
- Fixes "Not updated to last version" (Closes: #777199),
  LP: #1443590.
- Fixes "Default device for mode2 is /dev/lirc" (Closes: #702140).
- Fixes "/var/run/lirc contents disappear..." (Closes: #676343).
- Fixes "lircrcd segfaults" (Closes: #780062).
- Fixes "'/etc/init.d/lirc restart' is broken" (Closes: #782091).
- Fixes "Prompting due to modified conffiles..." (Closes: #655969).
- Fixes "LIRC installs bad udev rule" (Closes: #804397),
  users depending on this rule will need to explicitly start lircd.
- Fixes "lirc init script can create circular symlinks", LP: #698007.
- Fixes "Update Uploaders List (Closes: #762554).
- Fixes "Please switch to libftdi1" (Closes:  #810370).
- Fixes LP: #153457 "iguanaIR support not functional".
- Fixes LP: #460027 "using lirc init script restart function fails
  sometimes".
- Fixes LP: #499588 "lirc udev rule causes unreliable startup".
- Fixes LP: #567519 "lircd(8) mentions non-existent
  /dev/input/uinput".
- Fixes LP: #1029604 "mce remote doesn't work due to out of date
  lircd.conf.devinput".
- Fixes LP: #1312287 "lircd start problem".
  * The built-in irman support is moved to the lirc-drv-irman package.
  * Revised package structure: keep old liblircclient0 (renamed to
liblirc-client0). Adding new packages liblirc0, liblirc-dev and
lirc-doc. Former liblircclient-dev merged into new liblirc-dev.
  * Don't overwrite existing lircd.conf file.
  * Ship sysV scripts from the svn tree [Stefan Lippers-Hollmann]
  * Add handling of obsolete 0.9.0 udev rule restarting lircd
  * Old lircd output socket link /dev/lirc dropped. Use
/var/run/lirc/lircd.
  * Updated copyright
  * Update compiler flags: -Wl,as-needed + hardening
[Stefan Lippers-Hollmann]
  * Avoid negative architecture deps like [!hurd] (Closes: #634807)
[Stefan Lippers-Hollmann]
  * Add patch 0007-tools-remove-configs-symlink.patch + explicit link
to walk around #801719 (dh_python3 shortcomings).
  * Last parts of libirman dependencies removed.
  * Changing Vcs-* headers to point to upstream packaging branch.
  * Fixes existing large number of upgrade bugs.
  * Enhance hardening flags.
  * Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg
therein.
  * Tested (build-wise) on stretch and sid.

 -- Alec Leamas  <leamas.a...@gmail.com>  Thu, 26 May 2016 11:14:25
+0100


** Changed in: lirc (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/330203

Title:
  Add Winfast 2000XP ir remote settings to lirc

Status in lirc package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: lirc

  I would like to submit the settings for a Winfast 2000XP infrared remote, so 
they will be included in the next version of lirc. Here they are:
  Remote is marked LEADTEK Y04G0044
  lircd.conf is attached.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 913527] Re: Remote control "Rosewill RHRC-11001" doesn't work

[Alec Leamas]

At a second thought; Since it's now supported, let's close bug

** Changed in: lirc (Ubuntu)
   Status: Incomplete => Fix Committed

** Changed in: lirc (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/913527

Title:
  Remote control "Rosewill RHRC-11001" doesn't work

Status in lirc package in Ubuntu:
  Fix Released

Bug description:
  I have Rosewill RHRC-11001 IR:
  http://www.newegg.com/Product/Product.aspx?Item=N82E16880101007

  I run Ubuntu 10.10.
  I installed the latest avaiable lirc version 0.8.7~pre3 from official 
repository. My IR doesn't work.

  sudo mode2
  mode2: could not get file information for /dev/lirc
  mode2: default_init(): No such file or directory

  I tried to add my remote as it described in following article
  https://help.ubuntu.com/community/LIRC#Adding_support_for_more_remotes

  However it didn't resolve the problem.

  lsusb reports my IR as
  Bus 004 Device 002: ID 147a:e042 Formosa Industrial Computing, Inc.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 238032] Re: lircd doesn't find dvico usb IR remote device correctly (expects /dev/lirc)

[Alec Leamas]

expiring manually

** Changed in: lirc (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/238032

Title:
  lircd doesn't find dvico usb IR remote device correctly (expects
  /dev/lirc)

Status in Mythbuntu:
  Expired
Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: lirc

  A while back my DVICO usb (sometime during gutsy) remote stopped
  working, and I have only got around to fixing it on my upgraded hardy
  system.

  It appears that the dvico usb remote creates a device on
  /dev/usb/hiddev1, but lircd expects the remote to be on /dev/lirc ,
  and as a result I could no longer control my mythbuntu installation
  with the remote control.

  After a bit of googling ( http://gentoo-wiki.com/HOWTO_LIRC
  #DVICO_FusionHDTV_DVB-T_Plus_IR_Remote ) and 'cat /dev/usb/hiddev1'
  revealed the real address of the remote. In order to work around this
  problem I edited /etc/lirc/hardware.conf and replaced REMOTE_DEVICE=""
  with REMOTE_DEVICE="/dev/usb/hiddev1".

  I've only got irw to work at this stage, but getting the media centre
  control back shouldn't be too hard from here in.

  I'm not sure what files may be useful in diagnosing this problem, so
  please let me know what would help and I can add it here.

  (dmesg output from connection)
  [57662.280194] usb 6-2: new low speed USB device using ohci_hcd and address 4
  [57662.528453] usb 6-2: configuration #1 chosen from 1 choice
  [57662.499406] hiddev97hidraw3: USB HID v1.10 Device [DVICO DVICO USB HID 
Remocon V5.00] on usb-:00:13.4-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/238032/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 663651] Re: Streamzap remote control not operating correctly

[Alec Leamas]

Expiring

** Changed in: lirc (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/663651

Title:
  Streamzap remote control not operating correctly

Status in linux package in Ubuntu:
  Invalid
Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: lirc

  After upgrading to Ubuntu 10.10 my Streamzap IR remote control does not 
operate correctly.
  Pressing the direction buttons (Up, Down, Left and Right) generated 2 presses 
to the MythTV application.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 567512] Re: uinput broken for at least Mac mini

[Alec Leamas]

If/when you do, please file a new bug. This one is too old and
cluttered. Closing, as fixed in 0.9.4c

lirc (0.9.4b-0.1) experimental; urgency=medium

  * Non-maintainer upload.
  * First shot on major upstream updates.
- Re-packaged from scratch based on new dh primitives.
- Thanks for help on debian-mentors!
  * New upstream release 0.9.4
- Release 0.9.1 .. 0.9.3 was never packaged.
- Old 'lirc' service split into separate systemd services:
  lircd.service, lircmd.service and irexec.service.
- Remote definitions moved out of lirc to new project
  lirc-remotes; affects large number of LP issues.
- Builds also on FreeBSD 10.3.
- Fixes "Not updated to last version" (Closes: #777199),
  LP: #1443590.
- Fixes "Default device for mode2 is /dev/lirc" (Closes: #702140).
- Fixes "/var/run/lirc contents disappear..." (Closes: #676343).
- Fixes "lircrcd segfaults" (Closes: #780062).
- Fixes "'/etc/init.d/lirc restart' is broken" (Closes: #782091).
- Fixes "Prompting due to modified conffiles..." (Closes: #655969).
- Fixes "LIRC installs bad udev rule" (Closes: #804397),
  users depending on this rule will need to explicitly start lircd.
- Fixes "lirc init script can create circular symlinks", LP: #698007.
- Fixes "Update Uploaders List (Closes: #762554).
- Fixes "Please switch to libftdi1" (Closes:  #810370).
- Fixes LP: #153457 "iguanaIR support not functional".
- Fixes LP: #460027 "using lirc init script restart function fails
  sometimes".
- Fixes LP: #499588 "lirc udev rule causes unreliable startup".
- Fixes LP: #567519 "lircd(8) mentions non-existent
  /dev/input/uinput".
- Fixes LP: #1029604 "mce remote doesn't work due to out of date
  lircd.conf.devinput".
- Fixes LP: #1312287 "lircd start problem".
  * The built-in irman support is moved to the lirc-drv-irman package.
  * Revised package structure: keep old liblircclient0 (renamed to
liblirc-client0). Adding new packages liblirc0, liblirc-dev and
lirc-doc. Former liblircclient-dev merged into new liblirc-dev.
  * Don't overwrite existing lircd.conf file.
  * Ship sysV scripts from the svn tree [Stefan Lippers-Hollmann]
  * Add handling of obsolete 0.9.0 udev rule restarting lircd
  * Old lircd output socket link /dev/lirc dropped. Use
/var/run/lirc/lircd.
  * Updated copyright
  * Update compiler flags: -Wl,as-needed + hardening
[Stefan Lippers-Hollmann]
  * Avoid negative architecture deps like [!hurd] (Closes: #634807)
[Stefan Lippers-Hollmann]
  * Add patch 0007-tools-remove-configs-symlink.patch + explicit link
to walk around #801719 (dh_python3 shortcomings).
  * Last parts of libirman dependencies removed.
  * Changing Vcs-* headers to point to upstream packaging branch.
  * Fixes existing large number of upgrade bugs.
  * Enhance hardening flags.
  * Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg
therein.
  * Tested (build-wise) on stretch and sid.

 -- Alec Leamas  <leamas.a...@gmail.com>  Thu, 26 May 2016 11:14:25
+0100

** Changed in: lirc (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/567512

Title:
  uinput broken for at least Mac mini

Status in lirc package in Ubuntu:
  Fix Released
Status in lirc source package in Lucid:
  Won't Fix
Status in lirc source package in Maverick:
  Won't Fix

Bug description:
  I have patched and tested the latest lirc packages from lucid. I have
  uploaded a bzr branch to Launchpad and requested a merge to lucid-
  proposed. The debdiff is also attached.

  For the needs of the SRU:

  - Impact of this bug: This bug renders the "--uinput" of lirc useless.
  This options allows remote controls to input commands like key strokes
  (as you would with a multimedia keyboard with "play", "next/previous",
  "volume up/down", etc buttons). This is obviously a very simple and
  attractive way to use a remote control with Ubuntu, and is recommended
  in many tutorials (including on help.ubuntu.com). Currently, in lucid,
  the buttons pressed on the remote have no effect (until the lircd
  daemon is stopped or restarted).

  - Nominating for SRU, fulfills: (1) have an obviously safe patch (it
  only concerns the --uinput which is currently non-functional, and is
  tested by upstream and other distros) and (2) affect an application
  rather than critical infrastructure packages

  - My proposed patch simply includes a patch from upstream (git commit
  d987ce9c68239f637dddb9de9f9668f6e8f9fc1d) to fix this problem. It is
  included in the 0.8.7~pre3-0ubuntu1 version in maverick, which works
  fine.

  

[Desktop-packages] [Bug 626633] Re: Missing MCE remote from default config file

[Alec Leamas]

The patch is for kernel code, reassigning.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/626633

Title:
  Missing MCE remote from default config file

Status in linux-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: lirc

  Ubuntu release 10.04
  Lirc version 0.8.6

  There is missing support in the default lirc_mceusb.c for the mce
  remote with the following id: ID 147a:e03e Formosa Industrial
  Computing, Inc.

  The following needs to be in the code:

  static struct usb_device_id mceusb_dev_table[] = {

/* Formosa Industrial Computing, Inc. */
{ USB_DEVICE(VENDOR_FORMOSA, 0xe03e) },

  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/626633/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 597955] Re: LIRC not listed remote: Mediagate MG-IR01BK, Remote model #:RC126, Receiver model #:IR605.

[Alec Leamas]

Any news on this? Otherwise, without further input, I suggest this is
closed.

** Changed in: lirc (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/597955

Title:
  LIRC not listed remote: Mediagate MG-IR01BK, Remote model #:RC126,
  Receiver model #:IR605.

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  http://www.mediagateusa.com/MG-IR01BK.html

  Distro: Ubuntu 9.1 Karmic.
  Kernel Linux 2.6.31-14-generic
  GNOME 2.28.1

  The product package is  labelled : MG-IR01BK.  While the remote model
  # is:RC126 and the receiver model #:IR605.   Here's the lsusb
  vend:prod 147a:e03e. But no keymap.

  At  $30CAD w/ receiver I imagine it would be pretty popular as it is
  cost effective remote.  It also has a Media Center button.  Thanks.

  Receiver is in the code as Formosa IR605. I was following this set of
  instruction to no avail where I spotted the model number of the
  receiver.

  http://www.fscker.ca/rc/2010/04/27/mediagate-mg-ir01bk-and-
  ubuntu-9-10/

  lirc_mceusb.c
  static struct usb_device_id mceusb_dev_table[] = {
  ...
/* Formosa Industrial Computing AIM IR605/A */
{ USB_DEVICE(VENDOR_FORMOSA, 0xe03c) },
  
  }

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 626633] Re: Missing MCE remote from default config file

[Alec Leamas]

Possibly , wrog version

** Package changed: lirc (Ubuntu) => linux-lts-utopic (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/626633

Title:
  Missing MCE remote from default config file

Status in linux-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: lirc

  Ubuntu release 10.04
  Lirc version 0.8.6

  There is missing support in the default lirc_mceusb.c for the mce
  remote with the following id: ID 147a:e03e Formosa Industrial
  Computing, Inc.

  The following needs to be in the code:

  static struct usb_device_id mceusb_dev_table[] = {

/* Formosa Industrial Computing, Inc. */
{ USB_DEVICE(VENDOR_FORMOSA, 0xe03e) },

  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/626633/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 150480] Re: lirc needs an upstart init script

[Alec Leamas]

This  bug is old. The last release 0.9.4c addresses the issues here with
a new systemd setup. It also ships updated sysV scripts, split into
three services. Closiing


lirc (0.9.4b-0.1) experimental; urgency=medium

  * Non-maintainer upload.
  * First shot on major upstream updates.
- Re-packaged from scratch based on new dh primitives.
- Thanks for help on debian-mentors!
  * New upstream release 0.9.4
- Release 0.9.1 .. 0.9.3 was never packaged.
- Old 'lirc' service split into separate systemd services:
  lircd.service, lircmd.service and irexec.service.
- Remote definitions moved out of lirc to new project
  lirc-remotes; affects large number of LP issues.
- Builds also on FreeBSD 10.3.
- Fixes "Not updated to last version" (Closes: #777199),
  LP: #1443590.
- Fixes "Default device for mode2 is /dev/lirc" (Closes: #702140).
- Fixes "/var/run/lirc contents disappear..." (Closes: #676343).
- Fixes "lircrcd segfaults" (Closes: #780062).
- Fixes "'/etc/init.d/lirc restart' is broken" (Closes: #782091).
- Fixes "Prompting due to modified conffiles..." (Closes: #655969).
- Fixes "LIRC installs bad udev rule" (Closes: #804397),
  users depending on this rule will need to explicitly start lircd.
- Fixes "lirc init script can create circular symlinks", LP: #698007.
- Fixes "Update Uploaders List (Closes: #762554).
- Fixes "Please switch to libftdi1" (Closes:  #810370).
- Fixes LP: #153457 "iguanaIR support not functional".
- Fixes LP: #460027 "using lirc init script restart function fails
  sometimes".
- Fixes LP: #499588 "lirc udev rule causes unreliable startup".
- Fixes LP: #567519 "lircd(8) mentions non-existent
  /dev/input/uinput".
- Fixes LP: #1029604 "mce remote doesn't work due to out of date
  lircd.conf.devinput".
- Fixes LP: #1312287 "lircd start problem".
  * The built-in irman support is moved to the lirc-drv-irman package.
  * Revised package structure: keep old liblircclient0 (renamed to
liblirc-client0). Adding new packages liblirc0, liblirc-dev and
lirc-doc. Former liblircclient-dev merged into new liblirc-dev.
  * Don't overwrite existing lircd.conf file.
  * Ship sysV scripts from the svn tree [Stefan Lippers-Hollmann]
  * Add handling of obsolete 0.9.0 udev rule restarting lircd
  * Old lircd output socket link /dev/lirc dropped. Use
/var/run/lirc/lircd.
  * Updated copyright
  * Update compiler flags: -Wl,as-needed + hardening
[Stefan Lippers-Hollmann]
  * Avoid negative architecture deps like [!hurd] (Closes: #634807)
[Stefan Lippers-Hollmann]
  * Add patch 0007-tools-remove-configs-symlink.patch + explicit link
to walk around #801719 (dh_python3 shortcomings).
  * Last parts of libirman dependencies removed.
  * Changing Vcs-* headers to point to upstream packaging branch.
  * Fixes existing large number of upgrade bugs.
  * Enhance hardening flags.
  * Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg
therein.
  * Tested (build-wise) on stretch and sid.

 -- Alec Leamas  <leamas.a...@gmail.com>  Thu, 26 May 2016 11:14:25
+0100

lirc (0.9.0~pre1-1.2) unstable; urgency=medium

** Changed in: lirc (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/150480

Title:
  lirc needs an upstart init script

Status in lirc package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: lirc

  lirc should probably be started before gdm so that you can use the
  autologin feature of gdm and get a working lirc. Right now I have to
  restart gdm or logout/login to make lirc work on my dedicated mythtv
  machine.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 787735] Re: Snapstream Firefly non-functional

[Alec Leamas]

This bug is old.

The loast release (0.9.4c - zesty) deals with this. Actually the default
configuration  (--driver devinput --device auto) should cover the
devinput case. Here is also new documentation on how to setup the
default driver (also available at http://lirc.org/html/configuration-
guide.html.  Clsoing.

lirc (0.9.4b-0.1) experimental; urgency=medium

  * Non-maintainer upload.
  * First shot on major upstream updates.
- Re-packaged from scratch based on new dh primitives.
- Thanks for help on debian-mentors!
  * New upstream release 0.9.4
- Release 0.9.1 .. 0.9.3 was never packaged.
- Old 'lirc' service split into separate systemd services:
  lircd.service, lircmd.service and irexec.service.
- Remote definitions moved out of lirc to new project
  lirc-remotes; affects large number of LP issues.
- Builds also on FreeBSD 10.3.
- Fixes "Not updated to last version" (Closes: #777199),
  LP: #1443590.
- Fixes "Default device for mode2 is /dev/lirc" (Closes: #702140).
- Fixes "/var/run/lirc contents disappear..." (Closes: #676343).
- Fixes "lircrcd segfaults" (Closes: #780062).
- Fixes "'/etc/init.d/lirc restart' is broken" (Closes: #782091).
- Fixes "Prompting due to modified conffiles..." (Closes: #655969).
- Fixes "LIRC installs bad udev rule" (Closes: #804397),
  users depending on this rule will need to explicitly start lircd.
- Fixes "lirc init script can create circular symlinks", LP: #698007.
- Fixes "Update Uploaders List (Closes: #762554).
- Fixes "Please switch to libftdi1" (Closes:  #810370).
- Fixes LP: #153457 "iguanaIR support not functional".
- Fixes LP: #460027 "using lirc init script restart function fails
  sometimes".
- Fixes LP: #499588 "lirc udev rule causes unreliable startup".
- Fixes LP: #567519 "lircd(8) mentions non-existent
  /dev/input/uinput".
- Fixes LP: #1029604 "mce remote doesn't work due to out of date
  lircd.conf.devinput".
- Fixes LP: #1312287 "lircd start problem".
  * The built-in irman support is moved to the lirc-drv-irman package.
  * Revised package structure: keep old liblircclient0 (renamed to
liblirc-client0). Adding new packages liblirc0, liblirc-dev and
lirc-doc. Former liblircclient-dev merged into new liblirc-dev.
  * Don't overwrite existing lircd.conf file.
  * Ship sysV scripts from the svn tree [Stefan Lippers-Hollmann]
  * Add handling of obsolete 0.9.0 udev rule restarting lircd
  * Old lircd output socket link /dev/lirc dropped. Use
/var/run/lirc/lircd.
  * Updated copyright
  * Update compiler flags: -Wl,as-needed + hardening
[Stefan Lippers-Hollmann]
  * Avoid negative architecture deps like [!hurd] (Closes: #634807)
[Stefan Lippers-Hollmann]
  * Add patch 0007-tools-remove-configs-symlink.patch + explicit link
to walk around #801719 (dh_python3 shortcomings).
  * Last parts of libirman dependencies removed.
  * Changing Vcs-* headers to point to upstream packaging branch.
  * Fixes existing large number of upgrade bugs.
  * Enhance hardening flags.
  * Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg
therein.
  * Tested (build-wise) on stretch and sid.

 -- Alec Leamas  <leamas.a...@gmail.com>  Thu, 26 May 2016 11:14:25
+0100


** Changed in: lirc (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/787735

Title:
  Snapstream Firefly non-functional

Status in lirc package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: lirc

  Using the mythbuntu control center configuration for a Snapstream
  Firefly and atilibusb, no key presses show up under mythtv or irw.

  I couldn't get the userspace driver to work in 10.10 either (but
  didn't file a bug - bad user).  In 10.10, I got it working using the
  lirc_atiusb module, but that also doesn't work under 11.04.

  I've attached the hardware.conf below.  The lircd.conf just includes
  /usr/share/lirc/remotes/atiusb/lircd.conf.atilibusb

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: lirc 0.8.7-0ubuntu4.1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Tue May 24 12:39:59 2011
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lirc
  UpgradeStatus: Upgraded to natty on 2011-05-22 (1 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 663497] Re: Transmitter (irsend) broken in 10.10

[Alec Leamas]

indeed the kernel,media subsystem,possibly wrong version

** Package changed: lirc (Ubuntu) => linux-lts-utopic (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/663497

Title:
  Transmitter (irsend) broken in 10.10

Status in linux-lts-utopic package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  Hello,

  I'm using lirc not only for IR control of my applications, but also to
  control external hardware: the lirc 'transmitter' functionality sends
  information to the 'VDR extension board'. Depending on the sent
  information, the 'VDR extension board' is controlled. For example,
  LEDs are swithed on or off.

  This works with module lirc_serial. The transmitter must be enabled during 
compilation of the module.
  It works with 10.04 . For that, /etc/modprobe.d/lirc_serial.conf is:

  options lirc_serial type=0
  options lirc_serial io=0x3F8
  options lirc_serial irq=4
  options lirc_serial softcarrier=0

  It is broken in 10.10. Same configuration files as in 10.04. Log entries are 
also the same, no errors in the logs.
  Still,

  irsend send_once EXTB_TX B_LD5

  lets the LED blink in 10.04, and nothing happens in 10.10.

  
  Note: irw (recieving RC signals) works fine in both, 10.10 and 10.04.

  Regards, Markus

  
  Package: lirc   
  State: installed
  Automatically installed: yes
  Version: 0.8.7~pre3-0ubuntu1
  Priority: extra
  Section: utils
  Maintainer: Ubuntu Core Developers 
  Uncompressed Size: 2.769k
  Depends: libasound2 (> 1.0.22), libc6 (>= 2.7), libftdi1 (>= 0.18), 
libjack-jackd2-0 (>= 1.9.5~dfsg-14) | libjack-0.116, liblircclient0
   (>= 0.6.4), libportaudio2 (>= 19+svn20100220), libusb-0.1-4 (>= 
2:0.1.12), debconf (>= 0.5) | debconf-2.0, lsb-base, setserial
  Recommends: udev
  Suggests: lirc-modules-source, lirc-x
  Conflicts: makedev (< 2.3.1-88)
  Description: infra-red remote control support
   LIRC stands for 'Linux Infra-red Remote Control'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/663497/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 238032] Re: lircd doesn't find dvico usb IR remote device correctly (expects /dev/lirc)

[Alec Leamas]

Same expired goes for lirc...

** Changed in: lirc (Ubuntu)
   Status: Triaged => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/238032

Title:
  lircd doesn't find dvico usb IR remote device correctly (expects
  /dev/lirc)

Status in Mythbuntu:
  Expired
Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  A while back my DVICO usb (sometime during gutsy) remote stopped
  working, and I have only got around to fixing it on my upgraded hardy
  system.

  It appears that the dvico usb remote creates a device on
  /dev/usb/hiddev1, but lircd expects the remote to be on /dev/lirc ,
  and as a result I could no longer control my mythbuntu installation
  with the remote control.

  After a bit of googling ( http://gentoo-wiki.com/HOWTO_LIRC
  #DVICO_FusionHDTV_DVB-T_Plus_IR_Remote ) and 'cat /dev/usb/hiddev1'
  revealed the real address of the remote. In order to work around this
  problem I edited /etc/lirc/hardware.conf and replaced REMOTE_DEVICE=""
  with REMOTE_DEVICE="/dev/usb/hiddev1".

  I've only got irw to work at this stage, but getting the media centre
  control back shouldn't be too hard from here in.

  I'm not sure what files may be useful in diagnosing this problem, so
  please let me know what would help and I can add it here.

  (dmesg output from connection)
  [57662.280194] usb 6-2: new low speed USB device using ohci_hcd and address 4
  [57662.528453] usb 6-2: configuration #1 chosen from 1 choice
  [57662.499406] hiddev97hidraw3: USB HID v1.10 Device [DVICO DVICO USB HID 
Remocon V5.00] on usb-:00:13.4-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/238032/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 238032] Re: lircd doesn't find dvico usb IR remote device correctly (expects /dev/lirc)

[Alec Leamas]

..unless there is more input

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/238032

Title:
  lircd doesn't find dvico usb IR remote device correctly (expects
  /dev/lirc)

Status in Mythbuntu:
  Expired
Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  A while back my DVICO usb (sometime during gutsy) remote stopped
  working, and I have only got around to fixing it on my upgraded hardy
  system.

  It appears that the dvico usb remote creates a device on
  /dev/usb/hiddev1, but lircd expects the remote to be on /dev/lirc ,
  and as a result I could no longer control my mythbuntu installation
  with the remote control.

  After a bit of googling ( http://gentoo-wiki.com/HOWTO_LIRC
  #DVICO_FusionHDTV_DVB-T_Plus_IR_Remote ) and 'cat /dev/usb/hiddev1'
  revealed the real address of the remote. In order to work around this
  problem I edited /etc/lirc/hardware.conf and replaced REMOTE_DEVICE=""
  with REMOTE_DEVICE="/dev/usb/hiddev1".

  I've only got irw to work at this stage, but getting the media centre
  control back shouldn't be too hard from here in.

  I'm not sure what files may be useful in diagnosing this problem, so
  please let me know what would help and I can add it here.

  (dmesg output from connection)
  [57662.280194] usb 6-2: new low speed USB device using ohci_hcd and address 4
  [57662.528453] usb 6-2: configuration #1 chosen from 1 choice
  [57662.499406] hiddev97hidraw3: USB HID v1.10 Device [DVICO DVICO USB HID 
Remocon V5.00] on usb-:00:13.4-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/238032/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 454371] Re: Hauppauge HVR-1600 Remote Not Detected

[Alec Leamas]

Perhaps wrong kernel version, duuno. But it's the kernel, media
susbsystem.

** Package changed: lirc (Ubuntu) => linux-lts-utopic (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/454371

Title:
  Hauppauge HVR-1600 Remote Not Detected

Status in linux-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: lirc

  Running Ubuntu Karmic 9.10 64-bit.

  LIRC will not find the Hauppauage HVR-1600 remote.  The same procedure
  below was performed on Ubuntu 9.04 Jaunty and the remote just worked:

  sudo apt-get install lirc

  After the install, it will configure.  I choose Hauppauge TV Card and
  I do not use an IR Transmitter.

  Using irw, it would show that the commands were found.

  /dev/lirc0 is not even created.  It seems that the previously used
  module (lirc_i2c) no longer is finding the card as it did previously.

  ProblemType: Bug
  Architecture: amd64
  Date: Sat Oct 17 21:38:39 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: lirc 0.8.6-0ubuntu2
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: lirc
  Uname: Linux 2.6.31-14-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/454371/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 626030] Re: lirc does not have support for ITE8708 receiver

[Alec Leamas]

Closing bug, as it's very old and a fix is committed,

** Changed in: lirc (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/626030

Title:
  lirc does not have support for ITE8708 receiver

Status in lirc package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: lirc

  The Dell Studio XPS 16 (Studio XPS 1645) ships with an ITE8708
  receiver which lirc does not have a driver for.

  I tried with the ITE8709 driver but xev did not display any events generated 
by the handheld remote control.
  I booted into Windows 7 to verify that the combination of the receiver and 
the remote control works and indeed it does.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: lirc 0.8.6-0ubuntu4.1
  ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Sat Aug 28 16:47:54 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: lirc

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 991116] Re: lirc does not work/start

[Alec Leamas]

Does this mean that the bug is gone after updating hardware.conf?

** Changed in: lirc (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/991116

Title:
  lirc does not work/start

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  lirc is installed

  irw reports: 
  connect: No such file or directory

  irexec reports: 
  irexec: could not connect to socket
  connect: No such file or directory

  /lib/modules/3.2.0-24-generic-pae/kernel/drivers/staging/lirc does not exist
  /sys/class/rc is empty

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lirc 0.9.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  Uname: Linux 3.2.0-24-generic-pae i686
  NonfreeKernelModules: slamr nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  Date: Sun Apr 29 16:36:05 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lirc
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.lirc.hardware.conf: 2012-04-29T13:36:31.887446
  mtime.conffile..etc.lirc.lircd.conf: 2012-04-29T08:14:11.539446

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 786254] Re: lirc not working, irw empty, irrecord no gap found

[Alec Leamas]

The last lirc update 0.9.4 more or less obsoletes this bug since this
kind of configuration doesn't take place. In order to verify this bug we
need some testing on the latest version.

If you are still interested in this bug, please provide some feedback
from testing with 0.9.4c- Otherwise, without further input, let's
eventually close this bug.

** Changed in: lirc (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/786254

Title:
  lirc not working, irw empty, irrecord no gap found

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  I'm trying to use the Ir remote control from my Pinnacle PCTV,

  In dpkg-reconfigure, I've selected /dev/input/by-path/pci-:00:1d.7
  -event-ir  as device

  Lirc is starting without failure, but it seems that lirc is receiving
  no signal from the device...

  When trying to use irrecord, I get : 
  Hold down an arbitrary button.
  irrecord: gap not found, can't continue
  irrecord: closing '/dev/input/by-path/pci-:00:1d.1-usb-0:1:1.2-event'

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: lirc 0.8.7-0ubuntu4.2
  ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
  Uname: Linux 2.6.38-9-generic x86_64
  Architecture: amd64
  Date: Sat May 21 19:54:16 2011
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   LC_MESSAGES=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: lirc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 786254] Re: lirc not working, irw empty, irrecord no gap found

[Alec Leamas]

confirmed -> incomplete since we have no info on the status with recent
lirc versions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/786254

Title:
  lirc not working, irw empty, irrecord no gap found

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  I'm trying to use the Ir remote control from my Pinnacle PCTV,

  In dpkg-reconfigure, I've selected /dev/input/by-path/pci-:00:1d.7
  -event-ir  as device

  Lirc is starting without failure, but it seems that lirc is receiving
  no signal from the device...

  When trying to use irrecord, I get : 
  Hold down an arbitrary button.
  irrecord: gap not found, can't continue
  irrecord: closing '/dev/input/by-path/pci-:00:1d.1-usb-0:1:1.2-event'

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: lirc 0.8.7-0ubuntu4.2
  ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
  Uname: Linux 2.6.38-9-generic x86_64
  Architecture: amd64
  Date: Sat May 21 19:54:16 2011
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   LC_MESSAGES=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: lirc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 993202] Re: lircd crashing on boot in precise. Can be restarted and then stays up

[Alec Leamas]

We think this bug is resolved in the last update 0.9.4c (zesty). If you
are still interested in it, could you please provide som feedback from
testing this  version? There are backport version available at my ppa:
https://launchpad.net/~leamas-alec/+archive/ubuntu/lirc-0.9.4.

Otherwise, without further input, let's close this bug. Setting state to
Incomplete since we lack info on status in recent code.

** Changed in: lirc (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/993202

Title:
  lircd crashing on boot in precise.  Can be restarted and then stays up

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  On my fresh install of Precise Ubuntu, I am suffering an lircd crash
  on boot.  This occurs most boots and apport has sent a few error
  reports in, but I didn't see an official bug open yet.  I am using a
  usbuirt receiver.  Judging by the SegvAnalysis, it looks like a null
  pointer deference.

  Some interesting information is that once the system is booted, I can
  restart lircd using '/etc/init.d/lircd restart' and the daemon starts
  and stays stable (up for days no new crashes).  This makes me
  suspicious that this could be an initialization race where the driver
  is trying to access something that is not yet available or initialized
  during the boot strip.

  I am attaching the crash report along with an included file that
  contains button signal definitions that is referenced in my lircd.conf
  file.

  jheck@twilightzone:~$ lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04
  jheck@twilightzone:~$ apt-cache policy lirc
  lirc:
Installed: 0.9.0-0ubuntu1
Candidate: 0.9.0-0ubuntu1
Version table:
   *** 0.9.0-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status
  jheck@twilightzone:~$

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 826562] Re: Pinnacle PCTV 50/100i not working in Ubuntu 11.10

[Alec Leamas]

The kernel (media susbsystem), possibly wrong version

** Package changed: lirc (Ubuntu) => linux-lts-utopic (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/826562

Title:
  Pinnacle PCTV 50/100i not working in Ubuntu 11.10

Status in linux-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  This remote has stopped working since 10.10 ,used to be detected as
  /dev/input/eventx but now there is no such entry in /proc/devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lirc 0.9.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
  Uname: Linux 3.0.0-8-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Mon Aug 15 12:00:34 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110802.1)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lirc
  UpgradeStatus: Upgraded to oneiric on 2011-08-13 (1 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2011-08-07T10:25:45.992123
  mtime.conffile..etc.lirc.lircd.conf: 2011-08-07T10:25:46.002123

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/826562/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 614289] Re: LIRC MCE USB Config Crash

[Alec Leamas]

Marking as incomplete since we have  no information if this bug is still
present in recent versions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/614289

Title:
  LIRC MCE USB Config Crash

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  Release: Ubuntu maverick (development branch) / 10.10
  Pack Type / Version: LIRC 0.8.6-0ubuntu5
  Expected To Happen - LIRC installed and configured a Windows Media Center 
Transceivers /Remotes all device
  Actual Results -

  When attempting to install LIRC either by apt-get in a terminal and by
  package manager it gets to the configuration option of the
  installationwhere you select the type of remote control you have and
  when you select the device as;

  "Windows Media Center Transceivers /Remotes all"

  the install of LIRC crashes and hangs on "Installing Modules".

  If you select different remotes in the configuration options of LIRC
  it will then get past "Installing Modules" and complete the install of
  LIRC but obviously the remote in question does not work as its the
  wrong remote type.

  This leads me to the conclusion that it is only the "Windows Media
  Center Transceivers /Remotes all" option that is causing LIRC to fail
  its final configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: lirc 0.8.6-0ubuntu5
  ProcVersionSignature: Ubuntu 2.6.35-14.19-generic-pae 2.6.35
  Uname: Linux 2.6.35-14-generic-pae i686
  Architecture: i386
  Date: Fri Aug  6 19:25:05 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
  ProcEnviron:
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: lirc

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 912251] Re: lirc_register_driver: dev pointer not filled in!

[Alec Leamas]

The former lirc modules now belongs to kernel (media subsystem)

** Package changed: lirc (Ubuntu) => linux-lts-xenial (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/912251

Title:
  lirc_register_driver: dev pointer not filled in!

Status in linux-lts-xenial package in Ubuntu:
  Incomplete

Bug description:
  Lirc package installed on a Dell Latitude d600 with builtin infrared
  port and configured for "SIR IrDA (built-in IR ports)" on /dev/ttyS1
  (io=0x2f8, irq=3). BIOS is configured with IrDA on COM2.

  Created /etc/modprobe.d/lirc-sir.conf with:

  install lirc_sir setserial /dev/ttyS1 uart none; modprobe --ignore-
  install lirc_sir irq=3 io=0x2f8

  Starting lirc gives the following error:

  # /etc/init.d/lirc start
   * Loading LIRC modules  [ OK 
]
   * Unable to load LIRC kernel modules. Verify your
   * selected kernel modules in /etc/lirc/hardware.conf

  and the following kernel messages:

  [   23.184985] lirc_dev: IR Remote Control driver registered, major 251 
  [   23.192510] init: apport pre-start process (867) terminated with status 1
  [   23.222720] lirc_sir: module is from the staging directory, the quality is 
unknown, you have been warned.
  [   23.229006] lirc_register_driver: dev pointer not filled in!
  [   23.229083] lirc_sir: init_chrdev() failed.

  The lirc_sir module is not loaded and lirc doesn't work. Trying to
  manually load the module with the following commands gives the same
  error:

  # setserial /dev/ttyS1 uart none
  # insmod 
/lib/modules/3.0.0-12-generic/kernel/drivers/staging/lirc/lirc_sir.ko irq=3 
io=0x2f8
  insmod: error inserting 
'/lib/modules/3.0.0-12-generic/kernel/drivers/staging/lirc/lirc_sir.ko': -1 
Input/output error

  Compiling lirc version 0.9.1-git from the lirc git repository and
  manually loading the new modules works fine and I can then succesfully
  start lircd and test my remote with irw:

  [ 2354.994042] lirc_dev: IR Remote Control driver registered, major 251 
  [ 2380.204606] lirc_dev: lirc_register_driver: sample_rate: 0
  [ 2380.204797] lirc_sir: I/O port 0x02f8, IRQ 3.
  [ 2380.204815] lirc_sir: Installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lirc 0.9.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Thu Jan  5 13:42:56 2012
  InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Release i386 (20110426.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lirc
  UpgradeStatus: Upgraded to oneiric on 2011-10-31 (66 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2012-01-04T19:38:28.247174
  mtime.conffile..etc.lirc.lircd.conf: 2012-01-04T19:07:30.715709

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/912251/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 614289] Re: LIRC MCE USB Config Crash

[Alec Leamas]

We believe this bug has been fixed by lirc updates since 0.6.0. In
particular, the last release 0.9.4 does not rebuild lirc in any way and
these kind of problems just cannot occur (not to say other probklems
couldn't).

Please let us know if you are still interested in this. Otherwise,
without further input, let's close this bug.

** Changed in: lirc (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/614289

Title:
  LIRC MCE USB Config Crash

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  Release: Ubuntu maverick (development branch) / 10.10
  Pack Type / Version: LIRC 0.8.6-0ubuntu5
  Expected To Happen - LIRC installed and configured a Windows Media Center 
Transceivers /Remotes all device
  Actual Results -

  When attempting to install LIRC either by apt-get in a terminal and by
  package manager it gets to the configuration option of the
  installationwhere you select the type of remote control you have and
  when you select the device as;

  "Windows Media Center Transceivers /Remotes all"

  the install of LIRC crashes and hangs on "Installing Modules".

  If you select different remotes in the configuration options of LIRC
  it will then get past "Installing Modules" and complete the install of
  LIRC but obviously the remote in question does not work as its the
  wrong remote type.

  This leads me to the conclusion that it is only the "Windows Media
  Center Transceivers /Remotes all" option that is causing LIRC to fail
  its final configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: lirc 0.8.6-0ubuntu5
  ProcVersionSignature: Ubuntu 2.6.35-14.19-generic-pae 2.6.35
  Uname: Linux 2.6.35-14-generic-pae i686
  Architecture: i386
  Date: Fri Aug  6 19:25:05 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
  ProcEnviron:
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: lirc

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 816598] Re: Natty can't resume "lirc" after sleep

[Alec Leamas]

Possibly wrong kernel version... but still the kernel (media subsystem)

** Package changed: lirc (Ubuntu) => linux-lts-utopic (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/816598

Title:
  Natty can't resume "lirc" after sleep

Status in linux-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  My MCE remote won't work after sleep in Natty 11.04 using the latest
  kernel 2.6.39.  I'm able to wake the computer from sleep using the MCE
  remote but no respond after the system is awake.  No respond from irw
  or restarting lirc make any difference.  Pm-suspend.log and pm-
  powersave.log doesn't show any error message regarding lirc but the
  remote still doesn't work until I do a reboot of the system.  Any help
  would greatly be appreciate

  
  $ ls -l /dev/mce*
  crw--- 1 root root 10, 227 2011-07-21 01:21 /dev/mcelog

  $ lsmod | grep mce*
  rc_rc6_mce 12502  0 
  mceusb 17867  0 
  rc_core26918  9 
ir_lirc_codec,ir_sony_decoder,ir_jvc_decoder,rc_rc6_mce,ir_rc6_decoder,ir_rc5_decoder,ir_nec_decoder,mceusb

  $ ls -l /dev/lirc*
  crw--- 1 root root 250, 0 2011-07-21 01:21 /dev/lirc0
  lrwxrwxrwx 1 root root 19 2011-07-21 01:22 /dev/lircd -> 
/var/run/lirc/lircd

  $ lsmod | grep lirc_ 
  ir_lirc_codec  12898  0 
  lirc_dev   19232  1 ir_lirc_codec
  rc_core26918  9 
ir_lirc_codec,ir_sony_decoder,ir_jvc_decoder,rc_rc6_mce,ir_rc6_decoder,ir_rc5_decoder,ir_nec_decoder,mceusb

  
  $ dmesg | grep mceusb
  [9.355076] mceusb 7-1:1.0: Registered Microsoft Microsoft IR Transceiver 
on usb7:2
  [9.355131] usbcore: registered new interface driver mceusb
  [9.397277] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at 
minor = 0
  [18795.680738] mceusb 7-1:1.0: suspend
  [18798.424133] mceusb 7-1:1.0: resume
  [18798.424150] PM: resume of drv:mceusb dev:7-1:1.0 complete after 789.441 
msecs
  [18808.260732] Modules linked in: snd_hda_codec_realtek snd_hda_intel 
snd_hda_codec snd_hwdep snd_pcm nfsd snd_seq_midi exportfs i915 nfs snd_rawmidi 
snd_seq_midi_event lockd fscache nfs_acl ir_lirc_codec lirc_dev auth_rpcgss 
snd_seq rc_rc6_mce ir_sony_decoder snd_timer snd_seq_device joydev 
ir_jvc_decoder drm_kms_helper ir_rc6_decoder drm ir_rc5_decoder i2c_algo_bit 
snd video mceusb ir_nec_decoder psmouse soundcore usbhid snd_page_alloc rc_core 
hid sunrpc lp parport serio_raw usb_storage uas r8169 ahci libahci

  
  $ cat /proc/bus/input/devices

  I: Bus=0003 Vendor=045e Product=006d Version=0200
  N: Name="Media Center Ed. eHome Infrared Remote Transceiver (045e:006d)"
  P: Phys=usb-:00:1d.1-1
  S: Sysfs=/devices/pci:00/:00:1d.1/usb7/7-1/7-1:1.0/rc/rc0/input4
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=100013
  B: KEY=fff 0 200108fc326 2376051 0 700158000 41920011 
9e9680 1000
  B: MSC=10

  
  $ cat /sys/class/rc/rc0/protocols
  rc-5 nec rc-6 jvc sony [lirc]

  
  $ ir-keytable 
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: NEC RC-5 RC-6 JVC SONY LIRC 
Enabled protocols: LIRC 
Repeat delay = 500 ms, repeat period = 33 ms

  
  $ cat /etc/lirc/hardware.conf
  # /etc/lirc/hardware.conf
  #
  #Chosen Remote Control
  REMOTE="Windows Media Center Transceivers/Remotes (all)"
  REMOTE_MODULES="lirc_dev mceusb"
  #REMOTE_DRIVER="devinput"
  REMOTE_DRIVER=""
  REMOTE_DEVICE="/dev/lirc0"
  
#REMOTE_DEVICE="/dev/input/by-id/usb-Microsoft_Microsoft_IR_Transceiver_MS193YGT-event-if00"
  REMOTE_SOCKET=""
  #REMOTE_LIRCD_CONF="lircd.conf"
  REMOTE_LIRCD_CONF="mceusb/lircd.conf.mceusb"
  REMOTE_LIRCD_ARGS=""

  #Chosen IR Transmitter
  TRANSMITTER=""
  TRANSMITTER_MODULES=""
  TRANSMITTER_DRIVER=""
  TRANSMITTER_DEVICE=""
  TRANSMITTER_SOCKET=""
  TRANSMITTER_LIRCD_CONF=""
  TRANSMITTER_LIRCD_ARGS=""

  #Enable lircd
  START_LIRCD="true"

  #Don't start lircmd even if there seems to be a good config file
  #START_LIRCMD="false"

  #Try to load appropriate kernel modules
  LOAD_MODULES="false"

  # Default configuration files for your hardware if any
  LIRCMD_CONF=""

  #Forcing noninteractive reconfiguration
  #If lirc is to be reconfigured by an external application
  #that doesn't have a debconf frontend available, the noninteractive
  #frontend can be invoked and set to parse REMOTE and TRANSMITTER
  #It will then populate all other variables without any user input
  #If you would like to configure lirc via standard methods, be sure
  #to leave this set to "false"
  FORCE_NONINTERACTIVE_RECONFIGURATION="false"
  START_LIRCMD=""

  
  $ lsmod 
  Module  Size  Used by
  nfsd  316512  13 
  exportfs   12998  1 nfsd
  nfs   330417  0 
  lockd  85732  2 nfsd,nfs
  fscache  

[Desktop-packages] [Bug 624172] Re: Multiple copies of irexec started at login

[Alec Leamas]

The key issue her is how irexec is started. When you add the irexex
entry, do you provide the --daemon/-d option? If so, try without it.

If  the --daemon option isn't active, this is likely a gnome bug.
program started from ~/.config/autostart  is certainly a session issue.

If you are still interested in this please provide some feeedback.
Otherwise, without further input, let's close this bug.

** Changed in: lirc (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/624172

Title:
  Multiple copies of irexec started at login

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  I use irexec to generate multimedia keystrokes from my Apple remote.
  Hence, I created a Startup Applications entry for irexec. Sometimes
  when I log in, multiple copies of irexec are run. It seems that this
  could be because irexec is not always killed when I log out: for
  example, in my current session, one of the copies of irexec has a PID
  just a little greater than my gnome-session, whereas the other has a
  lower PID, which seems to be similar to PIDs of other processes
  created when I first logged in after rebooting, e.g. mpd.

  I don't know whether this bug is properly considered to be in lirc or
  in some program related to GNOME session management, but as I cannot
  tell it seemed logical to start here (with the specific program that
  is causing problems), especially as I have not noticed this behaviour
  with any other program.

  I suppose there are multiple questions to answer:

  1. Should irexec be killed (or die) when I log out? It seems that some
  programs started in my session, like mpd, persist when I log out.

  2. When I log in, should irexec realise that it is already running and
  not start a second instance?

  If either 1 or 2 were happening, then I would not have a problem...

  Sorry if this is a bit vague, and let me know what other information I
  can provide to help track down the bug.

  (In case you're wondering, the reason this bug is a problem is because
  when there are multiple copies of irexec running, each IR control
  keypress is acted on once per copy of irexec, so when I press
  "play/pause", nothing seems to happen, because the music is first
  paused, then immediately unpaused, for example.)

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: lirc 0.8.6-0ubuntu4.1
  ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic i686
  Architecture: i386
  Date: Wed Aug 25 18:59:59 2010
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_GB.UTF-8
  SourcePackage: lirc

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 517956] Re: Timing problem (garbage characters) in lirc-driver for iMon PAD VFD 15c2:0036

[Alec Leamas]

Indeed the kernelk (media subsystem), but possibly the  wrong version...
sorry

** Package changed: lirc (Ubuntu) => linux-meta-lts-xenial (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/517956

Title:
  Timing problem (garbage characters) in lirc-driver for iMon PAD VFD
  15c2:0036

Status in linux-meta-lts-xenial package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: lirc

  In the lirc-driver for the Soundgraph iMon PAD VFD, USB-ID 15c2:0036,
  there is a timing problem. Packets are sent too fast to the USB-
  Device. You can see that you are affected by this problem, if you find
  similar lines in your syslog:

  [...]
  Feb  6 08:06:09 mythtv kernel: [   47.727759] lirc_imon: vfd_write: send 
packet failed for packet #2
  Feb  6 08:06:09 mythtv kernel: [   47.978904] lirc_imon: send_packet: packet 
tx failed (-32)
  Feb  6 08:06:09 mythtv kernel: [   47.978909] lirc_imon: vfd_write: send 
packet failed for packet #4
  Feb  6 08:06:09 mythtv kernel: [   48.223802] lirc_imon: send_packet: packet 
tx failed (-32)
  Feb  6 08:06:09 mythtv kernel: [   48.223807] lirc_imon: vfd_write: send 
packet failed for packet #2
  Feb  6 08:06:09 mythtv kernel: [   48.471698] lirc_imon: send_packet: packet 
tx failed (-32)
  Feb  6 08:06:09 mythtv kernel: [   48.471703] lirc_imon: vfd_write: send 
packet failed for packet #1
  [...]

  To fix the problem, you can apply the enclosed patch and rebuild the dkms 
lirc modules:
  cd /usr/src/lirc-0.8.6/
  sudo dkms remove -m lirc -v 0.8.6 -k `uname -r`
  sudo patch -p0 < lirc-0.8.6-VFD_0x0036_timing.patch
  sudo dkms add -m lirc -v 0.8.6
  sudo dkms build -m lirc -v 0.8.6
  sudo dkms install --force -m lirc -v 0.8.6

  The patch will add some 20 microseconds delay before each package
  send. It's not the most beautiful solution, but until there is some
  corrected upstream, this will help.

  HTH, Edi

  Guideline informations:
  1) Ubuntu-Release:
  Description:  Ubuntu 9.10
  Release:  9.10

  2) Package Version:
  lirc-modules-source:
Installed: 0.8.6-0ubuntu2
Candidate: 0.8.6-0ubuntu2
Version table:
   *** 0.8.6-0ubuntu2 0
  500 http://archive.ubuntu.com karmic/universe Packages
  100 /var/lib/dpkg/status

  3) What should happen:
  Correct information displayed on the VFD

  4) What happens:
  Garbage characters displayed on VFD

  ProblemType: Bug
  Architecture: amd64
  Date: Sat Feb  6 09:07:02 2010
  DistroRelease: Ubuntu 9.10
  Package: lirc-modules-source 0.8.6-0ubuntu2 [modified: 
usr/src/lirc-0.8.6/drivers/lirc_imon/lirc_imon.c]
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
  SourcePackage: lirc
  Uname: Linux 2.6.31-19-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/517956/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 667054] Re: Totalmedia Unlisted Remotes LIRC

[Alec Leamas]

Well, that lien explains some of these bugs. However, it's old and the
question now if is you are still interested in this.

That said, a missing remote is not a bug but a support request. Please
refer to the upstream mailing list at http://sf.net/p/lirc if you need
assistance with unknown remotes.


Closing as invalid, despite that line :)

** Changed in: lirc (Ubuntu)
   Status: New => Incomplete

** Changed in: lirc (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/667054

Title:
  Totalmedia Unlisted Remotes LIRC

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: lirc

  UBUNTU 10.10 MAVERICK
  I haven't found the "Totalmedia" in a list of remotes  when I go to a 
"Unlisted Remotes" there was a line who said  """If your remote isn't listed in 
the lirc installation, you should file a bug on Launchpad. "" so i'm here  
Please sorry for my bad english!!!  Can you help me to find the best 
configuration for my remotes?!?!
  The hardware is ANALOGUE PCI "NOT ONLY TV PLATINUM model LV3A; in the box 
there was a remotes!!!

  Thanks you so much!!!

  Good work for all!!! ubuntu is the best distro in a LINUX WORLD

  BYE
  met

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 657991] Re: lirc fails to work with mce remote

[Alec Leamas]

** Changed in: lirc (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/657991

Title:
  lirc fails to work with mce remote

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: lirc

  After upgrading to maverick, lirc no longer works with microsoft media
  center remote and receiver. I attempted to reinstall lirc, choosing
  the mce option when prompted, but nothing shows up in irw, or with the
  gnome-lirc-properties.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 660185] Re: Issues with Generic Mceusb receiver after upgrade to 10.10

[Alec Leamas]

This  bug is old. Does it still affect you? if so , please let us know.


Otherwise, without further input, let's close this bug.

** Changed in: lirc (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/660185

Title:
  Issues with Generic Mceusb receiver after upgrade to 10.10

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  Issues with Generic Mceusb receiver after upgrade to 10.10

  I've upgraded a 10.04 system to 10.10 and seem to have problems with
  my generic mceusb receiver (the receiver works fine in 10.04)

  dmesg | grep lirc
  [   17.618734] lirc_dev: IR Remote Control driver registered, major 249
  [   17.630203] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at 
minor = 0

  dmesg | grep mceusb
  [   17.630203] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at 
minor = 0
  [   17.630222] mceusb 2-9:1.0: Registered Formosa21 SnowflakeEmulation on 
usb2:2
  [   17.630241] usbcore: registered new interface driver mceusb

  cat /proc/bus/input/devices
  ...
  I: Bus= Vendor= Product= Version=
  N: Name="Media Center Ed. eHome Infrared Remote Transceiver (147a:e017)"
  P: Phys=usb-:00:04.0-9/input0
  S: Sysfs=/devices/virtual/rc/rc0/input4
  U: Uniq=
  H: Handlers=kbd event4
  B: EV=13
  B: KEY=fff 0 108fc326 2176041 0 118000 41800011 9e9680 
1000

  The device seems to be recognised and /dev/lirc0 is created but irw
  does not respond to any buttons. Using 'sudo mode2 - d /dev/lirc0' I
  do get output when buttons are pressed.

  cat /etc/lirc/hardware.conf
  REMOTE="Windows Media Center Transceivers/Remotes (all)"
  TRANSMITTER="None"
  REMOTE_MODULES="lirc_dev mceusb"
  REMOTE_DRIVER=""
  REMOTE_DEVICE="/dev/lirc0"
  REMOTE_SOCKET=""
  REMOTE_LIRCD_CONF="mceusb/lircd.conf.mceusb"
  REMOTE_LIRCD_ARGS=""
  TRANSMITTER_MODULES=""
  TRANSMITTER_DRIVER=""
  TRANSMITTER_DEVICE=""
  TRANSMITTER_SOCKET=""
  TRANSMITTER_LIRCD_CONF=""
  TRANSMITTER_LIRCD_ARGS=""
  START_LIRCD="true"
  START_LIRCMD=""
  LOAD_MODULES=""
  LIRCMD_CONF=""
  FORCE_NONINTERACTIVE_RECONFIGURATION="false"

  Connecting a genuine Microsoft receiver to the machine using the same
  config works fine.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 657948] Re: Dell Branded Philips Remote Not Working

[Alec Leamas]

This bug is obsoleted by the new 0.9.4 version which doos not build
rebuild lirc in any case.

If you are still interested in this bug please let us know. Otherwise,
without further input, let's close this bug.

** Changed in: lirc (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/657948

Title:
  Dell Branded Philips Remote Not Working

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  Dell Branded Philips Remote was not working in Ubuntu, following the
  guide at https://help.ubuntu.com/community/LIRC I got it working,
  however I have no idea how to submit a patch as instructed, and the
  page says to submit a bug report.

  lsusb shows it as ID 0471:2093 Philips

  Directions on help page indicate module is at
  /usr/src/lirc-*/lirc_mceusb2 , however on my system it was at
  /usr/src/lirc-0.8.6/drivers/lirc_mceusb with file lirc_mceusb.c

  Let me know if I should send anything further.

  Thanks,

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 635947] Re: /etc/lirc/hardware.conf is incorrect for Philips SRM 7500 remote

[Alec Leamas]

This bug is old. Does it still affect you? In this case, let us know.
Otherwise, without firther input, let's close this bug

** Changed in: lirc (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/635947

Title:
  /etc/lirc/hardware.conf is incorrect for Philips SRM 7500 remote

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  Philips SRM 7500 needs the following line in /etc/lirc/hardware.conf

  REMOTE_DEVICE="macShortAddress=12:34,remoteShortAddress=56:78,macPANId=9a:bc"

  In the latest Maveric, the REMOTE_DEVICE option for this remote is
  empty.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 635947] Re: /etc/lirc/hardware.conf is incorrect for Philips SRM 7500 remote

[Alec Leamas]

Also, note that the new version 0.9.4 (zesty) basically obsoletes this
bug since it does not support hardware.conf

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/635947

Title:
  /etc/lirc/hardware.conf is incorrect for Philips SRM 7500 remote

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  Philips SRM 7500 needs the following line in /etc/lirc/hardware.conf

  REMOTE_DEVICE="macShortAddress=12:34,remoteShortAddress=56:78,macPANId=9a:bc"

  In the latest Maveric, the REMOTE_DEVICE option for this remote is
  empty.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 517304] Re: Lirc does not work; no remote's button presses visible in irw's output

[Alec Leamas]

I cannot see that this qualifies as a bug, it's more like a support
request "How should I configure lirc"· it's also very old. Closing.

Please refer to the upstream mailing list at http://sf.net/p/lirc if you
are still interested in this.

** Changed in: lirc (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/517304

Title:
  Lirc does not work; no remote's button presses visible in irw's output

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: lirc

  What else do I have to tell?

  ProblemType: Bug
  Architecture: i386
  Date: Fri Feb  5 00:30:11 2010
  DistroRelease: Ubuntu 9.10
  Package: lirc 0.8.6-0ubuntu2
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: lirc
  Uname: Linux 2.6.31-14-generic i686
  XsessionErrors:
   (xfce4-cpugraph-plugin:1646): Gtk-CRITICAL **: 
gtk_container_set_border_width: assertion `GTK_IS_CONTAINER (container)' failed
   (polkit-gnome-authentication-agent-1:1684): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (xfce4-terminal:1687): Terminal-WARNING **: Unable to load terminal 
preferences.
   (firefox:1737): GLib-WARNING **: g_set_prgname() called multiple times
   (firefox:1737): GLib-WARNING **: g_set_prgname() called multiple times

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 622255] Re: update manager stuck on :loadingLirc modules"

[Alec Leamas]

We believe this problem is solved by the latest lirc update 0.9.4 in
zesty (it does not do any kernel module loading whatsoever). If you are
still  ibterested in this bug, please provide some feedback from testing
zesty.

Otherwise, without further input, let's close this bug.

** Changed in: lirc (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/622255

Title:
  update manager stuck on :loadingLirc modules"

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  Can not update system or upgrade system as update gets stuck onload
  lirc modules

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: lirc 0.8.7~pre2-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-17.23-generic-pae 2.6.35.2
  Uname: Linux 2.6.35-17-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Sun Aug 22 19:58:26 2010
  ProcEnviron:
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: lirc

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 582274] Re: Leadtek WinFast DTV Dongle Gold remote not working with lirc after update to ubuntu 10.04

[Alec Leamas]

This is a HAL problem, and HAL is since long gone from modern linux'es.
If you are still interested in this bug please let us know. Without
further input the bug will be closed

** Changed in: lirc (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/582274

Title:
  Leadtek WinFast DTV Dongle Gold remote not working with lirc after
  update to ubuntu 10.04

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  When I had Ubuntu 9.04 my remote and LIRC was working great, then I
  updated to Ubuntu 10.04 and I believe my problem is the HAL is taking
  the device as a keyboard and not allowing LIRC to use the device.

  When I use the remotes number keys in a terminal, they act like
  keyboard presses, if I type in 'IRW' I get this output...

  matt@myth:~$ irw
  ^[[A^[[B^[[D^[[C

  The above happens when I press the UP, DOWN, LEFT, RIGHT keys.

  I have tried using a remote.fdi file and also editing the lirc.fdi file in 
this location...
  /usr/share/hal/fdi/preprobe/20thirdparty

  But I believe this only works up to 9.10 Ubuntu and now 10.04 requires
  UDEV rules instead of FDI files which no longer work.

  Can anyone help me to fix this, or confirm that is the problem?

  
  lshal output...

  udi = '/org/freedesktop/Hal/devices/temp/134'
info.ignore = true  (bool)
info.parent = 
'/org/freedesktop/Hal/devices/usb_device_413_6029_noserial_if1'  (string)
info.product = 'Ignored Device'  (string)
info.subsystem = 'input'  (string)
info.udi = '/org/freedesktop/Hal/devices/ignored-device'  (string)
input.device = '/dev/input/event7'  (string)
input.originating_device = 
'/org/freedesktop/Hal/devices/usb_device_413_6029_noserial_if1'  (string)
input.product = 'Leadtek WinFast DTV Dongle Gold'  (string)
linux.device_file = '/dev/input/event7'  (string)
linux.hotplug_type = 2  (0x2)  (int)
linux.subsystem = 'input'  (string)
linux.sysfs_path = 
'/sys/devices/pci:00/:00:10.4/usb1/1-5/1-5:1.1/input/input7/event7'  
(string)

  udi = '/org/freedesktop/Hal/devices/temp/131'
info.ignore = true  (bool)
info.parent = '/org/freedesktop/Hal/devices/usb_device_413_6029_noserial'  
(string)
info.product = 'Ignored Device'  (string)
info.subsystem = 'input'  (string)
info.udi = '/org/freedesktop/Hal/devices/ignored-device'  (string)
input.device = '/dev/input/event6'  (string)
input.originating_device = 
'/org/freedesktop/Hal/devices/usb_device_413_6029_noserial'  (string)
input.product = 'IR-receiver inside an USB DVB receiver'  (string)
linux.device_file = '/dev/input/event6'  (string)
linux.hotplug_type = 2  (0x2)  (int)
linux.subsystem = 'input'  (string)
linux.sysfs_path = 
'/sys/devices/pci:00/:00:10.4/usb1/1-5/input/input6/event6'  (string)

  udi = '/org/freedesktop/Hal/devices/usb_device_413_6029_noserial_dvb_2'
dvb.device = '/dev/dvb/adapter0/frontend0'  (string)
info.capabilities = {'dvb'} (string list)
info.category = 'dvb'  (string)
info.parent = '/org/freedesktop/Hal/devices/usb_device_413_6029_noserial'  
(string)
info.product = 'DVB Device'  (string)
info.subsystem = 'dvb'  (string)
info.udi = 
'/org/freedesktop/Hal/devices/usb_device_413_6029_noserial_dvb_2'  (string)
linux.device_file = '/dev/dvb/adapter0/frontend0'  (string)
linux.hotplug_type = 2  (0x2)  (int)
linux.subsystem = 'dvb'  (string)
linux.sysfs_path = 
'/sys/devices/pci:00/:00:10.4/usb1/1-5/dvb/dvb0.frontend0'  (string)

  udi = '/org/freedesktop/Hal/devices/usb_device_413_6029_noserial_dvb_1'
dvb.device = '/dev/dvb/adapter0/dvr0'  (string)
info.capabilities = {'dvb'} (string list)
info.category = 'dvb'  (string)
info.parent = '/org/freedesktop/Hal/devices/usb_device_413_6029_noserial'  
(string)
info.product = 'DVB Device'  (string)
info.subsystem = 'dvb'  (string)
info.udi = 
'/org/freedesktop/Hal/devices/usb_device_413_6029_noserial_dvb_1'  (string)
linux.device_file = '/dev/dvb/adapter0/dvr0'  (string)
linux.hotplug_type = 2  (0x2)  (int)
linux.subsystem = 'dvb'  (string)
linux.sysfs_path = 
'/sys/devices/pci:00/:00:10.4/usb1/1-5/dvb/dvb0.dvr0'  (string)

  udi = '/org/freedesktop/Hal/devices/usb_device_413_6029_noserial_dvb_0'
dvb.device = '/dev/dvb/adapter0/net0'  (string)
info.capabilities = {'dvb'} (string list)
info.category = 'dvb'  (string)
info.parent = '/org/freedesktop/Hal/devices/usb_device_413_6029_noserial'  
(string)
info.product = 'DVB Device'  (string)
info.subsystem = 'dvb'  (string)
info.udi = 
'/org/freedesktop/Hal/devices/usb_device_413_6029_noserial_dvb_0'  (string)
linux.device_file = '/dev/dvb/adapter0/net0'  (string)
linux.hotplug_type = 2  (0x2)  (int)
linux.subsystem = 'dvb'  

[Desktop-packages] [Bug 601630] Re: Bose 321 gs series remote not listed.

[Alec Leamas]

This is not a bug but a support request - lirc contains all the tools
and documentation to cope with an  unknown remote. See e. g.,
http://lirc.org/html/configuration-guide.html which refers to the latest
lirc version  0.9.4 (zesty).

Closing thius bug. Please refer to the upstream maling list at
http://sf.net/p/lirc if you have questions.

** Changed in: lirc (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/601630

Title:
  Bose 321 gs series remote not listed.

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: lirc

  The Bose 3-2-1 GS series Home Threader system comes with a Universal
  remote which most of the devices around the house. I think configuring
  this remote to work with Ubuntu/lirc would be a boon to a lot of
  people that already own this system.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 502276] Re: LIRC configuration for TechniSat/TechnoTrend USB IR receiver

[Alec Leamas]

As of current lirc (zesty + all other distros) remote configurations
lives at http://sf.net/p/lirc-remotes. Please submit this config there
to make it availale to others.

This bug is old. Unless there is more input, lets close it. The remote
configurations used by 0.9.0 are dropped upstream and it's IMHO not much
point adding downstream in Ubuntu.


** Changed in: lirc (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/502276

Title:
  LIRC configuration for TechniSat/TechnoTrend USB IR receiver

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  Find attached the configuration for the TechniSat (or TechnoTrend as
  lirc identifies it) TTS35AI remote.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 501061] Re: Tevion/KWorld DVB-T 220RF Remote Control not listed in LIRC configuration

[Alec Leamas]

This bug is old. Furhermore, lirc cannot accept bugs for each each and
every remote.not supported - lirc is designed to be able to cope woih
unknown remotes, but it requires user intervention.

If you are still intteresteed in this see the documentaion at
http://lirc.org/html/configuration-guide.html (which refers to latest
version 0.9.4 in zesty). There is also an upstream mailing list at
http://sf.net/p/lirc. Closing this as invalid, basicallhy as an old
support request.

** Changed in: lirc (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/501061

Title:
  Tevion/KWorld DVB-T 220RF Remote Control not listed in LIRC
  configuration

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: lirc

  I'm using Ubuntu 9.04.
  The Remote control of the TV card "Tevion/KWorld DVB-T 220RF" is not listed 
in the LIRC config tool.

  When I do "sudo dpkg-reconfigure lirc" the config tool shows a list of
  remotes but the "Tevion/KWorld DVB-T 220" remote is not listed.

  This is the dmesg about the card:
  [9.036205] saa7133[0]: found at :01:06.0, rev: 209, irq: 19, latency: 
64, mmio: 0xd800
  [9.036211] saa7133[0]: subsystem: 17de:7201, board: Tevion/KWorld DVB-T 
220RF [card=88,autodetected]
  [9.036239] saa7133[0]: board init: gpio is 100
  [9.184177] saa7133[0]: i2c eeprom 00: de 17 01 72 ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184184] saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184191] saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184197] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184203] saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184209] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184215] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184221] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184227] saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184233] saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184240] saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184246] saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184252] saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184258] saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184264] saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.184270] saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff
  [9.264281] tuner' 0-004b: chip found @ 0x96 (saa7133[0])
  [9.352124] tda829x 0-004b: setting tuner address to 61
  [9.420189] tda829x 0-004b: type set to tda8290+75a
  [   13.252673] saa7133[0]: registered device video0 [v4l2]
  [   13.252763] saa7133[0]: registered device vbi0
  [   13.252848] saa7133[0]: registered device radio0
  [   13.320375] saa7134 ALSA driver for DMA sound loaded
  [   13.320405] saa7133[0]/alsa: saa7133[0] at 0xd800 irq 19 registered as 
card -2
  [   13.428814] dvb_init() allocating 1 frontend
  [   13.532600] DVB: registering new adapter (saa7133[0])
  [   13.532605] DVB: registering adapter 0 frontend 3420965 (Philips TDA10046H 
DVB-T)...
  [   15.848168] tda1004x: timeout waiting for DSP ready
  [   15.888059] tda1004x: found firmware revision 0 -- invalid
  [   15.888062] tda1004x: trying to boot from eeprom
  [   18.216658] tda1004x: timeout waiting for DSP ready
  [   18.256643] tda1004x: found firmware revision 0 -- invalid
  [   18.256646] tda1004x: waiting for firmware upload...
  [   18.256650] saa7134 :01:06.0: firmware: requesting dvb-fe-tda10046.fw
  [   31.236167] tda1004x: found firmware revision 20 -- ok
  [14579.488431] lirc_dev: IR Remote Control driver registered, major 61 
  [14579.496329] lirc_dev: lirc_register_plugin: sample_rate: 0
  [14579.496488] lirc_sir: I/O port 0x02f8, IRQ 3.
  [14579.496499] lirc_sir: Installed.
  [14597.830985] lirc_sir: Uninstalled.
  [14617.903160] lirc_dev: IR Remote Control driver registered, major 61 
  [14617.908865] lirc_dev: lirc_register_plugin: sample_rate: 0
  [14617.909004] lirc_sir: I/O port 0x02f8, IRQ 3.
  [14617.909016] lirc_sir: Installed.
  [16002.854354] lirc_sir: Uninstalled.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 488080] Re: add support for IO Data MCE Remote

[Alec Leamas]

This is basaically a support request. Please refer to the upstream
mailing list at http://sf.nety/p/lirc; see also the configuration guide
at http://lirc.org/html/configuration-guide.html (which refers to latest
version 0.9.4 in zesty)

Closing bug

** Changed in: lirc (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/488080

Title:
  add support for IO Data MCE Remote

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: lirc

  Mythbuntu 9.10

  Remote control - IO Data MCE Remote

  Device ID : 0609:0338 SMK Manufacturing, Inc

  This is a Japanese Windows Vista remote control with USB receiver.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 484796] Re: After some time the module lirc_mceusb stops functioning

[Alec Leamas]

Belongs to kernel, media subsystem, but will most likley expire

** Package changed: lirc (Ubuntu) => linux-lts-vivid (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/484796

Title:
  After some time the module lirc_mceusb stops functioning

Status in linux-lts-vivid package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  me@ubu:~$ lsb_release -rd
  Description:  Ubuntu 9.10
  Release:  9.10

  me@ubu:~$ apt-cache policy lirc
  lirc:
Installed: 0.8.6-0ubuntu2
Candidate: 0.8.6-0ubuntu2
Version table:
   *** 0.8.6-0ubuntu2 0
  500 http://ftp.tudelft.nl karmic/universe Packages
  100 /var/lib/dpkg/status

  Running a server version with a minimal gnome config.
  Server is a AMD 64B quadcore with 8GB internal mem.
  lspci->
  00:00.0 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory 
Controller (rev a2)
  00:01.0 ISA bridge: nVidia Corporation MCP78S [GeForce 8200] LPC Bridge (rev 
a2)
  00:01.1 SMBus: nVidia Corporation MCP78S [GeForce 8200] SMBus (rev a1)
  00:01.2 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory 
Controller (rev a1)
  00:01.3 Co-processor: nVidia Corporation MCP78S [GeForce 8200] Co-Processor 
(rev a2)
  00:01.4 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory 
Controller (rev a1)
  00:02.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 
Controller (rev a1)
  00:02.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 
Controller (rev a1)
  00:04.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 
Controller (rev a1)
  00:04.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 
Controller (rev a1)
  00:06.0 IDE interface: nVidia Corporation MCP78S [GeForce 8200] IDE (rev a1)
  00:07.0 Audio device: nVidia Corporation MCP72XE/MCP72P/MCP78U/MCP78S High 
Definition Audio (rev a1)
  00:08.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev 
a1)
  00:09.0 RAID bus controller: nVidia Corporation MCP78S [GeForce 8200] SATA 
Controller (RAID mode) (rev a2)
  00:0a.0 Ethernet controller: nVidia Corporation MCP77 Ethernet (rev a2)
  00:0b.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express 
Bridge (rev a1)
  00:10.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express 
Bridge (rev a1)
  00:12.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express 
Bridge (rev a1)
  00:18.0 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, 
Sempron] HyperTransport Configuration
  00:18.1 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, 
Sempron] Address Map
  00:18.2 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, 
Sempron] DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, 
Sempron] Miscellaneous Control
  00:18.4 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, 
Sempron] Link Control
  01:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)
  01:07.0 Ethernet controller: 3Com Corporation 3c900B-TPO Etherlink XL 
[Cyclone] (rev 04)
  02:00.0 VGA compatible controller: nVidia Corporation C77 [GeForce 8200] (rev 
a2)

  lsmod->
  Module  Size  Used by
  joydev 12928  0
  hid_sunplus 2464  0
  nls_cp437   6976  0
  isofs  36424  0
  lirc_mceusb17668  0
  tun16992  6
  iptable_mangle  4192  1
  nf_conntrack_ftp9016  0
  ipt_MASQUERADE  2944  1
  iptable_nat 6656  1
  nf_nat 22164  2 ipt_MASQUERADE,iptable_nat
  nf_conntrack_ipv4  16376  6 iptable_nat,nf_nat
  nf_defrag_ipv4  2400  1 nf_conntrack_ipv4
  xt_state2432  3
  nf_conntrack   80832  6 
nf_conntrack_ftp,ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state
  ipt_REJECT  3584  0
  xt_tcpudp   3616  99
  kvm_amd41556  10
  kvm   190552  1 kvm_amd
  bridge 56384  0
  stp 3012  1 bridge
  snd_hda_codec_via  35360  1
  iptable_filter  3872  1
  snd_hda_intel  31880  1
  snd_hda_codec  87456  2 snd_hda_codec_via,snd_hda_intel
  ip_tables  21168  3 iptable_mangle,iptable_nat,iptable_filter
  nvidia   9620040  28
  snd_hwdep   9128  1 snd_hda_codec
  shpchp 37756  0
  snd_pcm92296  2 snd_hda_intel,snd_hda_codec
  snd_timer  26928  1 snd_pcm
  snd76808  7 
snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
  soundcore   9088  1 snd
  snd_page_alloc 10928  2 snd_hda_intel,snd_pcm
  i2c_nforce2 8168  0
  x_tables   25768  6 

[Desktop-packages] [Bug 484796] Re: After some time the module lirc_mceusb stops functioning

[Alec Leamas]

Is this bug still valid? it needs to be tested on a more recent ub
ubuntu version to be processed. If you are still interested in this
byug, please let us know.

Re-assigning to kernel, since this is about the kernel module.

** Changed in: lirc (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/484796

Title:
  After some time the module lirc_mceusb stops functioning

Status in linux-lts-vivid package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  me@ubu:~$ lsb_release -rd
  Description:  Ubuntu 9.10
  Release:  9.10

  me@ubu:~$ apt-cache policy lirc
  lirc:
Installed: 0.8.6-0ubuntu2
Candidate: 0.8.6-0ubuntu2
Version table:
   *** 0.8.6-0ubuntu2 0
  500 http://ftp.tudelft.nl karmic/universe Packages
  100 /var/lib/dpkg/status

  Running a server version with a minimal gnome config.
  Server is a AMD 64B quadcore with 8GB internal mem.
  lspci->
  00:00.0 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory 
Controller (rev a2)
  00:01.0 ISA bridge: nVidia Corporation MCP78S [GeForce 8200] LPC Bridge (rev 
a2)
  00:01.1 SMBus: nVidia Corporation MCP78S [GeForce 8200] SMBus (rev a1)
  00:01.2 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory 
Controller (rev a1)
  00:01.3 Co-processor: nVidia Corporation MCP78S [GeForce 8200] Co-Processor 
(rev a2)
  00:01.4 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory 
Controller (rev a1)
  00:02.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 
Controller (rev a1)
  00:02.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 
Controller (rev a1)
  00:04.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 
Controller (rev a1)
  00:04.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 
Controller (rev a1)
  00:06.0 IDE interface: nVidia Corporation MCP78S [GeForce 8200] IDE (rev a1)
  00:07.0 Audio device: nVidia Corporation MCP72XE/MCP72P/MCP78U/MCP78S High 
Definition Audio (rev a1)
  00:08.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev 
a1)
  00:09.0 RAID bus controller: nVidia Corporation MCP78S [GeForce 8200] SATA 
Controller (RAID mode) (rev a2)
  00:0a.0 Ethernet controller: nVidia Corporation MCP77 Ethernet (rev a2)
  00:0b.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express 
Bridge (rev a1)
  00:10.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express 
Bridge (rev a1)
  00:12.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express 
Bridge (rev a1)
  00:18.0 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, 
Sempron] HyperTransport Configuration
  00:18.1 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, 
Sempron] Address Map
  00:18.2 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, 
Sempron] DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, 
Sempron] Miscellaneous Control
  00:18.4 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, 
Sempron] Link Control
  01:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)
  01:07.0 Ethernet controller: 3Com Corporation 3c900B-TPO Etherlink XL 
[Cyclone] (rev 04)
  02:00.0 VGA compatible controller: nVidia Corporation C77 [GeForce 8200] (rev 
a2)

  lsmod->
  Module  Size  Used by
  joydev 12928  0
  hid_sunplus 2464  0
  nls_cp437   6976  0
  isofs  36424  0
  lirc_mceusb17668  0
  tun16992  6
  iptable_mangle  4192  1
  nf_conntrack_ftp9016  0
  ipt_MASQUERADE  2944  1
  iptable_nat 6656  1
  nf_nat 22164  2 ipt_MASQUERADE,iptable_nat
  nf_conntrack_ipv4  16376  6 iptable_nat,nf_nat
  nf_defrag_ipv4  2400  1 nf_conntrack_ipv4
  xt_state2432  3
  nf_conntrack   80832  6 
nf_conntrack_ftp,ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state
  ipt_REJECT  3584  0
  xt_tcpudp   3616  99
  kvm_amd41556  10
  kvm   190552  1 kvm_amd
  bridge 56384  0
  stp 3012  1 bridge
  snd_hda_codec_via  35360  1
  iptable_filter  3872  1
  snd_hda_intel  31880  1
  snd_hda_codec  87456  2 snd_hda_codec_via,snd_hda_intel
  ip_tables  21168  3 iptable_mangle,iptable_nat,iptable_filter
  nvidia   9620040  28
  snd_hwdep   9128  1 snd_hda_codec
  shpchp 37756  0
  snd_pcm92296  2 snd_hda_intel,snd_hda_codec
  snd_timer  26928  1 snd_pcm
  snd76808  7 
snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
  

[Desktop-packages] [Bug 379446] Re: pixelview playtv pro 2 remote not working

[Alec Leamas]

This bug has too little information to be handled:

  - what does irreccord say?
  - what does dmesg say?

If you are till  interested in this bug, please provide some more info
along these lines

** Changed in: lirc (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/379446

Title:
  pixelview playtv pro 2 remote not working

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  hi i have a H-338(as on back of the remote) remote which comes with
  playtv pro 2

  bttv config
  # i2c
  alias char-major-89 i2c-devb
  options i2c-algo-bit bit_test=1
  # bttv
  alias char-major-81 videodev
  alias char-major-81-0 bttv
  # My TV Card
  options bttv card=70 tuner=43 radio=1

  and i tried irrecord but no luck !

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 398362] Re: Unsupported Remote for Mythbuntu 9.04 - Pinnacle HDTV Pro Stick (801e SE)

[Alec Leamas]

Any news here, or vcan we close this bug?

** Changed in: lirc (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/398362

Title:
  Unsupported Remote for Mythbuntu 9.04 - Pinnacle HDTV Pro Stick (801e
  SE)

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  1) Release: Ubuntu version 9.04 (via mythbuntu)

  2) Package: Lirc
  Installed: 0.8.4a-0ubuntu5
  Candidate: 0.8.4a-0ubuntu5
  Version table: 
  *** 0.8.4a-0ubuntu5 0
   500 http://us.archive.ubuntu.com jaunty/universe Packages
   100 /bar/lib/dpkg/status

  3) Automatic support through Mythbuntu Control Centre setup.

  4) No remote listed.

  Furthermore, the remote is not recognized by "irw" or "irxevent" even
  after copying in known working (from other distro) lircd.conf and
  lircrc files.

  Mythbuntu Installation Manual requested that I submit a bug report.  I
  can supply the working lircd.conf and lircrc files if that would help
  for implementation purposes.  Please contact me at my email address.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 376244] Re: lirc does not work with avermedia m115 card remote

[Alec Leamas]

If you are still interested in this bug, it needs to be tested with the
new 0.9.4c release, basically on a zesty host.

In the updated package you could use mode2 using --driver devinput to
check whether the kernel decodes the signals or not. If it doesn't, it
might be perfectly possible to configure lirc to use the raw data
instead of the /dev/input devices.

In short, here is not enough to qualify for a bug. If you are still
interested in this please refer to the mailing list at
http://sf.net/p/lirc for help configuring lirc in situations where the
kernel decoding does not work. See also the configuration guide at
http://lirc.org/html/configuration-guide.html.

** Changed in: lirc (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/376244

Title:
  lirc does not work with avermedia m115 card remote

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: lirc

  Hi,

  I have an Avermedia M115 mini-pci-e TV card on an Acer Aspire 5652.
  The card has an infrared device which seems to work partially.  I can
  get some of the keys like 1-2-3...9-OK-VolUP,VolDown,Mute etc.

  System is Ubuntu 9.04, newly installed. (i disabled the saa7134 module
  as it's buggy at the moment)

  On the other hand, most of the special keys on the IR remote don't work, I 
receive such messages in dmesg output:
   atkbd.c: Unknown key pressed (translated set 2, code 0x9e on 
isa0060/serio0).
   atkbd.c: Use 'setkeycodes e01e ' to make it known.

  I have the following device in the lshal output, which seems to be
  related to the tv card:

  udi = '/org/freedesktop/Hal/devices/computer_logicaldev_input_0'
info.addons.singleton = {'hald-addon-input'} (string list)
info.callouts.add = {'debian-setup-keyboard'} (string list)
info.capabilities = {'input', 'input.keys', 'button'} (string list)
info.category = 'input'  (string)
info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
info.product = 'Video Bus'  (string)
info.subsystem = 'input'  (string)
info.udi = '/org/freedesktop/Hal/devices/computer_logicaldev_input_0'  
(string)
input.device = '/dev/input/event6'  (string)
input.product = 'Video Bus'  (string)
input.x11_driver = 'evdev'  (string)
input.xkb.layout = 'us'  (string)
input.xkb.model = 'pc105'  (string)
input.xkb.rules = 'evdev'  (string)
linux.device_file = '/dev/input/event6'  (string)
linux.hotplug_type = 2  (0x2)  (int)
linux.subsystem = 'input'  (string)
linux.sysfs_path = 
'/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/device:02/input/input6/event6'
  (string)

  cat /dev/input/event6 is always silent, except for the already
  recognized keys, which do write on the console:

  root@enterprise:/# cat /dev/input/event6 
  1123560
  1234567890
  ^C

  I guess the first step is to get the kernel recognize those keys. But
  if it's going to be manual, that would be a hard work due to a total
  of 48 keys on the remote (some working).

  Note: no input devices are configured in xorg.conf, nvidia driver is
  loaded to do it automatically. Xorg.0.log shows nothing about the
  remote getting configured.

  Any clues?

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 464661] Re: imon_knob no input in 9.10

[Alec Leamas]

Have you still any problem with this? Otherwise, without further input,
let's close this bug.

** Changed in: lirc (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/464661

Title:
  imon_knob no input in 9.10

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  Support for Soundgraph Imon knob is broken in Ubuntu Karmic 9.10.  Irexec and 
irw do not get any input from the device, though /dev/lirc0 receives the input 
(verified with cat /dev/lirc0).  Also irrecord and mode2 both get input.  
Retested on fresh install of 9.04 to verify same steps are being taken to set 
up lirc, but they do not work in 9.10.  Also tested with lircd.conf copied from 
working setup on 9.04, no good.

  Synaptic -> install lirc.  Select imon_knob.  Restart lirc daemon.  Launch 
irw, can verify input from remote on 9.04, exact same steps yield no irw input 
on 9.10.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 657954] Re: No default remote configuration was included for Hauppauge Nova-T 500; You will need to include your own custom configuration for this remote

[Alec Leamas]

Kernel, possibly wrong version... media subsystem, though.

** Package changed: lirc (Ubuntu) => linux-meta-lts-xenial (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/657954

Title:
  No default remote configuration was included for Hauppauge Nova-T 500;
  You will need to include your own custom configuration for this remote

Status in linux-meta-lts-xenial package in Ubuntu:
  New

Bug description:
  I have a USB WinTV Nova-T 500 of Hauppauge, this device is detected
  proprely by Ubuntu 10.10 but the remote controlling does not work. The
  remote controll is of Anubis(made in China)!!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/657954/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 657954] Re: No default remote configuration was included for Hauppauge Nova-T 500; You will need to include your own custom configuration for this remote

[Alec Leamas]

This is basically about the kernel modules. Re-assigning to kernel. My
own opinion is that the bug should be closed as expired unless thee is
more input

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/657954

Title:
  No default remote configuration was included for Hauppauge Nova-T 500;
  You will need to include your own custom configuration for this remote

Status in linux-meta-lts-xenial package in Ubuntu:
  New

Bug description:
  I have a USB WinTV Nova-T 500 of Hauppauge, this device is detected
  proprely by Ubuntu 10.10 but the remote controlling does not work. The
  remote controll is of Anubis(made in China)!!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/657954/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 371244] Re: Add support for Antec Zeris Multimedia Station Basic

[Alec Leamas]

This is not a bug but a support request. If you are still interested in
this bug, please refer to the upstream mailing list at
http://sf.net/p/lirc.

** Changed in: lirc (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/371244

Title:
  Add support for Antec Zeris Multimedia Station Basic

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: lirc

  I purchased the  Antec Zeris Multimedia Station Basic Reciever with
  RM100 remote

  IR: Antec Multimedia Station Basic w/ RM100 remote. Can fine here: 
http://www.newegg.com/Product/Product.aspx?Item=N82E16811999191=antec%20basic
  VendorID=15c2; 
  ProductID=0043;
  Manufacture=Soundgraph, Inc.

  OS: Ubuntu 9.04 Jaunty x86_amd64
  kernel: 2.6.28-11-generic
  Packages tried: 
Synaptic 0.8.4a-0ubuntu5(jaunty)
CVS install 0.8.4

  I expected to install lirc and make a few configuration changes in some files 
and the remote would let me contol XBMC.
  I've been at it for over 24+ hours over 4 days. I just don't understand what 
I need to do.

  I would like this device to be supported out-of-the-box for lirc, and
  I am posting this bug since it is recommended to do so when trying new
  hardware/version with LIRC.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 654160] Re: mceusb RC not working

[Alec Leamas]

We need more info in order to advance this bug.

First, what is the "IR Tray"?. This is certainly not part of  the lirc
package.

Secondly, testing with mode2(1) will reveal if this is about the kernel
not delivering timing ingo, or about a lircd failure.

Third, if the problem persists it needs to be checked against the latest
lirc 0.9.4c and also an updated kernel.

If you are still interested in this bug, could you please do this
testing?

** Changed in: lirc (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/654160

Title:
  mceusb RC not working

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  Sorry, not sure if that is the exactly correct package.

  The correct kernel modual loads: lirc_mceusb
  lircd loads ok
  The IR tray icon shows 3 mce remotes when I only have one.

  I've tried using the tray icon to configure all the remotes but when I
  try to use the remote with an application such as vlc nothing happens

  I tried testing the remote with irw but when I press buttons nothing is 
output to the terminal.
  I had this remote working with Kubuntu 10.4 after having added the device id 
(Bus 007 Device 002: ID 0609:0338 SMK Manufacturing, Inc.) in the drive source 
and recompiling. This device is now in the lirc 0.8.7~pre3 source included in 
Kubuntu 10.10

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: lirc 0.8.7~pre3-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  Architecture: amd64
  Date: Mon Oct  4 00:46:59 2010
  InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
  ProcEnviron:
   LANGUAGE=
   LANG=en_AU.utf8
   SHELL=/bin/bash
  SourcePackage: lirc

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 783202] Re: lircmd is not started properly by lirc init script when devinput is used

[Alec Leamas]

The bug is five years old, the buggy init scripts described are not
present in current systemd start up configuration and the patches does
thus not apply. I'm closing this one, referring to the 0.9.4c changelog.

lirc (0.9.4b-0.1) experimental; urgency=medium

  * Non-maintainer upload.
  * First shot on major upstream updates.
- Re-packaged from scratch based on new dh primitives.
- Thanks for help on debian-mentors!
  * New upstream release 0.9.4
- Release 0.9.1 .. 0.9.3 was never packaged.
- Old 'lirc' service split into separate systemd services:
  lircd.service, lircmd.service and irexec.service.
- Remote definitions moved out of lirc to new project
  lirc-remotes; affects large number of LP issues.
- Builds also on FreeBSD 10.3.
- Fixes "Not updated to last version" (Closes: #777199),
  LP: #1443590.
- Fixes "Default device for mode2 is /dev/lirc" (Closes: #702140).
- Fixes "/var/run/lirc contents disappear..." (Closes: #676343).
- Fixes "lircrcd segfaults" (Closes: #780062).
- Fixes "'/etc/init.d/lirc restart' is broken" (Closes: #782091).
- Fixes "Prompting due to modified conffiles..." (Closes: #655969).
- Fixes "LIRC installs bad udev rule" (Closes: #804397),
  users depending on this rule will need to explicitly start lircd.
- Fixes "lirc init script can create circular symlinks", LP: #698007.
- Fixes "Update Uploaders List (Closes: #762554).
- Fixes "Please switch to libftdi1" (Closes:  #810370).
- Fixes LP: #153457 "iguanaIR support not functional".
- Fixes LP: #460027 "using lirc init script restart function fails
  sometimes".
- Fixes LP: #499588 "lirc udev rule causes unreliable startup".
- Fixes LP: #567519 "lircd(8) mentions non-existent
  /dev/input/uinput".
- Fixes LP: #1029604 "mce remote doesn't work due to out of date
  lircd.conf.devinput".
- Fixes LP: #1312287 "lircd start problem".
  * The built-in irman support is moved to the lirc-drv-irman package.
  * Revised package structure: keep old liblircclient0 (renamed to
liblirc-client0). Adding new packages liblirc0, liblirc-dev and
lirc-doc. Former liblircclient-dev merged into new liblirc-dev.
  * Don't overwrite existing lircd.conf file.
  * Ship sysV scripts from the svn tree [Stefan Lippers-Hollmann]
  * Add handling of obsolete 0.9.0 udev rule restarting lircd
  * Old lircd output socket link /dev/lirc dropped. Use
/var/run/lirc/lircd.
  * Updated copyright
  * Update compiler flags: -Wl,as-needed + hardening
[Stefan Lippers-Hollmann]
  * Avoid negative architecture deps like [!hurd] (Closes: #634807)
[Stefan Lippers-Hollmann]
  * Add patch 0007-tools-remove-configs-symlink.patch + explicit link
to walk around #801719 (dh_python3 shortcomings).
  * Last parts of libirman dependencies removed.
  * Changing Vcs-* headers to point to upstream packaging branch.
  * Fixes existing large number of upgrade bugs.
  * Enhance hardening flags.
  * Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg
therein.
  * Tested (build-wise) on stretch and sid.

 -- Alec Leamas  <leamas.a...@gmail.com>  Thu, 26 May 2016 11:14:25
+0100


** Changed in: lirc (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/783202

Title:
  lircmd is not started properly by lirc init script when devinput is
  used

Status in lirc package in Ubuntu:
  Fix Committed

Bug description:
  Binary package hint: lirc

  lircmd (lirc mouse daemon) must be started with the -u option when
  devinput is used.

  This is not done correctly by the /etc/init.d/lirc startup script if
  the lircmd is started by specifiying

  START_LIRCMD="true"

  in /etc/lirc/hardware.conf.

  If /etc/init.d/lirc:

if [ "$START_LIRCMD" = "true" ]; then
[ -d "/var/run/lirc" ] || mkdir -p "/var/run/lirc"
log_daemon_msg "Starting remote control mouse daemon : 
LIRCMD "
start-stop-daemon --start --quiet --oknodo --exec 
/usr/sbin/lircmd < /dev/null
log_end_msg $?
fi

  is changed to

if [ "$START_LIRCMD" = "true" ]; then
[ -d "/var/run/lirc" ] || mkdir -p "/var/run/lirc"
log_daemon_msg "Starting remote control mouse daemon : 
LIRCMD "
start-stop-daemon --start --quiet --oknodo --exec 
/usr/sbin/lircmd -- -u < /dev/null
log_end_msg $?
fi

  it works i

[Desktop-packages] [Bug 311890] Re: imon driver (or IT87 driver) does not work, irw crashes lircd

[Alec Leamas]

The last note in this bug is five years old, end both the kernel and
lirc startup sequence is heavily changed. Could you please test this bug
on upcoming zesty and lirc0.9.4c if you are still interested in this
bug?

Setting status to Incomplete, since without input on status on current
code we cannot triage this bug.

When testing, the primary test tool is mode2 - using that with correct
--driver and --device should reveal if this problem in in the kernel or
in lircd. Please also raise the lircd loglevel to 'trace' and submit the
lircd logs.

** Changed in: lirc (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/311890

Title:
  imon driver (or IT87 driver) does not work, irw crashes lircd

Status in lirc package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: lirc

  Description:Ubuntu 8.10
  Release:8.10
  lirc 0.8.3-0ubuntu2 Linux Infra-red Remote Control support

  oot@mediapc:~# dmesg | grep imon
  [ 334.839718] lirc_imon: Driver for Soundgraph iMON MultiMedia IR/VFD w/imon 
pad2keys patch, v0.3p2k
  [ 334.839733] lirc_imon: Venky Raju 
  [ 334.841034] usbcore: registered new interface driver lirc_imon 

  root@mediapc:~# lsmod | grep lirc
  lirc_imon 23052 0
  lirc_dev 20020 1 lirc_imon
  usbcore 148848 7 lirc_imon,usbhid,usb_storage,libusual,ohci_hcd,ehc i_hcd 

  When I run irw it simply exits the 1st time without any message, the
  second time it errors and the lirc daemon crashes.

  root@mediapc:~# /etc/init.d/lirc restart
  * Stopping remote control daemon(s): LIRC [ OK ]
  * Loading LIRC modules [ OK ]
  * Starting remote control daemon(s) : LIRC [ OK ]
  root@mediapc:~# irw
  root@mediapc:~# irw
  connect: Connection refused
  root@mediapc:~# /etc/init.d/lirc restart
  * Stopping remote control daemon(s): LIRC [fail]
  * Loading LIRC modules [ OK ]
  * Starting remote control daemon(s) : LIRC [ OK ]
  I do not have a /dev/lirc0 but I do have /dev/lircd.
  Running irw /dev/lircd does not help.

  Mode 2 errors:

  root@mediapc:~# mode2
  mode2: error opening /dev/lirc
  mode2: No such file or directory

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 463050] Re: lirc does not configure IR transmitter properly

[Alec Leamas]

These  links makes no sense, at least not on a reasonable updated lirc.
The /dev/lirc? devices are lircd input stuff whereas the /var/run//lircd
devices are lircd output sockets. Linking input to output is, well, not
ideal.

Partly due to the the bad linking, partly due to the sheer age I'mn
closing this one.

** Changed in: lirc (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/463050

Title:
  lirc does not configure IR transmitter properly

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: lirc

  I am using Kubuntu Karmic Koala 9.10
  I have a Hauppauge 350 and IR blaster, my lirc is setup with:
  - Hauppauge HVR-1300
  - Serial Port (UART) : Motorola cable box

  When the the script /etc/init.d/lirc start it automatically links:
  lrwxrwxrwx 1 root root 19 2009-10-24 21:36 /dev/lircd -> /var/run/lirc/lircd
  lrwxrwxrwx 1 root root 20 2009-10-24 21:39 /dev/lircd1 -> /var/run/lirc/lircd

   instead of
  lrwxrwxrwx 1 root root 19 2009-10-24 21:36 /dev/lircd -> /var/run/lirc/lircd
  lrwxrwxrwx 1 root root 20 2009-10-24 21:39 /dev/lircd1 -> /var/run/lirc/lircd1

  
  I had to change it in /etc/init.d/lirc (see attached)

  ProblemType: Bug
  Architecture: i386
  Date: Wed Oct 28 18:58:07 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release Candidate i386 
(20091020.2)
  NonfreeKernelModules: nvidia
  Package: lirc 0.8.6-0ubuntu2
  ProcEnviron:
   LANGUAGE=
   LANG=en_CA.UTF-8
   SHELL=/bin/zsh
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: lirc
  Uname: Linux 2.6.31-14-generic i686

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1065138] Re: Module lirc_wpc8769l not provided

[Alec Leamas]

Rwe-assigning to lernel. After all, missing drivers is a kernel issue.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1065138

Title:
  Module lirc_wpc8769l not provided

Status in linux-meta-lts-xenial package in Ubuntu:
  Confirmed
Status in Debian:
  New

Bug description:
  This driver was provided by lirc-modules-source until natty.
  Now lirc modules are moved to the kernel, by the way there is not any kernel 
package including lirc_wpc8769l.
  It was forgotten by ubuntu packagers or it was rejected for some reason?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1065138/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1065138] Re: Module lirc_wpc8769l not provided

[Alec Leamas]

Moving to kernel,, media subsystem.   My own opinion is that this is
wontfix

** Package changed: lirc (Ubuntu) => linux-meta-lts-xenial (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1065138

Title:
  Module lirc_wpc8769l not provided

Status in linux-meta-lts-xenial package in Ubuntu:
  Confirmed
Status in Debian:
  New

Bug description:
  This driver was provided by lirc-modules-source until natty.
  Now lirc modules are moved to the kernel, by the way there is not any kernel 
package including lirc_wpc8769l.
  It was forgotten by ubuntu packagers or it was rejected for some reason?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1065138/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 574432] Re: Lirc unable to initialise IR portion of Mplay Blast VFD (Zalman HD-135 case)

[Alec Leamas]

Probab,ly  the  kernel,  put perhaps wrong version. Sorry. meda
subsystem, though.

** Package changed: lirc (Ubuntu) => linux-meta-lts-trusty (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/574432

Title:
  Lirc unable to initialise IR portion of Mplay Blast VFD (Zalman HD-135
  case)

Status in linux-meta-lts-trusty package in Ubuntu:
  New

Bug description:
  Binary package hint: lirc

  Re-written for clarity;

  The 'VL-System Mplay Blast' combined VFD/IR unit in the Zalman HD-135
  case is functional with Lirc using the HD44780 driver with seemingly
  one caveat. Lirc seems to be unable to physically initialise the IR
  portion of the unit after it is powered up before it can be used.

  The only way to do this is to boot into a Windows VM (with the
  display's usb device attached), run the Windows Mplay Home-Centre
  software supplied with the case which initialises the IR portion of
  the display (the red led on the display goes unlit) and then closing
  the VM (not shutting it down as this un-initialises it again) Lirc is
  then able to use the IR device as intended. If power is removed from
  the display (i.e physically unplugging the machine) then this process
  will need to be performed again, the display starts with the IR led
  lit (uninitialised) and doesn't go out on boot until the Windows
  software is run.

  Running Lcdproc (possibly with certain options, I've read maybe
  relating to enabling the keypad) seemingly used to be able to send the
  right initialisation commands to the unit when it initialised the lcd
  portion of the unit so Lirc would function without having to go
  through the Windows software step above. Unfortunately now for one
  reason or another this doesn't seem to work any more.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: lirc 0.8.6-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon May  3 13:23:26 2010
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: lirc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-trusty/+bug/574432/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 574432] Re: Lirc unable to initialise IR portion of Mplay Blast VFD (Zalman HD-135 case)

[Alec Leamas]

Re-assigning to kernel, this is seemingly about kernel modules and
mutexes..

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/574432

Title:
  Lirc unable to initialise IR portion of Mplay Blast VFD (Zalman HD-135
  case)

Status in linux-meta-lts-trusty package in Ubuntu:
  New

Bug description:
  Binary package hint: lirc

  Re-written for clarity;

  The 'VL-System Mplay Blast' combined VFD/IR unit in the Zalman HD-135
  case is functional with Lirc using the HD44780 driver with seemingly
  one caveat. Lirc seems to be unable to physically initialise the IR
  portion of the unit after it is powered up before it can be used.

  The only way to do this is to boot into a Windows VM (with the
  display's usb device attached), run the Windows Mplay Home-Centre
  software supplied with the case which initialises the IR portion of
  the display (the red led on the display goes unlit) and then closing
  the VM (not shutting it down as this un-initialises it again) Lirc is
  then able to use the IR device as intended. If power is removed from
  the display (i.e physically unplugging the machine) then this process
  will need to be performed again, the display starts with the IR led
  lit (uninitialised) and doesn't go out on boot until the Windows
  software is run.

  Running Lcdproc (possibly with certain options, I've read maybe
  relating to enabling the keypad) seemingly used to be able to send the
  right initialisation commands to the unit when it initialised the lcd
  portion of the unit so Lirc would function without having to go
  through the Windows software step above. Unfortunately now for one
  reason or another this doesn't seem to work any more.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: lirc 0.8.6-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon May  3 13:23:26 2010
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: lirc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-trusty/+bug/574432/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 491860] Re: lirc_mceusb doesn't recognize eHome IR receiver

[Alec Leamas]

Definitely the kernel (meda subsystem), but perhaps wrong  version.
Sorry, rookie doing my best...

** Package changed: lirc (Ubuntu) => linux-meta-lts-trusty (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/491860

Title:
  lirc_mceusb doesn't recognize eHome IR receiver

Status in linux-meta-lts-trusty package in Ubuntu:
  New

Bug description:
  Binary package hint: lirc

  lsb_release -rd:
  Description:  Ubuntu 9.10
  Release:  9.10 

  dpkg -l | grep lirc:
  ii  liblircclient00.8.6-0ubuntu2  
   infra-red remote control support - client li
  ii  lirc  0.8.6-0ubuntu2  
   infra-red remote control support
  ii  lirc-modules-source   0.8.6-0ubuntu2  
   infra-red remote control support - kernel mo
  ii  lirc-x0.8.6-0ubuntu2  
   infra-red remote control support - X utiliti 

  here's some lsusb output: (lsusb -vvs 1:2)
  Bus 001 Device 002: ID 0bda:0161 Realtek Semiconductor Corp. Mass Stroage 
Device
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   2.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize064
idVendor   0x0bda Realtek Semiconductor Corp.
idProduct  0x0161 Mass Stroage Device
bcdDevice   61.10
iManufacturer   1 Generic
iProduct2 USB2.0-CRW
iSerial 3 200708180
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength  139
  bNumInterfaces  3
  bConfigurationValue 1
  iConfiguration  4 CARD READER
  bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
  MaxPower  500mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   3
bInterfaceClass11 Chip/SmartCard
bInterfaceSubClass  0 
bInterfaceProtocol  0 
iInterface  6 Smart Card Reader Interface
** UNRECOGNIZED:  36 21 10 01 00 07 03 00 00 00 a6 0e 00 00 4c 1d 00 00 
00 60 27 00 00 b4 c4 04 00 00 fe 00 00 00 00 00 00 00 00 00 00 00 30 00 01 00 
0f 01 00 00 00 00 00 00 00 01
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x83  EP 3 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0040  1x 64 bytes
  bInterval   8
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x05  EP 5 OUT
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0200  1x 512 bytes
  bInterval   0
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x86  EP 6 IN
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0200  1x 512 bytes
  bInterval   0
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber1
bAlternateSetting   0
bNumEndpoints   2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass  6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
iInterface  5 Bulk-In, Bulk-Out, Interface
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x01  EP 1 OUT
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0200  1x 512 bytes
  bInterval   0
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x82  EP 2 IN
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data