Linux Lite Forums
Hardware - Support => Printing and Scanning => Topic started by: Yoru3 on February 21, 2015, 06:55:32 AM
-
Hi all,
Not sure if this is the right place since it might be more of a bug type report, unless I've missed something very basic. Also I can't believe that it hasn't been reported before, but I'm blowed if I can see it mentioned.
Anyway, it's about the printer (presumably driver) crashing when you inadvertently try and print a file that does not have the correct permissions.
I was recently setting up a minidlna server on Linux Lite, and set about editing its configuration file. By default, this file is set to user and group minidlna, with read only for other users.
So I had no problem opening the file in leafpad. but problems began when I tried to print it. The first thing is the output got stuck in the spooler, so I had to delete the job. Then I got a message displayed top right saying “printer may not be connected”. Even after a system restart, the same message appeared, and no print functionality could be achieved. The only way to get the printer working again was to remove it, and add it back again, which was straightforward, but a somewhat extreme way to recover.
I'm using a networked Epson Stylus Photo PX710W setup in pass through mode. After re-adding the printer and doing a chmod 777 on the file all was well for printing and configuring the file. Incidentally, minidlna now works great, much less of a pain than mediatomb. But surely shouldn't there be something in the system as a precursor, that stops this printer crash occurring, and gives a warning message box, maybe a watchdog script somewhere.