Bug 242451 - Wrong File Location Print Test Page sysutils/plasma5-systemsettings
Summary: Wrong File Location Print Test Page sysutils/plasma5-systemsettings
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: kde
Depends on:
Reported: 2019-12-05 14:11 UTC by Anthony
Modified: 2019-12-05 18:59 UTC (History)
1 user (show)

See Also:
tcberner: maintainer-feedback+

Remove Hardcoded path (393 bytes, patch)
2019-12-05 18:52 UTC, Anthony
no flags Details | Diff
Makefile patch (312 bytes, patch)
2019-12-05 18:58 UTC, Anthony
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Anthony 2019-12-05 14:11:41 UTC
When printing a test page from within plasma5 system settings, it returns an error that it couldn't find the file for the test page.

The file it tries to print is provided by cups-filter and is located in:


However, running truss when trying to print the test page shows it is looking in the wrong location:

openat(AT_FDCWD,"/usr/share/cups/data/testprint",O_RDONLY,00) ERR#2 'No such file or directory'

In one of the KDE packages there is a hardcoded path to the print test page.
Comment 1 Tobias C. Berner freebsd_committer 2019-12-05 17:39:34 UTC
Thanks, I'll look into it.

Mfg Tobias
Comment 2 commit-hook freebsd_committer 2019-12-05 18:50:51 UTC
A commit references this bug:

Author: tcberner
Date: Thu Dec  5 18:50:36 UTC 2019
New revision: 519104
URL: https://svnweb.freebsd.org/changeset/ports/519104

  print/print-manager: fix cups install location path

  PR:		242451
  Submitted by:	Anthony <amzo1337@gmail.com>

Comment 3 Tobias C. Berner freebsd_committer 2019-12-05 18:52:19 UTC
Fixed. Thank for the report.
Comment 4 Anthony 2019-12-05 18:52:45 UTC
Created attachment 209737 [details]
Remove Hardcoded path
Comment 5 Anthony 2019-12-05 18:58:03 UTC
Created attachment 209738 [details]
Makefile patch
Comment 6 Anthony 2019-12-05 18:59:32 UTC
Looks like I submitted my patches just as you fixed it. My bad. My way wasn't as efficient of a solution anyways.