Bug 68911 - Kopete crashes on Configure Kopete
Summary: Kopete crashes on Configure Kopete
Status: CLOSED NOT A BUG
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-24 01:48 UTC by Rob Kaper
Modified: 2003-11-24 22:34 UTC (History)
0 users

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 Rob Kaper 2003-11-24 01:48:02 UTC
Version:           0.7.93 (using KDE 3.1.93 (CVS >= 20031111), compiled sources)
Compiler:          gcc version 3.2
OS:          Linux (i686) release 2.4.19

Kopete crashes on opening Configure Kopete. The app had just started up, ICQ was already on-line and had been manually set to Offline, removing that plug-in was the reason I wanted to configure. MSN was still loading. I can reproduce this so I basically can't configure Kopete anymore. :-/

Backtrace:

0x41cbf989 in wait4 () from /lib/libc.so.6
#0  0x41cbf989 in wait4 () from /lib/libc.so.6
#1  0x41d3ed48 in sys_sigabbrev () from /lib/libc.so.6
#2  0x41ad7113 in waitpid () from /lib/libpthread.so.0
#3  0x410695d1 in KCrash::defaultCrashHandler(int) (sig=11) at kcrash.cpp:246
#4  0x41c3add8 in sigaction () from /lib/libc.so.6
#5  0x40e08922 in ~SButton (this=0x3c) at kdialogbase.cpp:86
#6  0x40e08868 in ~KDialogBasePrivate (this=0x20) at kdialogbase.cpp:216
#7  0x40e01906 in ~KDialogBase (this=0x8265cf0) at kdialogbase.cpp:216
#8  0x08090fc0 in ~KopetePluginConfig (this=0x8265cf0)
    at kopetepluginconfig.moc:28
#9  0x408d7c24 in createInstanceFromFactory<KCModule> (factory=0x82657e8, 
    parent=0x8264ab0, name=0x41842382 "unnamed", args=@0x8264be8)
    at ../kparts/componentfactory.h:68
#10 0x408d7385 in KCModuleLoader::load(KCModuleInfo const&, QString const&, KLibLoader*, QWidget*, char const*, QStringList const&) (mod=@0x8264bf0, 
    libname=@0xbfffe960, loader=0x81ecb30, parent=0x8264ab0, 
    name=0x41842382 "unnamed", args=@0x8264be8) at kcmoduleloader.cpp:49
#11 0x408d7636 in KCModuleLoader::loadModule(KCModuleInfo const&, bool, QWidget*, char const*, QStringList const&) (mod=@0x8264bf0, withfallback=false, 
    parent=0x8264ab0, name=0x41842382 "unnamed", args=@0x8264be8)
    at kcmoduleloader.cpp:89
#12 0x408e5906 in KCModuleProxy::realModule() const (this=0x8264ab0)
    at kcmoduleproxy.cpp:134
#13 0x408e56de in KCModuleProxy::buttons() const (this=0x8264ab0)
    at kcmoduleproxy.cpp:103
#14 0x408da4e5 in KCMultiDialog::slotAboutToShow(QWidget*) (this=0x823f868, 
    page=0x8263618) at kcmultidialog.cpp:316
#15 0x408d8005 in KCMultiDialog::qt_invoke(int, QUObject*) (this=0x823f868, 
    _id=89, _o=0xbfffeb10) at kcmultidialog.moc:136
#16 0x414b8203 in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x823f868, clist=0x82160b0, o=0xbfffeb10) at kernel/qobject.cpp:2333
#17 0x40e07257 in KDialogBase::aboutToShowPage(QWidget*) (this=0x823f868, 
    t0=0x8263618) at kdialogbase.moc:333
#18 0x408da04b in KCMultiDialog::addModule(KCModuleInfo const&, QStringList, bool) (this=0x823f868, moduleinfo=@0x8252250, parentmodulenames=
        {<QValueList<QString>> = {sh = 0x8263258}, <No data fields>}, 
    withfallback=false) at kcmultidialog.cpp:258
#19 0x408f406e in KSettings::PageNode::addToDialog(KCMultiDialog*) (
    this=0x81ef880, dlg=0x823f868) at dialog.cpp:216
#20 0x408f420b in KSettings::PageNode::addToDialog(KCMultiDialog*) (
    this=0x82280b8, dlg=0x823f868) at dialog.cpp:233
#21 0x408f25cd in KSettings::Dialog::createDialogFromServices() (
    this=0x822b7d0) at dialog.cpp:600
#22 0x408f1332 in KSettings::Dialog::show() (this=0x822b7d0) at dialog.cpp:416
#23 0x400e1e5c in KopetePreferencesAction::slotShowPreferences() (
    this=0x8195f48) at kopetestdaction.cpp:105
#24 0x400e2a14 in KopetePreferencesAction::qt_invoke(int, QUObject*) (
    this=0x8195f48, _id=15, _o=0xbfffef30) at kopetestdaction.moc:164
#25 0x414b8203 in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x8195f48, clist=0x8196020, o=0xbfffef30) at kernel/qobject.cpp:2333
#26 0x414b80a2 in QObject::activate_signal(int) (this=0x8195f48, signal=2)
    at kernel/qobject.cpp:2302
#27 0x40d6fb6e in KAction::activated() (this=0x8195f48) at kaction.moc:157
#28 0x40d6f548 in KAction::slotActivated() (this=0x8195f48) at kaction.cpp:1054
#29 0x40d6fe64 in KAction::qt_invoke(int, QUObject*) (this=0x8195f48, _id=14, 
    _o=0xbffff060) at kaction.moc:181
#30 0x400e2a2a in KopetePreferencesAction::qt_invoke(int, QUObject*) (
    this=0x8195f48, _id=14, _o=0xbffff060) at kopetestdaction.moc:166
#31 0x414b8203 in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x81a83d8, clist=0x81d3f98, o=0xbffff060) at kernel/qobject.cpp:2333
#32 0x417f0732 in QSignal::signal(QVariant const&) (this=0x81a83d8, 
    t0=@0x81a8400) at .moc/debug-shared-mt/moc_qsignal.cpp:100
#33 0x414d51d5 in QSignal::activate() (this=0x81a83d8)
    at kernel/qsignal.cpp:204
#34 0x415c9602 in QPopupMenu::mouseReleaseEvent(QMouseEvent*) (this=0x81be028, 
    e=0xbffff460) at widgets/qpopupmenu.cpp:1672
#35 0x414ef3a3 in QWidget::event(QEvent*) (this=0x81be028, e=0xbffff460)
    at kernel/qwidget.cpp:4419
#36 0x41455a2f in QApplication::internalNotify(QObject*, QEvent*) (
    this=0xbffff860, receiver=0x81be028, e=0xbffff460)
    at kernel/qapplication.cpp:2582
#37 0x414551f3 in QApplication::notify(QObject*, QEvent*) (this=0xbffff860, 
    receiver=0x81be028, e=0xbffff460) at kernel/qapplication.cpp:2368
#38 0x40fda440 in KApplication::notify(QObject*, QEvent*) (this=0xbffff860, 
    receiver=0x81be028, event=0xbffff460) at kapplication.cpp:509
#39 0x413ed2af in QApplication::sendSpontaneousEvent(QObject*, QEvent*) (
    receiver=0x81be028, event=0xbffff460) at kernel/qapplication.h:493
#40 0x413e691a in QETWidget::translateMouseEvent(_XEvent const*) (
    this=0x81be028, event=0xbffff750) at kernel/qapplication_x11.cpp:4291
#41 0x413e48bb in QApplication::x11ProcessEvent(_XEvent*) (this=0xbffff860, 
    event=0xbffff750) at kernel/qapplication_x11.cpp:3525
#42 0x413fe352 in QEventLoop::processEvents(unsigned) (this=0x8128620, flags=4)
    at kernel/qeventloop_x11.cpp:192
#43 0x4146b17e in QEventLoop::enterLoop() (this=0x8128620)
    at kernel/qeventloop.cpp:198
#44 0x4146b09a in QEventLoop::exec() (this=0x8128620)
    at kernel/qeventloop.cpp:145
#45 0x41455ba9 in QApplication::exec() (this=0xbffff860)
    at kernel/qapplication.cpp:2705
#46 0x08065df9 in main (argc=7, argv=0xbffff9f4) at main.cpp:95
#47 0x41c26fa4 in __libc_start_main () from /lib/libc.so.6
Comment 1 Tais P. Hansen 2003-11-24 02:06:43 UTC
You may have outdated Kopete kcm files and/or plugins in /opt/kde/lib/kde3.

Try

ls -l /opt/kde/lib/kde3/kcm_kopete_*
ls -l /opt/kde/lib/kde3/kopete_*

and check the dates of the files. Remove those who hasn't been updated at the last make install.
Comment 2 Martijn Klingens 2003-11-24 11:03:43 UTC
Notably PluginConfig, which is indeed gone since just prior to KDE 3.2 beta 1. And no, there won't be a kconf_update for it, there has never been a release which included this KCM, only CVS users are affected :)

Martijn
Comment 3 Rob Kaper 2003-11-24 21:47:57 UTC
Subject: Re:  Kopete crashes on Configure Kopete

On Mon, Nov 24, 2003 at 10:03:47AM -0000, Martijn Klingens wrote:
> Notably PluginConfig, which is indeed gone since just prior to KDE 3.2
> beta 1. And no, there won't be a kconf_update for it, there has never been
> a release which included this KCM, only CVS users are affected :)

Removed the old stuff, recompiled Kopete, and now Kopete indeed started
complaining about missing libs or old modules. (after I removed them!)

A very careful

find /usr/local/kde -name *kopete* -exec rm -rvf {} \;

and cvs-clean compile of Kopete fixed it.

This is not the first time this happened though, and it seems to occur
frequently enough to even warn about it in a widget, are you sure this can't
be prevented with some kconf_update magic?

CVS users are just as important, no? ;-(

Rob
Comment 4 Stefan Gehn 2003-11-24 22:34:33 UTC
> CVS users are just as important, no? ;-( 
They are important but they have to keep uptodate with changes like this. Or do you get warned everytime something BIC gets comitted to kdelibs?

> are you sure this can't be prevented with some kconf_update magic? 
Since when does kconf_update have root rights and remove outdated files from your kde install dir?