If you don't have an audit.log, check your normal syslog - AFAIK you'll find it as /var/log/syslog
Seeing the log messages would be helpful to confirm that this bug is really fixed in the latest upstream code, and might also help to convince the Ubuntu maintainers to release an update (these updates are not my job, therefore no promises on this ;-)
If you don't have an audit.log, check your normal syslog - AFAIK you'll find it as /var/log/syslog
Seeing the log messages would be helpful to confirm that this bug is really fixed in the latest upstream code, and might also help to convince the Ubuntu maintainers to release an update (these updates are not my job, therefore no promises on this ;-)