Version-Release number of selected component: hplip-3.21.2-11.fc35 Additional info: reporter: libreport-2.15.2 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-hplip-5569.scope cmdline: /usr/bin/python3 /usr/bin/hp-setup -u crash_function: disable exception_type: AttributeError executable: /usr/bin/hp-setup interpreter: python3-3.10.0-1.fc35.x86_64 kernel: 5.14.12-300.fc35.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: smart_install.py:236:disable:AttributeError: 'NoneType' object has no attribute 'exec_' Traceback (most recent call last): File "/usr/share/hplip/ui5/setupdialog.py", line 1337, in NextButton_clicked self.showDevicesPage() File "/usr/share/hplip/ui5/setupdialog.py", line 562, in showDevicesPage smart_install.disable(GUI_MODE, 'qt4') File "/usr/share/hplip/base/smart_install.py", line 236, in disable dialog.exec_() AttributeError: 'NoneType' object has no attribute 'exec_' Local variables in innermost frame: mode: 1 ui_toolkit: 'qt4' dialog: None app: None passwordObj: None dev_list: ['HP LaserJet Professional M1132 MFP'] return_val: 112 return_error_str: 'Failed to disable smart install' url: 'http://hplipopensource.com/node/367' file_name: 'SmartInstallDisable-Tool.run' printer_names: '"HP LaserJet Professional M1132 MFP"'
Created attachment 1835036 [details] File: backtrace
Created attachment 1835037 [details] File: cpuinfo
Created attachment 1835038 [details] File: environ
Created attachment 1835039 [details] File: mountinfo
Created attachment 1835040 [details] File: namespaces
Created attachment 1835041 [details] File: open_fds
Hi Vasil, thank you for reporting the issue! Unfortunately I don't have a machine for smart installation, so I needed to alter one variable to get into scope where the traceback happens. The traceback happens because we loaded ui5 module in canEnterGUIMode4() instead of ui4 as it wanted here: try: from ui4.queuesconf import QueuesDiagnose Qt4 is old, we've already used Qt5 for more than 5 years, but this line was missed. Would you mind trying the rpms from the scratch build and see if it helps? https://koji.fedoraproject.org/koji/taskinfo?taskID=77793063
FEDORA-2022-b33cf577e7 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b33cf577e7
FEDORA-2022-f5484faf06 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f5484faf06
FEDORA-2022-f5484faf06 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-2022-f5484faf06` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-f5484faf06 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-b33cf577e7 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-b33cf577e7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b33cf577e7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-b33cf577e7 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-f5484faf06 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days