Description of problem: I ran: hp-setup -i Version-Release number of selected component: hplip-3.20.11-1.fc33 Additional info: reporter: libreport-2.14.0 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.konsole-502f26ce77cf4df6ab372295c03b10a7.scope cmdline: /usr/bin/python3 /usr/bin/hp-setup -i 192.168.1.66 crash_function: getPPDFile2 exception_type: ValueError executable: /usr/bin/hp-setup interpreter: python3-3.9.1-1.fc33.x86_64 kernel: 5.9.16-200.fc33.x86_64 runlevel: N 5 type: Python3 uid: 0 Truncated backtrace: #1 [/usr/share/hplip/prnt/cups.py:596] getPPDFile2 #2 [/usr/bin/hp-setup:519] <module>
Created attachment 1744133 [details] File: backtrace
Created attachment 1744134 [details] File: cpuinfo
Created attachment 1744135 [details] File: environ
Created attachment 1744136 [details] File: mountinfo
Created attachment 1744137 [details] File: namespaces
Created attachment 1744138 [details] File: open_fds
Hi Salil, thank you for reporting the issue! Are you able to reproduce the issue? Would you mind telling me the detailed steps how you reproduced the issue? Thank you in advance!
Yes, this bug is still present: Steps to reproduce: 1. Run hp-setup -i <ip-addr-of-printer> This is my command output: ``` [swadnerkar@localhost ~]$ hp-setup -i 192.168.8.125 HP Linux Imaging and Printing System (ver. 3.20.11) Printer/Fax Setup Utility ver. 9.0 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. (Note: Defaults for each question are maked with a '*'. Press <enter> to accept the default.) Setting up device: hp:/net/ENVY_4500_series?ip=192.168.8.125 --------------------- | PRINT QUEUE SETUP | --------------------- Please enter a name for this print queue (m=use model name:'ENVY_4500'*, q=quit) ? Using queue name: ENVY_4500 Locating PPD file... Please wait. Traceback (most recent call last): File "/usr/bin/hp-setup", line 519, in <module> print_ppd = cups.getPPDFile2(mq, default_model, ppds) File "/usr/share/hplip/prnt/cups.py", line 596, in getPPDFile2 for f, pdl_list, driver_list in matches: ValueError: not enough values to unpack (expected 3, got 2) ```
Thanks, Salil! I tried to reproduce the issue with my HP printer, but with no luck - so IMO it is a model specific issue. Would you mind following the steps in https://fedoraproject.org/wiki/How_to_debug_printing_problems#I_have_HP_printer_and_have_a_problem_with_HPLIP_script and providing the mentioned data here? Thank you in advance!
Created attachment 1752214 [details] journalctl -f output
Created attachment 1752215 [details] hp-setup -ldebug -i output
Created attachment 1752217 [details] journalctl -u cups -e output
Created attachment 1752218 [details] printer ppd file
Seeing the same issue: hp-setup -i xxx.xxx.xxx.xxx [...] Please enter a name for this print queue (m=use model name:'Photosmart_7520'*, q=quit) ? Using queue name: Photosmart_7520 Locating PPD file... Please wait. Traceback (most recent call last): File "/usr/bin/hp-setup", line 519, in <module> print_ppd = cups.getPPDFile2(mq, default_model, ppds) File "/usr/share/hplip/prnt/cups.py", line 596, in getPPDFile2 for f, pdl_list, driver_list in matches: ValueError: not enough values to unpack (expected 3, got 2)
Hi Salil and Daniel, I found the cause of the issue - the searching algorithm did the exact driver match and ignored <model>_series if models device id doesn't have '_series'. The fix should be in this testing rpms (once they finish building), would you mind testing it? https://koji.fedoraproject.org/koji/taskinfo?taskID=61038920
I can confirm that this solved the problem for me.
Thank you very much for fixing this so quickly, Zdenek.
FEDORA-2021-ab42c9e8d3 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ab42c9e8d3
FEDORA-2021-3e0cfb2c53 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-3e0cfb2c53
FEDORA-2021-ab42c9e8d3 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-ab42c9e8d3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ab42c9e8d3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-3e0cfb2c53 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-3e0cfb2c53` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-3e0cfb2c53 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-a400e2d576 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-a400e2d576` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-a400e2d576 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-8b08af2e83 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-8b08af2e83` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8b08af2e83 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-8b08af2e83 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-a400e2d576 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.