Jindam,
This a good question that I would like to hear the answer to also.
In the meantime, I suggest that sometimes valuable troubleshooting
information can be had from the program itself, but it must be started
from an XTerm console to read it. In the past, I have discovered file
read errors and library problems using this method. Another possibility
is to create a script which opens LibreOffice, but redirects console
output to a file. Sometimes that works. However, if the program crashes,
that may not work either.
Good luck, and I hope someone responds with the answer to your question.
Girvin
On 7/21/22 11:18 PM, jindam, vani wrote:
i downloaded "Test file produced by EK RTF attached." and renamed "=_UTF-8_Q_test=2Ertf_=.bin" to
"91074.rtf" from bug #91074. for some reason file extension is .bin. all other file extensions are downloading
correctly. i tried to open in lo writer and it terminated my vnc session. i am running debian sid on userland app (android). so,
is there any way to capture some kind of logs. in my present setup its impossible to use gdb, strace, valgrind, etc..
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.