View Single Post
Old 10-04-2014, 10:04 AM   #95
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,705
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by blackest View Post
It is odd but it is a 32bit system which I should have said. Thankyou for taking time to investigate this (it also has 2gb ram).
I haven't extensively tested the 32-bit version of my Linux binary packages, but I use the 64-bit version every day on Linux Mint with no segfaults.

The only segfaults I've ever gotten with either of those packages have been when closing Sigil--and that was always limited to the first time it was run.

As far as debugging (without compiling your own debug version), about all you can is run it using gdb and see if the backtrace after the segfault yields anything useful. Also, the launch script (/usr/local/bin/sigil) has a line commented out that would allow one to do some debugging of the launching (or the availability) of the various Qt plugins.

Also keep in mind those packages are "unofficial"
But by all means, if you discover any details about the segfault, please consider sharing them in the stickied thread for those builds. I'd love to be able to fix it if at all possible.

Last edited by DiapDealer; 10-04-2014 at 10:09 AM.
DiapDealer is online now