Added Custom Cups Backend Discovers Cups error_log Now Available Via journalctl!

Written by James McDonald

April 13, 2015

Cups mailto Install

Playing with the cups-mailto from I discovered that you have to make the permissions correct in order for the backend to work

cp mailto /usr/lib/cups/backend

# unless you do this the backend will
# not showup in system-config-printer
chmod 700 /usr/lib/cups/backend/mailto

Mailto shows up as “SMTP” but only if you make the permissions correct as above. Once you select SMTP you need to enter at least a colon e.g. “mailto:” to the device URI field to be able to be able to go forward with the wizard

Screenshot from 2015-04-13 07:51:30




Viewing Error Log with journalctl

Screenshot from 2015-04-13 07:53:27

After setting LogLevel debug in /etc/cups/cupsd.conf by selecting “Save debuggin information for troubleshooting” in system-config-printer and restarting cups

systemctl restart cups.service

I couldn’t find the error_log in it’s traditional location under /var/log/cups/

That’s because under Fedora 21 it has moved into the journal

Using information from which discusses how to use journalctl and the cool auto complete options. I could then view the journal filtered for just the cups service.

journalctl _COMM=cupsd -xf

Screenshot from 2015-04-13 07:39:21


Submit a Comment

Your email address will not be published. Required fields are marked *

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

The reCAPTCHA verification period has expired. Please reload the page.

You May Also Like…

List local disks

GET-CimInstance -query "SELECT * from Win32_DiskDrive" DeviceID Caption Partitions Size Model -------- -------...

Create ISO using Powershell

Usage New-IsoFile -NewIsoFilePath C:\tmp\Hyper-V.iso-sources -ImageName Hyper-V -SourceFilePath 'C:\tmp\Hyper-V'...