SUMMARY Cannot create new event or new task by right clicking on a date. Using the "create" button at the top right of the window works, but not right clicking the date. STEPS TO REPRODUCE 1. Right click a date and choose new task OBSERVED RESULT Nothing happens after clicking New task. EXPECTED RESULT New task dialogue window with date prepopulated with the selected date SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.3 Kernel Version: 6.10.10-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7700X 8-Core Processor Memory: 30.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Manufacturer: ASUS
If you launch merkuro-calendar from the terminal, the standard error when making the new task is as follows: qt.qml.context: qrc:/DayGridView.qml:401:37 Parameter "type" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead. qrc:/DayGridView.qml:394: TypeError: Property 'setUpAdd' of object CalendarUiUtils_QMLTYPE_0(0x6270189cee00) is not a function
This error reproduces on an Arch Linux virtual machine in windows as well as on my baremetal arch linux system
Can confirm this problem on Manjaro Linux: Operating System: Manjaro Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.6.52-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-8600K CPU @ 3.60GHz Memory: 31.2 GiB of RAM Graphics Processor: AMD Radeon RX 6800 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B46 System Version: 1.0
Same here on Neon. This is quite a major bug in an application which is meant to manage events, I am surprised it is still there after six months. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2
*** Bug 500142 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 492820 ***