[Scribus] latest scribus segfaults

[Atlantic Tech Solutions]

On Thu, 2004-03-04 at 19:31, ffdjm at alaska.net wrote:
> After experiencing segfaults with scribus-1.5 I downloaded the latest
> version, cvs 03.03.2004.
> 
> Again, scribus segfaults immediately.
> 
> Earlier versions ran ok (and were very useful).
> 
> environment:
>   Qt-3.3.0
>   gcc-3.3.2
>   python 2.2.3
> 
> I tinkered with the configure script to get gcc to add debugging code
> and finally got this after the latest core dump:
> 
> ======================================================================
> 
> [ffdjm at donna Scribus]$ gdb -c core scribus/scribus
> GNU gdb 19991004
>   .....
> Core was generated by `scribus'.
> Program terminated with signal 11, Segmentation fault.
> Reading symbols from /usr/lib/libjpeg.so.62...(no debugging symbols found)...done.
> Reading symbols from /usr/local/lib/libart_lgpl_2.so.2...Error while reading shared library symbols:
> Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader.
> Error while reading shared library symbols:
> h       @??@/usr/local/lib/libtiff.so.3: No such file or directory.
> Cannot access memory at address 0x40098248
> 
> No stack.
> (gdb) 
> 
> ==========================================================================
> 
> I reinstalled libart2 (libart_lgpl-2.3.16) and the same thing happened.
> 
> What do I do now?
> 
> Douglas
> _______________________________________________
> Scribus mailing list
> Scribus at nashi.altmuehlnet.de
> http://nashi.altmuehlnet.de/mailman/listinfo/scribus
> 

Which distro?

Do you have required everything in:

http://ahnews.music.salford.ac.uk/scribus/documentation/index-2.html#ss2.2

and 
http://ahnews.music.salford.ac.uk/scribus/documentation/compile-cvs.html

The other potential source of crashing is dodgy fonts. Have you
installed some recently from free font collections on the web ?

Hope that helps,
Peter