Bug 468353

Summary:	Kalendar crashes when I double-click to create a new event
Product:	[Applications] Merkuro	Reporter:	DodoLeDev <N3verG0nnaGiveYouUp+kdeBugs>
Component:	general	Assignee:	Claudio Cambra <claudio.cambra>
Status:	CONFIRMED ---
Severity:	crash	CC:	akhtaboot, carl, florianmey
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	22.12.3
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	full backtrace

Description DodoLeDev 2023-04-10 13:17:00 UTC

Application: kalendar (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.9-arch1-1 x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 5.27.3 [KCrashBackend]

-- Information about the crash:
After opening Kalendar, in order to create a new event, I double-clicked on an empty space in the week view.
After that, the app crashed.
When I wanted to relaunch the app, Kalendar crashed at startup.
Then, it started to work normally again (No crash at startup, ability to add a new event with double click...).

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kalendar (kalendar), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fbd30b1da63 in QHashData::rehash(int) (this=this@entry=0x558551c61980, hint=11) at tools/qhash.cpp:681
#5  0x00007fbd3111e516 in QHashData::willGrow() (this=<optimized out>, this=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qhash.h:104
#6  QHash<QObject*, unsigned int>::insert(QObject* const&, unsigned int const&) (avalue=<synthetic pointer>: <optimized out>, akey=<synthetic pointer>: <optimized out>, this=0x558551c42ff0) at ../../include/QtCore/../../src/corelib/tools/qhash.h:775
#7  QAccessibleCache::insert(QObject*, QAccessibleInterface*) const (this=0x558551c42fd0, object=object@entry=0x558557770540, iface=iface@entry=0x558557783a60) at accessible/qaccessiblecache.cpp:124
#8  0x00007fbd3111e6f9 in QAccessible::queryAccessibleInterface(QObject*) (object=0x558557770540) at accessible/qaccessible.cpp:732
#9  0x00007fbd3111efd6 in QAccessibleEvent::accessibleInterface() const (this=0x7fffbf852450) at accessible/qaccessible.cpp:1784
#10 0x00007fbd3111ac05 in QAccessible::updateAccessibility(QAccessibleEvent*) (event=0x7fffbf852450) at accessible/qaccessible.cpp:882
#11 0x00007fbd328d0c71 in QQuickAccessibleAttached::QQuickAccessibleAttached(QObject*) (this=0x5585577886a0, parent=0x558557770540, this=<optimized out>, parent=<optimized out>) at /usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickaccessibleattached.cpp:349
#12 0x00007fbd328d1147 in QQuickAccessibleAttached::qmlAttachedProperties(QObject*) (obj=0x558557770540) at /usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickaccessibleattached.cpp:434
#13 0x00007fbd32235b1e in QtQml::resolveAttachedProperties(QQmlAttachedPropertiesFunc, QQmlData*, QObject*, bool) (pf=0x7fbd328d1120 <QQuickAccessibleAttached::qmlAttachedProperties(QObject*)>, data=0x558557770560, object=0x558557770540, create=<optimized out>) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlengine.cpp:1627
#14 0x00007fbd322a2a67 in QV4::QQmlTypeWrapper::virtualGet(QV4::Managed const*, QV4::PropertyKey, QV4::Value const*, bool*) (m=0x7fbd101bd990, id=..., receiver=0x7fbd101bd990, hasProperty=0x0) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypewrapper.cpp:264
#15 0x00007fbd3211ee2c in QV4::Lookup::getterFallback(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value const&) (l=0x558551d832e0, engine=0x558551a0b6a0, object=<optimized out>) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4lookup.cpp:231
#16 0x00007fbcacd1e3d5 in  ()
#17 0x00007fffbf8527d0 in  ()
#18 0x0000000000000000 in  ()
[Inferior 1 (process 4618) detached]

The reporter indicates this bug may be a duplicate of or related to bug 468031.

Reported using DrKonqi

Comment 1 akhtaboot 2025-12-11 21:28:55 UTC

Created attachment 187534 [details]
full backtrace

Comment 2 akhtaboot 2025-12-11 21:34:37 UTC

(In reply to akhtaboot from comment #1)
> Created attachment 187534 [details]
> full backtrace

I am encountering the exact same issue, only reporting it now, but I was hitting this months back
Double clicking on an empty space or "Create -> New Event" or "Create -> New Task" will trigger this, I can reproduce everytime

=== INFO ===
Merkuro Calendar: 25.08.3
NixOS 26.05 (Yarara) (Wayland)
KDE Frameworks: 6.20.0
Qt: Using 6.10.1 and built against 6.10.1
Unknown/Default
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.18.0

=====

Comment 3 akhtaboot 2025-12-12 07:05:54 UTC

(In reply to akhtaboot from comment #2)
> (In reply to akhtaboot from comment #1)
> > Created attachment 187534 [details]
> > full backtrace
> 
> I am encountering the exact same issue, only reporting it now, but I was
> hitting this months back
> Double clicking on an empty space or "Create -> New Event" or "Create -> New
> Task" will trigger this, I can reproduce everytime
> 
> === INFO ===
> Merkuro Calendar: 25.08.3
> NixOS 26.05 (Yarara) (Wayland)
> KDE Frameworks: 6.20.0
> Qt: Using 6.10.1 and built against 6.10.1
> Unknown/Default
> Build ABI: x86_64-little_endian-lp64
> Kernel: linux 6.18.0
> 
> =====

After some more testing, the issue is only encountered if a Caldav calendar is actually configured

Comment 4 Carl Schwan 2025-12-12 17:30:16 UTC

Confirmed on master. I will take a look at it in the next few days

Comment 5 Carl Schwan 2025-12-12 17:32:13 UTC

*** Bug 513209 has been marked as a duplicate of this bug. ***