abrt 1.0.3 detected a crash. How to reproduce: I think this was generated by Beagle Comment ----- I think I just logged in :-) There seems to be a missing file: mono --debug /usr/lib64/beagle/DocExtractor.exe /tmp/tmp26b203a4.doc Unhandled Exception: System.DllNotFoundException: libbeagleglue at (wrapper managed-to-native) DocExtractor:wv1_init () at DocExtractor.Main (System.String[] args) [0x0002c] in /builddir/build/BUILD/beagle-0.3.9/tools/DocExtractor.cs:105 rather than the segfault but the file is installed as best I can tell: locate libbeagleglue /usr/lib64/beagle/libbeagleglue.so /usr/lib64/beagle/libbeagleglue.so.0 /usr/lib64/beagle/libbeagleglue.so.0.0.0 Attached file: backtrace cmdline: mono --debug /usr/lib64/beagle/DocExtractor.exe /tmp/tmp26b203a4.doc component: mono executable: /usr/bin/mono kernel: 2.6.31.12-174.2.3.fc12.x86_64 package: mono-core-2.4.3.1-1.fc12 rating: 4 reason: Process was terminated by signal 11 (Segmentation fault)
Created attachment 386665 [details] File: backtrace
(In reply to comment #0) > mono --debug /usr/lib64/beagle/DocExtractor.exe /tmp/tmp26b203a4.doc > > Unhandled Exception: System.DllNotFoundException: libbeagleglue > at (wrapper managed-to-native) DocExtractor:wv1_init () > at DocExtractor.Main (System.String[] args) [0x0002c] in > /builddir/build/BUILD/beagle-0.3.9/tools/DocExtractor.cs:105 This error message indicates that this is a problem in the beagle package itself. The root cause is, that the shared library is just referenced by DllImport as "libbeagleglue" and so without any further information the mono runtime tries to search it in the standard search paths like /usr/lib64 etc. However, the file really resides in /usr/lib64/beagle/ . Most other mono-based programs like gtk-sharp2, gsf-sharp, gnome-sharp etc. solve this by installing the glue libs like libgtksharpglue-2.so directly into %{_libdir}/ Additionally the *.config file should map the generic library name used in the source code (e.g. "libbeagleglue" to a versioned! library name like "libbeagleglue.so.1") > rather than the segfault > > but the file is installed as best I can tell: > > locate libbeagleglue > /usr/lib64/beagle/libbeagleglue.so > /usr/lib64/beagle/libbeagleglue.so.0 > /usr/lib64/beagle/libbeagleglue.so.0.0.0 -> moving to beagle component
*** Bug 564112 has been marked as a duplicate of this bug. ***
*** Bug 545111 has been marked as a duplicate of this bug. ***
*** Bug 550194 has been marked as a duplicate of this bug. ***
*** Bug 550195 has been marked as a duplicate of this bug. ***
*** Bug 547412 has been marked as a duplicate of this bug. ***
*** Bug 540012 has been marked as a duplicate of this bug. ***
Hello maintainer? This is trivial to fix. What is the problem?
*** Bug 533648 has been marked as a duplicate of this bug. ***
I have looked a little bit more into the issue: There are lots of broken references to external (ELF) libraries. In order to fix them, it is necessary to create a bunch of *.config files which use the dllMap directive to map the used names from the DllImports to the real libraries in the system. To get an idea which files are needed, please look into https://launchpadlibrarian.net/26859744/beagle_0.3.9-3ubuntu1.diff.gz and search for "dllMap". In Fedora it is additionally necessary to pre-process these files in order to ensure that the absolute paths like <dllmap dll="libbeagleuiglue" target="/usr/lib/beagle/libbeagleuiglue.so"/> are fixed for x86_64. Juan, do you think you'll find some time to work on this?
How to reproduce ----- 1. I was closing applications when this happened. I think it might have been OpenOffice closing. 2. 3.
*** Bug 575033 has been marked as a duplicate of this bug. ***
How to reproduce ----- 1. I booted my PC, logged in, and started Firefox (which needed proxy passwords). I don't know when this crash happened. 2. 3.
How to reproduce ----- 1. Save a doc file. 2. 3.
How to reproduce ----- 1. Open Firefox 3.5.8 2. Open this link: https://www.bsi.bund.de/cae/servlet/contentblob/474906/publicationFile/31314/Richtlinien_Word_zip.zip 3. Choose "Save to file" Comment ----- Always if I try to download this above link. The download succeed and everything is fine, but this error pops up.
How to reproduce ----- 1.Install mono-core 2.Wait... 3.Goats! Comment ----- yum -y install mono
Comment ----- while beagle indexing
Comment ----- Beagle seems to go on indexing, however.
How to reproduce ----- Cannot send you description to reproduce it as I was not able to see the problem witi beagle in backgruond
How to reproduce ----- 1. No idea at all 2. 3.
Comment ----- Probably trying to record a user object in the user library
How to reproduce ----- 1. I am uncertain how this happened, but I think it occurred on BOOTUP. 2. 3.
How to reproduce ----- 1. No specific actions produced this crash 2. 3.
How to reproduce ----- 1. No specific actions were being done when this crash occured 2. 3. Comment ----- Appears to be a crash that occurs when beagle is indexing my files in the background. Adobe Acrobat files (.pdf) seem to cause the problem.
How to reproduce ----- 1. I don't know what caused this. 2. 3.
How to reproduce ----- 1. I don't know what caused this. 2. I THINK I was saving a document in Office Writer. 3.
How to reproduce ----- 1. Beagle was indexing the home directory 2. 3. Comment ----- Mono was running in the background
*** Bug 593156 has been marked as a duplicate of this bug. ***
*** Bug 595396 has been marked as a duplicate of this bug. ***
*** Bug 615049 has been marked as a duplicate of this bug. ***
Package: mono-core-2.6.4-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. gonna attach the document that made it fail. 2. 3.
Package: mono-core-2.6.4-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. zero-byte documents trigger it. the file in the mono --debug cmdline is a zero-byte file.
*** Bug 619107 has been marked as a duplicate of this bug. ***
Package: mono-core-2.4.3.1-2.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. I saved a new Open Office Writer document. 2. 3. Comment ----- ANY time a document is written to the drive, changed, or Open Office Writer is opened, the mono fault occurs.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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. Thank you for reporting this bug and we are sorry it could not be fixed.