gossip fails to authenticate

what version of the package?

Ar 23/02/2006 am 16:46, ysgrifennodd Sebastien Bacher:
> what version of the package?

0.10-0ubuntu1

--
Dafydd

Thanks for the bug report. As the critical warning clearly indicates some bug, may I ask, if you checked your user/password?

Ar 23/02/2006 am 18:17, ysgrifennodd Daniel Holbach:
> Thanks for the bug report. As the critical warning clearly indicates
> some bug, may I ask, if you checked your user/password?

I installed Gaim and succesfully managed to log into the Jabber account,
although authentication was very slow.

--
Dafydd

I can confirm this.

Me too, same symptoms.

Confirmed here as well. I checked my Jabber server's firewall logs and the Jabber daemon's error log - no issue with connectivity. Gajim and GAIM both connect with no problems.

I am using Dapper package 0.10-0ubuntu1.

could you try again with 0.10.1 (soon in the archive)?

Ok... 0.10.1 is still broken.

There are now no errors on the console. Gossip starts up and the notification icon is put in the console with the green "Connected" icon displayed.

However, the Status combobox and all of the menu options that would ordinarily be enabled when the client is connected to a server are *disabled*. The contact list remains empty. Selecting Chat->Connect does nothing. netstat shows no Jabber connections or other network activity.

Tried again after deleting ~/.gnome2/Gossip and got the same result.

I found a workaround. Jordi mentioned that this can happen if the <id> element in accounts.xml doesn't have a resource -- i.e. foo@bar rather than foo@bar/resource. Adding resources by hand to this file makes it work again.

Indeed, adding a resource to the <id> fixes it for me. Thanks for mentioning that.

Fixes it for me too. Can we assume that this is an upstream issue then? If so, should probably open a bug in the GNOME tracker and link it to this one.

In bug 35706 I asked for UpstreamVersionFreeze exception for gossip 0.10.2 - this includes the following fix

"- Changed the account ID for Jabber IDs back to 'username@server' and
make the resource a separate entity in the accounts.xml (note: there
is some extra code to make sure the same problems that occurred last
time don't reoccurr this time with invalid usernames when trying to
connect) (Martyn). "

That one will hopefully make the world happy again. I'd be grateful, if you could check, once it's in the archive.

I had added the resource to the <id> entity as suggested by Dafydd and so gossip 0.10.1 worked, and 0.10.2 has correctly converted that to use the <resource> entity, so it still works.

If I now delete that <resource> entity, gossip doesn't connect and also doesn't print an error message to the console. I'm not sure if it could cope with an old-style accounts.xml.

fixed according to upstream, I'm closing the bug. Feel free to reopen if you still get the issue with the new version