Comment 2 for bug 1950056

Revision history for this message
tellapu (tellapu) wrote :

Thank you, Kenneth for the reply!

I have two problems to provide the "real" debug.log.

1. The path to the file contains spaces. I know it would be better all the folder names have no space and I have been working on it for the past 10 years but it is hard to replace them all one by one. (Or do you know a way to do it in one go?)
With which "letters" can I replace the space in the terminal command to be able to give the full path to the file?
As the same file is accessible through a symlink, I did the debug.log with this path which does not contain a space. Maybe it is still useful.

2. The log is 103.7 MB large and contains a lot of personal information with the folder paths it contains. Which part of the log do you need? Or is it possible to create a debug.log without all the folder-paths and file names?
The file I tried to restore is from the date of the fresh backup.
I deleted all the personal paths and replaced the name of the computer with "..." in some paths. Hopefully this is fine. Attached you find the cleaned log, maybe it is still useful.
The two lines for the missed file were the same as the others without any error.

I am looking forward to your feedback. I am eager to learn something.

Thanks a lot for your help!