Lp and lpr postscript printing behaviour
I recently created a wireless print server with cups and samba on raspbian. I'm able to print from every device on my home network but I noticed a strange behaviour: when I print a postscript file directly from the raspberry pi lp works perfectly, while lpr prints a lot of sheets, the majority blank, some with random lines. Has someone experienced the same? Can someone give me or point me to a clear explanation about how gs, lp, lpr and cups interoperate?
printing cups raspbian postscript
add a comment |
I recently created a wireless print server with cups and samba on raspbian. I'm able to print from every device on my home network but I noticed a strange behaviour: when I print a postscript file directly from the raspberry pi lp works perfectly, while lpr prints a lot of sheets, the majority blank, some with random lines. Has someone experienced the same? Can someone give me or point me to a clear explanation about how gs, lp, lpr and cups interoperate?
printing cups raspbian postscript
add a comment |
I recently created a wireless print server with cups and samba on raspbian. I'm able to print from every device on my home network but I noticed a strange behaviour: when I print a postscript file directly from the raspberry pi lp works perfectly, while lpr prints a lot of sheets, the majority blank, some with random lines. Has someone experienced the same? Can someone give me or point me to a clear explanation about how gs, lp, lpr and cups interoperate?
printing cups raspbian postscript
I recently created a wireless print server with cups and samba on raspbian. I'm able to print from every device on my home network but I noticed a strange behaviour: when I print a postscript file directly from the raspberry pi lp works perfectly, while lpr prints a lot of sheets, the majority blank, some with random lines. Has someone experienced the same? Can someone give me or point me to a clear explanation about how gs, lp, lpr and cups interoperate?
printing cups raspbian postscript
printing cups raspbian postscript
asked Feb 16 '15 at 17:22
dashuilongdashuilong
112
112
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
CUPS is the printing system under Linux. In particular, it provides a server and clients. The lp
and lpr
are two common commands to print files: lpr
is the BSD one, and lp
the System V one. There exist various implementations (more or less compatible with the original commands), but nowadays they should be CUPS clients. You should check that with dlocate
or dpkg -S
: if raspbian is like Debian, lp
should be provided by cups-client
and lpr
should be provided by cups-bsd
(both binary packages are from the cups
source package). AFAIK, gs
is unrelated on the client side.
Your problem is quite strange since lp
and lpr
should behave in the same way (if they are both the CUPS clients). To solve your problem, I suggest that you look at strace
output to see if there are important differences. For instance, see what files under your home directory and under /etc
are read.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f185177%2flp-and-lpr-postscript-printing-behaviour%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
CUPS is the printing system under Linux. In particular, it provides a server and clients. The lp
and lpr
are two common commands to print files: lpr
is the BSD one, and lp
the System V one. There exist various implementations (more or less compatible with the original commands), but nowadays they should be CUPS clients. You should check that with dlocate
or dpkg -S
: if raspbian is like Debian, lp
should be provided by cups-client
and lpr
should be provided by cups-bsd
(both binary packages are from the cups
source package). AFAIK, gs
is unrelated on the client side.
Your problem is quite strange since lp
and lpr
should behave in the same way (if they are both the CUPS clients). To solve your problem, I suggest that you look at strace
output to see if there are important differences. For instance, see what files under your home directory and under /etc
are read.
add a comment |
CUPS is the printing system under Linux. In particular, it provides a server and clients. The lp
and lpr
are two common commands to print files: lpr
is the BSD one, and lp
the System V one. There exist various implementations (more or less compatible with the original commands), but nowadays they should be CUPS clients. You should check that with dlocate
or dpkg -S
: if raspbian is like Debian, lp
should be provided by cups-client
and lpr
should be provided by cups-bsd
(both binary packages are from the cups
source package). AFAIK, gs
is unrelated on the client side.
Your problem is quite strange since lp
and lpr
should behave in the same way (if they are both the CUPS clients). To solve your problem, I suggest that you look at strace
output to see if there are important differences. For instance, see what files under your home directory and under /etc
are read.
add a comment |
CUPS is the printing system under Linux. In particular, it provides a server and clients. The lp
and lpr
are two common commands to print files: lpr
is the BSD one, and lp
the System V one. There exist various implementations (more or less compatible with the original commands), but nowadays they should be CUPS clients. You should check that with dlocate
or dpkg -S
: if raspbian is like Debian, lp
should be provided by cups-client
and lpr
should be provided by cups-bsd
(both binary packages are from the cups
source package). AFAIK, gs
is unrelated on the client side.
Your problem is quite strange since lp
and lpr
should behave in the same way (if they are both the CUPS clients). To solve your problem, I suggest that you look at strace
output to see if there are important differences. For instance, see what files under your home directory and under /etc
are read.
CUPS is the printing system under Linux. In particular, it provides a server and clients. The lp
and lpr
are two common commands to print files: lpr
is the BSD one, and lp
the System V one. There exist various implementations (more or less compatible with the original commands), but nowadays they should be CUPS clients. You should check that with dlocate
or dpkg -S
: if raspbian is like Debian, lp
should be provided by cups-client
and lpr
should be provided by cups-bsd
(both binary packages are from the cups
source package). AFAIK, gs
is unrelated on the client side.
Your problem is quite strange since lp
and lpr
should behave in the same way (if they are both the CUPS clients). To solve your problem, I suggest that you look at strace
output to see if there are important differences. For instance, see what files under your home directory and under /etc
are read.
answered Feb 16 '15 at 22:13
vinc17vinc17
8,9991736
8,9991736
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f185177%2flp-and-lpr-postscript-printing-behaviour%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown