[kde-freebsd] mystery crash of a KDE4-service

[Tijl Coosemans]

On Monday 26 July 2010 19:12:16 Mikhail T. wrote:
> One of the users complained of a new problem, that started last week
> for them. A minute or two after logging in and starting a
> KDE4-session, they get Dr. Konqi's crash-notification. The crashing
> application is identified only as "Service KDE (kdeinit4)" (in
> Russian):
> 
>     Application: Служба KDE (kdeinit4), signal: Segmentation fault: 11
>     [KCrash Handler]
>     #6  0x29171810 in QVariant::QVariant () from /opt/lib/qt4/libQtCore.so.4
>     #7  0x28fa6eb9 in QDBusPendingReplyData::argumentAt () from
>     /opt/lib/qt4/libQtDBus.so.4
>     #8  0x2a1c659e in Solid::Networking::notifier () from
>     /opt/kde4/lib/libsolid.so.5
>     #9  0x2a1c4d97 in Solid::PowerManagement::appShouldConserveResources
>     () from /opt/kde4/lib/libsolid.so.5
>     #10 0x2a1c5252 in Solid::PowerManagement::appShouldConserveResources
>     () from /opt/kde4/lib/libsolid.so.5
>     #11 0x2a1c5a87 in Solid::Networking::status () from
>     /opt/kde4/lib/libsolid.so.5
>     #12 0x30e2e427 in KPackageKitD::systemIsReady () from
>     /opt/kde4/lib/kde4/kded_kpackagekitd.so
>     #13 0x30e2eedf in KPackageKitD::update () from
>     /opt/kde4/lib/kde4/kded_kpackagekitd.so
>     #14 0x30e3088b in KPackageKitD::init () from
>     /opt/kde4/lib/kde4/kded_kpackagekitd.so
>     #15 0x30e2e2a1 in KPackageKitD::qt_metacall () from
>     /opt/kde4/lib/kde4/kded_kpackagekitd.so
>     #16 0x29156a83 in QMetaObject::metacall () from
>     /opt/lib/qt4/libQtCore.so.4
>     #17 0x29163c37 in QMetaObject::activate () from
>     /opt/lib/qt4/libQtCore.so.4
>     #18 0x291bc107 in QTimer::timeout () from /opt/lib/qt4/libQtCore.so.4
>     #19 0x2916d1fe in QTimer::timerEvent () from /opt/lib/qt4/libQtCore.so.4
>     #20 0x29161c3a in QObject::event () from /opt/lib/qt4/libQtCore.so.4
>     #21 0x294a835c in QApplicationPrivate::notify_helper () from
>     /opt/lib/qt4/libQtGui.so.4
>     #22 0x294af44d in QApplication::notify () from
>     /opt/lib/qt4/libQtGui.so.4
>     #23 0x28c78eb3 in KApplication::notify () from
>     /opt/kde4/lib/libkdeui.so.7
>     #24 0x291507ab in QCoreApplication::notifyInternal () from
>     /opt/lib/qt4/libQtCore.so.4
>     #25 0x291803c4 in QTimerInfoList::activateTimers () from
>     /opt/lib/qt4/libQtCore.so.4
>     #26 0x2917dd44 in timerSourceDispatch () from
>     /opt/lib/qt4/libQtCore.so.4
>     #27 0x2917dd74 in idleTimerSourceDispatch () from
>     /opt/lib/qt4/libQtCore.so.4
>     #28 0x2a2de977 in g_main_context_dispatch () from
>     /opt/lib/libglib-2.0.so.0
>     #29 0x2a2e21ce in g_main_context_check () from /opt/lib/libglib-2.0.so.0
>     #30 0x2a2e27f5 in g_main_context_iteration () from
>     /opt/lib/libglib-2.0.so.0
>     #31 0x2917e1bb in QEventDispatcherGlib::processEvents () from
>     /opt/lib/qt4/libQtCore.so.4
>     #32 0x295619c5 in QGuiEventDispatcherGlib::processEvents () from
>     /opt/lib/qt4/libQtGui.so.4
>     #33 0x2914f7a3 in QEventLoop::processEvents () from
>     /opt/lib/qt4/libQtCore.so.4
>     #34 0x2914fb1a in QEventLoop::exec () from /opt/lib/qt4/libQtCore.so.4
>     #35 0x29151f96 in QCoreApplication::exec () from
>     /opt/lib/qt4/libQtCore.so.4
>     #36 0x294a7b37 in QApplication::exec () from /opt/lib/qt4/libQtGui.so.4
>     #37 0x2b7dac73 in kdemain () from /opt/kde4/lib/libkdeinit4_kded4.so
>     #38 0x0804dfba in ?? ()
>     #39 0x08050347 in ?? ()
>     #40 0x0804b391 in ?? ()
>     #41 0x00000002 in ?? ()
>     #42 0xbfbfea38 in ?? ()
>     #43 0xbfbfea44 in ?? ()
>     #44 0xbfbfea20 in ?? ()
>     #45 0xbfbfea34 in ?? ()
>     #46 0x00000000 in ?? ()
>     #47 0xbfbfea30 in ?? ()
>     #48 0x0804b305 in ?? ()
>     #49 0x28057f20 in dlclose () from /libexec/ld-elf.so.1
> 
> We don't know, what is crashing -- nor which library is being
> dlclosed for that matter. Some times there are no other ill effects,
> and some other times the icons in the tray get messed up a little --
> but remain functional. What is this, and how do we stop it from
> happening? Thanks! Yours,

Tray icons getting messed up points to kded4 and it appears in the
backtrace as well. It seems to be a problem with the kpackagekit
plugin for kded, so maybe the problem goes away if you remove
kpackagekit. The dlclose in the backtrace isn't a real call. It's
just data on the stack that the debugger thinks is a call.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-freebsd/attachments/20100728/bf76c95e/attachment.sig