Sigil segfaults on startup

[GoogleCodeExporter]

What steps will reproduce the problem?

From menu:
1. Try to start Sigil from menu
2. Sigil silently starts ... and then disappears

From command line:
1. @prompt, enter > "/opt/sigil/sigil.sh"
2. Prompt reappears after a "Segmentation fault" message

Using valgrind (via alleyoop front-end):
1. Run&trace "/opt/sigil/sigil.sh"
2. Fails at the following point: (full tracelog also attached)
   ------------------------------------------------------------
   Process terminating with default action of signal 4 (SIGILL)
     Illegal opcode at address 0x83FE3FF
     at 0x083fe3ff: xercesc_3_1::XMLInitializer::initializeTransService() (within /opt/sigil/sigil)
     by 0x083f842f: xercesc_3_1::XMLPlatformUtils::Initialize(char const*, char const*, xercesc_3_1::PanicHandler*, xercesc_3_1::MemoryManager*) (within /opt/sigil/sigil)
     by 0x0856f349: XercesExt::XercesInit::XercesInit() (within /opt/sigil/sigil)
     by 0x081d5fe1: main (within /opt/sigil/sigil)
   ------------------------------------------------------------

What version of the product are you using? On what operating system?
  New install via "Sigil-0.5.2-Linux-x86-Setup.bin"
  Xubuntu 11.10

Please provide any additional information below.
  Valgrind tracelog is attached.

Original issue reported on code.google.com by xpi6.d...@gmail.com on 18 Feb 2012 at 5:51

Attachments:

• Sigil-0.5.2-Linux-x86-Segfault-Valgrind.log

[GoogleCodeExporter]

Identical results for installs off "Sigil-0.4.905-Linux-x86-Setup.bin" & 
"Sigil-0.4.2-Linux-x86-Setup.bin", which have previously worked OK on another 
box.

Original comment by xpi6.d...@gmail.com on 20 Feb 2012 at 3:56

[GoogleCodeExporter]

> Identical results for installs off "Sigil-0.4.905-Linux-x86-Setup.bin" & 
"Sigil-0.4.2-Linux-x86-Setup.bin", which have previously worked OK on another 
box.

Those packages haven't changed. This is an issue with your system.

Original comment by john@nachtimwald.com on 20 Feb 2012 at 11:57

• Changed state: Invalid

[GoogleCodeExporter]

> ...which have previously worked OK on another box.
Sorry, I wasn't exactly clear: the other box was running Ubuntu 10.10.

> Those packages haven't changed. This is an issue with your system.
Yar, I sorta guessed that, the only question is whether it is a problem with 
Xubuntu in general (1), Xubuntu 11.10 in particular (2), or *my* Xubuntu 11.10 
specifically (3). Can you rule out (1), and possibly (2)? Also, if it comes 
down to (3) do you have any ideas as to what might be wrong, and what should be 
done to fix it?

Original comment by xpi6.d...@gmail.com on 21 Feb 2012 at 8:23

[GoogleCodeExporter]

Uninstall your existing sigil.  Re-install.  Make sure you start 
/opt/sigil/sigil.sh and not /opt/sigil.  You may need lib-nas or libaudio - see 
the FAQ.  Xubuntu works.

Original comment by meme90...@gmail.com on 21 Feb 2012 at 8:42

[GoogleCodeExporter]

0.5.2 was buit on Ubuntu 11.10.

Original comment by john@nachtimwald.com on 21 Feb 2012 at 12:35

[GoogleCodeExporter]

> Uninstall your existing sigil.  Re-install.  ...
Done & done! (Numerous times: that's how I tested the different versions).

> ... Make sure you start /opt/sigil/sigil.sh and not /opt/sigil.  ...
I assume you mean "... not /opt/sigil/sigil." and that has never been the 
problem (check the 4th line of the valgrind log).

> ... You may need lib-nas or libaudio - see the FAQ. ...
libaudio2 is installed.

> ... Xubuntu works.
OK, so that rules out case (1): sigil don't work on Xubuntu generally, but what 
about case (2): Xubuntu 11.10 particularly?

Going back to the segfault trace, I haven't looked at the sigil code yet; does 
the Xerces subroutine do anything that it could be borking on?

Original comment by xpi6.d...@gmail.com on 21 Feb 2012 at 5:06