Bug 1112013 - Crash in latest mariadb (10.0.11+) makes KDE's akonadi (kdepim) fail.
Summary: Crash in latest mariadb (10.0.11+) makes KDE's akonadi (kdepim) fail.
Keywords:
Status: CLOSED DUPLICATE of bug 1111191
Alias: None
Product: Fedora
Classification: Fedora
Component: mariadb
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Dorňák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-22 18:15 UTC by Martin Kho
Modified: 2014-06-27 09:46 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-27 09:46:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
mysql error log (150.74 KB, text/plain)
2014-06-22 18:15 UTC, Martin Kho
no flags Details

Description Martin Kho 2014-06-22 18:15:48 UTC
Created attachment 911171 [details]
mysql error log

Description of problem:
KMail's resource akonadi-imap fails to fetch mail. In the attached mysql log file - it seems - that this is caused by a crash in mysql-server.

Version-Release number of selected component (if applicable):
mariadb-server-1:10.0.11-1.fc21.x86_64 to
mariadb-server-1:10.0.12-1.fc21.x86_64

How reproducible:
always

Steps to Reproduce:
1. start KMail using imap
2. switch from some directories to some other directories
3. The message pane is empty and a error message appears on the statusbar.

Actual results:
KMail does not fetch/show messages

Expected results:
KMail fetches/shows messages

Additional info:

Comment 1 Jakub Dorňák 2014-06-23 14:59:53 UTC
Hi, this may be related to bug #1111191. Could You please try version 10.0.12-2.fc21?

Comment 2 Martin Kho 2014-06-24 07:36:40 UTC
Hi Jakub,

It looks indeed related to the gcc 4.9 issue. Build 10.0.12-2 works fine thus far. If something changes I'll let you know.


Thanks,

Martin Kho

Comment 3 Jakub Dorňák 2014-06-27 09:46:38 UTC

*** This bug has been marked as a duplicate of bug 1111191 ***


Note You need to log in before you can comment on or make changes to this bug.