Bug 142976 - crash when creating two accounts with the same name
Summary: crash when creating two accounts with the same name
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: Main Application (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-14 19:45 UTC by Thomas Schildknecht
Modified: 2008-07-10 05:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Schildknecht 2007-03-14 19:45:48 UTC
Version:           0.12.2 (using KDE 3.5.6, Kubuntu (edgy) 4:3.5.6-0ubuntu1~edgy1)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.17-11-generic

Kopete crash when one create two accounts with the same name (not useful I know, but anyway, it crash)

Steps to reproduce:
1. Create one account (I tested with MSN and Gadu-gadu)
2. Create a second account of the same type and with the same msn-email/gadugadu-ID...
3. enjoy

(there is no need to be connected to these accounts)

Voilà, thx for this nice piece of software :)
Comment 1 Bram Schoenmakers 2007-03-14 22:35:23 UTC
Do you have a backtrace of the crash? (Please install kdelibs-dbg and kdenetwork-dbg before you create one).
Comment 2 Thomas Schildknecht 2007-03-14 23:19:01 UTC
Here is a crash that occured when I created two msn accounts with the same name
==========================================================================
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1240521040 (LWP 16937)]
[KCrash handler]
#6  0xb6fdcc03 in KConfigBase::writeEntry (this=0x39, 
    pKey=0xb7f412b2 "ExcludeConnect", value=@0xbf80f548, bPersistent=true, 
    bGlobal=false, bNLS=false)
    at /root/kdelibs/kdelibs-3.5.6/./kdecore/kconfigbase.cpp:1031
#7  0xb6fdcfe0 in KConfigBase::writeEntry (this=0x39, 
    pKey=0xb7f412b2 "ExcludeConnect", bValue=false, bPersistent=true, 
    bGlobal=false, bNLS=false)
    at /root/kdelibs/kdelibs-3.5.6/./kdecore/kconfigbase.cpp:1536
#8  0xb7ec9e63 in Kopete::Account::setExcludeConnect ()
   from /usr/lib/libkopete.so.1
#9  0xb5b4431f in MSNEditAccountWidget::apply ()
   from /usr/lib/libkopete_msn_shared.so.0
#10 0x08086aac in AddAccountWizard::accept ()
#11 0xb6cbbec6 in QDialog::qt_invoke () from /usr/lib/libqt-mt.so.3
#12 0xb6cc03f1 in QWizard::qt_invoke () from /usr/lib/libqt-mt.so.3
#13 0xb723cdbb in KWizard::qt_invoke (this=0x8c04c80, _id=48, _o=0xbf80f81c)
    at ./kwizard.moc:77
#14 0x08086303 in AddAccountWizard::qt_invoke ()
#15 0xb6900957 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0xb69013fc in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb6c95f5f in QButton::clicked () from /usr/lib/libqt-mt.so.3
#18 0xb699efe8 in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
#19 0xb6937729 in QWidget::event () from /usr/lib/libqt-mt.so.3
#20 0xb6897b88 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#21 0xb6899d46 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#22 0xb7028c82 in KApplication::notify (this=0xbf810234, receiver=0x850b618, 
    event=0xbf80fc90)
    at /root/kdelibs/kdelibs-3.5.6/./kdecore/kapplication.cpp:550
#23 0xb682a3fd in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#24 0xb6829062 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#25 0xb682714c in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#26 0xb683e320 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#27 0xb68b225e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#28 0xb68b206e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#29 0xb6899731 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#30 0x0806e0bc in main ()
Comment 3 Matt Rogers 2007-09-12 05:30:31 UTC
I know why this happens and will look at fixing it.
Comment 4 Ruud Koolen 2008-07-07 16:08:24 UTC
Seems fixed in kde4 (Kopete 0.50.80).
Comment 5 Thomas Schildknecht 2008-07-07 16:20:17 UTC
I'm the reporter of this bug. I tested with Kopete from "KDE 4.00.85 (KDE 4.0.85 (KDE 4.1 >= 20080703))" and I can't reproduce the crash. 

However, there is no feedback when the user wants to create a second account with the same ID, the account is simply not created without any warning (don't know if this is important but well...)
Comment 6 Matt Rogers 2008-07-10 05:49:07 UTC
Let's close this bug then, since the crash is gone.

If you could open another bug about there being no message when attempting to 
create an account with the same ID, that would be great. Thanks in advance!