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. ***
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '39'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 39 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.