Bug 460569 - KOrganizer crashed on creating a new task
Summary: KOrganizer crashed on creating a new task
Status: RESOLVED WORKSFORME
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-10-17 07:10 UTC by Jim
Modified: 2023-12-12 03:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim 2022-10-17 07:10:54 UTC
Application: korganizer (5.21.2 (22.08.2))

Qt Version: 5.15.6
Frameworks Version: 5.99.0
Operating System: Linux 5.19.13-arch1-1 x86_64
Windowing System: X11
Distribution: Arch Linux
DrKonqi: 5.26.0 [KCrashBackend]

-- Information about the crash:
KOrganizer refuses to create a repeating event and crashes when creating a repeating event.
If I create a repeating event in another app and sync it with KOrganizer through CalDAV, the event does not show up, and I am unable to create subsequent events without it crashing.

The crash can be reproduced every time.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fe0c5148aaf in ?? () from /usr/lib/libKF5AkonadiCalendar.so.5
#5  0x00007fe0c5149c77 in ?? () from /usr/lib/libKF5AkonadiCalendar.so.5
#6  0x00007fe0c5d8a520 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#7  0x00007fe0c67dab1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#8  0x00007fe0c5d66b88 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#9  0x00007fe0c5d67693 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#10 0x00007fe0c5dad728 in ?? () from /usr/lib/libQt5Core.so.5
#11 0x00007fe0c35ad81b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#12 0x00007fe0c3603ec9 in ?? () from /usr/lib/libglib-2.0.so.0
#13 0x00007fe0c35ac0d2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#14 0x00007fe0c5db150c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#15 0x00007fe0c5d5f32c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#16 0x00007fe0c5d69e59 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#17 0x000055c218d42be8 in ?? ()
#18 0x00007fe0c56bd290 in ?? () from /usr/lib/libc.so.6
#19 0x00007fe0c56bd34a in __libc_start_main () from /usr/lib/libc.so.6
#20 0x000055c218d43065 in ?? ()
[Inferior 1 (process 1988820) detached]

Reported using DrKonqi
Comment 1 gjditchfield 2022-10-17 17:16:03 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?
Comment 2 Jim 2022-10-18 06:12:42 UTC
(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.
Comment 3 Bug Janitor Service 2022-11-02 05:05:49 UTC
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!
Comment 4 Jim 2022-11-02 08:17:00 UTC
see my other comment for info
Comment 5 Daniel Vrátil 2023-11-12 10:24:22 UTC
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.
Comment 6 Bug Janitor Service 2023-11-27 03:45:47 UTC
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!
Comment 7 Bug Janitor Service 2023-12-12 03:46:03 UTC
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!