Bug 227924 - Plasma-desktop crashes on startup
Summary: Plasma-desktop crashes on startup
Status: RESOLVED DUPLICATE of bug 191589
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-21 12:11 UTC by Alfred Egger
Modified: 2010-02-21 14:41 UTC (History)
1 user (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 Alfred Egger 2010-02-21 12:11:40 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-1-686-bigmem i686

 -- Backtrace:
Application: Plasma-Arbeitsfläche (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb5f9b700 (LWP 5006))]

Thread 2 (Thread 0xa60d3b90 (LWP 5007)):
#0  0xb7fdd424 in __kernel_vsyscall ()
#1  0xb66f1f65 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb68cb85d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb7ddd5c2 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#4  0xb65f7a9a in ?? () from /usr/lib/libQtNetwork.so.4
#5  0xb7ddc5e2 in ?? () from /usr/lib/libQtCore.so.4
#6  0xb66ee4b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb68bca5e in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb5f9b700 (LWP 5006)):
[KCrash Handler]
#6  0xb78f23dd in KIO::Slave::deref() () from /usr/lib/libkio.so.5
#7  0xb78f2bdc in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5
#8  0xb78f50b3 in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#9  0xb7ee2303 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#10 0xb7ee2f42 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#11 0xb77fec07 in KIO::Connection::readyRead() () from /usr/lib/libkio.so.5
#12 0xb7800513 in ?? () from /usr/lib/libkio.so.5
#13 0xb78008f6 in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#14 0xb7edbb0b in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4
#15 0xb7edd5e0 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#16 0xb6b6da94 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0xb6b75bee in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0xb75b762d in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#19 0xb7ecd1eb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#20 0xb7ecde2e in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#21 0xb7ece00d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#22 0xb7ef84cf in ?? () from /usr/lib/libQtCore.so.4
#23 0xb673be98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0xb673f623 in ?? () from /lib/libglib-2.0.so.0
#25 0xb673f7a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#26 0xb7ef8041 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0xb6c0d305 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb7ecb83a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0xb7ecbc82 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0xb7ece0d9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#31 0xb6b6d917 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#32 0xb39def40 in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#33 0x0804e291 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-21 14:41:40 UTC
Fixed in KDE SC 4.4.0
Thanks

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