Nabble - Gnome - Gossip - Dev

Mailing List Move After 9th January

2009-01-03T16:45:21Z

Hi,

This mailing list is going to be moved from lists.imendio.com to
mail.gnome.org. I have a list of everyone here subscribed and plan on
mass-subscribing everyone currently on this mailing list some time after
Friday 9th of January (to give people a chance to respond to this).

If anyone wishes to be excluded from this list, please send me an email
and I will omit you when I come to do it.

Hopefully this will be as painless as possible :)

--
Regards,
Martyn
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Gossip list moved to GNOME infrastructure

2009-01-03T14:05:08Z

Hi everyone,

We are currently obsoleting our public lists on lists.imendio.com and
have moved the Gossip list to a new location on GNOME infrastructure.
Unfortunately the archive has not yet been moved over due to some
issues with the GNOME import script. I'm not sure whether it makes a
big difference at this point, seeing that the rate of posting has been
very low lately and the last two years have been archived at Mail
Archive [1].

The new location for the list is at:

http://mail.gnome.org/mailman/listinfo/gossip-list

Be sure to subscribe to it if you intend to continue to follow the
Gossip project.

Cheers,
Mikael Hallendal

[1] http://www.mail-archive.com/gossip-dev@.../
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: Porting the latest gossip to FreeBSD

2008-08-03T16:27:17Z

Joe Marcus Clarke wrote:
> On Sun, 2008-08-03 at 21:45 +0100, Martyn Russell wrote:
>> Joe Marcus Clarke wrote:
> I found the problem. It is due to ebook support. This links gossip to
> e-d-s which links to NSS (for SSL support). There is a symbol conflict
> between GnuTLS and NSS on FreeBSD. If loudmouth is linked with
> -Wl,-Bsymbolic, the problem goes away, and gossip can once again
> authenticate and have working ebook support.

Oh, I saw your reply too late :)

Great that you found the problem!
Thanks for letting us know.

--
Regards,
Martyn
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: Porting the latest gossip to FreeBSD

2008-08-03T16:25:19Z

Joe Marcus Clarke wrote:
> On Sun, 2008-08-03 at 21:45 +0100, Martyn Russell wrote:
>
> Thanks for your reply.

:)

>>> The NetworkManager error doesn't appear to be fatal, and I get
>>> this with 0.28 as well.
>> The network manager issue there shouldn't be a problem. But I
>> wonder if it is part of the problem?
>
> I saw it in the working 0.28. FreeBSD doesn't have an NM port yet.

OK.

>>> Nothing else is different settings-wise between 0.28 and 0.31.
>>> I'm using the resource Home, and I am using encryption. I've
>>> tried both ports 5222 and 5223. The server is jabber.org.
>> Gossip should switch between ports for you. But for old SSL
>> authentication, you want to use port 5223. Otherwise port 5222
>> should work.
>
> It does. 0.26, 0.27, and 0.28 want to use 5223, but 0.29 and 0.31
> want to use 5222. Neither port authenticates successfully in 0.29
> and 0.31.

I know that in the past jabber.org hasn't worked for me using the
STARTTLS method on port 5222 (the new secure method of authenticating).

There are two set ups which should work:

Option #1:
- Port 5223
- Enable "Force older secure connection method".
- Enable "Ignore certificate warnings".
- Enable "Use Encryption".

Option #2:
- Port 5222
- Disable "Force older secure connection method".
- Enable "Ignore certificate warnings".
- Enable "Use Encryption".

>>> Both gossip 0.28 and pidgin can connect with this account and
>>> password. Creating a new account in gossip 0.31 also does not
>>> work. Any clue as to what the problem may be? Is there any
>>> additional troubleshooting I can do? A sniffer isn't helpful as
>>> this is all encrypted.
>> Hmm, interesting. I can connect to my jabber.org account fine here.
>> If you run Gossip with LM_DEBUG=all, does it give you any more
>> information?
>
> Well, it's all hashed, so it doesn't really tell me what it's really
> sending:
>
> *** Socket library initialising... *** Connecting to: jabber.org:5223
> *** SRV lookup disabled for jabber.org Going to connect to
> jabber.org:5223 Trying 208.68.163.220 port 5223... Connection success
> (2). *** Setting up SSL... *** GNUTLS negotiated compression: DEFLATE

So it looks like you are using the older secure connection method (i.e.
option #1 from above.

> RECV [77]: -----------------------------------
> '<failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-authorized/></failure>'
> -----------------------------------
> *** Read: 77 chars LM-PARSER:
> ATTRIBUTE: xmlns = urn:ietf:params:xml:ns:xmpp-sasl
> LM-PARSER: Trying to close node: not-authorized
> LM-PARSER: Trying to close node: failure
> LM-PARSER: Have a new message
> *** New message with type="failure" from: unknown
> LM-SASL: sasl_failure_cb:
> SASL authentication failed: unknown reason
> *** SASL authentication failed,
> closing connection
> *** Disconnecting from: jabber.org:5223

This looks like the password is wrong. The connection is made
successfully, the authentication stage just seems to fail.

Does authentication work if you don't use encryption?

> How can I see what username and password is actually being sent?

If you use:

export GOSSIP_DEBUG=Jabber

You should be able to see this sort of debug when you try to connect:

With option #1:

Jabber: Refreshing connection details
Jabber: Setting connection details for account:'Testing2'
Jabber: - ID:'testing2@...'
Jabber: - Server:'jabber.org'
Jabber: - Port:5223
Jabber: - Using OLD SSL method for connection
Jabber: Connecting...
Jabber: Untrusted certificate
Jabber: Connection open!
Jabber: Attempting to use JabberID:'testing2@...'
Jabber: Connection logged in!

With option #2:

Jabber: Refreshing connection details
Jabber: Setting connection details for account:'Testing2'
Jabber: - ID:'testing2@...'
Jabber: - Server:'jabber.org'
Jabber: - Port:5222
Jabber: - Using STARTTLS method for connection
Jabber: Connecting...
Jabber: Connection open!
Jabber: Attempting to use JabberID:'testing2@...'
Jabber: Untrusted certificate
Jabber: Connection logged in!

> Where could I add some debug code to print that?

You can also use:

export GOSSIP_DEBUG=all

But there is a lot of debugging there to drown in :)

If you want to print the password, try adding a debug line in this file:

http://svn.gnome.org/viewvc/gossip/trunk/libgossip/gossip-jabber.c?view=markup

In the function _gossip_jabber_set_connection(). Something like:

gossip_debug (DEBUG_DOMAIN,
"- Password:'%s'",
gossip_account_get_password (account));

We don't normally put the password in the log for security reasons.
Hope this helps.

--
Regards,
Martyn
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: Porting the latest gossip to FreeBSD

2008-08-03T16:12:37Z

On Sun, 2008-08-03 at 21:45 +0100, Martyn Russell wrote:

> Joe Marcus Clarke wrote:
>
> Hi :)
>
> > I have been trying to update our gossip port from 0.26 to 0.31.
> > Loudmouth 1.4.1 is successfully installed, and gossip 0.31 builds fine
> > except for one small patch (attached). The problem is, gossip 0.31
> > refuses to authenticate with jabber.org. I always get an authentication
> > failed (error 4). If I downgrade to gossip 0.28, everything works.
>
> OK.
>
> First, thanks for the patch!
>
> > If I then upgrade to 0.29, I am no longer able to login again. I am
> > using gnome-keyring, and I can see in my keyring that the password is
> > successfully stored. Debug from 0.31 shows:
> >
> > Jabber: Untrusted certificate
> > Jabber: Connection open!
> > Jabber: Attempting to use JabberID:'FreeBSDMarcus@...'
> > Jabber: Disconnecting for account:'Test'
> > Session: Protocol disconnecting for account:'Test'
> > Sound: Protocol disconnecting for account:'Test'
> > Session: Protocol disconnected (after 0.00 seconds)
> > AppSession: Disconnected account:'Test'
> > DBUS: Failed to complete 'state' request. The name
> > org.freedesktop.NetworkManager was not provided by any .service files
> > JabberUtils: Error:4->'Authentication failed.'
> > Session: Error:4->'Authentication failed.'
> > AppSession: Error for account:'Test'
> >
> > The NetworkManager error doesn't appear to be fatal, and I get this with
> > 0.28 as well.
>
> The network manager issue there shouldn't be a problem. But I wonder if
> it is part of the problem?
>
> > Nothing else is different settings-wise between 0.28 and
> > 0.31. I'm using the resource Home, and I am using encryption. I've
> > tried both ports 5222 and 5223. The server is jabber.org.
>
> Gossip should switch between ports for you. But for old SSL
> authentication, you want to use port 5223. Otherwise port 5222 should work.
>
> > Both gossip 0.28 and pidgin can connect with this account and password.
> > Creating a new account in gossip 0.31 also does not work. Any clue as
> > to what the problem may be? Is there any additional troubleshooting I
> > can do? A sniffer isn't helpful as this is all encrypted.
>
> Hmm, interesting. I can connect to my jabber.org account fine here.
> If you run Gossip with LM_DEBUG=all, does it give you any more information?

I found the problem. It is due to ebook support. This links gossip to
e-d-s which links to NSS (for SSL support). There is a symbol conflict
between GnuTLS and NSS on FreeBSD. If loudmouth is linked with
-Wl,-Bsymbolic, the problem goes away, and gossip can once again
authenticate and have working ebook support.

Joe

--
PGP Key : http://www.marcuscom.com/pgp.asc

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

signature.asc (202 bytes) Download Attachment

Re: Porting the latest gossip to FreeBSD

2008-08-03T14:20:26Z

On Sun, 2008-08-03 at 21:45 +0100, Martyn Russell wrote:

Thanks for your reply.

> > The NetworkManager error doesn't appear to be fatal, and I get this with
> > 0.28 as well.
>
> The network manager issue there shouldn't be a problem. But I wonder if
> it is part of the problem?

I saw it in the working 0.28. FreeBSD doesn't have an NM port yet.

>
> > Nothing else is different settings-wise between 0.28 and
> > 0.31. I'm using the resource Home, and I am using encryption. I've
> > tried both ports 5222 and 5223. The server is jabber.org.
>
> Gossip should switch between ports for you. But for old SSL
> authentication, you want to use port 5223. Otherwise port 5222 should work.

It does. 0.26, 0.27, and 0.28 want to use 5223, but 0.29 and 0.31 want
to use 5222. Neither port authenticates successfully in 0.29 and 0.31.

>
> > Both gossip 0.28 and pidgin can connect with this account and password.
> > Creating a new account in gossip 0.31 also does not work. Any clue as
> > to what the problem may be? Is there any additional troubleshooting I
> > can do? A sniffer isn't helpful as this is all encrypted.
>
> Hmm, interesting. I can connect to my jabber.org account fine here.
> If you run Gossip with LM_DEBUG=all, does it give you any more information?

Well, it's all hashed, so it doesn't really tell me what it's really
sending:

*** Socket library initialising...
*** Connecting to: jabber.org:5223
*** SRV lookup disabled for jabber.org
Going to connect to jabber.org:5223
Trying 208.68.163.220 port 5223...
Connection success (2).
*** Setting up SSL...
*** GNUTLS negotiated compression: DEFLATE
SEND:
-----------------------------------
<?xml version='1.0' encoding='UTF-8'?>
-----------------------------------
*** Sending stream header

SEND:
-----------------------------------
<stream:stream version="1.0" xmlns="jabber:client"
xmlns:stream="http://etherx.jabber.org/streams" to="jabber.org"
id="4360577850">
-----------------------------------

RECV [168]:
-----------------------------------
'<?xml version='1.0'?><stream:stream xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' id='2193159157'
from='jabber.org' version='1.0' xml:lang='en'>'
-----------------------------------
*** Read: 168 chars
LM-PARSER: ATTRIBUTE: xmlns = jabber:client
LM-PARSER: ATTRIBUTE: xmlns:stream = http://etherx.jabber.org/streams
LM-PARSER: ATTRIBUTE: id = 2193159157
LM-PARSER: ATTRIBUTE: from = jabber.org
LM-PARSER: ATTRIBUTE: version = 1.0
LM-PARSER: ATTRIBUTE: xml:lang = en
LM-PARSER: Trying to close node: stream:stream
LM-PARSER: Have a new message
*** New message with type="stream:stream" from: jabber.org
*** XMPP 1.0 stream received: 2193159157

RECV [220]:
-----------------------------------
'<stream:features><mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism></mechanisms><register xmlns='http://jabber.org/features/iq-register'/></stream:features>'
-----------------------------------
*** Read: 220 chars
LM-PARSER: ATTRIBUTE: xmlns = urn:ietf:params:xml:ns:xmpp-sasl
LM-PARSER: Trying to close node: mechanism
LM-PARSER: Trying to close node: mechanism
LM-PARSER: Trying to close node: mechanisms
LM-PARSER: ATTRIBUTE: xmlns = http://jabber.org/features/iq-register
LM-PARSER: Trying to close node: register
LM-PARSER: Trying to close node: stream:features
LM-PARSER: Have a new message
*** New message with type="stream:error" from: unknown
LM-SASL: Stream features received

SEND:
-----------------------------------
<auth mechanism="DIGEST-MD5" xmlns="urn:ietf:params:xml:ns:xmpp-sasl"
id="134986749423"></auth>

-----------------------------------

RECV [148]:
-----------------------------------
'<challenge
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>bm9uY2U9IjEwNzU0Mzk4MjEiLHFvcD0iYXV0aCIsY2hhcnNldD11dGYtOCxhbGdvcml0aG09bWQ1LXNlc3M=</challenge>'
-----------------------------------
*** Read: 148 chars
LM-PARSER: ATTRIBUTE: xmlns = urn:ietf:params:xml:ns:xmpp-sasl
LM-PARSER: Trying to close node: challenge
LM-PARSER: Have a new message
*** New message with type="challenge" from: unknown

SEND:
-----------------------------------
<response xmlns="urn:ietf:params:xml:ns:xmpp-sasl"
id="264451813363">dXNlcm5hbWU9IkZyZWVCU0RNYXJjdXMiLHJlYWxtPSJqYWJiZXIub3JnIixkaWdlc3QtdXJpPSJ4bXBwL2phYmJlci5vcmciLG5vbmNlPSIxMDc1NDM5ODIxIixuYz0wMDAwMDAwMSxjbm9uY2U9IkNaVWZOSkZqQllSNE5jSzBGOXdHYi9WMDR0ZXhFVW5KaUFFQzYvTUV6d2M9Iixxb3A9YXV0aCxjaGFyc2V0PXV0Zi04LHJlc3BvbnNlPTNlZDk1ZjQ5MGNhYzNmYTUzNGUxMjBkZTgwYWM5YWMw</response>

-----------------------------------

RECV [77]:
-----------------------------------
'<failure
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-authorized/></failure>'
-----------------------------------
*** Read: 77 chars
LM-PARSER: ATTRIBUTE: xmlns = urn:ietf:params:xml:ns:xmpp-sasl
LM-PARSER: Trying to close node: not-authorized
LM-PARSER: Trying to close node: failure
LM-PARSER: Have a new message
*** New message with type="failure" from: unknown
LM-SASL: sasl_failure_cb: SASL authentication failed: unknown reason***
SASL authentication failed, closing connection
*** Disconnecting from: jabber.org:5223

SEND:
-----------------------------------
</stream:stream>
-----------------------------------
Freeing up IOChannel and file descriptor

How can I see what username and password is actually being sent? Where
could I add some debug code to print that?

Joe

--
PGP Key : http://www.marcuscom.com/pgp.asc

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

signature.asc (202 bytes) Download Attachment

Re: Porting the latest gossip to FreeBSD

2008-08-03T13:45:18Z

Joe Marcus Clarke wrote:

Hi :)

> I have been trying to update our gossip port from 0.26 to 0.31.
> Loudmouth 1.4.1 is successfully installed, and gossip 0.31 builds fine
> except for one small patch (attached). The problem is, gossip 0.31
> refuses to authenticate with jabber.org. I always get an authentication
> failed (error 4). If I downgrade to gossip 0.28, everything works.

OK.

First, thanks for the patch!

> If I then upgrade to 0.29, I am no longer able to login again. I am
> using gnome-keyring, and I can see in my keyring that the password is
> successfully stored. Debug from 0.31 shows:
>
> Jabber: Untrusted certificate
> Jabber: Connection open!
> Jabber: Attempting to use JabberID:'FreeBSDMarcus@...'
> Jabber: Disconnecting for account:'Test'
> Session: Protocol disconnecting for account:'Test'
> Sound: Protocol disconnecting for account:'Test'
> Session: Protocol disconnected (after 0.00 seconds)
> AppSession: Disconnected account:'Test'
> DBUS: Failed to complete 'state' request. The name
> org.freedesktop.NetworkManager was not provided by any .service files
> JabberUtils: Error:4->'Authentication failed.'
> Session: Error:4->'Authentication failed.'
> AppSession: Error for account:'Test'
>
> The NetworkManager error doesn't appear to be fatal, and I get this with
> 0.28 as well.

The network manager issue there shouldn't be a problem. But I wonder if
it is part of the problem?

> Nothing else is different settings-wise between 0.28 and
> 0.31. I'm using the resource Home, and I am using encryption. I've
> tried both ports 5222 and 5223. The server is jabber.org.

Gossip should switch between ports for you. But for old SSL
authentication, you want to use port 5223. Otherwise port 5222 should work.

> Both gossip 0.28 and pidgin can connect with this account and password.
> Creating a new account in gossip 0.31 also does not work. Any clue as
> to what the problem may be? Is there any additional troubleshooting I
> can do? A sniffer isn't helpful as this is all encrypted.

Hmm, interesting. I can connect to my jabber.org account fine here.
If you run Gossip with LM_DEBUG=all, does it give you any more information?

--
Regards,
Martyn
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Porting the latest gossip to FreeBSD

2008-08-03T13:34:52Z

I have been trying to update our gossip port from 0.26 to 0.31.
Loudmouth 1.4.1 is successfully installed, and gossip 0.31 builds fine
except for one small patch (attached). The problem is, gossip 0.31
refuses to authenticate with jabber.org. I always get an authentication
failed (error 4). If I downgrade to gossip 0.28, everything works.

If I then upgrade to 0.29, I am no longer able to login again. I am
using gnome-keyring, and I can see in my keyring that the password is
successfully stored. Debug from 0.31 shows:

Jabber: Untrusted certificate
Jabber: Connection open!
Jabber: Attempting to use JabberID:'FreeBSDMarcus@...'
Jabber: Disconnecting for account:'Test'
Session: Protocol disconnecting for account:'Test'
Sound: Protocol disconnecting for account:'Test'
Session: Protocol disconnected (after 0.00 seconds)
AppSession: Disconnected account:'Test'
DBUS: Failed to complete 'state' request. The name
org.freedesktop.NetworkManager was not provided by any .service files
JabberUtils: Error:4->'Authentication failed.'
Session: Error:4->'Authentication failed.'
AppSession: Error for account:'Test'

The NetworkManager error doesn't appear to be fatal, and I get this with
0.28 as well. Nothing else is different settings-wise between 0.28 and
0.31. I'm using the resource Home, and I am using encryption. I've
tried both ports 5222 and 5223. The server is jabber.org.

Both gossip 0.28 and pidgin can connect with this account and password.
Creating a new account in gossip 0.31 also does not work. Any clue as
to what the problem may be? Is there any additional troubleshooting I
can do? A sniffer isn't helpful as this is all encrypted.

Joe

--
PGP Key : http://www.marcuscom.com/pgp.asc

[patch-libloudermouth_lm-bs-listener.c]

--- libloudermouth/lm-bs-listener.c.orig 2008-08-03 14:38:37.000000000 -0400 +++ libloudermouth/lm-bs-listener.c 2008-08-03 14:38:50.000000000 -0400 @@ -27,6 +27,7 @@ #include <glib.h> #ifndef G_OS_WIN32 +#include <sys/types.h> #include <sys/socket.h> #include <netinet/tcp.h> #endif /* G_OS_WIN32 */

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

signature.asc (202 bytes) Download Attachment

ANNOUNCE: Gossip 0.31 released

2008-08-02T04:41:00Z

Gossip 0.31 is now available for download from:
http://download.gnome.org/sources/gossip/0.31/

06be796f7df49156ecdb017f852a7c61 gossip-0.31.tar.gz
feacf7a78ced249268898d2a3f7063cd gossip-0.31.tar.bz2

What is it?
===========
Gossip is an instant messaging client for GNOME with an easy-to-use
interface, providing users of the GNOME Desktop with a friendly way to
keep in touch with their friends.

Where can I find out more?
==========================
You can visit the project web site:
http://developer.imendio.com/projects/gossip

What's New?
===========
- Loudmouth requirement has been bumped up to 1.4.1. Changed so that
normal XMPP "pings" are always sent when keep alive is enabled. This
fixes the problem where connections would drop periodically.

Bugs Fixed:
===========
- Fixed #544346, Roster contact name changes (Martyn Russell)
- Fixed #545451, Network traffic is incredibly high due to constant
vcard requests (Martyn Russell)

Translations:
=============
- Updated ar: Djihed Afifi
- Updated ca: Jordi Mallach
- Updated es: Daniel Mustieles, Jorge González
- Updated sv: Daniel Nylander

Manual Translations:
====================
None

02 August 2008
Gossip team
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

ANNOUNCE: Gossip 0.30 released

2008-07-20T07:43:42Z

Gossip 0.30 is now available for download from:
http://download.gnome.org/sources/gossip/0.30/

0be7a32b11a0957dcf8bddecfdfcd37e gossip-0.30.tar.gz
d36603e333f77dba51a6750dec036f8b gossip-0.30.tar.bz2

What is it?
===========
Gossip is an instant messaging client for GNOME with an easy-to-use
interface, providing users of the GNOME Desktop with a friendly way to
keep in touch with their friends.

Where can I find out more?
==========================
You can visit the project web site:
http://developer.imendio.com/wiki/Gossip

What's New?
===========

Gossip now depends on Loudmouth 1.3.4

Note: this has a TCP issue which means connections are sometimes dropped
on some routers, to fix this, compile Loudmouth by disabling TCP
stayalives. You can do this by editing the config.h file after
configuring the package and commenting out the USE_TCP_KEEPALIVES #define.

It is also recommended that the --with-asyncns switch is used when
building Loudmouth so there are no synchronous DNS lookups blocking the
user interface from drawing.

Also new is that group chat backend has been refactored to fix a number
of issues. This mostly affects private chat between contacts from chatrooms.

Bugs Fixed:
===========
- Fixed #347026, groupchat topic is changed local even though user have
not the permission (Martyn Russell)
- Fixed #350333, Uncorrect displaying of received private messages from
another groupchat participant (Martyn Russell)
- Fixed #435273, Usability issue: merge status submenu into task icon
menu (Martyn Russell)
- Fixed #522388, Add context menu to groupchat contact list (Igor
Stepura, Martyn Russell)
- Fixed #536683, Find entry behavior a little bit confusing (Martyn Russell)
- Fixed #541651, Contacts are offline if they go offline and come back
online (Martyn Russell)

Translations:
=============
- Updated ca: Jordi Mallach
- Updated cs: Petr Kovar
- Updated es: Jorge González, Jorge Gonzalez
- Updated nb: Sigurd Gartmann, Kjartan Maraas
- Updated sv: Daniel Nylander

Manual Translations:
====================
None

20 July 2008
Gossip team
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: Author and licence of wav files

2008-07-03T08:46:35Z

Hi,

> I'm searching the author and the licence of gossip/data/sounds/*.wav.
> Those files were added in the 2nd SVN commit with no special mention.
> Does someone has an idea?

If I remember correctly, they are from Psi (which is GPL). I think the
original gossip repo that was later moved to GNOME had the attribution
in the commit log. I thought we also had a note about it somewhere but
maybe not; we should add one if we don't.

Interestingly, they were supposed to be temporary to test the sound
support, but managed to stay in there for many years :)

/Richard

--
Imendio AB - Expert solutions in GTK+
http://www.imendio.com
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Author and licence of wav files

2008-07-03T07:36:27Z

Hello,

I'm searching the author and the licence of gossip/data/sounds/*.wav.
Those files were added in the 2nd SVN commit with no special mention.
Does someone has an idea?

Thanks,
Xavier Claessens.

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: Cant send message to people not in my roster

2008-06-04T01:33:42Z

Hi,

Am Mittwoch, den 04.06.2008, 09:48 +0200 schrieb Martyn Russell:
> Yea, actually, that's not a bad idea. Should be simple to do.
> Want to write the patch? :)

I am happy, when I managed to write a "hello world" in C...

Sorry :(

Regards,

Keywan

--
Keywan Najafi Tonekaboni
http://www.prometoys.net

people@world:/# apt-get --purge remove dominion
After unpacking world will be freed.
You are about to do something potentially beneficial
To continue type in the phrase 'Yes, do as We say!'

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: Cant send message to people not in my roster

2008-06-04T00:48:31Z

Keywan Najafi Tonekaboni wrote:

> Hi,
>
> Am Mittwoch, den 04.06.2008, 00:39 +0200 schrieb Martyn Russell:
>> It depends.
>>
>> Do you have multiple accounts set up? If so, is one definitely selected?
>
> No. Now I recognised the "Note"-label. Maybe the UI could somehow
> improved, sometimes users could be really blind.. I just paid attention
> for the inactive button and didn't care for the stuff at the upper parts
> of the dialog. What do you think about some kind of interactive note,
> like when you push Caps-Lock during GDM Login.

Yea, actually, that's not a bad idea. Should be simple to do.
Want to write the patch? :)

--
Regards,
Martyn
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: Cant send message to people not in my roster

2008-06-03T16:19:34Z

Hi,

Am Mittwoch, den 04.06.2008, 00:39 +0200 schrieb Martyn Russell:
> It depends.
>
> Do you have multiple accounts set up? If so, is one definitely selected?

No. Now I recognised the "Note"-label. Maybe the UI could somehow
improved, sometimes users could be really blind.. I just paid attention
for the inactive button and didn't care for the stuff at the upper parts
of the dialog. What do you think about some kind of interactive note,
like when you push Caps-Lock during GDM Login.

> If not, then it is a bug I think.
>
> It might well be a bug with trying to use a resource in the ID though.

This would be cool. Only checking node and host of the JID, but not the
resource. I don't think there are much cases where different resources
are added to different account, but this could be a pitfall.

Regards,

Keywan

--
Keywan Najafi Tonekaboni
http://www.prometoys.net

people@world:/# apt-get --purge remove dominion
After unpacking world will be freed.
You are about to do something potentially beneficial
To continue type in the phrase 'Yes, do as We say!'

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: Cant send message to people not in my roster

2008-06-03T15:39:32Z

Keywan Najafi Tonekaboni wrote:
> Hi,

Hi :)

> is this a bug or a "feature". I cant send message to people (or
> entities/resources) who are not in my roster/contact list. I use "New
> Message"/ Ctrl+N an typed a JID who is not in my roster (actually it was
> someone in my roster, but I want to write to a special resource.
> I use Gossip 0.28 on Ubuntu Hardy.

It depends.

Do you have multiple accounts set up? If so, is one definitely selected?
If not, then it is a bug I think.

It might well be a bug with trying to use a resource in the ID though.

--
Regards,
Martyn
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Cant send message to people not in my roster

2008-06-03T14:59:09Z

Hi,

is this a bug or a "feature". I cant send message to people (or
entities/resources) who are not in my roster/contact list. I use "New
Message"/ Ctrl+N an typed a JID who is not in my roster (actually it was
someone in my roster, but I want to write to a special resource.
I use Gossip 0.28 on Ubuntu Hardy.

If it's not intended I will file a bug.

Regards,

Keywan

--
Keywan Najafi Tonekaboni
http://www.prometoys.net

people@world:/# apt-get --purge remove dominion
After unpacking world will be freed.
You are about to do something potentially beneficial
To continue type in the phrase 'Yes, do as We say!'

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: TLS support?

2008-04-29T07:55:40Z

Martyn Russell wrote:

> Peter Saint-Andre wrote:
>> Hey guys, I know you're aware of the protocol for upgrading port 5222 to
>> an encrypted connection via STARTLS instead of using SSL on the old
>> legacy port 5223, but I'd like to put in a plug for that feature. We
>> recently have had some problems with support of 5223 at the jabber.org
>> service (and yes we're working to fix those), which prevented Gossip
>> users from logging in.
>
> Hi Peter,
>
> I have bumped the version requirement of Loudmouth to 1.3.4 in Gossip
> recently, I just need to release at some point. That should fix the
> problem hopefully!

Great!

> Thanks for notifying us about it.

No, thank you for coding STARTTLS support. :)

Peter

--
Peter Saint-Andre
https://stpeter.im/

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

smime.p7s (9K) Download Attachment

Re: TLS support?

2008-04-29T00:32:43Z

Peter Saint-Andre wrote:
> Hey guys, I know you're aware of the protocol for upgrading port 5222 to
> an encrypted connection via STARTLS instead of using SSL on the old
> legacy port 5223, but I'd like to put in a plug for that feature. We
> recently have had some problems with support of 5223 at the jabber.org
> service (and yes we're working to fix those), which prevented Gossip
> users from logging in.

Hi Peter,

I have bumped the version requirement of Loudmouth to 1.3.4 in Gossip
recently, I just need to release at some point. That should fix the
problem hopefully!

Thanks for notifying us about it.

--
Regards,
Martyn
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

TLS support?

2008-04-28T09:55:24Z

Hey guys, I know you're aware of the protocol for upgrading port 5222 to
an encrypted connection via STARTLS instead of using SSL on the old
legacy port 5223, but I'd like to put in a plug for that feature. We
recently have had some problems with support of 5223 at the jabber.org
service (and yes we're working to fix those), which prevented Gossip
users from logging in.

Thanks!

Peter

--
Peter Saint-Andre
https://stpeter.im/

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

smime.p7s (9K) Download Attachment

jabber client for audio/video chat

2008-02-29T04:19:07Z

Hello sir,

I am trying to get jabber client with audio/video chat.But unable to get.
There are some free(neos jabber client) but not open source.

I need free and opensource jabber cleint with audio/video chat.
Any one have download link for that.
Please help me

Any help appriciable.

Thanks
Ramj

Stepping down as co-maintainer

2008-02-24T06:26:13Z

Hi all,

While this will make little difference in practice I figured I should
officially step down as co-maintainer of Gossip. Bottom line is that I
do not have the time to work much on the project anymore.

I will instead try to get back on Loudmouth a bit more in order to
help it move forward faster (no promises though) which should benefit
Gossip as well.

Cheers,
Mikael Hallendal

--
Imendio AB, http://www.imendio.com

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: Russian translation

2008-02-04T04:00:01Z

Thanks for your response. I have sent it to gnome-l10n-ru team.

However I cannot understand why there are three sources for l10n:
developers, GNOME l10n team and Rosetta for Ubuntu... It seems quite
confusing to me... Oh well, never mind :)

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: Russian translation

2008-02-04T03:13:26Z

rubicon wrote:
> Please update Russian translation with this file (in attachment).

Hi, and thanks!

However, translations should be handled within the GNOME translation
project, otherwise there might be clashes when people work on the same
modules simultaneously. There might also be terminology and style
decisions within each language team that should be followed and so on.
So please contact the Russian team here:

http://l10n.gnome.org/

Regards,
Richard

--
Imendio AB, http://www.imendio.com/
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Russian translation

2008-02-04T03:03:27Z

Please update Russian translation with this file (in attachment).

I would like to say that the current version of ru-locale is, well,
crap. Thus I have translated all messages in Gossip from scratch.

Best regards.

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

po_gossip-ru.po.zip (25K) Download Attachment

Re: AIM/ICQ support?

2008-01-18T15:14:45Z

18 jan 2008 kl. 17.46 skrev Brian Pepple:

Hi,

> On Fri, 2008-01-18 at 17:40 +0100, Xavier Claessens wrote:
>> On ven, 2008-01-18 at 15:43 +0000, Martyn Russell wrote:
>>> Bastien Nocera wrote:
>>>
>>>> Has anyone managed to get the new AIM/ICQ gateway provided by AOL?
>>>> http://florianjensen.com/2008/01/17/aol-adopting-xmpp-aka-jabber/
>>>
>>> No I haven't tried it yet. This is indeed good news!
>>>
>>>> I couldn't get Gossip to connect to it. Using:
>>>> gossip-0.27-1.fc8
>>>> loudmouth-1.2.3-3.fc8
>>>
>>> Hmm, I wonder if it would work with loudmouth 1.3.3. It is much more
>>> XMPP compliant. I actually have an AIM/ICQ account from back in
>>> the day,
>>> I will try it some time soon.
>>
>> You have to connect using TLS encryption, so loudmouth 1.3.3 is
>> required
>> I think.
>
> Hmmm, probably a good reason for me to update loudmouth to 1.3.3 in
> Fedora Rawhide.

Yeah, while labelled as unstable it should be just as stable as 1.2
branch. I think it would make sense to use it for Gossip and start
making use of the new features in it.

// Micke

>
>
> /B
> --
> Brian Pepple <bpepple@...>
>
> http://fedoraproject.org/wiki/BrianPepple
> gpg --keyserver pgp.mit.edu --recv-keys 810CC15E
> BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E
> _______________________________________________
> Gossip-dev mailing list
> Gossip-dev@...
> http://lists.imendio.com/mailman/listinfo/gossip-dev

--
Imendio AB, http://www.imendio.com

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: AIM/ICQ support?

2008-01-18T08:46:51Z

On Fri, 2008-01-18 at 17:40 +0100, Xavier Claessens wrote:

> On ven, 2008-01-18 at 15:43 +0000, Martyn Russell wrote:
> > Bastien Nocera wrote:
> >
> > > Has anyone managed to get the new AIM/ICQ gateway provided by AOL?
> > > http://florianjensen.com/2008/01/17/aol-adopting-xmpp-aka-jabber/
> >
> > No I haven't tried it yet. This is indeed good news!
> >
> > > I couldn't get Gossip to connect to it. Using:
> > > gossip-0.27-1.fc8
> > > loudmouth-1.2.3-3.fc8
> >
> > Hmm, I wonder if it would work with loudmouth 1.3.3. It is much more
> > XMPP compliant. I actually have an AIM/ICQ account from back in the day,
> > I will try it some time soon.
>
> You have to connect using TLS encryption, so loudmouth 1.3.3 is required
> I think.

Hmmm, probably a good reason for me to update loudmouth to 1.3.3 in
Fedora Rawhide.

/B
--
Brian Pepple <bpepple@...>

http://fedoraproject.org/wiki/BrianPepple
gpg --keyserver pgp.mit.edu --recv-keys 810CC15E
BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

signature.asc (196 bytes) Download Attachment

Re: AIM/ICQ support?

2008-01-18T08:40:59Z

On ven, 2008-01-18 at 15:43 +0000, Martyn Russell wrote:

> Bastien Nocera wrote:
> > Heya,
>
> Hi Bastien.
>
> > Has anyone managed to get the new AIM/ICQ gateway provided by AOL?
> > http://florianjensen.com/2008/01/17/aol-adopting-xmpp-aka-jabber/
>
> No I haven't tried it yet. This is indeed good news!
>
> > I couldn't get Gossip to connect to it. Using:
> > gossip-0.27-1.fc8
> > loudmouth-1.2.3-3.fc8
>
> Hmm, I wonder if it would work with loudmouth 1.3.3. It is much more
> XMPP compliant. I actually have an AIM/ICQ account from back in the day,
> I will try it some time soon.

You have to connect using TLS encryption, so loudmouth 1.3.3 is required
I think.

Xavier Claessens.

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: AIM/ICQ support?

2008-01-18T07:43:27Z

Bastien Nocera wrote:
> Heya,

Hi Bastien.

> Has anyone managed to get the new AIM/ICQ gateway provided by AOL?
> http://florianjensen.com/2008/01/17/aol-adopting-xmpp-aka-jabber/

No I haven't tried it yet. This is indeed good news!

> I couldn't get Gossip to connect to it. Using:
> gossip-0.27-1.fc8
> loudmouth-1.2.3-3.fc8

Hmm, I wonder if it would work with loudmouth 1.3.3. It is much more
XMPP compliant. I actually have an AIM/ICQ account from back in the day,
I will try it some time soon.

--
Regards,
Martyn
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

AIM/ICQ support?

2008-01-18T07:13:25Z

Heya,

Has anyone managed to get the new AIM/ICQ gateway provided by AOL?
http://florianjensen.com/2008/01/17/aol-adopting-xmpp-aka-jabber/

I couldn't get Gossip to connect to it. Using:
gossip-0.27-1.fc8
loudmouth-1.2.3-3.fc8

Cheers

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

ANNOUNCE: Gossip 0.28 released

2007-11-10T06:36:59Z

Gossip 0.28 is now available for download from:
http://download.gnome.org/sources/gossip/0.28/

c4b53bcdac64e2ce6fb1b9525779d87a gossip-0.28.tar.gz
2c364a3fffec0fb57c71b6dbab6fa53a gossip-0.28.tar.bz2

What is it?
===========
Gossip is an instant messaging client for GNOME with an easy-to-use
interface, providing users of the GNOME Desktop with a friendly way to
keep in touch with their friends.

Where can I find out more?
==========================
You can visit the project web site:
http://developer.imendio.com/wiki/Gossip

Bugs Fixed
==========
- Fixed #371927, crash in Gossip Instant Messenger: Log in after
registration (Martyn Russell)
- Fixed #488455, crash in Gossip Instant Messenger: (Martyn Russell)
- Fixed #492285, Adding a contact doesn't work (Martyn Russell)
- Fixed #343513, Store password in gnome-keyring (Sam Morris, Martyn
Russell)
- Fixed #346291, Show all chatrooms in the chatroom window and support
filtering after (Martyn Russell)
- Fixed #470351, gossip 0.27 with galago (Martyn Russell)
- Fixed #471316, Crash in smooth scrolling code (Richard Hult)
- Fixed #473169, Translation contexts (Chat and Edit) (Stephane Raimbault)
- Fixed #475061, Log searching is broken (Martyn Russell)
- Fixed #475143, Add feature to kick users from group chats (Martyn Russell)
- Fixed #475882, Change "contact online" notifications (Alex Jones)
- Fixed #479630, Implement Drag & Drop on contact list for files (Alex
Jones)
- Fixed #493894, log search doesn't find things that it should (Sam Morris)

Translations:
=============
- Updated fr: Stéphane Raimbault
- Updated ca: Jordi Mallach
- Updated oc: Martyn Russell
- Updated sv: Daniel Nylander
- Updated hu: Gabor Kelemen
- Updated lt: Gintautas Miliauskas
- Updated eu: Inaki Larranaga Murgoitio
- Updated es: Jorge Gonzalez

Help Manual Translations:
=========================
None

10 November 2007
Gossip team
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: UTF8 encoding

2007-10-04T15:08:35Z

4 okt 2007 kl. 21.38 skrev Stéphane Raimbault:

Hi,

> 2007/10/4, Stéphane Raimbault <stephane.raimbault@...>:
>> Hi,
>>
>> I need to prepend POTFILES.in like this to run intltool-update fr !
>>
>> Index: POTFILES.in
>> ===================================================================
>> --- POTFILES.in (révision 2622)
>> +++ POTFILES.in (copie de travail)
>> @@ -1,6 +1,6 @@
>> # List of source files containing translatable strings.
>> # Please keep this file sorted alphabetically.
>> -
>> +[encoding: UTF-8]
>> gossip.desktop.in.in
>> gossip.schemas.in
>>
>> Can I commit this patch ?
>
> I commited because l10n.gnome.org raises an error too!

Thanks!

Cheers,
Micke

--
Imendio AB, http://www.imendio.com

_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: UTF8 encoding

2007-10-04T13:38:59Z

2007/10/4, Stéphane Raimbault <stephane.raimbault@...>:

> Hi,
>
> I need to prepend POTFILES.in like this to run intltool-update fr !
>
> Index: POTFILES.in
> ===================================================================
> --- POTFILES.in (révision 2622)
> +++ POTFILES.in (copie de travail)
> @@ -1,6 +1,6 @@
> # List of source files containing translatable strings.
> # Please keep this file sorted alphabetically.
> -
> +[encoding: UTF-8]
> gossip.desktop.in.in
> gossip.schemas.in
>
> Can I commit this patch ?

I commited because l10n.gnome.org raises an error too!

Stéphane
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

UTF8 encoding

2007-10-04T13:06:28Z

Hi,

I need to prepend POTFILES.in like this to run intltool-update fr !

Index: POTFILES.in
===================================================================
--- POTFILES.in (révision 2622)
+++ POTFILES.in (copie de travail)
@@ -1,6 +1,6 @@
# List of source files containing translatable strings.
# Please keep this file sorted alphabetically.
-
+[encoding: UTF-8]
gossip.desktop.in.in
gossip.schemas.in

Can I commit this patch ?

Regards,
Stéphane
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev

Re: Gossip patches

2007-09-01T02:55:27Z

Jordi Mallach wrote:

> Hey Martyn,
>
> I buggered you on jabber last night, I bugger you on mail now.
>
> I have tried compiling this, but I:
>
> - don't have anyone to make the birthday bit popup.
> - don't know of a server with just one conference room.
>
> So I guess I can't really test. :)

Thanks for the patch, I have committed it now ;)

--
Regards,
Martyn
_______________________________________________
Gossip-dev mailing list
Gossip-dev@...
http://lists.imendio.com/mailman/listinfo/gossip-dev