| Summary: | [abrt] evolution-2.32.2-1.fc14: __libc_message: Process /usr/bin/evolution was killed by signal 6 (SIGABRT) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Yann Droneaud <yann> | ||||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 14 | CC: | lucilanga, mbarnes, mcrha | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:1b1978fc7a447af2e7edf85508f42479a1c8657a | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-04-01 05:43:00 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Yann Droneaud
2011-03-30 08:14:47 UTC
Created attachment 488680 [details]
File: backtrace
Created attachment 488684 [details]
Content of .xsession-errors
This is probably related to nss update : I didn't restart evolution after the latest update. > 00400000-00404000 r-xp 00000000 fd:01 28605 /usr/bin/evolution (deleted)
> 00603000-0060c000 rw-p 00003000 fd:01 28605 /usr/bin/evolution (deleted)
Thanks for a bug report. The above is shown in your .xsession-errors file, so it seems to me that evolution package was updated too. I'm afraid that if it's not reproducible (without doing downgrade/update), then it can be caused by the change of underlying binaries/libraries while evolution was running, which makes sense it crashes, because new compilation with source code which changed will change also library binary format.
There is nothing to be done from the evolution itself, for this kind of issue, this is more system thing (from my point of view), where system tries its best to update files and keep "old" application running.
I didn't find similar bug upstream, thus my question is, is this anyhow reproducible, please?
It's not reproducible, so let's close this bug. If it happen again, I will reopen it. OK, thanks. |