Bug 214604 - fedora11 plasma startup crash
Summary: fedora11 plasma startup crash
Status: RESOLVED DUPLICATE of bug 213348
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: 2009-11-15 02:35 UTC by ver.cabrera
Modified: 2009-11-20 00:23 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 ver.cabrera 2009-11-15 02:35:15 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.30.9-96.fc11.i586 i686
Distribution: "Fedora release 11 (Leonidas)"

What I was doing when the application crashed:
Plasma crashes at startup. Can re-initialize though and continue normally

 -- Backtrace:
Application: Área de trabajo de Plasma (plasma-desktop), signal: Segmentation fault
[Current thread is 1 (Thread 0xb789c780 (LWP 1887))]

Thread 2 (Thread 0xac691b70 (LWP 1888)):
#0  0x00a11422 in __kernel_vsyscall ()
#1  0x00794fa5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0x003bd307 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#3  0x05456862 in ?? () from /usr/lib/libQtNetwork.so.4
#4  0x003bc2c2 in ?? () from /usr/lib/libQtCore.so.4
#5  0x00790935 in start_thread () from /lib/libpthread.so.0
#6  0x006c594e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb789c780 (LWP 1887)):
[KCrash Handler]
#6  0x06df16fe in Plasma::Applet::flushPendingConstraintsEvents() () from /usr/lib/libplasma.so.3
#7  0x06e1648d in Plasma::Corona::loadLayout(QString const&) () from /usr/lib/libplasma.so.3
#8  0x06e1756e in Plasma::Corona::initializeLayout(QString const&) () from /usr/lib/libplasma.so.3
#9  0x05f49db6 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#10 0x05f4a0ba in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#11 0x05f4a313 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#12 0x004c1dc3 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#13 0x004c2a22 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#14 0x004c6ed7 in ?? () from /usr/lib/libQtCore.so.4
#15 0x004c6fec in ?? () from /usr/lib/libQtCore.so.4
#16 0x004bbedf in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#17 0x02f678b4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0x02f6f029 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#19 0x05934c3a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#20 0x004ac0ab in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#21 0x004d929e in ?? () from /usr/lib/libQtCore.so.4
#22 0x004d6c30 in ?? () from /usr/lib/libQtCore.so.4
#23 0x052c2308 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0x052c59e0 in ?? () from /lib/libglib-2.0.so.0
#25 0x052c5b13 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#26 0x004d6b7c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0x03006c45 in ?? () from /usr/lib/libQtGui.so.4
#28 0x004aa639 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0x004aaa8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0x004acf0f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#31 0x02f67737 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#32 0x05f2d41d in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#33 0x080486fb in _start ()

Reported using DrKonqi
Comment 1 Marco Martin 2009-11-16 18:24:08 UTC
this backtrace looks incomplete, see
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Dario Andres 2009-11-20 00:23:05 UTC
This is likely to be bug 213348 Thanks

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