You are not logged in.
I've just updated to the Merkuro suite that replaces Kalendar, and I've been excited to try it. Merkuro Mail is a great application for me who doesn't need all the bells and whistles of KMail, and laments the lack of a tray icon function in Thunderbird.
Anyways, while Merkuro Mail and Contacts work fine, Merkuro Calendar segfaults on launch. This is the terminal output when I start it with Konsole:
merkuro-calendar
qrc:/BasicMonthListView.qml:22:5: Required property startDate was not initialized
qrc:/MainDrawerToggleButton.qml:25: TypeError: Cannot read property 'collapsed' of undefined
qrc:/MainDrawerToggleButton.qml:14: TypeError: Cannot read property 'collapsed' of undefined
qrc:/MainDrawerToggleButton.qml:11: TypeError: Cannot read property 'mainDrawer' of undefined
30 -- exe=/usr/bin/merkuro-calendar
17 -- platform=wayland
25 -- appname=merkuro-calendar
17 -- apppath=/usr/bin
10 -- signal=11
9 -- pid=5205
19 -- appversion=23.08.0
29 -- programname=Merkuro Calendar
31 -- bugaddress=submit@bugs.kde.org
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = merkuro-calendar path = /usr/bin pid = 5205
KCrash: Arguments: /usr/bin/merkuro-calendar
KCrash: Attempting to start /usr/lib/drkonqi
kf5idletime_wayland: This plugin does not support polling idle time
[1]+ Stopped merkuro-calendarThis happens in both X11 and Wayland, English and Norwegian locale.
It works fine when I downgrade back to the pre-Merkuro release, however, I would like to keep using Merkuro Mail; but I rely more on Kalendar, so if I can't use Merkuro Calendar I've no choice but to downgrade.
I have already reported the issue to the developers here, and I attached backtraces in there as well: https://bugs.kde.org/show_bug.cgi?id=473618
What I'm mostly wondering is, does anyone else have this issue, and have you found a workaround perhaps?
Thanks in advance!
Cheers,
Aurora
Last edited by ridge (2023-08-27 22:34:35)
Offline
does anyone else have this issue
Hi, yes same issue even with new user account on a wayland session.
Offline
Hi, yes same issue even with new user account on a wayland session.
A fix has been merged! ![]()
https://invent.kde.org/pim/merkuro/-/co … f00fbf4633
Offline
It is still crashing with a segmentation fault
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/globaltoolbar/ToolBarPageHeader.qml:32:9: QML Loader (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth"
Speicherzugriffsfehler (Speicherabzug geschrieben)Offline
It is also an already known bug (https://bugs.kde.org/show_bug.cgi?id=472793).
Why is an app that is still that faulty pushed to extra?
Offline
It is also an already known bug (https://bugs.kde.org/show_bug.cgi?id=472793).
Why is an app that is still that faulty pushed to extra?
Because it is not Arch's job to fix upstream bugs.
Offline
It is still crashing with a segmentation fault
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/globaltoolbar/ToolBarPageHeader.qml:32:9: QML Loader (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" Speicherzugriffsfehler (Speicherabzug geschrieben)
Well, the error is fixed in 23.08.1: https://bugs.kde.org/show_bug.cgi?id=473618
The version in the repos is 23.08.0-2
As a workaround you can start with `LANGUAGE=C merkuro-calendar`and it should run just fine.
If $LANG is not set on your system add it as well, e.g. `LANG=de_DE.UTF-8 LANGUAGE=C merkuro-calendar`
Offline
Well, the error is fixed in 23.08.1: https://bugs.kde.org/show_bug.cgi?id=473618
The version in the repos is 23.08.0-2
Which already includes the fix for https://bugs.kde.org/show_bug.cgi?id=473618 see https://gitlab.archlinux.org/archlinux/ … ea3ea4dec8
What did you find 23.08.1? https://invent.kde.org/pim/merkuro/-/tags
Offline
tOmAtE wrote:Well, the error is fixed in 23.08.1: https://bugs.kde.org/show_bug.cgi?id=473618
The version in the repos is 23.08.0-2
Which already includes the fix for https://bugs.kde.org/show_bug.cgi?id=473618 see https://gitlab.archlinux.org/archlinux/ … ea3ea4dec8
What did you find 23.08.1? https://invent.kde.org/pim/merkuro/-/tags
The issue clearly says it will be fixed in 23.08.1 (see Version Fixed in). The linked commit is from August 27th. The Tag for release 28.08.0 is from August 17th... so everything after that will be in a new version, not? IMHO the commit is not in Version 23.08.0
And the bug still happens on my system with 23.08.0-2 installed, and the workaround is still working.
Offline
loqs wrote:tOmAtE wrote:Well, the error is fixed in 23.08.1: https://bugs.kde.org/show_bug.cgi?id=473618
The version in the repos is 23.08.0-2
Which already includes the fix for https://bugs.kde.org/show_bug.cgi?id=473618 see https://gitlab.archlinux.org/archlinux/ … ea3ea4dec8
What did you find 23.08.1? https://invent.kde.org/pim/merkuro/-/tagsThe issue clearly says it will be fixed in 23.08.1 (see Version Fixed in). The linked commit is from August 27th. The Tag for release 28.08.0 is from August 17th... so everything after that will be in a new version, not?
Well, the error is fixed in 23.08.1
Note the different tense you used compared to tOmAtE.
IMHO the commit is not in Version 23.08.0
And the bug still happens on my system with 23.08.0-2 installed, and the workaround is still working.
The work around from https://bugs.kde.org/show_bug.cgi?id=472793 which is not marked as fixed and not mentioned in https://bugs.kde.org/show_bug.cgi?id=473618 which is already addressed in 23.08.0-2?
Offline
And the bug still happens on my system with 23.08.0-2 installed, and the workaround is still working.
No, the bug doesn't happen, a different bug happens. You are mixing them up.
Offline