Bug 515497

Summary: Merkuro segfaults when deleting all occurrences of a particular recurring event
Product: [Applications] Merkuro Reporter: hadrienpelissier
Component: generalAssignee: Carl Schwan <carl>
Status: REPORTED ---    
Severity: crash CC: claudio.cambra
Priority: NOR    
Version First Reported In: 25.12.1   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: backtrace in gdb
backtrace unrelated bug same event

Description hadrienpelissier 2026-02-04 11:40:40 UTC
Created attachment 189204 [details]
backtrace in gdb

SUMMARY


STEPS TO REPRODUCE
1. Open Merkuro
2. Delete my recurring event
3. Segfault

OBSERVED RESULT


EXPECTED RESULT
Delete the event

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.0-rc5-1-git-00036-g4427259cc7f7 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
Seems like an infinite loop. See backtrace.

Only visible logs prior to deleting:
 kirigamiaddons/components/ConvergentContextMenu.qml:274:9: QML ActionsMenu: cannot show menu: parent is null
qt.qml.context: qrc:/qt/qml/org/kde/merkuro/calendar/qml/MainViews/BasicInternalHourlyView.qml:991:45 Parameter "incidencePtr" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead.

Thread 1 "merkuro-calenda" received signal SIGSEGV, Segmentation fault.
Comment 1 hadrienpelissier 2026-02-04 11:58:52 UTC
I cannot extract the original event as it got deleted, but a second bug appears when I try to open that event for Edition.
It seems it comes from a franken-event  because when I recreate a new recurring one from Etar it is synced and I can edit it and delete it correctly. Prior to deleting it, editing it would result in another crash I can upload the backtrace if needed.

I no longer rely on it to be fixed so if you believe it's not important feel free to close.
Comment 2 hadrienpelissier 2026-02-04 12:17:20 UTC
Created attachment 189205 [details]
backtrace unrelated bug same event