Summary: | kopete not connecting to gmail/google talk id | ||
---|---|---|---|
Product: | [Applications] kopete | Reporter: | Unknown <null> |
Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | CLOSED NOT A BUG | ||
Severity: | normal | CC: | islam.alshaikh.news, mi+kde, spectrumdt, tejasdinkar |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Unknown
2009-02-20 23:20:00 UTC
Well, if you have installed all the plugins properly, (qca-tls, and qca2) the only mistake I can see offhand is that the server should actually be: "talk.google.com" not "gmail.com" or "google.com", port should be 5223, with "SSL", and allow "plain text authentication" checked. Further, your username should be your full emailaddress "xyz@gmail.com". If you have followed all these steps. Please respond with more information such as any output when running kopete from the konsole, or a backtrace if possible. "talk.google.com" fixed the it.. Thanks a lot... But the default server entry listed in the Connection tab of Account settings page is "gmail.com" which was kind of confusing. It should be "talk.google.com" for gtalk ids !! NOTABUG I had the same problem. Tejas Dinkar's advice above fixed it. Apparently the problem is that Kopete uses wrong settings by default when you add a Gmail account. It should use "talk.google.com" and 5223 and SSL (as Tejas Dinkar said) by default when adding a Gmail account. This counts as a Kopete bug in my book. Hi This is not invalid , but you can call it a bug in adding wizard Long time for fixing this problem by training & training without any good result , just I give up after around 6 months , I coming here to make it as a bug. this info. was fix it , so, kopete must fix add account wizard for google talk to make default as above (ssl, talk.google.com) please fix default settings of gmail accounts Thanks all I have the same problem and it certainly IS a bug. An application should never CRASH -- if the user-supplied settings are incorrect (talk.google.com vs. gmail.com, for example), then the nice GUI message should inform them of it... FWIW, the crash is in: #0 0x000000080422152c in strcmp () from /lib/libc.so.7 #1 0x0000000807c8c983 in OBJ_NAME_new_index () from /lib/libcrypto.so.4 #2 0x0000000807cb21d0 in lh_free () from /lib/libcrypto.so.4 #3 0x0000000807cb24e3 in lh_insert () from /lib/libcrypto.so.4 #4 0x0000000807c8cb49 in OBJ_NAME_add () from /lib/libcrypto.so.4 #5 0x000000080f96508c in ?? () #6 0x0000000802048a00 in q_SSL_load_error_strings () from /opt/lib/qt4/libQtNetwork.so.4 #7 0x000000080204541c in QSslSocketPrivate::ensureInitialized () from /opt/lib/qt4/libQtNetwork.so.4 #8 0x0000000802038c4f in QSslCertificate::QSslCertificate () from /opt/lib/qt4/libQtNetwork.so.4 #9 0x000000080204352b in QSslSocketPrivate::QSslSocketPrivate () from /opt/lib/qt4/libQtNetwork.so.4 #10 0x0000000802046b89 in QSslSocketBackendPrivate::QSslSocketBackendPrivate () from /opt/lib/qt4/libQtNetwork.so.4 #11 0x0000000802041d4e in QSslSocket::QSslSocket () from /opt/lib/qt4/libQtNetwork.so.4 #12 0x0000000802a096a1 in KSocketFactory::connectToHost () from /opt/kde4/lib/libkdecore.so.7 #13 0x000000080e9be55b in JabberByteStream::connect () from /opt/kde4/lib/kde4/kopete_jabber.so #14 0x000000080e9be07a in JabberConnector::connectToServer () ... |