Gwibber not sending or receiving facebook messages

[LSL]

Binary package hint: gwibber

Sending messages to facebook using Gwibber will not succeed, and gwibber will not receive any updates from facebook. If I delete the account and start over it will pull all the current messages from facebook, and then it will not receive any messages after that thereby repeating the same behavior. I don't know if it has send and receive issues with any other accounts as I have only been trying it with facebook, but I can't get it to do anything, and I don't know how to check if it is something wrong with gwibber, or with using desktopcouch to store the messages, or what but if there is something you guys need just let me know.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gwibber 2.30.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
Architecture: amd64
Date: Thu Jul 29 13:42:17 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: gwibber

[Victor Vargas (kamus)]

@Michael, Please could you run under latest version of gwibber: gwibber-service -d -o and attach all resulted output to a textfile (following your steps to reproduce this issue), Thanks!

[LSL (spesialstyrker)]

I would, but now it won't let me add my Facebook account. Here is all I get when I try to add my Facebook:

vexille@Sector7:~$ gwibber-service -d -o
** Message: pygobject_register_sinkfunc is deprecated (GtkWindow)
** Message: pygobject_register_sinkfunc is deprecated (GtkInvisible)
** Message: pygobject_register_sinkfunc is deprecated (GtkObject)
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Refresh interval is set to 15
Gwibber Dispatcher: DEBUG Refresh interval is set to 15
Gwibber Dispatcher: DEBUG Raising gwibber client
Gwibber Dispatcher: DEBUG Gwibber Client raised
Gwibber Dispatcher: INFO Gwibber Service is being shutdown
Gwibber Dispatcher: DEBUG Unlocking password cache!
vexille@Sector7:~$

[Victor Vargas (kamus)]

Please could you check before run debug if there is another instance of gwibber-service running and kill him, then run last command that I posted.

[LSL (spesialstyrker)]

Alright I got it to add my facebook account, and in the attached .txt file at line 151 is where it hung at for 10 minutes until I chose quit from the gwibber menu since it was not pulling in any of the Facebook stuff.

[LSL (spesialstyrker)]

I can send messages with gwibber, but messages that I send with gwibber, or messages that I write on my own wall on Facebook do not get updated in gwibber. Here is the log from when I sent the message with gwibber, and tried to refresh gwibber several times to receive new messages from Facebook.

[Victor Vargas (kamus)]

is this behaviour occurring while you are using another accounts (like twitter, identi.ca, etc) or just affects facebook? have you tried to use an alternative for resolve domains such OpenDNS?

[LSL (spesialstyrker)]

Just have a Facebook account, and no I didn't think to try using something like OpenDNS...

[LSL (spesialstyrker)]

Now starting gwibber-service using the latest version reports errors when trying to receive facebook messages. I have attached the gwibber debug log.

[Victor Vargas (kamus)]

Have you checked if gnome-keyring-daemon is running? if not, please open a terminal and run "gnome-keyring-daemon" then try to run gwibber again.

[LSL (spesialstyrker)]

I just tried it after running the gnome keyring daemon, and got the same results. Here is my log.

[Maverick JS (mavjs)]

I'm running Gwibber version 2.31.4. In my case I can receive messages from Facebook through Gwibber, but couldn't update my status through it. But as you mentioned above I run "gnome-keyring-daemon" and started up "gwibber-service -d -o", I could send my status update.

P.S. If you think that my case does not apply here, you can delete it. I'm just eager to help make Gwibber better.

[Victor Vargas (kamus)]

Michael you should try to run some workaround published in bug 614742, that contains a series of issues related to facebook.