Application: kalendar (22.12.0) Qt Version: 5.15.7 Frameworks Version: 5.101.0 Operating System: Linux 6.1.0-x64v2-xanmod1 x86_64 Windowing System: X11 Distribution: KDE neon 5.26 DrKonqi: 5.26.4 [CoredumpBackend] -- Information about the crash: Kalendar crashed while sitting idle in the background. No action was taken as the computer was completely idle. After the crash, I started Kalendar again, but it stopped showing available calendars, despite them being correctly reported in the "accounts" section. I then closed it to see if starting it again would fix the issue, but then it wouldn't start again. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 0x00007fe07999af95 in std::__atomic_base<int>::operator-- (this=0x0) at /usr/include/c++/11/bits/atomic_base.h:385 #7 QAtomicOps<int>::deref<int> (_q_value=<error reading variable: Cannot access memory at address 0x0>) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:289 [...] #9 QDateTime::Data::operator= (other=..., other=..., this=0x55d83d0b2518) at time/qdatetime.cpp:3411 #10 QDateTime::operator= (this=0x55d83d0b2518, other=...) at time/qdatetime.cpp:3791 [...] #12 0x00007fe079af40f4 in QtPrivate::QSlotObjectBase::call (a=0x7fff2b7f7bd0, r=0x55d83b811ee0, this=0x55d83b4d3010) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 Reported using DrKonqi
Created attachment 154840 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Created attachment 155132 [details] Second backtrace Here's another one.
Created attachment 155177 [details] Third backtrace (22.12.1) Here's another one. The interesting bit is that in the meantime I have updated Kalendar to version 22.12.1.
Created attachment 156097 [details] Crash with Kalendar 22.12.2 Uploading new crash as it's related to the new version (and I don't know if there were any changes).
*** This bug has been marked as a duplicate of bug 466063 ***