trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: June 2018

Re: [trinity-users] cups or tde belly ache, kmail can't print to cheap brother lazer

From: "E. Liddell" <ejlddll@...>
Date: Thu, 14 Jun 2018 22:27:35 -0400
On Thu, 14 Jun 2018 17:42:24 -0400
Gene Heskett <gheskett@...> wrote:

> On Thursday 14 June 2018 16:36:55 E. Liddell wrote:
> 
> > On Thu, 14 Jun 2018 13:03:02 -0400
> >
> > Gene Heskett <gheskett@...> wrote:
> > > Greetings all;
> > >
> > > I am in the process od transitioning to stretch, and there are some
> > > helpfull email messages I need to print.
> > > .  But I need to print them on a brother HL-2140, about a penny a
> > > sheet. not of the big ink squirter at 25 to 50 cents a sheet not to
> > > mention its in pages per hour speed.
> > >
> > > But when I send something to the little brother, knotify  pops up
> > > with the following message:
> > > A print error occurred. Error message received from system:
> > > Error while reading filter description for (bold>) true. Empty
> > > command line received.
> > >
> > > This printer is shared and works fine from any other machine on my 6
> > > machine home network, it only miss-behaves from kmail. Up to date
> > > TDE r14.0.0.5 install.
> >
> > Does it work from other programs on that machine?
> 
> Yes as expected.

[...]

The only other thing I can think of that might be useful is to check the CUPS
log ( /var/log/cups/error_log on my system, might need to change the message
level to get anything useful out of it).  Sometimes that reveals a bit more about
which filter's failing, anyway.

> > (Maybe someone else will have some more specific ideas--I've had some
> > interesting errors from my Brother multifunction, but not that one.)
> >
> I've wiresharked the data to an mfc-j6920.dw and had to grin a bit, when 
> sane tries to access its scanner, or the printer is being accessed, the 
> tcp command has a bad checksum the first 6 times the request is sent at 
> 1 second intervals, but then fixes it and the printer wakes up and does 
> its thing, using the brother drivers in that instance. So I can 
> appreciate your assessment of their driver "quality". Its not the 
> greatest. 

I had much worse problems than that (landscape mode not working, frex,
because the ppd was written for something like CUPS 1.3 and would
not play nice with 2.X at all).  Annoying as heck, and it isn't as though the
MFC-9130CW is an ancient piece of hardware.

E. Liddell