This was quite a strange one to track down, but in the short of it,
~/.config/dconf needs to be bind-mounted into the container. When xchat
would read gconf settings, they would always return null even though it
just set the key. This is due to how gconf settings are written and
read.
When writing a key, it goes over dbus. In our case, since we have the
dbus session bride, the host ~/.config/dconf/user backend would get
updated. However, when reading a key, it tries to read directly from
the file and since the backend was not bind-mounted, the container's
backend did not have any info in it.
At any rate, the fix is to bind-mount the ~/.config/dconf directory.
** Changed in: libertine
Status: New => In Progress
** Changed in: puritine
Status: In Progress => Invalid
** Changed in: libertine
Importance: Undecided => High
** Changed in: libertine
Assignee: (unassigned) => Christopher Townsend (townsend)
** Also affects: libertine (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libertine (Ubuntu)
Status: New => In Progress
** Changed in: libertine (Ubuntu)
Importance: Undecided => High
** Changed in: libertine (Ubuntu)
Assignee: (unassigned) => Christopher Townsend (townsend)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535421
Title:
Xchat: doesn't connect doesn't store info once added
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1535421/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
