[Scribus] document fails to open

[Peter Linnell]

On Wed, 2004-06-09 at 18:21, Franky Van Liedekerke wrote:
> On Wed, 09 Jun 2004 18:14:28 -0400
> Peter Linnell <scribusdocs at atlantictechsolutions.com> wrote:
> 
> > On Wed, 2004-06-09 at 07:49, Franky Van Liedekerke wrote:
> > > Hi all,
> > > 
> > > I had this with a recent document made in 1.1.5: it failed to open in
> > > 1.1.6 (scribus would eat up all cpu but show nada). It seemed one page
> > > was the cause of this: I found this by importing page by page in
> > > another document until I found the page that caused troubles.
> > > 
> > > Now again, a document created with 1.1.6 fails to open in 1.1.7 (again
> > > all cpu gets eatn but nothings shows, and I have to kill scribus).
> > > System is fedora core 2, all patches applied. Scribus version used:
> > > the supplied rpm for 1.1.7. When starting scribus on the command line,
> > > I get:
> > > 
> > > QSettings: failed to open file
> > > '/usr/lib/qt-3.3/etc/settings/qt_plugins_3.3rc' Could not find
> > > platform independent libraries <prefix> Could not find platform
> > > dependent libraries<exec_prefix> Consider setting $PYTHONHOME to
> > > <prefix>[:<exec_prefix>]'import site' failed; use -v for traceback
> > > 
> > > but this seems irrelevant to my document not opening.
> > > How can this be tracked down/handled/solved?
> > > 
> > > Franky
> > > 
> > > ______________________________________________________________________
> > FC-1 and FC-2 have different versions of python and in different
> > locations.
> > 
> > You would be better off rebuilding the Source RPM
> > 
> > you can get the fedora-rpmdevel package which helps creating a buildroot
> > in $home.
> > 
> > Cheers,
> > Peter
> 
> Hi Peter,
> 
> is this relevant for the not opening of the file?
> 
> Franky
> 
> ______________________________________________________________________
Possibly. I rarely have issues with opening older files. In fact I know
Franz keeps some older versions around, just for testing. 

I've got files from 0.5.6 which open fine here. (Ironically, it is a
training manual for Acrobat 5 ;)

Without a sample doc, it is hard to diagnose.

Cheers,
Peter