Bug 456216 - KReminder crashes randomly
Summary: KReminder crashes randomly
Status: RESOLVED WORKSFORME
Alias: None
Product: Merkuro
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Claudio Cambra
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-07-01 18:32 UTC by Bob Mattes
Modified: 2023-02-06 19:03 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bob Mattes 2022-07-01 18:32:43 UTC
Application: kalendarac (5.20.2)

Qt Version: 5.15.2
Frameworks Version: 5.95.0
Operating System: Linux 5.18.6-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.25.1 [KCrashBackend]

-- Information about the crash:
Usually the computer is idling when a reminder comes up from KCalendar, then I get the dialog that Reminder crashed. It always restarts without issues. Happens once or twice a day since about 28 June or so, maybe a day earlier.

The crash can be reproduced every time.

-- Backtrace:
Application: Reminders (kalendarac), signal: Aborted

[KCrash Handler]
#4  0x00007fd2800af6bc in __pthread_kill_implementation () from /lib64/libc.so.6
#5  0x00007fd28005c6f6 in raise () from /lib64/libc.so.6
#6  0x00007fd280045814 in abort () from /lib64/libc.so.6
#7  0x00007fd28053f0cd in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5
#8  0x00007fd27f2c8046 in ?? () from /lib64/libQt5Widgets.so.5
#9  0x00007fd27f4d88cc in QDialog::QDialog(QWidget*, QFlags<Qt::WindowType>) () from /lib64/libQt5Widgets.so.5
#10 0x00007fd27f94907f in KMessageBox::sorry(QWidget*, QString const&, QString const&, QFlags<KMessageBox::Option>) () from /lib64/libKF5WidgetsAddons.so.5
#11 0x00007fd2817848da in ?? () from /lib64/libKF5AkonadiCalendar.so.5
#12 0x00007fd28078b490 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#13 0x00007fd28075fce8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#14 0x00007fd280762c81 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5
#15 0x00007fd2807b7903 in ?? () from /lib64/libQt5Core.so.5
#16 0x00007fd27e199ea0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#17 0x00007fd27e19a258 in ?? () from /lib64/libglib-2.0.so.0
#18 0x00007fd27e19a2ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#19 0x00007fd2807b7106 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#20 0x00007fd28075e75b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#21 0x00007fd2807668c6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#22 0x00005637255af4d5 in ?? ()
#23 0x00007fd2800465b0 in __libc_start_call_main () from /lib64/libc.so.6
#24 0x00007fd280046679 in __libc_start_main_impl () from /lib64/libc.so.6
#25 0x00005637255afad5 in ?? ()
[Inferior 1 (process 2104) detached]

Reported using DrKonqi
Comment 1 Carl Schwan 2023-02-06 17:01:31 UTC
Hi,

It seems this bug report is missing some important backtrace information. Could you please install the missing debug symbols package, reproduce the bug, and generate a new backtrace? (https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports)

Thanks for reporting bugs.
Cheers,
Carl
Comment 2 Bob Mattes 2023-02-06 17:23:07 UTC
(In reply to Carl Schwan from comment #1)
> Hi,
> 
> It seems this bug report is missing some important backtrace information.
> Could you please install the missing debug symbols package, reproduce the
> bug, and generate a new backtrace?
> (https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports)
> 
> Thanks for reporting bugs.
> Cheers,
> Carl

Hi Carl,

Thank you for looking into this. I moved on from KDE and Kontact months ago and so cannot regenerate the issue. Sorry.

Cheers,
Bob
Comment 3 Claudio Cambra 2023-02-06 17:42:17 UTC
Hi, sorry to hear that Bob. We will be closing the issue due to lack of info, but if you try Kalendar again and encounter this issue please feel free to post to this bug report or open a new one
Comment 4 Bob Mattes 2023-02-06 19:03:12 UTC
(In reply to Claudio Cambra from comment #3)
> Hi, sorry to hear that Bob. We will be closing the issue due to lack of
> info, but if you try Kalendar again and encounter this issue please feel
> free to post to this bug report or open a new one

Thanks. Will do.