Bug 1293144 - cupsd puts spurious backslashes in log messages sent to syslog
cupsd puts spurious backslashes in log messages sent to syslog
Product: Fedora
Classification: Fedora
Component: cups (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Zdenek Dohnal
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-12-20 12:41 EST by Jonathan Kamens
Modified: 2016-12-20 12:13 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 12:13:46 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jonathan Kamens 2015-12-20 12:41:36 EST
cupsd puts spurious backslashes in front of quotation marks in log messages before feeding them to syslog. For example:

Dec 20 06:01:09 hostname cupsd: pdftops - copying to temp print file \"/var/spool/cups/tmp/cupsYkKbVW\"
Dec 20 06:01:09 hostname cupsd: Looking up \"m551dn.domainname\"...
Dec 20 06:01:09 hostname cupsd: Switching to Poppler\'s pdftops instead of Ghostscript for old HP LaserJet (\"LaserJet <number>\", no letters before <number>) printers to work around bugs in the printer\'s PS interpreters
Dec 20 06:01:09 hostname cupsd: Running command line for pstops: pstops 9727 username 32.pdf 1 \'finishings=3 print-quality=4 job-uuid=urn:uuid:760a74e0-4ecf-352b-5748-5647a864d556 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1450609269 time-at-processing=1450609269 document-name-supplied=32.pdf\'
Comment 1 Tim Waugh 2015-12-21 13:19:34 EST
I see the same here on F23 with cups-2.1.2-1.fc23.x86_64. Haven't seen the cause from a glance over the code.
Comment 2 Fedora Admin XMLRPC Client 2016-06-24 06:30:22 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Fedora End Of Life 2016-11-24 09:23:58 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Fedora End Of Life 2016-12-20 12:13:46 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.