Bug 463300

Summary: Kalendar crashing out of the blue
Product: [Applications] Merkuro Reporter: Riccardo Robecchi <sephiroth_pk>
Component: generalAssignee: Claudio Cambra <claudio.cambra>
Status: RESOLVED DUPLICATE    
Severity: crash CC: carl
Priority: NOR Keywords: drkonqi
Version First Reported In: 22.12.0   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description Riccardo Robecchi 2022-12-21 09:14:34 UTC 
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 just crashed out of the blue while open in the background. It is unclear what prompted the crash and how to reproduce (if it is possible).

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#7  0x00007f7aa54f40f4 in QtPrivate::QSlotObjectBase::call (a=0x7fff76669470, r=0x5634ebaeed10, this=0x5634eb0679f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8  doActivate<false> (sender=0x5634ea04fac0, signal_index=3, argv=0x7fff76669470) at kernel/qobject.cpp:3919
[...]
#10 0x00007f7aa5454b79 in QAbstractItemModel::dataChanged (this=this@entry=0x5634ea04fac0, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557
#11 0x00007f7aa54915c1 in QSortFilterProxyModelPrivate::_q_sourceDataChanged (this=0x5634e9f6daf0, source_top_left=..., source_bottom_right=..., roles=...) at itemmodels/qsortfilterproxymodel.cpp:1539
#12 0x00007f7aa54f4128 in doActivate<false> (sender=0x5634ea0db2f0, signal_index=3, argv=0x7fff76669720) at kernel/qobject.cpp:3931


Reported using DrKonqi
Comment 1 Riccardo Robecchi 2022-12-21 09:14:35 UTC 
Created attachment 154724 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Carl Schwan 2023-02-19 12:03:33 UTC 

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