Bug 912138 - *** glibc detected *** /usr/bin/kmail: double free or corruption (fasttop):
Summary: *** glibc detected *** /usr/bin/kmail: double free or corruption (fasttop):
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: 18
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: 2013-02-17 20:22 UTC by Patrick C. F. Ernzer
Modified: 2014-02-05 19:15 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 19:15:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
output in .xsession-errors when the crash happened (107.88 KB, text/plain)
2013-02-17 20:22 UTC, Patrick C. F. Ernzer
no flags Details
file saved by kcrash (11.94 KB, text/plain)
2013-03-02 16:15 UTC, Patrick C. F. Ernzer
no flags Details

Description Patrick C. F. Ernzer 2013-02-17 20:22:57 UTC
Created attachment 698622 [details]
output in .xsession-errors when the crash happened

Description of problem:
kmail recently started crashing shortly after launch (it seems to at least query some of the favourite folders) 

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

How reproducible:
always

Steps to Reproduce:
1. launch kmail (from the command line, or KDE menus or from kontact)
2. wait a while (not enough time to get very far in the settings menu)
  
Actual results:
kmail crashes

Expected results:
no crash

Additional info:

Comment 1 Rex Dieter 2013-02-17 22:42:06 UTC
A backtrace (from abrt or drknoqi) or even a valgrind log would help identify what's going on here.

Comment 2 Patrick C. F. Ernzer 2013-03-02 16:15:57 UTC
Created attachment 704494 [details]
file saved by kcrash

I could not find drknoqi (with "yum whatprovides \*/drknoqi")
abrt never sees the crash (I guess because kcrash traps it)

If the attached is useless, please do tell what I should collect.

Comment 3 Kevin Kofler 2013-03-02 22:51:34 UTC
> I could not find drknoqi (with "yum whatprovides \*/drknoqi")

That's because Rex misspelled it. :-) It's called drkonqi, it's part of kde-runtime, and it's the user-visible part of KCrash, so in fact you've already been using it.

Comment 4 Fedora End Of Life 2013-12-21 11:29:33 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 5 Fedora End Of Life 2014-02-05 19:15:08 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.