Bug 193928 - Plasma segfault after ALT-TAB while writing e-mail in KMail
Summary: Plasma segfault after ALT-TAB while writing e-mail in KMail
Status: RESOLVED DUPLICATE of bug 192066
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-05-24 18:56 UTC by planetzappa
Modified: 2009-05-27 20:01 UTC (History)
3 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 planetzappa 2009-05-24 18:56:40 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 125"
Qt Version: 4.5.2
Operating System: Linux 2.6.27.19-3.2-default x86_64
Distribution: "openSUSE 11.1 (x86_64)"

What I was doing when the application crashed:
Was writing an e-mail with KMail, then alt-tabbed to another KMail instance window, then observed a plasma crash

 -- Backtrace:
Application: Plasma-Arbeitsfläche (kdeinit), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fcde1cbf750 (LWP 18634))]

Thread 2 (Thread 0x7fcdc1ce5950 (LWP 18636)):
#0  0x00007fcde1497d59 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fcde1708e29 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4
#2  0x00007fcde033279c in ?? () from /usr/lib64/libQtNetwork.so.4
#3  0x00007fcde1707e75 in ?? () from /usr/lib64/libQtCore.so.4
#4  0x00007fcde1494070 in start_thread () from /lib64/libpthread.so.0
#5  0x00007fcdddfe610d in clone () from /lib64/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fcde1cbf750 (LWP 18634)):
[KCrash Handler]
#5  0x00007fcdddf8f560 in strlen () from /lib64/libc.so.6
#6  0x00007fcde17fa3b8 in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from /usr/lib64/libQtCore.so.4
#7  0x00007fcdd83bfe13 in Plasma::Animator::timerEvent(QTimerEvent*) () from /usr/lib64/libplasma.so.3
#8  0x00007fcde18015a3 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#9  0x00007fcddeb84b8d in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#10 0x00007fcddeb8ce0a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#11 0x00007fcddfc6e37b in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#12 0x00007fcde17f17bc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#13 0x00007fcde181ed20 in ?? () from /usr/lib64/libQtCore.so.4
#14 0x00007fcde181af9d in ?? () from /usr/lib64/libQtCore.so.4
#15 0x00007fcddd6640db in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#16 0x00007fcddd6678ad in ?? () from /usr/lib64/libglib-2.0.so.0
#17 0x00007fcddd667a6b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#18 0x00007fcde181aeff in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#19 0x00007fcddec1bcdf in ?? () from /usr/lib64/libQtGui.so.4
#20 0x00007fcde17f0042 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#21 0x00007fcde17f0414 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#22 0x00007fcde17f2704 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#23 0x00007fcdd49d1aab in kdemain () from /usr/lib64/libkdeinit4_plasma-desktop.so
#24 0x00000000004071fe in _start ()
Comment 1 Marco Martin 2009-05-24 19:32:31 UTC
this backtrace looks incomplete, please see
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Dario Andres 2009-05-24 19:34:44 UTC
Probably a duplicate of bug 192066. Thanks
Comment 3 Aaron J. Seigo 2009-05-27 20:01:45 UTC
yes, it is a dupe of 192066.

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