Which Linux distro do you use for Scrivener?

I just successfully installed it on a fully-updated Kubuntu system.
Haven’t had much chance to work with it, but everything appears to load correctly and the tutorial is there. :smiley:

Anytime. I’m glad it ended up being a simple fix. Good luck writing. =D

Bodhi Linux 3 RC 1 on an Acer 720 Chromebook.

Only problem with the Scrivener install was that it failed with a complaint about libgstapp-0.10.so.0 not being present.

After googling, I found that this is a component of libgstreamer, so I apt-got that and everything worked perfectly – didnt’ even have to reinstall the Scrivener deb.

The only problem I have is figuring out how to get a Control Home to work for Beginning / End of Document, and that’s a function of the restricted keyboard, not the Scrivener program.

Using 13.10 Saucy Salamander.

Will confess to being an absolute noob on Linux, (as in installed it yesterday, literally) and all the extra steps to install/configure almost everything is already making me tired, but my Scrivener does work like a charm now I’ve got it installed. I’ve high hopes that the frustration will decrease with experience, coming from Mac I’ve been utterly spoiled by simplicity for many years.

Many thanks to the people who went to the trouble of writing that step by step install guide, never could’ve done it without that.

:smiley:

I am using Arch with Gnome3 , but I have only just discovered Scrivener and have yet to explore it properly.
I will post if I have any problems. :slight_smile:

p.s. Daniwrites,
I have recently moved from Ubuntu-based distros to Arch and I am sure with a little perseverance you will get a great deal more from Linux than with a Mac.
I still have a Mac in my studio but seldom use it now and also have LinuxMint on a seperate hard-drive.
Anything you need to know about Linux, just google it and you should get an answer easily enough.
Have a good day. :smiley:

You may under estimate the word in bold. As a unix guy for a large company it is easy for me to agree with you. It just might be that you and I have a natural aptitude or learning style that makes this easier for us than others. For folks that see computers as “fancy paper”, they will likely get no “more” from any OS than an other. As a matter of fact they my have the opposite experience than you or me because

Maybe my uses are esoteric, but most useful information is buried behind many posts that aren’t all that helpful. Again, look at the answer from someone who is new… apt vs yum isn’t a big change if you are familiar with package managers, but it is frightening compared to a double click.

That said, a bit of work and note taking can make linux a wonderful platform for anyone.

Heh, my FIL just installed Ubuntu on a mac of his wanting to learn linux. I’m wondering if we should keep some liquid courage on hand (for him, that is) when he tries to do the “./configure && make && sudo make install” thing for the first time. :slight_smile:

The problem with Linux is that to know how to do more than the basics (that is, where you really learn to control the OS) takes a working knowledge of linux. “Just read the man page” doesn’t really do much good, if you’re just starting out. If you’re not sure of what the problem is, finding an answer can be difficult.

(And here’s where I insert a plug for linuxquestions.org. It’s got a pretty good community–so long as systemd isn’t discussed–and any issue I’ve asked about has had a prompt and intelligent reply. It’s also the “unofficial official” slackware forum, for what it’s worth.)

RTFM is the silliest concept.

yes, folks should do some basic leg work. But until every stinking document details all the concepts and provides context for the proper use of those concepts, you can not chastise the novice. They may not even know what manual to look read.

This is one of the biggest L&L lessons. They (and other fora members) answer every question no matter how repeat and obvious. Every noob is a noob. Be nice to them and hold their hand.

As to the FIL, take a truly educational approach. It’s what I do. An hour or two discussing things like AT&T unix, C, the history of shells, then the advent of PC and the horror of System0-9 and (MS|PC)DOS/OS2. This will loop you back to the BSD/MINIX/LINUX world. I’ve found that this approach sets folks in the mind of “traditional explorer” and increases their tendency to think of the problem as “learn the classic approach”.

My “teaching” approach for noobs uses the following segments (omit what isn’t needed or just a brief overview):

  1. History
  2. What is a system?
  3. What does the OS really do?
  4. How you talk to an OS, shells and basic commands
  5. System space vs user space
  6. Networks
  7. The internet is a big network
  8. The UIs: Console and X windows
  9. How to use Google.

That and lots of liquid courage.

Heh, I’ll need some if he ever needs to compile a kernel. :wink: Not hard, just a lot of moving parts, and lots of places where things can go wrong in a scary way.

Do people still do that for every day use?

I do it for embedded stuff, but thats to get small space and faster GPIO. Why would you do that as a casual user?

Not hard? I’ve never done it myself because I’ve had no need to, but all the books I’ve read make it sound like one of the easier things to compile. =P

I can say as someone who has been using Linux for years that a person who just needs a computer to work can find most anything they need built into the more popular Linux distros. Everything I’ve had to compile or do research on has been for niche projects I was working on.

As for compiling a kernel he might want to do something like install security enhanced linux or something. Perhaps he may decide that he wants some more features of the kernel added in or a patch he saw somewhere that he thought was snazzy. I doubt it’s much an everyday user will need. Crazy things happen though.

I can think of lots of reasons to need compilation of modules. there isn’t much that is in user space that needs a full kernel build though. most of the security tools are modular.

I get it for non-casual users. Seems like kernel builds are “the tales of old men* in suspenders”

[size=70]* No woman would be caught dead in suspenders.[/size]

I just installed Scrivener 1.6.* in a Debian-machine 7.6 64b, with MATE for environtment.

I am installing dictionaries now, and I tried open one of my proyects under Windows, with success. Only I missed can change the language (menues, etc.) to Spanish, as in Windows.

Linux Mint 17 64-bit

I bought the mac version of scrivener two years ago and am happy with it. But since I’m jumping ship from mac I want to put my vote in for the linux version.

LMDE Cinnamon (Debian 3.11.8-1)
Seems to work well on Mint. Had a challenge at first installing, but I reinstalled and it has (knock on wood) worked well.

Xubuntu 14 on an old Samsung NC10 netbook. Installed on count one-two, no hitch whatsoever.

NC10 is the last mobile computer I’ve seen which has a normal keyboard. I really hate those modern island type disasters which are now called keyboards and installed in all laptops. Now it kind of looks like I’m stuck with this old machine. :slight_smile:

Actually I have two Scriveners on it, because Xubuntu is in dual boot with Win XP originally installed on it. I just usually prefer to boot into Xubuntu, I like the feel of it.

Ubuntu, 14.04, with Unity.

Whoa, talk about topic creep! Although to me fair, most “What distro are you using” forum topics do end up devolving into a “Linux isn’t a good desktop OS!” argument thread. Such is life.

I’m using Scrivener for Linux 1.7.2.3 beta (64 bit), running on Linux Mint 17 XFCE. I am happy to report that I am having zero issues! I had seen quirks and minor issues in previous versions of Scrivener, but not anymore. It is rock-solid, and I’m in love!!! Color me happy!

Here’s a screenshot of my utilitarian but insanely effective Writing setup:

Just installed Scrivener yesterday, and going through the tutorials.
I’m running Fedora 20.

I’m running it on Linux Mint, in the Mate environment. (On a lenovo T61) Worked like a champ all through NaNo, no problems to speak of during 50,000 words.