Bug 772719 - KMail segfaults randomly
Summary: KMail segfaults randomly
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-09 18:59 UTC by Markku Kolkka
Modified: 2013-02-13 23:24 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 23:24:47 UTC
Type: ---


Attachments (Terms of Use)
crash dump (5.05 KB, text/plain)
2012-01-09 18:59 UTC, Markku Kolkka
no flags Details
SIGBUS version of the crash (5.02 KB, text/plain)
2012-01-10 12:57 UTC, Markku Kolkka
no flags Details

Description Markku Kolkka 2012-01-09 18:59:48 UTC
Created attachment 551640 [details]
crash dump

Description of problem:
When running Kontact, I get repeated messages about KMail components crashing with signals 7 and 11. I can't see any clear correlation between crashes and what I'm doing at the moment.

Version-Release number of selected component (if applicable):
kdepim-4.7.4-1.fc16.x86_64

How reproducible:
random

Steps to Reproduce:
1. Open Kontact
2. Use the Email component (KMail) normally
  
Actual results:
Eventually a dialog alerting of a SIGBUS or SIGSEGV inside a KMail component appears

Expected results:
KMail runs without problems

Additional info:

Comment 1 Markku Kolkka 2012-01-10 12:57:32 UTC
Created attachment 551831 [details]
SIGBUS version of the crash

The crash appears to consistently happen in __memmove_ssse3() called from KMBox::MBox::purge

Comment 2 Martin Bříza 2012-04-26 11:35:58 UTC
Please, what exact type of processor do you use in your computer? 
It seems the application (or an underlying library) is using an incompatible instruction.

Comment 3 Markku Kolkka 2012-04-26 12:41:20 UTC
(In reply to comment #2)
> Please, what exact type of processor do you use in your computer? 

Intel Core 2 Quad Q6700:
$ cat /proc/cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 Quad CPU    Q6700  @ 2.66GHz
stepping        : 11

Comment 4 Fedora End Of Life 2013-01-16 19:41:16 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-13 23:24:51 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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