1.2.6 Scrivener for Linux Released (NOT LATEST)

Scrivener Scrivener on Linux (Unofficial)
19

Thank you, lemke0.

When Scrivener is offered for sale to Linux users, I will gladly pay. I have bought Apple and Windows versions.

20

Rockin’, thanks. Two minor things that are–for practical purposes–non-issues, but that you might want to be aware of, are that when installing over 1.2.5, it still says, “Same version is installed,” indicating that the internal version number in the .deb file is still 1.2.5, and that the expiration date still shows as July 31, 2012.

Again, not that either has any practical effect–Just thought you’d want to know.

21

From this I would guess you have forced Scrivener to run under KDE?

Could you tell me how?

Thanks, Bwdjai

22

Try opening a terminal and running Scrivener like this:

unset QT_PLUGIN_PATH Scrivener

You might need to change the Scrivener line to point to where your Scrivener is located.

If it works, it looks like KDE’s environment variables are interfering with Scriveners version of QT’s variables.
A quick fix would be a script that starts Scrivener by running those commands (what I’m doing), a better fix would be to have Scrivener (un)set a bunch of environment variables at launch (but it’s been a long time since I’ve done any programming so no idea how easy that is to do in KDE).

Rod

23

Thanks Rod, that didn’t help.

I had a developer friend take a quick look and happy that he managed to fire it up I left contented.

However, if I try to open a file, other than one I have saved, Scrivener exits.

By saving a file and then changing the name of my exisiting.file to the saved.file name I have manage to open and continue to edit my original manuscripts. I can then open a ‘recent file’ which Scrivener knows all about?? :confused:

This is not the end of the world and in fact I am happy just to have it back running.

Hopefuly someone will come up with the definitve answer in the meantime as I really do like KDE ande do not want to go back to gnome just for this … :wink:

24

Was about to install this but Ubuntu Software Centre gives me this error

Guessing this is nothing too serious…

Anyway I’m on 64-bit so I needed to force architecture…it installed, but does not work…
Scrivener doesn’t even start up…how much longer till a bulletproof commercial version is released? Slightly impatient, but then I have half a project that I can’t even work on…I’ll try to roll back to 1.2.5, I only started getting the RTF reader error today, after months without problems

Okay that’s weird, removed 1.2.6,
reinstalled 1.2.5, got RTF reader error again
removed 1.2.5
reinstalled 1.2.6
works perfectly!

25

I am a newbie to ubuntu, Just bought a new laptop and when I try to install scrivener it goes to software center but it seems like it never recognizes it’s installed. I didn’t have any trouble installing on an ubuntu desktop…any ideas?

Thanks in advance for any help

26

Are you using the Unity interface on laptop?

I had the same install problem on desktop w/ Unity, but laptop worked no problem using Gnome 3.
I logged out of Unity on desktop, logged back in under Gnome, and the install worked just fine via Software Centre.

27

I installed it on 12.4 under Unity and it worked fine. Of course, I had the previous version installed and so may have already made the configuration changes required.

28

I installed in 12.04 under gnome. The application doesn’t show up in the software center, but it is installed and works fine.

29

[/quote]
Thanks so much teem, your suggestion worked!! Thanks again

30

Seems to work for me on 64 bit Kubuntu 12.04. I have a bunch of 32 bit compatibility libraries installed, though.

Still, excited to try it out for my next documentation project.

31

You might also want to grab gdebi-gtk so you can easily install local .deb files without invoking the software center. Search for gdebi in the Software Center, or enter this at the commandline:

sudo apt-get install gdebi

Then you can install any local .deb file by using the command

gdebi-gtk (package name.deb)

For example:

gdebi-gtk scrivener-1.2.6-beta.deb
32

Well, here’s a how-de-do; just been trying to install Linux Scriv on an old laptop running 32bit Kubuntu 12.04.1 LTS, a fresh install thereof. Even before installing Scriv, there’s some weirdness with crash reports that don’t tell you what they’re reporting on, or why; a glimpse at the Kubuntu forums reveals the problem to be mildly common, but as yet unanswered. (Indeed, a general air of discontent seems to cling to KDE at the moment, which is regrettable; it’s so much nicer than Gnome.)

Anyway, long story short: trying to run Scriv under KDE was getting me the ‘mixed libraries’ error message that we’ve all learned to loathe. After an assortment of buggerings about, I noticed someone in another thread recommending trying another window manager package for testing purposes, so I installed XFCE4, logged in to an XFCE session, and Scriv works just fine. Back into KDE, still broken.

I claim no expertise, here, but I think this is further evidence that the problem lies somewhere in KDE…

… but as I can run in XFCE for the few days I need to be without my usual writing machine (desktop), I’m nowhere near as panicked as I was a few hours ago. :slight_smile:

33

Having dropped to the terminal to try to run Scrivener and posting my error codes in various other forums I am fairly confident that the problem lies with the QT libraries.

It would appear that Scrivener is intended for use with Qt 4.8.0, while KDE (well mine at least ) has 4.8.1.

So I guess it’s just wait for L+L to update which is a bind as having found and fallen in love with KDE I find myself in a dilemma.

If anyone has any ideas I am open to try them…

Regards

Bwdjai :slight_smile:

34

See if what I did works for you:

  • Install xcfe (sudo apt-get install xcfe4)
  • Reboot machine
  • Choose xfce session at login
  • Try Scrivener

Works for me, even if still broken in KDE… :slight_smile:

35

Sincerely gratefull Paul!
That has given me a good work around.
I did spot the slight spilling error :laughing:

           Many thanks.  

                    Bwdjai (Frank)
36

I’m a little skeptical, unless XFCE uses 4.8.0 or earlier. (Could one of you who has it installed check?) If so, then it’s a change that just happened between 4.8.0 and 4.8.1. I’ve got 4.6.2 here, and haven’t had a hiccup.

So if we determine which libraries it is, simply by comparing versions of libqt4 that we have, perhaps that could help make the debugging easier.

37

Same. I’m able to run it without the QT_PLUGIN value unset, and I’m using KDE 4.9.1. I’ve got some other crash issues with the add file dialogue, but I think that’s a Scrivener bug, not me. (I’ve seen that bug before in the 1.1 build.)

Scrivener shouldn’t be touching the system QT libraries, though, since it comes with its own. At least mine point to the Qt libraries in the Scrivener directory.

For instance:

linux-gate.so.1 (0xf778e000)
libQtSolutions_MMLWidget-2.4.so.1 => /opt/scrivener/bin/…/lib/libQtSolutions_MMLWidget-2.4.so.1 (0xf774c000)
libQtWebKit.so.4 => /opt/scrivener/bin/…/lib/libQtWebKit.so.4 (0xf61b9000)
libphonon.so.4 => /opt/scrivener/bin/…/lib/libphonon.so.4 (0xf6164000)
libQtSvg.so.4 => /opt/scrivener/bin/…/lib/libQtSvg.so.4 (0xf610c000)
libQtSql.so.4 => /opt/scrivener/bin/…/lib/libQtSql.so.4 (0xf604c000)
libQtXml.so.4 => /opt/scrivener/bin/…/lib/libQtXml.so.4 (0xf6008000)
libQtGui.so.4 => /opt/scrivener/bin/…/lib/libQtGui.so.4 (0xf54b3000)
libQtNetwork.so.4 => /opt/scrivener/bin/…/lib/libQtNetwork.so.4 (0xf5396000)
libQtCore.so.4 => /opt/scrivener/bin/…/lib/libQtCore.so.4 (0xf50b0000)
libpthread.so.0 => /usr/lib32/libpthread.so.0 (0xf5060000)
libstdc++.so.6 => /usr/lib32/libstdc++.so.6 (0xf4f78000)
libm.so.6 => /usr/lib32/libm.so.6 (0xf4f39000)
libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0xf4f1e000)
libc.so.6 => /usr/lib32/libc.so.6 (0xf4d74000)
libfontconfig.so.1 => /usr/lib32/libfontconfig.so.1 (0xf4d3b000)
libfreetype.so.6 => /usr/lib32/libfreetype.so.6 (0xf4c9f000)
libXext.so.6 => /usr/lib32/libXext.so.6 (0xf4c8d000)
libX11.so.6 => /usr/lib32/libX11.so.6 (0xf4b56000)
libXrender.so.1 => /usr/lib32/libXrender.so.1 (0xf4b4c000)
libgio-2.0.so.0 => /usr/lib32/libgio-2.0.so.0 (0xf49f5000)
libgstapp-0.10.so.0 => /usr/lib32/libgstapp-0.10.so.0 (0xf49e8000)
libgstinterfaces-0.10.so.0 => /usr/lib32/libgstinterfaces-0.10.so.0 (0xf49d7000)
libgstpbutils-0.10.so.0 => /usr/lib32/libgstpbutils-0.10.so.0 (0xf49b5000)
libgstvideo-0.10.so.0 => /usr/lib32/libgstvideo-0.10.so.0 (0xf4997000)
libgstbase-0.10.so.0 => /usr/lib32/libgstbase-0.10.so.0 (0xf4935000)
libgstreamer-0.10.so.0 => /usr/lib32/libgstreamer-0.10.so.0 (0xf484f000)
libgobject-2.0.so.0 => /usr/lib32/libgobject-2.0.so.0 (0xf4801000)
libgmodule-2.0.so.0 => /usr/lib32/libgmodule-2.0.so.0 (0xf47fc000)
libxml2.so.2 => /usr/lib32/libxml2.so.2 (0xf46ae000)
libgthread-2.0.so.0 => /usr/lib32/libgthread-2.0.so.0 (0xf46aa000)
librt.so.1 => /usr/lib32/librt.so.1 (0xf46a1000)
libglib-2.0.so.0 => /usr/lib32/libglib-2.0.so.0 (0xf45a8000)
libz.so.1 => /usr/lib32/libz.so.1 (0xf4591000)
libdl.so.2 => /usr/lib32/libdl.so.2 (0xf458b000)
/lib/ld-linux.so.2 (0xf778f000)
libexpat.so.1 => /usr/lib32/libexpat.so.1 (0xf4562000)
libbz2.so.1.0 => /usr/lib32/libbz2.so.1.0 (0xf4552000)
libxcb.so.1 => /usr/lib32/libxcb.so.1 (0xf4530000)
libffi.so.6 => /usr/lib32/libffi.so.6 (0xf4529000)
libpcre.so.1 => /usr/lib32/libpcre.so.1 (0xf44c4000)
libresolv.so.2 => /usr/lib32/libresolv.so.2 (0xf44ac000)
liborc-0.4.so.0 => /usr/lib32/liborc-0.4.so.0 (0xf441c000)
libXau.so.6 => /usr/lib32/libXau.so.6 (0xf4418000)
libXdmcp.so.6 => /usr/lib32/libXdmcp.so.6 (0xf4410000)

38

Since we’re reaching the extent of my actual knowledge (and you seem to know more than me!), that implies that the folks who are having issues with KDE (or with mixed libraries at all) are having an issue at compile (install?) time, where it’s pointing to the system libraries instead of Scriv’s. Do I have that right?