Bug 310269

Summary:	updating system via aptitude, then first plasma dekstop and then kwin crashed
Product:	[Plasma] kwin	Reporter:	Simon Andric <simonandric5>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	crash
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Simon Andric 2012-11-18 02:24:52 UTC

Application: kwin (4.9.80)
KDE Platform Version: 4.9.80
Qt Version: 4.8.4
Operating System: Linux 3.7.0-2-generic i686
Distribution: Ubuntu Raring Ringtail (development branch)

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

updating system via aptitude, then first plasma dekstop and then kwin crashed. Im using project neon

:) thank you

nice day
Simon

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb100a980 (LWP 3551))]

Thread 2 (Thread 0xabdccb40 (LWP 3558)):
#0  0xb7720424 in __kernel_vsyscall ()
#1  0xb58dd995 in __pthread_cond_wait (cond=0xaeeefb68, mutex=0xaeeefb50) at pthread_cond_wait.c:155
#2  0xb749ea6c in __pthread_cond_wait (cond=0xaeeefb68, mutex=0xaeeefb50) at forward.c:149
#3  0xad12b86c in ?? () from /usr/lib/i386-linux-gnu/dri/r600_dri.so
#4  0xb58eb000 in ?? () from /lib/i386-linux-gnu/libpthread.so.0

Thread 1 (Thread 0xb100a980 (LWP 3551)):
[KCrash Handler]
#7  0xb594b11f in QObjectPrivate::isSignalConnected (this=0x0, signal_index=3) at ../../include/QtCore/private/../../../src/corelib/kernel/qobject_p.h:237
#8  0xb5aae211 in QMetaObject::activate (sender=0xa9fd378, m=0xb6b13afc <QDeclarativeTimer::staticMetaObject>, local_signal_index=1, argv=0x0) at kernel/qobject.cpp:3448
#9  0xb69aa3ed in QDeclarativeTimer::runningChanged (this=0xa9fd378) at .moc/debug-shared/moc_qdeclarativetimer_p.cpp:182
#10 0xb67bd3c5 in QDeclarativeTimer::finished (this=0xa9fd378) at util/qdeclarativetimer.cpp:321
#11 0xb69aa09d in QDeclarativeTimer::qt_static_metacall (_o=0xa9fd378, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf8e9e28) at .moc/debug-shared/moc_qdeclarativetimer_p.cpp:89
#12 0xb5aae61c in QMetaObject::activate (sender=0xa9fd420, m=0xb5c495a0 <QAbstractAnimation::staticMetaObject>, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3539
#13 0xb5947985 in QAbstractAnimation::finished (this=0xa9fd420) at .moc/debug-shared/moc_qabstractanimation.cpp:190
#14 0xb5946d33 in QAbstractAnimationPrivate::setState (this=0xa9fd430, newState=QAbstractAnimation::Stopped) at animation/qabstractanimation.cpp:604
#15 0xb5947425 in QAbstractAnimation::stop (this=0xa9fd420) at animation/qabstractanimation.cpp:958
#16 0xb594739e in QAbstractAnimation::setCurrentTime (this=0xa9fd420, msecs=150) at animation/qabstractanimation.cpp:912
#17 0xb5945fa1 in QUnifiedTimer::updateAnimationsTime (this=0xa23ddc0) at animation/qabstractanimation.cpp:235
#18 0xb594636e in QUnifiedTimer::timerEvent (this=0xa23ddc0, event=0xbf8ea480) at animation/qabstractanimation.cpp:306
#19 0xb5aa981c in QObject::event (this=0xa23ddc0, e=0xbf8ea480) at kernel/qobject.cpp:1156
#20 0xb4d65db8 in QApplicationPrivate::notify_helper (this=0x9ab1cf0, receiver=0xa23ddc0, e=0xbf8ea480) at kernel/qapplication.cpp:4562
#21 0xb4d6342f in QApplication::notify (this=0xbf8ea7b8, receiver=0xa23ddc0, e=0xbf8ea480) at kernel/qapplication.cpp:3944
#22 0xb70ccc5e in KApplication::notify (this=0xbf8ea7b8, receiver=0xa23ddc0, event=0xbf8ea480) at /build/buildd/project-neon-kdelibs-2+git20121116+r92189/kdeui/kernel/kapplication.cpp:311
#23 0xb75e6e46 in KWin::Application::notify (this=0xbf8ea7b8, o=0xa23ddc0, e=0xbf8ea480) at /build/buildd/project-neon-kde-workspace-2+git20121115+r47019/kwin/main.cpp:371
#24 0xb5a9239e in QCoreApplication::notifyInternal (this=0xbf8ea7b8, receiver=0xa23ddc0, event=0xbf8ea480) at kernel/qcoreapplication.cpp:946
#25 0xb6800afb in QCoreApplication::sendEvent (receiver=0xa23ddc0, event=0xbf8ea480) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#26 0xb5acd04d in QTimerInfoList::activateTimers (this=0x9ab246c) at kernel/qeventdispatcher_unix.cpp:622
#27 0xb5acde0c in QEventDispatcherUNIX::activateTimers (this=0x9a75eb8) at kernel/qeventdispatcher_unix.cpp:879
#28 0xb5ace157 in QEventDispatcherUNIX::processEvents (this=0x9a75eb8, flags=...) at kernel/qeventdispatcher_unix.cpp:941
#29 0xb4e34aff in QEventDispatcherX11::processEvents (this=0x9a75eb8, flags=...) at kernel/qeventdispatcher_x11.cpp:152
#30 0xb5a8fa4d in QEventLoop::processEvents (this=0xbf8ea6c8, flags=...) at kernel/qeventloop.cpp:149
#31 0xb5a8fbc5 in QEventLoop::exec (this=0xbf8ea6c8, flags=...) at kernel/qeventloop.cpp:204
#32 0xb5a92a34 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#33 0xb4d630b2 in QApplication::exec () at kernel/qapplication.cpp:3823
#34 0xb75e7ec1 in kdemain (argc=3, argv=0xbf8ea8a4) at /build/buildd/project-neon-kde-workspace-2+git20121115+r47019/kwin/main.cpp:545
#35 0x08048691 in main (argc=3, argv=0xbf8ea8a4) at /build/buildd/project-neon-kde-workspace-2+git20121115+r47019/obj-i686-linux-gnu/kwin/kwin_dummy.cpp:3

Reported using DrKonqi

Comment 1 Thomas Lübking 2012-11-18 03:01:43 UTC

I understand it crashed *once* after the update process and that happens with every update process, but afterwards things run ok?

In this case:
It crashes deep in Qt and right out of the event chain (so te bug would be upstream), but given the circumstances, apparently nobody told ubuntu (i've actually seen such reports more than once) that you cannot trivially override inodes on update and the "install" command is not just a fancy alias for "cp" and that not for no reason ...*

tl;dr - the bug is probably in ubuntus (debians?) update mechanism (i wonder whether it manages to crash itself when updating any lib/exec involved in the update process... leaving a broken config behind =) or eventually on your side (eg. if you're running out of disk space or use a funny filesystem configuration)

* read eg. here: http://en.chys.info/2009/05/install-vs-cp-and-mmap/