Broadcast Accounts window appears every time refresh should occur

[Sam L.]

Binary package hint: gwibber

Release: Ubuntu maverick 10.10
Gwibber version: 2.31.91

What I expected to happen: My broadcast account streams to be refreshed silently every x minutes as set in preferences.

What happens instead: The broadcast accounts window appears, which I'm forced to close thus, closing Gwibber which means "Broadcast" is not active in the messaging menu (no arrow beside it).

[Victor Vargas (kamus)]

This is weird, please could you run in a terminal gwibber --debug and included all the output while you reproduce this issue (and if you upgrade to 2.31.92-0ubuntu1 even better)? Thanks

[Sam L. (somethinginteres)]

Hi Kamus,
I have updated to the latest version and the problem still occurs. I have
run 'gwibber --debug' when the problem occurs and all I am getting is some
errors when the main app first opens (before any errors) and then some
printouts when I scroll up or down. Nothing when the error specifically
happens.

On Sat, Sep 11, 2010 at 6:09 AM, Kamus <email address hidden> wrote:

> This is wease could you run in a terminal gwibber --debug and
> included all the output while you reproduce this issue (and if you
> upgrade to 2.31.92-0ubuntu1 even better)? Thanks
>
> ** Changed in: gwibber (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: gwibber (Ubuntu)
> Status: New => Incomplete
>
> --
> Broadcast Accounts window appears every time refresh should occur
> https://bugs.launchpad.net/bugs/632965
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “gwibber” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: gwibber
>
> Release: Ubuntu maverick 10.10
> Gwibber version: 2.31.91
>
> What I expected to happen: My broadcast account streams to be refreshed
> silently every x minutes as set in preferences.
>
> What happens instead: The broadcast accounts window appears, which I'm
> forced to close thus, closing Gwibber which means "Broadcast" is not active
> in the messaging menu (no arrow beside it).
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/632965/+subscribe
>

[Omer Akram (om26er)]

thanks for the bug report. is it still happening in maverick?

[Sam L. (somethinginteres)]

Hi Omer,
It is indeed still happening in maverick.

[Sam L. (somethinginteres)]

In addition as with the duplicate bug, my twitter is not connecting for about 5 days now. Though, I did notice the arrow (> Broadcast) no longer goes away when I dismiss the dialog.

[Tim Penhey (thumper)]

I recently upgraded to maverick and I've had this problem since the upgrade.

Anything particular I could add?

[Vadim Rutkovsky (roignac)]

A call for people affected with the bug - please, specify which account types did you add. I had this reproduced after I've added Twitter account

[Robbie Williamson (robbiew)]

This is by no means a fix, but I found removing all my local gwibber settings and doing a purge/reinstall of gwibber helped a lot of my problems. If you are interested in trying this do a:
  ps -ef | grep gwibber
and kill -9 any processes running, then remove the following under your user directory in /home:
  rm .local/share/desktop-couch/gwibber_preferences.couch
  rm -rf ./.cache/gwibber/
  rm -rf .local/share/desktop-couch/.gwibber_accounts_design
  rm -rf ./.gconf/apps/gwibber
  rm -rf ./.config/gwibber
then purge all three gwibber package with:
  sudo dpkg --purge --force-depends gwibber gwibber-service libgwibber0
  sudo apt-get install gwibber
    (this should automatically install gwibber-service libgwibber0, but if not just apt-get install them too)

Unfortunately, this will force you to re-add all your accounts, but that shouldn't take but a few minutes.

[Tim Penhey (thumper)]

On Sat, 18 Sep 2010 20:57:50 you wrote:
> A call for people affected with the bug - please, specify which account
> types did you add. I had this reproduced after I've added Twitter
> account

I didn't add any accounts. On lucid I had facebook, identi.ca and twitter.
The problem only occurred on upgrading to maverick.

[Tim Penhey (thumper)]

Thanks Robbie for the workaround, but I'll keep the problem for a few days to see if I can help diagnose the underlying issue. I'm not that addicted to my social micro-bloggers :)

[Edward Betts (edwardbetts)]

Here is the output from gwibber --debug (Version: 2.32.0.2-0ubuntu1):

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

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

** (gwibber:10917): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
/usr/bin/gwibber:73: GtkWarning: IA__gtk_container_add: assertion `GTK_IS_CONTAINER (container)' failed
  gtk.main()
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 214, in maybe_handle_message
    self._handler(*args, **kwargs)
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 519, in on_loading_complete
    self.update_view()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 322, in update_view
    self.stream_view.update()
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 393, in update
    self.messages.update(self.navigation.selected_stream)
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 724, in update
    self.messages = self.message_view.render([selected_stream], count)
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 735, in render
    accounts = json.loads(self.model.accounts.List())
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking
    message, timeout)
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.
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 214, in maybe_handle_message
    self._handler(*args, **kwargs)
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 519, in on_loading_complete
    self.update_view()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 322, in update_view
    self.stream_view.update()
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 393, in update
    self.messages.update(self.navigation.selected_stream)
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 724, in update
    self.messages = self.message_view.render([selected_stream], count)
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 735, in render
    accounts = json.loads(self.model.accounts.List())
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking
    message, timeout)
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 t...

[Victor Vargas (kamus)]

@Edward you are facing a different issue, @Sam, please could you try to run the workaround published in comment #8 and check if is still affecting you? Thanks

[Sam L. (somethinginteres)]

Karmus,
An updated version at some point must have fixed the issues I was having. I'm now running the latest Gwibber maverick release and this is no longer an issue.

[Victor Vargas (kamus)]

Thanks for you feedback Sam, marked as fixed then. Thank you