PT9 on Linux--not working [SOLVED]

Question

I’m transitioning to Linux from Win7 (at its end of support…). I have seen mixed messages about PT9 working in Wasta Linux, so I decided to give it a try. It installed fine, and has even grabbed a few updates (as recently as yesterday), but it has never opened: I get a splash screen, with “Loading…” progress bars, and then… nothing. There’s no evidence of it in System Monitor (looking for a “Main” item with the command “/usr/bin/mono --debug /usr/lib/Paratext9/Paratext.exe”, similar to the one that appears when I run PT8 ["/usr/bin/mono --debug /usr/lib/Paratext8/Paratext.exe"]).
Q: does PT9 run in Linux? If yes, what do I need to do to get it to finish loading?

舊文章 - 以原文顯示

Answer 1

Yes, PT9 is running well in Wasta for a number of my colleagues; well
enough that it is being sent “home” with relatively inexperienced
computer users. You might try this: Hold down the Shift key as you click
the PT9 launcher icon. Keep Shift held down until you receive a message
asking if you want to reset PT to default settings. Then answer Yes or
OK. This will reset some PT settings but it will not remove your
registration info or any saved desktop layouts–you can re-apply a saved
layout after PT reopens (with no project or resource windows open).

If this doesn’t work, check to be sure all the PT9 dependencies are
installed and up-to-date. But I think if you are receiving PT9 updates
that this will be true.

KimB
Pacific Area Language Technology Coordinator
SIL International
Language Technology Consultant (LSS)
SIL Papua New Guinea
[Email Removed]

舊文章 - 以原文顯示

Comments

Thanks KimB–keeping the Shift key /held down/ was the trick! I got a “Select language” screen, and then away it went. So simple, but so far from obvious… Anyway, thank you again!

Paul

舊文章 - 以原文顯示

Answer 2

I have Wasta Linux on a virtual machine and Paratext 9 opens. My Wasta Linux version is 18.04. My system monitor shows the command you are expecting when Paratext is running. If I have system monitor when I start Paratext it shows a process “paratext9” /bin/bash/usr/bin/paratext while Paratext is loading.

I don’t know what to suggest to get you out of this state where it will not open.

舊文章 - 以原文顯示

Comments

Thanks sewhite. At least I know it’s /supposed/ to work.

舊文章 - 以原文顯示

Answer 3

from the command line/terminal can you run

paratext9 --debug

This will dump a bunch of info to the terminal, which may provide more info.

There is also a log file that can be examined:

Type the following into a terminal to find it:
find ~/.local/share -name "ParatextLog.log"

舊文章 - 以原文顯示

Comments

Hi hindlemail,

Thanks for the commands. Here are the results, for anyone that can make sense of them…

Paul@Paul-X250:~$ paratext9 --debug
Mozilla Roots Importer - version 3.2.8.0
Download and import trusted root certificates from Mozilla’s MXR.
Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD licensed.

Importing certificates into user store…
Import process completed.

(1,2): warning CS0105: The using directive for `System’ appeared previously in this namespace
Checking for ParatextProjects.
Apport Ignore file doesn’t need updating.
Updating EncConverts Registry Keys
SLT Resources already Installed.
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for ‘Paratext.LibronixSantaFeTranslator.SantaFeFocusMessageHandler’ threw an exception. —> System.EntryPointNotFoundException: RegisterWindowMessage
at (wrapper managed-to-native) Paratext.LibronixSantaFeTranslator.SantaFeFocusMessageHandler:RegisterWindowMessage (string)
at Paratext.LibronixSantaFeTranslator.SantaFeFocusMessageHandler…cctor () [0x00028] in /home/build/paratext-geckofx-linux-9.0/Paratext/LibronixSantaFeTranslator/SantaFeFocusMessageHandler.cs:73
— End of inner exception stack trace —
at Paratext.LibronixSantaFeTranslator.LiSaFT…ctor () [0x0004c] in /home/build/paratext-geckofx-linux-9.0/Paratext/LibronixSantaFeTranslator/LiSaFT.cs:55
at Paratext.LibronixSantaFeTranslator.LiSaFT.set_IsEnabled (System.Boolean value) [0x00010] in /home/build/paratext-geckofx-linux-9.0/Paratext/LibronixSantaFeTranslator/LiSaFT.cs:73
at Paratext.MainForm.UpdateState () [0x0037e] in /home/build/paratext-geckofx-linux-9.0/Paratext/MainForm.cs:2698
at Paratext.MainForm…ctor () [0x00259] in /home/build/paratext-geckofx-linux-9.0/Paratext/MainForm.cs:165
at (wrapper remoting-invoke-with-check) Paratext.MainForm:.ctor ()
at Paratext.Program.Main (System.String[] args) [0x00138] in /home/build/paratext-geckofx-linux-9.0/Paratext/Program.cs:166

Not sure what to do with the log file. Upload it somewhere?
Paul

舊文章 - 以原文顯示

Answer 4

No need to upload the log file, that is enough info.

So, somehow, sync with logos is enabled, even though it’s not supported on Linux.

Try starting paratext holding down the shift key.

This should ask you if you want to reset settings…

舊文章 - 以原文顯示

Comments

No dice… Any other suggestions? Is there something I can do on the Logos side of things? Not that I’ve got Logos sorted out yet…

舊文章 - 以原文顯示

Answer 5

Did it ask you to reset? and that didn’t work, or did it just not show the reset dialog?

you could try doing it manually:

cd ~/.local/share/United\ Bible\ Societies/

Ensure you in the correct place before running rm
ls
rm *

舊文章 - 以原文顯示

Comments

It didn’t even show a reset dialog. Splash screen: yes; reset: no.

舊文章 - 以原文顯示

---

Perhaps the key is to keep the SHIFT key held down until the reset
message appears? hindlemail, you might include this detail in your instructions
as a general rule.

KimB
Pacific Area Language Technology Coordinator
SIL International
Language Technology Consultant (LSS)
SIL Papua New Guinea
[Email Removed]

舊文章 - 以原文顯示