On Mon 11 Dec 2017 at 09:01:58 +0000, Brian Potkin wrote:
> On Sun 10 Dec 2017 at 22:53:02 +0530, P V Mathew wrote:
>
> > Thanks for all the help.
> >
> > Just uninstalled AppArmor and
> > rebooted the system.
> >
> > Everything fine now.
> >
> > Even localhost:631 is fine.
>
> Excellent.
>
> > Sorry once again for the trouble.
>
> It was an interesting issue; no trouble.
But now I would like to impose on your good will.
I do not know if you are aware of it, but apparmor has been activated
as an experiment in buster to see if it would be suitable in a stable
release. Would you reinstall it and look for "audit" in journalctl or
syslog when your printing fails and the connection to localhost:631
resets. It would be useful for us to have any error messages.
Cheers,
Brian.