On 3/17/12 6:01 PM, john Culleton wrote: > On Sat, 17 Mar 2012 10:56:41 -0400 > Gregory Pittman <gpittman at iglou.com> wrote: > >>> >> here's a mini-tutorial on backtrace: >> >> you need to have gdb on your system. >> >> then in console, type 'gdb /your/path/to/scribus1.50/bin/scribus' >> then type 'run' >> after the crash, type 'bt' and you get the backtrace >> >> Greg > > Here's an update. I built a new Slackware partition and got 1.5.0 > to compile and work. But that version won't work on my old > partition. So there is something that is called by Scribus 1.5.0 > that I have incautiously updated, maybe GTKMM. The same thing is > not called by 1.4.x. > > I'll do the backtrace bit and try to narrow it down. Worst case > I'll just replace the libs etc. on the old partition with those > on the new one.
If you are doing this kind of thing, you are likely breaking a lot. You should not just randomly copy executables or libraries between 2 different systems. This sort of process is likely where your problem has started. Stop trying to fix the Scribus issue, and fix the system. Craig
