Bug 245194 - kdeinit4 crash
Summary: kdeinit4 crash
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kded (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
: 245348 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-07-20 03:25 UTC by andrey amado
Modified: 2010-07-21 20:59 UTC (History)
2 users (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 andrey amado 2010-07-20 03:25:43 UTC
Application: kded4 ($Id: kded.cpp 1031637 2009-10-05 16:58:19Z lunakl $)
KDE Platform Version: 4.4.4 (KDE 4.4.4)
Qt Version: 4.6.3
Operating System: Linux 2.6.32-5-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
kdeinit4 proceed throws the crash about a minute of the start of kde, this results iconstray overlap.

The crash can be reproduced every time.

 -- Backtrace:
Application: Servicio de KDE (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f69da6d6169 in KComponentData::operator=(KComponentData const&) () from /usr/lib/libkdecore.so.5
#6  0x00007f69c77c25b7 in ?? () from /usr/lib/kde4/kded_kingston_update_notifier.so
#7  0x00007f69c77c2bfc in ?? () from /usr/lib/kde4/kded_kingston_update_notifier.so
#8  0x00007f69c77c2cb6 in ?? () from /usr/lib/kde4/kded_kingston_update_notifier.so
#9  0x00007f69d9216346 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#10 0x00007f69c77c2e2c in ?? () from /usr/lib/kde4/kded_kingston_update_notifier.so
#11 0x00007f69c77c349d in ?? () from /usr/lib/kde4/kded_kingston_update_notifier.so
#12 0x00007f69c77c372e in ?? () from /usr/lib/kde4/kded_kingston_update_notifier.so
#13 0x00007f69d9216346 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#14 0x00007f69d919d9d1 in QProcess::finished(int) () from /usr/lib/libQtCore.so.4
#15 0x00007f69d91a2723 in ?? () from /usr/lib/libQtCore.so.4
#16 0x00007f69d91a27f9 in QProcess::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#17 0x00007f69d9216346 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#18 0x00007f69d9262ebe in QSocketNotifier::activated(int) () from /usr/lib/libQtCore.so.4
#19 0x00007f69d921d1a3 in QSocketNotifier::event(QEvent*) () from /usr/lib/libQtCore.so.4
#20 0x00007f69d85a332c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#21 0x00007f69d85a980b in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#22 0x00007f69d974c436 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#23 0x00007f69d920315c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#24 0x00007f69d922caca in ?? () from /usr/lib/libQtCore.so.4
#25 0x00007f69d45d16c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0x00007f69d45d5538 in ?? () from /lib/libglib-2.0.so.0
#27 0x00007f69d45d56ec in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0x00007f69d922c766 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0x00007f69d865314e in ?? () from /usr/lib/libQtGui.so.4
#30 0x00007f69d9201a82 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#31 0x00007f69d9201e5c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#32 0x00007f69d9206aeb in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#33 0x00007f69cc45bca7 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so
#34 0x00000000004073f4 in _start ()

Reported using DrKonqi
Comment 1 Jonathan Thomas 2010-07-20 14:32:45 UTC
This is a problem with the Kingston Update Notifier from Debian. The author is aware of this issue, and an update should be coming to sid soon.
Comment 2 andrey amado 2010-07-21 15:37:27 UTC
Ok.thanks for the answer..
Comment 3 Christoph Feck 2010-07-21 20:59:18 UTC
*** Bug 245348 has been marked as a duplicate of this bug. ***