Bug 508427

Summary: Korganizer crashes when creating event/journal/to do
Product: [Applications] korganizer Reporter: phenrypereira <ordep.henrique.pereira>
Component: recurrenceAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: winter
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: KDE Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description phenrypereira 2025-08-18 15:38:04 UTC
***
phenry@a320mh:~$ korganizer
beginResetModel called on Akonadi::TodoModel(0x5ec9b182cee0, name = "TodoModel") without calling endResetModel first
beginResetModel called on QIdentityProxyModel(0x5ec9b1b15880) without calling endResetModel first
beginResetModel called on TodoViewSortFilterProxyModel(0x5ec9b1b12e60) without calling endResetModel first
endResetModel called on Akonadi::TodoModel(0x5ec9b182cee0, name = "TodoModel") without calling beginResetModel first
endResetModel called on QIdentityProxyModel(0x5ec9b1b15880) without calling beginResetModel first
endResetModel called on TodoViewSortFilterProxyModel(0x5ec9b1b12e60) without calling beginResetModel first
org.kde.pim.pimcommonactivities: Plasma activities is not running:  1
org.kde.pim.incidenceeditor: Faulty editor was  "IncidenceAttendee"
org.kde.pim.incidenceeditor: Incidence  "062ee3d7-3843-474b-9eda-57cf496daf14"
ASSERT failure in load: "editor shouldn't be dirty", file ./src/combinedincidenceeditor.cpp, line 93
KCrash: Application 'korganizer' crashing... crashRecursionCounter = 2
Abortado (imagem do nĂșcleo gravada)
phenry@a320mh:~$ 

***

SUMMARY


STEPS TO REPRODUCE
1. Open Korganizer
2.  Click on Create Event/Journal/To Do

OBSERVED RESULT
Korganizer Immediately crashes (close main window)

EXPECTED RESULT
See a new window to set up event/journal/to do

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: stable/user edition
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17
Qt Version: 6.9.1

ADDITIONAL INFORMATION
Comment 1 Allen Winter 2025-08-18 15:45:08 UTC

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