empathy no longer allows for extended jabber configuration

Bug #1044057 reported by Jamie Strandboge
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Invalid
Medium
Unassigned
Quantal
Invalid
Medium
Unassigned

Bug Description

I have been using Empathy for a longtime, primarily for Jabber to a private network. Recent updates in 12.10 imported my previous settings ok, but I am no longer able to edit those settings because when I click Empathy/Accounts from the global menu, I get the Online Accounts setup, and it doesn't seem to know about my previous setup. Furthermore, if I try to add a jabber account, the account setup is far too limited with only a jabber id and password presented, which prevents me from using empathy with the aforementioned private network.

Revision history for this message
Guillaume Desmottes (cassidy) wrote :

Actually, you can create your account using the 'simple' account widget and then change its advanced settings later.

The real bug here is that your account has been migrated to Ubuntu Online Accounts but doesn't appear in the UOA panel.
Which Empathy version are you using? Could you please post the output of 'mc-tool dump' ? (mission-control 5.13.1 needed).

tags: removed: rls-q-incoming
Changed in empathy (Ubuntu Quantal):
importance: Undecided → Medium
status: New → Confirmed
milestone: none → ubuntu-12.10-beta-2
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

This is on quantal. Empathy version 3.5.90-0ubuntu4. 'mc-tool dump' has a lot of private information in there. Here is a redacted version for the affected account:
     Account: gabble/jabber/<redacted>_40jabber_2e<redacted>_2ecom1
Display Name: <redacted>@jabber.<redacted>.com
  Normalized: <redacted>@jabber.<redacted>.com
     Enabled: enabled
        Icon: im-jabber
    Connects: only when requested
    Nickname: <redacted>
     Service: jabber

Presences:
   Automatic: available (2) ""
     Current: available (2) ""
   Requested: (2) ""
    Changing: no

        (bool) old-ssl = true
        (bool) require-encryption = true
        (uint) port = 5223
        (bool) register = false
      (string) resource = <redacted>
      (string) account = <redacted>@jabber.<redacted>.com
        (bool) ignore-ssl-errors = true

Revision history for this message
Guillaume Desmottes (cassidy) wrote :

The import code has been improved in 3.5.91.1 I'd be interested to see the logs when trying to re-import using this version.

Could you please once 3.5.91.1 has reached Ubuntu:
- Make sure any Empathy account is configured and not empathy process is running (especially empathy-auth-client)
- gsettings set org.gnome.Empathy sanity-cleaning-number 0
- EMPATHY_PERSIST=1 EMPATHY_DEBUG=all G_MESSAGES_DEBUG=all EMPATHY_LOGFILE=/tmp/auth.log /usr/lib/empathy/empathy-auth-client
- Attach /tmp/auth.log

Revision history for this message
Jamie Strandboge (jdstrand) wrote :
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

I did created auth.log using empathy 3.5.92-0ubuntu2.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Is that still an issue?

@Guillaume: subscribed you since you asked for a log and I'm not sure you were still watching the bug ;-)

Changed in empathy (Ubuntu Quantal):
milestone: ubuntu-12.10-beta-2 → quantal-updates
Revision history for this message
Guillaume Desmottes (cassidy) wrote :

The import code isn't run in this log. Are you sure you reset the sanity-cleaning-number gsetting key before ?

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

$ gsettings set org.gnome.Empathy sanity-cleaning-number 0
$ EMPATHY_PERSIST=1 EMPATHY_DEBUG=all G_MESSAGES_DEBUG=all EMPATHY_LOGFILE=/tmp/auth.log /usr/lib/empathy/empathy-auth-client
...

Attaching new auth.log

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

FYI, I can see that I can configure the advanced options after creating the account initially.

Changed in empathy (Ubuntu):
status: Confirmed → Invalid
Changed in empathy (Ubuntu Quantal):
status: Confirmed → Invalid
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.