Looks like the final solution happened out of the list, so I'm posting 
my solution and the explanation of the cause in case anyone also runs 
into this problem.  It was actually caused by something I didn't know 
would happen in you ran out of hard drive space.

This is quoted from my email that was sent privately:

Looks like you have /tmp mounted onto an overflow file system which is
only 1 meg.  Any print document or any other program for that matter
that needs more than 1 meg of space will will have problems. My
understanding is that putting /tmp into ram drive is something the
system does automatically upon boot so that things don't break while
booting.

overflow            1024       44       980   5% /tmp
The above is the offending line.  Now that you've freed up space on
your root (/) partition a simple reboot should cause /tmp to be put
back in it's proper place.  Just double check after a reboot and see
if that line is gone.  You probably won't have anything mounted on
/tmp at all.

After all that I'm betting your printing should be back working as
normal, and likely your other weird behavior from your software will
be gone as well.

Brian Cluff

On 3/15/21 12:34 AM, Brian Cluff via PLUG-discuss wrote:
> If your root drive is still almost completely full the print job is 
> probably not printing because the print system is trying to write a 
> temp file with the print job in your printers native language which 
> can be quite large and running out of space to write it.
> You're probably seeing small and simple print jobs succeed while 
> larger print jobs with images are failing.
>
> I once had someone complaining that her 22 page document was taking a 
> very long time to print to a network attached printer. It turned out 
> that the 22 page document because of some bad formatting and large 
> embedded images had to be turned into an 800+ meg file in order to be 
> printed and then that file was having to be sent over a 100Mb 
> connection which just plain took a few minutes to complete the 
> transfer of the entire document to the printer, making for a very slow 
> print.  Since it was a document that would be printed a lot, the fix 
> was to recreate the document in a way that minimized the actual print 
> file size.
>
> Brian Cluff
>
> On 3/14/21 8:40 PM, joe--- via PLUG-discuss wrote:
>> Thanks John (and all) ...
>>
>> Now the display of different backgrounds on different
>> desktops (which had stopped working) has mysteriously,
>> and spontaneously started working again, even though
>> I made no changes.
>>
>> And Libre office, which was knot working, has started
>> working again, again, even though I made no changes.
>>
>> But now Libre office will print .odt documents with
>> plain text in portrait mode, but it will not print
>> an .odt document in landscape with an image in the
>> document.
>>
>> PS: I have Mint 17.2 Mate with Brother printer HL2270DW
>>
>> -------------
>> On 2021-03-14 8:26 pm, John Seberg via PLUG-discuss wrote:
>>> It shouldn't be too hard to figure out how to change
>>> the background image of your desktop.
>>>
>>> Let us know which version of Mint you're currently running:
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:
>> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> https://lists.phxlinux.org/mailman/listinfo/plug-discuss

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss