Bug 474489 - Merkuro Calendar crashes when trying to edit a calendar source
Summary: Merkuro Calendar crashes when trying to edit a calendar source
Status: REPORTED
Alias: None
Product: Merkuro
Classification: Applications
Component: general (show other bugs)
Version: 23.08.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Claudio Cambra
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-09-13 14:02 UTC by aronkvh
Modified: 2023-09-13 17:49 UTC (History)
2 users (show)

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


Attachments
New crash information added by DrKonqi (77.56 KB, text/plain)
2023-09-13 14:02 UTC, aronkvh
Details

Note You need to log in before you can comment on or make changes to this bug.
Description aronkvh 2023-09-13 14:02:24 UTC
Application: merkuro-calendar (23.08.0)

Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.2.0-26-generic x86_64
Windowing System: Wayland
Distribution: KDE neon 5.27
DrKonqi: 5.27.7 [CoredumpBackend]

-- Information about the crash:
1. Google calendar doesn't sync
2. right click the calendar name
3. click edit calendar source
4. crash

The crash can be reproduced every time.

-- Backtrace (Reduced):
#6  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139649901474304) at ./nptl/pthread_kill.c:44
#7  __pthread_kill_internal (signo=6, threadid=139649901474304) at ./nptl/pthread_kill.c:78
#8  __GI___pthread_kill (threadid=139649901474304, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#9  0x00007f02d6242476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#10 0x00007f02d62287f3 in __GI_abort () at ./stdlib/abort.c:79


Reported using DrKonqi
This report was filed against 'kde' because the product 'merkuro-calendar' could not be located in Bugzilla. Add it to drkonqi's mappings file!
Comment 1 aronkvh 2023-09-13 14:02:25 UTC
Created attachment 161603 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 aronkvh 2023-09-13 17:49:50 UTC
It's actually not reproducible anymore after a reboot