Description of problem: SciDAVis fails to start with latest muParser installed (versions below) Version-Release number of selected component (if applicable): muParser 1.32-1.fc11 SciDAVis 0.2.3-11.fc11 - this combo fails How reproducible: Always Steps to Reproduce: 1. Update F11 fully 2. Start SciDAVis in terminal: 3. See in terminal: scidavis: Symbol `_ZTVN2mu6ParserE' has different size in shared object, consider re-linking terminate called after throwing an instance of 'mu::ParserError' Aborted (SciDAVis splash screen appears, but application window does not) Actual results: SciDAVis fails to start Expected results: SciDAVis starts Additional info: Removing muParser and SciDAVis then reinstalling with updates repo disabled allows SciDAVis to start ok. Not working combination: scidavis x86_64 0.2.3-11.fc11 muParser x86_64 1.32-1.fc11 Working combination: scidavis x86_64 0.2.1-1.fc11 muParser x86_64 1.28-5.fc11 Also works if SciDAVis is updated but not muParser, so this works ok: scidavis x86_64 0.2.3-11.fc11 muParser x86_64 1.28-5.fc11
I'm sorry but i have to orphan this package. I don't have any time for it.
scidavis-0.2.3-14.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/scidavis-0.2.3-14.fc11
Thanks for the update on this As far as I can tell (playing with a localinstall of the new scidavis package from koji) this requires sip-api(7) which is from sip-4.10 (also in Koji) but some existing packages such as PyKDE and PyQt depend on sip-api(6) This is no problem, as I have working scidavis with the old muParser in the meantime - just checking that you are aware.
(In reply to comment #3) > Thanks for the update on this > As far as I can tell (playing with a localinstall of the new scidavis package > from koji) this requires sip-api(7) which is from sip-4.10 (also in Koji) but > some existing packages such as PyKDE and PyQt depend on sip-api(6) > This is no problem, as I have working scidavis with the old muParser in the > meantime - just checking that you are aware. Normally I use qtiplot instead, the development in qtiplot seems much more active.
scidavis-0.2.3-14.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
Thanks for the update. After updating (scidavis-0.2.3-14.fc11.x86_64, muParser-1.32-1.fc11.x86_64) I get a segmentation fault when trying to open any SciDAVis project (app starts fine until trying to load a file). I have tried this also with a new file created in the updated SciDAVis - it appears to save ok but crashes when trying to open that same file. All I see in konsole is "Segmentation fault". Re comment #4 - I just checked QtiPlot again, it does seem to have progressed since last time I looked (when I switched to SciDAVis). However, it is inconvenient when I have many plots in the SciDAVis format and cannot transfer them, only the raw data as an ascii file :-(
(In reply to comment #6) > Thanks for the update. After updating (scidavis-0.2.3-14.fc11.x86_64, > muParser-1.32-1.fc11.x86_64) I get a segmentation fault when trying to open any > SciDAVis project (app starts fine until trying to load a file). I have tried > this also with a new file created in the updated SciDAVis - it appears to save > ok but crashes when trying to open that same file. All I see in konsole is > "Segmentation fault". > > Re comment #4 - I just checked QtiPlot again, it does seem to have progressed > since last time I looked (when I switched to SciDAVis). However, it is > inconvenient when I have many plots in the SciDAVis format and cannot transfer > them, only the raw data as an ascii file :-( The problem maybe related to qt 4.6 http://sourceforge.net/tracker/index.php?func=detail&aid=2935369&group_id=199120&atid=968214
(In reply to comment #7) > The problem maybe related to qt 4.6 > http://sourceforge.net/tracker/index.php?func=detail&aid=2935369&group_id=199120&atid=968214 Yeah, looks that way. Presumably have to wait for a new upstream release then?
(In reply to comment #8) > (In reply to comment #7) > > The problem maybe related to qt 4.6 > > http://sourceforge.net/tracker/index.php?func=detail&aid=2935369&group_id=199120&atid=968214 > Yeah, looks that way. Presumably have to wait for a new upstream release then? I'll try to get this problem solved this or next weekend.
This seems fixed with newest update: Name : scidavis Arch : x86_64 Version : 0.2.4 Release : 1.fc11 (new release from upstream - thanks for getting it packaged)