Bug 133351

Summary: Duplicate JabberIDs unsupported, and cause kopete to crash
Product: [Unmaintained] kopete Reporter: christopher
Component: Jabber PluginAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: RedHat Enterprise Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description christopher 2006-08-31 23:26:12 UTC 
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).
Comment 1 Matt Rogers 2006-11-10 06:26:38 UTC 
When I created the second account with the same settings as the first, I had to click the 'Finish' button twice. On the second click is when I get the crash.

Backtrace:
#0  0xb60ae54f in __dynamic_cast () from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libstdc++.so.6
#1  0xb5839f2c in JabberEditAccountWidget::account () from /home/kde/installs/3.5/lib/kde3/kopete_jabber.so
#2  0xb583a9e8 in JabberEditAccountWidget::apply () from /home/kde/installs/3.5/lib/kde3/kopete_jabber.so
#3  0x08086e3c in AddAccountWizard::accept ()
#4  0xb6b6eb9e in QDialog::qt_invoke (this=0x82c0948, _id=47, _o=0xbf8b517c)
    at .moc/debug-shared-mt/moc_qdialog.cpp:108
#5  0xb6b735fb in QWizard::qt_invoke (this=0x82c0948, _id=47, _o=0xbf8b517c)
    at .moc/debug-shared-mt/moc_qwizard.cpp:152
#6  0xb7344c0b in KWizard::qt_invoke () from /home/kde/installs/3.5/lib/libkdeui.so.4
#7  0x08086693 in AddAccountWizard::qt_invoke ()
#8  0xb67430b3 in QObject::activate_signal (this=0x82bd1b8, clist=0x82b2d08, o=0xbf8b517c) at kernel/qobject.cpp:2356
#9  0xb6743e4c in QObject::activate_signal (this=0x82bd1b8, signal=4) at kernel/qobject.cpp:2325
#10 0xb6b46613 in QButton::clicked (this=0x82bd1b8) at .moc/debug-shared-mt/moc_qbutton.cpp:152
#11 0xb67f7b0c in QButton::mouseReleaseEvent (this=0x82bd1b8, e=0xbf8b5594) at widgets/qbutton.cpp:836
#12 0xb6783d77 in QWidget::event (this=0x82bd1b8, e=0xbf8b5594) at kernel/qwidget.cpp:4677
#13 0xb66ceb77 in QApplication::internalNotify (this=0xbf8b5bdc, receiver=0x82bd1b8, e=0xbf8b5594)
    at kernel/qapplication.cpp:2635
#14 0xb66d0e63 in QApplication::notify (this=0xbf8b5bdc, receiver=0x82bd1b8, e=0xbf8b5594)
    at kernel/qapplication.cpp:2421
#15 0xb6f069be in KApplication::notify () from /home/kde/installs/3.5/lib/libkdecore.so.4
#16 0xb665795b in QApplication::sendSpontaneousEvent (receiver=0x82bd1b8, event=0xbf8b5594)
    at kernel/qapplication.h:499
#17 0xb66565bc in QETWidget::translateMouseEvent (this=0x82bd1b8, event=0xbf8b5a38) at kernel/qapplication_x11.cpp:4297
#18 0xb665475f in QApplication::x11ProcessEvent (this=0xbf8b5bdc, event=0xbf8b5a38) at kernel/qapplication_x11.cpp:3448
#19 0xb666d372 in QEventLoop::processEvents (this=0x815b110, flags=4) at kernel/qeventloop_x11.cpp:192
#20 0xb66ec7f1 in QEventLoop::enterLoop (this=0x815b110) at kernel/qeventloop.cpp:198
#21 0xb66ec612 in QEventLoop::exec (this=0x815b110) at kernel/qeventloop.cpp:145
#22 0xb66d083b in QApplication::exec (this=0xbf8b5bdc) at kernel/qapplication.cpp:2758
#23 0x0806e140 in main ()
Comment 2 Pino Toscano 2007-04-18 13:32:22 UTC 

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