According to bug 569543, the cause is because gwibber tries to parse
user data which is only sent to gwibber the first time the gwibber
application is authorized for a given facebook account. Is there anyone
affected by this bug who is a first-time user of gwibber?

Workaround that works for me:
- Sign into Facebook using a web browser
- Click Account, then Application settings
- in the Show drop-down, select Authorized
- Scroll to the Desktop Applications section at the bottom of the page
- click the X to delete Gwibber
- re-add your facebook account to gwibber as usual

(Note that my FB accounts have a username from facebook.com/username; I
do not know if this is a factor, but previous documentation indicates
that this is also required by gwibber.)

This bug is still a problem because the root cause hasn't been resolved
-- it's not possible to e.g. add the account to multiple gwibber
instances because the data is only available to the first computer where
you add the facebook account to gwibber. (IIRC, removing the app from
Facebook /should/ cancel previous authorizations for other instances of
gwibber.) It appears that the SRU in intended to prevent someone from
adding an invalid account entry to gwibber, but it also makes the
original bug more obvious because you suddenly can't add accounts that
you thought you could add before.

-- 
Can not add Facebook account as add button not displayed after authorisation.
https://bugs.launchpad.net/bugs/595265
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to