Application: kdialogd4 (0.10.1) KDE Platform Version: 4.6.2 (4.6.2) (Compiled from sources) Qt Version: 4.7.0 Operating System: Linux 2.6.35-28-generic i686 Distribution: Netrunner 3 Chromatic -- Information about the crash: - What I was doing when the application crashed: Design my Emerald Theme Manager. I switched between Compiz & Emerald and KWin & KDE4 Window Decorator -- Backtrace: Application: KDialog Daemon (kdialogd4), signal: Aborted [KCrash Handler] #7 0x00c02416 in __kernel_vsyscall () #8 0x0533c941 in raise () from /lib/libc.so.6 #9 0x0533fe42 in abort () from /lib/libc.so.6 #10 0x05374305 in ?? () from /lib/libc.so.6 #11 0x0537e501 in ?? () from /lib/libc.so.6 #12 0x0537fd70 in ?? () from /lib/libc.so.6 #13 0x05382e5d in free () from /lib/libc.so.6 #14 0x0617efed in qFree (ptr=0x9e12568) at global/qmalloc.cpp:60 #15 0x061d0180 in QString::free (d=0x0) at tools/qstring.cpp:1151 #16 0x00aaa44d in ~QString (node=0x6) at /usr/include/qt4/QtCore/qstring.h:882 #17 ~QHashNode (node=0x6) at /usr/include/qt4/QtCore/qhash.h:217 #18 QHash<Kuit::Tag::Var, QString>::deleteNode2 (node=0x6) at /usr/include/qt4/QtCore/qhash.h:519 #19 0x061a38fd in QHashData::free_helper (this=0xbfa17e80, node_delete=0xaaa420 <QHash<Kuit::Tag::Var, QString>::deleteNode2(QHashData::Node*)>) at tools/qhash.cpp:271 #20 0x00a8077d in freeData () at /usr/include/qt4/QtCore/qhash.h:568 #21 ~QHash () at /usr/include/qt4/QtCore/qhash.h:284 #22 ~KuitSemanticsStaticData () at ../../kdecore/localization/kuitsemantics.cpp:112 #23 destroy () at ../../kdecore/localization/kuitsemantics.cpp:323 #24 0x0091eeeb in KCleanUpGlobalStatic::~KCleanUpGlobalStatic (this=0xb367dc, __in_chrg=<value optimized out>) at ../../kdecore/kernel/kglobal.h:62 #25 0x0534169e in ?? () from /lib/libc.so.6 #26 0x0534170f in exit () from /lib/libc.so.6 #27 0x05328cef in __libc_start_main () from /lib/libc.so.6 #28 0x0804d1d1 in _start () This bug may be a duplicate of or related to bug 277004. Possible duplicates by query: bug 277893, bug 277004. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 277004 ***