1.2.6 Scrivener for Linux Released (NOT LATEST)

[uriel1998]

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.

Thanks so much teem, your suggestion worked!! Thanks again

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:

Code: Select all

sudo apt-get install gdebi


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

Code: Select all

gdebi-gtk (package name.deb)


For example:

Code: Select all

gdebi-gtk scrivener-1.2.6-beta.deb


[paulgrahamraven]

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.

[Bwdjai]

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

[paulgrahamraven]

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

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...

[Bwdjai]

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

Many thanks.

Bwdjai (Frank)

[uriel1998]

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.

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.

[garpu]

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.

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)

[uriel1998]

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.

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?

[garpu]

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.

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?

Yeah I think that's what's going on. Other people using KDE aside from the kubuntu folks seem to be OK. One person on Kubuntu got it working by installing the game Limbo. After that, it worked, so some setting somewhere got changed that made Kubuntu and Scrivener work.

Although if Scrivener is still tapping into the system libs behind the scenes, then it's a bug. (And I've no idea how to test for that--I know what ldd says.) I do think it's using the system aspell, not the one that comes with it, so it still being tied to some system QT library isn't beyond the realm of possibility.

[uriel1998]

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?

Yeah I think that's what's going on. Other people using KDE aside from the kubuntu folks seem to be OK. One person on Kubuntu got it working by installing the game Limbo. After that, it worked, so some setting somewhere got changed that made Kubuntu and Scrivener work.

Another possibility - something set in the environment, since some people are having success running it as root (and AFAIK, using root's environment and libraries, not %USER%'s, right?).

So what would the differential diagnosis questions be to help track this down? In instructions that novices can follow? (I don't know how to run ldd properly, for example, but I can help clean up directions into a single post...)

[garpu]

Hrm. Simply doing "ldd Scrivener" as a normal user in the .../Scrivener/bin directory (wherever it's installed) should pull up a number of libraries and where they're being loaded from. But like with apsell (which I suspect is using the system one, since it didn't work until I had 32 bit aspell installed), it could be pulling in a system library silently. (That is, aspell should've worked without it being installed on my computer, since it's bundled with a version of aspell, like the Windows one.)

If they want strace dumps, it's strace -o file.txt /absolute/path/to/scriveners/binary

Here's how to get a core dump: http://stackoverflow.com/questions/1796 ... p-in-linux

Beyond that, I'm not sure I know enough about the inner workings of Scrivener to interpret the data.

But, yeah. Comparing root's environment and path to the user's is a start. Also groups. (For instance I always forget to put myself into the udev group, then can't mount anything.)

Edit for clarity: It seems like there are two big issues right now: 1.) Some KDE users are having conflicts with system libraries. (And Scrivener may be using system libraries it shouldn't) 2.) Some users on the 64 bit platform are having crash isses with the add file dialogue (and snapshot, loading multimedia files, etc.) I think the two issues are unrelated, only because I've seen the 2nd one before in the Windows version and in earlier linux versions.

[mojohn]

Hi. Installed 1.2.6 on a laptop running Ubuntu 12.04 64 bit. Everything seems to work fine with one big exception. When I import PDF files into the Research folder, the documents are recognized as "there", and have the proper page count. However, nothing shows in the window - just blank pages. Any thoughts on what the problem might be?

Thanks.

[garpu]

That's because the PDF handling stuff isn't in yet.

[uriel1998]

Hi. Installed 1.2.6 on a laptop running Ubuntu 12.04 64 bit. Everything seems to work fine with one big exception. When I import PDF files into the Research folder, the documents are recognized as "there", and have the proper page count. However, nothing shows in the window - just blank pages. Any thoughts on what the problem might be?

Thanks.

In the meantime, you may wish to try poppler-utils which has pdftotext and pdfimages to extract text and images, or pdftohtml from http://sourceforge.net/projects/pdftohtml/.

(Or in other words, that's why I as a user hadn't noticed the PDF stuff wasn't there yet. )

To install poppler-utils from the commandline for Ubuntu (and probably Debian as well):

Code: Select all

sudo apt-get install poppler-utils

Commandlines to try (because of layout issues, sometimes one works better than another):

Code: Select all

pdftohtml -c -i -zoom 1 "filename"
pdftohtml -i -noframes "filename"

pdftotext -layout "filename"
pdftotext "filename"

pdfimages -j "filename"

[Jeco]

Unfortunately, I tried all the suggestions brought up in this forum, but wasn't able to make it work in Kubuntu 12.10. Maybe Lee can take a look and points us to the right direction?

Thanks.