Bug 423505 - Akonadi Server Crashed whilst running in the background.
Summary: Akonadi Server Crashed whilst running in the background.
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: server (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-06-25 14:28 UTC by Simon Brown
Modified: 2022-11-11 05:20 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (83.57 KB, patch)
2020-06-25 14:28 UTC, Simon Brown
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Brown 2020-06-25 14:28:12 UTC
Application: akonadiserver (5.13.3 (19.12.3))

Qt Version: 5.12.8
Frameworks Version: 5.68.0
Operating System: Linux 5.4.0-37-generic x86_64
Windowing system: X11
Distribution: Ubuntu 20.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
 I was not using any PIM apps, browsing the web using firefox. I have IMAP, Carddav and caldav accounts in akonadi.


- Unusual behavior I noticed:
System became almost unresponsive, mouse moved very slowly

-- Backtrace (Reduced):
#6  0x00007fd0f4f3130f in charset_uninit () at ./mysys/charset.cc:925
#7  0x00007fd0f4f36823 in my_end (infoflag=infoflag@entry=0) at ./mysys/my_init.cc:200
#8  0x00007fd0f4ed4243 in mysql_server_end () at ./libmysql/libmysql.cc:202
#9  0x00007fd0f55c40ee in qLibraryEnd () at qsql_mysql.cpp:1243
#10 QMYSQLDriver::~QMYSQLDriver (this=0x7fd0a40b3d20, __in_chrg=<optimized out>) at qsql_mysql.cpp:1243


The reporter indicates this bug may be a duplicate of or related to bug 387393.

Possible duplicates by query: bug 421614, bug 387393.

Reported using DrKonqi
Comment 1 Simon Brown 2020-06-25 14:28:12 UTC
Created attachment 129675 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Justin Zobel 2022-10-12 03:50:14 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-10-27 05:04:03 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 Bug Janitor Service 2022-11-11 05:20:43 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!