Bug 4654 - KMail encountered a fatal error and will terminate now.
Summary: KMail encountered a fatal error and will terminate now.
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-02-23 09:25 CET by Luan Pham
Modified: 2012-05-26 21:48 CEST (History)
4 users (show)

See Also:
Source RPM: kdepim4
CVE:
Status comment:


Attachments

Description Luan Pham 2012-02-23 09:25:13 CET
Description of problem: This for Mageia 2 Beta 1
Akonadi::SpecialCollectionsRequestJob::slotResult: Failed SpecialCollectionsRequestJob::slotResult "Unknown error. (Failed to fetch the resource collection.)"

Version-Release number of selected component (if applicable):


How reproducible: Every time start Kmail2


Steps to Reproduce:
1.
2.
3.
Comment 1 Manuel Hiebel 2012-02-25 00:29:12 CET
I can't reproduce with a new install (kde4 as default)

But I have found quickly http://forum.kde.org/viewtopic.php?f=20&t=95870

Keywords: (none) => NEEDINFO
Source RPM: kmail2(7749)/kdepimlibs => kdepim4

Comment 2 Luan Pham 2012-02-25 01:15:43 CET
This is for Kmail version 4.8.0-1.mga2 for Mageia 2 Beta 1 (Cauldron)
Comment 3 Marja Van Waes 2012-03-19 11:33:31 CET
see also https://bugs.mageia.org/show_bug.cgi?id=4983#c4

Maybe it is better not to try Kmail at all now, because of the mails you might lose if it starts working again.

cc'ing some KDE guys

@ KDE team

Can this bug be assigned to one of you (it is mikala's package)?

Keywords: NEEDINFO => (none)
CC: (none) => balcaen.john, juan.baptiste, lmenut, marja11

Comment 4 Marja Van Waes 2012-05-26 13:08:51 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 5 Luan Pham 2012-05-26 21:48:01 CEST
I thought I was close this out while ago.. It already fix.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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