gwibber tries to call has_key on list---doesn't update streams

Hi!
Thanks for taking time to report this bug and make Ubuntu better. However, there is no enough information in your report to try to reproduce the bug.
Please open gwibber from a console and try to send as the output on the console after you try to send a tweet.
Regards
malev

When posting to Twitter, an icon in the top right of the window just spins. gwibber outputs this to stdout/stderr:

[vr 21:52] martijn@martijn-desktop:~$ gwibber

** (gwibber:27068): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (gwibber:27068): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (gwibber:27068): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
No dbus monitor yet
Updating...
ERROR:dbus.proxies:Introspect error on com.Gwibber.Service:/com/gwibber/Service: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1
Updating...
ERROR:dbus.proxies:Introspect error on com.Gwibber.Accounts:/com/gwibber/Accounts: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Accounts was not provided by any .service files
ERROR:dbus.proxies:Introspect error on com.Gwibber.Streams:/com/gwibber/Streams: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Streams was not provided by any .service files

I couldn't see anything on the twitter account in gwibber, until I posted my first tweet. After that it seems to be working right.

Please could you upgrade to latest version of gwibber (2.29.92-1) and check if this problem is still affecting you? Thanks in advance!

Ran gwibber-service -o -d and found out that for some reason the CA used by Twitter's API wasn't set to "Trusted".

dpkg-reconfigure ca-certificates and enabling it fixed it!

i can send tweets to twitter, but i do not get the home screen. Search for twitter works too, but it does not fetch any information for me. Facebook seems to work fine. Here is the outut

** (gwibber:19400): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (gwibber:19400): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (gwibber:19400): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
No dbus monitor yet
Updating...
Updating...
ERROR:dbus.proxies:Introspect error on com.Gwibber.Accounts:/com/gwibber/Accounts: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Accounts was not provided by any .service files
ERROR:dbus.proxies:Introspect error on com.Gwibber.Streams:/com/gwibber/Streams: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Streams was not provided by any .service files
/usr/bin/gwibber:68: GtkWarning: gtk_container_add: assertion `GTK_IS_CONTAINER (container)' failed
  gtk.main()

For those who still face this please Quit gwibber and delete ~/.cache/desktop-couch ~/.config/desktop-couch and ~/.local/desktop-couch and then add new account and see if the problem is still there.

$ sudo aptitude purge gwibber gwibber-service
$ cd
$ rm -rf .cache/
$ rm -rf .config/desktop-couch/
$ rm -rf .local/share/desktop-couch/
$ sudo aptitude install gwibber gwibber-service

Add twitter account. Not received messages. Received only replies.

And gwibber-service load processor 100%

$ gwibber-service -o -d
Gtk-Message: Failed to load module "pk-gtk-module": libpk-gtk-module.so: cannot open shared object file: No such file or directory
Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Thu Apr 8 22:51:34 2010 **
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 69, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 146, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 149, in receive
    return self._get("statuses/home_timeline.json", count=count, since_id=since)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 136, in _get
    if data.has_key("error"):
AttributeError: 'list' object has no attribute 'has_key'

Gwibber Dispatcher: INFO Loading complete: 1 - ['Failure', 'Success', 'Success']

Vitali, high cpu usage would be bug 554005

Omer, I use the latest version from Ubuntu Lucid beta 2.

This bug still exists. Twitter doesn't work at all. I got a few updates yesterday after closing the application and open it again but now it stopped again and I don't get any updates or anything else. Please help, this is a very serious issue. It's seriously not working. Also the "Me Menu" still says "Set up Broadcast account" and doesn't realize that I already set up the account. But If I press this "set up broadcast account" button it will launch the not working gwibber program.

I did nothing special on setup, normal twitter account.

I use amd64 with username=realname on a macbook pro.

If you need any special debug files or anything else, please tell me. This is important. Thanks.

Christopher, sudo apt-get install python-indicate will remove 'setup broadcast accounts' problem and comment#8 has the workaround which should work. Please check if that solves the problem for you.

and for the record the latest version of gwibber that solves the high cpu usage bug has been uploaded and should reach your local mirror in a couple of hours

Sorry to say but comment #8 doesn't help me personally at all. It's the same like before. Twitter doesn't work.

Well it updates everything but CTRL+R to refresh doesn't work. It only updates once and after that never again. The last twitter message is from "11 hours earlier", this seems to be impossible, since I get messages every 10 minutes. So it didn't really update anything.

Ha, sorry for spamming this bug...

But now it actually worked. gwibber works now. No idea why it works now and not before but this is definitaly fixed for me.

Many thanks Omer.

Updated to version 2.29.95. I still can't receive messages from twitter timeline. I can do something to help?

same issue with me, I can't see twitter timeline. Please tellme if I can help.

i even tried ppa build for gwibber but the issue remains for me, so the issue is not with the gwibber build.

here is the service output if you need. I deleted desktop couch, cache. I then purged and reinstalled gwibber.
Here is the service output, still getting the bug
vipul@vipul-laptop:~$ gwibber-service -o -d
Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Sat Apr 10 12:51:20 2010 **
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: ERROR <twitter:responses> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 67, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 146, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 155, in responses
    return self._get("statuses/mentions.json", count=count, since_id=since)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 136, in _get
    if data.has_key("error"):
AttributeError: 'list' object has no attribute 'has_key'

Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: DEBUG <facebook:receive> Performing operation
Gwibber Dispatcher: DEBUG <facebook:receive> Finished operation
Gwibber Dispatcher: DEBUG <facebook:responses> Performing operation
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__
    self.curl.perform()
error: (28, 'Operation timed out after 15000 milliseconds with 208000 out of 268196 bytes received')
Gwibber Dispatcher: ERROR Failed to communicate with https://twitter.com/statuses/home_timeline.json?count=200
Gwibber Dispatcher: ERROR Failed to parse the response, error was: end is out of bounds
Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 67, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 146, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 149, in receive
    return self._get("statuses/home_timeline.json", count=count, since_id=since)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 136, in _get
    if data.has_key("error"):
AttributeError: 'str' object has no attribute 'has_key'

Gwibber Dispatcher: DEBUG <facebook:images> Performing operation
Gwibber Dispatcher: DEBUG <facebook:respon...

increasing the timeout interval and cooection timeout settings in network.py but still getting the error.
The error is definitely about ca cert file but i see no file for twitter.

Every ca file is enabled in my system

Omer the workaround of deleting desktop couch does not work.

...well... it doesn't work for me either anymore...

It worked once but I repeated the procedure and it doesn't work again...

Can't use gwibber.

I'm on gwibber daily build since a few days and now it works again.

Gwibber works.

I have the same kind of problem with the daily build (2.31.1~bzr733-0ubuntu1~daily1). No tweets download, instead my messages go online correctly from gwibber.

No results from workaround suggested, so can't use gwibber.

Some useful (I hope) debug:

$ gwibber-service -o -d
Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Thu Apr 15 21:09:37 2010 **
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 81, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args) File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 146, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 149, in receive
    return self._get("statuses/home_timeline.json", count=count, since_id=since)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 136, in _get
    if data.has_key("error"):
AttributeError: 'list' object has no attribute 'has_key'

Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: INFO Loading complete: 1 - ['Failure', 'Success', 'Success']

I have the same problem, but my output is slightly more abysmal. Ends with:

Gwibber Dispatcher: INFO Loading complete: 1 - ['Failure', 'Failure', 'Failure', 'Failure', 'Failure', 'Failure', 'Failure', 'Failure']

why is tagged amd64, its not specific but generic also why not remove the workaround from the description if it does not work

https://answers.edge.launchpad.net/gwibber/+faq/973

Just to say that my problem is not with ca-certificates as suggested from above link.

All certificates are correctly installed.

My results are received:failed, responses:success, private:success but I have NO responses and NO private on my twitter account (it's brand new), just received tweets.

I am unable to get a Twitter timeline, not able to send to Twitter using Gwibber or the MeMenu and unable to add Facebook to the leftpanel list.

I have tried all the suggestions listed above to no avail.

My recieved results are failed, failed, failed

As if by pure magic, this morning when I logged onto my computer I was welcomed by a working Gwibber and memenu, together with the ability to add facebook, send and recieve messages. I don't know what you guys at Gwibber HQ did, but make a note of your steps because it looks like you fixed it...for me anyway

Hi, i have some problems with gwibber in twitter, this is my debug -> http://pastebin.com/wHwfPDta

My debug with next steps:

* Create new twitter account
* Refresh data

http://pastebin.com/zxN3je1g

maybe this issue is related to bug 522067

Gwibber was dead on my machine, nothing worked.
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/552227/comments/55 fixed it. I did *not* see that coming. Hope this works other users as well.

Worked for me as well, thanks. I now have working Twitter and Facebook where I had none previously.

@Martijn, any news about this issue? is still affecting you under latest release of gwibber? Thanks.

Gwibber doesn't work for me with Twitter and Facebook. I've just installed the full release of Lucid. I can add my Twitter account but I don't receive and "tweets". If I type my own, it appears to be sent, but doesn't appear on my web account. Another thing I find strange is that if I purposely enter the wrong password or account name, there is no warning within Gwibber to say there's a problem.

As regards Facebook, I follow all the steps in Gwibber to set up and authorize the account, but it seems to reach a dead-end at the last authorize screen. It says that my Facebook account is authorized, but if I click on the final "Add" button, nothing happens, and the account is not added to Gwibber. However, I do get an automated email from Facebook warning me that my account has been accessed by Gwibber. But still, the account does not appear in Gwibber.

As it happens, I've done two fresh installs of Lucid on my laptop, and Gwibber is still no different.

Bharath,

Your problem seems to be different than mine. It seems more like a network
communication error (thats just my prima facie assessment) which if you look
at other items in the thread is probably due to some certificates issue.
This might just fix it for you :
https://bugs.launchpad.net/gwibber/+bug/530195/comments/6

While I edited twitter.py in dist-packages/.../ microblog in your case it is
not applicable since your problem seems to be a different one.

As a suggestion from abundant caution, perspective, if you are not sure,
wait a while longer for the bug fixes. Changing code without knowing the
implications could make things worse.

Cheers,
Dhananjay

On Fri, May 14, 2010 at 11:41 AM, Bharath C J
<email address hidden>wrote:

> Mr. Dhananjay,
>
> I have taken liberty to write to you, I hope you will excuse me for this.
>
> I am unable to load twitter.... and facebook also doesn't refresh
> properly.....
>
> Error:
> 2010-05-14 09:41:39,572 - Gwibber Dispatcher - ERROR - Failed to parse the
> response, error was: No JSON object could be decoded
> 2010-05-14 09:41:39,572 - Gwibber Dispatcher - ERROR - <facebook:images>
> Operation failed
> 2010-05-14 09:41:40,360 - Gwibber Dispatcher - ERROR - Failed to
> communicate with https://twitter.com/statuses/home_timeline.json?count=200
> 2010-05-14 09:41:40,360 - Gwibber Dispatcher - ERROR - Failed to parse the
> response, error was: No JSON object could be decoded
> 2010-05-14 09:41:40,361 - Gwibber Dispatcher - ERROR - <twitter:receive>
> Operation failed
>
> I am not a not a Techie (developer), I see many twitter.py files:
>
> /usr/lib/python2.6/dist-packages/gwibber/lib/gtk/twitter.py
> /usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py
> /usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.pyc
> /usr/share/pyshared/gwibber/lib/gtk/twitter.py
> /usr/share/pyshared/gwibber/microblog/twitter.py
>
> Which file should I edit.... Kindly help me out...
>
> Bharath
> 98450 76117
>
>
> On Thu, 2010-05-13 at 22:57 +0000, Dhananjay Nene wrote:
>
> After waiting for this bug to get fixed for a loooong time, I finally
> decided the best way was to investigate it myself by modifying the code.
>
> Turns out an exception was received at line 136 of twitter.py due to
> "unsupported locale setting"
>
> Changing line 12 of util/__init__.py to ->
> locale.setlocale(locale.LC_ALL, 'en_IN') Fixed it.
>
> (Note: en_IN is my default locale, will vary across installations)
>
> Maintainers kindly note and fix the problem.
>
> YoooHooo!, gwibber works for me now.
>
>
>

--
--------------------------------------------------------
blog: http://blog.dhananjaynene.com
twitter: http://twitter.com/dnene

Thanks for your reply Mr. Dhananjay.

I guess I will wait....

Bharath
98450 76117

On Fri, 2010-05-14 at 12:41 +0530, Dhananjay Nene wrote:

> Bharath,
>
> Your problem seems to be different than mine. It seems more like a
> network communication error (thats just my prima facie assessment)
> which if you look at other items in the thread is probably due to some
> certificates issue. This might just fix it for you :
> https://bugs.launchpad.net/gwibber/+bug/530195/comments/6
>
> While I edited twitter.py in dist-packages/.../ microblog in your case
> it is not applicable since your problem seems to be a different one.
>
> As a suggestion from abundant caution, perspective, if you are not
> sure, wait a while longer for the bug fixes. Changing code without
> knowing the implications could make things worse.
>
> Cheers,
> Dhananjay
>
>
> On Fri, May 14, 2010 at 11:41 AM, Bharath C J
> <email address hidden> wrote:
>
> Mr. Dhananjay,
>
> I have taken liberty to write to you, I hope you will excuse
> me for this.
>
> I am unable to load twitter.... and facebook also doesn't
> refresh properly.....
>
> Error:
> 2010-05-14 09:41:39,572 - Gwibber Dispatcher - ERROR - Failed
> to parse the response, error was: No JSON object could be
> decoded
> 2010-05-14 09:41:39,572 - Gwibber Dispatcher - ERROR -
> <facebook:images> Operation failed
> 2010-05-14 09:41:40,360 - Gwibber Dispatcher - ERROR - Failed
> to communicate with
> https://twitter.com/statuses/home_timeline.json?count=200
> 2010-05-14 09:41:40,360 - Gwibber Dispatcher - ERROR - Failed
> to parse the response, error was: No JSON object could be
> decoded
> 2010-05-14 09:41:40,361 - Gwibber Dispatcher - ERROR -
> <twitter:receive> Operation failed
>
> I am not a not a Techie (developer), I see many twitter.py
> files:
>
> /usr/lib/python2.6/dist-packages/gwibber/lib/gtk/twitter.py
> /usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py
> /usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.pyc
> /usr/share/pyshared/gwibber/lib/gtk/twitter.py
> /usr/share/pyshared/gwibber/microblog/twitter.py
>
> Which file should I edit.... Kindly help me out...
>
> Bharath
> 98450 76117
>
>
> On Thu, 2010-05-13 at 22:57 +0000, Dhananjay Nene wrote:
>
> > After waiting for this bug to get fixed for a loooong time, I finally
> > decided the best way was to investigate it myself by modifying the code.
> >
> > Turns out an exception was received at line 136 of twitter.py due to
> > "unsupported locale setting"
> >
> > Changing line 12 of util/__init__.py to ->
> > locale.setlocale(locale.LC_ALL, 'en_IN') Fixed it.
> >
> > (Note: en_IN is my default locale, will vary across installations)
> >
> > Maintainers kindly note and fix the problem.
> >
> ...

I'm at a loss ..

After apply patch #72, clear cache and add twitter account to gwibber i see next debug:

$ gwibber-service -o -d
Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG Raising gwibber client
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Account changed: twitter-sabotatore
Gwibber Dispatcher: DEBUG ** Starting Single Operation **
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
Gwibber Dispatcher: DEBUG Checking message 10117280443 timestamp (2010-03-07 13:53:54.00) to see if it is newer than 2010-05-14 10:39:41.15
Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
Gwibber Dispatcher: DEBUG Checking message 9304922662 timestamp (2010-02-19 00:40:08.00) to see if it is newer than 2010-05-14 10:39:41.20
Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
Gwibber Dispatcher: DEBUG Checking message 2689903104 timestamp (2009-07-17 18:28:26.00) to see if it is newer than 2010-05-14 10:39:41.24
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG Checking message 2131006635 timestamp (2009-06-12 16:20:29.00) to see if it is newer than 2010-05-14 10:39:41.28
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Fri May 14 10:49:42 2010 **
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: DEBUG Gwibber Client raised
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:receive> Finished operation
Gwibber Dispatcher: INFO Loading complete: 1 - ['Success', 'Success', 'Success']
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: DEBUG <twitter:receive> Finished operation
Gwibber Dispatcher: INFO Loading complete: 2 - ['Success', 'Success', 'Success']
Gwibber Dispatcher: DEBUG Refresh interval is set to 5

But I don't see twitter messages.

Before clear cache debug was:

gwibber-service -o -d
Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Fri May 14 10:45:10 2010 **
Gwibber Dispatcher: DEBUG <twi...

Twitter started working today May 15th after latest lucid-proposed update.

In my case the ran all commands from post #68.
After i ran gwibber in terminal...
i tried to add the facebook account the error is after the first "saving..."
then i tried to add the twitter account, that was added but no tweets have been pulled, the error you cans see after the second "saving..."
then i exited gwibber.
the output is below:

** (gwibber:32192): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (gwibber:32192): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (gwibber:32192): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
No dbus monitor yet
Updating...
Updating...

** (gwibber-accounts:32267): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (gwibber-accounts:32267): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (gwibber-accounts:32267): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
Updating...
Saving...
Could not identify preference: username
Could not identify preference: session_key
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/accounts.py", line 184, in on_edit_account_save
    self.get_account_data()
  File "/usr/lib/python2.6/dist-packages/gwibber/accounts.py", line 353, in get_account_data
    aId = "%s-%s" % (self.account["protocol"], self.account["username"])
KeyError: 'username'
Saving...
Updating...
ERROR:dbus.proxies:Introspect error on com.Gwibber.Accounts:/com/gwibber/Accounts: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Accounts was not provided by any .service files
ERROR:dbus.proxies:Introspect error on com.Gwibber.Streams:/com/gwibber/Streams: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Streams was not provided by any .service files

** (gwibber:32192): CRITICAL **: murrine_style_draw_box: assertion `width >= -1' failed

I ran instructions of #9, I have Version 2.30.0.1 and lucid-proposed updates active.
I have one Facebook account set up and accepted all privacy requests. Nothing shows up on my screen.
Starting gwibber from the terminal gives me the following errors:

** (gwibber:3998): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:3998): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:3998): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
No dbus monitor yet
Updating...
Updating...
ERROR:dbus.proxies:Introspect error on com.Gwibber.Accounts:/com/gwibber/Accounts: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Accounts was not provided by any .service files
ERROR:dbus.proxies:Introspect error on com.Gwibber.Streams:/com/gwibber/Streams: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Streams was not provided by any .service files
** (gwibber:3998): CRITICAL **: murrine_style_draw_box: assertion `width >= -1' failed

Twitter works now.

I am using lucid, with lucid proposed activated, and gwibber daily ppa, and am getting the following error when starting gwibber-service -o -d . all other services work other than twitter.

Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 81, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 146, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 149, in receive
    return self._get("statuses/home_timeline.json", count=count, since_id=since)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 136, in _get
    if data.has_key("error"):
AttributeError: 'list' object has no attribute 'has_key'

Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: INFO Loading complete: 1 - ['Success', 'Success', 'Failure', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Failure', 'Success', 'Success']

Still not working..

$ gwibber-service -o -d
Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Sun May 16 14:24:30 2010 **
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 75, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 146, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 149, in receive
    return self._get("statuses/home_timeline.json", count=count, since_id=since)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 136, in _get
    if data.has_key("error"):
AttributeError: 'list' object has no attribute 'has_key'

Gwibber Dispatcher: INFO Loading complete: 1 - ['Failure', 'Success', 'Success']
Gwibber Dispatcher: DEBUG Raising gwibber client
Gwibber Dispatcher: DEBUG Gwibber Client raised

Changin to OpenDNS (#81) did the trick for me. It also solved my issue not being able to add my Facebook account...

I think everyone has varying degrees of this same problem. I've used OpenDNS from the beginning and could add/post all my accounts, it's just that my specific problem is the viewing of my twitter stream, which, I cannot do at all other then the posts I make. Should we start splitting up the bugs based on our particular problems? This bug seems like a junk drawer at the moment for code and issues loosely related to services that don't work.

Ok,this is weird, twitter in gwibber gave me the error i previously posted,and then i tried it 5 hours later, and it seemed to work, no changes at all. my machine had been running the whole time, no reboot, no updates.

comment#8 and 10 on bug 571858 seems to have solved the problem for someone. (workaround)

This problem was completely solved for me by this post:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/552227
Look at #70.

This explains why people were getting relief by switching to openDNS or by just waiting until later. The timeouts for the Gwibber services are so small, that the slight speed edge you get with a better dns lookup makes it work. By the way, this fix also solved another problem I had where I couldn't add my Facebook account.

Could someone from the Gwibber team please propose Joe Ray's patch in #72 for inclusion in the code, if it hasn't been applied yet?
Thanks.

Solution in #96 does not work for me.
Currently getting 1 day old tweets, even after changing timeouts in network.py (web interface working fine).

Running Lucid with lucid-updates.

ORIGIN OF THE PROBLEM: NXDOMAIN DNS Server

My ISP is using this new feature called NXDOMAIN redirecting.
With this feature the browser displays an isp search page for None existing domains.

for example:
http://www.asfsdfaasdf.com/

how it works: if you request an none existing domain the dns server sends you the ip of an "search server" of the isp.

it seems gwibber or one of the python libs has a problem if the DNS server does not correclty answer queries.
I changed my dns server to one that correctly reply with NXDOMAIN and now EVERYTHING is WORKING

you may also try http://code.google.com/speed/public-dns/ or as mentioned opendns.

hope this information helps the developer to fix the problem.

Not yet there, aatdark. I have proper DNSs here (the kind that giver proper responses to non-existent domains and I still have a problem. Facebook, Twitter, Identi.ca accounts are quiet. Flickr works.

I use 2 ISP at home :
- Orange for my job, with an Ethernet connection ;
- Free for home, with a WIFI connection.
Gwibber 2.30.0.1 on my netbook (Ubuntu 10.04 UNE) works fine with each of these connections.
But it doesn't work if both of these connections are active at the same time !
On my desktop, Gwibber 2.0.0 with Ubuntu 9.10 works fine even with both connections active.

So, it's not a big issue for me and I hope that this comment will help to solve the problem for other people...

The solution in comment #80 solved the problem! Thanks for that great debugging work, Dhananjay.

Dhananjay solution in comment 80 worked for me too.....finally

Following my comment #101, I've discovered that for me the issue is related to IPv6 and a bug in the "Livebox" (network equipment for ADSL of Orange, french ISP). By using now static address for eth0, Gwibber works fine, event if I'm connected at the same time on two different networks.

I would like to try solution #80.
But I don't know how to edit /usr/share/pyshared/gwibber/microblog/__init__.py
Here is an empty file (on gedit).
Please help.

could anyone in this bug report with enough python knowledge try to fix this bug.?

there are too many people infected. there are many duplicate bugs with the same syptoms out there.

since this bug was reported the title was different and did not reflect the exact error. so many people subscribed to this bug report might not be actually facing the same issue so a workaround to increase the timeout might work for some.

$ gksudo gedit /usr/share/pyshared/gwibber/microblog/network.py

and edit

self.curl.setopt(pycurl.TIMEOUT, 15)
    self.curl.setopt(pycurl.CONNECTTIMEOUT, 8)

           to

self.curl.setopt(pycurl.TIMEOUT, 50)
    self.curl.setopt(pycurl.CONNECTTIMEOUT, 25)

Your might even want to try a higher timeout in some cases.

anyone facing this issue. please update gwibber to 2.30.1 from lucid-proposed repository. it solves lots of problems. maybe a timeout issue could solve this problem too. please check

did anyone try the proposed version?

WFM - works for me (2.30.1 from lucid-proposed on 10.04 amd64)

Thanks for the confirmation Karsten.

gwibber 2.30.1 is now in Lucid updates.

I still have errors:

$ gwibber-service -d -o
Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG Raising gwibber client
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Account changed: twitter-sabotatore
Gwibber Dispatcher: DEBUG ** Starting Single Operation **
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Thu Jul 15 09:19:24 2010 **
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
Gwibber Dispatcher: DEBUG Checking message 18019169712 timestamp (2010-07-08 11:02:02.00) to see if it is newer than 2010-07-15 09:09:25.24
Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
Gwibber Dispatcher: DEBUG Checking message 17941268076 timestamp (2010-07-07 14:18:40.00) to see if it is newer than 2010-07-15 09:09:25.28
Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
Gwibber Dispatcher: DEBUG Checking message 17940849118 timestamp (2010-07-07 14:09:26.00) to see if it is newer than 2010-07-15 09:09:25.33
Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
Gwibber Dispatcher: DEBUG Checking message 16676099166 timestamp (2010-06-21 10:07:42.00) to see if it is newer than 2010-07-15 09:09:25.37
Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
Gwibber Dispatcher: DEBUG Checking message 14856168773 timestamp (2010-05-27 23:02:26.00) to see if it is newer than 2010-07-15 09:09:25.42
Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
Gwibber Dispatcher: DEBUG Checking message 10117280443 timestamp (2010-03-07 13:53:54.00) to see if it is newer than 2010-07-15 09:09:25.47
Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
Gwibber Dispatcher: DEBUG Checking message 9304922662 timestamp (2010-02-19 00:40:08.00) to see if it is newer than 2010-07-15 09:09:25.51
Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
Gwibber Dispatcher: DEBUG Checking message 2689903104 timestamp (2009-07-17 18:28:26.00) to see if it is newer than 2010-07-15 09:09:25.56
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG Checking message 2131006635 timestamp (2009-06-12 16:20:29.00) to see if it is newer than 2010-07-15 09:09:25.61
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG Gwibber Client raised
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: DEBUG <twitter:responses> Finished ope...

these logs look more similar to bug 605543

On Thu, Jul 15, 2010 at 11:21 AM, Vitali Kulikou
<email address hidden>wrote:

> I still have errors:
>
> $ gwibber-service -d -o
> Updating...
> Gwibber Dispatcher: DEBUG Setting up monitors
> Gwibber Dispatcher: DEBUG Monitors are up
> Gwibber Dispatcher: INFO Gwibber Service is reloading account
> credentials
> Gwibber Dispatcher: DEBUG Refresh interval is set to 5
> Gwibber Dispatcher: DEBUG Raising gwibber client
> Gwibber Dispatcher: INFO Gwibber Service is reloading account
> credentials
> Gwibber Dispatcher: DEBUG Account changed: twitter-sabotatore
> Gwibber Dispatcher: DEBUG ** Starting Single Operation **
> Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
> Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
> Gwibber Dispatcher: INFO Gwibber Service is reloading account
> credentials
> Gwibber Dispatcher: DEBUG Refresh interval is set to 5
> Gwibber Dispatcher: DEBUG ** Starting Refresh - Thu Jul 15 09:19:24 2010
> **
> Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
> Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
> Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
> Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
> Gwibber Dispatcher: DEBUG Checking message 18019169712 timestamp
> (2010-07-08 11:02:02.00) to see if it is newer than 2010-07-15 09:09:25.24
> Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
> Gwibber Dispatcher: DEBUG Checking message 17941268076 timestamp
> (2010-07-07 14:18:40.00) to see if it is newer than 2010-07-15 09:09:25.28
> Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
> Gwibber Dispatcher: DEBUG Checking message 17940849118 timestamp
> (2010-07-07 14:09:26.00) to see if it is newer than 2010-07-15 09:09:25.33
> Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
> Gwibber Dispatcher: DEBUG Checking message 16676099166 timestamp
> (2010-06-21 10:07:42.00) to see if it is newer than 2010-07-15 09:09:25.37
> Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
> Gwibber Dispatcher: DEBUG Checking message 14856168773 timestamp
> (2010-05-27 23:02:26.00) to see if it is newer than 2010-07-15 09:09:25.42
> Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
> Gwibber Dispatcher: DEBUG Checking message 10117280443 timestamp
> (2010-03-07 13:53:54.00) to see if it is newer than 2010-07-15 09:09:25.47
> Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
> Gwibber Dispatcher: DEBUG Checking message 9304922662 timestamp
> (2010-02-19 00:40:08.00) to see if it is newer than 2010-07-15 09:09:25.51
> Gwibber Dispatcher: DEBUG <twitter:responses> Adding record
> Gwibber Dispatcher: DEBUG Checking message 2689903104 timestamp
> (2009-07-17 18:28:26.00) to see if it is newer than 2010-07-15 09:09:25.56
> Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
> Gwibber Dispatcher: DEBUG Checking message 2131006635 timestamp
> (2009-06-12 16:20:29.00) to see if it is newer than 2010-07-15 09:09:25.61
> Gwibber Dispatc...

Yes, thanks..

I'm still having the issue. Gwibber doesn't update twitts

I just noticed this happening to me and have been looking into it.
I went to my Twitter settings page and saw that under the "Connections" tab where I expected to see a "Gwibber" app as one that I've "OK'd" Twitter to allow connections to, wasn't there.

I remember having to do that when I first started using Gwibber. Where did it go? Could this be related to this problem? Where could I find the instructions to add Gwibber back into my Twitter "acceptable connections/apps"?

Reporting the same as @dooohhead / #118. Gwibber does not show up in my "Connections" tab in the Twitter interface. Still seeing this bug with 2.30.1.

For the last 24hrs Gwibber doesn't update my twitter stream. Have restarted Ubuntu a couple of times in this period:

I get the following error when running it from the shell:

alord@lobsang:~$ gwibber
** (gwibber:2642): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:2642): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:2642): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
Updating...
Updating...
/usr/bin/gwibber:68: GtkWarning: gtk_container_add: assertion `GTK_IS_CONTAINER (container)' failed
  gtk.main()

Gwibber loads but does not update.

HTH

same problem here

Found this today:

http://digitizor.com/2010/09/01/update-gwibber-to-continue-using-twitter-ubuntu/

<http://digitizor.com/2010/09/01/update-gwibber-to-continue-using-twitter-ubuntu/>I
implemented the update but haven't had much of a chance to see if it
actually fixes this problem but it did force me to re-register/authorize
Gwibber with my Twitter account so now it does show up in my connections
settings page (in Twitter).

--
*DooohHead*