Bug 480219 - Unable to autodiscover printer: hp deskjet plus 4100
Summary: Unable to autodiscover printer: hp deskjet plus 4100
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_printer_manager (show other bugs)
Version: 5.92.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-01-23 11:06 UTC by Eric Armbruster
Modified: 2024-05-16 03:45 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Armbruster 2024-01-23 11:06:04 UTC
SUMMARY
Trying to add my HP Deskjet Plus 4100, but it fails in systemsettings to find the network printer


STEPS TO REPRODUCE
1. Click add

OBSERVED RESULT
No printers where automatically discovered

EXPECTED RESULT
Printer is automatically discovered

Please note that my printer is automatically discovered through the system-config-printer application

Operating System: Arch Linux 
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.7.0
Kernel Version: 6.7.0-arch3-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics
Memory: 38.0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 20Y7CTO1WW
System Version: ThinkPad E14 Gen 3

ADDITIONAL INFORMATION
Comment 1 Mike 2024-01-24 13:13:30 UTC
Does the printer show in the list if you run lpinfo from a terminal?  Also, is it USB or network connected?
Comment 2 Mike 2024-01-24 13:21:28 UTC
Also, and you might have already tried, does it find anything if press the Refresh button a couple of times on the Add Printer dialog?
Comment 3 Eric Armbruster 2024-01-26 16:56:13 UTC
The printer does not show up when running lpinfo.

When using system-config-printer the following connections types are offered:
- HP Linux Imaging and Printing
- AppSocket/HpDirect

seems to be hp specific stuff.
Comment 4 Eric Armbruster 2024-01-26 16:57:30 UTC
Refresh does not help. It is a network connected printer.
Comment 5 Mike 2024-02-02 15:01:28 UTC
(In reply to Eric Armbruster from comment #3)
> The printer does not show up when running lpinfo.
> 
> When using system-config-printer the following connections types are offered:
> - HP Linux Imaging and Printing
> - AppSocket/HpDirect
> 
> seems to be hp specific stuff.

ok, well, if it doesn't detect with lpinfo, we can't auto-detect it at this point using the basic CUPS infra.  One more thing you could try, from a terminal, run "kde-add-printer --add-printer" and provide the root password and then see if it shows in the list provided.  That might indicate a clue if it does show up.
Comment 6 Mike 2024-04-03 23:22:15 UTC
Have you tried to add your printer with Plasma6?
Comment 7 Mike 2024-04-16 19:27:17 UTC
If you cannot get Plasma6 to discover this printer, you can make sure that the following packages are installed:
- hplip
- hplip-hpijs

and try again.

If that doesn't work, you get the ip address of the printer on your network and use the Print Manager manual config and enter the address: ipp://printer-address:631/ipp/print, select a driver for the printer and see if that works.
Comment 8 Bug Janitor Service 2024-05-01 03:45:59 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2024-05-16 03:45:26 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!