Bug 326375 - Add account dialog should explicitly say to use "facebook's username", not email used to sign in
Summary: Add account dialog should explicitly say to use "facebook's username", not em...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Facebook Resource (show other bugs)
Version: 4.11
Platform: Kubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Martin Klapetek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-21 11:37 UTC by Alaa
Modified: 2017-01-07 22:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alaa 2013-10-21 11:37:46 UTC 
After inserting the username and the password the page goes to "SUCCESS" but akonadi never really get the facebook data.

Reproducible: Always

Steps to Reproduce:
1.go to system settings>personal information>add>Facebook.
2.click Authenticate>enter username and password.
3.click log-in.
Actual Results:  
you hit the "SUCCESS" page.

Expected Results:  
go seamlessly to the "success" page,close the window and then start getting the data from my account on facebook,like events,contacts,....etc
Comment 1 Alaa 2013-10-22 07:43:41 UTC 
To fix this bug,you will have to sign in to Facebook from Akonadi with the username and not the email address.

Get your username from facebook like explained here:https://www.facebook.com/help/www/211813265517027?rdrhc

and then log in with that username.
Comment 2 Daniel Vrátil 2013-10-22 09:30:45 UTC 
Should probably be mentioned somewhere in the dialog then.
Comment 3 Denis Kurz 2016-09-24 20:40:32 UTC 
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:42:22 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.