Scribus 1.3.3.13svn on Ubuntu 10.4. Everything OK until I sent a job to print
- locally connected printer which works fine from any other
application. If I try to print directly from Scribus the print progress
bar gets to about 50% and then the package freezes. If I export the job
to pdf I can
On 05/13/2010 07:20 AM, Ray Chandler wrote:
> Scribus 1.3.3.13svn on Ubuntu 10.4. Everything OK until I sent a job to
> print - locally connected printer which works fine from any other
> application. If I try to print directly from Scribus the print progress
> bar gets to about 50% and then the
On Tuesday 17 January 2006 23:32, Craig Bradney wrote:
Craig in relation to the problem printing from Scribus to CUPS I did the
following;
1. Completely deleted all references to the EPSON CX6600 from both Cups
and
YaST. Uninstalled the pips rpm file from YaST.
2, I reinstalled e
On Tuesday 17 January 2006 23:32, Craig Bradney wrote:
> On Wednesday 18 January 2006 04:29, russbucket wrote:
> > On Tuesday 17 January 2006 16:30, Craig Bradney wrote:
> > > On Wednesday 18 January 2006 01:14, russbucket wrote:
> > > > On Saturday 14 January 2006 12:41, Craig Ringer wrote:
> > >
On Tuesday 17 January 2006 23:32, Craig Bradney wrote:
>snip
> Weird, but no I doubt it as I use Konqueror 99% of the time myself. Please
> try to make another account and we will see how that goes. I'll delete the
> old one when your new one works.
>
> Craig
I'll try later today after I return hom
On Wednesday 18 January 2006 04:29, russbucket wrote:
> On Tuesday 17 January 2006 16:30, Craig Bradney wrote:
> > On Wednesday 18 January 2006 01:14, russbucket wrote:
> > > On Saturday 14 January 2006 12:41, Craig Ringer wrote:
> > > >snip
> > > >
> > > > russbucket wrote:
> > > > > The error_log
On Wednesday 18 January 2006 01:14, russbucket wrote:
> On Saturday 14 January 2006 12:41, Craig Ringer wrote:
> >snip
> >
> > russbucket wrote:
> > > The error_log doesn't show much. Just this:
> > > E [10/Jan/2006:16:12:22 -0800] PID 7024 stopped with
> > > status 0!
>
> I posted an error
On Wednesday 18 January 2006 01:14, russbucket wrote:
> On Saturday 14 January 2006 12:41, Craig Ringer wrote:
> >snip
> >
> > russbucket wrote:
> > > The error_log doesn't show much. Just this:
> > > E [10/Jan/2006:16:12:22 -0800] PID 7024 stopped with status 0!
>
> I posted an error_log t
On Tuesday 17 January 2006 16:30, Craig Bradney wrote:
> On Wednesday 18 January 2006 01:14, russbucket wrote:
> > On Saturday 14 January 2006 12:41, Craig Ringer wrote:
> > >snip
> > >
> > > russbucket wrote:
> > > > The error_log doesn't show much. Just this:
> > > > E [10/Jan/2006:16:12:
On Saturday 14 January 2006 12:41, Craig Ringer wrote:
>snip
> russbucket wrote:
> > The error_log doesn't show much. Just this:
> > E [10/Jan/2006:16:12:22 -0800] PID 7024 stopped with status 0!
>
I posted an error_log to the bug report yesterday (00030190 but when I try to
log in today a
On Saturday 14 January 2006 22:37, Craig Ringer wrote:
> russbucket wrote:
> > Craig, thanks for responding so fast. I need to review how to turn on the
> > debugging, then I'll try that. I'll also check the other items you
> > mentioned. I'll post again after I try this stuff. The previous release
russbucket wrote:
> Craig, thanks for responding so fast. I need to review how to turn on the
> debugging, then I'll try that. I'll also check the other items you mentioned.
> I'll post again after I try this stuff. The previous release of Scribus
> worked fine with my Epson printer thru CUPS.
russbucket wrote:
> Actually I print the file I saved from Scribus (.sla) using lpr from the
> command line an it prints fine.
This still doesn't rule out a problem with the generated PostScript; it
could be an issue triggered by a setting in the PPD file you're using
(which AFAIK isn't used w
russbucket wrote:
> The error_log doesn't show much. Just this:
> E [10/Jan/2006:16:12:22 -0800] PID 7024 stopped with status 0!
Please turn on debug logging in CUPS and try again. I expect to see a
GhostScript error, but it could be something else.
Gregory Pittman wrote:
> It's hard
On Saturday 14 January 2006 09:38, Gregory Pittman wrote:
> russbucket wrote:
> > I sent the following to the CUPS group. Response was it looks like
> > Scribus problem.
> >
> > SuSE10.0 boxed version, Cups 1.1.23-21, Scribus 1.2.4-1, QT 3.3.4, USB2.0
> > using libusb. When I check thru admin it ju
On Saturday 14 January 2006 12:41, Craig Ringer wrote:
> russbucket wrote:
> > The error_log doesn't show much. Just this:
> > E [10/Jan/2006:16:12:22 -0800] PID 7024 stopped with status 0!
>
> Please turn on debug logging in CUPS and try again. I expect to see a
> GhostScript error, but it
russbucket wrote:
> I sent the following to the CUPS group. Response was it looks like Scribus
> problem.
>
> SuSE10.0 boxed version, Cups 1.1.23-21, Scribus 1.2.4-1, QT 3.3.4, USB2.0
> using libusb. When I check thru admin it just shows the job as aborted.
> More common on ps jobs. The printer p
I sent the following to the CUPS group. Response was it looks like Scribus
problem.
SuSE10.0 boxed version, Cups 1.1.23-21, Scribus 1.2.4-1, QT 3.3.4, USB2.0
using libusb. When I check thru admin it just shows the job as aborted.
More common on ps jobs. The printer prints fine with lpr (actually
18 matches
Mail list logo
