I ran into a problem printing schematic pages in 6.3.0 on linux. A job
is submitted to the CUPS, but nothing ever prints. Reverting back to
6.2 avoids the problem.
Has anyone seen a similar problem? If so, how did you fix it?
Thanks,
- Chuck
I ran into a problem printing schematic pages in 6.3.0 on linux. A job
is submitted to the CUPS, but nothing ever prints. Reverting back to
6.2 avoids the problem.
Has anyone seen a similar problem? If so, how did you fix it?
Thanks,
- Chuck
Chuck Huber wrote:
I ran into a problem printing schematic pages in 6.3.0 on linux. A job
is submitted to the CUPS, but nothing ever prints. Reverting back to
6.2 avoids the problem.
Has anyone seen a similar problem? If so, how did you fix it?
Thanks,
- Chuck
I run 6.3.0 on Gentoo, and printing via CUPS from Eagle works fine for me.
Typically, though, I just print to PDF and do my printing from a PDF viewer.
You might want to try that to help isolate the issue.
Whenever I have CUPS issues I always look at the following:
1) the CUPS web interface at http://localhost:631. Occasionally the error
message shown besides the printer there is useful. Often it isn't.
2) more often, I end up examining the CUPS error log in /var/log/cups.
Changing the LogLevel variable in /etc/cups/cupsd.conf to 'debug' (then
restarting CUPS) will spew tons of information in the logs and usually show
what is tripping up the output.
The paths I show above may not be the same paths used on your distribution.
Chuck Huber wrote:
I ran into a problem printing schematic pages in 6.3.0 on linux. A job
is submitted to the CUPS, but nothing ever prints. Reverting back to
6.2 avoids the problem.
Has anyone seen a similar problem? If so, how did you fix it?
Thanks,
- Chuck
I run 6.3.0 on Gentoo, and printing via CUPS from Eagle works fine for me.
Typically, though, I just print to PDF and do my printing from a PDF viewer.
You might want to try that to help isolate the issue.
Whenever I have CUPS issues I always look at the following:
1) the CUPS web interface at http://localhost:631. Occasionally the error
message shown besides the printer there is useful. Often it isn't.
2) more often, I end up examining the CUPS error log in /var/log/cups.
Changing the LogLevel variable in /etc/cups/cupsd.conf to 'debug' (then
restarting CUPS) will spew tons of information in the logs and usually show
what is tripping up the output.
The paths I show above may not be the same paths used on your distribution.