Bug 162758 - does not find jabber server (ignores SRV records)
Summary: does not find jabber server (ignores SRV records)
Status: RESOLVED DUPLICATE of bug 133097
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: 0.12.7
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-28 18:00 UTC by hadmut
Modified: 2008-07-11 04:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hadmut 2008-05-28 18:00:13 UTC
Version:           0.12.7 (using KDE 3.5.9)
Installed from:    Ubuntu Packages

Hi,

for some reason kopete does not find and contact the jabber daemon. 

As far as I can see it does not even query any DNS SRV record. So this might be related to the old bug #133097. 

However, I do not see what exactly is the reason for kopete to not query SRV record, whether this has not yet been implemented or whether there is any other problem. 

Querying SRV records is fundamental for Jabber. I do not see how kopete could claim to offer jabber functionality if it is not able to find the server. 

regards
Comment 1 Stef Louwers 2008-07-07 20:19:35 UTC
This indeed seems like an duplicate of bug #133097

Seems still valid for kde4 kopete 0.50.1 (I had to enter talk.google.com to use the gmail jabber service).
Comment 2 Matt Rogers 2008-07-10 06:28:45 UTC

*** This bug has been marked as a duplicate of 133907 ***
Comment 3 Tommaso Schiavinotto 2008-07-10 08:00:21 UTC
I think there is an error, bug 133987 is a digikam bug...

Comment 4 Tommaso Schiavinotto 2008-07-10 15:52:49 UTC
I'm sorry ignore my previous comment, what I meant is: bug #133907 is a digikam bug, the one of which this bug should be duplicated is #133097
Comment 5 Matt Rogers 2008-07-11 04:28:25 UTC
reopening to mark as a duplicate of 133097
Comment 6 Matt Rogers 2008-07-11 04:32:59 UTC

*** This bug has been marked as a duplicate of 133097 ***