Issues Encountered installing lirc on new 20.04 device

Bug #1891079 reported by John W. Burroughs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lirc (Debian)
Fix Released
Unknown
lirc (Ubuntu)
New
High
Unassigned

Bug Description

** The first issue: Missing module and Deprecated syntax

While installing lirc:

If I run at the command line: sudo apt install lirc, it installs
lirc version 0.10.1-6.1ubuntu1.1 successfully.

However, when I run "sudo lirc-setup", I get the following dump;

-------------------------------------------------------------------------
/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_control.py:13: PyGIWarning: Gtk was imported without specifying a v
ersion first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk # pylint: disable=no-name-in-module
/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_view.py:14: PyGIWarning: Vte was imported without specifying a vers
ion first. Use gi.require_version('Vte', '2.91') before import to ensure that the right version gets loaded.
  from gi.repository import Vte # pylint: disable=no-name-in-module
/usr/lib/python3/dist-packages/lirc/database.py:135: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the d
efault Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
  cf = yaml.load(f.read())
/usr/lib/python3/dist-packages/lirc/database.py:69: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the de
fault Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
  cf = yaml.load(f.read())
/usr/lib/python3/dist-packages/lirc/database.py:142: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the d
efault Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
  cf = yaml.load(f.read())
/usr/lib/python3/dist-packages/lirc/database.py:161: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the d
efault Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
  cf = yaml.load(f.read())
jwb@richese:~$ sudo lirc-setup
[sudo] password for jwb:
/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_control.py:13: PyGIWarning: Gtk was imported without specifying a v
ersion first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk # pylint: disable=no-name-in-module
Traceback (most recent call last):
  File "/usr/bin/lirc-setup", line 16, in <module>
    import mvc_control
  File "/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_control.py", line 16, in <module>
    import choosers
  File "/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/choosers.py", line 11, in <module>
    import mvc_model
  File "/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_model.py", line 14, in <module>
    from lirc.database import Database
  File "/usr/lib/python3/dist-packages/lirc/__init__.py", line 7, in <module>
    from .client import get_default_lircrc_path
  File "/usr/lib/python3/dist-packages/lirc/client.py", line 38, in <module>
    import _client
ModuleNotFoundError: No module named '_client'
-------------------------------------------------------------------------

The last line "ModuleNotFoundError: No module named '_client'" is
apparently the same as was found in 18.04 and previously reported.

Note: I only installed from the binary package and did not install any related source package.

The "deprecated calls" also will need addressing, but this is not
required immediately.

** Mis-located Document
   :PROPERTIES:
   :ID: a39c9ba0-7bfe-4ea9-8354-a67519473250
   :END:

See the attached screenshot of the message from lirc-setup when trying
to verify some of the online documentation. The installed document is
not in the location the source code expects, so only the warning message is displayed.

I have completed the install and configuration of lirc manually, but I feel these issues should be resolved to simplify use of lirc by others.

John

Revision history for this message
John W. Burroughs (john-w-burroughs) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, that's a known upstream issue and reported in other distributions

https://sourceforge.net/p/lirc/tickets/341/
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923397
https://bugzilla.redhat.com/show_bug.cgi?id=1652992

lirc isn't really an actively maintainer project nowadays

Changed in lirc (Ubuntu):
importance: Undecided → High
Revision history for this message
Sebastien Bacher (seb128) wrote :

(unsure if the tool needs to be started with sudo, also doing that removes a file on disk so the package needs to be reinstalled before trying again)

Changed in lirc (Debian):
status: Unknown → New
Changed in lirc (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.