Application: kwin (4.4.1 (KDE 4.4.1)) KDE Platform Version: 4.4.1 (KDE 4.4.1) Qt Version: 4.6.2 Operating System: Linux 2.6.32-16-generic x86_64 Distribution: Ubuntu lucid (development branch) -- Information about the crash: KWin just crashed. Prior to the crash I had noticed that my machine was swapping memory a lot, leading to major thrashing, with the digital clock stopping for almost a minute. -- Backtrace: Application: KWin (kwin), signal: Bus error [Current thread is 1 (Thread 0x7f58bc7bd820 (LWP 8813))] Thread 2 (Thread 0x7f589d04a710 (LWP 8814)): #0 0xffffffffff60017b in ?? () #1 0x00007f589d0499e0 in ?? () #2 0x00007fff12ef6852 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (Thread 0x7f58bc7bd820 (LWP 8813)): [KCrash Handler] #5 0x00007f58bbbd87b0 in KPixmapCache::Private::mmapFile (this=0x928990, filename=..., info=0x9289e0, newsize=33656832) at ../../kdeui/util/kpixmapcache.cpp:491 #6 0x00007f58bbbda0b4 in KPixmapCache::Private::mmapFiles (this=0x928990) at ../../kdeui/util/kpixmapcache.cpp:419 #7 0x00007f58bbbd9ed3 in KPixmapCache::Private::init (this=0x928990) at ../../kdeui/util/kpixmapcache.cpp:1061 #8 0x00007f58bbbdb94d in KPixmapCache::discard (this=0x905500) at ../../kdeui/util/kpixmapcache.cpp:1279 #9 0x00007f58bbbdc038 in KPixmapCache::deleteCache (name=...) at ../../kdeui/util/kpixmapcache.cpp:1255 #10 0x00007f58bb5f5add in Plasma::ThemePrivate::discardCache (this=0x903500) at ../../plasma/theme.cpp:221 #11 0x00007f58bb5f5f3d in Plasma::ThemePrivate::compositingChanged (this=0x903500) at ../../plasma/theme.cpp:213 #12 0x00007f58bb5fa912 in Plasma::Theme::qt_metacall (this=0x8ff2f0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff12ef01c0) at ./theme.moc:108 #13 0x00007f58b7edddbf in QMetaObject::activate (sender=0x8eb280, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7f58bc04707d) at kernel/qobject.cpp:3293 #14 0x00007f58bbbd258d in KSelectionWatcher::Private::x11Event (this=<value optimized out>, ev_P=0x0) at ../../kdeui/util/kmanagerselection.cpp:395 #15 0x00007f58bbb58ce6 in KAppX11HackWidget::publicx11Event (this=<value optimized out>, _event=0x7fff12ef0890) at ../../kdeui/kernel/kapplication.cpp:903 #16 KApplication::x11EventFilter (this=<value optimized out>, _event=0x7fff12ef0890) at ../../kdeui/kernel/kapplication.cpp:953 #17 0x00007f58b868c5e1 in qt_x11EventFilter (ev=0x7fff12ef0890) at kernel/qapplication_x11.cpp:399 #18 0x00007f58b869b111 in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7fff12ef0890) at kernel/qapplication_x11.cpp:3231 #19 0x00007f58b86c7632 in x11EventSourceDispatch (s=0x7459b0, callback=<value optimized out>, user_data=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:146 #20 0x00007f58b244d492 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #21 0x00007f58b2451308 in ?? () from /lib/libglib-2.0.so.0 #22 0x00007f58b24514bc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #23 0x00007f58b7ef4483 in QEventDispatcherGlib::processEvents (this=0x741ad0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412 #24 0x00007f58b86c721e in QGuiEventDispatcherGlib::processEvents (this=0x952260, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #25 0x00007f58b7ec9902 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #26 0x00007f58b7ec9cdc in QEventLoop::exec (this=0x7fff12ef0bc0, flags=) at kernel/qeventloop.cpp:201 #27 0x00007f58b7ecda1b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #28 0x00007f58bc33f72e in kdemain () from /usr/lib/libkdeinit4_kwin.so #29 0x00007f58bbf8dc4d in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff12ef1188) at libc-start.c:226 #30 0x00000000004006b9 in _start () This bug may be a duplicate of or related to bug 182026. Possible duplicates by query: bug 230368, bug 230119, bug 230103, bug 229868, bug 229726. Reported using DrKonqi
Different to bug 182026, I had not been switching themes during this session.
*** This bug has been marked as a duplicate of bug 182026 ***
> Plasma::ThemePrivate::compositingChanged you un/suspended compositing this will cause plasma to load the non/compositing variant of the theme and is more or less like a "normal" theme change (i hate mid air notions ;-)
Quoting Thomas Lübking <thomas.luebking@web.de>: > you un/suspended compositing Not knowingly. Could compositing have been suspended automatically due to low-memory concerns?
if you didn't disable the checks, yes - due to performance issues