Description of problem: This occurs when the service tries to start from systemd. It looks like this has been fixed upstream, adding a condition to call configparser.SafeConfigParser or configparser.ConfigParser based upon python version. Version-Release number of selected component: lirc-core-0.10.0-40.fc39 Additional info: reporter: libreport-2.17.11 exception_type: AttributeError interpreter: python3-3.12.0-1.fc39.x86_64 cgroup: 0::/system.slice/lircd-setup.service cmdline: /usr/bin/python3 /usr/sbin/lircd-setup type: Python3 reason: lircd-setup:37:main:AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'? kernel: 6.6.2-201.fc39.x86_64 comment: This occurs when the service tries to start from systemd. It looks like this has been fixed upstream, adding a condition to call configparser.SafeConfigParser or configparser.ConfigParser based upon python version. crash_function: main package: lirc-core-0.10.0-40.fc39 runlevel: unknown executable: /usr/sbin/lircd-setup uid: 0 Truncated backtrace: lircd-setup:37:main:AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'? Traceback (most recent call last): File "/usr/sbin/lircd-setup", line 51, in <module> main() File "/usr/sbin/lircd-setup", line 37, in main parser = configparser.SafeConfigParser() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'? Local variables in innermost frame: path: '/etc/lirc/lirc_options.conf'
Created attachment 2002997 [details] File: cpuinfo
Created attachment 2002998 [details] File: namespaces
Created attachment 2002999 [details] File: backtrace
Created attachment 2003000 [details] File: open_fds
Created attachment 2003001 [details] File: environ
Created attachment 2003002 [details] File: mountinfo
Created attachment 2003003 [details] File: os_info
This bug is fixed in LIRC 10.0.2. See: https://sourceforge.net/p/lirc/git/ci/b6e2de8005c263a5db38e6fe7b41befbfd92accc/
*** Bug 2279044 has been marked as a duplicate of this bug. ***