Thank you, James. That log is frustratingly quiet. It looks mostly normal until it is filled with zeros. It's doesn't help me much.
The last line is kind of interesting. Cups, the print service, tried to do something that the security policy didn't allow. IF you're having problems with that too, you might file a bug and attach that. I'd title it "cups apparmor profile denied 'block_suspend' capability". Dec 16 13:03:43 jamesmaz-K54C kernel: [ 8949.398708] type=1400 > audit(1387217023.287:29): apparmor="DENIED" operation="capable" parent=1 > profile="/usr/sbin/cupsd" pid=891 comm="cupsd" pid=891 comm="cupsd" > capability=36 capname="block_suspend" > > \00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\ > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250174 Title: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang() To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1250174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
