On Mon 11 Dec 2017 at 20:02:42 +0000, Brian Potkin wrote: > On Mon 11 Dec 2017 at 22:28:15 +0530, P V Mathew wrote: > > > dmesg showed some sort of infinite loop? > > > > Oops. realize now, may be about 2-3 years ago when my var partition got > > full, > > > > had moved the var/log on to /home/ and sym-linked to it in var. May be > > > > this is not consistent with apparmor(not sure?). > > When I do that I can still print but the error_log is not written to > because cupsd cannot change the permissions on /var/log/cups (as shown > by systemctl status cups after restarting cups).
I reckon the location of /var/log and the permissions on it is the cause of your getting an empty error_log and has nothing to do with the subject of your report. It would occur whether or not apparmor is installed. You can check this. > > any way, pieces of dmesg|grep cups attached. Not possible to attach full > > > > file as similar lines keeps repeating. > > > > Please let me know if any more input is required. > > Thanks, Mathew. > > From bb.bbz2: > > [ 2121.775238] audit: type=1400 audit(1513009058.480:17316): > apparmor="DENIED" \ > operation="chown" profile="/usr/sbin/cupsd" > name="/home/log/cups/" \ > pid=5896 comm="cupsd" requested_mask="w" denied_mask="w" > fsuid=0 ouid=0 > > [ 2121.775251] audit: type=1400 audit(1513009058.480:17317): > apparmor="DENIED" \ > operation="capable" profile="/usr/sbin/cupsd" pid=5896 > comm="cupsd" \ > capability=12 capname="net_admin" > > apparmor is new to buster and I am new to apparmor; but this looks like > cupsd has been refused write permission. > > intrigeri is our lifeline for things apparmor, so I have cc'ed him (her?) > for advice. I missed this in bb.bz2: [ 2153.319653] cupsd[5896]: segfault at c ip 00007f36a1f13f46 sp 00007ffc5bb5ba28 error 4 in libc-2.25.so[7f36a1e92000199000] You did say cupsd crashed? I am out of my depth with this sort of thing but came across https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052 Please read and carry out the instructions in message #38 there. You don't need sudo. How do you go on? Cheers, Brian.
