[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kopete-devel
Subject:    [kopete-devel] [Bug 133351] New: Duplicate JabberIDs unsupported,
From:       christopher () currie ! com
Date:       2006-08-31 21:26:13
Message-ID: 20060831232611.133351.christopher () currie ! com
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=133351         
           Summary: Duplicate JabberIDs unsupported, and cause kopete to
                    crash
           Product: kopete
           Version: unspecified
          Platform: RedHat RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kopete-devel kde org
        ReportedBy: christopher currie com


Version:            (using KDE KDE 3.5.3)
Installed from:    RedHat RPMs
Compiler:          GCC 3.2.3 
OS:                Linux

Use case: my company's corporate jabber server is migrating from one host/server app \
to another, and I want to be able to talk to both at the same time while people are \
still migrating. Since they both authenticate to the same LDAP, my JabberID has to be \
the same for both connections.

If I try to add a second Jabber account with the same JabberID, kopete will crash. \
Looking at the kopeterc file leads me to beleve that this would be unsupportable \
without some changes, but at the very least it shouldn't crash the app.

I've tried this with the stock KDE 3.5.3 kopete (0.11.3) and the latest release \
(0.12.2). _______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel


[prev in list] [next in list] [prev in thread] [next in thread]