https://bugs.kde.org/show_bug.cgi?id=512918
John <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from John <[email protected]> --- (In reply to Carl Schwan from comment #1) > Do you have a backtrace for the crash? > > You should be able to get one with coredumpctl debug merkuro-calendar Sorry for not knowing to to provide a backtrace. I tried in the past to learn, but I could never follow that tutorial until the end with success. That command gives me this output: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No match found. And with sudo this output: [sudo] password for john: No match found. And in both cases the "No match found." is in a dark red color. Merkuro Calendar dosn't open, if this command was supposed to also open with some debug turned on. If it was supposed to show info about last crash... It seems that the new event opens that pop-up window again, but the event is not added to the calendar after clicking the Add button. And the new task makes it crash immediately. (1-2 seconds delay after the click) BTW, the program is now at version: 25.08.3 I don't know how to check the version of Akonadi, if the program is using that. As a few things were updated (got into the testing repository): https://tracker.debian.org/pkg/merkuro https://tracker.debian.org/pkg/akonadi -- You are receiving this mail because: You are watching all bug changes.
