Ok, here's what I did.
I adapted the instructions from this comment: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/816554/comments/4
adding "owner /var/jay/.local/share/telepathy*/ rw," and the like to my /etc/apparmor.d/usr.lib.telepathy file, then running:
sudo apparmor_parser -r /etc/apparmor.d/usr.lib.telepathy
Empathy is now successfully saving logs, even though @{HOME}/.local/share/telepathy*/ is a symlink to /var/jay/.local/share/telepathy*/
Is it the symlinking that is causing this problem? I assume that it is. Why does apparmor balk at this symlink?
Ok, here's what I did.
I adapted the instructions from this comment: https:/ /bugs.launchpad .net/ubuntu/ +source/ telepathy- mission- control- 5/+bug/ 816554/ comments/ 4
adding "owner /var/jay/ .local/ share/telepathy */ rw," and the like to my /etc/apparmor. d/usr.lib. telepathy file, then running:
sudo apparmor_parser -r /etc/apparmor. d/usr.lib. telepathy
Empathy is now successfully saving logs, even though @{HOME} /.local/ share/telepathy */ is a symlink to /var/jay/ .local/ share/telepathy */
Is it the symlinking that is causing this problem? I assume that it is. Why does apparmor balk at this symlink?