Bug 337739

Summary:	pasted from dr-konqui (that was not able to connect any more after the event occurs). Kwin 4.11.11 segfaults (crash) occasionally at login.
Product:	[Plasma] kwin	Reporter:	stakanov
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description stakanov 2014-07-23 20:00:21 UTC

Application: kwin (4.11.11)
KDE Platform Version: 4.13.3
Qt Version: 4.8.5
Operating System: Linux 3.11.10-17-desktop x86_64
Distribution: "openSUSE 13.1 (Bottle) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

nothing, just starting the PC. What I did notice: there are "hangs" also in the normal operation mode of KDE. Since these appeared  it happens sometimes that kwin crashes. Can this be somehow related to baloo? (Just a doubt, because the hangs are especially when the respective session starts therefore the indexing runs and this is also when the kwin crash appears. 

4,13,3 from opensuse repo, 64 bit on a lenovo X201 with external monitor support via vga and hdmi (with a dockingstation.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8b3b0608c0 (LWP 3160))]

Thread 3 (Thread 0x7f8b1d0c1700 (LWP 3162)):
[KCrash Handler]
#6  0x00007f8b34bd9f3c in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#7  0x00007f8b389337c9 in waitForCallFinished (mutex=0xc00088, watcher=<optimized out>) at /usr/src/debug/kactivities-4.13.3/src/lib/core/utils_p.h:96
#8  KActivities::Consumer::listActivities (this=this@entry=0xc00af0) at /usr/src/debug/kactivities-4.13.3/src/lib/core/consumer.cpp:162
#9  0x00007f8b3ac2f3a9 in KWin::fetchActivityListAndCurrent (controller=0xc00af0) at /usr/src/debug/kde-workspace-4.11.11/kwin/activities.cpp:232
#10 0x00007f8b3ac31da8 in QtConcurrent::StoredFunctorCall1<QPair<QString, QStringList>, QPair<QString, QStringList> (*)(KActivities::Controller*), KActivities::Controller*>::runFunctor (this=0xe052a0) at /usr/include/QtCore/qtconcurrentstoredfunctioncall.h:267
#11 0x00007f8b3ac346e7 in QtConcurrent::RunFunctionTask<QPair<QString, QStringList> >::run (this=0xe052a0) at /usr/include/QtCore/qtconcurrentrunbase.h:106
#12 0x00007f8b34acb13e in ?? () from /usr/lib64/libQtCore.so.4
#13 0x00007f8b34ad768f in ?? () from /usr/lib64/libQtCore.so.4
#14 0x00007f8b348400db in start_thread () from /lib64/libpthread.so.0
#15 0x00007f8b3a83990d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f8b15477700 (LWP 3168)):
#0  0x00007f8b348440af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f8b39a358cb in ?? () from /usr/lib64/libQtScript.so.4
#2  0x00007f8b39a35909 in ?? () from /usr/lib64/libQtScript.so.4
#3  0x00007f8b348400db in start_thread () from /lib64/libpthread.so.0
#4  0x00007f8b3a83990d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f8b3b0608c0 (LWP 3160)):
#0  0x00007f8b348440af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f8b34ad7b66 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4
#2  0x00007f8b34acab52 in ?? () from /usr/lib64/libQtCore.so.4
#3  0x00007f8b34acbef5 in QThreadPool::~QThreadPool() () from /usr/lib64/libQtCore.so.4
#4  0x00007f8b34acbf29 in QThreadPool::~QThreadPool() () from /usr/lib64/libQtCore.so.4
#5  0x00007f8b34acc5b5 in ?? () from /usr/lib64/libQtCore.so.4
#6  0x00007f8b3a78a3d9 in __run_exit_handlers () from /lib64/libc.so.6
#7  0x00007f8b3a78a425 in exit () from /lib64/libc.so.6
#8  0x00007f8b33dbd298 in ?? () from /usr/lib64/libQtGui.so.4
#9  0x00007f8b394861a0 in KApplication::xioErrhandler (this=0x7fff7e70efa0, dpy=0xb96790) at /usr/src/debug/kdelibs-4.13.3/kdeui/kernel/kapplication.cpp:419
#10 0x00007f8b386323fe in _XIOError () from /usr/lib64/libX11.so.6
#11 0x00007f8b3862fded in _XEventsQueued () from /usr/lib64/libX11.so.6
#12 0x00007f8b38621ddb in XEventsQueued () from /usr/lib64/libX11.so.6
#13 0x00007f8b33df42a2 in ?? () from /usr/lib64/libQtGui.so.4
#14 0x00007f8b34bd5d0f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#15 0x00007f8b34bd6005 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#16 0x00007f8b34bdb13b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#17 0x00007f8b3ab80266 in kdemain (argc=1, argv=0x7fff7e70f0e8) at /usr/src/debug/kde-workspace-4.11.11/kwin/main.cpp:597
#18 0x00007f8b3a773be5 in __libc_start_main () from /lib64/libc.so.6
#19 0x0000000000400761 in _start () at ../sysdeps/x86_64/start.S:122

Possible duplicates by query: bug 333996, bug 325584.

Segnala a https://bugs.kde.org/

Comment 1 Thomas Lübking 2014-07-23 20:07:47 UTC

At least this crash is not related to baloo.

It's a threading issue when querying the activity list on startup.
(It's complicated. Basically we were between a rock and a hard place that time. Things changed in KDE5, though)

A "slow" system might however raise chances to run into this.

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