Created attachment 73241 [details]
New crash information added by DrKonqi

systemsettings (1.0) on KDE Platform 4.9.00 using Qt 4.8.2

- What I was doing when the application crashed:

I also clicked Desktop effects.
I think its fault is because of OpenGL or Nvidia drivers.
Also im using ubuntu 12.10

-- Backtrace (Reduced):
#6  0x00007f2c6d324c14 in QDeclarativeItem::~QDeclarativeItem (this=0x4901880, __in_chrg=<optimized out>) at graphicsitems/qdeclarativeitem.cpp:1668
#7  0x00007f2c6d2e84ee in ~QDeclarativeElement (this=0x4901880, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#8  QDeclarativePrivate::QDeclarativeElement<QDeclarativeItem>::~QDeclarativeElement (this=0x4901880, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#9  0x00007f2c70754878 in QObject::event (this=0x4901880, e=<optimized out>) at kernel/qobject.cpp:1176
#10 0x00007f2c71399d9c in QApplicationPrivate::notify_helper (this=this@entry=0xd2fa00, receiver=receiver@entry=0x4901880, e=e@entry=0x1788980) at kernel/qapplication.cpp:4556

Sorry.
I really was clicking "Desktop theme".

*** Bug 306159 has been marked as a duplicate of this bug. ***

*** Bug 306267 has been marked as a duplicate of this bug. ***

*** Bug 309287 has been marked as a duplicate of this bug. ***

According to bug 309287 it is caused by the QML window decoration list.

Neither "Desktop Effects" nor "Desktop theme" use QML.

The screenshot at https://bugs.kde.org/show_bug.cgi?id=309287#c5 should  be less misleading than those words.

can everybody please confirm that they got this crash when going to Window Decoration KCM? The crash traces do not match the description. This is very confusing and we need to solve the confusion prior to be able to investigate.

Created attachment 75008 [details]
attachment-30005-0.html

very basic test:
run "kcmshell4 kwindecoration" -> does it crash?

if yes, run "QT_NO_GLIB=1 kcmshell4 kwindecoration" -> does that crash?

Or does either crash on exit?

> From: adaptee@gmail.com
> To: rubenclecio@hotmail.com
> Subject: [Bug 304617] System configuration crashed after clicking desktop effects
> Date: Sun, 4 Nov 2012 07:56:49 +0000
> 
> https://bugs.kde.org/show_bug.cgi?id=304617
> 
> --- Comment #8 from Jekyll Wu <adaptee@gmail.com> ---
> The screenshot at https://bugs.kde.org/show_bug.cgi?id=309287#c5 should  be
> less misleading than those words.
> 
> -- 
> You are receiving this mail because:
> You are on the CC list for the bug.

Created attachment 75009 [details]
attachment-30005-1.dat

Created attachment 75010 [details]
meuDesktop2a.png

Does it matter how fast after any interaction you close the dialog?
Do you get the same crash on closing "kcmshell4 kwindecoration" (standalone version of teh dialog)?

*** Bug 309748 has been marked as a duplicate of this bug. ***

*** Bug 310522 has been marked as a duplicate of this bug. ***

Could anybody encountering this please see comments #10 & #14 and reply to the questions?

Created attachment 75418 [details]
Konsole's output while starting and scrolling the kwindecorator window

Regarding comment #10:
I can run the first terminal command without crashes.
* What I observed: Only my current selected theme is shown in the list.
* While scrolling the "list" I get errors like "file:///usr/share/kde4/apps/kwin/aurorae/aurorae.qml:150: Unable to assign [undefined] to QFont font". I have attached the output in a text file. 
*But after I have opened the windows decoration settings from within the system settings once I can see the different designs when running the terminal command again. 

I am not sure if that helps,  but I thought I should mention it.

In general, I've never encountered the crash again. I come to the conclusion that it happened because some old configuration files got updated after a first activation of every design. I was using KDE some time ago and started only recently to use it again with my old config.

Many thanks for your reply.
The konsole output is mostly harmless (for you) while the "unknown" decoration font is certainly not correct (btu not caused the crash)

Unfortunately this
> In general, I've never encountered the crash again.
actually means you currently can't really assist at investigation on this item  - we need to know what causes this ominous crash, therefore it's mandatory to reproduce it :-(

Your efforts are nevertheless much appreciated!

*** Bug 310545 has been marked as a duplicate of this bug. ***

Created attachment 75510 [details]
New crash information added by DrKonqi

systemsettings (1.0) on KDE Platform 4.9.2 using Qt 4.8.3

- What I was doing when the application crashed: System configuration crashed after clicking desktop effects

-- Backtrace (Reduced):
#6  0x00007f50f3b35dd4 in QDeclarativeItem::~QDeclarativeItem (this=0x1bbbee0, __in_chrg=<optimized out>) at graphicsitems/qdeclarativeitem.cpp:1668
#7  0x00007f50f3af96ee in ~QDeclarativeElement (this=0x1bbbee0, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#8  QDeclarativePrivate::QDeclarativeElement<QDeclarativeItem>::~QDeclarativeElement (this=0x1bbbee0, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#9  0x00007f50f6f6d468 in QObject::event (this=0x1bbbee0, e=<optimized out>) at kernel/qobject.cpp:1176
#10 0x00007f50f7bb4e9c in QApplicationPrivate::notify_helper (this=this@entry=0x119d230, receiver=receiver@entry=0x1bbbee0, e=e@entry=0x1408910) at kernel/qapplication.cpp:4562

Can please everybody raise hands who

a) encountered this crash more than once
AND/OR
b) does NOT use Ubuntu

Thanks.

At the time i reported this, i could easily reproduce that bug.
I tried to do it again today - now it seems gone. (ubuntu user)

Created attachment 75535 [details]
New crash information added by DrKonqi

systemsettings (1.0) on KDE Platform 4.9.3 using Qt 4.8.2

- What I was doing when the application crashed:
System settings crashed while navigating throught it

-- Backtrace (Reduced):
#7  0xb3bf207e in QDeclarativeItem::~QDeclarativeItem (this=0x970d680, __in_chrg=<optimized out>) at graphicsitems/qdeclarativeitem.cpp:1668
#8  0xb3bb0a50 in ~QDeclarativeElement (this=0x970d680, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#9  QDeclarativePrivate::QDeclarativeElement<QDeclarativeItem>::~QDeclarativeElement (this=0x970d680, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#10 0xb60251d3 in qDeleteInEventHandler (o=0x970d680) at kernel/qobject.cpp:4277
#11 0xb602c178 in QObject::event (this=0x970d680, e=0x947dcc0) at kernel/qobject.cpp:1176

(In reply to comment #23)
> At the time i reported this, i could easily reproduce that bug.
> I tried to do it again today - now it seems gone. (ubuntu user)

Do you happen to recall whether that may have been on the day of an update / upgrade?

I did an apt-get upgrade today. Now i can reproduce the crash every single time.
What i do: click "window decorations", then "desktop effects": boom.

This is what crash handler says:
Application: System Settings (systemsettings), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa360b9a780 (LWP 4917))]

Thread 3 (Thread 0x7fa3434d7700 (LWP 4930)):
#0  0x00007fa35db33303 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fa35727d036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fa35727d164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fa35e2b489f in QEventDispatcherGlib::processEvents (this=0x7fa33c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007fa35e283e42 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fa35e284097 in QEventLoop::exec (this=0x7fa3434d6dd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fa35e183057 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007fa35e263b4f in QInotifyFileSystemWatcherEngine::run (this=0x21fa6f0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fa35e18607b in QThreadPrivate::start (arg=0x21fa6f0) at thread/qthread_unix.cpp:307
#9  0x00007fa357749e9a in start_thread (arg=0x7fa3434d7700) at pthread_create.c:308
#10 0x00007fa35db3ecbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fa341910700 (LWP 4949)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fa35b977222 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007fa35b977259 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007fa357749e9a in start_thread (arg=0x7fa341910700) at pthread_create.c:308
#4  0x00007fa35db3ecbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fa360b9a780 (LWP 4917)):
[KCrash Handler]
#6  0x0000000000000000 in ?? ()
#7  0x00007fa35abd09f1 in QDeclarativeItem::~QDeclarativeItem (this=0x49da4a0, __in_chrg=<optimized out>) at graphicsitems/qdeclarativeitem.cpp:1668
#8  0x00007fa35ab93af5 in ~QDeclarativeElement (this=0x49da4a0, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#9  QDeclarativePrivate::QDeclarativeElement<QDeclarativeItem>::~QDeclarativeElement (this=0x49da4a0, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#10 0x00007fa35e29e958 in QObject::event (this=0x49da4a0, e=<optimized out>) at kernel/qobject.cpp:1176
#11 0x00007fa35eefc7b4 in notify_helper (e=0x3cfc0d0, receiver=0x49da4a0, this=0x1b2eff0) at kernel/qapplication.cpp:4556
#12 QApplicationPrivate::notify_helper (this=0x1b2eff0, receiver=0x49da4a0, e=0x3cfc0d0) at kernel/qapplication.cpp:4528
#13 0x00007fa35ef01583 in QApplication::notify (this=0x7fff9f581cc0, receiver=0x49da4a0, e=0x3cfc0d0) at kernel/qapplication.cpp:4417
#14 0x00007fa35fc37786 in KApplication::notify (this=0x7fff9f581cc0, receiver=0x49da4a0, event=0x3cfc0d0) at ../../kdeui/kernel/kapplication.cpp:311
#15 0x00007fa35e28530c in QCoreApplication::notifyInternal (this=0x7fff9f581cc0, receiver=0x49da4a0, event=0x3cfc0d0) at kernel/qcoreapplication.cpp:915
#16 0x00007fa35e2890ea in sendEvent (event=0x3cfc0d0, receiver=0x49da4a0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#17 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1ae01f0) at kernel/qcoreapplication.cpp:1539
#18 0x00007fa35e2b4473 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#19 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:279
#20 0x00007fa35727cd53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fa35727d0a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007fa35727d164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007fa35e2b489f in QEventDispatcherGlib::processEvents (this=0x1ae1ad0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#24 0x00007fa35efa4cde in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x00007fa35e283e42 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007fa35e284097 in QEventLoop::exec (this=0x7fff9f581c50, flags=...) at kernel/qeventloop.cpp:204
#27 0x00007fa35e2893e7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#28 0x000000000040a9e5 in ?? ()
#29 0x00007fa35da6c76d in __libc_start_main (main=0x40a5d0, argc=5, ubp_av=0x7fff9f581f88, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff9f581f78) at libc-start.c:226
#30 0x000000000040aa39 in _start ()

How can i help?

logout, login - does the issue remain?
if yes:
reboot - does the issue remain?

Created attachment 75546 [details]
New crash information added by DrKonqi

systemsettings (1.0) on KDE Platform 4.9.3 using Qt 4.8.2

- What I was doing when the application crashed:
Go to system settings>workspace appearance and click on Window Decorations tab. Then click on Back button and system settings will crash. Sometimes crash happens, sometimes it doesn't.

-- Backtrace (Reduced):
#7  0xb3bcb07e in QDeclarativeItem::~QDeclarativeItem (this=0x94f1d40, __in_chrg=<optimized out>) at graphicsitems/qdeclarativeitem.cpp:1668
#8  0xb3b89a50 in ~QDeclarativeElement (this=0x94f1d40, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#9  QDeclarativePrivate::QDeclarativeElement<QDeclarativeItem>::~QDeclarativeElement (this=0x94f1d40, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#10 0xb5ffe1d3 in qDeleteInEventHandler (o=0x94f1d40) at kernel/qobject.cpp:4277
#11 0xb6005178 in QObject::event (this=0x94f1d40, e=0x926f2d8) at kernel/qobject.cpp:1176

(In reply to comment #27)
> logout, login - does the issue remain?
> if yes:
> reboot - does the issue remain?

Yapp, both tested. Issue remains. Anything else? If you want, we could meet in some irc channel...

Check whether "kcmshell4 kwindecoration" crashes?
If not, check bug #310613, match your locale related order and see whether the order of kcm's has an impact.

(In reply to comment #30)
> Check whether "kcmshell4 kwindecoration" crashes?

kcmshell4 kwindecoration does not crash.
But i found something new: starting in systemsettings - window decoration, then clicking on "desktop theme" or "splash screen" causes a crash.

> If not, check bug #310613, 
bug #310613 seems not to be relevant for me.

>match your locale related order and see whether the order of kcm's has an impact.
Sorry, i'm not sure what exactly you want me to check. :(

Created attachment 75570 [details]
New crash information added by DrKonqi

systemsettings (1.0) on KDE Platform 4.9.2 using Qt 4.8.3

- What I was doing when the application crashed:

I changed my window decoaration theme and clicked to another node in the tree.

-- Backtrace (Reduced):
#6  0x00007f92efe6fdd4 in QDeclarativeItem::~QDeclarativeItem (this=0x4fbc200, __in_chrg=<optimized out>) at graphicsitems/qdeclarativeitem.cpp:1668
#7  0x00007f92efe336ee in ~QDeclarativeElement (this=0x4fbc200, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#8  QDeclarativePrivate::QDeclarativeElement<QDeclarativeItem>::~QDeclarativeElement (this=0x4fbc200, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#9  0x00007f92f32a7468 in QObject::event (this=0x4fbc200, e=<optimized out>) at kernel/qobject.cpp:1176
#10 0x00007f92f3eeee9c in QApplicationPrivate::notify_helper (this=this@entry=0xbf8920, receiver=receiver@entry=0x4fbc200, e=e@entry=0x1bb7220) at kernel/qapplication.cpp:4562

@Martin
in the light of bug #311018 and the (possible abd partially existing) solution in Aurorae i suspect at least Ubuntu ships some Qt lib where basically everything related to QGraphicsView/Scene/Item -> all QML can not be deleted by moc.

TODO:
- get reply on bug #311018
- figure whether this is a downstream or upstream bug
- if not, write a long rant, catch destroyed() and unlink QGraphicsStuff for the metaobject child deleter

@Everybody:
can anybody here apply, compile and test a patch?

*** Bug 311058 has been marked as a duplicate of this bug. ***

*** Bug 312230 has been marked as a duplicate of this bug. ***

Created attachment 76027 [details]
wild guess patch

wild guess patch attempt.

anybody encountering this bug more often than never and compiling from sources, who'd be able to inject the patch and see whether the issue remains, would do us, himself and probably every ubuntu user (anyone attached to this not using ubuntu?) a big favor by confirming or denying the patch approach.

Thanks.

Created attachment 76324 [details]
New crash information added by DrKonqi

kwin (4.9.97) on KDE Platform 4.9.97 using Qt 4.8.3

- What I was doing when the application crashed:
I was installing a new theme for the window decorations.  The first time I changed  it from a downloaded theme, "Diamond" I lost the window decorations and had to log out.  When I logged back in the decorations were back and when I changed them again Kwin crashed.  Running KDE 4.9.97 RC 2 on Kubuntu 12.10.  

- Custom settings of the application:

-- Backtrace (Reduced):
#7  0x00007f9a69822dd7 in QDeclarativeItem::~QDeclarativeItem (this=0x1aa2aa0, __in_chrg=<optimized out>) at graphicsitems/qdeclarativeitem.cpp:1668
#8  0x00007f9a697e66ee in ~QDeclarativeElement (this=0x1aa2aa0, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#9  QDeclarativePrivate::QDeclarativeElement<QDeclarativeItem>::~QDeclarativeElement (this=0x1aa2aa0, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#10 0x00007f9a65ccc468 in QObject::event (this=0x1aa2aa0, e=<optimized out>) at kernel/qobject.cpp:1176
#11 0x00007f9a6505ee9c in QApplicationPrivate::notify_helper (this=this@entry=0x13c4a80, receiver=receiver@entry=0x1aa2aa0, e=e@entry=0x20de0d0) at kernel/qapplication.cpp:4562

Created attachment 76592 [details]
New crash information added by DrKonqi

systemsettings (1.0) on KDE Platform 4.9.4 using Qt 4.8.3

- What I was doing when the application crashed: I modified the desktop theme settings, applied them and upon navigating to another selection in system settings, it crashed.

-- Backtrace (Reduced):
#8  0xb3e776d1 in QDeclarativeItem::~QDeclarativeItem (this=0xb7b9fc8, __in_chrg=<optimized out>) at graphicsitems/qdeclarativeitem.cpp:1668
#9  0xb3e36124 in ~QDeclarativeElement (this=0xb7b9fc8, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#10 QDeclarativePrivate::QDeclarativeElement<QDeclarativeItem>::~QDeclarativeElement (this=0xb7b9fc8, __in_chrg=<optimized out>) at ../../include/QtDeclarative/../../src/declarative/qml/qdeclarativeprivate.h:87
#11 0xb608b783 in qDeleteInEventHandler (o=o@entry=0xb7b9fc8) at kernel/qobject.cpp:4277
#12 0xb608df10 in QObject::event (this=0xb7b9fc8, e=0xac76770) at kernel/qobject.cpp:1176

UPSTREAM, or is there really a kwin issue?

given several other dupertaces placed there: dupe (and upstream)

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