Bug 348272 - kwin_x11 crashes on start-up
Summary: kwin_x11 crashes on start-up
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.3.1
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-05-26 21:44 UTC by Rewarp
Modified: 2015-05-28 23:38 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 Rewarp 2015-05-26 21:44:27 UTC
Application: kwin_x11 (5.3.1)

Qt Version: 5.4.1
Operating System: Linux 3.16.7-21-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Booting up computer.

- Unusual behavior I noticed:
Before the update and restart, switching activities with the shortcut key causes parts of the desktop to freeze, with the exception of KRunner and applications. Panel did not respond to mouse input, yet applications could run.

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7f2993085700 (LWP 2864)):
#0  0x00007ffc619f9bb6 in ?? ()
#1  0xb9e2e2df00000000 in ?? ()
#2  0x0000000000007f29 in ?? ()
#3  0x8c00111800000000 in ?? ()
#4  0x8c0008e000007f29 in ?? ()
#5  0x8c000a7800007f29 in ?? ()
#6  0x0000000000007f29 in ?? ()
#7  0x8c000f9800000000 in ?? ()
#8  0x8c0008c000007f29 in ?? ()
#9  0xb9e41cad00007f29 in ?? ()
#10 0xb9d60d7800007f29 in ?? ()
#11 0xb7b61aa600007f29 in ?? ()
#12 0x0000004300007f29 in ?? ()
#13 0x8c0008e000000000 in ?? ()
#14 0x93084be000007f29 in ?? ()
#15 0xb7cdf77900007f29 in ?? ()
#16 0x8c0008e000007f29 in ?? ()
#17 0xb7cdeb6300007f29 in ?? ()
#18 0x0000000000007f29 in ?? ()
#19 0x0000000000007f29 in ?? ()
#20 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f2991ea5700 (LWP 2865)):
#0  0x00007f29b96ed05f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f29b625961b in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x00007f29b6259649 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x00007f29b96e90a4 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f29b9e3506d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f29ba482800 (LWP 2822)):
[KCrash Handler]
#4  0x00007f29b47ed807 in at (i=0, this=0x696772614d510028) at /usr/include/qt5/QtCore/qvector.h:389
#5  pointer (this=<optimized out>) at /usr/include/qt5/QtCore/qresultstore.h:107
#6  value (this=<optimized out>) at /usr/include/qt5/QtCore/qresultstore.h:101
#7  resultReference (index=0, this=0x1599e90) at /usr/include/qt5/QtCore/qfutureinterface.h:247
#8  result (this=0x1599e90) at /usr/include/qt5/QtCore/qfuture.h:164
#9  result (this=0x1599e80) at /usr/include/qt5/QtCore/qfuturewatcher.h:122
#10 operator() (__closure=<optimized out>) at /usr/src/debug/kactivities-5.10.0/src/utils/dbusfuture_p.h:169
#11 call (arg=<optimized out>, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:494
#12 call<QtPrivate::List<>, void> (arg=<optimized out>, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:551
#13 QtPrivate::QFunctorSlotObject<DBusFuture::continueWith(const QFuture<T>&, _Continuation&&) [with _ReturnType = QString; _Continuation = KActivities::Manager::serviceOwnerChanged(const QString&, const QString&, const QString&)::__lambda43]::__lambda29, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=<optimized out>, this_=<optimized out>, r=<optimized out>, a=<optimized out>, ret=<optimized out>) at /usr/include/qt5/QtCore/qobject_impl.h:192
#14 0x00007f29b7cba456 in QObject::event (this=0x1599e80, e=e@entry=0x1990c30) at kernel/qobject.cpp:1245
#15 0x00007f29b7aa7732 in QFutureWatcherBase::event (this=<optimized out>, event=0x1990c30) at thread/qfuturewatcher.cpp:342
#16 0x00007f29b8949b5c in QApplicationPrivate::notify_helper (this=this@entry=0x150bbf0, receiver=receiver@entry=0x1599e80, e=e@entry=0x1990c30) at kernel/qapplication.cpp:3720
#17 0x00007f29b894ea26 in QApplication::notify (this=0x7ffc619f2c10, receiver=0x1599e80, e=0x1990c30) at kernel/qapplication.cpp:3503
#18 0x00007f29b7c89df5 in QCoreApplication::notifyInternal (this=0x7ffc619f2c10, receiver=0x1599e80, event=event@entry=0x1990c30) at kernel/qcoreapplication.cpp:935
#19 0x00007f29b7c8bc8f in sendEvent (event=0x1990c30, receiver=<optimized out>) at kernel/qcoreapplication.h:228
#20 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x14fb930) at kernel/qcoreapplication.cpp:1552
#21 0x00007f29b7cdf284 in QEventDispatcherUNIX::processEvents (this=0x1559e60, flags=flags@entry=...) at kernel/qeventdispatcher_unix.cpp:579
#22 0x00007f29a35a1b0d in QUnixEventDispatcherQPA::processEvents (this=<optimized out>, flags=...) at eventdispatchers/qunixeventdispatcher.cpp:62
#23 0x00007f29b7c87d5b in QEventLoop::exec (this=this@entry=0x7ffc619f2b40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#24 0x00007f29b7c8f3c6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188
#25 0x00007f29b81b819c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1507
#26 0x00007f29b8946235 in QApplication::exec () at kernel/qapplication.cpp:2956
#27 0x00007f29ba0fc668 in kdemain (argc=3, argv=0x7ffc619f2d78) at /usr/src/debug/kwin-5.3.1/main_x11.cpp:301
#28 0x00007f29b9d71b05 in __libc_start_main () from /lib64/libc.so.6
#29 0x000000000040085e in _start () at ../sysdeps/x86_64/start.S:122

Reported using DrKonqi
Comment 1 Rewarp 2015-05-26 22:22:52 UTC
kactivities5 was not properly updated. After logging in with a separate windows manager (E17), I cheked the Frameworks5 repository and saw kactivities5 was not updated. Desktop now runs normally.
Comment 2 Tony 2015-05-28 15:58:30 UTC
(In reply to Rewarp from comment #1)
> kactivities5 was not properly updated. After logging in with a separate
> windows manager (E17), I cheked the Frameworks5 repository and saw
> kactivities5 was not updated. Desktop now runs normally.

Thanks, this solved it for me too.  
Updated all avalable in Framwerks5 repo