Also had a problem installing via the Ubuntu Software Centre, however the command line worked: -
sudo dpkg -i scrivener-1.1.0-beta.deb
Or for 64-bit linux: -
sudo dpkg -i --force-architecture scrivener-1.1.0-beta.deb
Installed .deb file on CrunchBang linux using GDebi. Runs perfectly so far. Joy! 
I just installed Scrivener for the first time. Worked fine in Fedora 16 x86_64, just had to:
yum install gstreamer-plugins-base.i686
Haven’t tested it at all, just wanted to verify that it at least loads without complaining, once the 32-bit libraries it wants are available.
For other fedora / gnome-shell users, to make it available in the gnome-shell search, I created the file:
~/.local/share/applications/scrivener.desktop
with these contents:
#!/usr/bin/env xdg-open
[Desktop Entry]
Version=1.0
Type=Application
Name=Scrivener
Exec=/home//opt/Scrivener/bin/Scrivener
Path=/home//opt/Scrivener
MimeType=x-scheme-hoofler/scrivener;
Terminal=false
Categories=Office;
StartupNotify=false
Ekotyk, have you tried the following command for your installation:
sudo dpkg -i --force-architecture scrivener-1.1.0-beta.deb
Rob gave these instructions last year for getting the 32-bit debs to load, and it just worked for me again in installing 1.1.0 onto my 64-bit Kubuntu system.
You can find some additional information about getting spellcheck working at:
robhamm.com/legacy/primary-c … ux-29-beta
And by the by, big thanks to Lee and Rob and everyone who is working on Scrivener and Scrivener for Linux. Much appreciated and my money is still sitting in my wallet waiting for an appropriate opportunity. 
sudo dpkg -i --force-architecture scrivener-1.1.0-beta.debThe above works fine for me under Ubuntu 12.04 beta 2 64-bit on two separate computers. Thanks. 
Quick edit: And I agree with the above poster – I’ve got my money ready and waiting for the final release as well. 8)
For anyone getting “Cannot mix incompatible Qt library” errors while running KDE (but not otherwise), the solution is to clean up your environment:
unset QT_PLUGIN_PATHYou could probably just add this to the Scrivener shell script. Note that you won’t want to stick this in your .profile, as it will make KDE unhappy.
Registered just to share this tidbit, and to thank L&L for supporting linux (albeit incipiently). I look forward to the working linux release.
Hmm… doing that isn’t helping. I edited the Scrivener script in /usr/bin and put that before the LD_LIBRARY_PATH line. That’s the right place, correct?
Er, did the 64-bit versions ever get released? I couldn’t find a link in this thread.
Been doing my writing in vi for two months now – there really needs to be a Linux version that doesn’t expire.
Agreed!
I remember reading something not long ago that the 64-bit betas are pretty much dead for the time being. Priorities, limited resources, etc.
Try PyRoom (pyroom.org), full screen edit, simple, easy to configure. Writes plain text files. There’s an Ubuntu PPA or you can just use the tarball. Anything - even gedit - is better than vi for real writing–unless you’re a certifiable vi wizard, of course. I say this as someone who has used vi since the early 80s. [my god, nobody’s that old…]
I’ve got the beta working on my 64-bit Ubuntu 10.04 system – everything but the spelling & PDF display works fine. I’ve even moved away from running my Windows XP virtual machine, where I have the official release. Ubuntu manages font hinting better, among other things.
Cheers,
Nathan
Did you try these instructions for getting either of the last two betas running on a 64-bit system?
robhamm.com/legacy/primary-c … ux-29-beta
And yeah, but Lee and crew want to make sure it’s bulletproof before officially releasing a Linux version. Considering Lee has said something about Fedora becoming his development platform of choice (or something like that, if I remember correctly), you can have confidence that those releases will keep coming until there finally is a full official Linux release. And eventually, an Android release, as well. In the meantime, free betas that last three months at a time isn’t bad. (Uh, you did know that the last beta ran until the end of March and this one runs until the end of June, right?)
If I missed anything here, I–as usual–blame the pain pills, rather than taking responsibility for my own actions.
You should just blame vic-k like the rest of us. It’s easier and requires less concern of what the pain pills make actually be causing you to type.
Or I could just blame the terrorists; that’s even easier. “Oops, typo! Damn terrorists.”
Jaysen, I would suspect that Rob, being a denizen of the Linux world, may not have trawled through the inconsequentia of the “And Now For That Latte” forum and other areas haunted by Vic-K’s various personas. As for the comparison of Vic-K’s personas and “damned terrorists” … I leave others to wrangle over that one. 
X
Mr. X, I offer the “how to stop forum spam” thread to Mr Hamm.
Perhaps someone could help me. I previously had Beta 1.1.0 installed and working on my ubuntu 11.10 machine. I then did a clean install of Ubuntu 12.04 and tried to reinstall Scrivener. Fail. The command line install seems to work, yet when I try to run Scrivener–nothing. After purging the software, I tried to just use the software center; it indicated that the program was installed yet it still offered to let me install it (suggesting, on the hand, that it had not installed). The gdebi installer gave me the same contradictory indications. In both cases, the icons for launching Scrivener appeared in my menus but when I tried to launch the programs–nothing. Command line launch of program–nothing. Anyone have any ideas. I hate to think I’d have to go back to Windows just to use this program.
A lot of us are having that problem with Ubuntu right now. It seems like Scrivener is using the system libraries, even though it has it’s own. Or, there is a strange combination that the system doesn’t like.
For now, you’ll have to go back to Windows. It will get addressed, we just don’t know when. Lee et al seem to be focused on the Windows updates right now, making sure everything is working for the next version. Even though Linux is a priority for them, right now we’re still at the bottom of the proverbial totem pole 
But if you have a modern machine (mine, for example, is 2 years old) you can install Windows in a virtual machine and run Scrivener there; you don’t have to literally “go back to Windows.” That’s what I’ve been doing. I use VMware (which is now open source and therefore free), but there are other alternatives. I connect Windows and Ubuntu files via Dropbox, so I can work in either environment. Needless to say I never use both at the same time. I use this instead of network shares because it backgrounds the synchronization. Knowing all of my files, including my automatic backup directory, are saved in the Dropbox cloud provides a certain measure of peace of mind.
I’m looking forward to the day when I won’t need to do this, of course.
Here’s a question: has anyone tried running the Windows beta on Wine?
I switch between the two, and it requires a modern version of wine (at least 1.3.5 if not 1.5.whatever) and a bunch of overrides with winetricks. PDFs used to work, but don’t after they switched to quickpdf. If you search, I’ve dumped a bunch of tips gleaned to get various things working (like snapshots, which requires dx9 and a few overrides in the library tab.)
appdb.winehq.org/objectManager.p … &iId=21780 Preliminary install steps there. I don’t think you need the Qt dll anymore. I didn’t put it in place before installing on my laptop, and it runs fine. You do need to follow the override instructions if you want to get Snapshots working and to register. (They’re on the 1.0 test data.)
I just used a clean install of Lubuntu 12.04 for my write group, and had no trouble with Scrivener in LXDE. Getting ready to do a clean install of vanilla Ubuntu (I personally dislike Unity, but Scrivener needs to work with it, so I’ll take one for the team.) to check that out. Is this problem unique to 64-bit systems? If so, I may have to try to dig out another machine from someplace or re-install VirtualBox, as I’m back to all 32-bit.