Bug 6387 - Clicking on new mail on kontact crashes the software with no bt
Summary: Clicking on new mail on kontact crashes the software with no bt
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-09 17:06 CEST by Lucien XU
Modified: 2012-06-20 11:37 CEST (History)
1 user (show)

See Also:
Source RPM: kdepim4-4.8.4-1.mga3.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Lucien XU 2012-06-09 17:06:16 CEST 
Description of problem:
While clicking on "new mail" or "reply" on kontact, the application just closes. Running it in a debugger gives no debug trace. Only "*** KMail got signal 11 (Exiting)" Even if it is a segmentation fault, it cannot be caught

Version-Release number of selected component (if applicable):
kontact-4.8.4-1.mga3

How reproducible:


Steps to Reproduce:
1. Open kontact
2. click on new mail
3. kontact closes
Comment 1 Lucien XU 2012-06-10 10:35:10 CEST 
It seems to be related to nepomuk. Since I have some problems with it, when I killed nepomukserver, the mail editor works again.
Comment 2 John Balcaen 2012-06-17 16:49:44 CEST 
I'm not running cauldron but there's some know issue introduced by the combination of kde 4.8.4 & soprano 2.7.6 (so basically nepomuk :p)due to « wrong » changes pushed in kdelibs. It has been reversed, i'll try to add them & push them just in case.

CC: (none) => balcaen.john

Comment 3 John Balcaen 2012-06-17 19:59:31 CEST 
Fwang did add thoses patch to kdelibs, can you still reproduce with kdelibs 4.8.4-4 ?
Comment 4 Lucien XU 2012-06-20 11:37:09 CEST 
It seems to be better. I did not have any crash for the 5 minutes I tested. I close it as fixed, but may repoen it if needed.

Thanks about solving this bug :)

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.