> On Sat, Mar 9, 2019 at 5:15 PM ToddAndMargo via users
> <users(a)lists.fedoraproject.org <mailto:users@lists.fedoraproject.org>>
> wrote:
>
> On 3/9/19 4:49 PM, Jack Craig wrote:
> > this may be foolish, but have you swapped out cable & printer to
> rule
> > them out?
>
> Hi Jack,
>
> I booted of a Flash a drive I have Fedora 29 installed on. The
> printer printed perfectly over lp0.
>
> Then whilst still being booted into the flash drive, I did
> my updates, which I had ignored for a long time. After
> that the flash drive would not print either and with the same
> symptom.
>
> And yes, before that, I did check the cables. They
> were attached very securely. Life should be so easy.
>
> And the printer does print off its USB interface, but it is one
> of those old printers where the USB was done really poorly
> and it can get through printing an single invoice. And
> I need to get my billing out so as I can put food on the table.
>
> Something is buggering up lp0. I doubt it is CUPS either.
On 3/9/19 11:57 PM, Jack Craig wrote:
you looked at this link?
https://fedoraproject.org/wiki/How_to_debug_printing_problems#Which_drive...
ok, so i had a recent network printer problem. i would ctrl p, fill in
parm & print. the job simply evaporated!
i traced it to a munch filter path name, but didnt use the above link &
wish i had...
what do you have in ...
*ls -l /etc/cups/ppd*
*
*
*??*
Hi Jack,
CUPS is not causing it. I can NOT write directly to the port:
# echo -ne abc \\f > /dev/lp0
bash: /dev/lp0: Device or resource busy
# lsof | grep lp0
parallel 14949 lp 5w CHR
6,0 0t0 26621 /dev/lp0
# kill -9 14949
# echo -ne abc \\f > /dev/lp0
^C
bash: history: write error: Success
# lsof | grep lp0
<nothing>
Note that the redirect to lp0 hanged and had to be <ctrl><C>'ed. And
then it said success. Hmmmm...
-T