Description of problem: The problem occurred after the pc restarted. Version-Release number of selected component: hplip-3.21.2-6.fc35 Additional info: reporter: libreport-2.15.2 cgroup: 0::/system.slice/cups.service cmdline: /usr/bin/python3 -B /usr/lib/cups/backend/hpfax crash_function: probeDevices exception_type: SystemError executable: /usr/lib/cups/backend/hpfax interpreter: python3-3.10.0~b3-1.fc35.x86_64 kernel: 5.13.0-0.rc7.20210624git7426cedc7dad.54.fc35.x86_64 runlevel: N 5 type: Python3 uid: 0 Truncated backtrace: device.py:558:probeDevices:SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats Traceback (most recent call last): File "/usr/lib/cups/backend/hpfax", line 151, in <module> probed_devices = device.probeDevices(['usb', 'par'], filter={'fax-type': (operator.gt, 0)}) File "/usr/share/hplip/base/device.py", line 558, in probeDevices result_code, data = hpmudext.probe_devices(bn) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats Local variables in innermost frame: bus: ['usb', 'par'] timeout: 10 ttl: 4 filter: {'fax-type': (<built-in function gt>, 0)} search: '' net_search: 'slp' back_end_filter: ('hp',) num_devices: 0 ret_devices: {} b: 'usb' bn: 1
Created attachment 1794731 [details] File: backtrace
Created attachment 1794732 [details] File: cpuinfo
Created attachment 1794733 [details] File: environ
Created attachment 1794734 [details] File: mountinfo
Created attachment 1794735 [details] File: namespaces
Created attachment 1794736 [details] File: open_fds
Hi Nathan, thank you for reporting the issue! It is caused by Python 3.10 change[1]: The PY_SSIZE_T_CLEAN macro must now be defined to use PyArg_ParseTuple() and Py_BuildValue() formats which use #: es#, et#, s#, u#, y#, z#, U# and Z#. See Parsing arguments and building values and the PEP 353. (Contributed by Victor Stinner in bpo-40943.) I'll update hplip. [1] https://docs.python.org/3.10/whatsnew/3.10.html#id2
I can reproduce in rawhide by running /usr/lib/cups/backend/hpfax. I'll see where else it needs to be fixed.
Reported upstream https://bugs.launchpad.net/hplip/+bug/1933973 .
*** Bug 1977478 has been marked as a duplicate of this bug. ***
FEDORA-2021-547a66e937 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-547a66e937
FEDORA-2021-205d10fc51 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-205d10fc51
FEDORA-2021-205d10fc51 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-205d10fc51` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-205d10fc51 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-547a66e937 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-547a66e937` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-547a66e937 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-205d10fc51 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-547a66e937 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.