Bug 181997

Summary: The application Робочий простір Плазми (plasma) crashed and caused the signal 11 (SIGSEGV).
Product: [Unmaintained] plasma4 Reporter: Yuriy Padlyak <YuriyPadlyak>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra, christophe
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Yuriy Padlyak 2009-01-26 17:37:40 UTC
Version:            (using KDE 4.1.96)
Installed from:    Ubuntu Packages

Програма: Робочий простір Плазми (plasma), сигнал SIGSEGV
[Current thread is 0 (LWP 11313)]

Thread 3 (Thread 0xa9aeeb90 (LWP 11386)):
#0  0xb7fd8430 in __kernel_vsyscall ()
#1  0xb5823075 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb640a9ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb65f46f2 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb7974532 in ?? () from /usr/lib/libQtNetwork.so.4
#5  0xb65f36ae in ?? () from /usr/lib/libQtCore.so.4
#6  0xb581f50f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb63fc7ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xa92c1b90 (LWP 11427)):
#0  0xb7fd8430 in __kernel_vsyscall ()
#1  0xb5823075 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb640a9ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb65f46f2 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xa9bd8422 in ?? () from /usr/lib/kde4/plasma_wallpaper_image.so
#5  0xb65f36ae in ?? () from /usr/lib/libQtCore.so.4
#6  0xb581f50f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb63fc7ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb53af6c0 (LWP 11313)):
[KCrash Handler]
#6  0xa9ddbcda in TaskManager::GroupManager::add () from /usr/lib/libtaskmanager.so.4
#7  0xa9dddebf in TaskManager::GroupManager::qt_metacall () from /usr/lib/libtaskmanager.so.4
#8  0xb66f8a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#9  0xb66f97e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xa9df7c03 in TaskManager::TaskManager::taskAdded () from /usr/lib/libtaskmanager.so.4
#11 0xa9df9d5e in TaskManager::TaskManager::windowAdded () from /usr/lib/libtaskmanager.so.4
#12 0xa9dfae2c in TaskManager::TaskManager::qt_metacall () from /usr/lib/libtaskmanager.so.4
#13 0xb66f8a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb66f97e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb7846303 in KWindowSystem::windowAdded () from /usr/lib/libkdeui.so.5
#16 0xb78489a9 in ?? () from /usr/lib/libkdeui.so.5
#17 0xb78580a7 in NETRootInfo::update () from /usr/lib/libkdeui.so.5
#18 0xb785845f in NETRootInfo::event () from /usr/lib/libkdeui.so.5
#19 0xb7848dbd in ?? () from /usr/lib/libkdeui.so.5
#20 0xb76f3339 in KApplication::x11EventFilter () from /usr/lib/libkdeui.so.5
#21 0xb7f750e7 in ?? () from /usr/lib/libkdeinit4_plasma.so
#22 0xb69d2a9e in ?? () from /usr/lib/libQtGui.so.4
#23 0xb69e34d5 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#24 0xb6a0e7aa in ?? () from /usr/lib/libQtGui.so.4
#25 0xb56646f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0xb5667da3 in ?? () from /usr/lib/libglib-2.0.so.0
#27 0xb5667f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#28 0xb670e478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#29 0xb6a0dea5 in ?? () from /usr/lib/libQtGui.so.4
#30 0xb66e252a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#31 0xb66e26ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#32 0xb66e4da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#33 0xb6973767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#34 0xb7f62d86 in kdemain () from /usr/lib/libkdeinit4_plasma.so
#35 0x08048712 in _start ()
Comment 1 Dario Andres 2009-01-27 01:14:47 UTC
This is probably related to bug 174787
If you experience this all the time, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
Comment 2 Christophe Marin 2009-03-08 14:51:21 UTC
No useful backtrace was provided. Let's assume it was really a dup. of bug 174787 which is now fixed.

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