Description of problem: Version-Release number of selected component: lirc-core-0.10.0-44.fc41 Additional info: reporter: libreport-2.17.15 exception_type: AttributeError interpreter: python3-3.13.0-1.fc41.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.11.11-300.fc41.x86_64 comment: crash_function: main package: lirc-core-0.10.0-44.fc41 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' Potential duplicate: bug 2253406
Created attachment 2062496 [details] File: cpuinfo
Created attachment 2062497 [details] File: namespaces
Created attachment 2062498 [details] File: backtrace
Created attachment 2062499 [details] File: open_fds
Created attachment 2062500 [details] File: environ
Created attachment 2062501 [details] File: mountinfo
Created attachment 2062502 [details] File: os_info
This is fixed upstream in lirc 0.10.2. I have patches ready to update the lirc package to 0.10.2 but cannot upload them due to https://pagure.io/packager-sponsors/issue/693
This is fixed in update-testing: https://bodhi.fedoraproject.org/updates/FEDORA-2025-26036d2f3f Please confirm
Thanks Sean. Is there any possibility of a build for fc42? Will happily test and confirm then.
If it is broken, then I rather not have a broken version in both f42 and f43. Is it possible to test this in f43, in a container/vm or so. Thank you
Fair enough! I've tried it in f43 and it appears fixed. Many thanks. If possible it would be great to have the f42 package fixed as well, but not the end of the world if it isn't.
Ok, I've upgraded the f42 packages too. They should be hitting updates-testing soon. Please can you test and add karma, thank you. On a separate note, this issue can be closed, right?
FEDORA-2025-c714245b6c (lirc-0.10.2-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-c714245b6c
FEDORA-2025-c714245b6c has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-c714245b6c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c714245b6c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Downloaded and installed on f42 from updates-testing. It is working fine. The issue can be closed as far as I am concerned. Thanks for your help.
Thank you for reporting and testing Nigel
FEDORA-2025-c714245b6c (lirc-0.10.2-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.