Created attachment 181153 [details]
Screenshot of crashes

Thank you for the bug report and for helping test 6.4!

Can you press "See Developer Information" on that window, then attach the output to this bug report?

Make sure to enable debuginfod; there should be a checkbox directly in the window to do so. It will take a while to generate the backtrace that we need.

Pressing the "See Developer Information" the window closes and nothing else happens.

I have submitted more reports and put "Bug 504034" in the "tell us more" window.

Created attachment 181178 [details]
Window with additional info

Actually the window displays "Gathering crash information failed for unknown reason". Pressing "view detailed output" does nothing. Window just closes.

That's unfortunate, without this information there's nothing we can do here.

Maybe the method in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB can help you get a backtrace?

Is this useful?

(gdb) backtrace
#0  QQmlPropertyCacheCreator<QQmlTypeCompiler>::buildMetaObjectRecursively (this=0x7f9f90bf80d0, objectIndex=19, context=..., isVMERequired=<optimized out>) at /usr/src/debug/qtdeclarative-everywhere-src-6.9.0/src/qml/qml/qqmlpropertycachecreator_p.h:377
#1  0x00007f9fb679d2d6 in QQmlPropertyCacheCreator<QQmlTypeCompiler>::buildMetaObjectsIncrementally (this=0x7f9f90bf80d0) at /usr/include/c++/14/bits/stl_iterator.h:1114
#2  QQmlTypeCompiler::compile (this=0x7f9f90bf8380) at /usr/src/debug/qtdeclarative-everywhere-src-6.9.0/src/qml/qml/qqmltypecompiler.cpp:63
#3  0x00007f9fb67b74d0 in QQmlTypeData::compile (this=0x556d578bbcd0, typeNameCache=..., resolvedTypeCache=0x7f9f90bf82b8, dependencyHasher=...) at /usr/src/debug/qtdeclarative-everywhere-src-6.9.0/src/qml/qml/qqmltypedata.cpp:886
#4  QQmlTypeData::done (this=<optimized out>) at /usr/src/debug/qtdeclarative-everywhere-src-6.9.0/src/qml/qml/qqmltypedata.cpp:544
#5  0x00007f9fb66ed61b in QQmlDataBlob::tryDone (this=0x556d578bbcd0) at /usr/src/debug/qtdeclarative-everywhere-src-6.9.0/src/qml/qml/qqmldatablob.cpp:512
#6  QQmlDataBlob::tryDone (this=0x556d578bbcd0) at /usr/src/debug/qtdeclarative-everywhere-src-6.9.0/src/qml/qml/qqmldatablob.cpp:502
#7  0x00007f9fb67c4d00 in QQmlTypeLoader::setData (this=this@entry=0x556d56fe73e0, blob=..., d=...) at /usr/src/debug/qtdeclarative-everywhere-src-6.9.0/src/qml/qml/qqmltypeloader.cpp:442
#8  0x00007f9fb67c5ace in QQmlTypeLoader::setData (this=0x556d56fe73e0, blob=..., fileName=...) at /usr/src/debug/qtdeclarative-everywhere-src-6.9.0/src/qml/qml/qqmltypeloader.cpp:420
#9  0x00007f9fb67be91d in QQmlTypeLoader::loadThread (this=0x556d56fe73e0, blob=...) at /usr/src/debug/qtdeclarative-everywhere-src-6.9.0/src/qml/qml/qqmltypeloader.cpp:278
#10 0x00007f9fb67ce6e9 in QQmlThread::createMessageFromMethod<void (QQmlTypeLoaderThread::*)(QQmlRefPointer<QQmlDataBlob> const&), QQmlRefPointer<QQmlDataBlob> const&>(void (QQmlTypeLoaderThread::*&&)(QQmlRefPointer<QQmlDataBlob> const&), QQmlRefPointer<QQmlDataBlob> const&)::I::call(QQmlThread*) () at /usr/include/c++/14/bits/invoke.h:71
#11 0x00007f9fb68471bd in QQmlThreadPrivate::threadEvent (this=0x556d57060960) at /usr/src/debug/qtdeclarative-everywhere-src-6.9.0/src/qml/qml/ftw/qqmlthread_impl.cpp:144
#12 QQmlThreadPrivate::event (this=0x556d57060960, e=0x556d57896220) at /usr/src/debug/qtdeclarative-everywhere-src-6.9.0/src/qml/qml/ftw/qqmlthread_impl.cpp:101
#13 0x00007f9fb73e142a in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x556d57060960, e=0x556d57896220) at /usr/src/debug/qtbase-everywhere-src-6.9.0/src/widgets/kernel/qapplication.cpp:3301
#14 0x00007f9fb51b75e8 in QCoreApplication::notifyInternal2 (receiver=0x556d57060960, event=0x556d57896220) at /usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/kernel/qcoreapplication.cpp:1106
#15 0x00007f9fb51b762d in QCoreApplication::sendEvent (receiver=<optimized out>, event=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/kernel/qcoreapplication.cpp:1546
#16 0x00007f9fb51b79a7 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x556d5701dd70) at /usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/kernel/qcoreapplication.cpp:1879
#17 0x00007f9fb541c047 in postEventSourceDispatch (s=s@entry=0x7f9f54000f20) at /usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/kernel/qeventdispatcher_glib.cpp:246
#18 0x00007f9fb3fae678 in g_main_dispatch (context=0x7f9f54000c60) at ../glib/gmain.c:3398
#19 g_main_context_dispatch_unlocked (context=context@entry=0x7f9f54000c60) at ../glib/gmain.c:4249
#20 0x00007f9fb3fb03d8 in g_main_context_iterate_unlocked (context=context@entry=0x7f9f54000c60, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4314
#21 0x00007f9fb3fb0bec in g_main_context_iteration (context=0x7f9f54000c60, may_block=1) at ../glib/gmain.c:4379
#22 0x00007f9fb541a013 in QEventDispatcherGlib::processEvents (this=0x7f9f54000b70, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/kernel/qeventdispatcher_glib.cpp:399
#23 0x00007f9fb51c24db in QEventLoop::exec (this=0x7f9f90bf8a20, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/global/qflags.h:77
#24 0x00007f9fb52afbdc in QThread::exec (this=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/global/qflags.h:77
#25 0x00007f9fb532c22a in operator() (__closure=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/thread/qthread_unix.cpp:433
#26 (anonymous namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()> > (t=...) at /usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/thread/qthread_unix.cpp:365
#27 QThreadPrivate::start (arg=0x556d57060960) at /usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/thread/qthread_unix.cpp:393
#28 0x00007f9fb4899546 in start_thread (arg=<optimized out>) at pthread_create.c:448
#29 0x00007f9fb491d94c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
(gdb)

Yes, thanks a lot!

This has a stacktrace very similar to the ones collected in 463648. Unfortunately, we're a bit stumped on that one - it seems to affect some users, but is overall rather rare (it's been around for a long time), and the causes are unclear. It might be an upstream issue, as it doesn't seem to directly touch KDE code (though with qml-related things it's often hard to say exactly).

One user in that bug report seems to suggest that a broken qml cache may be relevant. You could try renaming the .cache directory in your home directory, and restarting the system to see if this helps.

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