Samsung ML-2251N User Manual (ENGLISH) - Page 142

On my SPL or PCL, error messages printing

Page 142 highlights

Problem Possible Cause and Solution I have CUPS and some options (such as N-up) seem to be always enabled even though I don't pick them in LLPR. There may be some local options defined in your ~/.lpoptions file, which is manipulated by the lpoptions command. These options will always be used if not overridden by LLPR settings. To get rid of all options for a printer, run the following command, replacing "printer" with the name of the queue: lpoptions -x printer I configured a printer to print to a file, but I get "Permission denied" errors. Most printing systems will not run as the super-user but as a special user (usually "lp"). Therefore, make sure that the file you have chosen to print to is accessible to the user owning the spooler daemon. On my SPL (or PCL) printer, I sometimes get error messages printing instead of my document. Unfortunately, some Unix applications may generate noncompliant PostScript output that may not be supported by Ghostscript, or even the printer itself in PostScript mode. You can try to capture the output to a file and view the results with Ghostscript (gv or ghostview will allow you to do so interactively) and see if you get error messages. However, since the application is probably at fault, contact your software vendor to inform them of the issue. 6 SOLVING PROBLEMS 6.25

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197

S
OLVING
PROBLEMS
6.
25
6
I have CUPS and some
options (such as N-up)
seem to be always enabled
even though I don’t pick
them in LLPR.
There may be some local options defined in your ~/.lpoptions
file, which is manipulated by the lpoptions command. These
options will always be used if not overridden by LLPR settings.
To get rid of all options for a printer, run the following
command, replacing “printer” with the name of the queue:
lpoptions -x printer
I configured a printer to
print to a file, but I get
“Permission denied” errors.
Most printing systems will not run as the super-user but as a
special user (usually “lp”). Therefore, make sure that the file
you have chosen to print to is accessible to the user owning
the spooler daemon.
On my SPL (or PCL)
printer, I sometimes get
error messages printing
instead of my document.
Unfortunately, some Unix applications may generate non-
compliant PostScript output that may not be supported by
Ghostscript, or even the printer itself in PostScript mode. You
can try to capture the output to a file and view the results
with Ghostscript (gv or ghostview will allow you to do so
interactively) and see if you get error messages. However,
since the application is probably at fault, contact your
software vendor to inform them of the issue.
Problem
Possible Cause and Solution