Bug 210739

Summary: plasma crashes on startup
Product: [Unmaintained] plasma4 Reporter: Andrew Felske <knopper67>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra, aseigo
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Andrew Felske 2009-10-16 02:43:58 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.31-ARCH x86_64

What I was doing when the application crashed:
I just did a fresh archlinux installation. As soon as KDE finished logging in, plasma-workspace crashesss. There was also a "blank" widget (a widget with no content) on the desktop, so I removed it. That could have something to do with it.

 -- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f69b76d1750 (LWP 1628))]

Thread 2 (Thread 0x7f6999082910 (LWP 1647)):
#0  0x00007f69b6ea0dd9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007f69b710bc6b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#2  0x00007f69b358bc9c in ?? () from /usr/lib/libQtNetwork.so.4
#3  0x00007f69b710aba5 in ?? () from /usr/lib/libQtCore.so.4
#4  0x00007f69b6e9c57a in start_thread () from /lib/libpthread.so.0
#5  0x00007f69b486714d in clone () from /lib/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f69b76d1750 (LWP 1628)):
[KCrash Handler]
#5  0x00007f69aec169b1 in Plasma::ExtenderItem::returnToSource() () from /usr/lib/libplasma.so.3
#6  0x00007f69aec2f227 in Plasma::ExtenderApplet::~ExtenderApplet() () from /usr/lib/libplasma.so.3
#7  0x00007f69b71ff07d in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#8  0x00007f69b555bb2b in QGraphicsWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#9  0x00007f69b4f8c07c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#10 0x00007f69b4f9334e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#11 0x00007f69b5bbf586 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#12 0x00007f69b71efbfc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#13 0x00007f69b71f080a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#14 0x00007f69b7218583 in ?? () from /usr/lib/libQtCore.so.4
#15 0x00007f69b3ef11fe in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#16 0x00007f69b3ef4bb8 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#17 0x00007f69b3ef4ce0 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#18 0x00007f69b7218123 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#19 0x00007f69b501f14e in ?? () from /usr/lib/libQtGui.so.4
#20 0x00007f69b71ee532 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#21 0x00007f69b71ee904 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#22 0x00007f69b71f0ab9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#23 0x00007f69ab35028f in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#24 0x0000000000406eae in _start ()

This bug may be a duplicate of or related to bug 207714

Reported using DrKonqi
Comment 1 Aaron J. Seigo 2009-10-16 05:29:26 UTC
looks a lot like a broken installation; can you install the debug packages and generate a full backtrace with line numbers? thanks.
Comment 2 Andrew Felske 2009-10-17 10:29:24 UTC
I wasn't able to reproduce the bug, so, sadly, I can't get a full backtrace. It appears it was a rare happening.

Also, if it helps at all, before I removed the "blank" widget, I opened it's preferences dialog. Apparently, it calls itself a "Container" widget or something like that.
Comment 3 Dario Andres 2009-11-06 03:25:06 UTC
If you haven't experienced this again we could consider closing this report. Thanks
Comment 4 Dario Andres 2009-12-05 14:37:55 UTC
Waiting for feedback. Closing.
Comment 5 Dario Andres 2009-12-18 17:28:18 UTC

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