Summary: | Signal 11 crash when loading a molecule (mulecular viewer) | ||
---|---|---|---|
Product: | [Applications] kalzium | Reporter: | David <DavidLBarbour> |
Component: | general | Assignee: | Kalzium Developers <kalzium> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | JKrollmann |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mandriva RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
David
2008-01-30 19:27:31 UTC
Thank you for the report. Could you please specify the exact version of OpenBabel you are using? Is that a 64bit system? Hm. We've already seen this issue many times before in Avogadro. In addition to what Carsten asked, please: 1) look for the directory containing the file named "cmlformat.so" on your hard drive (you can use 'slocate' or 'find'). 2) set the BABEL_LIBDIR environment variable to this directory Example: export BABEL_LIBDIR=/usr/lib/openbabel/2.1 if the file /usr/lib/openbabel/2.1/cmlformat.so exists. 3) rerun Kalzium if that works, you can set this variable permanently by e.g. editing your .bashrc. Hm. Thinking more about it -- I don't think that what I suggested in #2 will work. Could you 1) still tell me whether cmlformat.so exists on your hard drive 2) install openbabel (the program -- the library you already have) and post here the output of "babel -Hcml" Yes, I use a 64bit system. OpenBabel version is 2.1.1-1mdv2008.0 I cannot find the cmlformat.so file and "openbabel -Hcml" says: "Format type: cml was not recognized". *** Bug 160104 has been marked as a duplicate of this bug. *** Hello In the last couple of days we added a lot (a lot!) new stuff and fixes in the relevant code. Could you retry with KDE 4.1 as of today or later if this bug is still valid? I simply cannot reproduce here. Carsten No, there is the same problem with the same error-message. I tried to use a Nvidia-card instead of a Ati-card Now I tried with the 4.1 unstable Jan, The above discussion with Peter clearly shows that, at least in his case, the problem is caused by OpenBabel format plugins not being found. OpenBabel is the library we use to handle 80+ chemical file formats, and each format is handled by a separate plugin. Nothing to do with OpenGL and graphics cards. First check if this is also your problem: see comment #3. Then we can talk :) This is basically a distibution issue (or because you selfcompiled). We kind of fixed it. If the OB install is incomplete (for example you have libopenbabel installed but not openbabel itself (eg. the "babel" tool)) you get a popup with this warning: "Cannot read the file format. Check your OpenBabel installation." This should prevent any such crashes. |