Bug 278719 - KWin crash when i try to apply a theme to space work
Summary: KWin crash when i try to apply a theme to space work
Status: RESOLVED DUPLICATE of bug 257246
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-28 17:15 UTC by tmax26
Modified: 2011-07-28 17:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tmax26 2011-07-28 17:15:07 UTC
Application: kwin (4.7.00 (4.7.0) "release 6")
KDE Platform Version: 4.7.00 (4.7.0) "release 6"
Qt Version: 4.7.4
Operating System: Linux 2.6.37.6-45-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
KWin crash when i try to apply a theme to space work, i was trying several themes and then crashed

The crash can be reproduced some of the time.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f5d94f23760 (LWP 2644))]

Thread 2 (Thread 0x7f5d77fff700 (LWP 2694)):
#0  0x00007f5d9077f38c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f5d935b3114 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f5d938cc180) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x00007f5d935b3149 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=0x7f5d938da254) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x00007f5d9077aa3f in start_thread () from /lib64/libpthread.so.0
#4  0x00007f5d9478567d in clone () from /lib64/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f5d94f23760 (LWP 2644)):
[KCrash Handler]
#6  0x00007f5d942ece83 in KImageCache::insertPixmap(QString const&, QPixmap const&) () from /usr/lib64/libkdeui.so.5
#7  0x00007f5d93cee055 in Plasma::ThemePrivate::scheduledCacheUpdate() () from /usr/lib64/libplasma.so.3
#8  0x00007f5d93cf13c8 in Plasma::Theme::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libplasma.so.3
#9  0x00007f5d90b08a7f in QMetaObject::activate (sender=0x7e65c0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3278
#10 0x00007f5d90b080c9 in QObject::event (this=0x7e65c0, e=<value optimized out>) at kernel/qobject.cpp:1181
#11 0x00007f5d8fc9b194 in QApplicationPrivate::notify_helper (this=0x646cb0, receiver=0x7e65c0, e=0x7fffceea6dc0) at kernel/qapplication.cpp:4481
#12 0x00007f5d8fca374a in QApplication::notify (this=<value optimized out>, receiver=0x7e65c0, e=0x7fffceea6dc0) at kernel/qapplication.cpp:4360
#13 0x00007f5d94284736 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#14 0x00007f5d90af43dc in QCoreApplication::notifyInternal (this=0x7fffceea7290, receiver=0x7e65c0, event=0x7fffceea6dc0) at kernel/qcoreapplication.cpp:787
#15 0x00007f5d90b21d78 in sendEvent (this=0x648590) at kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x648590) at kernel/qeventdispatcher_unix.cpp:617
#17 0x00007f5d90b22340 in QEventDispatcherUNIX::processEvents (this=0x611a70, flags=...) at kernel/qeventdispatcher_unix.cpp:936
#18 0x00007f5d8fd41cdc in QEventDispatcherX11::processEvents (this=0x611a70, flags=...) at kernel/qeventdispatcher_x11.cpp:152
#19 0x00007f5d90af3832 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#20 0x00007f5d90af3a45 in QEventLoop::exec (this=0x7fffceea7180, flags=...) at kernel/qeventloop.cpp:201
#21 0x00007f5d90af7e8b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#22 0x00007f5d94a7c99d in kdemain () from /usr/lib64/libkdeinit4_kwin.so
#23 0x00007f5d946d0bfd in __libc_start_main () from /lib64/libc.so.6
#24 0x0000000000400699 in _start ()

Possible duplicates by query: bug 264952, bug 263580, bug 259505, bug 257433, bug 257246.

Reported using DrKonqi
Comment 1 Martin Flöser 2011-07-28 17:25:13 UTC

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