[Bug 990443] [NEW] apparmor doesn't let telepathy-logger directory to be symlinked

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Experienced while running Ubuntu 11.10 and 12.04 LTS.

Version of Empathy (12.04 LTS): 3.4.1-0ubuntu1

For backup and multiboot reasons, i symlink /home/{user}/.local/share/TpLogger to /media/mainhome/{user}/.local/share/TpLogger in order to have a shared place for backing up conversation logs.
I use this approach for a number of applications, and It works perfectly fine across multiple linux distributions.

However when I try to do the some for Empathy, this doesn't work.

What is expected: I setup my Empathy accounts, then symlink the log
directory. Empathy will read from/store logs to the symlinked location.

What happens: I setup my Empathy accounts, then symlink the log
directory. Empathy reads existing logs from the symlinked location but
is unable to store/create new logs.

>From the dmesg output, I'm almost certain this is due to apparmor
profiles. The output is attached, it show the relevant output of two
different account (Facebook and GTalk) trying to write in the log
directory.

I've been able to workaround the issue by adding the following lines to
/etc/apparmor.d/usr.lib.telepathy under

    owner @{HOME}/.local/share/TpLogger/   rw,
    owner @{HOME}/.local/share/TpLogger/** rwk,

# MY ADDS

	owner /media/mainhome/[USER]/.local/share/TpLogger/   rw,
	owner /media/mainhome/[USER]/.local/share/TpLogger/** rwk,

Could this be done distro-wise?

** Affects: telepathy-logger (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: bot-comment
-- 
apparmor doesn't let telepathy-logger directory to be symlinked
https://bugs.launchpad.net/bugs/990443
You received this bug notification because you are a member of Telepathy, which is subscribed to telepathy-logger in Ubuntu.