Description of problem:under the last version of hplip before 3.22.6-1 version, I always let my printer on; as I switch off my computer every evening, when I turned it on again the next morning, my computer was immediately available; this is no longer the case with the actual version of hplip, I have every evening to turn off my printer, and turn on it again after booting my computer in order it was recognized, which is very tedious Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
This looks like an old problem that was resolved, Bug 27906; but that was eventually about CUPS and 'system-config-printer-udev'. We need to check. Please provide the following, once logged in: 1. With the printer powered ON at boot $ sudo journalctl -b --no-hostname > bootlog_printer_ON.txt $ xz bootlog_printer_ON.txt 2. With the printer powered OFF at boot $ sudo journalctl -b --no-hostname > bootlog_printer_OFF.txt $ xz bootlog_printer_OFF.txt and attach each compressed log file *.xz to this bug.
CC: (none) => lewyssmithSummary: since hplip-3.22.6-1.mga8 my all-in-one HP ColorLaserjetPro MFP M283fdw is not recognized at boot => since hplip-3.22.6-1.mga8 my all-in-one HP ColorLaserjetPro MFP M283fdw is not recognized at boot if already on, but only when switched on later
Created attachment 13578 [details] journalctl with printer on
Created attachment 13579 [details] journalctl with printer off
Thank you for these journals, which I have scoured carefully up to a point. OFF & ON both show the same re CUPS: déc. 16 13:56:17 systemd[1]: Started CUPS Scheduler. déc. 16 13:56:17 systemd[1]: Listening on CUPS Scheduler déc. 16 13:56:51 systemd[1]: Starting CUPS Scheduler... déc. 16 13:56:54 systemd[1]: Started CUPS Scheduler. déc. 16 13:56:54 systemd[1]: Started Make remote CUPS printers available locally. re configure-printer, only ON at boot shows: 19:45:57 systemd[1]: Created slice Slice /system/configure-printer. 19:46:10 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=configure-printer@usb-002-003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' 19:46:10 kernel: audit: type=1130 audit(1671216370.266:55): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=configure-printer@usb-002-003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' 19:46:12 udev-configure-printer[2067]: task-printing-server-2018-6.mga8 19:46:12 udev-configure-printer[2031]: add usb-002-003 19:46:12 udev-configure-printer[2031]: device devpath is /devices/pci0000:00/0000:00:14.0/usb2/2-6 19:46:12 udev-configure-printer[2031]: MFG:HP MDL:HP ColorLaserJet MFP M282-M285 SERN:- serial:VNBRNDG2RQ 19:46:12 udev-configure-printer[2031]: CheckAndInstallDrivers() 19:46:12 udev-configure-printer[2031]: CheckInstalledDrivers() 19:46:12 udev-configure-printer[2031]: MissingDriver() 19:46:12 udev-configure-printer[2031]: FAIL HERE 19:46:12 systemd[1]: configure-printer@usb-002-003.service: Main process exited, code=exited, status=1/FAILURE 19:46:12 systemd[1]: configure-printer@usb-002-003.service: Failed with result 'exit-code'. 19:46:12 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=configure-printer@usb-002-003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' No reference to 'configure-printer' when printer OFF at boot. Both printer OFF & ON at boot show: 13:57:24 plasma_session[8950]: org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/hplip-systray.desktop" ("/usr/bin/hp-systray", "-x") the only reference to hplip at this stage. I must try this myself, but do not have HP printer. CC'ing TJ who does, to see whether he sees the same problem. CC'ing Martin who cracked the old problem
Source RPM: hplip-3.22.6-1.mga8 => hplip-3.22.6-1.mga8, system-config-printer-1.5.18-1.mga9.src.rpmCC: (none) => andrewsfarm, mageiaAssignee: bugsquad => mageia
Forgot to note that I assigned this to neoclust who nominally deals with system-config-printer.
The description reads to me as very similar to Bug 30626. All I can say is that it is being worked on; I don't know how much progress there might be. Since I use my printers infrequently, it's not a hardship for me to simply leave them turned off when I'm not going to use them. Of course, that workaround isn't as convenient for everybody as it is for me. Bug 30626 only affected printers when connected through usb. The one printer I have that has wireless capability doesn't show the problem when connected as a network printer. If he can do so, connecting as a network printer/scanner might be a better workaround for him than switching the printer on and off.
Thanks especially for that other bug reference; I suspected you would come up with something! For comparison, I just tried under Cauldron turning on my Epson printer before booting, and it subsequently worked. Yet the 'configure-printer' journal entries are similar to those in comment 4: Rha 17 09:48:42 systemd[1]: Started configure-printer@usb-001-007.service. Rha 17 09:48:42 kernel: audit: type=1130 audit(1671266922.497:35): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=configure-printer@usb-001-007 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Rha 17 09:48:42 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=configure-printer@usb-001-007 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Rha 17 09:48:42 udev-configure-printer[857]: task-printing-server-2018-7.mga9 Rha 17 09:48:42 udev-configure-printer[803]: add usb-001-007 Rha 17 09:48:42 udev-configure-printer[803]: device devpath is /devices/pci0000:00/0000:00:15.0/usb1/1-1/1-1.3/1-1.3.4 Rha 17 09:48:42 udev-configure-printer[803]: MFG:EPSON MDL:Stylus D92 SERN:- serial:423035303246A4BA6F Rha 17 09:48:42 udev-configure-printer[803]: CheckAndInstallDrivers() Rha 17 09:48:42 udev-configure-printer[803]: CheckInstalledDrivers() Rha 17 09:48:42 udev-configure-printer[803]: MissingDriver() Rha 17 09:48:42 udev-configure-printer[803]: FAIL HERE Rha 17 09:48:42 systemd[1]: configure-printer@usb-001-007.service: Main process exited, code=exited, status=1/FAILURE Rha 17 09:48:42 systemd[1]: configure-printer@usb-001-007.service: Failed with result 'exit-code'. Rha 17 09:48:42 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=configure-printer@usb-001-007 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Rha 17 10:06:08 udev-configure-printer[4610]: remove /devices/pci0000:00/0000:00:15.0/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.0 And all I got for CUPS was: Rha 17 09:48:44 cupsd[1590]: Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 Will try Mageia 8 later. And look at Peter's attached journals re hplip, which perhaps I should have done sooner... Taking back the bug assignment.
Assignee: mageia => bugsquadCC: mageia => (none)
I only have HP printers, so I can't speculate about other brands. That said, the issue the reporter described did indeed begin after the hplip 3.22.6 update. That update fixed Bug 10072, but it appears that the "fix" introduced this problem. I say this because Nicolas S. was able to change this in Cauldron by "reverting" to the previous behavior. Bug 30626 comment 20 That's the last I have heard about it. I'm assuming that it's just that it's a particularly difficult knot to untie.
Thanks for your further comment, especially the confirmation: > the issue the reporter described did indeed begin after the > hplip 3.22.6 update. Here under Mageia 8 (= bug), with my Epson printer switched on before booting, it worked subsequently. There is no mention of hplip in the journal. I will recheck the attached journals for that by next comment. Assigning to NicolasS who dealt with the other bug; with apologies for the configure-printer diversion for nothing.
Assignee: bugsquad => nicolas.salguero
Possibly related to Bug 31007 / Bug 30626
CC: (none) => fri
Assignee: nicolas.salguero => pkg-bugs
We stopped supporting Mageia 8 almost 8 months ago https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/ That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not. If this particular bug did not get fixed for Mageia 8, then we do regret that. If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field. If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing Mageia is a community project, meaning that we, the users, make Mageia together. The more active contributors we have, the more bug reports will get fixed. Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D
Status: NEW => RESOLVEDResolution: (none) => OLD