Bug 515454 - Crash on startup
Summary: Crash on startup
Status: NEEDSINFO BACKTRACE
Alias: None
Product: Merkuro
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.12.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Carl Schwan
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-02-03 11:41 UTC by Samuele
Modified: 2026-02-04 18:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Merkuro not opening with various attempts (312.29 KB, video/webm)
2026-02-03 11:41 UTC, Samuele
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Samuele 2026-02-03 11:41:50 UTC
Created attachment 189181 [details]
Merkuro not opening with various attempts

SUMMARY
I don't know if the message in the title is relevant to the crash: in other bug reports I see that it could just be a message of QT when the program stops.
What happens is that I cannot open Merkuro Calendar and the only output I see when trying to launch it from terminal is this:
```
QThreadStorage: entry 3 destroyed before end of thread 0x55f5f497f510
QThreadStorage: entry 2 destroyed before end of thread 0x55f5f497f510
```
The same output every attempt.

STEPS TO REPRODUCE
1. Open Merkuro Calendar

OBSERVED RESULT
The program doens't start

EXPECTED RESULT
I should see the UI opening

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.6-200.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-2400 CPU @ 3.10GHz
Memory: 16 GiB of RAM (15.4 GiB usable)
Graphics Processor: llvmpipe
Manufacturer: LENOVO
Product Name: 7052A9G
System Version: ThinkCentre M91p
Qt Version:
Comment 1 Samuele 2026-02-03 11:43:25 UTC
To be precise, the version of Merkuro is 25.12.1-1.fc43, and is not installed through Flatpak: I just found it in Discover without any other option.
Comment 2 Tobias Fella 2026-02-04 09:11:41 UTC
Please attach a backtrace for the crash; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports for how to do that. Thanks!
Comment 3 Samuele 2026-02-04 18:39:37 UTC
Now it's not happening and it's not a crash of the sort that would open DrKonqi: it was more of a silent crash. Maybe a reboot was enough to solve, but I'm not able to give any more information, so maybe we should close this.