I am ssh’d into his machine, and can only access cli, he can see what I do via tmux.

My friend is on Fedora 44, and has a HP103a printer which gets detected with lpstat:

~> lpstat -d
system default destination: HP-Laser-103-107-108

BUT, when I try to print with lp, he says the printer makes a little noise but nothing prints out.

I tried hp-setup but:

~> hp-setup -i -b usb
/usr/share/hplip/prnt/cups.py:705: SyntaxWarning: 'return' in a 'finally' block
  return fax_ppd,expected_fax_ppd_name, nick

HP Linux Imaging and Printing System (ver. 3.25.8)
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.)

^[[error: No device selected/specified or that supports this functionality.

I understand how painful printers can be, does anyone have experience with this? I haven’t used a printer with Linux before but I can provide logs.

  • anamethatisnt@sopuli.xyz
    14·
    2 days ago

    Found this older thread on the fedora forums
    https://discussion.fedoraproject.org/t/hp-printer-stopped-printing/87174/72

    If your friend has no other printer then it might be worthwhile to remove the printer if it exists, then remove ipp-usb and hplip, reboot and finally reinstall the hplip packages from dnf again.
    sudo dnf remove ipp-usb
    sudo dnf remove hplip
    reboot
    sudo dnf install hplip hplip-gui

    Personally I haven’t had the displeasure of touching a hp printer in a long time so my tip is based on the thread not experience.

    • siliconspoke@mander.xyzOP
      7·
      2 days ago

      It does have cups installed, I’ll try it in a bit. Looks like it wasn’t enabled.

      EDIT: what in the god damn

      ~> sudo systemctl status cups.service
● cups.service - CUPS Scheduler
     Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/cups.service.d
             └─10-foomaticrip-upgrade.conf
             /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Thu 2026-05-07 <redacted> +<redacted>; 7s ago
 Invocation: 8a2f6bd220ab4729b9b2bbd82d80b65a
TriggeredBy: ○ cups.path
             ● cups.socket
       Docs: man:cupsd(8)
   Main PID: 6717 (cupsd)
     Status: "Scheduler is running..."
      Tasks: 1 (limit: 4302)
     Memory: 2M (peak: 2.2M)
        CPU: 24ms
     CGroup: /system.slice/system-cups.slice/cups.service
             └─6717 /usr/bin/cupsd -l

May 07 <redacted> fedora cupsd[6717]: [Job 4] Unable to queue job for destination "HP-Laser-103-107-108".
May 07 <redacted> fedora cupsd[6717]: [Job 5] Unable to queue job for destination "HP-Laser-103-107-108".
May 07 <redacted> fedora cupsd[6717]: [Job 6] Unable to queue job for destination "HP-Laser-103-107-108".
May 07 <redacted> fedora cupsd[6717]: [Job 7] Unable to queue job for destination "HP-Laser-103-107-108".
May 07 <redacted> fedora cupsd[6717]: [Job 8] Unable to queue job for destination "HP-Laser-103-107-108".
May 07 <redacted> fedora cupsd[6717]: [Job 9] Unable to queue job for destination "HP-Laser-103-107-108".
May 07 <redacted> fedora cupsd[6717]: [Job 10] Unable to queue job for destination "HP-Laser-103-107-108".
May 07 <redacted> fedora cupsd[6717]: [Job 11] Unable to queue job for destination "HP-Laser-103-107-108".
May 07 <redacted> fedora cupsd[6717]: [Job 12] Unable to queue job for destination "HP-Laser-103-107-108".
      • atzanteol@sh.itjust.worksEnglish
        5·
        2 days ago

        That looks ‘reasonably healthy’ - at least the service is running. I haven’t spent a lot of time debugging cups but the web interface may give a better view of what’s going on.

        Since you’re on a remote system you can port-forward a local port to the remote host. ssh -L 8311:localhost:631 user@remotehost will forward “local” port 8311 to port 631 on the remote server. You can then point a web browser on your system at http://localhost:8311/ to connect to the CUPS daemon.

        • siliconspoke@mander.xyzOP
          3·
          2 days ago

          Yeah I couldn’t access it.

          I’m tired boss :(

          He says he’ll just boot up windows if he ever needs to print anything.