Bug 195058 - startup thats all i know
Summary: startup thats all i know
Status: RESOLVED DUPLICATE of bug 192525
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kded (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-03 06:16 UTC by Sebastian Wolf
Modified: 2009-06-12 23:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Wolf 2009-06-03 06:16:19 UTC
Application that crashed: kded4
Version of the application: $Id: kded.cpp 944898 2009-03-26 13:01:25Z dfaure $
KDE Version: 4.2.88 (KDE 4.2.88 (KDE 4.3 >= 20090527))
Qt Version: 4.5.1
Operating System: Linux 2.6.29-4.slh.4-sidux-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

What I was doing when the application crashed:
sorry that i can not give more information but i don't even know which app crashed because everytime i startup kde from svn the app crashes but i am never missin anything after that crash

 -- Backtrace:
Application: KDE Daemon (kdeinit), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f12f83b2618 in QBasicAtomicInt::ref (this=0x841f0f) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121
#6  0x00007f12f83b30f2 in QString (this=0x1df31f0, other=@0x7f12f9504818) at /usr/include/qt4/QtCore/qstring.h:712
#7  0x00007f12f83b9084 in QMap<QString, ExtraField>::node_create (this=0x19fd660, adt=0x1b2b460, aupdate=0x7fff01a8e5e0, akey=@0x7f12f9504818, avalue=@0x7f12f9504820)
    at /usr/include/qt4/QtCore/qmap.h:420
#8  0x00007f12f83b9268 in QMap<QString, ExtraField>::detach_helper (this=0x19fd660) at /usr/include/qt4/QtCore/qmap.h:708
#9  0x00007f12f83b93ed in QMap<QString, ExtraField>::operator= (this=0x19fd660, other=@0x1afe7f0) at /usr/include/qt4/QtCore/qmap.h:403
#10 0x00007f12f83b6934 in KIO::AuthInfo::operator= (this=0x7fff01a8e730, info=@0x1b67f80) at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/authinfo.cpp:146
#11 0x00007f12f83b6b98 in AuthInfo (this=0x7fff01a8e730, info=@0x1b67f80) at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/authinfo.cpp:123
#12 0x00007f12e0954368 in KPasswdServerAdaptor::qt_metacall (this=0x1a8d5b0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff01a8ea40)
    at /home/kde-devel/kde/build/KDE/kdebase/runtime/kpasswdserver/kpasswdserveradaptor.moc:139
#13 0x00007f12f9592862 in QMetaObject::activate (sender=0x1b092e0, from_signal_index=<value optimized out>, to_signal_index=8, argv=0x7fff01a8e5d8) at kernel/qobject.cpp:3120
#14 0x00007f12e094b16d in KPasswdServer::checkAuthInfoAsyncResult (this=0x1b092e0, _t1=6, _t2=1, _t3=@0x1b67f80) at /home/kde-devel/kde/build/KDE/kdebase/runtime/kpasswdserver/kpasswdserver.moc:121
#15 0x00007f12e094ef0d in KPasswdServer::processRequest (this=0x1b092e0) at /home/kde-devel/kde/src/KDE/kdebase/runtime/kpasswdserver/kpasswdserver.cpp:687
#16 0x00007f12e094f4a2 in KPasswdServer::qt_metacall (this=0x1b092e0, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0x7fff01a8f1c0)
    at /home/kde-devel/kde/build/KDE/kdebase/runtime/kpasswdserver/kpasswdserver.moc:108
#17 0x00007f12f9592862 in QMetaObject::activate (sender=0x1ae2fe0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x7fff01a8e5d8) at kernel/qobject.cpp:3120
#18 0x00007f12f9597b9f in QSingleShotTimer::timerEvent (this=0x1ae2fe0) at kernel/qtimer.cpp:298
#19 0x00007f12f958cb43 in QObject::event (this=0x1ae2fe0, e=0x7f12f9504818) at kernel/qobject.cpp:1082
#20 0x00007f12f67c94fd in QApplicationPrivate::notify_helper (this=0x18dab80, receiver=0x1ae2fe0, e=0x7fff01a8f8b0) at kernel/qapplication.cpp:4057
#21 0x00007f12f67d177a in QApplication::notify (this=0x7fff01a8fc00, receiver=0x1ae2fe0, e=0x7fff01a8f8b0) at kernel/qapplication.cpp:4022
#22 0x00007f12f792b53d in KApplication::notify (this=0x7fff01a8fc00, receiver=0x1ae2fe0, event=0x7fff01a8f8b0) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:302
#23 0x00007f12f957ce4c in QCoreApplication::notifyInternal (this=0x7fff01a8fc00, receiver=0x1ae2fe0, event=0x7fff01a8f8b0) at kernel/qcoreapplication.cpp:610
#24 0x00007f12f95aa036 in QTimerInfoList::activateTimers (this=0x18de780) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#25 0x00007f12f95a655d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164
#26 0x00007f12f5244f7a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0x00007f12f52485f8 in ?? () from /usr/lib/libglib-2.0.so.0
#28 0x00007f12f52487bc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0x00007f12f95a64bf in QEventDispatcherGlib::processEvents (this=0x1851840, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#30 0x00007f12f6861c7f in QGuiEventDispatcherGlib::processEvents (this=0x841f0f, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#31 0x00007f12f957b6f2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 27851552}) at kernel/qeventloop.cpp:149
#32 0x00007f12f957babd in QEventLoop::exec (this=0x7fff01a8fb60, flags={i = 27851632}) at kernel/qeventloop.cpp:200
#33 0x00007f12f957dd84 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#34 0x00007f12e7d0657e in kdemain (argc=1, argv=0x1893200) at /home/kde-devel/kde/src/KDE/kdelibs/kded/kded.cpp:938
#35 0x00000000004075e2 in launch (argc=1, _name=0x40bb70 "kded4", args=0x0, cwd=0x0, envc=0, envs=0x0, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40b692 "0")
    at /home/kde-devel/kde/src/KDE/kdelibs/kinit/kinit.cpp:671
#36 0x0000000000408e52 in main (argc=2, argv=0x7fff01a904c8, envp=0x7fff01a904e0) at /home/kde-devel/kde/src/KDE/kdelibs/kinit/kinit.cpp:1730

Reported using DrKonqi
Comment 1 Dario Andres 2009-06-03 15:13:12 UTC
The backtrace looks like bug 192525, but I'm not sure about the situation.
Thanks for reporting!
Comment 2 Michael Leupold 2009-06-12 23:54:23 UTC
Yes, this is a duplicate. Thanks Dario.

*** This bug has been marked as a duplicate of bug 192525 ***