Connecting Printers in elementary OS and Handling Print Queues

In Australia, plenty of households still keep a printer tucked near the home office, especially with hybrid work now standard. Whether you're printing invoices from a small business in Brisbane, scholarship forms from a flat in Carlton, or a school assignment from your kitchen table in Perth, getting elementary OS to talk to your printer shouldn't feel like pulling teeth.

elementary OS ships with a sensible printing stack built around CUPS, the Common Unix Printing System that handles jobs across most Linux distributions. Plug in a USB cable or join the same Wi-Fi network as your printer, and the system usually detects hardware without much fuss. If it doesn't, you'll need to install a driver or do a small amount of configuration, but the process is friendlier than it once was.

This walkthrough covers the practical bits: adding a printer in Pantheon's Settings panel, choosing between protocols like IPP and SMB, finding drivers, and wrangling the print queue when jobs stack up. It also dips into troubleshooting, because Australian internet at the edge of suburbia can be patchy, and some printers simply don't behave the same way they do on Windows.

For anyone juggling several projects at once, it's worth remembering that elementary OS handles printing in the background, which fits neatly into a productive multi-workspace setup. You can keep a print job rolling while drafting something else on a different desktop.

Understanding How Elementary OS Handles Printing

elementary OS uses CUPS as its printing engine, the long-standing standard on Linux desktops. It exposes a web interface on localhost:631 and integrates with Pantheon's Settings panel, giving you a graphical path that hides most of the technical plumbing. The system also relies on Gutenprint and manufacturer-supplied PPD files to translate between your document and the printer's own language.

When you send a document to print, the job first lands in a queue managed by CUPS. From there it's passed to the relevant backend — USB, network, or wireless — and on to the printer. If the printer is offline, out of paper, or missing a driver, the job simply sits in the queue waiting. This is one of the most useful features of the Linux printing stack: jobs rarely vanish into the ether.

You can monitor the queue from the print dialog itself, the system tray, or by opening the CUPS web interface in Epiphany, elementary's default browser. Each method gives you a slightly different view, but all of them let you pause, resume, or cancel jobs that have gone astray. Australian users printing at A4 by default will appreciate that CUPS handles paper sizes correctly without any extra setup.

The architecture also supports printer sharing, useful in homes where a Mac or another Linux box needs to send jobs to the same machine. Sharing works through Bonjour/mDNS, and you'll see advertised printers appear automatically when both machines sit on the same network.

Adding Network, USB, and Wireless Printers

The fastest path to a working printer is Settings → Printers. Open it from the system menu, click the small plus icon, and elementary OS will scan the local network for anything broadcasting IPP, LPD, or SMB services. Plug in a USB cable while the panel is open and most modern printers will appear in the list within seconds.

Network printers using IPP are usually the simplest because IPP Everywhere is built into CUPS and many printers now ship with native support. AirPrint-compatible machines, including a lot of Brother and Canon units sold at Officeworks, work this way too. If you know the printer's IP address, you can also add it manually by selecting "Add Printer" and typing the URI in the form ipp://192.168.1.42/ipp/print.

SMB printers are common in small offices and in shared housing where a multifunction device is plugged into a router or a NAS. You'll need the share name, the workgroup (often WORKGROUP), and any authentication credentials the device requires. USB printers are the easiest of all: plug them in, wait for CUPS to detect them, and you're away.

If the printer doesn't appear automatically, the system-config-printer utility is worth installing from the AppCenter. It exposes more advanced options than the default Pantheon panel, including manual driver selection and detailed connection diagnostics. For Australians using a router supplied by Telstra, Optus, or Aussie Broadband, mDNS works fine on the standard home gateway, though some mesh systems occasionally block multicast traffic and need a tweak in their admin page.

Picking the Right Driver for Your Machine

Driver selection is the bit that catches people out. elementary OS ships with a generic driver that handles text reasonably well, but colour accuracy, duplex, and high-resolution modes generally need a manufacturer-specific PPD. OpenPrinting maintains a useful database that tells you which driver family fits your model.

Brother printers are well supported on Linux because Brother publishes its own drivers as RPM and DEB packages. Canon has improved over the years, particularly for Pixma models, though some newer inkjets still require a manual install. HP remains the safest choice: HPLIP is bundled with most distributions and handles the bulk of LaserJet and Officejet machines sold through JB Hi-Fi and other Australian retailers.

For Fuji Xerox machines, still common in Australian offices, you'll usually need the manufacturer's own driver or a generic PCL driver. PostScript printers, including many higher-end Brother and HP units, are almost always plug-and-play because CUPS handles PostScript natively.

When a manufacturer doesn't supply a Linux driver, the printer's built-in PostScript or PCL emulation often means you can still use it with a generic driver. The trick is to match the printer's protocol: PCL 5, PCL 6, or PostScript. A quick look at the printer's spec sheet, usually on the manufacturer's Australian site, will tell you which one it speaks.

Managing and Cancelling Print Jobs

Once everything is wired up, you'll spend most of your time managing the queue rather than adding printers. elementary OS surfaces a small print icon in the system tray when jobs are active, and clicking it shows what's in flight, paused, or completed. Right-clicking a job gives you pause, resume, and cancel options.

For more control, the CUPS web interface at http://localhost:631 lets you reorder jobs, hold the entire queue, and inspect printer state with messages that often explain what's gone wrong. Errors like "media needed" or "printer offline" appear here before they show up on the printer's own display, which can save a trip down the hall.

If a printer refuses to release a stuck job, the terminal is your friend. Running cancel -a clears all jobs, and lpstat -o lists everything currently queued. These tools come from the CUPS command-line utilities, which elementary OS includes out of the box. Power users occasionally write a small systemd service that restarts CUPS when a job has been stuck for more than a few minutes, but for most households that's overkill.

Keeping tabs on ink or toner is harder because Linux doesn't always read the chip data on consumables. Tools like ink and printerinklevel can pull levels from some Brother and HP machines, but for many models you'll simply need to glance at the printer's own screen or count pages. Given how expensive genuine cartridges are in Australia, third-party refills from suppliers like Cartridge World are common, though they sometimes confuse the ink level reporting.

Sorting Out Common Printer Headaches

A handful of issues come up repeatedly, and most are fixable without too much effort. The most common is the printer appearing offline even when it's powered on. The usual culprit is the firewall on the host machine blocking port 631, or the printer having a static IP that's changed after a router reboot. Re-adding the printer with the correct URI clears it up almost every time. Beyond these standard troubleshooting steps, organising your desktop into focused areas helps when you're diagnosing a problem — a guide to managing multiple workspaces explains how to set those up properly.

Another classic is a job that prints garbage characters. This usually means the wrong driver is selected, particularly when a PCL printer is being driven by a PostScript PPD or vice versa. Switch to the correct driver in the printer's properties and resend the job. PDFs created by non-standard applications sometimes do the same thing; printing them from a different viewer usually fixes it.

Wireless printers that drop off the network are usually suffering from a router issue. Some Australian ISPs ship gateways with AP isolation turned on by default, which prevents wireless clients from talking to each other. Log into the router, disable AP isolation on the relevant band, and the printer should reappear.

If nothing else works, restarting CUPS itself often clears mysterious hangs. The command sudo systemctl restart cups does it, and it's worth committing to muscle memory for the days when the print queue decides to misbehave at 11pm the night before an assignment is due. After a restart, any paused jobs resume and the printer reconnects.

The real takeaway is that elementary OS treats printing as a quiet utility that gets out of your way. Once you've spent ten minutes setting it up the first time, the system handles the rest without nagging you about driver popups or trial software. Set up a sensible default, keep the CUPS service running, and your printer will be ready whenever you need to print a parcel label, a tax form for the ATO, or a boarding pass before a flight out of Tullamarine.