Bug 250072 - systemsettings crashed after clicking on Login Screen
Summary: systemsettings crashed after clicking on Login Screen
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: System Settings Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-03 20:24 UTC by Andrew Elian
Modified: 2010-09-05 02:01 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 Andrew Elian 2010-09-03 20:24:05 UTC
Application: kcmshell4 ()
KDE Platform Version: 4.5.1 (KDE 4.5.1) (Compiled from sources)
Qt Version: 4.6.3
Operating System: Linux 2.6.27.4 x86_64

-- Information about the crash:
While using systemsettings, a crash occurs after clicking on Login Screen or Date & Time

Running 'kcmshell4 kdm' or 'kcmshell4 clock' in an xterm results in:

ASSERT failure in QList<T>::operator[]: "index out of range", file /opt/qt-4.6.3/include/QtCore/qlist.h, line 447
KCrash: Application 'kcmshell4' crashing...

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Control Module (kcmshell4), signal: Aborted
[KCrash Handler]
#6  0x0000003a65032a1b in raise () from /lib/libc.so.6
#7  0x0000003a6503441a in abort () from /lib/libc.so.6
#8  0x00007f48c9b3c20d in qt_message_output (msgType=QtFatalMsg, buf=<value optimized out>) at global/qglobal.cpp:2266
#9  0x00007f48c9b3c3ad in qt_message (msgType=QtFatalMsg, msg=0x7f48c9c97ef8 "ASSERT failure in %s: \"%s\", file %s, line %d", ap=0x7fffd2f34710) at global/qglobal.cpp:2312
#10 0x00007f48c9b3c565 in qFatal (msg=<value optimized out>) at global/qglobal.cpp:2495
#11 0x00007f48b47201b0 in PolkitQt1::Authority::Private::init() () from /usr/local/lib/libpolkit-qt-core-1.so.0
#12 0x00007f48b4721a6a in PolkitQt1::Authority::Authority(_PolkitAuthority*, QObject*) () from /usr/local/lib/libpolkit-qt-core-1.so.0
#13 0x00007f48b4721b32 in PolkitQt1::Authority::instance(_PolkitAuthority*) () from /usr/local/lib/libpolkit-qt-core-1.so.0
#14 0x00007f48b492fcfb in Polkit1Backend (this=0x18f4c60) at /mnt/build/KDE/kdelibs-4.5.1/kdecore/auth/backends/polkit-1/Polkit1Backend.cpp:62
#15 0x00007f48b492fddd in qt_plugin_instance () at /mnt/build/KDE/kdelibs-4.5.1/kdecore/auth/backends/polkit-1/Polkit1Backend.cpp:183
#16 0x00007f48ca32f6be in KAuth::BackendsManager::retrieveInstancesIn (path=<value optimized out>) at /mnt/build/KDE/kdelibs-4.5.1/kdecore/auth/BackendsManager.cpp:69
#17 0x00007f48ca32f8c0 in KAuth::BackendsManager::init () at /mnt/build/KDE/kdelibs-4.5.1/kdecore/auth/BackendsManager.cpp:81
#18 0x00007f48ca32fc4d in KAuth::BackendsManager::authBackend () at /mnt/build/KDE/kdelibs-4.5.1/kdecore/auth/BackendsManager.cpp:123
#19 0x00007f48ca32c236 in KAuth::Action::setName (this=0x18f3e80, name=...) at /mnt/build/KDE/kdelibs-4.5.1/kdecore/auth/kauthaction.cpp:108
#20 0x00007f48ca32c4b3 in Action (this=0x18f3e80, name=...) at /mnt/build/KDE/kdelibs-4.5.1/kdecore/auth/kauthaction.cpp:61
#21 0x00007f48ca98cae0 in KCModule::setNeedsAuthorization (this=0x1722fa0, needsAuth=<value optimized out>) at /mnt/build/KDE/kdelibs-4.5.1/kdeui/widgets/kcmodule.cpp:141
#22 0x00007f48bd4c0fd5 in KDModule (this=0x1722fa0, parent=<value optimized out>) at /mnt/build/KDE/kdebase-workspace-4.5.1/kcontrol/kdm/main.cpp:275
#23 0x00007f48bd4c2525 in KPluginFactory::createInstance<KDModule, QWidget> (parentWidget=<value optimized out>, parent=<value optimized out>, args=...) at /usr/local/include/kpluginfactory.h:461
#24 0x00007f48ca3f5562 in KPluginFactory::create (this=0x171a7c0, iface=0x7f48caa5f2c0 "KCModule", parentWidget=0x0, parent=0x1725670, args=..., keyword=...)
    at /mnt/build/KDE/kdelibs-4.5.1/kdecore/util/kpluginfactory.cpp:191
#25 0x00007f48cad10ed4 in KPluginFactory::create<KCModule> (mod=..., report=KCModuleLoader::Inline, parent=0x1725670, args=...) at /mnt/build/KDE/kdelibs-4.5.1/kdecore/util/kpluginfactory.h:515
#26 KService::createInstance<KCModule> (mod=..., report=KCModuleLoader::Inline, parent=0x1725670, args=...) at /mnt/build/KDE/kdelibs-4.5.1/kdecore/services/kservice.h:532
#27 KService::createInstance<KCModule> (mod=..., report=KCModuleLoader::Inline, parent=0x1725670, args=...) at /mnt/build/KDE/kdelibs-4.5.1/kdecore/services/kservice.h:509
#28 KService::createInstance<KCModule> (mod=..., report=KCModuleLoader::Inline, parent=0x1725670, args=...) at /mnt/build/KDE/kdelibs-4.5.1/kdecore/services/kservice.h:552
#29 KCModuleLoader::loadModule (mod=..., report=KCModuleLoader::Inline, parent=0x1725670, args=...) at /mnt/build/KDE/kdelibs-4.5.1/kutils/kcmoduleloader.cpp:89
#30 0x00007f48cad15b39 in KCModuleProxyPrivate::loadModule (this=0x171cd10) at /mnt/build/KDE/kdelibs-4.5.1/kutils/kcmoduleproxy.cpp:106
#31 0x00007f48cad16685 in KCModuleProxy::realModule (this=<value optimized out>) at /mnt/build/KDE/kdelibs-4.5.1/kutils/kcmoduleproxy.cpp:83
#32 0x00007f48cad166f9 in KCModuleProxy::useRootOnlyMessage (this=0x4191) at /mnt/build/KDE/kdelibs-4.5.1/kutils/kcmoduleproxy.cpp:315
#33 0x00007f48cad12fbf in KCMultiDialog::addModule (this=0x16e5550, moduleInfo=..., parentItem=0x0, args=...) at /mnt/build/KDE/kdelibs-4.5.1/kutils/kcmultidialog.cpp:339
#34 0x0000003a6e60790c in kdemain (_argc=<value optimized out>, _argv=<value optimized out>) at /mnt/build/KDE/kdebase-runtime-4.5.0/kcmshell/main.cpp:278
#35 0x0000003a6501e3f6 in __libc_start_main () from /lib/libc.so.6
#36 0x00000000004006c9 in _start ()

Reported using DrKonqi
Comment 1 Christoph Feck 2010-09-04 03:17:34 UTC
What did cmake log say which Auth backend kdelibs was building?
Comment 2 Andrew Elian 2010-09-04 19:57:33 UTC
KDE4_AUTH_BACKEND_NAME:STRING=POLKITQT-1

cmake finds polkitqt-1 for the Auth backend.

Which lead me to wonder if there was something not quite
right with the polkit install I have. After doing more
googling and pondering, I discovered that polkit seems to
have a runtime dependancy on ConsoleKit. After installing
ConsoleKit and adding the line /usr/bin/ck-launch-session startkde
to ~/.xinitrc, systemsettings works as expected. :)
Comment 3 Christoph Feck 2010-09-05 02:01:35 UTC
Thanks for the update.