Description of problem: After resolving the Gtk issue in https://bugzilla.redhat.com/show_bug.cgi?id=1047618 , it is still unable to add accounts due to another error. When attempting to authorize an account with either Facebook or Twitter, the application times out and does not succeed in either authorizing the account, adding it to the main window, or providing posts and messages from Facebook or Twitter. Version-Release number of selected component (if applicable): [root@prannondesk /root]# rpm -q gwibber gwibber-3.4.2-9.fc19.x86_64 How reproducible: Open Gwibber in XFCE, attempt to add a twitter or facebook account and authorize it, wait, and see the timeout with no twitter or facebook information displayed on the main window. Steps to Reproduce: 1. Start Gwibber 2. Add an Account 3. Attempt to Authorize Account 4. Observe time out after authorization attempt when the client states "Redirecting you Back to Application. This may take a few minutes." Actual results: Gwibber does not successfully authorize the account, and you are unable to make use of the client to post to facebook or twitter. Expected results: Gwibber should successfully authorize the account and I should be able to proceed with using it to make posts. Additional info: The following is the shell output from program launch to error. [root@prannondesk /root]# gwibber (gwibber:30723): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion `!g_slist_find (group, radio_button)' failed (gwibber:30723): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed (gwibber:30723): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion `!g_slist_find (group, radio_button)' failed Loading plugin for pingfm Loading plugin for foursquare Loading plugin for friendfeed Loading plugin for identica Loading plugin for facebook Loading plugin for flickr Loading plugin for twitter Loading plugin for statusnet Loading plugin for qaiku Loading plugin for digg Loading plugin for buzz Traceback (most recent call last): File "/usr/share/gwibber/plugins/facebook/gtk/facebook/__init__.py", line 152, in on_facebook_auth_title_change saved = self.dialog.on_edit_account_save() File "/usr/lib/python2.7/site-packages/gwibber/accounts.py", line 252, in on_edit_account_save getattr(self.gwibber.accounts, fn)(json.dumps(self.account)) File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
I'm not sure if I'm having the same issue but when trying to add a Twitter account I can get to the Broadcast Accounts screen but it stays blank. When running from terminal I don't see the Python errors but do see ** (gwibber-accounts:23068): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.