@Omer: Bug 530195 is a long and confusing one :) with many different symptoms and possible root causes/code bugs/solutions. For example: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/530195/comments/51 (changing DNS didn't work); Comments 54 and 57 (CouchDB not running); Comment 58 (unknown - gwibber-service not running?); Comments 59, 62, 63 (unknown); Comment 69 (auth errors hidden); Comment 80 (locale setting problem)...
Although some of the 'Solved, working' comments in bug 530195 *are* related to DNS, plenty of others are not. In contrast, in this bug itself, by comment 7 we have already established that this error in log output: "error: (6, 'name lookup timed out')" means it is a DNS failure causing this particular problem. I think that this bug is a nice, short, straight-line test for whether Gwibber Twitter problems are due to DNS failures; if people reading this bug fail to find the given error message in their debug output, then they would, of course, search the many other Gwibber bugs, for symptoms matching the ones they see. Therefore, I've just changed this bug's title to include the defining error message from the log; hopefully people can find this bug, and get a potential solution, quickly. It's up to you, Omer, if you want to mark this as a duplicate of the other bug; I don't think it's a good idea because as cited above, there are too many suggestions and different problems in the other bug, while this one, so far, nails down exactly one problem. Thanks, Ed. -- Gwibber does not receive twitter messages [error: (6, 'name lookup timed out')] https://bugs.launchpad.net/bugs/571858 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
