I don' know how LitNLat view you, but I don't consider you a user of supported / paid software. What you consider me is largely irrelevant. I am actually two people in L&L's eyes -- one of me is the user of the free version of Scrivener for Linux. The other bought the full version of the Window...

pigfender wrote: They've not "abandoned" Linux... they've never actively developed for it. The Linux version is unofficial, provided by the team out of the kindness of their hearts. This is not entirely correct. It was developed on cross-platform qt libraries, which is what made the port ...

Look, I don't want to be That Guy On The Forum, but I guess I will be... I'm getting a bit pessimistic about Scrivener on Linux. Based on past experience with great software on other non-mainstream operating systems (I don't think Linux quite fits that category any more, but it's close enough to rou...

I'm willing to bet it's because libaspell-dev isn't installed.

A number of us just went out and bought licenses for the Windows version. At one point in time it was better to run the Windows version via WINE anyway, especially if you were on a 64 bit system. Lately though I've been getting the feeling that interest in supporting Linux, unofficial or not, has fl...

do you have libaspell-dev installed? I think that's the one I always miss.

You're not going to find Scrivener in the Kubuntu repositories because it isn't free software. In order to be included in a base Ubuntu or Kubuntu distribution, it has to be distributed under the correct licenses. Scrivener is proprietary so you're not going to find it there. Also, the Linux Scriven...

Go to the 1.7.2.3 post above and download the deb. Mint is based on ubuntu so the deb should work.

Are there any plans to update to 1.8.5?

I use bitsync to create a shared folder between multiple computers which is where I keep all my Scrivener projects. Works pretty well.

1.7.2.3 might have fixed this problem, whatever it was. Didn't get a segfault after upgrading. Fingers crossed!

I now use a python script to quickly set/reset constants.py when troubleshooting python segmentation faults in different apps I'm testing/developing. But I've not yet hit a segmentation fault error in Scrivener. Is there any way to do this with a flag? It seems like the easiest way to handle this w...

and I can confirm that with the patch in, Scrivener closes correctly.

... found it in /usr/lib/python2.7/dist-packages/gobject

I don't have a constants.py in /usr/share/pyshared/gobject - I wonder if the problem is I'm missing some python resources Scrivener needs to run?