How to troubleshoot printing problems in Linux after updating CUPS

Sometimes, after a system or printing package update, we find that automatic printer detection It has stopped working. This is a frustrating situation, especially in environments like Linux Mint, where the ease of installing a peripheral is one of its biggest draws. When you try to add the machine manually, and even though the system tells you that the document has been sent, the sheet does not come out of the trayThere is likely a conflict with the current version of CUPS or the drivers.

To solve these headaches, simply restarting the computer isn't enough. It's necessary to understand that the Common Unix Printing System (CUPS) It's the core that manages print queues and format filters. If the filters fail or the network configuration changes, we'll lose the ability to print. Therefore, we'll review everything from the simplest solutions to advanced configurations. restore printing service in any Unix-based distribution.

Installing and deploying CUPS on Debian and Arch Linux

Depending on the distribution you use, the installation process varies slightly, although the goal is the same. On systems based on Debian and its derivativesIdeally, you should ensure that the basic service and drivers are present by running the command apt install cups printer-driver-allThis ensures that we have the necessary foundation for the system to recognize the hardware.

If you move in the ecosystem of Arch LinuxThings change a bit. First, you need to install the CUPS package along with cups-filters, ghostscript and the sources gsfonts using the pacman package manager. A key detail here is that, unlike Debian, you must manually activate the service using systemctl start cups.service and enable it to boot with the system by systemctl enable cups.service.

Using virtual print queues and PaperCut

In corporate or university environments, systems like PaperCut are commonly used. In these cases, the physical printer is not installed directly, but rather a virtual print queueTo achieve this, the tool is used lpadmin from the terminal with root privileges. The typical command follows the structure /usr/sbin/lpadmin -p NombreImpresora -E -v "http://URL-DEL-SERVIDOR".

Once the queue is added, the trick to avoid errors is to select the controller. Generic PostScript Printer in the system configuration. This driver is extremely versatile and avoids the compatibility conflicts that often arise after CUPS updates. If everything is configured correctly, the system It will request network credentials at the time of launching the document.

Convert an old USB printer into a network printer using Raspberry Pi

If you have an old printer that only connects via cable and you want to make it accessible to all your devices, a Raspberry Pi is the perfect tool. The first step is to update the system with sudo apt-get update y upgradeand then install the CUPS server. To avoid having to type the root password repeatedly, it is highly recommended. add user pi to group lpadmin with the command sudo usermod -a -G lpadmin pi.

To make the printer visible from other computers, you need to run sudo cupsctl --remote-any and restart the server. This allows the print server listens for requests external. To access the management, simply enter the Raspberry Pi's IP address followed by port 631 in your browser (for example, https://192.168.1.100:631).

Windows integration via SAMBA

To allow a Windows PC to detect the printer connected to the Raspberry Pi, we need to install Samba. After running sudo apt-get install sambaWe need to edit the configuration file in /etc/samba/smb.confIt is vital to configure the sections correctly. [printers] and [print$]ensuring that the parameter guest ok = yes be active to facilitate connection without excessive complications.

After restarting the SAMBA service, we go to the CUPS web interface, "Administration" tab and click on Add PrinterWhen selecting the local USB printer, it is essential to check the box for Share this printerIn this way, Windows will recognize it as a standard network printer.

Advanced server administration and security

By default, CUPS is quite restrictive and only allows local administration. If we want to manage it from another PC on the network, we must modify the file cupsd.confChanging Listen localhost:631 by Listen *:631, we open the server to any IP address on the local network.

However, we can't leave the door open to just anyone. It's necessary to add directives such as Allow from all or specify specific IPs within the tags <Location /admin> to control who can delete queues or change drivers. For these changes to take effect, we must always run /etc/init.d/cups restart.

Troubleshooting common errors and maintenance

It is common for errors of this type to appear filter failed or that jobs get stuck in the queue. When this happens, the best course of action is to clear the print queue from the terminal and cancel all pending jobs. If the problem persists, checking the real-time error log is the best way to determine if the fault lies with the driver, in Ghostscript or in some filter specific.

Another recurring problem is that the web interface becomes unresponsive outside of the server. This can be fixed by adjusting the listening permissions in the configuration file. To ensure long-term stability, it is recommended to assign a static IP to the print server and always prioritize the Ethernet cable connection over Wi-Fi, as it drastically reduces packet loss.

Troubleshooting printing problems in Linux requires a thorough analysis, from installing basic packages to configuring network permissions and selecting the correct driver. Whether it involves reinstalling CUPS, using virtual queues, or creating a dedicated server with Raspberry Pi and Samba, the key lies in ensuring that data filters are compatible and that the service has the necessary permissions to communicate with the hardware and clients on the network.