Celestia icon indicating copy to clipboard operation
Celestia copied to clipboard

No logs output

Open Askaniy opened this issue 1 year ago • 6 comments

The complete absence of console output of those compiled Celestia versions I'm testing, applies to munix9's qt5 build for openSUSE Tumbleweed and Levin's build, tested on Windows 11. The --log option to save in a file works only on Linux.

Askaniy avatar Mar 05 '23 17:03 Askaniy

have you tried to find the file? i'm afraid it's written into wrong location while i did my best to ensure it's written to the current dir

375gnu avatar Mar 06 '23 07:03 375gnu

What file name you suggest to search? On Linux, I usually launch Celestia in /usr/share/applications (via icon) or ~ folders, so it would be inconvenient for me to save logs in the current folder. I expect them to be output to the console. Just tested, celestia-qt command with no options not shows or saves logs in any folder. Here are the logs that are obtained using the --log option if they can help: logs.txt

Askaniy avatar Mar 06 '23 10:03 Askaniy

just to clarify. in your 1st message are you talking about in-application console ``` or about output to log file (--log option)?

375gnu avatar Mar 06 '23 10:03 375gnu

In-application console is not affected, I meant external output. Just to clarify, is the output to the console supposed with no options?

Askaniy avatar Mar 06 '23 10:03 Askaniy

No, console is always written.

So, regarding your log file, run celestia-qt --log celestia.log then look for celestia.log file. By default it should be in the starting directory, but AppImage and windows may alter this.

375gnu avatar Mar 06 '23 10:03 375gnu

  • --log works well on Linux and by default uses current console directory as it should
  • --log doesn't work at all on Windows
  • console not written in both cases

If I'm not mistaken, the Linux build that I use in not AppImage, but classic installation

Askaniy avatar Mar 06 '23 12:03 Askaniy