Description of problem: hp-setup has previously had no problem with my manual discovery by pre-configured network address of 2 printers of the same model but assigned different addresses. (unfortunately it gives them the same name, so I have to remember their order). Now in M8 alpha1, after I've used manual discovery of one of our HP Officejet Pro 8600 Plus's with address 192.168.0.52 and proceeded with the hp-setup dialog, it reports something to the effect that this is already configured, and do I want to assign another port. In fact, what is already configured is the same model printer but with address 192.168.0.51. hp-setup did not have this problem in M7 A consequence, for example, is that xsane doesn't see the scanner just configured, gives no choice of multifunction printer, just goes straight through to 192.168.0.51 which is elsewhere on the network. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Hmm, deleted hplip, deleted all printers & faxes via MCC. Restarted, reinstalled hplip. Rebooted, ran hp-setup. Didn't get to the graphical window: [tony@oldtony ~]$ hp-setup HP Linux Imaging and Printing System (ver. 3.20.6) 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. Traceback (most recent call last): File "/usr/bin/hp-setup", line 313, in <module> ui = import_module(ui_package + ".setupdialog") File "/usr/lib64/python3.8/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1014, in _gcd_import File "<frozen importlib._bootstrap>", line 991, in _find_and_load File "<frozen importlib._bootstrap>", line 961, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "<frozen importlib._bootstrap>", line 1014, in _gcd_import File "<frozen importlib._bootstrap>", line 991, in _find_and_load File "<frozen importlib._bootstrap>", line 973, in _find_and_load_unlocked ModuleNotFoundError: No module named 'ui5' [tony@oldtony ~]$ Is there something missing from the package? Tony
Update: Problem with re-installed hp-setup dot proceeding to graphical part was that I'd deleted hplip gui and it didn't re-install with hplip re-installation. That aside, I've confirmed the problem on a 2nd M8 alpha1 installation. Whichever of the 2 printers 192.168.0.51 or same.52 are installed first, install OK. A later attempt to install the other one fails, saying the print queue already exists, which is not true Can ping both printers. I note that following the manual discovery step of the 2nd printer, the correct printer with its correct network address is displayed in hp-setup, but trying to progress from there is what fails with the faulty 'duplicate print queue' message. Get same message for whichever is the 2nd printer - have tried installing .51 or .52 first - first printer installed works, 2nd fails Tony
On Mageia 7, the current version is: hplip-3.19.5-1.mga7 It has had a lot of new versions since, 3.19.6->12, 3.20.2->6, so plenty of opportunity for changes. Can you try a forum on this one, Tony? Not only to see whether anyone else has this problem, but possibly pin down which update introduced it.
Source RPM: (none) => hplip-3.20.6-1.mga8.src.rpmCC: (none) => lewyssmith
CC: (none) => ouaurelien
Status of this in M8 Beta 2?
Created attachment 12079 [details] screensave failed add 2nd printer M8beta2 x86_64 still shows same problem at fresh install with only task-printing-hp and task-scanning added after initial M8 installation. Attached pic shows successful config of printer at 192.168.0.51, but failed attempt to attach different printer of same HP model at 192.168.0.52 The terminal window in the screensave shows hp-setup found the printer at 192.168.0.52, but then erroneously reports that one or more print queues already exist for this device. Tony
...and I've just updated the new M8beta2 to current, added 559 packages as of 15/12/2020, rebooted but still same bug. hplip version 3.20.11 Tony
@ Tony, Thanks answering. It seems there is 2 same models of HP printers on the same network. And HPLIP tries to add a print-job queue with the same name to CUPS server, because it uses the model as name. Have you ever the ability to rename the second model name of the print job before saving?
Hmmm, not sure how to do that. The issue is still there with M8 x86_64-rc. Seems to me that the problem is deeper than just the name of the printer. Many earlier versions of hp-setup had no problem in this regard. The core issue now is that when I manually configure e.g. printer at 192.168.0.51 it is added just fine, but when I do the same for printer at 192.168.0.52 it says printer queue already exists for this device, which is obviously not so. hp-setup seems to be ignoring the device IP address it was given, which is (relatively) new behaviour which hadn't been present over many iterations previously. Tony
Whiteboard: (none) => MGA8-x86_64-rc
Since I do not have 2 HP printers, and since this seems to be a hplip issue, this should be reported upstream. @Tony, have you ever tested if same behaviour occurs with an other Linux distribution like Fedora or even Ubuntu?
I had an - apparently related/similar - problem with a networked multifunction printer (MFP M281fdw) - OK up to and including Beta-2, the problem only appearing after a recent update: (a) scanimage -L does not report seeing the scanner, and (b) the scanner configuration dialog is not triggered. https://help.ubuntu.com/community/HpAllInOne proposes a manual procedure for configuring networked mfp printers, that I used as a workaround. That solved the problem for me, but with slight modifications applied : - in the list provided by hp-makeuri, replace the term "hpfax" by "hp" - restart cups with systemctl That might help also in your 2-printer case
CC: (none) => juergen.harms
CC: juergen.harms => (none)
Hi, note that hplip-3.21.2-1.mga8 is in Core/updates_testing
Source RPM: hplip-3.20.6-1.mga8.src.rpm => hplip-3.20.11-1.mga8.src.rpm
Whiteboard: MGA8-x86_64-rc => (none)Status: NEW => NEEDINFOVersion: Cauldron => 8
Assignee: bugsquad => ouaurelien
sorry, just to note that I've been interstate for the last month, no access to the 2-same-printers but will be back next week so can work further on it. (Not lack of interest in contributing to a fix!) Tony
(In reply to Aurelien Oudelet from comment #9) > Since I do not have 2 HP printers, and since this seems to be a hplip issue, > this should be reported upstream. > > @Tony, have you ever tested if same behaviour occurs with an other Linux > distribution like Fedora or even Ubuntu? This is an upstream hplip issue. It should name the second printer queue with a 2 number instead of trying to add a same named printer queue in cups. So, as long as you, Tony, own 2 hp printers, you should report upstream the issue here: https://launchpad.net/hplip/+filebug You will need an Ubuntu account.
Status: NEEDINFO => UPSTREAM
Whiteboard: (none) => MGA7TOO MGA8TOOTarget Milestone: --- => Mageia 9Version: 8 => Cauldron
Quick question - why report an hplip problem to Ubuntu? I'd previously tried to find an HP site... What don't I know about authorship of hplip? Tony
(In reply to Tony Blackwell from comment #14) > Quick question - why report an hplip problem to Ubuntu? I'd previously > tried to find an HP site... What don't I know about authorship of hplip? > Tony https://sourceforge.net/projects/hplip/support states that https://launchpad.net/hplip is the place to get support. Presumably the author(s) uses ubuntu.
CC: (none) => davidwhodgins
Created attachment 12708 [details] output of hp-doctor
Added bug report at https://bugs.launchpad.net/hplip/+bug/1927908 But to Mageia: Looking at output of hp-doctor (which I didn't know about until now), please review attached file. There may be issues there which HPLIP folk may consider outside their remit at present. What have we done differently in M8 to cause this to fail, where it has worked for years in earlier iterations of Mageia. Why does it seem to be looking for all those 32-bit packages? Tony
Created attachment 12709 [details] Converting hp-doctor.odt to a .txt file to be seen here. Please later add plain text file as a .txt one to be read within the browser.
hplip does not support our distribution from upstream installer. It does not reference us. This can be a topic we can discuss between us and upstream. hp-doctor software use hard-coded stuffs and packages names that come from Ubuntu and derivatives name conventions. We can't deal with them. hp-upgrade is removed from our policy as we don't allow Mageia's packaged software to have self-updating functionality. This is a security issue.
Created attachment 12710 [details] output of hp-doctor in .txt format Output of hp-doctor in .txt format. Yes, I wondered about that as I attached the .odt but chose that as perhaps better formatted than .txt. Won't do it again! Are there any issues reveaqled in that which HP would expect us to be dealing with? Tony
(In reply to Tony Blackwell from comment #20) > Created attachment 12710 [details] > output of hp-doctor in .txt format > > Output of hp-doctor in .txt format. Yes, I wondered about that as I > attached the .odt but chose that as perhaps better formatted than .txt. > Won't do it again! > > Are there any issues reveaqled in that which HP would expect us to be > dealing with? > Tony No, as I previously said: hp-doctor software use hard-coded stuffs and packages names that come from Ubuntu and derivatives name conventions. We can't deal with them. hp-upgrade is removed from our policy as we don't allow Mageia's packaged software to have self-updating functionality. This is a security issue. I don't see anything things we could care of. But, I already ask upstream to add support for Mageia Distribution. I don't have an answer for now.
Current update on this bug. HP-Setup is still at fault in that if you accept the default naming for the first printer, it gets added OK. If you accept the identical default printer name for the second identical printer, hp-setup will consider them to be the same printer and refuse to add the second despite them being at different network addresses. Still the same bug. However, the work-around now is simple. Just give the printer a different name while saving the hp-setup configuration and then all is well. So, although hp-setup still hs the same bug, given that its upstream, they don't seem to be doing anything about it and there is now a work-around, I'd suggest we close this. Tony
Aurelian are you happy if I just close this? Tony