Bug 676280 - [abrt] emelfm2-0.7.5-1.fc14: __libc_message: Process /usr/bin/emelfm2 was killed by signal 6 (SIGABRT)
Summary: [abrt] emelfm2-0.7.5-1.fc14: __libc_message: Process /usr/bin/emelfm2 was kil...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: emelfm2
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:38a152293301d56011fff3d1c02...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-09 10:29 UTC by Richard Ruhland
Modified: 2011-06-05 18:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-05 18:25:11 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (11.83 KB, text/plain)
2011-02-09 10:29 UTC, Richard Ruhland
no flags Details

Description Richard Ruhland 2011-02-09 10:29:21 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: emelfm2
component: emelfm2
crash_function: __libc_message
executable: /usr/bin/emelfm2
kernel: 2.6.35.10-74.fc14.i686.PAE
package: emelfm2-0.7.5-1.fc14
rating: 4
reason: Process /usr/bin/emelfm2 was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1297247026
uid: 500

How to reproduce
-----
1. new ACL
2.
3.

Comment 1 Richard Ruhland 2011-02-09 10:29:23 UTC
Created attachment 477783 [details]
File: backtrace

Comment 2 Christoph Wickert 2011-02-20 10:11:12 UTC
Thanks for submitting this crash report.

(In reply to comment #0)

> How to reproduce
> -----
> 1. new ACL
> 2.
> 3.

Can you describe this a little more in depth? Is this crash reproducable or does it only happen sometimes?

Comment 3 Christoph Wickert 2011-03-06 14:04:10 UTC
Can you please reply to my question? I fail to reproduce the crash.

Comment 4 Christoph Wickert 2011-03-28 00:49:13 UTC
Richard, any news here?

Comment 5 Christoph Wickert 2011-06-05 18:25:11 UTC
Sorry, but without more feedback there is not nothing I can do.


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