kprinters --nodialog option

[Ismet Kursunoglu]

> > kprinter --nodialog testfile
> > kprinter: cannot connect to X server
> > I tried running an X server socket but still the same error.
>
> An X server socket on its own won't help you, if there is not an X
> server running as well. Are you trying to use this trick on an X-less
> server?

You jogged my memory. We did this in the past with cupsd, X, and KDE running all on the same server.

> First, this is the wrong list for specific kprinter/KDE questions.
> Better advice may be obtained from <kde-print at kde.org> (Subscribe at
> https://mail.kde.org/mailman/listinfo/kde-print ).

Thank you for the information.

> Second, it is very rare that you may ever need to use kprinter with
> the --nodialog option. Most of the time you can use CUPS' own "lp"
> command if you don't need a GUI.

Thank you that worked perfectly. The problem was that in the last two years we have gotten so use to just passing everything off to kprinter that we forgot about lp!

> Third, if you are getting this error, you probably won't be able to
> use kprinter without the --nodialog option either? Which user are
> you when executing that command? Can that user start an xterm?

I was starting kprinter as a regular user, 'vista'. The system is running Debian-Stable/GT.M/OpenVistA (GTM is the Mumps layer from Fidelity and OpenVistA is a port of the VAH FOIA VistA system to GT.M for our medical clinic)

The user can't start an xterm as you point out as there is no xserver running.

Thank you very, very much for all the help and more importantly for all the amazing things you do to make our printing job painless.

Ismet