FaithLife-Community
Wine log no longer showing in console after launching in the CLI
Reproduction steps:
./main.py -C --debug- observer Logos launches in the background without any wine logs shown on the console
Can reproduce on 6f084de324d7ea610a4563ecdb38354e81271c69 but not df7505b9e5012d76d31054e31f5868bbb88f63ec
Ideally when launching -C --debug I want to see all the logs
Feel free to close this issue if you disagree, it is more of a matter of opinion
In the recent commits, I moved the wine info to its own log in ~/.local/state/Logos_on_Linux/ so that we can separate wine debug info from LLI debug info as per #153.
I also wanted a way for non-technical users to be able to access this info easily when sharing an issue.
-D can also break the TUI.
Relevant code is here:
https://github.com/FaithLife-Community/LogosLinuxInstaller/blob/9c3f5ff858c462784421f4d5cea8c7f5ba2958a8/wine.py#L261-L269
See this commit: 6f084de324d7ea610a4563ecdb38354e81271c69
We could add an optarg I suppose to disable the use of the config, or we could have it work only for TUI and GUI and not CLI?
I suggest that when using -D|--debug we can opt to send wine output to the terminal in addition to the wine log file. This would not work from TUI, as mentioned, but it would from GUI and CLI instances. I can imagine a user doing LogosLinuxInstaller --run-installed-app --debug to see both installer debug logging and wine logging (What level would be good for WINEDEBUG? fixme-all,err-all?).
We should also consider simply disabling/ignoring -D for TUI, since I don't think we want to try to incorporate all that output into the few stdout lines that show up in the TUI window (is that only for curses anyway?)
A workaround is to start the command as you show, then tail the wine.log file, either in a new terminal or in the same one once Logos launches and the command prompt returns:
$ ./LogosLinuxInstaller -C --debug
$ tail -f ~/.local/state/FaithLife-Community/wine.log