#52 Even more interesting (at least to me), and no please there's nothing to apologize about ^_^
I'm wondering if this could be related to the other "bug" where the workaround is to use a different DNS server like GoogleDNS or OpenDNS or Level3's?? (But I'm on GoogleDNS already.) I dunno, maybe this is Facebook's already. My Gwibber to Facebook posting has never been good since this bug and the other bug started. Facebook might be blocking Gwibber or something, because if I try using a different app or way to post to FB, it works instantly. But Gwibber to Facebook posting lasts for 3 posts only on average and then stops. I have to wait for at least 12 hours before Gwibber can post to my account again. Or maybe a change in FB's API? But either way, as I've notice in another test earlier, Gwibber thinks the authorization was successful when it was not. See this attachment: http://launchpadlibrarian.net/50676912/gwibber.zip It shows the difference between a fake-successful authorization (the Add button doesn't show up) vs. a real-successful authorization (the Add button shows up). Even the wording is different. The fake-successful authorization doesn't show our name while the real-successful authorization shows our name. -- 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
