Bug 735 - RFE: Extend /etc/init.d/xprint's "diag" option
Summary: RFE: Extend /etc/init.d/xprint's "diag" option
Alias: None
Product: xprint
Classification: Unclassified
Component: Server: Config: startup scripts (show other bugs)
Version: unspecified
Hardware: All All
: high enhancement
Assignee: Roland Mainz
QA Contact:
Depends on: 734
  Show dependency treegraph
Reported: 2004-06-09 14:14 UTC by Roland Mainz
Modified: 2011-09-13 12:28 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Description Roland Mainz 2004-06-09 14:14:00 UTC
[Followup to bug 734 and http://xprint.mozdev.org/bugs/show_bug.cgi?id=4805
("RFE: /etc/init.d/xprint should have a diagnostics option(s)")]:
RFE: Extend the "diag" option of /etc/init.d/xprint

Some ideas (from http://xprint.mozdev.org/bugs/show_bug.cgi?id=4805):
-- snip --
RRE: /etc/init.d/xprint should have one or more diagnostics options to collect
and analye problems (mainly font installation issues) on customer machines.

Informations which should be collected (draft):
- OS (% uname -a # + information whether
Debian/SuSE/Mandrake/RedHat/other-Linux, Solaris, AIX, HP-UX etc. is being used)
- Is /etc/init.d, /etc/rc.d, /etc/profile.d/ present ?
- Where are the Xprt config files installed ?
- Which print spoolers are installed (CUPS, LPRng, native (Solaris etc.)) ?
- If there is one (or more) running Xprint server:
    - Display ID
    - Font path
    - xdpyinfo output
- Fonts:
    - Font path of Xfree86/Xsun
    - Where does the system have fonts installed ?
    - Where is encodings.dir installed ?

Any more ideas what the functions should collect ?

------- Additional Comment #1 From Drew Parsons 2003-10-26 09:34 ------- 

As far as font problems go, on a Debian system it might be useful to know which
font packages are in fact installed.  This can be done with either dlocate or
"dpkg -S" against the font directories,
$ dlocate /usr/share/fonts | uniq -W 1
or (more slowly)
$ dpkg -S /usr/share/fonts

If we are going ahead with the idea of extracting fontpaths from Xserver config
files, then the diagnostic might want to test for the existence of those config

Probably want to report the version of Xprt if possible.

------- Additional Comment #2 From Roland Mainz 2003-12-14 23:42 ------- 

More items to test:
- Is the "Xprt" binary from Xfree86, xprint.mozdev.org, Sun, HP etc. (see bug
5239) ?
- xplsprinters output should check for spaces in printer names (see bug 5239)
- md5 hash of Xprt binary should be printed
- Is the PSdefault printer model-config present ?
- Are the PSdefault model fonts present, incl. fonts.dir ?
- Which resolution do the PSdefault model fonts have (1200DPI=old, 2540DPI=new)
-- snip --
Comment 1 Corbin Simpson 2011-09-13 12:28:36 UTC
Closing WONTFIX because nobody cares about Xprint. Reopen if you plan to address this bug.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.