Running 1.0.1 on Kubuntu 10.04 and loving it. Installed the deb for 1.0.1 on another computer running Kubuntu 11.10 and while the install appeared to go fine and the program launches with no problem, I cannot open any projects, getting a segmentation fault and program crash. I can create, save, and export new projects, and can open with the “Recent Projects” option on the File menu, but File -> Open or Ctrl-O both lead to segfault and crash back to the CLI prompt from which I launched it.
Love it on 10.04 and will happily pay for the Linux version when it’s ready, but any ideas on what’s happening on 11.10?
Ditto. If the Lit&&Lat guys feel bad about it charging for beta software, then make it a token amount (ten bucks?) to get a non-expiring beta.
With the post-holiday work blitz now dying off, I’m starting to do more writing, and would like to know that my primary authoring tool is not going to stop working right when I’m in the thick of things.
+1 to this… I’m happy to pay or otherwise contribute to maintain reliable access to Linux Scrivener. I have WIndows in VirtualBox for site testing, but I’d really rather not spend any time there. It spoils the mood.
I wouldn’t mind paying a little bit if there were a way to guarantee that it’d work to a certain level on my distro/desktop. But that would be rather difficult. Beta is always going to be buggy in some ways of course, but for the past couple of months I haven’t been able to even load the program, for example. And I would have been extremely unimpressed if I’d paid for Scrivener only to have this sort of thing happening later.
OpenSuse 11.4 with KDE. I’ve had my work eaten a few times by earlier betas and then it was fine for a while. And then the last beta developed the qtlib bug a few weeks before the new one was due and refused to open. Someone in another thread made a script that made it open when run, but the templates wouldn’t work.
The templates seem to be randomly working again now and I haven’t changed anything else recently so there must have been some kind of update somewhere. Now it all seems to be running normally again as far as I can tell, but I have to go into /bin and run the script from terminal as root every time I want to open it. Anyone have any idea how to make a desktop link to it that will run it as root from terminal?
This should make a desktop link - it calls kdesudo, which is the preferred way with KDE as your WM. Please note you’ll need to edit the icon file path and (possibly) the path to Scrivener. I attached the icon I use (I don’t think it’s official, but I like it.)
Disclaimer: I’m not affiliated with L&L. They can change things at any time. I bear no responsibility for anything that happens when you follow these instructions, unless it is TOTALLY KEWL. That said, I’ve followed these instructions myself (Ubuntu 10.04|Openbox/Gnome 2) for both the tarball and the debian package.
These instructions should:
Install Scrivener on your Linux box.
Provide a launcher on your desktop or where a launcher like Kupfer/Gnome-Do/Launchy can get to it.
Provide an (unofficial) icon that I mocked up a while back with Tux on it.
If you’re using a tarball, read the quoted section below:
If you’re installing from a .deb, .rpm, etc, read the quoted section below.
Save the attached icon to /home/(your username)/.icons/Scrivener_Logo.png
Then create the file below. Edit the Exec name to match the location of your binary.
NOTE: You could instead have this file as
/home/(your username)/.local/share/applications/Scrivener.desktop
which won’t show up on your desktop, but will let most launcher applications easily find it. Or, if you installed from the .deb (I presume the .rpm is the same), the installed launcher is located at
/usr/share/applications/Scrivener.desktop
and you can edit that file with whatever text editor you like.
Some folks had problems on KDE running as a normal user. TRY RUNNING WITHOUT ROOT ACCESS FIRST. Running with root permissions is A Bad Idea (see http://www.psychocats.net/ubuntu/graphicalsudo for why this can end up borking your system.) Honestly, if you find that you’re having to run something like Scrivener as root, there’s a deeper problem with file permissions on your system. Seriously. (Or library variables, which might be why the KDE folks are having issues. Still…)
But… if you find that you will need root access, add gksudo (for Gnome) or kdesudo (for KDE) to the “Exec” line in the launcher above. Example:
FOR KDE:
Exec=kdesudo /usr/bin/Scrivener %U
FOR GNOME:
Exec=gksudo /usr/bin/Scrivener %U
Still having problems? Check the forums for help. There’s a wide variety of folks running a wide variety of flavors of linux, and if you manage to make it work, share what you did.
Just a note, it seems like it’s the Kubuntu users having issues. I’m using KDE under Arch linux and haven’t had issues, beyond some things I think are bugs. I’m not entirely sure what Kubuntu does differently, although one user was able to get it working after installing Limbo. (And I’m not sure what that game installed or changed to make it work. While I’ve played Limbo, I did it from my home directory.) For what it’s worth, I didn’t have to dork with the QT plugin variable to get it working.
I recently installed Mint 13 MATE. After trying it for a bit I installed KDE. Then I installed Scrivener and it has worked flawlessly except for the well known bugs.
And isn’t that the delight of Linux? I know that I’ve got a WHOLE mishmash of libraries that I’ve hacked together and not bothered to document. My computer is a finely-tuned precision instrument held together with duct tape.
Yup. Heck, I just set up a tiny (1mb) RAMDISK for some tempfiles because … well, because.
Though in many ways, there’s just as many problems with Windows, but people don’t see them the same way. WinXP/Vista/7… I remember having to have a thumbdrive full of VBRUN.dlls that people may or may not have when doing (informal, unpaid) tech support… Heck, look at all the websites that simply have drivers for download, and tell me Windows doesn’t have its own issues just like *nix.
The only OS I’ve ever worked on at all that did not have that issue was OSX, and that’s simply because the same company controlled hardware and software, which has its own problems.
Heh, not to start that flame war all over again, but OSX has its own issues, too. Especially with Mountain Lion and their attempt to close things off. (Good luck getting it to run on a mac that’s 3 years old… The hardware is perfectly capable, but you probably won’t have all the drivers you need.) My in-laws are diehard mac fans, and they’re (loudly) complaining about Mountain Lion.
