gwibber-accounts crashed with ServerError in _request()

[Camille Appert]

Binary package hint: gwibber

Updated to Lucid Alpha 1 from Karmic, gwibber showed up in my notification area, so I clicked on it, I was offered to import accounts from pidgin, which I did, I had my 2 jabber (gmail+gafyd) accounts and my msn account selected, then clicking on Appliquer (french for Submit? I think it was the last panel), gwibber crashed and apport showed up.

Ask me, if you need any more information.

ProblemType: Crash
Architecture: amd64
Date: Fri Feb 26 09:31:28 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber-accounts
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: gwibber 2.29.90.1-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-accounts
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
PythonArgs: ['/usr/bin/gwibber-accounts']
SourcePackage: gwibber
Title: gwibber-accounts crashed with ServerError in _request()
Uname: Linux 2.6.32-14-generic x86_64
UserGroups: adm admin audio cdrom fuse lpadmin netdev plugdev sambashare scanner

[Camille Appert (bibinou)]

This bug is not a duplicate of bug 525302 because the tracebacks are different.

#525302 :
  File "/usr/lib/python2.6/dist-packages/desktopcouch/local_files.py", line 76, in __init__
    ":".join([admin_username, admin_password]), True)
BadArgumentsError

#528286 (this one) :

  File "/usr/lib/pymodules/python2.6/couchdb/client.py", line 1035, in _request
    raise ServerError((status_code, error))
ServerError: (500, '')

[Oded Arbel (oded-geek)]

I just updated gwibber from Lucid current, and got this error on "gwibber-service" (and also on "gwibber-accounts" - I tried both)

[Dan Wood (dan-wood)]

Lucid Alpha 2.

Crash when clicking on 'Broadcast Accounts...' on the menu.

No accounts yet set up.

[Victor Vargas (kamus)]

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

[Camille Appert (bibinou)]

I tried to reproduce the bug but can't find the specific program or command to trigger the dialog I saw.

Anyway, messing around a bit, I think this may not related to gwibber, but to the indicator-applet, or any indicator-stuff.

By killing indicator-me, the Accounts item in the indicator applet menu disappear, and gwibber only manage *broadcast* accounts, right ?

But maybe gwibber is in the same project ? (Social from the start project?)

Still, running gwibber or gwibber-preferences, or gwibber-accounts, I still get desktopcouch errors (like in this bug), but apport can't report it because it can't connect to the crash database, even if I'm connected to the Internet and made no network changes whatsoever.

I admit this message could be confusing, but if you could point me to resources explaining the relation between gwibber, the indicator applet, or desktopcouch; I would be happy to provide stacktraces and clear and concise bug reports.

[c. mehlis (mehlis-deactivatedaccount)]

I have gwibber not configured and clicked on the gwibber menu in the tool-tip area, then it cashes

[papukaija (papukaija)]

Confirmed, I didn't try to open gwibber. Apport just informed about a crash.

[Camille Appert (bibinou)]

Adding the Me Menu project per my comments in #6

[David Barth (dbarth)]

The "me menu" is just calling the gwibber-accounts command, part of the gwibber module. As such, there's not much the me menu can do to prevent that from hapenning. However, it may be interesting in the next version to catch async command exec that fail or provide some feedback mechanism to the user.

[Nigel Morton (nigelamorton)]

Bug appears on fresh install on Lucid beta 1 plus all updates up to 2nd April. Crash only occurs on first use setting up broadcast account; second attempt to enter an id works.

[Mike Grunewald (mikeg32)]

Bug appears on fresh install on Lucid beta 1 plus all updates up to 2nd April. Crash only occurs on first use setting up broadcast account

Confirmed same here

[Victor Vargas (kamus)]

@Camille, Please could you run under latest version of gwibber: gwibber --debug > gwibber-debug.txt and attach resulted output of this file to your report (following your steps to reproduce this issue), Thanks!

[papukaija (papukaija)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Camille Appert (bibinou)]

Sorry, I have had this bug on my task list for a long time, I'll do it next week.
As this only happen after a Karmic -> Lucid update I have to run a VM, so it can take some time.

[Camille Appert (bibinou)]

Cannot reproduce the bug.

Anyway, this is linked to desktopcouch and gwibber won't use it anymore : http://arstechnica.com/open-source/reviews/2010/05/lucid-dream-ars-reviews-ubuntu-1004.ars/9

[Camille Appert (bibinou)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Omer Akram (om26er)]

gwibber will use desktopcouch in future too in Ubuntu atleast.