Bug 681481 - [abrt] evolution-2.32.1-1.fc14: giop_tmpdir_init: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Summary: [abrt] evolution-2.32.1-1.fc14: giop_tmpdir_init: Process /usr/bin/evolution ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c435ad73723eb18392b404ab36d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-02 10:20 UTC by Velska
Modified: 2011-03-03 07:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-03 07:10:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (18.54 KB, text/plain)
2011-03-02 10:20 UTC, Velska
no flags Details

Description Velska 2011-03-02 10:20:08 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 18988 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 11894784 bytes
crash_function: giop_tmpdir_init
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.fc14.x86_64
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1299060771
uid: 500

How to reproduce
-----
1. Trying to start Evolution normally
2. Doesn't happen often at all, not readily reproducible
3.

Comment 1 Velska 2011-03-02 10:20:11 UTC
Created attachment 481834 [details]
File: backtrace

Comment 2 Milan Crha 2011-03-03 07:10:50 UTC
Thanks for a bug report. This is under GConf, when trying to init CORBA, and even the abrt still doesn't allow posting errors from the .xsession-errors, then the log shows this issue:
> "Resource problem creating '%s'"
I suppose it was a temporary issue in your system, thus I'm closing this, also because you indicated it's not reproducible.


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