Some online accounts cannot be added

Status changed to 'Confirmed' because the bug affects multiple users.

Also happens with AIM.

Same Problem with ICQ (account-plugin-icq). "dmesg | tail" shows "gnome-control-c[6323]: segfault at 38 ip 00007fb9db706809 sp 00007fff89616a00 error 4 in libempathy-gtk-3.6.4.so[7fb9db6d1000+ab000]"

Generally speaking, it happens with accounts that are not using browser authorization. For me, any type of "waiting workaround" is not working, I just have to restart system in order to set up ICQ account. It messes up again after removing and trying to re-add, and unfortunately, at least ICQ plugin is not working at all (and I believe it is connected to this bug).

@Jakub, same problem here, can't add am AIM account at all, waiting does not work. It just sits there indefinitely and the part to enter the username/password never appears. Seems to happen with all the non browser based plugins. And in the rare event it does appear and let me add the account, upon a reboot the account stops working again, and when you try to remove/re-add it it doesn't appear again.

actually I'm not sure I can reproduce this anymore after installing from the latest raring ISO. my aim account appears to be working fine as are facebook and google. I will need to test for a few days to confirm, because last time I thought this was fixed it came back after a day, but I'm crossing my fingers.

Nevermind :(, still does it. bug seemed to have been triggered after the first time I suspended the freshly installed raring to ram. after resume the aim account refused to reconnect, and trying to add an aim/jabber account in UOA is messed up again, it just sits there and doesnt bring up the spot to enter my credentials, and then gnome-control-center crashes with the SIGSEGV message in this bug report.

i still can't connect my irc account. also i'm getting apparmor messages in kernel log:

[ 22.934104] type=1400 audit(1365804121.486:22): apparmor="DENIED" operation="file_mmap" parent=1 profile="/usr/lib/telepathy/telepathy-*" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.11/modules/config_gnome3.so" pid=2680 comm="telepathy-gabbl" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

not sure these messages are related.

also i'm getting (after clicking "allow access" to my irc account):
"Applications can no longer access your <username> at <server> Online account. Choose Online Accounts from the user menu to reinstate access to this account."

As of now (24-4-13), it seems as though the online accounts dialogue no longer is crashing. However, I am still unable to create or edit Yahoo or AIM accounts. I have tested doing a purge and reinstall of empathy and all telepathy packages, and under the guest account. The dialogue with "Please enter your account details" appears, with cancel and done buttons, but no fields for actually entering any details ever appears. This also occurs *sometimes* for Jabber accounts. Let me know if there are any additional details I can provide.

I tested this on a live cd, and was able to create a new yahoo account in Online Accounts. It would seem then that the problem is related to having upgraded my system versus doing a fresh install. However, since the problem occurs even under the guest accounts, the issue must not be anything in my user-level configuration - it is system-wide. I'm pretty confused though, as I have done a apt-get remove --purge and reinstall of every package I thought relevant. I'm out of ideas as to how to track this down. I'm also not sure if this is even the same bug, as I'm not experiencing a crash anymore.

I'm not experiencing a crash anymore too, but the screen for entering the information is never shown or done after so much time.

Looks like this bug affects both existing accounts and the creation of new ones. After upgrading from 12.10 to 13.04, the only client working for me was Google. My other existing accounts for AIM, Yahoo and ICQ did not appear to be working. I decided to remove my AIM account and re-add it. Like the others above, the login details screen is blank.

Wish I hadn't upgraded my work computer now. I use IM extensively to keep in touch with co-workers and clients. I've been in the dark since upgrading.

Scott -
I use AIM for work as well. I've installed pidgin (an alternate IM
client) so I can still communicate until this bug is resolved.

On 05/02/2013 07:20 AM, Scott Hinton wrote:
> Looks like this bug affects both existing accounts and the creation of
> new ones. After upgrading from 12.10 to 13.04, the only client working
> for me was Google. My other existing accounts for AIM, Yahoo and ICQ did
> not appear to be working. I decided to remove my AIM account and re-add
> it. Like the others above, the login details screen is blank.
>
> Wish I hadn't upgraded my work computer now. I use IM extensively to
> keep in touch with co-workers and clients. I've been in the dark since
> upgrading.
>

also affects ICQ accounts. I installed the ICQ backend for Empathy and tried to create an account, but the account creation screen is just blank. It does work for Jabber (which I guess is not based upon a website log-in like google or facebook accounts).

Version is Ubuntu 13.04

This seems to be a duplicate of bug #1147639. Steffen (and others), if you still can reproduce it, can you please tell me what version of the following packages do you have installed?

- telepathy-mission-control-5
- empathy

Thanks!

telepathy - mission-control-5 - 1:5.14.0-0ubuntu2
empathy - 3.6.4-0ubuntu4

telepathy-mission-control-5 1:5.14.0-0ubuntu2
empathy 3.6.4-0ubuntu4

Thanks for the informations!
Alberto, I see that you reassigned the bug to yourself. Did you do that accidentally, or do you intend to work on fixing it yourself?

I reassigned the bug to me because I'm now testing if it is fix released, as the duplicated. But I run out of battery in my mouse when I was doing so, and I had to go to buy them! XD

The bug is still there, so it seems not to be a duplicate of bug #1147639.

I also experience this bug. I can temporarily add and edit configurations in Ubuntu Online Accounts (a.k.a. credentials-preferences) again by killing all empathy and telepathy processes, then loading the panel, but this behaviour recurs shortly after restarting empathy. The problem first started after I performed a release upgrade to 13.04 from 12.10. It happens under both Unity and Gnome. Blowing away the contents of ~/.config/libaccounts-glib allowed me to enter new account details again, but the bug returned later. (I also upgraded to gnome 3.8 via the Gnome team PPA, without any improvement.)

I see some errors in kern.log when reloading the accounts panel after restarting empathy:

 kernel: [ 526.559946] empathy-auth-cl[3249]: segfault at 200000028 ip 00007f909fb0261e sp 00007fff2c7dee10 error 4 in libaccounts-glib.so.0.1.3[7f909faf6000+19000]

Also various other warning messages (not sure how relevant):

(credentials-preferences:6073): credentials-cc-panel-WARNING **: cc-credentials-account-details-page.vala:346: Error looking up theme color
(gnome-control-center:8668): credentials-cc-panel-WARNING **: cc-credentials-login-capture.vala:61: Could not register service.
(gnome-control-center:8668): credentials-cc-panel-WARNING **: cc-credentials-login-capture.vala:33: Could not acquire name.

In addition to this bug, since upgrading to 13.04, I've been unable to connect to my AIM account in Empathy (which works fine in pidgin). Jabber connectivity seems okay, although sometimes Empathy fails to display anything at all in its Contact List until it's been killed and restarted a few times.

I'm attaching an apport crash report which hopefully contains more relevant details about the empathy-auth-client crash.

telepathy-mission-control-5 Version: 1:5.14.0-0ubuntu2
empathy Version: 3.6.4-0ubuntu4.1

My experience was similar to #14: Finally upgraded from 12.10 to 13.04 the other day, ICQ worked fine on first go after upgrade, but would not connect again after the computer had been suspended. Removed account, but can't add it again because UIN/pass fields are missing.

...has this ever been addressed? I'm currently forced to use Pidgen, but that has its own issues....

I don't know. I'm using pidgen again. Unity's messenger seems more broken
now.
On Aug 5, 2013 2:21 PM, "GonzO" <email address hidden> wrote:

> ...has this ever been addressed? I'm currently forced to use Pidgen,
> but that has its own issues....
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1159411
>
> Title:
> Some online accounts cannot be added
>
> Status in “gnome-control-center-signon” package in Ubuntu:
> Triaged
>
> Bug description:
> ********************
> HOW TO REPRODUCE
> ********************
> 1. Go to "System settings -> Online accounts".
> 2. Select to add a "AIM" new account.
> 3. Click on the "done" button.
>
> ***********
> BEHAVIOUR
> ***********
> - EXPECTED: An account to be created.
> - REAL: No account is added, because the screen for entering the
> information is never shown.
>
> ************
> WORKAROUND
> ************
> You can write the following line into the Terminal to get a fully
> working instant messaging client: sudo apt-get install pidgin -y && pidgin
>
> ******************
> RELEVANT DETAILS
> ******************
> - It affects AIM, ICQ, Salut, Jabber and Yahoo! accounts.
> - AIM and Yahoo!' never work.
> - Salut and Jabber' work a few times, not clear when they do.
> - Affects both existing accounts and the creation of new ones.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 13.04
> Package: gnome-control-center 1:3.6.3-0ubuntu16
> ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
> Uname: Linux 3.8.0-14-generic x86_64
> ApportVersion: 2.9.2-0ubuntu2
> Architecture: amd64
> Date: Sun Mar 24 14:08:46 2013
> ExecutablePath: /usr/bin/gnome-control-center
> InstallationDate: Installed on 2013-03-23 (0 days ago)
> InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64
> (20130323)
> MarkForUpload: True
> ProcCmdline: gnome-control-center
> ProcEnviron:
> SHELL=/bin/bash
> XDG_RUNTIME_DIR=<set>
> PATH=(custom, no user)
> LANG=es_ES.UTF-8
> SegvAnalysis:
> Segfault happened at: 0x7f8c10069809
> <empathy_account_widget_apply_and_log_in+9>: mov 0x38(%rdi),%rax
> PC (0x7f8c10069809) ok
> source "0x38(%rdi)" (0x00000038) not located in a known VMA region
> (needed readable region)!
> destination "%rax" ok
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: gnome-control-center
> StacktraceTop:
> empathy_account_widget_apply_and_log_in () from /usr/lib/empathy/
> libempathy-gtk-3.6.4.so
> g_cclosure_marshal_VOID(int0_t, void) () from
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> g_signal_emit_valist () from
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> Title: gnome-control-center crashed with SIGSEGV in
> empathy_account_widget_apply_and_log_in()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> XsessionErrors:
> (gnome-terminal:2352): Vte-2.90-WARNING **: No se pueden c...

I *think* I am also experiencing this with Google accounts. It does log in to some of the elements, but then continues to indicate each time I reboot that I needs me to re-enter my password (perhaps for Google Docs or something I'm not sure)

Ubuntu 13.04 x32

shaneonabike, it appears to me that the problem you are trying to describe needs to be handled in a new bug report. If you need further information about how to create a new report, you can have a look at http://wiki.ubuntu.com/DebuggingProcedures.

Thank you

Completely unable to add a simple IRC account in fresh install of Ubuntu 13.10. The accounts dialogue complains about "Giving Ubuntu access", and hitting the "Grant" button just makes the same message reappear instantly. (Ubuntu 13.10 is turning out to be a really hard fight overall.)

Hi Øyvind, can you provide a screenshot for this (or even better, a video)? I don't understand how this can happen: IRC doesn't require any authorization (not even a password!), it only requires that one chooses which IRC network to connect to, and a nickname.
I just tried on my machine, and I didn't see any request for access.

Alberto Mardegan <email address hidden> writes:

> Hi Øyvind, can you provide a screenshot for this (or even better, a video)? I
> don't understand how this can happen: IRC doesn't require any authorization (not
> even a password!), it only requires that one chooses which IRC network to
> connect to, and a nickname.
> I just tried on my machine, and I didn't see any request for access.

Hi,

1. Add new IRC account (I tested Freenode), input nick and hit done.

2. Things seem ok, it connects in Empathy (even though the Empathy
   connection button in accounts dialog isn't enabled yet, which is surprising.)

3. I have a registered nick at Freenode, so I need to provide password
   for NickServ at login. Hit "edit options" in accouts dialog and input
   a password, then hit done.

4. Now the access trouble starts (and Empathy disconnects).

Øyvind

Added screencast which demonstrates problem.

On 11/20/2013 02:55 PM, Øyvind Stegard wrote:
> 1. Add new IRC account (I tested Freenode), input nick and hit done.
>
> 2. Things seem ok, it connects in Empathy (even though the Empathy
> connection button in accounts dialog isn't enabled yet, which is surprising.)

I noticed as well. It's harmless, but it's indeed a bug.

> 3. I have a registered nick at Freenode, so I need to provide password
> for NickServ at login. Hit "edit options" in accouts dialog and input
> a password, then hit done.
>
> 4. Now the access trouble starts (and Empathy disconnects).

Ah, I didn't find that. It seems that Empathy fails to connect if a
password is given; without password, it can connect (even though then
nickserv asks you to identify).
However, this is a separate issue from the original bug. Do you mind
reporting a new one (just for this IRC issue)?

Alberto Mardegan <email address hidden> writes:

[...]

> Ah, I didn't find that. It seems that Empathy fails to connect if a
> password is given; without password, it can connect (even though then
> nickserv asks you to identify).
> However, this is a separate issue from the original bug. Do you mind
> reporting a new one (just for this IRC issue)?

Done:

https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1253096

Øyvind

Thanks Øyvind!