After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 613014 - initial account creation window gives no indication of successful account creation
initial account creation window gives no indication of successful account cre...
Status: RESOLVED DUPLICATE of bug 615271
Product: empathy
Classification: Core
Component: Accounts
2.29.x
Other Linux
: Normal enhancement
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2010-03-16 08:16 UTC by Omer Akram
Modified: 2010-09-13 15:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Omer Akram 2010-03-16 08:16:44 UTC
"I tried creating accounts for Facebook, AIM, Yahoo! and GoogleChat by running the "Messaging and VOIP accounts" item from the System/Preferences menu.

I entered Facebook account info, selected Yes to indicate I wanted to enter other accounts and then hit forward. Instead of getting a message telling me that my Facebook credentials had been successfuly authenticated and the account was set up, I was unceremoniously dumped back to the Account creation page, again showing Facebook as the type. So, I re-entered account information thinking that I had messed up, or there was some sort of problem.

I did this several times before I realized that I was not getting any success message.

empathy-accounts needs to either popup or present a Success or Failure page when creating accounts to ensure users know that they don't have to re-enter the same login info again."

originally reported at: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/539243
Comment 1 Guillaume Desmottes 2010-09-13 15:26:49 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 615271 ***