Xchat: doesn't connect doesn't store info once added

Bug #1535421 reported by Dave Morley
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Pocket Desktop
Fix Committed
Undecided
Unassigned
Libertine
Status tracked in Devel
Devel
Fix Released
High
Christopher Townsend
Trunk
Fix Released
High
Christopher Townsend
Puritine
Invalid
High
Christopher Townsend
libertine (Ubuntu)
Fix Released
High
Christopher Townsend

Bug Description

I assume this is either a permissions but or an issue with the container but:
If you open xchat-gnome you are requested to add a nick and a user. If you click on continue the system looks like is it going to connect it then tells you that it can't connect not all the details are there, If you drop down the preferences menu user name and nick are now empty again.

You however can't seem to be able to add these details and have them save. If you close the app and open it again it asks you for the same details like it did the first time.

Related branches

Dave Morley (davmor2)
tags: added: qa-manual-testing
Revision history for this message
Christopher Townsend (townsend) wrote :

Yeah, I can confirm this as well. Will investigate.

Changed in canonical-pocket-desktop:
status: New → Confirmed
Changed in puritine:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Christopher Townsend (townsend)
Revision history for this message
Christopher Townsend (townsend) wrote :

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
assignee: nobody → Christopher Townsend (townsend)
Changed in libertine (Ubuntu):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Christopher Townsend (townsend)
Revision history for this message
Libertine CI Bot (libertine-ci-bot) wrote :

Fix committed into lp:libertine at revision 170, scheduled for release in libertine, milestone Unknown

Changed in libertine:
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libertine - 0.99.10+16.04.20160208.1-0ubuntu1

---------------
libertine (0.99.10+16.04.20160208.1-0ubuntu1) xenial; urgency=medium

  [ Chris Townsend ]
  * data/libertine-lxc.conf: Remove the /etc/timezone & /etc/localtime
    bind-mounts. (LP: #1541524)
  * Add exception handling around the select calls to avoid "crashes" in
    the programs. (LP: #1541584)
  * Bind mount ~/.config/dconf/ so apps that programs that use it can read
    the correct gsettings data. (LP: #1535421)
  * libertine-container-manager: Add new "--force" option to force installation
    of Ubuntu distros that are no longer supported.

  [ Stephen M. Webb ]
  * fixed a spelling mistake in the container info page.

  [ CI Train Bot ]
  * No-change rebuild.

 -- Christopher Townsend <email address hidden> Mon, 08 Feb 2016 17:09:06 +0000

Changed in libertine (Ubuntu):
status: In Progress → Fix Released
Changed in canonical-pocket-desktop:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.