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