This particular problem is different from the 64-bit issues and the issues with modules within Scrivener, so because this title is most descriptive, I will post my investigations here, not in the thread that is more popular, more confused, and entirely unhelpful.
First, the specifics of what I’ve learned so far: the problem is KDE and it is intermittent across installs. It isn’t a problem with individual distros or 64-/32-bit.
What I suspect to be true. Either a particular install will run Scivener or it won’t; so far I haven’t seen a documented case where a non-functional system (with this error) was made functional. I don’t know for sure, but I strongly suspect that the reverse is also true: that a KDE install that works with Scrivener won’t suddenly stop working with this error.
The longer narrative:
I’m a long-time Fedora64 KDE user (I know, I know, but it involves my playing around with Centos back in 2005) and tried Scrivener out on my cheapo lappy running Fedora 64 and KDE. It worked fine. No issues, aside from lack of spellcheck and missing features I didn’t care to investigate.
I liked Scrivener well enough to try to install it on my desktop (F64, KDE). No go, with the QT version 4.8.0 vs. whatever-is-installed problem. Since that’s the system with the nice keyboard and the big screen, this rankled.
Another thing that rankled was I didn’t have google-earth working on either machine. I’d gotten it to work, in the past, on F64 but I’d forgotten how exactly and given up. The desktop was a newer install of F64, so I assumed the reason was that I had done so much work to the lappy trying out all the i386 compatibility packages.
Here’s a major piece of the puzzle for all of us. Because I don’t code, I’m very hazy about the logistics of getting a library to work. This is what I’m going to attempt to document and find a fix for. Back to the narrative.
So at this point I figured it was the old, intractable 64-/32-bit nonsense. When a newer version of Fedora came out, I put F32 on the desktop. Still the same problem. I searched around the web looking for information on why, but found little or nothing. I figured it was a Fedora problem. Because it seems like most of the software packaging for Linux versions are done in .deb and the non-Linux world seems to think Linux is all about Ubuntu, I decided to move my desktop to Kubuntu. When I installed Scrivener, I said, “Hey, new version (1.5), I’ll try that.”
Success!
So, at that moment I had a desktop Kubuntu 12.10 32-bit system with Scrivener 1.5.0.6 and a Fedora 16 64-bit system with Scrivener 1.2.6. Well, since I had confirmed that Kubuntu worked with Scrivener, I decided to update my lappy to match.
Failure! And swearing!
And yes, I have confirmed that with XFCE I can run Scrivener. But apart from this single issue, KDE is more flexible and more capable, and I’m not switching. Besides, there are quite a few KDE people out there that can’t get Scrivener to work on their system, and I’d like to figure out how to actually fix the problem.
So I’m going to clean and reinstall my lappy from scratch and take a very minimalist approach to tracking down the issue.