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.

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".

Sure, I’ll crosspost.

Americans using anything but the metric system