Bug 533648 - [abrt] crash detected in mono-core-2.4.2.3-2.fc12
Summary: [abrt] crash detected in mono-core-2.4.2.3-2.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 558548
Alias: None
Product: Fedora
Classification: Fedora
Component: mono
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Xavier Lamien
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:073137f4a2484d579610e142bbf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-08 05:15 UTC by phanisvara das
Modified: 2010-03-04 22:58 UTC (History)
19 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-04 22:58:43 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (9.18 KB, text/plain)
2009-11-08 05:15 UTC, phanisvara das 		no flags Details
View All

Description phanisvara das 2009-11-08 05:15:27 UTC 
abrt detected a crash.

How to reproduce
-----
1. installed beagle
2. as soon as beagle tries to extract docs, mono crashes
3.

Attached file: backtrace
cmdline: mono --debug /usr/lib64/beagle/DocExtractor.exe /home/phani/Documents/from_seva/CDJ 22/Sita-pati/Devotees_are_made_one_at_a_time--final.doc
component: mono
executable: /usr/bin/mono
kernel: 2.6.31.5-122.fc12.x86_64
package: mono-core-2.4.2.3-2.fc12
rating: 3
reason: Process was terminated by signal 11
Comment 1 phanisvara das 2009-11-08 05:15:31 UTC 
Created attachment 368002 [details]
File: backtrace
Comment 2 phanisvara das 2009-11-11 12:18:44 UTC 
this crash happens only when SELinux is active. a few days ago i disabled SELinux via it's conf file, and since then beagle runs fine.
Comment 3 Arnaud Siminski 2010-03-04 06:07:38 UTC 
Hi all, 
SELinux is disactived and beagle still does not index files. Any idea ? 
Keep on the good work
Comment 4 Christian Krause 2010-03-04 22:58:43 UTC 
Most likely this is a dupe of 558548: Beagle's DocExtractor does not work in 64bit installations due to a library lookup problem.

*** This bug has been marked as a duplicate of bug 558548 ***
Note You need to log in before you can comment on or make changes to this bug.