https://bugs.kde.org/show_bug.cgi?id=449068

--- Comment #15 from Claudio Cambra <claudio.cam...@gmail.com> ---
(In reply to Samuele from comment #14)
> Created attachment 146107 [details]
> New crash information added by DrKonqi
> 
> kalendar (0.4.0) using Qt 5.15.3
> 
> Ok now all subtasks are expanded, without an option to make them collapsed
> by deafault, but this is clearly not important now.
> Going from "All tasks" to a specific calendar is not a problem anymore. I
> mean, the problem appeared expanding a task in its subtasks, but now it's
> all expanded; we can say that doiing the reverse (collapsing a task and
> selecting a specific calendar) doesn't create issues.
> The same with going from a calendar to another calendar: no issue anymore.
> But...
> 
> - What I was doing when the application crashed:
> I managed to make it crash collapsing all the tasks in a specific calendar
> and changing calendar. i tried with the green calendar and it didn't happen;
> I don't know if it's related to calendar with more than a few tasks.
> You can see it happen here:
> https://nextcloud.samuelezappala.it/s/oTWSRsZQTSeP2BL
> 
> -- Backtrace (Reduced):
> #4  0x00007feffe6fe2fc in KDescendantsProxyModel::mapFromSource
> (this=0x561221316590, sourceIndex=...) at
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qmap.h:488
> #5  0x00007feffe7018ab in KDescendantsProxyModelPrivate::sourceRowsInserted
> (this=0x561221309760, parent=..., start=0, end=17) at
> ./src/core/kdescendantsproxymodel.cpp:802
> #6  0x00007feffcafa19e in QtPrivate::QSlotObjectBase::call
> (a=0x7fffde901de0, r=0x561221316590, this=0x56122137dcf0) at
> ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
> #7  doActivate<false> (sender=0x561221318ae0, signal_index=13,
> argv=0x7fffde901de0) at kernel/qobject.cpp:3886
> [...]
> #9  0x00007feffca650b2 in QAbstractItemModel::rowsInserted
> (this=this@entry=0x561221318ae0, _t1=..., _t2=<optimized out>,
> _t3=<optimized out>, _t4=...) at .moc/moc_qabstractitemmodel.cpp:592

Thank you for your patience and your dedication, it is seriously helpful.

I've added a new and improved fix that should, fingers crossed, retain the
prior behaviour of collapsed tasks by default while still preventing the
crashing, including in the case you provided above.

Could you try the latest commit? Thanks again!

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to