| Summary: | KOrganizer crashed on creating a new task | ||
|---|---|---|---|
| Product: | [Applications] korganizer | Reporter: | Jim <compositr> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | dvratil, gjditchfield |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Jim
2022-10-17 07:10:54 UTC
Can you install debugging symbols, to get line numbers where the crash happens? Does KOrganizer print anything useful to stderr when it crashes? Is Akonadi running? What calendar did you create the event in? If you launch akonadiconsole, does it show the events? (In reply to gjditchfield from comment #1) > Can you install debugging symbols, to get line numbers where the crash > happens? > > Does KOrganizer print anything useful to stderr when it crashes? > > Is Akonadi running? > > What calendar did you create the event in? > > If you launch akonadiconsole, does it show the events? Alright, I'll build korganizer w/ debug symbols once I have some spare time. Weirdly enough, this crash only happens if I launch KOrganizer through the plasma application launcher (which provides a single parameter "%U"). If I start KOrganizer from the console, it works perfectly fine (although previously created repeating events through CalDAV still don't show up) Akonadi is running. I created the event in a Nextcloud calendar which syncs through the WebDAV resource feature to KOrganizer. The events are nowhere to be found in akonaid console, and they don't sync w/ nextcloud's web-based calendar. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! see my other comment for info Hi, if you can still reproduce the issue, could you please try to obtain a full backtrace of the crash? It should no longer be necessary to build KOrganizer yourself, ArchLinux now offers debug symbols as well. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |