Empathy doesn't remember favorites, chat logs when ~/.local is a symlink
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
empathy (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
After upgrading to Oneiric, all of my Empathy favorites have been forgotten. Setting them again doesn't survive a logout/login cycle.
I now think this may be due to the fact that I keep my /home/jay/.local directory as a symlink to /var/jay/.local on my SSD (and the same with ~/.cache). This didn't used to be a problem in Natty, so I don't know what changed.
syslog shows these messages when I try to add a favorite or when i send/receive a message, respectively:
Oct 27 20:09:56 jay-desktop kernel: [112564.420709] type=1400 audit(131976059
Oct 27 20:27:13 jay-desktop kernel: [113599.103628] type=1400 audit(131976163
I changed some permissions on the folders in /var/jay/.local (and applied to sub-folders, probably an awful idea) and the problem remained.
I adapted the instructions from this comment: https:/
adding "owner /var/jay/
sudo apparmor_parser -r /etc/apparmor.
Empathy is now successfully saving logs, even though @{HOME}
Is it the symlinking that is causing this problem? I assume that it is. Why does apparmor balk at this symlink?
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: empathy 3.2.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-12-
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Fri Oct 14 18:48:13 2011
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.utf8
SourcePackage: empathy
UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago)
XsessionErrors:
(SparkleShare:
(gwibber-
summary: |
- Empathy doesn't remember favorites after logout + Empathy doesn't remember favorites after desktop logout |
description: | updated |
description: | updated |
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.