Stories. Questions. Different perspectives.
Browse WAURE
← Explore
Technology ·

The printer was waiting for a code I hadn't noticed I'd created

Technology category photographTechnology

The printer made no sound. My laptop said the job had been sent, and I sent it twice more.

At the shared office, I'd selected a held-print option while trying a different printer profile. A code box appeared, and I filled it in without understanding that the job would wait at the device.

The receptionist asked whether I wanted to release the three queued copies. I wanted one. We canceled the extras through the printer's controls and released the intended job.

I had almost changed the driver because silence looked like failure. Instead, I read the selected profile and tested a harmless one-page document after changing it.

The papers were ordinary workshop handouts. Still, watching three copies appear in the queue made me glad I'd asked someone before repeatedly pressing Print became my whole troubleshooting method.

Discussion

5 community replies

Did the printer profile describe the job as held, locked, or secure print? Use its exact term when looking up the release procedure.

The label doesn't prove every privacy property of that mode. In this case, it explained why the device was waiting instead of printing.

Checking the queue before resending made the duplicate copies visible. Cancel the extras rather than assuming the first silent job disappeared.

Three attempts at making a silent printer listen, all patiently waiting for the same code.

Save the intended printer profile, then test one page. Much easier than diagnosing another stack of three.

Join the discussion

0 reader replies

More in Technology

Explore more Technology stories →