gwibber tries to call has_key on list---doesn't update streams
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gwibber |
Fix Released
|
Undecided
|
Unassigned | ||
gwibber (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: gwibber
I've just installed Ubuntu 10.04, and I've set up my Twitter and Facebook accounts in the "Microblog settings" screen. I can now post to Facebook fine (I also get loads of facebook updates in my Gwibber main window), but I can't seem to get anything to/from Twitter.
No tweets from other people, my new tweets don't get to the website, etc.
My password is correct (checked it a LOT of times).
How do I go about debugging this?
ProblemType: Bug
Architecture: amd64
Date: Mon Mar 1 18:52:33 2010
DistroRelease: Ubuntu 10.04
Package: gwibber 2.29.90.1-0ubuntu2
PackageArchitec
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=nl_NL.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: gwibber
Uname: Linux 2.6.32-14-generic x86_64
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Martijn vdS (martijn) wrote : | #1 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
malev (marcosvanetta) wrote : | #2 |
Changed in gwibber (Ubuntu): | |
status: | New → Incomplete |
Changed in gwibber (Ubuntu): | |
importance: | Undecided → Low |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Martijn vdS (martijn) wrote : | #3 |
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@
** (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 'WnckWindowMove
No dbus monitor yet
Updating...
ERROR:dbus.
Updating...
ERROR:dbus.
ERROR:dbus.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Haggai Eran (haggai-eran) wrote : | #4 |
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Victor Vargas (kamus) wrote : | #5 |
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!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Martijn vdS (martijn) wrote : | #6 |
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!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vipul (vipul-bhandari) wrote : | #7 |
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 'WnckWindowMove
No dbus monitor yet
Updating...
Updating...
ERROR:dbus.
ERROR:dbus.
/usr/bin/
gtk.main()
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : | #8 |
For those who still face this please Quit gwibber and delete ~/.cache/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitali Kulikou (sabotatore) wrote : | #9 |
$ sudo aptitude purge gwibber gwibber-service
$ cd
$ rm -rf .cache/
$ rm -rf .config/
$ rm -rf .local/
$ sudo aptitude install gwibber gwibber-service
Add twitter account. Not received messages. Received only replies.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitali Kulikou (sabotatore) wrote : | #10 |
And gwibber-service load processor 100%
$ gwibber-service -o -d
Gtk-Message: Failed to load module "pk-gtk-module": libpk-gtk-
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/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if data.has_
AttributeError: 'list' object has no attribute 'has_key'
Gwibber Dispatcher: INFO Loading complete: 1 - ['Failure', 'Success', 'Success']
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : Re: [Bug 530195] Re: Twitter doesn't work at all | #11 |
Vitali, high cpu usage would be bug 554005
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Christopher "cv" (vchristopher) wrote : Re: Twitter doesn't work at all | #12 |
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.
Changed in gwibber (Ubuntu): | |
status: | Incomplete → Confirmed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : | #13 |
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : | #14 |
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
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Christopher "cv" (vchristopher) wrote : | #15 |
Sorry to say but comment #8 doesn't help me personally at all. It's the same like before. Twitter doesn't work.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Christopher "cv" (vchristopher) wrote : | #16 |
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Christopher "cv" (vchristopher) wrote : | #17 |
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitali Kulikou (sabotatore) wrote : | #18 |
Updated to version 2.29.95. I still can't receive messages from twitter timeline. I can do something to help?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vipul (vipul-bhandari) wrote : | #19 |
same issue with me, I can't see twitter timeline. Please tellme if I can help.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vipul (vipul-bhandari) wrote : | #20 |
i even tried ppa build for gwibber but the issue remains for me, so the issue is not with the gwibber build.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vipul (vipul-bhandari) wrote : | #21 |
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-
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/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if data.has_
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:
Traceback (most recent call last):
File "/usr/lib/
self.
error: (28, 'Operation timed out after 15000 milliseconds with 208000 out of 268196 bytes received')
Gwibber Dispatcher: ERROR Failed to communicate with https:/
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/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if data.has_
AttributeError: 'str' object has no attribute 'has_key'
Gwibber Dispatcher: DEBUG <facebook:images> Performing operation
Gwibber Dispatcher: DEBUG <facebook:respon...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vipul (vipul-bhandari) wrote : | #22 |
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vipul (vipul-bhandari) wrote : | #23 |
Every ca file is enabled in my system
description: | updated |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vipul (vipul-bhandari) wrote : | #24 |
Omer the workaround of deleting desktop couch does not work.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Christopher "cv" (vchristopher) wrote : | #25 |
...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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Christopher "cv" (vchristopher) wrote : | #26 |
I'm on gwibber daily build since a few days and now it works again.
Gwibber works.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Maurizio Daniele (hayabusa) wrote : | #27 |
I have the same kind of problem with the daily build (2.31.1~
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/
message_data = PROTOCOLS[
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if data.has_
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']
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ketil Wendelbo Aanensen (ketilwaa-deactivatedaccount) wrote : | #28 |
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']
Changed in gwibber (Ubuntu): | |
importance: | Low → Medium |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vipul (vipul-bhandari) wrote : | #29 |
why is tagged amd64, its not specific but generic also why not remove the workaround from the description if it does not work
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : | #30 |
description: | updated |
tags: | removed: amd64 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Maurizio Daniele (hayabusa) wrote : | #31 |
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Arthur Moore (arthur-moore85) wrote : | #32 |
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
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Arthur Moore (arthur-moore85) wrote : | #33 |
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
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
hoppus2a (hoppus2a) wrote : | #34 |
Hi, i have some problems with gwibber in twitter, this is my debug -> http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitali Kulikou (sabotatore) wrote : | #35 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Victor Vargas (kamus) wrote : | #36 |
maybe this issue is related to bug 522067
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ketil Wendelbo Aanensen (ketilwaa-deactivatedaccount) wrote : | #37 |
Gwibber was dead on my machine, nothing worked.
https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bo Rosén (bo-rosen) wrote : | #38 |
Worked for me as well, thanks. I now have working Twitter and Facebook where I had none previously.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Victor Vargas (kamus) wrote : | #39 |
@Martijn, any news about this issue? is still affecting you under latest release of gwibber? Thanks.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Neil Padgett (neil452) wrote : | #40 |
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ketil Wendelbo Aanensen (ketilwaa-deactivatedaccount) wrote : | #41 |
@bloodorangeonline: Have you tried the possible workaround in comment #37?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Aditya (adityapatadia) wrote : | #42 |
I am getting following output in gwibber.log file
2010-05-01 00:21:49,925 - Gwibber Accounts - INFO - Running from the system path
2010-05-01 00:21:52,975 - Gwibber Service - INFO - Running from the system path
2010-05-01 00:21:54,265 - Gwibber Service - INFO - Running from the system path
2010-05-01 00:21:55,322 - Gwibber Dispatcher - INFO - Gwibber Service is reloading account credentials
2010-05-01 00:22:16,548 - Gwibber Dispatcher - INFO - Gwibber Service is reloading account credentials
2010-05-01 00:22:19,419 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-05-01 00:22:24,658 - Gwibber GNOME Client - INFO - Running from the system path
2010-05-01 00:22:24,792 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-05-01 00:22:24,793 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-05-01 00:22:24,793 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-05-01 00:22:27,482 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-05-01 00:22:27,482 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-05-01 00:22:27,483 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2010-05-01 00:22:27,483 - Gwibber Dispatcher - INFO - Loading complete: 1 - ['Failure', 'Failure', 'Failure']
2010-05-01 00:22:33,776 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-05-01 00:22:34,043 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-05-01 00:22:42,170 - Gwibber Dispatcher - INFO - Loading complete: 2 - ['Failure', 'Failure', 'Success']
Hope this will help...
I am also getting the output in terminal which is same as in comment #3
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Aditya (adityapatadia) wrote : | #43 |
The idea of comment #37 is not working at all.
summary: |
- Twitter doesn't work at all + Twitter doesn't work at all in Gwibber |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Neil Padgett (neil452) wrote : Re: Twitter doesn't work at all in Gwibber | #44 |
Ketil Wendelbo Aanensen: I haven't tried the workaround in comment #37 as such because I'm actually already using OpenDNS.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Neil Padgett (neil452) wrote : | #45 |
I must apologize for blaming Gwibber/Ubuntu for my problem. I'm almost 100% sure that my problem is caused by my router and not a bug in Gwibber.
I connect to the internet via a D-Link 655 router, which is connected to my Virgin Media cable modem. It occurred to me to try connecting my laptop directly to the cable modem, bypassing the router. After doing this, Gwibber works perfectly! I can send/receive "tweets", and I can now set up Facebook easily, which also works fine.
Now my problem is that I when I reconnect the modem to the router, Gwibber doesn't work again. So, this must be a firewall setting or something in the router that needs changing. However, I don't know what to change safely without leaving myself exposed...
I've been using OpenDNS, and wondered if that was blocking Gwibber, but that isn't the case because if I change back to Virgin Media's DNS servers it makes no difference.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Matthew Pirocchi (matthew-pirocchi) wrote : | #46 |
Just wanted to confirm that the OpenDNS workaround worked for me.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ketil Wendelbo Aanensen (ketilwaa-deactivatedaccount) wrote : | #47 |
@bloodorangeonline Funny, I'm using the exact same router, and I had the same problem, but it went away after I added OpenDNS. However, this hasn't given me any problems with other applications.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Neil Padgett (neil452) wrote : | #48 |
Ketil Wendelbo Aanensen: Apology number 2! Sorry, Ketil, I should've listened to you the first time!! I just added the OpenDNS addresses to Ubuntu, and Gwibber now seems to be working again, even with the router connected.
I assumed that, because I'd got the OpenDNS addresses in my router, I didn't need to add them to Ubuntu. Wrong again!
I've left the router set to point to OpenDNS for the other computers attached to it. I can't quite understand how things are working now, though. I wonder how come it wasn't enough just to have the OpenDNS addresses on the router?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : | #49 |
Removing the desktopcouch configuration files could solve the problem for a few people (not all).
~/.local/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jorge G (geojorg) wrote : | #50 |
I just use google dns like the suggestion in comment #37 and it is now working.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitali Kulikou (sabotatore) wrote : | #51 |
Hm.. Don't work with any variant: add open dns to router, aad open dns to nm..
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitali Kulikou (sabotatore) wrote : | #52 |
And It doesn't work either at home, at work, at gprs internet..
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Lienex (regenmacher2k) wrote : | #53 |
Solving the problem by using Google DNS gave me the idea of just adding the address of api.facebook.com to /etc/hosts and voilà: it works!
So I guess the problem is a kind of too short DNS query timeout in network.py or curl (because it threw "name lookup timed out" in network.py) since resolving and connecting to api.facebook.com works through my router's DNS, but maybe just not fast enough.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Aditya (adityapatadia) wrote : | #54 |
I've uninstalled gwibber, deleted all the files related to it as well as couchdb. Then i reinstalled it. I am getting following error in terminal:
** (gwibber:1582): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:1582): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:1582): WARNING **: Trying to register gtype 'WnckWindowMove
Traceback (most recent call last):
File "/usr/bin/gwibber", line 67, in <module>
client.Client()
File "/usr/lib/
self.w = GwibberClient()
File "/usr/lib/
self.model = gwui.Model()
File "/usr/lib/
self.settings = util.SettingsMo
File "/usr/lib/
DEFAULT_
File "/usr/lib/
self.database = CouchDatabase(
File "/usr/lib/
port = desktopcouch.
File "/usr/lib/
return _direct_
File "/usr/lib/
raise RuntimeError(
RuntimeError: Unable to find listening port
Please give this bug higher priority and fix it as early as possible. This is forcing users to not to use gwibber.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitali Kulikou (sabotatore) wrote : | #55 |
I agree, this is a high priority bug, I'm isn't possible use gwibber for follow twitter friends.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ed S (edgar-b-dsouza) wrote : | #56 |
@Aditya: did you logout and log in again (or better, restart the system) after reinstalling couchdb and gwibber? If not, please try that.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Sylvestra (blackcatw) wrote : | #57 |
I hope this will be filed high soon. My terminal output is almost the same:
** (gwibber:7880): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:7880): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:7880): WARNING **: Trying to register gtype 'WnckWindowMove
Traceback (most recent call last):
File "/usr/bin/gwibber", line 67, in <module>
client.Client()
File "/usr/lib/
self.w = GwibberClient()
File "/usr/lib/
self.model = gwui.Model()
File "/usr/lib/
self.settings = util.SettingsMo
File "/usr/lib/
DEFAULT_
File "/usr/lib/
self.database = CouchDatabase(
File "/usr/lib/
server_
File "/usr/lib/
self.
File "/usr/lib/
if self._database_name not in self._server:
File "/usr/lib/
self.
File "/usr/lib/
return self._request(
File "/usr/lib/
resp, data = _make_request()
File "/usr/lib/
body=body, headers=headers)
File "/usr/lib/
(response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
File "/usr/lib/
(response, content) = self._conn_
File "/usr/lib/
raise ServerNotFoundE
httplib2.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joe Ray (joeray123) wrote : | #58 |
I'm also having a problem using Gwibber with Twitter on amd64. Have tried using OpenDNS directly (it's already enabled on our router), have tried deleting the cache files, neither solution worked. The output when running Gwibber from the terminal:
** (gwibber:3024): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:3024): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:3024): WARNING **: Trying to register gtype 'WnckWindowMove
No dbus monitor yet
Updating...
Updating...
ERROR:dbus.
ERROR:dbus.
/usr/bin/
gtk.main()
And the log:
2010-05-05 07:02:56,800 - Gwibber Dispatcher - DEBUG - ** Starting Refresh - Wed May 5 07:02:56 2010 **
2010-05-05 07:02:56,992 - Gwibber Dispatcher - DEBUG - <facebook:
2010-05-05 07:02:57,000 - Gwibber Dispatcher - DEBUG - <facebook:receive> Performing operation
2010-05-05 07:03:03,071 - Gwibber Dispatcher - DEBUG - <facebook:receive> Finished operation
2010-05-05 07:03:03,161 - Gwibber Dispatcher - DEBUG - <facebook:images> Performing operation
2010-05-05 07:03:05,461 - Gwibber Dispatcher - ERROR - <facebook:
2010-05-05 07:03:05,463 - Gwibber Dispatcher - DEBUG - Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return [self._
File "/usr/lib/
user = profiles[
KeyError: 61111372
2010-05-05 07:03:05,559 - Gwibber Dispatcher - DEBUG - <twitter:receive> Performing operation
2010-05-05 07:03:06,829 - Gwibber Dispatcher - DEBUG - <twitter:receive> Finished operation
2010-05-05 07:03:06,950 - Gwibber Dispatcher - DEBUG - <twitter:responses> Performing operation
2010-05-05 07:03:08,239 - Gwibber Dispatcher - DEBUG - <twitter:responses> Finished operation
2010-05-05 07:03:08,361 - Gwibber Dispatcher - DEBUG - <twitter:private> Performing operation
2010-05-05 07:03:09,610 - Gwibber Dispatcher - DEBUG - <twitter:private> Finished operation
2010-05-05 07:03:09,700 - Gwibber Dispatcher - DEBUG - <twitter:search> Performing oper...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Benoit St-André (benoit-st-andre) wrote : | #59 |
I experience the same behavior using gwibber-daily on Karmic and normal gwibber on Lucid i386.
I get Twitter responses, twitter search, but I can't get twitter receive.
Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if data.has_
AttributeError: 'list' object has no attribute 'has_key'
It has been like this since around 15 days. I tried changing my DNS to OpenDNS without any success. My ca-certificates are up-to-date. What is going on ?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vipul (vipul-bhandari) wrote : | #60 |
openDns may have worked for ppl for whom nothing worked in twitter, but my facebook worked but twitter did not. Nothing quoted here fixed it. So, i even tried changing some connection paramters in python file but this is not fixed.
Anyway stopped using gwibber and installed Seesmic desktop.....and it is way better.(no relation to bug)......i replied so that bug gets fixed coz these kind of minor issues push ppl away from linux....and i love ubuntu.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
danielsk (dskerr) wrote : Re: [Bug 530195] Re: Twitter doesn't work at all in Gwibber | #61 |
Gwibber 2.31.1
Lucid AMD64
This is what is working:
Facebook updates normally.
Twitter: I receive replys adressed to me and messages I send. Also if
I search for someone all their twits appear.ibber
Not working: I don't receive any other update from twitter.
Since Gwibber can get the twits if I specifically search, it might not
be an problem in updating. It seems more as if Gwibber is only showing
the messages to and from me.
I removed the .cache dir, completely removed and re-installed Gwibber,
but still no improvement. Also tried the DNS thing but also nothing.
If there is any test I can run to help I'll do. When it works I think
Gwibber is the best software to update social networks.
Thanks
Daniel
On Wed, May 5, 2010 at 5:58 PM, Vipul <email address hidden> wrote:
> openDns may have worked for ppl for whom nothing worked in twitter, but
> my facebook worked but twitter did not. Nothing quoted here fixed it.
> So, i even tried changing some connection paramters in python file but
> this is not fixed.
>
> Anyway stopped using gwibber and installed Seesmic desktop.....and it is
> way better.(no relation to bug)......i replied so that bug gets fixed
> coz these kind of minor issues push ppl away from linux....and i love
> ubuntu.
>
> --
> Twitter doesn't work at all in Gwibber
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Gwibber: New
> Status in “gwibber” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: gwibber
>
> I've just installed Ubuntu 10.04, and I've set up my Twitter and Facebook accounts in the "Microblog settings" screen. I can now post to Facebook fine (I also get loads of facebook updates in my Gwibber main window), but I can't seem to get anything to/from Twitter.
>
> No tweets from other people, my new tweets don't get to the website, etc.
>
> My password is correct (checked it a LOT of times).
>
> How do I go about debugging this?
>
> ProblemType: Bug
> Architecture: amd64
> Date: Mon Mar 1 18:52:33 2010
> DistroRelease: Ubuntu 10.04
> Package: gwibber 2.29.90.1-0ubuntu2
> PackageArchitec
> ProcEnviron:
> LANGUAGE=
> PATH=(custom, user)
> LANG=nl_NL.UTF-8
> SHELL=/bin/bash
> ProcVersionSign
> SourcePackage: gwibber
> Uname: Linux 2.6.32-14-generic x86_64
>
>
>
> To unsubscribe from this bug, go to:
> https:/
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joao Verissimo (joniv) wrote : Re: Twitter doesn't work at all in Gwibber | #62 |
Same issue with twitter (only replies and sent, but no messages), and same console messages.
Fresh installation of 10.04 final.
Did not work for a whole day on 3 different networks.
Started "magically" working a few hours later.
No fixes required.
Whatever the cause, it can be sorted without doing any of the stuff above.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
danielsk (dskerr) wrote : Re: [Bug 530195] Re: Twitter doesn't work at all in Gwibber | #63 |
I don't know if this was the suggestion above, the problem seems solved now.
I removed .cache/
Closed gwibber.
Opened it again.
Added the twitter account again (removing and adding didn't worked, I
added as if it was another account, it wasn't added again to the list,
but now twitter seems to be working)
Thanks a lot
On Thu, May 6, 2010 at 7:40 PM, Joao Verissimo <email address hidden> wrote:
> Same issue with twitter (only replies and sent, but no messages), and same console messages.
> Fresh installation of 10.04 final.
>
> Did not work for a whole day on 3 different networks.
> Started "magically" working a few hours later.
>
> No fixes required.
> Whatever the cause, it can be sorted without doing any of the stuff above.
>
> --
> Twitter doesn't work at all in Gwibber
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Gwibber: New
> Status in “gwibber” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: gwibber
>
> I've just installed Ubuntu 10.04, and I've set up my Twitter and Facebook accounts in the "Microblog settings" screen. I can now post to Facebook fine (I also get loads of facebook updates in my Gwibber main window), but I can't seem to get anything to/from Twitter.
>
> No tweets from other people, my new tweets don't get to the website, etc.
>
> My password is correct (checked it a LOT of times).
>
> How do I go about debugging this?
>
> ProblemType: Bug
> Architecture: amd64
> Date: Mon Mar 1 18:52:33 2010
> DistroRelease: Ubuntu 10.04
> Package: gwibber 2.29.90.1-0ubuntu2
> PackageArchitec
> ProcEnviron:
> LANGUAGE=
> PATH=(custom, user)
> LANG=nl_NL.UTF-8
> SHELL=/bin/bash
> ProcVersionSign
> SourcePackage: gwibber
> Uname: Linux 2.6.32-14-generic x86_64
>
>
>
> To unsubscribe from this bug, go to:
> https:/
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitali Kulikou (sabotatore) wrote : Re: Twitter doesn't work at all in Gwibber | #64 |
* Stop gwibber
* $ rm -rf .cache/ .config/
* $ mkdir .cache
* Run gwibber
* Create twitter account..
It didn't work, and not working now.. I receive only messages i send & reply to me.. :/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Captain Chaos (launchpad-chaos) wrote : | #65 |
I also tried deleting the Couch DB cache. For me it helped once: gwibber retrieved my twitter messages once after doing that, but then stopped working again.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Aditya (adityapatadia) wrote : | #66 |
The bug is not solved yet... Nothing is working.... Please give this bug high priority and assign to a responsible person..... Does anyone read this bug????
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jean Baptiste FAVRE (ubuntu-bugs-jbfavre) wrote : | #67 |
Also affected by this bug. Running gwibber-service -o -d gives:
Gwibber Dispatcher: DEBUG ** Starting Refresh - Sat May 8 11:46:11 2010 **
Gwibber Dispatcher: DEBUG <identica:private> Performing operation
Gwibber Dispatcher: DEBUG <identica:receive> Performing operation
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <identica:
Gwibber Dispatcher: DEBUG <identica:
Gwibber Dispatcher: DEBUG <identica:receive> Finished operation
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <identica:private> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if data.has_
AttributeError: 'list' object has no attribute 'has_key'
So, Identi.ca account works well but not Twitter's one.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniel Williams (spitfire23bc) wrote : | #68 |
Affects me too. Gwibber-service implies that there are no problems, but I don't get any updates, nor do any of my updates make it through. Using the Search *does* work.
I've tested Gwibber with Flickr and that updates fine.
I've done:
sudo aptitude purge gwibber gwibber-service dektop-couch
sudo aptitude install gwibber gwibber-service desktop-couch
rm -rf ~/.cache/gwibber/ ~/.cache/
gwibber-service -o -d
OUTPUT:
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 Account changed: _design/
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG Stream changed: _design/
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Account changed: twitter-
Gwibber Dispatcher: DEBUG ** Starting Single Operation **
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:receive> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: INFO Loading complete: 1 - ['Success', 'Success', 'Success']
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Sat May 8 21:28:28 2010 **
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <twitter:receive> Finished 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: 2 - ['Success', 'Success', 'Success']
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joe Ray (joeray123) wrote : | #69 |
- Patch to show Twitter authentication errors (though probably needs work) Edit (1.9 KiB, text/plain)
I found out what my problem was - I had entered the wrong password and because Gwibber had tried so much, Twitter locked the account for a certain amount of time. This probably meant that when I typed in different passwords to try them it further compounded the problem, and Gwibber gave no indication of an authentication error.
I found the problem in the Gwibber code, and have a patch attached, though it doesn't really fix the problem properly - it only works for really specific errors. Also, it doesn't differentiate between being denied because of a wrong password and being denied because the account is locked, although it does now show this in the log.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
fenrasa (fenrasa) wrote : | #70 |
Fresh install:
$ gwibber
** (gwibber:5027): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:5027): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:5027): WARNING **: Trying to register gtype 'WnckWindowMove
Removing stale, deceptive pid file.
Apache CouchDB has started, time to relax.
WARNING:root:Pid file does not contain int: '\n\n'
WARNING:root:Pid file does not contain int: '\n\n'
Browse your desktop CouchDB at file://
No dbus monitor yet
Updating...
Updating...
** (gwibber-
** (gwibber-
** (gwibber-
Here the Accountmanager shows:
Updating...
I created TwitterAccount:
Saving...
Gwibber updates TwitterTimeline:
Updating...
ERROR:dbus.
ERROR:dbus.
Twitter Update does not work. Correct password used.
Publishing on Twitter works. Yet this here happens:
/usr/bin/
gtk.main()
Going to try Joe Rays patch later today. If I grasp what he's done there.. :)
Greetings,
tags: | added: patch |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Nigel Babu (nigelbabu) wrote : | #71 |
Thank you for your work on this patch. While this is indeed great work, it would be much more nicer, if it would detect the specific errors too! I'm tagging this patch-needswork for now, please feel free to change to 'patch' tag when you have a new patch ready for review.
tags: |
added: patch-needswork removed: patch |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joe Ray (joeray123) wrote : | #72 |
- gwibber-twitter-updated.patch Edit (2.6 KiB, text/plain)
Adding patch to handle the difference between an authentication error and having been locked out.
tags: |
added: patch removed: patch-needswork |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Rene Vallecillo (reneval) wrote : | #73 |
I confirm that changing my dns fixed my problem with twitter. Same as #37
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
danielsk (dskerr) wrote : Re: [Bug 530195] Re: Twitter doesn't work at all in Gwibber | #74 |
Hi, I really dont have idea what the problem is anymore. It might be
some kind of connection problem, but from the same location it works
only sporadically.
Gwibber back again to getting only updates from myself or to myself.
On Tue, May 11, 2010 at 4:03 PM, Rene Vallecillo <email address hidden> wrote:
> I confirm that changing my dns fixed my problem with twitter. Same as
> #37
>
> --
> Twitter doesn't work at all in Gwibber
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Gwibber: New
> Status in “gwibber” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: gwibber
>
> I've just installed Ubuntu 10.04, and I've set up my Twitter and Facebook accounts in the "Microblog settings" screen. I can now post to Facebook fine (I also get loads of facebook updates in my Gwibber main window), but I can't seem to get anything to/from Twitter.
>
> No tweets from other people, my new tweets don't get to the website, etc.
>
> My password is correct (checked it a LOT of times).
>
> How do I go about debugging this?
>
> ProblemType: Bug
> Architecture: amd64
> Date: Mon Mar 1 18:52:33 2010
> DistroRelease: Ubuntu 10.04
> Package: gwibber 2.29.90.1-0ubuntu2
> PackageArchitec
> ProcEnviron:
> LANGUAGE=
> PATH=(custom, user)
> LANG=nl_NL.UTF-8
> SHELL=/bin/bash
> ProcVersionSign
> SourcePackage: gwibber
> Uname: Linux 2.6.32-14-generic x86_64
>
>
>
> To unsubscribe from this bug, go to:
> https:/
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Captain Chaos (launchpad-chaos) wrote : Re: Twitter doesn't work at all in Gwibber | #75 |
Yesterday Twitter suddenly started to work in Gwibber. Receiving all messages as normal. No updates had been installed since the last time I tried. This is the first time it has worked since upgrading to Lucid. I'll report back if it stops working again.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
baxter42 (baxter42) wrote : | #76 |
i had exactly the same output as #3 -- in fact, gwibber didn't work at all; #37 and #73 fixed it, it was was the dns
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Paul Jakma (paul+launchpad-jakma) wrote : | #77 |
I also see the same "Twitter messages generally don't get received, except for replies/searches - sending works" behaviour. I had opened bug #554999 fir it.
Note that in my case the problem may go away by itself, but then later it will come back, etc.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Captain Chaos (launchpad-chaos) wrote : | #78 |
...and it stopped working again. So out of the blue it worked once (without me doing anything out of the ordinary, such as installing updates or removing files). This is a very strange problem.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
brianclements (brianclements) wrote : | #79 |
Same stuff mostly here. Worked initially: sending, receiving, twitter stream. Now All I see are my sent messages via the me-menu and the gwibber window itself. Those show up on my stream but nothing incoming. Here is some related contents from my ~/.cache/gwibber log:
2010-04-30 13:49:02,515 - Gwibber Accounts - INFO - Running from the system path
2010-04-30 13:49:07,046 - Gwibber Service - INFO - Running from the system path
2010-04-30 13:49:08,243 - Gwibber Dispatcher - INFO - Gwibber Service is reloading account credentials
2010-04-30 13:49:29,682 - Gwibber Dispatcher - INFO - Gwibber Service is reloading account credentials
2010-04-30 13:49:36,774 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-04-30 13:49:36,775 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-04-30 13:49:46,057 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-04-30 13:49:46,226 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: Unterminated string starting at: line 1 column 263020 (char 263020)
2010-04-30 13:49:46,227 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-04-30 13:49:48,209 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-04-30 13:49:48,210 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2010-04-30 13:49:48,210 - Gwibber Dispatcher - INFO - Loading complete: 1 - ['Failure', 'Failure', 'Failure']
2010-04-30 13:54:24,312 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-04-30 13:54:40,870 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-04-30 13:54:41,111 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: Unterminated string starting at: line 1 column 400381 (char 400381)
2010-04-30 13:54:41,113 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2010-04-30 13:54:41,114 - Gwibber Dispatcher - INFO - Loading complete: 2 - ['Failure', 'Success', 'Failure']
2010-04-30 13:55:02,414 - Gwibber Dispatcher - INFO - Gwibber Service is reloading account credentials
2010-04-30 13:55:22,010 - Gwibber Dispatcher - INFO - Gwibber Service is reloading account credentials
2010-04-30 13:55:24,490 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-04-30 13:55:24,561 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: Unterminated string starting at: line 1 column 98187 (char 98187)
2010-04-30 13:55:24,562 - Gwibber Dispatcher - ERROR - <identica:receive> Operation failed
2010-04-30 13:55:24,586 - Gwibber Dispatcher - INFO - Loading complete: 3 - ['Failure', 'Success', 'Success']
2010-04-30 13:55:27,474 - Gwibber Dispatcher - ERROR - <flickr:images> Operation failed
2010-04-30 13:55:27,487 - Gwibber Dispatcher - INFO - Loading complete: 4 - ['Failure']
2010-04-30 13:58:38,209 - Gwibber Dispatcher - INFO - Gwibber Service is reloading account credentials
2010-04-30 13:58:42,035 - Gwibber Dis...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dhananjay Nene (dhananjay-nene) wrote : | #80 |
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.
(Note: en_IN is my default locale, will vary across installations)
Maintainers kindly note and fix the problem.
YoooHooo!, gwibber works for me now.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
The House of Kannan (carliskith) wrote : Re: [Bug 530195] Re: Twitter doesn't work at all in Gwibber | #81 |
Actually, switching to OpenDNS did the trick for me...and my webpages
load tons faster too :)
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.
>
> (Note: en_IN is my default locale, will vary across installations)
>
> Maintainers kindly note and fix the problem.
>
> YoooHooo!, gwibber works for me now.
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bharath (bharath) wrote : | #82 |
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:/
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/
/usr/lib/
/usr/lib/
/usr/share/
/usr/share/
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.
>
> (Note: en_IN is my default locale, will vary across installations)
>
> Maintainers kindly note and fix the problem.
>
> YoooHooo!, gwibber works for me now.
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dhananjay Nene (dhananjay-nene) wrote : | #83 |
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:/
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:/
> 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/
> /usr/lib/
> /usr/lib/
> /usr/share/
> /usr/share/
>
> 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.
>
> (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://
twitter: http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bharath (bharath) wrote : | #84 |
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:/
>
> 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:/
> 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/
> /usr/lib/
> /usr/lib/
> /usr/share/
> /usr/share/
>
> 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.
> >
> > (Note: en_IN is my default locale, will vary across installations)
> >
> > Maintainers kindly note and fix the problem.
> >
> ...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitali Kulikou (sabotatore) wrote : Re: Twitter doesn't work at all in Gwibber | #85 |
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...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
ar (arjenmeijernl) wrote : | #86 |
Twitter started working today May 15th after latest lucid-proposed update.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Veet Moha (veet-moha) wrote : | #87 |
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 'WnckWindowMove
No dbus monitor yet
Updating...
Updating...
** (gwibber-
** (gwibber-
** (gwibber-
Updating...
Saving...
Could not identify preference: username
Could not identify preference: session_key
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
aId = "%s-%s" % (self.account[
KeyError: 'username'
Saving...
Updating...
ERROR:dbus.
ERROR:dbus.
** (gwibber:32192): CRITICAL **: murrine_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jahmon (jahmonspam-forum) wrote : | #88 |
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 'WnckWindowMove
No dbus monitor yet
Updating...
Updating...
ERROR:dbus.
ERROR:dbus.
** (gwibber:3998): CRITICAL **: murrine_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Miloš Mandarić (mandzo18) wrote : | #89 |
Twitter works now.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Philip Taylor (scraliontis) wrote : | #90 |
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/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if data.has_
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']
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitali Kulikou (sabotatore) wrote : | #91 |
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/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if data.has_
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
summary: |
- Twitter doesn't work at all in Gwibber + AttributeError: 'list' object has no attribute 'has_key' twitter doesnot + work |
summary: |
- AttributeError: 'list' object has no attribute 'has_key' twitter doesnot - work + gwibber tries to call has_key on list---twitter doesnot work |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jeroen Brandligt (jbrandligt) wrote : Re: gwibber tries to call has_key on list---twitter doesnot work | #92 |
Changin to OpenDNS (#81) did the trick for me. It also solved my issue not being able to add my Facebook account...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
brianclements (brianclements) wrote : | #93 |
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Philip Taylor (scraliontis) wrote : | #94 |
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : | #95 |
comment#8 and 10 on bug 571858 seems to have solved the problem for someone. (workaround)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
judsonmitchell (jmitchel-loyno) wrote : | #96 |
This problem was completely solved for me by this post:
https:/
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ed S (edgar-b-dsouza) wrote : | #97 |
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joao Verissimo (joniv) wrote : | #98 |
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
bernhard (bernhardredl) wrote : | #99 |
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://
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://
hope this information helps the developer to fix the problem.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ricardo Bánffy (rbanffy) wrote : | #100 |
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Lordinux (lordinux) wrote : | #101 |
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...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Pranesh Prakash (the-solipsist) wrote : | #102 |
The solution in comment #80 solved the problem! Thanks for that great debugging work, Dhananjay.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vipul (vipul-bhandari) wrote : | #103 |
Dhananjay solution in comment 80 worked for me too.....finally
Changed in gwibber: | |
status: | New → Confirmed |
tags: | added: patch-forwarded-upstream |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Lordinux (lordinux) wrote : | #104 |
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
caixamagica (caixa-magica) wrote : | #105 |
I would like to try solution #80.
But I don't know how to edit /usr/share/
Here is an empty file (on gedit).
Please help.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : | #106 |
could anyone in this bug report with enough python knowledge try to fix this bug.?
summary: |
- gwibber tries to call has_key on list---twitter doesnot work + gwibber tries to call has_key on list---doesn't update streams |
Changed in gwibber (Ubuntu): | |
status: | Confirmed → Triaged |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : | #107 |
there are too many people infected. there are many duplicate bugs with the same syptoms out there.
Changed in gwibber (Ubuntu): | |
importance: | Medium → High |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : | #108 |
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/
and edit
self.curl.
self.
to
self.curl.
self.
Your might even want to try a higher timeout in some cases.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : | #109 |
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
Changed in gwibber: | |
status: | Confirmed → Incomplete |
Changed in gwibber (Ubuntu): | |
status: | Triaged → Incomplete |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : | #110 |
did anyone try the proposed version?
Changed in gwibber (Ubuntu): | |
importance: | High → Medium |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Karsten W. Rohrbach (byteborg) wrote : | #111 |
WFM - works for me (2.30.1 from lucid-proposed on 10.04 amd64)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : | #112 |
Thanks for the confirmation Karsten.
Changed in gwibber: | |
status: | Incomplete → Fix Released |
Changed in gwibber (Ubuntu): | |
status: | Incomplete → Fix Committed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : | #113 |
gwibber 2.30.1 is now in Lucid updates.
Changed in gwibber (Ubuntu): | |
status: | Fix Committed → Fix Released |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitali Kulikou (sabotatore) wrote : | #114 |
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...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Omer Akram (om26er) wrote : Re: [Bug 530195] Re: gwibber tries to call has_key on list---doesn't update streams | #115 |
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...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vitali Kulikou (sabotatore) wrote : | #116 |
Yes, thanks..
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
martincasc (martincasco) wrote : | #117 |
I'm still having the issue. Gwibber doesn't update twitts
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
dooohhead (dooohhead) wrote : | #118 |
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"?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Chris Bauer (cfbauer) wrote : | #119 |
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.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Alan Lord (theopensourcerer) wrote : | #120 |
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 'WnckWindowMove
Updating...
Updating...
/usr/bin/
gtk.main()
Gwibber loads but does not update.
HTH
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Sebastian Martinez (tychocity) wrote : | #121 |
same problem here
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
dooohhead (dooohhead) wrote : Re: [Bug 530195] Re: gwibber tries to call has_key on list---doesn't update streams | #122 |
Found this today:
http://
<http://
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/
Gwibber with my Twitter account so now it does show up in my connections
settings page (in Twitter).
--
*DooohHead*
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